At Red Hat we call it the Open Source Way. When we talk about open source, we’re talking about a proven way of collaborating to create technology. The freedom to see the code, to learn from it, to ask questions and offer improvements: This is the open source way.
That’s just what we saw today between the Puppet Enterprise teams and Red Hat Satellite Product teams. Carl Caum and Tim Zonca of Puppet Labs, along with Richard Jerrido and Christopher Wells of Red Hat, described their offerings and briefly demonstrated how they are collaborating on interoperability in order to bring the best experience they can to customers.
About Red Hat Satellite and Puppet Enterprise
Most of the room was already familiar with Red Hat Satellite and were current users. Chris did level set for those unfamiliar with Red Hat Satellite. He described Red Hat Satellite as Red Hat’s life-cycle management, which comprises provisioning, patching, subscription management of bare metal, virtual and public cloud environments.
Tim did the same for Puppet. In short, Puppet manages the configurations of your systems and what’s running on them. Ultimately, it allows for the automation of tasks, so less time is spent fighting fires so you have more time to be productive. Currently, Satellite provides Puppet as a component of Satellite 6.
So why would someone want to use a separate Puppet environment? Well, currently the Puppet included with Red Hat Satellite only supports Red Hat Enterprise Linux. Most organizations are quite heterogeneous and may need Puppet Enterprise support for UNIX distributions or Windows instances. Customers may want to use the enhanced tools that Puppet Enterprise offers. In the next few months, the teams will be announcing support for this integration.
How this integration works
So how would this integration work? Essentially, when a system is provisioned via Red Hat Satellite, a puppet agent is installed as a step in the kickstart post-provision process, handled by a reusable provisioning template called a finish script. This process is all handled by Foreman. A user would change this template to install the Puppet Enterprise agent and point it to the Puppet Enterprise puppet master instead of it being pointed at the Red Hat Satellite puppet master.
The Puppet Enterprise repositories are shared via Pulp on the Red Hat Satellite Server, which is the first point of integration. The user would then approve the agent request in the Puppet Enterprise puppet master. Every time the puppet agent runs, it pulls its configuration but also sends the report information and inventory data or system facts back to the puppet master. The integration will now send these reports and facts not only to Puppet Enterprise, but also to Red Hat Satellite using standard components of Puppet Enterprise called a Report Processor, and the Fact Terminus.
This integration was well received by the attendees and will likely be a much consumed feature. This exciting integration should be available to the public very soon!