Open Infrastructure Testing
E2E integration and testing continues to be a challenge for Open Source ecosystems. We are collaborating across communities to create shared architecture and tools.
OpenStack + Kubernetes
OpenStack and Kubernetes are two of the largest Open Source projects for Open Infrastructure. We are working to help strengthen their integration.
OpenStack SDKs
OpenStack SDKs are fundamental to building OpenStack native applications. We provide free space for growth, stability, and maintenance.


OpenLab’s mission is to enable the testing, reporting, and development of tools and applications for hybrid and multi-cloud environments.

OpenLab fulfills its mission by providing a ready to use and easy to replicate platform that tests the usability, reliability, and resiliency of hybrid and multi-cloud tooling.

Clouds live in a rich software stack, with key elements “below” and “above”. When you consider Open Source points of integration the options are staggering. Open Infrastructure is about helping to reduce the complexity.

By building on highly successful, mature, and rapidly emerging tools and applications that originate with cloud platform providers (OSVs), independent software vendors (ISVs), cloud service providers (CSPs), enterprise end-user IT, OpenLab is uniquely positioned as a key component to Open Infrastructure.

Download the complete overview deck here.

How OpenLab Works

As developer John Doe of Widgets, Inc. you want to test out your new widget-orchestrator. What can you expect:

  1. Fill out the “Let’s Get Started” form.
  2. You will receive a confirmation and someone will contact you within 24 hours.
  3. OpenLab team will work out the specifics of what you need and what is expected to complete your testing if anything is not clear on the form.
  4. Once the details of testing have been completed your request will go into the backlog which can be seen here.
  5. When your testing configuration is available you will receive relevant login credentials.
  6. Once testing is completed you will receive an email for feedback on the process and request for timeline for result reporting if not already done.

Support OpenLab

Working on the problems that are common and span across different communities in an isolated manner is not beneficial for the ecosystem since what is done by each of these communities individually can potentially be shared by others who are working on solving similar problems. This includes but is not limited to improved way of working, alignment on best practices, and tooling re-use.

Here are ways you can support OpenLab:

  • Additional infrastructure (commodity hardware, cloud resources, etc)
  • Engineering support (developers, project management, software support)
  • QA, QE, and test (unit, integration, e2e, scenario) builders.
  • Software/application and tooling integrations
  • Operations support
Support is not limited to only the items listed above and we are open for additional assistance and guidance. If you would like to get started supporting OpenLab, it is best to send an email to to get in touch with a governance team member. If you have testing scenarios simply fill out the “Let’s Get Started” form.

Current Architecture

We use a number of software components with the following being the cornerstones of the system:


Zuul is a program that drives continuous integration, delivery, and deployment systems with a focus on project gating and interrelated projects. Zuul is part of an effort to streamline Zuul into an easier-to-use system that scales better and is more flexible.

  • Scale to thousands of projects
  • Multi-tenant friendly
  • Easier to express complex scenarios in layout
  • Continuous Deployment
  • Private installations using external test resources


Nodepool is a system for launching single-use test nodes on demand based on images built with cached data. It is designed to work with any OpenStack based cloud, and is part of a suite of tools that form a comprehensive test system, including Zuul.

  • More useful for non virtual nodes
  • More efficient for multi-node tests
  • Remove the need for long-running slaves

OpenStack Cloud

By utilizing these components OpenLab is not limited to one OpenStack deployment and/or version and with resources provided by supporting organizations whether public, private, hybrid, or community cloud we have a vast array of scenarios and configurations that can be created for testing multi-cloud applications and tools.


Any organization or individual is welcome to participate and contribute to this program. OpenLab adheres, where applicable, to the four opens ( ) as its guiding principles.

OpenLab is in its forming stages and as an active participating member, an organization is expected to: either (1) provide hardware resources to support OpenLab activities; OR (2) provide engineering resources to support OpenLab activities.

We also welcome guidance and assistance regarding architecture, additional projects, resource allocation and/or utilization, and more.

Open Lab is governed by the appointed representatives from participating member companies and the OpenStack Foundation, collectively known as “Governance Board”.

The Governance Board responsiblities include (but are not limited to):

  • Oversight of the overall charter, mission, and objectives of OpenLab
  • Identify and define deliverables for each release cadence
  • Clear communication of OpenLab with the developer and user communities
  • Ensure sufficient resources (hardware and engineering resources) to support OpenLab activities
  • Elect a chair to manage day-to-day operations and meetings
  • Manage OpenLab memberships

Current Board Members:

Name Organization
Melvin Hillsman Huawei Technologies Co. Ltd
Dr Yih Leong Sun Intel Corporation
Chris Hoge OpenStack Foundation

Supporting Organizations


Weekly meeting agenda and notes: