[Starlingx-discuss] Minutes: Community Call (Sep 14 2022)
Khalil, Ghada
Ghada.Khalil at windriver.com
Thu Sep 15 20:55:26 UTC 2022
Etherpad: https://etherpad.opendev.org/p/stx-status
Minutes from the community call
September 14, 2022
Standing topics
- Build
- Main Branch CentOS Builds
- Builds have been green all week
- Main Branch Debian Builds
- Builds have been green 6/7 days last week. One intermittent issue seen, but the follow-up build passed.
- When will CentOS builds stop?
- Criteria for discussion
- Container builds all transitioned to build as part of Debian
- This can be a soft target given most container images are statically tagged, so previously built containers can continue to be used if a rebuild is not required.
- However, once a rebuild is required, the team responsible would have to transition the container build to be part of Debian builds
- Support for most/all deployment configs in Debian
- AIO-SX, AIO-DX, Standard, Storage, DC
- Regular sanity running on Debian builds
- stx-openstack
- Currently only built and supported in CentOS
- Will need a decision on whether transitioning stx-openstack to Debian is a gating item for stopping the CentOS builds
- Sanity
- CentOS Main Branch Sanity w/o stx-openstack
- AIO-SX sanity was green. https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013359.html
- AIO-DX sanity was not run due to a config/env issue
- CentOS Main Branch Sanity w/ stx-openstack
- Sanity was run last week and was yellow (same as stx.7.0) >> Action to ensure reports are sent to the emailing list
- Sanity pipeline hit some issues this week which are under investigation
- Debian Main Branch Sanity
- Action: Rob to look at plan to start these executions
- Need to consider an overlap period with both CentOS & Debian sanities running to ensure Debian is stable before discontinuing CentOS sanity.
- Team is also working on automating sanity emails to the mailing list
- Was discussed within the stx test team and there are some challenges with implementation.
- For now, the team will send the reports manually and follow the required "subject" format for tagging builds as green in CENGN
- Gerrit Reviews in Need of Attention
- FEC Operator Configurability
- https://review.opendev.org/c/starlingx/app-sriov-fec-operator/+/845179 >> Merged
- Follow-up reviews are now promptly reviewed and merging
- 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
- stx.7.0 Status
- Release milestone has been declared as of Sept 9.
- Email Announcement: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013352.html
- Blogs
- Release Blog was merged / released on Tuesday Sep 13 as per plan
- Pull Request: https://github.com/StarlingXWeb/starlingx-website/pull/201/
- Email follow-up regarding live updates/upgrades support
- https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013354.html
- Upgrades are not officially supported as per https://docs.starlingx.io/introduction/consuming.html
- Need to clarify this in the Updates/Upgrades section as well:
- Action: Greg/Steve to respond to the thread and open follow-up doc LPs to clarify the documentation
ARs from Previous Meetings
- Action: Rob to confirm if the bi-weekly build meeting is active and send the date for the next meeting to the mailing list.
- https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013354.html
- Still open
Open Requests for Help
- Base OS for stx.6.0: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-August/013206.html
- Closed. Greg responded: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013348.html
- Wireguard issue
- Tracked by LP: https://bugs.launchpad.net/starlingx/+bug/1984125
- Based on OS team meeting on Sept 14 (https://etherpad.opendev.org/p/stx-distro-other ), testing is successful. Team plans to submit patch to the stx main branch.
- Rebuilding ISOs
- No update this week
- Last Status:
- Raised on the call by Scott Kamp
- Scott and team are struggling to rebuild the starlingx source to prototype code changes. The documented process does not seem to be clear.
- Suggestion is to attend the bi-weekly build meeting to provide feedback and get help.
- Action: Rob to confirm if the bi-weekly build meeting is active and send the date for the next meeting to the mailing list. << still open
- Scott will also look at the latest updates to the build guide as they were updated recently.
More information about the Starlingx-discuss
mailing list