Mechanism to transfer ownership of a Cinder volume

Registered by Dermot Tynan on 2013-03-01

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:
milestone icon 2013.2
Started by
Dermot Tynan on 2013-05-14
Completed by
John Griffith on 2013-06-04

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/This,n,z

Addressed by: https://review.openstack.org/29227
    Implement DB migration for volume transfer BP

This seems like a potential use case for https://blueprints.launchpad.net/glance/+spec/image-transfer-service, any thoughts there?

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.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.