Cinder supports a variety of backends in the backend, and it really fits the needs of the user. Recently, our company's own internal OpenStack platform with SATA, SSD glusterfs volume, studied the configuration of the next cinder multi backends. Actually, the main thing is cinder.conf.
The cinder.conf configuration file is as follows:
[default]enabled_backends = glusterfs1,glusterfs2 # enable two glusterfs volumedefault_volume_type = GLUSTERFS1 # Default SATA volume [GLUSTERFS1] Glusterfs_shares_config=/etc/cinder/glusterfs_shares1volume_driver= Cinder.volume.drivers.glusterfs.glusterfsdrivervolume_backend_name=openstack # used when setting cinder type key [GLUSTERFS2 ]glusterfs_shares_config=/etc/cinder/glusterfs_shares2volume_driver= Cinder.volume.drivers.glusterfs.glusterfsdrivervolume_backend_name=ssd
[[Email protected] cinder (keystone_admin)]# Cat glusterfs_shares1gluster002.sh.99cloud.net:/openstack # SATA Volume path [[Email protected] cinder (keystone_admin)]# Cat GLUSTERFS_SHARES2GLUSTER002.SH.99CLOUD.NET:/SSD # SSD Volume path
Cinder type-create SATA # Cinder SATA type cinder Type-key SATA set Volume_backend_name=openstack #为sata类型设置key value, with the above C Inder.conf inside the configuration file corresponding to the Cinder Type-create SSD # cinder SSD type cinder Type-key SSD set VOLUME_BACKEND_NAME=SSD # for SSD type set key VA Lue
Reference: Redhat OpenStack Certified Training materials
This article is from the "The-way-to-cloud" blog, make sure to keep this source http://iceyao.blog.51cto.com/9426658/1601613
Cinder-multi Glusterfs Volume backends