258f6ca681
For some reason that isn't entirely clear to me, the attempt to update instance metadata in _instance_update() results in a stale sqlalchemy object state. This is a similar issue to the one fixed in commit: 9fdf7552779d518af9cda4e366bf81fddb0cb6f2 For some reason, session.refresh() doesn't work for instance['metadata'] in the same way, which also raises suspicion that perhaps it's not the right fix for system_metadata either. This patch adds an _instance_update_metadata_in_place() method that updates the actual instance['metadata'] list _and_ the database, mirroring the high-level behavior of instance_metadata_update(), but without requiring us to refresh or re-fetch the metadata or the whole instance (as a workaround). Fixes bug 1096653 Change-Id: Ic5a205631b1b7dce3744960ed4201dcc7b4b2ae6
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:
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:
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