Instead of registering new groups we can reuse already registered
groups in tempest/config.py.
Changes should be made to the following groups:
a) service_available_group - We don't need this group in plugin code
because it is already being registered in tempest code and service
availability is being checked for in the /tempest/api/volume/base.py
and the test cases in plugin code inherits this base.py
b) cinder group - Instead of registering a new cinder group for plugin
tests we can add plugin specific configuration options in the existing
volume group as the same conf object from tempest is being passed on
to the plugin
Change-Id: Ie0ca52ec389c581ca47db3e9bbb0793a2bb47fdf
Closes-Bug: #1626575
These tempest tests add coverage for all the API's related to
consistency groups in Cinder. They were originally proposed
for upstream tempest in https://review.openstack.org/#/c/252213/
but were not a good fit since they aren't supported by the
reference driver. They have been modified to work as part
of the in-tree tempest plugins for Cinder now.
The tests are behind a new config option for tempest, which
in turn is part of a new config group called 'cinder'. This
was added to avoid any collisions with the 'volume-features-enabled'
or 'volume' groups already in the upstream tempest tests.
To enable them set the following in tempest.conf
[cinder]
consistency_group = True
Then make sure to run tempest with the 'all-plugin' tox environment.
Don't forget to update policy.json to allow for CG API's to be called..
Change-Id: I772ea13ca156e71620d722eee476f222a8653831
Co-Authored-By: Xing Yang <xing.yang@emc.com>
To avoid conflicts, it needs to be done and
the subdirs 'api' and 'scenario' directly under
the cinder/tests/tempest directory
Closes-Bug: #1577016
Change-Id: I5b8d1411e0917ecb7e70eb5a6b139d75437ba032
Nishant Kumar