To access a volume using the Gluster native client (FUSE):

1. On the host where you intend to mount the Gluster volume, enable access to the Gluster Storage for Oracle Linux packages. For information on enabling access, see Section 2.3, “Enabling Access to the Gluster Storage for Oracle Linux Packages”.

2. Install the Gluster native client packages:

   # yum install glusterfs glusterfs-fuse

3. Create the directory where you intend to mount the volume. For example:

   # mkdir /gluster-storage

4. If you have configured TLS for a volume, you may need to perform additional steps before a client system is able to mount the Gluster volume. See Section 3.2, “Setting up Transport Layer Security (TLS)” for more information. The following steps are required to complete client configuration for TLS:

   To set up TLS with the Gluster native client (FUSE):

   1. Set up a certificate and private key on the client system. You can either use a CA signed certificate or create a self-signed certificate, as follows:

      # openssl req -newkey rsa:2048 -nodes -keyout /etc/ssl/glusterfs.key \
         -x509 -days 365 -out /etc/ssl/glusterfs.pem

   2. Append the client certificate to the /etc/ssl/glusterfs.ca file on each node in the trusted server pool. Equally, ensure that the client has a copy of the /etc/ssl/glusterfs.ca file that includes either the CA certificate that signed each node's certificate, or that contains all of the self-signed certificates for each node. Since Gluster performs mutual authentication, it is essential that both the client and the server node are able to validate each other's certificates.

   3. If you enabled encryption on management traffic, you must enable this facility on the client system to allow it to perform the initial mount. To do this, Gluster looks for a file at /var/lib/glusterfs/secure-access. This directory may not exist on a client system, so you might need to create it before touching the file:

      # mkdir -p /var/lib/glusterfs
      # touch /var/lib/glusterfs/secure-access

   4. If the Gluster volume is already set up and running before you added the client certificate to /etc/ssl/glusterfs.ca, you must stop the volume, restart the Gluster service and start up the volume again for the new certificate to be registered:

      # gluster volume stop myvolume
      # systemctl restart glusterd
      # gluster volume start myvolume 

5. Mount the volume on the directory using the glusterfs mount type and by specifying a node within the pool along with the volume name. For example:

   # mount -t glusterfs node1:myvolume /gluster-storage

   If you have set up the volume to enable mounting a subdirectory, you can add the subdirectory name to the path on the Gluster file system:

   # mount -t glusterfs node1:myvolume/subdirectory /gluster-storage

6. Check the permissions on the new mount to make sure the appropriate users can read and write to the storage. For example:

   # chmod 777 /gluster-storage

7. To make the mount permanent, edit your /etc/fstab file to include the mount. For example:

   node1:/myvolume /gluster-storage glusterfs defaults,_netdev 0 0

   If you are mounting a subdirectory on the volume, add the subdirectory name to the path on the Gluster file system. For example:

   node1:/myvolume/subdirectory /gluster-storage glusterfs defaults,_netdev 0 0