I wanted to deploy Puppet at $work but writing my own set of modules is a huge brick wall that I was just too lazy to get through. I hope that Puppet Forge gives rise to a standardised collection of portable modules that is shipped with Puppet itself.
Posted Feb 18, 2011 17:08 UTC (Fri) by droundy (subscriber, #4559)
[Link]
I can only agree that puppet is a royal pain to use. It seems to be designed for people who manage thousands of computers as their full-time job. For those of us who just manage a dozen or so computers as a peripheral aspect of our job, it's a whole lot of work to set up.
FOSDEM: Configuration management
Posted Feb 25, 2011 22:20 UTC (Fri) by filteredperception (guest, #5692)
[Link]
I looked at puppet years ago and came to that same conclusion. I've continued work on my own system (viros.sf.net), targeting users with even a smaller base of systems, i.e. a random engineer with a couple personal laptops/workstations and servers. Mainly from my own obsession with easy personal, and business disaster recovery, which is not so unrelated to the process of having to move to a new major linux distro version every 6 months. In any event, I did enjoy (and will link to) this excellent article on the current state of the art. While I still like my metaphor- OS as a virus/dna, configuration classes/modules as genes/traits with subtraits, I am glad to see that all the systems are basically headed down similar paths. I would probably choose puppet for a new 1000+ system deployment, suffering its apparently still steeper-than-ideal learning/complexity curve.
FOSDEM: Configuration management
Posted Feb 26, 2011 2:05 UTC (Sat) by nwmcsween (guest, #62367)
[Link]
I worked on creating a provider for a package manager with puppet, I stopped when I saw a variables being used as either boolean or a string... don't use puppet the architecture is broken.