Installs/Configures chrony
- chef (>= 12.1)
- debian (>= 8.0.0)
- ubuntu (>= 16.04.0)
- centos (>= 7.0.0)
- redhat
- amazon
No dependencies defined
node[cookbook_name]['config']- chrony.conf value. Hash value can be a string or an array of string. Defaults tocase node['platform_family'].node[cookbook_name]['amazon_time_sync_service']- Whether to use Amazon Time Sync Service. Defaults tofalse.node[cookbook_name]['config_update_restart']- Whether to restart chrony daemon after config file change. Defaults totrue.
- chrony_ii::config - Configures application name, path, and configuration file based on platform family.
- chrony_ii::default - Loads necessary recipes.
- chrony_ii::package - Removes competing packages and installs chrony.
- chrony_ii::service - Configures chrony service.
- chrony_ii::systemd_support
Configures application name, path, and configuration file based on platform family.
Loads necessary recipes.
Removes competing packages and installs chrony.
Configures chrony service.
Provides supporting resources for systemd
Manages additional chronyd service dependencies in systemd
- create: Create chronyd service dependencies in systemd Default action.
- delete: Delete chronyd service dependencies in systemd
- systemd_system_dir: systemd's system config directory path
- wants: systemd service 'Wants=' targets with symlinks to 'chronyd.service.wants' Defaults to
"network-online.target". - after: systemd service 'After=' targets with symlinks to 'chronyd.service.after' Defaults to
"network-online.target".
include_recipe 'chrony_ii::systemd_support'
chrony_ii_systemd_dependency '/usr/lib/systemd/system'include_recipe 'chrony_ii::systemd_support'
chrony_ii_systemd_dependency '/usr/lib/systemd/system' do
wants 'x.target y.target'
after 'x.target'
endWe are planning to migrate from attribute and recipe-based cookbook to custom resource-based cookbook. Most recipes will be deprecated after providing custom resources.
For custom resource's unified_mode feature mandatory for Chef 17, the next major update requires Chef >= 15.3.0.
- Version up: update
metadata.rb - Update Changelog:
github_changelog_generator -u elastic-infra -p chrony_ii --future-release v0.5.2 - Release cookbook:
chef exec stove
To lint the project
chef exec cookstyleUnit testing
chef exec rspecIntegration testing
chef exec kitchen testIf you are fine with using the public NTP servers you can simply include chrony_ii in your node's run_list:
{
"name":"my_node",
"run_list": [
"recipe[chrony_ii]"
]
}If you need to control your configuration use a role.
Maintainer:: Tomoya Kabe ([email protected])
Source:: https://github.com/elastic-infra/chrony_ii
Issues:: https://github.com/elastic-infra/chrony_ii/issues
License:: MIT