< Features
(→Owner) |
|||
| (13 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
= NetworkManager Bridging Support = | |||
= | == Summary == | ||
NetworkManager should be able to configure bridge interfaces with commonly used options and recognize their existing configuration on startup without disrupting their operation. | |||
NetworkManager should | |||
== Owner == | == Owner == | ||
* Name: [[User:dcbw| Dan Williams]] | * Name: [[User:dcbw| Dan Williams]] | ||
* Email: dcbw | * Email: dcbw at redhat dot com | ||
* Name: [[User:Pavlix|Pavel Šimerda]] | * Name: [[User:Pavlix|Pavel Šimerda]] | ||
* Email: psimerda at | * Email: psimerda at redhat dot com | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/ | |||
* Last updated: | * Targeted release: [[Releases/19|Fedora 19]] | ||
* Percentage of completion: | * Last updated: 2013-03-12 | ||
* Percentage of completion: 50% | |||
== Detailed Description == | == Detailed Description == | ||
Bridging is | A bridge connects two or more physical or virtual network interfaces to allow network traffic to flow between the two interfaces at a low level. Bridging is commonly used to connect Virtual Machines to the outside world; a bridge interface is created, to which a physical interface (typically ethernet) is assigned as a slave, and a virtual interface (typically TAP) is created and also assigned to the bridge as a slave, and then given to the Virtual Machine. Thus traffic from one or more VMs can be combined and sent out of the machine via the physical interface. | ||
This setup is currently done either manually using ifcfg files and ifup/ifdown, or by a tool like libvirt/netcf. NetworkManager should be able to configure bridge interfaces and their slaves with the same functionality as provided by libvirt, and should recognize and not disrupt existing bridge connections when it starts up. | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
NetworkManager | |||
NetworkManager will provide a unified API for network configuration, giving a more consistent user experience. Users setting up bridged connections who also run NetworkManager will not need to take additional action to determine whether the bridge should be controlled by libvirt or by NetworkManager as the two will cooperate. | |||
== Scope == | == Scope == | ||
This feature requires changes to | |||
This feature requires changes to nm-applet, nm-connection-editor, gnome-shell, gnome-control-center and KDE counterparts to expose bridge interfaces and their connection information in the user interface. NetworkManager also needs updates to implement the proposed changes. | |||
== How To Test == | == How To Test == | ||
Ensure that a bridge interface created by libvirt/netcf or the system initscripts is recognized by NetworkManager but not touched by it until either 'nmcli' or the network applet is used to change connections or deactivate bridge port interfaces. | |||
== User Experience == | == User Experience == | ||
Both the UI tools (applets, connection editors, etc) and the CLI tools (nmcli) will be updated for the bridging configuration options. Users will see bridge interfaces in network indicators and be able to inspect their status through the applets or the command-line tools. | |||
== Dependencies == | == Dependencies == | ||
libvirt | |||
The changes should be limited to NetworkManager and it's associated tools, and should not require changes to libvirt, netcf, initscripts, or other external tools. NetworkManager should be able to cooperate with the configurations set up by these tools. | |||
== Contingency Plan == | == Contingency Plan == | ||
Ensure NetworkManager only controls bridge interfaces it is told to control via NM_CONTROLLED in ifcfg files. Tools that need bridging would have to continue to use the same tools as before. | |||
== Documentation == | == Documentation == | ||
Documentation will be drafted at [[Networking/Bridging]]. | |||
== Release Notes == | == Release Notes == | ||
NetworkManager now supports bridging functionality and cooperates better with existing bridging tools and configurations. | |||
== Comments and Discussion == | == Comments and Discussion == | ||
* See [[Talk:Features/NetworkManagerBridging]] | |||
[[Category:FeatureAcceptedF19]] | |||
Revision as of 22:31, 12 March 2013
NetworkManager Bridging Support
Summary
NetworkManager should be able to configure bridge interfaces with commonly used options and recognize their existing configuration on startup without disrupting their operation.
Owner
- Name: Dan Williams
- Email: dcbw at redhat dot com
- Name: Pavel Šimerda
- Email: psimerda at redhat dot com
Current status
- Targeted release: Fedora 19
- Last updated: 2013-03-12
- Percentage of completion: 50%
Detailed Description
A bridge connects two or more physical or virtual network interfaces to allow network traffic to flow between the two interfaces at a low level. Bridging is commonly used to connect Virtual Machines to the outside world; a bridge interface is created, to which a physical interface (typically ethernet) is assigned as a slave, and a virtual interface (typically TAP) is created and also assigned to the bridge as a slave, and then given to the Virtual Machine. Thus traffic from one or more VMs can be combined and sent out of the machine via the physical interface.
This setup is currently done either manually using ifcfg files and ifup/ifdown, or by a tool like libvirt/netcf. NetworkManager should be able to configure bridge interfaces and their slaves with the same functionality as provided by libvirt, and should recognize and not disrupt existing bridge connections when it starts up.
Benefit to Fedora
NetworkManager will provide a unified API for network configuration, giving a more consistent user experience. Users setting up bridged connections who also run NetworkManager will not need to take additional action to determine whether the bridge should be controlled by libvirt or by NetworkManager as the two will cooperate.
Scope
This feature requires changes to nm-applet, nm-connection-editor, gnome-shell, gnome-control-center and KDE counterparts to expose bridge interfaces and their connection information in the user interface. NetworkManager also needs updates to implement the proposed changes.
How To Test
Ensure that a bridge interface created by libvirt/netcf or the system initscripts is recognized by NetworkManager but not touched by it until either 'nmcli' or the network applet is used to change connections or deactivate bridge port interfaces.
User Experience
Both the UI tools (applets, connection editors, etc) and the CLI tools (nmcli) will be updated for the bridging configuration options. Users will see bridge interfaces in network indicators and be able to inspect their status through the applets or the command-line tools.
Dependencies
The changes should be limited to NetworkManager and it's associated tools, and should not require changes to libvirt, netcf, initscripts, or other external tools. NetworkManager should be able to cooperate with the configurations set up by these tools.
Contingency Plan
Ensure NetworkManager only controls bridge interfaces it is told to control via NM_CONTROLLED in ifcfg files. Tools that need bridging would have to continue to use the same tools as before.
Documentation
Documentation will be drafted at Networking/Bridging.
Release Notes
NetworkManager now supports bridging functionality and cooperates better with existing bridging tools and configurations.