[Starlingx-discuss] Minutes: Community Call (Jan 18, 2023)
Khalil, Ghada
Ghada.Khalil at windriver.com
Sat Jan 21 01:34:07 UTC 2023
Etherpad: https://etherpad.opendev.org/p/stx-status
Minutes from the community call
January 18, 2023
Standing topics
- Build
- Main Branch Debian Builds
- Green
- Had 2 failures on Jan 15 & 16 due to recent packaging changes introduced in stx. This has been corrected.
- Main Branch CentOS Builds
- Green
- LP from last week is addressed : https://bugs.launchpad.net/starlingx/+bug/2002423
- 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 yet; will monitor until next week
- Forecast: Dec 14 >> Jan 31 (tentative; pending feedback from the larger community on the mailing list)
- 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 17: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013760.html
- Status: Green for both SX & DX
- stx-openstack Debian Main Branch Sanity
- Last sanity email sent on Jan 13: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013756.html
- Status: Yellow
- Team is working on a number of LPs. Targeting fixes to be merged Jan 18 and run another sanity before EOW.
- LPs:
- https://bugs.launchpad.net/starlingx/+bug/1999445
- https://bugs.launchpad.net/starlingx/+bug/2000168
- https://bugs.launchpad.net/starlingx/+bug/2000483
- https://bugs.launchpad.net/starlingx/+bug/2002113
- Gerrit Reviews in Need of Attention
- 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 4: ScottK will update by EOW
- Jan 11: Code review not updated by the author: ScottK
- Jan 18: Some activity in the review as of Jan 15
- 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
- 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
- openstack image migration to Debian is still in progress
- Feature Test Complete: Jan 25 >> Jan 31
- Regression Test Complete: Jan 25
- on track
- RC1 (branch creation): Feb 1
- hope to keep this date for branch creation; dependent on (1) regression results, (2) openstack sanity results
- Final Regression Complete: Feb 15
- Release: Feb 22
- Feature Status:
- 28 features are Done.
- 2 features are in progress
- Debian: Migrate Openstack app related packages - Code Merged: Dec 22 / Feature Tested: Jan 18
- Update openstack application containers to use Debian base image - Code Merged: Jan 16 >> Jan 25 / Feature Tested: Jan 23 >> Jan 31
- 6 features are continuing/deferred to stx.9.0
- Release Notes
- Hope to start next week
- Bugs
- stx.8.0: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.8.0
- Need each team to review and update as needed
- Risks
- stx-openstack sanity status
- stx.9.0
- No update from the last meeting. 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
- Call for community members to start proposing features for stx.
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
- 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