Hi Guys, thanks for your comments, please bear with me since I am trying to
grasp, learn and apply the best practices.

Has mentioned, my goal is to have all the VM's in sync with the minimum
offset possible, time is important but would like to focus more on having
all of them in sync for now.

If I am understanding correctly the best way could be to have a GPS/PPS
hardware, not a VM, use it as a stratum0 and then connect to that device
one or more servers (preferably not VM's)  that will behave like my pool of
stratum 1.

Now let's say that I create a pool of 3 servers in this using the following
setup:


                     my.pool
GPS/PPS hardware --- server 1 (America)
                                 `-- server 2 (Europe)
                                 `-- server 3 (Asia)

The main source for all of them is the GPS/PPS hardware but how to
"compensate" the latency and sync between them probably there is no need
for this but just wondering, for example, the configuration for the servers
would be something using only local or also the need of the servers are
needed:


local stratum 1
allow

Or should I use something like this for server 1:

    server server-2
    server server-3
    local stratum 1
    allow

For server 2:

    server server-1
    server server-3
    local stratum 1
    allow

For server 3:

    server server-1
    server server-2
    local stratum 1
    allow


If I also understood probably could be better to have a GPS/PPS device per
zone something like:

           my.pool
GPS/PPS -- server 1 (America)
GPS/PPS -- server 2 (Europe)
GPS/PPS -- server 3 (Asia)

But again how to compensate or sync the pool itself so that all the child’s
or machines using this service could be in sync.

And in cases (my current case) where I don’t have a GPS/PPS hardware device
could I make a pool full in sync using an existing public ntp server at
least just to try to achieve a very low offset?


Thanks in advance.

Reply via email to