Dell ObjectScale Application 1.3.x Installation Guide for Red Hat OpenShift

Deploy CSI bare-metal driver and ObjectScale

1. Set these additional environment variables:

   export REGISTRY=<PRIVATE-REGISTRY>:<PRIVATE-REGISTRY_PORT>

   export CSI_VERSION=1.3.0-648.59a295a

   export CSI_OPERATOR_VERSION=1.3.0-121.2e006fb

   export CHARTS_DIR=<CHARTS_DIRECTORY>

   NOTE:<CHARTS_DIRECTORY> is the directory that you created and where you downloaded the ObjectScale charts .tgz files.
2. Extract the CSI helm charts .tgz file.

   tar zxf dellemc-csi-helm-charts-1.3.0-121.2e006fb.tgz

3. Install the Secondary Scheduler Operator.

   helm install secondary-scheduler-operator $CHARTS_DIR/dellemc-csi-helm-charts/secondaryscheduleroperator-$CSI_OPERATOR_VERSION.tgz -n $SSO_NS --set global.registry=$REGISTRY --set csv.version=secondaryscheduleroperator.v1.1.2 --set image.tag=$CSI_OPERATOR_VERSION

   Wait for the Secondary Scheduler Operator to start.

4. Verify that the Secondary Scheduler Operator pods are in Running status.

   kubectl get pod -n $SSO_NS

5. Install CSI Bare-Metal Operator.

   helm install csi-baremetal-operator $CHARTS_DIR/dellemc-csi-helm-charts/csi-baremetal-operator-$CSI_OPERATOR_VERSION.tgz --set image.tag=$CSI_OPERATOR_VERSION --set global.registry=$REGISTRY  --namespace $CSI_NS

   Wait for CSI Bare-Metal Operator to start.

6. Use helm to install the CSI Bare-Metal deployment:

   helm install csi-baremetal $CHARTS_DIR/dellemc-csi-helm-charts/csi-baremetal-deployment-$CSI_OPERATOR_VERSION.tgz --set image.tag=$CSI_VERSION --set global.registry=$REGISTRY --set scheduler.patcher.enable=true --set platform=openshift --set driver.drivemgr.type=halmgr --namespace $CSI_NS

   Wait for approximately five minutes for CSI Bare-Metal Deployment to start.

7. After completing the installation process:
   1. Verify that the new CSI storage classes have been created:

      kubectl get storageclasses -n $CSI_NS

      NAME                        PROVISIONER    RECLAIMPOLICY  VOLUMEBINDINGMODE    ALLOWVOLUMEEXPANSION  AGE
      csi-baremetal-sc (default)  csi-baremetal  Delete         WaitForFirstConsumer false                 70m
      csi-baremetal-sc-hdd        csi-baremetal  Delete         WaitForFirstConsumer false                 70m
      csi-baremetal-sc-hddlvg     csi-baremetal  Delete         WaitForFirstConsumer true                  70m
      csi-baremetal-sc-nvme       csi-baremetal  Delete         WaitForFirstConsumer false                 70m
      csi-baremetal-sc-ssd        csi-baremetal  Delete         WaitForFirstConsumer false                 70m
      csi-baremetal-sc-ssdlvg     csi-baremetal  Delete         WaitForFirstConsumer true                  70m
      csi-baremetal-sc-syslvg     csi-baremetal  Delete         WaitForFirstConsumer true                  70m

   2. Wait for the new CSI Pods to be Running status and the count of pods in the Ready column is matched (for example, 3/3), before continuing:

      kubectl -n $CSI_NS get pods |grep csi-baremetal

      csi-baremetal-controller-5cc46bcc74-np6dd        4/4     Running   0          6m17s
      csi-baremetal-node-279hd                         4/4     Running   0          6m17s
      csi-baremetal-node-2ktc7                         4/4     Running   0          6m17s
      csi-baremetal-node-4zrd9                         4/4     Running   0          6m17s
      csi-baremetal-node-56bpx                         4/4     Running   0          6m17s
      csi-baremetal-node-7z9xp                         4/4     Running   0          6m17s
      csi-baremetal-node-controller-5796d96fcb-55g4s   1/1     Running   0          6m18s
      csi-baremetal-node-s66sc                         4/4     Running   0          6m17s
      csi-baremetal-node-sk95x                         4/4     Running   0          6m17s
      csi-baremetal-operator-5ff49885bd-8zqxq          1/1     Running   0          6m42s
      csi-baremetal-se-9gzs2                           1/1     Running   0          6m17s
      csi-baremetal-se-btpgr                           1/1     Running   0          6m17s
      csi-baremetal-se-xg8g2                           1/1     Running   0          6m17s
      

8. Extract the ObjectScale helm charts .tgz file.

   tar zxf objectscale-helm-charts-1.3.0.tgz

9. Display the Dell End User License Agreement (EULA):

   helm show readme $CHARTS_DIR/objectscale-portal-1.3.0.tgz | more

10. Set an environment variable for the EULA Revision Date value shown in the last line of the readme file.
    You must use this value in the helm install command to deploy ObjectScale. The date is in the format: ddMMMYYYY.

    export EULA_DATE=<ddMMMYYYY>

11. Install Postgres.

    helm install postgres $CHARTS_DIR/postgres-ha-{keyref: objectscale_version}.tgz --set global.storageClass=csi-baremetal-sc-ssdlvg --set global.registry=$REGISTRY --namespace=$OBJECTSCALE_NS

12. Install ObjectScale.
    This step installs the ObjectScale UI, ObjectScale Manager, DECKS, and KAHM on the OpenShift cluster.
    NOTE:You can modify these commands to tailor the storage resources that are used for the storageClassName and secondaryStorageClass by using your preferred csi-baremetal Storage Class.

    storageClassName

    The storage class used for the ObjectScale components that require high performance storage (csi-baremetal-sc-ssdlvg is used in the command provided below).

    secondaryStorageClass

    The storage class used for all other ObjectScale components that do not require high performance storage (csi-baremetal-sc-ssdlvg is used in the command provided below).

    helm install objs $CHARTS_DIR/objectscale-portal-{keyref: objectscale_version}.tgz --set global.watchAllNamespaces=true 
    --set global.registry=$REGISTRY --set global.storageClassName=csi-baremetal-sc-ssdlvg --set global.secondaryStorageClass=csi-baremetal-sc-ssdlvg 
    --set global.platform=OpenShift --set global.schedulerName=csi-baremetal-scheduler --namespace $OBJECTSCALE_NS --set accept_eula=$EULA_DATE --set global.deploymentmodel=application:openshift

13. Get a list of all the Kubernetes applications to ensure that all the ObjectScale components are present.

    kubectl -n $OBJECTSCALE_NS get app

    NAME                          TYPE                        VERSION      
    decks                         decks                       3.0.2    
    dellemc-objectscale-license   dellemc-license             3.0.2    
    kahm                          kahm                        2.3.0       
    objectscale-manager           objectscale-manager         1.3.0                  
    objectscale-monitoring                                                              
    supportassist-objectscale     supportassist-objectscale   3.0.2

14. After a few minutes, verify that the ObjectScale components are in Deployed status.

    helm list --all-namespaces

    NAME                            NAMESPACE                               REVISION        UPDATED                                 STATUS          CHART                                           APP VERSION
    csi-baremetal                   csi-ns                                  1               2023-09-30 07:27:41.343043396 +0000 UTC deployed        csi-baremetal-deployment-1.3.0-121.2e006fb      1.3.0
    csi-baremetal-operator          csi-ns                                  1               2023-09-30 07:27:17.85109974 +0000 UTC  deployed        csi-baremetal-operator-1.3.0-121.2e006fb        1.3.0
    decks                           objectscale                             1               2023-09-30 10:08:50.813194581 +0000 UTC deployed        decks-3.0.2                                     3.0.2
    dellemc-objectscale-license     objectscale                             1               2023-09-30 10:12:49.410034042 +0000 UTC deployed        dellemc-license-3.0.2                           3.0.2
    jake-str1                       objstr-ns                               1               2023-09-30 10:19:17.618885416 +0000 UTC deployed        ecs-cluster-1.3.0                               1.3.0
    kahm                            objectscale                             1               2023-09-30 10:08:46.107519914 +0000 UTC deployed        kahm-2.3.0                                      2.3.0
    objectscale                     objectscale                             1               2023-09-30 09:57:58.85858592 +0000 UTC  deployed        objectscale-portal-1.3.0                        1.3.0
    objectscale-manager             objectscale                             1               2023-09-30 09:58:09.947126415 +0000 UTC deployed        objectscale-manager-1.3.0                       1.3.0
    postgres                        objectscale                             1               2023-09-30 08:58:19.52372846 +0000 UTC  deployed        postgres-ha-1.3.0                               1.3.0
    secondary-scheduler-operator    openshift-secondary-scheduler-operator  1               2023-09-30 07:25:55.222338019 +0000 UTC deployed        secondaryscheduleroperator-1.3.0-121.2e006fb    1.1.0
    snmp-notifier                   objectscale                             1               2023-09-30 10:14:05.448733759 +0000 UTC deployed        snmp-notifier-2.3.0                             2.3.0
    supportassist-objectscale       objectscale                             1               2023-09-30 10:15:13.361602021 +0000 UTC deployed        supportassist-3.0.2                             3.0.2

15. Now that the KAHM app has been deployed, install the csi-baremetal-alerts chart into the default namespace:

    helm install csi-baremetal-alerts --namespace $CSI_NS  $CHARTS_DIR/csi-baremetal-alerts-1.3.0.tgz