Home > Workload Solutions > Container Platforms > Red Hat OpenShift Container Platform > Archive > Implementation Guide—Red Hat OpenShift Container Platform 4.10 on AMD-powered Dell Infrastructure > Provisioning PowerMax storage
The Dell PowerMax storage system delivers high levels of performance and efficiency with an integrated machine learning (ML) engine. For more information, see Dell PowerMax NVMe Storage.
Ensure that:
To provision Dell PowerMax storage, create the namespace and secret by referring to this sample file:
[core@csah-pri ~]$ oc create -f powermax.secrets.yaml
Note: Specify the secret name as powermax-creds and ensure that the username and password are in base64 format, as shown in the sample file.
To configure the CSI driver to use PowerMax over iSCSI:
[core@csah-pri powermax]$ oc create -f <YAML file>
[core@csah-pri powermax]$ oc get pods -n powermax
NAME READY STATUS RESTARTS AGE
powermax-controller-6cd9c84ff-jrslv 5/5 Running 0 109s
powermax-controller-6cd9c84ff-xl7dh 5/5 Running 0 109s
powermax-node-8kj4v 2/2 Running 0 109s
powermax-node-fvb6d 2/2 Running 0 109s
powermax-node-j2lb2 2/2 Running 0 109s
powermax-node-kwkfs 2/2 Running 0 109s
powermax-node-zck9f 2/2 Running 0 109s
[core@csah-pri powermax]$ oc create -f <YAML file>
[core@csah-pri powermax]$ oc get sc
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
powermaxsc-iscsi csi-powermax.dellemc.com Delete WaitForFirstConsumer true 10s
To create dynamic iSCSI volumes:
[core@csah-pri powermax] $ oc create -f <YAML file>
[core@csah-pri powermax]$ oc get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
powermax-iscsi-pvc Bound pmax-719f7c4e67 2098560Ki RWO powermaxsc-iscsi 47s
[core@csah-pri powermax]$ oc rsh powermax-iscsi-pod
sh-4.4# df -h
Filesystem Size Used Avail Use% Mounted on
overlay 1.5T 64G 1.4T 5% /
tmpfs 64M 0 64M 0% /dev
tmpfs 252G 0 252G 0% /sys/fs/cgroup
shm 64M 0 64M 0% /dev/shm
tmpfs 252G 89M 252G 1% /etc/hostname
/dev/mapper/360000970000297901797533030303442 2.0G 33M 2.0G 2% /mnt
/dev/nvme0n1p4 1.5T 64G 1.4T 5% /tmp
tmpfs 503G 20K 503G 1% /run/secrets/kubernetes.io/serviceaccount
tmpfs 252G 0 252G 0% /proc/acpi
tmpfs 252G 0 252G 0% /proc/scsi
tmpfs 252G 0 252G 0% /sys/firmware
To configure the CSI driver to use PowerMax over FC:
[core@csah-pri powermax]$ oc create -f <secret YAML file>
[core@csah-pri powermax]$ oc get pods -n powermax
NAME READY STATUS RESTARTS AGE
powermax-controller-655f9f859b-kfhwl 5/5 Running 0 4m41s
powermax-controller-655f9f859b-kq5xg 5/5 Running 0 4m41s
powermax-node-2ktq8 2/2 Running 0 4m41s
powermax-node-64bms 2/2 Running 0 4m41s
powermax-node-grr28 2/2 Running 0 4m41s
[core@csah-pri powermax]$ oc create -f <YAML file>
[core@csah-pri powermax]$ oc get sc
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
powermaxscfc csi-powermax.dellemc.com Delete Immediate true 3d14h
To create dynamic FC volumes:
[core@csah-pri powermax] $ oc create -f <YAML file>
[core@csah-pri powermax]$ oc get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
powermax-fc-pvc Bound pmax-029d7338ee 2098560Ki RWO powermaxscfc 9s
[core@csah-pri powermax]$ oc rsh powermax-fc-pod
sh-4.4# df -h
Filesystem Size Used Avail Use% Mounted on
overlay 1.5T 66G 1.4T 5% /
tmpfs 64M 0 64M 0% /dev
tmpfs 252G 0 252G 0% /sys/fs/cgroup
shm 64M 0 64M 0% /dev/shm
tmpfs 252G 90M 252G 1% /etc/hostname
/dev/mapper/360000970000297901797533030303442 10G 33M 10G 1% /mnt
/dev/nvme0n1p4 1.5T 66G 1.4T 5% /tmp
tmpfs 503G 20K 503G 1% /run/secrets/kubernetes.io/serviceaccount
tmpfs 252G 0 252G 0% /proc/acpi
tmpfs 252G 0 252G 0% /proc/scsi
tmpfs 252G 0 252G 0% /sys/firmware
PowerMax CSI drivers support snapshots of volumes. Snapshots that you create can be used to create a volume and restore the data.
[core@csah-pri ~]$ oc create -f <yaml file>
[core@csah-pri ~]$ oc get volumesnapshotclass
NAME DRIVER DELETIONPOLICY AGE
powermax-snap-class csi-powermax.dellemc.com Delete 41h
[core@csah-pri ~]$ oc create -f <yaml file>
[core@csah-pri ~]$ oc get volumesnapshot
NAME READYTOUSE SOURCEPVC SOURCESNAPSHOTCONTENT RESTORESIZE SNAPSHOTCLASS SNAPSHOTCONTENT CREATIONTIME AGE
powermax-fc-snapshot true dynamic-fc-powermax-pvc 0 powermax-snap-class snapcontent-7f5ed227-0f2a-4ad1-b99a-f6d5150580ea 2m20s 2m24s
[core@csah-pri ~]$ oc get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
dynamic-fc-powermax-pvc Bound pmax-e0f8b64a9d 5243520Ki RWO powermaxscfc 9m7s
powermax-restore Bound pmax-37815e55f2 5243520Ki RWO powermaxscfc 14s
[core@csah-pri ~]$ oc rsh restore-pod
sh-4.4# df -h
Filesystem Size Used Avail Use% Mounted on
overlay 1.5T 78G 1.4T 6% /
tmpfs 64M 0 64M 0% /dev
tmpfs 252G 0 252G 0% /sys/fs/cgroup
shm 64M 0 64M 0% /dev/shm
tmpfs 252G 92M 252G 1% /etc/hostname
/dev/mapper/360000970000297901797533030303443 5.0G 33M 5.0G 1% /home
/dev/nvme0n1p4 1.5T 78G 1.4T 6% /etc/hosts
tmpfs 503G 20K 503G 1% /run/secrets/kubernetes.io/serviceaccount
tmpfs 252G 0 252G 0% /proc/acpi
tmpfs 252G 0 252G 0% /proc/scsi
tmpfs 252G 0 252G 0% /sys/firmware
sh-4.4#
sh-4.4# cd /home/
sh-4.4# ls
keys snapshot
sh-4.4# cd snapshot/
sh-4.4# ls
powermaxbackup
sh-4.4#
Note: Use this sample file to create iSCSI snapshots. Ensure that the values referenced match the configuration for the environment.