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=Testing in openstack-dev/ci-sandbox to find workaround for [https://bugs.launchpad.net/tempest/+bug/1437328 issue #1437328] . }} | + | |status=Testing in openstack-dev/ci-sandbox to find workaround for [https://bugs.launchpad.net/tempest/+bug/1437328 issue #1437328] . Other issues have been solved. Currently running 295 tests (11 skipped, 12 failed because of the referenced issue) }} |
Revision as of 14:10, 27 March 2015
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: Testing in openstack-dev/ci-sandbox to find workaround for issue #1437328 . Other issues have been solved. Currently running 295 tests (11 skipped, 12 failed because of the referenced issue) |