Setting up shared storage for a remote physical location

The following storage is supported for the shared storage:

• NFS

You must configure the remote physical location to support dynamic provisioning.

The steps in this procedure use the Kubernetes NFS-Client Provisioner (from the Kubernetes SIGs organization) to set up dynamic provisioning with NFS storage.

Your NFS server must be accessible from your Red Hat® OpenShift® Container Platform cluster and the remote physical location.

If you pull images from a private container registry, mirror the images for the Kubernetes NFS-Client Provisioner to your private container registry. Complete the appropriate task for your environment:

• If your client workstation can connect to the internet and to the private container registry, you can mirror the images directly to your private container registry.
• If your client workstation cannot connect to the internet and to the private container registry, you must mirror images to an intermediary registry before you can mirror the images to your private container registry.

To configure dynamic storage:

1. Log the cpd-cli in to the Red Hat OpenShift Container Platform cluster:

   ${REMOTE_CPDM_OC_LOGIN}

   Remember: REMOTE_CPDM_OC_LOGIN is an alias for the cpd-cli manage login-to-ocp command when you are connecting to a remote cluster.
2. If you mirrored the images to a private container registry, update the global image pull secret so that the cluster can access the Kubernetes NFS-Client Provisioner images.

   The global image pull secret must contain the credentials of an account that can pull images from the private container registry:

   cpd-cli manage add-cred-to-global-pull-secret \
   --registry=${PRIVATE_REGISTRY_LOCATION} \
   --registry_pull_user=${PRIVATE_REGISTRY_PULL_USER} \
   --registry_pull_password=${PRIVATE_REGISTRY_PULL_PASSWORD}

3. Set the following environment variables:
   1. Set NFS_SERVER_LOCATION environment variable to the IP address or fully qualified domain name (FQDN) of the NFS server:

      export NFS_SERVER_LOCATION=<server-address>

   2. Set NFS_PATH environment variable to the exported path where you want the provisioner to create sub-directories. (The default path is /.)

      export NFS_PATH=<path>

   3. Set PROJECT_NFS_PROVISIONER environment variable to the project (namespace) where you want to deploy the Kubernetes NFS-Client Provisioner provisioner. The recommended project is nfs-provisioner; however, you can specify any project.
      Important: You must specify an existing project (namespace).

      export PROJECT_NFS_PROVISIONER=<project-name>

   4. Set the NFS_IMAGE environment variable to the location and name of the nfs-subdir-external-provisioner image to use to set up dynamic provisioning:

      Public registry

      export NFS_IMAGE=registry.k8s.io/sig-storage/nfs-subdir-external-provisioner:v4.0.2

      Private container registry

      export NFS_IMAGE=${PRIVATE_REGISTRY_LOCATION}/nfs-subdir-external-provisioner:v4.0.2

4. Run the following command to create the NFS storage provisioner and storage class:

   cpd-cli manage setup-nfs-provisioner \
   --nfs_server=${NFS_SERVER_LOCATION} \
   --nfs_path=${NFS_PATH} \
   --nfs_path_pattern=\${.PVC.annotations.nfs.io/storage-path} \
   --nfs_provisioner_name=shared.fuseim.pri/ifs \
   --nfs_provisioner_image=${NFS_IMAGE} \
   --nfs_provisioner_ns=${PROJECT_NFS_PROVISIONER} \
   --nfs_storageclass_name=managed-nfs-shared-storage

Now that you've set up shared storage for the remote physical location, you're ready to complete Installing Analytics Engine powered by Apache Spark on a remote physical location.