History

Patrick East 9b434d1117 Add tempest tests for Consistency Groups 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>		2016-08-29 11:23:51 -07:00
..
api	Add tempest tests for Consistency Groups	2016-08-29 11:23:51 -07:00
scenario	Move and rename tempest_tests to cinder/tests/tempest	2016-05-03 17:55:20 +00:00
services	Add tempest tests for Consistency Groups	2016-08-29 11:23:51 -07:00
README.rst	Move and rename tempest_tests to cinder/tests/tempest	2016-05-03 17:55:20 +00:00
__init__.py	Move and rename tempest_tests to cinder/tests/tempest	2016-05-03 17:55:20 +00:00
cinder_clients.py	Add tempest tests for Consistency Groups	2016-08-29 11:23:51 -07:00
config.py	Add tempest tests for Consistency Groups	2016-08-29 11:23:51 -07:00
plugin.py	Add tempest tests for Consistency Groups	2016-08-29 11:23:51 -07:00

README.rst

Tempest Integration for Cinder

This directory contains additional Cinder tempest tests.

See the tempest plugin docs for information on using it: http://docs.openstack.org/developer/tempest/plugin.html#using-plugins

To run all tests from this plugin, install cinder into your environment. Then from the tempest directory run:

$ tox -e all-plugin -- volume

It is expected that Cinder third party CI's use the all-plugin tox environment above for all test runs. Developers can also use this locally to perform more extensive testing.

Any typical devstack instance should be able to run all Cinder plugin tests. For completeness, here is an example of a devstack local.conf that should work. Update backend information to fit your environment.

[[local|localrc]]
VIRT_DRIVER=libvirt
ADMIN_PASSWORD=secret
SERVICE_TOKEN=$ADMIN_PASSWORD
MYSQL_PASSWORD=$ADMIN_PASSWORD
RABBIT_PASSWORD=$ADMIN_PASSWORD
SERVICE_PASSWORD=$ADMIN_PASSWORD
SCREEN_LOGDIR=/opt/stack/screen-logs
LOGFILE=$DEST/logs/stack.sh.log
LOGDAYS=2
SYSLOG=False
LOG_COLOR=False
RECLONE=yes
ENABLED_SERVICES=c-api,c-sch,c-vol,cinder,dstat,g-api,g-reg,key,mysql,
                 n-api,n-cond,n-cpu,n-crt,n-net,n-sch,rabbit,tempest
CINDER_ENABLED_BACKENDS=lvmdriver-1
CINDER_DEFAULT_VOLUME_TYPE=lvmdriver-1
CINDER_SECURE_DELETE=False
TEMPEST_ENABLED_BACKENDS=lvmdriver-1
TEMPEST_VOLUME_DRIVER=lvmdriver-1
TEMPEST_VOLUME_VENDOR="Open Source"
TEMPEST_STORAGE_PROTOCOL=iSCSI
LIBVIRT_FIREWALL_DRIVER=nova.virt.firewall.NoopFirewallDriver
VIRT_DRIVER=libvirt
ACTIVE_TIMEOUT=120
BOOT_TIMEOUT=120
ASSOCIATE_TIMEOUT=120
TERMINATE_TIMEOUT=120


[[post-config|$CINDER_CONF]]
[DEFAULT]
[lvmdriver-1]
volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver
volume_group=stack-volumes-1
volume_backend_name=lvmdriver-1``