Shared File Systems Option 1: No driver support for share servers management
For simplicity, this configuration references the same storage node
configuration for the Block Storage service. However, the LVM driver
requires a separate empty local block storage device to avoid conflict
with the Block Storage service. The instructions use /dev/sdc, but
you can substitute a different value for your particular node.
Prerequisites
Note
Perform these steps on the storage node.
Install the supporting utility packages:
Create the LVM physical volume /dev/sdc:
# pvcreate /dev/sdc
Physical volume "/dev/sdc" successfully created
Create the LVM volume group manila-volumes:
# vgcreate manila-volumes /dev/sdc
Volume group "manila-volumes" successfully created
The Shared File Systems service creates logical volumes in this volume
group.
Only instances can access Shared File Systems service volumes. However,
the underlying operating system manages the devices associated with
the volumes. By default, the LVM volume scanning tool scans the
/dev directory for block storage devices that
contain volumes. If projects use LVM on their volumes, the scanning
tool detects these volumes and attempts to cache them which can cause
a variety of problems with both the underlying operating system
and project volumes. You must reconfigure LVM to scan only the devices
that contain the cinder-volume and manila-volumes volume groups.
Edit the /etc/lvm/lvm.conf file and complete the following actions: