ZVMDriver/zVM-CI
Contents
Overview
This is the IBM z/VM CI status page.
The z/VM CI cloud currently runs OpenStack Mitaka release. Most devstack-gate jobs run on Ubuntu Xenial single use slaves.
Logs are uploaded to Softlayer's virtual log server and expire in 1 month. The test jobs are using devstack-gate to setup devstack and run the Tempest test suite.
This is how z/VM CI system is running.
Using an example of two tests servers running tempest tests each testing a different openstack patch, this diagram shows additional detail of the bottom layer of the preceding diagram. Each test server assumes it has a dedicated z/VM system that its OpenStack nova plugins are using. The test server is an OpenStack controller; a devstack installation running on the reference platform (x86 Ubuntu Linux) installed prior to running the tempest tests. Each test servers OpenStack nova plugin for z/VM are configured to talk to some z/VM system; depending upon how z/VM scales in practice, each worker might really have its own dedicated z/VM back end, or each worker might actually be sharing a z/VM instance as shown here. Each worker's plugin can be configured to use a different prefix when creating virtual servers on z/VM, so they will not directly collide; there might still be indirect interference in truly shared components like xCAT, SMAPI, and DirMaint. The wire flows use the xCAT REST API, not the OpenStack REST APIs, since there are no OpenStack services running natively on z/VM in this picture.
Contact
- IRC: Laurene, huangshilin
- Email: zvmosci@linux.vnet.ibm.com
Current Status
- nova, non-reporting,
System Status
| Start | End | Description |
|---|
Projects Tested
As z/VM CI has not been granted report access, current test status for all tested projects can be seen at Zuul Testing Report.
The report is compiled form zuul logs and Jenkins log, and is updated periodically. It might include aborted or otherwise terminated builds. In each tested project status table, the first column is linked to each code patch, second column is linked to test logs.
Non-reporting
- Nova
Skipped Tests
There are currently a few skipped tests, see test run logs for details.
Known Issues
None
