<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Thanks for your input, Simone.
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 4 Jul 2017, at 05:01, Simone Tiraboschi <<a href="mailto:stirabos@redhat.com" class="">stirabos@redhat.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class=""><br class="">
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Tue, Jul 4, 2017 at 5:50 AM, Vinícius Ferrão <span dir="ltr" class="">
<<a href="mailto:ferrao@if.ufrj.br" target="_blank" class="">ferrao@if.ufrj.br</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto" class="">
<div class="">Thanks, Konstantin.</div>
<div id="gmail-m_6933526667998627573AppleMailSignature" class=""><br class="">
</div>
<div id="gmail-m_6933526667998627573AppleMailSignature" class="">Just to be clear enough: the first deployment would be made on classic eth interfaces and later after the deployment of Hosted Engine I can convert the "ovirtmgmt" network to a LACP Bond, right?</div>
<div id="gmail-m_6933526667998627573AppleMailSignature" class=""><br class="">
</div>
<div id="gmail-m_6933526667998627573AppleMailSignature" class="">Another question: what about iSCSI Multipath on Self Hosted Engine? I've looked through the net and only found this issue: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1193961" target="_blank" class="">https://bugzilla.<wbr class="">redhat.com/show_bug.cgi?id=<wbr class="">1193961</a></div>
<div id="gmail-m_6933526667998627573AppleMailSignature" class=""><br class="">
</div>
<div id="gmail-m_6933526667998627573AppleMailSignature" class="">Appears to be unsupported as today, but there's an workaround on the comments. It's safe to deploy this way? Should I use NFS instead?</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">It's probably not the most tested path but once you have an engine you should be able to create an iSCSI bond on your hosts from the engine.</div>
<div class="">Network configuration is persisted across host reboots and so the iSCSI bond configuration.</div>
<div class=""><br class="">
</div>
<div class="">A different story is instead having ovirt-ha-agent connecting multiple IQNs or multiple targets over your SAN. This is currently not supported for the hosted-engine storage domain. </div>
<div class="">See:</div>
<div class=""><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1149579" class="">https://bugzilla.redhat.com/show_bug.cgi?id=1149579</a><br class="">
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>Just to be clear, when we talk about bonding on iSCSI, we’re talking about iSCSI MPIO and not LACP (or something similar) on iSCSI interfaces, right? In my case there are two different fabrics dedicated to iSCSI. They do not even transit on the same switch,
so it’s plain ethernet (with fancy things, like mtu 9216 enabled and QoS).</div>
<div><br class="">
</div>
<div>So I think we’re talking about the unsupported feature of multiple IQN’s right?</div>
<div><br class="">
</div>
<div>Thanks once again,</div>
<div>V.</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">
<div class="gmail_extra">
<div class="gmail_quote">
<div class=""> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto" class="">
<div id="gmail-m_6933526667998627573AppleMailSignature" class=""><br class="">
</div>
<div id="gmail-m_6933526667998627573AppleMailSignature" class="">Thanks,</div>
<div id="gmail-m_6933526667998627573AppleMailSignature" class="">V.</div>
<div id="gmail-m_6933526667998627573AppleMailSignature" class=""><br class="">
Sent from my iPhone</div>
<span class="gmail-">
<div class=""><br class="">
On 3 Jul 2017, at 21:55, Konstantin Shalygin <<a href="mailto:k0ste@k0ste.ru" target="_blank" class="">k0ste@k0ste.ru</a>> wrote:<br class="">
<br class="">
</div>
<blockquote type="cite" class="">
<div class="">
<blockquote type="cite" class=""><span class="">Hello,</span><br class="">
</blockquote>
<blockquote type="cite" class=""><span class=""></span><br class="">
</blockquote>
<blockquote type="cite" class=""><span class="">I’m deploying oVirt for the first time and a question has emerged: what is the good practice to enable LACP on oVirt Node? Should I create 802.3ad bond during the oVirt Node installation in Anaconda, or it should
be done in a posterior moment inside the Hosted Engine manager?</span><br class="">
</blockquote>
<blockquote type="cite" class=""><span class=""></span><br class="">
</blockquote>
<blockquote type="cite" class=""><span class="">In my deployment we have 4x GbE interfaces. eth0 and eth1 will be a LACP bond for management and servers VLAN’s, while eth1 and eth2 are Multipath iSCSI disks (MPIO).</span><br class="">
</blockquote>
<blockquote type="cite" class=""><span class=""></span><br class="">
</blockquote>
<blockquote type="cite" class=""><span class="">Thanks,</span><br class="">
</blockquote>
<blockquote type="cite" class=""><span class="">V.</span><br class="">
</blockquote>
<span class=""></span><br class="">
<span class="">Do all your network settings in ovirt-engine webadmin.</span><br class="">
</div>
</blockquote>
</span></div>
<br class="">
______________________________<wbr class="">_________________<br class="">
Users mailing list<br class="">
<a href="mailto:Users@ovirt.org" class="">Users@ovirt.org</a><br class="">
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank" class="">http://lists.ovirt.org/<wbr class="">mailman/listinfo/users</a><br class="">
<br class="">
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>