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 created.
For example: [lvm1] volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver volume_backend_name = lvm [lvm2] volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver volume_backend_name = lvm Then: 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 < [email protected]> 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 > | [email protected] > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
