79b49e2f58
Normally chronyd will cause the system to gradually correct any time offset, by slowing down or speeding up the clock as required. In certain situations, the system clock might be so far adrift that this slewing process would take a very long time to correct the system clock Change-Id: I939b6aae1dbeb133203085ec68bdb9f7936ee9ef Closes-Bug: #1696056
42 lines
731 B
Django/Jinja
42 lines
731 B
Django/Jinja
{% for host in groups['chrony-server'] %}
|
|
{% if inventory_hostname != host %}
|
|
server {{ hostvars[host]['ansible_' + hostvars[host]['api_interface']]['ipv4']['address'] }} iburst
|
|
{% endif %}
|
|
{% endfor %}
|
|
{% for ntp_server in external_ntp_servers %}
|
|
server {{ ntp_server }} iburst
|
|
{% endfor %}
|
|
|
|
keyfile /etc/chrony/chrony.keys
|
|
|
|
commandkey 1
|
|
|
|
driftfile /var/lib/chrony/chrony.drift
|
|
|
|
log tracking measurements statistics
|
|
logdir /var/log/kolla/chrony
|
|
|
|
makestep 3 3
|
|
|
|
maxupdateskew 100.0
|
|
|
|
dumponexit
|
|
|
|
dumpdir /var/lib/chrony
|
|
|
|
{% if inventory_hostname in groups['chrony-server'] %}
|
|
allow all
|
|
local stratum 10
|
|
{% else %}
|
|
port 0
|
|
deny all
|
|
{% endif %}
|
|
|
|
bindaddress {{ api_interface_address }}
|
|
|
|
logchange 0.5
|
|
|
|
hwclockfile /etc/adjtime
|
|
|
|
rtcsync
|