[PVE-User] Chrony?!

[PVE-User] Chrony?!

[Marco Gaiarin]

I've just installed a PVE7; impressive, thanks.


But i've found that Chrony get installed; looking at changelog/roadmap:

	https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.0

	Time Synchronization:
	 Due to the design limitations of systemd-timesync, which make it problematic for server use, new installations will install chrony as the default NTP daemon.
	 If you upgrade from a system using systemd-timesyncd, it's recommended that you manually install either chrony, ntp or openntpd.

But looking at wiki, still systemd-timesyncd is cited:

	https://pve.proxmox.com/wiki/Time_Synchronization


What are these «problematic for server use» limitation? Someone can point to
some clue?


Thanks.

-- 
  Il backup è quella cosa che andava fatta prima.
					(Proverbio Cinese, Simone Aliprandi)

Re: [PVE-User] Chrony?!

[Marco Gaiarin]

Mandi! Stefan Radman via pve-user
  In chel di` si favelave...

> Quoting from "chrony vs. systemd-timesyncd ??? What are the differences and use cases as NTP clients?

OK, clear.

But if you (as me) have a internal hierarchy of NTP server, with a stable
internal time server for local branch office and some stable server in
main/head office, «can synchronize to multiple sources» pay little...


Anyway, i've tried to uninstall chrony, and systemd-timesync get
installed...

-- 
  I matti tutta la vita dentro la notte
  chiusi a chiave					(F. De Gregori)

Re: [PVE-User] Chrony?!

[Marco Gaiarin]

Mandi! Mark Schouten via pve-user
  In chel di` si favelave...

> systemd-timesyncd use of a single source is the main issue. I've had Ceph clusters go down because one timeserver had gone haywire and the monitors decided that everyones time was incorrect.

Oh, sure, and NOT using Ceph... also my ceph cluster goes down for a power
outgage, and the NTP server is a virtual machine on the same cluster...
lession lerned mee too! ;-)

-- 
  La CIA ha scoperto chi porta il carbonchio... la befanchia!!!