openstack/openstack-manuals
Code Issues Proposed changes
6b3e552524
openstack-manuals/doc/install-guide/source/environment-ntp-controller.rst
Jiří Suchomel 2fd6bf3923 Update SUSE versions 
Update existing OBS repository locations for openSUSE Leap 42.1
and SLES 12 SP1.

Change-Id: If978ec39dfd2695e570bf73742372b244d6dfa7f
2016-03-17 10:25:48 +01:00

3.0 KiB
Raw Blame History

Controller node

Perform these steps on the controller node.

Install and configure components

  1. Install the packages:

    ubuntu or debian

    # apt-get install chrony

    rdo

    # yum install chrony

    obs

    On openSUSE:

    # zypper addrepo -f obs://network:time/openSUSE_Leap_42.1 network_time
# zypper refresh
# zypper install chrony

    On SLES:

    # zypper addrepo -f obs://network:time/SLE_12_SP1 network_time
# zypper refresh
# zypper install chrony

    Note

    The packages are signed by GPG key 17280DDF. You should verify the fingerprint of the imported GPG key before using it.

    Key Name:         network OBS Project <network@build.opensuse.org>
Key Fingerprint:  0080689B E757A876 CB7DC269 62EB1A09 17280DDF
Key Created:      Tue 24 Sep 2013 04:04:12 PM UTC
Key Expires:      Thu 03 Dec 2015 04:04:12 PM UTC

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.

    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.

  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.

    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.

  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