Mechanism to transfer ownership of a Cinder volume
There is a need to support transferring of Cinder Volumes from one customer to another. An example might be where a specialty consultancy produces bespoke bootable volumes or volumes with large data sets. Once the volume is created, it can be transferred to the end customer using this process. Similarly, for bulk import of data to the cloud, the data ingress system can create a new cinder volume, copy the data from the physical device, and then transfer ownership of the device to the end-user.
Blueprint information
- Status:
- Complete
- Approver:
- John Griffith
- Priority:
- Medium
- Drafter:
- Dermot Tynan
- Direction:
- Approved
- Assignee:
- Ollie Leahy
- Definition:
- Approved
- Series goal:
- Accepted for havana
- Implementation:
-
Implemented
- Milestone target:
-
2013.2
- Started by
- Dermot Tynan
- Completed by
- John Griffith
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Implement DB migration for volume transfer BP
This seems like a potential use case for https:/
Not sure that there's an overlap here, this blueprint is about changing the ownership (user/project) of a cinder volume, not moving data around.