d38844e390
In microversion 1.34 add a 'mappings' key to each allocation request. Its value is dict keyed by resource group suffixes with values of a list of resource providers satisfying that group. To preserve symmetry, the mappings key may be sent back when writing allocations so the schema for POST and PUT allocations and POST /reshaper are updated. api history, api-ref and reno are added Change-Id: Ie78ed7e050416d4ccb62697ba608131038bb4303 Story: 2005575 Task: 33536
15 lines
838 B
YAML
15 lines
838 B
YAML
---
|
|
features:
|
|
- |
|
|
In microversion 1.34_ the body of the response to a
|
|
``GET /allocation_candidates`` request_ has been extended to include a
|
|
``mappings`` field with each allocation request. The value is a dictionary
|
|
associating request group suffixes with the uuids of those resource
|
|
providers that satisfy the identified request group. For convenience, this
|
|
mapping can be included in the request payload for ``POST /allocations``,
|
|
``PUT /allocations/{consumer_uuid}``, and ``POST /reshaper``, but it will
|
|
be ignored.
|
|
|
|
.. _1.34: https://docs.openstack.org/placement/latest/placement-api-microversion-history.html#request-group-mappings-in-allocation-candidates
|
|
.. _request: https://developer.openstack.org/api-ref/placement/?expanded=list-allocation-candidates-detail#list-allocation-candidates
|