Jump to: navigation, search

Difference between revisions of "Cinder/tested-3rdParty-drivers"

(Testing for drivers merged *BEFORE* Kilo release: updating which tests need to be ran)
(Testing for *NEW* drivers in Kilo release)
Line 2: Line 2:
=== Testing for *NEW* drivers in Kilo release ===
=== 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.'''
New drivers need to have a CI by the end of Kilo, or it will be removed in the L release.
=== Testing for drivers merged *BEFORE* Kilo release ===
=== Testing for drivers merged *BEFORE* Kilo release ===

Revision as of 00:03, 19 December 2014

Driver Testing

Testing for *NEW* drivers in Kilo release

New drivers need to have a CI by the end of Kilo, or it will be removed 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 volume tests against their storage device for every Cinder commit, and provides feedback in to Gerrit.

Third Party CI Requirements

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.


  • Join Third Party Meeting
  • Reach out to IRC nicks DuncanT or asselin on Freenode #openstack-cinder.


What tests do I use?

Use the OpenStack integration test suite Tempest. Specifically you only need to run the volume tests. These tests can be started with the following command from a Tempest repo:

/path/to/tempest/tools/pretty_tox.sh volume

How do I configure DevStack so my Driver Passes Tempest?


# These options define  expected driver capabilities

# These options allow you to specify a branch other than "master" be used
CINDER_REPO=https://review.openstack.org/openstack/cinder<br />

# Disable security groups entirely


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.