cookbook 'chrony', '= 1.0.0'
chrony (13) Versions 1.0.0 Follow11
Installs/Configures chrony, an application used to maintain the accuracy of the system clock (similar to NTPd).
cookbook 'chrony', '= 1.0.0', :supermarket
knife supermarket install chrony
knife supermarket download chrony
chrony cookbook
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 or come chat with us on the Chef Community Slack in #sous-chefs.
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. 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.
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.
Dependent cookbooks
This cookbook has no specified dependencies.
Contingent cookbooks
There are no cookbooks that are contingent upon this one.
chrony CHANGELOG
This file is used to list changes made in each version of the chrony cookbook.
1.0.0 - 2021-01-21
- Sous Chefs Adoption
- Standardize helpers library
- Improve testing
- Remove unused attributes
- Create attribute to handle custom extra configuration settings
0.3.1 (2020-12-23)
- Minor updates to the kitchen files and metadata.rb source fix - @tas50
- Use platform_family so we also support RHEL-like platforms like Oracle Linux - @gsreynolds
- Cookstyle Bot Auto Corrections with Cookstyle 6.18.8 - @cookstyle
0.3.0 (2020-02-10
- Added full support for CentOS/Redhat 7 & 8
- Expanded test coverage for Ubuntu, CentOS, and Redhat platforms
- Segregated templates used to configure chrony.conf for client and master servers
0.2.0 (2018-09-25)
- This cookbook has been brought back to life now under the chef-cookbooks org. Ideally, we'll rewrite this, but this version is already improved over the previous so we'll be releasing it now. Since this is not 1.0 expect heavy breaking changes in the future.
- Resolved all Foodcritic and Cookstyle warnings
- Added very basic ChefSpec
- Add Travis config + badge
- Added contributing and testing documentation
- Moved templates out of the default directory (chef 11-ism)
- Added name metadata
- Added chef_version metadata
- Added source_url and issues_url metadata
- Added a kitchen config
- Added a delivery local mode config
- Updated copyrights to be Chef Software not Opscode
0.1.0
Initial release.