If you have a crazy environment, I see how config-management would be better, but if you (like most sane shops) have a homogeneous environment, simple shell scripts are probably the best way to do things.
That's kind of what I mean by homogeneous. A lot of this depends on your environment, so it's very much a YMMV thing, but for me, it has worked out much better.
> If you happen to have two or more roles for the servers, shell scripts start tearing at their seams.
I guess it depends on how you set up your scripts. I made mine "config-management-esque", which is very modular, and it works well for me.
Then I have a bad news for you: except for rare case of overgrown startups, virtually nobody else has this kind of environment. Larger, established companies need file servers, external web servers, application servers to run internal services (multiple of them), directory services, print servers, and many others I couldn't remember at the moment. Heck, even development vs. production environments can have significant differences in configuration.
>> If you happen to have two or more roles for the servers, shell scripts start tearing at their seams.
> I guess it depends on how you set up your scripts. I made mine "config-management-esque", which is very modular, and it works well for me.
Of course it depends. CM systems are regular programs and not magic, after all. One can write one from scratch. I just really doubt your is a sensibly generic one instead of being "mine set of scripts that only works for my environment". It takes a lot, lot of experience in both programming and system administration to develop such a thing.
Well, you said yourself:
>> Only if your environment is cluster-like set of clones of a golden image, dutifully kept up-to-date with it.
> That's kind of what I mean by homogeneous.
Apparently you meant something different than I understood from this.
I've seen Puppet used as replacements for simple bash scripts, more complete management of a host (this is what I would consider config management), deployment tools and distributed consensus.
We used to use chef-solo and keep cookbooks in a separate repo, which was fetched over git by instances at boot time. Now we have developers in control of bake and boot-time scripts, and since "it's just bash" and there's barely any indirection / meta programming, people generally just get it, and it works. Note that this is using an "immutable-ish infrastructure" approach. Chef worked OK before we went immutable, but we'd have problems where the instance would get into a bad state because someone "fixed" something and the next chef run wouldn't apply cleanly. Taking away ssh access would be nice, but we don't have all the log analysis / system insight stuff in place to make that a reality just yet.
If we had a more complex use-case, I'd totally use chef again. If our needs expand, I wouldn't expand our little bash "system", but replace it with chef or chef-solo.
My first gig was as a DBA at a place with a really good UNIX culture. They had a framework of scripts that documented and automated many tasks.
In the process, those scripts morphed into something like puppet. It's sort of a maturity curve -- as you institutionalize more automation, you start to need the "meta features" and complexity that the configuration management tools provide.
I have looked at the many configuration management tools out there and I think they do add more complexity than they remove.