Hi Noah, On Sat, Dec 09, 2017 at 12:52:09PM -0800, Noah Meyerhans wrote:
On Mon, Nov 16, 2015 at 11:30:05PM +0100, Vincent Blut wrote:Marking as wontfix as I’m definitely not sure implementing the debconf mechanism for such thing is the right approach.Hi. At a recent debian-cloud sprint, we made the choice to switch from ntpd to chrony for our cloud images.
Great!
As some of the cloud providers offer their own local NTP services, we'd like the ability to specify an entry for such a source in the default images for a given service.
Seems fair.
As such, I'd like to ask on behalf of the cloud team that you reconsider providing a debconf option to select a time source. I'm happy to send patches if that'll help.
Well if that’s something the cloud team wants to further improve their integration work, I’d be happy to accept such a patch. However I think using debconf in this case is quite fragile. Configuring the preferred time source depending on the cloud provider we are running on should ideally be done at runtime.
My suggestion would be to maintain the current pool.ntp.org entry as the default, and offer a debconf option to override this value at debconf's low priority so it won't bother most people installing the package.
I’m not sure that overriding the default pool of NTP servers we are using is the right approach, we should instead add the time source provided by the user to the configuration file and append the “prefer” option to it, so that if any issue should arise with that manually filled time source, that would leave the user with a sane fallback.
Thanks noah
Cheers, Vincent
signature.asc
Description: PGP signature
