Difference between revisions of "ThirdPartySystems/Quobyte CI"

Revision as of 09:19, 25 March 2015

**3rd party system:** Name of 3rd party system
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.
OpenStack Programs: Cinder, Nova, Manila
Current Status: Reporting in openstack/cinder (non-voting). Working on openstack/nova and openstack/manila CI setups.

@@ Line 3: / Line 3: @@
 |contact=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
+|structure=ansible installed [https://github.com/j-griffith/sos-ci sos-ci] setup with some  [https://github.com/casusbelli/sos-ci modifications]
-|method= ansible based installation, running volume related tempest tests vs. cinder, nova and manila changes on a quobyte backend based setup.
+|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.
 |programs=Cinder, Nova, Manila
 |status=Reporting in openstack/cinder (non-voting). Working on openstack/nova and openstack/manila CI setups.}}