Why people don't automate sysadmin stuff

May 3, 2008

Yesterday's entry raises an obvious question: why don't people automate things ahead of time, before they have so many systems that they have to automate or die?

The simple answer is that it is easier for them not to automate than it is for them to automate. But why is it that way?

There are at least two reasons:

  • there is pretty much no standard way to automate things at the various levels, especially across different Unixes and platforms. This means that you have to build an automation setup yourself, or at least evaluate a bunch of open source options to see which ones actually work in your environment.

  • when there are vendor tools, the vendors have generally done a bad job of making them available and convenient. The area that this particularly manifests in is that vendors have done a bad job of letting you grow into using the tools, where you can do things like install a system once by hand and then have it adopted by the vendor's auto-install framework.

From my perspective, part of the problem is that vendors often aim too high. Instead of adopting a Unix tools approach, where they try to create relatively simple pieces that can be used as building blocks, they try to create an 'Enterprise Management Application' or the like that meets all the needs in one go.

(The lack of standard tools has other costs, but that's another entry.)

Or in short: right now, the lack of standard tools and good integration means that it takes a bunch of work to automate, enough that it's hard to justify if you're not running enough systems.

Written on 03 May 2008.
« Automation changes as systems grow
On standard interfaces »

Page tools: View Source, Add Comment.
Login: Password:
Atom Syndication: Recent Comments.

Last modified: Sat May 3 23:19:49 2008
This dinky wiki is brought to you by the Insane Hackers Guild, Python sub-branch.