On Fri, Feb 5, 2010 at 4:53 AM, Dick Davies <rasput...@hellooperator.net> wrote: > On Tue, Feb 2, 2010 at 5:08 PM, Michael DeHaan > <mich...@reductivelabs.com> wrote: > >> With Puppet, if you're just learning it, what were some of your stumbling >> blocks? If you are an existing user, think back to that time, or times >> when you were talking with new users? > > #1 has to be variable scope and the inability to redefine variables. > That and the knock on impact on things like inheritance, > and the need for storeconfigs to 'know about' the variables of > another node.
Lexical scope is in work here, so that should help immensely. > #2 is the difficulty to test manifests reliably (the reliance on Facts > makes it tricky to even syntax > check recipes without actually running it on a node). Makes #1 > more of an issue. > I keep getting bitten by interactions between modules, so it > needs to be some sort of integration > test. > #3 is a best practice guide - e.g. is it best to have a separate class > heirarchy per OS / role, or fill > your modules with case statements? Very much so. We are totally doing this. The common modules pool will also enforce those best practices so we can have examples. Definitely looking to all of you to help define and evolve what these best practices are along with things that Teyo has picked up, among others. -- 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.
