deb-cinder/releasenotes/notes/operate-migrated-groups-with-cp-apis-e5835c6673191805.yaml
xing-yang 44ebdd2252 CG API changes for migrating CGs
CG APIs work as follows:
 * Create CG - Create only in groups table
 * Modify CG - Modify in CG table if CG in CG table, otherwise modify
               in groups table.
 * Delete CG - Delete from CG or groups table depending on where it is
 * List CG - Check both CG and groups tables
 * List CG snapshots - Check both CG and groups tables
 * Show CG - Check both tables
 * Show CG snapshot - Check both tables
 * Create CG snapshot - Create either in CG or groups table depending on
                        the CG.
 * Create CG from source - Create in either CG or groups table
                           depending on the source.
 * Create volume - Add volume either to CG or group

Additional notes:
 * default_cgsnapshot_type is reserved for migrating CGs.
 * Group APIs will only write/read in/from the groups table.
 * Group APIs won't work on groups with default_cgsnapshot_type.
 * Groups with default_cgsnapshot_type can only be operated by CG APIs.
 * After CG tables are removed, we'll allow default_cgsnapshot_type
   to be used by group APIs.

Partial-Implements: blueprint generic-volume-group
Change-Id: Idd88a5c9587023a56231de42ce59d672e9600770
2016-11-22 19:08:20 -05:00

30 lines
1.2 KiB
YAML

---
upgrade:
- |
After running the migration script to migrate CGs to
generic volume groups, CG and group APIs work as follows.
* Create CG only creates in the groups table.
* Modify CG modifies in the CG table if the CG is in the
CG table, otherwise it modifies in the groups table.
* Delete CG deletes from the CG or the groups table
depending on where the CG is.
* List CG checks both CG and groups tables.
* List CG Snapshots checks both the CG and the groups
tables.
* Show CG checks both tables.
* Show CG Snapshot checks both tables.
* Create CG Snapshot creates either in the CG or the groups
table depending on where the CG is.
* Create CG from Source creates in either the CG or the
groups table depending on the source.
* Create Volume adds the volume either to the CG or the
group.
* default_cgsnapshot_type is reserved for migrating CGs.
* Group APIs will only write/read in/from the groups table.
* Group APIs will not work on groups with default_cgsnapshot_type.
* Groups with default_cgsnapshot_type can only be operated by
CG APIs.
* After CG tables are removed, we will allow default_cgsnapshot_type
to be used by group APIs.