[Starlingx-discuss] Minutes: Community Call (Aug 16, 2023)
Khalil, Ghada
Ghada.Khalil at windriver.com
Mon Aug 21 01:09:58 UTC 2023
Etherpad: https://etherpad.opendev.org/p/stx-status
Minutes from the community call
Aug 16, 2023
Standing topics
- Build
- Main Branch Debian Builds
- Green. Issue with publishing images to dockerhub has been addressed.
- Build Output: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/
- Antelope Feature Branch Debian Builds
- Green
- stx.6.0 Weekly RC Builds
- Green
- 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
- Red. Build failed due to disk space error; even though there should be enough
- 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 13: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014404.html
- Status: Green for SX and DX
- Debian Main Branch stx-openstack Sanity
- Last sanity email sent on Aug 13: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014403.html
- Status: Red / Blocked
- https://bugs.launchpad.net/starlingx/+bug/2031401
- Introduced by a recent code change which was reverted. Should not impact the next sanity
- Gerrit Reviews in Need of Attention
- ARM Spec Review
- https://review.opendev.org/c/starlingx/specs/+/890514
- Has +1 from Chris. ScottL will review today. Greg is only available next 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
- stx.9.0 Release Status - Ghada Khalil
- Milestone-3 is planned for next week
- Not enough information is available from the feature primes to make the decision on the milestone and follow-up release plans
- Risk was also raised for release verification due to resourcing constraints
- ARM Enablement - Jackie Huang
- The ARM team is providing 6 servers to the StarlingX community, but there is no place to host them.
- The ARM team is not able to host them directly for public community access
- Steve Geary has been trying to find space to host these machines, but not much traction to date over many weeks
- Need a forum to escalate this issue. Agreed to start with the TSC and go from there
- Action: Steve/Jackie to raise this issue w/ the TSC on Aug 23.
- The ARM team also have questions about how to setup a CI/CD on those machines
- https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014396.html
- Action: Davlet to reply to the email with some initial responses
- dockerhub changed StarlingX from free-team to team - Scott Little
- This was done automatically by dockerhub. Not clear what the reason is.
- The cost is $300/year. Mike Matteson was following up
- Action: Scott to connect Ildiko with Mike
- Action: Ildiko to raise the topic of looking for alternatives to dockerhub with the TSC
- Ultimately, this will become a community resoucing discussion
- Looking for community members to participate in US gov security initiative - Manju Rupani
- Suggested to introduce the topic on the mailing list and see if there is any interest
- Action: Manju to send to the mailing list.
ARs from Previous Meetings
- 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
- Status: Closed. Email sent to mailing list: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014407.html
- 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.
- Work required by Build team and Container/Apps team.
- Action: Joshua Reed to create a story board to track this work.
- Update: 8/16/23 - Storyboard link: https://storyboard.openstack.org/#!/story/2010560
Open Requests for Help
- User Questions - sent by Ildiko
- https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014391.html
- 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.
- Status: Open
- Bruno responded with suggestions to the mailing list, but haven't received further feedback
- 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.
- Status: Open
- Still no success; looking for an alternative machine to setup the vbox installation
- 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
More information about the Starlingx-discuss
mailing list