Matt Riedemann
11f473b170
Per bug 1784022, it was not immediately clear that on a forced host live migration failure that the allocations on the dest host would be deleted and the original allocations for the instance would be back on the source host, but it is indeed working but as far as I could tell we didn't have a functional test for it, only the non-forced case. So this change adds the force=True wrinkle to the same existing functional test and also adds assertions on where the allocations exist for the source and dest nodes and the migration and instance records at the point of failure. Change-Id: Iaef9a4456c9c2bd9b2f4257b4ddd3efa3dea50f6 Related-Bug: #1784022
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: