Quality Assurance Project overview and update What does the QA - PowerPoint PPT Presentation

05.10.2017 Quality Assurance Project overview and update

What does the QA project do? • Develop, maintain, and initiate tools and plans to ensure the upstream stability and quality of OpenStack, and its release readiness at any point the release cycle • Horizontal team: users are the OpenStack developers, packagers and operators

Project background • Founded during the Folsom release of OpenStack • 198 contributors for the Ocata release User adoption: • Used by most OpenStack projects for CI • Implemented with plugin mechanisms for big-tent • Many companies use Tempest as an integration test suite internally • QA forum session Thursday morning (May 11th, 9:00-9:40) to get feedback from users

QA components • Tempest : Integration test suite • Grenade : Upgrade test suite • Patrole : Policy test suite • DevStack : Deployment tool for development • OpenStack-health , Stackviz : Visualizing test results of CI Jobs • Hacking , Bashate , eslint : Coding style check • os-testr : Testr wrapper for OpenStack projects

Pike themes for QA ● Stability ○ Stable APIs ○ Stable gate ● Usability ● Interoperability, backward compatibility

New features & enhancements for Pike Tempest Patrole ➡ ➡ • Increase the surface of stable interfaces • Test coverage for “core” projects • Micro-versions and schemas • CI, docs and release • Documentation OpenStack Health, Stackviz ➡ • Contributors are needed! Devstack ➡ • Performance tuning Upgrade testing ➡ • Python based devstack tools • Contributors are needed! • UCA packages for libvirt • Run services via systemd

Queens themes for QA ● Operators community ● Adjacent communities ● Streamlining, minimum maintenance ● Interoperability

Possible features & enhancements for Queens Gate stability monitor ➡ Rolling upgrade testing ➡ • Memory footprint per service • CPU and IO load on test nodes HA / Fault Injection ➡ Tempest lib / json schemas ➡ Community testing ➡ • Non functional testing on 3rd party premises Intelligent, automated log analysis ➡ • Cross-community testing (thanks for Zuul v3!) • Reduce complexity in gate analysis • OpenStack QA tools for other communities • Discover new issues

Rocky - Vision for QA ● Constellations verification ● Non functional testing in the open ● Contributors from adjacent communities ● Interoperability

References ● QA Priorities, Pike: https://etherpad.openstack.org/p/pike-qa-priorities ● Documentation: ○ Tempest docs: https://docs.openstack.org/developer/tempest/ ○ Devstack docs: https://docs.openstack.org/developer/devstack/ ○ Grenade docs: https://docs.openstack.org/developer/grenade/ ○ Patrole docs: https://docs.openstack.org/developer/patrole/ ○ OpenStack Health: http://git.openstack.org/cgit/openstack/openstack-health/tree/README.rst ○ Stackviz docs: https://docs.openstack.org/developer/stackviz/

How to contact us ● #openstack-qa in IRC ● openstack-dev@lists.openstack.org, quota [QA] in the subject ● Weekly IRC meetings in #openstack-meetings https://wiki.openstack.org/wiki/Meetings/QATeamMeeting ● Face to face at the Forum and the PTG

THANKS. Questions? openstack @OpenStack openstack OpenStackFoundation