List options for manage-existing APIs
Cinder currently has the ability to take over the management of existing volumes and snapshots ("manage existing") and to relinquish management of volumes and snapshots ("unmanage"). The API to manage an existing volume takes a reference, which is a driver-specific string that is used to identify the volume on the storage backend. This process is currently confusing and error
prone. This spec's purpose is to detail APIs for listing volumes and snapshots available for management to make this flow more user-friendly. Allowing the listing of available volumes/snapshots will allow for the creation of an easy-to-use GUI to migrate existing volumes to a new OpenStack environment, or to recover in the case the Cinder database is lost.
Blueprint information
- Status:
- Started
- Approver:
- Sean McGinnis
- Priority:
- Low
- Drafter:
- Avishay Traeger
- Direction:
- Approved
- Assignee:
- Avishay Traeger
- Definition:
- Approved
- Series goal:
- Accepted for rocky
- Implementation:
-
Started
- Milestone target:
-
rocky-2
- Started by
- Jay Bryant
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
List volumes/snapshots for manage-existing
Addressed by: https:/
List manageable volumes and snapshots
Gerrit topic: https:/
Addressed by: https:/
Map volume/snapshot manage extensions to v3
Addressed by: https:/
LVM driver: list manageable volumes and snapshots
Addressed by: https:/
[WIP] RBD: get manageable volumes
Addressed by: https:/
RBD: get manageable snapshots
Work Items
Dependency tree
* Blueprints in grey have been implemented.
