Comment 4 for bug 1939901
Revision history for this message
| Alexsander de Souza (alexsander-souza) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
A NTP server is an authoritative source of time, often directly connected to a high-precision source (e.g. GPS antenna). Its precision is shown by its stratum number (lower is better). Stratum zero (S0) clocks cannot be accessed through the Internet, so S1 is the best we can use.
A NTP peer can be any system that runs a NTP daemon. When it's connected to a server (normal operation), it gets the correct time from there and the peer connections are not used. In the absence of a server, peers slowly converge to the same time, using stored drift data to figure out the correct time.
The current MAAS behaviour seems reasonable, so I agree this ticket can be closed.
I suggest adding a third NTP server to the customer setup, because with only 2 the protocol doesn't converge. Also review the servers being used, avoiding mixing different stratums and preferring geographically close servers.