From scott.little at eng.windriver.com Fri Sep 1 19:43:52 2023 From: scott.little at eng.windriver.com (Scott.Little) Date: Fri, 1 Sep 2023 15:43:52 -0400 Subject: [Starlingx-discuss] DockerHub rate limit issues In-Reply-To: <9783AC48-EDCF-40B0-99BC-88ADA27F4443@openinfra.dev> References: <2E3BFA94-F03F-4545-AA3A-7ABAF885B923@openinfra.dev> <92826b45-9daa-19db-7ae2-9717eb0fbceb@windriver.com> <4E226ECC-6367-485D-94CA-EBB10389CFB0@openinfra.dev> <3D52AA13-4300-4C7E-BCBD-4268997C3F7D@openinfra.dev> <1545ff0e-e882-4025-bc21-1109733548c5@windriver.com> <9783AC48-EDCF-40B0-99BC-88ADA27F4443@openinfra.dev> Message-ID: <1b2030ef-f7db-4555-ad36-4340365128bd@eng.windriver.com> Hi Ildiko The majority of StarlingX developmers are employed by WindRiver. In addition, the daily StarlingX builds and PV effort have both moved to WindRiver hosted machines recently.? Now the documented StarlingX working model was to use anonymous pulls. So it was WindRiver's external IP address, rather than user accounts, that was getting 'billed' for all this activity. Scott On 2023-08-29 16:15, Ildiko Vancsa wrote: > CAUTION: This email comes from a non Wind River email account! > Do not click links or open attachments unless you recognize the sender and know the content is safe. > > Hi Scott, > > Thank you for the additional details. > > Another quick question to clarify. When you say "drove our quota down?, what does that mean exactly? What is ?our? in this context? And is that quota assigned to the IP address, or to a DockerHub user, or the images themselves? > > Thanks, > Ildik? > > ??? > > Ildik? V?ncsa > Director of Community > Open Infrastructure Foundation > > > > > >> On Aug 29, 2023, at 12:48, Scott Little wrote: >> >> It was hitting many images, not just golang. I just don't have any logs left from those failures. >> >> I don't see the OSS mark on the golang images, so perhaps those images drove our quota down to zero. However once the quota hit zero, then any anonymous download of an image could trigger the download failure, including OSS ones. The strange part was that the OSS download failures are only seen within build containers. The same image could be anonymously download on the containers host just fine. Both container and host were being billed to the same IP address. >> >> Scott >> >> >> On 2023-08-21 11:36, Ildiko Vancsa wrote: >>> CAUTION: This email comes from a non Wind River email account! >>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>> >>> Hi Scott, >>> >>> I also just recognized, that the snipped that you copied in refers to a golang image: ?Step 1/9 : FROMgolang:1.19 toomanyrequests: You have reached your pull rate limit.?. DO you have the same issue with StarlingX images as well? Or is it always the golang step that fails? >>> >>> Thanks, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Director of Community >>> Open Infrastructure Foundation >>> >>> >>> >>> >>> >>>> On Aug 18, 2023, at 12:13, Ildiko Vancsa wrote: >>>> >>>> Hi Scott, >>>> >>>> Great, thank you for the pointers. >>>> >>>> I reached out to Docker on the channel that is dedicated for their open source program, and also included the links that you added below so they have the full context. I will get back with updates on this thread, if I receive anything beyond what you got on the forums already. >>>> >>>> Thanks and Best Regards, >>>> Ildik? >>>> >>>> ??? >>>> >>>> Ildik? V?ncsa >>>> Director of Community >>>> Open Infrastructure Foundation >>>> >>>> >>>> >>>> >>>> >>>>> On Aug 17, 2023, at 07:40, Scott Little wrote: >>>>> >>>>> Here is a sample from a failed build ... >>>>> >>>>> docker build . --no-cache ... >>>>> Sending build context to Docker daemon 37.68MB >>>>> >>>>> Step 1/9 : FROMgolang:1.19 >>>>> toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading:https://www.docker.com/increase-rate-limit >>>>> make: *** [builder-build] Error 1 >>>>> >>>>> One thing to note, It's pulls from within our build container that hits the problem. We don't see it when pulling from bare metal hardware. >>>>> >>>>> I've tried raising the issue with the docker community here ... >>>>> >>>>> https://github.com/moby/moby/issues/46092#issuecomment-1654243988 >>>>> >>>>> https://forums.docker.com/t/inconsistent-behaviour-of-docker-pull-rate-limit/136896/2 >>>>> >>>>> We seem to be avoiding the rate limit by using docker login. Formal StarlingX builds are using a couple of service accounts. Designers were asked establish there own personal accounts with dockerhub. >>>>> >>>>> >>>>> >>>>> On 2023-08-16 16:17, Ildiko Vancsa wrote: >>>>>> CAUTION: This email comes from a non Wind River email account! >>>>>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>>>> >>>>>> Hi Scott, >>>>>> >>>>>> I looked into the DockerHub download issue again, to the capacity that I could. To confirm what was mentioned already, I have not found anything that would explain what the community is experiencing in terms of rate limits: >>>>>> >>>>>> - The StarlingX project is still listed as ?Sponsored OSS?: https://hub.docker.com/u/starlingx >>>>>> - The DockerHub docs point to a blog post that says ?we will suspend data pull rate restrictions, where no egress restrictions will apply to any Docker users pulling images from the approved OSS namespaces?: https://www.docker.com/blog/expanded-support-for-open-source-software-projects/ >>>>>> - I haven?t received any notifications from DockerHub recently about not meeting the criteria to participate in their open source program anymore >>>>>> >>>>>> Can you please share a screenshot or the error message that you are getting about hitting a pull rate limit? Also, are you getting that on every repo, or just specific ones? >>>>>> >>>>>> Once having more background information, I will reach out to the DockerHub team to see what the background issue might be. >>>>>> >>>>>> Thanks and Best Regards, >>>>>> Ildik? >>>>>> >>>>>> ??? >>>>>> >>>>>> Ildik? V?ncsa >>>>>> Director of Community >>>>>> Open Infrastructure Foundation >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >> From scott.little at windriver.com Fri Sep 1 19:41:25 2023 From: scott.little at windriver.com (Scott Little) Date: Fri, 1 Sep 2023 15:41:25 -0400 Subject: [Starlingx-discuss] DockerHub rate limit issues In-Reply-To: <9783AC48-EDCF-40B0-99BC-88ADA27F4443@openinfra.dev> References: <2E3BFA94-F03F-4545-AA3A-7ABAF885B923@openinfra.dev> <92826b45-9daa-19db-7ae2-9717eb0fbceb@windriver.com> <4E226ECC-6367-485D-94CA-EBB10389CFB0@openinfra.dev> <3D52AA13-4300-4C7E-BCBD-4268997C3F7D@openinfra.dev> <1545ff0e-e882-4025-bc21-1109733548c5@windriver.com> <9783AC48-EDCF-40B0-99BC-88ADA27F4443@openinfra.dev> Message-ID: <4b37f4e4-09c4-4502-8bbd-cb8baefefb25@windriver.com> Hi Ildiko The majority of StarlingX developmers are employed by WindRiver.? In addition, the daily StarlingX builds and PV effort have both moved to WindRiver hosted machines recently.? Now the documented StarlingX working model was to use anonymous pulls. So it was WindRiver's external IP address, rather than user accounts, that was getting 'billed' for all this activity. Scott On 2023-08-29 16:15, Ildiko Vancsa wrote: > CAUTION: This email comes from a non Wind River email account! > Do not click links or open attachments unless you recognize the sender and know the content is safe. > > Hi Scott, > > Thank you for the additional details. > > Another quick question to clarify. When you say "drove our quota down?, what does that mean exactly? What is ?our? in this context? And is that quota assigned to the IP address, or to a DockerHub user, or the images themselves? > > Thanks, > Ildik? > > ??? > > Ildik? V?ncsa > Director of Community > Open Infrastructure Foundation > > > > > >> On Aug 29, 2023, at 12:48, Scott Little wrote: >> >> It was hitting many images, not just golang. I just don't have any logs left from those failures. >> >> I don't see the OSS mark on the golang images, so perhaps those images drove our quota down to zero. However once the quota hit zero, then any anonymous download of an image could trigger the download failure, including OSS ones. The strange part was that the OSS download failures are only seen within build containers. The same image could be anonymously download on the containers host just fine. Both container and host were being billed to the same IP address. >> >> Scott >> >> >> On 2023-08-21 11:36, Ildiko Vancsa wrote: >>> CAUTION: This email comes from a non Wind River email account! >>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>> >>> Hi Scott, >>> >>> I also just recognized, that the snipped that you copied in refers to a golang image: ?Step 1/9 : FROMgolang:1.19 toomanyrequests: You have reached your pull rate limit.?. DO you have the same issue with StarlingX images as well? Or is it always the golang step that fails? >>> >>> Thanks, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Director of Community >>> Open Infrastructure Foundation >>> >>> >>> >>> >>> >>>> On Aug 18, 2023, at 12:13, Ildiko Vancsa wrote: >>>> >>>> Hi Scott, >>>> >>>> Great, thank you for the pointers. >>>> >>>> I reached out to Docker on the channel that is dedicated for their open source program, and also included the links that you added below so they have the full context. I will get back with updates on this thread, if I receive anything beyond what you got on the forums already. >>>> >>>> Thanks and Best Regards, >>>> Ildik? >>>> >>>> ??? >>>> >>>> Ildik? V?ncsa >>>> Director of Community >>>> Open Infrastructure Foundation >>>> >>>> >>>> >>>> >>>> >>>>> On Aug 17, 2023, at 07:40, Scott Little wrote: >>>>> >>>>> Here is a sample from a failed build ... >>>>> >>>>> docker build . --no-cache ... >>>>> Sending build context to Docker daemon 37.68MB >>>>> >>>>> Step 1/9 : FROMgolang:1.19 >>>>> toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading:https://www.docker.com/increase-rate-limit >>>>> make: *** [builder-build] Error 1 >>>>> >>>>> One thing to note, It's pulls from within our build container that hits the problem. We don't see it when pulling from bare metal hardware. >>>>> >>>>> I've tried raising the issue with the docker community here ... >>>>> >>>>> https://github.com/moby/moby/issues/46092#issuecomment-1654243988 >>>>> >>>>> https://forums.docker.com/t/inconsistent-behaviour-of-docker-pull-rate-limit/136896/2 >>>>> >>>>> We seem to be avoiding the rate limit by using docker login. Formal StarlingX builds are using a couple of service accounts. Designers were asked establish there own personal accounts with dockerhub. >>>>> >>>>> >>>>> >>>>> On 2023-08-16 16:17, Ildiko Vancsa wrote: >>>>>> CAUTION: This email comes from a non Wind River email account! >>>>>> Do not click links or open attachments unless you recognize the sender and know the content is safe. >>>>>> >>>>>> Hi Scott, >>>>>> >>>>>> I looked into the DockerHub download issue again, to the capacity that I could. To confirm what was mentioned already, I have not found anything that would explain what the community is experiencing in terms of rate limits: >>>>>> >>>>>> - The StarlingX project is still listed as ?Sponsored OSS?: https://hub.docker.com/u/starlingx >>>>>> - The DockerHub docs point to a blog post that says ?we will suspend data pull rate restrictions, where no egress restrictions will apply to any Docker users pulling images from the approved OSS namespaces?: https://www.docker.com/blog/expanded-support-for-open-source-software-projects/ >>>>>> - I haven?t received any notifications from DockerHub recently about not meeting the criteria to participate in their open source program anymore >>>>>> >>>>>> Can you please share a screenshot or the error message that you are getting about hitting a pull rate limit? Also, are you getting that on every repo, or just specific ones? >>>>>> >>>>>> Once having more background information, I will reach out to the DockerHub team to see what the background issue might be. >>>>>> >>>>>> Thanks and Best Regards, >>>>>> Ildik? >>>>>> >>>>>> ??? >>>>>> >>>>>> Ildik? V?ncsa >>>>>> Director of Community >>>>>> Open Infrastructure Foundation >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >> From Ghada.Khalil at windriver.com Sat Sep 2 23:51:50 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sat, 2 Sep 2023 23:51:50 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Aug 30/2023 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Aug 30 2023 stx.9.0 - Release/Feature Planning: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing - Upcoming Release Milestones - Milestone-3: Aug 23 >> needs to be re-forecasted - stx.9.0 Release Risks - Less feature content - Email sent to the community: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014458.html - No feedback yet - Openstack Rebase to Antelope is at risk of delivery within the stx.9.0 release timeframe - Email sent to the community: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014437.html - stx-openstack team made progress on the proposal of how to merge back to the main branch - Need to review/close with the build team to be able to propose delivery dates - Release Verification Status - Email sent to the community: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014459.html - No feedback yet - Further discussion on the stx.9.0 release risks will continue in the TSC/community meetings as a larger audience participates. Blogs - No updates - FEC Device Configurability (fec-operator Integration) for ACC100 & N3000 - Prime: Balendu (Mouli) Burla - Forecast: May 1 >> May 19 >> Aug 15 >> needs update - Status: Confirmed / Not posted - PTP O-RAN Compliant API Notification - Prime: Ghada Khalil - Forecast: Jun 30 >> Oct 15 - Status: Confirmed / Not posted From Ghada.Khalil at windriver.com Sun Sep 3 00:07:49 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sun, 3 Sep 2023 00:07:49 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Aug 30, 2023) Message-ID: 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 From Gabriel.CalixtodePaula at windriver.com Tue Sep 5 13:23:11 2023 From: Gabriel.CalixtodePaula at windriver.com (Calixto de Paula, Gabriel) Date: Tue, 5 Sep 2023 13:23:11 +0000 Subject: [Starlingx-discuss] Sanity and Regression - StarlingX + STX-Openstack MASTER build - No results this week Message-ID: Hi all, we'll be skipping this week's STX-Openstack sanity execution report due to some scheduling issues with our available testing hardware. Thanks STX-Openstack Distro Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ramaswamy.Subramanian at windriver.com Tue Sep 5 13:46:29 2023 From: Ramaswamy.Subramanian at windriver.com (Subramanian, Ramaswamy) Date: Tue, 5 Sep 2023 13:46:29 +0000 Subject: [Starlingx-discuss] DistCloud/Flock Services Project Meeting Minutes In-Reply-To: References: Message-ID: September 5, 2023: * StarlingX 9.0 Release: * Feature development in progress. More details are available in the release planning spread sheet. * Stale Code Review Cleanup to keep the review queue sane (more than 1 year old with no activity) * https://review.opendev.org/c/starlingx/distcloud/+/743475 * https://review.opendev.org/c/starlingx/config/+/838572 * https://review.opendev.org/c/starlingx/distcloud/+/817571 * Bug cleanup (more than 1 year old with no activity) * Closed. * https://bugs.launchpad.net/starlingx/+bug/1918722 * https://bugs.launchpad.net/starlingx/+bug/2026759 * https://bugs.launchpad.net/starlingx/+bug/2018409 * Candidate for Closure. * https://bugs.launchpad.net/starlingx/+bug/1980542 * https://bugs.launchpad.net/starlingx/+bug/1834081 * https://bugs.launchpad.net/starlingx/+bug/1848344 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peng.Peng at windriver.com Tue Sep 5 21:56:39 2023 From: Peng.Peng at windriver.com (Peng, Peng) Date: Tue, 5 Sep 2023 21:56:39 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20230904T060000Z Message-ID: Sanity Test from September 5, 2023 (https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230904T060000Z/outputs/iso/starlingx-intel-x86-64-cd.iso) Status: Yellow SX sanity Passed: 17 (100.0%) Failed: 0 (0.0%) Total Executed: 17 List of Test Cases: ------------------------------------------------------ PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_push_docker_image_to_local_registry_active PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_isolated_2p_2_big_pod_best_effort_HT_AIO PASS test_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS test_sriovdp_netdev_connectivity_ipv4[1-1-calico-ipam] PASS test_sriovdp_mixed_add_vf_interface[1] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] DX sanity Passed: 19 (100.0%) Failed: 0 (0.0%) Total Executed: 19 List of Test Cases: ------------------------------------------------------ PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host PASS test_swact_controller_platform PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_push_docker_image_to_local_registry_active PASS test_push_docker_image_to_local_registry_standby PASS test_upload_charts_via_helm_upload FAIL test_host_operations_with_custom_kubectl_app PASS test_isolated_1p_1pod_AIO PASS test_force_reboot_host[active_controller-True] PASS test_force_reboot_host[active_controller-False] PASS test_force_reboot_host[standby_controller-False] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] There was one failure found in DX sanity like: Locking controller timed out waiting for helm-controller to terminate We will open a Launchpad once the root cause is identified. Regards, PV team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Juanita.Balaraj at windriver.com Wed Sep 6 03:11:44 2023 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Wed, 6 Sep 2023 03:11:44 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 01-09-2023 In-Reply-To: References: Message-ID: Hello All, Here are last week's doc team meeting minutes. Details in [2]. Join us if you have interest in StarlingX docs! We meet on Fridays 6:00 a.m. PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Thanks, Juanita Balaraj ============ 01- September-23 Action Items / Status: - Stx 9.0 Release Tracking Spreadsheet: Doc Stories are tracked in https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing. - To add stories that are planned for Stx 9.0 - AR Juanita - WIP (add / replan as required). Features have been removed from Stx 9.0. See https://etherpad.opendev.org/p/stx-cores for more details. - Discussion about Merging the Installation Guides ; Virtual env with the Bare metal docs. WIP - Tabs Implement it upstream - AR Ron https://review.opendev.org/c/starlingx/docs/+/876107 - AR Ron/Juanita to talk to Greg - Split the docs and retain them as separate guides at a high level. Resue content from Bare Metal in the Virtual env docs. - AR Ron - Discussion about the tox version : https://review.opendev.org/c/starlingx/docs/+/890833 - AR Ron / Bruno (Allow list to be reviewed) - AR Bruno / Ron - Documentation Contributor Guide - StarlingX documentation - https://docs.starlingx.io/contributor/doc_contribute_guide.html - All to update the Contributor guide on an ongoing basis for new Styles / Standards implemented - The team to familiarize themselves with the Styles and Standards Guide. Contributor Guide - AR StarlingX Doc team Gerrit reviews: - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - Merged 2 Reviews. To get closure of the open reviews at the earliest. Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 9 outstanding bugs. - Closed 2 LP bugs. Miscellaneous Updates: - Stx. Virtual PTG Meeting: https://openinfra.dev/ptg/ - Stx Doc team is encouraged to participate in sessions as required. - Ron to update the Verified H/W page with the automated script updates https://www.windriver.com/studio/operator/self-validated-and-certified-hosts# - Currently Commented out - Script needs to be updated- Waiting for updates to the script -AR Ron - WIP - Bruno Muniz showed interest in creating DOC Videos supporting the StarlingX Installation Process. To check with Ildiko / Greg whether this is ok. These Videos can be hosted in a location in StarlingX. The Installation Docs can point to these videos - AR Bruno to get approvals from Ildiko / Greg for a future Update - Sphinx Tools - Need to have further discussions about the version used upstream vs. downstream - AR Ron -To determine version. - Docker Container upstream / downstream - AR Ron (Discuss it with Greg / Ildiko) - a long term project - Pending - Operations Guide Archive - On Hold until further clarifications are discussed with Greg (https://review.opendev.org/c/starlingx/docs/+/822030) Engineering Status: StarlingX Eng Stx Status: https://etherpad.opendev.org/p/stx-status StarlingX Eng Status 2023 https://etherpad.opendev.org/p/stx-cores StarlingX OS Status: https://etherpad.opendev.org/p/stx-distro-other ____________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Wed Sep 6 11:52:22 2023 From: Greg.Waines at windriver.com (Waines, Greg) Date: Wed, 6 Sep 2023 11:52:22 +0000 Subject: [Starlingx-discuss] 7pm Pacific on Every First Wednesday of the Month- Technical Steering Committee & Community Call Message-ID: ... just a reminder, it is the first Wednesday of the Month, so we are on the time-shifted slot for the STARLINGX Technical Steering Committee & Community Call this week. 7pm Pacific on Every First Wednesday of the Month- Technical Steering Committee & Community Call Call details * https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 * Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o Passcode: 419405 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes Agenda and Notes for the Technical Steering Committee: * Weekly TSC Meeting Agenda and Notes The agenda and notes for General Community Call are kept in Etherpads: * Weekly Agenda and Notes Please feel free to add items to the agendas for these meetings. Greg. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bruno.Muniz at encora.com Wed Sep 6 13:55:11 2023 From: Bruno.Muniz at encora.com (Bruno Drugowick Muniz) Date: Wed, 6 Sep 2023 13:55:11 +0000 Subject: [Starlingx-discuss] StarlingX App Deployment and Demo Message-ID: Hello, StarlingX Community. We want to share a work we've been doing in the past few weeks which now needs feedback from the Community. Scenario: package a user application/workload that's not part of the StarlingX ecosystem to run on StarlingX. Main objectives: - make it easier for newcomers to evaluate StarlingX with their workloads; - show some of the platform's capabilities. Our idea is to center all this around a quick and easy-to-consume Demo page, with some text and small video demonstrations for each important step. The main doc is complemented by (all still in progress): - a more detailed application Build Guide; - a single video with everything put together (might need captions to actually be helpful by itself): https://www.youtube.com/watch?v=IvBomQANXlo. It's important to understand that all the info that you'll find in the links above exists somehow either in https://docs.starlingx.io, https://wiki.openstack.org/wiki/StarlingX, or in the intangible place that I'll call "knowledge of the folks around the community" ?. It's not our intention to create yet another place to duplicate information, thus the repository linked above will be deleted at some point, but we needed a temporary place to organize all the info we gathered scattered around together with our own empiric tests. Feel free to use the GitHub Issues, reply to this message, or reach out to me on Matrix to give your feedback. Everything is valid for us to better understand the needs of the community, from small enhancements/fixes to opinions on the format of the presentation or technical aspects of what is being done in this demo regarding the StarlingX platform itself. This won't make us sad or anything: the journey to get all this info together brought us a lot of knowledge about the platform, which is something we are already applying on our next endeavor with StarlingX. Regards, Bruno. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peng.Peng at windriver.com Wed Sep 6 19:11:45 2023 From: Peng.Peng at windriver.com (Peng, Peng) Date: Wed, 6 Sep 2023 19:11:45 +0000 Subject: [Starlingx-discuss] FW: Sanity Master Test LAYERED build ISO 20230904T060000Z In-Reply-To: References: Message-ID: After analysis the failure, there is one launchpad opened. https://bugs.launchpad.net/starlingx/+bug/2034610 - Locking controller timed out waiting for helm-controller to terminate Thanks, Peng From: Peng, Peng Sent: Tuesday, September 5, 2023 5:57 PM To: starlingx-discuss at lists.starlingx.io Cc: Iqbal, Imad Subject: Sanity Master Test LAYERED build ISO 20230904T060000Z Sanity Test from September 5, 2023 (https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230904T060000Z/outputs/iso/starlingx-intel-x86-64-cd.iso) Status: Yellow SX sanity Passed: 17 (100.0%) Failed: 0 (0.0%) Total Executed: 17 List of Test Cases: ------------------------------------------------------ PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_push_docker_image_to_local_registry_active PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_isolated_2p_2_big_pod_best_effort_HT_AIO PASS test_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS test_sriovdp_netdev_connectivity_ipv4[1-1-calico-ipam] PASS test_sriovdp_mixed_add_vf_interface[1] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] DX sanity Passed: 19 (100.0%) Failed: 0 (0.0%) Total Executed: 19 List of Test Cases: ------------------------------------------------------ PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host PASS test_swact_controller_platform PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_push_docker_image_to_local_registry_active PASS test_push_docker_image_to_local_registry_standby PASS test_upload_charts_via_helm_upload FAIL test_host_operations_with_custom_kubectl_app PASS test_isolated_1p_1pod_AIO PASS test_force_reboot_host[active_controller-True] PASS test_force_reboot_host[active_controller-False] PASS test_force_reboot_host[standby_controller-False] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] There was one failure found in DX sanity like: Locking controller timed out waiting for helm-controller to terminate We will open a Launchpad once the root cause is identified. Regards, PV team -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openinfra.dev Thu Sep 7 01:02:04 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Wed, 6 Sep 2023 18:02:04 -0700 Subject: [Starlingx-discuss] TSC & Community call in the APAC-friendly time slot this week Message-ID: Hi StarlingX Community, It is a friendly reminder that this week?s TSC & Community Call will be in the APAC friendly time slot, in just under an hour. The call is scheduled to happen on September 6 at 7pm US Pacific Time / 10m pm US Eastern Time | September 7 at 0200 UTC / 10am China Standard Time. You can find dial-in information and further details here: https://wiki.openstack.org/wiki/Starlingx/Meetings#7pm_Pacific_on_Every_First_Wednesday_of_the_Month-_Technical_Steering_Committee_.26_Community_Call Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation From aqan_bj at sina.com Thu Sep 7 03:26:46 2023 From: aqan_bj at sina.com (aqan_bj at sina.com) Date: Thu, 07 Sep 2023 11:26:46 +0800 Subject: [Starlingx-discuss] If starlingx 8.0 support Nvidia gpu-operator Message-ID: <64f942f66b7275.63509149.17e2b495@m0.mail.sina.com.cn> ?Hi Stalingx Community, ? I'm using the starlingx 8.0. I tried to install gpu-operator v22.9.1 version helm chart but failed with the fllowing error message: ``` ========== NVIDIA Software Installer ========== Starting installation of NVIDIA driver version 525.60.13 for Linux kernel version 5.10.0-6-amd64 Stopping NVIDIA persistence daemon... Unloading NVIDIA driver kernel modules... Unmounting NVIDIA driver rootfs... Checking NVIDIA driver packages... Updating the package cache... Resolving Linux kernel version... Stopping NVIDIA persistence daemon... Unloading NVIDIA driver kernel modules... Unmounting NVIDIA driver rootfs... Could not resolve Linux kernel version ``` and I also tried to install the nvidia dirver manually with the 'sudo ./NVIDIA-Linux-x86_64-525.60.13.run'? but it let me to install gcc. when I tried to install the gcc pacage, i got the error "dpkg: error: unable to access the dpkg database directory /var/lib/dpkg: Read-only file system". So I want to know if stx8.0 support gpu-operator? and how I can install it sucessfully? Thank you for your help in advance. Best regards,Aqan -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Thu Sep 7 11:49:26 2023 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 7 Sep 2023 11:49:26 +0000 Subject: [Starlingx-discuss] StarlingX App Deployment and Demo In-Reply-To: References: Message-ID: Hey Bruno, Thanks for putting this together. Just some initial high-level comments: * your high-level objective appears to be more about end user?s wanting to run and manage their applications on StarlingX * ( i.e. not about a StarlingX Community member wanting to contribute the integration of a containerized application into the StarlingX solution ) * * For end-users wanting to run and manage their applications on StarlingX * I think it is very important to stress that you can package, run and manage your application on StarlingX with either * Helm * FluxCD * StarlingX Application * we do NOT want a StarlingX end user to think that they ?HAVE? to re-package their application in the StarlingX Application Packaging and manage their application with StarlingX APIs, in order to run their application on StarlingX * we want to make sure that a StarlingX end user who has a HELM packaging of their application that they have developed on vanilla K8S, knows that he can simply run it and manage it (UNMODIFIED) on StarlingX. * HELM is the ?standard? application package manage for K8S ? so need to make sure users know they can package, run and manage their applications on StarlingX with HELM * FluxCD provides additional application packaging/management capabilities over and above HELM ? that again is standard/open * would be good to highlight what are these additional capabilities, and * are they all supported on StarlingX?s deployment of FluxCD. * StarlingX Application provides additional application packaging/management capabilities over and above FluxCD ? mostly around custom integration with StarlingX infrastructure management itself. * would be good to highlight/describe these additional capabilities / additional integration points * i.e. if I was a user that already had a HELM or FluxCD packaging of my application, why would I want to consider re-packaging it as a StarlingX Application ? Greg. From: Bruno Drugowick Muniz Sent: Wednesday, September 6, 2023 9:55 AM To: starlingx-discuss at lists.starlingx.io Cc: Daniel Marques Caires ; Douglas Lopes Pereira ; Tom?s Nascimento Pimentel Barros Subject: [Starlingx-discuss] StarlingX App Deployment and Demo CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hello, StarlingX Community. We want to share a work we've been doing in the past few weeks which now needs feedback from the Community. Scenario: package a user application/workload that's not part of the StarlingX ecosystem to run on StarlingX. Main objectives: - make it easier for newcomers to evaluate StarlingX with their workloads; - show some of the platform's capabilities. Our idea is to center all this around a quick and easy-to-consume Demo page, with some text and small video demonstrations for each important step. The main doc is complemented by (all still in progress): - a more detailed application Build Guide; - a single video with everything put together (might need captions to actually be helpful by itself): https://www.youtube.com/watch?v=IvBomQANXlo. It's important to understand that all the info that you'll find in the links above exists somehow either in https://docs.starlingx.io, https://wiki.openstack.org/wiki/StarlingX, or in the intangible place that I'll call "knowledge of the folks around the community" ?. It's not our intention to create yet another place to duplicate information, thus the repository linked above will be deleted at some point, but we needed a temporary place to organize all the info we gathered scattered around together with our own empiric tests. Feel free to use the GitHub Issues, reply to this message, or reach out to me on Matrix to give your feedback. Everything is valid for us to better understand the needs of the community, from small enhancements/fixes to opinions on the format of the presentation or technical aspects of what is being done in this demo regarding the StarlingX platform itself. This won't make us sad or anything: the journey to get all this info together brought us a lot of knowledge about the platform, which is something we are already applying on our next endeavor with StarlingX. Regards, Bruno. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Sep 7 21:24:13 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 7 Sep 2023 21:24:13 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Sep 6, 2023) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call Sept 6, 2023 Standing topics - Build - Main Branch Debian Builds - Hitting some intermittent failures that are affecting various builds; especially container builds - Some have been addressed, but two issues are still outstanding: - One issue with connectivity between the build server and the mirror - The second issue is a deficiency with the git repo - Build Output: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/ - Antelope Feature Branch Debian Builds - Some build failures due to above issues - 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 - Green - 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 Sept 6: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-September/014493.html - Status: Green for SX and Yellow for DX - One LP opened: https://bugs.launchpad.net/starlingx/+bug/2034610 - WIP review posted - Debian Main Branch stx-openstack Sanity (Ussuri) - No sanity this week due to scheduling/lab issues: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-September/014487.html - 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 - Review is active. Got +1 from Scott (build team). Still waiting for input from Greg and MarkA/Yue Tao - Memory Utilization Documentation - https://review.opendev.org/c/starlingx/docs/+/890816 - Bruno requested this review to be abandoned. Consider closed. - 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 - (Ildiko) FYI. Mailing list will be upgraing to mailman3. This should have no user impact. 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 - 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: Closed - Ildiko got StarlingX reinstated as an OSS Program-supported project - pending some documentation. - Team to monitor rate-limiting issues and bring this up again if there are still issues. - 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 - User Questions - sent by Ildiko - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-August/014391.html - Several responses on the mailing list. It looks like this thread has been closed off. - Status: Closed - Not able to use NVIDIA drivers with StarlingX vbox installation - raised in the Aug9 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 - No updates for the last 3 meetings - 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: Closed - Believe that Bruno already answered the outstanding questions. From Chris.Wang at arm.com Fri Sep 8 02:06:52 2023 From: Chris.Wang at arm.com (Chris Wang) Date: Fri, 8 Sep 2023 02:06:52 +0000 Subject: [Starlingx-discuss] StarlingX CI/CD setup on Arm platform In-Reply-To: References: <0d974610-db91-4729-9083-240478b3e03c@windriver.com> Message-ID: + Steve in the loop. Hi Steve, As you mentioned that Davlet or Scott may be on vacation, would you please help to see who could answer Tianyu?s question regarding the test cases? Thanks Chris From: Tianyu Li Sent: Wednesday, August 30, 2023 3:32 PM To: Huang, Jie (Jackie) ; Little, Scott ; Panech, Davlet Cc: starlingx-discuss at lists.starlingx.io; Scott Kamp ; Chris Wang ; Lijian Zhang ; Geary, Stephen (Steve) ; Wang, Linda ; nd Subject: Re: StarlingX CI/CD setup on Arm platform Thanks Davlet and Scott for information, I tried to setup the Jenkins pipeline jobs on local Arm server, after applied Jackie's Arm porting patches[0] with environment variable PATCH_LIST, the build job passed some stage and failed at 'download-prerequisites' with following log[1], looks like the downloader still trying to download some x86 packages. Any idea what could cause this? I have another general question regarding testing stage in CI/CD process, What is the minimum automation test case should be done after image is done? If Davlet and Scott are not familiar with this area, who can help on this? FYI, this is our plan to support StartingX CI/CD on Arm. 1. Reproduce the build CI/CD on arm in our internal lab 2. Verify procedure to trigger test cases for CI/CD on arm machine (internal lab) with few selected cases 3. Discuss with community to merge code changes to enable CI/CD on arm in community lab once arm servers are in place. 4. Fix build and ?minimal test set? errors by all maintainers of community 5. Enable voting right by community per necessary [0] https://review.opendev.org/q/topic:arm64/20230725-stx-master-native [1] downloaderERROR "The cache has no package named 'gcc-alpha-linux-gnu'" Thanks, Tianyu ________________________________ From: Huang, Jie (Jackie) > Sent: Thursday, August 24, 2023 8:57 PM To: Huang, Jie (Jackie) >; Little, Scott >; Panech, Davlet >; Tianyu Li > Cc: starlingx-discuss at lists.starlingx.io >; Scott Kamp >; Trevor Tao >; Geary, Stephen (Steve) >; Wang, Linda > Subject: RE: StarlingX CI/CD setup on Arm platform Hi Scott / Davlet, As we discussed on the OS Distro call, a local CENGEN like server is needed for the local CI/CD setup, Could you please share the info of how to setup a CENGEN like server, specifically how to prepare the package mirror, we need to get it setup and prepare the mirror for ARM deb packages, and for the LAT-SDK for ARM as well. Thanks! Thanks, Jackie From: Huang, Jie (Jackie) > Sent: Friday, August 18, 2023 1:33 PM To: Little, Scott >; Panech, Davlet >; Tianyu Li > Cc: starlingx-discuss at lists.starlingx.io; Scott Kamp >; Trevor Tao >; Geary, Stephen (Steve) >; Wang, Linda > Subject: Re: [Starlingx-discuss] StarlingX CI/CD setup on Arm platform Hi Scott, Thanks for sharing, it?s very helpful. Thanks, Jackie From: Little, Scott > Sent: Thursday, August 17, 2023 11:48 PM To: Huang, Jie (Jackie) >; Panech, Davlet >; Tianyu Li > Cc: starlingx-discuss at lists.starlingx.io; Scott Kamp >; Trevor Tao >; Geary, Stephen (Steve) >; Wang, Linda > Subject: Re: StarlingX CI/CD setup on Arm platform There is also ... https://github.com/starlingx-staging/jenkins Which contains the current state of the StarlingX jenkins setup, less a few credentials. It includes 'Debian_build_server.txt' with crude documentation of how the server was setup. Scott On 2023-08-16 21:04, Huang, Jie (Jackie) wrote: Hi Davlet, Thanks for the detailed answers, which are very helpful, Tianyu and I will start by familiarizing ourselves and check if there are any more questions. Thanks, Jackie From: Panech, Davlet Sent: Wednesday, August 16, 2023 11:30 PM To: Huang, Jie (Jackie) ; Little, Scott ; Tianyu Li ; Wang, Linda Cc: starlingx-discuss at lists.starlingx.io; Scott Kamp ; Trevor Tao ; Geary, Stephen (Steve) Subject: Re: StarlingX CI/CD setup on Arm platform Hi Jackie, CI/CD can be thought of as 2 somewhat disconnected parts - build & automated testing. I know little about test automation, the current build set up is outlined below. You would need a dedicated server: 1. Linux : we currently use Debian 11, but it shouldn't matter since most build steps run in docker containers 2. Docker 3. Kubernetes 4. Jenkins: integrated with k8s and able to run k8s pipelines 5. git 6. git-repo https://gerrit.googlesource.com/git-repo Other prerequisites: 1. You would need some DockerHub account to avoid DockerHub's rate limits when pulling images 2. Once your ARM set up is ready we can replace that with a controlled account that we manage in order to push the images to Docker Hub. Jenkins job definitions (Jenkinsfiles) are source-controlled here: https://opendev.org/starlingx/jenkins-pipelines . You would need to define Jenkins jobs manually in the GUI, and point them to the corresponding Jenkinsfiles in this git repo. 1. The repo itself acts as a pipeline library in Jenkins with shared functions under vars/ . The library must be defined at Jenkins' folder level. 2. pipelines/monolithic.Jenkinsfile : top-level job that calls other jobs under parts/ 3. pipelines/parts/ : directory containing sub-job Jenkinsfiles. You would create a Jenkins folder in the GUI called "parts" and define individual jobs pointing to individual Jenkinsfiles from this subdirectory in git repo 4. scripts/ : shell scripts that implement individual build steps (called by Jenkinsfiles) Required directories on the server, owned by jenkins user: 1. /localdisk/designer/jenkins/ root for per-project build areas 2. /localdisk/loadbuild/jenkins/ root for per-project build archives At first execution the monolithic job will fail, but create an example configuration file in the project build area that you are expected to copy & edit: 1. /localdisk/designer/jenkins/$PROJECT/build.cond.example There are many options with comments in it; the example file is also source controlled under scripts/templates/build.conf.example.in Builds are slow and would greatly benefit from fast storage (SSDs etc). Please start by familiarizing yourself with this repository and ping me if you have any more questions. Hope this helps, D. ________________________________ From: Huang, Jie (Jackie) > Sent: August 9, 2023 10:28 AM To: Little, Scott >; Panech, Davlet >; Tianyu Li >; Wang, Linda > Cc: starlingx-discuss at lists.starlingx.io >; Scott Kamp >; Trevor Tao >; Geary, Stephen (Steve) > Subject: RE: StarlingX CI/CD setup on Arm platform Hi Scott and Davlet, As mentioned in the Multi-OS call, I?m re-sending this with all the questions about StarlingX CI/CD, please help answer as many as you can, thanks! There would be 6 Arm servers contributed to our community for CI/CD (2 for build, 4 for testing of different deployment configs), what we want to know is: 1. What?s the current status of StarlingX CICD for x86-64? 2. What needs to be done for the CICD workflow setup and how after the 6 ARM servers are ready and hosted in the lab? a. E.g. how to setup build servers and testing env? b. What CICD tools need to be setup? Zuul/Jenkins/etc. c. Are there any docs or info of the steps for these setups? 3. How many efforts and how long will it take? 4. Can this only be done by specific person? Or anyone have permission to access to the servers? If the later, I think Tianyu from Arm team and I can also help on that if we got enough information. Tianyu, please add if you have any other questions. Thanks, Jackie From: Huang, Jie (Jackie) Sent: Monday, July 31, 2023 12:57 PM To: Trevor Tao >; Geary, Stephen (Steve) >; Little, Scott >; Scott Kamp > Cc: starlingx-discuss at lists.starlingx.io Subject: RE: StarlingX CI/CD setup on Arm platform Hi, Scott Kamp and Scott Little, I found the following actions in the meeting minutes in stx-status | OpenDev Etherpad: o ARM Support ? Action: Scott Kamp to respond to Jackie/the mailing list to provide assistance/access to some arm machines ? Action: Scott Little to respond regarding build questions ? Cannot mirror more files on CENGN; will need to wait until we transition away from CENGN ? Action: Scott Kamp to explore providing a hosting env temporarily So I think you might be able to help on Trevor?s and my questions: There would be 6 Arm servers contributed to our community for CI/CD (2 for build, 4 for testing of different deployment configs), what we want to know is: 1. What needs to be done for the CICD workflow setup and how? a. E.g. how to setup build servers and testing env? b. What CICD tools need to be setup? Zuul/Jenkins/etc. c. Are there any docs for these setups? 2. How many efforts and how long will it take? 3. Is there a CICD team or someone that can help on the setup or just providing useful information? Thanks, Jackie From: Trevor Tao > Sent: Thursday, July 27, 2023 5:06 PM To: Geary, Stephen (Steve) >; starlingx-discuss at lists.starlingx.io Cc: Huang, Jie (Jackie) > Subject: StarlingX CI/CD setup on Arm platform Hi Steve, StarlingX: From the OS distro meeting yesterday, we knew that there would be 6 Arm servers contributed to our community to do the CI/CD related work. So we would like to ask who can help on the setup of CI/CD environment on the arm platform, and any other useful information/details for the CI/CD issue here. Thanks, Best Regards, Zijin Tao(Trevor Tao, ???) ARM Electronic Technology (Shanghai) Co., Ltd ?????????????? Building 11, Shanghai Busininess Park? , No.1016 Tianlin Rd, Minhang District, Shanghai, 200233 China ?????????1016???????2??10??200233 Cell: +86-153 7109 6192 IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ronald.Stone at windriver.com Fri Sep 8 15:12:16 2023 From: Ronald.Stone at windriver.com (Stone, Ronald) Date: Fri, 8 Sep 2023 15:12:16 +0000 Subject: [Starlingx-discuss] Virtual Install guide updates Message-ID: We've discussed two approaches to updating the StarlingX virtual install documentation on the weekly stx-docs calls. Options are: * Include chunks of content from the bare-metal docs in the existing virtual docs, maintaining only one copy in the source. * Remove the Virtual guide and include that content in tabs in the existing base metal guide where they differ from bare metal: [Virtual tab | Bare metal tab] These tabs will need to be conditionalized, testing indicates this will work. Soliciting opinions here on which approach to take. The tabbed approach will involve adding a new plugin. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Fri Sep 8 15:54:05 2023 From: Greg.Waines at windriver.com (Waines, Greg) Date: Fri, 8 Sep 2023 15:54:05 +0000 Subject: [Starlingx-discuss] Virtual Install guide updates In-Reply-To: References: Message-ID: ... just my thoughts. I'd like to try the option with tabs ... to see how this looks and works for the guides. Greg. p.s. how would prints of web pages work with tabs, print only the current tab selection ? From: Stone, Ronald Sent: Friday, September 8, 2023 11:12 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Virtual Install guide updates We've discussed two approaches to updating the StarlingX virtual install documentation on the weekly stx-docs calls. Options are: * Include chunks of content from the bare-metal docs in the existing virtual docs, maintaining only one copy in the source. * Remove the Virtual guide and include that content in tabs in the existing base metal guide where they differ from bare metal: [Virtual tab | Bare metal tab] These tabs will need to be conditionalized, testing indicates this will work. Soliciting opinions here on which approach to take. The tabbed approach will involve adding a new plugin. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Juanita.Balaraj at windriver.com Mon Sep 11 02:14:59 2023 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Mon, 11 Sep 2023 02:14:59 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 08-09-2023 In-Reply-To: References: Message-ID: Hello All, Here are this week's doc team meeting minutes. Details in [2]. Join us if you have interest in StarlingX docs! We meet on Fridays 6:00 a.m. PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Thanks, Juanita Balaraj ============ 08- September-23 Action Items / Status: - Stx 9.0 Release Tracking Spreadsheet: Doc Stories are tracked in https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing. - To add stories that are planned for Stx 9.0 - AR Juanita - WIP (add / replan as required). Features have been removed from Stx 9.0. See https://etherpad.opendev.org/p/stx-cores for more details. - Discussion about Merging the Installation Guides ; Virtual env with the Bare metal docs. https://review.opendev.org/c/starlingx/docs/+/876107 - 3 options: AR Ron to reach out to Bruno- StarlingX discuss group - Split the docs and retain them as separate guides at a high level. Resue content from Bare Metal in the Virtual env docs. - Get rid of the Virtual Guide and use tabs in the Baremetal guide with Virtual env updates - Maintain the virtual guide and pull the shared content in from Baremetal - Bruno / Ron - - Ron to update the Troubleshooting information in the Sphinx Contributor Guide - AR Ron - Discussion about upgrading to the latest Sphinx / tox version; https://pypi.org/project/tox/: https://review.opendev.org/c/starlingx/docs/+/890833 - AR Ron - Documentation Contributor Guide - StarlingX documentation - https://docs.starlingx.io/contributor/doc_contribute_guide.html - All to update the Contributor guide on an ongoing basis for new Styles / Standards implemented - The team to familiarize themselves with the Styles and Standards Guide. Contributor Guide - AR StarlingX Doc team Gerrit reviews: - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - Merged 2 Reviews. To get closure of the open reviews at the earliest. - Check with Greg and if the Installation doc updates are required on Stx 8.0 https://review.opendev.org/c/starlingx/docs/+/876107 - AR Ron / Juanita - https://review.opendev.org/c/starlingx/docs/+/890960 - AR Ron to check with Scott about the Antelope repositories Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 10 outstanding bugs. Miscellaneous Updates: - Stx. Virtual PTG Meeting: https://openinfra.dev/ptg/ - Stx Doc team is encouraged to participate in sessions as required. - Update the Verified H/W page with the automated script updates https://www.windriver.com/studio/operator/self-validated-and-certified-hosts# - Currently Commented out - Script needs to be updated- Waiting for updates to the script -AR Ron - WIP - Bruno Muniz showed interest in creating DOC Videos supporting the StarlingX Installation Process. To check with Ildiko / Greg whether this is ok. These Videos can be hosted in a location in StarlingX. The Installation Docs can point to these videos - AR Bruno to get approvals from Ildiko / Greg for a future Update - Operations Guide Archive - On Hold until further clarifications are discussed with Greg (https://review.opendev.org/c/starlingx/docs/+/822030) Engineering Status: StarlingX Eng Stx Status: https://etherpad.opendev.org/p/stx-status StarlingX Eng Status 2023 https://etherpad.opendev.org/p/stx-cores StarlingX OS Status: https://etherpad.opendev.org/p/stx-distro-other ____________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From amy at demarco.com Mon Sep 11 20:16:02 2023 From: amy at demarco.com (Amy Marrich) Date: Mon, 11 Sep 2023 15:16:02 -0500 Subject: [Starlingx-discuss] [Diversity] Diversity and Inclusion WG Meeting reminder Message-ID: This is a reminder that the Diversity and Inclusion WG will be meeting tomorrow at 14:00 UTC in the #openinfra-diversity channel on OFTC. We hope members of all OpenInfra projects join us as we look at the progress on responses to the Foundation-wide diversity survey. Thanks, Amy (spotz) 0 - https://etherpad.opendev.org/p/diversity-wg-agenda From Bruce.Jones at windriver.com Mon Sep 11 23:48:46 2023 From: Bruce.Jones at windriver.com (Jones, Bruce) Date: Mon, 11 Sep 2023 23:48:46 +0000 Subject: [Starlingx-discuss] Container meeting Tuesday Message-ID: Reminder that the Container team is having their bi-weekly meeting this Tuesday. Here are the details: 6:30am Pacific - StarlingX Infrastructure Containerization sub-project bi-weekly call This is the StarlingX Infrastructure Containerization sub-project team bi-weekly call, the sub-project team members as well as other project participants are welcome to join. Call details * https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 * Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o Passcode: 419405 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes * Project notes are at https://etherpad.openstack.org/p/stx-containerization * Call recordings: https://wiki.openstack.org/wiki/Starlingx/Meeting_Logs#StarlingX_Infrastructure_Containerization_Team_Call brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peng.Peng at windriver.com Tue Sep 12 14:10:57 2023 From: Peng.Peng at windriver.com (Peng, Peng) Date: Tue, 12 Sep 2023 14:10:57 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20230910T060000Z Message-ID: Sanity Test from September 11, 2023 (https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230910T060000Z/outputs/iso/starlingx-intel-x86-64-cd.iso) Status: Yellow SX sanity Passed: 17 (100.0%) Failed: 0 (0.0%) Total Executed: 17 List of Test Cases: ------------------------------------------------------ PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_push_docker_image_to_local_registry_active PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_isolated_2p_2_big_pod_best_effort_HT_AIO PASS test_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS test_sriovdp_netdev_connectivity_ipv4[1-1-calico-ipam] PASS test_sriovdp_mixed_add_vf_interface[1] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] DX sanity lab installation failed. There was one failure found in DX installation, like DX DM config controller-1 failed, INSYNC in false status We will open a Launchpad once the root cause is identified. Regards, PV team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Gabriel.CalixtodePaula at windriver.com Tue Sep 12 14:53:44 2023 From: Gabriel.CalixtodePaula at windriver.com (Calixto de Paula, Gabriel) Date: Tue, 12 Sep 2023 14:53:44 +0000 Subject: [Starlingx-discuss] Sanity and Regression - StarlingX + STX-Openstack MASTER build - Sep -12 NO RESULTS Message-ID: Hi all, We'll be skipping this week's STX-Openstack sanity execution report due to some scheduling issues with our available testing hardware, also we're waiting for a full stable Antelope build for openstack testing, that is still not the case. Thanks STX-Openstack Distro Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peng.Peng at windriver.com Tue Sep 12 18:26:55 2023 From: Peng.Peng at windriver.com (Peng, Peng) Date: Tue, 12 Sep 2023 18:26:55 +0000 Subject: [Starlingx-discuss] FW: Sanity Master Test LAYERED build ISO 20230910T060000Z In-Reply-To: References: Message-ID: After analysis, a new launchpad is opened. https://bugs.launchpad.net/starlingx/+bug/2035277 - DX config controller-1 failed, INSYNC in false status Thanks, Peng From: Peng, Peng Sent: Tuesday, September 12, 2023 10:11 AM To: starlingx-discuss at lists.starlingx.io Subject: Sanity Master Test LAYERED build ISO 20230910T060000Z Sanity Test from September 11, 2023 (https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230910T060000Z/outputs/iso/starlingx-intel-x86-64-cd.iso) Status: Yellow SX sanity Passed: 17 (100.0%) Failed: 0 (0.0%) Total Executed: 17 List of Test Cases: ------------------------------------------------------ PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_push_docker_image_to_local_registry_active PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_isolated_2p_2_big_pod_best_effort_HT_AIO PASS test_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS test_sriovdp_netdev_connectivity_ipv4[1-1-calico-ipam] PASS test_sriovdp_mixed_add_vf_interface[1] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] DX sanity lab installation failed. There was one failure found in DX installation, like DX DM config controller-1 failed, INSYNC in false status We will open a Launchpad once the root cause is identified. Regards, PV team -------------- next part -------------- An HTML attachment was scrubbed... URL: From ThalesElero.Cervi at windriver.com Tue Sep 12 19:42:57 2023 From: ThalesElero.Cervi at windriver.com (Cervi, Thales Elero) Date: Tue, 12 Sep 2023 19:42:57 +0000 Subject: [Starlingx-discuss] Minutes: OpenStack Distro Team Call (Sep 12, 2023) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-distro-openstack-meetings Minutes from the OpenStack Distro team call Sep 12, 2023 Build: - Build Issues: None Installation: - Installation Issues: None Sanity with stx-openstack (main branch): - Last Successful Execution: (OVS) Tue Aug 29 12:39:12 UTC 2023 - Overall status: YELLOW ??????Sanity - Passed: 13 (86.67%) | Failed: 2 (13.33%) ??????Regression - Passed: 9 (75.0%) | Failed: 3 (25.0%) - Master Build (20230829T060000Z) - Last Execution: PENDING - Test hardware is currently unavaiblable for this execution - Team is waiting for a green stx-openstack build from f/antelope branch - Bugs Affecting Weekly Sanity/Regression: - No Reproducible bugs currently open. Only intermittent issues (ussuri application) # LP 2023657: STX-O| config-out-of-date alarm won't disappear on controller-1 after swact and reapplying app # LP 2012389: STX-Openstack: Failed to activate binding for port for live migration # LP 2007303: STX-Openstack: "nova live-migration" fails to live migrate after host is forcefully turned off/on - STX 9.0 Features Status: - Storyboard/Tasks for containerizing OpenStack clients: https://storyboard.openstack.org/#!/story/2010774 - Tests started, no issues found so far - Storyboard/Tasks for OpenStack upversion (Antelope): https://storyboard.openstack.org/#!/story/2010715 - All changes are already merged into f/antelope branch (last merge was Sep 11th) - Waiting for a green stx-openstack build from f/antelope branch - There is still a pending change that only affect the platform ISO - As soon as we are comfortable with both application and platform builds from f/antelope, we should start merging the code back to main branch -- Best Regards, Thales Elero Cervi -------------- next part -------------- An HTML attachment was scrubbed... URL: From Rob.Cooke at windriver.com Tue Sep 12 20:49:27 2023 From: Rob.Cooke at windriver.com (Cooke, Rob) Date: Tue, 12 Sep 2023 20:49:27 +0000 Subject: [Starlingx-discuss] Minutes: Test Status Call - September 12, 2023 Message-ID: Hi everyone, Please find below the minutes from this week's StarlingX Test Status Call: Minutes for 09/12/2023 * Open Topics: ? STX9.0 GA date decision still pending, no resources available to regress STX9.0 * Sanity Status: o Sanity on STX 9.0 - Green for SX. ? Last execution, September 11, 2023 - Results email: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-September/014504.html ? DX experienced installation issues, being investigated, will raise launchpad as appropriate and send details as a follow up to the sanity email * Sanity on STX 9.0 plus Openstack: ? Sanity skipped for week of September 11th. * Hardware unavailable * Also waiting for full stable Antelope build * Details shared via email: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-September/014505.html ? Last Successful Execution: (OVS) Tue Aug 22 12:39:12 UTC 2023 - Overall status: YELLOW * Sanity - Passed: 13 (86.67%) | Failed: 2 (13.33%) * Regression - Passed: 9 (75.0%) | Failed: 3 (25.0%) * Master Build (20230820T060000Z) * Feature Test Status: o Feature testing is tracked in the following google sheet: ? https://docs.google.com/spreadsheets/d/1El3g0ute5K2S5DTR9p_rxa1jQlq8gcUzgMCNCE_sx8g/edit#gid=968103774 ? Some features are in progress, sheet does need updating ACTION: Rob/Nimalini * Regression Testing will be tracked here closer to release end: ? https://docs.google.com/spreadsheets/d/1NjYk9N0whK91nHViB5HFG2C1-XdJ09StVuLMxsz0KAY/edit?pli=1#gid=1717644237 Thanks, Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Wed Sep 13 14:43:30 2023 From: Greg.Waines at windriver.com (Waines, Greg) Date: Wed, 13 Sep 2023 14:43:30 +0000 Subject: [Starlingx-discuss] StarlingX 9 Release will be deferred until Q1/2024 Message-ID: StarlingX Community, We have been discussing the RISKS to the STX 9 Release dates for the last few weeks in our TSC meeting. See https://etherpad.opendev.org/p/stx-cores The critical path item that can NOT meet the STX 9 Release date is the full Release Verification and Regression testing by the STX Test Project Team. We have discussed/explored a number of options * asking whether anyone else in the community can pick up the STX 9 Release Verification and Regression testing effort. o we have had no feedback from the community on this * considering releasing a 'sanity quality' ONLY STX 9 Release o but general consensus in tsc/community meeting was that this would be unwise as users of StarlingX would still expect high quality regardless of the sanity-only indication. * consider deferring the release of STX 9 until Q1 2024 when the STX Test Project Team's resources free up again and have time to do the full Release Verification and Regression testing o we have asked community for impact of not delivering Antelope (STX 9 feature) in October/2023 ? we have had no feedback from the community on this o we have asked community members about impact of deferring the complete STX 9 release to Q1 2024 ? we have had no feedback from the community on this This email is to inform you that last week, the STX TSC voted on proposal to defer the release of STX 9 until Q1/2024 * ALL TSC members voted +1 to defer NEXT STEPS: * "Stake-in-the-Ground" proposal for STX 9 Release date is end-of-March 2024 * ACTION: Release Team (Ghada) to a) forecast updated milestones based on end-of-march release b) get updated view from feature owners on whether they can meet these milestones * ACTION: Test Team (Rob) to confirm, based on updated view of feature content, that test milestones can be met based on end-of-march milestone dates Let us know of any concerns, STX TSC. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tianyu.Li at arm.com Wed Sep 13 07:45:22 2023 From: Tianyu.Li at arm.com (Tianyu Li) Date: Wed, 13 Sep 2023 07:45:22 +0000 Subject: [Starlingx-discuss] StarlingX CI/CD setup on Arm platform In-Reply-To: References: <0d974610-db91-4729-9083-240478b3e03c@windriver.com> Message-ID: Hi, To have a better understanding process of the CI/CD setup on Arm platform, I summarize and come up with the following simple topology diagram. With action items list below. Welcome any comments and suggestions. The proposed topology [cid:5c2ebdb3-30c3-4019-b6b0-62c3feaa1be2] Work steps 1. Reproduce the build CI/CD on arm in our internal lab 2. Verify procedure to trigger test cases for CI/CD on arm machine (internal lab) with few selected cases 3. Discuss with community to merge code changes to enable CI/CD on arm in community lab once arm servers are in place. 4. Fix build and ?minimal test set? errors by all maintainers of community 5. Enable voting right by community per necessary Current status I am trying step 1, build ISO image with Jackie's porting patch series in our internal lab to understand the build process. The previous build packages error is because I missed some patches from Jackie. I still need to figure out an error during generating ISO image with Jackie. The auto test part in step 2 still needs some input. What is test repo used? What is the minimal test set? Any quick get started guide? Thanks, Tianyu ________________________________ From: Chris Wang Sent: Friday, September 8, 2023 10:06 AM To: Tianyu Li ; Huang, Jie (Jackie) ; Little, Scott ; Panech, Davlet ; Geary, Stephen (Steve) Cc: starlingx-discuss at lists.starlingx.io ; Scott Kamp ; Lijian Zhang ; Geary, Stephen (Steve) ; Wang, Linda ; nd Subject: RE: StarlingX CI/CD setup on Arm platform + Steve in the loop. Hi Steve, As you mentioned that Davlet or Scott may be on vacation, would you please help to see who could answer Tianyu?s question regarding the test cases? Thanks Chris From: Tianyu Li Sent: Wednesday, August 30, 2023 3:32 PM To: Huang, Jie (Jackie) ; Little, Scott ; Panech, Davlet Cc: starlingx-discuss at lists.starlingx.io; Scott Kamp ; Chris Wang ; Lijian Zhang ; Geary, Stephen (Steve) ; Wang, Linda ; nd Subject: Re: StarlingX CI/CD setup on Arm platform Thanks Davlet and Scott for information, I tried to setup the Jenkins pipeline jobs on local Arm server, after applied Jackie's Arm porting patches[0] with environment variable PATCH_LIST, the build job passed some stage and failed at 'download-prerequisites' with following log[1], looks like the downloader still trying to download some x86 packages. Any idea what could cause this? I have another general question regarding testing stage in CI/CD process, What is the minimum automation test case should be done after image is done? If Davlet and Scott are not familiar with this area, who can help on this? FYI, this is our plan to support StartingX CI/CD on Arm. 1. Reproduce the build CI/CD on arm in our internal lab 2. Verify procedure to trigger test cases for CI/CD on arm machine (internal lab) with few selected cases 3. Discuss with community to merge code changes to enable CI/CD on arm in community lab once arm servers are in place. 4. Fix build and ?minimal test set? errors by all maintainers of community 5. Enable voting right by community per necessary [0] https://review.opendev.org/q/topic:arm64/20230725-stx-master-native [1] downloaderERROR "The cache has no package named 'gcc-alpha-linux-gnu'" Thanks, Tianyu ________________________________ From: Huang, Jie (Jackie) > Sent: Thursday, August 24, 2023 8:57 PM To: Huang, Jie (Jackie) >; Little, Scott >; Panech, Davlet >; Tianyu Li > Cc: starlingx-discuss at lists.starlingx.io >; Scott Kamp >; Trevor Tao >; Geary, Stephen (Steve) >; Wang, Linda > Subject: RE: StarlingX CI/CD setup on Arm platform Hi Scott / Davlet, As we discussed on the OS Distro call, a local CENGEN like server is needed for the local CI/CD setup, Could you please share the info of how to setup a CENGEN like server, specifically how to prepare the package mirror, we need to get it setup and prepare the mirror for ARM deb packages, and for the LAT-SDK for ARM as well. Thanks! Thanks, Jackie From: Huang, Jie (Jackie) > Sent: Friday, August 18, 2023 1:33 PM To: Little, Scott >; Panech, Davlet >; Tianyu Li > Cc: starlingx-discuss at lists.starlingx.io; Scott Kamp >; Trevor Tao >; Geary, Stephen (Steve) >; Wang, Linda > Subject: Re: [Starlingx-discuss] StarlingX CI/CD setup on Arm platform Hi Scott, Thanks for sharing, it?s very helpful. Thanks, Jackie From: Little, Scott > Sent: Thursday, August 17, 2023 11:48 PM To: Huang, Jie (Jackie) >; Panech, Davlet >; Tianyu Li > Cc: starlingx-discuss at lists.starlingx.io; Scott Kamp >; Trevor Tao >; Geary, Stephen (Steve) >; Wang, Linda > Subject: Re: StarlingX CI/CD setup on Arm platform There is also ... https://github.com/starlingx-staging/jenkins Which contains the current state of the StarlingX jenkins setup, less a few credentials. It includes 'Debian_build_server.txt' with crude documentation of how the server was setup. Scott On 2023-08-16 21:04, Huang, Jie (Jackie) wrote: Hi Davlet, Thanks for the detailed answers, which are very helpful, Tianyu and I will start by familiarizing ourselves and check if there are any more questions. Thanks, Jackie From: Panech, Davlet Sent: Wednesday, August 16, 2023 11:30 PM To: Huang, Jie (Jackie) ; Little, Scott ; Tianyu Li ; Wang, Linda Cc: starlingx-discuss at lists.starlingx.io; Scott Kamp ; Trevor Tao ; Geary, Stephen (Steve) Subject: Re: StarlingX CI/CD setup on Arm platform Hi Jackie, CI/CD can be thought of as 2 somewhat disconnected parts - build & automated testing. I know little about test automation, the current build set up is outlined below. You would need a dedicated server: 1. Linux : we currently use Debian 11, but it shouldn't matter since most build steps run in docker containers 2. Docker 3. Kubernetes 4. Jenkins: integrated with k8s and able to run k8s pipelines 5. git 6. git-repo https://gerrit.googlesource.com/git-repo Other prerequisites: 1. You would need some DockerHub account to avoid DockerHub's rate limits when pulling images 2. Once your ARM set up is ready we can replace that with a controlled account that we manage in order to push the images to Docker Hub. Jenkins job definitions (Jenkinsfiles) are source-controlled here: https://opendev.org/starlingx/jenkins-pipelines . You would need to define Jenkins jobs manually in the GUI, and point them to the corresponding Jenkinsfiles in this git repo. 1. The repo itself acts as a pipeline library in Jenkins with shared functions under vars/ . The library must be defined at Jenkins' folder level. 2. pipelines/monolithic.Jenkinsfile : top-level job that calls other jobs under parts/ 3. pipelines/parts/ : directory containing sub-job Jenkinsfiles. You would create a Jenkins folder in the GUI called "parts" and define individual jobs pointing to individual Jenkinsfiles from this subdirectory in git repo 4. scripts/ : shell scripts that implement individual build steps (called by Jenkinsfiles) Required directories on the server, owned by jenkins user: 1. /localdisk/designer/jenkins/ root for per-project build areas 2. /localdisk/loadbuild/jenkins/ root for per-project build archives At first execution the monolithic job will fail, but create an example configuration file in the project build area that you are expected to copy & edit: 1. /localdisk/designer/jenkins/$PROJECT/build.cond.example There are many options with comments in it; the example file is also source controlled under scripts/templates/build.conf.example.in Builds are slow and would greatly benefit from fast storage (SSDs etc). Please start by familiarizing yourself with this repository and ping me if you have any more questions. Hope this helps, D. ________________________________ From: Huang, Jie (Jackie) > Sent: August 9, 2023 10:28 AM To: Little, Scott >; Panech, Davlet >; Tianyu Li >; Wang, Linda > Cc: starlingx-discuss at lists.starlingx.io >; Scott Kamp >; Trevor Tao >; Geary, Stephen (Steve) > Subject: RE: StarlingX CI/CD setup on Arm platform Hi Scott and Davlet, As mentioned in the Multi-OS call, I?m re-sending this with all the questions about StarlingX CI/CD, please help answer as many as you can, thanks! There would be 6 Arm servers contributed to our community for CI/CD (2 for build, 4 for testing of different deployment configs), what we want to know is: 1. What?s the current status of StarlingX CICD for x86-64? 2. What needs to be done for the CICD workflow setup and how after the 6 ARM servers are ready and hosted in the lab? a. E.g. how to setup build servers and testing env? b. What CICD tools need to be setup? Zuul/Jenkins/etc. c. Are there any docs or info of the steps for these setups? 3. How many efforts and how long will it take? 4. Can this only be done by specific person? Or anyone have permission to access to the servers? If the later, I think Tianyu from Arm team and I can also help on that if we got enough information. Tianyu, please add if you have any other questions. Thanks, Jackie From: Huang, Jie (Jackie) Sent: Monday, July 31, 2023 12:57 PM To: Trevor Tao >; Geary, Stephen (Steve) >; Little, Scott >; Scott Kamp > Cc: starlingx-discuss at lists.starlingx.io Subject: RE: StarlingX CI/CD setup on Arm platform Hi, Scott Kamp and Scott Little, I found the following actions in the meeting minutes in stx-status | OpenDev Etherpad: o ARM Support * Action: Scott Kamp to respond to Jackie/the mailing list to provide assistance/access to some arm machines * Action: Scott Little to respond regarding build questions * Cannot mirror more files on CENGN; will need to wait until we transition away from CENGN * Action: Scott Kamp to explore providing a hosting env temporarily So I think you might be able to help on Trevor?s and my questions: There would be 6 Arm servers contributed to our community for CI/CD (2 for build, 4 for testing of different deployment configs), what we want to know is: 1. What needs to be done for the CICD workflow setup and how? a. E.g. how to setup build servers and testing env? b. What CICD tools need to be setup? Zuul/Jenkins/etc. c. Are there any docs for these setups? 2. How many efforts and how long will it take? 3. Is there a CICD team or someone that can help on the setup or just providing useful information? Thanks, Jackie From: Trevor Tao > Sent: Thursday, July 27, 2023 5:06 PM To: Geary, Stephen (Steve) >; starlingx-discuss at lists.starlingx.io Cc: Huang, Jie (Jackie) > Subject: StarlingX CI/CD setup on Arm platform Hi Steve, StarlingX: From the OS distro meeting yesterday, we knew that there would be 6 Arm servers contributed to our community to do the CI/CD related work. So we would like to ask who can help on the setup of CI/CD environment on the arm platform, and any other useful information/details for the CI/CD issue here. Thanks, Best Regards, Zijin Tao(Trevor Tao, ???) ARM Electronic Technology (Shanghai) Co., Ltd ?????????????? Building 11, Shanghai Busininess Park? , No.1016 Tianlin Rd, Minhang District, Shanghai, 200233 China ?????????1016???????2??10??200233 Cell: +86-153 7109 6192 IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 27523 bytes Desc: image.png URL: From Ghada.Khalil at windriver.com Thu Sep 14 02:23:42 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 14 Sep 2023 02:23:42 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Sep 13/2023 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Sep 13 2023 stx.9.0 - Release/Feature Planning: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing - stx.9.0 Release Decision - The TSC voted to defer the release to Q1 2024 - The test team will not have bandwidth for testing until Q1 - The current target date is no later than end of March 2024 - Need to re-forecast the release milestones accordingly - Action: Feature primes to re-evaluate the feature dates that were previously considered out of the release Blogs - No updates - FEC Device Configurability (fec-operator Integration) for ACC100 & N3000 - Prime: Balendu (Mouli) Burla - Forecast: May 1 >> May 19 >> Aug 15 >> needs update - Status: Confirmed / Not posted - PTP O-RAN Compliant API Notification - Prime: Ghada Khalil - Forecast: Jun 30 >> Oct 15 - Status: Confirmed / Not posted From Ghada.Khalil at windriver.com Thu Sep 14 02:29:28 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 14 Sep 2023 02:29:28 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Sep 13, 2023) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call Sept 13, 2023 Standing topics - Build - Main Branch Debian Builds - Update on build issues from last week: - One issue with connectivity between the build server and the mirror >> Resolved - The second issue is a deficiency with the git repo >> Still open - Also hit other issues related to container builds which were resolved. - Current build status is unknown. Cannot check the status as the build server is offline due to a power outage at WR Ottawa - Build Output: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/ - Antelope Feature Branch Debian Builds - Unknown - server down due to power outage - Two previous build issues were addressed; waiting for a rebuild to confirm - bug/2035346: stx-horizion image build failed - bug/2035347: stx-ceph-manager image build failed - stx.6.0 Weekly RC Builds - Unknown - server down due to power outage - 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 - Unknown - server down due to power outage - 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 - Unknown - server down due to power outage - 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 Sept 12: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-September/014506.html - Status: Green for SX and Red for DX - New LP opened: https://bugs.launchpad.net/starlingx/+bug/2035277 - Issue related to "kubeadm join". Investigating in progress by the container team, but hampered by power outage at WR Ottawa - Suspect a recent code change from Sept 8: https://review.opendev.org/c/starlingx/stx-puppet/+/893091 - Debian Main Branch stx-openstack Sanity (Ussuri) - No sanity this week also due to scheduling/lab issues: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-September/014505.html - 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 - No progress since Sept 6. - Last update: Got +1 from Scott (build team). Still waiting for input from Greg and MarkA/Yue Tao - 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 - None 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: Remove. Will be tracked in the TSC - 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 - No updates since Aug 31. Open Requests for Help - NVIDIA gpu-operator Support in stx.8.0 - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-September/014495.html - Status: Open - No response on the mailing list as of Sept 13. - Not able to use NVIDIA drivers with StarlingX vbox installation - raised in the Aug9 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 - No updates for the last 4 meetings From scott.little at eng.windriver.com Thu Sep 14 13:32:12 2023 From: scott.little at eng.windriver.com (Scott.Little) Date: Thu, 14 Sep 2023 09:32:12 -0400 Subject: [Starlingx-discuss] [Build] StarlingX build server down. Message-ID: The official StarlingX builds has been temporarily disabled due to the failure of a networking component. We hope to have it resolved soon. The mirror https://mirror.starlingx.windriver.com/mirror/ remains available, but no new builds will be published until the networking issue is resolved. Scott From fungi at yuggoth.org Thu Sep 14 17:34:56 2023 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 14 Sep 2023 17:34:56 +0000 Subject: [Starlingx-discuss] Mailman v3 migration for StarlingX mailing lists 2023-09-21 Message-ID: <20230914173456.cuy4sbxazujgcdwi@yuggoth.org> On Thursday, September 21 at 15:30 UTC, the OpenDev Collaboratory systems administrators will be migrating the lists.starlingx.io mailing list site from the aging Mailman 2.1.29 server to a newer Mailman 3.3.8 deployment. This maintenance window is expected to last no more than one hour. The key takeaways are as follows: * There will be a brief outage for the site while DNS is updated and configuration, subscriber lists and message archives are imported, but incoming messages should correctly queue at the sender's end and arrive at the conclusion of our work * Because this is on a new server, there are new IP addresses from which list mail will be originating: 162.209.78.70 and 2001:4800:7813:516:be76:4eff:fe04:5423 * Moderation queues will not be copied to the new server, so moderators are encouraged to process any held messages prior to the migration time in order to avoid losing them * Anyone wishing to adjust their list subscriptions, or handle moderation or list configuration after the migration, needs to use the Sign Up button on the Web page to create a new account; it will be linked to your imported roles as soon as you confirm by following a URL from an E-mail message the server sends you, and is global for all sites on the server so you only need to do this once * The software providing Web front-ends for list management and archive browsing is entirely new in Mailman v3 and therefore has a much different appearance, though we've added appropriate redirects and frozen copies of old archives in order to accommodate existing hyperlinks If you have any questions or concerns, feel free to follow up on the service-discuss mailing list or find us in the #opendev channel on the OFTC IRC network. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From Scott.Little at windriver.com Fri Sep 15 02:44:41 2023 From: Scott.Little at windriver.com (Little, Scott) Date: Fri, 15 Sep 2023 02:44:41 +0000 Subject: [Starlingx-discuss] [Build] StarlingX build server down. In-Reply-To: References: Message-ID: The official StarlingX build server has been restored. I expect to see new builds being published tomorrow morning. Scott ________________________________ From: Scott.Little Sent: September 14, 2023 9:32 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Build] StarlingX build server down. The official StarlingX builds has been temporarily disabled due to the failure of a networking component. We hope to have it resolved soon. The mirror https://mirror.starlingx.windriver.com/mirror/ remains available, but no new builds will be published until the networking issue is resolved. Scott _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From Linda.Wang at windriver.com Fri Sep 15 22:56:39 2023 From: Linda.Wang at windriver.com (Wang, Linda) Date: Fri, 15 Sep 2023 22:56:39 +0000 Subject: [Starlingx-discuss] Bi-Weekly StartlingX OS Distro & Multi-OS Meeting: Aug 23 2023 Message-ID: Hi, Below is the Meeting Minutes from StarlingX OS Distro and Multi-OS meeting. 1. General Topics 1.1 Split package list betweeen repositories (ISO and container images) * Separeation of the list is done per Davlet. * AI: Devlet will check the documentation on package list. * 1.2 Log into the git before download the source. * How to pass the credential through the tooling layer when log into git repo. * workaround: currently use repo sync outside of the containers. * AI: Scott to write up a feature request for the tool - file a request in Story Board. * Created: https://storyboard.openstack.org/#!/story/2010777, (create a jira for it) * 1.3 Pre-patch ISO (Luis Sampaio is back, will ping him to join us next time) 2. ARM Support * a. Equipment * Ampere provided 6 servers * Still waiting on exact location where the servers should be sent from Steve G. of the CTO office * 6 Ampere servers will go to where the CENGN lab is going to be. 2 for build, 4 for testing. * Can the community support the lab? * AI: ARM is still waiting on a location to host these servers. AI: Steve is help looking for a location to host these servers. * AI: who from the community can help setup these servers? and support the CI/CD on ARM platform * Check with Steve Gnery and Warren Bayek * b. CI/CD Setup (Jackie) * Who can help explain the CI/CD method to Jackie, Tiayu. * A lot of left over work with CNGN transition. Got help from Scott/Davlet and Tianyu tried on local server. Failed on downloading packages. * ARM is running native build on servers. May need to change the alternate download of the CI/CD code. * c. Porting still in progreess (Jakie) * rewrote the coding to support build system for both x86 and arm * build system will detect the arch, and if it is arm, it will build arm arch. * Wrote up the SPEC on the implementtaion., and now waiting on SPEC to be review * SPEC review first then will send code for code review. * Some kernel modules don't work * QEMU is not working yet. Waiting on kernel up-rev, then and see if QEMU can be fixed then. * Created 2 wikipages for setting up the build environment for ARM arch: * https://wiki.openstack.org/wiki/StarlingX/StarlingX_Debian_on_ARM_Information_Guide * https://wiki.openstack.org/wiki/StarlingX/DebianArmBuildEnvironment * SPEC file review continoues, Kernel SPEC file needs reviewer. * Need more community reviewers. * d. Packages for x86_64 are in CNGN, need to push ARM packages there. * Set up the own (CNGN like) website, push the packages to the website as part of CI/CD website (/export/mirror) * Secureboot is disabled for now. Will do it in the future. * ELF SDK is used to build image. Need to push the SDK to CNGN, no permission to push to CNGN yet, it is on local disk. * Need to change meta-lat layer for ELF SDK, but want to link the task to different repo, but can't. * meta-lat layer is not in the StarlingX repo, but its in github repo. fork it.. do a pull request to github lab for any changes. * meta-lat used is with the WR's repo, not community one. Will migrate later. * OSTree * removing OSTree from the installer ISO. (not from the StarlingX) * Work in progress, not sure when it will be ready. Possible early next year, StarlingX 9. 3. StartlingX 8.0 * SPEC from Chuck on OSTree generation on the controller, pending review. * Work is being done, but the SPEC will need to be rewritten. Deferred. Next meeting: September 6, 2023 Thanks, Linda -------------- next part -------------- An HTML attachment was scrubbed... URL: From Linda.Wang at windriver.com Fri Sep 15 23:00:48 2023 From: Linda.Wang at windriver.com (Wang, Linda) Date: Fri, 15 Sep 2023 23:00:48 +0000 Subject: [Starlingx-discuss] Bi-Weekly StarlingX OS Distro & Multi-OS meeting Sept 6, 2023 Message-ID: Hi, 1. General Topics 1.1 Split package list betweeen repositories (ISO and container images) * Separeation of the list is done per Davlet. * AI: Devlet will check the documentation on package list. * 1.2 Log into the git before download the source. * How to pass the credential through the tooling layer when log into git repo. * workaround: currently use repo sync outside of the containers. * AI: Scott to write up a feature request for the tool - file a request in Story Board. * Created: https://storyboard.openstack.org/#!/story/2010777, (create a jira for it) * 1.3 Pre-patch ISO (Luis Sampaio is back, will ping him to join us next time) 2. ARM Support * a. Equipment * Steve gave the addresses for the location of the hosts, 4 in Alameda, and 1 in Ottawa lab, 1 remains to confirm. * ARM is sending those machines to these locations. * pre-installed? * b. CI/CD updates * CI/CD try to set up the workflow in ARM's local lab (ARM's Shanghai Lab), applied Jackie's patches, but may still need more patches to do builds. * c. Porting still in progreess (Jakie) * rewrote the coding to support build system for both x86 and arm * build system will detect the arch, and if it is arm, it will build arm arch. * Wrote up the SPEC on the implementtaion., and now waiting on SPEC to be review * SPEC review first then will send code for code review. * Some kernel modules don't work * QEMU is not working yet. Waiting on kernel up-rev, then and see if QEMU can be fixed then. * Created 2 wikipages for setting up the build environment for ARM arch: * https://wiki.openstack.org/wiki/StarlingX/StarlingX_Debian_on_ARM_Information_Guide * https://wiki.openstack.org/wiki/StarlingX/DebianArmBuildEnvironment * SPEC file review continoues, Kernel SPEC file needs reviewer. * Need more community reviewers. * d. Packages for x86_64 are in CNGN, need to push ARM packages there. * Set up the own (CNGN like) website, push the packages to the website as part of CI/CD website (/export/mirror) * Secureboot is disabled for now. Will do it in the future. * ELF SDK is used to build image. Need to push the SDK to CNGN, no permission to push to CNGN yet, it is on local disk. * AI: Need to provide permission to Jackie so that he can push ELF SDK to CNGN. * Need to change meta-lat layer for ELF SDK, but want to link the task to different repo, but can't. * meta-lat layer is not in the StarlingX repo, but its in github repo. fork it.. do a pull request to github lab for any changes. * meta-lat used is with the WR's repo, not community one. Will migrate later. * e. OSTree * removing OSTree from the installer ISO. (not from the StarlingX) * Work in progress, not sure when it will be ready. Possible early next year, StarlingX 9. 3. StarlingX 8.0 * SPEC from Chuck on OSTree generation on the controller, pending review. * Work is being done, but the SPEC will need to be rewritten. Deferred/Pending. Next Meeting: September 20, 2023 Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peng.Peng at windriver.com Tue Sep 19 16:40:59 2023 From: Peng.Peng at windriver.com (Peng, Peng) Date: Tue, 19 Sep 2023 16:40:59 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20230917T060059Z Message-ID: Sanity Test from 2023 August 19 (https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230917T060059Z/outputs/iso/starlingx-intel-x86-64-cd.iso) Status: GREEN SX sanity Passed: 17 (100.0%) Failed: 0 (0.0%) Total Executed: 17 List of Test Cases: ------------------------------------------------------ PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_push_docker_image_to_local_registry_active PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_isolated_2p_2_big_pod_best_effort_HT_AIO PASS test_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS test_sriovdp_netdev_connectivity_ipv4[1-1-calico-ipam] PASS test_sriovdp_mixed_add_vf_interface[1] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] DX sanity Passed: 19 (100.0%) Failed: 0 (0.0%) Total Executed: 19 List of Test Cases: ------------------------------------------------------ PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host PASS test_swact_controller_platform PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_push_docker_image_to_local_registry_active PASS test_push_docker_image_to_local_registry_standby PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_force_reboot_host[active_controller-True] PASS test_force_reboot_host[active_controller-False] PASS test_force_reboot_host[standby_controller-False] PASS test_bmc_verify_bm_type_ipmi PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] Regards, PV team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Juanita.Balaraj at windriver.com Tue Sep 19 22:24:59 2023 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Tue, 19 Sep 2023 22:24:59 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 15-09-2023 In-Reply-To: References: Message-ID: Hello All, Here are last week's doc team meeting minutes. Details in [2]. Join us if you have interest in StarlingX docs! We meet on Fridays 6:00 a.m. PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Thanks, Juanita Balaraj ============ 15- September-23 Action Items / Status: - Stx 9.0 Release Tracking Spreadsheet: Doc Stories are tracked in https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing. - To add stories that are planned for Stx 9.0 - AR Juanita - WIP (add / replan as required). Features have been removed from Stx 9.0. See https://etherpad.opendev.org/p/stx-cores for more details. - Discussion about Merging the Installation Guides ; Virtual env with the Bare metal docs. https://review.opendev.org/c/starlingx/docs/+/876107 - - Option discussed and solution is to maintain the virtual guide and pull the shared content in from Baremetal with tabs on the Virtual docs...as per discussion with Greg - AR Ron - Ron to update the Troubleshooting information in the Sphinx Contributor Guide - AR Ron - Discussion about upgrading to the latest Sphinx / tox version; https://pypi.org/project/tox/: https://review.opendev.org/c/starlingx/docs/+/890833 - AR Ron - Documentation Contributor Guide - StarlingX documentation - https://docs.starlingx.io/contributor/doc_contribute_guide.html - All to update the Contributor guide on an ongoing basis for new Styles / Standards implemented - The team to familiarize themselves with the Styles and Standards Guide. Contributor Guide - AR StarlingX Doc team Gerrit reviews: - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - Merged 4 Reviews. To get closure of the open reviews at the earliest. - Check with Greg and if the Installation doc updates are required on Stx 8.0 https://review.opendev.org/c/starlingx/docs/+/876107 - AR Ron / Juanita - https://review.opendev.org/c/starlingx/docs/+/890960 - AR Ron to check with Scott about the Antelope repositories Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 13 outstanding bugs. Miscellaneous Updates: - Stx. Virtual PTG Meeting: https://openinfra.dev/ptg/ - Stx Doc team is encouraged to participate in sessions as required. The Agenda is being tracked in https://etherpad.opendev.org/p/stx-ptg-planning-october-2023. - Update the Verified H/W page with the automated script updates https://www.windriver.com/studio/operator/self-validated-and-certified-hosts# - Currently Commented out - Script needs to be updated- Waiting for updates to the script -AR Ron - WIP - Bruno Muniz showed interest in creating DOC Videos supporting the StarlingX Installation Process. To check with Ildiko / Greg whether this is ok. These Videos can be hosted in a location in StarlingX. The Installation Docs can point to these videos - AR Bruno to get approvals from Ildiko / Greg for a future Update - Operations Guide Archive - On Hold until further clarifications are discussed with Greg (https://review.opendev.org/c/starlingx/docs/+/822030) Engineering Status: StarlingX Eng Stx Status: https://etherpad.opendev.org/p/stx-status StarlingX Eng Status 2023 https://etherpad.opendev.org/p/stx-cores StarlingX OS Status: https://etherpad.opendev.org/p/stx-distro-other ____________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Rob.Cooke at windriver.com Wed Sep 20 13:33:48 2023 From: Rob.Cooke at windriver.com (Cooke, Rob) Date: Wed, 20 Sep 2023 13:33:48 +0000 Subject: [Starlingx-discuss] Minutes: Test Status Call - September 19, 2023 Message-ID: Hi everyone, Please find below the minutes from this week's StarlingX Test Status Call: Minutes for 09/19/2023 * Open Topics: ? End of March 2024 being proposed as GA for STX9.0 * We will need to plan accordingly * Sanity Status: o Sanity on STX 9.0 - Green for SX and DX. ? Last execution, September 19, 2023 - Results email: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-September/014518.html * Sanity on STX 9.0 plus Openstack: ? Sanity skipped again for week of September 18th. * Hardware unavailable o the team is working on a solution to free something up * Team achieved success getting an Antelope build o This will be used for the next sanity once it is scheduled * Last Successful Execution: (OVS) Tue Aug 22 12:39:12 UTC 2023 - Overall status: YELLOW * Sanity - Passed: 13 (86.67%) | Failed: 2 (13.33%) * Regression - Passed: 9 (75.0%) | Failed: 3 (25.0%) * Master Build (20230820T060000Z) * Feature Test Status: o Feature testing is tracked in the following google sheet: ? https://docs.google.com/spreadsheets/d/1El3g0ute5K2S5DTR9p_rxa1jQlq8gcUzgMCNCE_sx8g/edit#gid=968103774 ? Some features are in progress, sheet does need updating ACTION: Rob/Nimalini * Regression Testing will be tracked here closer to release end: ? https://docs.google.com/spreadsheets/d/1NjYk9N0whK91nHViB5HFG2C1-XdJ09StVuLMxsz0KAY/edit?pli=1#gid=1717644237 Thanks, Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: