Add generation to aggregate association representation
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_
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:
- rocky-1
- Started by
- Matt Riedemann
- Completed by
- Matt Riedemann
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add generation support in aggregate association
Addressed by: https:/
Clarify old microversion behavior
Addressed by: https:/
Update placement aggregates spec to clarify generation handling
Addressed by: https:/
placement: generation in provider aggregate APIs
Merged placement API microversion 1.19 for this blueprint on March 17, 2018.
Consumed by: https:/
Handle agg generation conflict in report client
Gerrit topic: https:/