Newbie questions -- do you use PuppetDB and Facter with Foreman?
87 views
Skip to first unread message
Bryan Arenal
Feb 10, 2015, 12:40:47 PM2/10/15
to puppet...@googlegroups.com
Hi,
I'm just getting started with Puppet (I have it installed but that's
pretty much the extent of it). I'm planning on using Foreman with it
but was wondering what "most" Puppet users do. Is it more or less
standard to use PuppetDB and Facter? Or do you even need those
components when using Foreman? Are there others that are typically
installed in an Enterprise Puppet installation?
Sorry for the total n00b questions!
Cheers
I'm just getting started with Puppet (I have it installed but that's
pretty much the extent of it). I'm planning on using Foreman with it
but was wondering what "most" Puppet users do. Is it more or less
standard to use PuppetDB and Facter? Or do you even need those
components when using Foreman? Are there others that are typically
installed in an Enterprise Puppet installation?
Sorry for the total n00b questions!
Cheers
Christopher Wood
Feb 10, 2015, 1:24:34 PM2/10/15
to puppet...@googlegroups.com
Not sure how typical we are, but it feels pretty standard for a medium-sized installation. Just starting out I had a puppetmaster and some agents, so two lines of this list. The rest came later.
puppetmasters behind a load balancer
facter (this is standard, yes)
hiera
hiera-eyaml
puppetdb
Puppet Explorer
puppet agents (daemons, running from cron is likely be better for you)
monit watching daemons incl. puppet, run from init just in case it dies
git (for manifests/modules/hieradata, puppetmasters check out a copy)
jenkins (for some tests, needs expanding here)
mcollective with the default mcollective agents
activemq (for mcollective)
cobbler (bootstrap from bare metal to the cert signing request)
In your place I'd start with getting your manifests/modules/hieradata into git or some revision control system, that way you can track what happens to your code. Then work up from 'puppet apply' to either puppetmasters or 'masterless puppet' (google that). Once you have things puppetized to your satisfaction you can put optional bits in place via puppet which is much easier.
> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CANvovHQMrPrGEoYKD_R8f%2BrqNrrS0MtqVLDsOcHV7CZy4z5fPQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
puppetmasters behind a load balancer
facter (this is standard, yes)
hiera
hiera-eyaml
puppetdb
Puppet Explorer
puppet agents (daemons, running from cron is likely be better for you)
monit watching daemons incl. puppet, run from init just in case it dies
git (for manifests/modules/hieradata, puppetmasters check out a copy)
jenkins (for some tests, needs expanding here)
mcollective with the default mcollective agents
activemq (for mcollective)
cobbler (bootstrap from bare metal to the cert signing request)
In your place I'd start with getting your manifests/modules/hieradata into git or some revision control system, that way you can track what happens to your code. Then work up from 'puppet apply' to either puppetmasters or 'masterless puppet' (google that). Once you have things puppetized to your satisfaction you can put optional bits in place via puppet which is much easier.
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CANvovHQMrPrGEoYKD_R8f%2BrqNrrS0MtqVLDsOcHV7CZy4z5fPQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages