[Starlingx-discuss] Community Call (Nov 27, 2019)

Mon Dec 2 17:50:07 UTC 2019

Notes from last week's Community Call.

This week's call will be hosted by Bruce. 

Thanks, Bill...  

- Standing Topics

    - Gerrit Reviews in Need of Attention
        - nothing this week 

    - Sanity: any RED since last week?
        - no

    - Unanswered Requests for Help on Mailing List
        - STX 2.0: swift? - Volker von Hoesslin - http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/007035.html
            - per Brent, the API is supported as an optional service, backed by Ceph
            - Yong will get some input from Brent & will revert to Volker (& include Austin re: storage, as appropriate)
        - DPDK with VPP - Ezpeer Chen - http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/007063.html
            - Brent will revert to Ezpeer
        - Enabling Object Storage - Austin Gillmann - http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/007053.html
            - similar to first Q - Yong/Brent/Austin to collaborate
        - Reduce OpenStack VM Size? - Sai Chandu - http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/007031.html
            - Sai Chandu to share some before & after sizes 

- This Week's Topics

    - stx.3.0
        - No release meeting on 11/28 due to American Thanksgiving and meeting conflicts for WR team in Canada
        - Reminder: stx.3.0 release branch will be created on 11/28
        - Once created, all stx.3.0 gating bugs needs to be merged in master and then cherry-picked by the developer to the release branch
        - Test teams to schedule sanity and move all stx.3.0 test activities to the stx.3.0 builds.
        - stx.3.0 Gating Bugs
            - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0
            - The current count is 61 -- down from 80 last week
            - Good progress! Let's continue this momentum.
            - distro.openstack: 14 (was 15) https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.distro.openstack
            - security: 5 (was 14 - first place!) https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.security
                - Jim Somerville & Robin Lu made great progress on CVEs. Actively working on 3 more related to kernel CVEs and 1 related to the OVMF package.
            - config: 13 (was 11) https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.config
            - containers: 16 (was 24 - nice!) https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.containers
            - networking: 5 (was 5) https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.networking
                - Huifeng - moved some to 4.0, actively working on the 5 remaining
            - storage: 6 (was 5) https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.storage
                - Austin - actively working, all are medium
            - distcloud: 2 (no change) https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.distcloud
            - metal: 3 (was 2) https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.metal
            - fault: 1 (no change) https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.fault
            - update: 1 (no change) https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.update
            - There are 23 bugs that are older than 100 days
                - These are medium priority bugs that were moved from stx.2.0 to stx.3.0
                - Request each sub-project team to review to determine if these are still valid
                - Some requests sent to the reporters (if part of the test team) for re-test
                - Ghada: No point in moving these again to stx.4.0 if not addressed by stx.3.0
                - Community agrees that moving this set to stx.4.0 is not a good idea.
                - The current recommendation is to keep them open, but mark them not-gating / low priority.
        - Regression Test Update: (Requested from Elio)
              - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237
              - Making good progress. On track to finish regression first pass execution by 11/29.
    - stx.4.0
        - Reminder about planning email
            - http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/007029.html
        - Release Planning Spreadsheet (see the Release Candidates worksheet)
            - https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0

    - Sai chandu / Calsoft -- The deployment of Openstack in StarlingX all-in-one Simplex is done successfully. It is containing StarlingX with k8s, EdgeX and Openstack
         - http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/007064.html
         - Setup Document:  https://drive.google.com/open?id=110kbsRoBFZQ3J99hobu0QGxC_xchYwKk 
         - Image:  https://drive.google.com/open?id=14jxBWnB5ydCk2sf_jc7I2B_e0aTC-rc6   

    - Proposed rules regarding patch files re: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/007070.html
         - +1 from Saul, this will be discussed in Build meeting 

    - Unit Test 
         - per http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006710.html
         - each sub-project to consider a similar path as what was followed by Config 
         - what level/type of automation testing would provide most benefit to the sub-project - applicability, address current lack of coverage, other considerations
         - what area of the sub-project's code is most in need of additional coverage - heat map of issues, rate of change, desire to 'open' to non-experts 
         - where should the sub-project invest to increase/maintain quality while enabling contributions 
         - what work is required - example testcases, documentation, test infrastructure to lower the bar for writing effective unit tests?

    - Doc Process re: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006985.html
    - Dev Process: what's the process for modifying this process? re: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/007020.html
         - didn't get to these 2 topics

-----Original Message-----
From: Zvonar, Bill 
Sent: Wednesday, November 27, 2019 7:40 AM
To: 'starlingx-discuss at lists.starlingx.io' <starlingx-discuss at lists.starlingx.io>
Subject: Community Call (Nov 27, 2019)

Hi all, reminder of the Community call later today.

We have many topics on the agenda [0], so we'll likely have to prune it a bit...

- standing topics 
    - Gerrit review in need of attention - none so far 
    - Sanity: any RED since last week? - not so far 
    - Unanswered Requests for Help on Mailing List - 4 this week

- this week's topics
    - stx.3.0 update, including gating bugs 
    - PSA re: deployment of OpenStack in StarlingX AIO Simplex
    - Doc Process 
    - Unit Test 
    - Proposed rules regarding patch files  
    - Dev Process - what's the process for modifying the process

Bill...

[0] etherpad: https://etherpad.openstack.org/p/stx-status
[1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call
[2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191127T1500