openstack-manuals/doc/install-guide/source/environment-ntp-controller.rst
Christian Berendt 245fe26289 [install] use code-block directive instead of code directive
Change-Id: Id56dfc8572824d1dad47eee014870c9a64381645
Implements: blueprint installguide-liberty
2015-10-08 10:12:30 +02:00

2.2 KiB

Controller node

Install and configure components

Install the packages:

ubuntu or debian

# apt-get install chrony

rdo

# yum install chrony

obs

On openSUSE:

# zypper addrepo http://download.opensuse.org/repositories/network:time/openSUSE_13.2/network:time.repo
# zypper refresh
# zypper install chrony

On SLES:

# zypper addrepo http://download.opensuse.org/repositories/network:time/SLE_12/network:time.repo
# zypper refresh
# zypper install chrony

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.

ubuntu or debian

  1. Edit the /etc/chrony/chrony.conf file and add, change, or remove the following 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.

  2. Restart the NTP service:

    # service chrony restart

rdo or obs

  1. Edit the /etc/chrony.conf file and add, change, or remove the following 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.

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

    allow 10.0.0.0/24

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

  3. Start the NTP service and configure it to start when the system boots:

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