Allow setting of volume backend name while creating volume type

Registered by Julie Gravel on 2014-10-16

Currently when a user creates a new volume type through the “Create Volume Type” action in Admin -> Volumes -> Volume Types tab, there is only one input field that the user can provide a value: volume type name. But the process of setting up a new volume type can also involve setting up volume backend name associated with the volume type. To set up the volume backend name, a user creates a new Extra Specs key/value pair through the “View Extra Specs” action. This is an additional and separate process from the volume type creation process. These two processes should be combined into one clean process that allows the setting of volume backend right within the creation of a new volume type.

Horizon should provide a process that helps to guide users into completing a task in a more intuitive way which consumes less time.

The purpose of this blueprint is to combine the steps to set up volume backend name for a volume type into the volume type creation process.

A new field “Volume Backend Name” field will be added to the “Create Volume Type” dialog, below the volume type name field. The input field for “Volume Backend Name” will be a dropdown menu containing a list of available volume backend names for users to select from. The list of available volume backend names will be provided by a Cinder command. The dropdown menu will also include “None” as an option for the case that users are not ready to specify the volume backend name.

Outside Dependencies:
N/A (The required Cinder API is already available)

Requirements Update Required:

Doc Impact:

Blueprint information

David Lyle
Julie Gravel
Julie Gravel
Series goal:
Milestone target:
Started by
David Lyle on 2014-12-16
Completed by
David Lyle on 2016-10-28

Related branches



Gerrit topic:,topic:bp/vol-type-set-backend-name,n,z

Addressed by:
    Add Volume Backend Name to Create Volume Type

amotoki (Nov 27, 2014) - The proposal looks good and reasonable.
Is there any progress on Cinder spec? The proposed cinder-spec has no progress since Oct 30.

jgravel (Nov 28, 2014) - Thanks Akiriho for looking at this blueprint. The reason that the Cinder spec showed no progress was because there were face-to-face discussions happened at the Paris summit among Cinder people. The decision came out of those discussions was that Cinder already provided the volume backend names in the scheduler_stats API call. And that there was no need for a new API call as proposed in the Cinder spec ( So I abandoned the spec. I will update the Outside Dependencies section of this blueprint shortly.

amotoki (Dec 4, 2014) - Thanks for the clarification. I added some comment to "Outside Dependencies" section: "the required Cinder API is already available".
The BP looks good for approval.

[david-lyle | 2015-03-03] python-cinderclient hasn't released making this unlikely for Kilo, moving out.

Gerrit topic:,topic:vol-type-set-backend-name,n,z


Work Items

This blueprint contains Public information 
Everyone can see this information.


No subscribers.