cd_ntp | Release Notes


Timekeeping is of vital essence in modern computer networks. Network Time Protocol (NTP) manages the skew of computer clocks to be compliant to either an internal ntp server, or an external pool from the internet.

cd_ntp is a puppet module to automate the NTP configuration and the daemon.


**__!!! Attention: Never use this puppet module on systems which have been previously configured manually. It is impossible to predict how and what would have been configured, hence previuos configurations outside the scope of this module may be overwritten! Automated configurations require a test environment to verify that the module suits the purpose intended by the user, as well as tune the parameters, before deploying into live production!!! __**



  • Installation:
    • install ntp binaries
  • Configuration:
    • distinguish between client and server based on FQDN
    • configure ntp.conf for server, clients or default settings based on parameters
    • enable or disable additional settings:
    • broadcast
    • multicast
    • manycast
    • fudge
    • cryptography (excluding the actual cryptography keys at this stage)
  • Maintenance:
    • manage service user
    • ensure service availability

Repo Structure

Repostructure has moved to in repo.


All dependencies must be included in the catalogue.


native Puppet deployment

via site.pp or nodes.pp

node '' {
  include cd_puppetdb

through Foreman:

In order to apply parameters through Foreman, cd_ntp::params must be added to the host or hostgroup in question.

See more details about class deployment on


The following parameters are editable via params.pp or through ENC (recommended). Values changed will take immediate effect at next puppet run. Services will be restarted where neccessary.

  • $ntp_local_ntp_server : Whether or not to use a local ntp server in your network. recommended.
  • $ntp_server : The FQDN for the ntp server(s). Only effective if $ntp_local_ntp_server is set to true. If matched, server configuration will be applied, otherwise, the client configuraion.

For a full list of parameters see docs/index.html.


All files and directories are configured with correct selinux context. If selinux is disabled, these contexts are ignored.

Known Problems


  • OS: CentOS 6, 7
  • Puppet: 3.x


  • Puppet Lint
    • excluded tests:
    • --no-class_inherits_from_params_class-check:relavant only to non-supported outdated puppet versions
    • --no-variable_scope-check: not applicable as we are inheriting parameters from params class. the lint check does not distinguish between facts and inherited parameters.
    • --no-80chars-check: it is not always possible to stay within 80 characters, although typically only occurring on the parameter vault params.pp.
    • --no-arrow_alignment-check: this check leads to actually not having am easily readable arrow alignment, as this checks per block, not per class.
  • Puppet Parser
  • ERB Template Parser

Contact Us

contact Us


ConfDroid as entity is entirely independent from Puppet. We provide custom configuration modules, written for specific purposes and specific environments. The modules are tested and supported only as documented, and require testing in designated environments (i.e. lab or development environments) for parameter tuning etc. before deploying into production environments.

Leave a Reply