[Starlingx-discuss] Minutes: Community Call (Feb 2, 2023)

Khalil, Ghada Ghada.Khalil at windriver.com
Thu Feb 2 03:55:37 UTC 2023

Etherpad: https://etherpad.opendev.org/p/stx-status

Minutes from the community call
February 1, 2023
Meeting is at 7pm PDT / 10pm EDT / +1 10am CST

Standing topics
- Build
     - Main Branch Debian Builds
          - Debian build from Jan 30 seems to be stuck; has been running for 30hrs.
          - Build was reset and was progressing as of earlier today
          - Email: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013792.html
     - Main Branch CentOS Builds
          - Builds failed due to two recent code changes
              - Email: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013793.html
              - Two LPs opened:
                  - https://bugs.launchpad.net/starlingx/+bug/2004428 - Fixed as of Feb 1
                  - https://bugs.launchpad.net/starlingx/+bug/2004506 - Fixed as of Feb 1
              - Monitoring for a new successful build
          - Stopping CentOS Builds
                  - Email sent to the mailing list on Jan 16: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013758.html
                  - No concerns raised by the community on the mailing list since the email was sent
                  - stx-openstack images were migrated to Debian as of Jan 31
                  - Will wait for a final successful build before turning the build off
              - Forecast: Dec 14  >> Jan 31 >> Feb 8
     - stx.6.0 Weekly Build 
          - Green
          - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/
     - stx.7.0 Weekly Build
          - Green
          - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/
- Sanity
     - Debian Main Branch Sanity
          - Last sanity email sent on Jan 31: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013787.html
          - Status: Green for both SX & DX
     - stx-openstack Debian Main Branch Sanity
          - Planned for Feb 2 - once a build w/ Debian-build stx-openstack images is available
          - All gating LPs were addressed with the exception of https://bugs.launchpad.net/starlingx/+bug/2003813
          - Team continues to work on the remaining LP as it will result in a yellow sanity / failing 4 TCs
- Gerrit Reviews in Need of Attention
     - stx-openstack Debian image migration: https://review.opendev.org/q/topic:stx-openstack-debian-images
          - All merged as of Jan 30
     - From previous meetings: Fixes to libvirt env: https://review.opendev.org/c/starlingx/tools/+/863735
          - Review comments provided in Nov; still waiting for author (Scott Kamp) to respond/address review comments
          - Jan 18: Some activity in the review as of Jan 15
          - Feb 1: Alternative fix proposed; waiting for ScottK's review
     - Reference Links:
          - Active Branch (open): https://review.opendev.org/q/projects:starlingx+is:open+branch:+master
          - Active Branch (merged): https://review.opendev.org/q/projects:starlingx+is:merged+branch:master

Topics for this week
- Low pariticipation in today's meeting. Total attendees: 3
- Release Status
     - stx.8.0
          - Release Tracking Spreadsheet: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846
          - Upcoming Milestones:
              - Milestone-3: Jan 18  >> Jan 25 >> Jan 27 / Actual: Jan 31
              - Feature Test Complete: Jan 25 >> Jan 31 >> Feb 2
                   - Pending stx-openstack sanity
              - Regression Test Complete: Jan 25 / Actual: Jan 30
              - RC1 (branch creation): Feb 1 >> Feb 6
                   - Heads Up sent to mailing list: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-February/013794.html
              - Final Regression Complete: Feb 15
              - Release: Feb 22
          - Feature Status:
              - 28 features are Done.
              - Debian: Migrate Openstack app related packages
                   - Team still working on LP:  https://bugs.launchpad.net/starlingx/+bug/2003813 which needs to be resolved for stx.8.0
                   - Team is actively working on the issue. WIP code review opened. Will cherrypick if this isn't addressed by the branch creation
              - Update openstack application containers to use Debian base image
                   - Code Complete
                   - 18 images are ported to Debian. They're all building successfully. helm charts updates are also merged.
                   - The plan is to run sanity once the required build is available: Feb 2
          - Bugs
              - stx.8.0: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.8.0
              - Only one stx-openstack LP is left
          - Release Notes
              - Starting on Feb 2. Code review planned for Feb 6.
          - Risks
              - stx-openstack sanity >> trending in the right direction
     - stx.9.0
          - No new feature proposals added to the tracking spreadsheet.  Call for community members to start proposing features for stx.
          - Would like to have the majority of features proposed by the March virtual PTG
          - Release Tracking Spreadsheet created: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing

ARs from Previous Meetings
- None

Open Requests for Help
- stx-openstack apply failed after enabling cpu_dedicated_setInbox
     - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013720.html
     - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013724.html
     - Seen w/ stx.7.0. Issue only happens when setting cpu dedicated CPUs on a running system. During the unlock, the openstack fails to re-apply.
     - LP: https://bugs.launchpad.net/starlingx/+bug/2002157
          - Assigned to Thales; not investigated yet; team focused on stx.8.0 and openstack sanity. 
          - Reached out to reporter, so they have a view of the status. They're fine to wait until the team has bandwidth
- Documenting Tested Hardware by the community
          - Action: Scott Kamp will discuss documenting community tested hardware with the TSC

More information about the Starlingx-discuss mailing list