Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/Quobyte CI"

(Updated recheck command info)
(Updated Manila CI status, now stable)
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. 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.
 
|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.
 
|programs=Cinder, Manila, (Nova to be added)
 
|programs=Cinder, Manila, (Nova to be added)
|status=Reporting in Cinder project (stable), testing in Manila and in sandbox project (currently unstable)<br>
+
|status=Reporting in Cinder project (stable) and Manila project (stable)
 +
<br>
 
Bugs/changes affecting the Cinder CI results:
 
Bugs/changes affecting the Cinder CI results:
  
Line 13: Line 14:
 
<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 thorough.
+
* CI currently runs with a patched backend (fix in preparation) but provides correct results
* Security Service issue (possibly setup issue) [https://bugs.launchpad.net/manila/+bug/1479497 #1479497]
+
* CI skips several groups of non-implemented Manila feature test groups (snapshots, etc.) based on the Manila tempest tests config parameters
* Issue with shared network not found [https://bugs.launchpad.net/manila/+bug/1479499 #1479499]
+
 
 
}}
 
}}
  

Revision as of 10:00, 23 September 2015

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, 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) and Manila project (stable)


Bugs/changes affecting the Cinder CI results:

  • The CI runs with devstack installing Nova from the patch ref of a fix for a Nova bug #1465416 until that fix has merged.
  • CI explicitely skips encrypted volume test as proposed on the mailing list, affects 1 test.


Bugs/changes affecting the Manila CI results:

  • CI currently runs with a patched backend (fix in preparation) but provides correct 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

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.