feature/CSTACKEX-46: Create, Delete iSCSI type Cloudstack volumes, Enter, Cancel Maintenance mode

[sandeeplocharla]

Description

This PR has the following changes:

1. Create iSCSI type cloudstack volume
2. Delete iSCSI type cloudstack volume
3. Enter and Cancel Maintenance when storagepool has CS volumes

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)
• Build/CI
• Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

• Major
• Minor

Bug Severity

• BLOCKER
• Critical
• Major
• Minor
• Trivial

Screenshots (if appropriate):

How Has This Been Tested?

1. https://netapp.zoom.us/rec/share/r0rh_HhXD_lZNuppLeGGMk4Y4jg8-p9DXwIB_GD2e-uEslEH5geYzchrYcBDY7PJ.WjzaTxXoGt0B8nqe?startTime=1768919430000
   Passcode: n=AE=.C9

• Create ISCSI type Primary storage pool
• Create Compute & Disk offering.
• Create an instance with compute & disk offering to create both ROOT & DATA disks via ontap plugin.
• Add additional CS Volume with ontap plugin and allocate it to the instance created.
• Disable, Re-Enable Storage Pool (with CS Volumes)
• Enter, Cancel Maintenance of Storage Pool (with CS Volumes)
• Delete Instance + Expunge Volumes
• Disable, Re-Enable Storage Pool (without CS Volumes)
• Enter, Cancel Maintenance of Storage Pool (without CS Volumes)
• Delete Storage Pool

2. https://netapp.zoom.us/rec/share/Ax74XcCVkQtXglaNwNb9rTcn_1k1TvxplvaLmXTdFxjz7DeQixmiqj-uwX0QXjz0.EwnlsurMGr3jLku3?startTime=1768920957000
   Passcode: $%j3+K4B

• Create an instance with compute & disk offering to create both ROOT & DATA disks via Default Primary & ontap plugins.
• Add additional CS Volume with ontap plugin and allocate it to the instance created.
• Disable, Re-Enable Storage Pool (with CS Volumes)
• Enter, Cancel Maintenance of Storage Pool (with CS Volumes)
• Delete Instance + Expunge Volumes
• Disable, Re-Enable Storage Pool (without CS Volumes)
• Enter, Cancel Maintenance of Storage Pool (without CS Volumes)
• Delete Storage Pool

Observations:

Though we have increased retries to wait for discovery of luns, the additional volume attachment still times out, so, it needs a manual retry.
When placed into Maintenance mode, Instance is getting Stopped in the first case while it remains in Running state in the second case. We currently don't have any code attributing to this behaviour in our plugin code. Need to understand why cloudstack is behaving this way.

I've also tested force delete of storage pool when CS volumes were present, but, haven't covered it in these recordings.