Difference between revisions of "ThirdPartySystems/Quobyte CI"
(Updated Manila CI status) |
(Updated Cinder CI hitting a sporadically rising issue.) |
||
| Line 12: | Line 12: | ||
* The CI runs with devstack installing Nova from the patch ref of a fix for a Nova bug [https://bugs.launchpad.net/nova/+bug/1465416 #1465416] until that fix has merged. | * The CI runs with devstack installing Nova from the patch ref of a fix for a Nova bug [https://bugs.launchpad.net/nova/+bug/1465416 #1465416] until that fix has merged. | ||
* CI explicitely skips encrypted volume test as proposed on [http://lists.openstack.org/pipermail/openstack-dev/2015-July/069099.html the mailing list], affects 1 test. | * CI explicitely skips encrypted volume test as proposed on [http://lists.openstack.org/pipermail/openstack-dev/2015-July/069099.html the mailing list], affects 1 test. | ||
| + | * The CI sporadically hits an UnicodeError in Cinder / NovaClient as described in [https://bugs.launchpad.net/cinder/+bug/1498559 #1498559] | ||
<br> | <br> | ||
Bugs/changes affecting the Manila CI results: | Bugs/changes affecting the Manila CI results: | ||
Revision as of 06:17, 30 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 installation testing manila changes with their respective tempest tests on a quobyte backend based setup. | |
| OpenStack Programs: Cinder, Manila, (Nova to be added) | |
| Current Status: Reporting in Cinder project (stable) and Manila project (stable)
|
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.
