Ask Your Question

UPDATED: Puppet Enterprise and Satellite 6 Puppet Community integration

asked 2015-08-21 02:39:14 -0600

gorantornqvist gravatar image

updated 2015-08-27 06:57:24 -0600

Hi, I know that PE and Sat 6 integration is coming.

  • We are looking at PE for about 15 mission critical AIX systems.
  • We are also looking at moving from Satellite 5 and Puppet Community to Satellite 6 for about 150 RHEL-systems.

The preferred path would probably be PE for all systems (and use Sat 6 without builtin puppet for RHEL systems) but I was wondering what other options there are if my customer decides they dont want to use PE for the 150 RHEL systems.

UPDATE: I learned a bit more about Sat 6 now so I´ve updated the below questions:

Can PE in any way expose its installed modules by http? I know that you can create a repo in Satellite 6 of type puppet and point it to puppetforge or an internal repo and it will automatically sync the puppet repo just like any other yum repo. Could this "repo" be the PE server directly?

Or another alternative would be to use the same upstream source repo to import modules from, to both Sat 6 puppet and PE. Could something like be used, what do you think?

Thanks for your thoughts ...

edit retag flag offensive close merge delete

2 Answers

Sort by » oldest newest most voted

answered 2015-08-27 14:01:17 -0600

johnnyb04 gravatar image

This may or may not be useful. Red Hat recently came and did a presentation at our company for Satellite 6. When asked how the Puppet piece of Sat 6 would function with an existing Puppet Master, Red Hat was hesitant to say that both would coexist peacefully. They suggested exporting all Puppet modules to Satellite and using it as the master. I suspect this was their default answer since they don't provide technical support for Puppet. Other users may have heard something different though.

In regards to exposing Puppet modules via HTTP, there might be a way to do this. To start, I would suggest installing httpd on the system and creating a soft link under /var/www/html/ and pointing it to your Puppet modules folder (ie: /etc/puppet/modules/). If you're running SELinux, you'll need to add the http context to your modules folder. This should expose all of your modules to the web. You're more than likely creating a large security hole in your network by making your Puppet configurations viewable. Just keep that in mind.

edit flag offensive delete link more

answered 2015-08-28 02:34:41 -0600

gorantornqvist gravatar image

Thanks for your answer.

My feeling after learning how lifecycle environments and content views are working in Sat 6, where you need to publish/promote both packages and puppet config before it is is accessible to content hosts, is that using an external puppet master will break this control/behavior/automation since it will introduce an extra step in the workflow where you need to first promote your release in Sat 6 and then go to your puppet master and upgrade the corresponding modules.

It would be interesting to know how people using Sat 6 + external puppet are doing it...or are planning to do it.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools



Asked: 2015-08-21 02:39:14 -0600

Seen: 611 times

Last updated: Aug 28 '15