Placement Forbidden Traits in Requests

Registered by Chris Dent on 2018-03-01

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_candidates and GET /resource_providers.

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:
milestone icon rocky-1
Started by
Matt Riedemann on 2018-04-06
Completed by
Matt Riedemann on 2018-04-14

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/placement-forbidden-traits,n,z

Addressed by: https://review.openstack.org/548915
    Express forbidden traits in placement API

Approved for Rocky. -- mriedem 20180312

Addressed by: https://review.openstack.org/554665
    WIP: Parse placement forbidden traits query string

Addressed by: https://review.openstack.org/556472
    [placement] Filter resource providers by forbidden traits in db

Addressed by: https://review.openstack.org/556660
    Support forbidden traits in allocation_candidates in db

Addressed by: https://review.openstack.org/556819
    [placement] Parse forbidden traits in query strings

Addressed by: https://review.openstack.org/556820
    [placement] Support forbidden traits in API

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.