ThirdPartySystems/Quobyte CI

**3rd party system:** Quobyte CI
Gerrit Account: quobyteci
Contact Information: silvan@quobyte.com (kaisers@IRC), robert@quobyte.com (mrlarkin@IRC), felix@quobyte.com, bjoern@quobyte.com,
Intent: Test Cinder, Manila (and later Nova) changes against Quobyte drivers
Structure: ansible installed sos-ci setup with some modifications
Method: sos-ci monitors Gerrit event stream and triggers test builds, ansible based installation in DevStack instances, running volume related tempest tests vs. cinder. Similar installation testing manila changes with their respective tempest tests on a quobyte backend based setup.
OpenStack Programs: Cinder, Manila, (Nova to be added)
Current Status: Reporting in Cinder project (stable) and Manila project (stable) Bugs/changes affecting the Cinder CI results: Cinder CI is currently hitting a new issue and failing to build devstack instances for testing, we're investigating (2015-11-05 09:30 CET) CI explicitely skips encrypted volume test as proposed on the mailing list, affects 1 test. Bugs/changes affecting the Manila CI results: CI skips several groups of non-implemented Manila feature test groups (snapshots, etc.) based on the Manila tempest tests config parameters

All CI systems run by Quobyte support rechecking by adding the comment 'run <ci-instance-name>' to the patch set in question. For example:

run cinder-quobyteci-dsvm-volume

This command works even if there's no previous report from the given CI instance for the given patch set.