[Starlingx-discuss] Minutes: StarlingX Release Meeting - June 27/2019

[Khalil, Ghada]

Agenda/Minutes are posted at:
https://etherpad.openstack.org/p/stx-releases

Release meeting agenda / notes June 27 2019
stx.2.0
- Feature Exceptions Status
     - Most are going in this week and next -- July 12
     - Agreed to delay package upversions from Erich until RC1 given the upversion is not required to address any bugs.
- Feature Testing Status
     - Tracker: https://docs.google.com/spreadsheets/d/15us6HWgcb0dmHHZe2SyOR_UI5BvVpoU8TCST0rQd4zg/edit#gid=1717644237 
     - Containers 
            - Ada - 75/41/1/2
            - Numan - 82/58/3/0
            - Question to Ada/Numan: Does the container testing cover ironic and the final nova overrides being added?
     - OpenStack patch elimination 
            - Ada - 50/21/0/6
            - Numan - 8/4/4/0
     - CentOS 7.6 - QAT - 12/9/0/0
     - Containerized OVS - 15/12/0/0
     - Ceph upgrade - 26/16/0/6
            - Due to hardware requirements for these tests, tests have been delayed (all our hardware is being used for regression testing). Working on scheduling the execution of the remaining ones. Also, we still have 6 blocked waiting for feedback on the instructions. I'm reforecasting the due date to 07/12.
     - As per Elio, the team plans to add more testing for IPv6. Plans are being worked. Some are covered under regression already, but scope can be expanded to cover k8s cluster network.
- Regression testing:
     - Tracker: https://docs.google.com/spreadsheets/d/1MoBroFimeQjsJvCC_N_DSLYMQsNZVMzTwAVc5tPy_t0/edit?usp=sharing 
     - Reports to be sent to mailing list on Tuesdays and Thursdays. 
     - Running with ISO 20190621T013000Z
            - Question to Ada/Numan: How often will regression be picking up new green sanity loads?
            - As per Elio, the plan is to update the regression labs with a new green load every week (Fridays)
     - Total / Pass / Fail / Blocked = 421 / 123 / 7 / 2
            - Percentage complete is higher as Numan's team still need to update the tracker
            - Testcase First Pass Execution for regression: July 5
            - Plan to run another full execution cycle in 3wks: July 26
            - Then focus on bug retest until stx.2.0 is out
     - Launchpads:
            - Will use stx.regression tag to identify bugs found during regression: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.regression  (currently showing 11 open)
                   - Ghada to send a note to the mailing list to remind the test teams -- stx.sanity & stx.regression
            - List from Ada:
               - Controller can't unlock after lock on AIO-SX -  https://bugs.launchpad.net/starlingx/+bug/1833472 
               - user does not login within configured time(60s) login is aborted -  https://bugs.launchpad.net/starlingx/+bug/1833469 
               - removing attributes from bash.log should not be possible -  https://bugs.launchpad.net/starlingx/+bug/1833619 
               - sysadmin user not locked out after 5 wrong password attempts  - https://bugs.launchpad.net/starlingx/+bug/1834116 

stx.3.0
- Release dates were agreed call on the community call on 6/26
     - https://docs.google.com/spreadsheets/d/1ZFR-9-riwhIwiBYBmWmi1qOVyHtgJ8Xk_FaF2jp5rY0/edit#gid=0 
- MS-1 Next Steps
     - Start compiling the list

Feature backlog tracking - AR from TSC meeting 6/27
Options:
     - Jira - Pros: well known, full featured.  Cons: Not open source, not integrated with opendev infra
     - Trello - Pros: free, full featured, light and easy to use  Cons: Not open source, not integrated with opendev infra
     - Storyboard - Pros: part of opendev infra, already in use.  Cons: Missing key features
            - Continue to use storyboard for more "mature" items that are in getting into the implementation phase
     - Launchpad bugs - Pros: part of opendev infra, already in use.  Cons: Already used for bugs, not really suited for feature tracking
     - Launchpad blueprints - Pros: part of opendev infra, has key features (priority, approval, owner, tracking).  Cons: Not yet configured for StarlingX
            - Recommended by Bruce
            - Use for backlog tracking until approval for inclusion in a release. Then use storyboard for the implementation phase.
            - Bruce to publish to the mailing list. Then review in the community call
     - Google sheet to track backlog
            - To date, we've used google sheets to track the dates for the items/features planned for a release