Difference between revisions of "ThirdPartySystems/Quobyte CI"

Revision as of 07:22, 11 July 2016

**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 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

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:

Currently affected by a bug related to online snapshot test test_snapshot_create_with_volume_in_use, details at #1598833
- Error reason is partially hidden in Nova logs by #1168011.
Currently affected by a permission issue introduced by Change-Id: Ia84579b84105e8ad6146591188a96e847e762c77 monitored in bug #1597644
CI explicitely skips encrypted volume test as proposed on the mailing list, affects 1 test.

Bugs/changes affecting the OS-Brick CI results:

Currently affected by the same bugs as the Cinder CI (see above).
OS-Brick CI is is reporting

Bugs/changes affecting the Nova CI results:

Currently affected by the same bugs as the Cinder CI (see above).
Nova CI is reporting

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

Recheck trigger: "run <ci-instance-name>"

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.

@@ Line 6: / Line 6: @@
 |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, and Nova
-|status=Reporting in Cinder project (stable), OS-Brick project (stable), Manila project (stable), and Nova project (stable)
+|status=enabled}}
+=== Status Details ===
+Reporting in Cinder project (stable), OS-Brick project (stable), Manila project (stable), and Nova project (stable)
 <br>
 Bugs/changes affecting the Cinder CI results:
@@ Line 24: / Line 27: @@
 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 ===
+'''Recheck trigger:''' "run <ci-instance-name>"
 All CI systems run by Quobyte support rechecking by adding the comment 'run <ci-instance-name>' to the patch set in question.
 For example: