openstack/openstack-manuals
Code Issues Proposed changes
openstack-manuals/doc/install-guide/source/environment-ntp-controller.rst
Doug Hellmann e39304d4ae fix pdf build 
The PDF build does not include content multiple times if the same file
is included in a toctree more than once. That means we need to
restructure the guide to handle the common parts differently. This
approach merges some of the previously split sections back together
using inline prose to indicate where minor variations apply for
different operating systems but retaining separate files for cases where
the differences are significant.

Change-Id: I5d9ff549b05ca4ce54486719d70858589b8fcfa3
Depends-On: Ia750cb049c0f53a234ea70ce1f2bbbb7a2aa9454
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2017-07-03 08:46:57 -04:00

1.6 KiB
Raw Blame History

Controller node

Perform these steps on the controller node.

Install and configure components

  1. Install the packages:

    For Debian or Ubuntu:

    # apt install chrony

    For Red Hat or CentOS:

    # yum install chrony

    For SUSE:

    # zypper install chrony

  2. Edit the /etc/chrony/chrony.conf file and add, change, or remove these keys as necessary for your environment:

    server NTP_SERVER iburst

    Replace NTP_SERVER with the hostname or IP address of a suitable more accurate (lower stratum) NTP server. The configuration supports multiple server keys.

    Note

    By default, the controller node synchronizes the time via a pool of public servers. However, you can optionally configure alternative servers such as those provided by your organization.

  3. To enable other nodes to connect to the chrony daemon on the controller node, add this key to the /etc/chrony/chrony.conf file:

    allow 10.0.0.0/24

    If necessary, replace 10.0.0.0/24 with a description of your subnet.

  4. Restart the NTP service:

    For Debian or Ubuntu:

    # service chrony restart

    For Red Hat or SUSE:

    # systemctl enable chronyd.service
# systemctl start chronyd.service