Difference between revisions of "Cinder/tested-3rdParty-drivers"
(mentioning new CI deadline and testing required for new drivers in kilo) |
(→Most Recent Results for Icehouse) |
||
| Line 24: | Line 24: | ||
Once third party CI's become more common and stable, we'll revisit the subject. For now you can review the [http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-10-15-16.00.log.html discussion] on the decision. | Once third party CI's become more common and stable, we'll revisit the subject. For now you can review the [http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-10-15-16.00.log.html discussion] on the decision. | ||
| − | === | + | === Results for new Drivers === |
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
! Driver Name !! Pass/Fail !! Link to Log Files !! Date of Test Run | ! Driver Name !! Pass/Fail !! Link to Log Files !! Date of Test Run | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
| Example || Example || Example || Example | | Example || Example || Example || Example | ||
|} | |} | ||
Revision as of 23:15, 2 December 2014
Contents
Driver Testing
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.
The current list of the most recent run of the tests and a link to the resultant log files is included in the table found at the bottom of this wiki page.
Testing for drivers merged before Kilo release
Deadline for drivers merged before Kilo to have a CI is end of k-2 - Discussion regarding this here
To be designated as compatible, a third-party plugin and/or driver code must implement external third party testing. The testing should be Tempest executed against a Devstack build with the proposed code changes. The environment managed by the vendor should be configured to incorporate the plugin and/or driver solution. The OpenStack Infrastructure team has provided details on how to integrate 3rd party testing at:
http://ci.openstack.org/third_party.html
and Tempest can be found at:
https://github.com/openstack/tempest
The Cinder team expects that the third party testing will provide (for now) non-voting results for all changes to any cinder code. In addition, the Cinder team expects that the third party test will also provide non-voting results for all code submissions by the jenkins user. The jenkins user regularly submits requirements changes and the Cinder team hopes to catch any possible regressions as early as possible. More information on drivers, the Cinder CI policy and additional links to setting up a CI system at:
https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver
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.
Results for new Drivers
| Driver Name | Pass/Fail | Link to Log Files | Date of Test Run |
|---|---|---|---|
| Example | Example | Example | Example |
