b36c44c449
Prior to change I4244f7dd8fe74565180f73684678027067b4506e in Stein, conductor would pass a legacy dict request spec to compute during cold migrate / resize and if compute rescheduled it would not pass the request spec back to conductor, so the _cold_migrate method in conductor would have to create a new RequestSpec from components it had available. As of that change, compute will send the request spec it got back to conductor and _cold_migrate avoids the RequestSpec.from_components call. There are two issues here: 1. Technically if conductor RPC API is pinned to less than 1.13 the ComputeTaskAPI.migrate_server method will remove the request spec from the call to conductor. So conductor (server-side) can still not get a RequestSpec and need to use from_components. As a result the TODO in the _cold_migrate method needs to be updated since we require an RPC API major version bump to make request spec required. 2. Just because conductor is passing compute a RequestSpec object, if compute RPC API versions are pinned to less than 5.1, conductor will pass a legacy request spec dict to compute and compute will send that back to conductor, so the _cold_migrate method needs to handle getting a request spec that is a dict and convert it to an object. A new test is added for that case. Change-Id: I188b7aa9cb220f93e69a68f0c3592b28d41ba5b6 Closes-Bug: #1843090 |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| playbooks | ||
| releasenotes | ||
| roles/run-post-test-hook | ||
| 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 | ||
| 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: