Discussion:
Puppet and OpenBSD. Any examples/experience for unattended provisioning?
Kirill Peskov
2015-06-21 13:00:14 UTC
Permalink
Hi All,

Looks like there is no comprehensive guide/howto in the Net for $subj...
Googling gives some discussions and presentations regarding running
puppet server on OpenBSD, which is not so interesting. My task is to
automate provisioning of bunch of OpenBSD servers across several LANs
and puppet would be a good helper here (OK, maybe Saltstack could be an
alternative solution, but there is even less info about such a
combination out there).

Thanx in advance,
Kirill
Alexander Salmin
2015-06-21 20:21:28 UTC
Permalink
Are you looking into running a puppet server or puppet client on
OpenBSD? For the server, the requirements are many, and even if it's
possible, it can be a bit hard to get everything right. As for the
puppet client, it works as intended.

Unless you are aiming for bare-metal (with foreman or something similar)
and if you are open to suggestions I'd say try ansible. I'm using it on
some 30+ OpenBSD servers which works great. It's really easy to learn.
Both package managment and sysctl configuration is of high quality as
well as templates with jinja2-syntax.

But as always, use what works best for you. Maybe if you explain more
about what parts of the OpenBSD system you want to automate the list can
help you with some suitable automation options.

Alexander Salmin
Post by Kirill Peskov
Hi All,
Looks like there is no comprehensive guide/howto in the Net for $subj...
Googling gives some discussions and presentations regarding running
puppet server on OpenBSD, which is not so interesting. My task is to
automate provisioning of bunch of OpenBSD servers across several LANs
and puppet would be a good helper here (OK, maybe Saltstack could be an
alternative solution, but there is even less info about such a
combination out there).
Thanx in advance,
Kirill
nusenu
2015-06-22 08:07:43 UTC
Permalink
Post by Alexander Salmin
Unless you are aiming for bare-metal (with foreman or something
similar) and if you are open to suggestions I'd say try ansible.
+1 although ansible is probably for servers that have already been
deployed and ready to be configured with services.
Post by Alexander Salmin
Both package managment and sysctl configuration is of high quality
You are really using ansible's sysctl module on OpenBSD servers?
It isn't supported yet:
https://github.com/ansible/ansible-modules-core/issues/1233
I'm missing a ansible ports module for OpenBSD.
Raf Czlonka
2015-06-22 09:20:49 UTC
Permalink
Post by Alexander Salmin
Are you looking into running a puppet server or puppet client on
OpenBSD? For the server, the requirements are many, and even if it's
possible, it can be a bit hard to get everything right. As for the
puppet client, it works as intended.
I'm running puppetmaster on OpenBSD just fine - pleas don't spread
misinformation :^)

Raf
Sebastian Reitenbach
2015-06-22 10:11:23 UTC
Permalink
Post by Kirill Peskov
Hi All,
Looks like there is no comprehensive guide/howto in the Net for $subj...
Googling gives some discussions and presentations regarding running
puppet server on OpenBSD, which is not so interesting. My task is to
automate provisioning of bunch of OpenBSD servers across several LANs
and puppet would be a good helper here (OK, maybe Saltstack could be an
alternative solution, but there is even less info about such a
combination out there).
I'm running Puppetmaster behind nginx, with puppetdb and puppetboard on
OpenBSD.
I combined initial provisioning with autoinstall(8) that takes care of
initially installing puppet
via site.script and then firing it up. The puppetmaster configures
itself with a bunch of
puppet appy commands in standalone, all my other boxen just run puppet
agent --test
and connect to the puppetmaster for further bootstrapping.
For Puppet module management, r10k is used.

I have a bunch of puppet modules for OpenBSD here:
https://github.com/buzzdeee

In short: puppet works like a charm for me.

Note: I run -current on all of my gear, and that has some fixes for the
service and package providers, that
unfortunately didn't made it into 5.7.


cheers,
Sebastian
Post by Kirill Peskov
Thanx in advance,
Kirill
Loading...