From ildiko.vancsa at gmail.com Fri Jul 1 03:53:49 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 30 Jun 2022 20:53:49 -0700 Subject: [Starlingx-discuss] Challenges with the support to deploy stx-openstack in 7.0 In-Reply-To: References: <1656591176286.175119764.1933541420@optimcloud.com> Message-ID: Hi, Thank you all for chiming in on the topic with comments and updates. To quickly summarize the responses so far: * Users are currently relying on the OpenStack component within StarlingX ?> if 7.0 does not support OpenStack that prevents them from being able upgrade * The FluxCD transition currently doesn?t support to deploy OpenStack as a StarlingX application * stx-openstack can be deployed with Armada, that is supposed to work in 7.0 with Kubernetes 1.21; however, Armada probably does not work with Kubernetes 1.22 or higher * The community is currently working on testing the 7.0 release and as part of that to verify if 7.0 in its current state can deploy OpenStack * Beyond using the mailing list, further discussions will happen in the Release Team meetings and TSC & Community calls based on the results of sanity testing I?m still somewhat confused about marking the FluxCD feature and work item ?complete'. Since the spec lists the support of StarlingX applications I think it would be more accurate to mark the feature ?incomplete? or ?limited functionality?. That is more transparent regarding the actual status of the implementation and testing work. Would you all agree? I would also like to encourage everyone who has questions or input to this topic to chime in to this mail thread. In addition, please also join the aforementioned meetings if you can, to follow and participate in the discussions. Thanks and Best Regards, Ildik? > On Jun 30, 2022, at 05:27, Waines, Greg wrote: > > I said that "It is believed that stx-openstack in STX7 w/k8s v1.21" ... > simply because in STX7, we have not had a clean sanity run from the StarlingX Test subproject for over a month. > Greg. > > -----Original Message----- > From: Embedded Devel > Sent: Thursday, June 30, 2022 8:17 AM > To: Waines, Greg ; Ildiko Vancsa ; Qi, Mingyuan ; Shuquan Huang ; Subramanian, Ramaswamy ; StarlingX ML > Subject: Re: [Starlingx-discuss] Challenges with the support to deploy stx-openstack in 7.0 > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > On Thursday 30 June 2022 18:42:35 PM (+07:00), Waines, Greg wrote: > >> I think what I heard yesterday is that we believe stx-openstack runs on STX 7 w/k8s v1.21 ... although there are two outstanding sanity problems that are currently open. >> Stx-openstack sanity has not been running for over a month because of transition of starlingx sanity from Intel to Wind River. >> It is believed that stx-openstack application (based on armada) will NOT work on STX 7 w/k8s v1.22 or v1.23; where v1.23 is the default for STX 7. > Why is it believed ??? We run k8s 1.21.3 on STX 6.x and openstack-helm deploys just fine, where are you finding this information. > > controller-0:~$ kubectl get pods --all-namespaces > NAMESPACE NAME READY STATUS RESTARTS AGE > armada armada-api-dc8b94475-28hsg 2/2 Running 2 2d3h > cert-manager cm-cert-manager-74cc8d687-rfhwz 1/1 Running 1 2d2h > ----snip----------------- > kube-system rbd-provisioner-759dfb8b6b-sjq5h 1/1 Running 0 2d2h > openstack cinder-api-79b6497c55-9bzqs 1/1 Running 0 2d > openstack cinder-backup-d7b4c8946-gnx49 1/1 Running 0 2d > openstack cinder-scheduler-7fd896457c-82j7c 1/1 Running 0 2d > openstack cinder-volume-57cfc5fcc-8ft7m 1/1 Running 0 2d > openstack cinder-volume-usage-audit-27609840-v46qc 0/1 Completed 0 15m > openstack cinder-volume-usage-audit-27609845-5dh89 0/1 Completed 0 10m > openstack cinder-volume-usage-audit-27609850-qs4bb 0/1 Completed 0 5m29s > openstack cinder-volume-usage-audit-27609855-6rglw 1/1 Running 0 29s > openstack fm-db-init-7mnt2 0/1 Completed 0 2d > openstack fm-db-sync-km7dp 0/1 Completed 0 2d > openstack fm-ks-endpoints-htsfz 0/3 Completed 0 2d > openstack fm-ks-service-9sqk2 0/1 Completed 0 2d > openstack fm-ks-user-wtr27 0/1 Completed 0 2d > openstack fm-rest-api-675d7867f6-bpv6w 1/1 Running 0 2d > openstack glance-api-699b77f6db-xssfj 1/1 Running 0 2d > openstack heat-api-cd74f79c6-kcdtm 1/1 Running 0 2d > openstack heat-bootstrap-nhvzl 0/1 Completed 0 2d > openstack heat-cfn-5c69ff4548-z7dgw 1/1 Running 0 2d > openstack heat-db-init-88lkz 0/1 Completed 0 2d > openstack heat-db-sync-df2dp 0/1 Completed 0 2d > openstack heat-domain-ks-user-rv6c6 0/1 Completed 0 2d > openstack heat-engine-6745946fd4-p6lr4 1/1 Running 0 2d > openstack heat-engine-cleaner-27609840-skjm4 0/1 Completed 0 15m > openstack heat-engine-cleaner-27609845-xdkj9 0/1 Completed 0 10m > openstack heat-engine-cleaner-27609850-f5crb 0/1 Completed 0 5m29s > openstack heat-engine-cleaner-27609855-4m6kr 1/1 Running 0 29s > openstack heat-ks-endpoints-dfng4 0/6 Completed 0 2d > openstack heat-ks-service-7czzq 0/2 Completed 0 2d > openstack heat-ks-user-pk7p7 0/1 Completed 0 2d > openstack heat-purge-deleted-27607700-mfbbz 0/1 Completed 0 35h > openstack heat-purge-deleted-27609140-9sdlw 0/1 Completed 0 11h > openstack heat-rabbit-init-74xhg 0/1 Completed 0 2d > openstack heat-trustee-ks-user-45xd4 0/1 Completed 0 2d > openstack heat-trusts-nsq8j 0/1 Completed 0 2d > openstack horizon-5c4c9b79f4-s6v6b 1/1 Running 0 2d > openstack horizon-db-init-bs6b5 0/1 Completed 0 2d > openstack horizon-db-sync-59gbt 0/1 Completed 0 2d > openstack ingress-7559b8d644-2qx6v 1/1 Running 0 2d > openstack ingress-error-pages-7975fd4db5-jqn4q 1/1 Running 0 2d > openstack keystone-api-84bb867c4c-2n2tj 1/1 Running 0 2d > openstack keystone-fernet-rotate-27608400-vsscl 0/1 Completed 0 24h > openstack keystone-fernet-rotate-27609120-k2zsv 0/1 Completed 0 12h > openstack keystone-fernet-rotate-27609840-2fmmv 0/1 Completed 0 15m > openstack libvirt-libvirt-default-ggp5l 1/1 Running 0 2d > openstack mariadb-ingress-847cdb5dfb-7q59v 1/1 Running 0 2d > openstack mariadb-ingress-error-pages-857f748f89-lvqqc 1/1 Running 0 2d > openstack mariadb-server-0 1/1 Running 0 2d > openstack neutron-dhcp-agent-controller-0-937646f6-p5nfg 1/1 Running 0 2d > openstack neutron-l3-agent-controller-0-937646f6-w5zxp 1/1 Running 0 2d > openstack neutron-metadata-agent-controller-0-937646f6-f2vqp 1/1 Running 0 2d > openstack neutron-netns-cleanup-cron-default-jx9zr 1/1 Running 1 2d > openstack neutron-ovs-agent-controller-0-937646f6-8rzpz 1/1 Running 0 2d > openstack neutron-server-764ff69bbd-wqnh6 1/1 Running 0 2d > openstack nova-api-metadata-75cf57b549-t97d8 1/1 Running 2 2d > openstack nova-api-osapi-5f9d8b8d5d-j848v 1/1 Running 0 2d > openstack nova-api-proxy-7c86f9dc4d-vjp66 1/1 Running 1 2d > openstack nova-bootstrap-5t9jg 0/1 Completed 0 2d > openstack nova-cell-setup-7dr9v 0/1 Completed 0 2d > openstack nova-compute-controller-0-937646f6-g6748 2/2 Running 0 2d > openstack nova-conductor-c9757f646-bzr5s 1/1 Running 0 2d > openstack nova-db-sync-g5w7s 0/1 Completed 0 2d > openstack nova-novncproxy-7f58c4dcdb-zxrql 1/1 Running 0 2d > openstack nova-scheduler-7b98545d78-zpxvv 1/1 Running 0 2d > openstack nova-service-cleaner-27609720-z8nh6 0/1 Completed 0 135m > openstack nova-service-cleaner-27609780-vbj58 0/1 Completed 0 75m > openstack nova-service-cleaner-27609840-7mb7r 0/1 Completed 0 15m > openstack openvswitch-db-ltwlf 1/1 Running 1 2d > openstack openvswitch-vswitchd-92tn6 1/1 Running 0 2d > openstack osh-openstack-memcached-memcached-54cc965966-96bp9 1/1 Running 0 2d > openstack osh-openstack-rabbitmq-rabbitmq-0 1/1 Running 0 2d > openstack pci-irq-affinity-agent-fnn94 1/1 Running 0 2d > openstack placement-api-8759c476f-c4gfc 1/1 Running 0 2d > > > controller-0:~$ kubectl version > Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.3", GitCommit:"ca643a4d1f7bfe34773c74f79527be4afd95bf39", GitTreeState:"archive", BuildDate:"2022-01-19T17:43:43Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.3", GitCommit:"ca643a4d1f7bfe34773c74f79527be4afd95bf39", GitTreeState:"clean", BuildDate:"2021-07-15T20:59:07Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"} > > > > >> I agree that it is concerning that the work on stx-openstack support of fluxcd and k8s v1.22 & v1.23 is behind. >> >> Generally the starlingx community support for stx-openstack sub-project has decreased significantly in the last few years. >> - A team from Intel (Bruce Jones, Austin Sun, Mingyuan Qi) supported >> this originally, but stopped supporting stx-openstack in StarlingX a >> year ago or so, >> - A team from Wind River (Douglas Periera) picked up support for >> stx-openstack in StarlingX a year and a half ago, but as mentioned at the last PTG, their level of contribution has been reduced due to internal Wind River priorities. >> I believe Douglas only has a team of ~4 working on stx-openstack. >> They are currently working on fluxcd support and Debian support for stx-openstack, but current plans don't show this being available until end of year, due to capacity of team. >> >> >> Despite this, I still think it is the right decision to release STX 7 without stx-openstack fully supported. >> I believe the majority of users of StarlingX are not using stx-openstack. >> I believe the majority of users of StarlingX are only leveraging the Kubernetes Platform, and StarlingX's infrastructure management of that Kubernetes Platform. >> >> >> Greg. >> >> p.s. If we release STX 7, and we do get concerned feedback on limited support for stx-openstack in STX 7, perhaps this is good opportunity to seek help from these concerned StarlingX Users of stx-openstack to become contributors. >> >> >> >> -----Original Message----- >> From: Ildiko Vancsa >> Sent: Wednesday, June 29, 2022 11:24 PM >> To: Waines, Greg ; Qi, Mingyuan >> ; Shuquan Huang ; >> Subramanian, Ramaswamy ; >> StarlingX ML >> Subject: Challenges with the support to deploy stx-openstack in 7.0 >> >> [Please note: This e-mail is from an EXTERNAL e-mail address] >> >> Hi StarlingX TSC and Community, >> >> I?m reaching out to you about one of the topics that came up during the Release Team meeting[1] earlier today, which is the replacement of Armada with FluxCD. The conversation got me a little confused and I would like to follow up on a few questions and concerns. >> >> Background: According to the current state of the 7.0 release the work item is in a stage where it is operational and the feature is marked ?Done? in the release spreadsheet. At the same time, it does not support the deployment of OpenStack as part of StarlingX. I found this surprising, as my expectation was that the goal and expected outcome of the feature implementation was to provide the same functionality as Armada did. >> >> The spec[2] also lists the following work items: >> * Update the application framework to use the Helm/Source controllers >> * Update all applications to use the Helm/Source controllers for >> deploying/updating applications >> * Provide upgrade support to update all applications to the Helm >> Controller and remove the Armada pod >> >> Questions and concerns: My understanding was that ?application? refers to OpenStack among other components. Is that a false assumption? >> >> While it can happen that a bigger work item gets released with partial functionality, it was raised during the call today that StarlingX 7.0 might get released without the support to deploy OpenStack potentially due to issues with the now deprecated Armada component. Is my understanding correct that it is a possible scenario for StarlingX 7.0? >> >> If the above scenario happened, it would result in a very visible user-facing change which can provide issues to existing users or shrink the pool of potential new ones. While OpenStack is utilizing the advantages of being deployed in containers, it is still a dominant feature of StarlingX to provide infrastructure functionality. In that sense, I think there are concerns that would be worthwhile to evaluate to decide if it is a blocking issue to not being able to deploy it within StarlingX in the 7.0 release. What are your thoughts about this? Have the impacts of the above mentioned scenario been evaluated already? >> >> Thanks and Best Regards, >> Ildik? >> >> [1] https://etherpad.opendev.org/p/stx-releases >> [2] https://review.opendev.org/c/starlingx/specs/+/829595 >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem >> Open Infrastructure Foundation >> >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > -- > Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com From vburru at marvell.com Fri Jul 1 21:06:45 2022 From: vburru at marvell.com (Veerasenareddy Burru) Date: Fri, 1 Jul 2022 21:06:45 +0000 Subject: [Starlingx-discuss] unable to push new spec to starlingx/specs Message-ID: Hi, I have followed the process listed in below page to push new spec file. https://docs.starlingx.io/developer_resources/code-submission-guide.html It is failing with below error: vburru at PowerEdge-T630:/disk2/vsr/upstream/stx/specs$ git push origin HEAD:refs/for/master --verbose Pushing to https://review.opendev.org/starlingx/specs Username for 'https://review.opendev.org': vburru Password for 'https://vburru at review.opendev.org': remote: Unauthorized fatal: Authentication failed for 'https://review.opendev.org/starlingx/specs/' vburru@ PowerEdge-T630:/disk2/vsr/upstream/stx/specs$ It seems I do not have permissions to push changes to starlingx/specs repo. May I know how to get the correct permissions for this repo ? Thanks & Regards, VSR -------------- next part -------------- An HTML attachment was scrubbed... URL: From vburru at marvell.com Fri Jul 1 21:12:11 2022 From: vburru at marvell.com (Veerasenareddy Burru) Date: Fri, 1 Jul 2022 21:12:11 +0000 Subject: [Starlingx-discuss] unable to push new spec to starlingx/specs In-Reply-To: References: Message-ID: Hi, I am able to push the change with the password generated using "generate new password" option below "HTTP credentials" in gerrit settings page. How can I set HTTP password to something of my choice ? Thanks & Regards, VSR. From: Veerasenareddy Burru Sent: Friday, July 1, 2022 2:07 PM To: starlingx-discuss at lists.starlingx.io Subject: unable to push new spec to starlingx/specs Hi, I have followed the process listed in below page to push new spec file. https://docs.starlingx.io/developer_resources/code-submission-guide.html It is failing with below error: vburru at PowerEdge-T630:/disk2/vsr/upstream/stx/specs$ git push origin HEAD:refs/for/master --verbose Pushing to https://review.opendev.org/starlingx/specs Username for 'https://review.opendev.org': vburru Password for 'https://vburru at review.opendev.org': remote: Unauthorized fatal: Authentication failed for 'https://review.opendev.org/starlingx/specs/' vburru@ PowerEdge-T630:/disk2/vsr/upstream/stx/specs$ It seems I do not have permissions to push changes to starlingx/specs repo. May I know how to get the correct permissions for this repo ? Thanks & Regards, VSR -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Fri Jul 1 21:22:49 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 1 Jul 2022 14:22:49 -0700 Subject: [Starlingx-discuss] unable to push new spec to starlingx/specs In-Reply-To: References: Message-ID: Hi, Thank you for submitting your spec for the 8.0 release cycle. Do you have your ssh key set up and uploaded to Gerrit as it is described here: https://docs.openstack.org/contributors/common/setup-gerrit.html#setup-ssh-keys ? When you set up the ssh key, you should also update your git remote by using the following command: ?git remote add ssh://vburru at review.opendev.org:29418/starlingx/specs.git' Does this help? Best Regards, Ildik? > On Jul 1, 2022, at 14:12, Veerasenareddy Burru wrote: > > Hi, > > I am able to push the change with the password generated using ?generate new password? option below ?HTTP credentials? in gerrit settings page. > How can I set HTTP password to something of my choice ? > > Thanks & Regards, > VSR. > > From: Veerasenareddy Burru > Sent: Friday, July 1, 2022 2:07 PM > To: starlingx-discuss at lists.starlingx.io > Subject: unable to push new spec to starlingx/specs > > Hi, > > I have followed the process listed in below page to push new spec file. > https://docs.starlingx.io/developer_resources/code-submission-guide.html > > It is failing with below error: > > vburru at PowerEdge-T630:/disk2/vsr/upstream/stx/specs$ git push origin HEAD:refs/for/master --verbose > Pushing to https://review.opendev.org/starlingx/specs > Username for 'https://review.opendev.org': vburru > Password for 'https://vburru at review.opendev.org': > remote: Unauthorized > fatal: Authentication failed for 'https://review.opendev.org/starlingx/specs/' > vburru@ PowerEdge-T630:/disk2/vsr/upstream/stx/specs$ > > > It seems I do not have permissions to push changes to starlingx/specs repo. > May I know how to get the correct permissions for this repo ? > > > Thanks & Regards, > VSR > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From fungi at yuggoth.org Fri Jul 1 21:37:06 2022 From: fungi at yuggoth.org (Jeremy Stanley) Date: Fri, 1 Jul 2022 21:37:06 +0000 Subject: [Starlingx-discuss] unable to push new spec to starlingx/specs In-Reply-To: References: Message-ID: <20220701213706.5k4lfinc6nukpbyz@yuggoth.org> On 2022-07-01 21:12:11 +0000 (+0000), Veerasenareddy Burru wrote: [...] > How can I set HTTP password to something of my choice ? You can't. Gerrit only allows you to generate random passwords, which it then shows you and securely hashes into its database. It does not allow you to set a specific password. This is so that secure password handling can be done statelessly in the application. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From vburru at marvell.com Sat Jul 2 00:10:05 2022 From: vburru at marvell.com (Veerasenareddy Burru) Date: Sat, 2 Jul 2022 00:10:05 +0000 Subject: [Starlingx-discuss] [EXT] Re: unable to push new spec to starlingx/specs In-Reply-To: References: Message-ID: > -----Original Message----- > From: Ildiko Vancsa > Sent: Friday, July 1, 2022 2:23 PM > To: Veerasenareddy Burru > Cc: starlingx-discuss at lists.starlingx.io > Subject: [EXT] Re: [Starlingx-discuss] unable to push new spec to > starlingx/specs > Importance: Low > > External Email > > ---------------------------------------------------------------------- > Hi, > > Thank you for submitting your spec for the 8.0 release cycle. > > Do you have your ssh key set up and uploaded to Gerrit as it is described > here: https://urldefense.proofpoint.com/v2/url?u=https- > 3A__docs.openstack.org_contributors_common_setup-2Dgerrit.html-23setup- > 2Dssh- > 2Dkeys&d=DwIFaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=XkP_75lnbPIeeucsPX36Zgj > iMqEKttwZfwNyWMCLjT0&m=iruTD9nn948bOeoNEZjYy-orLT6cmshvWDAKQm- > rPNcgkP-9D-0damTf77KC- > h1l&s=kj5nUKcONcgjOVFOgbvdBAndIDbhk_otByaQKP6Ez5U&e= ? > > When you set up the ssh key, you should also update your git remote by > using the following command: ?git remote add > ssh://vburru at review.opendev.org:29418/starlingx/specs.git' > > Does this help? Hello Ildiko, Thanks for your response. This did not help. Mainly, I am unable to clone using ssh. Below command just stalls. git clone "ssh://vburru at review.opendev.org:29418/starlingx/specs" && scp -p -P 29418 vburru at review.opendev.org:hooks/commit-msg "specs/.git/hooks/" Below is the verbose log when I try just ssh: vburru at sburla-PowerEdge-T630:/disk2/vsr/upstream/stx/tmp$ ssh -p 29418 vburru at review.opendev.org -vv OpenSSH_7.6p1 Ubuntu-4ubuntu0.6, OpenSSL 1.0.2n 7 Dec 2017 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: resolving "review.opendev.org" port 29418 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to review.opendev.org [199.204.45.33] port 29418. debug1: Connection established. debug1: identity file /home/vburru/.ssh/id_rsa type 0 debug1: key_load_public: No such file or directory debug1: identity file /home/vburru/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/vburru/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/vburru/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/vburru/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/vburru/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/vburru/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/vburru/.ssh/id_ed25519-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.6 <<<<----- it stalls here. Thanks & Regards, VSR > > Best Regards, > Ildik? > > > > On Jul 1, 2022, at 14:12, Veerasenareddy Burru > wrote: > > > > Hi, > > > > I am able to push the change with the password generated using ?generate > new password? option below ?HTTP credentials? in gerrit settings page. > > How can I set HTTP password to something of my choice ? > > > > Thanks & Regards, > > VSR. > > > > From: Veerasenareddy Burru > > Sent: Friday, July 1, 2022 2:07 PM > > To: starlingx-discuss at lists.starlingx.io > > Subject: unable to push new spec to starlingx/specs > > > > Hi, > > > > I have followed the process listed in below page to push new spec file. > > https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.starlingx.io > > _developer-5Fresources_code-2Dsubmission- > 2Dguide.html&d=DwIFaQ&c=nKjWe > > > c2b6R0mOyPaz7xtfQ&r=XkP_75lnbPIeeucsPX36ZgjiMqEKttwZfwNyWMCLjT0&m > =iruT > > D9nn948bOeoNEZjYy-orLT6cmshvWDAKQm-rPNcgkP-9D-0damTf77KC- > h1l&s=8Io0b6K > > Z41uQtSKCYQ6IJafOM7lJG-64dUP0slmI6kk&e= > > > > It is failing with below error: > > > > vburru at PowerEdge-T630:/disk2/vsr/upstream/stx/specs$ git push origin > > HEAD:refs/for/master --verbose Pushing to > > https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.or > > > g_starlingx_specs&d=DwIFaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=XkP_75lnbPIee > ucs > > PX36ZgjiMqEKttwZfwNyWMCLjT0&m=iruTD9nn948bOeoNEZjYy- > orLT6cmshvWDAKQm-r > > PNcgkP-9D-0damTf77KC-h1l&s=Z_08ZKmrD8g4c_OnO-Y1SGLtYt3Y6EtNYJ5s- > d2Cs3w > > &e= Username for > > 'https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.o > > > rg&d=DwIFaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=XkP_75lnbPIeeucsPX36ZgjiMqE > KttwZfwNyWMCLjT0&m=iruTD9nn948bOeoNEZjYy-orLT6cmshvWDAKQm- > rPNcgkP-9D-0damTf77KC- > h1l&s=sPuDxhUPmpKDyVX0GhRPcRA8Gk342LdDGvGisc7EZ3Q&e= ': vburru > Password for 'https://urldefense.proofpoint.com/v2/url?u=https-3A__vburru- > 40review.opendev.org&d=DwIFaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=XkP_75ln > bPIeeucsPX36ZgjiMqEKttwZfwNyWMCLjT0&m=iruTD9nn948bOeoNEZjYy- > orLT6cmshvWDAKQm-rPNcgkP-9D-0damTf77KC-h1l&s=OWxwYqCSfD0H_R- > dTeh-jN1IYXFBjgw_JSwrrubUVlc&e= ': > > remote: Unauthorized > > fatal: Authentication failed for > 'https://urldefense.proofpoint.com/v2/url?u=https- > 3A__review.opendev.org_starlingx_specs_&d=DwIFaQ&c=nKjWec2b6R0mOyPa > z7xtfQ&r=XkP_75lnbPIeeucsPX36ZgjiMqEKttwZfwNyWMCLjT0&m=iruTD9nn948 > bOeoNEZjYy-orLT6cmshvWDAKQm-rPNcgkP-9D-0damTf77KC-h1l&s=ceQ2f7- > rRS0SjW7uwq20xOhw9cz2CZZTTk6yJySbsqI&e= ' > > vburru@ PowerEdge-T630:/disk2/vsr/upstream/stx/specs$ > > > > > > It seems I do not have permissions to push changes to starlingx/specs repo. > > May I know how to get the correct permissions for this repo ? > > > > > > Thanks & Regards, > > VSR > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.starlingx.io > > _cgi-2Dbin_mailman_listinfo_starlingx- > 2Ddiscuss&d=DwIFaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=XkP_75lnbPIeeucsPX36 > ZgjiMqEKttwZfwNyWMCLjT0&m=iruTD9nn948bOeoNEZjYy- > orLT6cmshvWDAKQm-rPNcgkP-9D-0damTf77KC- > h1l&s=4zFHw6hnzhXw3BTURPfAD1U4WZ4BI32XBya-Hcq4-l8&e= From vburru at marvell.com Sat Jul 2 00:12:36 2022 From: vburru at marvell.com (Veerasenareddy Burru) Date: Sat, 2 Jul 2022 00:12:36 +0000 Subject: [Starlingx-discuss] [EXT] Re: unable to push new spec to starlingx/specs In-Reply-To: References: Message-ID: > -----Original Message----- > From: Veerasenareddy Burru > Sent: Friday, July 1, 2022 5:10 PM > To: Ildiko Vancsa > Cc: starlingx-discuss at lists.starlingx.io > Subject: RE: [EXT] Re: [Starlingx-discuss] unable to push new spec to > starlingx/specs > > > > > -----Original Message----- > > From: Ildiko Vancsa > > Sent: Friday, July 1, 2022 2:23 PM > > To: Veerasenareddy Burru > > Cc: starlingx-discuss at lists.starlingx.io > > Subject: [EXT] Re: [Starlingx-discuss] unable to push new spec to > > starlingx/specs > > Importance: Low > > > > External Email > > > > ---------------------------------------------------------------------- > > Hi, > > > > Thank you for submitting your spec for the 8.0 release cycle. > > > > Do you have your ssh key set up and uploaded to Gerrit as it is > > described > > here: https://urldefense.proofpoint.com/v2/url?u=https- > > 3A__docs.openstack.org_contributors_common_setup-2Dgerrit.html- > 23setup > > - > > 2Dssh- > > > 2Dkeys&d=DwIFaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=XkP_75lnbPIeeucsPX36Zgj > > iMqEKttwZfwNyWMCLjT0&m=iruTD9nn948bOeoNEZjYy- > orLT6cmshvWDAKQm- > > rPNcgkP-9D-0damTf77KC- > > h1l&s=kj5nUKcONcgjOVFOgbvdBAndIDbhk_otByaQKP6Ez5U&e= ? > > > > When you set up the ssh key, you should also update your git remote by > > using the following command: ?git remote add > > > ssh://vburru at review.opendev.org:29418/starlingx/specs.git' > > > > Does this help? > Hello Ildiko, > Thanks for your response. This did not help. Mainly, I am unable to clone > using ssh. Below command just stalls. > git clone "ssh://vburru at review.opendev.org:29418/starlingx/specs" && scp -p > -P 29418 vburru at review.opendev.org:hooks/commit-msg "specs/.git/hooks/" > > Below is the verbose log when I try just ssh: > vburru at sburla-PowerEdge-T630:/disk2/vsr/upstream/stx/tmp$ ssh -p 29418 > vburru at review.opendev.org -vv > OpenSSH_7.6p1 Ubuntu-4ubuntu0.6, OpenSSL 1.0.2n 7 Dec 2017 > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: /etc/ssh/ssh_config line 19: Applying options for * > debug2: resolving "review.opendev.org" port 29418 > debug2: ssh_connect_direct: needpriv 0 > debug1: Connecting to review.opendev.org [199.204.45.33] port 29418. > debug1: Connection established. > debug1: identity file /home/vburru/.ssh/id_rsa type 0 > debug1: key_load_public: No such file or directory > debug1: identity file /home/vburru/.ssh/id_rsa-cert type -1 > debug1: key_load_public: No such file or directory > debug1: identity file /home/vburru/.ssh/id_dsa type -1 > debug1: key_load_public: No such file or directory > debug1: identity file /home/vburru/.ssh/id_dsa-cert type -1 > debug1: key_load_public: No such file or directory > debug1: identity file /home/vburru/.ssh/id_ecdsa type -1 > debug1: key_load_public: No such file or directory > debug1: identity file /home/vburru/.ssh/id_ecdsa-cert type -1 > debug1: key_load_public: No such file or directory > debug1: identity file /home/vburru/.ssh/id_ed25519 type -1 > debug1: key_load_public: No such file or directory > debug1: identity file /home/vburru/.ssh/id_ed25519-cert type -1 > debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.6 > <<<<----- it stalls here. This could be due to my office VPN preventing it. I will check with my IT on this. > > Thanks & Regards, > VSR > > > > Best Regards, > > Ildik? > > > > > > > On Jul 1, 2022, at 14:12, Veerasenareddy Burru > > wrote: > > > > > > Hi, > > > > > > I am able to push the change with the password generated using > > > ?generate > > new password? option below ?HTTP credentials? in gerrit settings page. > > > How can I set HTTP password to something of my choice ? > > > > > > Thanks & Regards, > > > VSR. > > > > > > From: Veerasenareddy Burru > > > Sent: Friday, July 1, 2022 2:07 PM > > > To: starlingx-discuss at lists.starlingx.io > > > Subject: unable to push new spec to starlingx/specs > > > > > > Hi, > > > > > > I have followed the process listed in below page to push new spec file. > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.starlingx. > > > io > > > _developer-5Fresources_code-2Dsubmission- > > 2Dguide.html&d=DwIFaQ&c=nKjWe > > > > > > c2b6R0mOyPaz7xtfQ&r=XkP_75lnbPIeeucsPX36ZgjiMqEKttwZfwNyWMCLjT0&m > > =iruT > > > D9nn948bOeoNEZjYy-orLT6cmshvWDAKQm-rPNcgkP-9D-0damTf77KC- > > h1l&s=8Io0b6K > > > Z41uQtSKCYQ6IJafOM7lJG-64dUP0slmI6kk&e= > > > > > > It is failing with below error: > > > > > > vburru at PowerEdge-T630:/disk2/vsr/upstream/stx/specs$ git push origin > > > HEAD:refs/for/master --verbose Pushing to > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev. > > > or > > > > > > g_starlingx_specs&d=DwIFaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=XkP_75lnbPIee > > ucs > > > PX36ZgjiMqEKttwZfwNyWMCLjT0&m=iruTD9nn948bOeoNEZjYy- > > orLT6cmshvWDAKQm-r > > > PNcgkP-9D-0damTf77KC-h1l&s=Z_08ZKmrD8g4c_OnO-Y1SGLtYt3Y6EtNYJ5s- > > d2Cs3w > > > &e= Username for > > > 'https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev > > > .o > > > > > > rg&d=DwIFaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=XkP_75lnbPIeeucsPX36ZgjiMqE > > KttwZfwNyWMCLjT0&m=iruTD9nn948bOeoNEZjYy-orLT6cmshvWDAKQm- > > rPNcgkP-9D-0damTf77KC- > > h1l&s=sPuDxhUPmpKDyVX0GhRPcRA8Gk342LdDGvGisc7EZ3Q&e= ': vburru > > Password for > > 'https://urldefense.proofpoint.com/v2/url?u=https-3A__vburru- > > > 40review.opendev.org&d=DwIFaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=XkP_75ln > > bPIeeucsPX36ZgjiMqEKttwZfwNyWMCLjT0&m=iruTD9nn948bOeoNEZjYy- > > orLT6cmshvWDAKQm-rPNcgkP-9D-0damTf77KC-h1l&s=OWxwYqCSfD0H_R- > > dTeh-jN1IYXFBjgw_JSwrrubUVlc&e= ': > > > remote: Unauthorized > > > fatal: Authentication failed for > > 'https://urldefense.proofpoint.com/v2/url?u=https- > > > 3A__review.opendev.org_starlingx_specs_&d=DwIFaQ&c=nKjWec2b6R0mOyPa > > > z7xtfQ&r=XkP_75lnbPIeeucsPX36ZgjiMqEKttwZfwNyWMCLjT0&m=iruTD9nn948 > > bOeoNEZjYy-orLT6cmshvWDAKQm-rPNcgkP-9D-0damTf77KC-h1l&s=ceQ2f7- > > rRS0SjW7uwq20xOhw9cz2CZZTTk6yJySbsqI&e= ' > > > vburru@ PowerEdge-T630:/disk2/vsr/upstream/stx/specs$ > > > > > > > > > It seems I do not have permissions to push changes to starlingx/specs > repo. > > > May I know how to get the correct permissions for this repo ? > > > > > > > > > Thanks & Regards, > > > VSR > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.starlingx. > > > io > > > _cgi-2Dbin_mailman_listinfo_starlingx- > > > 2Ddiscuss&d=DwIFaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=XkP_75lnbPIeeucsPX36 > > ZgjiMqEKttwZfwNyWMCLjT0&m=iruTD9nn948bOeoNEZjYy- > > orLT6cmshvWDAKQm-rPNcgkP-9D-0damTf77KC- > > h1l&s=4zFHw6hnzhXw3BTURPfAD1U4WZ4BI32XBya-Hcq4-l8&e= From starlingx.build at gmail.com Sat Jul 2 02:10:05 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Fri, 1 Jul 2022 22:10:05 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 2900 - Failure! Message-ID: <1272359118.19.1656727808440.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 2900 Status: Failure Timestamp: 20220702T020719Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20220702T013001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20220702T013001Z DOCKER_BUILD_ID: jenkins-master-compiler-20220702T013001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20220702T013001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20220702T013001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From starlingx.build at gmail.com Sat Jul 2 02:10:12 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Fri, 1 Jul 2022 22:10:12 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 983 - Failure! Message-ID: <1464275811.22.1656727813305.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 983 Status: Failure Timestamp: 20220702T013001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20220702T013001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From ildiko.vancsa at gmail.com Sat Jul 2 03:10:32 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 1 Jul 2022 20:10:32 -0700 Subject: [Starlingx-discuss] [EXT] unable to push new spec to starlingx/specs In-Reply-To: References: Message-ID: <5066E5A1-92E3-47AC-A536-D1F63494ECB0@gmail.com> >>> [?] >>> Does this help? >> Hello Ildiko, >> Thanks for your response. This did not help. Mainly, I am unable to clone >> using ssh. Below command just stalls. >> git clone "ssh://vburru at review.opendev.org:29418/starlingx/specs" && scp -p >> -P 29418 vburru at review.opendev.org:hooks/commit-msg "specs/.git/hooks/" >> >> Below is the verbose log when I try just ssh: >> vburru at sburla-PowerEdge-T630:/disk2/vsr/upstream/stx/tmp$ ssh -p 29418 >> vburru at review.opendev.org -vv >> OpenSSH_7.6p1 Ubuntu-4ubuntu0.6, OpenSSL 1.0.2n 7 Dec 2017 >> debug1: Reading configuration data /etc/ssh/ssh_config >> debug1: /etc/ssh/ssh_config line 19: Applying options for * >> debug2: resolving "review.opendev.org" port 29418 >> debug2: ssh_connect_direct: needpriv 0 >> debug1: Connecting to review.opendev.org [199.204.45.33] port 29418. >> debug1: Connection established. >> debug1: identity file /home/vburru/.ssh/id_rsa type 0 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/vburru/.ssh/id_rsa-cert type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/vburru/.ssh/id_dsa type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/vburru/.ssh/id_dsa-cert type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/vburru/.ssh/id_ecdsa type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/vburru/.ssh/id_ecdsa-cert type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/vburru/.ssh/id_ed25519 type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/vburru/.ssh/id_ed25519-cert type -1 >> debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.6 >> <<<<----- it stalls here. > This could be due to my office VPN preventing it. I will check with my IT on this. I just tried and I could clone the specs repo through ssh. Since your command stalled and didn?t give an error message I can?t tell what might be the issue on your end. Office firewall and VPN settings can indeed cause problems like the above. I hope IT can help you figure it out. If they find everything alright then we can keep looking into what the actual error message is and what might be causing it. In the meantime someone here might ran into the same or similar issue before and has some more ideas. Best Regards, Ildik? >> >> [?] From Ghada.Khalil at windriver.com Sun Jul 3 21:12:33 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sun, 3 Jul 2022 21:12:33 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Jun 29/2022 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Sanity - Last Update: The current plan to restart work on enabling sanity in 2wks by June 29. Then can start building a plan at that time. - Starting on WR sanity setup today: June 29. - Action: Rob to provide further details on the plan/status in the next community call: July 6 - Sanity Recommendations - Run sanity w/o openstack to start. See note below about openstack not workng w/ k8s 1.23 / FluxCD - Backup plan: Run sanity w/ openstack & k8s 1.21 stx.7.0 - Release/Feature Planning: https://docs.google.com/spreadsheets/d/171PJAu9SykXm9h9Ny2IsZ8YMbhvEwOzuTbISWUMQhiE/edit#gid=1107209846 - Release Verification: - Folder: https://drive.google.com/drive/folders/1szAP-xVZq7ebSyGJ-EHTVebMmsupSY7w - Feature Testing: https://docs.google.com/spreadsheets/d/1hXJJ4LvxhWwLIF_PHpCyxlGpfKdXtcPjlyclfKFVxKo/edit#gid=968103774 - Regression Testing: https://docs.google.com/spreadsheets/d/19OQmmo5OfD1eHS8rp5uBgnVaS7i8J-NhQuiKVqcyZ0Y/edit#gid=1717644237 - Release Updates - Feature Code & Test Update - Feature status updated in the planning spreadsheet. - 37 features are complete. - 1 feature deferred to stx.8.0 -- FEC Device Configurability (fec-operator Integration) - Team was still having build issues, so will not hold up stx.7.0 and will continue this in stx.8.0 - Bug status - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.7.0 - In good shape. - 3 LPs open: 1 related to the last sanity done by Intel. 1 related to docs. 1 looks to be fixed and needs updating. - Key Note: stx-openstack does not apply/work on k8s 1.23 which is the default k8s version in stx.7.0 - The dependency may also be related to the Armada deprecation. openstack was not moved to FluxCD. - From Greg: this is on the openstack team's radar for stx.8.0. Action: Greg to follow up on storyboards for stx.8.0 tracking - Will likely need to release stx.7.0 without openstack support. Decision pending sanity results. - Branch Creation - Pending sanity - earliest would be the week of July 11 - Milestone Re-forecast - Can still make the current dates (or close to them) if we have sanity running by July 8 - RC1 (Branch Creation): week of July 4 >> week of July 11 - Final Regression: week of July 18 - Release: week of July 25 - Docs - Most doc updates are done. A few reviews still left to merge; trying to close these today: June 29. - Plan to start working on the release notes next week. stx.8.0 - Need to start planning - Action: Ghada to create a Release/Feature Planning spreadsheet for the next release meeting: July 13 - spec structure is already created. From Ghada.Khalil at windriver.com Sun Jul 3 21:19:09 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sun, 3 Jul 2022 21:19:09 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Jun 29 2022) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call June 29 2022 Standing Topics - Build - CentOS builds - No build issues for the last week - Fixed an issue w/ CentOS mirror - Debian builds - 2 builds failed out of 7; one related to a network glitch and the other one is related to glitch during publication. - Need to confirm that build errors for Debian are being published to the mailing list correctly. - New upstream Debian release (11.4) is being released - Build & OS team are working to ensure stx stays on 11.3 - Reviews in progress: - https://review.opendev.org/c/starlingx/tools/+/839126 - https://review.opendev.org/c/starlingx/root/+/844816 - Sanity - Starting on WR sanity setup today: June 29. - Action: Rob to provide further details on the plan/status in the next community call: July 6 - Gerrit Reviews in Need of Attention - Debian release lock-down reviews -- Author: Yue Tao / Reviewers: Scott Little / Davlet Panech - urgent to ensure we don't move to Debian 11.4 prematurely - https://review.opendev.org/c/starlingx/tools/+/839126 - https://review.opendev.org/c/starlingx/root/+/844816 - Layer Build Fixes encountered in developer environment -- Author: Chant Yu / Reviewers: Scott Little / Davlet Panech - https://review.opendev.org/c/starlingx/tools/+/846573 - https://review.opendev.org/c/starlingx/tools/+/846846 - https://review.opendev.org/c/starlingx/containers/+/847231 - https://review.opendev.org/c/starlingx/tools/+/847066 - https://review.opendev.org/c/starlingx/tools/+/847061 - Reference Links: - Active Branch (open): https://review.opendev.org/q/projects:starlingx+is:open+branch:+master - Active Branch (merged): https://review.opendev.org/q/projects:starlingx+is:merged+branch:master Topics for This Week - stx.7.0 Release Status - 37 features are complete. 1 feature deferred to stx.8.0 -- FEC Device Configurability (fec-operator Integration) - Further milestones are pending successful sanity setup - Upcoming Milestones - RC1 (Branch Creation): week of July 4 >> week of July 11 -- assuming sanity is running by July 8 - Final Regression: week of July 18 (no change) - Release: week of July 25 (no change) - Edge infrastructure orchestration discussion with the edge WG - Email from Ildiko / Raised by Steve Geary - http://lists.starlingx.io/pipermail/starlingx-discuss/2022-June/013095.html - Meeting is scheduled for July 18 at 6am US Pacific time - StarlingX should look to participate in this conversation - specifically share challenges and collaborate with this neighbor community - Action: Identify participants in the next community meeting ARs from Previous Meetings - Follow-up on issues reported from the last sanity - https://bugs.launchpad.net/starlingx/+bug/1970645 - Stx-openstack apply timeout because some pods are not ready - Team has an idea on how to fix, but are not able to reproduce to validate fix. - Discussed waiting to see if the issue is reproduced in the WR sanity env which is being setup starting this week - https://bugs.launchpad.net/starlingx/+bug/1975921 - Provision failed: IndexError: Given index 0 is out of the range 0--1 - Appears to be an automation issue, not a starlingx software issue Open Requests for Help - Error adding subcloud: http://lists.starlingx.io/pipermail/starlingx-discuss/2022-June/013094.html - Action: RamS to review and follow-up - docker vs cri-io: http://lists.starlingx.io/pipermail/starlingx-discuss/2022-June/013096.html - Action: Greg to reply - Incorrect public key for signed starlingX 5.0 iso: http://lists.starlingx.io/pipermail/starlingx-discuss/2022-June/013072.html - Action: Greg to reply From starlingx.build at gmail.com Sun Jul 3 02:09:35 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 2 Jul 2022 22:09:35 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 2901 - Still Failing! In-Reply-To: <261425644.17.1656727802332.JavaMail.javamailuser@localhost> References: <261425644.17.1656727802332.JavaMail.javamailuser@localhost> Message-ID: <1795495443.27.1656814177054.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 2901 Status: Still Failing Timestamp: 20220703T020656Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20220703T013001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20220703T013001Z DOCKER_BUILD_ID: jenkins-master-compiler-20220703T013001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20220703T013001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20220703T013001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From yatindra.shashi at intel.com Sun Jul 3 21:04:56 2022 From: yatindra.shashi at intel.com (Shashi, Yatindra) Date: Sun, 3 Jul 2022 21:04:56 +0000 Subject: [Starlingx-discuss] Failed to boot controller-1 using PXE with connection timeout reading initrd file - STX 5.0.1-duplex Message-ID: Hi Team, I am trying to install starlingX 5.0.1 Duplex in my setup where I had running stx 5.0.1 before. Controller-0 installation and configuration works perfectly. I can see my controller-0 active and configured properly. After that I tried to install controller-1 and select PXE boot at controller-1. I change the personality of node from the controller-0 of new node as controller-1 and controller-1 start to load but it fails on loading initrd file from controller-0 and stuck on that stage. Can any body suggest what could be reason? Mit freundlichen Gr??en/ with best regards, Yatindra Shashi Intel Deutschland GmbH Registered Address: Am Campeon 10, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Sun Jul 3 02:09:39 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 2 Jul 2022 22:09:39 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 984 - Still Failing! In-Reply-To: <2021826663.20.1656727809534.JavaMail.javamailuser@localhost> References: <2021826663.20.1656727809534.JavaMail.javamailuser@localhost> Message-ID: <620630723.30.1656814179820.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 984 Status: Still Failing Timestamp: 20220703T013001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20220703T013001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From starlingx.build at gmail.com Sun Jul 3 23:39:08 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sun, 3 Jul 2022 19:39:08 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 2902 - Still Failing! In-Reply-To: <964592551.25.1656814172202.JavaMail.javamailuser@localhost> References: <964592551.25.1656814172202.JavaMail.javamailuser@localhost> Message-ID: <1615826587.37.1656891550832.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 2902 Status: Still Failing Timestamp: 20220703T233624Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20220703T230001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20220703T230001Z DOCKER_BUILD_ID: jenkins-master-compiler-20220703T230001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20220703T230001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20220703T230001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From starlingx.build at gmail.com Sun Jul 3 23:39:12 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sun, 3 Jul 2022 19:39:12 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 985 - Still Failing! In-Reply-To: <1969835557.28.1656814177699.JavaMail.javamailuser@localhost> References: <1969835557.28.1656814177699.JavaMail.javamailuser@localhost> Message-ID: <1821670004.40.1656891553820.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 985 Status: Still Failing Timestamp: 20220703T230001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20220703T230001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From Greg.Waines at windriver.com Mon Jul 4 12:30:16 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 4 Jul 2022 12:30:16 +0000 Subject: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . In-Reply-To: References: Message-ID: Hey Chandan, Thanks for bringing this up. I chatted with Scott about this. Currently the StarlingX public builds on CENGN are not building a secure boot capable load ? i.e. signing the appropriate items to enable secure boot. Although the StarlingX build infrastructure allows it to be added. Neither of these points are properly documented in docs.starlingx.io ? I can?t remember the details of why we are not doing this. I am guessing that the thinking was that a user of StarlingX that wanted to use UEFI Secure Boot, would want to sign with his own private key. Can you raise a starlingx launchpad ( https://launchpad.net/starlingx ) to address the docs.starlingx.io documentation issue, i.e. to indicate that the StarlingX CENGN builds are not signed to support uefi secure boot, and describe how a starlingx user could add signing to their StarlingX build environment in order to sign for uefi secure boot with their own private key ? Greg. From: Scott Little Sent: Wednesday, June 29, 2022 10:42 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . On 2022-06-02 13:12, Kumar, Chandan wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I am trying to validate signed starlingX 5.0 iso on a secureboot enabled setup against public key(TiBoot.crt) embedded inside iso. After rebooting , operating system is not coming up with error screen saying ?Verification failed: (0X1A) Security Violation?. However, when I signed images with self-generated private key and validated against corresponding public key, system is able to boot up successfully. Signing is done after flashing the iso on a server. Please find attached procedure for signing images inside iso. I believe, the public key provided with iso is not correct. Can you please confirm ? Regards, Chandan Kumar. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss Thanks for the report. I'll look into it Scott Little -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Mon Jul 4 13:34:43 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 4 Jul 2022 13:34:43 +0000 Subject: [Starlingx-discuss] docker vs cri-o / centos vs alma / silverblue / coreos In-Reply-To: <1656406485704.742713062.1917902131@optimcloud.com> References: <1656406485704.742713062.1917902131@optimcloud.com> Message-ID: See in-lined comments below, Greg. -----Original Message----- From: Embedded Devel Sent: Tuesday, June 28, 2022 5:01 AM To: StarlingX ML Subject: [Starlingx-discuss] docker vs cri-o / centos vs alma / silverblue / coreos [Please note: This e-mail is from an EXTERNAL e-mail address] can i ask if there is a plan to remove docker moving forward in favor of cri-o? as we know k8s 1.24.+ drops docker support unless using the docker-shim > [Greg] > StarlingX's default container runtime is containerd > (StarlingX switched from docker container runtime to containerd several releases ago ... can't remember exactly ... but quite a while ago. ) > > There are no specific plans for cri-o container runtime at the moment. > It is on StarlingX's wish list of things to investigate > preferably we have already tested and run k8s / openstack-helm via crio so we know it works curious how this applies to starlingx V7 and higher? > [Greg] > its containerd runtime for StarlingX R7 and the immediate future > further to that are there plans aside from CentOS to move the rpm base to say Alma or CoreOS or Silverblue even. (both are ostree based) as Ive seen the debian build deploying with ostree onboard? or is the plan to drop rpm based distros long term and just run with debian ? > [Greg] > Starlingx is moving to Yocto Kernel, Debian distro delivered with ostree. > https://docs.starlingx.io/specs/specs/stx-6.0/approved/starlingx_2008846_debian_build.html > https://docs.starlingx.io/specs/specs/stx-6.0/approved/starlingx_2008704_debian_transition.html > > the specs were written in R6 timeframe, > initial work is being done in R7 timeframe, with a Debian Preview (with lots of limitations ... e.g. only the kubernetes platform and not stx-openstack is supported on Debian) is available in R7 ( https://docs.starlingx.io/debian/index-debian-introduction-8eb59cf0a062.html ) > NOTE for R7, the CentOS build is still the main StarlingX build > StarlingX will be transitioning completely to Debian in R8 timeframe ... i.e. CentOS builds will be removed. We have deployed magmacore on stx 6.0 and are in the process of upgrading the infrastructure. My curiosities exists as whats the starling X impact going to be long term, as I would like to put all my eggs in this basket. > [Greg] > > Good to hear ? . > The more you can share about your use case (and what capabilities of StarlingX you rely on) the better, so we can make informed decisions on StarlingX's evolution. > I'd also encourage you to attend StarlingX Release Meetings, Community Meetings and even PTG meetings in order to understand and provide input on the direction of StarlingX. > > Greg. -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From outbackdingo at gmail.com Mon Jul 4 13:58:37 2022 From: outbackdingo at gmail.com (Outback Dingo) Date: Mon, 4 Jul 2022 20:58:37 +0700 Subject: [Starlingx-discuss] docker vs cri-o / centos vs alma / silverblue / coreos In-Reply-To: References: <1656406485704.742713062.1917902131@optimcloud.com> Message-ID: On Mon, Jul 4, 2022 at 8:43 PM Waines, Greg wrote: > > > [Greg] > > StarlingX's default container runtime is containerd > > (StarlingX switched from docker container runtime to containerd several releases ago ... can't remember exactly ... but quite a while ago. ) > > > > There are no specific plans for cri-o container runtime at the moment. > > It is on StarlingX's wish list of things to investigate > > thats good to know at least. > further to that are there plans aside from CentOS to move the rpm base to say Alma or CoreOS or Silverblue even. (both are ostree based) as Ive seen the debian build deploying with ostree onboard? or is the plan to drop rpm based distros long term and just run with debian ? > > > [Greg] > > Starlingx is moving to Yocto Kernel, Debian distro delivered with ostree. > > https://docs.starlingx.io/specs/specs/stx-6.0/approved/starlingx_2008846_debian_build.html > > https://docs.starlingx.io/specs/specs/stx-6.0/approved/starlingx_2008704_debian_transition.html > > > > the specs were written in R6 timeframe, > > initial work is being done in R7 timeframe, with a Debian Preview (with lots of limitations ... e.g. only the kubernetes platform and not stx-openstack is supported on Debian) is available in R7 ( https://docs.starlingx.io/debian/index-debian-introduction-8eb59cf0a062.html ) > > NOTE for R7, the CentOS build is still the main StarlingX build > > StarlingX will be transitioning completely to Debian in R8 timeframe ... i.e. CentOS builds will be removed. > > Welp, that kills our use case for upgrading, first we need openstack-helm in the mix, second it sounds like it will be a fork-life upgrade, not backwards compatible seeing as the os changed from CentOS to Debian Im familiar with yocto, so at least bring ostree into the mix is a good idea. > > > We have deployed magmacore on stx 6.0 and are in the process of upgrading the infrastructure. > My curiosities exists as whats the starling X impact going to be long term, as I would like to put all my eggs in this basket. > > > [Greg] > > > > Good to hear ? . > > The more you can share about your use case (and what capabilities of StarlingX you rely on) the better, so we can make informed decisions on StarlingX's evolution. > > I'd also encourage you to attend StarlingX Release Meetings, Community Meetings and even PTG meetings in order to understand and provide input on the direction of StarlingX. LOL Wind River should just hire me to work on STX full-time. I can say im not 100% happy about the dropping of CentOS, in lieu of an Os change to CoreOs, or other, Yocto/Debian is nice but... thats a reinstall for sure. a good amount of interruption to prod environments and capex for new servers. > > Greg. > > > > -- > Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Greg.Waines at windriver.com Mon Jul 4 14:30:03 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 4 Jul 2022 14:30:03 +0000 Subject: [Starlingx-discuss] docker vs cri-o / centos vs alma / silverblue / coreos In-Reply-To: References: <1656406485704.742713062.1917902131@optimcloud.com> Message-ID: See in-lined below, Greg. -----Original Message----- From: Outback Dingo Sent: Monday, July 4, 2022 9:59 AM To: Waines, Greg Cc: Embedded Devel ; StarlingX ML Subject: Re: [Starlingx-discuss] docker vs cri-o / centos vs alma / silverblue / coreos [Please note: This e-mail is from an EXTERNAL e-mail address] On Mon, Jul 4, 2022 at 8:43 PM Waines, Greg wrote: > > > [Greg] > > StarlingX's default container runtime is containerd (StarlingX > > switched from docker container runtime to containerd several > > releases ago ... can't remember exactly ... but quite a while ago. ) > > > > There are no specific plans for cri-o container runtime at the moment. > > It is on StarlingX's wish list of things to investigate > > thats good to know at least. > further to that are there plans aside from CentOS to move the rpm base to say Alma or CoreOS or Silverblue even. (both are ostree based) as Ive seen the debian build deploying with ostree onboard? or is the plan to drop rpm based distros long term and just run with debian ? > > > [Greg] > > Starlingx is moving to Yocto Kernel, Debian distro delivered with ostree. > > https://docs.starlingx.io/specs/specs/stx-6.0/approved/starlingx_200 > > 8846_debian_build.html > > https://docs.starlingx.io/specs/specs/stx-6.0/approved/starlingx_200 > > 8704_debian_transition.html > > > > the specs were written in R6 timeframe, initial work is being done > > in R7 timeframe, with a Debian Preview (with lots of limitations ... e.g. only the kubernetes platform and not stx-openstack is supported on Debian) is available in R7 ( https://docs.starlingx.io/debian/index-debian-introduction-8eb59cf0a062.html ) > > NOTE for R7, the CentOS build is still the main StarlingX > > build StarlingX will be transitioning completely to Debian in R8 timeframe ... i.e. CentOS builds will be removed. > > Welp, that kills our use case for upgrading, first we need openstack-helm in the mix, second it sounds like it will be a fork-life upgrade, not backwards compatible seeing as the os changed from CentOS to Debian Im familiar with yocto, so at least bring ostree into the mix is a good idea. [Greg] I don't understand your comment [Greg] You could upgrade from STX R6 @ CentOS to STX R7 @ CentOS ... and then from STX R7 @ CentOS to STX R8 @ Debian [Greg] 'openstack-helm' is being used in all releases of STX > > > We have deployed magmacore on stx 6.0 and are in the process of upgrading the infrastructure. > My curiosities exists as whats the starling X impact going to be long term, as I would like to put all my eggs in this basket. > > > [Greg] > > > > Good to hear ? . > > The more you can share about your use case (and what capabilities of StarlingX you rely on) the better, so we can make informed decisions on StarlingX's evolution. > > I'd also encourage you to attend StarlingX Release Meetings, Community Meetings and even PTG meetings in order to understand and provide input on the direction of StarlingX. LOL Wind River should just hire me to work on STX full-time. I can say im not 100% happy about the dropping of CentOS, in lieu of an Os change to CoreOs, or other, Yocto/Debian is nice but... thats a reinstall for sure. a good amount of interruption to prod environments and capex for new servers. [Greg] You are very welcome to contribute to StarlingX independent of where you are actually working. [Greg] [Greg] You should be able to use StarlingX to support an upgrade from STX R7 @ CentOS to STX R8 @ Debian . [Greg] That is the plan ... the individuals working on StarlingX have experience on similar projects doing such an OS transition over an upgrade. [Greg] It will likely require you to build a PATCH for StarlingX R7 @ CentOS in order to get it to work. (design details TBD) [Greg] ( As you probably know, StarlingX CENGN build services does not build PATCHes. ) [Greg] [Greg] Greg. > > Greg. > > > > -- > Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From outbackdingo at gmail.com Mon Jul 4 15:26:47 2022 From: outbackdingo at gmail.com (Outback Dingo) Date: Mon, 4 Jul 2022 22:26:47 +0700 Subject: [Starlingx-discuss] docker vs cri-o / centos vs alma / silverblue / coreos In-Reply-To: References: <1656406485704.742713062.1917902131@optimcloud.com> Message-ID: On Mon, Jul 4, 2022 at 9:30 PM Waines, Greg wrote: > > See in-lined below, > Greg. > > -----Original Message----- > From: Outback Dingo > Sent: Monday, July 4, 2022 9:59 AM > To: Waines, Greg > Cc: Embedded Devel ; StarlingX ML > Subject: Re: [Starlingx-discuss] docker vs cri-o / centos vs alma / silverblue / coreos > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > On Mon, Jul 4, 2022 at 8:43 PM Waines, Greg wrote: > > > > > > [Greg] > > > StarlingX's default container runtime is containerd (StarlingX > > > switched from docker container runtime to containerd several > > > releases ago ... can't remember exactly ... but quite a while ago. ) > > > > > > There are no specific plans for cri-o container runtime at the moment. > > > It is on StarlingX's wish list of things to investigate > > > > > thats good to know at least. > > > > further to that are there plans aside from CentOS to move the rpm base to say Alma or CoreOS or Silverblue even. (both are ostree based) as Ive seen the debian build deploying with ostree onboard? or is the plan to drop rpm based distros long term and just run with debian ? > > > > > [Greg] > > > Starlingx is moving to Yocto Kernel, Debian distro delivered with ostree. > > > https://docs.starlingx.io/specs/specs/stx-6.0/approved/starlingx_200 > > > 8846_debian_build.html > > > https://docs.starlingx.io/specs/specs/stx-6.0/approved/starlingx_200 > > > 8704_debian_transition.html > > > > > > the specs were written in R6 timeframe, initial work is being done > > > in R7 timeframe, with a Debian Preview (with lots of limitations ... e.g. only the kubernetes platform and not stx-openstack is supported on Debian) is available in R7 ( https://docs.starlingx.io/debian/index-debian-introduction-8eb59cf0a062.html ) > > > NOTE for R7, the CentOS build is still the main StarlingX > > > build StarlingX will be transitioning completely to Debian in R8 timeframe ... i.e. CentOS builds will be removed. > > > > > > Welp, that kills our use case for upgrading, first we need openstack-helm in the mix, second it sounds like it will be a fork-life upgrade, not backwards compatible seeing as the os changed from CentOS to Debian Im familiar with yocto, so at least bring ostree into the mix is a good idea. > > [Greg] I don't understand your comment > [Greg] You could upgrade from STX R6 @ CentOS to STX R7 @ CentOS ... and then from STX R7 @ CentOS to STX R8 @ Debian > [Greg] 'openstack-helm' is being used in all releases of STX > where you mentioned "not stx-openstack is supported on Debian" i took it to mean by STX R8 openstack-helm would be dropped in the transition from CentOS to Debian. > > LOL Wind River should just hire me to work on STX full-time. I can say im not 100% happy about the dropping of CentOS, in lieu of an Os change to CoreOs, or other, Yocto/Debian is nice but... thats a reinstall for sure. a good amount of interruption to prod environments and capex for new servers. > > [Greg] You are very welcome to contribute to StarlingX independent of where you are actually working. > [Greg] > [Greg] You should be able to use StarlingX to support an upgrade from STX R7 @ CentOS to STX R8 @ Debian . > [Greg] That is the plan ... the individuals working on StarlingX have experience on similar projects doing such an OS transition over an upgrade. > [Greg] It will likely require you to build a PATCH for StarlingX R7 @ CentOS in order to get it to work. (design details TBD) > [Greg] ( As you probably know, StarlingX CENGN build services does not build PATCHes. ) > [Greg] > [Greg] Greg. > > > > Greg. > > > > > > > > -- > > Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Juanita.Balaraj at windriver.com Mon Jul 4 16:12:38 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Mon, 4 Jul 2022 16:12:38 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 29-June-22 Message-ID: Hello all, Here are last 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 ============ 29-June-22 - Stx 7.0 GA date is July 25th https://docs.google.com/spreadsheets/d/171PJAu9SykXm9h9Ny2IsZ8YMbhvEwOzuTbISWUMQhiE/edit#gid=0 - Need to update the Installation Guide to display Stx 7.0 once docs are merged : https://docs.starlingx.io/deploy_install_guides/index-install-e083ca818006.html - AR Ron - Version drop-down on https://docs.starlingx.io/ to be updated to display Stx 7.0 - AR Ron - Stx Release Notes - AR Juanita - To automate the updates for the Introduction Guide - AR Ron - Scott to cut the Stx 7.0 docs branch - To confirm the date - Team reviewed open Gerrit reviews and cherry pick / merged - Team to address LP Bugs - https://bugs.launchpad.net/starlingx/+bug/1932314; https://bugs.launchpad.net/starlingx/+bug/1951165 - AR Elaine to close these bugs - https://bugs.launchpad.net/starlingx/+bug/1972748 - Fixed - AR Elisa - Introduction Guide to be updated with new features for Stx 7.0 - Team and pulled in from STx 7.0 Release Notes - Ron to automate it - Planning Guide - To be updated with any new requirements for Stx 7.0 - Done by Oliver - TAI clock updates - Juanita to discuss with Ghada regarding https://storyboard.openstack.org/#!/story/2010033 - Operations Guide Archive - On Hold until further clarifications are discussed - https://review.opendev.org/c/starlingx/docs/+/82203 - https://review.opendev.org/c/starlingx/docs/+/848117 - Elisa to pick dsr6 _______________________________________________ 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 Mon Jul 4 23:39:43 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Mon, 4 Jul 2022 19:39:43 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 986 - Still Failing! In-Reply-To: <561358586.38.1656891551534.JavaMail.javamailuser@localhost> References: <561358586.38.1656891551534.JavaMail.javamailuser@localhost> Message-ID: <1686805983.49.1656977984588.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 986 Status: Still Failing Timestamp: 20220704T230001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20220704T230001Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From starlingx.build at gmail.com Mon Jul 4 23:39:40 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Mon, 4 Jul 2022 19:39:40 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 2903 - Still Failing! In-Reply-To: <1910366320.35.1656891546668.JavaMail.javamailuser@localhost> References: <1910366320.35.1656891546668.JavaMail.javamailuser@localhost> Message-ID: <1345921878.46.1656977981223.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 2903 Status: Still Failing Timestamp: 20220704T233651Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20220704T230001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20220704T230001Z DOCKER_BUILD_ID: jenkins-master-compiler-20220704T230001Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20220704T230001Z/logs BUILD_IMG: false FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20220704T230001Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From Chandan.Kumar at commscope.com Tue Jul 5 07:19:10 2022 From: Chandan.Kumar at commscope.com (Kumar, Chandan) Date: Tue, 5 Jul 2022 07:19:10 +0000 Subject: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . In-Reply-To: References: Message-ID: Hi Greg, Thanks for acknowledgement. I have raised starlingx launchpad for document update. Meanwhile it would be really great if you can share the steps which has to be done to integrate signing of images as part of StarlingX build infrastructure. Regards, Chandan Kumar. From: Waines, Greg Sent: Monday, July 4, 2022 6:00 PM To: starlingx-discuss at lists.starlingx.io Cc: Little, Scott Subject: Re: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . Hey Chandan, Thanks for bringing this up. I chatted with Scott about this. Currently the StarlingX public builds on CENGN are not building a secure boot capable load ? i.e. signing the appropriate ite External (greg.waines at windriver.com) Report This Email FAQ Protection by INKY Hey Chandan, Thanks for bringing this up. I chatted with Scott about this. Currently the StarlingX public builds on CENGN are not building a secure boot capable load ? i.e. signing the appropriate items to enable secure boot. Although the StarlingX build infrastructure allows it to be added. Neither of these points are properly documented in docs.starlingx.io ? I can?t remember the details of why we are not doing this. I am guessing that the thinking was that a user of StarlingX that wanted to use UEFI Secure Boot, would want to sign with his own private key. Can you raise a starlingx launchpad ( https://launchpad.net/starlingx ) to address the docs.starlingx.io documentation issue, i.e. to indicate that the StarlingX CENGN builds are not signed to support uefi secure boot, and describe how a starlingx user could add signing to their StarlingX build environment in order to sign for uefi secure boot with their own private key ? Greg. From: Scott Little > Sent: Wednesday, June 29, 2022 10:42 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . On 2022-06-02 13:12, Kumar, Chandan wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I am trying to validate signed starlingX 5.0 iso on a secureboot enabled setup against public key(TiBoot.crt) embedded inside iso. After rebooting , operating system is not coming up with error screen saying ?Verification failed: (0X1A) Security Violation?. However, when I signed images with self-generated private key and validated against corresponding public key, system is able to boot up successfully. Signing is done after flashing the iso on a server. Please find attached procedure for signing images inside iso. I believe, the public key provided with iso is not correct. Can you please confirm ? Regards, Chandan Kumar. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss Thanks for the report. I'll look into it Scott Little -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Jul 5 17:29:03 2022 From: scott.little at windriver.com (Scott Little) Date: Tue, 5 Jul 2022 13:29:03 -0400 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_compiler_master_master - Build # 983 - Failure! In-Reply-To: <1464275811.22.1656727813305.JavaMail.javamailuser@localhost> References: <1464275811.22.1656727813305.JavaMail.javamailuser@localhost> Message-ID: <2f1aa101-423a-1ddf-27e6-6e83d198945a@windriver.com> Compiler layer build failure is due to missing dependency for new package 'expat' Launchpad: https://bugs.launchpad.net/starlingx/+bug/1980674 Fixed by: https://review.opendev.org/c/starlingx/tools/+/848756 Scott On 2022-07-01 22:10, starlingx.build at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_layer_compiler_master_master > Build #: 983 > Status: Failure > Timestamp: 20220702T013001Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20220702T013001Z/logs > -------------------------------------------------------------------------------- > Parameters > > FULL_BUILD: false > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From kennelson11 at gmail.com Tue Jul 5 20:44:59 2022 From: kennelson11 at gmail.com (Kendall Nelson) Date: Tue, 5 Jul 2022 15:44:59 -0500 Subject: [Starlingx-discuss] Fwd: October 2022 PTG Dates & Registration In-Reply-To: References: Message-ID: Hello Everyone! As you may have seen, we announced the next PTG[1] which will take place October 17-20, 2022 in Columbus, Ohio! Registration is now open[2]. We have also secured a limited, discounted hotel block for PTG attendees [3]. If your organization is interested in sponsoring the event, information on packages and pricing are now available on the PTG website [1] or feel free to reach out directly to ptg at openinfra.dev. Can't wait to SEE you all there! -Kendall Nelson (diablo_rojo) [1] https://openinfra.dev/ptg/ [2] https://openinfra-ptg.eventbrite.com/ [3] https://www.hyatt.com/en-US/group-booking/CMHRC/G-L0RT -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Wed Jul 6 08:55:38 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 6 Jul 2022 04:55:38 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_installer - Build # 1376 - Failure! Message-ID: <39004091.58.1657097746129.JavaMail.javamailuser@localhost> Project: STX_build_installer Build #: 1376 Status: Failure Timestamp: 20220706T085124Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220706T043001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20220706T043001Z DOCKER_BUILD_ID: jenkins-master-20220706T043001Z-builder OS: centos PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220706T043001Z/logs MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20220706T043001Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From starlingx.build at gmail.com Wed Jul 6 08:55:50 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 6 Jul 2022 04:55:50 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1340 - Failure! Message-ID: <1150911764.61.1657097751831.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1340 Status: Failure Timestamp: 20220706T043001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220706T043001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From Juanita.Balaraj at windriver.com Wed Jul 6 20:06:07 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Wed, 6 Jul 2022 20:06:07 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 06-July-22 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 ============ 06-July-22 - Stx 7.0 GA date is July 25th https://docs.google.com/spreadsheets/d/171PJAu9SykXm9h9Ny2IsZ8YMbhvEwOzuTbISWUMQhiE/edit#gid=0 - Need to update the Installation Guide to display Stx 7.0 once docs are merged - Version drop-down on https://docs.starlingx.io/ to be updated to display Stx 7.0 - Stx Release Notes - Feature content be reused in the Introduction Guide - Stx 7.0 docs branch to be cut for Docs - No Cherry picks this week - Received a new LP Doc Bug - See https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs for a list of pending Doc Bugs - Introduction Guide to be updated with new features for Stx 7.0 - TAI clock updates - not in the Storyboard list; https://storyboard.openstack.org/#!/story/2010033 - Operations Guide Archive - On Hold until further clarifications are discussed - https://review.opendev.org/c/starlingx/docs/+/822030 - Glossary File to keep it current; https://review.opendev.org/c/starlingx/docs/+/848772 _______________________________________________ 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 Wed Jul 6 20:21:55 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 6 Jul 2022 20:21:55 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (July 6 2022) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call July 6 2022 Standing Topics - Build - CentOS builds - One build issue due to a recent code submission (expat CVE fix): https://bugs.launchpad.net/starlingx/+bug/1980838 - This is only affecting the monolithic installer build. - We are still getting successful layered builds in CENGN. - Developers can still do monolithic builds if they don't build the installer. - Debian builds - Not affected by the above expat issue. Had 4 successful builds. - New upstream Debian release (11.4) is being released - Build & OS team are working to ensure stx stays on 11.3 - Reviews in progress: - https://review.opendev.org/c/starlingx/tools/+/839126 - https://review.opendev.org/c/starlingx/root/+/844816 - Bob Church is suggesting we get a developer build w/ those reviews before they merge. Sanity - WR sanity setup is progressing well. Was able to install the stx load on a DX lab. - Expect to have a sanity report out this week - by July 8 - Note: The sanity suite is based on WR sanity suite, not the original sanity suite run by Intel. Hit technical issues running the original Intel suite. - Next week the goal is to try to run w/ stx-openstack pending fixes for: - https://bugs.launchpad.net/starlingx/+bug/1978409 - https://bugs.launchpad.net/starlingx/+bug/1980397 Gerrit Reviews in Need of Attention - From last week - Debian release lock-down reviews -- Author: Yue Tao / Reviewers: Scott Little / Davlet Panech - UPDATE: Reviews are still in progress, but appear active - urgent to ensure we don't move to Debian 11.4 prematurely - https://review.opendev.org/c/starlingx/tools/+/839126 - https://review.opendev.org/c/starlingx/root/+/844816 - Layered Build Fixes encountered in developer environment -- Author: Chant Yu / Reviewers: Scott Little / Davlet Panech - UPDATE: Some reviews merged, but others still have review comments to address. Trying to verify each one separately before merging. - https://review.opendev.org/c/starlingx/tools/+/846573 - https://review.opendev.org/c/starlingx/tools/+/846846 - https://review.opendev.org/c/starlingx/containers/+/847231 - https://review.opendev.org/c/starlingx/tools/+/847066 - https://review.opendev.org/c/starlingx/tools/+/847061 - Reference Links: - Active Branch (open): https://review.opendev.org/q/projects:starlingx+is:open+branch:+master - Active Branch (merged): https://review.opendev.org/q/projects:starlingx+is:merged+branch:master Topics for This Week - stx.7.0 Release Status - From the TSC meeting, agreed that getting stx-openstack running on stx.7.0 is a release blocker - Plans in place to address the identified issues and re-enable stx-openstack - Two key fixes required which are forecast for ~July 12 - https://bugs.launchpad.net/starlingx/+bug/1978409 - https://bugs.launchpad.net/starlingx/+bug/1980397 - Upcoming Milestones - Revised - RC1 (Branch Creation): week of July 4 >> week of July 18 (based on above sanity plans) - Final Regression: week of July 18 >> week of July 25 - Release: week of July 25 >> week of Aug 1 - October PTG - https://lists.starlingx.io/pipermail/starlingx-discuss/2022-June/013098.html - Dates: Oct 17 - 20, 2022 / Location: Columbus, OH - This is planned as an in-person event, not a hybrid event. - The planning committee will keep the COVID situation in mind - Only limited facilities (zoom) for remote participation will be available. ARs from Previous Meetings - Edge infrastructure orchestration discussion with the edge WG - Meeting on July 18 - Greg will attend or will find someone (w/ Distributed Cloud knowledge) to attend Open Requests for Help - Error adding subcloud: http://lists.starlingx.io/pipermail/starlingx-discuss/2022-June/013094.html - John Kung responded with additional guidance: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-June/013099.html - No response since then - docker vs cri-io: http://lists.starlingx.io/pipermail/starlingx-discuss/2022-June/013096.html - Consider this closed. Greg responded to the initial thread and follow-up questions. - Incorrect public key for signed starlingX 5.0 iso: http://lists.starlingx.io/pipermail/starlingx-discuss/2022-June/013072.html - Initial response provided. Discussion is still ongoing on the mailing list. - Signing is beyond the mandate of StarlingX. No signing is provided/supported on StarlingX. - This is something that every user will need to manage on their own if they need signing capabilities. - Greg & Scott agreed to provide a high level answer. From ildiko.vancsa at gmail.com Wed Jul 6 22:38:14 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 6 Jul 2022 15:38:14 -0700 Subject: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync Message-ID: Hi StarlingX Community, I?m reaching out to you to organize a call between the StarlingX project and the OpenInfra Foundation Board of Directors (BoD). The Open Infrastructure Foundation BoD is looking into engaging in regular check-ins with official OpenInfra projects in an online format. The goal of these meetings is to establish a closer connection and collaboration between the OpenInfra projects, including StarlingX, and the OpenInfra BoD group. This will help the Board to have a clearer view about each project?s state, achievements and challenges and it will be in a better position to support all the communities. At the same time, the projects will get a better understanding of the Board?s structure and responsibilities and have a better alignment with the group. The aim is to schedule a 1-hour long call some time in the upcoming weeks that will involve members of the Board as well as the StarlingX TSC along with further interested community members from the project. There is no expectation for a formal presentation from the projects and with that no materials have to be prepared in advance. If the community would like to provide an update in the form of a presentation that should work too. I created an etherpad to collect potential topics for the conversation and build an agenda for the call: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync I also created a poll to try to find time slot options that we can share with the OpenInfra Board of Directors. The poll is covering options for August, if we fail to find good options for that month, I will extend it to September. Please find the poll here: https://doodle.com/meeting/participate/id/b48Pv7Vb Both our BoD and community are distributed all around the globe and there is no time slot that works well well everywhere. In that sense, please mark ALL the time slots when you are available, so we can find one that is accessible for most of our Board and community members. __Please submit your preferences by the end of day on July 20, 2022.__ Please let me know if you have any questions. Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From starlingx.build at gmail.com Thu Jul 7 09:04:47 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 7 Jul 2022 05:04:47 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_installer - Build # 1377 - Still Failing! In-Reply-To: <902016271.56.1657097734228.JavaMail.javamailuser@localhost> References: <902016271.56.1657097734228.JavaMail.javamailuser@localhost> Message-ID: <1733930934.67.1657184690119.JavaMail.javamailuser@localhost> Project: STX_build_installer Build #: 1377 Status: Still Failing Timestamp: 20220707T090034Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220707T043000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20220707T043000Z DOCKER_BUILD_ID: jenkins-master-20220707T043000Z-builder OS: centos PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220707T043000Z/logs MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20220707T043000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From starlingx.build at gmail.com Thu Jul 7 09:05:00 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 7 Jul 2022 05:05:00 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1341 - Still Failing! In-Reply-To: <1560409419.59.1657097748277.JavaMail.javamailuser@localhost> References: <1560409419.59.1657097748277.JavaMail.javamailuser@localhost> Message-ID: <1538592238.70.1657184702052.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1341 Status: Still Failing Timestamp: 20220707T043000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220707T043000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From ildiko.vancsa at gmail.com Thu Jul 7 22:58:28 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 7 Jul 2022 15:58:28 -0700 Subject: [Starlingx-discuss] Edge infrastructure orchestration discussion with the edge WG In-Reply-To: <4EA744BF-EAD8-4CCE-BBBA-128660FB9CE4@gmail.com> References: <4EA744BF-EAD8-4CCE-BBBA-128660FB9CE4@gmail.com> Message-ID: <9DB7CC7D-F165-4637-97F9-92FD977D8515@gmail.com> Hi, It is a quick reminder about an upcoming OpenInfra Edge Computing Group session I reached to you about earlier. We are planning to discuss infrastructure orchestration and its challenges in large-scale, geographically distributed edge environments on Monday, July 18 at 6am US Pacific Time. I would like to encourage those of you who are interested in the topic and would like to participate to join the meeting. If any of you already know that you will be available for the session please reply on this thread or reach out to me directly. That way I can highlight StarlingX in the agenda directly to discuss details about the project in the context of the meeting?s main topic. You can find further information about the group and our calls on this wiki: https://wiki.openstack.org/wiki/Edge_Computing_Group Thanks and Best Regards, Ildik? > On Jun 27, 2022, at 16:45, Ildiko Vancsa wrote: > > Hi StarlingX community, > > I?m reaching out to you on behalf of the OpenInfra Edge Computing Group. > > On today?s call we touched on topics about infrastructure orchestration and its challenges in large-scale, geographically distributed edge environments. The group is planning to explore this area further and participants on today?s call suggested to look into solutions as well, such as the StarlingX project. > > Would anyone from the community be available to join the OpenInfra Edge Computing Group weekly call on July 18 at 6am US Pacific time, to participate in the conversation and share details about StarlingX? > > You can find further information about the group and our calls on this wiki: https://wiki.openstack.org/wiki/Edge_Computing_Group > > Thanks and Best Regards, > Ildik? > > From starlingx.build at gmail.com Fri Jul 8 09:11:29 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Fri, 8 Jul 2022 05:11:29 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_installer - Build # 1378 - Still Failing! In-Reply-To: <1537776370.65.1657184679780.JavaMail.javamailuser@localhost> References: <1537776370.65.1657184679780.JavaMail.javamailuser@localhost> Message-ID: <1847616556.75.1657271492626.JavaMail.javamailuser@localhost> Project: STX_build_installer Build #: 1378 Status: Still Failing Timestamp: 20220708T090656Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220708T043003Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20220708T043003Z DOCKER_BUILD_ID: jenkins-master-20220708T043003Z-builder OS: centos PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220708T043003Z/logs MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20220708T043003Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From starlingx.build at gmail.com Fri Jul 8 09:11:35 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Fri, 8 Jul 2022 05:11:35 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1342 - Still Failing! In-Reply-To: <302163295.68.1657184694048.JavaMail.javamailuser@localhost> References: <302163295.68.1657184694048.JavaMail.javamailuser@localhost> Message-ID: <771900817.78.1657271496199.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1342 Status: Still Failing Timestamp: 20220708T043003Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220708T043003Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From ildiko.vancsa at gmail.com Sat Jul 9 01:38:22 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 8 Jul 2022 18:38:22 -0700 Subject: [Starlingx-discuss] Pre-recorded presentation at OpenInfra Days Mexico Message-ID: <1032E502-9EB3-4C8A-83D7-8ACD7C829B8B@gmail.com> Hi StarlingX Community, I?m reaching out to you about a speaking opportunity at OpenInfra Days Mexico. OpenInfra communities have been organizing smaller, regional events which weren?t stopped by the pandemic but moved them to online platforms. Many of the events are still happening virtually, OpenInfra Days Mexico (https://openinfradays.mx) is one of the upcoming events, scheduled for August 15, that is still looking for content and presenters. Topics related to deployment and lifecycle management of infrastructure services are in the interest in that region. As StarlingX covers this functionality, we have an opportunity to have a presentation about the project at the event. Presentation details: * ~30min slot * Pre-recorded session * Deadline to submit the recording is August 1 Would any of you be interested and available to record a talk about StarlingX or be a co-presenter? Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From starlingx.build at gmail.com Sat Jul 9 09:12:00 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 9 Jul 2022 05:12:00 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_installer - Build # 1379 - Still Failing! In-Reply-To: <517118874.73.1657271487833.JavaMail.javamailuser@localhost> References: <517118874.73.1657271487833.JavaMail.javamailuser@localhost> Message-ID: <886041177.85.1657357923131.JavaMail.javamailuser@localhost> Project: STX_build_installer Build #: 1379 Status: Still Failing Timestamp: 20220709T090723Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220709T043001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20220709T043001Z DOCKER_BUILD_ID: jenkins-master-20220709T043001Z-builder OS: centos PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220709T043001Z/logs MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20220709T043001Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From starlingx.build at gmail.com Sat Jul 9 09:12:06 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 9 Jul 2022 05:12:06 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1343 - Still Failing! In-Reply-To: <1693640390.76.1657271493584.JavaMail.javamailuser@localhost> References: <1693640390.76.1657271493584.JavaMail.javamailuser@localhost> Message-ID: <1485256796.88.1657357929391.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1343 Status: Still Failing Timestamp: 20220709T043001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220709T043001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From starlingx.build at gmail.com Sun Jul 10 09:12:51 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sun, 10 Jul 2022 05:12:51 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_installer - Build # 1380 - Still Failing! In-Reply-To: <1619002701.83.1657357918385.JavaMail.javamailuser@localhost> References: <1619002701.83.1657357918385.JavaMail.javamailuser@localhost> Message-ID: <1766650426.94.1657444372620.JavaMail.javamailuser@localhost> Project: STX_build_installer Build #: 1380 Status: Still Failing Timestamp: 20220710T090901Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220710T043001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20220710T043001Z DOCKER_BUILD_ID: jenkins-master-20220710T043001Z-builder OS: centos PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220710T043001Z/logs MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20220710T043001Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From starlingx.build at gmail.com Sun Jul 10 09:12:55 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sun, 10 Jul 2022 05:12:55 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1344 - Still Failing! In-Reply-To: <2014527790.86.1657357924908.JavaMail.javamailuser@localhost> References: <2014527790.86.1657357924908.JavaMail.javamailuser@localhost> Message-ID: <308283113.97.1657444376028.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1344 Status: Still Failing Timestamp: 20220710T043001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220710T043001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From starlingx.build at gmail.com Mon Jul 11 09:25:38 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Mon, 11 Jul 2022 05:25:38 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_installer - Build # 1381 - Still Failing! In-Reply-To: <15124393.92.1657444369233.JavaMail.javamailuser@localhost> References: <15124393.92.1657444369233.JavaMail.javamailuser@localhost> Message-ID: <1323025905.102.1657531540086.JavaMail.javamailuser@localhost> Project: STX_build_installer Build #: 1381 Status: Still Failing Timestamp: 20220711T092129Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220711T043001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20220711T043001Z DOCKER_BUILD_ID: jenkins-master-20220711T043001Z-builder OS: centos PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220711T043001Z/logs MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20220711T043001Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From starlingx.build at gmail.com Mon Jul 11 09:25:42 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Mon, 11 Jul 2022 05:25:42 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1345 - Still Failing! In-Reply-To: <1713133771.95.1657444373546.JavaMail.javamailuser@localhost> References: <1713133771.95.1657444373546.JavaMail.javamailuser@localhost> Message-ID: <932236022.105.1657531543373.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1345 Status: Still Failing Timestamp: 20220711T043001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220711T043001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From ildiko.vancsa at gmail.com Mon Jul 11 22:27:45 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 11 Jul 2022 15:27:45 -0700 Subject: [Starlingx-discuss] Equinix (formerly Packet) resources Message-ID: <84F82D69-521C-4B0E-A02D-30953F877B51@gmail.com> Hi StarlingX Community, I?m reaching out to you about the HW resources that Equinix has been donating to the project. They reached out to a few of us to give a notification that they are doing some upgrades in their data centers to ensure that they don?t disrupt any of our activities on the servers. To ensure that they can safely move forward, I wanted to check if anyone is still using any HW donated by Equinix? __Please reply to this thread or reach out to me if you do, or if yo have any data on any of the machines that you used to make sure that your work will not be affected.__ Since Equinix is switch some of their processes, it is also a great time to plan for future usage and inform them about our plans to be able to better coordinate our resource usage. We used to run workshops on the donated servers, which we could bring back as events are starting to happen in person again. What do you all think? Also, is any of you have any additional plans to use the available HW we could discuss and share with Equinix? Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From starlingx.build at gmail.com Tue Jul 12 08:29:19 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 12 Jul 2022 04:29:19 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_installer - Build # 1382 - Still Failing! In-Reply-To: <1024769678.100.1657531535116.JavaMail.javamailuser@localhost> References: <1024769678.100.1657531535116.JavaMail.javamailuser@localhost> Message-ID: <750563916.110.1657614563042.JavaMail.javamailuser@localhost> Project: STX_build_installer Build #: 1382 Status: Still Failing Timestamp: 20220712T082456Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220712T043001Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20220712T043001Z DOCKER_BUILD_ID: jenkins-master-20220712T043001Z-builder OS: centos PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220712T043001Z/logs MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20220712T043001Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From starlingx.build at gmail.com Tue Jul 12 08:29:25 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Tue, 12 Jul 2022 04:29:25 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1346 - Still Failing! In-Reply-To: <33540518.103.1657531541002.JavaMail.javamailuser@localhost> References: <33540518.103.1657531541002.JavaMail.javamailuser@localhost> Message-ID: <1627727720.113.1657614566732.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1346 Status: Still Failing Timestamp: 20220712T043001Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20220712T043001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From Greg.Waines at windriver.com Wed Jul 13 14:43:41 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Wed, 13 Jul 2022 14:43:41 +0000 Subject: [Starlingx-discuss] FW: Incorrect public key for signed starlingX 5.0 iso . In-Reply-To: <424ce5c6-7965-c694-11c9-0dbdf7a3ace3@windriver.com> References: <424ce5c6-7965-c694-11c9-0dbdf7a3ace3@windriver.com> Message-ID: Forwarding ?. I think scott meant this for the starlingx discuss list. Greg. From: Little, Scott Sent: Wednesday, July 6, 2022 2:37 PM To: Waines, Greg Subject: Re: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . I'll attempt to answer this at a high level. Secure boot signing uses a client/server approach. build-pkgs acts as the client. The server holds the signing scripts and the keys used for signing. The client side code was released to open source as part of StarlingX. The server side code was not released. The interface between client and server is currently undocumented. I'll try to give an overview as best I can. Basically it is a series of ssh/scp calls made into signing server. 'build-pkgs' requires that the following environment variables be defined before it will attempt to request a secure boot signing. export SIGNING_SERVER= export SIGNING_USER= export SIGNING_SERVER_SCRIPT= 'build-pkgs' further requires that "$USER" == "jenkins", and export FORMAL_BUILD=1 If that is satisfied, it calls into 'sign-secure-boot' 'sign-secure-boot' contains a fairly good set of comments describing what happens next. The client side call sequence looks like this ... # Set up the server side directory for files transfers. UPLOAD_PATH=`ssh $SIGNING_USER@$SIGNING_SERVER sudo $SIGNING_SCRIPT -r` # upload the original package scp -q $FILE $SIGNING_USER@$SIGNING_SERVER:$UPLOAD_PATH # Request that the package be signed ssh $SIGNING_USER@$SIGNING_SERVER sudo $SIGNING_SCRIPT -v -i $UPLOAD_PATH/$(basename $FILE) $UNSIGNED_OPTION -t $TYPE > $TMPFILE # Download the file from the signing server DOWNLOAD_FILENAME=$(basename $OUTPUT_FILE) scp -q $SIGNING_USER@$SIGNING_SERVER:$OUTPUT_FILE $(dirname $FILE) Within the signing server there are two keys used for signing, known as the 'boot' key and the 'shim' key. The public half of the 'boot' key must manually added to the secure boot keychain in firmware. The 'boot' key signs first executable loaded, contained in the 'shim' package. The first executable must then install the public half of the shim key (automatically) before passing control to grub, and ultimately the kernel, both of which are signed by the 'shim' key. Three packages need to be passed to the signing server. The rpms need to be unpacked, the relevant binaries signed with correct keys, and the rpms reassembled. package key files to sign ========= ==== =========================== shim boot BOOTX64, shim, shimx64 shim MokManager, fallback, mmx64, fbx64 grub shim grubx64.efi, gcdx64.efi kernel shim vmlinuz NOTE: shim files to sign might include a '.efi' or '.EFI' suffix. Sign those as well. NOTE: some files may be absent in newer packages. It is probably ok if some of the above are missing. Signing looks like this ... sbsign --key $KEYPATH/$KEYNAME.key --cert $KEYPATH/$KEYNAME.crt --output $SIGNEDFILE $UNSIGNEDFILE On keys and certs ... boot.crt - Certificate to boot (to be programmed in firmware) boot.key - Private key with which to sign shim shim.crt - Certificated embedded within shim used to validate kernel, grub shim.key - Private key with which to sign kernel/grub key generation ... openssl req -new -x509 -newkey rsa:2048 -keyout $KEY.key -out $KEY.pem -days 3650 openssl x509 -in $KEY.pem -out $KEY.crt -outform DER Note: boot.crt should be copied to cgcs-root/build-tools/certificates/TiBoot.crt for inclusion during the 'build-iso' step Hope this helps Scott On 2022-07-05 03:19, Kumar, Chandan wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Greg, Thanks for acknowledgement. I have raised starlingx launchpad for document update. Meanwhile it would be really great if you can share the steps which has to be done to integrate signing of images as part of StarlingX build infrastructure. Regards, Chandan Kumar. From: Waines, Greg Sent: Monday, July 4, 2022 6:00 PM To: starlingx-discuss at lists.starlingx.io Cc: Little, Scott Subject: Re: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . Hey Chandan, Thanks for bringing this up. I chatted with Scott about this. Currently the StarlingX public builds on CENGN are not building a secure boot capable load ? i.e. signing the appropriate items to enable secure boot. Although the StarlingX build infrastructure allows it to be added. Neither of these points are properly documented in docs.starlingx.io ? I can?t remember the details of why we are not doing this. I am guessing that the thinking was that a user of StarlingX that wanted to use UEFI Secure Boot, would want to sign with his own private key. Can you raise a starlingx launchpad ( https://launchpad.net/starlingx ) to address the docs.starlingx.io documentation issue, i.e. to indicate that the StarlingX CENGN builds are not signed to support uefi secure boot, and describe how a starlingx user could add signing to their StarlingX build environment in order to sign for uefi secure boot with their own private key ? Greg. From: Scott Little > Sent: Wednesday, June 29, 2022 10:42 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . On 2022-06-02 13:12, Kumar, Chandan wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I am trying to validate signed starlingX 5.0 iso on a secureboot enabled setup against public key(TiBoot.crt) embedded inside iso. After rebooting , operating system is not coming up with error screen saying ?Verification failed: (0X1A) Security Violation?. However, when I signed images with self-generated private key and validated against corresponding public key, system is able to boot up successfully. Signing is done after flashing the iso on a server. Please find attached procedure for signing images inside iso. I believe, the public key provided with iso is not correct. Can you please confirm ? Regards, Chandan Kumar. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss Thanks for the report. I'll look into it Scott Little -------------- next part -------------- An HTML attachment was scrubbed... URL: From Juanita.Balaraj at windriver.com Wed Jul 13 22:18:27 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Wed, 13 Jul 2022 22:18:27 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 13-July-22 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 ============ 13-July-22 - Stx 7.0 GA date is July 25th - AR Juanita to review Stx 7.0 Release checklist - Need to update the Installation Guide to display Stx 7.0 once docs are merged : https://docs.starlingx.io/deploy_install_guides/index-install-e083ca818006.html - AR Ron - Version drop-down on https://docs.starlingx.io/ to be updated to display Stx 7.0 - AR Ron - Stx Release Notes - AR Juanita - To automate the updates for the Introduction Guide - AR Ron - Scott to cut the Stx 7.0 docs branch - To confirm the date - No Cherry picks this week. Waiting for reviews to merge. - Team to address LP Bugs - https://bugs.launchpad.net/starlingx/+bug/1932314; https://bugs.launchpad.net/starlingx/+bug/1951165 - AR Elaine to close these bugs - On hold - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs for a list of pending Doc Bugs - https://bugs.launchpad.net/starlingx/+bug/1980666 - AR Elisa - Introduction Guide to be updated with new features for Stx 7.0 - Team and pulled in from STx 7.0 Release Notes - Ron to automate it - TAI clock updates - Juanita to discuss with Ghada regarding https://storyboard.openstack.org/#!/story/2010033 - Operations Guide Archive - On Hold until further clarifications are discussed - https://review.opendev.org/c/starlingx/docs/+/822030 - Ron in the process of updating the Glossary File to keep it current; https://review.opendev.org/c/starlingx/docs/+/848772 - https://review.opendev.org/c/starlingx/docs/+/849003 - AR Juanita to confirm if this needs to be cherrypicked to dsr6 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Thu Jul 14 12:07:10 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 14 Jul 2022 12:07:10 +0000 Subject: [Starlingx-discuss] Looking for StarlingX Build Environment help for INTEL Team In-Reply-To: References: <2ccdbf47-229f-8721-4cfe-fc45617d64af@windriver.com> <61b2a429-6add-2fc4-b89d-599d5b8896ff@windriver.com> <5f53e242-5d3f-31e1-38c3-35fec4d747b7@windriver.com> Message-ID: + starlingx-discuss at lists.starlingx.io From: Shivashankara Belur, Nidhi Sent: Wednesday, July 13, 2022 4:06 PM To: Little, Scott ; Khalil, Ghada ; Sun, Austin ; Waines, Greg ; Qi, Mingyuan ; Liu, ZhipengS ; Burla, Balendu ; Yu, Chengde ; Panech, Davlet Cc: Webster, Steven ; Thothadri, Ram ; Melnick, Ruth ; Jones, Bruce E ; Nowell, Anthony Subject: RE: Looking for StarlingX Build Environment help for INTEL Team [Please note: This e-mail is from an EXTERNAL e-mail address] Hello Davlet, After yesterday?s call, I tried building the sriov-fec-operator package again, the BuildRequires as in the dependency packages chartmuseum, helm and openstack-helm-infra in the application spec file was commented out, therefore it did not show any errors. I rebuilt the package after adding these deps back and still shows the same error. Please refer to the same build logs that I shared in my previous email. Mouli and I discussed after the call yesterday and decided that we want to try bring up build system with centos as the host OS, then try to build packages to see if that makes any difference. @Panech, Davlet Can you please share any instructions on build system bring up steps for CentOS. Currently we are running this on a Ubuntu 16.04 as per the starlingx official build system documentation. We would like to try this in parallel while working on debugging build issues on ubuntu. Thank you, Nidhi From: Shivashankara Belur, Nidhi Sent: Monday, July 11, 2022 1:53 PM To: Scott Little >; Khalil, Ghada >; Sun, Austin >; Waines, Greg >; Qi, Mingyuan >; Liu, ZhipengS >; Burla, Balendu >; Yu, Chengde >; Panech, Davlet > Cc: Webster, Steven >; Ram.Thothadri >; ruth.melnick >; Jones, Bruce E >; Nowell, Anthony > Subject: RE: Looking for StarlingX Build Environment help for INTEL Team Hi Davlet, I?m sending build logs from last Friday that you requested. After adding the missing packages, there are still some errors and build-pkgs fails. I executed the build-pkgs a few times and collected multiple logs, attached in this email. 1. build-pkgs-serial stx-sriov-fec-operator-helm 2. build-pkgs-serial chartmuseum helm openstack-helm-infra stx-sriov-fec-operator-helm We will definitely need to schedule another debug session for this week, I suggest tomorrow between 9 AM ? 11 AM (PST), which is 12 PM ? 2 PM (EST). I?ll send a meeting invite, please let me know your availability. Regards, Nidhi From: Shivashankara Belur, Nidhi Sent: Wednesday, July 6, 2022 12:14 PM To: Scott Little >; Khalil, Ghada >; Sun, Austin >; Waines, Greg >; Qi, Mingyuan >; Liu, ZhipengS >; Burla, Balendu >; Yu, Chengde >; Panech, Davlet > Cc: Webster, Steven >; Ram.Thothadri >; ruth.melnick >; Jones, Bruce E >; Nowell, Anthony > Subject: RE: Looking for StarlingX Build Environment help for INTEL Team I did run just build-pkgs, before attempting with the package name, it also fails building all the pkgs due to same error. I see the following errors in every single package build. 1. ERROR: Command failed: 19:03:30 # mount -n -t tmpfs -o mode=0755 -o nr_inodes=0 -o size=11g mock_chroot_tmpfs /localdisk/loadbuild/stx_builder/fec-operator/std/mock/b3/root 1. ERROR: Command failed: 19:03:29 # /usr/bin/yum --installroot /localdisk/loadbuild/stx_builder/fec-operator/std/mock/b0/root/ --releasever 7 install @buildsys-build pigz lbzip2 bash yum python3 This 2nd error is followed by below messages, which suggests to me that the mirror is not accessible from my lab maybe due to proxy? 19:03:29 Failed to set locale, defaulting to C 19:03:29 http://127.0.0.1:8088/localdisk/loadbuild/stx_builder/fec-operator/std/results/stx_builder-fec-operator-4.0-std/repodata/$ epomd.xml: [Errno 14] HTTP Error 403 - Forbidden 19:03:29 Trying other mirror. 19:03:29 To address this issue please refer to the below wiki article 19:03:29 19:03:29 https://wiki.centos.org/yum-errors 19:03:29 19:03:29 If above article doesn't help to resolve this issue please use https://bugs.centos.org/. 19:03:29 19:03:29 http://127.0.0.1:8088/localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/repodata/repomd.xml: [Errno 14] HTT$ Error 403 - Forbidden 19:03:29 Trying other mirror. 19:03:29 http://127.0.0.1:8088/localdisk/designer/stx_builder/fec-operator/cgcs-root/centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden 19:03:29 Trying other mirror. 19:03:29 One of the configured repositories failed (Stx-Centos-7-Distro), 19:03:29 and yum doesn't have enough cached data to continue. At this point the only 19:03:29 safe thing yum can do is fail. There are a few ways to work "fix" this: 19:03:29 19:03:29 1. Contact the upstream for the repository and get them to fix the problem. 19:03:29 19:03:29 2. Reconfigure the baseurl/etc. for the repository, to point to a working 19:03:29 upstream. This is most often useful if you are using a newer 19:03:29 distribution release than is supported by the repository (and the 19:03:29 packages for the previous distribution release still work). 19:03:29 19:03:29 3. Run the command with the repository temporarily disabled 19:03:29 yum --disablerepo=StxCentos7Distro ... 19:03:29 19:03:29 4. Disable the repository permanently, so yum won't use it by default. Yum 19:03:29 will then just ignore the repository until you permanently enable it 19:03:29 again or use --enablerepo for temporary usage: 19:03:29 19:03:29 yum-config-manager --disable StxCentos7Distro 19:03:29 or 19:03:29 subscription-manager repos --disable=StxCentos7Distro 19:03:29 19:03:29 5. Configure the failing repository to be skipped, if it is unavailable. 19:03:29 Note that yum will try to contact the repo. when it runs most commands, 19:03:29 so will have to try and fail each time (and thus. yum will be be much 19:03:29 slower). If it is a very temporary problem though, this is often a nice 19:03:29 compromise: 19:03:29 19:03:29 yum-config-manager --save --setopt=StxCentos7Distro.skip_if_unavailable=true 19:03:29 19:03:29 failure: repodata/repomd.xml from StxCentos7Distro: [Errno 256] No more mirrors to try. 19:03:29 http://127.0.0.1:8088/localdisk/designer/stx_builder/fec-operator/cgcs-root/centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden 19:03:29 Regards, Nidhi From: Scott Little > Sent: Wednesday, July 6, 2022 7:09 AM To: Shivashankara Belur, Nidhi >; Khalil, Ghada >; Sun, Austin >; Waines, Greg >; Qi, Mingyuan >; Liu, ZhipengS >; Burla, Balendu >; Yu, Chengde >; Panech, Davlet > Cc: Webster, Steven >; Ram.Thothadri >; ruth.melnick >; Jones, Bruce E >; Nowell, Anthony > Subject: Re: Looking for StarlingX Build Environment help for INTEL Team Did you do a full 'build-pkgs' before attempting 'build-pkgs ' ? Your first build should build everything. Scott On 2022-07-05 8:23 p.m., Shivashankara Belur, Nidhi wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Scott, Quick update from today?s build, * Resolved all issues related to ?DOS? formatting. * build-pkgs moved forward and able to fix some mistakes in our operator source code .spec file 00:05:56 ==== Update repodata complete ===== 00:05:56 00:05:56 Successfully built 1 packages: 00:05:56 stx-sriov-fec-operator-helm 00:05:56 00:05:56 Compiled src.rpm's can be found here: /localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS ######## Wed Jul 6 00:05:56 UTC 2022: build-srpm-parallel --std was successful * build-pkgs of our fec-operator now fails at the same step as cert-manager. 00:06:16 b0: Mock Version: 1.4.16 00:06:16 b0: INFO: Mock Version: 1.4.16 00:06:16 b0: Start: yum install 00:06:16 b0: ERROR: Command failed: 00:06:16 b0: # /usr/bin/yum --installroot /localdisk/loadbuild/stx_builder/fec-operator/std/mock/b0/root/ --relea sever 7 install @buildsys-build pigz lbzip2 bash yum python3 00:06:16 b0: Failed to set locale, defaulting to C 00:06:16 b0: http://127.0.0.1:8088/localdisk/loadbuild/stx_builder/fec-operator/std/results/stx_builder-fec-operat or-4.0-std/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden 00:06:16 b0: Trying other mirror. 00:06:16 b0: To address this issue please refer to the below wiki article 00:06:16 b0: 00:06:16 b0: https://wiki.centos.org/yum-errors 00:06:16 b0: 00:06:16 b0: If above article doesn't help to resolve this issue please use https://bugs.centos.org/. 00:06:16 b0: 00:06:16 b0: http://127.0.0.1:8088/localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/repodata/repomd .xml: [Errno 14] HTTP Error 403 - Forbidden 00:06:16 b0: Trying other mirror. 00:06:16 b0: http://127.0.0.1:8088/localdisk/designer/stx_builder/fec-operator/cgcs-root/centos-repo/Binary/repoda ta/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden 00:06:16 b0: Trying other mirror. 00:06:16 b0: failure: repodata/repomd.xml from StxCentos7Distro: [Errno 256] No more mirrors to try. 00:06:16 b0: http://127.0.0.1:8088/localdisk/designer/stx_builder/fec-operator/cgcs-root/centos-repo/Binary/repoda ta/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden 00:06:16 b0: 00:06:16 mock_update_or_init: out 00:06:16 00:06:34 ===== wait for last jobs in iteration 1 to complete ===== 00:06:34 End build on 'b0': /localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/stx-sriov-fec-operato r-helm-1.0-2.tis.src.rpm 00:06:34 Error building stx-sriov-fec-operator-helm-1.0-2.tis.src.rpm on 'b0'. 00:06:34 Will try to build again (if some other package will succeed). 00:06:34 ===== iteration 1 complete ===== 00:06:34 failed=['/localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/build-info-1.0-4.tis.src.rpm', '/localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/stx-sriov-fec-operator-helm-1.0-2.tis.src.rpm'] 00:06:34 to_be_built=['/localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/build-info-1.0-4.tis.src.r pm', '/localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/stx-sriov-fec-operator-helm-1.0-2.tis.src.r pm'] 00:06:34 00:06:34 *** Build Failed *** 00:06:34 Tried 1 times - following pkgs could not be successfully built: 00:06:34 *** Build Failed *** 00:06:34 /localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/build-info-1.0-4.tis.src.rpm 00:06:34 /localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/stx-sriov-fec-operator-helm-1.0-2.tis.sr c.rpm 00:06:34 00:06:34 00:06:34 Results out to: /localdisk/loadbuild/stx_builder/fec-operator/std/results/stx_builder-fec-operator-4.0-st d 00:06:34 00:06:34 Pkgs built: 0 00:06:34 dirname: missing operand 00:06:34 Try 'dirname --help' for more information. 00:06:34 Recreate repodata 00:06:35 00:06:35 Failed to build packages: stx-sriov-fec-operator-helm-1.0-2.tis.src.rpm build-info-1.0-4.tis.src.rpm ######## Wed Jul 6 00:06:36 UTC 2022: build-rpm-parallel --std failed with rc=1 Wed Jul 6 00:06:36 UTC 2022: build-rpm-parallel --std failed with rc=1 Can we have another live debug session tomorrow to see further into this issue? Thank you, Nidhi From: Scott Little Sent: Tuesday, July 5, 2022 12:52 PM To: Shivashankara Belur, Nidhi ; Khalil, Ghada ; Sun, Austin ; Waines, Greg ; Qi, Mingyuan ; Liu, ZhipengS ; Burla, Balendu ; Yu, Chengde ; Panech, Davlet Cc: Webster, Steven ; Ram.Thothadri ; ruth.melnick ; Jones, Bruce E ; Nowell, Anthony Subject: Re: Looking for StarlingX Build Environment help for INTEL Team Within the build container, the first place it would have been copied is $HOME/buildrc . That file initializes your environment variables within the container. It should remain confined to the environment variables after that as far as I can recall. That file should be reset if you clean and recreate the build container. If that procedure doesn't fix $HOME/buildrc, perhaps deleting and recreating the image from which the container is launched might also be required. Let me know if you find that to be the case. On 2022-07-05 15:05, Shivashankara Belur, Nidhi wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Scott, Thank you for providing the feedback on remaining issues. It was a federal holiday yesterday and I?m trying the fixes you mentioned right now. I?ll send another update once it completes. If any issues still remain, we would need a follow up call tomorrow. However, I still see this error pops up, even after applying the ff as unix on localrc find: ?/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config/centos/flock \r?: No such file or directory Not quite sure how to find which other file could have been edited on windows. Regards, Nidhi From: Scott Little Sent: Tuesday, July 5, 2022 10:20 AM To: Shivashankara Belur, Nidhi ; Khalil, Ghada ; Sun, Austin ; Waines, Greg ; Qi, Mingyuan ; Liu, ZhipengS ; Burla, Balendu ; Yu, Chengde ; Panech, Davlet Cc: Webster, Steven ; Ram.Thothadri ; ruth.melnick ; Jones, Bruce E ; Nowell, Anthony Subject: Re: Looking for StarlingX Build Environment help for INTEL Team Do you need a follow up call ? Scott On 2022-07-01 17:39, Shivashankara Belur, Nidhi wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Ghada, Please find below detail description with error logs of all issues along with 1 line ?current status? for each issue. Build system errors: 1. Download source code repositories, step 3: synchronize the repository (repo sync -j`nproc`). This step fails to download yocto linux repository, therefore fails. Resolved: Replaced ?git? with ?https? in the manifest default.xml file, another pointer is to run the command ?repo sync? without any arguments as ?-j? has some known issues. Resolution was given by WR team on 6/29/22 live debug session (attendees: Davelet, Scott, Steven) 2. Download Packages, download_mirror.sh had multiple failures ?permission denied? due to a root privilege docker access issue. Resolved: Running the following command, adding env variables for sudo as well as proxies. cd $MY_REPO_ROOT_DIR/stx-tools/centos-mirror-tools && sudo bash -c "source env_sudo.sh && bash download_mirror.sh" cat env_sudo.sh export MY_REPO_ROOT_DIR=/localdisk/designer/stx_builder/fec-operator export MY_REPO=/localdisk/designer/stx_builder/fec-operator/cgcs-root export MY_WORKSPACE=/localdisk/loadbuild/stx_builder/fec-operator export http_proxy=http://proxy-chain.intel.com:911 export https_proxy=http://proxy-chain.intel.com:911 Resolution was given by WR team on 6/29/22 live debug session (attendees: Davelet, Scott, Steven) 3. Download packages in the above step had some failures, resolved it by manually downloading and moving the following rpms to ?downloads? (Not verified by WR) [stx_builder at 4df2aa3dafa0 centos-mirror-tools]$ cat logs/*_failmoved_*.log fail_move_srpm:bash-4.2.46-34.el7.x86_64.rpm fail_move_srpm:linuxptp-2.0-2.el7.src.rpm fail_move_srpm:net-tools-2.0-0.24.20131004git.el7.src.rpm fail_move_srpm:openldap-2.4.44-20.el7.tis.9.x86_64.rpm fail_move_srpm:openldap-2.4.44-20.el7.x86_64.rpm fail_move_srpm:openssh-7.4p1-21.el7.src.rpm fail_move_srpm:puppet-firewall-1.8.2-2.2f892e9git.el7.src.rpm fail_move_srpm:python-2.7.5-89.el7.src.rpm fail_move_srpm:rabbitmq-server-3.6.5-1.el7.src.rpm fail_move_srpm:setup-2.8.71-10.el7.src.rpm fail_move_srpm:sudo-1.8.23-10.el7_9.1.x86_64.rpm Status: Need help from WR to verify that this resolution is valid. 4. Populate downloads step shows an error [stx_builder at 4df2aa3dafa0 cgcs-root]$ ln -s /import/mirrors/CentOS/stx/CentOS/downloads/ $MY_REPO/stx/ ln: failed to create symbolic link ?/localdisk/designer/stx_builder/fec-operator/cgcs-root/stx/downloads?: File exists [stx_builder at 4df2aa3dafa0 cgcs-root]$ populate_downloads.sh /import/mirrors/CentOS/stx/CentOS/ mirror_dir=/import/mirrors/CentOS/stx/CentOS/ config_dir=/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config distro=centos layer=all find: ?/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config/centos/flock \r?: No such file or directory find: ?/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config/centos/flock \r?: No such file or directory Status: Need help from WR to resolve this issue. 5. Build packages, updating symbolic links shows similar error: [stx_builder at 4df2aa3dafa0 toCOPY]$ bash generate-centos-repo.sh /import/mirrors/CentOS/stx/CentOS/ mirror_dir=/import/mirrors/CentOS/stx/CentOS/ config_dir=/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config distro=centos layer=all layer_pkg_urls= layer_image_inc_urls= layer_wheels_inc_urls= find: ?/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config/centos/flock\r?: No such file or directory find: ?/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config/centos/flock\r?: No such file or directory find: ?/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config/centos/flock\r?: No such file or directory find: ?/localdisk/designer/stx_builder/fec-operator/cgcs-root/../stx-tools/centos-mirror-tools/config/centos/flock\r?: No such file or directory rpm_lst_files=rpms_3rdparties.lst rpms_centos3rdparties.lst rpms_centos.lst rpm_lst_files_rt= layer_dirs= Status: Need help from WR to resolve this issue. 6. build-pkgs command fails for all packages, probably due to dependency on previous steps. Error logs: [stx_builder at 4df2aa3dafa0 stx]$ build-pkgs stx-sriov-fec-operator-helm No changes for stx projects build-pkgs-parallel stx-sriov-fec-operator-helm Reading: /localdisk/designer/stx_builder/fec-operator/cgcs-root/build-data/build_avoidance_source BUILD_AVOIDANCE_DIR= BUILD_AVOIDANCE_HOST= BUILD_AVOIDANCE_USR= BUILD_AVOIDANCE_FLAG=0 CLEAN_FLAG=0 EDIT_FLAG=0 find: ?/localdisk/designer/stx_builder/fec-operator/cgcs-root/stx/app-sriov-fec-operator/stx-sriov-fec-operator-helm\r/centos/?: No such file or directory find: ?/localdisk/designer/stx_builder/fec-operator/cgcs-root/stx/app-sriov-fec-operator/stx-sriov-fec-operator-helm\r/centos/?: No such file or directory TARGETS_STD= TARGETS_RT= TARGETS_INSTALLER= TARGETS_CONTAINERS= EXTRA_ARGS_COMMON='' EXTRA_ARGS_SRPM='' EXTRA_ARGS_RPM='' TARGETS=' stx-sriov-fec-operator-helm ' TARGETS_STD=' ' TARGETS_RT=' ' TARGETS_INSTALLER=' ' TARGETS_CONTAINERS=' ' TARGETS_MISC=' stx-sriov-fec-operator-helm ' Capture build context Launching std build, logging to /localdisk/loadbuild/stx_builder/fec-operator/build-std.log ######## Fri Jul 1 21:10:15 UTC 2022: Launching build-srpms-parallel --std BUILD_AVOIDANCE_URL= /localdisk/designer/stx_builder/fec-operator/cgcs-root/build-tools/build-srpms-parallel --std stx-sriov-fec-operator-helm MAX_WORKERS=8 CLEAN_FLAG=0 21:10:17 build-srpms-parallel --std stx-sriov-fec-operator-helm 21:10:17 make: stx-sriov-fec-operator-helm 21:10:17 removed ?/localdisk/loadbuild/stx_builder/fec-operator/std/tmp/SRPM_REBUILT_LIST_6? ' in file '/localdisk/designer/stx_builder/fec-operator/cgcs-root/stx/app-sriov-fec-operator/centos_pkg_dirs' 21:10:29 ==== Update repodata ===== 21:10:33 Directory walk started 21:10:33 Directory walk done - 302 packages 21:10:33 Temporary output repo path: /localdisk/loadbuild/stx_builder/fec-operator/std/rpmbuild/SRPMS/.repodata/ 21:10:33 Preparing sqlite DBs 21:10:33 Pool started (with 5 workers) 21:10:33 Pool finished 21:10:33 ==== Update repodata complete ===== 21:10:33 21:10:33 No packages required a rebuild 21:10:33 21:10:33 ERROR: (1600): failed to resolve build targets: stx-sriov-fec-operator-helm ######## Fri Jul 1 21:10:33 UTC 2022: build-srpm-parallel --std failed with rc=1 Fri Jul 1 21:10:33 UTC 2022: build-srpm-parallel --std failed with rc=1 Status: Need help from WR to resolve this issue. @Sun, Austin I got your email on proposed changes for build-system issues. I tried a few of them applicable for us. 1. We have already passed noProxy env variable for docker container 2. Download_mirror.sh command was executed as ?sudo? 3. "get_sources.sh", is not executable. Fixed this locally by changing the file mode. Question: I didn?t quite understand these two changes, feat: Modify layer build process (Ibded97db) ? Gerrit Code Review (opendev.org) ; didn?t think this was applicable to us since we are not doing layer build. Do we need to do layer build ? fix: drop the relative gopath (I950184f0) ? Gerrit Code Review (opendev.org) ; I applied this fix locally on my system. Is this a mandatory fix ? Regards, Nidhi From: Khalil, Ghada Sent: Wednesday, June 29, 2022 6:32 AM To: Sun, Austin ; Waines, Greg ; Qi, Mingyuan ; Liu, ZhipengS ; Burla, Balendu ; Shivashankara Belur, Nidhi ; Yu, Chengde ; Little, Scott ; Panech, Davlet Cc: Webster, Steven ; Ram.Thothadri ; ruth.melnick ; Jones, Bruce E ; Nowell, Anthony Subject: RE: Looking for StarlingX Build Environment help for INTEL Team There was a live zoom session yesterday with @Shivashankara Belur, Nidhi and @Panech, Davlet / @Little, Scott to investigate the build failures as well. Can someone provide a readout of the meeting please so that everyone is on the same page? Thanks, Ghada From: Sun, Austin > Sent: Wednesday, June 29, 2022 3:41 AM To: Waines, Greg >; Qi, Mingyuan >; Liu, ZhipengS >; Burla, Balendu >; Shivashankara Belur, Nidhi >; Yu, Chengde > Cc: Khalil, Ghada >; Webster, Steven >; Thothadri, Ram >; Melnick, Ruth >; Jones, Bruce E >; Little, Scott >; Panech, Davlet >; Nowell, Anthony > Subject: RE: Looking for StarlingX Build Environment help for INTEL Team [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Greg and Scott : Chant has been working on build latest starlingx with layer-build in intel environment and uploaded several patches to address build issues. With these patches, Chant can build iso successfully . would you like review these patches ? https://review.opendev.org/c/starlingx/tools/+/846573 https://review.opendev.org/c/starlingx/tools/+/846846 https://review.opendev.org/c/starlingx/containers/+/847231 https://review.opendev.org/c/starlingx/tools/+/847066 https://review.opendev.org/c/starlingx/tools/+/847061 @Burla, Balendu and @Shivashankara Belur, Nidhi: you can cherry-pick those patches and try build in your environment . Thanks. BR Austin Sun. From: Waines, Greg > Sent: Friday, June 10, 2022 6:47 PM To: Sun, Austin >; Qi, Mingyuan >; Liu, ZhipengS >; Burla, Balendu >; Shivashankara Belur, Nidhi > Cc: Khalil, Ghada >; Webster, Steven >; Ram.Thothadri >; ruth.melnick >; Jones, Bruce E >; Little, Scott >; Panech, Davlet >; Nowell, Anthony > Subject: RE: Looking for StarlingX Build Environment help for INTEL Team thanks very much Austin. Greg. From: Sun, Austin > Sent: Thursday, June 9, 2022 11:39 PM To: Waines, Greg >; Qi, Mingyuan >; Liu, ZhipengS >; Burla, Balendu >; Shivashankara Belur, Nidhi > Cc: Khalil, Ghada >; Webster, Steven >; Thothadri, Ram >; Melnick, Ruth >; Jones, Bruce E >; Little, Scott >; Panech, Davlet >; Nowell, Anthony > Subject: RE: Looking for StarlingX Build Environment help for INTEL Team [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Greg: OK. @Burla, Balendu, and @Shivashankara Belur, Nidhi, please contact us , we can syn-cup internally . Thanks. BR Austin Sun. From: Waines, Greg > Sent: Thursday, June 9, 2022 9:41 PM To: Qi, Mingyuan >; Sun, Austin >; Liu, ZhipengS > Cc: Burla, Balendu >; Shivashankara Belur, Nidhi >; Khalil, Ghada >; Webster, Steven >; Ram.Thothadri >; ruth.melnick >; Jones, Bruce E >; Little, Scott >; Panech, Davlet >; Nowell, Anthony > Subject: Looking for StarlingX Build Environment help for INTEL Team Mingyuan, Austin, Zhipeng, (Intel StarlingX folks) Balendu (Mouli) Burla and Nidhi Shivashankara Belur are new members of StarlingX from the Intel Networking(?) org who are in the process of contributing a kubernetes operator for configuring FEC in a couple of intel hardware devices. They are having difficulty setting up their StarlingX Build Environment and getting it to work. Is there any chance that you guys (who have working StarlingX Build Environments inside Intel) could help Mouli and Nidhi out in setting up their environment ? let me know, thanks a lot, Greg. From: Waines, Greg Sent: Tuesday, June 7, 2022 6:58 AM To: Burla, Balendu >; Nowell, Anthony > Cc: Shivashankara Belur, Nidhi >; Khalil, Ghada >; Webster, Steven >; Thothadri, Ram >; Melnick, Ruth >; Rasa, Nimalini >; Peters, Matt > Subject: RE: sriov-fec-operator plan update ? Thanks Mouli. Anthony ? I think scott or davlet have provided a bit of help to Mouli on his build-pkg issues ? any chance we can get some more direct help from them in order to get over this build issue ? Greg. From: Burla, Balendu > Sent: Monday, June 6, 2022 6:14 PM To: Waines, Greg >; Shivashankara Belur, Nidhi > Cc: Khalil, Ghada >; Webster, Steven >; Thothadri, Ram >; Melnick, Ruth >; Rasa, Nimalini >; Peters, Matt > Subject: RE: sriov-fec-operator plan update ? [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Greg, We have tested the fec-operator on StarlingX platform manually using the helm chats. And we have packaged the helm chats as system application with the help of documentation and Teresa for integration. However, To test that, we need a local build environment and we are struck in brining up the local build environment and looking for help from WR/STX to resolve the build-pkg issues since 4 weeks. Without resolving those build issues, we can not submit a working code. Although, Nidhi will submit the code for review in a draft status. Assuming the local build issues are resolved, from there on we can try to submit the working code, review, tested in two weeks. Can someone help in resolving our local build-pkg issues? Nidhi can setup a debug call, if that work for your team members. NOTE: these build-pkg issues are not related to fec-operator, trying to build the default iso image with latest master. Best regards, Mouli. From: Waines, Greg > Sent: Monday, June 6, 2022 6:12 AM To: Shivashankara Belur, Nidhi >; Burla, Balendu > Cc: Khalil, Ghada >; Webster, Steven >; Ram.Thothadri >; ruth.melnick >; Rasa, Nimalini >; Peters, Matt > Subject: RE: sriov-fec-operator plan update ? Thanks for the status update. What I?m looking for though is a committed date for - code submitted, merged and tested, and - customer documentation updated. Do you have a forecast for that date ? Greg. From: Shivashankara Belur, Nidhi > Sent: Friday, June 3, 2022 2:18 PM To: Waines, Greg >; Burla, Balendu > Cc: Khalil, Ghada >; Webster, Steven >; Thothadri, Ram >; Melnick, Ruth >; Rasa, Nimalini >; Peters, Matt > Subject: RE: sriov-fec-operator plan update ? [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Greg, I am currently blocked by 2 issues, 1. Build-pkgs tool is failing 2. System application-apply fails to bring up operator pods. Pending items: 1. Build fec-operator docker images for STX ? WIP: * Imported pre-built docker images for the operator and pushed it with tag registry.local. But system application-apply fails here. * Include build images into build iso ? Not yet started. I have 2 active email threads for these 2 issues. Contact person for build issues is Scott Little, there isn?t much progress here yet. Can you please include a contact who can help resolve this issue through a live debug call ? Contact person for system application-apply failure is Teresa Ho, we are doing 1:1 debug sessions since yesterday. Some reasons for failure identified, we will meet again on Monday to try some solutions. Regards, Nidhi From: Waines, Greg > Sent: Monday, May 30, 2022 7:39 AM To: Burla, Balendu > Cc: Khalil, Ghada >; Webster, Steven >; Ram.Thothadri >; ruth.melnick >; Shivashankara Belur, Nidhi >; Rasa, Nimalini >; Peters, Matt > Subject: sriov-fec-operator plan update ? Hey Mouli, Wrt your ?FEC Operator Integration to enable FEC Device Configurability? ( https://storyboard.openstack.org/#!/story/2009749 ), are you still tracking to your ?Code Merge? (5/27) and ?Feature Tested? (6/6) dates in the StarlingX STX7.0 Feature Planning Spreadsheet ( ROW 36 of https://docs.google.com/spreadsheets/d/171PJAu9SykXm9h9Ny2IsZ8YMbhvEwOzuTbISWUMQhiE/edit#gid=1107209846 ) ? Although there is no hard commitment in StarlingX for the delivery of this functionality, there are hard commitments wrt this functionality being available in Wind River?s commercial product based on StarlingX. I?d like to confirm that your feature delivery dates are still accurate and you are getting all the support you need from the StarlingX projects, so I can make sure your dates align with Wind River commercial product dates. let me know, Greg. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu Jul 14 20:02:21 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 14 Jul 2022 13:02:21 -0700 Subject: [Starlingx-discuss] Alternating the time slot for the TSC & Community call Message-ID: <565FB23D-505A-4756-B25C-EFD7C5479D8A@gmail.com> Hi StarlingX Community, I?m reaching out to you about a topic that we discussed during the TSC & Community call this week. It was raised that the time of the meeting is very inconvenient in the APAC region and it prevents our TSC members and contributors in that area from actively participating. The idea is to start alternating the call times and provide a better opportunity for everyone in the global community to participate in the calls. I created a poll to find a time slot option that works for most: https://doodle.com/meeting/participate/id/aAnlZE9b __Please fill it out for by the end of next week (July 24).__ Please mark ALL the time slots that would work for you on an ongoing basis, independently from the dates displayed in the poll! Please let me know if you have any questions. Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From Peng.Peng at windriver.com Thu Jul 14 20:35:10 2022 From: Peng.Peng at windriver.com (Peng, Peng) Date: Thu, 14 Jul 2022 20:35:10 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20220709T013733Z Message-ID: Sanity Test from 2022-July-11 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220709T013733Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220709T013733Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal Environment AIO - Duplex Setup 1 TCs [PASS] Sanity Platform 09 TCs [PASS] Daily Regression Platform 10 TCs [PASS] TOTAL: [ 20 TCs ] Kind regards, PV Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu Jul 14 21:17:46 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 14 Jul 2022 14:17:46 -0700 Subject: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync In-Reply-To: References: Message-ID: <6E9D75C2-7681-42CD-B2E3-0556CD366CC1@gmail.com> Hi StarlingX Community, It is a friendly reminder to please fill out the poll to help organizing the sync call between the OpenInfra BoD and the StarlingX project. You can find the poll here: https://doodle.com/meeting/participate/id/b48Pv7Vb __Please submit your preferences on the poll by the end of day on July 20, 2022.__ I created an etherpad to collect potential topics for the conversation and build an agenda for the call. Please add discussion points that you think would be important to bring up during the call: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync Please let me know if you have any questions. Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Jul 6, 2022, at 15:38, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > I?m reaching out to you to organize a call between the StarlingX project and the OpenInfra Foundation Board of Directors (BoD). > > The Open Infrastructure Foundation BoD is looking into engaging in regular check-ins with official OpenInfra projects in an online format. The goal of these meetings is to establish a closer connection and collaboration between the OpenInfra projects, including StarlingX, and the OpenInfra BoD group. This will help the Board to have a clearer view about each project?s state, achievements and challenges and it will be in a better position to support all the communities. At the same time, the projects will get a better understanding of the Board?s structure and responsibilities and have a better alignment with the group. > > The aim is to schedule a 1-hour long call some time in the upcoming weeks that will involve members of the Board as well as the StarlingX TSC along with further interested community members from the project. > > There is no expectation for a formal presentation from the projects and with that no materials have to be prepared in advance. If the community would like to provide an update in the form of a presentation that should work too. > > I created an etherpad to collect potential topics for the conversation and build an agenda for the call: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync > > I also created a poll to try to find time slot options that we can share with the OpenInfra Board of Directors. The poll is covering options for August, if we fail to find good options for that month, I will extend it to September. Please find the poll here: https://doodle.com/meeting/participate/id/b48Pv7Vb > > Both our BoD and community are distributed all around the globe and there is no time slot that works well well everywhere. In that sense, please mark ALL the time slots when you are available, so we can find one that is accessible for most of our Board and community members. > > __Please submit your preferences by the end of day on July 20, 2022.__ > > Please let me know if you have any questions. > > Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > From Peng.Peng at windriver.com Fri Jul 15 17:32:51 2022 From: Peng.Peng at windriver.com (Peng, Peng) Date: Fri, 15 Jul 2022 17:32:51 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20220714T014026Z Message-ID: Sanity Test from 2022-July-15 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220714T014026Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220714T014026Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Sanity Test executed on Bare Metal Environment AIO - Duplex Setup 1 TCs [PASS] Sanity Platform 09 TCs [PASS] Daily Regression Platform 10 TCs [PASS] TOTAL: [ 20 TCs ] Test case detail: 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[controller] 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_force_reboot_host[active_controller-True] PASS test_force_reboot_host[active_controller-False] PASS test_force_reboot_host[standby_controller-False] 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_isolated_1p_1pod[2-fill-static-best-effort-None-AIO] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] Kind regards, PV Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Sun Jul 17 21:42:12 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sun, 17 Jul 2022 21:42:12 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Jul 13/2022 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Sanity - Last Update - Community Call on July 6 - Expect to have a sanity report (w/o stx-openstack) - by July 8 - Plan is to work on sanity w/ stx-openstack once fixes are available for: - https://bugs.launchpad.net/starlingx/+bug/1978409 - merged July 12 - https://bugs.launchpad.net/starlingx/+bug/1980397 - still open - Sanity w/o stx-openstack - WR team was able to run an AIO-SX sanity. - Hit some issues w/ AIO-DX that are under investigation; TBD whether it's a procedural or software issue - Action: Rob to ensure sanity reports start getting sent this week. - Sanity w/ stx-openstack - Blocked on https://bugs.launchpad.net/starlingx/+bug/1980397 stx.7.0 - Reference Links: - Release/Feature Planning: https://docs.google.com/spreadsheets/d/171PJAu9SykXm9h9Ny2IsZ8YMbhvEwOzuTbISWUMQhiE/edit#gid=1107209846 - Release Verification: - Folder: https://drive.google.com/drive/folders/1szAP-xVZq7ebSyGJ-EHTVebMmsupSY7w - Feature Testing: https://docs.google.com/spreadsheets/d/1hXJJ4LvxhWwLIF_PHpCyxlGpfKdXtcPjlyclfKFVxKo/edit#gid=968103774 - Regression Testing: https://docs.google.com/spreadsheets/d/19OQmmo5OfD1eHS8rp5uBgnVaS7i8J-NhQuiKVqcyZ0Y/edit#gid=1717644237 - From TSC / Community Call on July 6 - Agreed that getting stx-openstack running on stx.7.0 is a release blocker - Plans in place to address the identified issues and re-enable stx-openstack - Two key fixes required which are forecast for ~July 12 - https://bugs.launchpad.net/starlingx/+bug/1978409 - merged July 12 - https://bugs.launchpad.net/starlingx/+bug/1980397 - still open - Some WIP reviews posted. Need an update from the openstack team; expected in the community call - Upcoming Milestones - Revised - Based on discussion in Community Call on July 13 - RC1 (Branch Creation): week of July 4 >> week of July 18 (based on above sanity plans) - Final Regression: week of July 18 >> week of July 25 - Release: week of July 25 >> week of Aug 1 - Branch Creation - Option 1: Go ahead and branch the r/stx.7.0 branch - suggested by Frank - PRO: Avoid pollution from content unrelated to stx.7.0 (ex: prep for stx.8.0 features / Debian / etc) - CON: If we branch w/o a sanity, we don't have a known state of the load - Option 2: Institute a freeze on the stx main branch - suggested by Ildiko - PRO: Nothing goes in, so no pollution from unrelated content - CON: Impact to more community members who are already looking at stx.8.0 or bugs - Decision - Agreed a sanity w/o stx-openstack is sufficient for branch creation as the required stx-openstack changes are understood and in progress. - If it's not red, we can proceed with branch creation next week as per the plan discussed last week. - Bug status - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.7.0 - In good shape. Only 3 LPs open. 2 are actively being worked and 1 is pending a sanity re-reun. - Docs - Majority of doc updates have merged. - Release notes in progress. Juanita expects to send draft this week. - Blogs - Release Announcement - Prime: Ildiko - In progress - Debian OS Migration - Prime: Frank Miller - PTP Enhancements - Dual NIC Support / SyncE / Various NIC Support - Prime: Ghada Khalil - Subcloud Local Install - Prime: RamS - Action: Each prime to provide forecast for draft info for the next planning meeting: July 27 stx.8.0 - Release folder and planning spreadsheet created: - Release Folder: https://drive.google.com/drive/folders/1qbnm3Zz5JzM16Drhw4locVQhn4uk7HI1?usp=sharing - Release/Feature Planning: https://docs.google.com/spreadsheets/d/1cjhRQm717zOTo2ngs5SEs3elhJwSRxFAI-ruqJaBe80/edit?usp=sharing - Milestones (based on typical durations) are proposed - Milestone-1 8/29/2022 - Milestone-2 - 4wks after MS-1 9/26/2022 - Milestone-3 - 10wks after MS-2 12/5/2022 - Feature Test Complete - 4wks after MS-3 1/2/2023 - Regression Test Start - 1wk after MS-3 (in parallel w/ feature test) 12/12/2022 - Regression Test Complete - 3wks after Regression Start 1/2/2023 - RC1 - 1wk after Regression Test Complete 1/9/2023 - Final Regression Complete - 2wks after RC1 1/23/2023 - Release - 1wk after Final Regression 1/30/2023 - Dates are currently aligned with the typical release cadence - one release in Jan and one in July. - Action: Release team to review; we'll discuss again in the next - Next steps: Populate with candidate features - Action: Community / PLs to update the planning spreadsheet From Ghada.Khalil at windriver.com Sun Jul 17 21:48:50 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sun, 17 Jul 2022 21:48:50 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (July 13 2022) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call July 13 2022 Standing Topics - Build - CentOS builds - Installer monolithic build issue (due to expat CVE fix) is addressed as of July 12 - LP: https://bugs.launchpad.net/starlingx/+bug/1980838 - Today's builds are passing now - Debian builds - Lock down of Debian release in stx Complete - Reviews merged - https://review.opendev.org/c/starlingx/tools/+/839126 - https://review.opendev.org/c/starlingx/root/+/844816 - Some Debian build failures were seen; likely due to the Debian upstream upgrade - Latest Debian build is still in progress. Build team will investigate if that failed. - Sanity - Sanity w/o stx-openstack - WR team was able to run an AIO-SX sanity. - Hit some issues w/ AIO-DX that are under investigation; TBD whether it's a procedural or software issue - Action: Rob to ensure sanity reports start getting sent to stx-discuss this week. - Sanity w/ stx-openstack - Blocked on https://bugs.launchpad.net/starlingx/+bug/1980397 - Gerrit Reviews in Need of Attention - Nothing brought up in the meeting today - Reference Links: - Active Branch (open): https://review.opendev.org/q/projects:starlingx+is:open+branch:+master - Active Branch (merged): https://review.opendev.org/q/projects:starlingx+is:merged+branch:master Topics for This Week - stx-openstack Support on stx.7.0 - LP: https://bugs.launchpad.net/starlingx/+bug/1980397 - Actively being worked. - Made some progress: - 60% of stx-openstack pods are applying properly - Currently investigating issues w/ neutron & nova pods getting stuck; looks to be related to volume attachment - Forecast: hard to predict at this time ARs from Previous Meetings - Edge infrastructure orchestration discussion with the edge WG - Meeting on July 18 - Closed. Greg will be attending. Open Requests for Help - Nothing new on the mailing list - Incorrect public key for signed starlingX 5.0 iso: http://lists.starlingx.io/pipermail/starlingx-discuss/2022-June/013072.html - Scott prepared a high level explanation last week which will be sent to the mailing list - Topic was also generally covered in TSC. Current proposal is to add some clarification on usage to the StarlingX docs. - Greg took the action to create a Doc story board to track the suggested updates. - Consider Closed From Ghada.Khalil at windriver.com Sun Jul 17 22:17:44 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sun, 17 Jul 2022 22:17:44 +0000 Subject: [Starlingx-discuss] Request to create the r/stx.7.0 release branch Message-ID: Hello StarlingX Build team, Given we have a successful sanity on the stx main branch, please proceed with creating the r/stx.7.0 release branch. This is in agreement with discussions in the release planning as well as the community meeting last week. Sanity Email: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-July/013161.html Thanks, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peng.Peng at windriver.com Tue Jul 19 13:23:46 2022 From: Peng.Peng at windriver.com (Peng, Peng) Date: Tue, 19 Jul 2022 13:23:46 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20220715T013854Z Message-ID: Sanity Test from 2022-July-18 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220715T013854Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20220715T013854Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Sanity Test executed on Bare Metal Environment AIO - Duplex Setup 1 TCs [PASS] Sanity Platform 09 TCs [PASS] Daily Regression Platform 10 TCs [PASS] TOTAL: [ 20 TCs ] Test case detail: 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[controller] 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_force_reboot_host[active_controller-True] PASS test_force_reboot_host[active_controller-False] PASS test_force_reboot_host[standby_controller-False] 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_isolated_1p_1pod[2-fill-static-best-effort-None-AIO] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] Kind regards, PV Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Wed Jul 20 16:03:59 2022 From: openinfradn at gmail.com (open infra) Date: Wed, 20 Jul 2022 21:33:59 +0530 Subject: [Starlingx-discuss] Use of --reuse-values in Nova config Message-ID: Hi, I referred to two documents while setting up, GPU passthrough in STX 6 and stx-openstack. In one of the documents [2], "--reuse-values" used twice within single command. What is the purpose of using "--reuse-values" twice? I hope it is not a typo. According to [1] ; ~(keystone_admin)$ system helm-override-update stx-openstack nova openstack --reuse-values --values=your-override-file.yaml ~(keystone_admin)$ system application-apply stx-openstack According to [2]; ~(keystone_admin)]$ system helm-override-update --reuse-values --values ./gpu_override.yaml stx-openstack nova openstack --reuse-values ~(keystone_admin)]$ system application-apply stx-openstack [1] https://docs.starlingx.io/node_management/openstack/configure-pci-passthrough-interface-to-nvidia-gpu.html [2] https://docs.starlingx.io/system_configuration/openstack/configuring-a-pci-alias-in-nova.html Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Jul 20 22:45:39 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 20 Jul 2022 22:45:39 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (July 20 2022) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call July 20 2022 Standing Topics - Build - CentOS builds - Builds are green this week. No failures. - Debian builds - Mostly green. One failure reported. - Sanity - Sanity w/o stx-openstack - Sanity is now running on AIO-DX and is green - Latest Report is Green: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-July/013165.html - Next step is to add AIO-SX to the sanity suite - Sanity w/ stx-openstack - Blocked on https://bugs.launchpad.net/starlingx/+bug/1980397 - Should be unblocked next week based on plan below - Gerrit Reviews in Need of Attention - stx.7.0 Release Notes: - https://review.opendev.org/c/starlingx/docs/+/850424 - Reference Links: - Active Branch (open): https://review.opendev.org/q/projects:starlingx+is:open+branch:+master - Active Branch (merged): https://review.opendev.org/q/projects:starlingx+is:merged+branch:master Topics for This Week - stx-openstack Support on stx.7.0 - LP: https://bugs.launchpad.net/starlingx/+bug/1980397 - Progress since last week: - The stx-openstack application is now applied w/ k8s 1.23 - Now facing issues w/ application removal, but it doesn't seem related to the recent changes - New LP opened: https://bugs.launchpad.net/starlingx/+bug/1982220 - This looks an existing issue. TBC - Agreed to proceed with the code review and merge. Then continue to investigate the removal issue. - Forecast: July 22 - stx.7.0 Release Branch Creation - As per community agreement, proceeding with branch creation given we have sanity reports - Request sent on July 17: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-July/013164.html - Both Scott & Davlet are out this week. Jason Norton will start the branch creation today: July 20 - High Level Steps: - Create branch and tag/build the first RC build - Start sanity on the RC builds - Cherry-pick required fixes - Once all fixes are in, build and run final sanity - Tag final build and update CENGN to move the build under the release directory ARs from Previous Meetings - None Open Requests for Help - Build Issues: https://lists.starlingx.io/pipermail/starlingx-discuss/2022-July/013157.html - Discussion ongoing. But not making progress this week since Scott & Davlet are both out From ildiko.vancsa at gmail.com Sat Jul 23 09:25:22 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Sat, 23 Jul 2022 11:25:22 +0200 Subject: [Starlingx-discuss] StarlingX Survey discussion follow up Message-ID: <897DBF0E-C59D-49D1-9D7C-C60CE98794A9@gmail.com> Hi StarlingX Community, I?m reaching out to provide some information as a follow up to the StarlingX survey discussion on the TSC & Community call this week. The open question during the call was: Where can the community see the info that?s been collected? A few people from the OpenInfra Foundation staff have access to the raw data. We cannot share that publicly due to confidentiality reasons. We aggregate and anonymize responses to these surveys before sharing, to ensure that our communities can still receive information that is important for them. You can find statistics extracted from the survey under the StarlingX section here: https://openinfra.dev/user-survey/ When the responders provide contact information I always reach out to them to find out more and encourage them to get in touch with the community. I usually share data and some specifics from the feedback section on the starlingx-discuss mailing list, where we get new results that contain responses to those questions. The responses from the past one year were partial and din't include feedback about the platform. Call to Action: If you know anyone who?s using or evaluating StarlingX but is not in touch with the community yet, please encourage them to fill out the survey to still help the contributors? work. As a reminder, you can find the survey here: https://www.surveymonkey.com/r/StarlingX We can also update some of the questions or the structure of the survey, if the community has a preference on any of that. Please let me know if you have any questions or comments on any of the above. Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation From Greg.Waines at windriver.com Mon Jul 25 11:10:40 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 25 Jul 2022 11:10:40 +0000 Subject: [Starlingx-discuss] Use of --reuse-values in Nova config In-Reply-To: References: Message-ID: See https://docs.starlingx.io/system_configuration/kubernetes/application-commands-and-helm-overrides.html ( the repeated --reuse-values on same command line is a typo, although it has no impact ) Greg. From: open infra Sent: Wednesday, July 20, 2022 12:04 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Use of --reuse-values in Nova config [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I referred to two documents while setting up, GPU passthrough in STX 6 and stx-openstack. In one of the documents [2], "--reuse-values" used twice within single command. What is the purpose of using "--reuse-values" twice? I hope it is not a typo. According to [1] ; ~(keystone_admin)$ system helm-override-update stx-openstack nova openstack --reuse-values --values=your-override-file.yaml ~(keystone_admin)$ system application-apply stx-openstack According to [2]; ~(keystone_admin)]$ system helm-override-update --reuse-values --values ./gpu_override.yaml stx-openstack nova openstack --reuse-values ~(keystone_admin)]$ system application-apply stx-openstack [1] https://docs.starlingx.io/node_management/openstack/configure-pci-passthrough-interface-to-nvidia-gpu.html [2] https://docs.starlingx.io/system_configuration/openstack/configuring-a-pci-alias-in-nova.html Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at optimcloud.com Mon Jul 25 12:40:52 2022 From: lists at optimcloud.com (Embedded Devel) Date: Mon, 25 Jul 2022 12:40:52 +0000 Subject: [Starlingx-discuss] calicoctl / calico containers stx 6.0 aio duplex and wireguard - DONE! In-Reply-To: <1632975869705.1585507874.3975460403@optimcloud.com> References: <1632974745542.605493260.58076787@optimcloud.com> <1632975869705.1585507874.3975460403@optimcloud.com> Message-ID: <1658752499190.46719352.2357280429@optimcloud.com> So literally after all the research I did on wireguard and a working model, in the dev lab, now i go to put it in production only to discover stx 6.0 has now literally disabled wireguard in the kernel, months of time and research is now wasted. I even mentioned it back in september and was told to file a bug report on previous errors with wireguard loading, then a later pre 6.0 appeared to have it fixed, and now i find in 6.0 ... # CONFIG_WIREGUARD is not set completely useless waste of time as well as when you upgraded mellanox drivers to the latest version rendering thousands of $s in hardware useless to us for future revisions of starlingX, im sorry but i really have to say Ive gotten to the point where i ask why i bother supporting stx, championing stx, and deploying it for clients, Im sorry but i am beyond fscking pissed off right now! On Thursday 30 September 2021 11:41:20 AM (+07:00), Embedded Devel wrote: > LOL Achievement unlocked ... it works now > steps to reproduce: > controller-0:~$ wget https://centos.pkgs.org/7/epel-testing-x86_64/wireguard-tools-1.0.20210914-1.el7.x86_64.rpm.html > > controller-0:~$ sudo yum install -y wireguard-tools-1.0.20210914-1.el7.x86_64.rpm Loaded plugins: fastestmirror > Examining wireguard-tools-1.0.20210914-1.el7.x86_64.rpm: wireguard-tools-1.0.20210914-1.el7.x86_64 > Marking wireguard-tools-1.0.20210914-1.el7.x86_64.rpm to be installed > Resolving Dependencies > --> Running transaction check > ---> Package wireguard-tools.x86_64 0:1.0.20210914-1.el7 will be installed > --> Finished Dependency Resolution > > Dependencies Resolved > > =============================================================================================================================================================== > Package Arch Version Repository Size > =============================================================================================================================================================== > > Installing: > wireguard-tools x86_64 1.0.20210914-1.el7 /wireguard-tools-1.0.20210914-1.el7.x86_64 291 k > > Transaction Summary > =============================================================================================================================================================== > > Install 1 Package > > Total size: 291 k > Installed size: 291 k > Downloading packages: > Running transaction check > Running transaction test > Transaction test succeeded > Running transaction > Installing : wireguard-tools-1.0.20210914-1.el7.x86_64 1/1 Verifying : wireguard-tools-1.0.20210914-1.el7.x86_64 1/1 > Installed: > wireguard-tools.x86_64 0:1.0.20210914-1.el7 > controller-0:~$ curl -o kubectl-calico -O -L "https://github.com/projectcalico/calicoctl/releases/download/v3.19.1/calicoctl" > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 100 615 100 615 0 0 1930 0 --:--:-- --:--:-- --:--:-- 1933 > 100 42.8M 100 42.8M 0 0 28.1M 0 0:00:01 0:00:01 --:--:-- 46.2M > controller-0:~$ chmod +x kubectl-calico > controller-0:~$ sudo mv kubectl-calico /bin/ > controller-0:~$ kubectl calico patch felixconfiguration default --type='merge' -p '{"spec":{"wireguardEnabled":true}}' > Successfully patched 1 'FelixConfiguration' resource > > controller-0:~$ sudo wg > interface: wireguard.cali > public key: LcaQ5thd7yo4thPR/d0g4LHCnWwEfVsLJaaveeQnago= > private key: (hidden) > listening port: 51820 > fwmark: 0x100000 > > peer: n1+ugi4bv8Vfpnhfau7/Uaqm/9RqhmQnQ9U+7DoOsj8= > endpoint: 192.168.206.3:51820 > allowed ips: 172.16.166.128/26, 172.16.166.128/32, 172.16.166.163/32 > controller-0:~$ > controller-1:~$ sudo wg > interface: wireguard.cali > public key: n1+ugi4bv8Vfpnhfau7/Uaqm/9RqhmQnQ9U+7DoOsj8= > private key: (hidden) > listening port: 51820 > fwmark: 0x100000 > > peer: LcaQ5thd7yo4thPR/d0g4LHCnWwEfVsLJaaveeQnago= > endpoint: 192.168.206.2:51820 > allowed ips: 172.16.192.64/32, 172.16.192.64/26, 172.16.192.87/32 > controller-1:~$ > > > > On Thursday 30 September 2021 11:11:01 AM (+07:00), Embedded Devel wrote: > > > based on the calico documentation, https://docs.projectcalico.org/security/encrypt-cluster-pod-traffic we should be able to patch felix calicoctl patch felixconfiguration default --type='merge' -p '{"spec":{"wireguardEnabled":true}}' > > > > I have a pre-6 stx aio duplex deployed, wireguard does work, i yum installed wireguard-tools, i can bring up the wg interface > > > > so two things, how can we execute calico commands ? i see 0 documentation on it > > > > and two im curious what wireguard firewall rules for calico would look like. > > > > id imagine based on the docs > > > > cat < gnp-oam-overrides.yaml > > apiVersion: crd.projectcalico.org/v1 > > kind: GlobalNetworkPolicy > > metadata: > > name: wg-oam-overrides > > spec: > > ingress: > > - action: Allow > > destination: > > ports: > > - 51820 > > protocol: UDP > > order: 500 > > selector: has(iftype) && iftype == 'oam' > > types: > > - Ingress > > EOF > > > > > > when applied, i cannot connect a remote client to the OAM address, or the floating address > > -- Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com From ildiko.vancsa at gmail.com Tue Jul 26 09:47:04 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 26 Jul 2022 11:47:04 +0200 Subject: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - UPDATE In-Reply-To: <6E9D75C2-7681-42CD-B2E3-0556CD366CC1@gmail.com> References: <6E9D75C2-7681-42CD-B2E3-0556CD366CC1@gmail.com> Message-ID: <92139142-1684-46A6-BD03-EA6CFA251478@gmail.com> Hi StarlingX Community, I?m reaching out to you with an update with regards to the sync call between the OpenInfra Foundation Board of Directors and the StarlingX community. The proposed meeting time that the Board is currently voting on, is August 4 (next Thursday) at 1300 UTC / 6am PDT / 8am CDT / 9pm CST. You can see the original email and follow the thread here: https://lists.openinfra.dev/pipermail/foundation-board/2022-July/000646.html As a reminder, we have an etherpad to propose topics for the call and take notes during the meeting: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync Please let me know if you have any questions. Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Jul 14, 2022, at 23:17, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > It is a friendly reminder to please fill out the poll to help organizing the sync call between the OpenInfra BoD and the StarlingX project. > > You can find the poll here: https://doodle.com/meeting/participate/id/b48Pv7Vb > > __Please submit your preferences on the poll by the end of day on July 20, 2022.__ > > > I created an etherpad to collect potential topics for the conversation and build an agenda for the call. Please add discussion points that you think would be important to bring up during the call: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync > > Please let me know if you have any questions. > > Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > >> On Jul 6, 2022, at 15:38, Ildiko Vancsa wrote: >> >> Hi StarlingX Community, >> >> I?m reaching out to you to organize a call between the StarlingX project and the OpenInfra Foundation Board of Directors (BoD). >> >> The Open Infrastructure Foundation BoD is looking into engaging in regular check-ins with official OpenInfra projects in an online format. The goal of these meetings is to establish a closer connection and collaboration between the OpenInfra projects, including StarlingX, and the OpenInfra BoD group. This will help the Board to have a clearer view about each project?s state, achievements and challenges and it will be in a better position to support all the communities. At the same time, the projects will get a better understanding of the Board?s structure and responsibilities and have a better alignment with the group. >> >> The aim is to schedule a 1-hour long call some time in the upcoming weeks that will involve members of the Board as well as the StarlingX TSC along with further interested community members from the project. >> >> There is no expectation for a formal presentation from the projects and with that no materials have to be prepared in advance. If the community would like to provide an update in the form of a presentation that should work too. >> >> I created an etherpad to collect potential topics for the conversation and build an agenda for the call: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >> >> I also created a poll to try to find time slot options that we can share with the OpenInfra Board of Directors. The poll is covering options for August, if we fail to find good options for that month, I will extend it to September. Please find the poll here: https://doodle.com/meeting/participate/id/b48Pv7Vb >> >> Both our BoD and community are distributed all around the globe and there is no time slot that works well well everywhere. In that sense, please mark ALL the time slots when you are available, so we can find one that is accessible for most of our Board and community members. >> >> __Please submit your preferences by the end of day on July 20, 2022.__ >> >> Please let me know if you have any questions. >> >> Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem >> Open Infrastructure Foundation >> >> >> > From Greg.Waines at windriver.com Tue Jul 26 10:41:13 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Tue, 26 Jul 2022 10:41:13 +0000 Subject: [Starlingx-discuss] StarlingX TSC & Community Call Message-ID: Both Ghada and I (and majority of wind river contributors) have conflicts this week with workshops at wind river, so we will have to cancel the TSC & Community call this week. We will re-convene next week. Greg. -----Original Appointment----- From: Zvonar, Bill Sent: Wednesday, October 7, 2020 10:57 AM To: Zvonar, Bill; starlingx-discuss at lists.starlingx.io Cc: Wensley, Barton; Jones, Bruce E Subject: [Starlingx-discuss] [Starlingx-discuss] StarlingX TSC & Community Call When: Wednesday, July 27, 2022 10:00 AM-11:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Tue Jul 26 13:29:59 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 26 Jul 2022 15:29:59 +0200 Subject: [Starlingx-discuss] 7.0 release overview blog post for review Message-ID: <45C2A4D8-2CDC-40FF-9165-1077A1A75859@gmail.com> Hi, I?ve put together an overview blog post to publish when the 7.0 release is out. You can find the draft here: https://github.com/StarlingXWeb/starlingx-website/pull/201 Please let me know if there?s anything to change or add/remove by reviewing the change or replying to this thread. Thanks and Best Regards, Ildik? From Greg.Waines at windriver.com Tue Jul 26 15:00:55 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Tue, 26 Jul 2022 15:00:55 +0000 Subject: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - UPDATE In-Reply-To: <92139142-1684-46A6-BD03-EA6CFA251478@gmail.com> References: <6E9D75C2-7681-42CD-B2E3-0556CD366CC1@gmail.com> <92139142-1684-46A6-BD03-EA6CFA251478@gmail.com> Message-ID: hey Ildiko, I am available on the Aug 4 1300 UTC timeslot. What's the format for this meeting ? ... i.e. just informal discussion or are they expecting StarlingX to present something ? I added our favourite discussion topic to the etherpad: * Looking for guidance on diversifying the Users and Contributors in the community Greg. -----Original Message----- From: Ildiko Vancsa Sent: Tuesday, July 26, 2022 5:47 AM To: StarlingX ML Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - UPDATE [Please note: This e-mail is from an EXTERNAL e-mail address] Hi StarlingX Community, I?m reaching out to you with an update with regards to the sync call between the OpenInfra Foundation Board of Directors and the StarlingX community. The proposed meeting time that the Board is currently voting on, is August 4 (next Thursday) at 1300 UTC / 6am PDT / 8am CDT / 9pm CST. You can see the original email and follow the thread here: https://lists.openinfra.dev/pipermail/foundation-board/2022-July/000646.html As a reminder, we have an etherpad to propose topics for the call and take notes during the meeting: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync Please let me know if you have any questions. Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Jul 14, 2022, at 23:17, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > It is a friendly reminder to please fill out the poll to help organizing the sync call between the OpenInfra BoD and the StarlingX project. > > You can find the poll here: > https://doodle.com/meeting/participate/id/b48Pv7Vb > > __Please submit your preferences on the poll by the end of day on July > 20, 2022.__ > > > I created an etherpad to collect potential topics for the conversation > and build an agenda for the call. Please add discussion points that > you think would be important to bring up during the call: > https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync > > Please let me know if you have any questions. > > Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > >> On Jul 6, 2022, at 15:38, Ildiko Vancsa wrote: >> >> Hi StarlingX Community, >> >> I?m reaching out to you to organize a call between the StarlingX project and the OpenInfra Foundation Board of Directors (BoD). >> >> The Open Infrastructure Foundation BoD is looking into engaging in regular check-ins with official OpenInfra projects in an online format. The goal of these meetings is to establish a closer connection and collaboration between the OpenInfra projects, including StarlingX, and the OpenInfra BoD group. This will help the Board to have a clearer view about each project?s state, achievements and challenges and it will be in a better position to support all the communities. At the same time, the projects will get a better understanding of the Board?s structure and responsibilities and have a better alignment with the group. >> >> The aim is to schedule a 1-hour long call some time in the upcoming weeks that will involve members of the Board as well as the StarlingX TSC along with further interested community members from the project. >> >> There is no expectation for a formal presentation from the projects and with that no materials have to be prepared in advance. If the community would like to provide an update in the form of a presentation that should work too. >> >> I created an etherpad to collect potential topics for the >> conversation and build an agenda for the call: >> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >> >> I also created a poll to try to find time slot options that we can >> share with the OpenInfra Board of Directors. The poll is covering >> options for August, if we fail to find good options for that month, I >> will extend it to September. Please find the poll here: >> https://doodle.com/meeting/participate/id/b48Pv7Vb >> >> Both our BoD and community are distributed all around the globe and there is no time slot that works well well everywhere. In that sense, please mark ALL the time slots when you are available, so we can find one that is accessible for most of our Board and community members. >> >> __Please submit your preferences by the end of day on July 20, >> 2022.__ >> >> Please let me know if you have any questions. >> >> Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >> >> >> > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Wed Jul 27 01:28:04 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 27 Jul 2022 01:28:04 +0000 Subject: [Starlingx-discuss] No StarlingX release meeting on July 27 Message-ID: Hello all, I cannot host the StarlingX release meeting tomorrow due to a conflict. Therefore, I will be canceling the meeting. My apologies for the short notice. Regards, Ghada From scott.little at windriver.com Wed Jul 27 03:54:50 2022 From: scott.little at windriver.com (Scott Little) Date: Tue, 26 Jul 2022 23:54:50 -0400 Subject: [Starlingx-discuss] [Action Required] Please review branch creation for r/stx.7.0 Message-ID: <0a0d2d3c-0199-c64e-87e3-f6acca1efc36@windriver.com> The full set of reviews is ... ?? https://review.opendev.org/q/topic:r.stx.7.0 Note: There are multiple pages of reviews. From Ghada.Khalil at windriver.com Wed Jul 27 00:54:30 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 27 Jul 2022 00:54:30 +0000 Subject: [Starlingx-discuss] Canceled: Bi-weekly StarlingX Release Meeting (new time) Message-ID: I cannot host the StarlingX release meeting tomorrow due to a conflict. Therefore, I will be canceling the meeting. My apologies for the short notice. New meeting series for the StarlingX Release Meeting Bi-weekly meeting on Wednesday 06:30AM PT / 09:30AM ET / 02:30PM UTC Zoom Link: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 Meeting agenda/minutes: https://etherpad.openstack.org/p/stx-releases -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3347 bytes Desc: not available URL: From ildiko.vancsa at gmail.com Wed Jul 27 06:15:56 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 27 Jul 2022 08:15:56 +0200 Subject: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - UPDATE In-Reply-To: References: <6E9D75C2-7681-42CD-B2E3-0556CD366CC1@gmail.com> <92139142-1684-46A6-BD03-EA6CFA251478@gmail.com> Message-ID: <00BCFA6E-E921-47DA-815F-BBF1B6F851A9@gmail.com> Hi Greg, Great, thank you for being available! The format is planned to be an informal conversation, there is no expectation from the community to deliver a presentation. I think diversity is a great topic for the call and should be a basis for a good discussion. I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra Board of Directors group! If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Jul 26, 2022, at 17:00, Waines, Greg wrote: > > hey Ildiko, > I am available on the Aug 4 1300 UTC timeslot. > What's the format for this meeting ? ... i.e. just informal discussion or are they expecting StarlingX to present something ? > > I added our favourite discussion topic to the etherpad: > * Looking for guidance on diversifying the Users and Contributors in the community > > Greg. > > -----Original Message----- > From: Ildiko Vancsa > Sent: Tuesday, July 26, 2022 5:47 AM > To: StarlingX ML > Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - UPDATE > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi StarlingX Community, > > I?m reaching out to you with an update with regards to the sync call between the OpenInfra Foundation Board of Directors and the StarlingX community. > > The proposed meeting time that the Board is currently voting on, is August 4 (next Thursday) at 1300 UTC / 6am PDT / 8am CDT / 9pm CST. > > You can see the original email and follow the thread here: https://lists.openinfra.dev/pipermail/foundation-board/2022-July/000646.html > > As a reminder, we have an etherpad to propose topics for the call and take notes during the meeting: https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync > > Please let me know if you have any questions. > > Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > >> On Jul 14, 2022, at 23:17, Ildiko Vancsa wrote: >> >> Hi StarlingX Community, >> >> It is a friendly reminder to please fill out the poll to help organizing the sync call between the OpenInfra BoD and the StarlingX project. >> >> You can find the poll here: >> https://doodle.com/meeting/participate/id/b48Pv7Vb >> >> __Please submit your preferences on the poll by the end of day on July >> 20, 2022.__ >> >> >> I created an etherpad to collect potential topics for the conversation >> and build an agenda for the call. Please add discussion points that >> you think would be important to bring up during the call: >> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >> >> Please let me know if you have any questions. >> >> Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem >> Open Infrastructure Foundation >> >> >> >>> On Jul 6, 2022, at 15:38, Ildiko Vancsa wrote: >>> >>> Hi StarlingX Community, >>> >>> I?m reaching out to you to organize a call between the StarlingX project and the OpenInfra Foundation Board of Directors (BoD). >>> >>> The Open Infrastructure Foundation BoD is looking into engaging in regular check-ins with official OpenInfra projects in an online format. The goal of these meetings is to establish a closer connection and collaboration between the OpenInfra projects, including StarlingX, and the OpenInfra BoD group. This will help the Board to have a clearer view about each project?s state, achievements and challenges and it will be in a better position to support all the communities. At the same time, the projects will get a better understanding of the Board?s structure and responsibilities and have a better alignment with the group. >>> >>> The aim is to schedule a 1-hour long call some time in the upcoming weeks that will involve members of the Board as well as the StarlingX TSC along with further interested community members from the project. >>> >>> There is no expectation for a formal presentation from the projects and with that no materials have to be prepared in advance. If the community would like to provide an update in the form of a presentation that should work too. >>> >>> I created an etherpad to collect potential topics for the >>> conversation and build an agenda for the call: >>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>> >>> I also created a poll to try to find time slot options that we can >>> share with the OpenInfra Board of Directors. The poll is covering >>> options for August, if we fail to find good options for that month, I >>> will extend it to September. Please find the poll here: >>> https://doodle.com/meeting/participate/id/b48Pv7Vb >>> >>> Both our BoD and community are distributed all around the globe and there is no time slot that works well well everywhere. In that sense, please mark ALL the time slots when you are available, so we can find one that is accessible for most of our Board and community members. >>> >>> __Please submit your preferences by the end of day on July 20, >>> 2022.__ >>> >>> Please let me know if you have any questions. >>> >>> Best Regards, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>> >>> >>> >> > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Wed Jul 27 06:42:00 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 27 Jul 2022 08:42:00 +0200 Subject: [Starlingx-discuss] No StarlingX release meeting on July 27 In-Reply-To: References: Message-ID: Hi Ghada, Thank you for the heads up about canceling the call today. Since the 7.0 release is still forecasted for next week and there were bugs and remaining testing activities that the community has been working on, do you have any updates about the release timeline? And new forecast, if there?s any? Thanks, Ildik? > On Jul 27, 2022, at 03:28, Khalil, Ghada wrote: > > Hello all, > I cannot host the StarlingX release meeting tomorrow due to a conflict. Therefore, I will be canceling the meeting. My apologies for the short notice. > > Regards, > Ghada > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Greg.Waines at windriver.com Wed Jul 27 10:55:27 2022 From: Greg.Waines at windriver.com (Waines, Greg) Date: Wed, 27 Jul 2022 10:55:27 +0000 Subject: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - UPDATE In-Reply-To: <00BCFA6E-E921-47DA-815F-BBF1B6F851A9@gmail.com> References: <6E9D75C2-7681-42CD-B2E3-0556CD366CC1@gmail.com> <92139142-1684-46A6-BD03-EA6CFA251478@gmail.com> <00BCFA6E-E921-47DA-815F-BBF1B6F851A9@gmail.com> Message-ID: I can't find the zoom link for the meeting ... do you have it ? Greg. -----Original Message----- From: Ildiko Vancsa Sent: Wednesday, July 27, 2022 2:16 AM To: Waines, Greg Cc: StarlingX ML Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - UPDATE [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Greg, Great, thank you for being available! The format is planned to be an informal conversation, there is no expectation from the community to deliver a presentation. I think diversity is a great topic for the call and should be a basis for a good discussion. I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra Board of Directors group! If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation > On Jul 26, 2022, at 17:00, Waines, Greg wrote: > > hey Ildiko, > I am available on the Aug 4 1300 UTC timeslot. > What's the format for this meeting ? ... i.e. just informal discussion or are they expecting StarlingX to present something ? > > I added our favourite discussion topic to the etherpad: > * Looking for guidance on diversifying the Users and > Contributors in the community > > Greg. > > -----Original Message----- > From: Ildiko Vancsa > Sent: Tuesday, July 26, 2022 5:47 AM > To: StarlingX ML > Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - > StarlingX Sync - UPDATE > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi StarlingX Community, > > I?m reaching out to you with an update with regards to the sync call between the OpenInfra Foundation Board of Directors and the StarlingX community. > > The proposed meeting time that the Board is currently voting on, is August 4 (next Thursday) at 1300 UTC / 6am PDT / 8am CDT / 9pm CST. > > You can see the original email and follow the thread here: > https://lists.openinfra.dev/pipermail/foundation-board/2022-July/00064 > 6.html > > As a reminder, we have an etherpad to propose topics for the call and > take notes during the meeting: > https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync > > Please let me know if you have any questions. > > Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > >> On Jul 14, 2022, at 23:17, Ildiko Vancsa wrote: >> >> Hi StarlingX Community, >> >> It is a friendly reminder to please fill out the poll to help organizing the sync call between the OpenInfra BoD and the StarlingX project. >> >> You can find the poll here: >> https://doodle.com/meeting/participate/id/b48Pv7Vb >> >> __Please submit your preferences on the poll by the end of day on >> July 20, 2022.__ >> >> >> I created an etherpad to collect potential topics for the >> conversation and build an agenda for the call. Please add discussion >> points that you think would be important to bring up during the call: >> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >> >> Please let me know if you have any questions. >> >> Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >> >> >> >>> On Jul 6, 2022, at 15:38, Ildiko Vancsa wrote: >>> >>> Hi StarlingX Community, >>> >>> I?m reaching out to you to organize a call between the StarlingX project and the OpenInfra Foundation Board of Directors (BoD). >>> >>> The Open Infrastructure Foundation BoD is looking into engaging in regular check-ins with official OpenInfra projects in an online format. The goal of these meetings is to establish a closer connection and collaboration between the OpenInfra projects, including StarlingX, and the OpenInfra BoD group. This will help the Board to have a clearer view about each project?s state, achievements and challenges and it will be in a better position to support all the communities. At the same time, the projects will get a better understanding of the Board?s structure and responsibilities and have a better alignment with the group. >>> >>> The aim is to schedule a 1-hour long call some time in the upcoming weeks that will involve members of the Board as well as the StarlingX TSC along with further interested community members from the project. >>> >>> There is no expectation for a formal presentation from the projects and with that no materials have to be prepared in advance. If the community would like to provide an update in the form of a presentation that should work too. >>> >>> I created an etherpad to collect potential topics for the >>> conversation and build an agenda for the call: >>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>> >>> I also created a poll to try to find time slot options that we can >>> share with the OpenInfra Board of Directors. The poll is covering >>> options for August, if we fail to find good options for that month, I >>> will extend it to September. Please find the poll here: >>> https://doodle.com/meeting/participate/id/b48Pv7Vb >>> >>> Both our BoD and community are distributed all around the globe and there is no time slot that works well well everywhere. In that sense, please mark ALL the time slots when you are available, so we can find one that is accessible for most of our Board and community members. >>> >>> __Please submit your preferences by the end of day on July 20, >>> 2022.__ >>> >>> Please let me know if you have any questions. >>> >>> Best Regards, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>> >>> >>> >> > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Wed Jul 27 12:32:55 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 27 Jul 2022 14:32:55 +0200 Subject: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - UPDATE In-Reply-To: References: <6E9D75C2-7681-42CD-B2E3-0556CD366CC1@gmail.com> <92139142-1684-46A6-BD03-EA6CFA251478@gmail.com> <00BCFA6E-E921-47DA-815F-BBF1B6F851A9@gmail.com> Message-ID: Hi Greg, I believe it is still being finalized with the Board if the proposed time will work for them. Once that is determined Julia will share the dial-in information. Best Regards, Ildik? > On Jul 27, 2022, at 12:55, Waines, Greg wrote: > > I can't find the zoom link for the meeting ... do you have it ? > Greg. > > -----Original Message----- > From: Ildiko Vancsa > Sent: Wednesday, July 27, 2022 2:16 AM > To: Waines, Greg > Cc: StarlingX ML > Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - StarlingX Sync - UPDATE > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi Greg, > > Great, thank you for being available! > > The format is planned to be an informal conversation, there is no expectation from the community to deliver a presentation. > > I think diversity is a great topic for the call and should be a basis for a good discussion. > > I would also like to encourage everyone from the community to join the call to build and foster a good relationship between the StarlingX community and the OpenInfra Board of Directors group! > > If you have any questions or need more information and background before being able to join please feel free to reach out to me or just reply to this thread to discuss. > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Senior Manager, Community & Ecosystem > Open Infrastructure Foundation > > > >> On Jul 26, 2022, at 17:00, Waines, Greg wrote: >> >> hey Ildiko, >> I am available on the Aug 4 1300 UTC timeslot. >> What's the format for this meeting ? ... i.e. just informal discussion or are they expecting StarlingX to present something ? >> >> I added our favourite discussion topic to the etherpad: >> * Looking for guidance on diversifying the Users and >> Contributors in the community >> >> Greg. >> >> -----Original Message----- >> From: Ildiko Vancsa >> Sent: Tuesday, July 26, 2022 5:47 AM >> To: StarlingX ML >> Subject: Re: [Starlingx-discuss] OpenInfra Board of Directors - >> StarlingX Sync - UPDATE >> >> [Please note: This e-mail is from an EXTERNAL e-mail address] >> >> Hi StarlingX Community, >> >> I?m reaching out to you with an update with regards to the sync call between the OpenInfra Foundation Board of Directors and the StarlingX community. >> >> The proposed meeting time that the Board is currently voting on, is August 4 (next Thursday) at 1300 UTC / 6am PDT / 8am CDT / 9pm CST. >> >> You can see the original email and follow the thread here: >> https://lists.openinfra.dev/pipermail/foundation-board/2022-July/00064 >> 6.html >> >> As a reminder, we have an etherpad to propose topics for the call and >> take notes during the meeting: >> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >> >> Please let me know if you have any questions. >> >> Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Senior Manager, Community & Ecosystem >> Open Infrastructure Foundation >> >> >> >>> On Jul 14, 2022, at 23:17, Ildiko Vancsa wrote: >>> >>> Hi StarlingX Community, >>> >>> It is a friendly reminder to please fill out the poll to help organizing the sync call between the OpenInfra BoD and the StarlingX project. >>> >>> You can find the poll here: >>> https://doodle.com/meeting/participate/id/b48Pv7Vb >>> >>> __Please submit your preferences on the poll by the end of day on >>> July 20, 2022.__ >>> >>> >>> I created an etherpad to collect potential topics for the >>> conversation and build an agenda for the call. Please add discussion >>> points that you think would be important to bring up during the call: >>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>> >>> Please let me know if you have any questions. >>> >>> Best Regards, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>> >>> >>> >>>> On Jul 6, 2022, at 15:38, Ildiko Vancsa wrote: >>>> >>>> Hi StarlingX Community, >>>> >>>> I?m reaching out to you to organize a call between the StarlingX project and the OpenInfra Foundation Board of Directors (BoD). >>>> >>>> The Open Infrastructure Foundation BoD is looking into engaging in regular check-ins with official OpenInfra projects in an online format. The goal of these meetings is to establish a closer connection and collaboration between the OpenInfra projects, including StarlingX, and the OpenInfra BoD group. This will help the Board to have a clearer view about each project?s state, achievements and challenges and it will be in a better position to support all the communities. At the same time, the projects will get a better understanding of the Board?s structure and responsibilities and have a better alignment with the group. >>>> >>>> The aim is to schedule a 1-hour long call some time in the upcoming weeks that will involve members of the Board as well as the StarlingX TSC along with further interested community members from the project. >>>> >>>> There is no expectation for a formal presentation from the projects and with that no materials have to be prepared in advance. If the community would like to provide an update in the form of a presentation that should work too. >>>> >>>> I created an etherpad to collect potential topics for the >>>> conversation and build an agenda for the call: >>>> https://etherpad.opendev.org/p/2022-summer-bod-starlingx-sync >>>> >>>> I also created a poll to try to find time slot options that we can >>>> share with the OpenInfra Board of Directors. The poll is covering >>>> options for August, if we fail to find good options for that month, I >>>> will extend it to September. Please find the poll here: >>>> https://doodle.com/meeting/participate/id/b48Pv7Vb >>>> >>>> Both our BoD and community are distributed all around the globe and there is no time slot that works well well everywhere. In that sense, please mark ALL the time slots when you are available, so we can find one that is accessible for most of our Board and community members. >>>> >>>> __Please submit your preferences by the end of day on July 20, >>>> 2022.__ >>>> >>>> Please let me know if you have any questions. >>>> >>>> Best Regards, >>>> Ildik? >>>> >>>> ??? >>>> >>>> Ildik? V?ncsa >>>> Senior Manager, Community & Ecosystem Open Infrastructure Foundation >>>> >>>> >>>> >>> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From scott.little at windriver.com Wed Jul 27 13:41:46 2022 From: scott.little at windriver.com (Scott Little) Date: Wed, 27 Jul 2022 09:41:46 -0400 Subject: [Starlingx-discuss] [Action Required] Please review branch creation for r/stx.7.0 In-Reply-To: <0a0d2d3c-0199-c64e-87e3-f6acca1efc36@windriver.com> References: <0a0d2d3c-0199-c64e-87e3-f6acca1efc36@windriver.com> Message-ID: <03059c34-ff5f-0d1a-5203-801500f11661@windriver.com> The branch was created from a timestamp of 2022-07-26 17:20:00 GMT, aka 1:20 pm Eastern Scott On 2022-07-26 23:54, Scott Little wrote: > The full set of reviews is ... > > ?? https://review.opendev.org/q/topic:r.stx.7.0 > > Note: There are multiple pages of reviews. > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Wed Jul 27 13:55:08 2022 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 27 Jul 2022 13:55:08 +0000 Subject: [Starlingx-discuss] No StarlingX release meeting on July 27 In-Reply-To: References: Message-ID: Hi Ildiko / all, The status is as follows: - A fix for the key openstack LP has been merged: https://bugs.launchpad.net/starlingx/+bug/1978409 - r/stx.7.0 branch creation is in progress. Email sent to the mailing list for reviews. - Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.7.0 -- 2 still open - Sanity: The WR team is working on setting up a sanity w/ openstack Regards, Ghada -----Original Message----- From: Ildiko Vancsa Sent: Wednesday, July 27, 2022 2:42 AM To: Khalil, Ghada Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] No StarlingX release meeting on July 27 [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Ghada, Thank you for the heads up about canceling the call today. Since the 7.0 release is still forecasted for next week and there were bugs and remaining testing activities that the community has been working on, do you have any updates about the release timeline? And new forecast, if there?s any? Thanks, Ildik? > On Jul 27, 2022, at 03:28, Khalil, Ghada wrote: > > Hello all, > I cannot host the StarlingX release meeting tomorrow due to a conflict. Therefore, I will be canceling the meeting. My apologies for the short notice. > > Regards, > Ghada > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Chandan.Kumar at commscope.com Wed Jul 27 13:57:00 2022 From: Chandan.Kumar at commscope.com (Kumar, Chandan) Date: Wed, 27 Jul 2022 13:57:00 +0000 Subject: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . In-Reply-To: References: <424ce5c6-7965-c694-11c9-0dbdf7a3ace3@windriver.com> Message-ID: Hi Scott, I was going through the procedure that you have shared below. Please clarify these two points: * The rpms need to be unpacked, the relevant binaries signed with correct keys, and the rpms reassembled. : The signing server unpacks images like BOOTX64, shim, shimx64 to get rpms, then signs it using `sbsign` and then repack it as original image. Is this understanding correct ? * shim.crt - Certificated embedded within shim used to validate kernel, grub : How is this certificate embedded inside shim image ? I got review notification for launchpad, I had raised but could not find where to add comments so replying to this mail. Regards, Chandan Kumar. From: Waines, Greg Sent: Wednesday, July 13, 2022 8:14 PM To: StarlingX ML Cc: Kumar, Chandan Subject: FW: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . Forwarding ?. I think scott meant this for the starlingx discuss list. Greg. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? External (greg.waines at windriver.com) Report This Email FAQ Protection by INKY Forwarding ?. I think scott meant this for the starlingx discuss list. Greg. From: Little, Scott > Sent: Wednesday, July 6, 2022 2:37 PM To: Waines, Greg > Subject: Re: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . I'll attempt to answer this at a high level. Secure boot signing uses a client/server approach. build-pkgs acts as the client. The server holds the signing scripts and the keys used for signing. The client side code was released to open source as part of StarlingX. The server side code was not released. The interface between client and server is currently undocumented. I'll try to give an overview as best I can. Basically it is a series of ssh/scp calls made into signing server. 'build-pkgs' requires that the following environment variables be defined before it will attempt to request a secure boot signing. export SIGNING_SERVER= export SIGNING_USER= export SIGNING_SERVER_SCRIPT= 'build-pkgs' further requires that "$USER" == "jenkins", and export FORMAL_BUILD=1 If that is satisfied, it calls into 'sign-secure-boot' 'sign-secure-boot' contains a fairly good set of comments describing what happens next. The client side call sequence looks like this ... # Set up the server side directory for files transfers. UPLOAD_PATH=`ssh $SIGNING_USER@$SIGNING_SERVER sudo $SIGNING_SCRIPT -r` # upload the original package scp -q $FILE $SIGNING_USER@$SIGNING_SERVER:$UPLOAD_PATH # Request that the package be signed ssh $SIGNING_USER@$SIGNING_SERVER sudo $SIGNING_SCRIPT -v -i $UPLOAD_PATH/$(basename $FILE) $UNSIGNED_OPTION -t $TYPE > $TMPFILE # Download the file from the signing server DOWNLOAD_FILENAME=$(basename $OUTPUT_FILE) scp -q $SIGNING_USER@$SIGNING_SERVER:$OUTPUT_FILE $(dirname $FILE) Within the signing server there are two keys used for signing, known as the 'boot' key and the 'shim' key. The public half of the 'boot' key must manually added to the secure boot keychain in firmware. The 'boot' key signs first executable loaded, contained in the 'shim' package. The first executable must then install the public half of the shim key (automatically) before passing control to grub, and ultimately the kernel, both of which are signed by the 'shim' key. Three packages need to be passed to the signing server. The rpms need to be unpacked, the relevant binaries signed with correct keys, and the rpms reassembled. package key files to sign ========= ==== =========================== shim boot BOOTX64, shim, shimx64 shim MokManager, fallback, mmx64, fbx64 grub shim grubx64.efi, gcdx64.efi kernel shim vmlinuz NOTE: shim files to sign might include a '.efi' or '.EFI' suffix. Sign those as well. NOTE: some files may be absent in newer packages. It is probably ok if some of the above are missing. Signing looks like this ... sbsign --key $KEYPATH/$KEYNAME.key --cert $KEYPATH/$KEYNAME.crt --output $SIGNEDFILE $UNSIGNEDFILE On keys and certs ... boot.crt - Certificate to boot (to be programmed in firmware) boot.key - Private key with which to sign shim shim.crt - Certificated embedded within shim used to validate kernel, grub shim.key - Private key with which to sign kernel/grub key generation ... openssl req -new -x509 -newkey rsa:2048 -keyout $KEY.key -out $KEY.pem -days 3650 openssl x509 -in $KEY.pem -out $KEY.crt -outform DER Note: boot.crt should be copied to cgcs-root/build-tools/certificates/TiBoot.crt for inclusion during the 'build-iso' step Hope this helps Scott On 2022-07-05 03:19, Kumar, Chandan wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Greg, Thanks for acknowledgement. I have raised starlingx launchpad for document update. Meanwhile it would be really great if you can share the steps which has to be done to integrate signing of images as part of StarlingX build infrastructure. Regards, Chandan Kumar. From: Waines, Greg Sent: Monday, July 4, 2022 6:00 PM To: starlingx-discuss at lists.starlingx.io Cc: Little, Scott Subject: Re: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . Hey Chandan, Thanks for bringing this up. I chatted with Scott about this. Currently the StarlingX public builds on CENGN are not building a secure boot capable load ? i.e. signing the appropriate items to enable secure boot. Although the StarlingX build infrastructure allows it to be added. Neither of these points are properly documented in docs.starlingx.io ? I can?t remember the details of why we are not doing this. I am guessing that the thinking was that a user of StarlingX that wanted to use UEFI Secure Boot, would want to sign with his own private key. Can you raise a starlingx launchpad ( https://launchpad.net/starlingx ) to address the docs.starlingx.io documentation issue, i.e. to indicate that the StarlingX CENGN builds are not signed to support uefi secure boot, and describe how a starlingx user could add signing to their StarlingX build environment in order to sign for uefi secure boot with their own private key ? Greg. From: Scott Little > Sent: Wednesday, June 29, 2022 10:42 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . On 2022-06-02 13:12, Kumar, Chandan wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I am trying to validate signed starlingX 5.0 iso on a secureboot enabled setup against public key(TiBoot.crt) embedded inside iso. After rebooting , operating system is not coming up with error screen saying ?Verification failed: (0X1A) Security Violation?. However, when I signed images with self-generated private key and validated against corresponding public key, system is able to boot up successfully. Signing is done after flashing the iso on a server. Please find attached procedure for signing images inside iso. I believe, the public key provided with iso is not correct. Can you please confirm ? Regards, Chandan Kumar. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss Thanks for the report. I'll look into it Scott Little -------------- next part -------------- An HTML attachment was scrubbed... URL: From starlingx.build at gmail.com Wed Jul 27 18:37:22 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 27 Jul 2022 14:37:22 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_compiler - Build # 1 - Failure! Message-ID: <1277616022.178.1658947044249.JavaMail.javamailuser@localhost> Project: STX_7.0_build_layer_compiler Build #: 1 Status: Failure Timestamp: 20220727T174951Z Branch: r/stx.7.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/compiler/20220727T174951Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true From Juanita.Balaraj at windriver.com Wed Jul 27 19:43:59 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Wed, 27 Jul 2022 19:43:59 +0000 Subject: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . In-Reply-To: References: <424ce5c6-7965-c694-11c9-0dbdf7a3ace3@windriver.com> Message-ID: + Elisa FYI Related to Gerrit Review https://review.opendev.org/c/starlingx/docs/+/851084 Thanks Juanita From: Kumar, Chandan Sent: July 27, 2022 9:57 AM To: Waines, Greg ; StarlingX ML ; Little, Scott Subject: Re: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Scott, I was going through the procedure that you have shared below. Please clarify these two points: * The rpms need to be unpacked, the relevant binaries signed with correct keys, and the rpms reassembled. : The signing server unpacks images like BOOTX64, shim, shimx64 to get rpms, then signs it using `sbsign` and then repack it as original image. Is this understanding correct ? * shim.crt - Certificated embedded within shim used to validate kernel, grub : How is this certificate embedded inside shim image ? I got review notification for launchpad, I had raised but could not find where to add comments so replying to this mail. Regards, Chandan Kumar. From: Waines, Greg > Sent: Wednesday, July 13, 2022 8:14 PM To: StarlingX ML > Cc: Kumar, Chandan > Subject: FW: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . Forwarding ?. I think scott meant this for the starlingx discuss list. Greg. From: Little, Scott > Sent: Wednesday, July 6, 2022 2:37 PM To: Waines, Greg > Subject: Re: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . I'll attempt to answer this at a high level. Secure boot signing uses a client/server approach. build-pkgs acts as the client. The server holds the signing scripts and the keys used for signing. The client side code was released to open source as part of StarlingX. The server side code was not released. The interface between client and server is currently undocumented. I'll try to give an overview as best I can. Basically it is a series of ssh/scp calls made into signing server. 'build-pkgs' requires that the following environment variables be defined before it will attempt to request a secure boot signing. export SIGNING_SERVER= export SIGNING_USER= export SIGNING_SERVER_SCRIPT= 'build-pkgs' further requires that "$USER" == "jenkins", and export FORMAL_BUILD=1 If that is satisfied, it calls into 'sign-secure-boot' 'sign-secure-boot' contains a fairly good set of comments describing what happens next. The client side call sequence looks like this ... # Set up the server side directory for files transfers. UPLOAD_PATH=`ssh $SIGNING_USER@$SIGNING_SERVER sudo $SIGNING_SCRIPT -r` # upload the original package scp -q $FILE $SIGNING_USER@$SIGNING_SERVER:$UPLOAD_PATH # Request that the package be signed ssh $SIGNING_USER@$SIGNING_SERVER sudo $SIGNING_SCRIPT -v -i $UPLOAD_PATH/$(basename $FILE) $UNSIGNED_OPTION -t $TYPE > $TMPFILE # Download the file from the signing server DOWNLOAD_FILENAME=$(basename $OUTPUT_FILE) scp -q $SIGNING_USER@$SIGNING_SERVER:$OUTPUT_FILE $(dirname $FILE) Within the signing server there are two keys used for signing, known as the 'boot' key and the 'shim' key. The public half of the 'boot' key must manually added to the secure boot keychain in firmware. The 'boot' key signs first executable loaded, contained in the 'shim' package. The first executable must then install the public half of the shim key (automatically) before passing control to grub, and ultimately the kernel, both of which are signed by the 'shim' key. Three packages need to be passed to the signing server. The rpms need to be unpacked, the relevant binaries signed with correct keys, and the rpms reassembled. package key files to sign ========= ==== =========================== shim boot BOOTX64, shim, shimx64 shim MokManager, fallback, mmx64, fbx64 grub shim grubx64.efi, gcdx64.efi kernel shim vmlinuz NOTE: shim files to sign might include a '.efi' or '.EFI' suffix. Sign those as well. NOTE: some files may be absent in newer packages. It is probably ok if some of the above are missing. Signing looks like this ... sbsign --key $KEYPATH/$KEYNAME.key --cert $KEYPATH/$KEYNAME.crt --output $SIGNEDFILE $UNSIGNEDFILE On keys and certs ... boot.crt - Certificate to boot (to be programmed in firmware) boot.key - Private key with which to sign shim shim.crt - Certificated embedded within shim used to validate kernel, grub shim.key - Private key with which to sign kernel/grub key generation ... openssl req -new -x509 -newkey rsa:2048 -keyout $KEY.key -out $KEY.pem -days 3650 openssl x509 -in $KEY.pem -out $KEY.crt -outform DER Note: boot.crt should be copied to cgcs-root/build-tools/certificates/TiBoot.crt for inclusion during the 'build-iso' step Hope this helps Scott On 2022-07-05 03:19, Kumar, Chandan wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Greg, Thanks for acknowledgement. I have raised starlingx launchpad for document update. Meanwhile it would be really great if you can share the steps which has to be done to integrate signing of images as part of StarlingX build infrastructure. Regards, Chandan Kumar. From: Waines, Greg Sent: Monday, July 4, 2022 6:00 PM To: starlingx-discuss at lists.starlingx.io Cc: Little, Scott Subject: Re: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . Hey Chandan, Thanks for bringing this up. I chatted with Scott about this. Currently the StarlingX public builds on CENGN are not building a secure boot capable load ? i.e. signing the appropriate items to enable secure boot. Although the StarlingX build infrastructure allows it to be added. Neither of these points are properly documented in docs.starlingx.io ? I can?t remember the details of why we are not doing this. I am guessing that the thinking was that a user of StarlingX that wanted to use UEFI Secure Boot, would want to sign with his own private key. Can you raise a starlingx launchpad ( https://launchpad.net/starlingx ) to address the docs.starlingx.io documentation issue, i.e. to indicate that the StarlingX CENGN builds are not signed to support uefi secure boot, and describe how a starlingx user could add signing to their StarlingX build environment in order to sign for uefi secure boot with their own private key ? Greg. From: Scott Little > Sent: Wednesday, June 29, 2022 10:42 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Incorrect public key for signed starlingX 5.0 iso . On 2022-06-02 13:12, Kumar, Chandan wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I am trying to validate signed starlingX 5.0 iso on a secureboot enabled setup against public key(TiBoot.crt) embedded inside iso. After rebooting , operating system is not coming up with error screen saying ?Verification failed: (0X1A) Security Violation?. However, when I signed images with self-generated private key and validated against corresponding public key, system is able to boot up successfully. Signing is done after flashing the iso on a server. Please find attached procedure for signing images inside iso. I believe, the public key provided with iso is not correct. Can you please confirm ? Regards, Chandan Kumar. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss Thanks for the report. I'll look into it Scott Little -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Jul 27 21:48:59 2022 From: scott.little at windriver.com (Scott Little) Date: Wed, 27 Jul 2022 17:48:59 -0400 Subject: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_compiler - Build # 1 - Failure! In-Reply-To: <1277616022.178.1658947044249.JavaMail.javamailuser@localhost> References: <1277616022.178.1658947044249.JavaMail.javamailuser@localhost> Message-ID: <1c0c6f78-8c86-ef41-2d9c-a2384e699a21@windriver.com> A temporary download issue.? Succeeded on the second try. Scott On 2022-07-27 2:37 p.m., starlingx.build at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_7.0_build_layer_compiler > Build #: 1 > Status: Failure > Timestamp: 20220727T174951Z > Branch: r/stx.7.0 > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/compiler/20220727T174951Z/logs > -------------------------------------------------------------------------------- > Parameters > > FULL_BUILD: false > FORCE_BUILD: true > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Jul 27 21:54:37 2022 From: scott.little at windriver.com (Scott Little) Date: Wed, 27 Jul 2022 17:54:37 -0400 Subject: [Starlingx-discuss] [Action Required] Please review branch creation for r/stx.7.0 In-Reply-To: <0a0d2d3c-0199-c64e-87e3-f6acca1efc36@windriver.com> References: <0a0d2d3c-0199-c64e-87e3-f6acca1efc36@windriver.com> Message-ID: The manifest and config changes have merged.? That's sufficient to launch the first CENGN build of r/stx.7.0. I don't expect to see the result until. Thursday morning. There are still a lot of .gitreview updates yet to merge.? Those will gate any code submissions to the new branch.? I call upon all cores to work through the remaining reviews under https://review.opendev.org/q/topic:r.stx.7.0 . Scott On 2022-07-26 11:54 p.m., Scott Little wrote: > The full set of reviews is ... > > ?? https://review.opendev.org/q/topic:r.stx.7.0 > > Note: There are multiple pages of reviews. > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From starlingx.build at gmail.com Thu Jul 28 00:54:53 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 27 Jul 2022 20:54:53 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_distro - Build # 1 - Failure! Message-ID: <1890199485.184.1658969694103.JavaMail.javamailuser@localhost> Project: STX_7.0_build_layer_distro Build #: 1 Status: Failure Timestamp: 20220727T224953Z Branch: r/stx.7.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/distro/20220727T224953Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true From ildiko.vancsa at gmail.com Thu Jul 28 07:03:07 2022 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 28 Jul 2022 09:03:07 +0200 Subject: [Starlingx-discuss] No StarlingX release meeting on July 27 In-Reply-To: References: Message-ID: Hi Ghada, Great, thank you for the update! I did see the branch creation mails as well, I?ve been following that part. With regards to the current status, I assume it is safe to say that the release will not come out next week. Do you happen to have a new time estimate for the release? It would be very helpful to coordinate release communication plans and timeline. Thanks and Best Regards, Ildik? > On Jul 27, 2022, at 15:55, Khalil, Ghada wrote: > > Hi Ildiko / all, > The status is as follows: > - A fix for the key openstack LP has been merged: https://bugs.launchpad.net/starlingx/+bug/1978409 > - r/stx.7.0 branch creation is in progress. Email sent to the mailing list for reviews. > - Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.7.0 -- 2 still open > - Sanity: The WR team is working on setting up a sanity w/ openstack > > Regards, > Ghada > > -----Original Message----- > From: Ildiko Vancsa > Sent: Wednesday, July 27, 2022 2:42 AM > To: Khalil, Ghada > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] No StarlingX release meeting on July 27 > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi Ghada, > > Thank you for the heads up about canceling the call today. > > Since the 7.0 release is still forecasted for next week and there were bugs and remaining testing activities that the community has been working on, do you have any updates about the release timeline? And new forecast, if there?s any? > > Thanks, > Ildik? > > >> On Jul 27, 2022, at 03:28, Khalil, Ghada wrote: >> >> Hello all, >> I cannot host the StarlingX release meeting tomorrow due to a conflict. Therefore, I will be canceling the meeting. My apologies for the short notice. >> >> Regards, >> Ghada >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From starlingx.build at gmail.com Thu Jul 28 07:26:23 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 28 Jul 2022 03:26:23 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 2976 - Failure! Message-ID: <1675973544.189.1658993184960.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 2976 Status: Failure Timestamp: 20220728T065819Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220728T055624Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-7.0-flock/20220728T055624Z DOCKER_BUILD_ID: jenkins-rc-7.0-flock-20220728T055624Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/rc-7.0-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220728T055624Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/7.0/centos/flock/20220728T055624Z/logs MASTER_JOB_NAME: STX_7.0_build_layer_flock LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/rc-7.0-flock BUILD_ISO: true From starlingx.build at gmail.com Thu Jul 28 07:26:27 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 28 Jul 2022 03:26:27 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_flock - Build # 1 - Failure! Message-ID: <1530453273.192.1658993188389.JavaMail.javamailuser@localhost> Project: STX_7.0_build_layer_flock Build #: 1 Status: Failure Timestamp: 20220728T055624Z Branch: r/stx.7.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220728T055624Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From openinfradn at gmail.com Thu Jul 28 10:31:30 2022 From: openinfradn at gmail.com (open infra) Date: Thu, 28 Jul 2022 16:01:30 +0530 Subject: [Starlingx-discuss] What is the base OS for Starlingx Release 6 Message-ID: Hi, Which CentOS release is the compatible with STX release boot image? Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From Juanita.Balaraj at windriver.com Thu Jul 28 14:09:46 2022 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Thu, 28 Jul 2022 14:09:46 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 27-July-22 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 ============ 27-July-22 * Launchpad Bugs: https://bugs.launchpad.net/starlingx/+bug/1982058 / - 2 identical LP Bugs have been raised - Action JB to review and delete 1 or merge the bugs. * Stx 7.0 GA date is July 25th - AR Juanita to review Stx 7.0 Release checklist Release: week of July 25 >> week of Aug 1 https://docs.google.com/spreadsheets/d/171PJAu9SykXm9h9Ny2IsZ8YMbhvEwOzuTbISWUMQhiE/edit#gid=0 * https://review.opendev.org/c/starlingx/docs/+/845379 - To confirm if this Gerrit Review is being delivered for Stx 7.0 - AR Juanita * Need to update the Installation Guide to display Stx 7.0 once docs are merged : https://docs.starlingx.io/deploy_install_guides/index-install-e083ca818006.html - AR Ron * Version drop-down on https://docs.starlingx.io/ to be updated to display Stx 7.0 - AR Ron * Stx Release Notes - AR Juanita - To automate the updates in the Introduction Guide - AR Ron * Scott to cut the Stx 7.0 docs branch - To confirm the date * No Cherry picks this week. Waiting for reviews to merge. * Team to address LP Bugs - https://bugs.launchpad.net/starlingx/+bug/1932314; https://bugs.launchpad.net/starlingx/+bug/1951165 - AR Elaine to close these bugs - On hold * https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs for a list of pending Doc Bugs - 11 bugs pending * https://bugs.launchpad.net/starlingx/+bug/1980666 - AR Elisa * Operations Guide Archive - On Hold until further clarifications are discussed - 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 scott.little at windriver.com Thu Jul 28 15:36:30 2022 From: scott.little at windriver.com (Scott Little) Date: Thu, 28 Jul 2022 11:36:30 -0400 Subject: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_flock - Build # 1 - Failure! In-Reply-To: <1530453273.192.1658993188389.JavaMail.javamailuser@localhost> References: <1530453273.192.1658993188389.JavaMail.javamailuser@localhost> Message-ID: <1ad3c732-db3a-3ae0-cbd5-e6b3d7bf77ff@windriver.com> Another transient download error that the existing retries couldn't cope with.? A new build is running, and is already passed the download step. I'd like folks to continue to hold off pushing updates to the r/stx.7.0 branch until CENGN has built all the layers at least once. Scott On 2022-07-28 03:26, starlingx.build at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_7.0_build_layer_flock > Build #: 1 > Status: Failure > Timestamp: 20220728T055624Z > Branch: r/stx.7.0 > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220728T055624Z/logs > -------------------------------------------------------------------------------- > Parameters > > FULL_BUILD: false > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Thu Jul 28 17:58:00 2022 From: scott.little at windriver.com (Scott Little) Date: Thu, 28 Jul 2022 13:58:00 -0400 Subject: [Starlingx-discuss] master branch is open for stx.8.0 submissions Message-ID: The master branch is now open for submissions of feature content destined for stx.8.0 From starlingx.build at gmail.com Thu Jul 28 19:38:24 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 28 Jul 2022 15:38:24 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 2980 - Failure! Message-ID: <948735142.197.1659037106484.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 2980 Status: Failure Timestamp: 20220728T192137Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220728T184055Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-7.0-flock/20220728T184055Z DOCKER_BUILD_ID: jenkins-rc-7.0-flock-20220728T184055Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/rc-7.0-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220728T184055Z/logs BUILD_IMG: true FULL_BUILD: true PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/7.0/centos/flock/20220728T184055Z/logs MASTER_JOB_NAME: STX_7.0_build_layer_flock LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/rc-7.0-flock BUILD_ISO: true From starlingx.build at gmail.com Thu Jul 28 19:38:28 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 28 Jul 2022 15:38:28 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_flock - Build # 2 - Still Failing! In-Reply-To: <1726398011.190.1658993185872.JavaMail.javamailuser@localhost> References: <1726398011.190.1658993185872.JavaMail.javamailuser@localhost> Message-ID: <1506173894.200.1659037109479.JavaMail.javamailuser@localhost> Project: STX_7.0_build_layer_flock Build #: 2 Status: Still Failing Timestamp: 20220728T184055Z Branch: r/stx.7.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220728T184055Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: true FORCE_BUILD: true From starlingx.build at gmail.com Fri Jul 29 02:15:26 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Thu, 28 Jul 2022 22:15:26 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_containers - Build # 1 - Failure! Message-ID: <135181786.210.1659060927295.JavaMail.javamailuser@localhost> Project: STX_7.0_build_layer_containers Build #: 1 Status: Failure Timestamp: 20220729T014202Z Branch: r/stx.7.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/containers/20220729T014202Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From scott.little at windriver.com Fri Jul 29 15:22:22 2022 From: scott.little at windriver.com (Scott Little) Date: Fri, 29 Jul 2022 11:22:22 -0400 Subject: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_containers - Build # 1 - Failure! In-Reply-To: <135181786.210.1659060927295.JavaMail.javamailuser@localhost> References: <135181786.210.1659060927295.JavaMail.javamailuser@localhost> Message-ID: <97cd22e8-4155-b560-d324-47f55f61f2b0@windriver.com> Another transient download error that the existing retries couldn't cope with.? A new build is running... investigating. Scott On 2022-07-28 22:15, starlingx.build at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_7.0_build_layer_containers > Build #: 1 > Status: Failure > Timestamp: 20220729T014202Z > Branch: r/stx.7.0 > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/containers/20220729T014202Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: true > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From starlingx.build at gmail.com Fri Jul 29 15:53:20 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Fri, 29 Jul 2022 11:53:20 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_containers - Build # 2 - Still Failing! In-Reply-To: <991768097.208.1659060924902.JavaMail.javamailuser@localhost> References: <991768097.208.1659060924902.JavaMail.javamailuser@localhost> Message-ID: <725803495.215.1659110001740.JavaMail.javamailuser@localhost> Project: STX_7.0_build_layer_containers Build #: 2 Status: Still Failing Timestamp: 20220729T151714Z Branch: r/stx.7.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/containers/20220729T151714Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From starlingx.build at gmail.com Sat Jul 30 02:37:13 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Fri, 29 Jul 2022 22:37:13 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_flock - Build # 4 - Failure! Message-ID: <331486102.225.1659148634984.JavaMail.javamailuser@localhost> Project: STX_7.0_build_layer_flock Build #: 4 Status: Failure Timestamp: 20220730T014232Z Branch: r/stx.7.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220730T014232Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From starlingx.build at gmail.com Sat Jul 30 02:37:03 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Fri, 29 Jul 2022 22:37:03 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 2989 - Failure! Message-ID: <1460147758.222.1659148631194.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 2989 Status: Failure Timestamp: 20220730T021954Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220730T014232Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-7.0-flock/20220730T014232Z DOCKER_BUILD_ID: jenkins-rc-7.0-flock-20220730T014232Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/rc-7.0-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/flock/20220730T014232Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/7.0/centos/flock/20220730T014232Z/logs MASTER_JOB_NAME: STX_7.0_build_layer_flock LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/rc-7.0-flock BUILD_ISO: true From starlingx.build at gmail.com Sun Jul 31 02:13:40 2022 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Sat, 30 Jul 2022 22:13:40 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.7.0 STX_7.0_build_layer_containers - Build # 3 - Still Failing! In-Reply-To: <754613804.213.1659109998970.JavaMail.javamailuser@localhost> References: <754613804.213.1659109998970.JavaMail.javamailuser@localhost> Message-ID: <1316816632.233.1659233622791.JavaMail.javamailuser@localhost> Project: STX_7.0_build_layer_containers Build #: 3 Status: Still Failing Timestamp: 20220731T014139Z Branch: r/stx.7.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/centos/containers/20220731T014139Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From openinfradn at gmail.com Sun Jul 31 09:14:56 2022 From: openinfradn at gmail.com (open infra) Date: Sun, 31 Jul 2022 14:44:56 +0530 Subject: [Starlingx-discuss] Use of --reuse-values in Nova config In-Reply-To: References: Message-ID: Thanks Greg! On Mon, Jul 25, 2022 at 4:40 PM Waines, Greg wrote: > See > https://docs.starlingx.io/system_configuration/kubernetes/application-commands-and-helm-overrides.html > > > > ( the repeated --reuse-values on same command line is a typo, although it > has no impact ) > > > > Greg. > > > > *From:* open infra > *Sent:* Wednesday, July 20, 2022 12:04 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Use of --reuse-values in Nova config > > > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi, > > > > I referred to two documents while setting up, GPU passthrough in STX 6 and > stx-openstack. > > In one of the documents [2], "--reuse-values" used twice within single > command. > > What is the purpose of using "--reuse-values" twice? I hope it is not a > typo. > > > > According to [1] ; > > ~(keystone_admin)$ system helm-override-update stx-openstack nova openstack > --reuse-values --values=your-override-file.yaml > > ~(keystone_admin)$ system application-apply stx-openstack > > > > > > According to [2]; > > ~(keystone_admin)]$ system helm-override-update --reuse-values --values ./gpu_override.yaml > stx-openstack nova openstack --reuse-values > > ~(keystone_admin)]$ system application-apply stx-openstack > > > > [1] > https://docs.starlingx.io/node_management/openstack/configure-pci-passthrough-interface-to-nvidia-gpu.html > > > > > [2] > https://docs.starlingx.io/system_configuration/openstack/configuring-a-pci-alias-in-nova.html > > > > > Regards, > > Danishka > -------------- next part -------------- An HTML attachment was scrubbed... URL: