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
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
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 '-'.
Adding Manila share groups spec:
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.
(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?