Difference between revisions of "ThirdPartySystems/Quobyte CI"
(Update on CI migration statuses) |
(Added Quobyte Nova 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, OS-Brick, Manila | + | |intent=Test Cinder, OS-Brick, Manila, and 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. | + | |method= sos-ci monitors Gerrit event stream and triggers test builds, ansible based installation in DevStack instances, running volume related tempest tests vs. Cinder, OS-Brick, and Nova changes. Similar installation testing manila changes with their respective tempest tests on a quobyte backend based setup. |
− | |programs=Cinder, OS-Brick, Manila, | + | |programs=Cinder, OS-Brick, Manila, and Nova |
− | |status=Reporting in Cinder project ( | + | |status=Reporting in Cinder project (stable), OS-Brick project (down), Manila project (stable), and Nova project (experimental) |
<br> | <br> | ||
Bugs/changes affecting the Cinder CI results: | Bugs/changes affecting the Cinder CI results: | ||
Line 13: | Line 13: | ||
<br> | <br> | ||
Bugs/changes affecting the Manila CI results: | 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 | + | * CI skips several groups of non-implemented Manila feature test groups (snapshots, etc.) based on the Manila tempest tests config parameters. |
<br> | <br> | ||
Bugs/changes affecting the OS-Brick CI results: | Bugs/changes affecting the OS-Brick CI results: | ||
* OS-Brick CI is currently down due to service migration. Cinder CI migration is complete, OS-Brick CI will follow up shortly (2016-01-29) | * OS-Brick CI is currently down due to service migration. Cinder CI migration is complete, OS-Brick CI will follow up shortly (2016-01-29) | ||
+ | <br> | ||
+ | Bugs/changes affecting the Nova CI results: | ||
+ | * Currently running experimental tests. | ||
}} | }} |
Revision as of 14:51, 29 January 2016
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 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, OS-Brick, and Nova changes. Similar installation testing manila changes with their respective tempest tests on a quobyte backend based setup. | |
OpenStack Programs: Cinder, OS-Brick, Manila, and Nova | |
Current Status: Reporting in Cinder project (stable), OS-Brick project (down), Manila project (stable), and Nova project (experimental)
|
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.