No edit summary |
No edit summary |
||
Line 11: | Line 11: | ||
== Current status == | == Current status == | ||
* Targeted release: Fedora 18 | * Targeted release: Fedora 18 | ||
* Last updated: 2012- | * Last updated: 2012-07-18 | ||
* Percentage of completion: 90% | * Percentage of completion: 90% | ||
Revision as of 14:12, 18 July 2012
= Network Team driver
Summary
Network Team driver allows multiple NICs to be teamed together and act like a single one.
Owner
- Name: Jiri Pirko
- Email: jiri@pirko.cz
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.
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