The work consists of three parts:
* Allow for bootstrapping remotely,
this makes it possible to run the tests
on e.g. OSX with VirtualBox installed
* Make bootstrapping a fully automated process
where the manifests can be generated by the tests
and the tests can call the bootstrapper directly in python
* Create a framework wherein instances can be booted up
using the bootstrapped images and subsequently tested
This is the first step in the effort of combining all documentation about
bootstrap-vz into sphinx while still being able to access it from github
(github can parse rst as well)
If all you want is to test an image or product and to achieve this
you need to generate several images a day, you will end up with
lots of AMI's and snapshots that have no use in the end of the day.
This commit adds the new boolean manifest option "deregister_ami"
that, if True, deletes the recently created AMI and snapshot. So, the
final result will be only the running instance, nothing else.
Instead of storing just its ID.
This gives quick access to the recently created instance, which
allows us to simplify the code that needs to fetch the instance object
every time it was necessary.
Use the function waituntil() available in the integration-test branch
to simplify the code that retrieves the IP of the instance.
A 'TODO' note was also added to remember us to merge this function
once it gets merged.
It adds the ability to automatically launch an EC2 instance
after AMI registration.
It has no mandatory configuration, only optional ones, like
instance type, security groups, etc. They should be documented in
later documentation patches.
Documentation says about that, but it's not implemented like that.
If the command to be executed is an array with just one string, it's
likely the user passed the entire command inside the string.
Plus, they benefit from shell expansion of wildcards like '*'.
