I'd rather have most of my changes done in a consistent way that's been tested on dozens of my nodes than have a special out of band config mechanism just for puppetmasters. Although my view might change if we ever really screw it up - but a mistake of that size will kill more than one node in staging anyway :)
Makes sense. Perhaps I'll go this route. I'd still be a little hesitant to ldapify the boxes, as a failed LDAP daemon would potentially could slow(er) authentication to the box I need to log into to fix the issue. But I can see how puppetizing the puppet master would help with consistency.
Still, this is a virtual environment, so nightly snapshots are occuring anyway :) But that still doesn't solve the issue of re-producing a box from the ground up.
Anyone else making their puppetmaster a puppet client? -Matt -- 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.
