User story (meta) #1040
Add possibility to delete an accepted node
| Status: | Released | Start date: | 2011-03-09 | |
|---|---|---|---|---|
| Priority: | 2 | Due date: | ||
| Assignee: | % Done: | 100% |
||
| Category: | Webapp - Node management | |||
| Target version: | 2.4.0~alpha1 | |||
| Needs translating: | No |
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
Associated revisions
Fixes #1040: Add a button to remove a node from Rudder
Issue #1040: technical review, formatting
Issue #1040: technical review: missing pattern matching case
Issue #1040: formatting
History
#1
Updated by Jonathan CLARKE almost 2 years ago
- Target version set to Ideas (2.3 specific)
#2
Updated by François ARMAND over 1 year ago
- Target version changed from Ideas (2.3 specific) to Ideas (2.5 specific)
#3
Updated by Jonathan CLARKE over 1 year ago
- Priority changed from N/A to 2
- Target version changed from Ideas (2.5 specific) to Ideas (2.4 specific)
#4
Updated by Jonathan CLARKE over 1 year ago
- Needs translating set to Yes
#5
Updated by Nicolas PERRON over 1 year ago
- Subject changed from Pouvoir supprimer un noeud accepté to Add possibility to delete an accepted node
- Description updated (diff)
#6
Updated by Nicolas PERRON over 1 year ago
- Needs translating changed from Yes to No
#7
Updated by François ARMAND over 1 year ago
- Target version changed from Ideas (2.4 specific) to 2.4.0~alpha1
#8
Updated by Jonathan CLARKE over 1 year ago
- Category set to Webapp - Node management
- 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.
#9
Updated by Nicolas CHARLES over 1 year ago
- Status changed from 2 to In progress
#10
Updated by Nicolas CHARLES over 1 year ago
- 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)
- 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
#11
Updated by Nicolas CHARLES over 1 year ago
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Applied in changeset 32c31555bb8905d700787cef4f698f63f3b4a6d2.
#12
Updated by Nicolas CHARLES over 1 year ago
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)
#13
Updated by François ARMAND over 1 year ago
- Status changed from Pending technical review to Pending functional review
Seems ok for me.
#14
Updated by Jonathan CLARKE over 1 year ago
- Status changed from Pending functional review to Released