> > The structure itself is complicated, however the usage is quite simple if > you understand the structure..... nevertheless, if you have any > better/simpler idea - I would really love to hear it..
I'm starting to look into what other users of Puppet are doing before I draw any conclusions/recommendations. I would like to hear of any other users and their comments. In order for Puppet to really work it must not only scale to large amounts of computers but also a large amount of administrations/system programmers working on recipes. > I'm not sure I understood your question...What do you mean module syntax? > (the define?) we are only using the puppet language (with a special > directory structure in scm). Ok really Class statement, other than file structure there is no Module statement in the language itself. Maybe this is part of the problem :-) > > I'm thinking: > > - module version > > should not be managed by puppet - puppet is not a scm not scm, but the module state it's version info. Kinda like Ruby gems. So you can require a specific version of a module when running your app. Also have the ability to have multiple versions with Puppet. > > - dependencies needed to get the module working (with version info) > > thats easy to achieve if you save the version number as a variable - > nevertheless, usually you dont care about a specific module version, you > care about a mix of modules. Well it can be both. For example (puppetshow as for one) how many times you an app develop in Ruby and you need a specific version of Rails?? Use the latest and boom! Not nice in a production enviroment. It is also possible in the existing Puppet world that one person has a module that overlaps another module developed by someone else. Yes it can be a variable but it's not forced on the module creator. Putting it into the language forces this on the developer. In order for Puppet to allow easy sharing of modules something like this needs to happen. > I would really love to have a public repo (and if I'm allowed, I would love > to publish our manifests) I know that there was a try to get a public repo - > is it still around? As I am getting ready to release some Puppet modules, I'm realizing the current limitations of Puppet and sharing modules with the general public. IMHO this is also one of the reasons why the public module list in the wiki is so small. Puppet so far has changed the way we perform administration, what it hasn't done yet is make it easy to share 'the secret sauce" with other administrators. Once this happens on large scale I think some interesting things will happen. -L --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
