On 06/20/2012 06:54 PM, Jo Rhett wrote: >> Humm, I believe it's fair to assume that "most people" have some way of >> puppet provisioning that will be able to take care of this configuration >> detail. > > Okay, I've worked at 4 different shops using puppet over the last 6 > years (one is a non-profit I work at part time). In not one of those > shops was bare-metal provisioning something I set up (so the following > decision was not mine and never has been) and in every case, the system > kickstarts to install puppet rpm, then uses puppet to configure the rest > of the system based on the system name. > > This goes back to this funny thing, where people keep saying I should be > using a different configuration management system to handle things > outside of puppet. Should we boot to install cfengine and use that to > set up puppet? :p
I seem to have your personal red cloth on me ;) I'm not suggesting an additional config management system. Most (all?) bare metal provisioning tools offer some way to carbon copy some base files, so a default puppet.conf that differs from the one in the RPM would be one idea to go about it. If the site has a need to maintain its own RPM of puppet agent (I know I do, but I realize it's not commonplace), this is a non-issue. But, again, I'm totally down with using puppet to configure puppet. This should definitely be an option, and it's a bummer that an important module keeps it from Just Working. Cheers, Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
