Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 985458

Summary: [RFE] Transfer ownership of volumes
Product: Red Hat OpenStack Reporter: Eric Harney <eharney>
Component: openstack-cinderAssignee: Eric Harney <eharney>
Status: CLOSED ERRATA QA Contact: Yogev Rabl <yrabl>
Severity: unspecified Docs Contact: yeylon <yeylon>
Priority: medium    
Version: 4.0CC: breeler, eharney, mlopes, sclewis, slong, srevivo
Target Milestone: Upstream M2Keywords: FutureFeature, OtherQA
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/cinder/+spec/volume-transfer
Whiteboard:
Fixed In Version: openstack-cinder-2013.2-0.4.b2.el6ost Doc Type: Enhancement
Doc Text:
Red Hat OpenStack now allows the transfer of ownership of Block Storage Volumes, by providing a mechanism to let another tenant take ownership of a volume. This can be used, for instance, when bespoke bootable volumes or volumes with large data sets are produced by a supplier, and then transferred to a customer. The process requires that both parties agree to the operation and can securely exchange an authorization key. Once the volume is created, it can be transferred to the end-user using this process.
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-19 23:55:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 988538    
Bug Blocks: 975499    

Description Eric Harney 2013-07-17 14:18:30 UTC
Support transferring of Cinder Volumes from one customer to another

https://blueprints.launchpad.net/cinder/+spec/volume-transfer

Comment 3 Scott Lewis 2013-08-01 17:10:11 UTC
Changed Priority to match upstream

Comment 10 errata-xmlrpc 2013-12-19 23:55:30 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2013-1859.html