-
Notifications
You must be signed in to change notification settings - Fork 38
Open
Description
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:
device {
vendor "Nimble"
product "Server"
hardware_handler "1 alua"
path_checker tur
rr_weight uniform
rr_min_io_rq 1
dev_loss_tmo infinity
fast_io_fail_tmo 5
no_path_retry 30
path_selector "service-time 0"
path_grouping_policy group_by_prio
prio alua
failback immediate
}
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):
device {
prio alua
vendor "3PARdata VV"
path_grouping_policy group_by_prio
hardware_handler "1 alua"
failback immediate
fast_io_fail_tmo 10
path_selector "round-robin 0"
product "Server"
no_path_retry 30
path_checker tur
dev_loss_tmo infinity
}
Metadata
Metadata
Assignees
Labels
No labels