openstack
/
placement
Code Issues Proposed changes

Merge "Spec: Support filtering by forbidden aggregates 2"

This commit is contained in:
Zuul 2019-03-28 17:09:11 +00:00 committed by Gerrit Code Review
parent f8089dfbec bbc2af0b2a
commit 15e3e8c6c3
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/source/specs/train/approved/2005297-negative-aggregate-membership.rst
View File

@ -170,6 +170,22 @@ A new microversion will be created which will update the validation for the
as a prefix to the ``in:`` prefix to express that the prefixed aggregate (or
the aggregates) is to be excluded from the results.
We do not return 400 if an agg UUID is found on both the positive and negative
sides of the request. For example::
&member_of=in:<agg1>,<agg2>&member_of=!<agg2>
The first member_of would return all resource_providers in either agg1 or agg2,
while the second member_of would eliminate those in agg2. The result will be a
200 containing just those resource_providers in agg1. Likewise, we do not
return 400 for cases like::
&member_of=<agg1>&member_of=!<agg1>
As in the previous example, we return 200 with empty results, since this is a
syntactically valid request, even though a resource provider cannot be both
inside and outside of agg1 at the same time.
Security impact
---------------