Architectural Changes in NetworkManager
summary
A large redesign over about three quarters of a year refocuses NetworkManager on server and virtualization use cases: a new 0.9.10 branch introduces server.conf for server defaults, runtime connection profiles that merge kernel and on-disk state, and nmcli as a usable CLI. It adds generic device tracking, teaming and veth/bridge awareness, an option to refuse management (blacklist), user‑space router discovery so takeover works, DHCPv4/v6 and address lifetime handling (kernel support added), and experimental policy routing/multipath TCP; much is in git branches, not yet in a stable release.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:29Focusing on
- 2:36Purpose of network configuration service
- 5:21Why redesign?
- 10:04Device initialization and hotplugging
- 16:19Supported devices
- 19:42Runtime state information
- 21:53Configuration files
- 25:00External changes
- 29:53Dynamic configuration
- 30:17Configuration take over
- 31:17Address configuration information
- 35:09Route configuration information
- 36:59Policy routing
- 54:33Connection sharing
- 55:57DNS backends
- 57:39DNSSEC support
- 59:41Configuration, API and tools
related talks
18mLinux System Roles: Network Config with Nmstate
24mDeclare your Linux Network state!
18mPast, Present, and Future of Network Operations
22mWhat's new in systemd in 2016?
21mChange Management in Physical Network Lifecycle Automation
34mBuilding switches like servers: the strange world of overlapping networking
24mNetworking track kick-off
37mPodman 5 & Long-Term Software Maintenance