From 8d1f87fcbbc077b55d65e327e2b54f664786ce9f Mon Sep 17 00:00:00 2001 From: HarishH-DELL Date: Mon, 17 Apr 2023 13:43:29 +0530 Subject: [PATCH 1/2] Multi array support documentation improvements --- .../csidriver/installation/helm/isilon.md | 46 +++++++++++++++++++ 1 file changed, 46 insertions(+) diff --git a/content/docs/csidriver/installation/helm/isilon.md b/content/docs/csidriver/installation/helm/isilon.md index b7888484fa..bec653784c 100644 --- a/content/docs/csidriver/installation/helm/isilon.md +++ b/content/docs/csidriver/installation/helm/isilon.md @@ -296,6 +296,52 @@ Deleting a storage class has no impact on a running Pod with mounted PVCs. You c >Note: If you continue to use the old storage classes, you may not be able to take advantage of any new storage class parameter supported by the driver. +**Steps to create secondary storage class:** + +There are samples storage class yaml files available under `samples/storageclass`. These can be copied and modified as needed. + +1. Copy the `storageclass.yaml` to `storageclass_2.yaml` ( This is just an example, you can rename to file you require. ) +2. Edit the `storageclass_2.yaml` yaml file and update following parameters: +- Update the `name` parameter to you require + ````yaml + metadata: + name: isilon-new + ```` +- Cluster name of 2nd array looks like this in the secret file.( Under `/samples/secret/secret.yaml`) + ````yaml + - clusterName: "cluster2" + username: "user name" + password: "Password" + endpoint: "10.X.X.X" + endpointPort: "8080 + +- Use same clusterName ↑ in the `storageclass_2.yaml` + ````yaml + # Optional: true + ClusterName: "cluster2" +- *Note*: These are two essential parameters that you need to change in the "storageclass_2.yaml" file and other parameters that you change as required. +3. Save the `storageclass_2.yaml` file +4. Create your 2nd storage class by using `kubectl`: + ````bash + kubectl create -f + ```` +5. Use newly created storage class `isilon-new` for volumes to spin up on `cluster2` + + PVC example + ````yaml + apiVersion: v1 + kind: PersistentVolumeClaim + metadata: + name: test-pvc + spec: + accessModes: + - ReadWriteOnce + resources: + requests: + storage: 5Gi + storageClassName: isilon-new + ```` + ## Volume Snapshot Class Starting CSI PowerScale v1.6, `dell-csi-helm-installer` will not create any Volume Snapshot Class during the driver installation. Sample volume snapshot class manifests are available at `samples/volumesnapshotclass/`. Use these sample manifests to create a volumesnapshotclass for creating volume snapshots; uncomment/ update the manifests as per the requirements. From b81dfabce7d031a0e730dac124a903182195918c Mon Sep 17 00:00:00 2001 From: HarishH-DELL Date: Tue, 18 Apr 2023 11:26:12 +0530 Subject: [PATCH 2/2] renamed sc name --- content/docs/csidriver/installation/helm/isilon.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/content/docs/csidriver/installation/helm/isilon.md b/content/docs/csidriver/installation/helm/isilon.md index bec653784c..438360ea1e 100644 --- a/content/docs/csidriver/installation/helm/isilon.md +++ b/content/docs/csidriver/installation/helm/isilon.md @@ -300,8 +300,8 @@ Deleting a storage class has no impact on a running Pod with mounted PVCs. You c There are samples storage class yaml files available under `samples/storageclass`. These can be copied and modified as needed. -1. Copy the `storageclass.yaml` to `storageclass_2.yaml` ( This is just an example, you can rename to file you require. ) -2. Edit the `storageclass_2.yaml` yaml file and update following parameters: +1. Copy the `storageclass.yaml` to `second_storageclass.yaml` ( This is just an example, you can rename to file you require. ) +2. Edit the `second_storageclass.yaml` yaml file and update following parameters: - Update the `name` parameter to you require ````yaml metadata: @@ -315,15 +315,15 @@ There are samples storage class yaml files available under `samples/storageclass endpoint: "10.X.X.X" endpointPort: "8080 -- Use same clusterName ↑ in the `storageclass_2.yaml` +- Use same clusterName ↑ in the `second_storageclass.yaml` ````yaml # Optional: true ClusterName: "cluster2" -- *Note*: These are two essential parameters that you need to change in the "storageclass_2.yaml" file and other parameters that you change as required. -3. Save the `storageclass_2.yaml` file +- *Note*: These are two essential parameters that you need to change in the "second_storageclass.yaml" file and other parameters that you change as required. +3. Save the `second_storageclass.yaml` file 4. Create your 2nd storage class by using `kubectl`: ````bash - kubectl create -f + kubectl create -f ```` 5. Use newly created storage class `isilon-new` for volumes to spin up on `cluster2`