Description

• Create and delete support for block Metro volume. This feature is only implemented at the driver level like PowerMax Metro, without the involvement of replication module.
• Two backend volumes get created for single PV upon replication request specified in Storage class. If the ReclaimPolicy is 'Retain', both backend volumes along with PV are retained. If it is 'Delete', all are deleted.
• Updates to PV's volumeHandle to contain both backend volumes ID will be in next PR.

GitHub Issues

List the GitHub issues impacted by this PR:

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 (controller pkg 42.0% to 42.3%. Luke's PR will include changes to report better code coverage number)
• 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
• Backward compatibility is not broken

How Has This Been Tested?

• Tested that Metro PV is created and then deleted successfully. Remote backed volume is also created and deleted on the remote array as subsequent calls are made on source PV. (Logs are added to the ticket 23538)
• Tested that configure metro call is idempotent, also tested the failure scenarios as added in the code.
• Added new unit tests.
• Verified that non-metro PV creation and deletion continues to work. Updated tests/simple/simple.yaml to reflect CSM doc.