Puppet users - Dec 2012 - Having puppetmaster checkout manifests from subversion

Hi

I''m looking into a setup where we''d like the puppetmaster to 
checkout/update all the manifests from subversion before it compiles the 
manifests served to puppet nodes. I have been looking through the 
documentation, and I can''t seem to find a way of doing this.

We''d like to be able to develop our manifests on our local computers
and
when committed to subversion, force a puppet agent run and this run would 
then use the newest manifests available. We are not using automated puppet 
agent runs, so the problem of a commit suddenly breaking code without 
noticing should not be a problem. 

The subversion server is not running on the same server as puppetmaster, so 
any interaction from subversion to puppet is not possible.

Any ideas how this problem can be solved? 

We are running puppet 2.7.18 on our master server.

Regards
Thomas

-- 
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/-/eIWMOngAR90J.
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.

Hi Thomas,

About the only way I can see that working is if you setup a cron job on the
puppet master that updates the svn and then do the remote puppet runs.

Git may be a better way to achieve this.

On 6 December 2012 21:19, Thomas Rasmussen
<rasmussen.thomas@gmail.com>wrote:
> Hi
>
> I''m looking into a setup where we''d like the puppetmaster
to
> checkout/update all the manifests from subversion before it compiles the
> manifests served to puppet nodes. I have been looking through the
> documentation, and I can''t seem to find a way of doing this.
>
> We''d like to be able to develop our manifests on our local
computers and
> when committed to subversion, force a puppet agent run and this run would
> then use the newest manifests available. We are not using automated puppet
> agent runs, so the problem of a commit suddenly breaking code without
> noticing should not be a problem.
>
> The subversion server is not running on the same server as puppetmaster,
> so any interaction from subversion to puppet is not possible.
>
> Any ideas how this problem can be solved?
>
> We are running puppet 2.7.18 on our master server.
>
> Regards
> Thomas
>
> --
> 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/-/eIWMOngAR90J.
> 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.

Thomas,

Have you looked at SVN''s post-commit hooks?  I think it can do what you
want (though, I''m a git guy, so don''t take my word for it).

Maybe something like rsync/scp your files over to the puppet masters in
your post-commit hook?

FWIW, we use git and the post-receive hooks to distribute the code to our
masters, then another post-receive hook on each master to handle setting up
our dynamic environments.  The code we run is here:

https://github.com/arusso23/git-hooks/blob/master/vcs/post-receive_distribute
https://github.com/arusso23/git-hooks/blob/master/puppet/post-receive_environments

Cheers,

Aaron Russo
IST Infrastructure Services, Unix Group
UC Berkeley


On Thu, Dec 6, 2012 at 3:55 PM, Peter Brown <rendhalver@gmail.com> wrote:
> Hi Thomas,
>
> About the only way I can see that working is if you setup a cron job on
> the puppet master that updates the svn and then do the remote puppet runs.
>
> Git may be a better way to achieve this.
>
> On 6 December 2012 21:19, Thomas Rasmussen
<rasmussen.thomas@gmail.com>wrote:
>
>> Hi
>>
>> I''m looking into a setup where we''d like the
puppetmaster to
>> checkout/update all the manifests from subversion before it compiles
the
>> manifests served to puppet nodes. I have been looking through the
>> documentation, and I can''t seem to find a way of doing this.
>>
>> We''d like to be able to develop our manifests on our local
computers and
>> when committed to subversion, force a puppet agent run and this run
would
>> then use the newest manifests available. We are not using automated
puppet
>> agent runs, so the problem of a commit suddenly breaking code without
>> noticing should not be a problem.
>>
>> The subversion server is not running on the same server as
puppetmaster,
>> so any interaction from subversion to puppet is not possible.
>>
>> Any ideas how this problem can be solved?
>>
>> We are running puppet 2.7.18 on our master server.
>>
>> Regards
>> Thomas
>>
>> --
>> 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/-/eIWMOngAR90J.
>> 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.
>
-- 
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.