Project

General

Profile

Actions
Copy link

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 about 10 years ago. Updated over 9 years ago.

Status:
Released
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
Web - Nodes & inventories
Target version:
3.0.0~beta1
Pull Request:
https://github.com/Normation/rudder/p...
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

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

Related issues 2 (0 open — 2 closed)

Related to Rudder - Bug #5789: Frequency displayed for agent run schedule is missing leading 0s (ex: 4:0 instead of 04:00)ReleasedFrançois ARMAND2014-11-20Actions
Related to Rudder - Bug #5438: Eventlogs for frequency modification on node are missingRejectedFrançois ARMAND2014-08-27Actions
Actions
Copy link
 #1

Updated by Nicolas CHARLES about 10 years ago

These value can be empty (default value), or specific (overiden value)

Actions
Copy link
 #2

Updated by Nicolas CHARLES about 10 years ago

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

Actions
Copy link
 #3

Updated by Nicolas CHARLES about 10 years ago

  • 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
Actions
Copy link
 #4

Updated by Matthieu CERDA about 10 years ago

  • Target version changed from 140 to 3.0.0~beta1
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 10 years ago

  • 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
Actions
Copy link
 #6

Updated by Nicolas CHARLES about 10 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ almost 10 years ago

  • 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.

Actions
Copy link
 #9

Updated by Benoît PECCATTE over 9 years ago

  • Tracker changed from Enhancement to User story
Actions
Copy link

Also available in: Atom PDF