Chapter 3. Deploy using local storage devices

1. Install the Red Hat OpenShift Container Storage Operator.
2. Install Local Storage Operator.
3. Find the available storage devices.
4. Create OpenShift Container Storage cluster service on Amazon EC2 storage optimized - i3en.2xlarge instance type.

Procedure

1. Navigate in the web console to the click Operators → OperatorHub.
2. Scroll or type a keyword into the Filter by keyword box to search for OpenShift Container Storage Operator.
3. Click Install on the OpenShift Container Storage operator page.

4. On the Install Operator page, the following required options are selected by default:

   1. Update Channel as stable-4.7.
   2. Installation Mode as A specific namespace on the cluster.
   3. Installed Namespace as Operator recommended namespace openshift-storage. If Namespace openshift-storage does not exist, it will be created during the operator installation.
   4. Select Approval Strategy as Automatic or Manual.

   5. Click Install.

      If you selected Automatic updates, then the Operator Lifecycle Manager (OLM) automatically upgrades the running instance of your Operator without any intervention.

      If you selected Manual updates, then the OLM creates an update request. As a cluster administrator, you must then manually approve that update request to have the Operator updated to the new version.

Procedure

1. Log in to the OpenShift Web Console.
2. Click Operators → OperatorHub.
3. Type local storage in the Filter by keyword…​ box to search for Local Storage operator from the list of operators and click on it.
4. Click Install.

5. Set the following options on the Install Operator page:

   1. Update Channel as stable-4.7
   2. Installation Mode as A specific namespace on the cluster.
   3. Installed Namespace as Operator recommended namespace openshift-local-storage.
   4. Approval Strategy as Automatic
6. Click Install.
7. Verify that the Local Storage Operator shows the Status as Succeeded.

Procedure

1. List and verify the name of the nodes with the OpenShift Container Storage label.

   $ oc get nodes -l cluster.ocs.openshift.io/openshift-storage=

   Example output:

   NAME                                        STATUS   ROLES    AGE     VERSION
   ip-10-0-135-71.us-east-2.compute.internal    Ready    worker   6h45m   v1.16.2
   ip-10-0-145-125.us-east-2.compute.internal   Ready    worker   6h45m   v1.16.2
   ip-10-0-160-91.us-east-2.compute.internal    Ready    worker   6h45m   v1.16.2

2. Log in to each node that is used for OpenShift Container Storage resources and find the unique by-id device name for each available raw block device.

   $ oc debug node/<node name>

   Example output:

   $ oc debug node/ip-10-0-135-71.us-east-2.compute.internal
   Starting pod/ip-10-0-135-71us-east-2computeinternal-debug ...
   To use host binaries, run `chroot /host`
   Pod IP: 10.0.135.71
   If you don't see a command prompt, try pressing enter.
   sh-4.2# chroot /host
   sh-4.4# lsblk
   NAME                         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
   xvda                         202:0    0   120G  0 disk
   |-xvda1                      202:1    0   384M  0 part /boot
   |-xvda2                      202:2    0   127M  0 part /boot/efi
   |-xvda3                      202:3    0     1M  0 part
   `-xvda4                      202:4    0 119.5G  0 part
     `-coreos-luks-root-nocrypt 253:0    0 119.5G  0 dm   /sysroot
   nvme0n1                      259:0    0   2.3T  0 disk
   nvme1n1                      259:1    0   2.3T  0 disk

   In this example, for the selected node, the local devices available are nvme0n1 and nvme1n1.

3. Identify the unique ID for each of the devices selected in Step 2.

   sh-4.4#  ls -l /dev/disk/by-id/ | grep Storage
   lrwxrwxrwx. 1 root root 13 Mar 17 16:24 nvme-Amazon_EC2_NVMe_Instance_Storage_AWS10382E5D7441494EC -> ../../nvme0n1
   lrwxrwxrwx. 1 root root 13 Mar 17 16:24 nvme-Amazon_EC2_NVMe_Instance_Storage_AWS60382E5D7441494EC -> ../../nvme1n1

   In the example above, the IDs for the two local devices are

   • nvme0n1: nvme-Amazon_EC2_NVMe_Instance_Storage_AWS10382E5D7441494EC
   • nvme1n1: nvme-Amazon_EC2_NVMe_Instance_Storage_AWS60382E5D7441494EC
4. Repeat the above step to identify the device ID for all the other nodes that have the storage devices to be used by OpenShift Container Storage. See this Knowledge Base article for more details.

1. Create PVs by using the LocalVolume CR
2. Create a new StorageClass

Procedure

1. Create local persistent volumes (PVs) on the storage nodes using LocalVolume custom resource (CR).

   Example of LocalVolume CR local-storage-block.yaml using OpenShift Storage Container label as node selector and by-id device identifier:

   apiVersion: local.storage.openshift.io/v1
   kind: LocalVolume
   metadata:
     name: local-block
     namespace: openshift-local-storage
     labels:
       app: ocs-storagecluster
   spec:
     tolerations:
     - key: "node.ocs.openshift.io/storage"
       value: "true"
       effect: NoSchedule
     nodeSelector:
       nodeSelectorTerms:
         - matchExpressions:
             - key: cluster.ocs.openshift.io/openshift-storage
               operator: In
               values:
                 - ''
     storageClassDevices:
       - storageClassName: localblock
         volumeMode: Block
         devicePaths:
           - /dev/disk/by-id/nvme-Amazon_EC2_NVMe_Instance_Storage_AWS10382E5D7441494EC   # <-- modify this line
           - /dev/disk/by-id/nvme-Amazon_EC2_NVMe_Instance_Storage_AWS1F45C01D7E84FE3E9   # <-- modify this line
           - /dev/disk/by-id/nvme-Amazon_EC2_NVMe_Instance_Storage_AWS136BC945B4ECB9AE4   # <-- modify this line
           - /dev/disk/by-id/nvme-Amazon_EC2_NVMe_Instance_Storage_AWS10382E5D7441464EP   # <-- modify this line
           - /dev/disk/by-id/nvme-Amazon_EC2_NVMe_Instance_Storage_AWS1F45C01D7E84F43E7   # <-- modify this line
           - /dev/disk/by-id/nvme-Amazon_EC2_NVMe_Instance_Storage_AWS136BC945B4ECB9AE8   # <-- modify this line

   Each Amazon EC2 I3 instance has two disks and this example uses both disks on each node.

2. Create the LocalVolume CR.

   $ oc create -f local-storage-block.yaml

   Example output:

   localvolume.local.storage.openshift.io/local-block created

3. Check if the pods are created.

   $ oc -n openshift-local-storage get pods

4. Check if the PVs are created.

   You must see a new PV for each of the local storage devices on the three worker nodes. Refer to the example in the Finding available storage devices section that shows two available storage devices per worker node with a size 2.3 TiB for each node.

   $ oc get pv

   Example output:

   NAME               CAPACITY ACCESS MODES  RECLAIM POLICY STATUS       CLAIM     STORAGECLASS  REASON   AGE
   local-pv-1a46bc79  2328Gi   RWO           Delete         Available              localblock             14m
   local-pv-429d90ee  2328Gi   RWO           Delete         Available              localblock             14m
   local-pv-4d0a62e3  2328Gi   RWO           Delete         Available              localblock             14m
   local-pv-55c05d76  2328Gi   RWO           Delete         Available              localblock             14m
   local-pv-5c7b0990  2328Gi   RWO           Delete         Available              localblock             14m
   local-pv-a6b283b   2328Gi   RWO           Delete         Available              localblock             14m

5. Check for the new StorageClass that is now present when the LocalVolume CR is created. This StorageClass is used to provide the StorageCluster PVCs in the following steps.

   $ oc get sc | grep localblock

   Example output:

   NAME            PROVISIONER                    RECLAIMPOLICY
   VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION     AGE
   localblock      kubernetes.io/no-provisioner   Delete
   WaitForFirstConsumer  false                15m

6. Create the StorageCluster CR that uses the localblock StorageClass to consume the PVs created by the Local Storage Operator.

   Example of StorageCluster CR ocs-cluster-service.yaml using monDataDirHostPath and localblock StorageClass.

   apiVersion: ocs.openshift.io/v1
   kind: StorageCluster
   metadata:
     name: ocs-storagecluster
     namespace: openshift-storage
   spec:
     manageNodes: false
     resources:
       mds:
         limits:
           cpu: 3
           memory: 8Gi
         requests:
           cpu: 1
           memory: 8Gi
     monDataDirHostPath: /var/lib/rook
     storageDeviceSets:
       - count: 2
         dataPVCTemplate:
           spec:
             accessModes:
               - ReadWriteOnce
             resources:
               requests:
                 storage: 2328Gi
             storageClassName: localblock
             volumeMode: Block
         name: ocs-deviceset
         placement: {}
         portable: false
         replica: 3
         resources:
           limits:
             cpu: 2
             memory: 5Gi
           requests:
             cpu: 1
             memory: 5Gi

   Important

   To ensure that the OSDs have a guaranteed size across the nodes, the storage size for storageDeviceSets must be specified as less than or equal to the size of the PVs created on the nodes.

7. Create StorageCluster CR.

   $ oc create -f ocs-cluster-service.yaml

   Example output

   storagecluster.ocs.openshift.io/ocs-cluster-service created