April 2023 - Starlingx-discuss - lists.starlingx.io

[Starlingx-discuss] [build-report] master STX_build_debian_master - Build # 152 - Still Failing!
by starlingx.build＠gmail.com 24 Apr '23

24 Apr '23

Project: STX_build_debian_master Build #: 152 Status: Still Failing Timestamp: 20230423T060000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/… -------------------------------------------------------------------------------- Parameters BUILD_PACKAGES_LIST: CLEAN_DOWNLOADS: false BUILD_HELM_CHARTS: true USE_DOCKER_CACHE: true DOCKER_IMAGE_LIST: PUSH_DOCKER_IMAGES: true CLEAN_DOCKER: true REFRESH_SOURCE: true DRY_RUN: false CLEAN_PACKAGES: true BUILD_RT: true BUILD_PACKAGES: true CLEAN_REPOMGR: true PKG_REUSE: false JENKINS_SCRIPTS_BRANCH: master BUILD_DOCKER_BASE_IMAGE: true BUILD_DOCKER_IMAGES: true FORCE_BUILD: false REBUILD_BUILDER_IMAGES: true CLEAN_ISO: true BUILD_ISO: true

1 0

[Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_containers - Build # 35 - Failure!
by starlingx.build＠gmail.com 23 Apr '23

23 Apr '23

Project: STX_7.0_build_layer_containers Build #: 35 Status: Failure Timestamp: 20230423T053318Z Branch: r/stx.7.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/containers/… -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true

1 0

[Starlingx-discuss] [stable] [build-report] r/stx.7.0 STX_build_docker_images_layered - Build # 465 - Failure!
by starlingx.build＠gmail.com 23 Apr '23

23 Apr '23

Project: STX_build_docker_images_layered Build #: 465 Status: Failure Timestamp: 20230423T054808Z Branch: r/stx.7.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/containers/… -------------------------------------------------------------------------------- Parameters BRANCH: r/stx.7.0 MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-7.0-containers/20230423T053318Z OS: centos MUNGED_BRANCH: rc-7.0 MY_REPO: /localdisk/designer/jenkins/rc-7.0-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/containers/… MASTER_BUILD_NUMBER: 35 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/7.0/centos/containers/20230423T053318Z/logs MASTER_JOB_NAME: STX_7.0_build_layer_containers MY_REPO_ROOT: /localdisk/designer/jenkins/rc-7.0-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/7.0/centos/containers PUBLISH_TIMESTAMP: 20230423T053318Z DOCKER_BUILD_ID: jenkins-rc-7.0-containers-20230423T053318Z-builder TIMESTAMP: 20230423T053318Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/rc/7.0/centos/containers/20230423T053318Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/7.0/centos/containers/20230423T053318Z/outputs MAIN_HELM_CHART_RPM_NAME: stx-openstack-helm

1 0

[Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 709 - Failure!
by starlingx.build＠gmail.com 23 Apr '23

23 Apr '23

Project: STX_build_docker_flock_images Build #: 709 Status: Failure Timestamp: 20230423T061724Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/containers/… -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-7.0-containers/20230423T053318Z OS: centos MY_REPO: /localdisk/designer/jenkins/rc-7.0-containers/cgcs-root BASE_VERSION: rc-7.0-stable-20230423T053318Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/containers/… REGISTRY_USERID: slittlewrs LATEST_PREFIX: rc-7.0 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/7.0/centos/containers/20230423T053318Z/logs PUBLISH_TIMESTAMP: 20230423T053318Z FLOCK_VERSION: rc-7.0-centos-stable-20230423T053318Z WEB_HOST_PORT: 80 PREFIX: rc-7.0 TIMESTAMP: 20230423T053318Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/7.0/centos/containers/20230423T053318Z/outputs REGISTRY: docker.io

1 0

[Starlingx-discuss] Minutes: Community Call (Apr 19, 2023)
by Khalil, Ghada 23 Apr '23

23 Apr '23

Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call April 19, 2023 Standing topics - Build - Main Branch Debian Builds - Two new build failures due to a recent code changes which resulted in containerd failing to build - LP: https://bugs.launchpad.net/starlingx/+bug/2016936 - Fix is posted for review and a rebuild will be triggered once it merges. - stx.6.0 Weekly Builds - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/ - stx.7.0 Weekly Builds - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/ - stx.8.0 Weekly Builds - Green - Build Output: https://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/ - Transition from CENGN - As discussed in the PTG, CENGN will no longer be able to host the StarlingX builds. - Build team is working on transitioning the builds to WR infrastructure. - Started mirroring jobs - Timing is TBD - Sanity - Debian Main Branch Platform Sanity - Last sanity email sent on Apr 18: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-April/013986.ht… - Status: Green for SX. Investigating an issue w/ DX. - Debian Main Branch stx-openstack Sanity - Last sanity email sent on Apr 11: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-April/013968.ht… - No sanity run this week yet. - Status: Yellow - Sanity LPs - LP: https://bugs.launchpad.net/starlingx/+bug/2007303 -- intermittent issue / works on retest - LP: https://bugs.launchpad.net/starlingx/+bug/2012389 -- intermittent issue - LP: https://bugs.launchpad.net/starlingx/+bug/2012392 -- consistently failing - Team has some resourcing challenges, so hasn't been able to investigate the failures further - Gerrit Reviews in Need of Attention - Pending doc reviews. Request for Juanita for community members to review: - https://review.opendev.org/q/starlingx/docs+status:open - 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 18: Some activity in the review as of Jan 15 - Feb 1: Alternative fix proposed on Jan 18; waiting for ScottK's review - Feb 15: ScottK is going back to this - Mar 22: Next action is w/ ScottK; As per today's meeting, he'll be looking at the comments - Apr 11: Review is still open. Next action is w/ ScottK (the author) - 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.9.0 - Release Tracking Spreadsheet created: https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrT… - Milestone-1 is declared. Milestone-2 is scheduled for the week of May 8. - See more details in the April 12 release meeting minutes: https://etherpad.opendev.org/p/stx-releases - Mission Statement Discussion - Latest Email: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-April/013987.ht… - Vote on the 1-sentence mission statement here: https://etherpad.opendev.org/p/starlingx-mission-statement - ARM Support in StarlingX - Interest raised by Trevor Tao - Topic has been discussed in the last PTG; still at an early stage - Suggestion is to raise the topic on the mailing list: https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss (now in vacation, maybe some time later) - Project / Team Meetings - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-April/013942.ht… - Latest Email: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-April/013973.ht… - Ildiko will follow up directly w/ the appropriate PLs if there are no responses on the mailing list. - Install Script Enhancement - Prime: Douglas Pereira - Work started and making progress on this. - Once the script is funcitonal, it will be posted for review. Then a doc update/simplification will follow. ARs from Previous Meetings - None Open Requests for Help - Build System Setup - Question was posted on IRC by Kevin - StarlingX documentation has a lot of outdated information. It took a lot of digging to find the right documentation for setting up a build env with minikube. - Requested that Kevin open an LP to the doc team and/or send an email to the mailing list w/ more details to the mailing list - Status: Open / No email sent to the mailing list yet. Unsure if LP was opened. - IP allocation is failing after StarlingX ISO image installation - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-April/013940.ht… - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-April/013966.ht… - Status: Closed / Resolved. Greg to respond to the mailing list w/ the resolution for traceability - Main branch Installation Issues - Reported by Prashanthi - Unclear what the issue is. Request to direct help in debugging. Action: Greg to see if someone can help. Note: Greg is off Apr 20-25 - stx.8.0 Interface Bonding issue - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-March/013877.ht… - Response sent Apr 19: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-April/013989.ht… / workaround confirmed / LP opened to track: https://bugs.launchpad.net/starlingx/+bug/2010119 - Status: Leave open for any further feedback from the reporter - stx-openstack apply failed after enabling cpu_dedicated_setInbox - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013720.… - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-January/013724.… - 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; team still has no bandwidth to look at this. - Status: Open / No updates ... still waiting for Thales/team to have time to look at this.

1 0

[Starlingx-discuss] [build-report] master STX_build_debian_master - Build # 151 - Failure!
by starlingx.build＠gmail.com 22 Apr '23

22 Apr '23

Project: STX_build_debian_master Build #: 151 Status: Failure Timestamp: 20230421T060000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/… -------------------------------------------------------------------------------- Parameters BUILD_PACKAGES_LIST: CLEAN_DOWNLOADS: false BUILD_HELM_CHARTS: true USE_DOCKER_CACHE: true DOCKER_IMAGE_LIST: PUSH_DOCKER_IMAGES: true CLEAN_DOCKER: true REFRESH_SOURCE: true DRY_RUN: false CLEAN_PACKAGES: true BUILD_RT: true BUILD_PACKAGES: true CLEAN_REPOMGR: true PKG_REUSE: false JENKINS_SCRIPTS_BRANCH: master BUILD_DOCKER_BASE_IMAGE: true BUILD_DOCKER_IMAGES: true FORCE_BUILD: false REBUILD_BUILDER_IMAGES: true CLEAN_ISO: true BUILD_ISO: true

1 0

[Starlingx-discuss] Opendev => github mirroring broken
by Panech, Davlet 22 Apr '23

22 Apr '23

Good day, We have noticed that StarlingX git repo mirrors on github are no longer being synchronized with opendev.org . This is because github.com has changed its SSH host key recently, and Zuul mirroring configuration in the individual repos still contain the old key. Ie lines similar to: https://opendev.org/starlingx/root/src/branch/master/.zuul.yaml#L31 must be updated with the new key. We are working on doing just that as a short term fix, but I really think we should tweak the Zuul job that drives this process to include the current github SSH key. That way we will have the key in one place and it will be much easier to fix next time this happens. Additionally, we may want to think of consolidating common Zuul tasks into some sort of centralized setup. I don't have all the details at this time -- let's discuss this at the next community call. Thank you, D.

1 0

Re: [Starlingx-discuss] Starlingx-discuss Digest, Vol 59, Issue 32
by Shavin Wijetunge 21 Apr '23

21 Apr '23

Sent from my Galaxy -------- Original message -------- From: starlingx-discuss-request(a)lists.starlingx.io Date: 19/04/2023 20:30 (GMT+05:30) To: starlingx-discuss(a)lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 59, Issue 32 Send Starlingx-discuss mailing list submissions to starlingx-discuss(a)lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request(a)lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner(a)lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Re: Need support for starlingX 8 setup bring up. (Waines, Greg) ---------------------------------------------------------------------- Message: 1 Date: Wed, 19 Apr 2023 14:59:13 +0000 From: "Waines, Greg" <Greg.Waines(a)windriver.com> To: "Gao, Litao" <Litao.Gao(a)windriver.com>, Prashanthi Moligi <prashanthi.moligi(a)tcs.com>, "Schwager, Udi" <Udi.Schwager(a)windriver.com>, StarlingX ML <starlingx-discuss(a)lists.starlingx.io> Cc: Nidhi Tomar <nidhi.tomar1(a)tcs.com>, Meghana S <s.meghana10(a)tcs.com>, Naga Sushma Gandrothu <g.nagasushma(a)tcs.com>, "Khalil, Ghada" <Ghada.Khalil(a)windriver.com>, "Thothadri, Ram" <Ram.Thothadri(a)windriver.com>, "Subramanian, Ramaswamy" <Ramaswamy.Subramanian(a)windriver.com>, "Geary, Stephen (Steve)" <Steve.Geary(a)windriver.com> Subject: Re: [Starlingx-discuss] Need support for starlingX 8 setup bring up. Message-ID: <CO1PR11MB5090C3C0AFC74C3F107B2F46E5629(a)CO1PR11MB5090.namprd11.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" + starlingx-discuss From: Gao, Litao <Litao.Gao(a)windriver.com> Sent: Wednesday, April 19, 2023 5:25 AM To: Waines, Greg <Greg.Waines(a)windriver.com>; Prashanthi Moligi <prashanthi.moligi(a)tcs.com>; Schwager, Udi <Udi.Schwager(a)windriver.com> Cc: Nidhi Tomar <nidhi.tomar1(a)tcs.com>; Meghana S <s.meghana10(a)tcs.com>; Naga Sushma Gandrothu <g.nagasushma(a)tcs.com>; Khalil, Ghada <Ghada.Khalil(a)windriver.com>; Thothadri, Ram <Ram.Thothadri(a)windriver.com>; Subramanian, Ramaswamy <Ramaswamy.Subramanian(a)windriver.com>; Geary, Stephen (Steve) <Steve.Geary(a)windriver.com> Subject: RE: Need support for starlingX 8 setup bring up. Hi Prashanthi, MEC services/app is supposed to be run as a standard k8s workload in pod (deployment, service, etc), you can launch your via kubectl, helmchart, or other ways available on k8s. And the GPU, High speed NIC, or accelerator support are available in StarlingX which may be used by MEC application. As I know, there is no publicly announced MEC applications running on StarlingX, but as I can see it is capable to carry the MEC workload you mentioned. And as Greg pointed, we have many commercial solutions for 5G vRAN solutions. Best Regards, Litao ________________________________ [Wind River]<https://www.windriver.com/> From: Waines, Greg <Greg.Waines(a)windriver.com<mailto:Greg.Waines@windriver.com>> Sent: Tuesday, April 18, 2023 7:03 PM To: Prashanthi Moligi <prashanthi.moligi(a)tcs.com<mailto:prashanthi.moligi@tcs.com>>; Gao, Litao <Litao.Gao(a)windriver.com<mailto:Litao.Gao@windriver.com>>; Schwager, Udi <Udi.Schwager(a)windriver.com<mailto:Udi.Schwager@windriver.com>> Cc: Nidhi Tomar <nidhi.tomar1(a)tcs.com<mailto:nidhi.tomar1@tcs.com>>; Meghana S <s.meghana10(a)tcs.com<mailto:s.meghana10@tcs.com>>; Naga Sushma Gandrothu <g.nagasushma(a)tcs.com<mailto:g.nagasushma@tcs.com>>; Khalil, Ghada <Ghada.Khalil(a)windriver.com<mailto:Ghada.Khalil@windriver.com>>; Thothadri, Ram <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>>; Subramanian, Ramaswamy <Ramaswamy.Subramanian(a)windriver.com<mailto:Ramaswamy.Subramanian@windriver.com>>; Geary, Stephen (Steve) <Steve.Geary(a)windriver.com<mailto:Steve.Geary@windriver.com>> Subject: RE: Need support for starlingX 8 setup bring up. + Udi as well ... he might be the proper contact for ORAN on StarlingX. Greg. From: Waines, Greg Sent: Tuesday, April 18, 2023 7:03 AM To: Prashanthi Moligi <prashanthi.moligi(a)tcs.com<mailto:prashanthi.moligi@tcs.com>>; Gao, Litao <Litao.Gao(a)windriver.com<mailto:Litao.Gao@windriver.com>> Cc: Nidhi Tomar <nidhi.tomar1(a)tcs.com<mailto:nidhi.tomar1@tcs.com>>; Meghana S <s.meghana10(a)tcs.com<mailto:s.meghana10@tcs.com>>; Naga Sushma Gandrothu <g.nagasushma(a)tcs.com<mailto:g.nagasushma@tcs.com>>; Khalil, Ghada <Ghada.Khalil(a)windriver.com<mailto:Ghada.Khalil@windriver.com>>; Thothadri, Ram <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>>; Subramanian, Ramaswamy <Ramaswamy.Subramanian(a)windriver.com<mailto:Ramaswamy.Subramanian@windriver.com>>; Geary, Stephen (Steve) <Steve.Geary(a)windriver.com<mailto:Steve.Geary@windriver.com>> Subject: RE: Need support for starlingX 8 setup bring up. There are commercial solutions for 5G RAN solutions from companies like Samsung that can run on StarlingX. There is also work on open ran ORAN solutions running on StarlingX. I have added Litao Gao to TO list. He may be able to provide pointers to you on how to get and run ORAN on StarlingX. Greg. From: Prashanthi Moligi <prashanthi.moligi(a)tcs.com<mailto:prashanthi.moligi@tcs.com>> Sent: Tuesday, April 18, 2023 12:03 AM To: Waines, Greg <Greg.Waines(a)windriver.com<mailto:Greg.Waines@windriver.com>>; Subramanian, Ramaswamy <Ramaswamy.Subramanian(a)windriver.com<mailto:Ramaswamy.Subramanian@windriver.com>> Cc: Nidhi Tomar <nidhi.tomar1(a)tcs.com<mailto:nidhi.tomar1@tcs.com>>; Meghana S <s.meghana10(a)tcs.com<mailto:s.meghana10@tcs.com>>; Naga Sushma Gandrothu <g.nagasushma(a)tcs.com<mailto:g.nagasushma@tcs.com>>; Khalil, Ghada <Ghada.Khalil(a)windriver.com<mailto:Ghada.Khalil@windriver.com>>; Thothadri, Ram <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>> Subject: RE: Need support for starlingX 8 setup bring up. 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. TCS Confidential Hi Greg, Thanks for quick reply. Yes Greg, MEC I meant "computing capabilities at the edge of the mobile network, within the Radio Access Network (RAN) and in close proximity to mobile subscribers." Dose starlingX platform supports to run MEC services or applications? Do we have any MEC applications available with starlingX, like we have in Akarino blueprints (Ex: 5G cloud Gaming, HD video, Live broadcasting)? If yes, I want to bring up starlingX platform ASAP, for that I need your support, if possible can we have one teams call and discuss about bring up issues. Thanks, Prashanthi. From: Waines, Greg <Greg.Waines(a)windriver.com<mailto:Greg.Waines@windriver.com>> Sent: Monday, April 17, 2023 4:25 PM To: Prashanthi Moligi <prashanthi.moligi(a)tcs.com<mailto:prashanthi.moligi@tcs.com>>; Subramanian, Ramaswamy <Ramaswamy.Subramanian(a)windriver.com<mailto:Ramaswamy.Subramanian@windriver.com>> Cc: Nidhi Tomar <nidhi.tomar1(a)tcs.com<mailto:nidhi.tomar1@tcs.com>>; Meghana S <s.meghana10(a)tcs.com<mailto:s.meghana10@tcs.com>>; Naga Sushma Gandrothu <g.nagasushma(a)tcs.com<mailto:g.nagasushma@tcs.com>>; Khalil, Ghada <Ghada.Khalil(a)windriver.com<mailto:Ghada.Khalil@windriver.com>>; Thothadri, Ram <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>> Subject: RE: Need support for starlingX 8 setup bring up. TCS Confidential "External email. Open with Caution" See in-lined responses below, Greg. From: Prashanthi Moligi <prashanthi.moligi(a)tcs.com<mailto:prashanthi.moligi@tcs.com>> Sent: Monday, April 17, 2023 1:57 AM To: Waines, Greg <Greg.Waines(a)windriver.com<mailto:Greg.Waines@windriver.com>>; Subramanian, Ramaswamy <Ramaswamy.Subramanian(a)windriver.com<mailto:Ramaswamy.Subramanian@windriver.com>> Cc: Nidhi Tomar <nidhi.tomar1(a)tcs.com<mailto:nidhi.tomar1@tcs.com>>; Meghana S <s.meghana10(a)tcs.com<mailto:s.meghana10@tcs.com>>; Naga Sushma Gandrothu <g.nagasushma(a)tcs.com<mailto:g.nagasushma@tcs.com>>; Khalil, Ghada <Ghada.Khalil(a)windriver.com<mailto:Ghada.Khalil@windriver.com>>; Thothadri, Ram <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>> Subject: RE: Need support for starlingX 8 setup bring up. 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. TCS Confidential Hi Greg, Yes, we were able to get internet connectivity by running DHCP client command, IP is also getting allocate. Thanks for your support and working on further configurations. Have few doubts about that: 1. Are all the configurations mandatory, For example I want to run my containers on Kubernetes, is openstack configurations has to be done or optional?? [Greg] OpenStack is optional. There are many users of StarlingX that only use the base StarlingX Kubernetes Platform. 2. After completing all setting, if I want run MEC services/applications how to run those containers in this server, do you have any applications available along with starlingX? 3. Please share document, if you have any to configure MEC. [Greg] Are you referring to ? ... "MEC or Mobile edge Computing provides an IT service environment and cloud-computing capabilities at the edge of the mobile network, within the Radio Access Network (RAN) and in close proximity to mobile subscribers." Greg. Thanks, Prashanthi.M From: Waines, Greg <Greg.Waines(a)windriver.com<mailto:Greg.Waines@windriver.com>> Sent: Sunday, April 16, 2023 6:25 PM To: Prashanthi Moligi <prashanthi.moligi(a)tcs.com<mailto:prashanthi.moligi@tcs.com>>; Subramanian, Ramaswamy <Ramaswamy.Subramanian(a)windriver.com<mailto:Ramaswamy.Subramanian@windriver.com>> Cc: Nidhi Tomar <nidhi.tomar1(a)tcs.com<mailto:nidhi.tomar1@tcs.com>>; Meghana S <s.meghana10(a)tcs.com<mailto:s.meghana10@tcs.com>>; Naga Sushma Gandrothu <g.nagasushma(a)tcs.com<mailto:g.nagasushma@tcs.com>>; Khalil, Ghada <Ghada.Khalil(a)windriver.com<mailto:Ghada.Khalil@windriver.com>>; Thothadri, Ram <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>> Subject: RE: Need support for starlingX 8 setup bring up. TCS Confidential "External email. Open with Caution" Any luck ? Greg. From: Waines, Greg Sent: Thursday, April 13, 2023 9:07 AM To: Prashanthi Moligi <prashanthi.moligi(a)tcs.com<mailto:prashanthi.moligi@tcs.com>>; Subramanian, Ramaswamy <Ramaswamy.Subramanian(a)windriver.com<mailto:Ramaswamy.Subramanian@windriver.com>> Cc: Nidhi Tomar <nidhi.tomar1(a)tcs.com<mailto:nidhi.tomar1@tcs.com>>; Meghana S <s.meghana10(a)tcs.com<mailto:s.meghana10@tcs.com>>; Naga Sushma Gandrothu <g.nagasushma(a)tcs.com<mailto:g.nagasushma@tcs.com>>; Khalil, Ghada <Ghada.Khalil(a)windriver.com<mailto:Ghada.Khalil@windriver.com>>; Thothadri, Ram <Ram.Thothadri(a)windriver.com<mailto:Ram.Thothadri@windriver.com>> Subject: RE: Need support for starlingX 8 setup bring up. Hey Prashanthi, Before I try to find someone to work closely with you on this ... can you try the following solutions. So, you say that your ISO install completes and you are able to login as 'sysadmin' (initial password is 'sysadmin' and you are forced to change it). But then you have no IP connectivity. So I learned that automatic DHCP does not seem to be working with our DEBIAN loads (STX 8.0) So two options for you to try: * Run 'dhclient' manually * RUN THE FOLLOWING: * sudo dhclient <ifname> * * WHERE <ifname> is the linux interface name of the interface that is physically cabled to a router that gives you internet access * OR * Configure IP Address and Default IP Route manually * RUN THE FOLLOWING: * sudo ip address add <IP-ADDRESS>/<SUBNET-LENGTH> dev <PORT> * sudo ip link set up dev <PORT> * sudo ip route add default via <GATEWAY-IP-ADDRESS> dev <PORT> * ping 8.8.8.8<https://urldefense.com/v3/__http:/8.8.8.8__;!!AjveYdw8EvQ!c2QTPp_0Xx4jJQ1va…> * * WHERE <PORT> is the linux interface name of the interface that is physically cabled to a router that gives you internet accdess <IP-ADDRESS>/<SUBNET-LENGTH> is the IP ADDRESS for your server (i.e. StarlingX controller-0) based on your local addressing plan <GATEWAY-IP-ADDRESS> is the IP ADDRESS of your adjacent router. Let me know if that works first, Greg. From: Prashanthi Moligi <prashanthi.moligi(a)tcs.com<mailto:prashanthi.moligi@tcs.com>> Sent: Thursday, April 13, 2023 2:17 AM To: Waines, Greg <Greg.Waines(a)windriver.com<mailto:Greg.Waines@windriver.com>>; Subramanian, Ramaswamy <Ramaswamy.Subramanian(a)windriver.com<mailto:Ramaswamy.Subramanian@windriver.com>> Cc: Nidhi Tomar <nidhi.tomar1(a)tcs.com<mailto:nidhi.tomar1@tcs.com>>; Meghana S <s.meghana10(a)tcs.com<mailto:s.meghana10@tcs.com>>; Naga Sushma Gandrothu <g.nagasushma(a)tcs.com<mailto:g.nagasushma@tcs.com>> Subject: Need support for starlingX 8 setup bring up. 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. TCS Confidential Hi Greg, Thanks for your suggestion in yesterday's meeting. As we discussed in meeting can you please give me one POC name who can help me to bring up StarlingX 8 in my internal PC. I got struck at IP assignment part from long time, I want to bring this up setup ASAP, so your quick support will be helpful. Thanks & Regards, Prashanthi. TCS Confidential =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you TCS Confidential TCS Confidential TCS Confidential TCS Confidential

1 0

[Starlingx-discuss] [build-report] master STX_build_debian_master - Build # 149 - Still Failing!
by starlingx.build＠gmail.com 20 Apr '23

20 Apr '23

Project: STX_build_debian_master Build #: 149 Status: Still Failing Timestamp: 20230419T060000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/… -------------------------------------------------------------------------------- Parameters BUILD_PACKAGES_LIST: CLEAN_DOWNLOADS: false BUILD_HELM_CHARTS: true USE_DOCKER_CACHE: true DOCKER_IMAGE_LIST: PUSH_DOCKER_IMAGES: true CLEAN_DOCKER: true REFRESH_SOURCE: true DRY_RUN: false CLEAN_PACKAGES: true BUILD_RT: true BUILD_PACKAGES: true CLEAN_REPOMGR: true PKG_REUSE: false JENKINS_SCRIPTS_BRANCH: master BUILD_DOCKER_BASE_IMAGE: true BUILD_DOCKER_IMAGES: true FORCE_BUILD: false REBUILD_BUILDER_IMAGES: true CLEAN_ISO: true BUILD_ISO: true

1 0

[Starlingx-discuss] Re：RE: how to install my own rpm
by LiuYongfu 20 Apr '23

20 Apr '23

Hi，     thanks very much . so I need to make a pach  and install it .  my first step is to build the starlingx .when I build this.  It has some problems as below: could you please help me ? thanks very much. LiuYongfu 114769003(a)qq.com Original From:"Bailey, Henry Albert (Al)"< Al.Bailey(a)windriver.com >; Date:2023/2/18 5:05 To:"LiuYongfu"< 114769003(a)qq.com >;"starlingx-discuss"< starlingx-discuss(a)lists.starlingx.io >; Subject:RE: [Starlingx-discuss] how to install my own rpm With StarlingX, the way to add an rpm to the platform is through a patch. Within the StarlingX patching system it will install the rpm, and will prevent it from being removed by a reboot.   There is a video from the Open Infrastructure Foundation that shows an example of creating your own patch to allow an rpm to be installed.  It uses the patch_build.sh command https://www.youtube.com/watch?v=vwqhxpgaxXE     For example, if I wanted to add an RPM for pyflame  my patch_build.sh   syntax would look something like this:   # Run this script from within $MY_WORKSPACE PATH=$MY_REPO/stx/update/extras/scripts:$PATH PATCH_ID=PYFLAME DIR=std/rpmbuild/RPMS PYFLAME=pyflame-1.6.6-4.el7.tis.1.x86_64.rpm   patch_build.sh \ --id ${PATCH_ID} \ --reboot-required=Y \ --summary "New pyflame rpm " \ --desc "Adds a new pyflame rpm "\ --controller ${DIR}/${PYFLAME} \ --controller-worker ${DIR}/${PYFLAME} \ --controller-worker-lowlatency ${DIR}/${PYFLAME}     Be aware that in this example,  I am ‘adding’ an rpm  rather than updating one, so I needed to include special fields (--controller ,  --controller-worker ,  --controller-worker-lowlatency ) so that the platform knows that the rpm belongs on controller and AIO hosts (and in this example it will not install it on worker or storage nodes)   The video (and my example) assume you have a development environment setup with your variables, etc..  already defined.  If that is not the case, you may need to ensure you have the starlingx/update repo checked out and make the appropriate changes to the commands.     Al   From: LiuYongfu <114769003(a)qq.com> Sent: Saturday, February 11, 2023 5:52 AM To: starlingx-discuss <starlingx-discuss(a)lists.starlingx.io> Subject: [Starlingx-discuss] how to install my own rpm   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. Brief Description ----------------- when I install my private(own) rpm to the compute node. when the node is restarted .my private rpm is deleted. so I want to know : are there some ways to install my own rpm on compute nodes or is it just a bug? Steps to Reproduce ------------------ I installed my GPU rpm packages on the compute node,and it worked right. Expected Behavior ------------------ the rpm packages works correctly all the time. Actual Behavior when reboot the compute nodes .my gpu rpm packages are removed by the system. thanks very much. LiuYongfu 114769003(a)qq.com  

3 2