Go to main content

Using Puppet to Perform Configuration Management in Oracle® Solaris 11.4

Exit Print View

Updated: October 2019
 
 

Perform Pre-Installation Tasks

Prior to installing the Puppet IPS package on the master server and on the managed nodes, perform the following tasks:

How to Configure NTP on the Puppet Master

Perform this procedure on the Puppet master prior to installing the system/management/puppet Puppet IPS package.

Because the Puppet master server acts as the certificate authority, best practice is to configure the Network Time Protocol (NTP) to accurately keep time on the master prior to installing Puppet. Otherwise, the master could issue certificates that the agents could treat as expired. For more information about managing NTP, see Managing Clock Synchronization in Oracle Solaris 11.4.

Before You Begin

Assume the Puppet Management rights profile. Use pfedit to edit the ntp.conf file.

  1. Create an NTP configuration file.

    Copy server information from the /etc/inet/ntp.client file to /etc/inet/ntp.conf.

    In this procedure, the following four time servers are specified so that a backup is available if one time server fails:

    server 0.pool.ntp.org
    server 1.pool.ntp.org
    server 2.pool.ntp.org
    server 3.pool.ntp.org
  2. Add the required configuration parameters to the NTP configuration file.

    Add the following parameters to the /etc/inet/ntp.conf file:

    driftfile /var/ntp/ntp.drift
    statsdir /var/ntp/ntpstats/
    filegen peerstats file peerstats type day enable
    filegen loopstats file loopstats type day enable
  3. Force an initial time synchronization.
    # ntpdate 0.pool.ntp.org
  4. Enable the ntp SMF service.
    # svcadm enable ntp
  5. Verify that NTP is working.
    # ntpq -p

    Note -  NTP start-up can take from 15 to 60 minutes or longer.

Next Steps

You can also specify NTP configuration by using a Puppet manifest. See Writing Puppet Manifests, Classes, and Modules in Oracle Solaris.