Hi Andy; I'm taking this to mean that you find that iteration constructs and new > structures move the language away from simplicity and their utility does > not offset that lo > ss of simplicity. Is that right? >
indeed. I should had been more clear ;) > > > We've found that many end up resorting to using inline templates to do > many things that are not related to generating text, which is what a > template is intended to be. Have you not found that to be the case for you? > i dont remember using inline template as a last resort solution. it is true though that its a pretty useful hack. every time i am confronted with a need for a loop, i use create_resources. if the problem reveals to be more complicated than that, then we turn to other types of solutions(functions, providers, etc) i think that that feature is a drift on puppet 'fundamentals'. on the other hand, what we would really love to see: a serious increase on performance. simply adding more resources to the master or installing more masters when the number of clients grow is clearly not a scalable solution. imho there are lots of work to be done here. (even if ruby has its limitations on this matter) a production ready 'environment' feature: we have found from our own experience and also on irc that the risk of 'leak' between environments is so high that makes it unusable on production. more emphasis on security. not long ago we were migrating a master to a PCI dss environment and i recall making a question on irc about this subject. to my surprise, i learned that the master relies on a fact for client auth and not on the dn of the certificate!(or maybe i just got it all wrong). anyway, my point here is that puppet stills some work in this area. testing testing and more testing. we need tools to test the catalogs locally. (a coworker works on a tool to addr this issue http://lpuppet.banquise.net) people are forced to use all sorts of hacks in the toolchain like apply the catalogs on a test server to check that nothing broke , and a bunch of other similar solutions. we would really love to see puppet grow, but on the number of features ;) cheers, evelio -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
