On Thu, May 3, 2012 at 12:22 AM, rmarque <rob.j.marq...@gmail.com> wrote: > I just became the Linux Admin for a large company's development team. There > are about 6 servers (ubuntu on HP) and roughly 35 people who all have ubuntu > workstations and laptops (dual boot). I have heard of puppet and have tried > to wrap my head around what it might be good for in the environment. I do > have to keep these environments pretty strict as it is development of major > software. I also have a couple of new servers coming in that I will need to > image as close to the other servers as possible. > > So, in laymans terms...would puppet be good for deploying/imaging new > servers/workstation/laptops in the same strict OS/pkgs as everybody else? > Would it be good at deploying new pckgs/patches to the OS across all of > them? > > Any and all comments welcome. > > Yes, I am a newb. ;-) > > Thanks! > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/61KLMNJD6d4J. > 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.
My experience is with Redhat/RPM but I can see that what I use applies to ubuntu/debian as well so here it is. [Specially the latest versions of cobbler/puppet] I have successfully been using cobbler and puppet for provisioning and management. 1. Cobbler for pxe/dhcp/dns management. I use cobbler to store all the distros that I can possibly be asked to install. Also I use it to mirror all external repositories so everything is local. As a result, a base systems install takes about 10 minutes from pxe to bash prompt. 2. Puppet for configuration management - all machines have a puppet profile , after cobbler is done installing the server, puppet kicks in pulling the configuration for the particular machine being installed and it goes its way installing the packages/software. For server, I package everything and keep them in our custom repo. As a result re-installation is a snap and automated with puppet. For desktop machines, the users $HOME are stored in an nfs share. This provides a side effect that a desktop can blow up and I can restore everything to a new machine just by booting it up with cobbler and letting puppet apply the configs. Puppet might be hard at the start but there are great tutorials out there. Start with running puppet locally by using it to configure your desktop before you attempt to set it up in a server/client setting. I hope this helps /Jason -- 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.
