The tests removed here are now available in the Tempest plugin inside
sahara-tests.
Also remove few test dependencies which are not needed anymore (as a result
of this code removal but also of previous changes).
Change-Id: I6394cd0ed01d7799ba303fd36e4777018de16854
This commit removes the usage of the services decorators from the
tempest plugin tests. That decorator is an internal interface and
not meant for external consumption, and is now causing failures
because of recent tempest changes. Plugins should only use documented
stable interfaces. [1]
Also the use of the decorator here actually adds nothing to the tests.
They do 2 things, add a test attr to filter by service and add a skip
check on the service availability. However both of these are already
done, data_processing is already part of the test_id so filtering
will just work and the skip check for sahara is baked into the base
test class. So using this decorator does nothing except break the
plugin.
[1] http://docs.openstack.org/developer/tempest/plugin.html#stable-tempest-apis-plugins-may-use
Change-Id: I45587d065c1b7b7f28feb29e8845f8f0f8405b8c
Tempest-lib has been reintegrated into tempest (as code, but it still provides
a stable API). The old library is still available, but tempest tests are
failing because when sahara is installed and exports the scenario tests
for python clients, python-lib is not installed (it's correcly in
test-requirements.txt, not requirements.txt), and tempest does not
install tempest-lib anymore. Hence, fix the tests to use the new
official location.
Change-Id: Iaded03ee387b4a0bbabb7bfe9e54d38e010d9c4f
Use the Tempest plugin interface for python client tests (which
are already tempest-based) instead of copying the tests inside
the tempest tree.
Inspired by the same type of change applied to Manila,
see Ie5ed64a6777ed1acf8dd56522c26705ae897596d
Depends-On: I06f1e13207cc6d661c078c4c4cf1ae7974ecf3da
Change-Id: I6073a528413aefd96882179a1eb8bbe715c6417b