You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we are using the csi-driver with primera3par instead of nimble storage. During csi-driver execution in "node" mode, a call to tunelinux.ConfigureMultipath() is done. This function extends the multipath.conf file and and the "Nimble" configuration:
So, two issues as we are using primera3par and not nimble storage in our infrastructure, we do not have this in our multipath.conf, for us is just garbage that will not get used.
Would it be possible to avoid adding this Nimble configuration when Nimble storage is not being used? Wouldn't be necessary to have a "devices" default configuration created by csi driver in case of primera3par so an external source of configuration is not needed? We are using this in our case (as recommended by HPE):
Hi,
we are using the csi-driver with primera3par instead of nimble storage. During csi-driver execution in "node" mode, a call to tunelinux.ConfigureMultipath() is done. This function extends the multipath.conf file and and the "Nimble" configuration:
So, two issues as we are using primera3par and not nimble storage in our infrastructure, we do not have this in our multipath.conf, for us is just garbage that will not get used.
Would it be possible to avoid adding this Nimble configuration when Nimble storage is not being used? Wouldn't be necessary to have a "devices" default configuration created by csi driver in case of primera3par so an external source of configuration is not needed? We are using this in our case (as recommended by HPE):
The text was updated successfully, but these errors were encountered: