Volume Retype
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/
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:
-
2014.1
- Started by
- Avishay Traeger
- Completed by
- Avishay Traeger
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add ability to modify volume type
Addressed by: https:/
Use mock for scheduler tests
Addressed by: https:/
Add support for volume retype of Storwize/SVC driver
Addressed by: https:/
Change volume retype behavior when driver raise exception
Gerrit topic: https:/
Addressed by: https:/
StorPool: implement volume retyping and migrations
Addressed by: https:/
Re-add the StorPool distributed storage driver
Gerrit topic: https:/