06256d86c7
This changes the handling required for creating the 'mappings' output in the allocation_requests section of the GET /allocation_candidates response. Whereas before they were tracked as a suffix on the AllocationRequestResource object, this became untenable when it was realized (see the linked Story) that sometimes multiple request groups (and thus suffixes) can consume resources from the same provider and the original implementation did not account for this. Change Ifb687698dd1aa434781d06c7f111d8969120bf71 provides a fix for this but it is represents some cognitive and maintenance issues because it associates a vector value with a scalar concept. That is: it is illogical for an AllocationRequestResource (a representation of single consumption of a resource) with multiple suffixes doing that consumption. Instead, a new mappings attribute is added to AllocationRequest. This is probably where it should have been from the start, because the things we want to manage are: * mappings * in an allocation_request All existing tests pass. An additional test, borrowed from Ifb687698dd1aa434781d06c7f111d8969120bf71 , is also included to make sure we cover some of the ideas raised in that patch. Change-Id: Iba590d618fa493a4516d41f6b4ad5b5d0a8a07cb Story: #2006068
If you are viewing this README on GitHub, please be aware that placement development happens on OpenStack git and OpenStack gerrit.
Team and repository tags
OpenStack Placement
OpenStack Placement provides an HTTP service for managing, selecting, and claiming providers of classes of inventory representing available resources in a cloud.
API
To learn how to use Placement'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 Placement, 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 Placement, please see the contents of CONTRIBUTING.rst.
Further developer focused documentation is available at: