News for hackers. Stuff that matters.
Re:Configuration (mis)management or why I hate puppet, ansib... by PaulHoule on Friday August 05, 2016 @05:21PM (#12235823)
The Unix equivalent of your Powershell scripts is bash scripts. You can go pretty far that way.

I have looked at the many configuration management tools out there and I think they do add more complexity than they remove.

Re:Configuration (mis)management or why I hate puppet, ansib... by CaptSpify on Friday August 05, 2016 @06:33PM (#12236150)
I've used puppet, chef, ansible, and probably others that I can't remember. I eventually just gave up and wrote everything in bash-scripts, because it's quicker, easier and simpler.

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.

Re:Configuration (mis)management or why I hate puppet, ansib... by dozzie on Friday August 05, 2016 @07:30PM (#12236364)
Only if your environment is cluster-like set of clones of a golden image, dutifully kept up-to-date with it. If you happen to have two or more roles for the servers, shell scripts start tearing at their seams.
Re:Configuration (mis)management or why I hate puppet, ansib... by CaptSpify on Friday August 05, 2016 @11:02PM (#12236823)
> 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. 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.

Re:Configuration (mis)management or why I hate puppet, ansib... by dozzie on Saturday August 06, 2016 @04:52AM (#12237547)
> That's kind of what I mean by homogeneous.

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.

Re:Configuration (mis)management or why I hate puppet, ansib... by CaptSpify on Saturday August 06, 2016 @04:09PM (#12239671)
I think our definition of homogeneous might be different then. I have file-servers, web-servers, app-servers, etc, and I would consider my environment homogeneous. I use the same base-os, and I can reuse the same scripts for each type of server because of how modular my system is. For my setup, just using shell scripts works much simpler and easier. But I'm also not advocating that shell-scripts will work for everyone. For many situations, a full-fledged config-mgmt system is the better solution. I've just never been in one.
Re:Configuration (mis)management or why I hate puppet, ansib... by dozzie on Saturday August 06, 2016 @05:33PM (#12240031)
> I think our definition of homogeneous might be different then.

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.

Re:Configuration (mis)management or why I hate puppet, ansib... by placebo on Friday August 05, 2016 @05:43PM (#12235922)
Agree. Occam's razor isn't always adhered to in the software world. Often a tool that is more hyped will be used instead of a tool that is more suitable, but I'd be careful to blame the tool - the problem is usually the choice to use it in a scenarios that doesn't require it at present (and probably not in the future)
Re:Configuration (mis)management or why I hate puppet, ansib... by daenney on Friday August 05, 2016 @05:48PM (#12235943)
This, a million times this. Ansible, Chef, Puppet, cfengine and a bunch of others serve certain use cases. Unfortunately, once you give someone a tool it quickly turns into a hammer, then a jackhammer, a crowbar, sonic screwdriver, fork lift and a lot more.

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.

Re:Configuration (mis)management or why I hate puppet, ansib... by seanp2k2 on Saturday August 06, 2016 @04:51PM (#12239864)
I feel the same way. I've invented a config management system which executes an environment-specific shell script based on some metadata about the instance it's running on. Most of these config scripts are <50 lines and contain no logic, just "copy this config file, mount this volume, grab this secret, restart this service". Works really well for our limited use-case.

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.

Re:Configuration (mis)management or why I hate puppet, ansib... by Spooky23 on Friday August 05, 2016 @05:58PM (#12235997)
When tool implementations fail, it's usually because the business process wasn't well defined.

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.