--_000_91E0EEC887094D9184F7F7B8836343AEifufrjbr_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks, Konstantin. 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 th= e "ovirtmgmt" network to a LACP Bond, right? Another question: what about iSCSI Multipath on Self Hosted Engine? I've lo= oked through the net and only found this issue: https://bugzilla.redhat.com= /show_bug.cgi?id=3D1193961 Appears to be unsupported as today, but there's an workaround on the commen= ts. It's safe to deploy this way? Should I use NFS instead? Thanks, V. Sent from my iPhone On 3 Jul 2017, at 21:55, Konstantin Shalygin <k0ste@k0ste.ru<mailto:k0ste@k= 0ste.ru>> wrote: Hello, 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 bon= d during the oVirt Node installation in Anaconda, or it should be done in a= posterior moment inside the Hosted Engine manager? In my deployment we have 4x GbE interfaces. eth0 and eth1 will be a LACP bo= nd for management and servers VLAN's, while eth1 and eth2 are Multipath iSC= SI disks (MPIO). Thanks, V. Do all your network settings in ovirt-engine webadmin. --_000_91E0EEC887094D9184F7F7B8836343AEifufrjbr_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> </head> <body dir=3D"auto"> <div>Thanks, Konstantin.</div> <div id=3D"AppleMailSignature"><br> </div> <div id=3D"AppleMailSignature">Just to be clear enough: the first deploymen= t would be made on classic eth interfaces and later after the deployment of= Hosted Engine I can convert the "ovirtmgmt" network to a LACP Bo= nd, right?</div> <div id=3D"AppleMailSignature"><br> </div> <div id=3D"AppleMailSignature">Another question: what about iSCSI Multipath= on Self Hosted Engine? I've looked through the net and only found this iss= ue: <a href=3D"https://bugzilla.redhat.com/show_bug.cgi?id=3D1193961">= https://bugzilla.redhat.com/show_bug.cgi?id=3D1193961</a></div> <div id=3D"AppleMailSignature"><br> </div> <div id=3D"AppleMailSignature">Appears to be unsupported as today, but ther= e's an workaround on the comments. It's safe to deploy this way? Should I u= se NFS instead?</div> <div id=3D"AppleMailSignature"><br> </div> <div id=3D"AppleMailSignature">Thanks,</div> <div id=3D"AppleMailSignature">V.</div> <div id=3D"AppleMailSignature"><br> Sent from my iPhone</div> <div><br> On 3 Jul 2017, at 21:55, Konstantin Shalygin <<a href=3D"mailto:k0ste@k0= ste.ru">k0ste@k0ste.ru</a>> wrote:<br> <br> </div> <blockquote type=3D"cite"> <div> <blockquote type=3D"cite"><span>Hello,</span><br> </blockquote> <blockquote type=3D"cite"><span></span><br> </blockquote> <blockquote type=3D"cite"><span>I’m deploying oVirt for the first tim= e and a question has emerged: what is the good practice to enable LACP on o= Virt 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=3D"cite"><span></span><br> </blockquote> <blockquote type=3D"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=3D"cite"><span></span><br> </blockquote> <blockquote type=3D"cite"><span>Thanks,</span><br> </blockquote> <blockquote type=3D"cite"><span>V.</span><br> </blockquote> <span></span><br> <span>Do all your network settings in ovirt-engine webadmin.</span><br> </div> </blockquote> </body> </html> --_000_91E0EEC887094D9184F7F7B8836343AEifufrjbr_--