openstack-manuals/doc/install-guide/source/manila-share-install-dhss-false-option1.rst

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.

1. Install the supporting utility packages:

   obs

   • Install LVM and NFS server packages:

     # zypper install lvm2 nfs-kernel-server

   • (Optional) If you intend to use non-raw image types such as QCOW2 and VMDK, install the QEMU package:

     # zypper install qemu

   rdo

   • Install LVM and NFS server packages:

     # yum install lvm2 nfs-utils nfs4-acl-tools portmap

   • Start the LVM metadata service and configure it to start when the system boots:

     # systemctl enable lvm2-lvmetad.service
     # systemctl start lvm2-lvmetad.service

   ubuntu

   • Install LVM and NFS server packages:

     # apt-get install lvm2 nfs-kernel-server

2. Create the LVM physical volume /dev/sdc:

   # pvcreate /dev/sdc
   Physical volume "/dev/sdc" successfully created

3. 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.

4. 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:

   • In the devices section, add a filter that accepts the /dev/sdb and /dev/sdc devices and rejects all other devices:

     devices {
     ...
     filter = [ "a/sdb/", "a/sdc", "r/.*/"]

     Warning

     If your storage nodes use LVM on the operating system disk, you must also add the associated device to the filter. For example, if the /dev/sda device contains the operating system:

     filter = [ "a/sda/", "a/sdb/", "a/sdc", "r/.*/"]

     Similarly, if your compute nodes use LVM on the operating system disk, you must also modify the filter in the /etc/lvm/lvm.conf file on those nodes to include only the operating system disk. For example, if the /dev/sda device contains the operating system:

     filter = [ "a/sda/", "r/.*/"]

Configure components

1. Edit the /etc/manila/manila.conf file and complete the following actions:

   • In the [DEFAULT] section, enable the LVM driver and the NFS/CIFS protocols:

     [DEFAULT]
     ...
     enabled_share_backends = lvm
     enabled_share_protocols = NFS,CIFS

     Note

     Back end names are arbitrary. As an example, this guide uses the name of the driver.

   • In the [lvm] section, configure the LVM driver:

     [lvm]
     share_backend_name = LVM
     share_driver = manila.share.drivers.lvm.LVMShareDriver
     driver_handles_share_servers = False
     lvm_share_volume_group = manila-volumes
     lvm_share_export_ip = MANAGEMENT_INTERFACE_IP_ADDRESS

     Replace MANAGEMENT_INTERFACE_IP_ADDRESS with the IP address of the management network interface on your storage node, typically 10.0.0.41 for the first node in the example architecture <overview-example-architectures>.

Return to Finalize installation <manila-share-finalize-install>.