<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 28, 2017 at 1:54 PM, Nir Soffer <span dir="ltr"><<a href="mailto:nsoffer@redhat.com" target="_blank">nsoffer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><br><div class="gmail_quote"><span class=""><div dir="ltr">On Wed, Sep 27, 2017 at 11:01 PM Ben Bradley <<a href="mailto:listsbb@virtx.net" target="_blank">listsbb@virtx.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi All<br>
<br>
I'm looking to add a new host to my oVirt lab installation.<br>
I'm going to share out some LVs from a separate box over iSCSI and will<br>
hook the new host up to that.<br>
I have 2 NICs on the storage host and 2 NICs on the new Ovirt host to<br>
dedicate to the iSCSI traffic.<br>
I also have 2 separate switches so I'm looking for redundancy here. Both<br>
iSCSI host and oVirt host plugged into both switches.<br>
<br>
If this was non-iSCSI traffic and without oVirt I would create bonded<br>
interfaces in active-backup mode and layer the VLANs on top of that.<br>
<br>
But for iSCSI traffic without oVirt involved I wouldn't bother with a<br>
bond and just use multipath.<br>
<br>
From scanning the oVirt docs it looks like there is an option to have<br>
oVirt configure iSCSI multipathing.<br>
<br>
So what's the best/most-supported option for oVirt?<br></blockquote><div><br></div></span><div>oVirt support only multipath devices, so the best way is to use multipath</div><div>features.</div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Manually create active-backup bonds so oVirt just sees a single storage<br>
link between host and storage?<br></blockquote><div><br></div></span><div>This will always be on top of multipath device, giving you the same </div><div>capabilities, so why would you want to do that? </div></div></div></blockquote><div><br></div><div>If the link is not only for storage traffic, then it makes sense to use bonding.</div><div>Active-Active is much better, of course, if possible.</div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Or leave them as separate interfaces on each side and use oVirt's<br>
multipath/bonding?<br></blockquote><div><br></div></span><div>Yes.</div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Also I quite like the idea of using IPv6 for the iSCSI VLAN, purely down<br>
to the fact I could use link-local addressing and not have to worry<br>
about setting up static IPv4 addresses or DHCP. Is IPv6 iSCSI supported<br>
by oVirt?<br>
<br>
Thanks, Ben<br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
</blockquote></span></div></div>
<br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br></blockquote></div><br></div></div>