Request Pipeline

Inquiries that have not been assigned to anyone and/or have not received an allocation to begin. We have at least 7 status’ a request can be in; received, reviewed, awaiting allocation, awaiting ci integration, awaiting job configuration, cleared, complete. When a request has been sent to OpenLab team, it will stay in received until a team member has communicated with requester. Once reviewed, if no CI integration is needed, status will move to incubation, if CI integration is needed, CI and job status’ listed will be used until cleared. Requests will stay listed here until at least 14 days after they have been cleared. Cleared means that the agreed upon output has been or is being provided to the OpenLab team and readily available public consumption.

Requested by Project Focus Area Status
Mohammed Naser
Application Ecosystem
Awaiting job configuration
Gilles Dubreil
OpenStack SDKs
Awaiting job configuration
Lingxian Kong
Integration
Awaiting resource allocation
Pablo Iranzo Gómez
Operational Tooling
Awaiting resource allocation
Marco Voelz
PaaS
Awaiting CI integration
Gilles Dubreil
OpenStack SDKs
Awaiting CI integration
Monty Taylor
OpenStack SDKs
Awaiting CI integration
Dmitry Tantsur
OpenStack SDKs
Awaiting CI integration

Infrastructure Utilization

Availability and utilization information about the underlying infrastructure; we are currently reporting monthly aggregating on a weekly basis while working on tools to automate reporting.

Note: 1 VM is equal to 8 vCPUs, 8G RAM, and 80G Disk. Dedicated and Baremetal Servers vary in number of CPUs, RAM, and Disk but meet and exceed the minimum 8 vCPU, 8G RAM, and 80G Disk unless specifically noted otherwise.

Supporting Organizations

irc

twitter

github

© 2018 OpenLab | All rights reserved.

Close Menu

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 some ways to 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. Fill out the form to get in touch with a governance team member.

Supporting Organizations

How OpenLab Works

As developer John Doe of Widgets, Inc. you want to test …; 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.