openstack/placement
Code Issues Proposed changes

Follow up fix for same_subtree documentation

Browse Source 
This patch fixes incorrect usages of fixed articles changing them to
indefinite articles in same_subtree documentation.

Change-Id: I6ba2e2f13400b4c2ae9a44cad7a1fc9a9e39b41d
Story: 2005575
Task: 30784
This commit is contained in:
Tetsuro Nakamura 2019-07-09 10:23:54 +00:00
parent 34c1dd88b3
commit efaa36443f
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
api-ref/source/parameters.yaml
View File

@ -197,7 +197,7 @@ allocation_candidates_same_subtree:
A comma-separated list of request group suffix strings ($S). Each must
exactly match a suffix on a granular group somewhere else in the request.
Importantly, the identified request groups need not have a resources[$S].
If this is provided, at least one of the resource providers satisfying the
If this is provided, at least one of the resource providers satisfying a
specified request group must be an ancestor of the rest.
The ``same_subtree`` query parameter can be repeated and each repeat group
is treated independently.

2
placement/rest_api_version_history.rst
View File

@ -662,6 +662,6 @@ Add support for the ``same_subtree`` query parameter to the ``GET
group suffix strings $S. Each must exactly match a suffix on a granular group
somewhere else in the request. Importantly, the identified request groups need
not have a resources$S. If this is provided, at least one of the resource
providers satisfying the specified request group must be an ancestor of the
providers satisfying a specified request group must be an ancestor of the
rest. The ``same_subtree`` query parameter can be repeated and each repeat
group is treated independently.

2
releasenotes/notes/allocation-candidate-same_subtree-aeed7b2570293dfb.yaml
View File

@ -6,6 +6,6 @@ features:
list of request group suffix strings ($S). Each must exactly match a suffix
on a granular group somewhere else in the request. Importantly, the
identified request groups need not have a resources$S. If this is provided,
at least one of the resource providers satisfying the specified request
at least one of the resource providers satisfying a specified request
group must be an ancestor of the rest. The ``same_subtree`` query parameter
can be repeated and each repeated group is treated independently.