On 11/06/2015 04:26 AM, John Spray wrote: >> If the answer is "no", would it make sense to make NTP a runtime >> > dependency and tell the ceph-mon systemd service to wait for >> > ntpd.service before it starts? > Just waiting for the service is quick, but it doesn't achieve any > effect on the clock other than promising that it will be synced at > some point in the future. Wouldn't we have to wait for time sync > rather than just waiting for the service? That could take a while. For teuthology we have an optional task to stop ntpd, run ntpdate to slam-sync the clocks, and restart ntpd; by default ntpd can take a minimum of five minutes to adjust the clock, assuming it's got good sync data from its servers. I've wondered whether we ought to try to distribute that technique for users, but it's pretty half-baked in teuthology right now (the code exists but we're not running it as a matter of course). One wonders if there is a service that could be a sync point for "actual time update from ntpd/chronyd". -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
