Difference between revisions of "ThirdPartySystems/Quobyte CI"
(Status update) |
(Updated Cinder CI state to reporting.) |
||
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, Nova, Manila | |programs=Cinder, Nova, Manila | ||
− | |status= | + | |status=Reporting in Cinder and Sandbox projects<br> |
− | + | The Cinder driver currently contains a bug [https://bugs.launchpad.net/cinder/+bug/1438603 #1438603] that we're solving now. | |
<br> | <br> | ||
These bugs that where found by Quobyte CI so far: | These bugs that where found by Quobyte CI so far: |
Revision as of 07:18, 8 July 2015
Gerrit Account: quobyteci | |
Contact Information: silvan@quobyte.com, bjoern@quobyte.com, felix@quobyte.com, kaisers @ IRC | |
Intent: Test Cinder, Nova and Manila 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, Nova, Manila | |
Current Status: Reporting in Cinder and Sandbox projects The Cinder driver currently contains a bug #1438603 that we're solving now.
|