In our “The features and benefits of using LucidLink with the Enterprise File Fabric” last blog post we outlined the features and benefit of using LucidLink with the File Fabric. We have made available this integration to the Enterprise File Fabric as a technology preview. The following instructions outline the adding of a File Fabric ‘Filesystem’ Provider connected to one or more filespaces.
As a technology preview, some addition configuration is required vs the normal addition of a supported File Fabric provider.
- Log into the Enterprise File Fabric and become the root user.
- Install the LucidLink container:
yum makecache yum install sme-containers-lucidlink
- Change SElinux enforcement:
setenforce 0
- Disable SElinux by editing the file /etc/sysconfig/selinux and setting to disabled:
vi /etc/sysconfig/selinux
Change the line SELINUX=enabled
to
SELINUX=disabled - Navigate to the LucidLink folder. Create the configuration file from the template and edit the configuation values
(vi shown below, but feel free to use nano)cd /var/www/smestorage/containers/lucidlink cp config/startup.template config/startup.sh chmod +x config/startup.sh vi config/startup.sh
- An example of the startup file is below. Replace data.filespace with the name of your filespace. It should be in the format filespace_name.domain. This can be determined by logging into your LucidLink account. In the screenshot below the filespace is “test” and the domain is “filefabriclabs”. Therefore, “data.filespace” will be replaced with “test.filefabriclabs”. Next input the root password for the filespace. Edit the “xxxxxx” and replace it with the proper filespace password.Lastly, the Enterprise File Fabric will mount all filespaces into the directory /net/lucid. Each filespace should have a unique name. For our example it is best to keep the name consistent. Thus it is recommended that the directory “test” be used. Therefore the mount directory would be /net/lucid/test in our example.
-
Contents of startup.sh:
lucid daemon --fs data.filespace --password xxxxxx --mount-point /net/lucid/xxxx
Edited as per our example:
lucid daemon --fs test.filefabriclabs --password SMEisBest --mount-point /net/lucid/test
If your organization has multiple filespaces, they can all be mounted in the /net/lucid directory. Simply add an & to each of the filespace command lines except for the last. Example below:
lucid daemon --fs test.filefabriclabs --password SMEisBest --mount-point /net/lucid/test & lucid daemon --fs test2.filefabriclabs --password SMEisG8t --mount-point /net/lucid/test2
- Start the container:
docker-compose up -d
- Check the logs to ensure everything looks fine. Use Ctrl-C to exit the logs.
docker-compose logs -f
- If the logs indicate that there was a password error, simple stop the container with:
docker-compose down
Fix the startup file and repeat step 5.
- Finally ensure your data is accessible. List the directory mounted in the startup script:
ls -l /net/lucid/test
Enabling the Filesystem provider
The Enterprise File Fabric ships with the Filesystem (FS) provider off by default. If you have already enabled the Filesystem (FS) provider for NFS, Quantum StorNext, Spectrum Scale or other FS provider this step can be skipped.
Please follow the instruction on our doc site to enable the Filesystem provider for the appliance and for the organization which will use LucidLink.
https://docs.storagemadeeasy.com/cloudappliance/fsprovider
Adding LucidLink as a File Fabric provider
Once the LucidLink container is running and the FS provider is enabled as per the setup above LucidLink can be added as a provider.
As the org admin navigate to the Dashboard and add a provider. Select FS from the dropdown list.
Name your Cloud ”LucidLink (or whatever you want, it can be changed later)
For the technology preview the root user must be used. Input the EFF appliance root user password as the FS password.
Note: If your instance is running in AWS, Azure, Google Clouds with sudo access, you will need to become root via sudo and run passwd to add a password for the root user.
Lastly input the folder that was mapped in step 6. If you have multiple LucidLink filespaces then the folder /net/lucid can be mapped and each of the individual filespaces will be presented as sub-directories. Alternatively, you can add the FS provider twice, once for each LucidLink filespace.
by 
Douglas Soltesz
Latest posts by Douglas Soltesz (see all)
- LucidLink Technology Preview Setup Guide - September 6, 2021
- The features and benefits of using LucidLink with the Enterprise File Fabric - September 2, 2021
