Page MenuHomeVyOS Platform

Migrate NTP server addresses from *.pool.ntp.org to our own
Closed, DuplicatePublic

Description

Using hardcoded *.pool.ntp.org servers in a default config of an OS is actually a violation of the NTP Pool project policies. It's just that when VyOS was a small project with few users, it didn't matter, and we definitely couldn't setup our own pool and offer it to NTP.org (or just use it ourselves).

Whether we are ever going to make a vendor pool at NTP.org or not, we'll have to replace old *.pool.ntp.org addresses with new ones.

When the new NTP infrastructure is in place, we need to add a migration script for it. It should only replace *.pool.ntp.org, custom user-defined NTP servers should be left untouched.

Details

Difficulty level
Unknown (require assessment)
Version
-
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Behavior change

Event Timeline

dmbaturin created this task.

If I want to use also x.pool.ntp.org how should I use it if it will migrate anything from x.pool.ntp.org?

We already have:

vyos@r1# show system ntp 
 server time1.vyos.net {
 }
 server time2.vyos.net {
 }
 server time3.vyos.net {
 }

But I'm against migration, as I can't use x.pool.ntp.org and there is no option to detect whether are default NTP servers or configured by the user.