On Fri, 7 Feb 2020 02:32:12 -0800 (PST) matzuba <[email protected]> wrote:
> [...]
> NM seems to be the recommended way and where things are going so i would
> like to get this to work but obviously, i cant use the nmcli module to do
> so.
> NM will still read the interface scripts and i have also tested
> /etc/networkmanager/conf.d configuration.
> [...]
Let me share couple of thoughts that might help you to make your choice.
The problem is the complexity. Both vertical and horizontal. Horizontal
across the distributions and vertical across the layers "User_land <-> D-Bus
<-> System_configuration <-> Device_drivers". A nightmare for any maintainer.
With Ansible, you connect to the remote host and escalate to root. Then you
use nmcli, which is user-land tool, and go through D-Bus to configure the
system. It's an overkill.
It's not a core module. The nmcli module is maintained by community and is in
preview.
HTH,
-vlado
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/20200207133410.1739b630%40gmail.com.
pgpOk3BChSD_i.pgp
Description: OpenPGP digital signature
