Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call November 16, 2022 Standing topics - Build - Main Branch CentOS Builds - Green all week - Main Branch Debian Builds - 6 out of 7 builds passed. - One failure last night was related to a transient connectivity issue. Build will be re-triggered tonight as per the usual schedule. - Debian Build Acceleration/Reuse Feature - The Acceleration feature is now functional for the ISO build, but not yet for container builds. - Work on container build re-use has not started yet. - Weekly CentOS Builds for stx.6.0 & stx.7.0 - Complete - Sanity - CentOS Main Branch Sanity w/ stx-openstack - Last sanity email sent on Nov 10: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013554.... - Status: Red - LP: https://bugs.launchpad.net/starlingx/+bug/1991701 - Already addressed on the latest build. - Team discussing options of (1) moving to new CentOS build to pick up fix OR (2) waiitng for stx-openstack sanity on Debian - Currently, the platform CentOS build is fixed on Sept18 which is the last green sanity build for CentOS. - stx-openstack sanity transition to Debian - Planned for the Dec time-frame. On track. - Email to the mailing list: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-October/013487.h... - Debian Main Branch Sanity - Had a tool issue which prevented install/sanity from running. - Team believes the issue is addressed. - Will aim to trigger another sanity by end of week. If not, it will be on the coming Monday. - Last sanity email sent on Nov 8: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013541.... - Status: Green - Gerrit Reviews in Need of Attention - From last meeting: Fixes to libvirt env: https://review.opendev.org/c/starlingx/tools/+/863735 - Review comments provided; waiting for new patchset from author - 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 - TSC Elections - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013568.... - IMPORTANT: Voters need to opt-in to receive a ballot ARs from Previous Meetings - None Open Requests for Help - StarlingX 6.0 fails to deploy - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013536.... - This is using the released stx.6.0 release which hasn't changed, so unclear why this is failing now. - ScottK Update (Nov 16): Fails to install on one node, but installed successfully on other ones. - Appears to be some kind of anomoly specific to this node. - Consider Closed as it's tied to a specific h/w system - StarlingX 7.0 & 8.0 deployment failures - NEW - Reported by ScottK in the Nov 16 meeting - Working through installation issues on various hardware. Will share more info w/ the mailing list once issues are more isolated. - Virtio-forwarder with StarlingX - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013505.... - ScottK responded with additional questions: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-November/013532.... - Waiting for response / no response as of Nov 16 - Enabling cpu_dedicated_set - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-September/013382... - Last Question posted in the thread: Is there a way I can enable application-isolation across all the worker nodes including new nodes to be added in future? - Responses provided. There is no capability to do this at the moment. - Consider Closed.