Expose a volume's backend to admin
Registered by
Avishay Traeger
Expose a volume's backend name and class to admins. This is useful knowledge for admins in general (i.e., "this volume is giving poor performance, i'd like to investigate on the backend"), and is specifically useful as a basis for an admin interface for
volume migration (i.e., admin says "migrate this volume to that back-end").
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Avishay Traeger
- Direction:
- Needs approval
- Assignee:
- Avishay Traeger
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Avishay Traeger
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Expose volume backend information to admins.
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
