Add generation to aggregate association representation

Registered by Chris Dent

To support the management of aggregates via the report client and ProviderTree mechanism, especially in the context of virt drivers that may wish to manage aggregates themselves, we need to make it so associating aggregates to resource providers makes use of the resource provider generation. This means sending and receiving the generation value in the request and response bodies of PUT and GET /resource_providers/{uuid}/aggregates. If the generation is out of sync on PUT a 409 should be raised.

Blueprint information

Status:
Complete
Approver:
Dan Smith
Priority:
Low
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
Completed by
Matt Riedemann

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#/q/topic:bp/placement-aggregate-generation

Addressed by: https://review.openstack.org/540447
    Add generation support in aggregate association

Addressed by: https://review.openstack.org/544092
    Clarify old microversion behavior

Addressed by: https://review.openstack.org/548237
    Update placement aggregates spec to clarify generation handling

Addressed by: https://review.openstack.org/548249
    placement: generation in provider aggregate APIs

Merged placement API microversion 1.19 for this blueprint on March 17, 2018.

Consumed by: https://review.openstack.org/556669
    Handle agg generation conflict in report client

Gerrit topic: https://review.openstack.org/#q,topic:reportclient-aggregate-generation,n,z

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.