Skip to content

Conversation

@arndt-netapp
Copy link
Contributor

Added the limitAggregateUsageOnResize configuration parameter for ONTAP backends that support the limitAggregateUsage configuration parameter. If the limitAggregateUsageOnResize parameter is not set, the original behavior with the limitAggregateUsage parameter is used. If the limitAggregateUsageOnResize is configured, PVC expansion can be allowed at a different aggregate utilization threshold than PVC creation.

Below is an example of a backend configuration using this new parameter:

{
"version": 1,
"storageDriverName": "ontap-nas",
"backendName": "sim1",
"managementLIF": "192.168.227.130",
"dataLIF": "192.168.227.131",
"svm": "svm1",
"username": "admin",
"password": "netapp123",
"limitAggregateUsage": "60%",
"limitAggregateUsageOnResize": "80%",
"limitVolumeSize": "50Gi",
"nfsMountOptions": "nfsvers=3",
"defaults": {
"exportPolicy": "default",
"snapshotPolicy": "none",
"snapshotReserve": "0"
}
}

backends that support the limitAggregateUsage configuration parameter.
If the limitAggregateUsageOnResize parameter is not set, the original
behavior with the limitAggregateUsage parameter is used.  If the
limitAggregateUsageOnResize is configured, PVC expansion can be
allowed at a different aggregate utilization threshold than PVC creation.
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.

1 participant