So that we can run the shorter set of unittests if desired.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

I've found that it's useful to check just the autotest installation steps
with a single VM with increased resources, mainly memory.

First 1G of memory is too little to do things like compiling the GWT client,
2G is OK, but 4G is preferrable. On most development machines (mine included),
starting two VMs with 2G or 4G is usually not a good idea.

To set this single VM (server only) mode, simply set the "vms" parameter to
a single (server) VM name.

Also, be a lot more generous about the installation timeout, as based on my
experience, things like downloading GWT and the git trees can take a long
time (YMMV).
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Since the next branch does not exist anymore.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Since autotest has been helping to test the Linux virt
technologies, why not let them help to test autotest?

This is an early preview of a test suite designed
to do functional regression testing of autotest
using vms, as well as execute both the unittests
and the pylint checkers on it, and very basic
initial verification of the autotest server features.

It wouldn't be possible without the many cleanups
in static checking run made during the past couple
of weeks, now we're to a point where autotest master
can give useful static checking reports.

Hopefully this code will be refactored, and coverage
expanded.

Changes from v2:
 * Far better error checking and progress
   verification.

Changes from v1:
 * Fix stupid mistake from one of the rebases I've
   made (client ip acquisition was made too early,
   resulting in a VMIPAddressMissingError right
   in the beginning of the test).
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>