Bug 985953

Summary:	[RFE] Volume migration
Product:	Red Hat OpenStack	Reporter:	Eric Harney <eharney>
Component:	openstack-cinder	Assignee:	Eric Harney <eharney>
Status:	CLOSED ERRATA	QA Contact:	Yogev Rabl <yrabl>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.0	CC:	abaron, breeler, eharney, hateya, mlopes, sclewis, scohen, sgordon
Target Milestone:	---	Keywords:	FutureFeature, TestOnly
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/cinder/+spec/volume-migration
Whiteboard:	upstream_milestone_none upstream_status_implemented upstream_definition_approved
Fixed In Version:	openstack-cinder-2013.2-0.9.b3.el6ost	Doc Type:	Enhancement
Doc Text:	A feature has been added to OpenStack Block Storage which allows migrating a block storage volume from one backend to another. This is an admin-only interface used for manually invoking volume migration. It is useful for manual tuning and scripting.	Story Points:	---
Clone Of:
Clones:	988443 1045054 (view as bug list)		Environment:
Last Closed:	2013-12-20 00:13:12 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:	975499, 1045054, 1056108

Description Eric Harney 2013-07-18 15:06:56 UTC

This work will add an admin-only interface to manually invoke volume migration - "I want to move this volume to that specific backend". This is useful for manual tuning and scripting.

This initial version will be the simplest case - a detached volume with no snapshots. A later blueprint will handle cases of attached volumes and volumes with snapshots. Attaching/detaching during migration will not be allowed for now.

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

Comment 12 Yogev Rabl 2013-11-17 12:04:26 UTC

The verification of the RFE is blocked by Bug 1031010 .

Comment 17 errata-xmlrpc 2013-12-20 00:13:12 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