Project

General

Profile

Actions
Copy link

User story #2888

closed

Be able to disable a node

Added by Matthieu CERDA about 12 years ago. Updated almost 7 years ago.

Status:
Rejected
Priority:
5 (lowest)
Assignee:
-
Category:
Web - Config management
Target version:
Ideas (not version specific)
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

It would be useful to be able to disable a node, with three use cases:
  • Disable the node completely, CFEngine included (abortclasses)
  • Use the node normally but ignore the compliance/logs
  • "Park the node": only give it base promises and act like if it were in no groups.

Related issues 2 (0 open — 2 closed)

Has duplicate Rudder - User story #2741: Be able to deactivate a node/group instead of a directive or ruleRejected2012-07-31Actions
Has duplicate Rudder - User story #4658: Option to disable a nodeRejected2014-03-19Actions
Actions
Copy link
 #1

Updated by Jonathan CLARKE about 12 years ago

  • Assignee deleted (François ARMAND)
  • Target version changed from 18 to Ideas (not version specific)
Actions
Copy link
 #2

Updated by Dennis Cabooter over 11 years ago

Would be a very nice to have.

Actions
Copy link
 #3

Updated by François ARMAND almost 8 years ago

Some more information on that: the first use case to that feature is to manage shut-down VMs that can be restarted.
When the VMis shut down, I don't want to generate new policies for it, and I don't want that compliance is impacted.

Actions
Copy link
 #4

Updated by Alexis Mousset almost 8 years ago

Actions
Copy link
 #5

Updated by Benoît PECCATTE almost 7 years ago

  • Status changed from New to Rejected

This is now implemented with node lifecycle.

Actions
Copy link

Also available in: Atom PDF