Project

General

Profile

Actions
Copy link

User story #1040

closed

Add possibility to delete an accepted node

Added by Jonathan CLARKE almost 14 years ago. Updated almost 13 years ago.

Status:
Released
Priority:
2
Assignee:
Nicolas CHARLES
Category:
Web - Nodes & inventories
Target version:
2.4.0~alpha1
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

It could be necessary to delete a node from Rudder: for example if a test machine became non-existant (case of EC2's instance) or if an old machine is out of service.

  • Add a button "Remove from Rudder" in detail view of a node
  • After a click appears a popup asking confirmation: "Are you sure you want to remove this node from Rudder? This operation cannot be undone. Cancel / Yes, remove it"
  • Deactive the machine into LDAP base in order to be no more into the interface and be out of his groups

Related issues 1 (0 open — 1 closed)

Related to Rudder - User story #267: If a server is deleted/refuse, remove its trace everywhereRejected2010-05-24Actions
Actions
Copy link
 #1

Updated by Jonathan CLARKE over 13 years ago

  • Target version set to 10
Actions
Copy link
 #2

Updated by François ARMAND about 13 years ago

  • Target version changed from 10 to 24
Actions
Copy link
 #3

Updated by Jonathan CLARKE about 13 years ago

  • Priority changed from N/A to 2
  • Target version changed from 24 to 18
Actions
Copy link
 #5

Updated by Nicolas PERRON about 13 years ago

  • Subject changed from Pouvoir supprimer un noeud accepté to Add possibility to delete an accepted node
  • Description updated (diff)
Actions
Copy link
 #7

Updated by François ARMAND about 13 years ago

  • Target version changed from 18 to 2.4.0~alpha1
Actions
Copy link
 #8

Updated by Jonathan CLARKE about 13 years ago

  • Category set to Web - Nodes & inventories
  • Status changed from New to 2
  • Assignee set to Nicolas CHARLES

The aim of this user story in 2.4.0~alpha1 iteration is to validate how easy this is to do: it may be quite simple. If it is not, we must create new user stories to cut up the work, and consider planning them for the 2.4.0~alpha2 iteration.

Actions
Copy link
 #9

Updated by Nicolas CHARLES about 13 years ago

  • Status changed from 2 to In progress
Actions
Copy link
 #10

Updated by Nicolas CHARLES about 13 years ago

First test :
  • deleting entries from ou=Nodes and ou=Accepted Inventories,ou=Nodes and ou=Nodes Configuration is simply not enough
    The systemGroup "hasPolicyServer-root" isn't automatically updated (and the deployement fails because of that)
    The static group are not updated either, but it doesn't make the deploiement fails (but makes error when displaying the group)
So the point to validate are :
  • delete the node
  • delete the references to the node in the groups
  • delete the machine is it was only related to the node (container of the nodeId in ou=Accepted Inventories

And it would be great not to delete but to move in a Deleted Inventories branch

Actions
Copy link
 #11

Updated by Nicolas CHARLES about 13 years ago

  • Status changed from In progress to Pending technical review
  • % Done changed from 0 to 100
Actions
Copy link
 #12

Updated by Nicolas CHARLES about 13 years ago

Now we can delete a Node from Rudder.
The is indeed deleted, and not moved (there is no consensus on where and what to do). It is removed from :
  • Nodes
  • Nodes Configuration
  • The groups
  • The accepted inventories (it deletes the machine also)
Actions
Copy link
 #13

Updated by François ARMAND about 13 years ago

  • Status changed from Pending technical review to 10

Seems ok for me.

Actions
Copy link
 #14

Updated by Jonathan CLARKE almost 13 years ago

  • Status changed from 10 to Released
Actions
Copy link

Also available in: Atom PDF