Jump to: navigation, search

Difference between revisions of "Meetings/QATeamMeeting"

(Proposed Agenda for January 9 2013 (2200 UTC))
(Agenda for next Office hours)
 
(624 intermediate revisions by 57 users not shown)
Line 1: Line 1:
 +
__TOC__
  
 
= Weekly QA Team meeting =
 
= Weekly QA Team meeting =
The OpenStack QA Team holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code>, '''Thursday alternating every week between 17:00 UTC and 22:00 UTC''.<br />
+
The [[QA|OpenStack Quality Assurance (QA)]] team 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.
Everyone interested in testing, quality assurance, performance engineering, etc, should attend!
 
  
The meeting minutes of can be found here: [http://eavesdrop.openstack.org/meetings/qa meeting minutes on everdrop]
+
The [[QA|OpenStack Quality Assurance (QA)]] team holds public weekly Office hours:
 +
* Channel:  <code><nowiki>#openstack-qa</nowiki></code>
 +
* Time: Thursday every week at 00:00 UTC.
 +
* ical - http://eavesdrop.openstack.org/#QA_Team_Office_hours
  
''Rules for adding to the agenda'':
+
Everyone interested in testing, quality assurance, performance engineering, etc, should attend! The meeting minutes of previous meetings can be found here: [http://eavesdrop.openstack.org/meetings/qa meeting minutes on eavesdrop]
* anyone is free to add to proposed agenda, please do so by 1 hr before the meeting
+
 
 +
'''''Rules for adding to the agenda''''':
 +
* anyone is free to add to proposed agenda, please do so by 1 hr before the Office hours
 
* if you add an item to the agenda, please include your ircnick (i.e. sdague) to the end of your item, so we know who did, and who should lead the discussion
 
* if you add an item to the agenda, please include your ircnick (i.e. sdague) to the end of your item, so we know who did, and who should lead the discussion
  
=== Proposed Agenda for January 9 2013 (2200 UTC) ===
 
* Negative test status/discussion (dkranz)
 
* Blueprints
 
** Current state
 
** Status updates from people
 
** Reconsideration of https://blueprints.launchpad.net/tempest/+spec/refactor-rest-client, according to changes (vponomaryov):
 
*** https://review.openstack.org/#/c/62923/
 
*** https://review.openstack.org/#/c/64948/
 
* Bugs
 
** Critical / High bug review
 
** Closing invalid Tempest bugs
 
* Neutron testing
 
* Critical Reviews
 
  
== Previous meetings ==
+
'''''Tips to Chair the Office hours''''':
All previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/qa/.
+
* Start this meeting using: #startmeeting qa
 +
* If nothing much to discuss then we can always finish Office hours any time before 1 hour.
 +
* Announcement and Priority Items progress (first 2 items of Agenda) can be skipped and need not to be tracked every week.
  
=== Agenda for December 19 2013 (1700 UTC) ===
+
== Agenda for next Office hours ==
* Cancelling meetings for the rest of the year (mtreinish)
+
PING LIST-
* Blueprints
+
* Announcement and Action Item (Optional)
** Current state
+
* Train Priority Items progress
** Status updates from people
+
** https://etherpad.openstack.org/p/qa-train-priority
** Needing some attention (gfidente)
+
* OpenStack Events Updates and Planning
*** https://blueprints.launchpad.net/tempest/+spec/fail-gate-on-log-errors (close or not?)
+
** <This includes the OpenStack Summit and PTG updates and planning>
*** https://blueprints.launchpad.net/tempest/+spec/quantum-basic-api (seems to me pretty hard to track/implement, yet useful)
+
** Next: Shanghai Summit & PTG
*** https://blueprints.launchpad.net/tempest/+spec/refactor-rest-client (there is actual work here, approve?)
+
*** Summit & PTG Planning:
*** https://blueprints.launchpad.net/tempest/+spec/keystoneclient-api (approve/low?)
+
**** Forum: https://etherpad.openstack.org/p/PVG-forum-qa-ops-user-feedback
*** https://blueprints.launchpad.net/tempest/+spec/multi-keystone-api-version-tests (maybe we should just use latest?)
+
**** PTG: https://etherpad.openstack.org/p/shanghai-ptg-qa
*** https://blueprints.launchpad.net/tempest/+spec/swift-test-without-keystone (is it a good idea at all?)
+
* Sub Teams highlights (Sub Teams means individual projects under QA program)
* Bugs (sdague)
+
** Tempest
** Critical / High bug review
+
*** https://review.openstack.org/#/q/project:openstack/tempest+status:open
** Closing invalid Tempest bugs
+
** Patrole
* Neutron testing
+
*** Initial implementation for multi-policy support: https://review.openstack.org/#/c/554764/
* Bug status
+
*** Once merged, need to create etherpad to track multiple policy changes
* On new tests tracking (plus and cons of wiki/etherpad/blueprint) (gfidente)
+
** Any other (active sub team will add their status reporting here)
 +
* Bug Triage
 +
** https://etherpad.openstack.org/p/openstack_qa_tempest_2019_bug_review
 +
*** old- https://etherpad.openstack.org/p/QA-Stein-Bug-Triage
 
* Critical Reviews
 
* Critical Reviews
 +
* Open Discussion
 +
** [everyone feel free to add their topics under Open Discussion prior to the Office hours with your irc nickname]
  
=== Agenda for December 12 2013 (2200 UTC) ===
+
== Previous meetings ==
 
+
* All previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/qa/.
* Blueprints
+
* Old agendas are stored on [[Meetings/QATeamMeeting/OldAgendas]]
** Current state
 
** Status updates from people
 
* Neutron testing
 
** Progress on API tests gap analysis in https://etherpad.openstack.org/p/icehouse-summit-qa-neutron (mlavalle)
 
** Report on https://bugs.launchpad.net/neutron/+bug/1251448 (sixth top bug in the gate this week) and its relationship to https://bugs.launchpad.net/tempest/+bug/1259282 (mlavalle)
 
* Bug status
 
** How should we handle bug traffic after we finish the current purge to make sure the noise doesn't come back?
 
** Rotating dispatcher for incoming bugs?
 
** Ask people to put a logstash query in bug tickets that are about test failures?
 
** https://etherpad.openstack.org/p/tempest-bug-triage
 
* Critical Reviews
 
* We should consider putting a fast-track on heat and ceilometer tests since they are integrated but lacking. (dkranz)
 
* Should we have more specialization on the Core review team? e.g. I am comfortable with the nova v3 patches, but no where on neutron. (dkranz)
 
 
 
=== Agenda for December 5 2013 ===
 
* Meeting time change proposal
 
* Getting additional folks signed up as point people
 
** Meeting organizer - mtreinish voluteered
 
** Blueprint Triage point person - need volunteer
 
** Bug Triage point person - need volunteer
 
* Blueprints
 
** Current state
 
** Status updates from people
 
* Neutron testing
 
** Progress on API tests gap analysis in https://etherpad.openstack.org/p/icehouse-summit-qa-neutron (mlavalle)
 
** Wiki page for new comers on how to contribute Neutron API tests (mlavalle)
 
* Critical Reviews
 
* How can we make sure reviews don't slide >1 week (dkranz)
 
 
 
=== Agenda for November 21 2013 ===
 
*  Blueprints
 
* Negative testing (mkoderer/dkranz)
 
* Neutron testing: Discussion of what needs to happen for the sprint in January to take place / succeed? What do we need to accomplish by mid-December to make sure the sprint happens? (mlavalle)
 
* Critical Reviews
 
 
 
=== Agenda for November 14 2013 ===
 
* Possible Meeting Time change to include .jp (sdague)
 
* Blueprints
 
** Blueprints breakdown (sdague)
 
** Negative testing (mkoderer/dkranz)
 
* Neutron testing
 
** Negative tests coverage: neutron status (EmilienM)
 
** Progress on https://bugs.launchpad.net/swift/+bug/1224001 (mlavalle)
 
* How should we sync the teams (neutron/scenario test)? One BP with work items, bugs or ML? (mkoderer)
 
* Onboarding documentation - where should we put it? (mkoderer)
 
* Critical Reviews (sdague)
 
 
 
=== Agenda for October 24 2013 ===
 
* Design Summit Schedule (sdague)
 
** http://icehousedesignsummit.sched.org/ - figure out if there are last minute changes we need (note: many time blocks are fixed due to conflicts, so wiggle room is limited)
 
* Neutron job status (mtreinish)
 
* Scope and place for performance testing such as Rally (dkranz)
 
* Status and roll-out plan for failing the gate on log errors (dkranz)
 
* State of 'smoke' tagging: can we make it useful? (dkranz)
 
* Tempest config reorg and cleanup (mtreinish)
 
 
 
=== Agenda for October 17 2013 ===
 
* Unblocking of Ceilometer QA testing (jd__, sileht)
 
** https://review.openstack.org/#/c/49394/
 
 
 
=== Agenda for October 10 2013 ===
 
* Blueprints (sdague)
 
** started cleaning up blueprints, need to start a purge of all the Unknown items
 
* Neutron job status (sdague)
 
* Elastic Recheck Top issues (mtreinish)
 
* Stable branch timing (sdague)
 
* Design Summit Initial Planning (sdague)
 
** QA sessions needed at DS - https://etherpad.openstack.org/icehouse-qa-session-planning
 
* Lot's of new negative tests. Do we want that? (dkranz)
 
** some are "validating strings", like passing long strings or checking for invalid vs. non existent uuids (gfidente)
 
** some are "traversing" the components, like ensuring we can't attach resources to non existent servers (gfidente)
 
** I've the feeling they should not be tagged as 'smoke' ... and maybe a lot not even 'gate'?
 
* Rollout plan for failing builds that pass tempest but with spurious log ERRORs (dkranz)
 
** https://review.openstack.org/#/c/50795/
 
 
 
=== Agenda for October 3 2013 ===
 
* Blueprints (sdague)
 
** started cleaning up blueprints, need to start a purge of all the Unknown items
 
* Neutron job status (sdague)
 
* Elastic Recheck Top issues (mtreinish)
 
* Stable branch timing (sdague)
 
* Design Summit Initial Planning (sdague)
 
** QA sessions needed at DS - https://etherpad.openstack.org/icehouse-qa-session-planning
 
 
 
=== Agenda for September 26 2013 ===
 
* Blueprints (sdague)
 
** neutron testing status (mlavalle)
 
** Bogus errors in logs (dkranz)
 
* rework "skip test" functionality, reprises mkoderer's proposal (gfidente)
 
* Critical Reviews (sdague)
 
=== Agenda for September 19 2013 ===
 
* Blueprints (mtreinish)
 
** neutron testing status (mlavalle)
 
* Critical Reviews (mtreinish)
 
* How to handle bug fixes in launchpad (mtreinish)
 
* Bogus errors in logs one more time (dkranz)
 
 
 
=== Agenda for September 12 2013 ===
 
* Leader for next week's meeting - sdague on a plane back from LinuxCon during this time
 
* New core members (sdague)
 
* Summit planning (sdague)
 
** my intent is to wait until October to evaluate the agenda we want, however as ideas come forward now feel free to register
 
* Blueprints (sdague)
 
* neutron testing status (mlavalle)
 
* whitebox test removal (sdague)
 
** need a volunteer to ensure these tests are covered in Nova unit tests
 
* Critical Reviews (sdague)
 
* OpenStack qa repo for test plans that can be pointed at from blueprints (mkollaro)
 
 
 
=== Agenda for August 29 2013 ===
 
 
 
* Blueprints (mtreinish)
 
** testr status (mtreinish)
 
*** Do we need a way to "incubate" new tests to avoid flakiness with parallel testr? (dkranz)
 
*** Now that parallel testr is in place (wow) maybe we should organize another bug triage day? (gfidente)
 
** stress tests (mkoderer)
 
** neutron testing status (mlavalle)
 
* Update on slow heat gating job (dkranz)
 
* Critical Reviews (mtreinish)
 
* Testing client library compatibility (dkranz)
 
* Devstack independent tempest usage (afazekas)
 
* BP proposal: rework "skip test" functionaly (mkoderer)
 
 
 
 
 
=== Agenda for August 22 2013 ===
 
* Blueprints (mtreinish)
 
** testr parallel status (mtreinish)
 
** stress tests (mkoderer)
 
* Critical Reviews (mtreinish)
 
* Heat test merge (afazekas)
 
* Devstack independent tempest usage (afazekas)
 
* Adding test plans for new features into the tempest repo (mkollaro)
 
 
 
=== Agenda for August 15 2013 ===
 
* Blueprints (mtreinish)
 
** testr parallel status (mtreinish)
 
** stress tests (mkoderer)
 
* Critical Reviews (mtreinish)
 
 
 
=== Agenda for August 8 2013 ===
 
* Volunteers to run meeting while sdague out (sdague)
 
* Blueprints (sdague)
 
* Critical Reviews (sdague)
 
* Stress tests scope and behaviour, also see reviews on https://review.openstack.org/#/c/39752 (gfidente)
 
* Status of slow heat tests (dkranz)
 
 
 
=== Agenda of August 1 2013 ===
 
''See the [http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-08-01-16.59.html meeting minutes for July 1 on eavesdrop].''
 
 
 
* Blueprints (sdague)
 
* Critical Reviews (sdague)
 
* Call for more Core reviewers (dkranz)
 
 
 
=== Agenda of July 25 2013 ===
 
''See the [http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-07-25-17.00.html meeting minutes for July 25 on eavesdrop].''
 
 
 
* Blueprints (sdague)
 
** Current state of implementation
 
** Stress Tests https://blueprints.launchpad.net/tempest/+spec/stress-tests (mkoderer)
 
* WebDav status codes in nova? Consistently using the 404 or 422 on actions.
 
* Adding test cases with skip attribute vote? Exact rule (afazekas)
 
* py26 compatibility (afazekas)
 
* Consistent reviewing (afazekas)
 
* Critical Reviews (sdague)
 
* Separate heat job and slow tests in general (dkranz)
 
 
 
 
 
===Agenda of July 18 2013 ===
 
''See the [http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-07-18-17.00.html meeting minutes for July 18 on eavesdrop].''
 
 
 
* Blueprints (sdague)
 
** Havana-2 status check in - https://launchpad.net/tempest/+milestone/havana-2 (sdague .. et al)
 
** Testr Progress - https://blueprints.launchpad.net/tempest/+spec/speed-up-tempest (mtreinish)
 
** Stress Tests (new Blueprint and findings) - https://blueprints.launchpad.net/tempest/+spec/stress-tests (mkoderer)
 
* Mailing list move (voting on moving to -dev) (sdague)
 
* White Box Tests (owner for discussion?)
 
** Should they really be unit tests?
 
** Current state of implementation
 
** Integration in CI
 
** Adding test cases with skip attribute (afazekas)
 
* Critical Reviews (sdague)
 
 
 
=== Agenda of July 11 2013 ===
 
''See the [http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-07-11-17.03.html meeting minutes for July 11 on eavesdrop].''
 
 
 
* QA Program Business
 
** PTL Nominations close - see if we need to run election
 
** Program Description
 
* Blueprints
 
** Havana-2 status check in - https://launchpad.net/tempest/+milestone/havana-2
 
** Testr Progress - https://blueprints.launchpad.net/tempest/+spec/speed-up-tempest
 
* Critical Reviews
 
* Stress Tests in CI
 
* Full Open Stack networking gate job
 
* New stress tests in tempest --[[User:M-koderer|m-koderer]] ([[User talk:M-koderer|talk]]) 16:36, 11 July 2013 (UTC)
 
 
 
 
 
=== Agenda of June 27 2013 ===
 
''See the [http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-06-27-17.01.html meeting minutes for June 27 on eavesdrop].''
 
 
 
* ''nothing in Agenda ... only QA as OpenStack Program, QA Leader and testr topics were discussed little bit''
 

Latest revision as of 00:03, 16 October 2019

Weekly QA Team meeting

The OpenStack Quality Assurance (QA) team 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 Quality Assurance (QA) team holds public weekly Office hours:

Everyone interested in testing, quality assurance, performance engineering, etc, should attend! The meeting minutes of previous meetings can be found here: meeting minutes on eavesdrop

Rules for adding to the agenda:

  • anyone is free to add to proposed agenda, please do so by 1 hr before the Office hours
  • if you add an item to the agenda, please include your ircnick (i.e. sdague) to the end of your item, so we know who did, and who should lead the discussion


Tips to Chair the Office hours:

  • Start this meeting using: #startmeeting qa
  • If nothing much to discuss then we can always finish Office hours any time before 1 hour.
  • Announcement and Priority Items progress (first 2 items of Agenda) can be skipped and need not to be tracked every week.

Agenda for next Office hours

PING LIST-

Previous meetings