[Starlingx-discuss] Minutes: StarlingX Release Meeting - May 7/2020

[Khalil, Ghada]

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

stx.4.0
- Feature Tracking: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=1107209846  
- Specific Feature Follow-up  --- features we haven't talked about in a while
      - Fault Containerization / Prime: Saul
             - Is this being worked? Is it going to make it for 5/15? Or should we mark it as out?
             - Someone is assigned from Intel Bangalore team, but not sure about progress. Action: Bruce will follow up.
      - python3 / Prime: Austin
             - A small # of reviews are posted & merging. 
             - https://review.opendev.org/#/q/projects:+starlingx+topic:python3+(status:open+OR+status:merged) 
             - What's the risk of the code being merged? Is the code benign? Do we keep this going until MS3 and resume after the stx.4.0 branch is created?
             - Agreed to evaluate risk on a commit-by-commit basis, especially as we get closer to MS3 and RC1.
      - Backup & Restore (k8s portion) / Prime: Frank
             - Is this done?
             - Main functionality is in, but some gaps have been identified and need to be re-worked. Forecast date revised.
      - Containerize Openstack clients / Prime: Bruce
             - Is this being worked? Is it going to make it for MS-3 (5/29)? Or should we mark it as out?
             - Still not resourced. Mark as Out of stx.4.0
      - System Upgrade Support / Prime: Dariush
             - Reviews/code is being merged.
             - Where are we? What will be achieved by MS-3 (5/29)?
             - Expect the framework to be in place for MS-3 to allow a null upgrade (stx.4 to stx.4). Then need to determine what code changes are required on the stx3 side to enable an actual upgrade. This will likely do beyond the stx.4.0 release date.
      - IPv6 support for PXE boot network / Prime: Kunpeng
             - Is this being worked? 
             - Ghada to ask Steve, the networking PL if he knows the status of this feature. 
      - Layered Build / Prime: Frank
             - Is this considered done? Are there remaining work items?
             - Consider DONE. Frank to clean up the storyboard. Reported issues are tracked by launchpads.

- Update on Feature Testing -- Yang / Nick
      - Feature Testing: https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=968103774
             - Things are going well overlap / making good progress in general
             - Action: Yang/Nick to update the feature testing dates in the feature tracking spreadsheet.
             - Kernel Upversion
                     - Feature testing is underway with engineering build. Agreed to look at moving the remaining testing to stx master as the code is all merged now.
             - Openstack host services upversion to train
                     - Feature testing complete with engineering build
             - Ceph Rook
                     - Did a sanity with an engineering build.
                     - Will start feature test-cases
             - Kata Containers
                     - Need to wait 
             - TSN
                     - Not started. Will start to look into the setup requirements next week.
             - Cert Manager
                     - Test was in progress, but blocked on a good load from stx master

- Regression Testing: https://docs.google.com/spreadsheets/d/1gA3bnLS7aY2y8dKxm4MuqpWyELq3PVJMYtiHn4IWiAk/edit#gid=1921715792 
      - Working on test-case selection next week
      - Will start execution the week after - May 18
      - Delay is due to lack of good loads from stx master

- Sanity Issues
      - Sanity with monolithic build
             - Nick & team will try this today
      - Sanity with layered build
             - Saul working on a fix to address the issue causing the openstack failure on bootstrap
             - https://bugs.launchpad.net/starlingx/+bug/1877035