3 ms·
> Can you explain to me why netplan is bad? I don't see the advantage over networkmanager, honestly. And now there's another thing I have to learn and support
by znpy 6y ago
> Can you explain to me why netplan is bad?
I don't see the advantage over networkmanager, honestly. And now there's another thing I have to learn and support, with no real benefit.
- Godel_unicode 6y agoI really think that netplan exists because "everyone knows" networkmanager is bad. Ironically, I think it's for the same reason that netplan is now bad; it's a leaky abstraction which doesn't always support the feature you want. I've worked with people who disable nm as a matter of muscle memory on new systems, and I wonder how long it'll be until netplan goes that route (hehe).
- orwin 6y agoWell, unless you used to do bridges with nmcli (and if you did, i'm really impressed), netplan do have some advantages. And for all the swearing i did when i add to change the packer conf, then the ansible conf, i do think netplan is in fact easier to understand, read and change than brctl/bridge-utils. I hate snaps though.
- znpy 6y agoUhm, so far I've used network manager for wired and wireless ethernet, vpns via openvpn and fortinet, and network bonding (lacp etc). Yeah you have to look the details for the specific kind of configuration, but reading the fine manual is the norm, not the exception.
- galgalesh 6y agoWould you use NetworkManager on a server?
- znpy 6y agoMost of the enterprise world does, it's the default in RHEL (in 7 for sure, it probably still is in rhel8). And regarding me personally: yes I would and I do. It's not that bad.