bb8ba2cf56
Change I2c86989ab7c6593bf346611cde8c043116d55bc5 way back in Essex added the "setup_network_on_host" network API calls to the migration flows, including rollback_live_migration_at_destination. The initial implementation of that method for Quantum (Neutron) was a no-op. Change Ib1cc44bf9d01baf4d1f1d26c2a368a5ca7c6ab68 in Newton added the Neutron implementation for the setup_networks_on_host method in order to track the destination host being migrated to for instances that have floating IPs with DVR. When rolling back from a live migration failure on the destination host, the "migrating_to" attribute in the port binding profile, added in pre_live_migration() on the destination compute, is cleared. However, that only happens in rollback_live_migration_at_destination, which is only called if the instance is not on shared storage (think libvirt with the rbd image backend or with NFS). That's controlled via the "do_cleanup" flag returned from _live_migration_cleanup_flags(). If the live migration is happening over shared storage and fails, then rollback_live_migration_at_destination isn't called which means setup_network_on_host isn't called, which means the "migrating_to" attribute in the port binding profile isn't cleaned up. This change simply adds the cleanup in _rollback_live_migration in the event that neutron is being used and we're live migrating over shared storage so rollback_live_migration_at_destination isn't called. Change-Id: I658e0a749e842163ed74f82c975bcaf19f9f7f07 Closes-Bug: #1757292 |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| contrib | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| placement-api-ref/source | ||
| playbooks/legacy | ||
| releasenotes | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| README.rst | ||
| babel.cfg | ||
| bindep.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tests-py3.txt | ||
| tox.ini | ||
README.rst
Team and repository tags
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
To learn how to use Nova's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure 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
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
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:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: