Puppet users - May 2012 - distributing updates to multiple puppet masters (Subversion)

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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

I use a combination of git and puppet itself to push to productions, but
git for dev/qa puppet masters. Puppet Pro has nice examples of git with
environments but here is a link also.

http://puppetlabs.com/blog/git-workflow-and-puppet-environments/

On Wed, May 2, 2012 at 10:18 AM, Scott Merrill <skippy@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+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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 <skippy@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+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Our SVN repo box is shared with some other projects so I haven''t
implemented a post-commit hook at this point.  We used to have Puppet
perform the checkouts, but since a commit may break Puppet''s ability to
run it didn''t seem like the best way.  For now we''re doing it
via
MCollective.

On 05/02/2012 07:18 AM, Scott Merrill 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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Yes, actually each of my masters has its own SVN-URL checked out with the
appropriate configuration.  A cron job is doing updates in 5 minute intervals.
Quite easy and works very reliable.

Bernd
> -----Ursprüngliche Nachricht-----
> Von: puppet-users@googlegroups.com [mailto:puppet-
> users@googlegroups.com] Im Auftrag von Scott Merrill
> Gesendet: Mittwoch, 2. Mai 2012 16:18
> An: puppet-users@googlegroups.com
> Betreff: [Puppet Users] distributing updates to multiple puppet masters
> (Subversion)
> 
> 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+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

We use puppet and a module called vcsdeploy to deploy our modules to the 
puppet masters using a puppet run on the puppetmaster.  We insist that all 
modules are tagged and so our nodes file fotr the puppetmaster node looks 
like this: -

node ''puppetmaster'' {

  # ONLY DEPLOY tagged versions to TEST!!!
  Vcsdeploy {
    source    => 
''http://svnserver.practicalclouds.com/repos/puppet/modules/%%NAME%%/tags/%%VERSION%%'',
    path      =>
''/etc/puppet/environments/test/modules/%%NAME%%'',
    provider  => ''svn'',
    user      => ''user'',
    pass      => ''######'',
    templates => ''off'',
  }
  vcsdeploy {  ''centrify'':
    version => ''1.7'',
  }
  vcsdeploy {  ''wamps_repository'':
    version => ''1.1'',
  }
  vcsdeploy { ''weblogic'':
    version => ''4.5'',
  }
  vcsdeploy { ''motd'':
    version => ''1.0'',
  }
  vcsdeploy { ''ntp_client'':
    version => ''1.0'',
  }

You can find out more about vcsdeploy either on the puppet 
forge http://forge.puppetlabs.com/pclouds/vcsdeploy or 
here http://www.practicalclouds.com/content/guide/pclouds-vcsdeploy-deploy-stuff

regards



Dave

On Wednesday, May 2, 2012 3:18:28 PM UTC+1, Scott Merrill
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 unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.