chrony

#puppet-chrony

####Table of Contents

1. Overview
2. Module Description - What the module does and why it is useful
3. Setup - The basics of getting started with chrony
   • What chrony affects
   • Setup requirements
   • Beginning with chrony
4. Usage - Configuration options and additional functionality
5. Reference - An under-the-hood peek at what the module is doing and how
6. Limitations - OS compatibility, etc.

Overview

Chrony Puppet Module

Manage chrony time daemon on Archlinux and Redhat

##Module Description

The Chrony module handles running chrony in Archlinux and Redhat systems with systemd.

##Setup

###What chrony affects

• chrony package.
• chrony configuration file.
• chrony key file.
• chrony service.

###Beginning with chrony

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' ],
}

##Usage

All interaction with the chrony module can be done through the main chrony class.

###I just want chrony, what's the minimum I need?

include '::chrony'

###I just want to tweak the servers, nothing else.

class { '::chrony':
  servers => [ 'ntp1.corp.com', 'ntp2.corp.com', ],
}

###I'd like to make sure a secret password is used:

class [ '::chrony':
  servers         => [ 'ntp1.corp.com', 'ntp2.corp.com', ],
  chrony_password => 'secret_password',
}

###Allow some hosts

class [ '::chrony':
  queryhosts  => [ '192.168/16', ],
}

##Reference

###Classes

• chrony: Main class, includes all the rest.
• chrony::install: Handles the packages.
• chrony::config: Handles the configuration and key file.
• chrony::service: Handles the service.

###Parameters

The following parameters are available in the chrony module

####chrony_password

This sets the chrony password to be used in the key file.

####config

This sets the file to write chrony configuration into.

####config_template

This determines which template puppet should use for the chrony configuration.

####config_keys

This sets the file to write chrony keys into.

####config_keys_template

This determines which template puppet should use for the chrony key file.

####package_ensure

This can be set to 'present' or 'latest' or a specific version to choose the chrony package to be installed.

####package_name

This determines the name of the package to install.

####servers

This selects the servers to use for ntp peers.

####queryhosts

This adds the networks, hosts that are allowed to query the daemon.

####service_enable

This determines if the service should be enabled at boot.

####service_ensure

This determines if the service should be running or not.

####service_manage

This selects if puppet should manage the service in the first place.

####service_name

This selects the name of the chrony service for puppet to manage.

##Limitations

This module has been built on and tested against Puppet 3.2.3 and higher.

The module has been tested on:

• Arch Linux
• Red Hat