< Features
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== NetworkManager Bridging Support == | |||
= | === Summary === | ||
NetworkManager should be able to configure bridging interfaces consisting of | |||
NetworkManager should | wired and wireless ethernet devices. It should be able to fulfill server | ||
and virtualization bridging usecases. | |||
=== Owner === | |||
* Name: [[User:dcbw| Dan Williams]] | * Name: [[User:dcbw| Dan Williams]] | ||
* Email: dcbw@redhat.com | * Email: dcbw@redhat.com | ||
* Name: [[User:Pavlix|Pavel Šimerda]] | |||
* Email: psimerda at readhat dot com | |||
=== Current status === | |||
* Targeted release: [[Releases/19|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 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 22: | 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 | |||
This feature requires changes to NetworkManager, nm-applet, nm-connection-editor, | |||
gnome-shell, gnome-control-center and KDE counterparts. | |||
=== How To Test === | |||
TBD | TBD | ||
== User Experience == | === User Experience === | ||
TBD | TBD | ||
== Dependencies == | === Dependencies === | ||
libvirt may need to be adapted. | |||
libvirt may need to be adapted. See also [[Features/Shared_Network_Interface]]. | |||
=== 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 | TBD | ||
== Release Notes == | === Release Notes === | ||
TBD | TBD | ||
== Comments and Discussion == | === Comments and Discussion === | ||
* See [[Talk:Features/ | |||
* See [[Talk:Features/NetworkManagerBridging]] | |||
Revision as of 23:45, 20 November 2012
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
- Name: Dan Williams
- Email: dcbw@redhat.com
- Name: Pavel Šimerda
- Email: psimerda at readhat dot com
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
TBD
User Experience
TBD
Dependencies
libvirt may need to be adapted. See also Features/Shared_Network_Interface.
Contingency Plan
Don't support bridging in NetworkManager, virtualization will continue to rely on libvirt for this purpose.
Documentation
TBD
Release Notes
TBD
Comments and Discussion