Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call June 12, 2024 Standing topics - Build - Main Branch Debian Builds - Green; All builds: iso, container, and openstack - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/master/debian/ - stx.9.0 Weekly RC Builds - Green - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/rc/9.0/ - stx.8.0 Weekly RC Builds - Green - Build Output: https://mirror.starlingx.windriver.com/mirror/starlingx/rc/8.0/ - Note: Extended EOL for stx.8.0 to Sept 2024 - Feature Branch Weekly Builds for kernel update for stx.10.0 (f/kernel-6.6) - ISO build is Green - The docker image build is failing on stx-neutron - Openstack build is failing - https://bugs.launchpad.net/starlingx/+bug/2067500 - https://bugs.launchpad.net/starlingx/+bug/2068031 - OS team identified the root-cause. There's a missing commit that needs to be cherry-picked to the kernel branch. Then will try a rebuild. - Note: There are also install/runtime issues w/ the 6.6 kernel branch builds that are under investigation - From Linda: The issue is preventing us from being able to unlock controller-1 on multi-node systems - Feature Branch for bookworm (f/bookworm) - ScottL made some build tools changes to pull content from the correct mirror. - 95% of packages are building properly. Failures are seen in gcc and qemu packages; - Build tools support is considered done. The packaging porting effort is on hold due to lack of resources - ARM Builds - No progress on seting up ARM build machine as the f/w is password locked. - Still working w/ supermicro to get a tool to enable accessing the f/w. - Sanity - Debian Main Branch Platform Sanity - Labs were not available earlier this week. The plan is to run the sanity on June 13. - Last sanity email sent on June 3: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Green - Other LPs raised from sanity: - LP: https://bugs.launchpad.net/starlingx/+bug/2056295 - One fix was merged, but issue is intermittent, so waiting for some soak - Debian Main Branch stx-openstack Sanity - Team is continuing with re-enabling sanity and lab setup. - Hope to have a more concrete update next week. - Thales is helping to facilitate this activity - Gerrit Reviews in Need of Attention - ARM port Reviews: - Covered in TSC. Still not merged due to lack of build machines / regular builds. - 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 - Debian Bullseye is EOL at the end of June - That being said, the OS team and the larger community has no resources to migrate to bookworm in the stx.10.0 timeframe. - So the end result is that we are taking the risk on sticking w/ Bullseye for the coming release - The risk is mainly to CVE fixes not being available for the various packages ARs from Previous Meetings - None Open Requests for Help - Ildiko looking for help to update the overview / on-boarding slide deck - https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.i... - Status: Open (Reported: May 8) - May 8: Greg will provide input - May 15: On Greg's To-Do list - May 22: Greg provided an initial response and added others for their input - May 29: Still waiting for responses from Tee Ngo, Joshua Reed, Steven Webster - Jun 5: Still no responses from Tee Ngo, Joshua Reed, Steven Webster - Jun 12: Response received from Steven Webster. Not likely to get responses from Tee and Joshua, so Greg will have another look. - Felipe Borges is looking to contribute to StarlingX by fixing bugs - Discussed in the community meeting on May 22. The suggestion is to engage with one of the sub-project teams in the area of interest. They should be able to provide suggestions on what to work on. - Status: Open (Reported: May 22) - May 22: Felipe will reach out to the platform-services/flock team - May 29: No further update as Felip didn't join the community call this week - Jun 5: " - Jun 12: "