On Sun, May 23, 2010 at 6:42 AM, Joe McDonagh <joseph.e.mcdon...@gmail.com> wrote: > > The only thing I can think of limitations in puppet that people > frequently encounter is inter-node dependencies. I'm interested to see > what other limitations you ran into ...
I haven't tried puppet in over a year, but when I was evaluating it I could never get puppet to build a template from more than one piece. For example, if I wanted to add a line to crontab for each of several different classes. Also, the Ruby dependency for puppet is something I'm philosophically biased against. Too many dependencies, too many possibilites for problems. Configuration management should be one of the most dependable applications on the system. > ... as I read a lot about puppet from > the mailing lists, use it a lot, and try to help out on the IRC channel > when I can. It's the first software package I ever felt helped me so > much in my everyday life that I should really help out in the community > with it. I felt that way when I first started using cfengine, oh so long ago. But now that I see all it's flaws I'd love to move to cfengine3 or something else that is easier to teach and handles templates and class dependencies better; but I have so much invested in cfengine2 that it it difficult to migrate away from it. I'd also really, really like to have my configuration engine be part of my monitoring system, so that I can trigger configuration changes from status changes. -- Perfection is just a word I use occasionally with mustard. --Atom Powers-- _______________________________________________ Discuss mailing list Discuss@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
