You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there is a better place for this type of question, let me know and I can close.
Netplan is an abstraction over NetworkManager / networkd. It uses YAML configuration files to specify supported backends and renders configs. It currently is released on Ubuntu 17.10 and will ship with Ubuntu 18.04 LTS.
Where does this module fit in that landscape? Would the advice be to disable management abstractions like Netplan and rely on the module? Or would expanding scope of this module to manage Netplan, itself (for Ubuntu systems) be a reasonable approach?
Mostly interested in discussion; no specific issue to report.
The text was updated successfully, but these errors were encountered:
Hi @mdwheele, thanks for bringing this up. I am not sure if this module is the right place for netplan, probably not. Maybe it needs its own module, which uses puppet-network as a dependency (depending on the type of backend)? For networkd support you maybe want to check out https://github.com/camptocamp/puppet-systemd.
Hi @mdwheele, thanks for bringing this up. I am not sure if this module is the right place for netplan, probably not.
It seems strange to me to have a module called 'network' that can't manage the default network configuration system of a major distribution.
Should this perhaps be renamed to 'ifupdown' instead?
Related: https://wiki.ubuntu.com/Netplan, https://wiki.ubuntu.com/MigratingToNetplan
If there is a better place for this type of question, let me know and I can close.
Netplan is an abstraction over
NetworkManager
/networkd
. It uses YAML configuration files to specify supported backends and renders configs. It currently is released on Ubuntu 17.10 and will ship with Ubuntu 18.04 LTS.Where does this module fit in that landscape? Would the advice be to disable management abstractions like Netplan and rely on the module? Or would expanding scope of this module to manage Netplan, itself (for Ubuntu systems) be a reasonable approach?
Mostly interested in discussion; no specific issue to report.
The text was updated successfully, but these errors were encountered: