On: Why I left Heroku, and notes on my new AWS setup

[mpdehaan2]

If you are looking for another general purpose orchestrator, I'd suggest taking a look at Ansible - http://ansible.cc/

Disclaimer: I am the primary author.

[stavros → mpdehaan2]

I have tried ansible and love it. I invested the time (a few hours) to get a script working for my stack, and now I have a 70ish line script that will provision a server or VM (with a shared code directory in the VM), from clean installation to the codebase up and running in its production state, in one command.

New project? I just copy the script, change a few variables (names and packages it needs), and I get deployment for free.

[23david → stavros]

Sounds interesting. Any possibility that you could anonymize the script and paste a link to a gist of it? would be interesting to see some real-world Ansible examples.

[stavros → 23david]

Sure: http://pastebin.com/KPrm3Zky

It could use variables a bit more, I think, but there were a few bugs with expanding them, so I didn't use them. I'll fix them later on, though.

[23david → stavros]

amazing. that example explains how it works better than 200 pages of documentation :-)

thx!

[stavros → 23david]

You're welcome, examples are pretty useful for this sort of thing. Plus, after you have a base to work off, it's trivial to extend.

I'll put this up in a post on my blog, maybe it'll help others as well.

[23david → mpdehaan2]

I never thought of Ansible for orchestration particularly, but that sounds interesting! The current orchestration support in saltstack is somewhat limited, so it would be neat to check out.

Are people using Ansible to replace or manage fabric scripts? I'd like to figure out some way to limit the spread of one-off fabric scripts (reminds me too much of bash script proliferation) and it'd be great to get everything under one roof.