QA - OpenStack
Page Discussion View source History Print/export
Create a book
Download as PDF
Printable version
Tools
Page information
Permanent link
Special pages
Related changes
What links here
Create account
Log in
Log in / create account with OpenID
English
Home
Software
User Stories
Community
Profile
Blog
Wiki
Documentation
Jump to:
navigation
search
QA
Contents
Project Team Definition
How to add new Project under QA program
Feature Proposal & Design discussions
3.1
QA Specification
3.1.1
QA Specs Core Team
Releases Process
Meetings
Projects
7.1
Tempest
7.1.1
Tempest Core Team
7.2
DevStack
7.2.1
Devstack Core Team
7.2.2
Mission Statement
7.2.3
Description
7.3
Grenade
7.3.1
Grenade Core Team
7.4
Hacking
7.4.1
Hacking Core Team
7.5
os-testr
7.5.1
OS Testr Core Team
7.6
Stackviz
7.6.1
Stackviz Core Team
7.7
coverage2sql
7.7.1
Coverage2sql Core Team
7.8
OS Performance Tools
7.8.1
OS Performance Tools Core Team
7.9
Bashate
7.9.1
Bashate Core Team
7.10
Devstack Plugin Container
7.10.1
Devstack Plugin Container Core Team
7.11
Devstack Plugin Ceph
7.11.1
Devstack Plugin Ceph Core Team
7.12
Devstack Plugin Open Cas
7.12.1
Devstack Plugin Open Cas Core Team
7.13
Devstack Plugin NFS
7.13.1
Devstack Plugin NFS Core Team
7.14
Devstack Tools
7.14.1
Devstack Tools Core Team
7.15
Devstack Vagrant
7.15.1
Devstack Vagrant Core Team
7.16
Eslint Config Openstack
7.16.1
Eslint Config Openstack Core Team
7.17
Karma Subunit Reporter
7.17.1
Karma Subunit Reporter Core Team
7.18
Tempest Stress
7.18.1
Tempest Stress Core Team
7.19
Tempest Plugin Cookiecutter
7.19.1
Tempest Plugin Cookiecutter Core Team
7.20
Devstack Plugin Cookiecutter
7.20.1
Devstack Plugin Cookiecutter Core Team
7.21
Whitebox Tempest Plugin
7.21.1
Whitebox Tempest Plugin Core Team
7.22
Tempest-lib (RETIRED)
7.23
Openstack Health (RETIRED)
7.23.1
Openstack Health Core Team
7.24
Patrole (RETIRED)
7.24.1
Patrole Core Team
Project liaisons
QA (Quality Assurance) is an official OpenStack project team.
Official Title:
OpenStack Quality Assurance
PTL:
Martin Kopec (kopecmartin)
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.
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.
Example:
https://review.opendev.org/#/c/656890/
Once Spec is merged then follow this
process
to add your project under QA via OpenStack Governance
https://review.opendev.org/#/c/714478/
https://review.opendev.org/#/c/714480/
Any feature for any of the QA projects which need design discussions can be done via proposing the spec in qa-specs repository. Refer
qa-specs-process
for details.
Not all features need QA spec, to know that if your proposal needs QA spec please feel free to reach out to QA team in #openstack-qa IRC channel or
Source code
https://opendev.org/openstack/qa-specs
Along with the release of few projects as per the release team process, QA needs to do some extra steps during OpenStack release to set up the infra for in DevStack and Grenade.
The complete process for project releases and QA responsibilities are documented here:
QA/releases
IRC Channel: #openstack-qa on OFTC
Email:
The QA project team has a weekly IRC meeting, for more details see:
Meetings/QATeamMeeting
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.
https://opendev.org/openstack/tempest/
Reviews
https://review.opendev.org/q/project:openstack/tempest+status:open
Bug tracker
https://bugs.launchpad.net/tempest
Feature tracker
https://blueprints.launchpad.net/tempest
https://docs.openstack.org/tempest/latest//
As of 19Aug2014 'DevStack is part of the
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.
Source Code
https://opendev.org/openstack/devstack
https://review.opendev.org/q/project:openstack/devstack+status:open
https://bugs.launchpad.net/devstack
https://blueprints.launchpad.net/devstack
Developer Documentation
https://docs.openstack.org/devstack/latest/
For more information see:
https://opendev.org/openstack/grenade
https://review.opendev.org/q/project:openstack/grenade+status:open
https://bugs.launchpad.net/grenade
https://blueprints.launchpad.net/grenade
https://docs.openstack.org/grenade/latest
https://opendev.org/openstack/hacking
https://review.opendev.org/q/project:openstack/hacking+status:open
https://bugs.launchpad.net/hacking
https://blueprints.launchpad.net/hacking
https://docs.openstack.org/hacking/latest
https://opendev.org/openstack/os-testr/
https://review.opendev.org/q/project:openstack/os-testr+status:open
https://bugs.launchpad.net/os-testr
https://blueprints.launchpad.net/os-testr
https://docs.openstack.org/os-testr/latest/
https://opendev.org/openstack/stackviz/
https://review.opendev.org/q/project:openstack/stackviz+status:open
https://docs.openstack.org/stackviz/latest/
https://opendev.org/openstack/coverage2sql
https://review.opendev.org/q/project:openstack/coverage2sql+status:open
https://bugs.launchpad.net/coverage2sql
https://blueprints.launchpad.net/coverage2sql
https://docs.openstack.org/coverage2sql/latest//
https://opendev.org/openstack/os-performance-tools/
https://review.opendev.org/q/project:openstack/os-performance-tools+status:open
https://docs.openstack.org/os-performance-tools/latest/
https://opendev.org/openstack/bashate
https://review.opendev.org/q/project:openstack/bashate+status:open
https://docs.openstack.org/bashate/latest/
https://opendev.org/openstack/devstack-plugin-container
https://review.opendev.org/q/project:openstack/devstack-plugin-container+status:open
https://opendev.org/openstack/devstack-plugin-ceph
https://review.opendev.org/q/project:openstack/devstack-plugin-ceph+status:open
https://bugs.launchpad.net/devstack-plugin-ceph
https://blueprints.launchpad.net/devstack-plugin-ceph
https://docs.openstack.org/devstack-plugin-ceph/latest/
https://opendev.org/openstack/devstack-plugin-open-cas
https://review.opendev.org/q/project:openstack/devstack-plugin-open-cas+status:open
https://opendev.org/openstack/devstack-plugin-nfs
https://review.opendev.org/q/project:openstack/devstack-plugin-nfs+status:open
https://bugs.launchpad.net/devstack-plugin-nfs
https://blueprints.launchpad.net/devstack-plugin-nfs
https://docs.openstack.org/devstack-plugin-nfs/latest/
https://opendev.org/openstack/devstack-tools
https://review.opendev.org/q/project:openstack/devstack-tools+status:open
https://docs.openstack.org/devstack-tools/latest/
https://opendev.org/openstack/devstack-vagrant
https://review.opendev.org/q/project:openstack/devstack-vagrant+status:open
https://opendev.org/openstack/eslint-config-openstack
https://review.opendev.org/q/project:openstack/eslint-config-openstack+status:open
https://bugs.launchpad.net/eslint-config-openstack
https://blueprints.launchpad.net/eslint-config-openstack
https://opendev.org/openstack/karma-subunit-reporter
https://review.opendev.org/q/project:openstack/karma-subunit-reporter+status:open
https://opendev.org/openstack/tempest-stress
https://review.opendev.org/q/project:openstack/tempest-stress+status:open
https://docs.openstack.org/tempest-stress/latest/
https://opendev.org/openstack/tempest-plugin-cookiecutter/
https://review.opendev.org/q/project:openstack/tempest-plugin-cookiecutter+status:open
https://opendev.org/openstack/devstack-plugin-cookiecutter
https://review.opendev.org/q/project:openstack/devstack-plugin-cookiecutter+status:open
https://opendev.org/openstack/whitebox-tempest-plugin
https://review.opendev.org/q/project:openstack/whitebox-tempest-plugin+status:open
https://storyboard.openstack.org/#!/project/1162
NA
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
After several years of deprecation, this project got retired (April 6th 2022) after an agreement on Zed PTG:
https://etherpad.opendev.org/p/qa-zed-ptg
https://opendev.org/openstack/openstack-health/
https://review.opendev.org/q/project:openstack/openstack-health+status:open
https://bugs.launchpad.net/openstack-health
https://blueprints.launchpad.net/openstack-health
https://opendev.org/openstack/patrole/
https://review.opendev.org/q/project:openstack/patrole+status:open
Bug & Feature tracker
https://storyboard.openstack.org/#!/project/1040
https://docs.openstack.org/patrole/latest/
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
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 and Wallaby release
Martin Kopec (kopecmartin): Xena, Yoga, Zed and Antelope
Retrieved from "
https://wiki.openstack.org/w/index.php?title=QA&oldid=183034
Category
Horizontal Team
Privacy policy
About OpenStack
Disclaimers