f8a01887dc
When an instance is snapshotted, the resultant image should have the image_type property set to "snapshot". However, if the base image already had image_type set to "base", the image_type on the snapshot will also be set to "base". This turns out to be because we set image properties in two different places. The first is when the image record is created in glance, which occurs in nova.compute.api:API._create_image(); this is when image_type is set to "snapshot". However, in nova.virt.xenapi.vm_utils:upload_image(), all the properties from the base image are copied over, so all the properties set by _create_image() could be overwritten. The quick solution was to extend the non_inheritable_image_properties configuration setting to also cover the image properties set by _create_image(). Long-term, these two metadata-setting processes need to be more closely unified. (It should be noted that the upload_image() function contains a TODO stating that the code should move into the compute manager, so it can be shared across hypervisors…) Fixes bug 1031079. Change-Id: I936bc147fb823eca67e40084cba5c3bc1a7fe73a
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 dicussion 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:
Changes to OpenStack Nova should be submitted for review via the Gerrit tool, following the workflow documented at:
-- End of broadcast