From scott.little at windriver.com Tue Jan 3 15:28:55 2023 From: scott.little at windriver.com (Scott Little) Date: Tue, 3 Jan 2023 10:28:55 -0500 Subject: [Starlingx-discuss] Happy New Year Message-ID: First post of 2023! Ok, my ulterior motive is that CENGN's script that scrapes sanity results from the list is unhappy that there are no posts yet in 2023. Scott From Peng.Peng at windriver.com Tue Jan 3 21:01:02 2023 From: Peng.Peng at windriver.com (Peng, Peng) Date: Tue, 3 Jan 2023 21:01:02 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20230101T070000Z Message-ID: Sanity Test from 2023 January 3 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230101T070000Z/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] Regards, PV team -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Wed Jan 4 03:08:48 2023 From: kennelson11 at gmail.com (Kendall Nelson) Date: Tue, 3 Jan 2023 21:08:48 -0600 Subject: [Starlingx-discuss] 2023 PTGs + Virtual Team Signup In-Reply-To: References: Message-ID: Hello Everyone! Wanted to resurface this email in your inboxes in case you were out on vacation when I sent the original! Email ptg at openinfra.dev if you have any questions! -Kendall Nelson (diablo_rojo) On Wed, Dec 14, 2022 at 8:22 AM Kendall Nelson wrote: > Hello Everyone! > > The next PTG on the calendar will be our usual virtual format and it will > take place March 27 -31. The project signup survey is already ready to go! > If your team is interested in participating, sign them up here[1]! > Registration is also open now[2] > > We have also heard many requests from the contributor community to bring > back in person events and also heard that with global travel reduction, it > would be better travel wise for the community at large to combine it with > the OpenInfra Summit[3]. So, an in-person PTG will take place Wednesday and > Thursday! June 14 -15th. OpenInfra Summit registration will be required to > participate, and contributor pricing and travel support[4] will be > available. > > We will also be planning another virtual PTG in the latter half of the > year. The exact date is still being finalized. > > This will give you three opportunities to get your team together in 2023: > two virtual and one in-person. > > > - > > Virtual: March 27-31 > - > > In- Person: June 14-15 collocated with the OpenInfra Summit > - > > Virtual: TBD, but second half of the year > > > As any project in our community, you are free to take advantage of all or > some of the PTGs this coming year. I, for one, hope to see you and your > project at as many as make sense for your team! > > To make sure we are as inclusive as possible I will continue to encourage > team moderators to write summaries of their discussions to gather and > promote after the events as well. > > Stay tuned for more info as we get closer, but the team signup survey[1] > has opened for the first virtual PTG and is ready for you! > > -Kendall (diablo_rojo) > > [1] https://openinfrafoundation.formstack.com/forms/march2023_vptg_survey > > [2] https://openinfra-ptg.eventbrite.com > > [3]https://openinfra.dev/summit/vancouver-2023 > > [4] https://openinfrafoundation.formstack.com/forms/openinfra_tsp > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openinfra.dev Wed Jan 4 05:07:37 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Tue, 3 Jan 2023 21:07:37 -0800 Subject: [Starlingx-discuss] The CFP for the OpenInfra Summit 2023 is open! In-Reply-To: References: <90DD4E6A-84BB-43D6-BCF6-4BAA3E3C96F4@openstack.org> Message-ID: Hi StarlingX Community, It is a friendly reminder that the CFP[1] for the upcoming OpenInfra Summit[2] (June 13-15, 2023) is still open! __The CFP closes January 10, 2023, at 11:59 p.m. PT__ The event is a great opportunity to raise awareness of the project as well as find and onboard new contributors! You can submit session proposals to cover different areas of the project, like a feature you?ve been working on, a case study or demo about how the platform works. Helpful tips to prepare your session proposal: * Take a look at the conference tracks[3] to see which one your talk fit into the best. This way you can fine tune your abstract and talk the theme of the track you pick. * Pick a catchy session title * Write an abstract that highlights the context and topics that you will cover (max. 1000 characters) * You will also need to explain what the audience will learn and take away from your presentation (max. 1000 characters) For more helpful tips and best practices on how to write up your session proposal, please see the OpenInfra Live episode[4] that was recorded during the CFP period for the previous OpenInfra Summit in Berlin. Please disregard any mentions in the video that are specific to the Summit that already happened in Berlin! Please let me know if you have any questions! Thanks and Best Regards, Ildik? [1] https://openinfra.dev/summit/vancouver-2023 [2] https://cfp.openinfra.dev/app/vancouver-2023/19/presentations [3] https://openinfra.dev/summit/vancouver-2023/summit-tracks/ [4] https://superuser.openstack.org/articles/berlin-openinfra-summit-2022-cfp-101-openinfra-live-recap/ ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Dec 15, 2022, at 17:03, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > It is a friendly reminder that the CFP for the upcoming OpenInfra Summit (June 13-15, 2023) is still open! > > The OpenInfra Summit will gather people who're building and running open source infrastructure including building blocks such as the Linux kernel, OpenStack, Kubernetes, StarlingX and more! The event is a great opportunity to raise awareness of the project as well as find and onboard new contributors to the project. > > I would like to encourage you to submit your proposals before the deadline. You can cover a feature that you are working on, talk about how to deploy and operate the platform or cover topics more in the area of community and open collaboration. > > __The CFP closes January 10, 2023, at 11:59 p.m. PT__ > > Please let me know if you need any help with putting together or review your abstract! > > Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > >> On Nov 15, 2022, at 07:00, Erin Disney wrote: >> >> Hi Everyone! >> >> The CFP for the 2023 OpenInfra Summit (June 13-15, 2023) is NOW LIVE [1]! Check out the full list of tracks and submit a talk on your topic of expertise [2]. >> >> The CFP closes January 10, 2023, at 11:59 p.m. PT >> >> We are also now accepting submissions for Forum sessions [3]! What should you submit to the forum vs. the traditional CFP? For the Forum, submit discussion-oriented sessions, including challenges around different software components, working group progress or best practices to tackle common issues. >> >> Looking for other resources? Registration [4], sponsorships [5], travel support [6] and visa requests [7] are also all open! >> >> Find all the information on the OpenInfra Summit 2023 in one place [8]! >> >> Cheers, >> Erin >> >> [1] https://cfp.openinfra.dev/app/vancouver-2023/19/presentations >> [2] https://openinfra.dev/summit/vancouver-2023/summit-tracks/ >> [3] https://cfp.openinfra.dev/app/vancouver-2023/20/ >> [4] http://openinfra.dev/summit/registration >> [5] http://openinfra.dev/summit/vancouver-2023/summit-sponsor/ >> [6] https://openinfrafoundation.formstack.com/forms/openinfra_tsp >> [7] https://openinfrafoundation.formstack.com/forms/visa_yvrsummit2023 >> [8] https://openinfra.dev/summit/vancouver-2023 >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From openinfradn at gmail.com Wed Jan 4 16:13:28 2023 From: openinfradn at gmail.com (open infra) Date: Wed, 4 Jan 2023 21:43:28 +0530 Subject: [Starlingx-discuss] stx-openstack apply failed after enabling cpu_dedicated_set Message-ID: Hi, I have enabled cpu on a worker node as per the documentation [1]. There were couple of VMs already created and vGPUs were attached to each VM. After configuring the worker, I just unlocked the worker and noticed that stx-openstack apply failed. Here is the armada log: https://paste.opendev.org/show/b4z1jLSPbeEZDXyvFeBV/ Couple of pods were failing. NAME READY STATUS RESTARTS AGE nova-compute-worker-ov-01-cdc7009a-n95w9 1/2 CrashLoopBackOff 18 (94s ago) 72m pci-irq-affinity-agent-2kgds 0/1 Init:0/1 0 24h Collect Logs available at [2]. pci-irq-affinity-agent-2kgds pod log: Error from server (BadRequest): container "pci-irq-affinity-agent" in pod "pci-irq-affinity-agent-2kgds" is waiting to start: PodInitializing [1] https://docs.starlingx.io/admintasks/openstack/configure-dedicated-and-shared-cpu-pools-on-hosts.html [2] https://drive.google.com/drive/folders/1YxuWOlkoHBsdg9UUuJ0ozZ2maxXcWzX-?usp=sharing Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openinfra.dev Wed Jan 4 18:00:26 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Wed, 4 Jan 2023 10:00:26 -0800 Subject: [Starlingx-discuss] StarlingX segment for the 2022 OpenInfra Foundation Annual report - REVIEW NEEDED In-Reply-To: References: Message-ID: Hi Greg, Thank you for the review! I will go ahead and delete that feature from the list as we have enough other content. In case you or anyone from the community can confirm that it made the release after all I can add it back. __The deadline to submit the annual report segment is this Friday (January 6).__ Please let me know if there is anything else in the text that needs to be fixed or should be included before the deadline! Thanks, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Dec 21, 2022, at 05:53, Waines, Greg wrote: > > hey Ildiko, > I took a quick read thru. > It looks good. > Only comment ... I believe we ended up NOT doing this feature: > Moving from all-in-one simplex to all-in-one duplex configuration without the need to re-install > > RamS ? ... can you confirm ? > > Greg. > > -----Original Message----- > From: Ildiko Vancsa > Sent: Wednesday, December 14, 2022 8:46 PM > To: StarlingX ML > Subject: [Starlingx-discuss] StarlingX segment for the 2022 OpenInfra Foundation Annual report - REVIEW NEEDED > > 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 StarlingX Community, > > I?m reaching out to you about the OpenInfra Foundation Annual Report for 2022. > > As every year the Foundation is putting out a report to summarize the activities and achievements for a calendar year. Since the project?s launch there is a segment that covers these topics for StarlingX as well. > > While 2022 is still rolling, I put together a starting point to cover StarlingX in the report next January: https://etherpad.opendev.org/p/2022_StarlingX_Annual_Update > > > Please review the text and either add questions or comments to the etherpad or reply to this thread if you have any comments or concerns. > > __Please provide your comments and input until EoD on January 4th, 2023.__ > > Thanks, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From ildiko at openinfra.dev Wed Jan 4 17:53:50 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Wed, 4 Jan 2023 09:53:50 -0800 Subject: [Starlingx-discuss] This week's TSC & Community Call is in APAC time Message-ID: Hi StarlingX Community, It is a friendly reminder that this week's TSC & Community Call will run in the APAC-friendly time slot on January 4 at 7pm US Pacific Time / January 5 at 11am China Standard Time! For further details about the call, including dial-in information, please see the ?Meetings? wiki page: https://wiki.openstack.org/wiki/Starlingx/Meetings#7pm_Pacific_on_Every_First_Wednesday_of_the_Month-_Technical_Steering_Committee_.26_Community_Call Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From Juanita.Balaraj at windriver.com Wed Jan 4 23:45:43 2023 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Wed, 4 Jan 2023 23:45:43 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 04-01-23 In-Reply-To: References: Message-ID: Hello All, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Thanks, Juanita Balaraj ============ 04-Jan-23 StarlingX 8.0 Release: - https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Doc Tasks created - Doc Team to ensure Stories/Tasks are added to the commit messages - Ongoing WIP - https://review.opendev.org/c/starlingx/docs/+/862705: Verified Hardware Updates - Done for Stx 8.0. - events.yaml - Reviewers need to refer to https://docs.starlingx.io/fault-mgmt/index-fault-98d5f50a9b8c.html to view updated alarms and log files. - Alarm updates are only supported on Master - Manual updates need to be implemented on the branches for alarms (events.yaml) since script is not supported on the branches as of date. - Doc Team to be included as part of the Gerrit review cycle for any alarm updates in the event.yaml files - To discuss details with Greg Waines / Frank Miller / Ghada (To update the Contributor Guide after discussion with the primes with the required process) Installation Guide - Restructuring of the Installation Guide is WIP and the plan is to deliver for stx 8.0?? Gerrit Reviews: - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - Merged 4 Reviews - Test teams need to review and +1 open Gerrit reviews wherever applicable NOTE: All core reviewers to review and +1 or WF the Doc reviews at : https://review.opendev.org/q/starlingx/docs+status:open Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 5 bugs outstanding - The DOC team to create LP defects corresponding with any DS defects - WIP. Teams to add all the impacted Releases when raising a LP bug Miscellaneous Updates: - Backslashes to be removed from rst files wherever applicable especially in code blocks, for example, \(code\_remove\) - To be cleaned up in rst files as the files are being updated for any doc Gerrit reviews. - Numbering in the Distributed Cloud Guide is causing issues - AR Ron to check - WIP General Updates: - Operations Guide Archive - On Hold until further clarifications are discussed with Greg (https://review.opendev.org/c/starlingx/docs/+/822030) ____________________ 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 openinfradn at gmail.com Thu Jan 5 01:41:01 2023 From: openinfradn at gmail.com (open infra) Date: Thu, 5 Jan 2023 07:11:01 +0530 Subject: [Starlingx-discuss] stx-openstack apply failed after enabling cpu_dedicated_set In-Reply-To: References: Message-ID: container logs of nova-compute-worker-ov-01-cdc7009a pod: https://paste.opendev.org/show/bGrxgZTRBp4SDnG8HHmI/ https://paste.opendev.org/show/b7TNroMVFQRibpPwt5Rc/ On Wed, Jan 4, 2023 at 9:43 PM open infra wrote: > Hi, > > I have enabled cpu on a worker node as per the documentation [1]. > There were couple of VMs already created and vGPUs were attached to each > VM. > > After configuring the worker, I just unlocked the worker and noticed that > stx-openstack apply failed. > Here is the armada log: > https://paste.opendev.org/show/b4z1jLSPbeEZDXyvFeBV/ > > Couple of pods were failing. > NAME READY STATUS > RESTARTS AGE > nova-compute-worker-ov-01-cdc7009a-n95w9 1/2 > CrashLoopBackOff 18 (94s ago) 72m > pci-irq-affinity-agent-2kgds 0/1 > Init:0/1 0 24h > > Collect Logs available at [2]. > > pci-irq-affinity-agent-2kgds pod log: > Error from server (BadRequest): container "pci-irq-affinity-agent" in pod > "pci-irq-affinity-agent-2kgds" is waiting to start: PodInitializing > > [1] > https://docs.starlingx.io/admintasks/openstack/configure-dedicated-and-shared-cpu-pools-on-hosts.html > > [2] > https://drive.google.com/drive/folders/1YxuWOlkoHBsdg9UUuJ0ozZ2maxXcWzX-?usp=sharing > > Regards, > Danishka > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Jan 5 02:05:34 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 5 Jan 2023 02:05:34 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Jan 4/2023 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Jan 4 2023 Happy New Year! stx.8.0 - Reference Links: - Release/Feature Planning: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Release Verification: - Folder: https://drive.google.com/drive/folders/1E_AQPxVrNnbVtSqQ9_CdqYidqMmYcq4n - Feature Testing: https://docs.google.com/spreadsheets/d/1yzlArypq3sgdNdYzMwBONLnOsx6OqMpxj6KT0P6Pc6M/edit#gid=968103774 - Regression Testing: https://docs.google.com/spreadsheets/d/1b5w2oLlGwipTlrNysWwl1JnM1dvyboIIQhpBJLcZECI/edit#gid=1717644237 - Feature Status - 27 features are Done. 16 in the last month. - 2 features still in progress -- related to stx-openstack - Debian: Migrate Openstack app related packages - Update openstack application containers to use Debian base image - 1 feature requires follow-up - Kubernetes Custom Configuration Support - Need to determine the status of this feature. This is likely Partial for stx.8.0 and continuing in stx.9.0. - 6 features deferred/continuing in stx.9.0 - Marvell Octeon NIC Accelerator Integration - Support for Silicom TimeSync Server Adaptor - Platform Network Parameters Reconfiguration - AppArmor Support - Vault Application Upversion - Portieris Application Upversion - Test Status - Regression re-forecasted to start Jan 11 instead of Jan 4. No change to completion date of Jan 25. - Release Notes - Will start posting the review in the next week stx.7.0 Blogs - PTP Enhancements - Multiple NIC Support / SyncE / Various NIC Support - Prime: Ghada Khalil - Forecast: mid-Sept >> end-Oct >> mid-Dec >> end-Jan / Author: Cole Walker - Status: Not Started. Targeting start in mid-Jan. - Subcloud Local Install - Prime: RamS - Forecast: end-Nov >> mid-Jan / Author: Shrikumar Sharma - Status: Started. On track to have a PR posted by mid-Jan stx.9.0 - New release folder created: https://drive.google.com/drive/folders/1beMET3I7GGa79tv4wfwzeKTy-yFVl6xR?usp=share_link - New Release/Feature Planning: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing - Populated with deferred features from stx.8.0 From Ghada.Khalil at windriver.com Thu Jan 5 21:56:16 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 5 Jan 2023 21:56:16 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Jan 4, 2023) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call January 4, 2023 Meeting is at 7pm PDT / 10pm EDT / +1 10am CST Happy New Year! Standing topics - Build - Main Branch Debian Builds - Build successful as of Jan 4 - Main Branch CentOS Builds - Build successful as of Jan 4 - CentOS Builds are planned to be stopped in Dec 2022 after 2 successful Debian-based stx-openstack sanities - Forecast: Dec 14 >> TBD - Scott (Dec 14): Should continue to run the CentOS builds for the container build portion as Debian builds don't build all the containers yet - stx.6.0 Weekly Build - Unsure of the status. - Sanity - Debian Main Branch Sanity - Last sanity email sent on Jan 3: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013717.html - Status: Green - stx-openstack Debian Main Branch Sanity - Last sanity email on Dec 30: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-December/013715.html - Status: Red - LPs: - https://bugs.launchpad.net/starlingx/+bug/1999445 >> fix is in test. - https://bugs.launchpad.net/starlingx/+bug/2000168 >> lower priority. no negative functional impact - https://bugs.launchpad.net/starlingx/+bug/2000483 - Should be able to make some progress now that developers/core reviewers are back from the holidays. - Gerrit Reviews in Need of Attention - From previous meetings: Fixes to libvirt env: https://review.opendev.org/c/starlingx/tools/+/863735 - Review comments provided in Nov; still waiting for author (Scott Kamp) to respond/address review comments - Jan 4: Scott will update by EOW - 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 - Virtual PTG planned for March / In-Person Summit/PTG planned for June - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013718.html - In-person PTG co-located with the OpenInfra Summit, June 13-15 in Vancouver Canada - https://openinfra.dev/summit/vancouver-2023 - Call For Papers for the June Summit - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013719.html - Deadline is Jan 10 ARs from Previous Meetings - None Open Requests for Help - stx-openstack apply failed after enabling cpu_dedicated_setInbox - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013720.html - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013724.html - Seen w/ stx.7.0. Issue only happens when setting cpu dedicated CPUs on a running system. During the unlock, the openstack fails to re-apply. - Action: Scott Kamp will have his team look at this issue - Documenting Tested Hardware by the community - Action: Scott Kamp will discuss with the TSC how to best capture this - StarlingX 7.0 & 8.0 deployment failures - Reported by ScottK in the Nov 16 meeting - Working through installation issues on various hardware. Will share more info w/ the mailing list once issues are more isolated. - Nov 23: Team working thru setting up new hardware to re-test the deployments. - Nov 30: No Update - Dec 7: Team is trying a deployment this week. Will have an update for next week (Dec 14) - Dec 14, 21: No Update as ScottK did not attend. - Jan 4: Confirmed that the issue was related to a bad memory chip. Was successful in deploying on other functional hardware. - Consider Closed. From Steven.Webster at windriver.com Thu Jan 5 23:04:57 2023 From: Steven.Webster at windriver.com (Webster, Steven) Date: Thu, 5 Jan 2023 23:04:57 +0000 Subject: [Starlingx-discuss] Minutes: networking sub-team meeting 01-05-23 Message-ID: Happy new year everyone ======== Next meeting: 01-19-23 Meeting logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings Agenda/Detailed minutes are posted at: https://etherpad.opendev.org/p/stx-networking ======== Feature Updates: FEC Operator Integration: https://storyboard.openstack.org/#!/story/2009749 - Feature docs updated - Feature testing complete for device variants ACC100, N3000, ACC200 - Actions: - Still need to verify pf-bb-config w/ secure boot Marvell Accelerator Support in StarlingX: https://storyboard.openstack.org/#!/story/2010047 - Not able to have the driver integrated in kernel.org - Planning to proceed with posting the driver on sourceforge Silicom NIC support https://storyboard.openstack.org/#!/story/2010213 - Deferred to stx 9.0 ORAN O2 Service: https://storyboard.openstack.org/#!/story/2010278 - Feature testing complete as of mid. Dec 2022 Platform network reconfig (distributed cloud) - target: stx 9.0 - Work ongoing, 12 reviews in progress. -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Fri Jan 6 00:56:06 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 5 Jan 2023 19:56:06 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 1061 - Failure! Message-ID: <824315724.133.1672966567613.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 1061 Status: Failure Timestamp: 20230106T000624Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230106T000624Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From starlingx.build at gmail.com Fri Jan 6 00:56:03 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 5 Jan 2023 19:56:03 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 3518 - Failure! Message-ID: <910420252.130.1672966564667.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 3518 Status: Failure Timestamp: 20230106T004335Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230106T000624Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20230106T000624Z DOCKER_BUILD_ID: jenkins-master-flock-20230106T000624Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230106T000624Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20230106T000624Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From Lucas.DeAtaidesBarreto at windriver.com Fri Jan 6 13:01:05 2023 From: Lucas.DeAtaidesBarreto at windriver.com (De Ataides Barreto, Lucas) Date: Fri, 6 Jan 2023 13:01:05 +0000 Subject: [Starlingx-discuss] Sanity - StarlingX + STX-Openstack MASTER build ISO [20230104T070000Z] results - Jan-5 Message-ID: Hi all, Here are the results for StarlingX + STX-Openstack using the Jan-4 build: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230104T070000Z/outputs/iso/starlingx-intel-x86-64-20230104154137-cd.iso and Helm-Charts: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230104T070000Z/outputs/helm-charts/stx-openstack-1.0-1.stx.4-debian-stable-latest.tgz Overall Sanity Results: RED AIO-DX Baremetal with VSWITCH_TYPE=ovs Sanity Status: RED Automated Test Results Summary: ------------------------------------------------------ Passed: 9 (60.0%) Failed: 6 (40.0%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS 20230105 20:15:31 test_ssh_to_hosts FAIL 20230105 20:16:27 test_lock_unlock_host PASS 20230105 20:18:47 test_openstack_services_healthy PASS 20230105 20:19:15 test_reapply_stx_openstack_no_change[controller-0] PASS 20230105 20:21:35 test_reapply_stx_openstack_no_change[controller-1] PASS 20230105 20:34:00 test_horizon_create_delete_instance FAIL 20230105 20:40:56 test_swact_controllers PASS 20230105 20:49:26 test_ping_between_two_vms[tis-centos-guest-virtio-virtio] FAIL 20230105 20:53:11 test_migrate_vm[tis-centos-guest-live-None] FAIL 20230105 20:55:34 test_nova_actions[tis-centos-guest-dedicated-pause-unpause] FAIL 20230105 20:57:58 test_nova_actions[tis-centos-guest-dedicated-suspend-resume] FAIL 20230105 21:00:31 test_evacuate_vms PASS 20230105 21:30:20 test_system_coredumps_and_crashes[core_dumps] PASS 20230105 21:30:34 test_system_coredumps_and_crashes[crash_reports] PASS 20230105 21:30:41 test_system_alarms ----------------------------------------------------------------------- All the failed test cases above are related to these launchpads: * https://bugs.launchpad.net/starlingx/+bug/1999445 * https://bugs.launchpad.net/starlingx/+bug/2000483 * https://bugs.launchpad.net/starlingx/+bug/2002113 (NEW) Thanks, STX-Openstack Distro Team * -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Fri Jan 6 15:17:02 2023 From: openinfradn at gmail.com (open infra) Date: Fri, 6 Jan 2023 20:47:02 +0530 Subject: [Starlingx-discuss] stx-openstack apply failed after enabling cpu_dedicated_set In-Reply-To: References: Message-ID: Hi Thales, I have created a LP. https://bugs.launchpad.net/starlingx/+bug/2002157 Regards, Danishka On Fri, Jan 6, 2023 at 6:48 PM Cervi, Thales Elero < ThalesElero.Cervi at windriver.com> wrote: > Hi Danishka, > > Thanks for raising this issue. Do you mind creating a Launchpad for it > though? > This way we can centralize any discussion/investigation topics there and > it can go through the appropriate triage process so the team can prioritize > this work. > > --- > Regards, > Thales > ------------------------------ > *From:* open infra > *Sent:* Wednesday, January 4, 2023 1:13 PM > *To:* StarlingX ML > *Subject:* [Starlingx-discuss] stx-openstack apply failed after enabling > cpu_dedicated_set > > * 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, > > I have enabled cpu on a worker node as per the documentation [1]. > There were couple of VMs already created and vGPUs were attached to each > VM. > > After configuring the worker, I just unlocked the worker and noticed that > stx-openstack apply failed. > Here is the armada log: > https://paste.opendev.org/show/b4z1jLSPbeEZDXyvFeBV/ > > > Couple of pods were failing. > NAME READY STATUS > RESTARTS AGE > nova-compute-worker-ov-01-cdc7009a-n95w9 1/2 > CrashLoopBackOff 18 (94s ago) 72m > pci-irq-affinity-agent-2kgds 0/1 > Init:0/1 0 24h > > Collect Logs available at [2]. > > pci-irq-affinity-agent-2kgds pod log: > Error from server (BadRequest): container "pci-irq-affinity-agent" in pod > "pci-irq-affinity-agent-2kgds" is waiting to start: PodInitializing > > [1] > https://docs.starlingx.io/admintasks/openstack/configure-dedicated-and-shared-cpu-pools-on-hosts.html > > > [2] > https://drive.google.com/drive/folders/1YxuWOlkoHBsdg9UUuJ0ozZ2maxXcWzX-?usp=sharing > > > Regards, > Danishka > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ThalesElero.Cervi at windriver.com Fri Jan 6 13:18:36 2023 From: ThalesElero.Cervi at windriver.com (Cervi, Thales Elero) Date: Fri, 6 Jan 2023 13:18:36 +0000 Subject: [Starlingx-discuss] stx-openstack apply failed after enabling cpu_dedicated_set In-Reply-To: References: Message-ID: Hi Danishka, Thanks for raising this issue. Do you mind creating a Launchpad for it though? This way we can centralize any discussion/investigation topics there and it can go through the appropriate triage process so the team can prioritize this work. --- Regards, Thales ________________________________ From: open infra Sent: Wednesday, January 4, 2023 1:13 PM To: StarlingX ML Subject: [Starlingx-discuss] stx-openstack apply failed after enabling cpu_dedicated_set 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, I have enabled cpu on a worker node as per the documentation [1]. There were couple of VMs already created and vGPUs were attached to each VM. After configuring the worker, I just unlocked the worker and noticed that stx-openstack apply failed. Here is the armada log: https://paste.opendev.org/show/b4z1jLSPbeEZDXyvFeBV/ Couple of pods were failing. NAME READY STATUS RESTARTS AGE nova-compute-worker-ov-01-cdc7009a-n95w9 1/2 CrashLoopBackOff 18 (94s ago) 72m pci-irq-affinity-agent-2kgds 0/1 Init:0/1 0 24h Collect Logs available at [2]. pci-irq-affinity-agent-2kgds pod log: Error from server (BadRequest): container "pci-irq-affinity-agent" in pod "pci-irq-affinity-agent-2kgds" is waiting to start: PodInitializing [1] https://docs.starlingx.io/admintasks/openstack/configure-dedicated-and-shared-cpu-pools-on-hosts.html [2] https://drive.google.com/drive/folders/1YxuWOlkoHBsdg9UUuJ0ozZ2maxXcWzX-?usp=sharing Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From ThalesElero.Cervi at windriver.com Fri Jan 6 16:07:59 2023 From: ThalesElero.Cervi at windriver.com (Cervi, Thales Elero) Date: Fri, 6 Jan 2023 16:07:59 +0000 Subject: [Starlingx-discuss] stx-openstack apply failed after enabling cpu_dedicated_set In-Reply-To: References: Message-ID: Brilliant Danishka, thanks for raising it. We will handle it via LP from now on, probably will discuss the priority in the next planning or community call after some triage. --- Regards, Thales ________________________________ From: open infra Sent: Friday, January 6, 2023 12:17 PM To: Cervi, Thales Elero Cc: StarlingX ML Subject: Re: [Starlingx-discuss] stx-openstack apply failed after enabling cpu_dedicated_set 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 Thales, I have created a LP. https://bugs.launchpad.net/starlingx/+bug/2002157 Regards, Danishka On Fri, Jan 6, 2023 at 6:48 PM Cervi, Thales Elero > wrote: Hi Danishka, Thanks for raising this issue. Do you mind creating a Launchpad for it though? This way we can centralize any discussion/investigation topics there and it can go through the appropriate triage process so the team can prioritize this work. --- Regards, Thales ________________________________ From: open infra > Sent: Wednesday, January 4, 2023 1:13 PM To: StarlingX ML > Subject: [Starlingx-discuss] stx-openstack apply failed after enabling cpu_dedicated_set 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, I have enabled cpu on a worker node as per the documentation [1]. There were couple of VMs already created and vGPUs were attached to each VM. After configuring the worker, I just unlocked the worker and noticed that stx-openstack apply failed. Here is the armada log: https://paste.opendev.org/show/b4z1jLSPbeEZDXyvFeBV/ Couple of pods were failing. NAME READY STATUS RESTARTS AGE nova-compute-worker-ov-01-cdc7009a-n95w9 1/2 CrashLoopBackOff 18 (94s ago) 72m pci-irq-affinity-agent-2kgds 0/1 Init:0/1 0 24h Collect Logs available at [2]. pci-irq-affinity-agent-2kgds pod log: Error from server (BadRequest): container "pci-irq-affinity-agent" in pod "pci-irq-affinity-agent-2kgds" is waiting to start: PodInitializing [1] https://docs.starlingx.io/admintasks/openstack/configure-dedicated-and-shared-cpu-pools-on-hosts.html [2] https://drive.google.com/drive/folders/1YxuWOlkoHBsdg9UUuJ0ozZ2maxXcWzX-?usp=sharing Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From helena at openstack.org Fri Jan 6 19:09:06 2023 From: helena at openstack.org (Helena Spease) Date: Fri, 6 Jan 2023 13:09:06 -0600 Subject: [Starlingx-discuss] The OpenInfra Summit 2023 CFP is closing soon! Message-ID: <774B3ACD-0A3D-4468-8CEB-C4FED5C3A01C@openstack.org> Hi Everyone! The CFP for the 2023 OpenInfra Summit (June 13-15, 2023) is closing in just a few days[1]! Check out the full list of tracks and submit a talk on your topic of expertise [2]. The CFP closes January 10, 2023, at 11:59 p.m. PT. See what that is in your timezone [3] We are also now accepting submissions for Forum sessions [4]! Looking for other resources? Find information on registration, sponsorships, travel support and visa requests at https://openinfra.dev/summit/ If you have any questions feel free to reach out :) Cheers, Helena [1] https://cfp.openinfra.dev/app/vancouver-2023/19/presentations [2] https://openinfra.dev/summit/vancouver-2023/summit-tracks/ [3] https://www.timeanddate.com/worldclock/fixedtime.html?msg=2023+OpenInfra+Summit+CFP+Closes&iso=20230110T2359&p1=137 [4] https://cfp.openinfra.dev/app/vancouver-2023/20/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Sat Jan 7 03:08:56 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Fri, 6 Jan 2023 22:08:56 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 1062 - Still Failing! In-Reply-To: <535106359.131.1672966565416.JavaMail.javamailuser@localhost> References: <535106359.131.1672966565416.JavaMail.javamailuser@localhost> Message-ID: <2122867059.140.1673060937112.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 1062 Status: Still Failing Timestamp: 20230107T021638Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230107T021638Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From starlingx.build at gmail.com Sat Jan 7 03:08:52 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Fri, 6 Jan 2023 22:08:52 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 3521 - Failure! Message-ID: <2000314745.137.1673060934450.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 3521 Status: Failure Timestamp: 20230107T025559Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230107T021638Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20230107T021638Z DOCKER_BUILD_ID: jenkins-master-flock-20230107T021638Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230107T021638Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20230107T021638Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From starlingx.build at gmail.com Sat Jan 7 17:07:37 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 7 Jan 2023 12:07:37 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 1605 - Failure! Message-ID: <920422837.143.1673111258568.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 1605 Status: Failure Timestamp: 20230107T141418Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20230107T140000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20230107T140000Z DOCKER_BUILD_ID: jenkins-master-20230107T140000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20230107T140000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20230107T140000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From starlingx.build at gmail.com Sat Jan 7 17:07:40 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 7 Jan 2023 12:07:40 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1463 - Failure! Message-ID: <1434019953.146.1673111261495.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1463 Status: Failure Timestamp: 20230107T140000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20230107T140000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From starlingx.build at gmail.com Mon Jan 9 00:57:37 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sun, 8 Jan 2023 19:57:37 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 3530 - Failure! Message-ID: <556713458.152.1673225858936.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 3530 Status: Failure Timestamp: 20230109T004526Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230109T000805Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20230109T000805Z DOCKER_BUILD_ID: jenkins-master-flock-20230109T000805Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230109T000805Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20230109T000805Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From starlingx.build at gmail.com Mon Jan 9 00:57:41 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sun, 8 Jan 2023 19:57:41 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 1063 - Still Failing! In-Reply-To: <335245225.138.1673060935101.JavaMail.javamailuser@localhost> References: <335245225.138.1673060935101.JavaMail.javamailuser@localhost> Message-ID: <851079099.155.1673225861863.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 1063 Status: Still Failing Timestamp: 20230109T000805Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230109T000805Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From amy at demarco.com Mon Jan 9 13:48:04 2023 From: amy at demarco.com (Amy Marrich) Date: Mon, 9 Jan 2023 07:48:04 -0600 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 continue working on planning for the OpenInfra Summit as well as Foundation-wide surveys. Thanks, Amy (spotz) 0 - https://etherpad.opendev.org/p/diversity-wg-agenda -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Tue Jan 10 02:13:08 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Mon, 9 Jan 2023 21:13:08 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 1064 - Still Failing! In-Reply-To: <1797361567.153.1673225859636.JavaMail.javamailuser@localhost> References: <1797361567.153.1673225859636.JavaMail.javamailuser@localhost> Message-ID: <1893383676.162.1673316788890.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 1064 Status: Still Failing Timestamp: 20230110T011934Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230110T011934Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From starlingx.build at gmail.com Tue Jan 10 02:13:04 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Mon, 9 Jan 2023 21:13:04 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 3533 - Failure! Message-ID: <2049659569.159.1673316785958.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 3533 Status: Failure Timestamp: 20230110T015932Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230110T011934Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20230110T011934Z DOCKER_BUILD_ID: jenkins-master-flock-20230110T011934Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230110T011934Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20230110T011934Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From helena at openstack.org Tue Jan 10 17:05:29 2023 From: helena at openstack.org (Helena Spease) Date: Tue, 10 Jan 2023 11:05:29 -0600 Subject: [Starlingx-discuss] The OpenInfra Summit 2023 CFP is closing soon! In-Reply-To: <774B3ACD-0A3D-4468-8CEB-C4FED5C3A01C@openstack.org> References: <774B3ACD-0A3D-4468-8CEB-C4FED5C3A01C@openstack.org> Message-ID: Hi everyone, I want to throw out a reminder that it is the last day to submit your talks to the CFP for the 2023 OpenInfra Summit (June 13-15, 2023)[1]! The CFP closes January 10, 2023, at 11:59 p.m. PT. Happy CFP-ing, everyone! Cheers, Helena [1] https://openinfra.dev/summit/vancouver-2023/summit-tracks/ > On Jan 6, 2023, at 1:09 PM, Helena Spease wrote: > > Hi Everyone! > > The CFP for the 2023 OpenInfra Summit (June 13-15, 2023) is closing in just a few days[1]! Check out the full list of tracks and submit a talk on your topic of expertise [2]. > > The CFP closes January 10, 2023, at 11:59 p.m. PT. See what that is in your timezone [3] > > We are also now accepting submissions for Forum sessions [4]! Looking for other resources? Find information on registration, sponsorships, travel support and visa requests at https://openinfra.dev/summit/ > > If you have any questions feel free to reach out :) > > Cheers, > Helena > > [1] https://cfp.openinfra.dev/app/vancouver-2023/19/presentations > [2] https://openinfra.dev/summit/vancouver-2023/summit-tracks/ > [3] https://www.timeanddate.com/worldclock/fixedtime.html?msg=2023+OpenInfra+Summit+CFP+Closes&iso=20230110T2359&p1=137 > [4] https://cfp.openinfra.dev/app/vancouver-2023/20/ _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Wed Jan 11 02:20:20 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 10 Jan 2023 21:20:20 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 3536 - Failure! Message-ID: <1664242064.166.1673403621384.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 3536 Status: Failure Timestamp: 20230111T020535Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230111T012209Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20230111T012209Z DOCKER_BUILD_ID: jenkins-master-flock-20230111T012209Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230111T012209Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20230111T012209Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From starlingx.build at gmail.com Wed Jan 11 02:20:23 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 10 Jan 2023 21:20:23 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 1065 - Still Failing! In-Reply-To: <908463039.160.1673316786702.JavaMail.javamailuser@localhost> References: <908463039.160.1673316786702.JavaMail.javamailuser@localhost> Message-ID: <911558406.169.1673403624232.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 1065 Status: Still Failing Timestamp: 20230111T012209Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230111T012209Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From Peng.Peng at windriver.com Wed Jan 11 13:59:39 2023 From: Peng.Peng at windriver.com (Peng, Peng) Date: Wed, 11 Jan 2023 13:59:39 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20230108T070000Z Message-ID: Sanity Test from 2023 January 10 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230108T070000Z/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] Regards, PV team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Linda.Wang at windriver.com Wed Jan 11 20:25:48 2023 From: Linda.Wang at windriver.com (Wang, Linda) Date: Wed, 11 Jan 2023 20:25:48 +0000 Subject: [Starlingx-discuss] Bi-Weekly StarlingX OS Distro & Multi-OS meeting minutes - January 11th, 2023 Message-ID: Jan 11, 2023 Attendees: Mark A., Scott, Marcelo, Linda Happy belated New Year! 1. General Topic ???1.1 Split package list between repositories (ISO and container images) * AI: We'll need to look closely to see if there is. any further improvement is needed 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. 1.3 Pre-patch ISO (Luis) (Carols replacing Luis Barbosa) * AI: to invite Carlos to this meeting to discuss Pre-patch ISO. 2. StarlingX 8.0 2.1 Secureboot Enablement * Need to have a different repo/storage to storage keys without changing any code. * One option is to interface with the concept of Vault. * Sent the checksum into the Vault to get sign. and the key is always in the Vault. * Put the public key into the public key ring. * AI: to invite DevSecOPs team from Studio side to discuss Vault's implementation. 2.2 ISO size greater than 4G ISO size limit with OOT driver may need to include the kernel source/debug package that will allow OOT tree driver to be built on customer target. * This will add the ISO size back up to greater than 4G. * Extension to the ISO build standard, 9660, for longer file names, addresses the daisy chain of the ISO for larger achieve. * AI: need to investigate the "ISO daisy chain extension of another 4G, and tooling needs. 2.3 Kernel Live Patching Integration with the build system * start to look into the requirements of integration of feature. Next Meeting: January 25th, 2023 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Juanita.Balaraj at windriver.com Wed Jan 11 22:36:04 2023 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Wed, 11 Jan 2023 22:36:04 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 11-01-23 In-Reply-To: References: Message-ID: Hello All, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Thanks, Juanita Balaraj ============ 11-Jan-23 StarlingX 8.0 Release: - https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Doc Tasks created - Doc Team to ensure Stories/Tasks are added to the commit messages - Ongoing WIP - events.yaml - Reviewers need to refer to https://docs.starlingx.io/fault-mgmt/index-fault-98d5f50a9b8c.html to view updated alarms and log files. - Alarm updates are only supported on Master - Manual updates need to be implemented on the branches for alarms (events.yaml) since script is not supported on the branches as of date. - Doc Team to be included as part of the Gerrit review cycle for any alarm updates in the event.yaml files - To discuss details with Greg Waines / Frank Miller / Ghada (To update the Contributor Guide after discussion with the primes with the required process) Installation Guide - Restructuring of the Installation Guide is WIP and the plan is to deliver for stx 8.0?? Gerrit Reviews: - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - Merged 3 Reviews - Test teams need to review and +1 open Gerrit reviews wherever applicable NOTE: All core reviewers to review and +1 or WF the Doc reviews at : https://review.opendev.org/q/starlingx/docs+status:open Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 6 bugs outstanding - The DOC team to create LP defects corresponding with any DS defects - WIP. Teams to add all the impacted Releases when raising a LP bug Miscellaneous Updates: - Elisa and Elaine reported tox related failutres in the last 24-48 hours. To forward the gerrit URLs to Ron. - Backslashes to be removed from rst files wherever applicable especially in code blocks, for example, \(code\_remove\) - To be cleaned up in rst files as the files are being updated for any doc Gerrit reviews. - Numbering in the Distributed Cloud Guide is causing issues - AR Ron to check - WIP General Updates: - Operations Guide Archive - On Hold until further clarifications are discussed with Greg (https://review.opendev.org/c/starlingx/docs/+/822030) ____________________ 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 starlingx.build at gmail.com Thu Jan 12 02:18:59 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 11 Jan 2023 21:18:59 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 3539 - Failure! Message-ID: <406613801.175.1673489941207.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 3539 Status: Failure Timestamp: 20230112T020324Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230112T012225Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20230112T012225Z DOCKER_BUILD_ID: jenkins-master-flock-20230112T012225Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230112T012225Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20230112T012225Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From starlingx.build at gmail.com Thu Jan 12 02:19:03 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 11 Jan 2023 21:19:03 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 1066 - Still Failing! In-Reply-To: <1401576513.167.1673403622171.JavaMail.javamailuser@localhost> References: <1401576513.167.1673403622171.JavaMail.javamailuser@localhost> Message-ID: <1192820452.178.1673489944119.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 1066 Status: Still Failing Timestamp: 20230112T012225Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230112T012225Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From ildiko at openinfra.dev Thu Jan 12 04:52:28 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Wed, 11 Jan 2023 20:52:28 -0800 Subject: [Starlingx-discuss] Diversity and Inclusion survey and efforts at OpenInfra Message-ID: <93EED86F-FD84-4897-A07E-429917A33B2D@openinfra.dev> Hi Starlingx Community, I?m reaching out to you to raise awareness about the Diversity & Inclusion Working Group (D&I WG)[1] and its efforts. The working group is a top-level working group under the OpenInfra Foundation and is working with the OpenInfra communities and Board of Directors to help the communities to build and maintain a diverse and inclusive environment. It is crucial for every OpenInfra community, including StarlingX to participate in these efforts to ensure that the project has all the resources to build an ecosystem where all people feel safe and welcomed. The D&I WG is currently targeting to create and release a new survey to help understand contributor demographics as well as challenges they face as they are participating in the projects they are interested in. To ensure that all projects get meaningful information that they care about, the working group is inviting and encouraging contributors from every community, including StarlingX, to participate. As an example to what scope the survey covers, please see this older OpenStack Diversity Survey: https://www.surveymonkey.com/r/OpenStackDiversity The aim is to finalize and have the new survey available by the OpenInfra Summit in June. People who are participating in the effort will use the D&I WG meetings and the group?s PTG session to make progress. I?m looking for a few volunteers to participate in the D&I efforts. Who from the community would be interested? Thanks and Best Regards, Ildik? [1] https://wiki.openstack.org/wiki/Diversity ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From starlingx.build at gmail.com Fri Jan 13 01:00:56 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 12 Jan 2023 20:00:56 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 3542 - Failure! Message-ID: <273183719.185.1673571657634.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 3542 Status: Failure Timestamp: 20230113T004508Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230113T000759Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20230113T000759Z DOCKER_BUILD_ID: jenkins-master-flock-20230113T000759Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230113T000759Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20230113T000759Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From starlingx.build at gmail.com Fri Jan 13 01:00:59 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 12 Jan 2023 20:00:59 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 1067 - Still Failing! In-Reply-To: <813264580.176.1673489942019.JavaMail.javamailuser@localhost> References: <813264580.176.1673489942019.JavaMail.javamailuser@localhost> Message-ID: <2138580139.188.1673571661683.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 1067 Status: Still Failing Timestamp: 20230113T000759Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230113T000759Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From Lucas.DeAtaidesBarreto at windriver.com Fri Jan 13 17:07:09 2023 From: Lucas.DeAtaidesBarreto at windriver.com (De Ataides Barreto, Lucas) Date: Fri, 13 Jan 2023 17:07:09 +0000 Subject: [Starlingx-discuss] Sanity - StarlingX + STX-Openstack MASTER build ISO [20230111T070000Z] results - Jan-13 Message-ID: Hi all, Here are the results for StarlingX + STX-Openstack using the Jan-4 build: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230112T070000Z/outputs/iso/starlingx-intel-x86-64-20230112155308-cd.iso and Helm-Charts: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230111T070000Z/outputs/helm-charts/stx-openstack-1.0-1.stx.4-debian-stable-versioned.tgz Overall Sanity Results: YELLOW AIO-DX Baremetal with VSWITCH_TYPE=ovs Sanity Status: YELLOW Automated Test Results Summary: ------------------------------------------------------ Passed: 7 (46.6%) Failed: 8 (53.0%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS 20230113 13:14:04 test_ssh_to_hosts FAIL 20230113 13:15:20 test_lock_unlock_host PASS 20230113 13:18:23 test_openstack_services_healthy PASS 20230113 13:19:10 test_reapply_stx_openstack_no_change[controller-0] PASS 20230113 13:23:17 test_reapply_stx_openstack_no_change[controller-1] PASS 20230113 13:48:33 test_horizon_create_delete_instance PASS 20230113 13:56:21 test_swact_controllers FAIL 20230113 14:14:37 test_ping_between_two_vms[tis-centos-guest-virtio-virtio] FAIL 20230113 14:15:03 test_migrate_vm[tis-centos-guest-live-None] FAIL 20230113 14:19:13 test_nova_actions[tis-centos-guest-dedicated-pause-unpause] FAIL 20230113 14:22:21 test_nova_actions[tis-centos-guest-dedicated-suspend-resume] FAIL 20230113 14:25:36 test_evacuate_vms FAIL 20230113 15:09:17 test_system_coredumps_and_crashes[core_dumps] FAIL 20230113 15:09:41 test_system_coredumps_and_crashes[crash_reports] PASS 20230113 15:11:47 test_system_alarms ----------------------------------------------------------------------- All the failed test cases above are related to these launchpads: * https://bugs.launchpad.net/starlingx/+bug/1999445 * https://bugs.launchpad.net/starlingx/+bug/2000483 * https://bugs.launchpad.net/starlingx/+bug/2000168 Thanks, STX-Openstack Distro Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lucas.DeAtaidesBarreto at windriver.com Fri Jan 13 17:16:46 2023 From: Lucas.DeAtaidesBarreto at windriver.com (De Ataides Barreto, Lucas) Date: Fri, 13 Jan 2023 17:16:46 +0000 Subject: [Starlingx-discuss] Sanity - StarlingX + STX-Openstack MASTER build ISO [20230111T070000Z] results - Jan-13 In-Reply-To: References: Message-ID: Hi all, Sorry for the confusion, these are the results for StarlingX + STX-Openstack using the Jan-11 build. Thanks, STX-Openstack Distro Team ________________________________ From: De Ataides Barreto, Lucas Sent: Friday, January 13, 2023 2:07 PM To: starlingx-discuss at lists.starlingx.io Subject: Sanity - StarlingX + STX-Openstack MASTER build ISO [20230111T070000Z] results - Jan-13 Hi all, Here are the results for StarlingX + STX-Openstack using the Jan-4 build: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230112T070000Z/outputs/iso/starlingx-intel-x86-64-20230112155308-cd.iso and Helm-Charts: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230111T070000Z/outputs/helm-charts/stx-openstack-1.0-1.stx.4-debian-stable-versioned.tgz Overall Sanity Results: YELLOW AIO-DX Baremetal with VSWITCH_TYPE=ovs Sanity Status: YELLOW Automated Test Results Summary: ------------------------------------------------------ Passed: 7 (46.6%) Failed: 8 (53.0%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS 20230113 13:14:04 test_ssh_to_hosts FAIL 20230113 13:15:20 test_lock_unlock_host PASS 20230113 13:18:23 test_openstack_services_healthy PASS 20230113 13:19:10 test_reapply_stx_openstack_no_change[controller-0] PASS 20230113 13:23:17 test_reapply_stx_openstack_no_change[controller-1] PASS 20230113 13:48:33 test_horizon_create_delete_instance PASS 20230113 13:56:21 test_swact_controllers FAIL 20230113 14:14:37 test_ping_between_two_vms[tis-centos-guest-virtio-virtio] FAIL 20230113 14:15:03 test_migrate_vm[tis-centos-guest-live-None] FAIL 20230113 14:19:13 test_nova_actions[tis-centos-guest-dedicated-pause-unpause] FAIL 20230113 14:22:21 test_nova_actions[tis-centos-guest-dedicated-suspend-resume] FAIL 20230113 14:25:36 test_evacuate_vms FAIL 20230113 15:09:17 test_system_coredumps_and_crashes[core_dumps] FAIL 20230113 15:09:41 test_system_coredumps_and_crashes[crash_reports] PASS 20230113 15:11:47 test_system_alarms ----------------------------------------------------------------------- All the failed test cases above are related to these launchpads: * https://bugs.launchpad.net/starlingx/+bug/1999445 * https://bugs.launchpad.net/starlingx/+bug/2000483 * https://bugs.launchpad.net/starlingx/+bug/2000168 Thanks, STX-Openstack Distro Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Mon Jan 16 13:35:37 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 16 Jan 2023 13:35:37 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Jan 11, 2023) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call January 11, 2023 Standing topics - Build - Main Branch Debian Builds - Green all week - Main Branch CentOS Builds - Builds started failing as of Jan 4. - LP: https://bugs.launchpad.net/starlingx/+bug/2002423 - Introduced by recent code changes which are only compatible w/ python3 - Stopping CentOS Builds - Currently running for the container builds as Debian builds don't build all the containers yet - Need the openstack image builds to transition to the Debian build. This is currently in progress. Forecast: Jan 16 - Action: Ghada to send an email to the community announcing the plan to stop the builds - Forecast: Dec 14 >> Jan 31 (tentative; pending feedback from the larger community on the mailing list) - stx.6.0 Weekly Build - Green - Sanity - Debian Main Branch Sanity - Last sanity email sent on Jan 11: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013747.html - Status: Green - stx-openstack Debian Main Branch Sanity - Last sanity email sent on Jan 6: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013730.html - Status: Red - LPs: - https://bugs.launchpad.net/starlingx/+bug/1999445 >> fix is in test. - https://bugs.launchpad.net/starlingx/+bug/2000168 >> lower priority. no negative functional impact - https://bugs.launchpad.net/starlingx/+bug/2000483 - https://bugs.launchpad.net/starlingx/+bug/2002113 - Need an update from the stx-openstack team. Action: Thales to provide an update in the next meeting - Gerrit Reviews in Need of Attention - From previous meetings: Fixes to libvirt env: https://review.opendev.org/c/starlingx/tools/+/863735 - Review comments provided in Nov; still waiting for author (Scott Kamp) to respond/address review comments - Jan 4: ScottK will update by EOW - Jan 11: Code review not updated by the author: ScottK - 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 - Virtual PTG planned for March / In-Person Summit/PTG planned for June - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013718.html - In-person PTG co-located with the OpenInfra Summit, June 13-15 in Vancouver Canada - https://openinfra.dev/summit/vancouver-2023 - OpenInfra Diversity & Inclusion WG is working on updating their survey (Ildiko) - The group has a D&I survey and is looking into renewing and extending it - They are looking for involvement and input from all OpenInfra projects - WG Charter: https://wiki.openstack.org/wiki/Diversity - Previous survey: https://www.surveymonkey.com/r/OpenStackDiversity - Release Status - stx.8.0 - Release Tracking Spreadsheet: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Upcoming Milestones: - Milestone-3: Jan 18 - Feature Test Complete: Jan 25 - Regression Test Start: Jan 11 - Regression Test Complete: Jan 25 - RC1 (branch creation): Feb 1 - Final Regression Complete: Feb 15 - Release: Feb 22 - Feature Status: - 27 features are Done. - 3 features are in progress - Kubernetes Custom Configuration Support - Code Merged: Jan 4 / Feature Tested: Jan 16 - Debian: Migrate Openstack app related packages - Code Merged: Dec 22 / Feature Tested: Jan 18 - Update openstack application containers to use Debian base image - Code Merged: Jan 16 / Feature Tested: Jan 23 - 6 features are continuing/deferred to stx.9.0 - Risks - stx-openstack sanity continues to be red - stx.9.0 - Release Tracking Spreadsheet created: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing - Agreed to align Milestone-1 with the March virtual PTG - end of March - Call for community members to start proposing features for stx. ARs from Previous Meetings - None Open Requests for Help - stx-openstack apply failed after enabling cpu_dedicated_setInbox - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013720.html - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013724.html - Seen w/ stx.7.0. Issue only happens when setting cpu dedicated CPUs on a running system. During the unlock, the openstack fails to re-apply. - LP: https://bugs.launchpad.net/starlingx/+bug/2002157 - Assigned to Thales - Documenting Tested Hardware by the community - Action: Scott Kamp will discuss documenting community tested hardware with the TSC From Ghada.Khalil at windriver.com Mon Jan 16 13:45:34 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 16 Jan 2023 13:45:34 +0000 Subject: [Starlingx-discuss] Heads Up: CentOS Active Branch Builds to be stopped on Jan 31 Message-ID: Hello community members, This is a heads up that StarlingX CentOS builds on the active branch will be stopped on Jan 31. As all of you are aware, stx.8.0 only supports Debian. The CentOS builds were left running to allow community members time to transition any container images which are build through the CentOS builds to the Debian builds. As we near the release date for stx.8.0, it's time to stop the CentOS builds. Please plan to migrate any container image builds that require regular builds to the Debian build by Jan 31. If there are any concerns, please respond to this thread on the mailing list. Regards, Ghada PS: This topic was discussed on the community call on Jan 11. Etherpad: https://etherpad.opendev.org/p/stx-status#L19 From scott.little at eng.windriver.com Tue Jan 17 15:49:14 2023 From: scott.little at eng.windriver.com (Scott.Little) Date: Tue, 17 Jan 2023 10:49:14 -0500 Subject: [Starlingx-discuss] Fwd: Build failed in Jenkins: STX_build_debian_master #70 In-Reply-To: <1130162962.204.1673885188518.JavaMail.javamailuser@localhost> References: <1130162962.204.1673885188518.JavaMail.javamailuser@localhost> Message-ID: The build-iso step is currently failing on CENGN with logs ... ?? 11:22:37 2023-01-15 16:22:37,186 - build-image - ERROR: ====STX patched packages checking fail: ?? 11:22:37 2023-01-15 16:22:37,186 - build-image - ERROR: mtce-guest-agent ?? 11:22:37 2023-01-15 16:22:37,186 - build-image - ERROR: mtce-guest-server ?? 11:22:37 2023-01-15 16:22:37,186 - build-image - ERROR: ====STX patched packages missing This appears to have been triggered by the merger of ... https://review.opendev.org/c/starlingx/nfv/+/869817 ...which removed mtce-guest-agent and mtce-guest-server from debian_iso_image.inc. The update looks correct to me, and other non-CENGN builds are passing.? I'm still studying what the issue might be on CENGN. I have created LaunchPad https://bugs.launchpad.net/starlingx/+bug/2003096 to track the issue. Scott -------- Forwarded Message -------- Subject: Build failed in Jenkins: STX_build_debian_master #70 Date: Mon, 16 Jan 2023 11:06:28 -0500 (EST) From: starlingx.build at gmail.com Reply-To: build.starlingx at gmail.com To: scott.little at windriver.com, davlet.panech at windriver.com 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. See ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building in workspace No emails were triggered. [STX_build_debian_master] $ /bin/sh -xe /tmp/jenkins6974239306904272200.sh ++ date --utc +%Y%m%dT%H%M%SZ + TIMESTAMP=20230116T070000Z + EMAIL_LIST=' davlet.panech at windriver.com, scott.little at windriver.com ' + cat Waiting for the completion of starlingx-jenkins-pipelines ? monolithic starlingx-jenkins-pipelines ? monolithic #221 completed. Result was FAILURE Build step 'Trigger/call builds on other projects' marked build as failure -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peng.Peng at windriver.com Tue Jan 17 22:48:58 2023 From: Peng.Peng at windriver.com (Peng, Peng) Date: Tue, 17 Jan 2023 22:48:58 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20230113T070000Z Message-ID: Sanity Test from 2023 January 17 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230113T070000Z/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: 23 (100.0%) Failed: 0 (0.0%) Total Executed: 23 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_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS test_sriovdp_netdev_connectivity_ipv4[1-1-calico-ipam] PASS test_sriovdp_netdev_connectivity_ipv6[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] Regards, PV team -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openinfra.dev Wed Jan 18 03:49:23 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Tue, 17 Jan 2023 19:49:23 -0800 Subject: [Starlingx-discuss] Open Source Summit NA - CFP is open Message-ID: Hi All, I?m reaching out to you to draw your attention to the Open Source Summit North America event, which will take place in Vancouver, BC on May 10-12. The event gathers people from around the globe with interest in open source. The event covers various tracks and provides the opportunity to discuss topics that are ranging from embedded Linux, cloud, containers all the way to community management. The event has a diverse set of attendees and would be a great opportunity to raise more awareness about the StarlingX project and reach a wide audience! The event?s CFP is currently open! __The CFP deadline is February 5 at 11:59 PM PST__. You can find more information and submit your talk here: https://events.linuxfoundation.org/open-source-summit-north-america/program/cfp/ Please let me know if I can help you putting together your session proposal! Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From sergei.akhmatov at xunison.com Thu Jan 19 10:58:47 2023 From: sergei.akhmatov at xunison.com (Sergei Akhmatov) Date: Thu, 19 Jan 2023 10:58:47 +0000 Subject: [Starlingx-discuss] STX networking question. Message-ID: Hello. I've got starlingx 7.0 duplex cluster, debiab-based installation. For now, let's say it's Kubernetes only, without openstack. According to documentation any interface could be used for access to applications running in Kubernetes. I'd prefer to keep OAM & Management networks for internal management only, on private Ips and without access from internet, and use cluster-host or cluster-services network dedicated to public applications access. My problem is: during installation the default gateway could be set up only on OAM interface and seems like it can't be changed afterwards. So, all the outbound traffic to internet will go through this interface, and that's not what I want to achieve. What's the correct way to setup networking on stx to dedicate network and interface it's attached to for access to public services deployed as Kubernetes pods from internet and route all inbound and outbound traffic through this interface? I could share some more details if needed. Any advice would be appreciated. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openinfra.dev Thu Jan 19 21:11:29 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Thu, 19 Jan 2023 13:11:29 -0800 Subject: [Starlingx-discuss] StarlingX feedback in an edge case study article Message-ID: <73BC5320-4A0D-4BB7-8E21-C8CC7CD0A8E0@openinfra.dev> Hi StarlingX Community, I cam across a case study article on LinkedIn that mentions StarlingX: https://www.linkedin.com/pulse/fairbanks-edge-cloud-case-study-michiel-manten/ The author briefly describes their evaluation process and discusses the outcome. The article is a good example to the relevance of OpenStack and virtualized services on the market: ?So, StarlingX is very interesting in case you use a container based Edge Cloud. But we needed more functionality and found this in OpenStack, which is the solution we eventually went for.? Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From Shrikumar.Sharma at windriver.com Fri Jan 20 18:47:15 2023 From: Shrikumar.Sharma at windriver.com (Sharma, Shrikumar) Date: Fri, 20 Jan 2023 18:47:15 +0000 Subject: [Starlingx-discuss] Request to review blog page In-Reply-To: References: Message-ID: Hello, all Requesting interested members here to review the github pull request at : https://github.com/StarlingXWeb/starlingx-website/pull/218 This is a blog article that I would like to contribute. Thank you and Best regards Shrikumar From Steven.Webster at windriver.com Fri Jan 20 18:52:12 2023 From: Steven.Webster at windriver.com (Webster, Steven) Date: Fri, 20 Jan 2023 18:52:12 +0000 Subject: [Starlingx-discuss] Minutes: networking sub-team meeting 01-19-23 Message-ID: ======== Next meeting: 02-02-23 Meeting logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings Agenda/Detailed minutes are posted at: https://etherpad.opendev.org/p/stx-networking ======== Feature Updates: Marvell Accelerator Support in StarlingX: https://storyboard.openstack.org/#!/story/2010047 - StarlingX build error noted in last meeting has been resolved - Some issues encountered running DPDK (testpmd) application with SR-IOV devices in container. It seems DPDK is not detecting the interface. - Still working with helm deployment, just to get an initial run on StarlingX Silicom NIC support https://storyboard.openstack.org/#!/story/2010213 - New driver versions are available from the vendor. Some of the StarlingX OS team plans to integrate with forecast of Feb. 10 Ethernet Operator Support: - Kevin and Rafal joined who are spearheading this feature, quick presentation was given about the goals of the feature - Spec is planned to be submitted to StarlingX - Steve gave some details about current SR-IOV support / configuration in StarlingX - Discussed trying to get this to land for stx 9.0 Platform network reconfig (distributed cloud) - Work ongoing, Initial reviews are merged and would allow one to use the admin network at bootstrap (no subcloud rehoming or updating). Bug Updates: One new one: https://bugs.launchpad.net/starlingx/+bug/1999690 -- Kubernetes cluster is getting IPs from "Management Network" instead of "Cluster Host Network" -------------- next part -------------- An HTML attachment was scrubbed... URL: From Juanita.Balaraj at windriver.com Fri Jan 20 22:17:23 2023 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Fri, 20 Jan 2023 22:17:23 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 18-01-23 In-Reply-To: References: Message-ID: Hello All, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Thanks, Juanita Balaraj ============ 18-Jan-23 StarlingX 8.0 Release: - https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Doc Tasks created - Doc Team to ensure Stories/Tasks are added to the commit messages - Ongoing WIP - Stx 8.0 Release Notes - AR Juanita - events.yaml - Reviewers need to refer to https://docs.starlingx.io/fault-mgmt/index-fault-98d5f50a9b8c.html to view updated alarms and log files. - Alarm updates are only supported on Master - Manual updates need to be implemented on the branches for alarms (events.yaml) since script is not supported on the branches as of date. - Doc Team to be included as part of the Gerrit review cycle for any alarm updates in the event.yaml files - To discuss details with Greg Waines / Frank Miller / Ghada (To update the Contributor Guide after discussion with the primes with the required process) Installation Guide - Restructuring of the Installation Guide is WIP and the plan is to deliver for stx 8.0?? Gerrit Reviews: - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - Merged 2 Reviews Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 5 bugs outstanding - The DOC team to create LP defects corresponding with any DS defects - WIP. Teams to add all the impacted Releases when raising a LP bug Miscellaneous Updates: - Elisa and Elaine reported tox related failures in the last 24-48 hours. To forward the gerrit URLs to Ron. - Fix Done by Ron - Backslashes to be removed from rst files wherever applicable especially in code blocks, for example, \(code\_remove\) - To be cleaned up in rst files as the files are being updated for any doc Gerrit reviews. - Numbering in the Distributed Cloud Guide is causing issues - AR Ron to check - WIP General Updates: -Since Stx 5.0 is EOL, we continue to Cherry Pick to the stx 5.0 branch -Retain TOC with Stx 5.0 included as EOL. Hide Stx 5.0 from the Master Index upstream with a link to the Stx 5.0 Archived page - AR Ron -Sphinx Tools - Need to have further discussions about the version used upstream vs. downstream - AR Ron - Operations Guide Archive - On Hold until further clarifications are discussed with Greg (https://review.opendev.org/c/starlingx/docs/+/822030) ____________________ 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 Ghada.Khalil at windriver.com Sat Jan 21 01:21:38 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sat, 21 Jan 2023 01:21:38 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Jan 18/2023 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Jan 18 2023 stx.8.0 - Reference Links: - Release/Feature Planning: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Release Verification: - Folder: https://drive.google.com/drive/folders/1E_AQPxVrNnbVtSqQ9_CdqYidqMmYcq4n - Feature Testing: https://docs.google.com/spreadsheets/d/1yzlArypq3sgdNdYzMwBONLnOsx6OqMpxj6KT0P6Pc6M/edit#gid=968103774 - Regression Testing: https://docs.google.com/spreadsheets/d/1b5w2oLlGwipTlrNysWwl1JnM1dvyboIIQhpBJLcZECI/edit#gid=1717644237 - Feature Status - 28 features are Done. - 2 features still in progress -- related to stx-openstack - Debian: Migrate Openstack app related packages - Feature code is complete. Working LPs reported from sanity. - Targeting fixes to be merged Jan 18 and run another sanity before EOW. - Update openstack application containers to use Debian base image - 12 of 17 images are ported to Debian. Likley need another week to complete the others. - Note: Debian images are not running as part of sanity yet. The last sanity on Jan 13 only used 2 Debian images out of 17 total. - Test Status - Automated regression run has not started yet on stx. But team expects to be able to meet the completion date of Jan 25. - The plan is to run regression on SX & DX. TBD whether regression will be run on std as well. - Bugs - stx.8.0: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.8.0 - Need each team to review and update as needed - stx.8.0 Release Decisions - Criteria to create the release branch -- week of Feb 1 - Automated regression is complete and no gating - Openstack yellow sanity w/ Debian images (preferred, but can have mix/match) - Failure results are analysed and deemed as acceptable limitations - Release Notes - No update; Juanita did not attend stx.7.0 - Blogs - PTP Enhancements - Multiple NIC Support / SyncE / Various NIC Support - Prime: Ghada Khalil - Forecast: mid-Sept >> end-Oct >> mid-Dec >> end-Jan / Author: Cole Walker - Status: Not Started. Targeting start in mid-Jan. - Subcloud Local Install - Prime: RamS - Forecast: end-Nov >> mid-Jan / Author: Shrikumar Sharma - Status: PR posted. https://github.com/StarlingXWeb/starlingx-website/pull/218 stx.9.0 - New release folder created: https://drive.google.com/drive/folders/1beMET3I7GGa79tv4wfwzeKTy-yFVl6xR?usp=share_link - New Release/Feature Planning: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing - Populated with deferred features from stx.8.0 From Ghada.Khalil at windriver.com Sat Jan 21 01:34:07 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sat, 21 Jan 2023 01:34:07 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Jan 18, 2023) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call January 18, 2023 Standing topics - Build - Main Branch Debian Builds - Green - Had 2 failures on Jan 15 & 16 due to recent packaging changes introduced in stx. This has been corrected. - Main Branch CentOS Builds - Green - LP from last week is addressed : https://bugs.launchpad.net/starlingx/+bug/2002423 - Stopping CentOS Builds - Email sent to the mailing list on Jan 16: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013758.html - No concerns raised by the community yet; will monitor until next week - Forecast: Dec 14 >> Jan 31 (tentative; pending feedback from the larger community on the mailing list) - stx.6.0 Weekly Build - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/ - stx.7.0 Weekly Build - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/ - Sanity - Debian Main Branch Sanity - Last sanity email sent on Jan 17: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013760.html - Status: Green for both SX & DX - stx-openstack Debian Main Branch Sanity - Last sanity email sent on Jan 13: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013756.html - Status: Yellow - Team is working on a number of LPs. Targeting fixes to be merged Jan 18 and run another sanity before EOW. - LPs: - https://bugs.launchpad.net/starlingx/+bug/1999445 - https://bugs.launchpad.net/starlingx/+bug/2000168 - https://bugs.launchpad.net/starlingx/+bug/2000483 - https://bugs.launchpad.net/starlingx/+bug/2002113 - Gerrit Reviews in Need of Attention - From previous meetings: Fixes to libvirt env: https://review.opendev.org/c/starlingx/tools/+/863735 - Review comments provided in Nov; still waiting for author (Scott Kamp) to respond/address review comments - Jan 4: ScottK will update by EOW - Jan 11: Code review not updated by the author: ScottK - Jan 18: Some activity in the review as of Jan 15 - 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 - Release Status - stx.8.0 - Release Tracking Spreadsheet: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Upcoming Milestones: - Milestone-3: Jan 18 >> Jan 25 - openstack image migration to Debian is still in progress - Feature Test Complete: Jan 25 >> Jan 31 - Regression Test Complete: Jan 25 - on track - RC1 (branch creation): Feb 1 - hope to keep this date for branch creation; dependent on (1) regression results, (2) openstack sanity results - Final Regression Complete: Feb 15 - Release: Feb 22 - Feature Status: - 28 features are Done. - 2 features are in progress - Debian: Migrate Openstack app related packages - Code Merged: Dec 22 / Feature Tested: Jan 18 - Update openstack application containers to use Debian base image - Code Merged: Jan 16 >> Jan 25 / Feature Tested: Jan 23 >> Jan 31 - 6 features are continuing/deferred to stx.9.0 - Release Notes - Hope to start next week - Bugs - stx.8.0: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.8.0 - Need each team to review and update as needed - Risks - stx-openstack sanity status - stx.9.0 - No update from the last meeting. Would like to have the majority of features proposed by the March virtual PTG - Release Tracking Spreadsheet created: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing - Call for community members to start proposing features for stx. ARs from Previous Meetings - None Open Requests for Help - stx-openstack apply failed after enabling cpu_dedicated_setInbox - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013720.html - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013724.html - Seen w/ stx.7.0. Issue only happens when setting cpu dedicated CPUs on a running system. During the unlock, the openstack fails to re-apply. - LP: https://bugs.launchpad.net/starlingx/+bug/2002157 - Assigned to Thales; not investigated yet; team focused on stx.8.0 and openstack sanity - Documenting Tested Hardware by the community - Action: Scott Kamp will discuss documenting community tested hardware with the TSC From ildiko at openinfra.dev Mon Jan 23 18:42:59 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Mon, 23 Jan 2023 19:42:59 +0100 Subject: [Starlingx-discuss] Hands-on workshop at the OpenInfra Summit Message-ID: Hi StarlingX Community, On last week?s Community Call the idea came up to run the StarlingX Hands-on workshop at the upcoming OpenInfra Summit again. Background: community members used to run a hands-on workshop at OpenInfra Summits and other in-person events to show people how to deploy the platform and get started with the UI. The attendees really liked and appreciated these sessions. The goal of running the workshop again is to raise awareness of the project and help people with getting started with StarlingX. I checked and we have a room where the community could reserve a ~2-hour slot. We can update the content of the workshop to provide the best experience to attendees to learn more about and get more comfortable with the latest version of the platform. The past workshops were running on Equinix HW that was donated to the community by the company. While that infrastructure is currently not available, their offer to provide the community with HW for purposes like this still stands. I will reach out to them once the community confirms to run the workshop in vancouver. What do you all think? Who would be interested in helping out with building and running the workshop? @Greg: Can you provide information about HW needs? Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From starlingx.build at gmail.com Wed Jan 25 00:59:21 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 24 Jan 2023 19:59:21 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 3584 - Failure! Message-ID: <1023624852.242.1674608363749.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 3584 Status: Failure Timestamp: 20230125T005129Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230125T000819Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20230125T000819Z DOCKER_BUILD_ID: jenkins-master-flock-20230125T000819Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230125T000819Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20230125T000819Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From starlingx.build at gmail.com Wed Jan 25 00:59:25 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 24 Jan 2023 19:59:25 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 1077 - Failure! Message-ID: <1627647605.245.1674608366808.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 1077 Status: Failure Timestamp: 20230125T000819Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230125T000819Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From ildiko at openinfra.dev Wed Jan 25 09:25:58 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Wed, 25 Jan 2023 10:25:58 +0100 Subject: [Starlingx-discuss] OpenInfra Live StarlingX episode idea Message-ID: <4D79A887-3DE0-4431-ABC2-2852564E2A56@openinfra.dev> Hi StarlingX community, With the OpenInfra Foundation team we are always looking for opportunities to showcase our projects and the work that our communities are doing. I?m reaching out to you with an OpenInfra Live episode idea that we came up with for the OpenInfra projects. We would like to do a series to talk about the origin of our projects. Each project would program their own episode to show how the project got started and it would also allow for showing the community?s journey since the project?s launch, which gives some room to come up with topics to fill a full episode. As the StarlingX project is celebrating its 5th year anniversary this year, this could be a great way to start the recognition of that milestone as well! What do you think? Who from the community would be interested in participating? Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From Greg.Waines at windriver.com Wed Jan 25 14:15:26 2023 From: Greg.Waines at windriver.com (Waines, Greg) Date: Wed, 25 Jan 2023 14:15:26 +0000 Subject: [Starlingx-discuss] Hands-on workshop at the OpenInfra Summit In-Reply-To: References: Message-ID: @Greg: Can you provide information about HW needs? I would think we would only do virtual AIO-SX setups. I would use the following as a guide: https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_duplex_environ.html#physical-host-requirements-and-setup Summary: // I increased a little Hardware requirements? The host system should have at least: - Processor: x86_64 only supported architecture with BIOS enabled hardware virtualization extensions - Cores: 16 - Memory: 64GB RAM - Hard Disk: 1TB HDD - Network: One network adapter with active Internet connection Software requirements? The host system should have at least: - A workstation computer with Ubuntu 16.04 LTS 64-bit All other required packages will be installed by scripts in the StarlingX tools repository. Greg. -----Original Message----- From: Ildiko Vancsa Sent: Monday, January 23, 2023 1:43 PM To: StarlingX ML Subject: [Starlingx-discuss] Hands-on workshop at the OpenInfra Summit 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 StarlingX Community, On last week?s Community Call the idea came up to run the StarlingX Hands-on workshop at the upcoming OpenInfra Summit again. Background: community members used to run a hands-on workshop at OpenInfra Summits and other in-person events to show people how to deploy the platform and get started with the UI. The attendees really liked and appreciated these sessions. The goal of running the workshop again is to raise awareness of the project and help people with getting started with StarlingX. I checked and we have a room where the community could reserve a ~2-hour slot. We can update the content of the workshop to provide the best experience to attendees to learn more about and get more comfortable with the latest version of the platform. The past workshops were running on Equinix HW that was donated to the community by the company. While that infrastructure is currently not available, their offer to provide the community with HW for purposes like this still stands. I will reach out to them once the community confirms to run the workshop in vancouver. What do you all think? Who would be interested in helping out with building and running the workshop? @Greg: Can you provide information about HW needs? Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io From Peng.Peng at windriver.com Wed Jan 25 14:18:27 2023 From: Peng.Peng at windriver.com (Peng, Peng) Date: Wed, 25 Jan 2023 14:18:27 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20230122T070000Z Message-ID: Sanity Test from 2023 January 17 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230122T070000Z/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: 23 (100.0%) Failed: 0 (0.0%) Total Executed: 23 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_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS test_sriovdp_netdev_connectivity_ipv4[1-1-calico-ipam] PASS test_sriovdp_netdev_connectivity_ipv6[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] Regards, PV team -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openinfra.dev Wed Jan 25 14:33:48 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Wed, 25 Jan 2023 15:33:48 +0100 Subject: [Starlingx-discuss] Hands-on workshop at the OpenInfra Summit In-Reply-To: References: Message-ID: Hi Greg, Great, thank you! Would the workshop need one machine or multiple servers? Thanks, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Jan 25, 2023, at 15:15, Waines, Greg wrote: > > @Greg: Can you provide information about HW needs? > > I would think we would only do virtual AIO-SX setups. > I would use the following as a guide: https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_duplex_environ.html#physical-host-requirements-and-setup > > Summary: // I increased a little > Hardware requirements? > The host system should have at least: > - Processor: x86_64 only supported architecture with BIOS enabled hardware virtualization extensions > - Cores: 16 > - Memory: 64GB RAM > - Hard Disk: 1TB HDD > - Network: One network adapter with active Internet connection > > Software requirements? > The host system should have at least: > - A workstation computer with Ubuntu 16.04 LTS 64-bit > All other required packages will be installed by scripts in the StarlingX tools repository. > > Greg. > > -----Original Message----- > From: Ildiko Vancsa > Sent: Monday, January 23, 2023 1:43 PM > To: StarlingX ML > Subject: [Starlingx-discuss] Hands-on workshop at the OpenInfra Summit > > 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 StarlingX Community, > > On last week?s Community Call the idea came up to run the StarlingX Hands-on workshop at the upcoming OpenInfra Summit again. > > Background: community members used to run a hands-on workshop at OpenInfra Summits and other in-person events to show people how to deploy the platform and get started with the UI. The attendees really liked and appreciated these sessions. > > The goal of running the workshop again is to raise awareness of the project and help people with getting started with StarlingX. > > > I checked and we have a room where the community could reserve a ~2-hour slot. We can update the content of the workshop to provide the best experience to attendees to learn more about and get more comfortable with the latest version of the platform. > > The past workshops were running on Equinix HW that was donated to the community by the company. While that infrastructure is currently not available, their offer to provide the community with HW for purposes like this still stands. I will reach out to them once the community confirms to run the workshop in vancouver. > > > What do you all think? Who would be interested in helping out with building and running the workshop? > > @Greg: Can you provide information about HW needs? > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From Lucas.DeAtaidesBarreto at windriver.com Wed Jan 25 14:39:41 2023 From: Lucas.DeAtaidesBarreto at windriver.com (De Ataides Barreto, Lucas) Date: Wed, 25 Jan 2023 14:39:41 +0000 Subject: [Starlingx-discuss] Sanity - StarlingX + STX-Openstack MASTER build ISO [CUSTOM] results - Jan-25 Message-ID: Hi all, Here are the results for StarlingX + STX-Openstack using the Jan-12 build: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230120T070000Z/outputs/iso/starlingx-intel-x86-64-20230120162312-cd.iso + https://review.opendev.org/c/starlingx/nfv/+/870538 and Helm-Charts: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230111T070000Z/outputs/helm-charts/stx-openstack-1.0-1.stx.4-debian-stable-versioned.tgz + STX-Debian based images from https://review.opendev.org/q/topic:stx-openstack-debian-images Why custom ISO and Helm charts? Since Jan-12, the Helm Charts for STX-Openstack were not being built due to https://bugs.launchpad.net/starlingx/+bug/2003261. The STX-Openstack Distro team has been actively working on closing launchpads and making changes to the code. Since we don't have official Helm-Charts for this week, we decided to run a sanity with the latest improvements that the team has made, and that are opened for review, or already merged. The 20230124T070000Z build already has STX-Openstack Helm-Charts, but the team needed fixes to the ISO which were still not merged, and neither were the STX-Debian based images. Overall Sanity Results: YELLOW AIO-DX Baremetal with VSWITCH_TYPE=ovs Sanity Status: YELLOW Automated Test Results Summary: ------------------------------------------------------ Passed: 11 (73.33%) Failed: 4 (26.66%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS 20230124 00:48:39 test_ssh_to_hosts PASS 20230124 00:50:14 test_lock_unlock_host* PASS 20230124 01:09:32 test_openstack_services_healthy PASS 20230124 01:10:57 test_reapply_stx_openstack_no_change[controller-0] PASS 20230124 01:13:29 test_reapply_stx_openstack_no_change[controller-1] PASS 20230124 01:18:31 test_horizon_create_delete_instance PASS 20230124 01:21:24 test_swact_controllers PASS 20230124 01:29:16 test_ping_between_two_vms[tis-centos-guest-virtio-virtio] FAIL 20230124 01:36:01 test_migrate_vm[tis-centos-guest-live-None] FAIL 20230124 01:40:32 test_nova_actions[tis-centos-guest-dedicated-pause-unpause] FAIL 20230124 01:44:35 test_nova_actions[tis-centos-guest-dedicated-suspend-resume] FAIL 20230124 01:48:40 test_evacuate_vms PASS 20230124 19:29:36 test_system_coredumps_and_crashes[core_dumps] PASS 20230124 19:29:51 test_system_coredumps_and_crashes[crash_reports] PASS 20230124 19:29:58 test_system_alarms ----------------------------------------------------------------------- All the failed tests are related to this launchpad: * https://bugs.launchpad.net/starlingx/+bug/2003813 * *: https://bugs.launchpad.net/starlingx/+bug/2000483 (Waiting for code review) Thanks, STX-Openstack Distro Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Wed Jan 25 14:45:50 2023 From: Greg.Waines at windriver.com (Waines, Greg) Date: Wed, 25 Jan 2023 14:45:50 +0000 Subject: [Starlingx-discuss] Hands-on workshop at the OpenInfra Summit In-Reply-To: References: Message-ID: In the previous workshop, We used one machine per person ... and they had that machine to do a virtual install. So maybe if we planned for 50 people max ... we could reserve 50 servers from Equinix. Greg. -----Original Message----- From: Ildiko Vancsa Sent: Wednesday, January 25, 2023 9:34 AM To: Waines, Greg Cc: StarlingX ML Subject: Re: [Starlingx-discuss] Hands-on workshop at the OpenInfra Summit 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 Greg, Great, thank you! Would the workshop need one machine or multiple servers? Thanks, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Jan 25, 2023, at 15:15, Waines, Greg wrote: > > @Greg: Can you provide information about HW needs? > > I would think we would only do virtual AIO-SX setups. > I would use the following as a guide: https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_duplex_environ.html#physical-host-requirements-and-setup > > Summary: // I increased a little > Hardware requirements? > The host system should have at least: > - Processor: x86_64 only supported architecture with BIOS enabled hardware virtualization extensions > - Cores: 16 > - Memory: 64GB RAM > - Hard Disk: 1TB HDD > - Network: One network adapter with active Internet connection > > Software requirements? > The host system should have at least: > - A workstation computer with Ubuntu 16.04 LTS 64-bit > All other required packages will be installed by scripts in the StarlingX tools repository. > > Greg. > > -----Original Message----- > From: Ildiko Vancsa > Sent: Monday, January 23, 2023 1:43 PM > To: StarlingX ML > Subject: [Starlingx-discuss] Hands-on workshop at the OpenInfra Summit > > 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 StarlingX Community, > > On last week?s Community Call the idea came up to run the StarlingX Hands-on workshop at the upcoming OpenInfra Summit again. > > Background: community members used to run a hands-on workshop at OpenInfra Summits and other in-person events to show people how to deploy the platform and get started with the UI. The attendees really liked and appreciated these sessions. > > The goal of running the workshop again is to raise awareness of the project and help people with getting started with StarlingX. > > > I checked and we have a room where the community could reserve a ~2-hour slot. We can update the content of the workshop to provide the best experience to attendees to learn more about and get more comfortable with the latest version of the platform. > > The past workshops were running on Equinix HW that was donated to the community by the company. While that infrastructure is currently not available, their offer to provide the community with HW for purposes like this still stands. I will reach out to them once the community confirms to run the workshop in vancouver. > > > What do you all think? Who would be interested in helping out with building and running the workshop? > > @Greg: Can you provide information about HW needs? > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From ildiko at openinfra.dev Wed Jan 25 14:48:20 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Wed, 25 Jan 2023 15:48:20 +0100 Subject: [Starlingx-discuss] Hands-on workshop at the OpenInfra Summit In-Reply-To: References: Message-ID: <6F42DC9D-E2D7-40D7-85F6-E3119A4DCB6A@openinfra.dev> Hi Greg, Noted, thank you. I will reach out to my contact at Equinix and check what they have available. I will copy you as well in case they have follow up questions. Thanks, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Jan 25, 2023, at 15:45, Waines, Greg wrote: > > In the previous workshop, > We used one machine per person ... and they had that machine to do a virtual install. > So maybe if we planned for 50 people max ... we could reserve 50 servers from Equinix. > Greg. > > -----Original Message----- > From: Ildiko Vancsa > Sent: Wednesday, January 25, 2023 9:34 AM > To: Waines, Greg > Cc: StarlingX ML > Subject: Re: [Starlingx-discuss] Hands-on workshop at the OpenInfra Summit > > 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 Greg, > > Great, thank you! > > Would the workshop need one machine or multiple servers? > > Thanks, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > > >> On Jan 25, 2023, at 15:15, Waines, Greg wrote: >> >> @Greg: Can you provide information about HW needs? >> >> I would think we would only do virtual AIO-SX setups. >> I would use the following as a guide: https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_duplex_environ.html#physical-host-requirements-and-setup >> >> Summary: // I increased a little >> Hardware requirements? >> The host system should have at least: >> - Processor: x86_64 only supported architecture with BIOS enabled hardware virtualization extensions >> - Cores: 16 >> - Memory: 64GB RAM >> - Hard Disk: 1TB HDD >> - Network: One network adapter with active Internet connection >> >> Software requirements? >> The host system should have at least: >> - A workstation computer with Ubuntu 16.04 LTS 64-bit >> All other required packages will be installed by scripts in the StarlingX tools repository. >> >> Greg. >> >> -----Original Message----- >> From: Ildiko Vancsa >> Sent: Monday, January 23, 2023 1:43 PM >> To: StarlingX ML >> Subject: [Starlingx-discuss] Hands-on workshop at the OpenInfra Summit >> >> 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 StarlingX Community, >> >> On last week?s Community Call the idea came up to run the StarlingX Hands-on workshop at the upcoming OpenInfra Summit again. >> >> Background: community members used to run a hands-on workshop at OpenInfra Summits and other in-person events to show people how to deploy the platform and get started with the UI. The attendees really liked and appreciated these sessions. >> >> The goal of running the workshop again is to raise awareness of the project and help people with getting started with StarlingX. >> >> >> I checked and we have a room where the community could reserve a ~2-hour slot. We can update the content of the workshop to provide the best experience to attendees to learn more about and get more comfortable with the latest version of the platform. >> >> The past workshops were running on Equinix HW that was donated to the community by the company. While that infrastructure is currently not available, their offer to provide the community with HW for purposes like this still stands. I will reach out to them once the community confirms to run the workshop in vancouver. >> >> >> What do you all think? Who would be interested in helping out with building and running the workshop? >> >> @Greg: Can you provide information about HW needs? >> >> Thanks and Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem >> Open Infrastructure Foundation >> >> >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > From scott.little at windriver.com Wed Jan 25 15:58:04 2023 From: scott.little at windriver.com (Scott Little) Date: Wed, 25 Jan 2023 10:58:04 -0500 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 1077 - Failure! In-Reply-To: <1627647605.245.1674608366808.JavaMail.javamailuser@localhost> References: <1627647605.245.1674608366808.JavaMail.javamailuser@localhost> Message-ID: <23c2d4f5-4e81-1cb8-9a07-fe599a881058@windriver.com> Looks like someone tried to upgrade portieris, but missed something on the Centos packaging side. Debian is ok. Probable cause is update: https://review.opendev.org/c/starlingx/portieris-armada-app/+/868494 Opened LaunchPad: https://bugs.launchpad.net/starlingx/+bug/2003883 Scott On 2023-01-24 19:59, starlingx.build at gmail.com 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. > > Project: STX_build_layer_flock_master_master > Build #: 1077 > Status: Failure > Timestamp: 20230125T000819Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20230125T000819Z/logs > -------------------------------------------------------------------------------- > Parameters > > FULL_BUILD: false > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Fri Jan 27 01:42:59 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 27 Jan 2023 01:42:59 +0000 Subject: [Starlingx-discuss] New registries: registry.k8s.io & icr.io and associated images Message-ID: Hello all, Recent commits introduced support for two new registries: - registry.k8s.io: This is required for the k8s-security-profiles-operator (SPO) containerized app being introduced in stx.9.0 Story: https://storyboard.openstack.org/#!/story/2010310 Review for new registry: https://review.opendev.org/q/topic:registry-k8s-io New images: - registry.k8s.io/security-profiles-operator/security-profiles-operator:v0.6.0 - gcr.io/kubebuilder/kube-rbac-proxy:v0.13.1 - icr.io: This is required for the portieris fluxcd app being upversioned in stx.9.0 Story: https://storyboard.openstack.org/#!/story/2010394 Review adding the new registry: https://review.opendev.org/q/topic:icr-io New images: - icr.io/portieris/portieris:v0.13.1 Neither registry is required for bootstrapping the system, so if you have no plan to use the above optional applications, this should not affect you. If you have interest in these applications and use a private registry, please populate it accordingly. Regards, Ghada From Ghada.Khalil at windriver.com Fri Jan 27 02:20:49 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 27 Jan 2023 02:20:49 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Jan 25, 2023) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call January 25, 2023 Standing topics - Build - Main Branch Debian Builds - ISO Green all week - Container builds were skipped due to https://bugs.launchpad.net/starlingx/+bug/2003261 - This has been addressed as of Jan 23 and the builds were successful on Jan 24. - Main Branch CentOS Builds - ISO failed yesterday due to a recent code submission related to a portieris package upversion; Scott investigating. - Stopping CentOS Builds - Email sent to the mailing list on Jan 16: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013758.html - No concerns raised by the community on the mailing list or during the meeting today - stx-openstack team appears to be on track to finish their image migration by Jan 27 - Forecast: Dec 14 >> Jan 31 (tentative; pending feedback from the larger community on the mailing list) - stx.6.0 Weekly Build - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/ - stx.7.0 Weekly Build - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/ - Sanity - Debian Main Branch Sanity - Last sanity email sent on Jan 25: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013774.html - Status: Green for both SX & DX - stx-openstack Debian Main Branch Sanity - Last sanity email sent on Jan 25: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013776.html - Status: Yellow - Custom builds of Debian images used due to issues building container images due to LP: https://bugs.launchpad.net/starlingx/+bug/2003261 - Fixed as of Jan 23 - Expect to be able to run next week's sanity using the regular Debian builds - LPs: - https://bugs.launchpad.net/starlingx/+bug/1999445 - Fixed as of Jan 24 - https://bugs.launchpad.net/starlingx/+bug/2000168 - Fixed as of Jan 16 - https://bugs.launchpad.net/starlingx/+bug/2000483 - Fix in progress - https://bugs.launchpad.net/starlingx/+bug/2003813 - New / Under investigation - https://bugs.launchpad.net/starlingx/+bug/2002113 - Not Gating stx.8.0 - Gerrit Reviews in Need of Attention - stx-openstack Debian image migration: https://review.opendev.org/q/topic:stx-openstack-debian-images - Need attention from core reviewers as this is required for the stx.8.0 release declaration - Repos: openstack-armada-app, root, upstream, nfv - From previous meetings: Fixes to libvirt env: https://review.opendev.org/c/starlingx/tools/+/863735 - Review comments provided in Nov; still waiting for author (Scott Kamp) to respond/address review comments - Jan 4: ScottK will update by EOW - Jan 11: Code review not updated by the author: ScottK - Jan 18: Some activity in the review as of Jan 15 - 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 - Release Status - stx.8.0 - Release Tracking Spreadsheet: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Upcoming Milestones: - Milestone-3: Jan 18 >> Jan 25 >> Jan 27 - openstack image migration to Debian is still in progress - Feature Test Complete: Jan 25 >> Jan 31 - Regression Test Complete: Jan 25 - No update as Rob (Test PL) did not attend - RC1 (branch creation): Feb 1 - Hope to keep this date for branch creation; dependent on (1) regression results, (2) openstack sanity results - Will evaluate the status on Feb 1 in the release meeting - Final Regression Complete: Feb 15 - Release: Feb 22 - Feature Status: - 28 features are Done. - 2 features are in progress - Debian: Migrate Openstack app related packages - Code Merged: Dec 22 / Feature Tested: Jan 18 - Testing Complete - New LP: https://bugs.launchpad.net/starlingx/+bug/2003813 needs to be resolved for stx.8.0 - Update openstack application containers to use Debian base image - Code Merged: Jan 16 >> Jan 25 >> Jan 27 / Feature Tested: Jan 23 >> Jan 31 - All 18 images were ported to Debian and internal testing looks good. - Reviews still need to merge: https://review.opendev.org/q/topic:stx-openstack-debian-images - New LP: https://bugs.launchpad.net/starlingx/+bug/2003813 may require more time beyond Jan 31 - Bugs - stx.8.0: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.8.0 - 5 in total / 2 CVEs / 2 stx-openstack / 1 docs - Release Notes - Plan to start the week of Jan 30 - Risks - stx-openstack sanity / feature status - stx.9.0 - No new feature proposals added to the tracking spreadsheet. Call for community members to start proposing features for stx. - Would like to have the majority of features proposed by the March virtual PTG - Release Tracking Spreadsheet created: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing - New contributor introduction - Rajesh - Based in the Netherlands - Reached out to Ildiko for some introductory material - Interested in contributing to the k8s/container area - https://docs.starlingx.io/ is a good starting point. Also emails to the stx mailing list. ARs from Previous Meetings - None Open Requests for Help - stx-openstack apply failed after enabling cpu_dedicated_setInbox - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013720.html - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013724.html - Seen w/ stx.7.0. Issue only happens when setting cpu dedicated CPUs on a running system. During the unlock, the openstack fails to re-apply. - LP: https://bugs.launchpad.net/starlingx/+bug/2002157 - Assigned to Thales; not investigated yet; team focused on stx.8.0 and openstack sanity. - Reached out to reporter, so they have a view of the status. They're fine to wait until the team has bandwidth - Documenting Tested Hardware by the community - Action: Scott Kamp will discuss documenting community tested hardware with the TSC From Juanita.Balaraj at windriver.com Fri Jan 27 22:24:41 2023 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Fri, 27 Jan 2023 22:24:41 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 25-01-23 In-Reply-To: References: Message-ID: Hello All, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Thanks, Juanita Balaraj ============ 25-Jan-23 Stx 8.0. - February 22nd StarlingX 8.0 Release: - https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit#gid=1107209846 - Doc Tasks created - Doc Team to ensure Stories/Tasks are added to the commit messages - Ongoing WIP - Stx 8.0 Release Notes - AR Juanita - events.yaml - Reviewers need to refer to https://docs.starlingx.io/fault-mgmt/index-fault-98d5f50a9b8c.html to view updated alarms and log files. - Alarm updates are only supported on Master - Manual updates need to be implemented on the branches for alarms (events.yaml) since script is not supported on the branches as of date. - Doc Team to be included as part of the Gerrit review cycle for any alarm updates in the event.yaml files - To discuss details with Greg Waines / Frank Miller / Ghada (To update the Contributor Guide after discussion with the primes with the required process) Installation Guide - Restructuring of the Installation Guide is WIP and the plan is to deliver for stx 8.0?? Gerrit Reviews: - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - Merged 8 Reviews Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 6 bugs outstanding - The DOC team to create LP defects corresponding with any DS defects - WIP. Teams to add all the impacted Releases when raising a LP bug Miscellaneous Updates: - Backslashes to be removed from rst files wherever applicable especially in code blocks, for example, \(code\_remove\) - To be cleaned up in rst files as the files are being updated for any doc Gerrit reviews. - Numbering in the Distributed Cloud Guide is causing issues - AR Ron to check - WIP General Updates: - Since Stx 5.0 is EOL, we continue to Cherry Pick to the stx 5.0 branch Retain TOC with Stx 5.0 included as EOL. Hide Stx 5.0 from the Master Index upstream with a link to the Stx 5.0 Archived page - AR Ron - Sphinx Tools - Need to have further discussions about the version used upstream vs. downstream - AR Ron - Reviews for Install directory structure for Stx 6.0 / Stx 7.0 - AR Ron - Operations Guide Archive - On Hold until further clarifications are discussed with Greg (https://review.opendev.org/c/starlingx/docs/+/822030) ____________________ 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 starlingx.build at gmail.com Tue Jan 31 07:34:48 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 31 Jan 2023 02:34:48 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 692 - Failure! Message-ID: <1584954320.278.1675150492323.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 692 Status: Failure Timestamp: 20230131T034652Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20230131T021511Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20230131T021511Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20230131T021511Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20230131T021511Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20230131T021511Z/logs PUBLISH_TIMESTAMP: 20230131T021511Z FLOCK_VERSION: master-centos-stable-20230131T021511Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20230131T021511Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20230131T021511Z/outputs REGISTRY: docker.io From starlingx.build at gmail.com Tue Jan 31 07:34:54 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 31 Jan 2023 02:34:54 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 448 - Failure! Message-ID: <59631182.281.1675150495728.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 448 Status: Failure Timestamp: 20230131T031408Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20230131T021511Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20230131T021511Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20230131T021511Z/logs MASTER_BUILD_NUMBER: 432 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20230131T021511Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20230131T021511Z DOCKER_BUILD_ID: jenkins-master-containers-20230131T021511Z-builder TIMESTAMP: 20230131T021511Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20230131T021511Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20230131T021511Z/outputs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm-fluxcd From starlingx.build at gmail.com Tue Jan 31 07:34:58 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 31 Jan 2023 02:34:58 -0500 (EST) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 432 - Failure! Message-ID: <1591063131.284.1675150498938.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 432 Status: Failure Timestamp: 20230131T021511Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20230131T021511Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From ildiko at openinfra.dev Tue Jan 31 12:20:24 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Tue, 31 Jan 2023 13:20:24 +0100 Subject: [Starlingx-discuss] New StarlingX blog post Message-ID: Hi StarlingX Community, I?m reaching out to you to draw your attention to the new blog post on the StarlingX blog! The article describes the local installation feature in the platform, to show why it is needed and in what scenarios it can be utilized. You can read the article here: https://www.starlingx.io/blog/starlingx-subcloud-local-install/ Thank you to Shrikumar Sharma for submitting the article! If you have a topic that you would like to share in the form of a blog post, you can find the steps to submit your piece here: https://docs.starlingx.io/contributor/blog_contribute_guide.html Please let me know if you have any questions or need help with the above process. Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From Peng.Peng at windriver.com Tue Jan 31 15:56:38 2023 From: Peng.Peng at windriver.com (Peng, Peng) Date: Tue, 31 Jan 2023 15:56:38 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20230125T070000Z Message-ID: Sanity Test from 2023 January 30 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230125T070000Z/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: 23 (100.0%) Failed: 0 (0.0%) Total Executed: 23 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_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS test_sriovdp_netdev_connectivity_ipv4[1-1-calico-ipam] PASS test_sriovdp_netdev_connectivity_ipv6[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] Regards, PV team -------------- next part -------------- An HTML attachment was scrubbed... URL: