Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call Aug 9, 2023 Standing topics - Build - Main Branch Debian Builds - Builds are passing, but the container builds weren't publishing images to dockerhub. - This has been addressed and a build is in progress to publish the images. - Build Output: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/ - stx.6.0 Weekly RC Builds - Green. CENGN transition issues have been resolved. - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/ - Note: No container image builds are done for stx.6.0 - stx.7.0 Weekly RC Builds - Green. CENGN transition issues have been resolved. - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/ - Note: No container image builds are done for stx.7.0 - stx.8.0 Weekly RC Builds - Green - Build Output: https://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/ - Note: The same issue of not publishing images (as in the main branch) exists for stx.8.0 and will be resolved in the next build. - Sanity - Debian Main Branch Platform Sanity - Last sanity email sent on Aug 9: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014394.ht... - Status: Green for SX and DX - Debian Main Branch stx-openstack Sanity - No sanity this week - reason: unknown as no reps were on the community call - Last sanity email sent on Aug 1: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014357.ht... - Status: RED - https://bugs.launchpad.net/starlingx/+bug/2029376 Fix merged on Aug 2 - https://bugs.launchpad.net/starlingx/+bug/2029378 Fix merged on Aug 3 - Gerrit Reviews in Need of Attention - No Gerrit reviews needing attention this week. - 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 - Request from Juanita that engineers making contributions to the StarlingX docs copy the doc leads - Action: Juanita to send an email to the stx-discuss mailing list - Matrix setup for community collaboration - Ildiko is working with Jeremy on the setup and room creation - Launchpad status not being automatically updated - This has been addressed now! LPs are updating automatically. - We still suggest that developers check the status as this functionality has been broken multiple times in the past. ARs from Previous Meetings - dockerhub is cracking down on download limits - Davlet introduced an option to workaround this issue by having individual users login instead of using the same corporate IP - Action: Davlet to share this info on the mailing list and also open a stx.docs launchpad to add this info permanently to the project docs - Status: Closed - Email sent by Davlet. Wiki was also updated. - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014337.html - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014338.html - StarlingX docs were not updated as in general the build info in the docs is outdated and needs a bigger activity to clean it up. This is on the Build team's To-Do list. - Another suggestion is to look at an alternative to dockerhub - Examples: quay.io / nexsus-repo community edition / harbour - https://quay.io - From Ildiko: some open-infra projects moved to quay due to the dockerhub limits. Perhaps we can get some input from them. - https://www.sonatype.com/products/sonatype-nexus-repository - This would have to be handled as a feature propsal / spec given the large scope - Work would be required by the Build team - Note: StarlingX uses open-source images as well which are hosted in dockerhub - Allow stx-openstack to be built independently from the platform - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-June/014206.html - The proposal has changed from using a manifest to using a branch. - Action: Build team to propose a timeline based on their priorities/availability - Status: Closed - The proposal has changed from using a manifest to using a branch. - Plan to start this work within a week. Expect to complete by mid-Aug (TBC) - StoryBoard tracking the work: https://storyboard.openstack.org/#!/story/2010797 - Renaming App Repos to remove the "armada" - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-June/014215.html - Minor / cosmetic change. Lower priority, but would be nice to do. Should have no impact on runtime. - Action: Build team to propose a timeline based on their priorities/availability. (lower priority than the manifest repo re-config) - Status: Open - No update. Build team is focused on CENGN transition - Will likely only be planned after splitting the openstack build Open Requests for Help - User Questions - sent by Ildiko - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014391.ht... - Responses are coming in on the mailing list - Issues raised are related to networking setup. - Bruno/team provided an automated script for virtual installation (vbox) which should handle the networking setup. - As per Bruno, there are some vbox bugs which could be impacting users. Bruno will sent info on these unresolved issues. - Not able to use NVIDIA drivers with StarlingX vbox installation - raised in the meeting by Manju Rupani - NVIDIA drivers should not be required to successfully setup StarlingX vbox installation, so the suggestion is to try w/o them first. - Help w/ Install - Two people asking for help with installation on IRC - Bruno is trying to help them, but it appears that they are in a different timezone. If others can participate, it would be great. - Status: Open - Discussion is continuing between Bruno and others on IRC. This is related to the "User Questions" topic above. - The questions are a mix of how to setup a virtual env as well the installation itself - For virtual env, there are two options currently: vbox & libvirt/kvm - Note: There is recent effort to get libvirt/kvm working. Email reference: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014267.html