[chef-client] Enable chef-client scheduled task to behave like cron, … #739
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make chef-client scheduled task behave like cron, with a predictable start time and splay that stays consistent for a given node
Description
The chef-client windows scheduled task uses a random delay that can be up to 25 minutes and a start time based on when the code actually runs. Instead this change is meant to make the start time predictable, similar to a cron entry like */30, and the splay is used to compute a distinct per node value identical to how it's being done on cron (splay_sleep_time method). This enables the next actual start time for a chef run to be predictable for a given node.
Issues Resolved
Check List