4.6. OpenStack Manila CSI Driver Operator

1. Log in to the OpenShift Container Platform web console.
2. Navigate to Operators OperatorHub.
3. Type Manila CSI Driver Operator into the filter box to locate the Operator.
4. Click Install.
5. On the Install Operator page, select openshift-manila-csi-driver-operator from the Installed Namespace drop-down menu.
6. Adjust the values for Update Channel and Approval Strategy to the values that you want. The only supported Installation Mode is All namespaces on the cluster.
7. Click Install.

1. Log in to the OpenShift Container Platform web console.
2. Navigate to Operators Installed Operators.
3. Locate the Manila CSI Driver Operator from the list and click on the Operator link.

4. Create the driver:

   1. From the Details tab, click Create Instance.
   2. Optional: Select YAML view to make modifications, such as adding notations, to the ManilaDriver object template.

   3. Click Create to finalize.

      重要

      Renaming the cluster and specifying a certain namespace are not supported functions.

1. Create an object YAML file, such as maniladriver.yaml, to define the ManilaDriver:

   Example maniladriver

     apiVersion: csi.openshift.io/v1alpha1
     kind: ManilaDriver
     metadata:
       name: cluster 1

   1

   Renaming the cluster and specifying a certain namespace are not supported functions.

2. Create the ManilaDriver CR object in your OpenShift Container Platform cluster by specifying the file you created in the previous step:

   $ oc create -f maniladriver.yaml

Verification

1. Verify that the ManilaDriver CR was created successfully by entering the following command:

   $ oc get all -n openshift-manila-csi-driver

   NAME                                                              READY   STATUS    RESTARTS   AGE
   pod/csi-nodeplugin-nfsplugin-lzvpm                                1/1     Running   0          18h
   pod/csi-nodeplugin-nfsplugin-slvg2                                1/1     Running   0          18h
   pod/csi-nodeplugin-nfsplugin-xmps9                                1/1     Running   0          18h
   pod/openstack-manila-csi-controllerplugin-7d4f5d985b-mw4x5        3/3     Running   0          17h
   pod/openstack-manila-csi-nodeplugin-6xchs                         2/2     Running   0          18h
   pod/openstack-manila-csi-nodeplugin-bkcmz                         2/2     Running   0          18h
   pod/openstack-manila-csi-nodeplugin-rlpps                         2/2     Running   0          18h
   
   NAME                                                              DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
   daemonset.apps/csi-nodeplugin-nfsplugin                           3       3       3     3          3                       18h
   daemonset.apps/openstack-manila-csi-nodeplugin                    3       3       3     3          3                       18h
   
   NAME                                                              READY UP-TO-DATE AVAILABLE AGE
   deployment.apps/openstack-manila-csi-controllerplugin             1/1   1          1         18h
   
   NAME                                                              DESIRED CURRENT READY AGE
   replicaset.apps/openstack-manila-csi-controllerplugin-7d4f5d985b  1       1       1     17h

2. Verify that the storage class was created successfully by entering the following command:

   $ oc get storageclasses | grep -E "NAME|csi-manila-"

   NAME              PROVISIONER               RECLAIMPOLICY   VOLUMEBINDINGMODE   ALLOWVOLUMEEXPANSION  AGE
   csi-manila-gold   manila.csi.openstack.org  Delete          Immediate           false                 18h

1. In the OpenShift Container Platform console, click Storage Persistent Volume Claims.
2. In the persistent volume claims overview, click Create Persistent Volume Claim.

3. Define the required options on the resulting page.

   1. Select the appropriate StorageClass.
   2. Enter a unique name for the storage claim.

   3. Select the access mode to specify read and write access for the PVC you are creating.

      重要
      • Use RWX if you want the persistent volume (PV) that fulfills this PVC to be mounted to multiple Pods on multiple nodes in the cluster.
      • Use RWO mode if you want to prevent additional Pods from being dynamically provisioned.
4. Define the size of the storage claim.
5. Click Create to create the persistent volume claim and generate a persistent volume.

1. Create and save a file with the PersistentVolumeClaim object described by the following YAML:

   pvc-manila.yaml

   apiVersion: v1
   kind: PersistentVolumeClaim
   metadata:
     name: pvc-manila
   spec:
     accessModes: 1
       - ReadWriteMany
     resources:
       requests:
     	storage: 10Gi
     storageClassName: csi-manila-gold 2

   1

   Use RWX if you want the persistent volume (PV) that fulfills this PVC to be mounted to multiple Pods on multiple nodes in the cluster. Use ReadWriteOnce (RWO) mode to prevent additional Pods from being dynamically provisioned.

   2

   The name of the storage class that provisions the storage back end. Manila StorageClasses are provisioned by the Operator and have the csi-manila- prefix.

2. Create the object you saved in the previous step by running the following command:

   $ oc create -f pvc-manila.yaml

   A new PVC is created.

3. To verify that the volume was created and is ready, run the following command:

   $ oc get pvc pvc-manila

   The pvc-manila shows that it is Bound.

1. Log in to the web console.
2. Navigate to Storage Persistent Volume Claims.
3. Select any PVCs that are in use by the Manila CSI Driver Operator and click Delete.
4. From the Operators Installed Operators page, scroll or type Manila CSI into the Filter by name field to find the Operator. Then, click on it.
5. On the right-hand side of the Installed Operators details page, select Uninstall Operator from the Actions drop-down menu.
6. When prompted by the Uninstall Operator window, click the Uninstall button to remove the Operator from the namespace. Any applications deployed by the Operator on the cluster will need to be cleaned up manually.