News for hackers. Stuff that matters.
Re:ShutIt – Automation framework for programmers by throwanem on Sunday July 10, 2016 @11:09AM (#12065824)
I agree that YAML's a mess, but not requiring a client-side agent is a pretty big win in my experience, and to be honest none of the configuration management systems I've used has had a particularly comfortable specification language.
Re:ShutIt – Automation framework for programmers by zwischenzug on Sunday July 10, 2016 @11:13AM (#12065839)
I've learned the hard way that CM is a Hard Problem. Any solution is going to be a trade-off, which is why there is space for multiple solutions.
Re:ShutIt – Automation framework for programmers by dozzie on Sunday July 10, 2016 @11:26AM (#12065890)
Oh, but Ansible does require a client-side agent. It just happens that the agent is the same one as you use for interactive purposes, which is another big no-go in the long run (when you let your servers' users configure SSH server to some extent, and then you need to make sure they don't cut out your configuration management tool).

Also, configuration management tool should be, apart from downloading configuration from somewhere, independent from any external server/service.

Re:ShutIt – Automation framework for programmers by collyw on Sunday July 10, 2016 @02:32PM (#12066597)
Yes, but is pretty standard. Could you even use a virtual machine without ssh (or an equivalent)?
Re:ShutIt – Automation framework for programmers by dozzie on Sunday July 10, 2016 @04:42PM (#12067180)
As a (somewhat) seasoned sysadmin, I tell you that mixing responsibilities of services is a Bad Idea[tm]. You wouldn't put disk access into your HTTP header handling code, would you? So why do you think overloading an interactive shell with configuration management is a good idea? It doesn't even work well, considering that you need to manage SSH keys, which quickly gets ugly when the number of hosts grows, and then there's the need to re-send configuration for each host that happened to be down or otherwise unreachable at the time of issuing it the first time.

You need a) interactive shell, b) configuration management tool (which works in scheduled batch mode and in "pull" style, not "push" as in Ansible), and c) system for running ad-hoc commands synchronously (this one is "push" style). Yes, all three. Yes, separate, not a weird mix of them. Been there, done that.

Re:ShutIt – Automation framework for programmers by throwanem on Sunday July 10, 2016 @07:08PM (#12067708)
Nobody's saying that Puppet or CFEngine isn't the best solution for a lot of cases, only that there are also cases where Ansible, or something like it, is a better choice.

You seem to have a serious down on the whole concept behind Ansible, and I'm curious why that is. Have you had a bad experience with it? If so, I'd like to hear about it, in order to better inform my own analysis of the tool.

Re:ShutIt – Automation framework for programmers by dozzie on Monday July 11, 2016 @06:24AM (#12070068)
> You seem to have a serious down on the whole concept behind Ansible, and I'm curious why that is.

No, not really. Not on the high-level idea(s). Heck, I've written myself (or at least deployed already-written) tools for what Ansible tries to do: configuration management, synchronous mass running an ad-hoc command on a set of machines, and running a specific, parametrized procedure on a single host. I recognize all these scenarios are important and I want to have tools for each of those, but let the tools do these jobs robustly.

What bothers me is design decisions and architecture of Ansible (and other tools sharing them). The decisions seem sound from far away, but they start leaking once you look closely. Good general tool would be robust for pretty much all the use cases; Ansible is brittle (breaks when you misconfigure sshd_config a little; breaks when you accidentally overwrite SSH keys; can't work if you don't have account with working shell and $HOME; breaks apart when some of the hosts are down; and so on).

Ansible apparently started as a script that automated somebody's workflow (which is a good thing) -- and stayed that way, but now is marketed as a general tool (which is not, but resembles it closely enough to trick many its users into thinking it is).

It all boils down to Ansible still being a quick hack for somebody's specific workflow and me hating buzz around half-assed tools.

> Have you had a bad experience with it? If so, I'd like to hear about it, in order to better inform my own analysis of the tool.

I have so many objections against Ansible (some I mentioned above) that it actually makes more sense to write a separate article about it, but this will take time.

Re:ShutIt – Automation framework for programmers by zwischenzug on Monday July 11, 2016 @06:53AM (#12070179)
> Ansible apparently started as a script that automated somebody's workflow (which is a good thing) -- and stayed that way, but now is marketed as a general tool (which is not, but resembles it closely enough to trick many its users into thinking it is).

I think that's a key critique of many of these things. They start off solving one problem, then eventually become 'enterprise', and the design trade-offs get exposed. This is what I was alluding to above with my trade-offs comment.

Re:ShutIt – Automation framework for programmers by dozzie on Monday July 11, 2016 @08:20AM (#12070500)
Well, CFEngine (especially 3.x, a third rewrite of the same basic idea) does not show these trade-offs. It was designed from the ground up as a general tool based on previous experiences with wide deployments, it (its codebase) did not start as a script for solving some specific problem in some specific workflow.

Puppet has similar history, I believe, as a tool that was written to replace cfengine (2.x) without its shortcomings.

Re:ShutIt – Automation framework for programmers by throwanem on Sunday July 10, 2016 @12:10PM (#12066046)
See your own sibling comment from the ShutIt dev.
Re:ShutIt – Automation framework for programmers by dozzie on Sunday July 10, 2016 @01:37PM (#12066350)
The one that is cutely general and thus at the same time completely agreeable by anybody and totally unactionable? Sure, I've seen it.
Re:ShutIt – Automation framework for programmers by zwischenzug on Sunday July 10, 2016 @02:12PM (#12066510)
Client-side agent is great for some orgs (esp those that need control), but I wanted something that would be more general-purpose (hence using (p)expect).