Implement generic share groups in Manila
Manila needs a grouping construct that, like shares, is a 1st-class atomic data type. Our experience with CGs has demonstrated the complexity of adding a grouping capability, yet there are other use cases such as migration, replication, and backup in which some storage controllers could only offer such features on share groups. CGs also highlighted the poor optics of an advanced feature with comparatively little potential for vendor support. And adding new grouping constructs for each new feature is not technically feasible. All of the above may be addressed by generic groups, which we think is a clean extension to the original architecture of Manila.
Blueprint information
- Status:
- Complete
- Approver:
- Ben Swartzlander
- Priority:
- Undefined
- Drafter:
- Clinton Knight
- Direction:
- Needs approval
- Assignee:
- Valeriy Ponomaryov
- Definition:
- Review
- Series goal:
- Accepted for ocata
- Implementation:
- Implemented
- Milestone target:
- ocata-3
- Started by
- Clinton Knight
- Completed by
- Ben Swartzlander
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add spec for Manila share groups
Gerrit topic: https:/
Addressed by: https:/
Rename consistency group modules to share groups
Addressed by: https:/
Manila Share Groups
Gerrit topic: https:/
Addressed by: https:/
[Tempest] Add functional tests for share groups feature
Addressed by: https:/
Upgrade share group snapshot members DB model
Addressed by: https:/
[Share groups] Add scheduler filter ConsistentSnaps
Addressed by: https:/
[Share Groups] Add availability zone support
Addressed by: https:/
[Share Groups] Add two new fields to SG API object
Gerrit topic: https:/