We at Inuits are using vagrant for a lot of use cases, neither you are a developer or a sysadmin you for sure will walk into it. Me, myself I do use it merely to automate the many different use cases asked by various projects. It took some time to get myself organized with this pretty nifty piece of software.

In the beginning I used it with the default virtualization provider virtualbox later on I switched to lxc containers instead. By using those containers I already gained on performance. Spinning up and down new containers to test if an application …

I do use puppet as our main configuration management tool. Together with puppetdb all our services are automatically configured from bottom to top.

And it rocks, getting automated as much as possible it is like easy as hell to get a server up and running. The only feature it lacked in my opinion is orchestration. I do know about collective which is made for this purpose.

Only it's yet again using an agent which fails from time to time and eating resources which can be avoided. It's the same reason I don't use the puppet agent daemon but trigger puppet …

I finally got to the point where I upgraded a whole puppet infrastructure from puppet 2.6.x to the last stable version of puppet, 3.3.0. And after finding out the way to go it was surprisingly easy and no big issues came across.

One of the main reasons to upgrade was to start using the latest version of foreman, were we used 0.4, so we can start provisioning our own development vm's with some fancy cloud solution like for example cloudstack using our production puppet tree.

Before the upgrade we had the puppet-client & server (2.6 …

I started the day with ssl issues using puppet. Last week I cleaned 2 hosts in our tree using the puppet command

# puppet node clean [hostname]

on the puppetmaster. I did this to clean out the stored configs for those nodes.

But I didn't realized this also cleaned out the ssl certificates for those clients. So I started the new week with this uncomfortable issue:

[root@agent ~]# puppet agent --test err: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked warning: Not using cache on failed …

Mumble is an open source, low-latency, high quality voice chat software primarily intended for use while gaming.

Puppet is a tool designed to manage the configuration of Unix-like and Microsoft Windows systems decoratively.

The puppet-mumble module installs a mumble server (version 1.2.3) automatically on a CentOS 6.x machine using the puppet software based on mumble-documentation.

The module needs a repository which contains the mumble-server package. I distribute this package on my own visibilityspots repository.

Using puppet this will create the necessary mumble user and group and will configure the mumble-server using your desired settings, like username, password …