Jump to: navigation, search


Revision as of 23:30, 18 April 2020 by Ghanshyam Mann (talk | contribs)

QA (Quality Assurance) is an official OpenStack project team.

Project Team Definition

Official Title: OpenStack Quality Assurance

PTL: Masayuki Igawa (masayukig)

Mission Statement:
Develop, maintain, and initiate tools and plans to ensure the upstream stability and quality of OpenStack, and its release readiness at any point during the release cycle.


The OpenStack QA project team is made of multiple projects which each run independently towards the goals of the project team. Each project maintains a separate core team based on who provides reviews in those projects.

For the purposes of voting on QA Project Team activities, anyone that's core on any of the projects gets a vote.


Tempest Core Team

Source code http://git.openstack.org/cgit/openstack/tempest/
Bug tracker https://bugs.launchpad.net/tempest
Feature tracker https://blueprints.launchpad.net/tempest
Developer Documentation http://docs.openstack.org/developer/tempest/

Test removal procedure:


Tempest-lib (Deprecated)

Source code http://git.openstack.org/cgit/openstack/tempest-lib/
Bug tracker https://bugs.launchpad.net/tempest
Feature tracker https://blueprints.launchpad.net/tempest
Developer Documentation http://docs.openstack.org/developer/tempest-lib/

Tempest -> Tempest-lib migration

To migrate a module from tempest into tempest-lib follow these instructions: tempest-lib-migration

Tempest Plugin Cookiecutter

Tempest Plugin Cookiecutter Core Team

Source code http://git.openstack.org/cgit/openstack/tempest-plugin-cookiecutter
Bug tracker https://bugs.launchpad.net/tempest


Grenade Core Team

For more information see: Grenade

Source code http://git.openstack.org/cgit/openstack-dev/grenade/
Bug tracker https://bugs.launchpad.net/grenade


Devstack Core Team

As of 19Aug2014 'DevStack is part of the QA program.

Mission Statement

DevStack's mission is to provide and maintain tools used for the installation of the central OpenStack services from source (git repository master, or specific branches) suitable for development and operational testing. It also demonstrates and documents examples of configuring and running services as well as command line client usage.


DevStack is an opinionated script to quickly create an OpenStack development environment. It can also be used to demonstrate starting/running OpenStack services and provide examples of using them from a command line. The example exercises were fleshed out beyond simple examples and became useful as a quick sanity check for the OpenStack installation. That sanity check became the basis for the Gerrit gate tests for all OpenStack checkins and continues in that role until Tempest takes over. These remain as the driving priorities for ongoing DevStack development.

DevStack is not and has never been intended to be a general OpenStack installer. It has evolved to support a large number of configuration options and alternative platforms and support services. However, that evolution has grown well beyond what was originally intended and unfortunately many of the configuration combinations are rarely, if ever, tested.

The simplest way to try DevStack is to run script https://github.com/makelinux/devstack-install-on-iso, which automatically installs Ubuntu in VM and DevStack without any manual configuration.

Documentation http://docs.openstack.org/developer/devstack/
GitHub https://github.com/openstack-dev/devstack
Bug tracker https://bugs.launchpad.net//devstack

Devstack Plugin Cookiecutter

Devstack Plugin Cookiecutter Core Team

Source code http://git.openstack.org/cgit/openstack-dev/devstack-plugin-cookiecutter
Bug tracker https://bugs.launchpad.net/devstack

Devstack Vagrant

Devstack Vagrant Core Team

Source code http://git.openstack.org/cgit/openstack-dev/devstack-vagrant
Bug tracker https://bugs.launchpad.net/devstack


Hacking Core Team

Source code http://git.openstack.org/cgit/openstack-dev/hacking
Bug tracker https://bugs.launchpad.net/hacking
Documentation http://docs.openstack.org/developer/hacking


Bashate Core Team

Source code http://git.openstack.org/cgit/openstack-dev/bashate


OS Testr Core Team

Source code http://git.openstack.org/cgit/openstack/os-testr
Bug tracker https://bugs.launchpad.net/os-testr
Documentation http://docs.openstack.org/developer/os-testr

Openstack Health

Openstack Health Core Team

Source code http://git.openstack.org/cgit/openstack/openstack-health
Bug tracker https://bugs.launchpad.net/openstack-health


Stackviz Core Team

Source code http://git.openstack.org/cgit/openstack/stackviz

OS Performance Tools

OS Performance Tools Core Team

Source code http://git.openstack.org/cgit/openstack/os-performance-tools


Patrole Core Team

Source code http://git.openstack.org/cgit/openstack/patrole
Bug tracker https://bugs.launchpad.net/patrole

Project liaisons

To make cross project communication easier and fill gaps in domain expertise between projects and QA (bidirectionally) each project designates a liaison for handling integration issues. See QAProjectLiaisons.

Feature proposals

To propose a feature to any of the QA projects you first need to file a spec in qa-specs. The entire process is outlined here: qa-specs-process

Pushing Releases

The process for pushing project releases is documented here: QA/releases


IRC Channel: #openstack-qa on freenode


The QA project team has a weekly IRC meeting, for more details see:



  • Previous PTLs
    • Sean Dague (sdague), ..Havana and Icehouse release
    • Matthew Treinish (mtreinish): Juno, Kilo, Liberty and Mitaka releases
    • Ken'ichi Ohmichi (oomichi): Newton and Ocata releases
    • Andrea Frittoli (andreaf): Pike and Queens releases
    • Ghanshyam Mann (gmann): Rocky, Stein, Train and Ussuri release
    • Masayuki Igawa (masayukig): Victoria Release