How is it better than using NetworkManager or systemd-networkd directly?
Why is it worth the extra complexity?
this post was submitted on 14 Nov 2023
51 points (100.0% liked)
Linux
48039 readers
779 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
It has a structured yaml with a test command for potentially destructive config changes over ssh. Other than that: none. It was a real pain upgrading some servers, as always with Ubuntu.
I just moved to Ubuntu from Fedora Silverblue, for some $reasons. I regret it already.
You know what can also test destructive changes?
Cockpit's networkmanager interface.
It literally has no benefits, and is only a pain to use.
Actually, it does have one benefit: it integrates with Canonical's other tech. For example, MAAS uses ot for networking, and I bet lxc uses it somehow.
I like yaml generally but netplan was a huge unnecessary pain in the ass.
The question is, is it going to suck more or less than NetworkManager?
It’s not replacing it.
I know, that wasn't the question I asked.
Can it suck more than NetworkManager? 🥹
It's not really worth it, honestly. All netplan does is generate a config for systemd-networkd. It's better to just configure systemd-networkd directly and have a portable configuration, rather than use Canonical's proprietary stuff. The documentation is quite good for systemd in general, and with more people using it directly for network config it's easier to find examples when you need help.
What is even the value of Netplan on... desktop? Most people just pick their WiFi in the menu in Gnome. That sounds like a lot of unnecessary complexity.
For servers, sure, it's fairly nice. But, desktop? Why?
24.04 LTS is a distribution intended primarily for servers, desktop is not the priority environment.
Netplan's been the default since 20.04 on the server side and the article says it's coming to the desktop release with 24.04.
For what it's worth I didn't even notice they changed it. Can't be the end of the world but I'd like to hear what network admins opinion's are.
If you're just using DHCP, you won't. What Netplan does is take a YAML input file and renders it as a systemd-networkd or NetworkManager configuration file. It's a very quick and easy way to configure your network, and even have a try command that auto reverts in case you get kicked out of your SSH session.
It seems like what they're doing for the desktop is hacking up NetworkManager so that it saves back its config as Netplan configs instead of regular NetworkManager configs. That's the part I'm confused about, because NetworkManager is huge and Netplan doesn't support close to every option. Their featuresets are wildly different. And last time I checked, the NetworkManager renderer was the least polished one, with the systemd-networkd one being close to a 1:1 match and more reliable.
It made a lot more sense when it was one way only. Two way sounds like an absolute mess.
I think it was actually the default on 18.04 LTS as well.
For Ubuntu 24.04 LTS, Canonical plans to polish the Netplan codebase and deliver a Netplan 1.0 release with API/ABI stability. They are also hoping other Linux distributions begin adopting Netplan. Debian so far has decided to go with Netplan for their nework stack on Debian Cloud images.
That’s probably the reason for pushing it to desktop builds.
Netplan makes more sense for the desktop then it does for a server because yaml is UI friendly. For the server it just adds an unnecessary level of complexity.
If you use a GUI configuration tool for NetworkManger like virtually every user I don't know how that works. Odds are not well.
This is the best summary I could come up with:
The Canonical-developed Netplan has served for Linux network configuration on Ubuntu Server and Cloud versions for years.
Canonical is committing to fully leveraging Netplan for network configuration with the upcoming Ubuntu 24.04 LTS release and in turn also marking the Netplan 1.0 release.
Netplan considers itself as a "network configuration abstraction renderer" that in turn interfaces with NetworkManager or systemd-networkd.
Netplan finally made its way to the Ubuntu 23.10 desktop by default with having better integration for knowing when connections are created/modified through NetworkManager.
Netplan can be used transparently to control a workstation’s network configuration and plays hand-in-hand with many desktop environments through its tight integration with NetworkManager.
It allows for easy network monitoring, using common graphical interfaces and provides a “single source of truth” to network administrators, allowing for configuration of Ubuntu Desktop fleets in a streamlined and declarative way.
The original article contains 227 words, the summary contains 141 words. Saved 38%. I'm a bot and I'm open source!
Ubuntu: If it wasn't created here, we want nothing to do with it.