
live_migration_progress_timeout aims to timeout a live-migration well before the live_migration_completion_timeout limit, by looking for when it appears that no progress has been made copying the memory between the hosts. However, it turns out there are several problems with the way we monitor progress. In production, and stress testing, having live_migration_progress_timeout > 0 has caused random timeout failures for live-migrations that take longer than live_migration_progress_timeout One problem is that block_migrations appear to show no progress, as it seems we only look for progress in copying memory. Also the way we query QEMU via libvirt breaks when there are multiple iterations of memory copying. We need to revisit this bug and either fix the progress mechanism or remove the all the code that checks for the progress (including the automatic trigger for post-copy). But in the mean time, lets default to having no timeout, and warn users that have overridden this configuration by deprecating the live_migration_progress_timeout configuration option. For users concerned about live-migration timeout errors, I have cleaned up the configuration option descriptions, so they have a better chance of stopping the live-migration timeout errors they may come across. Related-Bug: #1644248 Change-Id: I1a1143ddf8da5fb9706cf53dbfd6cbe84e606ae1
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 and OpenStack Ironic.
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.
API
To learn how to use Nova's API, consult the documentation available online at:
http://developer.openstack.org/api-guide/compute/ http://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
http://www.openstack.org/appdev/ http://developer.openstack.org/
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, please read:
http://docs.openstack.org/developer/nova/feature_classification.html
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: