RedHat is telegraphing that hostnamectl might be the future: https://www.redhat.com/sysadmin/change-hostname-linux

Zhenech: for a new release we should first finish https://github.com/voxpupuli/beaker-hostgenerator/pull/275

bastelfreak, welp, finish it! </mortal combat voice>

hostnamectl is IMHO to set the system's hostname while hostname is there to get the hostname

and that article does the same thing

If you do

hostnamectl status

you get a structured return that gives you the static hostname

and

hostnamectl --static

gives you the FQDN

can I get a review for https://github.com/voxpupuli/puppet-erlang/pull/19

grafana bricked their testing/beta repos, can we still move https://github.com/voxpupuli/puppet-grafana/pull/310 (and the two linked PRs)?

can I get a review for https://github.com/voxpupuli/puppet-varnish/pull/13 plz

can I get a review for https://github.com/voxpupuli/puppet-varnish/pull/13 plz

done

Thank you

our new puppets arrived \o/

https://forge.puppet.com/modules/puppet/sslcertificate/dependencies has puppetlabs/stdlib (>= 4.13.1 < 7.0.0). Please help to upgrade to 'puppetlabs-stdlib', '8.5.0'

it probably works fine with stdlib 8.5, just nobody raised the upper limit yet

https://github.com/voxpupuli/puppet-sslcertificate/blob/master/metadata.json#L25 looks like we did, just didn't release it yet

https://github.com/voxpupuli/puppet-sslcertificate/blob/master/metadata.json#L25 looks like we did, just didn't release it yet

getting this warning: 'puppet-sslcertificate' (v4.1.0) requires 'puppetlabs-stdlib' (>= 4.13.1 < 7.0.0). It will be nice to have a new release to raise the limit. I don't like to get warning in puppet module list --tree

See the

puppet-sslcertificate

module at https://forge.puppet.com/puppet/sslcertificate?src=slack&amp;channel=voxpupuli

Hey guys, does anyone know whats the current state of augeasproviders_sysctl? Is it currently compatible with augeasproviders_core? (https://github.com/voxpupuli/puppet-augeasproviders_sysctl)

Hey guys, does anyone know whats the current state of augeasproviders_sysctl? Is it currently compatible with augeasproviders_core? (https://github.com/voxpupuli/puppet-augeasproviders_sysctl)

and the github is on vox but the forge still on herculesteam, but the core provider is both on vox (forge and github). thonk confusing

My current understanding, after a digging a bit into this rabbit hole, is that core and its addons (sysctl, syslog, nagios, etc) were close to being abandoned and voxpopuli adopted them a bit over half a year ago. Core was updated and re-released (while deprecating the herculesteam version) but the addons are still a WIP. Currently, I think the addons are not compatible with core (at the very least sysctl seems to be failing to install alongside core for us). But just wanted to check whether this assumption is correct, and ask whether there is an estimate on sysctl being released.

no, core and sysctl work together, just teste/used it a minute ago together 😄

just a mom, i go look which versions i took

i took those together for some net.bridge and net.ipv* rules

mod 'herculesteam-augeasproviders_sysctl',  '2.6.2' # k8s dependency
mod 'puppet-augeasproviders_core',          '3.2.0' # k8s dependency

See the

herculesteam-augeasproviders_sysctl

module at https://forge.puppet.com/herculesteam/augeasproviders_sysctl?src=slack&amp;channel=voxpupuli

on ubuntu 20.04/22.04