Enable Trove to optionally restict the Cinder backend used for Trove Volumes

Registered by Nikhil Manchanda on 2014-04-18

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:
milestone icon 2014.2
Started by
Nikhil Manchanda on 2014-07-07
Completed by
Nikhil Manchanda on 2014-07-16

Related branches

Sprints

Whiteboard

We discussed this at the bp-review (http://eavesdrop.openstack.org/meetings/trove_bp_review/2014/trove_bp_review.2014-04-21-17.59.html) and we decided to go this route, but leverage the capabilities API to do so.

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

Addressed by: https://review.openstack.org/104370
    Enable trove to specify cinder volume_type when creating a volume

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.