OpenStack Quality Assurance Summit & PTG Summary
Open Infrastructure Summit, Shanghai 2019
Open Infrastructure Summit followed by OpenStack PTG was held in Shanghai, China: 4th Nov 2019 till 8th Nov 2019.
The first 3 days were for Summit where we had the forum sessions about user feedback on QA tooling on Monday and the last 3 days for Project Team Gathering (PTG) with one day overlap.
QA Forum sessions
OpenStack QA – Project Update: Wednesday, November 6, 10:15am-10:30am
We gave the updates on what we finished on Train and draft plan for the Ussuri cycle.
due to fewer contributors in QA, Train cycle activities are decreased as compare to Stein. We tried to maintain the daily QA
activity and finished a few important things.
Slides: QA Project Update
Users / Operators adoption of QA tools / plugins :Mon 4, 1:20pm – 2:00pm
Etherpad. This is another useful session for QA to get feedback as well as information about downstream tooling.
Few tools we talked about:
One big concern shared from a few people about a long time to get merged tempest patches. One idea to solve this is to bring critical reviews in Office hours.
QA PTG: 6th – 8th Nov:
It was a small gathering this time for one day for PTG on Wednesday. Even with small number of developers, we had good discussions on many topics. I am summarizing the discussions:
Retrospective bought up the few key issues where we need improvement. We collected the below action items including bug triage. Untriage QA bugs are increasing day by day.
With testtools being not so active, we need to think on the alternate or best suitable options to solve this issue. We discussed the few options which need to be discussed further on ML.
Remove/migrate the .testr.conf to .stestr
hen verify that .stestr conf has the correct test path.
Moving subunit2html script from os-testr
open an issue on stestr to discuss moving to stestr repo. ust because ostestr is deprecated and being removed doesn’t mean it’s not the proper home for those other tools.
Separate integrated services tests can be used in TriplO CI
RBAC testing strategy
defaults and system scope in its policy and added a unit test to cover the new policies. Nova is implementing the same in Ussuri cycle. As discussed in Denver PTG also, Tempest will implement the new credential for all 9 personas available in keystone. Slowly migrate the tests start using the new policies. That will be done via a flag switching Tempest to use system scope or new defaults and that flag will be false to keep using the old policies for stable branch testing.
We can use patrole tests or implement new tests in the Tempest plugin and verify the response. Both have the issue of performing the complete operation which is not required always for policy verification. Running full functional tests is expensive and duplicates existing tests. One solution for that (we talked about it in Denver PTG also) is via some flag like os-profiler by just do the policy check and return the API response with specific return code.
How to remove tempest plugin sanity BLACKLIST
Some of them are less active. Remove below plugins from BLACKLIST:
Python 2.7 drop plan
We discussed the next steps to drop the py2 from Tempest and other QA tools.
Adding New glance tests to Tempest
We discussed on testing the new glance v2 api and feature. Below are the glance features and agreed points on how to test them.
Tempest volunteers for reviewing patches
We encourage people to bring up the critical or stuck patches in office hours.
Ussuri Priority & Planning
This was the last session for the PTG which could not happen on Wed due to strict time-up policy of the conference place which I really liked. Time-based working is much needed for IT people :). We met on Thursday morning in coffee area and discussed about priority for Ussuri cycle. QA Ussuri Priority Etherpad has the priority items with the assignee.