Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenHPC 2: chrony.conf needs changes #1265

Closed
phpHavok opened this issue Oct 1, 2020 · 1 comment
Closed

OpenHPC 2: chrony.conf needs changes #1265

phpHavok opened this issue Oct 1, 2020 · 1 comment
Milestone

Comments

@phpHavok
Copy link

phpHavok commented Oct 1, 2020

In the chrony configuration steps under section 3.3 titled "Add provisioning services on master node," chrony.conf needs a couple changes.

  1. chrony.conf needs a line to allow internal network clients to use it as an NTP server. Specifically, something like this should be added:
echo "allow ${sms_ip}/${internal netmask}" >> /etc/chrony.conf
  1. chrony.conf needs to comment out or remove the pool line since we are using an NTP server line. Something like:
perl -pi -e "s/^(pool.*)$/#\\1/" /etc/chrony.conf

This pool change also needs to be made for the VNFS images in section 3.8.2 titled "Add OpenHPC components".

@phpHavok phpHavok changed the title chrony.conf needs line to allow internal network clients chrony.conf needs changes Oct 1, 2020
@phpHavok phpHavok changed the title chrony.conf needs changes OpenHPC 2: chrony.conf needs changes Oct 2, 2020
@koomie
Copy link
Contributor

koomie commented Oct 4, 2020

Thanks for this suggestion. We also detected a needed change in the ntp configuration which was made in the current 2.0 branch and will be in the final 2.0 release.

It is slightly different than you suggested, but should be sufficient to ensure that ntp synchronization is done. I also added a quick ntp test to the ohpc test suite to confirm the daemons are talking. In the current recipe example, we include the following line in chrony.conf on head node:

allow all

But the docs also have tooltip to indicate how to restrict to a local subnet as well (similar to your suggestion).

Regarding the removal of pool options, I'm not sure if we really need that. My testing seems to indicate that the server line will have priority over pool settings, so I've left that as is.

Please advise if that is inconsistent with your experience.

@koomie koomie added this to the 2.0 milestone Oct 4, 2020
@koomie koomie closed this as completed Oct 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants