Jump to: navigation, search

ThirdPartySystems/Quobyte CI

< ThirdPartySystems
Revision as of 12:58, 4 July 2016 by Kaisers (talk | contribs) (Updated on snapshot issue)
3rd party system: Quobyte CI
Gerrit Account: quobyteci
Contact Information: silvan@quobyte.com (kaisers@IRC), robert@quobyte.com (mrlarkin@IRC), felix@quobyte.com, bjoern@quobyte.com,
Intent: Test Cinder, OS-Brick, Manila, and Nova 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, OS-Brick, and Nova changes. Similar installation testing manila changes with their respective tempest tests on a quobyte backend based setup.
OpenStack Programs: Cinder, OS-Brick, Manila, and Nova
Current Status: Reporting in Cinder project (stable), OS-Brick project (stable), Manila project (stable), and Nova project (stable)


Bugs/changes affecting the Cinder CI results:


Bugs/changes affecting the OS-Brick CI results:

  • Currently affected by the same bugs as the Cinder CI (see above).
  • OS-Brick CI is is reporting


Bugs/changes affecting the Nova CI results:

  • Currently affected by the same bugs as the Cinder CI (see above).
  • Nova CI is reporting


Bugs/changes affecting the Manila CI results:

  • CI skips several groups of non-implemented Manila feature test groups (snapshots, etc.) based on the Manila tempest tests config parameters.


Rechecking Quobyte CI Systems

All CI systems run by Quobyte support rechecking by adding the comment 'run <ci-instance-name>' to the patch set in question. For example:

run cinder-quobyteci-dsvm-volume

This command works even if there's no previous report from the given CI instance for the given patch set.

Retrieved from "https://wiki.openstack.org/w/index.php?title=ThirdPartySystems/Quobyte_CI&oldid=127625"