I don't use them as multipathing generally works without OVirt
bonds in
my setup, I configured multipathd directly to use round robin e.g.
Thanks, Uwe. Am I understanding correctly that you're just letting your nodes attach
to the iSCSI storage on their own by leaving "node.startup = automatic" in
/etc/iscsi/iscsid.conf so the hosts attach to all known targets as they boot, long before
oVirt services ever attempt to connect them? I've considered flipping that to
automatic, it's currently on "manual" as the idea was "let's let
oVirt connect and manage the storage it wants".
As another poster below mentioned, going the route of two separate iSCSI bonds in the
"iSCSI Multipath" section does work when you're adding new storage domains.
The aspect he talks about, where you connect both paths and save it, isn't possible if
you import an existing storage domain. When importing, the UI won't expose the
"Add" button that's available when creating a new domain, so you can't
add redundant paths. You can import the storage, then edit it and discover/login to the
other path, but that does _not_ save to the database and will not persist across reboots
or connect on other hosts you add to the cluster (have to login manually on each). You
can't edit your iSCSI bonds and check the box for these manually logged in targets
either, they'll never populate in that part of the UI so can't be selected. I
think it's just a UI issue because some very easy fidling in the database makes it
work exactly as you'd expect (and as it does for domains you newly add instead of
importing
).
Sorry, rambling, but I am curious about your "node.startup" setting in
iscid.conf. If left at 'automatic' (the default), are your hosts attaching all
the disks as they boot and oVirt doesn't mind that? It could be the path I'll take
as honestly I'd much prefer configuring the storage connections directly.
Thanks!
Mark