This wishlist bug has been open a year without any activity. I'm going to move it to "Opinion / Wishlist", which is an easily-obtainable queue of older requests that have come on. If you decide to work on this consider using a blueprint [1] (with spec [2]). I'll recommend to read [3] if not yet done.
If there are any questions left, feel free to contact me (markus_z) in the IRC channel #openstack-nova References: [1] https://blueprints.launchpad.net/nova/ [2] https://github.com/openstack/nova-specs [3] https://wiki.openstack.org/wiki/Blueprints ** Changed in: nova Status: Confirmed => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1101839 Title: Don't use the local compute time when syncing Status in OpenStack Compute (nova): Opinion Bug description: Right now there is a strong tendency to rely on NTP for determining if services are up or down, especially compute nodes. This has been problematic since it is very fragile in its implementation (aka when NTP gets slightly out of sync on any compute node then that compute node will no longer be useable). It seems simpler to let the database decide what is "time" using its own internal functions like NOW() and such and not worry about time being in sync on the other nodes... Examples of this: https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L502 (note the time is from the caller, not from the db)... and https://github.com/openstack/nova/blob/master/nova/compute/resource_tracker.py#L276 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1101839/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
