I personally think that running NTP on master node & relying on master node
hardware clock is okay as a default configuration. As long as the menu
allows for configuring an external NTP.
At the same time, we should carefully explain both options in the
documentation ("built-in NTP" vs. "external NTP") and provide guidance
regarding the choice. So that any person in the community, including our
own services team, can make an intelligent call. I believe there is a
"Deployment pre-requisites" section in the docs for this type of
information.
Roman
On Mon, Jan 27, 2014 at 7:49 AM, Matthew Mosesohn <[email protected]>wrote:
> Andrew,
>
> I believe it's not done yet, but there was an objective to pass these
> NTP time sources directly to all nodes during deployment as a fact.
> Fuel Master should have a reliable time source because clock skews
> break mcollective and also make reading logs quite painful.
>
> Nodes try to sync against Fuel Master still today, and I agree that
> it's bad. If there's no 3rd party time source available, then we have
> little choice.
>
> On Sun, Jan 26, 2014 at 10:33 PM, Andrew Woodward <[email protected]>
> wrote:
> > Fuel master shouldn't care too badly about ntp, this illuminates the
> need to
> > add these settings into the cluster and UI. We shouldn't be providing a
> bad
> > time source unless the owner doesn't have their own. Especially since we
> > need three time sources to keep a stable clock.
>
--
Mailing list: https://launchpad.net/~fuel-dev
Post to : [email protected]
Unsubscribe : https://launchpad.net/~fuel-dev
More help : https://help.launchpad.net/ListHelp
