Re: Puppet & Chef
Thanks for your comments Nate.
I have to agree with you. I personally loathe the term webscale, but unfortunately Gartner has started using it and it's steadily making its way into the everyday terminology of vendors in the IT world. Everyone wants to pretend that their offering is webscale. Like cloud it has little to no real meaning other than to be a buzzword category for vendors to pay Gartner to advertise them in.
For most of the clients I've ever worked with any installation with 3 physical servers and above IS webscale as far as they are concerned. In the real world most admins, myself very much included, won't ever see an implementation of sufficient size to be defined as webscale by the folks at Gartner. Does it mean then that we shouldn't use automation (or orchestration) to make things easier? For me that answer is absolutely not.
I'm sorry that I lost you when I mentioned webscale (and I hope I didn't just lose you again), but I tried to make the point near the end of the piece that there is no one size fits all equation when it comes to automation. It's purely subjective when and for what you should use it.
Personally, I use scripted automation to perform all the mindlessly repetitive tasks that need to be done everyday and then to email me the log files for those tasks. I also use runbook based orchestration (with a side order of scripted automation thrown in) to make build processes for virtual server instances (lab and production) simpler.
In total, automation probably frees up around 10-15 hrs a week of my time on a light week and anywhere from 45-60hrs when I've got heavy project work on. As a guideline I won't automate a task I wouldn't feel comfortable farming off to a PFY but if I would delegate it (and it can be automated without having to spend 6 months creating a runbook) then its fair game.