the 1.5 version has issues

abbey.py will launch an instance into a VPC, run ansible on it
and monitor it for updates using an SQS queue.  At the end of
the ansible run it will create an AMI and terminate the instance.

If you tell supervisorctl to update and a process autostarts
sometimes you will get ERROR (already started) if you immediately
ensure the process is started afterwards.

* ora user wasn't created during initial configuration run
* removing forked ec2 module
* updating ec2.py and ec2.ini to latest ansible repo version

This rolls the ec2 elb management script into a module.
Now if an ELB is added or removed "changed" will return True/False
so you can tell if any action was taken based on the coloring of
the response (yellow/green).

By default ansible will load libs in library/ which means
you do not need to specify a module path if you are invoking
ansible from the playbooks/ dir.

Added some comments to the rolling example