On Tuesday, April 2, 2013 12:48:57 PM UTC-5, Thomas A. Fine wrote: > > Hi, > > As we gradually spread puppet management to all of our systems, we've > run across a group that's managed by us, but also semi-self-managed, and > they'd set up puppet to manage some of their own software configurations > (they provide an outward facing archive service). > > Is there a way to set up puppet so that it looks at multiple servers for > it's configuration? > > My first guess is to say that we control /etc/puppet/puppet.conf and > point it at our servers, and that they fall back to running puppet from > cron with "--config /path/to/their/puppet.conf". >
Yes, something like that could do what you ask, but it's a bad idea. > > Is there a better way to handle this? i.e. can you put something in > puppet.conf that tells it to apply rules found on more than one server? > No, you can't. There is a fundamental problem with the approach: you rely on independent sources of truth with overlapping scope. Conflicts WILL arise. Instead, you want a mechanism by which the group in question can have its own declarations incorporated into the catalog generated by the central master. Conflicts are less likely in that case, and they will be recognized by the master when they occur. Garrett had some good suggestions for how to provide this kind of feature, and I will add that you may also get some mileage out of hiera, with which you can provide for the special group to override site-wide standard data and parameters with customized data for their group. John -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
