Hello DM multipath developers,
I've been messing quite a while today with getting my blacklisting for a system right. The current solution works; blacklisting all internal disks by wwid, but I still think its sub-optimal.
Wouldn't it be easier to make the blacklist and whitelist behave just like IPtables or PostFix ? That is as soon as the first decision is made its done. I think it would also be easier to code as it would be a list of regular expressions which need to be matched and the first one triggering wins.
With that solution the config for most setups would be something like:
whitelist {
device {
vendor "My SAN vendor"
product "My SAN product"
}
}
blacklist {
devnode "*"
}
This would make configuration alot easier than it is right now when I have to blacklist all the 'non multipath' devices.
Kind regards,
Arno
This non-optimal setup still exists, and proposals for a better whitelist/blacklist have been discussed on dm-devel, but no work has been done on it yet.
Hello DM multipath developers, I've been messing quite a while today with getting my blacklisting for a system right. The current solution works; blacklisting all internal disks by wwid, but I still think its sub-optimal. Wouldn't it be easier to make the blacklist and whitelist behave just like IPtables or PostFix ? That is as soon as the first decision is made its done. I think it would also be easier to code as it would be a list of regular expressions which need to be matched and the first one triggering wins. With that solution the config for most setups would be something like: whitelist { device { vendor "My SAN vendor" product "My SAN product" } } blacklist { devnode "*" } This would make configuration alot easier than it is right now when I have to blacklist all the 'non multipath' devices. Kind regards, Arno