# Whether or not to install the ceph-test package.
#ceph_test: false
-# Enable the ntp service by default to avoid clock skew on
-# ceph nodes
+# Enable the ntp service by default to avoid clock skew on ceph nodes
+# Disable if an appropriate NTP client is already installed and configured
#ntp_service_enabled: true
+# Set type of NTP client daemon to use, valid entries are chronyd, ntpd or timesyncd
+# Note that this selection is currently ignored on containerized deployments
+#ntp_daemon_type: timesyncd
+
+
# Set uid/gid to default '64045' for bootstrap directories.
# '64045' is used for debian based distros. It must be set to 167 in case of rhel based distros.
# These values have to be set according to the base OS used by the container image, NOT the host.
# Whether or not to install the ceph-test package.
#ceph_test: false
-# Enable the ntp service by default to avoid clock skew on
-# ceph nodes
+# Enable the ntp service by default to avoid clock skew on ceph nodes
+# Disable if an appropriate NTP client is already installed and configured
#ntp_service_enabled: true
+# Set type of NTP client daemon to use, valid entries are chronyd, ntpd or timesyncd
+# Note that this selection is currently ignored on containerized deployments
+#ntp_daemon_type: timesyncd
+
+
# Set uid/gid to default '64045' for bootstrap directories.
# '64045' is used for debian based distros. It must be set to 167 in case of rhel based distros.
# These values have to be set according to the base OS used by the container image, NOT the host.
---
-- name: install ntp on debian
- package:
- name: ntp
- state: present
+- name: setup ntpd
+ block:
+ - command: timedatectl set-ntp no
+ - package:
+ name: ntp
+ state: present
+ - service:
+ name: ntp
+ enabled: yes
+ state: started
+ when: ntp_daemon_type == "ntpd"
-- name: start the ntp service
- service:
- name: ntp
- enabled: yes
- state: started
+- name: setup chrony
+ block:
+ - command: timedatectl set-ntp no
+ - package:
+ name: chrony
+ state: present
+ - service:
+ name: chronyd
+ enabled: yes
+ state: started
+ when: ntp_daemon_type == "chronyd"
+
+- name: setup timesyncd
+ block:
+ - command: timedatectl set-ntp on
+ when: ntp_daemon_type == "timesyncd"
---
-- name: install ntp
- package:
- name: ntp
- state: present
+- name: setup ntpd
+ block:
+ - command: timedatectl set-ntp no
+ - package:
+ name: ntp
+ state: present
+ - service:
+ name: ntpd
+ enabled: yes
+ state: started
+ when: ntp_daemon_type == "ntpd"
-- name: start the ntp service
- service:
- name: ntpd
- enabled: yes
- state: started
+- name: setup chrony
+ block:
+ - command: timedatectl set-ntp no
+ - package:
+ name: chrony
+ state: present
+ - service:
+ name: chronyd
+ enabled: yes
+ state: started
+ when: ntp_daemon_type == "chronyd"
+
+- name: setup timesyncd
+ block:
+ - command: timedatectl set-ntp on
+ when: ntp_daemon_type == "timesyncd"
# Whether or not to install the ceph-test package.
ceph_test: false
-# Enable the ntp service by default to avoid clock skew on
-# ceph nodes
+# Enable the ntp service by default to avoid clock skew on ceph nodes
+# Disable if an appropriate NTP client is already installed and configured
ntp_service_enabled: true
+# Set type of NTP client daemon to use, valid entries are chronyd, ntpd or timesyncd
+# Note that this selection is currently ignored on containerized deployments
+ntp_daemon_type: timesyncd
+
+
# Set uid/gid to default '64045' for bootstrap directories.
# '64045' is used for debian based distros. It must be set to 167 in case of rhel based distros.
# These values have to be set according to the base OS used by the container image, NOT the host.
- ceph_rhcs_cdn_debian_repo == 'https://customername:customerpasswd@rhcs.download.redhat.com'
- ceph_repository not in ['rhcs', 'dev', 'obs']
+- name: validate ntp daemon type
+ fail:
+ msg: "ntp_daemon_type must be one of chronyd, ntpd, or timesyncd"
+ when:
+ - ntp_service_enabled
+ - ntp_daemon_type not in ['chronyd', 'ntpd', 'timesyncd']
+
- name: make sure journal_size configured
debug:
msg: "WARNING: journal_size is configured to {{ journal_size }}, which is less than 5GB. This is not recommended and can lead to severe issues."