<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 4, 2017 at 5:50 AM, Vinícius Ferrão <span dir="ltr"><<a href="mailto:ferrao@if.ufrj.br" target="_blank">ferrao@if.ufrj.br</a>></span> wrote:<br><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">
<div>Thanks, Konstantin.</div>
<div id="gmail-m_6933526667998627573AppleMailSignature"><br>
</div>
<div id="gmail-m_6933526667998627573AppleMailSignature">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"><br>
</div>
<div id="gmail-m_6933526667998627573AppleMailSignature">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">https://bugzilla.<wbr>redhat.com/show_bug.cgi?id=<wbr>1193961</a></div>
<div id="gmail-m_6933526667998627573AppleMailSignature"><br>
</div>
<div id="gmail-m_6933526667998627573AppleMailSignature">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><br></div><div>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>Network configuration is persisted across host reboots and so the iSCSI bond configuration.</div><div><br></div><div>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>See:</div><div><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1149579">https://bugzilla.redhat.com/show_bug.cgi?id=1149579</a><br></div><div> </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">
<div id="gmail-m_6933526667998627573AppleMailSignature"><br>
</div>
<div id="gmail-m_6933526667998627573AppleMailSignature">Thanks,</div>
<div id="gmail-m_6933526667998627573AppleMailSignature">V.</div>
<div id="gmail-m_6933526667998627573AppleMailSignature"><br>
Sent from my iPhone</div><span class="gmail-">
<div><br>
On 3 Jul 2017, at 21:55, Konstantin Shalygin <<a href="mailto:k0ste@k0ste.ru" target="_blank">k0ste@k0ste.ru</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<blockquote type="cite"><span>Hello,</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>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>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>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>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Thanks,</span><br>
</blockquote>
<blockquote type="cite"><span>V.</span><br>
</blockquote>
<span></span><br>
<span>Do all your network settings in ovirt-engine webadmin.</span><br>
</div>
</blockquote>
</span></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>