The chrony package is included in the standard Leap 42.2 and SLES-12-SP2 repositories. It is not necessary anymore to add a special repository. backport: newton Change-Id: I94495209e12237eff5e5f26e56785173289e0494
2.6 KiB
Controller node
Perform these steps on the controller node.
Install and configure components
Install the packages:
ubuntu or debian
# apt install chrony
rdo
# yum install chrony
obs
# zypper install chrony
ubuntu or debian
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 multipleserver
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.
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
Restart the NTP service:
# service chrony restart
rdo or obs
Edit the
/etc/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 multipleserver
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.
To enable other nodes to connect to the chrony daemon on the controller node, add this 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.Start the NTP service and configure it to start when the system boots:
# systemctl enable chronyd.service # systemctl start chronyd.service