Open Stack

Yes, it does.

On Sat, Nov 15, 2014 at 3:15 AM, Rick Jones <rick.jones2 at hp.com> wrote:

> On 11/14/2014 04:01 PM, Dmitry Borodaenko wrote:
>
>> If NTP server is not reachable on the first boot of the master node,
>> it should be disabled by bootstrap_admin_node, that eliminates the
>> possibility of it spontaneously coming to life and changing the clock
>> for fuel master node and all target nodes in the middle of a
>> deployment. Then all Nailgun needs to do is pop a warning notification
>> that no NTP server is configured on the master node, and it should be
>> fixed manually before starting any deployments. No need to block
>> deployment altogether: if the user doesn't need need global time at
>> all (e.g. in an off-the-grid bunker 2 miles beneath Fort Knox),
>> synchronizing clocks on all environments just to the Fuel master will
>> still work.
>>
>
> I thought NTP (well ntpd) had an option to tell it to only ever slew the
> clock, never step it?  Or is that only some implementations of NTP?
>
> rick jones
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Andrey Danin
adanin at mirantis.com
skype: gcon.monolake
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141118/4f511e54/attachment.html>