[ceejayoz]

You can use Ansible to create an AMI to get the best of both worlds - fast provisioning, plus the ability to make new AMIs in a repeatable, self-documenting manner. You're arguing configuration management is "error prone", but I've found it a lot less error prone than other methods. If something doesn't install right I can blow away the whole thing rather than trying to un-break a destroyed install.

If your Ansible scripts are in Ruby you've done something very odd, and if they're messy it's your own fault. Mine are pretty clean, and once built they work the same way for subsequent runs.

[Sssnake]

>If your Ansible scripts are in Ruby

The popular options are in ruby. Just because you use a less popular one that is written in python doesn't change the main point.

[ceejayoz]

Ansible itself is Python, and the docs all use Python examples. I've yet to come across a Ruby one...

[Sssnake]

Why are you replying if you can't be bothered to read?

[ceejayoz]

The post you replied to was about Ansible (which is pretty popular).

If you're intending to bash Puppet/Chef, why are you doing it in response to someone mentioning how handy Ansible is?

[Sssnake]

http://www.nizkor.org/features/fallacies/straw-man.html

[ceejayoz]

http://en.wikipedia.org/wiki/Non_sequitur_(logic)