openstack-manuals/doc/install-guide/source/environment-ntp-other.rst
Pranav Salunke de38f2767f install: Updates syntax for training labs parser.
Training labs parser will allow us to automatically parse RST code
to BASH. This BASH code in turn will be invoked by install-guides for
validating the install guides. To provide the correct information to the
parser for generating BASH code, there are a few changes required to the
RST syntax.

Introduces the following changes to RST syntax:

  - `.. end`

    This tag provides information for the parser to stop extracting the
    given block which could be code, file injection or configuration
    file edit.

  - `.. endonly`

    This tag provides information for the parser with the correct
    distro-switch logic for identifying distro-specific code.

    For .. only:: tags, it is better to avoid nesting. If nesting
    is not avoidable then it is preferable to add the .. endonly
    tag to close the outer block immediately.

  - Extra new lines in code-blocks

    Some commands in the code-blocks provides the expected output of the
    given command. This is not a BASH command which we want to run but
    rather some visual niceness for the users. These new lines provides
    the parser information to identify the end of the command. This
    basic logic would be something similar to find '\r\n' which at least
    for python means new empty line.

  - `mysql>`

    Introducing this operator for mysql commands. This could potentially
    be changed to `pgsql>` or similar for other SQL type databases.
    This allows the parser to identify mysql commands and then run
    them in mysql instead of in 'sh' or 'bash'.

  - `.. path`

    Introducing this tag to provide the parser with the information with
    the path of the configuration file. Using the description text for
    the same is not reliable since the description text may not be
    consistent.

This commit should ideally introduce all the syntax changes required for
the parser to convert the code-blocks in here to BASH code. These
changes should have no impact on the HTML output of the RST code.

Change-Id: I47830b1bc61c8b1a0f3350932d15aa3ce88fa672
2016-09-28 10:58:06 +02:00

2.3 KiB

Other nodes

Other nodes reference the controller node for clock synchronization. Perform these steps on all other nodes.

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 comment out or remove all but one server key. Change it to reference the controller node:

    server controller iburst
  2. Restart the NTP service:

    # service chrony restart

rdo or obs

  1. Edit the /etc/chrony.conf file and comment out or remove all but one server key. Change it to reference the controller node:

    server controller iburst
  2. Start the NTP service and configure it to start when the system boots:

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