We use cobbler for client installs and that works well for our centos servers, foreman can handle more distributions.
As for installing the client software itself, we use a custom RPM package that is installed at build time or anytime after. We are still building out our manifests so we are tackling one service at a time on each node type. Cheers, On 07/04/2011, at 5:11, Ohad Levy <[email protected]> wrote: > > > On Wed, Apr 6, 2011 at 9:54 PM, Forrie <[email protected]> wrote: > Our shop is newly adopting puppet. Our number of nodes is growing > and my installation method is thus far manual and tedious. This will > change when/if we migrate to Puppet Enterprise. > > My question is what's a best practice for managing puppet > installations on client nodes? Is it possible to separate out the > client portion of the install from the server or is that now fully > integrated? > > The puppet.conf file could be templated for distribution. > > Thanks for any tips, etc. > > -- > You might consider using Foreman [1] for this task. > > Ohad > > [1] - http://theforeman.org > > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
