This post describes how to setup a Nimble Storage array within a cinder multi backend configuration, running OpenStack Icehouse.
If you are new to OpenStack or cinder, you might be asking why should you run single-backend vs multi-backend.
Basically, single-backend means you are using a single storage array/single group of arrays as your backend storage. In a multi backend configuration, you might have storage arrays from multiple vendors or you might just have different Nimble Storage arrays which provide several levels of performance. For example, you might want to use your CS700 as high-performance storage and your CS220 as a less performance intensive storage.
- Upload your Cinder driver to /usr/lib/python2.6/site-packages/cinder/volume/drivers
- Add theNimbleCinderparameters to /etc/cinder/cinder.conf as a new section
#Nimble Cinder Configuration [nimble-cinder] san_ip=management-ip san_login=admin_user san_password=password volume_driver=cinder.volume.drivers.nimble.NimbleISCSIDriver
- Add [nimble-cinder] to enabled-backend.Ifenabled-backends does not yet exist in your cinder.conf file, please add the following line:
enabled_backends=nimble-cinder,any_additional_backends
- Create a new volume type for the nimble-cinder backend:
root@TS-Training-OS-01 nova(keystone_admin)]# cinder type-create nimble1
- Next, link the backend name to the volume type:
root@TS-Training-OS-01 nova(keystone_admin)]# cinder type-key nimble1 set volume_backend_name=nimble-cinder
- Restartcinder-api, cinder-scheduler and cinder-volume
root@TS-Training-OS-01 (keystone_admin)]# service openstack-cinder-scheduler restart Stopping openstack-cinder-scheduler: [ OK ] Starting openstack-cinder-scheduler: [ OK ] [root@TS-Training-OS-01 (keystone_admin)]# service openstack-cinder-api restart Stopping openstack-cinder-api: [ OK ] Starting openstack-cinder-api: [ OK ] [root@TS-Training-OS-01 (keystone_admin)]# service openstack-cinder-volume restart Stopping openstack-cinder-volume: [ OK ] Starting openstack-cinder-volume: [ OK ]
- Create a volume either via Horizon or the CLI
root@TS-Training-OS-01 nova(keystone_admin)]# cinder create --volume_type nimble1 --display-name test_volume 50
+---------------------+--------------------------------------+ | Property | Value | +---------------------+--------------------------------------+ | attachments | [] | | availability_zone | nova | | bootable | false | | created_at | 2014-11-05T18:23:54.011013 | | display_description | None | | display_name | test_volume | | encrypted | False | | id | 6cce44ad-a71f-4973-b862-aefe9c5f0a79 | | metadata | {} | | size | 50 | | snapshot_id | None | | source_volid | None | | status | creating | | volume_type | nimble1 | +---------------------+--------------------------------------+ - Verify the volume has successfully been created
[root@TS-Training-OS-01 nova(keystone_admin)]# cinder list
- Verify the creation of the volume on your storage array. Go to Manage -> Volumes
