Difference between revisions of "ThirdPartySystems/Quobyte CI"
(Outage status update.) |
(Updating ci state) |
||
Line 9: | Line 9: | ||
<br> | <br> | ||
''CI systems are currently down due to upgrade issues (2016-03-04). We're doing a new RDO based setup (2016-03-10).'' | ''CI systems are currently down due to upgrade issues (2016-03-04). We're doing a new RDO based setup (2016-03-10).'' | ||
+ | * RDO setup complete, adapting CIs to new setup currently (2016-03-14) | ||
<br> | <br> | ||
<br> | <br> |
Revision as of 07:18, 15 March 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 due to migration), Manila project (stable), and Nova 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.
CI Volume Logs prior to 2016-01-29
Log files for volume jobs run prior to 2016-01-29 can be found at http://osci4.ext/old_logs/logs/ .