Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/Quobyte CI"

m
(Updated & extended contact information)
Line 1: Line 1:
 
{{ThirdPartySystemInfo|name=Quobyte CI
 
{{ThirdPartySystemInfo|name=Quobyte CI
 
|account=quobyteci
 
|account=quobyteci
|contact=openstack-ci-external@quobyte.com, kaisers in IRC
+
|contact=silvan@quobyte.com, bjoern@quobyte.com, felix@quobyte.com, kaisers @ IRC
 
|intent=Test Cinder, Nova and Manila changes against [[Quobyte]] drivers
 
|intent=Test Cinder, Nova and Manila changes against [[Quobyte]] drivers
 
|structure=ansible installed [https://github.com/j-griffith/sos-ci sos-ci] setup with some  [https://github.com/casusbelli/sos-ci modifications]
 
|structure=ansible installed [https://github.com/j-griffith/sos-ci sos-ci] setup with some  [https://github.com/casusbelli/sos-ci modifications]

Revision as of 07:52, 31 March 2015

3rd party system: Quobyte CI
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 openstack-dev/ci-sandbox.

Currently running 304 tests, 11 skipped by tempest marked bugs, 3 failing. These three failing tests are currently skipped while debugging them:

  • VolumesV2SnapshotTestJSON.test_snapshot_create_with_volume_in_use
  • VolumesV1SnapshotTestJSON.test_snapshot_create_with_volume_in_use
  • test_minimum_basic_scenario .