Minutes: Community Call (Jul 2, 2025)
Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call July 2 2025 Asia-friendly Timezone: Meeting is at 7pm PDT / 10pm EDT / +1 10am CST Standing topics - Build - Main Branch Debian Builds - Platform: no update - OpenStack: no update - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/master/debian/ - stx.10.0 Weekly RC Builds - no update - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/rc/10.0/ - stx.9.0 Weekly RC Builds - no update - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/rc/9.0/ - f/trixie Feature Branch - no update - Work on trixie is deferred to focus on python upversion for stx.11.0 - f/portable-dc Feature Branch - no update - Red since May 24 - suffering from issue in main branch whose fix needs to be ported to this branch ... via a branch merge to be decided by dist-cloud team - Action: Michel / DC team to determine next steps - ARM Builds - ARM build machine is being setup in WIND RIVER labs - 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: Open / Not urgent - Scott will handle this time-permitting - New Feature Idea: Experimenting w/ setting up builds based on a gerrit review topic - This can be alternative to feature branches for smaller features - Status: - script DONE to experiment with building based on a gerrit review topic - documentation TBD ... so others can experiment with it as well - /mirror Restructuring - In the process of changing the build output structure to have bullseye & trixie builds co-exist and further structures for amd64 & arm builds - https://mirror.starlingx.windriver.com/mirror/starlingx/master/debian/ - symlinks are pointing to bullseye to avoid issues for the community - Sanity - Debian Main Branch Platform Sanity - Last sanity email executed on June 30: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Green for AIO-SX - RED for AIO-DX ... install failed - Sanity LPs: - https://bugs.launchpad.net/starlingx/+bug/2114756 - Unassigned. Action: Jim Beacom to assign. - Debian Main Branch stx-openstack Sanity - Lab has some hardware issues?? - Last sanity email executed STILL(?) on May 14: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Need an update from Thales. Parvathi will follow up. - Sanity LPs - https://bugs.launchpad.net/starlingx/+bug/2110683 - Intermittent issue causing some sanity TCs to fail - Gerrit Reviews in Need of Attention - Open vSwtich DPDK support on Debian (puppet work) - https://review.opendev.org/q/topic:%22ovs-dpdk-support%22 - Merges are progressing. Reviews appear active. - 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 - Greg on vacation: Jul 7 - 18 - Will defer the TSC portion of the meeting and continue with the community call - Reminder to use the new zoom link from the LFX calendar - https://zoom-lfx.platform.linuxfoundation.org/meetings/starlingx?view=week - Potential inaccuracies in stx.10.0 install guide - Raised by: Felipe Borges - Horizon GUI is using https instead of http - This is a change of behavior in stx.10.0 - Action: Felipe to open a doc LP to update the install guide - Status: Open - LP has not been raised yet ARs from Previous Meetings - None Open Requests for Help - Request for help installing a StarlingX instance for a community nonprofit - Sent by Rizwan Ashraf on Mar 2 - Email: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Status: Open - 03/05: Greg will respond to the email requesting more info - 03/12: Still on Greg's To-Do for this week - 03/26: Greg reached out by email: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - 04/02: No update as Greg did not attend - 04/16: Discussion is ongoing. Latest email thread: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - 04/23: Greg is planning to respond this week - 04/30: Request is for explicit help to install StarlingX and onboard various applications. Greg is working to find someone from the community to take this on as dedicated time is required - 05/07: Greg will provde the initial support until a more dedicated resource can be identified - 05/14: No update - 05/21: Greg is waiting on a response from Rizwan - 05/28: Rizwan responded indicating he'll setup a channel for further communication. The suggestion is to use the StarlingX matrix channels for communication - 06/25: No update. Greg hasn't heard from Rizwan in a while. - 07/02: Rizwan has the access ready. Greg suggested to have a kick-off the week of July 21: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Automatically assigning node personality - Sent by sreerag.r@ortseam.com on Apr 3 - Email: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Status: Closed - 04/16: JimB took the action to have someone from flock/platform-services respond - 04/23: No response yet - 04/30: JimB pinged his team to review and respond - 05/07: No response yet - 05/14: No update - 05/21: JimB will follow up with his team to have someone to respond - 05/28: Requested info was provided by Eric M: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... ; now waiting for further response from the reporter - 06/04: No update/reply from the reporter - 06/25: Still no response from the reporter - 07/02: Consider closed due to lack of activity - StarlingX for Home Use & Ansible issues - Sent by asa.losurdo@gmail.com on May 17 - Email: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Status: Closed - 05/21: JimB took the action to review and identify someone to respond - 05/28: Response provided by Joshua K: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... with a follow-up response from the reporter - 06/04: Followup question / logs received on May 28 - 07/02: Joshua K identified the issue and suggested a resolution. The reporter confirmed that the issue is resolved. https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i...
participants (1)
-
Khalil, Ghada