Difference between revisions of "QA"
Haim Ateya (talk | contribs) (→Knowledge Base) |
(→Projects) |
||
(28 intermediate revisions by 11 users not shown) | |||
Line 1: | Line 1: | ||
__TOC__ | __TOC__ | ||
− | QA is an official OpenStack | + | QA is an official OpenStack project team. |
− | == | + | == Project Team Definition == |
'''Official Title:''' OpenStack Quality Assurance<br /> | '''Official Title:''' OpenStack Quality Assurance<br /> | ||
− | '''PTL:''' | + | '''PTL:''' Ghanshyam Mann (gmann)<br /> |
'''Mission Statement:''' <blockquote> 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. | '''Mission Statement:''' <blockquote> 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. | ||
Line 14: | Line 14: | ||
== Projects == | == Projects == | ||
− | The OpenStack QA | + | 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 | + | For the purposes of voting on QA Project Team activities, anyone that's core on any of the projects gets a vote. |
− | === | + | === Tempest === |
+ | {| border="1" cellpadding="2" | ||
+ | | 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/ | ||
+ | |} | ||
− | |||
− | === Tempest === | + | ====Test removal procedure:==== |
+ | [http://docs.openstack.org/developer/tempest/test-removal.html Tempest-test-removal] | ||
+ | |||
+ | === Tempest-lib (Deprecated) === | ||
+ | {| border="1" cellpadding="2" | ||
+ | | 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=== | ||
+ | {| border="1" cellpadding="2" | ||
+ | | Source code | ||
+ | | http://git.openstack.org/cgit/openstack/tempest-plugin-cookiecutter | ||
+ | |- | ||
+ | | Bug tracker | ||
+ | | https://bugs.launchpad.net/tempest | ||
+ | |} | ||
=== Grenade === | === Grenade === | ||
+ | For more information see: [[Grenade]] | ||
+ | {| border="1" cellpadding="2" | ||
+ | | Source code | ||
+ | | http://git.openstack.org/cgit/openstack-dev/grenade/ | ||
+ | |- | ||
+ | | Bug tracker | ||
+ | | https://bugs.launchpad.net/grenade | ||
+ | |} | ||
+ | |||
+ | === DevStack === | ||
+ | For more information see: [[DevStack]] | ||
+ | |||
+ | {| border="1" cellpadding="2" cellspacing="0" | ||
+ | | '''Documentation''' | ||
+ | | http://docs.openstack.org/developer/devstack/ | ||
+ | |- | ||
+ | | '''GitHub''' | ||
+ | | https://github.com/openstack-dev/devstack | ||
+ | |- | ||
+ | | '''Bug tracker''' | ||
+ | | https://bugs.launchpad.net//devstack | ||
+ | |} | ||
+ | |||
+ | ===Devstack Plugin Cookiecutter=== | ||
+ | {| border="1" cellpadding="2" | ||
+ | | Source code | ||
+ | | http://git.openstack.org/cgit/openstack-dev/devstack-plugin-cookiecutter | ||
+ | |- | ||
+ | | Bug tracker | ||
+ | | https://bugs.launchpad.net/devstack | ||
+ | |} | ||
+ | |||
+ | ===Devstack Vagrant=== | ||
+ | {| border="1" cellpadding="2" | ||
+ | | Source code | ||
+ | | http://git.openstack.org/cgit/openstack-dev/devstack-vagrant | ||
+ | |- | ||
+ | | Bug tracker | ||
+ | | https://bugs.launchpad.net/devstack | ||
+ | |} | ||
+ | |||
+ | ===Hacking=== | ||
+ | {| border="1" cellpadding="2" | ||
+ | | 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=== | ||
+ | {| border="1" cellpadding="2" | ||
+ | | Source code | ||
+ | | http://git.openstack.org/cgit/openstack-dev/bashate | ||
+ | |- | ||
+ | |} | ||
+ | |||
+ | ===os-testr=== | ||
+ | {| border="1" cellpadding="2" | ||
+ | | 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=== | ||
+ | {| border="1" cellpadding="2" | ||
+ | | Source code | ||
+ | | http://git.openstack.org/cgit/openstack/openstack-health | ||
+ | |- | ||
+ | | Bug tracker | ||
+ | | https://bugs.launchpad.net/openstack-health | ||
+ | |} | ||
+ | |||
+ | ===stackviz=== | ||
+ | {| border="1" cellpadding="2" | ||
+ | | Source code | ||
+ | | http://git.openstack.org/cgit/openstack/stackviz | ||
+ | |} | ||
+ | |||
+ | ===os-performance-tools=== | ||
+ | {| border="1" cellpadding="2" | ||
+ | | Source code | ||
+ | | http://git.openstack.org/cgit/openstack/os-performance-tools | ||
+ | |} | ||
+ | |||
+ | === Patrole === | ||
+ | {| border="1" cellpadding="2" | ||
+ | | 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 [[CrossProjectLiaisons#QA|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 == | == Community == | ||
+ | IRC Channel: #openstack-qa on freenode | ||
+ | === Meetings === | ||
+ | The QA project team has a weekly IRC meeting, for more details see: | ||
− | + | [[Meetings/QATeamMeeting]] | |
− | + | [[Category: Horizontal_Team]] | |
− | [[ |
Revision as of 19:57, 10 March 2018
Contents
- 1 Project Team Definition
- 2 Projects
- 3 Project liaisons
- 4 Feature proposals
- 5 Community
QA is an official OpenStack project team.
Project Team Definition
Official Title: OpenStack Quality Assurance
PTL: Ghanshyam Mann (gmann)
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
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
Source code | http://git.openstack.org/cgit/openstack/tempest-plugin-cookiecutter |
Bug tracker | https://bugs.launchpad.net/tempest |
Grenade
For more information see: Grenade
Source code | http://git.openstack.org/cgit/openstack-dev/grenade/ |
Bug tracker | https://bugs.launchpad.net/grenade |
DevStack
For more information see: DevStack
Documentation | http://docs.openstack.org/developer/devstack/ |
GitHub | https://github.com/openstack-dev/devstack |
Bug tracker | https://bugs.launchpad.net//devstack |
Devstack Plugin Cookiecutter
Source code | http://git.openstack.org/cgit/openstack-dev/devstack-plugin-cookiecutter |
Bug tracker | https://bugs.launchpad.net/devstack |
Devstack Vagrant
Source code | http://git.openstack.org/cgit/openstack-dev/devstack-vagrant |
Bug tracker | https://bugs.launchpad.net/devstack |
Hacking
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
Source code | http://git.openstack.org/cgit/openstack-dev/bashate |
os-testr
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
Source code | http://git.openstack.org/cgit/openstack/openstack-health |
Bug tracker | https://bugs.launchpad.net/openstack-health |
stackviz
Source code | http://git.openstack.org/cgit/openstack/stackviz |
os-performance-tools
Source code | http://git.openstack.org/cgit/openstack/os-performance-tools |
Patrole
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
Community
IRC Channel: #openstack-qa on freenode
Meetings
The QA project team has a weekly IRC meeting, for more details see: