Deploying OpenShift Data Foundation on Satellite clusters with Azure worker nodes

Objectives

In this tutorial, you complete the following tasks to set up OpenShift Data Foundation.

A Satellite Location that uses Azure hosts.
A Satellite cluster that uses your Azure hosts as worker nodes.
A Satellite storage configuration that deploys the Azure Disk CSI driver to your cluster.
A Satellite storage configuration that deploys OpenShift Data Foundation to your cluster.

Audience

This tutorial is for location administrators who are using OpenShift Data Foundation and Satellite storage config for the first time.

Deploy the Azure location template

Verify you have the required permissions in your Azure account.
Follow the steps to deploy an Azure location by using the Schematics template. Make sure to deploy hosts across 3 zones and select a VM size that has at least 16CPUs and 64GB RAM.

Create a Satellite cluster that uses your Azure hosts

After setting up your location, you have unassigned hosts that can be used to create a cluster.

Follow the steps to deploy a cluster to your location. Make sure to select the Enable admin access for Satellite config option.
Wait until your cluster finishes deploying then deploy the Azure Disk CSI driver.

Deploy the Azure Disk CSI driver

Follow the steps to create an assign an Azure Disk storage configuration to your cluster.
Wait until the configuration is successfully assigned, then list the storage classes in your cluster.
```
oc get sc
```
Make sure the Azure Disk storage classes are deployed, then deploy ODF.

Deploy OpenShift Data Foundation

Follow the steps to create a Satellite storage configuration that uses the OpenShift Data Foundation for remote storage template. When you deploy ODF for remote storage you must provide a storage driver and a storage class that are used for provisioning app storage. In this example, you use the Azure Disk CSI driver and the sat-azure-block-gold-metro storage class that you deployed to your cluster in the previous step.

From the Satellite console click Locations, then click the location where you want to deploy OpenShift Data Foundation.
Click Storage > Create storage configuration.
On the Basics tab, enter a name for your configuration and select the OpenShift Data Foundation for remote storage, select the version that matches your cluster version, and click Next.
On the Parameters tab, enter sat-azure-block-gold-metro as the OSD pod storage class, and leave the remaining fields as their default values.
On the Secrets tab, enter your IAM API Key and click Next.
On the Storage Classes tab, review the storage classes that are deployed to your cluster. These storage classes are available for your apps.
On the Assign to service tab, select your cluster and click Complete.

Verify your deployment

Access your Satellite cluster.

Verify that the storage configuration resources are deployed. Run the following commands or review the openshift-storage namespace in the Red Hat OpenShift console.

Get the storagecluster that you deployed and verify that the phase is Ready.

oc get ocscluster -n openshift-storage

Example output

NAME                 AGE   PHASE   EXTERNAL   CREATED AT             VERSION
ocs-storagecluster   72m   Ready              2021-02-10T06:00:20Z   4.6.0

Get a list of pods in the openshift-storage namespace and verify that the status is Running.

oc get pods -n openshift-storage

Example output

NAME                                                              READY   STATUS      RESTARTS   AGE
csi-cephfsplugin-9g2d5                                            3/3     Running     0          8m11s
csi-cephfsplugin-g42wv                                            3/3     Running     0          8m11s
csi-cephfsplugin-provisioner-7b89766c86-l68sr                     5/5     Running     0          8m10s
csi-cephfsplugin-provisioner-7b89766c86-nkmkf                     5/5     Running     0          8m10s
csi-cephfsplugin-rlhzv                                            3/3     Running     0          8m11s
csi-rbdplugin-8dmxc                                               3/3     Running     0          8m12s
csi-rbdplugin-f8c4c                                               3/3     Running     0          8m12s
csi-rbdplugin-nkzcd                                               3/3     Running     0          8m12s
csi-rbdplugin-provisioner-75596f49bd-7mk5g                        5/5     Running     0          8m12s
csi-rbdplugin-provisioner-75596f49bd-r2p6g                        5/5     Running     0          8m12s
noobaa-core-0                                                     1/1     Running     0          4m37s
noobaa-db-0                                                       1/1     Running     0          4m37s
noobaa-endpoint-7d959fd6fb-dr5x4                                  1/1     Running     0          2m27s
noobaa-operator-6cbf8c484c-fpwtt                                  1/1     Running     0          9m41s
ocs-operator-9d6457dff-c4xhh                                      1/1     Running     0          9m42s
rook-ceph-crashcollector-169.48.170.83-89f6d7dfb-gsglz            1/1     Running     0          5m38s
rook-ceph-crashcollector-169.48.170.88-6f58d6489-b9j49            1/1     Running     0          5m29s
rook-ceph-crashcollector-169.48.170.90-866b9d444d-zk6ft           1/1     Running     0          5m15s
rook-ceph-drain-canary-169.48.170.83-6b885b94db-wvptz             1/1     Running     0          4m41s
rook-ceph-drain-canary-169.48.170.88-769f8b6b7-mtm47              1/1     Running     0          4m39s
rook-ceph-drain-canary-169.48.170.90-84845c98d4-pxpqs             1/1     Running     0          4m40s
rook-ceph-mds-ocs-storagecluster-cephfilesystem-a-6dfbb4fcnqv9g   1/1     Running     0          4m16s
rook-ceph-mds-ocs-storagecluster-cephfilesystem-b-cbc56b8btjhrt   1/1     Running     0          4m15s
rook-ceph-mgr-a-55cc8d96cc-vm5dr                                  1/1     Running     0          4m55s
rook-ceph-mon-a-5dcc4d9446-4ff5x                                  1/1     Running     0          5m38s
rook-ceph-mon-b-64dc44f954-w24gs                                  1/1     Running     0          5m30s
rook-ceph-mon-c-86d4fb86-s8gdz                                    1/1     Running     0          5m15s
rook-ceph-operator-69c46db9d4-tqdpt                               1/1     Running     0          9m42s
rook-ceph-osd-0-6c6cc87d58-79m5z                                  1/1     Running     0          4m42s
rook-ceph-osd-1-f4cc9c864-fmwgd                                   1/1     Running     0          4m41s
rook-ceph-osd-2-dd4968b75-lzc6x                                   1/1     Running     0          4m40s
rook-ceph-osd-prepare-ocs-deviceset-0-data-0-29jgc-kzpgr          0/1     Completed   0          4m51s
rook-ceph-osd-prepare-ocs-deviceset-1-data-0-ckvv2-4jdx5          0/1     Completed   0          4m50s
rook-ceph-osd-prepare-ocs-deviceset-2-data-0-szmjd-49dd4          0/1     Completed   0          4m50s
rook-ceph-rgw-ocs-storagecluster-cephobjectstore-a-7f7f6df9rv6h   1/1     Running     0          3m44s
rook-ceph-rgw-ocs-storagecluster-cephobjectstore-b-554fd9dz6dm8   1/1     Running     0          3m41s

Next Steps

To deploy an example application, see Deploying an app that uses OpenShift Data Foundation.