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

Set storage use limit on ONTAP side #341

Open
ArtemKaba opened this issue Feb 13, 2020 · 5 comments
Open

Set storage use limit on ONTAP side #341

ArtemKaba opened this issue Feb 13, 2020 · 5 comments

Comments

@ArtemKaba
Copy link

ArtemKaba commented Feb 13, 2020

Brief: how to set up limit on storage utilisation in case of using ontap-nas (or ontap-nas-economy) driver?
We have trident installation with Openshift 3.11 cluster, backend was create at storage that we aren't own.
And now ONTAP Administrator wants to set limit to use his storage device because we can fill in all disks at any time.
How would he can acheive it?
We already have added line "limitVolumeSize" to backend configuration, but it is not under ONTAP Admin's control.

I hope I clearly explained the problem :)

@balaramesh
Copy link
Contributor

Hi @ArtemKaba

You can set storage limits at the K8s level by defining Storage Resource Quotas and also limit the volume size provisioned by Trident using the limitVolumeSize parameter. The expectation is for the K8s admin to work with the storage admin when establishing these limits within k8s. As I understand, the question is wrt establishing limits at the ONTAP cluster itself. Take a look at our best practices for configuring ONTAP backends. You can limit the max number of volumes and set the maximum size per volume. You can also limit the aggregates assigned to your Trident SVM

@ArtemKaba
Copy link
Author

@balaramesh as i know there is no way to set the maximum size per volume for SVM in ONTAP.
In case of using nas-economy driver, trident will create 200 qtrees in volume and then create new one. And every volume can expand as much as possible.
As a result we can establish limit only on the k8s side.

@gnarl
Copy link
Contributor

gnarl commented Jun 7, 2020

@ArtemKaba we tested resize and don't agree with your statement. If you set the limitVolumeSize parameter for the backend that will enforce the maximum volume size when resizing a volume. Can you verify this?

@ArtemKaba
Copy link
Author

@gnarl You absolutely right. But I am talking about limiting storage usage exactly on ONTAP side.
Owner of storage device can't set up quota for our k8s cluster because we have svm-admin permissions as well as limitVolumeSize parameter under our control.

netapp-ci pushed a commit that referenced this issue Jul 29, 2020
Remove backend config JSON from update backend log
@darthVikes
Copy link

This ref; shows limiting the size per the user role below URL link but I don't see this now listed in the newer documentation for v20.04? Any idea why that was removed? I would also like to ensure we can also enforce this on the OnTap side as well as people that may have access to the PVC side are different roles.

https://netapp-trident.readthedocs.io/en/stable-v19.01/dag/kubernetes/storage_configuration_trident.html#limit-the-maximum-size-of-volumes-created-by-the-trident-user

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants