Bug 1256510

Summary:	[RFE] Cinder replication V2
Product:	Red Hat OpenStack	Reporter:	Sean Cohen <scohen>
Component:	openstack-cinder	Assignee:	Eric Harney <eharney>
Status:	CLOSED DUPLICATE	QA Contact:	nlevinki <nlevinki>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	eharney, sgotliv, yeylon
Target Milestone:	Upstream M3	Keywords:	FutureFeature
Target Release:	9.0 (Mitaka)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/cinder/+spec/replication-v2
Whiteboard:	upstream_milestone_liberty-3 upstream_definition_approved upstream_status_implemented
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:	A new scaled backend replication implementation between backends that leaves the bulk of the work up to the driver, while providing basic admin API methods to do things like enable/disable and fail-over. This first iteration of the new API supports only a single remote device, with limited tenants visibility.
Last Closed:	2015-11-24 11:10:05 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-24 19:14:52 UTC

The goal is to take some of the lessons learned from the first version of replication that was added in teh Juno release and make it something that is more widely usable by other backend devices.

This spec proposes a use of our entire tool-box to implement replication.
http://specs.openstack.org/openstack/cinder-specs/specs/liberty/replication_v2.html

    Capabilities - determine if we can even do anything related to replication
    Types/Extra-Specs - provide mechanism for vendor-unique custom info and help level out some of the unique aspects among the different back-ends.
    API Calls - provide some general API calls for things like enable, disable etc

Comment 3 Sergey Gotliv 2015-11-24 11:10:05 UTC


*** This bug has been marked as a duplicate of bug 1258645 ***