Description of problem: ----------------------- NTP config file (/etc/ntp.conf) defaults to NTP servers as available with /etc/ntp.conf. If the user already wished to move to a different NTP servers, then gdeploy should provide an option to change to the newer NTP server Version-Release number of selected component (if applicable): -------------------------------------------------------------- cockpit-ovirt-dashboard-0.10.7-0.0.5 How reproducible: ----------------- Always Steps to Reproduce: -------------------- 1. Perform gluster deployment from cockpit-ovirt 2. Check the generated gdeploy config file Actual results: --------------- No input for custom NTP server Expected results: ----------------- One of option for the user is to check whether to proceed with custom NTP server. If the answer is yes ( then gdeploy ansible module should be used ), else /etc/ntp.conf is taken by default
if custom_NTP_server: [shell1] action=execute command=sed -i 's/^\(server .*iburst\)/#\1/' /etc/ntp.conf [update-file1] action=add dest=/etc/ntp.conf line=server <custom_NTP_server> iburst else: do nothing But irrespective of above conditional loop, NTP service needs to be started and should be persisted across reboots. So, the following sections should be present: [service1] action=enable service=ntpd [service2] action=restart service=ntpd
NTP server configuration will be removed from gdeploy template. Currently user has to manually edit the configuration to change NTP server. Also user can make use of the NTP server feature available in cockpit to change the ntp server configurations. RFE https://bugzilla.redhat.com/show_bug.cgi?id=1417351 will introduce this feature in cockpit wizard.
Tested with ovirt-cockpit-dashboard-0.10.7-0.0.13 Hardcoded NTP server is now removed from generated gdeploy config file