February 2026 - Starlingx-discuss

Starlingx-discuss] [docs] [meeting] Docs team notes 05-04-2024
by Balaraj, Juanita 12 Jun '26

12 Jun '26

Hello All, Here are last week's doc team meeting minutes. Details in [2]. Join us if you have interest in StarlingX docs! We meet on Fridays 6:00 a.m. PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings<https://urldefense.com/v3/__https:/wiki.openstack.org/wiki/Starlingx/Meetin…> [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation<https://urldefense.com/v3/__https:/etherpad.openstack.org/p/stx-documentati…> 29-March-24 The meeting was cancelled since there was no participation. 05-April-24 Action Items / Status: - To discuss the earlier Release notes that are currently in master (r_1 - r_9) - Ron has moved out the earlier StarlingX RNs from master. The latest version only is available on master. - DONE - Stx.6.0 is EOL as of Dec 2022: https://wiki.openstack.org/wiki/StarlingX/Release_Plan#List_of_Releases. Email will be sent out declaring EOL. - Stx 9.0 Release Tracking Spreadsheet: Doc Stories are tracked in https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrT… - Team to add in the commit message stories planned for Stx 9.0 only. The rest of the stories that are not planned for 9.0 needs to remain unmerged in Stx master for future releases of StarlingX. - Release successfully delivered - Release Feature 10 planning has started: https://docs.google.com/spreadsheets/d/1FMNIfVSRSsdDuWizZzWhZvvcSfYCoiXgW-a… - We need to attempt to catch up to a more recent version of Sphinx that better aligns with OpenStack and stay current: AR: Ron (Update to a more current version) - Need to update tox version used in Zuul - AR: Ron Gerrit reviews: - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - Merged ~5 Reviews for all releases. Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs 11 outstanding launchpad bugs. Some defects are assigned back to the reporter due to lack of response or clarification. Miscellaneous Updates: Virtual Project Teams Gathering (PTG)[1] event is scheduled for April 8-12, 2024; - https://etherpad.opendev.org/p/stx-ptg-planning-april-2024 - PrePTG https://etherpad.opendev.org/p/opendev-preptg-202402 - Update the Verified H/W page with the automated script updates https://www.windriver.com/studio/operator/self-validated-and-certified-host… - Currently Commented out - Script needs to be updated- Waiting for updates to the script -AR Ron Engineering Status: StarlingX Eng Stx Status: https://etherpad.opendev.org/p/stx-status StarlingX Eng Status 2023 https://etherpad.opendev.org/p/stx-cores StarlingX OS Status: https://etherpad.opendev.org/p/stx-distro-other ____________________________ Starlingx-discuss mailing list Starlingx-discuss(a)lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss<https://urldefense.com/v3/__http:/lists.starlingx.io/cgi-bin/mailman/listin…>

1 70

Overview slide deck - Is it still accurate? - HELP NEEDED
by Ildiko Vancsa 20 Apr '26

20 Apr '26

Hi StarlingX Community, I'm reaching out to you about the StarlingX project's overview slide deck: https://www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf I was recently asked for materials, preferably slides, that can be helpful as an overview on the StarlingX platform in terms of use cases, capabilities, etc. The project's overview slide deck came to my mind to point people at, but I'm not sure how up to date it is. I need help from the community to understand if the information in the slide deck is still accurate, or, in what ways it needs to be updated to introduce StarlingX in its current state. Can you please help me with letting me know what needs to be removed or updated and what still seems to be good information to keep in the slides? Thanks and Best Regards, Ildikó ——— Ildikó Váncsa Director of Community OpenInfra Foundation

5 8

StarlingX Sanity Master Test LAYERED build ISO 20260219T051000Z
by Celidonio Heiland Puteri, Arthur 08 Apr '26

08 Apr '26

Sanity Test from February 19, 2026 https://mirror.starlingx.windriver.com/mirror/starlingx/master/debian/monol… Status: Green SX sanity Passed: 14 (100.0%) Failed: 0 (0.0%) Total Executed: 14 List of Test Cases: ------------------------------------------------------ PASS test_horizon_host_inventory_display_active_controller PASS test_lock_unlock_simplex PASS test_host_to_service_connection PASS test_pod_to_service_connection PASS test_pod_to_pod_connection PASS test_nginx_ingress_controller_applied PASS test_platform_integ_apps_applied PASS test_check_all_pods_healthy PASS test_push_docker_image_to_local_registry_simplex PASS test_upload_charts_via_helm_upload_simplex PASS test_host_operations_with_custom_kubectl_app_simplex PASS test_sriovdp_netdev_connectivity_ipv6 PASS test_system_core_dumps PASS test_system_crash_reports DX sanity Passed: 18 (100.0%) Failed: 0 (0.0%) Total Executed: 18 List of Test Cases: ------------------------------------------------------ PASS test_horizon_host_inventory_display_active_controller PASS test_lock_unlock_standby_controller PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_swact PASS test_check_all_pods_healthy PASS test_check_alarms PASS test_platform_integ_apps_applied PASS test_nginx_ingress_controller_applied PASS test_push_docker_image_to_local_registry_standby PASS test_upload_charts_via_helm_upload_standby_controller PASS test_host_operations_with_custom_kubectl_app_standby PASS test_isolated_2processors_2big_pods_best_effort_standby_controller PASS test_force_reboot_host_standby_controller PASS test_force_reboot_host_active_controller PASS test_system_core_dumps PASS test_system_crash_reports

2 2

Minutes: Community Call (Feb 25, 2026)
by Khalil, Ghada 26 Feb '26

26 Feb '26

Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call Feb 25 2026 Standing topics - Build - Main Branch Debian Builds - Platform: Green - OpenStack: Green - ( some issues over the weekend with starlingx mirror going down .. but fixed now ) - 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. - 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 - Last sanity executed on Feb 19: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.… - Load used: 20260219T051000Z - Green for AIO-SX & Green for AIO-DX - Sanity LPs: - None - Debian Main Branch stx-openstack Sanity - Last sanity executed on Feb 24: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.… - Load Used: platform: 20260223T162439Z openstack: 2026-02-20 20:11:02 +0000 - Note: openstack builds are using epoxy - Green - Sanity LPs - None - Gerrit Reviews in Need of Attention - Trixie build/packaging content - The most urgent focus now is for re-structuring affecting bullseye - https://review.opendev.org/q/topic:%22stx-trixie-dir-change%22 - These reviews should have addressed the previous concern about diverging packages when that was not needed. - Update: All merged. - Lower priority reviews: (porting of bullseye packages over to trixie and building) - https://review.opendev.org/q/project:starlingx/metal+status:open+topic:%22s… - https://review.opendev.org/q/project:starlingx/config+status:open+topic:%22… - https://review.opendev.org/q/project:starlingx/ha+status:open+topic:%22stx-… - https://review.opendev.org/q/project:starlingx/config-files+status:open+top… - Still need to be rebased; lots of merge conflicts - 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. - Recommend the developers to add core reviewers explicitly on the reviews. Although not absolutely necessary, this would bring more attention to 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 - Trixie Code Merges - See notes in "Gerrit Reviews in Need of Attention" - 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 - No other new topics 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.… - 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 - Reverting CPU Core isolation - Sent to the mailing list on Feb 3 - Email: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.… - Status: Open >> Closed - Feb 4: New. Will ask Michel Desjardins to review and have someone from the container team respond - Feb 11: Chris responded on Feb 9; waiting for further response from the reporter - Feb 18: No further responses from the reporter; will close off next week if there is nothing further from the reporter. - Feb 25: No further responses, so closing.

1 0

Minutes: StarlingX Release Meeting - Feb 25 / 2026
by Khalil, Ghada 26 Feb '26

26 Feb '26

Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Feb 25 2026 stx.12.0 - Release/Feature Planning: https://docs.google.com/spreadsheets/d/1Insq01desInEl76Wz7BUzY1fWKmTmAtZTk9… - Next Release Milestone - Milestone-3 - Forecast: Mar 4 -- next week. Plan to do the official review on the community call on March 4. - Criteria - Feature freeze: All feature code merged and feature testing completing within an acceptable timeframe - Status: On track - 56 features are already code complete. 1 features still in progress; however, this is the trixie prep feature, so will be considered closed next week. - Debian OS Update: Move to the latest Trixie content (prep) - The majority of features are also tested. Only 13 features still in test. - No blocking issues from Automated Sanity and Regression - Status: On track - Recent sanity reports are green - platform: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.… - openstack: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.… - No critical issues severely impacting system stability or release test activities - Status: On track - No critical issues have been raised - Release regression testing starting - Status: On track - Testing is planned to start after MS-3 as per plan - Documentation plan defined; including a prioritized list of the various documentation items - Status: On track - Feature documentation updates are in progress - Blog Posts planned/available - Status: On track - Plan is in place as per below Blogs - OIDC Auth for StarlingX API/CLI & Support for OIDC IDP with MFA (stx.12.0) - Prime: Greg Waines / Rei Olive - Status: Planned - Forecast: mid-March - PTP Partial Timing Source (stx.12.0) - Prime: Ghada Khalil / Cole Walker - Status: Planned - Forecast: mid-May (TBC)

1 0

TSC & Community call is at the APAC-friendly time slot next week!
by Ildiko Vancsa 26 Feb '26

26 Feb '26

Hi StarlingX Community, This is a friendly reminder that we have the TSC & Community call happening in the APAC-friendly time slot next week! The call is scheduled to happen on March 4 at 7pm US Pacific Time / 10m pm US Eastern Time | March 5 at 0300 UTC / 11am China Standard Time. You can find dial-in information and further details here: https://zoom-lfx.platform.linuxfoundation.org/meetings/starlingx?view=week Best Regards, Ildikó ——— Ildikó Váncsa Director of Community OpenInfra Foundation

2 1

[tsc] Upcoming TSC elections timeline - REVIEW NEEDED
by Ildiko Vancsa 25 Feb '26

25 Feb '26

Hi StarlingX TSC, I created a patch that proposes the timeframe for the first TSC election in 2026: https://review.opendev.org/c/starlingx/election/+/943214 The timeline is the same as it was in the past 2 years, running the election during May, starting on May 5. Please review the patch and add review comments if you have any questions or concerns. Thanks and Best Regards, Ildikó ——— Ildikó Váncsa Director of Community OpenInfra Foundation

3 3

Sanity - StarlingX + STX-Openstack MASTER build ISO 2026-02-23 16:24:39 results
by Cardoso Cunha, Ricardo 24 Feb '26

24 Feb '26

Hi All, Here's the results for StarlingX + STX-openstack using the 2026-02-20 build : https://mirror.starlingx.windriver.com/mirror/starlingx/master/debian/monol… and STX-Openstack: https://mirror.starlingx.windriver.com/mirror/starlingx/master/debian/opens… SW_VERSION="26.03" BUILD_ID="20260223T162439Z" BUILD_DATE="2026-02-23 16:24:39 +0000" app_name: stx-openstack app_version: 26.03-0-debian-stable-latest build_date: 2026-02-20 20:11:02 +0000 OpenStack Deployed: stx-openstack master Node Config: All-in-one / simplex - ipv4 with VSWITCH_TYPE=ovs-dpdk Overall Sanity Results: [GREEN] Automated Test Results Summary: ------------------------------------------------------ Passed: 7 (100.00%) Failed: 0 (0,00%) Total Executed: 7 List of Test Cases: ------------------------------------------------------ PASS test_reapply_stx_openstack_no_change[controller-0] PASS test_openstack_services_healthy PASS test_horizon_create_delete_instance PASS test_ssh_to_hosts PASS test_system_alarms PASS test_ping_between_two_vms[ubuntu-noble-virtio-virtio] ----------------------------------------------------------------------- Status Color Legend: GREEN: Stable - None issues found. YELLOW: Attention - Minor/Major issues detected, no critical impact. RED: Critical - Critical issues found

1 0

Minutes: Community Call (Feb 18, 2026)
by Khalil, Ghada 19 Feb '26

19 Feb '26

Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call Feb 18 2026 Standing topics - Build - Main Branch Debian Builds - Platform: Mostly green this week. - One build failure reported today and is already fixed: https://review.opendev.org/c/starlingx/fault/+/977221 - LP: https://bugs.launchpad.net/starlingx/+bug/2141564 has been addressed. Container builds have been successful. - Ghada to ping CaioV to update the LP - OpenStack: Green - The current build is expected to fail, but will pass once rebuilt w/ https://review.opendev.org/c/starlingx/fault/+/977221 - Note: - Build package order fixes were merged late last week. The build durations increased for a few days, but are now back to normal. - 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. - Tooling for container image builds is still outstanding. Scott is actively working on that. - Status of trixie build: still red; issue with circular dependency. - Note: Designer builds seem to work, but don't successfully boot on hardware platforms - 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 since Feb 5; unclear why. - Last sanity executed on Feb 5: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.… - Load used: 20260205T051000Z - Green for AIO-SX & Green for AIO-DX - Sanity LPs: - None - Debian Main Branch stx-openstack Sanity - Last sanity executed on Feb 18: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.… - Load Used: platform: 20260217T051000Z openstack: 2026-02-15 21:43:39 +0000 - Note: openstack builds are using epoxy - Green - Sanity LPs - None - Gerrit Reviews in Need of Attention - Trixie build/packaging content - The most urgent focus now is for re-structuring affecting bullseye - https://review.opendev.org/q/topic:%22stx-trixie-dir-change%22 - These reviews should have addressed the previous concern about diverging packages when that was not needed. - Waiting on core reviewers to review/merge. - Lower priority reviews: - https://review.opendev.org/q/project:starlingx/metal+status:open+topic:%22s… - https://review.opendev.org/q/project:starlingx/config+status:open+topic:%22… - https://review.opendev.org/q/project:starlingx/ha+status:open+topic:%22stx-… - https://review.opendev.org/q/project:starlingx/config-files+status:open+top… - Still need to be rebased - 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. - Recommend the developers to add core reviewers explicitly on the reviews. Although not absolutely necessary, this would bring more attention to the reviews. - Scott also raised a concern about diverging packages (which may not be needed). Bob Church is aware of this and working w/ the trixie team to address. << Addressed - 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 - Trixie Code Merges - See notes in "Gerrit Reviews in Need of Attention" - 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 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.… - 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 - Reverting CPU Core isolation - Sent to the mailing list on Feb 3 - Email: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.… - Status: Open - Feb 4: New. Will ask Michel Desjardins to review and have someone from the container team respond - Feb 11: Chris responded on Feb 9; waiting for further response from the reporter - Feb 18: No further responses from the reporter; will close off next week if there is nothing further from the reporter.

1 0

Sanity - StarlingX + STX-Openstack MASTER build ISO 2026-02-17 05:10:00 results
by Cardoso Cunha, Ricardo 18 Feb '26

18 Feb '26

Hi All, Here's the results for StarlingX + STX-openstack using the 2026-02-15 build : https://mirror.starlingx.windriver.com/mirror/starlingx/master/debian/monol…<https://mirror.starlingx.windriver.com/mirror/starlingx/master/debian/monol…> and STX-Openstack: https://mirror.starlingx.windriver.com/mirror/starlingx/master/debian/opens…<https://mirror.starlingx.windriver.com/mirror/starlingx/master/debian/opens…> SW_VERSION="26.03" BUILD_ID="20260217T051000Z" BUILD_DATE="2026-02-17 05:10:00 +0000" app_name: stx-openstack app_version: 26.03-0-debian-stable-latest build_date: 2026-02-15 21:43:39 +0000 OpenStack Deployed: stx-openstack master Node Config: All-in-one / simplex - ipv4 with VSWITCH_TYPE=none Overall Sanity Results: [GREEN] Automated Test Results Summary: ------------------------------------------------------ Passed: 7 (100.00%) Failed: 0 (0,00%) Total Executed: 7 List of Test Cases: ------------------------------------------------------ PASS test_reapply_stx_openstack_no_change[controller-0] PASS test_openstack_services_healthy PASS test_horizon_create_delete_instance PASS test_ssh_to_hosts PASS test_system_alarms PASS test_ping_between_two_vms[ubuntu-noble-virtio-virtio] ----------------------------------------------------------------------- Status Color Legend: GREEN: Stable - None issues found. YELLOW: Attention - Minor/Major issues detected, no critical impact. RED: Critical - Critical issues found

1 0