Project

General

Profile

User story #11748

Node lifecycle: add a node state

Added by François ARMAND over 1 year ago. Updated over 1 year ago.

Status:
Released
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
Suggestion strength:
User visibility:
Effort required:

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

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

Related to Rudder - User story #11811: Make node post-acceptation properties configurableReleasedActions
Related to Rudder - User story #12564: It's not possible to search Nodes by their node lifecycleReleasedActions
Related to Rudder - User story #12592: Node lifecycle: documentationReleasedActions

Associated revisions

Revision 92c51d4c (diff)
Added by François ARMAND over 1 year ago

Fixes #11748: Node lifecycle: add a node state

Revision 0eb62907 (diff)
Added by François ARMAND over 1 year ago

Fixes #11748: Node lifecycle: add a node state

History

#1

Updated by François ARMAND over 1 year ago

  • Status changed from New to In progress
#2

Updated by François ARMAND over 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1783
#3

Updated by François ARMAND over 1 year ago

  • Status changed from Pending technical review to Pending release
#4

Updated by François ARMAND over 1 year ago

  • Tracker changed from Architecture to User story

It is really an user story, not architecture.

#5

Updated by François ARMAND over 1 year ago

  • Related to User story #11811: Make node post-acceptation properties configurable added
#6

Updated by Vincent MEMBRÉ over 1 year ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.3.0~beta1 which was released today.

#7

Updated by Nicolas CHARLES about 1 year ago

  • Related to User story #12564: It's not possible to search Nodes by their node lifecycle added
#8

Updated by François ARMAND about 1 year ago

Also available in: Atom PDF