Forge Home


A module to manage Chronyd on RHEL7


6,834 latest version

4.3 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.1.2 (latest)
  • 0.1.1
  • 0.1.0
released Jul 17th 2017
This version is compatible with:
  • Puppet Enterprise 2017.2.x, 2017.1.x, 2016.4.x
  • Puppet >= 4.9.0 < 5.0.0
  • ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'beergeek-chronyd', '0.1.2'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add beergeek-chronyd
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install beergeek-chronyd --version 0.1.2

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



beergeek/chronyd — version 0.1.2 Jul 17th 2017


Table of Contents

  1. Description
  2. Setup
  3. Usage
  4. Reference
  5. Limitations


Configures the chrony daemon in RHEL 7.

This module installs and configures the chrony package, service, and configuration files.


Beginning with chronyd

To set up chrony with default values:

class { '::chronyd':
  servers => ['',''],



servers: The list of NTP servers to connect to

keyfile_hash: A hash of keys to install in the format { key_id => key_data }. Defaults to an empty hash

package_name: Name of the package to install, defaults to chrony

config_path: Path to the config file, defaults to /etc/chrony.conf

template_name: Template to use, modify this if the default template does not have enough flexibility. Defaults to chronyd/chrony.conf.epp

service_name: The service to manage, defaults to chronyd

package_ensure: Defaults to present

template_hash: Hash of local variables to pass to the template, only useful combination with template_name

service_ensure: Defaults to running

service_enable: Defaults to true

iburst: Whether to use iburst, defaults to true

stratumweight: Does this, defaults to 0

drift_file: Defaults to /var/lib/chrony/drift

rtcsync: Defaults to true

makestep: Defaults to true

step_threshold: Defaults to 0.1

step_number: Defaults to 10

ipv4_bindaddress: Defaults to ''

ipv6_bindaddress: Defaults to '::1'

keyfile: Defaults to '/etc/chrony.keys'

noclientlog: Defaults to false

logchange_value: Defaults to 1

logdir: Defaults to '/var/log/chrony'

template_keyfile: Defaults to chronyd/keyfile.epp

keyfile_path: Defaults to /etc/chrony.keys

replace_keyfile: Defaults to true


This is only tested on RHEL 7