Bug 1317268

Summary:	[RFE][cinder] Volume Replication API v2.1
Product:	Red Hat OpenStack	Reporter:	Sean Cohen <scohen>
Component:	openstack-cinder	Assignee:	Eric Harney <eharney>
Status:	CLOSED ERRATA	QA Contact:	lkuchlan <lkuchlan>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	unspecified	CC:	egafford, eharney, jjoyce, nlevinki, srevivo
Target Milestone:	ga	Keywords:	FutureFeature, TestOnly, ZStream
Target Release:	9.0 (Mitaka)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/cinder/+spec/replication
Whiteboard:	upstream_milestone_none upstream_definition_approved upstream_status_implemented
Fixed In Version:	openstack-cinder-8.0.0-4.el7ost	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	1317347 (view as bug list)		Environment:
Last Closed:	2016-08-24 12:53:19 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:	1317347, 1342858

Description Sean Cohen 2016-03-13 15:44:51 UTC

Problem description

The existing design is great for some backends, but is challenging for many devices to fit in to. It’s also filled with pitfalls with the question of managed/unmanaged, not to mention trying to deal with failing over some volumes and leaving others. The concept of failing over on a volume basis instead of on a device basis while nice for testing doesn’t fit well into the intended use case and results in quite a bit of complexity and also is not something that a number of backends can even support.

Use Cases

This is intended to be a DR mechanism. The model Use Case is a catastrophic event occurring on the backend storage device, but some or all volumes that were on the primary backend may have been replicated to another backend device in which case those volumes may still be accessible.


Full spec: https://specs.openstack.org/openstack/cinder-specs/specs/mitaka/cheesecake.html

Comment 2 Mike McCune 2016-03-28 22:34:54 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 9 errata-xmlrpc 2016-08-24 12:53:19 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-1761.html