Storage Capacity Tracking for CSI-Powerflex

[ashleyvjoy]

Description

This PR adds addresses changes in csm-operator to support Storage Capacity Tracking feature for PowerFlex driver

GitHub Issues

List the GitHub issues impacted by this PR:

| GitHub Issue # |
| (dell/csm#876) |

Checklist:

• I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
• I have verified that new and existing unit tests pass locally with my changes
• I have not allowed coverage numbers to degenerate
• I have maintained at least 90% code coverage
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• I have maintained backward compatibility

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

• Deployed driver using csm-operator with sct flag set to true and described csi-driver. StorageCapacity is enabled and csistoraagecapacitiesobjects are created. Successfully executed Cert-CSI test suites and StorageCapacity Functional test suites. Test Suites passed 100%
• Deployed driver using csm-operator with sct flag set to false and described csi-driver. StorageCapacity is not enabled

INFO 1. ScalingSuite {replicas: 2, volumes: 5, volumeSize: 8Gi}
INFO 2. CloneVolumeSuite {pods: 2, volumes: 1, volumeSize: 8Gi}
INFO 3. VolumeIoSuite {volumes: 2, volumeSize: 8Gi chains: 2-2}
INFO 4. SnapSuite {snapshots: 3, volumeSize; 8Gi}
INFO 5. ReplicationSuite {pods: 2, volumes: 5, volumeSize: 8Gi}
Does it look OK? (Y)es/(n)o
-> y
INFO Avg time of a run:   60.37s
INFO Avg time of a del:   13.81s
INFO Avg time of all:     79.24s
INFO During this run 100.0% of suites succeeded
------------------------------------------------------------
./cert-csi functional-test capacity-tracking --sc vxflexos-xfs --drns vxflexos --pi 5m
INFO Starting cert-csi; ver. 0.8.1
INFO Using EVENT observer type
INFO Using default config
INFO Successfully loaded config. Host: https://
INFO Created new KubeClient
INFO Found 1 topology segment(s) in csinode
INFO Creating capacity-tracking-4367b929 storage class
INFO Waiting for CSIStorageCapacity to be CREATED for capacity-tracking-4367b929 storage class in vxflexos namespace
INFO All CSIStorageCapacity are created in 2.005263936s
INFO Deleting capacity-tracking-4367b929 storage class,
INFO Waiting for CSIStorageCapacity to be DELETED for capacity-tracking-4367b929 storage class in vxflexos namespace
INFO All CSIStorageCapacity are deleted in 2.005498431s
INFO Updating CSIStorageCapacity for vxflexos-xfs storage class, setting capacity to 0
INFO Creating capacity-tracking-pod-d0a8eb93 pod using vxflexos-xfs storage class
INFO capacity-tracking-pod-d0a8eb93 pod is PENDING
INFO Waiting for provisioner to POLL GetCapacity for vxflexos-xfs storage class in 5m0s
INFO Provisioner POLLED GetCapacity for vxflexos-xfs storage class
INFO Waiting for pod capacity-tracking-pod-d0a8eb93 to be READY
INFO capacity-tracking-pod-d0a8eb93 pod is RUNNING
INFO SUCCESS: CapacityTrackingSuite in 1m10.092508801s
INFO Trying to connect to cluster...
INFO Created new KubeClient
INFO During this run 100.0% of suites succeeded

[khareRajshree]

Please update the e2e files and execute the e2e tests with the latest changes done for SCT.

[ashleyvjoy]

Please update the e2e files and execute the e2e tests with the latest changes done for SCT.

Executed the e2e test and logs are attached in Jira.