I’ve been following off and on the progress of Puppet, a system administators configuration management tool. It certainly does look way more promising than CFEngine (which I last touched in 2000. Boy what a pain in the ass that tool was.)
Unfortunately, I do not like to put any kind of software in place that is undergoing rapid change. I get enough of that at my job where I am constantly putting in the build-of-the-day into production simply because of the sheer number of critical bugs or business-enabling feature enhancements that are needed PDQ, RFN.
Rapid change in software that needs to be stable just creates pain for the sysadmins, nevermind users (who are the whole point of providing working systems anyways). Users who are generally angsty over any kind of perceived change in their universe that would require them to stop and think for a moment about anything other than their business processes that they need to accomplish as part of their job. Not that I blame them, much. They could learn to be a bit more flexible but that’s another rant.
Good news is, there does seem to be light at the end of the tunnel for my being able to try out Puppet at work. It appears that the perpetrator of Puppet will be doing a commercial installation of this tool sometime this quarter and as part of that will have a 1.0 release available at that time.
Goody.. so now all I have to do is wait for 1.0 to come out and then a few weeks after tha for all the early adoptors waiting for the magic 1.0 to do their task - find the nasty bugs that only new users can find. (Sorry Luke!) Unless all those early adopters read this or think similarily
Oh wait. I’m doing a trackback to the original blog posting. doh!
Here’s to Puppet 1.0.5, whenever it arrives. Cheers!