Fix NTP verify appearing before install

Due to the way the toctree was working on this page, the
steps to verify the NTP installation:
a) appeared prominently on the initial page, leading to
people wanting to try them before installing the service
b) were not available in a logical order when using the
previous/next buttons

This patch adds a new file for the verify steps to fix a)
and b) and includes it from the toctree. It's a solution,
but may not be the best solution.

Change-Id: I14b977147e70bf29ea42e40bb337c89426e6b8d5
Closes-Bug: 1501704
This commit is contained in:
Tom Fifield 2015-10-05 12:18:55 +08:00
parent d9539ba199
commit ec25954df1
2 changed files with 36 additions and 34 deletions

View File

@ -0,0 +1,35 @@
.. _environment-ntp-verify:
Verify operation
~~~~~~~~~~~~~~~~
We recommend that you verify NTP synchronization before proceeding
further. Some nodes, particularly those that reference the controller
node, can take several minutes to synchronize.
#. Run this command on the *controller* node:
.. code-block:: console
# chronyc sources
210 Number of sources = 2
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^- 192.0.2.11 2 7 12 137 -2814us[-3000us] +/- 43ms
^* 192.0.2.12 2 6 177 46 +17us[ -23us] +/- 68ms
Contents in the *Name/IP address* column should indicate the hostname or IP
address of one or more NTP servers. Contents in the *S* column should indicate
*\** for the server to which the NTP service is currently synchronized.
#. Run the same command on *all other* nodes:
.. code-block:: console
# chronyc sources
210 Number of sources = 1
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^* controller 3 9 377 421 +15us[ -87us] +/- 15ms
Contents in the *remote* column should indicate the hostname of the controller node.

View File

@ -16,37 +16,4 @@ nodes to reference the controller node.
environment-ntp-controller.rst environment-ntp-controller.rst
environment-ntp-other.rst environment-ntp-other.rst
environment-ntp-verify.rst
Verify operation
----------------
We recommend that you verify NTP synchronization before proceeding
further. Some nodes, particularly those that reference the controller
node, can take several minutes to synchronize.
#. Run this command on the *controller* node:
.. code-block:: console
# chronyc sources
210 Number of sources = 2
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^- 192.0.2.11 2 7 12 137 -2814us[-3000us] +/- 43ms
^* 192.0.2.12 2 6 177 46 +17us[ -23us] +/- 68ms
Contents in the *Name/IP address* column should indicate the hostname or IP
address of one or more NTP servers. Contents in the *S* column should indicate
*\** for the server to which the NTP service is currently synchronized.
#. Run the same command on *all other* nodes:
.. code-block:: console
# chronyc sources
210 Number of sources = 1
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^* controller 3 9 377 421 +15us[ -87us] +/- 15ms
Contents in the *remote* column should indicate the hostname of the controller node.