Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/sous-chefs/chrony
Development repository for the chrony cookbook
https://github.com/sous-chefs/chrony
chef chef-cookbook chef-resource chrony hacktoberfest managed-by-terraform
Last synced: about 1 month ago
JSON representation
Development repository for the chrony cookbook
- Host: GitHub
- URL: https://github.com/sous-chefs/chrony
- Owner: sous-chefs
- License: apache-2.0
- Created: 2018-09-25T22:25:26.000Z (about 6 years ago)
- Default Branch: main
- Last Pushed: 2024-02-07T16:00:15.000Z (11 months ago)
- Last Synced: 2024-04-14T04:19:42.005Z (8 months ago)
- Topics: chef, chef-cookbook, chef-resource, chrony, hacktoberfest, managed-by-terraform
- Language: Ruby
- Homepage: https://supermarket.chef.io/cookbooks/chrony
- Size: 111 KB
- Stars: 3
- Watchers: 27
- Forks: 26
- Open Issues: 8
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
# chrony cookbook
[](https://supermarket.chef.io/cookbooks/chrony)
[](https://github.com/sous-chefs/chrony/actions?query=workflow%3Aci)
[](#backers)
[](#sponsors)
[](https://opensource.org/licenses/Apache-2.0)
Configures the time synchronization application `chrony` as a client or master timeserver, maintaining the accuracy of the system clock (similar to NTP). Isolated networks are supported as well.
## Maintainers
This cookbook is maintained by the Sous Chefs. The Sous Chefs are a community of Chef cookbook maintainers working together to maintain important cookbooks. If you’d like to know more please visit [sous-chefs.org](https://sous-chefs.org/) or come chat with us on the Chef Community Slack in [#sous-chefs](https://chefcommunity.slack.com/messages/C2V7B88SF).
## Requirements
### Platforms
- Debian / Ubuntu
- CentOS / Redhat
### Chef
- Chef 13+
## Recipes
### client
Configures the node to use the `chrony` application to keep the node's clock synced. If there is a node using the `chrony::master` recipe, the client will attempt to sync with it, unless disabled via `['chrony']['search_masters']`. If there is not an available master, the attribute list `['chrony'][:servers]` is used (defaults are `[0-3].debian.pool.ntp.org`). If there is a master node, the `['chrony'][:allowed]` will be set to allow for syncing with the master.
### default
The default recipe passes through to the client recipe.
### master
The node will use the `chrony` application to provide time to nodes using the `chrony::client` recipe. The master sets its own time against the attribute list `['chrony'][:servers]` (defaults are `[0-3].debian.pool.ntp.org`). Access to this master is restricted by the `['chrony'][:allowed]` attribute set in the recipe (default is to the `x.y.*` subnet).
## Usage
Nodes using the `chrony::client` recipe will attempt to sync time with nodes using the `chrony::master` recipe. If there are no `chrony::master` nodes found, the contents of the attribute list `['chrony'][:servers]` are used (defaults are `[0-3].debian.pool.ntp.org`).
The current configurations are supported:
1) Clients with direct NTP server access
2) A master with direct NTP server access with clients pointing to it
## Contributors
This project exists thanks to all the people who [contribute.](https://opencollective.com/sous-chefs/contributors.svg?width=890&button=false)
### Backers
Thank you to all our backers!
### Sponsors
Support this project by becoming a sponsor. Your logo will show up here with a link to your website.
