ff747792b8
In Neutron, commit b7c303ee0a16a05c1fdb476dc7f4c7ca623a3f58 introduced events sent during a live migration when the VIFs are plugged on destination node. The Linux bridge agent mechanism driver is detecting new networks on the destination host only when the TAP devices are created, and these tap devices are only created when libvirt starts the migration. As a result, we must actually start the migration and then slow it as we wait for the neutron events. This change ensures we wait for these events. Depends-On: Icb039ae2d465e3822ab07ae4f9bc405c1362afba Conflicts: nova/tests/unit/virt/libvirt/test_driver.py nova/virt/libvirt/driver.py NOTE(lyarwood): The driver.py conflict is due to additional QEMU and LIBVIRT version constants being present in Queens. The test_driver.py conflict being the result of our need to assert byte strings in Pike as also seen by I9b545ca8aa6dd7b41ddea2d333190c9fbed19bc1 and resolved by I85cd9a903fba310b5ae7bedeed118ca4ea98dff6 in Queens. Closes-Bug: #1414559 Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@redhat.com> Change-Id: I407034374fe17c4795762aa32575ba72d3a46fe8 (cherry picked from commit |
||
---|---|---|
api-guide/source | ||
api-ref/source | ||
contrib | ||
devstack | ||
doc | ||
etc/nova | ||
gate | ||
nova | ||
placement-api-ref/source | ||
playbooks/legacy/nova-live-migration | ||
plugins/xenserver | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.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-functional-py3.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: