b03a6836e6
Currently, We can't delete instance system metadata after instance is deleted because of following reason: 1) We might have 'changed-since' request which will access the soft deleted system_metadata 2) We might has period audit function which also access the soft deleted system_metadata The root cause is the join function filtered the 'deleted' data of system metadata and it lead to ValueError later. Conceptually the system metadata is associated with instance, it will be used in instance's lifecycle, the data will only be updated so we won't have 2 copies or more system_metadata for the same instance. So allow to read it even if it's deleted is safe. This patch load the system_metadata from db when instance is in deleted state to avoid can't delete system_metadata issue. Co-Authored-By: Alex Xu <hejie.xu@intel.com> Change-Id: Ifd8d2c91879834d3759aafdb036dac209a246d1b Partial-Bug: #1226049
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