Bug 1033926 - Cinder-documentation: Openstack End User Guide - transfer a volume
Summary: Cinder-documentation: Openstack End User Guide - transfer a volume
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: doc-User_Guide
Version: 4.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: 4.0
Assignee: Deepti Navale
QA Contact: ecs-bugs
URL: https://bugs.launchpad.net/openstack-...
Whiteboard: storage
Depends On:
Blocks: 1011085 1038347
TreeView+ depends on / blocked
 
Reported: 2013-11-24 12:00 UTC by Yogev Rabl
Modified: 2016-04-27 00:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1038347 (view as bug list)
Environment:
Last Closed: 2014-01-07 00:35:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.