<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. -->

<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. -->

−

Currently, the feature is fully functional. Only some little things and tweaks are going to go in for Fedora 18. But if some of this little things won't make it, it would not be a show-stopper.

+

Currently, the feature is fully functional. Only some little things and tweaks are going to go in for Fedora 18.

Summary

Owner

Current status

Targeted release: Fedora 18

Last updated: 2012-07-18

Percentage of completion: 90%

Detailed Description

The purpose of the Team driver is to provide a mechanism to team multiple NICs (ports) into one logical one (teamdev) at L2 layer. The process is called "channel bonding", "Ethernet bonding", "channel teaming", "link aggregation", etc. This is already implemented in the Linux kernel by the bonding driver. The main thing to realize is that the Team driver project is not trying to replicate or mimic the bonding driver. What it does is it resolve the same problem using a different approach. Therefore, for example, the way Team is configured differs dramatically from the way bonding is. Team has many advantages over Bonding. It's modular, userspace driven, fast.

This feature consists of two parts:

kernel module (modules). They are already part of Fedora 18 kernel package.

userspace library (libteam package) and daemon (teamd package).

Benefit to Fedora

This will bring possibility to run userspace driven NIC teaming. There are some features not supported by bonding are supported by Team driver, for example:

load balancing for LACP

separate per-port link monitoring setup

port priorities and stickiness

IPv6 Neighbor Solicitation/Neighbor Advertisement link monitoring

Scope

Team driver is quite isolated, and does not impact other areas. It does not touch any existing things.

How To Test

Install "teamd" package first. You need two network interfaces for this basic test. In case their names are not "eth1" and "eth2", please adjust the config file.

Documentation

Release Notes

Fedora 18 includes Team Driver which provides a possibility to team multiple network interfaces together so they act like a single network interface. This extends teaming possibilities provided by existing bonding driver. It also provides userspace driven, modular alternative to bonding driver.