On Nov 1, 2010, at 7:18 AM, Oliver Hookins <ohook...@gmail.com> wrote:
> On Oct 18, 10:22 pm, Carl Caum <carl.c...@gmail.com> wrote: >> Is there a way to run your own puppetforgerepository? We are interested >> versioning and distributing our modules the same way we do our custom RPMs. >> We want to use puppet-module-tool and configure it to point to our local >> repository. > > Hmm, no replies yet but I am also interested in this topic. It also > gets into the murky water of managing modules for Puppet with > packages. Do we then use yet another layer of management tool on top > of the Puppet module packages (since it is probably safe to assume > that we cannot have Puppet adding and removing its own modules without > the possibility of something breaking)? > > -- > 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. > Yes, we would need to have another tool to manage the distribution of modules. I was looking at writing an mcollective plugin that I can push a configuration to that would include which module and which version of that module to install on the local system. The configuration would also include a manifest for the node to run. I currently have a similar system that uses subversion tags to check out the modules I need and tie in to a home grown queuing system that triggers a run. It works, but it's not elegant. -- 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.
