On Sun, Feb 8, 2009 at 9:59 AM, Larry Ludwig <larry...@gmail.com> wrote:
> > Hmm some comments to this... > > This sounds like a bear to maintain, while I think it's important to > do in a complex environment like you have. > 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 wishing the info you are doing is more included in the module > syntax of Puppet's language itself. 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). > > > It's interesting to see you don't use Puppet's built in tagging (ie > development, staging, production). Just curious why? > by tagging you mean to tag resources? that would be hard to maintain when you have multiple environments (e.g. 10+) additionally, it means that someone could edit/break a productive manifest. if by development staging, production you mean puppet modules/environments, of course we use them, but we simply have way more environments that just 3 ( different locations/applications have different "stable/production" levels) - and thats kinda the tricky part here. one of our goals was to harmonize our global environment, but at the same time, its impossible to force everyone to do a change at a certain given time. therefor, every location subscribes to a module combinations (an environment) which in turn is made out of modules in predefined versions. > What would you consider needed in Puppet to make your development > easier? I'm not really sure if puppet can help much here, its more of having guidelines of how to use modules, where to put them and how to call them... > > > I'm thinking: > - module version should not be managed by puppet - puppet is not a scm > > - 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. > > - some sort of naming convention to allow modules to be shareable, and > cannot overlap (ie one person has a openssh-server module that does > one thing, yet another person uses the same name but does something > different) This is needed so modules can be shared in some sort of > public repository. 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? Ohad --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
