[Starlingx-discuss] Minutes: Community Call (Nov 2, 2022)
Khalil, Ghada
Ghada.Khalil at windriver.com
Thu Nov 3 18:19:10 UTC 2022
Etherpad: https://etherpad.opendev.org/p/stx-status
Minutes from the community call
November 2, 2022
Meeting is at 7pm PDT / 10pm EDT / +1 10am CST
Standing topics
- Build
- Main Branch CentOS Builds
- Several build failures this week. Issues are addressed.
- Summary sent by ScottL: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013516.html
- Main Branch Debian Builds
- Several build failures this week. Majority of issues are addressed to re-enabled the builds. May need to re-work some of the short terms fixes.
- Summary sent by ScottL: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013516.html
- Debian Build Acceleration Feature
- Code caused the Debian build issues. Fixes were merged.
- The Acceleration feature is now functional for the ISO build, but not yet for container builds.
- Weekly CentOS Builds for stx.6.0 & stx.7.0
- stx.6.0 - plan to build ISO only and no containers
- stx.7.0 - plan to build both ISO and containers (since stx.8.0 is several months from being released)
- Working through build issues.
- stx.6.0 issue has been addressed.
- stx.7.0 issue is still under investigation.
- Sanity
- CentOS Main Branch Sanity w/ stx-openstack
- LP causing the last red sanity has been resolved as of Oct 27
- LP: https://bugs.launchpad.net/starlingx/+bug/1993832
- No new sanity email sent since then
- Rob will follow up to ensure the stx-openstack sanity is restarted.
- stx-openstack sanity transition to Debian
- Planned for the Dec time-frame
- Email to the mailing list: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-October/013487.html
- Debian Main Branch Sanity
- Last sanity email sent on Nov 1: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013506.html
- Status: Green
- Gerrit Reviews in Need of Attention
- Doc review from Ildiko: https://review.opendev.org/c/starlingx/docs/+/843349
- Request for Juanita to merge.
- 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
- Upcoming Elections
- Nomination period starts next week on Nov 1 for both TSC & PL/TL positions.
- Nomination period ends on Nov 8
ARs from Previous Meetings
- Action: Ghada to ask Frank about the latest in the plan to disable stx CentOS builds. This needs community communication via the mailing list.
- Closed. Time-frame is Dec. Email to the mailing list: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-October/013487.html
- Action: Rob/Thales to discuss if stx-openstack CentOS can be stopped for the next 4-6wks if the builds are stopping. To make this decision, a community poll via the mailing list is needed.
- Closed. stx-openstack sanity will continue on CentOS until it's ready to migrate to Debian in Dec.
- Action: Ildiko to add Scott Kamp to the electoral as a contributor to the project.
- Closed. ScottK has been added.
Open Requests for Help
- Virtio-forwarder with StarlingX - NEW
- https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013505.html
- Action: ScottK to respond
- stx aio bare metal 7.0 centos / openstack fails
- Response sent to mailing list: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013507.html
- Reported issue is not reproduced.
- LP Reference: https://bugs.launchpad.net/starlingx/+bug/1993593
- The reporter (ScottK) is in the process of rebuilding the server and retesting the stx-openstack install.
- Consider this closed for now.
- Rook Installation
- https://lists.starlingx.io/pipermail/starlingx-discuss/2022-October/013404.html
- Response sent to the mailing list: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-October/013488.html
- Summary: rook was not transitioned to FluxCD in stx.7.0. To use the armada version, need to configure the system w/ k8s 1.18
- Consider this closed
- Enabling cpu_dedicated_set
- https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013382.html
- Last Question posted in the thread: Is there a way I can enable application-isolation across all the worker nodes including new nodes to be added in future?
- Pinged Chris Friesen, but no response
More information about the Starlingx-discuss
mailing list