Volume Retype

Registered by Avishay Traeger on 2013-05-21

This will enable a user to change a volume's type after its creation. This is useful for changing QoS settings (e.g., a volume that sees heavy usage once a month), changing properties (e.g., compressed/uncompressed), etc.

Migrating the volume will be necessary if:
1. The volume's current host cannot handle the new type
2. The volume's driver cannot change the type

In either case, migration will be policy-based, where the policy is passed via scheduler hints. The options are:
1. Never migrate
2. Migrate if necessary (default)
3. Migrate if necessary using host-based copy

This blueprint does not cover QoS and encryption, which require special handling.

Blueprint information

Status:
Complete
Approver:
Avishay Traeger
Priority:
Medium
Drafter:
Avishay Traeger
Direction:
Approved
Assignee:
Avishay Traeger
Definition:
Approved
Series goal:
Accepted for icehouse
Implementation:
Implemented
Milestone target:
milestone icon 2014.1
Started by
Avishay Traeger on 2013-10-27
Completed by
Avishay Traeger on 2014-01-08

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/volume-retype,n,z

Addressed by: https://review.openstack.org/44881
    Add ability to modify volume type

Addressed by: https://review.openstack.org/60715
    Use mock for scheduler tests

Addressed by: https://review.openstack.org/65635
    Add support for volume retype of Storwize/SVC driver

Addressed by: https://review.openstack.org/84991
    Change volume retype behavior when driver raise exception

Gerrit topic: https://review.openstack.org/#q,topic:storpool-block-driver,n,z

Addressed by: https://review.openstack.org/188730
    StorPool: implement volume retyping and migrations

Addressed by: https://review.openstack.org/188725
    Re-add the StorPool distributed storage driver

Gerrit topic: https://review.openstack.org/#q,topic:bp/storpool-block-driver,n,z

(?)

Work Items