Trident: Is it possible for ontap-nas-economy driver to disable the duplicate storagePrefix for volume & qtree name?

[mircster]

Hello Trident team,

at the moment my mountpath for the Qtree created with ontap-nas-economy driver looks like this:
xx03v10cl02.xxxxxxxxxxxxx.com:/trident_qtree_pool_xx03v10_ocpeco_000000_sq2_nas_nfs_ABCDEFGHIJ/xx03v10_ocpeco_000000_sq2_nas_nfs_projectname_postgresql_00abc

_storagePrefix = "xx03v10_ocpeco_000000_sq2_nas_nfs"_

This is very long.
I cannot spare the storagePrefix for the volume name because of naming convention requirements.
But i could spare the storagePrefix for the qtree name!
I don´t need the duplicate information from the storagePrefix in the volume name + qtree name.

I would like to be able to disable the storagePrefix only for the qtree name in the backend config:
xx03v10cl02.xxxxxxxxxxxxx.com:/trident_qtree_pool_xx03v10_ocpeco_000000_sq2_nas_nfs_ABCDEFGHIJ/projectname_postgresql_00abc

Is this possible or can it be implemented?
Thanks & Regards

[innergy]

That's a very long storage prefix indeed! There are details around how the ONTAP API works and how volumes and qtree objects are managed in ONTAP itself that require us to include a unique identifier like the storage prefix in the qtree name.

We may be able to allow you to specify a separate unique identifier for cases like this where duplicating the storage prefix results in a very long name. It would still need to be unique, but it could be short. We'll take a look.

[cgajan]

I created the pull request #238 which include this enhancement. Hope it will be integrated soon :-)

[mircster]

Hello cgajan!
This is great! I also hope that it will be integrated soon!
But still this is not 100% what helps us!
Would it be possible to also add a qtreePrefix or to disable storagePrefix for qtrees?
We need this ASAP, as we are hitting the maxQtreeNameLength = 64 limit.
We already shrink the prefix, but still we need more characters for projectname and pvc.

[MikeTomlin19]

Hi, we are facing the same issue, but with namespace naming conventions. Removing the storage prefix wouldn’t solve our use case, as the QTree names would still be more than 64 characters. Is it possible for Trident to create the QTree names like it does for e-series (create a random GUID due to length restrictions).

[gandalftg]

Hi,

having a similar request (case 2007961146), ontap-nas-economy should be aware of 64 characters limit in ONTAP and shouldn't create to long qtree names. maxQtreeNameLength = 64 looks as good option to add.
if possible also to control the naming convention so they won't get shorten in the wrong place

Thanks

[gnarl]

This issue was fixed with commit 5afa354.