From Fedora Project Wiki
< Changes
No edit summary |
m (→Owner) |
||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 18: | Line 18: | ||
--> | --> | ||
= NetworkManager 1.2 | = NetworkManager 1.2 = | ||
== Summary == | == Summary == | ||
| Line 27: | Line 27: | ||
* Name: [[User:Lkundrak| Lubomir Rintel]] | * Name: [[User:Lkundrak| Lubomir Rintel]] | ||
* Email: lkundrak@v3.sk | * Email: lkundrak@v3.sk | ||
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->[mailto:sclark@fedoraproject.org Simon Clark] ([[User:sclark|sclark]]) | ||
== Current status == | == Current status == | ||
| Line 40: | Line 40: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1274026 #1274026] | ||
== Detailed Description == | == Detailed Description == | ||
| Line 56: | Line 56: | ||
* Support for managing container (LXC, Docker) connectivity | * Support for managing container (LXC, Docker) connectivity | ||
* RFC7217 stable privacy addressing | * RFC7217 stable privacy addressing | ||
* CLI improvements, colors, significantly better command completion | |||
TODO: Update once 1.2 is actually released. | TODO: Update once 1.2 is actually released. | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 177: | Line 178: | ||
We'll need to digest the upstream NEWS into the Fedora release notes. | We'll need to digest the upstream NEWS into the Fedora release notes. | ||
[[Category: | [[Category:ChangeAcceptedF24]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Latest revision as of 07:21, 23 April 2016
NetworkManager 1.2
Summary
Update to NetworkManager to version 1.2.
Owner
- Name: Lubomir Rintel
- Email: lkundrak@v3.sk
- Release notes owner: Simon Clark (sclark)
Current status
Detailed Description
NetworkManager 1.2 will include significant changes and improvements:
- Port to GDBus
- New libnma library for GUIs
- New VPN services plugin API
- Support for multiple VPN connections with a single plugin
- VPN plugins ported to libnm & libnma
- CLI secret agent with support for VPN secrets
- Capability of editing VPN connections via the TUI interface
- Support for arbitrary software device (bond, bridge, vlan, team) hierarchy
- Support for managing container (LXC, Docker) connectivity
- RFC7217 stable privacy addressing
- CLI improvements, colors, significantly better command completion
TODO: Update once 1.2 is actually released.
Benefit to Fedora
A major feature release, brings new features often requested by users.
Scope
- Proposal owners: Update NetworkManager, connection editor and VPN plugin packages.
- Other developers: We'll take care of porting the VPN property plugins; the VPN plugin package maintainers should pull in the patches or new upstream releases. The libnm-glib and libnm-gtk users (network management tools in various desktop environments should port their tools to libnm and libnma; but we're keeping the old libraries as well.
- Release engineering: N/A (not needed for this Change)
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
We're not removing any functionality and keeping the ABI in place (though we add new libraries). The upgrades should be seamless.
How To Test
The usual test cases for NetworkManager will do. It would be great to test these areas:
- IPv6-enabled and legacy-free networks (no IPv4)
- Wireless access points with various security mechanisms (WPA, WEP, ...)
- Multiple links to the same network, wireless & wired
- Server setups, bonding, teaming, bridging, vlans (possibly stacked)
- Other tools that namange networking installed for testing interoperability: libvirt, Docker, VMWare, VirtualBox, systemd-networkd, ...
- A Mobile broadband connectivity dongle
- Bluetooth DUN & PAN enabled dongle or a phone
- VPN servers, concentrators
- Different desktop environemnts installed, to test integration: GNOME, KDE, Xfce, ...
The detailed tes plans:
Wireless
VPN
Mobile connectivity
Advanced
User Experience
The users may notice new features available: better TUI & CLI tools, more flexible VPN support, possibility of more advanced network configurations.
Dependencies
These are packages directly affected by this change. They will be updated to new major versions:
- NetworkManager
- network-manager-applet
- nm-connection-editor
- NetworkManager-openvpn
- NetworkManager-openswan
- NetworkManager-openconnect
- NetworkManager-vpnc
- NetworkManager-pptp
- NetworkManager-l2tp
- NetworkManager-iodine
- NetworkManager-ssh
These packages rely on the legacy libnm-glib; some of them may start using the new libnm:
- anaconda-core
- dnssec-trigger
- firewall-applet
- firewall-config
- balsa
- cinnamon
- cinnamon-control-center
- control-center
- geoclue
- gnome-initial-setup
- gnome-settings-daemon
- gnome-shell
- krb5-auth-dialog
- nntpgrab-core
- strongswan-charon-nm
- telepathy-mission-control
- tracker
Contingency Plan
It would be possible to revert the change by downgrading the affected packages (see "Dependencies" above). All packages would need to be downgraded. However, as the new version is compatible with the previous versions we don't anticipate the need to do this.
- Contingency mechanism: Revert the packages
- Contingency deadline: Beta freeze
- Blocks release? Yes
Documentation
We'll write extensive release notes upstream.
Release Notes
We'll need to digest the upstream NEWS into the Fedora release notes.