[ovirt-users] Network redundancy with Manual balancing per VLAN

[Fernando Frediani]

Well, yes. That's actually the name VMware uses.

If it bring similar functionalities then that's the solution. Thanks for 
sharing. looks pretty intresting.

Fernando

Em 27/06/2016 09:39, Fabrice Bacchella escreveu:
> Isn't teaming[1] the futur, instead of bonding ?
>
> [1] http://rhelblog.redhat.com/2014/06/23/team-driver/
>
>
>> Le 27 juin 2016 à 14:31, Fernando Frediani 
>> <fernando.frediani at upx.com.br <mailto:fernando.frediani at upx.com.br>> 
>> a écrit :
>>
>> Thanks for the reply.
>>
>> Perhaps is the case of contacting the maintainer of Linux Bond module 
>> and see if there is room for this feature to be implement anytime. 
>> OVS is great in the coming future, but Bond module is still something 
>> very handy that simplify the things a lot.
>>
>> Thanks
>> Fernando
>>
>> Em 27/06/2016 03:00, Edward Haas escreveu:
>>>
>>>
>>> On Sun, Jun 26, 2016 at 4:37 PM, Yevgeny Zaspitsky 
>>> <yzaspits at redhat.com> wrote:
>>>
>>>     Dan, Edy,
>>>
>>>     Could you guys answer this?
>>>
>>>     IIUC, the requirements are:
>>>
>>>       * stream the traffic of few VLANs(network roles) through a
>>>         single bond
>>>       * be able to bind a VLAN to a bond slave with an option of
>>>         fallback
>>>       * have redundancy
>>>       * assign different QoS to every VLAN (my addition)
>>>
>>>     I guess this is a new RFC that we do not support currently, but
>>>     would we be able to provide in any future?
>>>
>>>     ---------- Forwarded message ----------
>>>     From: *Fernando Frediani* <fernando.frediani at upx.com.br>
>>>     Date: Sat, Jun 25, 2016 at 11:17 PM
>>>     Subject: [ovirt-users] Network redundancy with Manual balancing
>>>     per VLAN
>>>     To: users at ovirt.org <mailto:users at ovirt.org>
>>>
>>>
>>>     Hello,
>>>
>>>     In VMware it is possible to bond two network interfaces and for
>>>     each Portgroup (equivalent to a VLAN) is possible to tell which
>>>     of the physical interfaces underneath it you wish the traffic to
>>>     flow primarily and which stays as secondary(bond mode=1
>>>     equivalent). So for certain VLANs (Management, Live Migration,
>>>     etc) is possible to force traffic flow via one physical NIC of
>>>     the bond and for other VLANs (Virtual Machine's traffic) outs
>>>     via the other NIC with failover to each other should a cable or
>>>     switch fails.
>>>
>>>     This is specially good for better utilize the fewer NICs
>>>     available and still have redundancy.
>>>
>>>     In oVirt it is also possible to have bonds, but would it still
>>>     be possible to do that same and favor the traffic per VLAN basis
>>>     ? I guess it is something related to Linux Bond module but
>>>     perhaps someone has done this already.
>>>
>>>
>>>     Thanks
>>>
>>>     Fernando
>>>
>>>     _______________________________________________
>>>     Users mailing list
>>>     Users at ovirt.org <mailto:Users at ovirt.org>
>>>     http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>> Hello Fernando,
>>>
>>> As you mentioned, oVirt is using the Linux Bond and the solution you 
>>> are looking for is not supported.
>>> The oVirt way to handle this is by applying QoS on the networks, 
>>> providing the guaranteed rates for each and utilizing the bond for 
>>> throughput beyond the one link limit.
>>>
>>> With the introduction of OVS as an alternative networking 
>>> infrastructure for the hosts, you could create a hook that 
>>> implements some special functionality, but ovs is not in yet.
>>>
>>> Thanks,
>>> Edy.
>>>
>>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org <mailto:Users at ovirt.org>
>> http://lists.ovirt.org/mailman/listinfo/users
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20160627/5f5a7478/attachment-0001.html>