Tempest plugin for Cinder project.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
OpenDev Sysadmins 6ab522516f OpenDev Migration Patch 1 month ago
cinder_tempest_plugin Add metadata to snapshot for revert test 3 months ago
.coveragerc Apply cookiecutter to newly split project 1 year ago
.gitignore Apply cookiecutter to newly split project 1 year ago
.gitreview OpenDev Migration Patch 1 month ago
.mailmap Apply cookiecutter to newly split project 1 year ago
.testr.conf Apply cookiecutter to newly split project 1 year ago
.zuul.yaml OpenDev Migration Patch 1 month ago
CONTRIBUTING.rst Clean up some initial repo creation boilerplate 1 year ago
HACKING.rst Update the documentation link for doc migration 1 year ago
LICENSE Apply cookiecutter to newly split project 1 year ago
README.rst Clean up some initial repo creation boilerplate 1 year ago
babel.cfg Apply cookiecutter to newly split project 1 year ago
bindep.txt Clean up some initial repo creation boilerplate 1 year ago
requirements.txt Sync requirements for cinder-tempest-plugin 1 year ago
setup.cfg Change openstack-dev to openstack-discuss 5 months ago
setup.py Updated from global requirements 1 year ago
tempest_blacklist.txt Added cinder tempest plugin zuulv3 jobs to execute tempest 1 year ago
test-requirements.txt Updated from global requirements 1 year ago
tox.ini fix tox python3 overrides 8 months ago

README.rst

Tempest Integration for Cinder

This directory contains additional Cinder tempest tests.

See the tempest plugin docs for information on using it: https://docs.openstack.org/tempest/latest/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
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_VOLUME_CLEAR=none
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