[Starlingx-discuss] Community Call (July 31, 2019)

[Zvonar, Bill]

>From today's meeting... 

- sanity - any red sanities since last Community meeting
   - green so far this week
   - per Ghada, the red sanity last week was due to the allocation of huge pages causing OVS-DPDK failures - it's intermittent but recently increasing 
   - The sanity was caused by https://bugs.launchpad.net/starlingx/+bug/1838031  and https://bugs.launchpad.net/starlingx/+bug/1837936 -- both are duplicates of https://bugs.launchpad.net/bugs/1829403
   - A fix was submitted as of July 29
- reviews in need of attention
   - nothing this week  
- defect trend / gating launchpads: https://docs.google.com/spreadsheets/d/1DZZgqrCIL6wxv51_yFBk6Lfmtf1AqPD6z7e5hEs3prU/edit#gid=1694187926
   - will continue to focus on getting plans in place for the High importance bugs 
- RC1 next week (Ghada)
   - Logistics/Mechanics to be discussed in the release meeting team. >> Scott, Dean, Don, please attend
   - Community should expect that merges will be halted on master for a short period while the branch is being created.
   - Test deliverables for the milestone are still open. Need discuss exception or moving branch creation date
      - Feature Test: 33 TCs not run yet, 9 blocked, 12 deferred 
      - Regression Test: 39 TCs not run, 30 blocked, 6 deferred
      - will discuss in the Release Team meeting tomorrow  
      - Elio mentioned that they have some L2 issues - Ghada advised him to get Forrest involved (Networking PL) and/or send questions to the mailing list 
- Doc update (Mike T)
   - Review of gating doc stories -- https://storyboard.openstack.org/#!/story/list?tags=stx.docs&tags=stx.2.0 - Most already closed. Currently 7 remaining open with 4 well in progress with pending reviews:
   - Wiki migration status -- See https://docs.google.com/spreadsheets/d/1UJjUttsWQRyauATrip0wKGIxSO7DvyetDKmPwvEIDaA
   - Bug status -- https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs 
- Bitergia update: https://etherpad.openstack.org/p/stx-bitergia
   - asked folks to check the "individual contributor" dashboard: https://starlingx.biterg.io/goto/f8ba64af7d170d0b3d20b820bd9aac77
- PL/TL elections coming up in September 
   - no comments
- IPv6 questions from Elio - he'll put his questions up on the mailing list 
- Release 2.0 communication preparations (ildikov)
   - Blog post topics and authors
   - Features to highlight
      - https://etherpad.openstack.org/p/2019_StarlingX_Marketing_Plans
   - OpenStack fork status
   - New overview slide deck: https://github.com/StarlingXWeb/starlingx-website/files/3392060/StarlingX.Onboarding.Deck.for.Web.July.2019.pdf
- updates on open actions
   - ACTION: Yong to propose how we could formalize the process of assessing the impact of a bug from different perspectives
   - Yong to send his thoughts to the mailing list or here
   - some practices - ask the questions to evaluate 1). the importance (how much it impacts to users), 2). severity (how bad the system gets hurt) of an issue. 3). what kind of users (admin or normal end-users) would be impacted?
      - Does the issue lead to a major feature (mostly visible to users) misfunctional or missing? for example, VMs cannot be created, or Pods fail to run.
      - Does the issue impact the user experience? For example, information in Horizon dashboard is not correct or out of date, but users can still use the functionality to operate the system.
      - Does the issue impact usability over time? for example, memory leaking issues.
      - Does the issue cause a measurable performance drop or an obvious regression, compared to a prior version? 
      - Do we have workarounds when the issue occurs?  Workaround means some reasonable manual operations to users, and it doesn't include the hacking ways.
      - Is the issue 100% reproducible or just randmon occuring?
      - Does the issue blocks the rest of testing once it happens?
      - Is this issue confirmed by an upstream issue? Is there a solution for that upstream issue?
      - ACTION: Ghada to add a sub-section about Workarounds to the bug template 
   - ACTION: release team make the recommendation re: Blueprints for Backlog in the next TSC meeting - pending 
      - presented at TSC meeting last week, not closed yet
   - ACTION: Frank to talk to CENGN about getting sufficient space (pending any other parameters from Scott)
      - CENGN to get back to Frank on this - re: feasability & cost 
      - they're setting up a PoC for us, no firm date 
   - ACTION: Numan & Ada to sort out how aggregate regression reporting will be done (manual & automated) - they have booked a meeting to discuss
      - done
      - they're also working on harmonizing their Sanity reports - one common set of tests being run by the GDC/Ottawa test teams - it'll be sent to the Community for review 
   - ACTION: Numan/Yang arrange an automation framework info session for the Community (in a few weeks after Yang's vacation)
      - Numan is setting this up w/ Yang - details tbd by next week's Community call

-----Original Message-----
From: Zvonar, Bill 
Sent: Tuesday, July 30, 2019 9:29 AM
To: starlingx-discuss at lists.starlingx.io
Subject: Community Call (July 31, 2019)

Hi everyone, reminder of the Community Call tomorrow.

Topics on the agenda include... 

- sanity - any red sanities since last Community meeting?
- reviews in need of attention
- defect trend / gating launchpads 
- stx.2.0 RC1 is next week
- documentation update
- bitergia update: see https://etherpad.openstack.org/p/stx-bitergia
- open actions from previous meetings

Please feel free to add topics on the etherpad [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=20190731T1400