On Tue, Feb 2, 2010 at 9:02 PM, Ohad Levy <ohadl...@gmail.com> wrote:
> > > On Wed, Feb 3, 2010 at 9:27 AM, James Cammarata <j...@sngx.net> wrote: > >> I've found the puppetrun utility to be very lacking, in many ways, and >> have >> resorted to my own scripts to trigger runs. This script runs using ssh to >> hit servers, which is unfortunately not ideal right now since it operates >> in a serial fashion, and it creates a chicken/egg problem (puppet is used >> to deploy the user/sudoers/ssh key...). >> >> You might want to have a look at puppetlist/puppetrun in the ext > directory, it could provide some of the functionality you are looking for. > As an aside -- I see puppetd and /usr/sbin/puppet share many common options, but not quite all of them. Possibly these could be unified. Some evolution of puppetrun should be in the main distribution, IMHO, as part of puppetmaster. We've talked a little bit about staged (timed) rollouts of new manifests and so forth, and environments, and I can see that playing a role. This is another conversation we should have too -- how to roll all the scripts (in ext, or in the community on git somewhere, like the ones you have created) into the main core, versus having folks have to learn about it the hard way :) --Michael -- 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.
