4.2. Configuring Openstack Block Storage to Use Red Hat Storage Volume

Procedure 4.1. Configure Openstack Block Storage to Use Red Hat Storage Volume

1. Update the cinder.conf File

   Set the glusterFS default configuration parameters in the cinder.conf file as follows:

   # openstack-config --set /etc/cinder/cinder.conf DEFAULT volume_driver cinder.volume.drivers.glusterfs.GlusterfsDriver
   # openstack-config --set /etc/cinder/cinder.conf DEFAULT glusterfs_shares_config /etc/cinder/shares.conf
   # openstack-config --set /etc/cinder/cinder.conf DEFAULT glusterfs_mount_point_base /var/lib/cinder/volumes

2. Create the shares.conf File

   Create the /etc/cinder/shares.conf file. Add a list of Red Hat Storage Volumes from different trusted storage pools with the client mount point for each. Each storage volume and mount point must be on a new line, as follows:

   STORAGEHOST:VOLUME
   STORAGEHOST1:NEXTVOLUME
   STORAGEHOSTHOST2:ANOTHERVOLUME

   An example of this configuration is as follows:

   10.1.1.11:/cinder-vol
   10.1.2.12:/nextcinder-vol
   10.1.3.13:/anothercinder-vol

   When listing the storage volume and mount point, Red Hat recommends that you use the backup-volfile-servers=volfile_server2:volfile_server3:...:volfile_serverN option to list the backup volfile servers to mount the client. If this option is specified while mounting the FUSE client, and if the first volfile server fails, the servers specified in the backup-volfile-servers option are used as volfile servers to mount the client until the mount operation is successful. Add this option to the storage volume and mount point list in /etc/cinder/shares.conf file as shown below:

   10.1.1.11:/cinder-vol -o backup-volfile-servers=volfile_server2:volfile_server3

3. Restart Services

   Restart the cinder services as follows:

   # service openstack-cinder-api restart
   # service openstack-cinder-volume restart
   # service openstack-cinder-scheduler restart