Difference between revisions of "ThirdPartySystems/Quobyte CI"
m |
(Added contact information) |
||
| Line 1: | Line 1: | ||
{{ThirdPartySystemInfo|name=Quobyte CI | {{ThirdPartySystemInfo|name=Quobyte CI | ||
|account=quobyteci | |account=quobyteci | ||
| − | |contact= silvan@quobyte.com (kaisers@IRC) | + | |contact= primary contact: silvan@quobyte.com (kaisers@IRC); backup contacts (in order): robert@quobyte.com (mrlarkin@IRC), felix@quobyte.com, bjoern@quobyte.com, |
|intent=Test Cinder, OS-Brick, Manila, and Nova changes against [[Quobyte]] drivers | |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] | ||
Revision as of 07:58, 28 July 2016
| Gerrit Account: quobyteci | |
| Contact Information: primary contact: silvan@quobyte.com (kaisers@IRC); backup contacts (in order): 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: enabled |
Contents
Status Details
Reporting in Cinder project (stable), OS-Brick project (stable), Manila project (stable), and Nova project (stable)
Bugs/changes affecting the Cinder CI results:
- Cinder CI explicitely skips encrypted volume test as proposed on the mailing list, affects 1 test.
- Cinder CI runs with basic apparmor protection as a workaround for #1598833 until that bug is solved
Bugs/changes affecting the OS-Brick CI results:
- OS-Brick CI runs with basic apparmor protection as a workaround for #1598833 until that bug is solved
Bugs/changes affecting the Nova CI results:
- Nova CI runs with basic apparmor protection as a workaround for #1598833 until that bug is solved
Bugs/changes affecting the Manila CI results:
- Manila CI skips several groups of non-implemented Manila feature test groups (snapshots, etc.) based on the Manila tempest tests config parameters.
- Manila CI produces random false negatives due to bug #1560345. A driver update to remedy this is in preparation at change #345219.
Rechecking Quobyte CI Systems
Quobyte CI systems trigger rechecks in two scenarios:
- Jenkins recheck: Every time Jenkins comments +1 on a change the corresponding Quobyte CI is triggered. This includes initial check runs as well as recheck triggered Jenkins re-runs
- CI specific recheck (see below)
Quobyte CI Specific Rechecks
All CI systems run by Quobyte support rechecking by adding the comment 'run <ci-instance-name>' to the patch set in question.
Recheck trigger: "run <ci-instance-name>"
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.
