[Starlingx-discuss] Minutes: Community Call (Jun 21, 2023)
Khalil, Ghada
Ghada.Khalil at windriver.com
Fri Jun 23 23:22:26 UTC 2023
Etherpad: https://etherpad.opendev.org/p/stx-status
Minutes from the community call
June 21, 2023
Standing topics
- Build
- Main Branch Debian Builds
- Some build failures during the last week
- One build issue with the container images due to a Debian package upgrade >> already fixed
- Build failed yesterday due to a networking outage; this is now happening once/twice per week
- There's a build currently in progress
- stx.6.0 Weekly RC Builds
- Green
- Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/
- stx.7.0 Weekly RC Builds
- Failed due to a recent change to faciliate transition off of CENGN; ScottL is investigating
- Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/
- Note: No container image builds are done for stx.7.0
- stx.8.0 Weekly RC Builds
- Green
- Build Output: https://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/
- Transition from CENGN
- Build team is working on transitioning the builds to WR infrastructure as CENGN will no longer be able to host the StarlingX builds.
- Timing: Tentatively end-July / early-Aug
- Status:
- All mirror jobs are working
- Able to build Debian: the main branch builds (iso+container) as well as stx.8.0 RC builds with similar reliability
- Now working on building stx.7.0 (CentOS build) and investigating issues
- Working w/ WR IT on publicly posting build results << still under discussion
- Sanity
- Debian Main Branch Platform Sanity
- Last sanity email sent on June 20: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-June/014226.html
- Status: Green for SX and DX
- Debian Main Branch stx-openstack Sanity
- Last sanity email sent on June 18: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-June/014218.html
- Status: Green
- Gerrit Reviews in Need of Attention
- tools repo reviews - Virtual Env Setup
- https://review.opendev.org/c/starlingx/tools/+/880870
- Key reviewers have not been active in reviewing the code
- The changes are isolated and should be low risk
- Agreed that Davlet will merge the changes based on the current +1s
- Also agreed that the tools repo will be split into smaller repos. This action is with the build team to plan/implement.
- 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 on Jan 18; waiting for ScottK's review
- Feb 15: ScottK is going back to this
- Mar 22: Next action is w/ ScottK; As per today's meeting, he'll be looking at the comments
- Apr 11: Review is still open. Next action is w/ ScottK (the author)
- May 4: ScottK lost his setup, so needs to recover the review
- Jun 21: No updates
- 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
- Manifest repo re-configuration / split to allow stx-openstack to be built independently from the platform
- https://lists.starlingx.io/pipermail/starlingx-discuss/2023-June/014206.html
- No concerns from the community regarding this proposal.
- The key issue is scheduling time for the build team to implement the change.
- Action: Build team to propose a timeline based on their priorities/availability.
- StoryBoard tracking the work: https://storyboard.openstack.org/#!/story/2010797
- Renaming App Repos to remove the "armada"
- https://lists.starlingx.io/pipermail/starlingx-discuss/2023-June/014215.html
- Minor / cosematic change. Lower priority, but would be nice to do. Should have no impact on runtime.
- Action: Build team to propose a timeline based on their priorities/availability. (lower priority than the manifest repo re-config)
ARs from Previous Meetings
- Restarting the containers subproject meeting?
- Action: Bruce to send the question to the mailing list to see if there is any interest in restarting the meetings
- Status: Open / No update
- github Mirroring
- Action: Greg to review the requirements for github mirroring to confirm if it's required for all repos or just a subset to meet k8s conformance requirements.
- Status: Closed
- Greg reviewed his notes from the discussion w/ CNCF and confirmed that the requirement is to only mirror the core repos (the config repo is considered the core repo).
- There is no explicit requirement to mirror new repos.
- ARM Support
- Action: Scott Kamp to respond to Jackie/the mailing list to provide assistance/access to some arm machines
- Action: Scott Little to respond regarding build questions
- Cannot mirror more files on CENGN; will need to wait until we transition away from CENGN
- Action: Scott Kamp to explore providing a hosting env temporarily
- No plan to publish images to dockerhub/starlingx until they are part of the official build infrastructure
- Under discussion in the OS subproject meeting
- Jackie is donating hardware, but it needs to be managed by someone
- Status: Open
- Greg took the action to identify the right prime to drive the ARM Support project within StarlingX
- StarlingX Subproject Meetings Update
- Action: Scott Little to confirm w/ Mike Matteson on the build meeings
- Scott is suggesting to cover build topics as part of the OS-distro meeting. Scott to discuss with the PL/TL.
- Status Open / No Update
- Action: Chris Friesen to provide an update on the containerization meetings
- Bruce will follow up on whether to restart the containerization meetings on the mailing list
- Status: Open / No Update
Open Requests for Help
- Issue w/ pxebooting a second node on StarlingX
- Question raised on the community call (Apr 26) by Kevin
- The initial node installs/boots correctly, but but an identical second node doesn't. This setup is using vmare to run StarlingX in VMs.
- Status: Open / Greg has some information to share, but isn't sure how to get in touch w/ Kevin
- Build System Setup
- Question was posted on IRC by Kevin
- StarlingX documentation has a lot of outdated information. It took a lot of digging to find the right documentation for setting up a build env with minikube.
- Requested that Kevin open an LP to the doc team and/or send an email to the mailing list w/ more details to the mailing list
- Status: Open / No email sent to the mailing list yet. Unsure if LP was opened.
- Support for StarlingX 8 setup bring up
- Reported by Prashanthi
- Email thread: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-April/014026.html
- Status:
- Open / Discussion is active on the mailing list. Greg providing assistance. The issues are related to date/time issues on servers being setup as well as firewall issues
- CURRENTLY PAUSED ... Prashanthi had higher internal priorities that have taken her away from looking at StarlingX for the time being; waiting for Prashanthi to get back to us.
More information about the Starlingx-discuss
mailing list