[Starlingx-discuss] Community Call (June 26, 2019)

[Zvonar, Bill]

Notes & actions from today's call... 

MS-3 is official!
   - Thank you everyone!
   - Reminder to clean up storyboard: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.2.0
   - reminder of code merge guidelines until RC1. This was discussed and sent out previously.
       - Priority goes to stx.2.0 bug fixes and stx.2.0 MS-3 exceptions (above)
       - For code unrelated to stx.2.0 (code for deferred items to stx.3.0, new stx.3.0 features, enhancements), 
         only passive/disabled code should be merged in master until the stx.2.0 RC1 branch is created (Aug 5). 
         We will leave it to the judgment of the technical leads and core reviewers to determine if code is safe to merge.  
         If you need an opinion, the release planning team is happy to help (Ghada, Bill and Bruce).

Feedback on the new wiki has been positive (Bruce).  
   - Any objections to me making https://wiki.openstack.org/wiki/StarlingX/Draft_new_wiki_home_page the new wiki home page?
   - we agreed to go ahead with the new wiki, Bruce will update it later today, and include a link to the old wiki off the new page 

regression status 
   - http://lists.starlingx.io/pipermail/starlingx-discuss/2019-June/005094.html
   - the 115 testcases that were run were all run manually 
   - regression reports will be sent twice a week - Tuesdays & Thursdays 
   - per Numan, we've started automated regression as well 
   - that'll be an additional 1100+ testcases, over & above the 421 manual that Maria's reporting on 
   - ACTION: Numan & Ada to sort out how they aggregate reporting will be done (manual & automated)

automation framework (Numan)
   - thanks to Bruce, Saul & Erich et al for reviewing the automation framework that Yang is making available to the Community 
   - once it's up, folks can start using it - it includes a good number of testcases 
   - ACTION: Numan/Yang arrange an info session for the Community (in a few weeks after Yang's vacation)

defect trend (Bill)
   - marginally better than last week, but still a major cause of concern 

Docker image list: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-June/005063.html
   - per Brent / Frank, Al Bailey's going to work on this - he has an action to get a forecast for when it can be done 
   - ACTION: Frank update on the forecast for this 

stx.3.0 next steps (Ghada)
   - Tentative Release Dates show MS-1 as July 17 -- based on a 6wk offset from the openstack train release
       - https://docs.google.com/spreadsheets/d/1ZFR-9-riwhIwiBYBmWmi1qOVyHtgJ8Xk_FaF2jp5rY0/edit#gid=0
       - MS-1 criteria - https://wiki.openstack.org/wiki/StarlingX/Release_Plan#Release_Milestones
           - Release priorities and major features defined.
               - a list of features 
                    - TSC is working through an overall list (etherpad)
                    - the list for 3.0 will ultimately be tracked on the Release Plan google sheet
           - High level resourcing secured.
                   - an intended resource plan for each feature that's on the list 
       - we agreed to remove the word "tentative" from the 3.0 dates - those are the dates now 
       - Release Candidates: https://etherpad.openstack.org/p/stx-r3-feature-candidates
           - So far, 4 features are marked as "Agreed for R3 / Do in R3":
               - Containerization Deferrals:
                   - Backup and Restore
                   - Containerized FM
                   - Containerized openstack clients
                   - CPU manager static policy for non-openstack worker nodes
               - Distributed Cloud
               - Upgrade from R2->R3 
               - Openstack Train Release Support
               - Python 2->3 cutover
           - Some specs are in progress: https://review.opendev.org/#/q/project:starlingx/specs+status:ope-                - Containerized Ceph
               - Time Sensitive Networking
               - Infrastructure and Cluster Monitoring
               - OVS-DPDK Containerization
               - Redfish (coming soon)
           - Other stuff in progress
               - MultiOS w/ focus on OpenSuse
               - K8s device plugin integration
                    - Intel GPU    >> initial review underway.
                    - Nvidia GPU
                    - Intel FPGA  >> investigation starting / spec to follow.
                    - QAT
           - 17 stories in Storyboard: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.3.0
               - This covers some distro.other patch reduction work items (deferred from stx.2.0)
       - How do we move the planning forward?  Can we achieve MS-1 on July 17?
           - we agreed to stay the course 
           - look through the candidate list in the next TSC meeting

first contact (Bill)
   - ACTION: Bill start checking if any 'new' people emails are going unresponded 

updates on actions 
   - sanity - still not boring, but getting greener - we'll keep it in view 
       - list of stx-sanity tagged lps: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.sanity&orderby=-datecreated&start=0
   - big files
       - ACTION: Scott & Dean to talk about the mechanics of how this would work given a big honkin' storage somewhere
       - ACTION: Frank to talk to CENGN about getting sufficient space (pending any other parameters from Scott)
   - Mailing list post size (Brent)
       - Brent's had mailing list replies blocked due to size restrictions 
       - per Dean, the limit is ~64k, he'll talk to Jeremy about making it higher - but it may be a global OpenStack limit 
       - ACTION: Dean find out what our options for increasing this are
   - Mid-cycle Meeting? -  (Saul)
       - possibly a mid-cycle meeting in September in Ottawa, align with some training sessions that are planned 
       - ACTION: Bill check with Ian about the logistics/timing 
   - stx.1.0 installation documentation (Cindy)
       - are we preserving the installation procedures for stx.1.0 as we work on the 2.0 
       - ACTION: Bruce (or Doc team) let us know if there is such a thing

-----Original Message-----
From: Zvonar, Bill 
Sent: Tuesday, June 25, 2019 8:45 AM
To: 'starlingx-discuss at lists.starlingx.io' <starlingx-discuss at lists.starlingx.io>
Subject: Community Call (June 26, 2019)

Reminder of tomorrow's Community call, topics include...

- MS-3 officially declared - policy for changes going forward 
- bug count / resolution forecast 
- updated wiki 
- first contact 

Please feel free to add topics to the agenda at [0].

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=20190626T1400