Puppet users - Jul 2012 - Is is possible/acceptable to create a private puppet forge?

We have a pretty large internal distribution of puppet content, with a 
bunch of disparate teams using a lot of modules written internally.  
Currently we have been using git with submodules to manage all of our 
puppet content and version control.

I have recently been looking at librarian-puppet and it seems like a much 
simpler solution to the same problem.  This however triggered the concern 
that a lot of our internal machines cannot reach the public forge.  So I am 
wondering what is the process to build an internal forge?  We could 
continue to use our existing GIT infrastructure, however I personally like 
the forge better.  

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/-/qHmo-8-oLK0J.
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 John,

Unfortunately, we don''t yet have that capability but are interested in
exploring it. Would you mind elaborating on your needs and what you''d
want from a private Forge in addition to what the public Forge offers?

--Ryan

On Wed, Jul 11, 2012 at 6:45 AM, jtimon <john.a.timon@gmail.com>
wrote:
> We have a pretty large internal distribution of puppet content, with a
bunch
> of disparate teams using a lot of modules written internally.  Currently we
> have been using git with submodules to manage all of our puppet content and
> version control.
>
> I have recently been looking at librarian-puppet and it seems like a much
> simpler solution to the same problem.  This however triggered the concern
> that a lot of our internal machines cannot reach the public forge.  So I am
> wondering what is the process to build an internal forge?  We could
continue
> to use our existing GIT infrastructure, however I personally like the forge
> better.
>
> 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/-/qHmo-8-oLK0J.
> 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.


-- 
Ryan Coleman | about.me/ryc
Modules & Forge @ 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.

I work for a large company with a number of disparate groups using Puppet. 
A private forge would provide a central publishing point and help us to 
collaborate.

We have modules which are private to our company due to IP restrictions or 
simply aren''t useful outside of our company so the public forge is not
the
place for our modules.

In another respect many of our systems don''t have access to the
Internet
and if they did (by use of a proxy) it would be frowned upon by our 
security and operations groups. In many cases we would even be pulling 
modules off the public forge and hosting them on our private forge after 
they''d passed some QA criteria. This is the same process that is widely
used for other software packages, like RPMs from EPEL.

Jonathan

On Wednesday, 11 July 2012 23:45:48 UTC+10, jtimon
wrote:
>
> We have a pretty large internal distribution of puppet content, with a 
> bunch of disparate teams using a lot of modules written internally.  
> Currently we have been using git with submodules to manage all of our 
> puppet content and version control.
>
> I have recently been looking at librarian-puppet and it seems like a much 
> simpler solution to the same problem.  This however triggered the concern 
> that a lot of our internal machines cannot reach the public forge.  So I am
> wondering what is the process to build an internal forge?  We could 
> continue to use our existing GIT infrastructure, however I personally like 
> the forge better.  
>
> 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/-/QRFpMvXKkdcJ.
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.