Minutes: Community Call (Dec 17, 2025)
Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call Dec 17 2025 Standing topics - Build - Main Branch Debian Builds - Platform: Multiple green builds this week, but failed last night - Issue introduced by the concurrent build restructuring: - LP: https://bugs.launchpad.net/starlingx/+bug/2136746 - Fix is in progress: https://review.opendev.org/c/starlingx/ptp-notification-armada-app/+/971332 - OpenStack: Green - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/master/debian/ - stx.11.0 Weekly RC Builds - Green - 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 have merged. - Additional package restructuring are in progress - Some merges have caused build failures for the main bullseye build as per above - Team has agreed that Dec 17 is the last day in 2025 for these merges to occur so that the build can be stabilized before the holidays - No successful trixie build yet. - 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 for the last two weeks due to lab issues - Last sanity executed on Dec 2: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Load used: 20251201T051000Z - Green for AIO-SX & AIO-DX - Sanity LPs: - https://bugs.launchpad.net/starlingx/+bug/2131174 - Not reported in the most recent sanity. No notes in the LP. - Debian Main Branch stx-openstack Sanity - Last sanity executed on Dec 16: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Load Used: platform: 2025-12-15 05:10:00 +0000 openstack: 2025-12-11 00:44:27 +0000 - Green - Sanity LPs - None - Gerrit Reviews in Need of Attention - Doc reviews pushed for application updates w/o clear indication if these are tested and ready to merge. Sometimes reviews are duplicated as well. - Example: - https://review.opendev.org/c/starlingx/docs/+/969498 - https://review.opendev.org/c/starlingx/docs/+/970401 - Action: Juanita to speak to Gleb about this - Status: Closed - Dec 17: Juanita talked to Gleb (app upversion automation prime) and confirmed that the team will take responsibility of abandoning the stale 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 - Metrics Dashboard Changes - Email: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Some work is in progress by the Linux Foundation to integrate gerrit-based projects (like StarlingX) into the LFX dashboard (https://insights.linuxfoundation.org/) - Note: The StarlingX Bitergia dashboard will be available only until Jan 14 2026 - Request to generated pdf from starlingx.io - Raised by Juanita - Ildiko suggested that Juanita sends a query to openstack-discuss community to see if the openstack doc team have done this - Holiday Schedule - Community calls will be cancelled on Dec 24 & 31 - The first community call in 2026 will be on Jan 7 (Asia friendly timezone) Open Requests for Help - Installation of StaringX 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
participants (1)
-
Khalil, Ghada