[openstack-dev] [Cinder]Restrict volume creation based on type

Erlon Cruz sombrafam at gmail.com
Fri Jul 10 12:58:02 UTC 2015

Hi Eduard,

What extra_specs do you configured in this volume_type?
Yes you can force a volume to an specific node, or backend. You must
configure the volume_backend_name on cinder.conf, and add an extra spec
"volume_backend_name='same_as_in_cinder_conf'" on the volume type  you

For example:
volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver
volume_backend_name = lvm

volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver
volume_backend_name = lvm

cinder type-create lvm
$ cinder type-key lvm_node set volume_backend_name=lvm

On Fri, Jul 10, 2015 at 5:36 AM, Eduard Matei <
eduard.matei at cloudfounders.com> wrote:

> Hi,
> We've been testing a multi-node setup with our driver and ended up in a
> strange situation:
> - having a driver configured on multiple cinder nodes (But not all)
> - having a volume type (available)
> - creating a volume with specified volume type causes the volume to be
> created (attempted) on a node where the driver is not configured.
> We found something called "storage_availability_zone" but not quite
> understood it, and it looks like an extra choice in the "Create volume
> wizard" (which can be skipped/forgotten).
> So, question:
> - can we "force" a volume type to be tied to specific nodes? (something
> like availability zones, but determined based on volume type, not a
> separate setting)
> Thanks,
> --
> *Eduard Biceri Matei, Senior Software Developer*
> www.cloudfounders.com
>  | eduard.matei at cloudfounders.com
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150710/2ac9b067/attachment.html>

More information about the OpenStack-dev mailing list