User story #5434
closed
User story #5293: Add a 'changes only' compliance mode, only reporting changes on systems
Change the frequency of the agent execution
Added by Nicolas CHARLES over 9 years ago.
Updated about 9 years ago.
Category:
Web - Nodes & inventories
Description
Now, we can define globally the agent execution frequency, and all nodes must have the same.
This ticket is to :
- have the frequency per node
- and also define the heartbeat frequency
- and define for each node in which mode they are
These value can be empty (default value), or specific (overiden value)
Since we need to store a lot of data, we have the following:
- the computed frequency (in minutes), empty is not overriden
- the serialization of the user defined data (frequency, start minute, start hour, splay hour, minutes), plus the info of it is overriden or not
- for compliance we'll have:
- empty if never defined (so the global value), or a specific value if overriden, plus the serialization of overriden or not, and previous value
- Subject changed from Change the frequency of the agent execution/heartbeat per agent to Change the frequency of the agent execution
- Status changed from New to 10
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder/pull/600
- Target version changed from 140 to 3.0.0~beta1
- Status changed from 10 to Pending technical review
- Assignee changed from Jonathan CLARKE to Nicolas CHARLES
- Pull Request changed from https://github.com/Normation/rudder/pull/600 to https://github.com/Normation/rudder/pull/654
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0~beta1 which was release on 01/12/2014.
- Tracker changed from Enhancement to User story
Also available in: Atom
PDF
Updated by 
Updated by Matthieu CERDA 
Updated by 
Updated by