You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
In the chrony configuration steps under section 3.3 titled "Add provisioning services on master node," chrony.conf needs a couple changes.
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".
The text was updated successfully, but these errors were encountered: