Difference between revisions of "ThirdPartySystems/IBM DB2 CI"

Revision as of 03:23, 16 June 2015

IBM DB2 CI

IBM DB2 CI is a continuous integration for OpenStack running on DB2 backend. With a pipeline, DB2 CI listens to newly created patch sets on review.openstack.org and runs the Tempest test suites on the patch.

In the case of sqlalchemy-migrate, py26 and py27 unit tests are also run.

Current Status

a. Jobs

Enabled and published: cinder

Enabled, not published: Keystone (Reason: needs community's review and agreement.)

Glance CI is enabled but only publishes test result to one patch(167101) (Reason: [bug 1434440])

Nova CI only publish result to in-progress patch 69047

CI for ironic and heat are disabled, because of nova_api db sync failure.

Disabled: Neutron (Reason: neutron subnet-create hangs forever even though the operation succeeds)

b. Infrastructure

For now, we have 30 slaves online for testing. Because we are sharing a Cloud with other users, we sometimes may face environment issues, with each time, we will recheck the CI test to avoid annoying results published.

Triggering Methods

The DB2 CI can be triggered by newly-uploaded patch set, or by leaving a commnand "recheck db2-test" in comments.

Excluded Tests

A small handful of Tempest tests are excluded from run because there are known issues or a specific feature may not be implemented. Information about these tests can be found here.

Issue Tracker

If you got any issues of this IBM DB2 CI, please contact "yanfengxi@cn.ibm.com", or reach irc account "yanfengxi" on channel #openstack-infra.

There are currently some known issues with the ibm-db-sa library running with newer versions of sqlalchemy:

bug 1434440(glance db sync failed when using DB2): https://bugs.launchpad.net/glance/+bug/1434440

 Fix: https://review.openstack.org/#/c/167101/

neutron subnet-create hangs forever.

@@ Line 22: / Line 22: @@
 '''b. Infrastructure'''
-Now, DB2 CI is suffering from so limited hardware resource. Because of this, DB2 CI can not handle so many community patches, which results in the fact that only a few patches got tested.
+For now, we have 30 slaves online for testing. Because we are sharing a Cloud with other users, we sometimes may face environment issues, with each time, we will recheck the CI test to avoid annoying results published.
-To solve this, we are trying to added more clouds in as the slave nodes provider. As we are doing the integration tests for newly-added cloud, the CI publication will be stopped for a while, and will back to normal before 2015/05/16.
 == Triggering Methods ==