OpenStack SDKs

Below you will see status cells that represent 6 key metrics we are targeting for each OpenStack SDK:

  1. CI Integration
  2. Unit Testing
  3. Integration/E2E/Functional Testing
  4. Engineering Activity
  5. User Activity
  6. Versioning
  7. SDK Certification*

SDKs are the foundation for building OpenStack native applications and tools. We will continue to work with SDKs which is why they are not part of the pipeline but rather listed prominently with key metrics clearly visible.

It is worth also noting that these SDKs are not required to utilize OpenLab and where we have reached out to an SDK community and they have decided to not use OpenLab we will clearly note their decision; a in CI Integration cell indicates this.

*SDK Certification is still in concept phase within the community so all SDKs currently cannot meet this metric.


 Complete  Will Not Complete  Not Applicable  Researching Health Discussing
Danger – Warning –
Good – Great –


 SDK  Language  CI Integration  Unit Testing  Integration/E2E/Functional Testing Engineering Activity  User Activity  Versioning  SDK Certification
 gophercloud  Go            
misty  Ruby              
 python-openstacksdk  Python              
 openstack4j  Java              
 jclouds  Java              
 libcloud  Python          
 goose  Go          
 fog-openstack  Ruby              
 pkgcloud  JavaScript            

Supporting Organizations




© 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.