Actions
Architecture #18255
closed
Architecture #18092: Improve compliance performance and reliability
Don't compute runs information, but use data from rudder-relayd
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Fix check:
To do
Regression:
Description
Runs information were computed by webapp, but all info comes from rudder-relayd, making it more efficient
We should use this, and compute the compliance on the fly from it
Also, introduce events for cache: we compute compliance, and send message to cache with the computed compliance
Goal is to be isofunctionnal with previous method (no improvement in feature), except that it is a bit more efficient
Updated by Nicolas CHARLES over 3 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES over 3 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/3227
Updated by Alexis Mousset about 3 years ago
- Status changed from Pending technical review to Pending release
Updated by Vincent MEMBRÉ over 2 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.0.0~beta1 which was released today.
Actions