As of Dec 23, 2021, ocs-kustomization project is deprecated, please consider use odf-kustomization instead.

This kustomization makes use of ocs-operator to deploy OpenShift Container Storage.

Red Hat OpenShift Container Storage product documentation can be found here.

This kustomization was tested on:

• VMware vSphere
• Amazon AWS

• OpenShift cluster with a minimum of 3 OCS worker nodes.

• Each worker node needs to have a minimum of 16 CPUs and 64 GB memory available.

• Worker nodes must be labeled with a label cluster.ocs.openshift.io/openshift-storage=

  • To label a node, issue the command:

    $ oc label nodes <node> cluster.ocs.openshift.io/openshift-storage=
    

  • To verify labeling, you can list the OCS worker nodes with:

    $ oc get node --selector cluster.ocs.openshift.io/openshift-storage=
    

    You should see at least three nodes listed in the output.

• If you plan to use the OCS worker nodes exlusively for OCS services, you can avoid double charges of both OpenShift and OpenShift Container Storage for OCS worker nodes, see also here. Refer to the following documentation on how to create infra nodes in your OpenShift cluster:

  • Creating an Infra Node in OpenShift v4
  • Openshift 4 create infra machines
  • Custom pools

  The creation of infra nodes has also been implemented by the openshift-post-install project.

• It is recommended that you apply a taint to the nodes to mark them for exclusive OpenShift Container Storage use:

  $ oc adm taint nodes <node names> node.ocs.openshift.io/storage=true:NoSchedule
  

• The default storage class is set to the appropriate storage class for your infrastructure provider.

  • On AWS, the default storage class must be gp2.
  • On VMware vSphere, the default storage class must be thin.

  For example, on AWS you can verify the default storage class setting with:

  $ oc get storageclass
  NAME            PROVISIONER             AGE
  gp2 (default)   kubernetes.io/aws-ebs   27m
  

The commands in this section must be issued by an OpenShift user with a cluster-admin role.

Review the ocs-operator/base kustomization and modify it to suit your needs. Notably, set the version of the ocs-operator you want to deploy in ocs-operator/base/openshift-storage-subscription.yaml.

To deploy an ocs-operator, issue the command:

$ oc apply --kustomize ocs-operator/base

Wait until the ocs-operator csvs are fully deployed. You can watch their deployment status with:

$ oc get csv --namespace openshift-storage
NAME                  DISPLAY                       VERSION   REPLACES              PHASE
awss3operator.1.0.1   AWS S3 Operator               1.0.1     awss3operator.1.0.0   Succeeded
ocs-operator.v4.2.1   OpenShift Container Storage   4.2.1                           Succeeded

All csvs must reach the phase Succeeded. Note that you must wait until the csvs are fully deployed before creating an OCS instance!

Review the ocs-instance/base kustomization and modify it to suit your needs. Make sure that the storageClassName set in the ocs-storagecluster-storagecluster.yaml manifests is appropriate storage class for your infrastructure provider (use gp2 for AWS, thin for vSphere).

To deploy an OCS instance on AWS, issue the command:

$ oc apply --kustomize ocs-instance/overlays/aws

To deploy an OCS instance on vSphere, issue the command:

$ oc apply --kustomize ocs-instance/overlays/vsphere

Watch the status conditions of the storagecluster resource while the OCS instance is being deployed:

$ oc get storagecluster --namespace openshift-storage --output yaml

When the OCS instance deployment is complete, the status of the Available condition changes to True like this:

$ oc get storagecluster \
  --namespace openshift-storage \
  --output jsonpath='{.items[0].status.conditions[?(@.type=="Available")].status}' 
True

Congrats on completing the installation of OpenShift Container Storage!

Mark the current StorageClass as non-default:

$ oc patch storageclass gp2 \
    -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class": "false"}}}'

Configure ceph rbd as your default StorageClass:

$ oc patch storageclass ocs-storagecluster-ceph-rbd \
    -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class": "true"}}}'

Optionally, you can deploy a Ceph toolbox:

$ oc patch \
    --namespace openshift-storage \
    --type json \
    --patch  '[{ "op": "replace", "path": "/spec/enableCephTools", "value": true }]' \
    OCSInitialization ocsinit

Obtain the rook-ceph-tools pod:

$ TOOLS_POD=$(oc get pods --namespace openshift-storage --selector app=rook-ceph-tools --output name)

Run Ceph commands:

$ oc rsh --namespace openshift-storage $TOOLS_POD ceph status
$ oc rsh --namespace openshift-storage $TOOLS_POD ceph osd status
$ oc rsh --namespace openshift-storage $TOOLS_POD ceph osd tree
$ oc rsh --namespace openshift-storage $TOOLS_POD ceph df
$ oc rsh --namespace openshift-storage $TOOLS_POD rados df

Enable dashboard (remember to set the TOOLS_POD variable as shown above before running this command):

$ oc rsh --namespace openshift-storage $TOOLS_POD ceph mgr module enable dashboard

Create user admin with the role administrator. Replace with your own admin password:

$ echo <password> | oc rsh --namespace openshift-storage $TOOLS_POD ceph dashboard ac-user-create admin administrator -i -

Forward local port 8443 to the dashboard endpoint:

$ oc port-forward deploy/rook-ceph-mgr-a 8443

Browse to https://localhost:8443 to access the dashboard.

You can create test volumes by issuing the commands:

$ oc apply -f docs/samples/test-rwo-pvc.yaml

$ oc apply -f docs/samples/test-rwx-pvc.yaml

$ oc apply -f docs/samples/test-bucket-obc.yaml

To further exercise the OCS cluster, you can follow the OCS-training hands-on workshop.

Collect debugging data about the currently running Openshift cluster:

$ oc adm must-gather

Collect debugging information specific to OpenShift Container Storage:

$ oc adm must-gather --image quay.io/rhceph-dev/ocs-must-gather:latest-4.7