[Starlingx-discuss] Minutes: Community Call (Aug 30, 2023)

Khalil, Ghada Ghada.Khalil at windriver.com
Sun Sep 3 00:07:49 UTC 2023


Etherpad: https://etherpad.opendev.org/p/stx-status

Minutes from the community call
Aug 30, 2023

Standing topics
- Build
     - Main Branch Debian Builds
          - Green. Two failures earlier in the week, but they were resolved.
          - Build Output: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/
     - Antelope Feature Branch Debian Builds
          - Green
     - stx.6.0 Weekly RC Builds
          - Failed due to download errors
          - 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 due to download errors; got past the previous errors related to disk space error.
          - 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 29: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014467.html
          - Status: Green for SX and DX
     - Debian Main Branch stx-openstack Sanity (Ussuri)
          - Last sanity email sent on Aug 29: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014472.html
          - Status: Yellow
          - Same LPs which were reported from last week
               - https://bugs.launchpad.net/starlingx/+bug/2030883
               - https://bugs.launchpad.net/starlingx/+bug/2030888
               - Confirmed that the issues are reproducible based on two sanity runs on Ussuri. Team will attempt to reproduce on Antelope and investigate further. No plan to investigate on Ussuri currently,
- Gerrit Reviews in Need of Attention
     - ARM Spec Review
          - https://review.opendev.org/c/starlingx/specs/+/890514
          - Still waiting for Greg, Scott, MarkA/Yue Tao to review.
     - Memory Utilization Documentation
          - https://review.opendev.org/c/starlingx/docs/+/890816
          - Feedback provided by Chris and Greg
     - Local registry guide for developers to speed up installation
          - https://review.opendev.org/c/starlingx/docs/+/884643
          - Got +2 and several +1. Juanita did the final merge during the meeting.
     - 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
     - Discussion is continuing in the TSC portion of the meeting - See: https://etherpad.opendev.org/p/stx-cores
     - Milestone-3 still needs to be re-forecasted
     - Emails are sent to the mailing list on the various risks and still waiting for feedback
     - Team is leaning towards delaying the release vs releasing as a tech preview. Final descision is still TBD.
- Any interest in a guide for packaging a FluxCD app? - Douglas Pereira
     - There is some material already in the stx wiki
          - https://wiki.openstack.org/wiki/StarlingX/Containers/HowToAddNewFluxCDAppInSTX
     - This is on the To-Do list for the container-infra as well and they are open to collaborate with Douglas and team 
- Reminder: Next week the community call is in the APAC friendly timezone

ARs from Previous Meetings
- ARM Enablement - Jackie Huang
     - The ARM team is providing 6 servers to the StarlingX community and would like WR to host them.
          - Discussed in the TSC portion of the meeting  - See: https://etherpad.opendev.org/p/stx-cores
          - This requires additional resources to manage the servers within WR; no current bandwidth to take this on.
          - Action: SteveG following up on funding.
          - Status: Open
     - 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: Closed 
              - The ARM team received the info and are working to setup the CI/CI internally.
              - Agreed to close this action
- dockerhub changed StarlingX from free-team to team - Scott Little
     - Discussed in the TSC portion of the meeting  - See: https://etherpad.opendev.org/p/stx-cores
     - Action: Ildiko/Mike working to address this with docker.
     - Status: In progress. 
          - (Ildiko) StarlingX is still listed as OSS Program-supported organization as of August 30, 2023
          - Ildiko submitted the application to extend the project's participation in Docker's OSS Program
     - Action: Ildiko to raise the topic of looking for alternatives to dockerhub with the TSC. Ultimately, this will become a community resoucing discussion
     - Status: Deferred. Ildiko shared the alternatives on the mailing list. This should still be considered for the future as dockerhub policies are not consistent
- 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: In progress. 
          - Discussion started on the mailing list: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014481.html

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