This article applies to OpenStack versions prior to Ocata.
For OpenStack Ocata or later, see OpenStack InfiniBox Volume Driver.
- Install OpenStack.
- Install the InfiniBox volume driver for OpenStack Cinder.
- Nova, Cinder and ESX hosts must be prepared to work with InfiniBox.
Configuring the volume driver using
infini-openstack command-line tool
infini-openstack is a command line tool for adding the InfiniBox system and volume backend types to Cinder's configuration file.
infini-openstackre-writes Cinder's configuration file, it deletes comments inside it. If you want to keep the comments, you add the requires changes manually, as explained here.
For cinder to provision volume within InfiniBox, one has to:
- Configure one or more InfiniBox volume-backend types (Each volume-backend type is associated with an <Infinibox system>/<pool> pair).
- Enable those volumes-backend types (i.e configure Cinder to load the driver for each pool).
For example, in order to configure a volume-backend type, one has to run:
where the flag "--commit" allows the script to override Cinder's configuration file. The list of the volume-backend types can be viewed using:
where each row of the output corresponds to a volume-backend type, and contains the following information:
Using the pool id obtained from the above output, one can then enable a specific volume-backend:
In addition, if iSCSI is enabled in the host, but fibrechannel should be used for this volume backend, please run:
To get more details about infini-openstack command line interface, run:
For the changes to take effect, the Cinder volume service should be restarted using:
Configuring the volume driver manually
This step is not necessary if you are already using
Cinder's configuration file is located at "/etc/cinder/cinder.conf". For each volume-backend type, one has to append a section to Cinder's configuration file:
To enable one or more volume backend type, you should edit the following line in the default section of Cinder's configuration file:
where each element is a section name corresponding to a volume-backend type. For the changes to take effect, the Cinder volume service should be restarted using:
Once that completes, you need to create the volume type in Cinder database by running: