Cinder's default backend storage provider is LVM. When cinder LVM backend driver is configured, a Cinder-volume service consumes a preconfigured volume group of the host Cinder-volume runs on. Cinder-volume manages the logical volumes of the configured volume group and uses an iSCSI target helper to provide a direct connection path to the volume.
In this recipe, we will configure LVM Cinder backend storage provider. A cinder-volume service will utilize a volume group of the host cinder-volume service runs on. Before getting started with configuring the Cinder backend driver, we need to make sure that the database, message broker, and Keystone are set for Cinder.
Additionally, make sure that the Nova-compute hosts are set to consume Cinder API.
[root@controller ~]# grep cinder.API /etc/nova/nova.conf volume_api_class=nova.volume.cinder.API
To create an LVM volume group to be consumed by the cinder-volume service...