b9bae02af2
Currently we use the auto-updated "updated_at" field to determine whether a service is "up". An end-user can cause the "updated_at" field to be updated by disabling or enabling the service, thus potentially causing a service that is unavailable to be detected as "up". This could result in the scheduler trying to assign instances to an unavailable compute node, or in the system mistakenly preventing evacuation of an instance. The fix is to add a new field to explicitly track the timestamp of the last time the service sent in a status report and use that if available when testing whether the service is up. DocImpact This commit will cause a behaviour change for the DB servicegroup driver. It will mean that enabling/disabling the service will cause the "updated_at" field to change (as before) but that will no longer be tied to the "up/down" status of the service. So "nova service-list" could show the service as "down" even if it shows a recent "updated_at". (But this could happen for the other servicegroup drivers already.) Closes-Bug: #1420848 Change-Id: Ied7d47363d0489bca3cf2c711217e1a3b7d24a03
OpenStack Nova README
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMware, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.
OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.
To keep updated with new developments in the OpenStack project follow @openstack on Twitter.
To learn how to deploy OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:
Developers should also join the discussion on the mailing list, at:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests. Further developer focused documentation is available at:
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.
-- End of broadcast