Clarify `resources` query param for /r_p and /a_c
It was pointed out [1] that the semantic difference between how the `resources` query parameter is handled by GET /resource_providers versus GET /allocation_candidates is not clear based on the API reference descriptions, which are identical. This change set clarifies the wording for both, making it clear that a) allocations are taking into account; and b) GET /allocation_candidates is working with groups of providers that must *collectively* satisfy the resource specification. [1] https://review.openstack.org/#/c/547056/2/specs/rocky/approved/traits-on-list-resource-providers.rst@33 Change-Id: Ia2a4f8f80ec68dd9c95e084c292a2fe2d6ec1b2d
This commit is contained in:
parent
7b51fead3f
commit
9abccf8f77
|
@ -104,7 +104,7 @@ resources_query:
|
|||
description: |
|
||||
A comma-separated list of strings indicating an amount of
|
||||
resource of a specified class that a provider must have the
|
||||
capacity to serve::
|
||||
capacity and availability to serve::
|
||||
|
||||
resources=VCPU:4,DISK_GB:64,MEMORY_MB:2048
|
||||
min_version: 1.4
|
||||
|
@ -114,8 +114,8 @@ resources_query_required:
|
|||
required: true
|
||||
description: |
|
||||
A comma-separated list of strings indicating an amount of
|
||||
resource of a specified class that a provider must have the
|
||||
capacity to serve::
|
||||
resource of a specified class that providers in each allocation request
|
||||
must *collectively* have the capacity and availability to serve::
|
||||
|
||||
resources=VCPU:4,DISK_GB:64,MEMORY_MB:2048
|
||||
trait_associated:
|
||||
|
|
Loading…
Reference in New Issue