Manage chrony time daemon on Archlinux and Redhat
The Chrony module handles running chrony in Archlinux and Redhat systems with systemd.
Please review metadata.json
for a list of requirements.
include 'chrony'
is all you need to get it running. If you
wish to pass in parameters like which servers to use
then you can use:
class { 'chrony':
servers => ['ntp1.corp.com', 'ntp2.corp.com' ],
}
All interaction with the chrony module can be done through the main chrony class.
include 'chrony'
class { 'chrony':
servers => [ 'ntp1.corp.com', 'ntp2.corp.com', ],
}
class { 'chrony':
servers => [ 'ntp1.corp.com', 'ntp2.corp.com', ],
chrony_password => 'secret_password',
}
class { 'chrony':
keys => ['25 SHA1 HEX:1dc764e0791b11fa67efc7ecbc4b0d73f68a070c'],
servers => {
'ntp1.corp.com' => ['key 25', 'iburst'],
'ntp2.corp.com' => ['key 25', 'iburst'],
},
}
class { 'chrony':
chrony_password => 'unset',
config_keys_manage => false,
}
class { 'chrony':
queryhosts => [ '192.168/16', ],
}
class { 'chrony':
leapsecmode => 'slew',
smoothtime => '400 0.001 leaponly',
maxslewrate => 1000.0
}
RedHat and Suse provide a default disabled chrony-wait.service
to block the time-sync.target
until node is synchronised.
To enable it:
class { 'chrony':
wait_enable => true,
wait_ensure => true,
}
Reference documentation for the chrony module is generated using puppet-strings and available in REFERENCE.md
This module has been built on and tested against Puppet 5.5 and higher.
The module has been tested on:
This module is distributed under the Apache License 2.0. Copyright belongs to the module's authors, including Niels Abspoel and others.
The module was originally written by Niels Abspoel and released as aboe76/chrony. Since version 0.4.0, it is maintained by Vox Pupuli.