Your Browser is Out of Date

ShareDemos uses technology that works best in other browsers.
For a full experience use one of the browsers below
Deployment Guide—Dell EMC Ready Stack for Red Hat OpenShift Container Platform 4.6
Provisioning Storage
Introduction Prerequisites Unity XT storage PowerMax storage PowerScale storage OpenShift Container storage

Unity XT storage

  • Dell EMC Unity is a midrange storage platform that is designed for performance and efficiency. For more information, see Dell EMC Unity.

    Ensure that:

    • Dell CSI Operator is installed. See Installing the CSI Operator.
    • The Dell EMC Unity storage system is configured properly.
    • Storage pools have been created along with FC ports, iSCSI interfaces are configured, and the NFS configured as necessary

    To provision Dell EMC Unity storage:

    1. Create the namespace:

    [core@csah ~]$ oc new-project unity

    1. Create an empty secret (see this sample file in GitHub),
    2. Apply the empty secret:

    [core@csah unity]$ oc create -f <secret YAML file>

    1. Create a JSON configuration file containing the IP address and Unity array ID. Enter the username and password that you used to log in to Unity through Unisphere. Ensure that the username and password are specified in base64 format (see this sample file in GitHub).
    2. Create a secret by using the JSON file:

    [core@csah unity]$ oc create secret generic unity-creds -n unity --from-file=config=secret.json

    Configure the Unity CSI driver

    Note: You can use the Unity CSI driver to create volumes using either the iSCSI, FC, or NFS protocols.

    Create the CSI Unity driver file by following the steps in this sample file in GitHub.

    Note: Obtain the arrayID, storagePool, and nasServer information from the UniSphere UI.

    1. Create the Unity setup using the driver file that you created in step 1:

    [core@csah unity]$ oc create -f <YAML file>

    1. Ensure that the Unity pods are running in the unity namespace:

    [core@csah unity]$ oc get pods -n unity -o wide

    Note: There are two Unity controller pods and one Unity node pod running for every compute node that is running. The Unity pod in each compute node automatically adds any FC or iSCSI Qualified Name into the Unisphere Unity.

    1. Verify that the storage classes for Unity are created. Because the CSI driver is the same for the iSCSI, FC, and NFS protocols, three storage classes are created:

       [core@csah unity]$ oc get sc

    NAME          PROVISIONER             RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION   AGE

    unity-fc      csi-unity.dellemc.com   Delete          Immediate           true                   2m30s

    unity-iscsi   csi-unity.dellemc.com   Delete          Immediate           true                   2m30s

    unity-nfs     csi-unity.dellemc.com   Delete          Immediate           true                   2m30s

    Configure iSCSI for Unity Create dynamic iSCSI volumes

    Note: For compute nodes running RHCOS, the /etc/iscsi/initiatorname.iscsi file is missing with OCP version 4.6.8 or earlier. For more information, see Red Hat Bug908847 - RHCOS 4.6 - Missing Initiatorname.

    Create a YAML file with which to create a PVC by following the steps in this sample file in GitHub.

    1. Create a PVC using the YAML file:

    [core@csah ~]$ oc create -f <YAML file>

    Note: Ensure that the storage class name designates an iSCSI configuration. This guide uses unity-iscsi as the iSCSI storage class name.

    1. Verify that the volume is created

    [core@csah ~]$ oc get pvc

    NAME                         STATUS   VOLUME            CAPACITY   ACCESS MODES   STORAGECLASS     AGE

    dynamic-iscsi-unity-pvc   Bound    csiunity-dd5f2628cb   7Gi        RWO            unity-iscsi    21m

    Attach a pod to the iSCSI volume

    Create a YAML file with which to create a pod, and mount a volume using the PVC you created in step 2 of Create dynamic iSCSI volumes. Follow the steps in this sample file in Git Hub.

    1. Create a pod:

    [core@csah unity] $ oc create -f <YAML file>

    1. Verify that the pod is created and the Unity volume is mounted:

    [core@csah unity]$ oc get pods dynamic-iscsi-unity-pod -o wide

    NAME                      READY   STATUS    RESTARTS   AGE   IP             NODE                    NOMINATED NODE   READINESS GATES

    dynamic-iscsi-unity-pod   1/1     Running   0          28s   10.131.0.168   compute-2.example.com   <none>           <none>

    [core@csah unity]$ oc exec -it dynamic-iscsi-unity-pod -- df -h /usr/share/nginx/html

    Filesystem          Size  Used Avail Use% Mounted on

    /dev/mapper/mpathc  6.9G   32M  6.5G   1% /usr/share/nginx/html

    Configure FC Unity

    Create dynamic FC volumes

    It is not necessary to create a volume manually when you use a dynamic volume. The PV is created automatically and is attached to the PVC through a YAML file.

    Create a YAML file to create the PVC by following the steps in this sample file in GitHub.

    1. Use the YAML file that you created in step 1 to create the dynamic PV:

    [core@csah unity] $ oc create -f <YAML file>

    Note: Ensure that the storage class name designates an FC configuration. This guide uses unity-fc as the FC storage class name.

    1. Verify that the volume is created:

    [core@csah unity]$ oc get pvc

    NAME                      STATUS   VOLUME                CAPACITY   ACCESS MODES   STORAGECLASS   AGE

    dynamic-fc-unity-pvc      Bound    csiunity-64e67b27c4   6Gi        RWO            unity-fc       24m

    Attach a pod to the FC volume

    Create a YAML file with which to create a pod, and mount a volume using the PVC you created in step 2 of Create dynamic FC volumes. Follow the steps in this sample file in GitHub.

    1. Create a pod:

    [core@csah unity] $ oc create -f <YAML file>

    1. Verify that the pod is created and the PowerMax volume is mounted:

    [core@csah unity]$ oc get pods dynamic-fc-unity-pod -o wide

    NAME                   READY   STATUS    RESTARTS   AGE     IP             NODE                    NOMINATED NODE   READINESS GATES

    dynamic-fc-unity-pod   1/1     Running   0          2m59s   10.131.0.167   compute-2.example.com   <none>           <none>

    [core@csah unity]$ oc exec -it dynamic-fc-unity-pod -- df -h /usr/share/nginx/html

    Filesystem          Size  Used Avail Use% Mounted on

    /dev/mapper/mpathb  5.9G   24M  5.6G   1% /usr/share/nginx/html

    NFS Unity setup

    Create dynamic NFS volumes

    Create a YAML file with which to create the PVC by following the steps in this sample file in GitHub.

    1. Use the YAML file that you created in step 1 to create the dynamic PV:

    [core@csah unity] $ oc create -f <YAML file>

    Note: Ensure that the storage class name designates an NFS configuration. This guide uses unity-nfs as the NFS storage class name.

    1. Verify that the volume is created:

    core@csah unity]$ oc get pvc

    NAME                      STATUS   VOLUME                CAPACITY   ACCESS MODES   STORAGECLASS   AGE

    dynamic-nfs-unity-pvc     Bound    csiunity-f81650fca8   4Gi        RWX            unity-nfs      20m

    Attach a pod to the NFS volume

    Create a YAML file with which to create a pod, and mount a volume using the PVC you created in step 2 of Create dynamic NFS volumes. For guidance, see this sample file in GitHub.

    1. Create a pod:

    [core@csah unity] $ oc create -f <YAML file>

    1. Verify that the pod is created and the PowerMax volume is mounted:

    [core@csah unity]$ oc get pods dynamic-nfs-unity-pod -o wide

    NAME                   READY   STATUS    RESTARTS   AGE     IP             NODE                    NOMINATED NODE   READINESS GATES

    dynamic-nfs-unity-pod   1/1     Running   0          2m59s   10.131.0.12    compute-2.example.com   <none>           <none>

    [core@csah unity]$ oc exec -it dynamic-nfs-unity-pod -- df -h /usr/share/nginx/html

    Filesystem                                 Size  Used Avail Use% Mounted on

    192.168.46.8:/csishare-csiunity-f81650fca8  5.5G  1.6G  4.0G  28% /usr/share/nginx/html

    Creating Unity snapshots

    Dell Unity CSI drivers support snapshots of volumes. Create snapshots as a means of backing up either the iSCSI, FC, or NFS volume that you created, and then use the snapshots to create a volume and attach it to the pod.

    Note: You can take Unity volume snapshots for all the volumes that are created using FC, iSCSI, or NFS protocols. The following example shows snapshots that were taken using Unity snapshot volume class unity-snap and the iSCSI volume.

    1. Verify that the volume snapshot class is created:

    [core@csah unity]$ oc get volumesnapshotclass

    NAME         DRIVER                  DELETIONPOLICY   AGE

    unity-snap   csi-unity.dellemc.com   Delete           2m53s

    1. Add content to the iSCSI pod that is mounted with the iSCSI volume that you created previously. Perform this step to validate successful volumes created using snapshots with the same content:

    [core@csah unity]$ oc exec -it dynamic-iscsi-unity-pod /bin/bash

    kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.

    root@dynamic-iscsi-unity-pod:/# touch /usr/share/nginx/html/sample

    root@dynamic-iscsi-unity-pod:/# echo 'powermax backup' > /usr/share/nginx/html/sample

    root@dynamic-iscsi-unity-pod:/# cat /usr/share/nginx/html/sample

    unity backup

    1. Create a snapshot (see this sample file in GitHub) using the YAML file:

    [core@csah unity]$ oc create -f <YAML file>

    1. Verify that the volume snapshots are created:

    [core@csah unity]$ oc get volumesnapshot

    NAME             READYTOUSE   SOURCEPVC                 SOURCESNAPSHOTCONTENT   RESTORESIZE   SNAPSHOTCLASS   SNAPSHOTCONTENT                                    CREATIONTIME   AGE

    unity-snapshot   true         dynamic-iscsi-unity-pvc                           7Gi           unity-snap      snapcontent-ccf83239-03bf-4207-80e9-41d02bd5e77d   104s           20s

    1. Create a volume using the snapshot (see this sample file in Git Hub), and then verify that the restored volume is created:

    [core@csah unity]$ oc create -f restore.yaml

    persistentvolumeclaim/unity-restore created

    [core@csah unity]$ oc get pvc unity-restore

    NAME            STATUS   VOLUME                CAPACITY   ACCESS MODES   STORAGECLASS   AGE

    unity-restore   Bound    csiunity-765d68a92b   7Gi        RWO            unity-iscsi    28s

    1. Create a pod and attach the volume you created in the preceding step. Verify that the pod is created, that the volume is attached, and that the content you added in step 2 exists (see this sample file in GitHub):

    [core@csah unity]$ oc get pods restore-pod

    NAME          READY   STATUS    RESTARTS   AGE

    restore-pod   1/1     Running   0          9m58s

    [core@csah unity]$ oc exec -it restore-pod -- cat /usr/share/nginx/html/sample

    unity backup

next

PowerMax storage