That's right, but I think you want to do a slightly deeper analysis of
NTP config, and make sure that the schema you start with can evolve to
be more complete in future.
I think a list of timeservers is a fine starting point. I also think the
default behaviour should be to use a pool backed by ntp.ubuntu.com.
So I think you want to start with something a little more like:
config:
core:
ntp:
enabled: auto | off | custom # auto uses pool+ubuntu in addition
to any time servers configured timeservers: [ list, of, custom, servers ]
The default would be auto. If I add time servers then those get added to
pool+ntp.ubuntu.com, if I say custom then I only get the servers I
explicitly list.
That's a quick starting point and can definitely be improved so consider
it a straw man and feel free to poke at it.
And if you want to get fancy, I have a personal interest in enabling
hardware devices like GPS and PPS pins on weekend time :)
That's right, but I think you want to do a slightly deeper analysis of
NTP config, and make sure that the schema you start with can evolve to
be more complete in future.
I think a list of timeservers is a fine starting point. I also think the
default behaviour should be to use a pool backed by ntp.ubuntu.com.
So I think you want to start with something a little more like:
config:
timeservers: [ list, of, custom, servers ]
core:
ntp:
enabled: auto | off | custom # auto uses pool+ubuntu in addition
to any time servers configured
The default would be auto. If I add time servers then those get added to ubuntu. com, if I say custom then I only get the servers I
pool+ntp.
explicitly list.
That's a quick starting point and can definitely be improved so consider
it a straw man and feel free to poke at it.
And if you want to get fancy, I have a personal interest in enabling
hardware devices like GPS and PPS pins on weekend time :)
Mark