Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature StorageCapacityTracking for Powermax #281

Merged
merged 1 commit into from
Jul 10, 2023
Merged

Conversation

tssushma
Copy link
Contributor

@tssushma tssushma commented Jun 26, 2023

Description

Support storagecapacitytracking feature for PowerMax.

Additional context
This feature helps the scheduler to schedule the pod on a node (satisfying the topology constraints) only if the requested capacity is available on the storage array.

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
image

  • Test A
  • Test B

@@ -53,6 +53,8 @@ const (
CSIPmaxVsphereHostname = "<X_CSI_VSPHERE_HOSTNAME>"
CSIPmaxVsphereHost = "<X_CSI_VCENTER_HOST>"
CSIPmaxChap = "<X_CSI_POWERMAX_ISCSI_ENABLE_CHAP>"
// CSIStorageCapacityEnabled - Storage capacity flag
CSIStorageCapacityEnabled = "false"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the use of this param?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This parameter is a redundant entry.
Rectified it and removed this from constant list.

delldubey
delldubey previously approved these changes Jul 3, 2023
Copy link
Contributor

@delldubey delldubey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@suryagupta4
Copy link
Contributor

suryagupta4 commented Jul 4, 2023

@tssushma We can also give users an option for configuring the capacity-poll-interval
This is done for PowerStore & PowerScale, refer here:
https://github.com/dell/csm-operator/blob/main/samples/storage_csm_powerstore_v270.yaml#L65
https://github.com/dell/csm-operator/blob/main/samples/storage_csm_powerscale_v270.yaml#L249

@rensyct
Copy link
Contributor

rensyct commented Jul 6, 2023

@tssushma , is this change intended for 2.7 or 2.8 version of the driver

@tssushma
Copy link
Contributor Author

tssushma commented Jul 7, 2023

@tssushma , is this change intended for 2.7 or 2.8 version of the driver

@tssushma , is this change intended for 2.7 or 2.8 version of the driver

@rensyct , Done updating the version to v2.8.
@suryagupta4, Done adding capacity-poll-interval configuration variable for giving the users an option for configuring poll interval.

@@ -0,0 +1 @@
minUpgradePath: v2.6.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be 2.7.0

forceRemoveDriver: true
common:
# Image for CSI PowerMax driver v2.7.0
image: dellemc/csi-powermax:v2.7.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be v2.8.0

@@ -1 +1 @@
minUpgradePath: v2.6.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove test files related to v2.7.0

@@ -0,0 +1 @@
minUpgradePath: v2.6.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be v2.7.0

- name: socket-dir
mountPath: /var/run/csi
- name: driver
image: dellemc/csi-powermax:v2.7.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be v2.8.0

capabilities:
add: ["SYS_ADMIN"]
allowPrivilegeEscalation: true
image: dellemc/csi-powermax:v2.7.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be v2.8.0

# true: enable storage capacity tracking
# false: disable storage capacity tracking
storageCapacity: true
# Config version for CSI PowerMax v2.7.0 driver
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be v2.8.0

forceUpdate: false
forceRemoveDriver: true
common:
# Image for CSI PowerMax driver v2.7.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be v2.8.0

- name: socket-dir
mountPath: /var/run/csi
- name: driver
image: dellemc/csi-powermax:v2.7.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be v2.8.0

capabilities:
add: ["SYS_ADMIN"]
allowPrivilegeEscalation: true
image: dellemc/csi-powermax:v2.7.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be v2.8.0

@shanmydell shanmydell merged commit be426fe into main Jul 10, 2023
7 checks passed
@shanmydell shanmydell deleted the feature_sct branch July 10, 2023 12:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants