Add metadata to all share resources
Metadata encompasses flexible key=value pairs to attach useful optional/additional information to resources. In Manila, there are several resources that users interact with. The goal of this specification is that all "user facing" resources must metadata and we must provide a way to manipulate them. User facing resources at this time:
* User facing resources
* Shares
* Snapshots
* Export Locations
* Share Replicas
* Share Groups
* Share Group Snapshots
* Security Services
* Share Networks
* Share Network Subnets
1) The user interaction/
2) Resources must be filterable by metadata
3) Metadata implementation must be consistent across resources and conforming to the specification from the API SIG: https:/
Blueprint information
- Status:
- Started
- Approver:
- Goutham Pacha Ravi
- Priority:
- Medium
- Drafter:
- Goutham Pacha Ravi
- Direction:
- Approved
- Assignee:
- Ashley Rodriguez
- Definition:
- Approved
- Series goal:
- Accepted for zed
- Implementation:
-
Slow progress
- Milestone target:
-
zed-rc1
- Started by
- Goutham Pacha Ravi
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Refactoring of the metadata APIs happened in the Yoga cycle.
Zed cycle plans will be discussed at the PTG: https:/
Gerrit topic: https:/
Addressed by: https:/
Fix incorrect extend syntax
