Project

General

Profile

Actions

Architecture #24963

open

Persist compliance in base to know last state for a long time

Added by François ARMAND 6 months ago. Updated about 1 month ago.

Status:
Pending release
Priority:
N/A
Category:
Architecture - evolution
Target version:
Effort required:
Name check:
To do
Fix check:
To do
Regression:
No

Description

We need to persist compliance in base to be able to:

- restore the last known state when rudder start up
- more finely control persistance expiration by node.

More saillantly, we want to be able to address the case:
- a node compliance should be kept for several days when a node is not answering (typically: laptop when people go on hollidays),
- we want to avoid keeping run reports for more than a day for storage reason

That case is not possible without persistence in base.
Today, we compute compliance from expected reports and last run reports, always. If we don't have run reports, we don't have compliance.


Subtasks 14 (1 open13 closed)

Architecture #25038: Switch service related to compliance persistance from box to IOResultReleasedClark ANDRIANASOLOActions
Architecture #25057: There is now a loop in initializationReleasedVincent MEMBRÉActions
Architecture #25087: Remove unexpected interpretation choice for vars because it's not meaningful anymoreReleasedClark ANDRIANASOLOActions
Architecture #25088: Remove unused methods in ReportingServiceReleasedClark ANDRIANASOLOActions
Architecture #25092: Refactor CachedReportingService to make persistance simplerReleasedClark ANDRIANASOLOActions
User story #25120: Use node properties to decide how long compliance is validReleasedClark ANDRIANASOLOActions
Architecture #25219: Cache for node properties and hierarchiesPending releaseVincent MEMBRÉActions
Bug #25319: Inheritance error in properties stop running startupReleasedClark ANDRIANASOLOActions
Bug #25336: Inheritance errors in properties but policy generation succeeds and properties are not loadedResolvedActions
Architecture #25311: Remove expected reports from NodeStatusReportReleasedClark ANDRIANASOLOActions
Architecture #25396: Persist compliance in baseReleasedClark ANDRIANASOLOActions
Architecture #25421: User documentation on compliance persistanceReleasedClark ANDRIANASOLOActions
Architecture #25662: Images are not visible in compliance persistence documentationReleasedAlexis MoussetActions
Bug #25430: Property sub-key is used in place of name for lookupReleasedClark ANDRIANASOLOActions

Related issues 6 (0 open6 closed)

Related to Rudder - Architecture #24876: Add a compliance-by-feature logic and save compliance in baseReleasedVincent MEMBRÉActions
Related to Rudder - User story #4234: Add online|offline check before calculating statusResolvedActions
Related to Rudder - Architecture #24964: Remove unused tables about compliance and eventlogsReleasedVincent MEMBRÉActions
Related to Rudder - Enhancement #25649: Node with kept compliance should have the clock icon in node listReleasedFrançois ARMANDActions
Related to Rudder - Enhancement #25572: We need an icon and recognizable message style for node with expired maintained complianceReleasedClark ANDRIANASOLOActions
Related to Rudder - Bug #25650: Node in with no reports, pending and keep compliance lead to computation loopReleasedClark ANDRIANASOLOActions
Actions #1

Updated by François ARMAND 6 months ago

  • Related to Architecture #24876: Add a compliance-by-feature logic and save compliance in base added
Actions #2

Updated by François ARMAND 6 months ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions #3

Updated by François ARMAND 6 months ago

  • Related to User story #4234: Add online|offline check before calculating status added
Actions #4

Updated by François ARMAND 6 months ago

Actions #5

Updated by François ARMAND 5 months ago

  • Subtask #25038 added
Actions #6

Updated by François ARMAND 5 months ago

  • Subtask #25087 added
Actions #7

Updated by François ARMAND 5 months ago

  • Subtask #25088 added
Actions #8

Updated by François ARMAND 5 months ago

  • Subtask #25092 added
Actions #9

Updated by François ARMAND 5 months ago

  • Subtask #25120 added
Actions #10

Updated by François ARMAND 4 months ago

  • Subtask #25219 added
Actions #11

Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 8.2.0~alpha1 to 8.2.0~beta1
Actions #13

Updated by François ARMAND 3 months ago

  • Subtask #25311 added
Actions #14

Updated by François ARMAND 3 months ago

  • Subtask #25396 added
Actions #15

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 8.2.0~beta1 to 8.2.0~rc1
Actions #16

Updated by François ARMAND 3 months ago

  • Subtask #25421 added
Actions #17

Updated by François ARMAND 3 months ago

  • Subtask #25430 added
Actions #18

Updated by François ARMAND about 1 month ago

  • Status changed from In progress to Pending release

This was completed in Rudder 8.2.0.beta2

Actions #19

Updated by François ARMAND about 1 month ago

  • Related to Enhancement #25649: Node with kept compliance should have the clock icon in node list added
Actions #20

Updated by François ARMAND about 1 month ago

  • Related to Enhancement #25572: We need an icon and recognizable message style for node with expired maintained compliance added
Actions #21

Updated by François ARMAND about 1 month ago

  • Related to Bug #25650: Node in with no reports, pending and keep compliance lead to computation loop added
Actions #22

Updated by Vincent MEMBRÉ about 1 month ago

This bug has been fixed in Rudder 8.2.0~rc1 which was released today.

Actions

Also available in: Atom PDF