Bug 1300425

Summary: [RFE][manila] Consistency Groups (being replaced by Generic Share Groups)
Product: Red Hat OpenStack Reporter: Sean Cohen <scohen>
Component: openstack-manilaAssignee: Tom Barron <tbarron>
Status: CLOSED UPSTREAM QA Contact: Dustin Schoenbrun <dschoenb>
Severity: medium Docs Contact: Don Domingo <ddomingo>
Priority: medium    
Version: 7.0 (Kilo)CC: adahms, dschoenb, egafford, jschluet, lbopf, nlevinki, rhos-flags, sgotliv, tbarron
Target Milestone: ---Keywords: FutureFeature, TechPreview, TestOnly, ZStream
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/manila/+spec/manila-consistency-groups
Whiteboard:
Fixed In Version: Doc Type: Technology Preview
Doc Text:
With the Manila service, you can now create shares within Consistency Groups to guarantee snapshot consistency across multiple shares. Driver vendors must report this capability and implement its functions to work according to the back end. This feature is not recommended for production cloud environments, as it is still in its experimental stage.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-23 15:51:50 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:

Description Sean Cohen 2016-01-20 18:41:22 UTC
Consistency groups are a mechanism to allow multiple filesystem shares to be guaranteed snapshots are able to be created at the exact same point in time. For example, a database may have its tables, logs, and configuration on separate volumes. If we wanted to restore the database from a previous point in time, it would only make sense to restore the logs, tables, and configuration together from the exact same point in time. 


Full spec can be found at: https://wiki.openstack.org/wiki/Manila/design/manila-liberty-consistency-groups

Comment 3 Mike McCune 2016-03-28 23:38:32 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 4 Andrew Dahms 2016-03-31 01:12:21 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 7 Sean Cohen 2016-09-23 15:51:50 UTC
Adding Manila share groups spec:

Comment 8 Tom Barron 2017-02-08 13:18:48 UTC
Consistency Group API was replaced by Generic Share Group API in ocata but implementation and testing of generic share groups is rolling over into pike.  ConsistencyGroups and Generic Share Groups are Experimental API features - i.e., their REST headers indicate that they are Experimental and that is advertised to mean that the API can change or even be eliminated (as happened with Consistency Groups) in future releases.

I am moving the target release to Pike as that is the very earliest that this experimental feature will be available and testable.

Comment 9 Lucy Bopf 2017-05-15 06:08:52 UTC
(In reply to Tom Barron from comment #8)
> Consistency Group API was replaced by Generic Share Group API in ocata but
> implementation and testing of generic share groups is rolling over into
> pike.  ConsistencyGroups and Generic Share Groups are Experimental API
> features - i.e., their REST headers indicate that they are Experimental and
> that is advertised to mean that the API can change or even be eliminated (as
> happened with Consistency Groups) in future releases.
> 
> I am moving the target release to Pike as that is the very earliest that
> this experimental feature will be available and testable.

Hi Tom,

The text in the 'Doc Text' field is currently set to be included in the RHOSP 11 Release Notes, because the bug is still flagged for rhos-11.0.

Should the release flag also be moved to rhos-12.0?