Features/NetworkManagerBridging

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Current status)
Line 1: Line 1:
 
== NetworkManager Bridging Support ==
 
== NetworkManager Bridging Support ==
  
=== Summary ===
+
== Summary ==
  
 
NetworkManager should be able to configure bridging interfaces consisting of
 
NetworkManager should be able to configure bridging interfaces consisting of
Line 7: Line 7:
 
and virtualization bridging usecases.
 
and virtualization bridging usecases.
  
=== Owner ===
+
== Owner ==
  
 
* Name: [[User:dcbw| Dan Williams]]
 
* Name: [[User:dcbw| Dan Williams]]
Line 14: Line 14:
 
* Email: psimerda at readhat dot com
 
* Email: psimerda at readhat dot com
  
=== Current status ===
+
== Current status ==
  
 
* Targeted release: [[Releases/19|Fedora 19]]  
 
* Targeted release: [[Releases/19|Fedora 19]]  
Line 20: Line 20:
 
* Percentage of completion: 40%
 
* Percentage of completion: 40%
  
=== Detailed Description ===
+
== Detailed Description ==
  
 
Bridging is about connecting 2 or more network devices to make network traffic automatically go from the one to the other. The network devices can be physical or virtual.
 
Bridging is about connecting 2 or more network devices to make network traffic automatically go from the one to the other. The network devices can be physical or virtual.
Line 28: Line 28:
 
Bonding is about glueing two network connections together and treat them as a single connection with bigger bandwidth. This happens at the ethernet level and thus only works if the two connections are to the same network. Bonding has uses mainly on servers, and is more of a byproduct in this feature, since the infrastructure for bridging will likely also support bonding.
 
Bonding is about glueing two network connections together and treat them as a single connection with bigger bandwidth. This happens at the ethernet level and thus only works if the two connections are to the same network. Bonding has uses mainly on servers, and is more of a byproduct in this feature, since the infrastructure for bridging will likely also support bonding.
  
=== Benefit to Fedora ===
+
== Benefit to Fedora ==
  
 
NetworkManager becomes a more central point for network configuration, giving a more unified user experience. Virtualization on Fedora will be easier to set up.
 
NetworkManager becomes a more central point for network configuration, giving a more unified user experience. Virtualization on Fedora will be easier to set up.
  
=== Scope ===
+
== Scope ==
  
 
This feature requires changes to NetworkManager, nm-applet, nm-connection-editor,
 
This feature requires changes to NetworkManager, nm-applet, nm-connection-editor,
 
gnome-shell, gnome-control-center and KDE counterparts.
 
gnome-shell, gnome-control-center and KDE counterparts.
  
=== How To Test ===
+
== How To Test ==
  
TBD
+
Configure a bridging interface and its slaves using GUI or CLI. Check using <code>ip link</code>, <code>brctl</code> or other tool. Test that the bridging actually works.
  
=== User Experience ===
+
== User Experience ==
  
TBD
+
GUI and CLI tools.
  
=== Dependencies ===
+
== Dependencies ==
  
libvirt may need to be adapted. See also [[Features/Shared_Network_Interface]].
+
NetworkManager must only use bridging when configured so and it must only take over bridge configuration if requested so by administrator or by another tool. Therefore libvirt and other tools that rely on bridging can be ported to the new functionality at any time.
  
=== Contingency Plan ===
+
== Contingency Plan ==
  
 
Don't support bridging in NetworkManager, virtualization will continue to rely on libvirt for this purpose.
 
Don't support bridging in NetworkManager, virtualization will continue to rely on libvirt for this purpose.
  
=== Documentation ===
+
== Documentation ==
  
TBD
+
Documentation will be drafted at [[Networking/Bridging]].
  
=== Release Notes ===
+
== Release Notes ==
  
TBD
+
NetworkManager now supports ethernet bridging.
  
=== Comments and Discussion ===
+
== Comments and Discussion ==
  
 
* See [[Talk:Features/NetworkManagerBridging]]
 
* See [[Talk:Features/NetworkManagerBridging]]
 
  
 
[[Category:FeaturePageIncomplete]]
 
[[Category:FeaturePageIncomplete]]
<!-- When your feature page is completed and ready for review -->
 
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
 
 
 
<!-- Note that the current Feature guidelines require useful Scope and Test Plans at certain milestones; QA is responsible for checking these, and will change this category as needed. -->
 

Revision as of 11:17, 8 January 2013

Contents

NetworkManager Bridging Support

Summary

NetworkManager should be able to configure bridging interfaces consisting of wired and wireless ethernet devices. It should be able to fulfill server and virtualization bridging usecases.

Owner

Current status

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

Detailed Description

Bridging is about connecting 2 or more network devices to make network traffic automatically go from the one to the other. The network devices can be physical or virtual.

Bridging is a commonly used technology to connect VMs to the outside world: create a tap device on the host, create a bridge between the physical nic and the tap, let the vm use the tap device as its nic. So far, this setup is handled by libvirt. This is the main driving use case for this feature.

Bonding is about glueing two network connections together and treat them as a single connection with bigger bandwidth. This happens at the ethernet level and thus only works if the two connections are to the same network. Bonding has uses mainly on servers, and is more of a byproduct in this feature, since the infrastructure for bridging will likely also support bonding.

Benefit to Fedora

NetworkManager becomes a more central point for network configuration, giving a more unified user experience. Virtualization on Fedora will be easier to set up.

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 bridging interface and its slaves using GUI or CLI. Check using ip link, brctl or other tool. Test that the bridging actually works.

User Experience

GUI and CLI tools.

Dependencies

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

Contingency Plan

Don't support bridging in NetworkManager, virtualization will continue to rely on libvirt for this purpose.

Documentation

Documentation will be drafted at Networking/Bridging.

Release Notes

NetworkManager now supports ethernet bridging.

Comments and Discussion