659ec75eaf
During live block migrations both pre_live_migration and pre_block_migration check for the presence of the instance on the destination and create the instance dir if it doesn't exist. As a result the call to pre_block_migration always fails as pre_live_migration has already created the instance dir on the destination. As it turns out the pre_block_migration call is completely unnecessary. The libvirt driver is the only driver that uses the call and the work it does can easily be done in the existing pre_live_migration call. In order to streamline things we completely remove the pre_block_migration call from all drivers. Additionally we update the function definition for pre_live_migration to pass needed disk info down to the virt drivers. Fixes bug: #1193359 Change-Id: Id9dfe482db3471d6a1b9b6c7d59a5ddc48775d7f
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:
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