Minutes: Community Call (Mar 11, 2026)
Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call Mar 11 2026 Standing topics - Build - Main Branch Debian Builds - Platform: Green - OpenStack: Green - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/master/debian/ - stx.11.0 Weekly RC Builds - Red; Build failure is caused by image: intel-gpu-initcontainer - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/rc/11.0/debian/ - stx.10.0 Weekly RC Builds - Green - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/rc/10.0/ - Concurrent distro Builds (bullseye & trixie) - Tooling required to enable concurrent builds has merged. Additional package restructuring is mostly done. - Tooling for container image builds is still outstanding. Scott is actively working on that. - Status of bullseye build: Green - Status of trixie build: Still red - not sure about the details of the most recent issues - Feature Branch: f/portable-dc - Green - CentOS repo maintenance - No plan to maintain the repos moving forward as StarlingX has transitioned to Debian almost more than 2 years ago. - Action: Scott to inform the mailing list to confirm there is no serious impact to stopping maintenance on the CentOS repos - Status: Deferred / Not urgent - Scott will handle this time-permitting - Sanity - Debian Main Branch Platform Sanity - No sanity emails for the last two weeks - Nimalini is following up - Last sanity executed on Feb 19: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Load used: 20260219T051000Z - Green for AIO-SX & Green for AIO-DX - Sanity LPs: - None - Debian Main Branch stx-openstack Sanity - Last sanity executed on Mar 11: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Load Used: platform: 20260310T041000Z openstack: 2026-03-10 19:11:53 +0000 - Green - Sanity LPs - None - Gerrit Reviews in Need of Attention - Trixie build/packaging content - Lower priority reviews: (porting of bullseye packages over to trixie and building) - https://review.opendev.org/q/project:starlingx/metal+status:open+topic:%22st... - https://review.opendev.org/q/project:starlingx/config+status:open+topic:%22s... - https://review.opendev.org/q/project:starlingx/ha+status:open+topic:%22stx-m... - https://review.opendev.org/q/project:starlingx/config-files+status:open+topi... - Some topics look to be active. Others have zuul issues that need to be resolved. - General Notes: - bullseye build/sanity is required in order to ensure there is no impact on the main builds. A comment was added to one of the reviews. - 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 - Juanita (doc team) raised a concern about the events.yaml being outdated - Action: Juanita will send an email to the mailing list with the expectation/process around file updates. - Also discussed adding this info to the contributor guide - No update for the last 3 weeks. - Need Juanita to confirm if this still needs community visibility/tracking - StarlingX Overview Deck - Slide updates are in progress. - PLs/TLs are encouraged to take a look at slides pertaining to their functional areas in the StarlingX Technology section and update if required. - Email: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... Open Requests for Help - Installation of StarlingX using automated virtual install (vbox) - Sent to the mailing list on Nov 20 - Email: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Status: Open >> Closed - Nov 26: Not discussed - Dec 3: Team was not sure about the reported error. Will follow up w/ flock services team to review the email. - Dec 10: No update. Ghada to ping Lisa (flock PL) to see if someone can review/respond - Dec 17: Lisa is trying to identify an owner to respond -- focusing on the core reviewers of the virtual-deployment repo - Jan 7: No response on the mailing list yet. Lisa will follow up. - Jan 14: No update - Jan 21: No update yet. Lisa will follow up - Feb 4: Lisa reached out to Douglas Pereira - Feb 11: No update - Feb 18: No update - Feb 25: No update ... Lisa not on call - Mar 4: No update - Mar 11: Not able to make traction. No clear ownership on the used virtual-env which is not actively maintained. Consider closed w/ no resolution.
participants (1)
-
Khalil, Ghada