Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/Quobyte CI"

(Updated Quobyte CI status)
m
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=Down for updates and DevStack issue debugging, reporting  in ci-sandbox during this outage. }}
+
|status=Down for updates, widening test coverage and DevStack issue debugging, reporting  in ci-sandbox during this outage. }}

Revision as of 07:57, 27 March 2015

3rd party system: Quobyte CI
Gerrit Account: quobyteci
Contact Information: openstack-ci-external@quobyte.com, kaisers in 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: Down for updates, widening test coverage and DevStack issue debugging, reporting in ci-sandbox during this outage.