Difference between revisions of "ThirdPartySystems/Quobyte CI"
(Added information on how to recheck on Quobyte CI systems. Moved here from Quobyte wiki page.) |
(updated manila ci state) |
||
| Line 13: | Line 13: | ||
<br> | <br> | ||
Bugs/changes affecting the Manila CI results: | Bugs/changes affecting the Manila CI results: | ||
| + | * Quobyte Manila CI is currently being reworked to use the Manila Tempest plugin, meanwhile tests are false negative thorought. | ||
* Security Service issue (possibly setup issue) [https://bugs.launchpad.net/manila/+bug/1479497 #1479497] | * Security Service issue (possibly setup issue) [https://bugs.launchpad.net/manila/+bug/1479497 #1479497] | ||
* Issue with shared network not found [https://bugs.launchpad.net/manila/+bug/1479499 #1479499] | * Issue with shared network not found [https://bugs.launchpad.net/manila/+bug/1479499 #1479499] | ||
Revision as of 13:34, 17 September 2015
| 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 installations testing nova and manila changes with their respective tempest tests on a quobyte backend based setup. Working on openstack/nova and openstack/manila CI setups. | |
| OpenStack Programs: Cinder, Manila, (Nova to be added) | |
| Current Status: Reporting in Cinder project (stable), testing in Manila and in sandbox project (currently unstable) Bugs/changes affecting the Cinder CI results:
|
Rechecking Quobyte CI Systems
All CI systems run by Quobyte support rechecking by adding the comment 'recheck <ci-instance-name>' to the patch set in question. For example:
recheck cinder-quobyteci-dsvm-volume
This command works even if there's no previous report from the given CI instance for the given patch set.
