Bug 1351510 - [RFE] Support using Team devices instead of bond devices
Summary: [RFE] Support using Team devices instead of bond devices
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: future
Hardware: Unspecified
OS: Unspecified
unspecified
low with 3 votes
Target Milestone: ---
: ---
Assignee: Rob Young
QA Contact: Gil Klein
URL:
Whiteboard:
Depends On:
Blocks: 1549300
TreeView+ depends on / blocked
 
Reported: 2016-06-30 08:40 UTC by Barak Korren
Modified: 2021-08-30 12:42 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1549300 (view as bug list)
Environment:
Last Closed: 2018-06-06 07:50:32 UTC
oVirt Team: Network
Embargoed:
ylavi: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1724795 1 high CLOSED [RFE] Support for a 'source-load-balancing' bonding mode 2023-11-07 10:18:36 UTC
Red Hat Issue Tracker RHV-38562 0 None None None 2021-08-30 12:09:48 UTC
Red Hat Knowledge Base (Solution) 2852031 0 None None None 2017-01-09 20:33:41 UTC

Internal Links: 1724795

Description Barak Korren 2016-06-30 08:40:54 UTC
The teaming device [1] had been in Fedora since Fedora 18 and in RHEL since RHEL 7.0.
It provides some advantages over the bonding driver [2]. The most interesting of which seems to be the LACP load balancing.

[1]: http://libteam.org/
[2]: https://github.com/jpirko/libteam/wiki/Bonding-vs.-Team-driver-features

It may be desirable to enable oVirt to setup teaming on hypervisors instead of or in addition to bonding.

Comment 9 Peter Morgan 2018-05-15 00:50:31 UTC
Bump - I cannot use bonding on my blades due to the nature of the networking, but teaming would give me network redundancy/resiliency.

Comment 10 Yaniv Lavi 2018-06-06 07:50:32 UTC
Closing old RFEs, please reopen if still needed.
Patches are always welcomed.

Comment 11 Yaniv Lavi 2018-06-11 10:28:16 UTC
(In reply to Peter Morgan from comment #9)
> Bump - I cannot use bonding on my blades due to the nature of the
> networking, but teaming would give me network redundancy/resiliency.

Please explain the use case with detail. Why is bonding not working.

Comment 12 Dominik Holler 2019-05-14 13:50:54 UTC
https://lists.ovirt.org/archives/list/users@ovirt.org/message/N4OJ2SXBUMSOJ4CD2XXZJ2A3HH3VVVLF/

> Purely the load balancing for
> LACP support and the low overhead. Since teamd is probably going to be
> the future I wanted to have oVirt using it. Furthermore, teamd is much
> more flexible to extend, add new interfaces, change priorities and you
> name it.

Comment 13 Carlos 2019-11-14 12:33:30 UTC
IMHO would be nice, add support bond0 or nic teaming, like VMware, where in some cases there is no needed special config on network/switch side and we still have some redundancy and availability.
Maybe NIC teaming woulb be a good choice.

Regards

Carlos

Comment 15 franz.skale@itg.graz.at 2020-06-02 10:27:46 UTC
Hi,
not supporting teamd (using Netlink) is a show stopper for enterprise environments.
When using state of the art Hardware (e.g. CISCO ACI) and LACP (mode 4 -> TX/RX Loadbalancing) then bonding will not work for you.
Right now, bonding doesn't support "load-balancing for LACP -> mode 4".
See the readhat support page for details: (8.3)
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-comparison_of_network_teaming_to_bonding
Using the well written NetLink Interface provides a bunch of pros. (See kernel docs for details).
How can we manage to get things going using teamd ?


Best regards
Franz


Note You need to log in before you can comment on or make changes to this bug.