Project

General

Profile

Actions

User story #11748

closed

Node lifecycle: add a node state

Added by François ARMAND over 6 years ago. Updated about 6 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

We want to assign a "state" tag for nodes, which can then be used to decide Rudder behavior on several aspects, mainly:

- are they special rules to apply to the node ?
- are policies updated for that node?
- does the node takes part of aggregated compliance?

Ideally, of these aspects should be configurable by the user for each state (appart from "default" which must be identical to what a node state is on rudder today).

The status list should be extensible, but we want at least:

- init (an initializing state that could be automatically set just after node acceptation, or before the first inventory comes once we get the possibility to pre-define nodes)
- enabled / default: the default status for a node,
- decomissionning: meaning that the node is still managed by Rudder, but that it will be removed at some point (and so, perhaps some special rules should be applied).
- disabled : when a node should not be managed by Rudder. Mainly, that mean that the node doesn't have new policy generated for him, nor that it should be part of the aggreagated compliance reports

All these state are different from the action of deleting a node.

This ticket is just here to implements the data structures and internal algo.


Subtasks 5 (0 open5 closed)

Architecture #11750: Missing node state information in node detailsReleasedVincent MEMBRÉActions
User story #11809: Make node states behavior and name clearer ReleasedVincent MEMBRÉActions
User story #11810: Make node state configurable in node detailsReleasedVincent MEMBRÉActions
Bug #11842: Node in "ignored" state get a spinning wheel in place of complianceRejectedFrançois ARMANDActions
User story #11943: Display of node state could be improvedReleasedNicolas CHARLESActions

Related issues 3 (0 open3 closed)

Related to Rudder - User story #11811: Make node post-acceptation properties configurableReleasedFrançois ARMANDActions
Related to Rudder - User story #12564: It's not possible to search Nodes by their node lifecycleReleasedVincent MEMBRÉActions
Related to Rudder - User story #12592: Node lifecycle: documentationReleasedAlexis MoussetActions
Actions

Also available in: Atom PDF