(Created page with "= Network Team driver - Update for new features = == Summary == <!-- A sentence or two summarizing what this feature is and what it will do. This information is used for th...") |
No edit summary |
||
| Line 59: | Line 59: | ||
== Dependencies == | == Dependencies == | ||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | ||
No dependencies. | |||
== Contingency Plan == | == Contingency Plan == | ||
| Line 74: | Line 76: | ||
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | ||
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | ||
New features are added to Team driver. All changes are backward compatible so current users of Team drivers should not experience any difficulties. | |||
== Comments and Discussion == | == Comments and Discussion == | ||
Revision as of 15:41, 29 January 2013
Network Team driver - Update for new features
Summary
Network Team driver allows multiple network interfaces to be teamed together and act like a single one. This update adds several kind of new features to it.
Owner
- Name: Jiri Pirko
- Email: jiri@pirko.cz
Current status
- Targeted release: Fedora 19
- Last updated: 2012-01-29
- Percentage of completion: 20%
Detailed Description
The goal is to extend current Team driver experience in Fedora. In order to do that, following features will be implemented:
- ARP link validation over VLAN
- Transmit hashing involving L4 headers
- Support for NICs which do now allow mac change on run
- Load balancing support for incoming traffic
- Corrected carrier detection
Benefit to Fedora
The benefit is in fact that Fedora will be providing more complete network teaming solution.
Scope
Team driver is quite isolated, and does not impact other areas.
How To Test
User Experience
User will not experience any difference comparing to existing state. Only there is new possibility to use newly added Team driver features.
Dependencies
No dependencies.
Contingency Plan
None necessary, revert to previous release behaviour.
Documentation
Release Notes
New features are added to Team driver. All changes are backward compatible so current users of Team drivers should not experience any difficulties.