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.
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 or come chat with us on the Chef Community Slack in #sous-chefs.
- Debian / Ubuntu
- CentOS / Redhat
- Chef 13+
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.
The default recipe passes through to the client recipe.
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).
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:
- Clients with direct NTP server access
- A master with direct NTP server access with clients pointing to it
This project exists thanks to all the people who contribute.
Thank you to all our backers!
Support this project by becoming a sponsor. Your logo will show up here with a link to your website.
