On 04.09.24 13:28, Daniel Baumann wrote:
On 9/3/24 18:24, Lukas Märdian wrote:
The nice thing about Netplan is that it [...] functions as a
layer on top.
I don't understand what actual problem netplan is trying to solve.
On servers I want systemd-networkd directly anyway (for lacp, vlan and
bridges), and on end-user desktops I'm not modifying anything other than
selecting the WLAN.
Is netplan then only ment for "power-users" who don't want
systemd-networkd or need a everything-in-one-file oversimplification of
systemd-networkd?
I'd argue it's the exact opposite, actually.
Netplan is for the average user who googles about "how to configure network
on debian" and ends up with the "4 ways to configure the network" [4ways] or
even more options in the Debian Reference [debref]:
* The modern network configuration for desktop
* The modern network configuration without GUI
* The modern network configuration for cloud
* The low level network configuration
Now, what configuration does the average user chose, without necessarily
knowing the underlying stack? With Netplan we could slowly converge to a set
of instructions that work everywhere. While at the same time we could still
support/provide two modern upstream stacks (NetworkManager & systemd-networkd)
for everybody's liking.
OTOH, "power-users" (and I count most people on this mailinglist into that
group) know exactly what network stack comes with their chosen variant of
Debian and they know how to drive it.
-- Lukas
PS: Netplan isn't a everything-in-one-file thing. It parses a hierarchy
of configuration files and packages or installers could for example ship
drop-in config snippets in /usr/lib/neptlan/, as debian-installer [d-i] and
Calamares [live] are doing.
[4ways]
https://wiki.debian.org/NetworkConfiguration#A4_ways_to_configure_the_network
[debref] https://www.debian.org/doc/manuals/debian-reference/ch05.en.html
[d-i] https://salsa.debian.org/installer-team/netcfg/-/merge_requests/9
[live] https://github.com/calamares/calamares/pull/2284
