QA
Contents
- 1 Project Team Definition
- 2 Projects
- 3 Project liaisons
- 4 Feature proposals
- 5 Community
- 6 History
QA (Quality Assurance) is an official OpenStack project team.
Project Team Definition
Official Title: OpenStack Quality Assurance
PTL: Masayuki Igawa (masayukig)
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.
Projects
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
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 |
Documentation | https://docs.openstack.org/tempest/latest// |
Patrole
Patrole Core Team
Source code | http://git.openstack.org/cgit/openstack/patrole |
Bug & Feature tracker | https://storyboard.openstack.org/#!/project/1040 |
Documentation | https://docs.openstack.org/patrole/latest// |
DevStack
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.
Description
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.
Source Code | https://github.com/openstack-dev/devstack |
Bug tracker | https://bugs.launchpad.net//devstack |
Feature tracker | https://blueprints.launchpad.net/devstack |
Developer Documentation | https://docs.openstack.org/devstack/latest// |
Grenade
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 |
Feature tracker | https://blueprints.launchpad.net/grenade |
Documentation | https://docs.openstack.org/grenade/latest |
Hacking
Hacking Core Team
Source code | http://git.openstack.org/cgit/openstack-dev/hacking |
Bug tracker | https://bugs.launchpad.net/hacking |
Feature tracker | https://blueprints.launchpad.net/hacking |
Documentation | https://docs.openstack.org/hacking/latest |
os-testr
OS Testr Core Team
Source code | http://git.openstack.org/cgit/openstack/os-testr |
Bug tracker | https://bugs.launchpad.net/os-testr |
Feature tracker | https://blueprints.launchpad.net/os-testr |
Documentation | https://docs.openstack.org/os-testr/latest/ |
Openstack Health
Openstack Health Core Team
Source code | http://git.openstack.org/cgit/openstack/openstack-health |
Bug tracker | https://bugs.launchpad.net/openstack-health |
Feature tracker | https://blueprints.launchpad.net/openstack-health |
Stackviz
Stackviz Core Team
Source code | http://git.openstack.org/cgit/openstack/stackviz |
Bug tracker | https://bugs.launchpad.net/tempest |
Feature tracker | https://blueprints.launchpad.net/tempest |
Documentation | https://docs.openstack.org/stackviz/latest/ |
OS Performance Tools
OS Performance Tools Core Team
Source code | http://git.openstack.org/cgit/openstack/os-performance-tools |
Bug tracker | https://bugs.launchpad.net/tempest |
Feature tracker | https://blueprints.launchpad.net/tempest |
Documentation | https://docs.openstack.org/os-performance-tools/latest/ |
Bashate
Bashate Core Team
Source code | http://git.openstack.org/cgit/openstack-dev/bashate |
Bug tracker | https://bugs.launchpad.net/tempest |
Feature tracker | https://blueprints.launchpad.net/tempest |
Documentation | https://docs.openstack.org/bashate/latest/ |
Devstack Vagrant
Devstack Vagrant Core Team
Source code | http://git.openstack.org/cgit/openstack-dev/devstack-vagrant |
Bug tracker | https://bugs.launchpad.net/devstack |
Feature tracker | https://blueprints.launchpad.net/devstack |
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 |
Feature tracker | https://blueprints.launchpad.net/tempest |
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 |
Feature tracker | https://blueprints.launchpad.net/devstack |
Tempest-lib (Deprecated)
As of the 1.0.0 release tempest-lib as a separate repository and project is deprecated. The library now exists as part of the tempest project, all future development will occur there. To use the library for future releases update your imports from tempest_lib to tempest.lib, and add tempest>=10 to your project requirements
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
Community
IRC Channel: #openstack-qa on freenode
Meetings
The QA project team has a weekly IRC meeting, for more details see:
History
- 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