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

Enable Per-node igroup for ontap-san-economy #758

Closed
eedo369 opened this issue Aug 11, 2022 · 1 comment
Closed

Enable Per-node igroup for ontap-san-economy #758

eedo369 opened this issue Aug 11, 2022 · 1 comment

Comments

@eedo369
Copy link

eedo369 commented Aug 11, 2022

Describe the solution you'd like
Trident 22.07 introduced the feature of per-node igroup for the ONTAP-SAN driver. We would like to have this feature for the ONTAP-SAN-ECONOMY driver

Describe alternatives you've considered
None

Additional context
We are using on-prem OpenShift 4.6.8 with CoreOS and the ONTAP-SAN-ECONOMY driver. We have reached a high number of PVs in the cluster - about 650+. Due to the way iscsid and multipathd work, each node need to scan all of its devices periodically and when creating a new device. And so, we hope that the per-node mapping of PVs with help us with the performance and scalability of hundreds of PVs per cluster (we are looking for this feature for performance reasons and not security reasons).

This is dark site environment with no internet connectivity so we are limited with log collection and screenshots.

Pasting from the release notes of 22.07:
"ONTAP-SAN volumes will now use per-node igroups and only map LUNs to igroups while actively published to those nodes to improve our security posture. Existing volumes will be opportunistically switched to the new igroup scheme when Trident determines it is safe to do so without impacting active workloads."

@gnarl
Copy link
Contributor

gnarl commented Apr 25, 2023

The per-node igroup capability is now available for the ontap-san and ontap-san-economy storage drivers with the Trident v23.04 release.

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

2 participants