Allow no body PUT to create custom resource class in placement API

Registered by Chris Dent on 2017-03-22

A new microversion of the placement API will be created to adjust the PUT /resource_classes/{resource_class} handling to allow the creation of a new or validation of existing resource class in a single request. To put it another way, the PUT request will be made idempotent. The first request will result in a 201 and subsequent requests will result in a 204.

This will replace the currently flawed handling on the same URL which allows a custom resource class to be renamed. This is not functionality we want or need and in fact could be considered dangerous.

For more information see: http://lists.openstack.org/pipermail/openstack-dev/2017-March/114136.html

Blueprint information

Status:
Complete
Approver:
Sylvain Bauza
Priority:
Low
Drafter:
Chris Dent
Direction:
Approved
Assignee:
Chris Dent
Definition:
Approved
Series goal:
Accepted for pike
Implementation:
Implemented
Milestone target:
milestone icon pike-2
Started by
Matt Riedemann on 2017-04-14
Completed by
Matt Riedemann on 2017-06-09

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/placement-put-resource-class,n,z

Addressed by: https://review.openstack.org/448791
    WIP: [placement] Idempotent PUT /resource_classes/{name}

Addressed by: https://review.openstack.org/453732
    A spec for idempotent custom resource classe creation

Addressed by: https://review.openstack.org/447625
    [placement] Allow PUT and POST without bodies

Addressed by: https://review.openstack.org/456915
    Update resource tracker to PUT custom resource classes

Approved for Pike. -- mriedem 20170414

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.