7daa3f59e2
fill_provider_mapping is used from *most* code paths where it's necessary to associate RequestSpec.request_groups with the resource providers that are satisfying them. (Specifically, all the code paths where we have a Selection object available. More about that below.) Prior to Placement microversion 1.34, the only way to do this mapping was by reproducing much of the logic from GET /allocation_candidates locally to reverse engineer the associations. This was incomplete, imperfect, inefficient, and ugly. That workaround was nested in the call from fill_provider_mapping to fill_provider_mapping_based_on_allocation. Placement microversion 1.34 enhanced GET /allocation_candidates to return these mappings [1], and Nova started using 1.34 as of [2], so this commit makes fill_provider_mapping bypass fill_provider_mapping_based_on_allocations completely. We would love to get rid of the entire hack, but fill_provider_mapping_based_on_allocation is still used from finish_revert_resize to restore port bindings on a reverted migration. And when reverting a migration, we don't have allocation candidates with mappings, only the original source allocations. It is left to a future patch to figure out how to get around this, conceivably by saving the original mappings in the migration context. [1] https://docs.openstack.org/placement/train/specs/train/implemented/placement-resource-provider-request-group-mapping-in-allocation-candidates.html [2] I52499ff6639c1a5815a8557b22dd33106dcc386b Related to blueprint: placement-resource-provider-request-group-mapping-in-allocation-candidates Change-Id: I45e0b2b73f88b86a20bc70ddf4f9bb97c8ea8312 |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| playbooks | ||
| releasenotes | ||
| roles/run-post-test-hook | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .pre-commit-config.yaml | ||
| .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
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: