8b9d6f6fed
This commit addresses the situation in which a compute node is deleted, but its compute node stats still remain in the database as **not** deleted. This causes ill side effects in compute_node_get_all when it's retrieving host stats as it doesn't expect there to be compute node stats for which there is no corresponding compute node (i.e., causing some nodes' stats to be empty). As such, when a compute node is deleted, its stats should also be implicitly deleted. The new test case that's been created fails without the code changes, which illustrates the problem that compute node stats are empty when they should not be. Also included is a simple DB migration script that will update old stats that were not marked soft-deleted as they should have been. Change-Id: Ief0f7cf1a506e71898b5a45a0513d34167432d67 Closes-Bug: #1224712
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
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