Easier to read console output

The console output was hard to read because it was displayed on one
line as a string as part of a tuple. Split them up so it's readable.

Change-Id: Ieb59909802a587027c4691924e70923c61476591
Clean up tox.ini and make tempest and unit test distinct

This commit creates a separate base env for tempest tests and
tempest's unit tests. However, to keep the same interface the tempest
env is setup by overloading the testenv using substitution from a
common base section.

As part of this internal reorganization in the tox.ini several other
things are cleaned up or removed. Usless or duplicate job definitions
are removed. The unit tests are switched to pretty_tox. Previously
they were run without any output which made it difficult to figure out
exactly what was running. Additionally, this removes the unnecessary
regex filter on the unit test job. The unit tests use a different
discovery path so there is no need to also filter it on the same path
this will allow the use of more specific regexes with tox to filter
tests.

Change-Id: I996d81dec2739bbe907f5fe87a335994c01697b3
Fix duplicate ref of volume_types_client in vol tests

tempest/api/volume/base.py admin base tests class has duplicate
reference for 'volume_types_client'. Tests use mix of both.

This patch fix this duplicate reference and modify tests accordingly

Closes-Bug: #1379106

Change-Id: I016d364ad792c97d1dce12ee7da225ebe0a690f6
Don't use a specific arg list for stress in tox.ini

Callers should be able to specify the arguments.

Change-Id: I1d60af5e5300ff91ce3777ac46df655442098013
Add a server console-log test with unlimited length

Now server console-log API is important for debugging gate problems
and the API is called with unlimited length for debugging. However,
there is not the API test with unlimited length.
This patch adds the test.

Change-Id: I5a35f086deddfcd54e995cb1156699592d1daea6
Make rest_client.wait_for_resource_deletion timeout error more specific

Currently the timeout error message just says 'Failed to delete resource
within the required time' and includes the test class/test case, but
when we're seeing all volume-related tests racing with a delete hang, we
can't fingerprint an elastic-recheck query on the various test
class/test case names, and there aren't errors in the cinder logs.

The best thing we have to fingerprint is the timeout message, but we
need it to be more specific to the type of resource rather than any
resource type that might have timed out during a delete operation.

This is similar to the is_resource_deleted method in the various rest
clients in that the concrete implementations of the base class return
their specific type so we can use that in the timeout message.

Closes-Bug: #1380712

Change-Id: I36b49c59daa95219c4377d1e207ea4a0c8cf8782
Merge "Add a server console-log test with unlimited length"
Merge "Fix duplicate ref of volume_types_client in vol tests"
Merge "Easier to read console output"
Merge "Clean up tox.ini and make tempest and unit test distinct"
Merge "Don't use a specific arg list for stress in tox.ini"
Merge "Make rest_client.wait_for_resource_deletion timeout error more specific"
Merge branch 'master' of https://github.com/openstack/tempest