hsafe
commented
7 years ago Hi again, I found the solution. Sometimes the answer is too clear to notice :). Now the answer to anyone stumbling here and with more or less the same problem is as follows: Declare the class as usual in either node.pp or the site.pp in the manifest;giving further granulation with the server resource value ...only this time for the prefer server, you include the prefer word as here: class { '::chrony': servers => ['172.16.1.1 prefer', '0.centos.pool.ntp.org', '1.centos.pool.ntp.org', '2.centos.pool.ntp.org', '3.centos.pool.ntp.org' ], }
That is all ...now a bit of context with original desired status but all is set and works as desired.
Hi, First thanks for the module, secondly I was trying to achieve a bit more granulated config generation. I am trying to get one of the servers with "prefer" option so that chrony prefers that server over other servers. I am not a ruby literate and the configuration does its job as promised...however can you please guide me how I can do that tweak as well? One way was trying to apply the file from the puppet source in a file resource declaration, however if I can get it through your module it will be a perfect neat way... (The desired status on a centos7 environment eventually would like to look like this: server 172.16.1.1 iburst prefer server 0.centos.pool.ntp.org iburst server 1.centos.pool.ntp.org iburst server 2.centos.pool.ntp.org iburst server 3.centos.pool.ntp.org iburst ) Thank you for your time and efforts