Puppet Community

Completely agree. The puppet community is over-focused on unit testing because acceptance testing in public/free CI was painful for a very long time. There are instances where a unit test is needed, for example to check ordering, but as a community we should be doing less unit and more acceptance testing.

Yeah, but smortex is right in thinking that this should be unit-tested. He even gave me a stub, but that only worked with modifications up until the point I wanted to change the initial parameters. :wink:

The thing is that the overlay spec doesn't test `described_class`, just the provider instance it made itself, not sure if that's the right approach

if you ask ewoud nicely, he might take a look 

Well, I've just arrived in the advanced rubber duck programming stage aka whining about it in chat and maybe noticing something in the process

<https://github.com/voxpupuli/puppet-jenkins/pull/1050>

Are you using systemd::network to configure entire files?

the unit vs acceptance test is always a hard one to balance

unit tests can be much faster, but you always have to question what you're really testing

for example, if you want to verify a template renders correctly given a certain input, unit testing is typically good enough and much faster

but it doesn't guarantee that a service would actually behave the way it should

<@U01AZE7JFPE> I just came across <https://bugzilla.redhat.com/show_bug.cgi?id=2020254> . What did you end up doing?

I've ended up with NetworkManager for now, but I'm planning to make the switch to systemd-networkd "at some point"

I just discovered that there are ifup/down scripts in an NM package which isn't installed by default for some reason, that will help.

but in general, NM causes me grief.  I have a rhel7 box that the physical interfaces occasionally flap on and NM gets out of sync with reality. Right now at this very moment there is a vlan interface which is up and passing traffic and NM insists that it is down.

if you're able to jump directly to systemd-networkd, I'd go with it

Do you have a link? I'm at least an order of magnitude if not two away from being a hyperscaler

Is this what you were thinking of? Repo is archived. <https://github.com/facebookarchive/rpm-backports/tree/main/rpms/systemd|https://github.com/facebookarchive/rpm-backports/tree/main/rpms/systemd>

<https://pagure.io/centos-sig-hyperscale/systemd> is the current source location, the repo itself is at <http://mirror.stream.centos.org/SIGs/9-stream/hyperscale/x86_64/packages-main/>

I turned this up but haven't tried it. <https://github.com/redhat-plumbers|https://github.com/redhat-plumbers>

I think i'm probably going to try to kick `example42/network` into working on EL8 for the short term

See the `example42-network` module at <https://forge.puppet.com/example42/network?src=slack&amp;channel=voxpupuli>

`puppet/network` as is needs changes or wrapper class to restart interfaces when there is a change

See the `puppet-network` module at <https://forge.puppet.com/puppet/network?src=slack&amp;channel=voxpupuli>

ideally puppet-network needs a rework to front-end `nmcli`.  i'd work on that, but i don't know `nmcli` well enough (yet).  :upside_down_face:

googling a bit yeseterday, I was thinking trying to build a type around <https://puppetcommunity.slack.com/archives/C0W1Y5VL0/p1661996744958949> might be the least effort way to build a provider

pip installing things on the system is usually asking for breakage down the road... so maybe build a mod to install `jc` in a dedicated env

please dont work on the dead example42 module, we archived it for a reason :)

if you want to contribute something, I highly recommend the puppet/network module

I contributed to `puppet/network` long before it was donated to voxpupuli. I am very familiar with it.

I'm not enthastic about redoing all of the network setup in my control repo... not because it is hard but because of the testing required

<@U1QVBAUS2> We are going to work on puppet-network module to add support for several missing os. This will be paid work and we are happy to share work (and payments) with the community. I am going to announce the work offer in jobs channel once we have received the order (this should happen within a couple of days)

<@U5V9MMW9E> <@U1PC2RAH0> ^^ we will receive a work order from a customer to add os support and functionality to puppet-network module. Paid work! Please let me know if you are interested or if you are aware of anyone who is able to support.

<@U11QGB2PN>... not sure why you pinged me :slightly_smiling_face: ?

Ah... I thought you were confusing that module with my network_config module....  *need more coffee*

i'm doing exactly that on el9.  it's not the greatest answer, but it definitely works.

I contributed to `puppet/network` long before it was donated to voxpupuli. I am very familar with it.

Haven’t looked at why tests on main started failing recently, but would like to help this along if I can.

a good question. I did say getting <https://github.com/voxpupuli/puppet-jenkins/pull/1045/files> green should be the next step. that will more the whole CI more robust and easier to add newer OSes

so if you can take a look at that PR, that would be awesome

You probably want the <#C0W298S9G|puppet> channel, and it is best to just ask the question.

this is a bit unspecific. you just want to have *a* PKI? Puppetserver has one built in

Not just pki but a complete Pki server which should be installed automatically after creating a puppet module in puppetserver.

what's the overall goal you're trying to achive?

we basically have a pki server which was set up manually few years back but not added in puppetserver. So I need to have all the things required to call this a pki server in puppetserver which can create us a new pki server but automatically this time.

so identify which software you use and check if there are already modules for this software on the internet

That is what I want to understand what needs to be done. So far I have some scripts which can create, renew, revoke certificates,etc . I added these to the puppetserver and connected with a test node .

I still don't quite understand if you installed a PKI or if you use the built-in PKI in puppetserver

provide more information :slightly_smiling_face: Share the scripts, explain what they do, when/how you use it

I haven't installed or used built in PKI......Just wanted to share information that I have some scripts from the already running pki server which are basically used to create or revoke certificate

So the question is how do i create a puppet module and what should be used so that it proves that this would be a pki server

puppet has a lot of beginner tutorial available for getting started, understanding the language and writing modules

But I did say as a first step you should understand how your setup actually works, which pieces you want to automate and what should be replaced

someone told me to use this and add all the mod in a puppetfile and use r10k to install it.  <https://forge.puppet.com/modules/simp/pki>

write down how your current system works, then write down what you want to have/what should change

The only thing i can say is I dont know anything about PKI. If you can guide me what needs to be checked on the already installed pki server then i can share the info to understand better

check the scripts you have, understand what they do, identify which scripts are used/required

I told you already these scripts helps to create renew revoke the user or web certificates

yes. but it sounds like you don't understand them at the moment, otherwise you wouldn't say you don't understand PKI

and before you try to automate anything, you need to understand the software and your requirements

yeah ur right, that is why i asked for help. I dont have any documentation atm which can say what is needed for a pki server

it's not about the requirements for *a* pki server

it's about the requirements for your environment

do multiple people use the scripts? just a single person? are they used by APIs/scripts? are all scripts still required? Should they be replaced by another software like hashicorp vault or do you want to keep it, do you want to switch to the puppetserver PKI

we need just a basic pki server setup as I already have the scripts and i will add them to the manifests

you can't just install *a* PKI and expect your scripts to work

We are 3 people who will use these scripts. Yes we need all the scripts which i listed and not to be replaced by any software as we have 2 another server where one is for vpn, client and other is for softwares

I think this Pki server are using only service CA online while the root and SubCA are offline and used using flash drive

Hello, I am looking for a puppet module for pki server. This should automatically install a pki server on agent node after the module is created in Puppet master. If you have any documentation where it provide details step by step would help better.

<https://github.com/voxpupuli/voxpupuli.github.io/pull/268> I updated our styleguide to clarify the usage of puppet/systemd. I think we agreed on that ages ago, but never wrote it down