Hi Experts, I am just wondering is there anything like a "Puppet Module Repository" in production yet? For the "Puppet Module Repository" I am looking for two main features: 1. Versioning control of each individual module 2. automatic dependency resolution, one module will be able to say which module (at which version) this module depend on. Basically, something like python easy_install or ruby gems will be the best. Thanks a lot! -Yushu -- 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.
On 11/10/2010 01:14 PM, Yushu Yao wrote:> Hi Experts, > > I am just wondering is there anything like a "Puppet Module > Repository" in production yet? > > For the "Puppet Module Repository" I am looking for two main features: > 1. Versioning control of each individual module > 2. automatic dependency resolution, one module will be able to say > which module (at which version) this module depend on. > > Basically, something like python easy_install or ruby gems will be the > best. > > Thanks a lot! > > -Yushu > > -- > 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.http://forge.puppetlabs.com/ -- Joe McDonagh AIM: YoosingYoonickz IRC: joe-mac on freenode "When the going gets weird, the weird turn pro." -- 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.
This is not exactly what you''re looking for but may be a solution. We
are using the multiple environment functionality (http://
projects.puppetlabs.com/projects/1/wiki/Using_Multiple_Environments)
to manage version control to prevent changes from impacting production
while we''re implementing and testing in DEV. We basically have a
checkout/working copy of the puppet modules for each environment.
When we want to upgrade production, we snap a new tag, and then update
the working directory on the PM to the new version. Our tree looks
like:
/etc/puppet/env
|-- dev
| |-- manifests
| `-- modules
|-- preprod
| |-- manifests
| `-- modules
`-- prod
|-- manifests
`-- modules
This gives us version control at the environment level instead of at
the module level. I don''t know of any dependency resolution solution.
John
--
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.