puppet, or rather, Ruby on FreeBSD has received an upgrade that forces me to upgrade my EOL 13.0 jails…

hrm, nope, seems to be puppet, not ruby

or, well, one of the Gems puppet loads

Polling if there is appetite in vox to create a module for networkmanager, aka the replacement for network-scripts in rhel/centos 8+ (I'm not overly familiar with other linux flavours to know where else it is used). The only module i see for it was last updated in 2016 and has a low stdlib requirement https://forge.puppet.com/modules/camptocamp/networkmanager. I did ask a contact at puppet if they would consider it but they may be consumed with the proposed uplift of their firewall module at present. AFAIK the vox network module https://forge.puppet.com/modules/puppet/network/ will be unusable on rhel/centos 8+ without support for networkmanager (I have actually found that the vox network module can be applied to centos 8 if network-scripts package is installed as a legacy feature, replacing networkmanager. However this workaround cannot/should not be done in v9 where networkmanager seems to be the only mechanism to define networking)

Polling if there is appetite in vox to create a module for networkmanager, aka the replacement for network-scripts in rhel/centos 8+ (I'm not overly familiar with other linux flavours to know where else it is used). The only module i see for it was last updated in 2016 and has a low stdlib requirement https://forge.puppet.com/modules/camptocamp/networkmanager. I did ask a contact at puppet if they would consider it but they may be consumed with the proposed uplift of their firewall module at present. AFAIK the vox network module will be unusable on rhel/centos 9 without support for networkmanager

Polling if there is appetite in vox to create a module for networkmanager, aka the replacement for network-scripts in rhel/centos 8+ (I'm not overly familiar with other linux flavours to know where else it is used). The only module i see for it was last updated in 2016 and has a low stdlib requirement https://forge.puppet.com/modules/camptocamp/networkmanager. I did ask a contact at puppet if they would consider it but they may be consumed with the proposed uplift of their firewall module at present. AFAIK the vox network module https://forge.puppet.com/modules/puppet/network/ will be unusable on rhel/centos 8+ without support for networkmanager

Polling if there is appetite in vox to create a module for networkmanager, aka the replacement for network-scripts in rhel/centos 8+ (I'm not overly familiar with other linux flavours to know where else it is used). The only module i see for it was last updated in 2016 and has a low stdlib requirement https://forge.puppet.com/modules/camptocamp/networkmanager. I did ask a contact at puppet if they would consider it but they may be consumed with the proposed uplift of their firewall module at present. AFAIK the vox network module https://forge.puppet.com/modules/puppet/network/ will be unusable on rhel/centos 8+ without support for networkmanager (I have actually found that the vox network module can be applied to centos 8 if network-scripts package is installed as a legacy feature, replacing networkmanager. However this workaround cannot/should not be done in v9 where networkmanager seems to be the only mechanism to define networking)

@canihavethisone personal opinion: I hope networkmanager dies. Its awful software that's awful to automate. systemd-networkd is way easier and available on every modern distribution. I use that at customers and on private servers since years without issues

and I won't invest time in a networkmanager module. I think instead we should push networkd

because of that I also consider out network module deprecated and don't put any work into it

@bastelfreak thanks, valid opinion there. However it appears that RHEL/CentOS 8+ don't support networkd https://bugzilla.redhat.com/show_bug.cgi?id=1650342#c1. Guess users of this stream are in a bind.

I think I am somehwere in that ticket :)

It is in EPEL for EL7-9

I've also been active on the "get networkd into RHEL" front.

nice!

I seem to remember bugs with the NetworkManager file formats. Honestly, I'd love to see it burned away by something not awful. DBus interfaces into the firewall are a security nightmare.

I’d expect systemd-firewalld to appear one day (with dbus interface) :)

I’d expect systemd-firewalld to appear one day (with dbus interface) :)

What need to be done to get my PR merged? https://github.com/voxpupuli/puppet-mongodb/pull/662 https://github.com/voxpupuli/puppet-mongodb/pull/661

What need to be done to get my PR merged? https://github.com/voxpupuli/puppet-mongodb/pull/662 https://github.com/voxpupuli/puppet-mongodb/pull/661

@bastelfreak thanks for that info, looks like networkd is indeed a better option to automate! So perhaps my revised question should be: Is there appetite in vox to create a module that manages systemd-networkd? I see that the systemd module can write files for it, however a somewhat expanded module with all available options defined in a template for multiple interfaces (from a hash) and ensuring that NetworkManager and network services are stopped and masked, plus any other perceived value adding? In the meantime I am looking at creating a single class to do this.

@bastelfreak thanks for that info, looks like networkd is indeed a better option to automate! So perhaps my revised question should be: Is there appetite in vox to create a module that manages systemd-networkd? I see that the systemd module can write files for it, however a somewhat expanded module with all available options defined in a template for multiple interfaces (from a hash) and ensuring that NetworkManager and network services are stopped and masked, plus any other perceived value adding? In the meantime I am looking at creating a single class to do this.

I considered this for our systemd module. But there are a lot of options and I think it requires a lot of work to keep the module up2date

but and option in the networkd class to stop/mask networkmanager would be a nice addition I think

FWIW, not using NM on RHEL-ish systems may cause applications that are built for RHEL to break. That's not necessarily a deal-breaker but something to keep in mind.

I'm fairly certain that we cover the NM capabilities decently in the simp-network module though. (That thing probably needs a rename at some point sigh)

See the

simp-network

module at https://forge.puppet.com/simp/network?src=slack&channel=voxpupuli

@canihavethisone I have some primitive NM support as profiles in my control repo that I am planning to break out as a module

It was sort of a 1day desperate move to get EL9 going

@bastelfreak merge the fact, he said. It'll be fine, he said. ;)