How do I nova boot from image create volume and specify the cinder backend to use?

asked 2015-01-14 16:43:05 -0600

med gravatar image

nova boot --block-device seems to lack a way to boot from an image and create a new volume on a SPECIFIC CINDER BACKEND device. How do I do that? I have 3 different cinder backends.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2015-01-14 17:41:54 -0600

updated 2015-01-14 17:43:15 -0600

I believe this should work, you can set up a specific volume type to create on a specific Cinder backend, then you can nova boot with the --block-device-mapping switch and specify the volume type.

The volume_type must be defined in the volume_type table in the database. When creating a volume for a particular backend (or group of > 1 backends) the volume_type is passed in. There can be > 1 backend per volume_type, and the capacity scheduler kicks in and keeps the backends of a particular volume_type even. In order to group a volume_type to a backend, you must define extra specs for the type.

cinder --os-username admin --os-tenant-name admin type-key lvm set volume_backend_name=LVM_iSCSI

then you can just nova boot with the --block-device-mapping option and make sure you set the specific type of volume.

 --block-device-mapping <dev-name=mapping>
                                Block device mapping in the format <dev-

Reference Material:

edit flag offensive delete link more


No. The type in the --block-device does not refer to the volume type, but the device type. Quoted from the link below: " type=device type (e.g. disk, cdrom, ...; defaults to 'disk') " (

strony_zhang gravatar imagestrony_zhang ( 2015-08-07 11:10:48 -0600 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools



Asked: 2015-01-14 16:43:05 -0600

Seen: 1,391 times

Last updated: Jan 14 '15