On Fri, Sep 26, 2014 at 01:00:44PM -0700, Ciro Iriarte wrote: > El viernes, 26 de septiembre de 2014 15:21:19 UTC-4, Christopher Wood > escribió: > > In your place I'd add a level to my hiera setup and template the bird > config. > > There's a number of different options you could use to classify which > node is in which site, from the node yaml in hiera to an ENC to a fact > provisioned when the host is built. > > Currently I'm running 1 puppet slave for tests and a master. Hiera is not > (yet?) in the mix, whatever that is O_o' > I assume this is a basic setup and I'm missing components, which are the > components expected in a current Puppet 3 implementation?
I couldn't say what's expected since requirements vary. For hiera take a look at: https://docs.puppetlabs.com/hiera/1/configuring.html Other things you may be interested in as you grow, see docs.puppetlabs.com for details: ca puppetmaster non-ca puppetmasters at each location for catalog compilation roles/profiles (http://www.craigdunn.org/2012/05/239/) git to store your manifests puppetdb mcollective ENC of some kind custom facts https://forge.puppetlabs.com/ hiera-eyaml or similar https://github.com/TomPoulton/hiera-eyaml (The list rather goes on and on, you seem to be doing just fine without most of this. They're still available should you need them.) -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20140926201521.GA12027%40iniquitous.heresiarch.ca. For more options, visit https://groups.google.com/d/optout.
