| 1 |
--- |
| 2 |
upgrade: |
| 3 |
- | |
| 4 |
After running the migration script to migrate CGs to |
| 5 |
generic volume groups, CG and group APIs work as follows. |
| 6 |
|
| 7 |
* Create CG only creates in the groups table. |
| 8 |
* Modify CG modifies in the CG table if the CG is in the |
| 9 |
CG table, otherwise it modifies in the groups table. |
| 10 |
* Delete CG deletes from the CG or the groups table |
| 11 |
depending on where the CG is. |
| 12 |
* List CG checks both CG and groups tables. |
| 13 |
* List CG Snapshots checks both the CG and the groups |
| 14 |
tables. |
| 15 |
* Show CG checks both tables. |
| 16 |
* Show CG Snapshot checks both tables. |
| 17 |
* Create CG Snapshot creates either in the CG or the groups |
| 18 |
table depending on where the CG is. |
| 19 |
* Create CG from Source creates in either the CG or the |
| 20 |
groups table depending on the source. |
| 21 |
* Create Volume adds the volume either to the CG or the |
| 22 |
group. |
| 23 |
* default_cgsnapshot_type is reserved for migrating CGs. |
| 24 |
* Group APIs will only write/read in/from the groups table. |
| 25 |
* Group APIs will not work on groups with default_cgsnapshot_type. |
| 26 |
* Groups with default_cgsnapshot_type can only be operated by |
| 27 |
CG APIs. |
| 28 |
* After CG tables are removed, we will allow default_cgsnapshot_type |
| 29 |
to be used by group APIs. |