Foreman Blog

This is the first edition of what I hope will continue as a monthly overview of events in and around the Foreman project, news from our plugin community and must-read articles or tips.  Comments and suggestions are most welcome.

One of the most important features that will be released soon as part of Foreman 1.1 is locations & organizations. We will probably do a deep dive (which will get recorded) pretty soon, but I recorded a quick screencast to show how they work. Enjoy!

The volume in the recording is low, but it gets very degraded when I try to increase the gain so make sure to crank up your output.

We’ve got Parameterized Class support in Foreman now, and it’ll be in the next release! I’ve recorded a small screencast demonstrating its use:

You can find the mentioned wiki page at wiki:Parameterized_class_support

So I’ve been managing the Debian packages for about 8 months now, and every so often I get asked if there’s anything people can do to help. I have to answer “Not really” because the way we’re building the Debian packages is somewhat arcane.

At least, it was. This blog is to tell you all about how it’s now much more open.

Overview

We started working on a new project to create build and test pipelines for releasing code and running tests, and small, but dense infrastructure arose from working on that project. Instead of keeping the Puppet code locked up, we decided specifically to make it public. There are lots of benefits of doing this, but it made sense specifically for us so others can help manage the infrastructure on an unfettered basis. Lots of other benefits come with public Puppet code, too, like thinking more acutely about storing private information in the repositories and reducing the ability of manual changes to cause issues in the test environment.