Stratum 0 are the highly exact time sources such as atomic clocks or GPS clocks, these are our reference time devices.
also, if you have this working reliably it'd help to see your code. @gmiranda23 we are actually still running into this issue, and very sporadically.
Once we figure out the exact cause and figure out a fix, I'd be happy to open a PR to fix the issue.
If installed it will run once at boot time to set up your time according to Ubuntu's NTP server.
Later on anytime a new interface comes up it retries to update the time - while doing so it will try to slowly drift time as long as the delta it has to cover isn't too big.
To work around it, we have been setting ['ntp']['sync_clock'] to false.
Instead of an execute block that notifies the ntpd service (https://github.com/gmiranda23/ntp/blob/master/recipes/default.rb#L92), if it's rewritten to be a service block that stops ntpd, then runs ntpd -q, then another service block that starts ntpd, it appears to work properly. can you elaborate on how you determine it is not running properly?
That behaviour can be controlled with the By default the systemd based tools request time information at ntp.
In classic ntpd based service uses the pool of [0-3].Of the pool number 2.as well as ntp.also support ipv6 if needed.
Stratum 2 servers then get their time from the stratum 1 servers, while stratum 3 servers synchronize with stratum 2 sources.