7dd6a4a193
The current live migration code simply invokes migrateToURI and waits for it to finish, or raise an exception. It considers all exceptions to mean the live migration aborted and the VM is still running on the source host. This is totally bogus, as there are a number of reasons why an error could be raised from the migrateToURI call. There are at least 5 different scenarios for what the VM might be doing on source + dest host upon error. The migration might even still be going on, even if after the error has occurred. A more reliable way to deal with this is to actively query libvirt for the domain job status. This gives an indication of whether the job is completed, failed or cancelled. Even with that though, there is a need for a few heuristics to distinguish some of the possible error scenarios. This change to do active monitoring of the live migration process also opens the door for being able to tune live migration on the fly to adjust max downtime or bandwidth to improve chances of getting convergence, or to automatically abort it after too much time has elapsed instead of letting it carry on until the end of the universe. This change merely records memory transfer progress and leaves tuning improvements to a later date. Closes-bug: #1414065 Change-Id: I6fcbfa31a79c7808c861bb3a84b56bd096882004 |
||
|---|---|---|
| contrib | ||
| doc | ||
| etc/nova | ||
| nova | ||
| plugins/xenserver | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .testr.conf | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MANIFEST.in | ||
| README.rst | ||
| babel.cfg | ||
| openstack-common.conf | ||
| requirements.txt | ||
| run_tests.sh | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
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:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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