- 1 Driver Testing
- 1.1 Testing for *NEW* drivers in Kilo release
- 1.2 Testing for drivers merged *BEFORE* Kilo release
- 1.3 Third Party CI Requirements
- 1.4 Existing CI Solutions
- 1.5 Questions
- 1.6 FAQ
Testing for *NEW* drivers in Kilo release
We've implemented a simple wrapper around the tempest volume.api tests at https://github.com/openstack-dev/devstack/tree/master/driver_certs . The process currently is for each vendor to run this test against their backend driver in their own environment. The wrapper is very simple, it just does a fresh clone of the cinder and tempest repos and restarts services, then runs the tempest volume.api tagged tests in the tempest suites and collects the output to a temporary log file. Once you have a log file, create a cinder launchpad bug and attach the log to it. Post a comment to your driver's gerrit review with a link to the bug. NOTE: Your driver needs to have a CI by the end of Kilo, or we will target your driver for removal in the L release.
Testing for drivers merged *BEFORE* Kilo release
Deadline for drivers merged before Kilo to have a CI is end of k-2 (5th of Feb 2015). Failure will result in driver removal in the Kilo release. - Discussion regarding this here
The Cinder community (and other OpenStack projects) have agreed that if a vendor wishes to submit a driver for their particular storage device that said vendor should also be required to set up a third party CI system in their lab which runs tempest-dsvm-full against their device for every Cinder commit, and provides feedback in to Gerrit.
Third Party CI Requirements
- See the official Third Party Testing wiki.
Existing CI Solutions
- Puppet modules for deploying OpenStack CI
- Git repo
- Fork of Jay Pipe's external test repo and more up-to-date.
- Simple OpenStack Continuous Integration (sos-ci)
- Git repo
- Builds Devstack virtual machines with Ansible.
- Jay Pipe's external testing series
- Join Third Party Meeting
- Reach out to IRC nicks DuncanT or asselin on Freenode #openstack-cinder.
What tests do I use?
How do I configure DevStack so my Driver Passes Tempest?
[[local|localrc]] ADMIN_PASSWORD=password MYSQL_PASSWORD=password RABBIT_PASSWORD=password SERVICE_PASSWORD=password SERVICE_TOKEN=password # These options define expected driver capabilities TEMPEST_VOLUME_DRIVER=foo TEMPEST_VOLUME_VENDOR="Foo Inc" TEMPEST_STORAGE_PROTOCOL=iSCSI # These options allow you to specify a branch other than "master" be used CINDER_REPO=https://review.openstack.org/openstack/cinder<br /> CINDER_BRANCH=refs/changes/83/72183/4 # Disable security groups entirely Q_USE_SECGROUP=False LIBVIRT_FIREWALL_DRIVER=nova.virt.firewall.NoopFirewallDriver CINDER_SECURE_DELETE=False [[post-config|$CINDER_CONF]] volume_driver=cinder.volume.drivers.foo.FooDriver
When thirdparty CI voting will be required?
Once third party CI's become more common and stable, we'll revisit the subject. For now you can review the discussion on the decision.