>>>>> "Lukas" == Lukas Märdian <l...@slyon.de> writes:
Lukas> Therefore, I'd love to see Netplan to be used in combination
Lukas> with this! It's a clean, declarative configuration language
Lukas> not specifically tied to systemd-networkd as an
Lukas> implementation. So it could also be used on desktop installs
Lukas> where NetworkManager is important, for example to handle
Lukas> roaming between varying WiFi networks. It would also allow
Lukas> for d-i to install a single, common default network
Lukas> configuration, independently of the underlying daemon.
I currently use netplan.io when I need to interact with cloud-init and
network configs.
I think netplan is a great tool when
1) You need to interact with cloud-init
or
2) When a human is generating systemd-networkd config or NetworkManager
config.
systemd-network splits its config across multiple files in a way that's
really nice when you have some provisioning system generating it, but
isn't so nice when you are wanting to look at the config all in one
place as a human.
NetworkManager's config is a bit fiddly to generate by hand, much less
so than netplan.io.
However, there are some significant disadvantages to netplan:
1) It's an extra layer. You can ignore it when reading the config (at
least if you aren't too surprised by your config ending up in /run).
But it is extra complexity, especially in a situation like " run dhcp on
my ethernet" that is relatively simple.
2) It's a layer that you cannot ignore when editing the config. Netplan
is one way. It takes in config in its format and spews out either
NetworkManager config or systemd-networkd config. You can generate
extra config on top of what netplan does, but in my experience if you
want to edit the config that netplan controls, you need to either do it
through netplan or remove netplan and generate those config chunks by
hand (possibly after looking at how netplan did it).
It's possible there are some netplan modes I missed and some other ways
of doing things. It's also possible netplan has evolved since I looked
at it.
In the non-wifi case I think d-i's networking is too simple to justify
netplan.
A simple .network unit for systemd-networkd sounds like a better option.
In the wifi case though, I agree that netplan is a good idea.
It doesn't look like systemd-networkd supports setting up the
authentication for a wireless network. So, you'd need to be using
wpa_supplicant directly and systemd-networkd. I think using
NetworkManager is going to provide a better user experience than
directly configuring wpa_supplicant, and I think netplan has significant
added value for automatic configuration of NetworkManager.
signature.asc
Description: PGP signature
