Placement Forbidden Traits in Requests
In order to satisfy placement requests where a workload wants to say it does _not_ want a certain trait to be in the returned allocation candidates or resource providers a new microversion is required that will add syntax to query parameters that filter both GET /allocation_
Blueprint information
- Status:
- Complete
- Approver:
- Sylvain Bauza
- Priority:
- Medium
- Drafter:
- Chris Dent
- Direction:
- Approved
- Assignee:
- Chris Dent
- Definition:
- Approved
- Series goal:
- Accepted for rocky
- Implementation:
-
Implemented
- Milestone target:
-
rocky-1
- Started by
- Matt Riedemann
- Completed by
- Matt Riedemann
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Express forbidden traits in placement API
Approved for Rocky. -- mriedem 20180312
Addressed by: https:/
WIP: Parse placement forbidden traits query string
Addressed by: https:/
[placement] Filter resource providers by forbidden traits in db
Addressed by: https:/
Support forbidden traits in allocation_
Addressed by: https:/
[placement] Parse forbidden traits in query strings
Addressed by: https:/
[placement] Support forbidden traits in API
Work Items
Dependency tree
* Blueprints in grey have been implemented.
