1f48d3d83b
Currently port binding call is made at destination compute in post live migration phase. This may cause network outage during post-copy as the virtual CPUs are paused immediately at source and unpaused at destination by transferring a minimum set of pages. The following domain life cycle events are emitted in this order during post-copy: * VIR_DOMAIN_EVENT_STARTED(destination) * VIR_DOMAIN_EVENT_SUSPENDED_POSTCOPY(source)--migration entered post-copy mode * VIR_DOMAIN_EVENT_RESUMED_POSTCOPY(destination)--guest is running on the destinaton host while some if its memory pages still remain on sourcehost. * VIR_DOMAIN_EVENT_RESUMED_MIGRATED(destination) * VIR_DOMAIN_EVENT_STOPPED_MIGRATED(source)--migration finished successfully and the destination host holds a complete guest state. In this change, dest host port binding activation is done when the following events are emitted at source for post-copy and pre-copy: * VIR_DOMAIN_EVENT_SUSPENDED_POSTCOPY * VIR_DOMAIN_EVENT_SUSPENDED_MIGRATED This reduces the network outage during live migration as network switch is done right before VM resumes at destination. Co-Authored-By: Matt Riedemann <mriedem.os@gmail.com> Change-Id: Ic5cab99944df9e501ba2032eb96911c36304494d Closes-Bug: #1605016 |
||
---|---|---|
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 | ||
lower-constraints.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: