NetApp
Import volume for nas/san economy driver
A feature to import nas/san volume and use it with the nas/san-economy-driver. With that, it is possible to pre-provision volumes, import it, so trident can use it for following automatic qtree creations, instead of letting trident dynamically create that volume.
We also need this, as the volume prefix is not used as a prefix by the nas-economy-driver. The volume prefix is embedded INSIDE the volume name, not in front of it. Therefore we cannot follow our naming conventions for ONTAP storage volumes.
If we could pre-provision the volume to be used by the nas-economy-driver, everything could work smoothly ...
Alternatively a volume name like PREFIX_trident_qtree_pool_... with a real configurable volume PREFIX variable will be fine.
Sorry, but I forgot to ask: Is it likely that the preconfigured nas-economy-driver volume is implemented within 2020 ? We are in trouble, because we reached the maxvol number of 499 volumes per aggregate, so we have to migrate from provisioning volumes to provisioning qtrees ...
Do you have any update on this ? Do you plan to implement this feature ?
We have more than 2000 PVC in Kubernetes and we had to use the ontap-nas-economy driver to avoid reaching the SVM volume number's limit.
But we are stuck to do disaster recovery because the volume import tool in DR does not seem to support qtree.
Hi team,
Any update on this issue?
we are planning to move from a k8s to another about 5000 PVC ontap-nas-economy :(
Hi all, Is there any update on this issue? (~900 volumes per node, and reaching the max won't be pretty 🥲)
+1 for this.
Volume limitation on NetApp hardware platform is biggest concern with nas driver. And nas-economy driver not having any recovery, import functionality makes it harldy usable.
This is forcing customers to move away from using trident. A solution to this is much needed.
