- 1 Project Team Definition
- 2 How to add new Project under QA program
- 3 Design discussions
- 4 Projects
- 4.1 Tempest
- 4.2 Patrole
- 4.3 DevStack
- 4.4 Grenade
- 4.5 Hacking
- 4.6 os-testr
- 4.7 Openstack Health
- 4.8 Stackviz
- 4.9 coverage2sql
- 4.10 OS Performance Tools
- 4.11 Bashate
- 4.12 Devstack Plugin Container
- 4.13 Devstack Plugin Ceph
- 4.14 Devstack Plugin Open Cas
- 4.15 Devstack Plugin NFS
- 4.16 Devstack Tools
- 4.17 Devstack Vagrant
- 4.18 Eslint Config Openstack
- 4.19 Karma Subunit Reporter
- 4.20 Tempest Stress
- 4.21 Tempest Plugin Cookiecutter
- 4.22 Devstack Plugin Cookiecutter
- 4.23 Tempest-lib (Deprecated)
- 5 Project liaisons
- 6 Feature proposals
- 7 Community
- 8 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.
How to add new Project under QA program
Any new tool or project contributing towards the QA mission can be added under QA program. Below are the steps to do that.
- Discuss the idea on #openstack-qa channel or openstack-discuss ML with [qa] tag in the subject line.
- You need to propose a QA spec with all the details.
- Once Spec is merged then follow this process to add your project under QA via OpenStack Governance
Any feature for any of the QA projects which need design discussions can be done qa-specs repository.
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.
|Bug & Feature tracker||https://storyboard.openstack.org/#!/project/1040|
As of 19Aug2014 'DevStack is part of the QA program.
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.
For more information see: Grenade
OS Performance Tools
Devstack Plugin Container
Devstack Plugin Ceph
Devstack Plugin Open Cas
Devstack Plugin NFS
Eslint Config Openstack
Karma Subunit Reporter
Tempest Plugin Cookiecutter
Devstack Plugin Cookiecutter
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
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.
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
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