Puppet and Satellite 6 Integration roles / profiles / control repo

asked 2018-12-28 09:21:35 -0600

gilbo gravatar image


we're pretty nifty with puppet 2016.4 and are looking to upgrade to Puppet enterprise 5. Coincidentally someone else is looking at a brand new satellite 6.4 installation., so naturally were looking at integrating them.

I'd like to keep our current version control system (gitlab) and keep our current workflow of roles / profiles, etc.

Has anyone done that migration? Any caviets? the thinking of my approach so far is to just configure a gitlab webhook to push to satellite 6 server under the code directory and away we go. However a lot of redhat documentation says to import modules into satellite 6, create content views, etc so i'm not sure of the best way to go about it. Ultimately i want to keep all our code in gitlab and i want to keep classifying agents by role.

edit retag flag offensive close merge delete


As a guy who's used Satellite and Puppet separately for years (and who just passed the RH Satellite exam), my recommendation is to skip Puppet on Satellite and use separate servers. The integration with satellite just stinks in my opinion and you're stuck with the version that Red Hat dictates

bschonecker gravatar imagebschonecker ( 2019-01-02 06:47:54 -0600 )edit

to you. Only recently has Puppet 5 been available on Satellite 6.4 (I think). Isn't Puppet 7 out now? The only down side is when you provision servers with Satellite. The puppet integration is pretty good for that use case and you do have to jump through an extra hoop or two when you provision

bschonecker gravatar imagebschonecker ( 2019-01-02 06:48:16 -0600 )edit

with Satellite 6.4 and Puppetize on a separate server.

bschonecker gravatar imagebschonecker ( 2019-01-02 06:48:22 -0600 )edit