[Starlingx-discuss] Minutes: Community Call (Aug 23, 2023)
Khalil, Ghada
Ghada.Khalil at windriver.com
Thu Aug 24 20:58:42 UTC 2023
Etherpad: https://etherpad.opendev.org/p/stx-status
Minutes from the community call
Aug 23, 2023
Standing topics
- Build
- Main Branch Debian Builds
- Green
- 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
- Failed with the same error as last week; failed due to disk space error; even though there should be enough
- Need to investigate more. Will attempt to shift the build schedule to avoid concurrent builds to see if this resolves the issue
- 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 22: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014451.html
- Status: Green for SX and DX
- Debian Main Branch stx-openstack Sanity
- Last sanity email sent on Aug 29: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014447.html
- Status: Yellow (issue which caused a red sanity last week was resolved)
- Two New LPs
- https://bugs.launchpad.net/starlingx/+bug/2030883
- https://bugs.launchpad.net/starlingx/+bug/2030888
- Team is currently focusing on Antelope, so it will take a while to investigate. Will also monitor if the issues are reproduced in the upcoming sanity runs.
- Gerrit Reviews in Need of Attention
- ARM Spec Review
- https://review.opendev.org/c/starlingx/specs/+/890514
- No progress in terms of review since last week.
- ScottL and Greg are planning to review this week. It was also suggested that MarkA and Yue Tao (OS team) to review
- Memory Utilization Documentation
- https://review.opendev.org/c/starlingx/docs/+/890816/4/doc/source/deploy_install_guides/release/bare_metal/aio_duplex_install_kubernetes.rst#290
- Looking for input from the community on what to recommend in terms of memory usage.
- ChrisF provided some input on the call; suggesting that the default values may need to be discussed instead of suggesting that each user has to change the defaults
- The values maybe dependent on the config used (ex: deploying stx-openstack app)
- 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
- Discussed in the TSC portion - See: https://etherpad.opendev.org/p/stx-cores
- Milestone-3 will not be declard today.
- Action: Ghada to send a summary of the feature cotent to the mailing list and get feedback
- Email sent: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014458.html / waiting for feedback until next week
- October PTG (virtual)
- https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014454.html
- https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014448.html
- Time slots have been proposed on the mailing list.
- Container Lights-On Activities
- The container team has a number of lights-on activity every release - like upgrading to new version of k8s.
- Is a spec needed for that type of work?
- Greg suggested to have one high-level spec every stx release to summarize the planned upversioning work - including k8s, CNIs, applications, kernel, etc.
- Agreed to have a spec starting in stx.10.0
ARs from Previous Meetings
- 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: SteveG/Jackie to raise this issue w/ the TSC on Aug 23.
- Status: Open. Not discussed in the TSC on Aug 23 / SteveG on vacation; added to TSC agenda for Aug 30.
- 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
- Status: In progress. Under discussion on the mailing list
- https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014409.html
- 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
- Status: In progress. Ildiko is talking to dockerhub people. Mike will sync up with Ildiko. Deadline for payment is Aug 24.
- Action: Ildiko to raise the topic of looking for alternatives to dockerhub with the TSC. Ultimately, this will become a community resoucing discussion
- Status: Open. Not discussed in the TSC on Aug 23; added to TSC agenda for Aug 30.
- 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.
- Status: Open. Not sent yet
- Renaming App Repos to remove "armada" from the name
- 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
- Status: Closed. Build and Container/Apps team to work together to determine the timeline/resourcing for this item
Open Requests for Help not discussed this week
- 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