Minutes: Community Call (Mar 4, 2026)
Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call Mar 4 2026 Asia-friendly Timezone: Meeting is at 7pm PDT / 10pm EDT / +1 10am CST Standing topics - Build - Main Branch Debian Builds - Platform: Was green earlier, but failed yesterday due to a bad commit. A fix has been merged: https://review.opendev.org/c/starlingx/tools/+/978873 and waiting for a new build - OpenStack: Same as above - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/master/debian/ - stx.11.0 Weekly RC Builds - Red; needs investigation - 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: Red? issue with inconsistent meta data ... Scott to track down whether launchpad exists for this or not - 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 email this week yet - 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 3: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Load Used: platform: 20260303T051000Z openstack: 2026-03-01 19:58:42 +0000 - Note: openstack builds are using epoxy - 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... - Not ready to merge; several reviews have zuul failures and/or W-1 - 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 this week again - StarlingX Overview Deck - Slide updates have started. Feedback is requested. - Email: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - stx.12.0 Milestone-3 Review: - Forecast: Mar 4 - Criteria - Feature freeze: All feature code merged and feature testing completing within an acceptable timeframe - Status: Achieved - 55 features are code complete. Prep features (trixie) will only merge benign code until branch creation. - The majority of features are also tested. Only 7 features still in test. - No blocking issues from Automated Sanity and Regression - Status: Achieved - Recent sanity reports are green - platform: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... -- from last week - openstack: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - No critical issues severely impacting system stability or release test activities - Status: TBD - One build issue recently reported, but is already resolved - Action: Confirm successful builds on Mar 5-6 - Release regression testing starting - Status: Achieved - Testing is planned to start after MS-3 as per plan - Documentation plan defined; including a prioritized list of the various documentation items - Status: Achieved - Feature documentation updates are in progress - Blog Posts planned/available - Status: Achieved - Plan is in place as per below - Verdict - Conditional pass -- dependent on a successful build on Mar 5 - Would be nice: platform sanity report for this week 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 - 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
participants (1)
-
Khalil, Ghada