4817165fc5
Change Id515137747a4b76e9b7057c95f80c8ae74017519 modified the libvirt driver to not wait for network-vif-plugged events on resize revert, saying that the vifs were never unplugged. That's true for the source host but not the dest host. The ComputeManager.revert_resize method calls driver.destroy and for the libvirt driver, driver.destroy calls cleanup which calls unplug_vifs *on the dest host*. As of change If00736ab36df4a5a3be4f02b0a550e4bcae77b1b, the API will route all events to both the source and dest host while the instance has a migration_context. When revert_resize is done on the dest host, it RPC casts to finish_revert_resize on the source host which calls driver.finish_revert_migration which restarts the guest on the source host and plugs vifs. Therefore, we can wait for the network-vif-plugged event before changing the instance status back to ACTIVE. Change-Id: I9e0cffb889c94713c7f28812918103a5d97cefeb Related-Bug: #1788403 |
||
---|---|---|
api-guide/source | ||
api-ref/source | ||
contrib | ||
devstack | ||
doc | ||
etc/nova | ||
gate | ||
nova | ||
placement-api-ref | ||
playbooks/legacy | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.stestr.conf | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MAINTAINERS | ||
README.rst | ||
babel.cfg | ||
bindep.txt | ||
lower-constraints.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.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: