- 1 NetworkManager 1.2
- 1.1 Summary
- 1.2 Owner
- 1.3 Current status
- 1.4 Detailed Description
- 1.5 Benefit to Fedora
- 1.6 Scope
- 1.7 Upgrade/compatibility impact
- 1.8 How To Test
- 1.9 User Experience
- 1.10 Dependencies
- 1.11 Contingency Plan
- 1.12 Documentation
- 1.13 Release Notes
Update to NetworkManager to version 1.2.
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.
- 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)
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:
The users may notice new features available: better TUI & CLI tools, more flexible VPN support, possibility of more advanced network configurations.
These are packages directly affected by this change. They will be updated to new major versions:
These packages rely on the legacy libnm-glib; some of them may start using the new libnm:
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
We'll write extensive release notes upstream.
We'll need to digest the upstream NEWS into the Fedora release notes.