Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/Quobyte CI"

(manila ci is back to normal)
(added Quobyte os-brick CI)
Line 2: Line 2:
 
|account=quobyteci
 
|account=quobyteci
 
|contact= silvan@quobyte.com (kaisers@IRC), robert@quobyte.com (mrlarkin@IRC), felix@quobyte.com, bjoern@quobyte.com,
 
|contact= 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
+
|intent=Test Cinder, OS-Brick, Manila (and later Nova) changes against [[Quobyte]] drivers
 
|structure=ansible installed [https://github.com/j-griffith/sos-ci sos-ci] setup with some  [https://github.com/casusbelli/sos-ci modifications]
 
|structure=ansible installed [https://github.com/j-griffith/sos-ci sos-ci] setup with some  [https://github.com/casusbelli/sos-ci 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.
+
|method= sos-ci monitors Gerrit event stream and triggers test builds, ansible based installation in DevStack instances, running volume related tempest tests vs. cinder and os-brick. Similar installation testing manila changes with their respective tempest tests on a quobyte backend based setup.
|programs=Cinder, Manila, (Nova to be added)
+
|programs=Cinder, OS-Brick, Manila, (Nova to be added)
|status=Reporting in Cinder project (stable) and Manila project (stable)
+
|status=Reporting in Cinder project (stable), OS-Brick project (experimental) and Manila project (stable)
 
<br>
 
<br>
 
Bugs/changes affecting the Cinder CI results:
 
Bugs/changes affecting the Cinder CI results:

Revision as of 11:25, 1 December 2015

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, OS-Brick, 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 and os-brick. Similar installation testing manila changes with their respective tempest tests on a quobyte backend based setup.
OpenStack Programs: Cinder, OS-Brick, Manila, (Nova to be added)
Current Status: Reporting in Cinder project (stable), OS-Brick project (experimental) and Manila project (stable)


Bugs/changes affecting the Cinder CI results:

  • 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


Rechecking Quobyte CI Systems

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.