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
Reviewed: https:/ /review. openstack. org/375808 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=4e1643ea5b1 3867c0c5adebca2 6112a8c804e4b6
Committed: https:/
Submitter: Jenkins
Branch: master
commit 4e1643ea5b13867 c0c5adebca26112 a8c804e4b6
Author: Nishant Kumar <email address hidden>
Date: Fri Sep 23 20:11:58 2016 +0530
Reuse already existing groups in tempest plugin
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 api/volume/ base.py
because it is already being registered in tempest code and service
availability is being checked for in the /tempest/
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: Ie0ca52ec389c58 1ca47db3e9bbb07 93a2bb47fdf
Closes-Bug: #1626575