Bug 1258060

Summary:	[RFE][manila] Share Migration
Product:	Red Hat OpenStack	Reporter:	Sean Cohen <scohen>
Component:	openstack-manila	Assignee:	Sergey Gotliv <sgotliv>
Status:	CLOSED ERRATA	QA Contact:	Dustin Schoenbrun <dschoenb>
Severity:	medium	Docs Contact:	Don Domingo <ddomingo>
Priority:	medium
Version:	unspecified	CC:	adahms, dschoenb, jschluet, mlopes, sgotliv
Target Milestone:	---	Keywords:	FutureFeature, TechPreview
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/manila/+spec/share-migration
Whiteboard:
Fixed In Version:	openstack-manila-1.0.0-2.el7ost	Doc Type:	Technology Preview
Doc Text:	You can now migrate shares between back ends within Manila. Manila performs the migration using a vendor-agnostic approach, however, driver vendors are able to implement their own optimized migration functions (when the migration involves backends or pools related to the same vendor). This feature is still in the experimental stage, and is not recommended for production use. At present, Manila itself remains a technology preview service.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-07 21:05:33 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:

Description Sean Cohen 2015-08-28 20:17:05 UTC

Share migration is a feature to allow move shares from backend to backend.
Upon implementing Share Migration, the Share re-type use case can be implemented, using Migration.

https://blueprints.launchpad.net/manila/+spec/share-migration

Comment 5 Andrew Dahms 2016-03-31 01:12:33 UTC

The doc text for this bug has been incorporated into the formal Technology Preview section, and does not need to be collected from this bug.

Changing 'requires_doc_text' to '-'.

Comment 8 errata-xmlrpc 2016-04-07 21:05:33 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.

https://rhn.redhat.com/errata/RHEA-2016-0603.html