feat(EL7 Stack): Add chrony monitoring #106
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Some initial tests show that chrony works just as well on EL7 as it does on EL8+. Hence i'd like to switch to chrony for all client systems. I don't plan to touch nodes involved with providing NTP services. IMO this simplifies our setup because we can use the same monitoring and configuration principals for both environments. It will aid in shortening our internal NTP docs.
This is draft for now because i want to keep an eye on the EL7+ chrony test system i have so far and gradually add some more systems before fully committing.