Features/NetworkManagerBonding

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Current status)
Line 1: Line 1:
 
== NetworkManager Bonding Support ==
 
== NetworkManager Bonding Support ==
  
=== Summary ===
+
== Summary ==
  
 
NetworkManager should be able to configure bonding interfaces consisting of
 
NetworkManager should be able to configure bonding interfaces consisting of
Line 7: Line 7:
 
desktop and laptop bonding use cases.
 
desktop and laptop bonding use cases.
  
=== Owner ===
+
== Owner ==
  
 
* Name: [[User:Pavlix|Pavel Šimerda]]
 
* Name: [[User:Pavlix|Pavel Šimerda]]
 
* Email: psimerda at redhat.com
 
* Email: psimerda at redhat.com
  
=== Current status ===
+
== Current status ==
  
 
* Targeted release: [[Releases/19|Fedora 19]]
 
* Targeted release: [[Releases/19|Fedora 19]]
Line 18: Line 18:
 
* Percentage of completion: 40%
 
* Percentage of completion: 40%
  
=== Detailed description ===
+
== Detailed description ==
  
 
The current bonding configuration in NetworkManager doesn't always work. The purpose of this Fedora feature is to implement reliable bonding configuration infrastructure in NetworkManager that would
 
The current bonding configuration in NetworkManager doesn't always work. The purpose of this Fedora feature is to implement reliable bonding configuration infrastructure in NetworkManager that would
Line 26: Line 26:
 
* Configuration using keyfiles
 
* Configuration using keyfiles
  
=== Benefit to Fedora ===
+
== Benefit to Fedora ==
  
 
Bonding is necessary for enterprise virtualization. There is also a common laptop usage for bonding wifi and ethernet together to present the laptop computer under a single MAC address to the local network and thus aquire just one MAC address regardless it is connected through cable and wifi.
 
Bonding is necessary for enterprise virtualization. There is also a common laptop usage for bonding wifi and ethernet together to present the laptop computer under a single MAC address to the local network and thus aquire just one MAC address regardless it is connected through cable and wifi.
 +
 +
== Scope ==
 +
 +
This feature requires changes to NetworkManager, nm-applet, nm-connection-editor,
 +
gnome-shell, gnome-control-center and KDE counterparts.
 +
 +
== How To Test ==
 +
 +
Configure a bonding interface and its slaves using GUI or CLI. Check using <code>ip link</code> or other tool. Test that the bonding actually works.
 +
 +
== User Experience ==
 +
 +
GUI and CLI tools.
 +
 +
== Dependencies ==
 +
 +
NetworkManager must only use bonding when configured so and it must only take over bond configuration if requested so by administrator or by another tool. Therefore libvirt and other tools that rely on bonding can be ported to the new functionality at any time.
 +
 +
== Contingency Plan ==
 +
 +
Don't support bonding in NetworkManager. Tools that need bonding would have to continue to use the same tools as before.
 +
 +
== Documentation ==
 +
 +
Documentation will be drafted at [[Networking/Bonding]].
 +
 +
== Release Notes ==
 +
 +
NetworkManager now supports ethernet bonding.
 +
 +
== Comments and Discussion ==
 +
 +
* See [[Talk:Features/NetworkManagerBonding]]
 +
 +
[[Category:FeaturePageIncomplete]]

Revision as of 11:24, 8 January 2013

Contents

NetworkManager Bonding Support

Summary

NetworkManager should be able to configure bonding interfaces consisting of wired and wireless ethernet devices. It should be able to fulfill server, desktop and laptop bonding use cases.

Owner

Current status

  • Targeted release: Fedora 19
  • Last updated: 2012-11-21
  • Percentage of completion: 40%

Detailed description

The current bonding configuration in NetworkManager doesn't always work. The purpose of this Fedora feature is to implement reliable bonding configuration infrastructure in NetworkManager that would have the following features:

  • Reliable wired and wireless ethernet bonding
  • Configuration using keyfiles

Benefit to Fedora

Bonding is necessary for enterprise virtualization. There is also a common laptop usage for bonding wifi and ethernet together to present the laptop computer under a single MAC address to the local network and thus aquire just one MAC address regardless it is connected through cable and wifi.

Scope

This feature requires changes to NetworkManager, nm-applet, nm-connection-editor, gnome-shell, gnome-control-center and KDE counterparts.

How To Test

Configure a bonding interface and its slaves using GUI or CLI. Check using ip link or other tool. Test that the bonding actually works.

User Experience

GUI and CLI tools.

Dependencies

NetworkManager must only use bonding when configured so and it must only take over bond configuration if requested so by administrator or by another tool. Therefore libvirt and other tools that rely on bonding can be ported to the new functionality at any time.

Contingency Plan

Don't support bonding in NetworkManager. Tools that need bonding would have to continue to use the same tools as before.

Documentation

Documentation will be drafted at Networking/Bonding.

Release Notes

NetworkManager now supports ethernet bonding.

Comments and Discussion