On Dec 12, 2010, at 8:00 PM, Josh wrote: > Greetings, > I'm just getting started with setting up Puppet in an environment of > about ~15 servers, a mixture of Mac OS X servers and Ubuntu servers - > each with different roles and obviously different versions of configs. > > Before I get too carried away, I was hoping to get advice on the "rule > of thumb" about different versions of configs. Most of the > documentation and examples I've seen seem to be geared more towards > "roles" of a set of nodes, such as "http nodes, dns nodes" etc. What > hasn't been too clear to me is a smaller scale environment where there > aren't multiple nodes sharing the same job. > > Say I have an application installed on two of my servers and > obviously, each server has its own version of the config files for > that.
I find that in this case either: 1) You can template the config file to reuse it. or 2) You define each as a diffierent role so one might be puppetmaster::slave and the other might be puppetmaster::ca. (In my config both serve configuration. Ca is the CA and holds the reports) Obviously, depending on what you're doing, this might not be true. > What is the "best practice" to manage that? Do I define a > class for "server1" with each thing I want to manage, and point to a > specific file (e.g. puppet://puppet/files/server1/config.cfg .../ > server2/config.cfg ...etc)? > > Any nudge in the right direction is greatly appreciated! Thanks. I've found that -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
