multipath-tools has support for "foreign" libraries in multipath-tools since 0.8.0, and support for enabling/disabling them at runtime since 0.8.3. The only foreign library that exists is "nvme" (for native NVMe multipath), and it's likely to remain so for some time. Currently upstream multipath-tools ships with all foreign libraries enabled by default, and documentation about how to disable them. There's an ongoing discussion between myself and folks from Netapp about changing the code such that the nvme library is disabled by default. People at Netapp are worried that multipath's output for NVMe native multipath maps would confuse customers and break scripts. I've suggested that Netapp simply ship a drop-in configuration file to be put in /etc/multipath/conf.d to disable the nvme library, but I'm told that customers are wary about vendor-supplied configuration files. For SUSE's enterprise product, SLE, we have made this change and disabled the nvme library by default. Now Netapp is asking me to forward this change upstream. Personally, I'm not too fond of the proposal, because I think the original idea (enable people to use the tools they are used to) is still valid (*). OTOH, the "nvme" tool can provide similar information and is likely to be used by NVMe users anyway, so perhaps there's no urgent need for this functionality in multipath-tools any more. I really don't know if people out there find this feature rather helpful or rather confusing. Therefore I'd like to ask for opinions here on the list. Regards, Martin (*) Also because I, myself, have put quite some effort into the "foreign/nvme" feature and wouldn't be happy to see it go away. -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
