Enable Trove to optionally restict the Cinder backend used for Trove Volumes
It's likely that a Trove admin might want to restrict the type of Cinder backend used for Trove Volumes (e.g. he may want to only use a highly durable backend for database volumes). Cinder allows us to specify a volume_type to be able to do this. This BP suggests making the volume_type param in cinder an optional, configurable parameter to be read from the Trove Config.
Blueprint information
- Status:
- Complete
- Approver:
- Nikhil Manchanda
- Priority:
- Medium
- Drafter:
- Nikhil Manchanda
- Direction:
- Approved
- Assignee:
- Steve Leon
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
- Implemented
- Milestone target:
- 2014.2
- Started by
- Nikhil Manchanda
- Completed by
- Nikhil Manchanda
Related branches
Related bugs
Sprints
Whiteboard
We discussed this at the bp-review (http://
Gerrit topic: https:/
Addressed by: https:/
Enable trove to specify cinder volume_type when creating a volume