Bug 1033926

Summary: Cinder-documentation: Openstack End User Guide - transfer a volume
Product: Red Hat OpenStack Reporter: Yogev Rabl <yrabl>
Component: doc-User_GuideAssignee: Deepti Navale <dnavale>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: eharney, hateya, slong, yeylon
Target Milestone: ---Keywords: Documentation
Target Release: 4.0   
Hardware: x86_64   
OS: Linux   
URL: https://bugs.launchpad.net/openstack-manuals/+bug/1254429
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1038347 (view as bug list) Environment:
Last Closed: 2014-01-07 00:35:00 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:    
Bug Blocks: 1011085, 1038347    

Description Yogev Rabl 2013-11-24 12:00:20 UTC 
Description of problem:

The description of the process of volume transfer in the documentation lacks the prerequisites of the two servers, the volume and their relations.

1. how can the receiver discover the transferred volume if the two servers can communicate directly?
2. What is the procedure of the transfer if the administrator need to copy the volume to the disk and import the volume to the received Cinder?
3. Is there any preconfiguration in the donor/receiver?

-----------------------------------
Built: 2013-11-24T02:45:51 00:00
git SHA: 1440ab46a2a6510869c62f58c849fb687e3b17ae
URL: http://docs.openstack.org/user-guide/content/cli_manage_volumes.html
source File: file:/home/jenkins/workspace/openstack-user-guide/doc/common/section_cinder_cli_manage_volumes.xml
xml:id: cli_manage_volumes
Comment 3 Deepti Navale 2013-11-26 00:15:52 UTC 
Eric, can you please answer questions in comment 0 and we'll add the info.
Comment 4 Eric Harney 2013-12-04 16:57:50 UTC 
(In reply to Yogev Rabl from comment #0)
> 1. how can the receiver discover the transferred volume if the two servers
> can communicate directly?
Cinder doesn't handle this type of discovery AFAICT.  The upstream doc mentions that the donor should email the transfer id and auth key to the receiver.

> 2. What is the procedure of the transfer if the administrator need to copy
> the volume to the disk and import the volume to the received Cinder?
This sounds like a different feature -- see https://blueprints.launchpad.net/cinder/+spec/add-export-import-volumes .  This feature is only about changing ownership of a volume.

The upstream doc mentions something along these lines "data ingress system creates volume ... copies data ... transfers ownership", but this is not actually part of this functionality in Cinder.  The ability to transfer ownership just makes it possible to do something like this with other tools.

> 3. Is there any preconfiguration in the donor/receiver?
The assumption is that both users are tenants within the same deployment.  Otherwise, no.
Comment 6 Deepti Navale 2013-12-12 00:36:16 UTC 
No reviews received from Eric Harney for the gerrit change. Approved and merged this change as it was a minor update.