[colug-432] puppet: leveraging another module

[Scott Merrill]

The Puppet in Satellite 6 will be locked in at an older version, and will be very slow to upgrade. I think you're likely to miss out on a lot of the developing features of Puppet if you use Sat6.

I see Sat6's Puppet+Foreman as cobbler before them: a good jump start for big, slow moving enterprises that will benefit from some level of automation, but not something super useful for more nimble customers who can tackle automation and config management on their own.

But maybe I'm wrong.

On Jun 12, 2015 12:06 PM, Rick Hornsby <richardjhornsby at gmail.com> wrote:
>
>
> > On Jun 12, 2015, at 09:41, Matthew Hyclak <hyclak at gmail.com> wrote: 
> > 
> > Count me in for a meetup. 
> > 
> > We're doing some things with Satellite 6 and Puppet/hiera/r10k that may be interesting. I've been spending some time rewriting modules into the roles/profiles pattern as well. 
>
> While I'm geographically unable to attend a meetup, I'm interested to hear your progress/experience/thoughts on using Satellite 6's built-in puppet master capabilities.  I'm presently learning/architecting/developing Puppet on a stand-alone Puppet server, but I've been asked to look at using our coming Satellite 6 server as the more permanent puppet master.  So much of Satellite comes pre-configured (Foreman, etc) that I'm a bit leery of making configuration changes under the hood to support hiera (instead of the default of letting Foreman handle the class assignments for example). 
>
>
> -rick 
>
>
> _______________________________________________ 
> colug-432 mailing list 
> colug-432 at colug.net 
> http://lists.colug.net/mailman/listinfo/colug-432