VMAX driver - Performance improvements when cloning a generic volume group
Bug #1713957 reported by
Ciara Stacke
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
Incomplete
|
Undecided
|
Ciara Stacke | ||
Bug Description
Currently, the user must wait for a clone generic volume group to be fully copied before the new group can be accessed. VMAX allows the target volumes to be read/ write accessible before all the tracks are fully copied, so it is unnecessary to force the user to wait for the full copy to complete.
| Changed in cinder: | |
| assignee: | nobody → Ciara Stacke (cstacke) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on cinder (master) | #1 |
| Changed in cinder: | |
| status: | In Progress → Incomplete |
To post a comment you must log in.
Change abandoned by Ciara Stacke (<email address hidden>) on branch: master
Review: https:/
Reason: There are issues with Unisphere that are unfortunately taking some time to rectify - abandoning this patch for the time being until they can be resolved