Minutes: Community Call (Jan 21, 2026)
Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call Jan 21 2026 Standing topics - Build - Main Branch Debian Builds - All build issues from last week have been addressed - Platform: Green - 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 has merged. Additional package restructuring is mostly done. - Status of trixie build: issues are being worked by trixie team - Feature Branch: f/portable-dc - Builds are being re-activated. Rebase was recently done to bring up content to the latest. - 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 - Last sanity executed on Jan 19: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Load used: 20260116T051000Z - Green for AIO-SX & Red for AIO-DX - Sanity LPs: - https://bugs.launchpad.net/starlingx/+bug/2138678 - New. Affecting DX sanity. flock/platorm-services team to investigate. Looks like a lab config issue. - https://bugs.launchpad.net/starlingx/+bug/2138254 - Reported in Jan 12 sanity. Test-case issue due to changes introduced by the latest kernel: 6.12.57. - Assigned to Nimalini to update/close - Debian Main Branch stx-openstack Sanity - Last sanity executed on Jan 20: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Load Used: platform: 20260116T051000Z openstack: 2026-01-16 20:11:34 +0000 - Green - Sanity LPs - None - Gerrit Reviews in Need of Attention - None - 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 - New community participants from Vodafone - Chris Cannon and Francesco Colferai. Interested in using StarlingX for IAAS solutions. - Had a great conversation with Ildiko earlier this week (Jan 20) - Community Call Discussion: - Discussed how the stx platform is applicable to multiple use-cases; not only telco/edge. - Other applicable use-cases can include infrastructure-as-a-service (IAAS); likely need more marketing/info, but likely some missing capabilities as well. - Scale of deployments (# of workers) may be one of the limiting factors. Scale is also limited by the 2-node control plane solution of StarlingX. - External storage is another capability that should be reviewed for enterprise use-cases. - Should consider some improvements for the upcoming stx.13.0 release -- Q3-Q4 2026 - OpenInfra Foundation 2026 annual goals - Email: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Ildiko is looking for input on the draft goal for StarlingX: - Mobilize the StarlingX ecosystem to build a 'Use Cases' page on the StarlingX website, to strengthen the platform's position on the market through displaying the current and emerging production use cases it's utilized for. - The community attendees and TSC reps agree with the above goal. - Next steps: Ildiko to get goal agreement in the board meeting and then drive the next steps to creating the required content on the starlingx.io site. 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 - 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.
participants (1)
-
Khalil, Ghada