We have 600 compute nodes, and we face the same issue. Fortunately, all of our nodes (except for 10 dual-homed gateways) are on a private 10.x.x.x network, so once someone is authenticated he or she can rsh around the cluster. So, we used multi-rsh to do the initial work for us. I created a tarball with everything the client needed to get itself up and running: ruby, facter, config file, the works. Then multi-rsh pushed the tarball to the boxes, untarred the file and launched the client. From there is was a matter of signing all the cert requests, then waiting for all the boxes to settle down.
I spent a day using our test cluster to get everything working correctly, I even compiled ruby from source. This make upgrading puppet on the clients a breeze. I create a new tarball, and untar it across the cluster, restart the clients, and in a few minutes all 600 nodes are upgraded. Again, this is possible because we use rsh after authentication so multi-rsh just works. ~Charles~ On Tue, May 24, 2011 at 8:55 AM, CHEBRIAN <ksd....@gmail.com> wrote: > Hi, > > how to install puppet client thru puppet master . > > My requirement is to install puppet client nearly 400 client servers. > > its difficult to install puppet client in all the servers by apt- > get . > > share u r suggestions . > > Regards > > chebrian > > -- > 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. > > -- 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.
