There are three types of backend configured here:
(1) Local creation of logical volume LVM backend
(2) Glusterfs back end
(3) using the third-party driven Ip-san in OpenStack, the model is the IBM Storwize series
The cinder.conf configuration is as follows:
[default]enabled_backends = Lvm,glusterfs,ibm[lvm]volume_driver = Cinder.volume.drivers.lvm.LVMVolumeDrivervolume_ Backend_name=lvmvolume_group = Cinder-volumesiscsi_protocol = Iscsiiscsi_helper = lioadm[glusterfs]volume_driver= cinder.volume.drivers.glusterfs.glusterfsdrivervolume_backend_name=glusterfsglusterfs_shares_config=/etc/ Cinder/shares.confglusterfs_mount_point_base=/var/lib/cinder/glusterfs[ibm]volume_driver = Cinder.volume.drivers.ibm.storwize_svc. Storwizesvcdriversan_ip = 172.28.21.10san_login = Superusersan_password = 123456storwize_svc_volpool_name = Vtt1storwize_svc_connection_protocol = ISCSIVOLUME_BACKEND_NAME=IBM
Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.
Openstack:cinder-volume configuration Lvm/glusterfs/ip-san and many other backend