<div dir="ltr">Thanks all for your answer, it's more clear now<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 22, 2018 at 7:24 PM, FERNANDO FREDIANI <span dir="ltr"><<a href="mailto:fernando.frediani@upx.com" target="_blank">fernando.frediani@upx.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"><div><div><div><div><div>Hello Tal<br><br></div>It seems you have a very big overkill on your environment. I would say that normally 2 x 10Gb interfaces can do A LOT for nodes with proper redundancy. Just creating Vlans you can separate traffic and apply, if necessary, QoS per Vlan to guarantee which one is more priority.<br> <br></div>If you have 2 x 10Gb in a LACP 802.3ad Aggregation in theory you can do 20Gbps of aggregated traffic. If you have 10Gb of constant storage traffic it is already huge, so I normally consider that Storage will not go over a few Gbps and VMs another few Gb which fit perfectly within even 10Gb<br><br></div>The only exception I would make is if you have a very intensive (and I am not talking about IOPS, but throughput) from your storage then may be worth to have 2 x 10Gb for Storage and 2 x 10Gb for all other networks (Managment, VMs Traffic, Migration(with cap on traffic), etc).<br><br></div>Regards<span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888">Fernando<br></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">2018-03-21 16:41 GMT-03:00 Yaniv Kaul <span dir="ltr"><<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 21, 2018 at 12:41 PM, Tal Bar-Or <span dir="ltr"><<a href="mailto:tbaror@gmail.com" rel="noreferrer" target="_blank">tbaror@gmail.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"><div dir="auto"><div dir="ltr"><div><div><div><div><div><div><div><div>Hello All,<br><br></div>I am about to deploy a new Ovirt platform, the platform will consist 4 Ovirt nodes including management, all servers nodes and storage will have the following config:<br></div><u>nodes server<br></u></div>4x10G ports network cards<u><br></u></div>2x10G will be used for VM network.<br></div>2x10G will be used for storage connection<br></div>2x1Ge 1xGe for nodes management<br><br></div><u>Storage<br>
</u>4x10G ports network cards<u><u><br></u> </u></div>3 x10G for NFS storage mount Ovirt nodes<u><br></u><div dir="auto"><u><br></u>Now given above network configuration layout, what is best practices in terms of nodes for storage NFS connection, throughput and path resilience suggested to use </div><div dir="auto">First option each node 2x 10G lacp and on storage side 3x10G lacp?</div></div></div></div></blockquote><div><br></div><div>I'm not sure how you'd get more throughout than you can get in a single physical link. You will get redundancy. </div><div dir="auto"><br></div><div dir="auto">Of course, on the storage side you might benefit from multiple bonded interfaces. </div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="auto"><div dir="ltr"><div dir="auto"><br></div><div dir="auto" style="background-color:transparent">The second option creates 3 VLAN's assign each node on that 3 VLAN's across 2 nic, and on storage, side assigns 3 nice across 3 VLANs?<br></div></div></div></div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">Interesting - but I assume it'll still stick to a single physical link. </div><div dir="auto">Y. </div><div dir="auto"><br></div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="auto"><div dir="ltr"><div dir="auto" style="background-color:transparent"></div><div style="background-color:transparent">Thanks<span class="m_-4576238908643818255m_-1601599680632436643m_8684922469927056416HOEnZb"><font color="#888888"><br></font></span></div><span class="m_-4576238908643818255m_-1601599680632436643m_8684922469927056416HOEnZb"><font color="#888888"><div dir="auto" style="background-color:transparent"><br></div><div dir="auto"><u><br></u></div><div dir="auto"><u><br></u><div dir="auto"><div><div><u></u><div><div><div><div><br clear="all"><span class="m_-4576238908643818255HOEnZb"><font color="#888888"><div><br>-- <br><div class="m_-4576238908643818255m_-1601599680632436643m_8684922469927056416m_2471060979689768246m_-4404947222072348665m_-4543245849406367883gmail_signature" data-smartmail="gmail_signature">Tal Bar-or</div>
</div></font></span></div></div></div></div></div></div></div></div></font></span></div></div></div><span class="m_-4576238908643818255HOEnZb"><font color="#888888">
<br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" rel="noreferrer" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
<br></font></span></blockquote></div><br></div></div></div>
<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/mailman<wbr>/listinfo/users</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Tal Bar-or</div>
</div>