NTP on april

Currently Have, Summary

April is running chrony, an NTP client and server.

April is currently getting time from the default Debian pool

2.debian.pool.ntp.org

The other servers (leonardo, michaelangelo, donatello, and rafael) are still getting their time from the same default Debian ntp.org pool via the default client, systemd-timesyncd

Would Like to Have / Next Steps

• Reconsider whether april should continue to be time server (b/c no Real Time Clock)
• If yes, point timesyncd config on servers to get time from april.
• Contemplate whether to use chrony on servers.
• Add appropriate public NTP servers to april.

Considerations Why

1. It is highly desirable for time on all of our machines to be in sync with as much accuracy as reasonably attainable.
2. (When we get serious about firewall), having servers sync to one internal NTP server is safer than allowing all of them to send outgoing NTP requests/receive NTP replies. It means fewer open ports and less incoming traffic from unfamiliar sources.
3. Having an in-house NTP source permits maintaining sync during external internet outage.

Foreseeable Complications

April - like all raspberry pi's - lacks a Real Time Clock. If turned off, she will need to get re-synced to an internet time server. Another solution is to Add a Real Time Clock to Raspberry Pi