02a82c41f9
When forcing a destination host during live migration, conductor bypasses the scheduler, performs some pre-migration checks and then casts to the specified destination compute host directly. With change I40b5af5e85b1266402a7e4bdeb3705e1b0bd6f3b we are still bypassing the scheduler but conductor will attempt to allocate resources against the specified destination host, which could fail and result in the live migration failing even though the force flag was specified in the API. This change simply adds a release note for the new behavior which was missing from the original fix. Change-Id: I1811dfa59865c0a878522007e0070f0fde8344f0 Related-Bug: #1712008
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: