Chapter 2. Deploy OpenShift Data Foundation using local storage devices

Procedure

1. Log in to the OpenShift Web Console.
2. Click Operators OperatorHub.
3. Scroll or type OpenShift Data Foundation into the Filter by keyword box to find the OpenShift Data Foundation Operator.
4. Click Install.

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

   1. Update Channel as stable-4.18.
   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 is created during the operator installation.

   4. Select Approval Strategy as Automatic or Manual.

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

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

   5. Ensure that the Enable option is selected for the Console plugin.
   6. Click Install.

Procedure

1. Log in to the OpenShift Web Console.
2. Click Operators OperatorHub.
3. Type local storage in the Filter by keyword​ box to find the Local Storage Operator from the list of operators, and click on it.

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

   1. Update channel as stable.
   2. Installation mode as A specific namespace on the cluster.
   3. Installed Namespace as Operator recommended namespace openshift-local-storage.
   4. Update approval as Automatic.
5. Click Install.

Procedure

1. List and verify the name of the worker nodes with the OpenShift Data Foundation label.

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

   Copy to Clipboard Toggle word wrap

   Example output:

   NAME          STATUS   ROLES    AGE     VERSION
   bmworker01    Ready    worker   6h45m   v1.16.2
   bmworker02    Ready    worker   6h45m   v1.16.2
   bmworker03    Ready    worker   6h45m   v1.16.2

   Copy to Clipboard Toggle word wrap

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

   $ oc debug node/<node name>

   Copy to Clipboard Toggle word wrap

   Example output:

   $ oc debug node/bmworker01
   Starting pod/bmworker01-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
   loop0                          7:0    0   500G  0 loop
   sda                            8:0    0   120G  0 disk
   |-sda1                         8:1    0   384M  0 part /boot
   `-sda4                         8:4    0 119.6G  0 part
   `-coreos-luks-root-nocrypt   253:0    0 119.6G  0 dm   /sysroot
   sdb                            8:16   0   500G  0 disk

   Copy to Clipboard Toggle word wrap

   In this example, for bmworker01, the available local device is sdb.

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

   sh-4.4#ls -l /dev/disk/by-id/  | grep sdb
   lrwxrwxrwx. 1 root root  9 Feb  3 16:49 scsi-360050763808104bc2800000000000259 -> ../../sdb
   lrwxrwxrwx. 1 root root  9 Feb  3 16:49 scsi-SIBM_2145_00e020412f0aXX00 -> ../../sdb
   lrwxrwxrwx. 1 root root  9 Feb  3 16:49 scsi-0x60050763808104bc2800000000000259 -> ../../sdb

   Copy to Clipboard Toggle word wrap

   In the above example, the ID for the local device sdb

   scsi-0x60050763808104bc2800000000000259

   Copy to Clipboard Toggle word wrap
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 Data Foundation. See this Knowledge Base article for more details.

Procedure

1. To add a disk to a KVM guest, run the following command:

   virsh attach-disk <guest-name> --source <disk-path> --target vdc --persistent --serial <unique-serial-value>

   Copy to Clipboard Toggle word wrap

   where:

   --persistent

   Specifies that the configuration survives guest restarts.

   --serial

   Specifies that device identifiers remain constistent across restarts.

   <unique-serial-value>

   Specifies a unique serial value that is assigned to the disk.

2. When solid state drives (SSD) are passed through to a KVM guest, the guest might incorrectly set the rotational flag to 1, for hard disk drive (HDD). You must manually set the rotational flag to 0 so ODF can detect and use the device. To verify the current rotational flag, run the following command:

   lsblk -o NAME,ROTA

   Copy to Clipboard Toggle word wrap

   Example output:

   sh-5.1# lsblk -o NAME,ROTA
   NAME   ROTA
   vda       1
   |-vda3    1
   `-vda4    1
   vdb       1
   sh-5.1#

   Copy to Clipboard Toggle word wrap

   To manually set the rotational flag, follow the steps described in How to override device rotational flags in ODF/FDF environments (IBM documentation).

Procedure

1. To enable the DASD device, run the following command:

   sudo chzdev -e <device_bus_id> 

   1

   Copy to Clipboard Toggle word wrap

   1

   For <device_bus_id>, specify the ID of the DASD device bus-ID. For example, 0.0.b100.

   To verify the status of the DASD device you can use the the lsdasd and lsblk commands.

2. To low-level format the device and specify the disk name, run the following command:

   sudo dasdfmt /dev/<device_name> -b 4096 -p --mode=full 

   1

   Copy to Clipboard Toggle word wrap

   1

   For <device_name>, specify the disk name. For example, dasdb.

   Important

   The use of DASD quick-formatting Extent Space Efficient (ESE) DASD is not supported on OpenShift Data Foundation. If you are using ESE DASDs, make sure to disable quick-formatting with the --mode=full parameter.

3. To auto-create one partition using the whole disk, run the following command:

   sudo fdasd -a /dev/<device_name> 

   1

   Copy to Clipboard Toggle word wrap

   1

   For <device_name>, enter the disk name you have specified in the previous step. For example, dasdb.

Procedure

1. In the OpenShift Web Console, click Operators Installed Operators to view all the installed operators.

   Ensure that the Project selected is openshift-storage.

2. Click on the OpenShift Data Foundation operator and then click Create StorageSystem.

3. In the Backing storage page, perform the following:

   1. Select the Create a new StorageClass using the local storage devices for Backing storage type option.
   2. Select Full Deployment for the Deployment type option.

   3. Click Next.

      Important

      You are prompted to install the Local Storage Operator if it is not already installed. Click Install, and follow the procedure as described in Installing Local Storage Operator.

4. In the Create local volume set page, provide the following information:

   1. Enter a name for the LocalVolumeSet and the StorageClass.

      By default, the local volume set name appears for the storage class name. You can change the name.

   2. Choose one of the following:

      • Disks on all nodes

        Uses the available disks that match the selected filters on all the nodes.

      • Disks on selected nodes

        Uses the available disks that match the selected filters only on the selected nodes.

        Important

        • The flexible scaling feature is enabled only when the storage cluster that you created with three or more nodes are spread across fewer than the minimum requirement of three availability zones.

          For information about flexible scaling, see knowledgebase article on Scaling OpenShift Data Foundation cluster using YAML when flexible scaling is enabled.

        • Flexible scaling features get enabled at the time of deployment and can not be enabled or disabled later on.

        • If the nodes selected do not match the OpenShift Data Foundation cluster requirement of an aggregated 30 CPUs and 72 GiB of RAM, a minimal cluster is deployed.

          For minimum starting node requirements, see the Resource requirements section in the Planning guide.

   3. From the available list of Disk Type, select SSD/NVME.

   4. Expand the Advanced section and set the following options:

      Volume Mode	Block is selected by default.
      Device Type	Select one or more device type from the dropdown list. By default, Disk and Part options are included in the Device Type field. Note For a multi-path device, select the Mpath option from the drop-down exclusively. For a DASD-based cluster, ensure that only the Part option is included in the Device Type and remove the Disk option.
      Disk Size	Set a minimum size of 100GB for the device and maximum available size of the device that needs to be included.
      Maximum Disks Limit	This indicates the maximum number of PVs that can be created on a node. If this field is left empty, then PVs are created for all the available disks on the matching nodes.

   5. Click Next.

      A pop-up to confirm the creation of LocalVolumeSet is displayed.

   6. Click Yes to continue.

5. In the Capacity and nodes page, configure the following:

   1. Available raw capacity is populated with the capacity value based on all the attached disks associated with the storage class. This takes some time to show up. The Selected nodes list shows the nodes based on the storage class.
   2. You can check the box to select Taint nodes.
   3. Click Next.

6. Optional: In the Security and network page, configure the following based on your requirement:

   1. To enable encryption, select Enable data encryption for block and file storage.

   2. Choose one or both of the following Encryption level:

      • Cluster-wide encryption

        Encrypts the entire cluster (block and file).

      • StorageClass encryption

        Creates encrypted persistent volume (block only) using encryption enabled storage class.

   3. Select Connect to an external key management service checkbox. This is optional for cluster-wide encryption.

      1. Key Management Service Provider is set to Vault by default.
      2. Enter Vault Service Name, host Address of Vault server ('https://<hostname or ip>''), Port number and Token.

      3. Expand Advanced Settings to enter additional settings and certificate details based on your Vault configuration:

         1. Enter the Key Value secret path in Backend Path that is dedicated and unique to OpenShift Data Foundation.
         2. Optional: Enter TLS Server Name and Vault Enterprise Namespace.
         3. Upload the respective PEM encoded certificate file to provide CA Certificate, Client Certificate and Client Private Key.
         4. Click Save.
   4. Select Default (SDN) as Multus is not yet supported on OpenShift Data Foundation on IBM Z.
   5. Click Next.

7. In the Review and create page::

   1. Review the configuration details. To modify any configuration settings, click Back to go back to the previous configuration page.
   2. Click Create StorageSystem.