Fix unit tests to detect import failures

This commit adds onto the existing unit test which simply runs
'testr list-tests' to run discovery on tempest. This is done to ensure
that from a bare tempest repo with the requirements all present we can
actually import and list all the tests. However, there wasn't a check
of the return code. Historically this has been an issue with discovery
failing so adding a check to enforce it moving forward should prevent
it from slipping back in. Part of this is to also fix the test so that
it runs discovery on the correct test suite.

In order to make the unit test pass a config dependency in the
scenario test test_basic_server_ops during the testscenarios call in
load_tests had to be removed. Instead if there is a configuration
error raised while running load tests on this module instead of
failing it will just return the base test class. This is fine
because the test itself will fail on the same configuration
dependencies that load_tests is, however it won't happen silently
during discovery anymore.

Change-Id: Ie74c020de7c9c27adc4ff68dddbae5d4481d1224
Delete console negative tests

These autogenerated tests are wrong in at least 2 ways, one is
assumptions about when servers are available, and the other a schema
which makes assumptions about the resource end points that are
provably wrong when you look at the Nova code (which is unchanged for
2 years).

It's not clear there is any value generated from these tests, suggest
to delete them.

Related-Bug: #1392860

Change-Id: I4822546f73055e307017960bd470333c81cdea01
skip test_server_cfn_init as the failure rate is too high

Change-Id: I9a102bdd06fc8d3eb94fc3437c1cab3cfc121b88
Related-Bug: #1374175
Update README.rst for generating sample conf file

Change-Id: Ifff6664242ed7d1b96555eb7fb2d1d26a87b5ffa
Adds doc for public_router_id in tempest.conf

Inexperienced users keep configuring this value even though it is kept for
legacy reasons only

Change-Id: Ib22b6c7f7a69736c6f9ab0c4349bd1374ab5afef
Adds test for deleting external network with floatingIPs

The attached neutron bug causes server to hang when deleting external network
that still has a floating IP in it.
This test should recreate the bug, and verify it is fixed

Closes-Bug: #1374573

Change-Id: Ib7d8dcbb4485e87a49cb008ace37c81f6b06a32c
Enable cinder v2 api for volume hosts

To run v2 api for volume hosts, volume_hosts_v2_client
is added for volume hosts.

Partially implements: blueprint cinder-v2-api-tests

Change-Id: I6a34f401ea8defabbdf1fc83b2769e02444c2a9e
Merge "Update README.rst for generating sample conf file"
Merge "Adds doc for public_router_id in tempest.conf"
Merge "Fix unit tests to detect import failures"
Merge "Delete console negative tests"
Merge "Enable cinder v2 api for volume hosts"
Merge "skip test_server_cfn_init as the failure rate is too high"
Merge "Adds test for deleting external network with floatingIPs"
Merge branch 'master' of https://github.com/openstack/tempest