[Starlingx-discuss] Minutes: Community Call (Jan 25, 2023)
Khalil, Ghada
Ghada.Khalil at windriver.com
Fri Jan 27 02:20:49 UTC 2023
Etherpad: https://etherpad.opendev.org/p/stx-status
Minutes from the community call
January 25, 2023
Standing topics
- Build
- Main Branch Debian Builds
- ISO Green all week
- Container builds were skipped due to https://bugs.launchpad.net/starlingx/+bug/2003261
- This has been addressed as of Jan 23 and the builds were successful on Jan 24.
- Main Branch CentOS Builds
- ISO failed yesterday due to a recent code submission related to a portieris package upversion; Scott investigating.
- 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 or during the meeting today
- stx-openstack team appears to be on track to finish their image migration by Jan 27
- 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 25: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013774.html
- Status: Green for both SX & DX
- stx-openstack Debian Main Branch Sanity
- Last sanity email sent on Jan 25: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013776.html
- Status: Yellow
- Custom builds of Debian images used due to issues building container images due to LP: https://bugs.launchpad.net/starlingx/+bug/2003261 - Fixed as of Jan 23
- Expect to be able to run next week's sanity using the regular Debian builds
- LPs:
- https://bugs.launchpad.net/starlingx/+bug/1999445 - Fixed as of Jan 24
- https://bugs.launchpad.net/starlingx/+bug/2000168 - Fixed as of Jan 16
- https://bugs.launchpad.net/starlingx/+bug/2000483 - Fix in progress
- https://bugs.launchpad.net/starlingx/+bug/2003813 - New / Under investigation
- https://bugs.launchpad.net/starlingx/+bug/2002113 - Not Gating stx.8.0
- Gerrit Reviews in Need of Attention
- stx-openstack Debian image migration: https://review.opendev.org/q/topic:stx-openstack-debian-images
- Need attention from core reviewers as this is required for the stx.8.0 release declaration
- Repos: openstack-armada-app, root, upstream, nfv
- 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 >> Jan 27
- openstack image migration to Debian is still in progress
- Feature Test Complete: Jan 25 >> Jan 31
- Regression Test Complete: Jan 25
- No update as Rob (Test PL) did not attend
- RC1 (branch creation): Feb 1
- Hope to keep this date for branch creation; dependent on (1) regression results, (2) openstack sanity results
- Will evaluate the status on Feb 1 in the release meeting
- 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
- Testing Complete
- New LP: https://bugs.launchpad.net/starlingx/+bug/2003813 needs to be resolved for stx.8.0
- Update openstack application containers to use Debian base image - Code Merged: Jan 16 >> Jan 25 >> Jan 27 / Feature Tested: Jan 23 >> Jan 31
- All 18 images were ported to Debian and internal testing looks good.
- Reviews still need to merge: https://review.opendev.org/q/topic:stx-openstack-debian-images
- New LP: https://bugs.launchpad.net/starlingx/+bug/2003813 may require more time beyond Jan 31
- Bugs
- stx.8.0: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.8.0
- 5 in total / 2 CVEs / 2 stx-openstack / 1 docs
- Release Notes
- Plan to start the week of Jan 30
- Risks
- stx-openstack sanity / feature status
- 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
- New contributor introduction
- Rajesh
- Based in the Netherlands
- Reached out to Ildiko for some introductory material
- Interested in contributing to the k8s/container area
- https://docs.starlingx.io/ is a good starting point. Also emails to the stx mailing list.
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