Many people I talk to prefer postcommit hooks to do this work. We had an on-site engagement where we wrote an MCollective agent that would do all the heavy Git lifting, and the postcommit would call the MCollective agent. This also let you quickly move your Masters to different commits as-needed (so long as you had privileges to access the message queue with MCollective).
On Wed, May 2, 2012 at 7:18 AM, Scott Merrill <ski...@skippy.net> wrote: > For folks with multiple Puppet Masters, how are you pushing out > manifest and module updates to them? > > We intend to use Subversion for our version control. Obviously one > option would be to have each Puppet Master perform a checkout of the > svn repo. We could schedule periodic updates via cron. Or we could use > a post-commit hook to rsync the updates out from the repo to each > Puppet Master. > > What are you doing? What works well, and what headaches have you > experienced? > > Thanks, > Scott > > -- > 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. > > -- Gary Larizza Professional Services Engineer Puppet Labs -- 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.
