From amy at demarco.com Sun Aug 1 21:14:30 2021 From: amy at demarco.com (Amy Marrich) Date: Sun, 1 Aug 2021 16:14:30 -0500 Subject: [Starlingx-discuss] Diversity and Inclusion Meeting Reminder - OFTC Message-ID: The Diversity & Inclusion WG invites members of all OIF projects to attend our next meeting Monday Auguat 2nd, at 17:00 UTC in the #openinfra-diversity channel on OFTC. The agenda can be found at https://etherpad.openstack.org/p/ diversity-wg-agenda. Please feel free to add any topics you wish to discuss at the meeting. Thanks, Amy (apotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Mon Aug 2 00:45:42 2021 From: austin.sun at intel.com (Sun, Austin) Date: Mon, 2 Aug 2021 00:45:42 +0000 Subject: [Starlingx-discuss] Openstack applying failed and nova-compute-worker-0 pod with CrashLoopBackOff staus In-Reply-To: References: Message-ID: suggest you split to small files and upload. From: open infra Sent: Friday, July 30, 2021 9:17 PM To: Sun, Austin Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Openstack applying failed and nova-compute-worker-0 pod with CrashLoopBackOff staus I am unable to upload the file. On Fri, Jul 30, 2021 at 2:15 PM open infra > wrote: Just asked, as the file size is almost 1GB. Let me try. On Fri, Jul 30, 2021 at 1:30 PM Sun, Austin > wrote: You can directly Click “Add attachment or patch” in bottom of bug link . From: open infra > Sent: Friday, July 30, 2021 3:46 PM To: Sun, Austin > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Openstack applying failed and nova-compute-worker-0 pod with CrashLoopBackOff staus Hi Austin, Sorry for the delay. Bug ID is 1938508. Is there Google Drive or similar location available to upload the tar file of the 'collect' output? Regards, Danishka On Fri, Jul 30, 2021 at 5:58 AM Sun, Austin > wrote: Hi Danishka: Would you like know the bug number once you created ? Thanks. BR Austin Sun. From: open infra > Sent: Thursday, July 29, 2021 11:16 AM To: Sun, Austin > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Openstack applying failed and nova-compute-worker-0 pod with CrashLoopBackOff staus Thanks, Austin. I will file a bug. On Thu, Jul 29, 2021 at 6:25 AM Sun, Austin > wrote: Hi Danishka: I checked the three pieces log you shared, but it’s hard to find any hint to triage the issue. But most likely some wrong in worker nodes. Would you like report a bug [1] and upload all logs for controller/workers. FYI: One way to collect log is to run “collect –all” from controller-0 which will collect all necessary info from system. [1] https://bugs.launchpad.net/starlingx/+bugs Thanks. BR Austin Sun. From: open infra > Sent: Monday, July 26, 2021 8:58 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Openstack applying failed and nova-compute-worker-0 pod with CrashLoopBackOff staus Hi, After rebooting the entire stx (r5 standard dedicated storage) environment, noticed that OpenStack vm can not start and hypervisor status is down (we have only one worker node). Furthermore, openstack-apply was failed as nova-compute-worker-0-13cc482d-7t9kq pod was not ready [1] and status is CrashLoopBackOff [2]. Here is the description of the pod [3]. VMs were created using nova-local and mounted a shared volume, which is a ceph based volume. Lock and Unlocking + re-applying of stx-openstack didn't fix the issue. I would like to know any hint or suggestion to fix this issue and avoid similar issue in future. [1] https://paste.opendev.org/show/807707/ [2] https://paste.opendev.org/show/807705/ [3] https://paste.opendev.org/show/807704/ Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From chengde.yu at intel.com Mon Aug 2 08:10:21 2021 From: chengde.yu at intel.com (Yu, Chengde) Date: Mon, 2 Aug 2021 08:10:21 +0000 Subject: [Starlingx-discuss] Please review the patch "Separate CA for k8s and etcd" Message-ID: Hi Bob, Tee, Ghada, Joao: Starlingx shares same certificate between kubernetes-ca and etcd-ca. It will dramatically increase the complexity of updating etcd-ca cert. Therefore do the separating CA work. Need your help to check and review. Thanks Please refer to patches below https://review.opendev.org/c/starlingx/ansible-playbooks/+/800412 https://review.opendev.org/c/starlingx/stx-puppet/+/799569 Best Regard Chant Yu -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Mon Aug 2 11:13:04 2021 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Mon, 2 Aug 2021 11:13:04 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210731T013530Z Message-ID: Sanity Test from 2021-July-31 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210731T013530Z/outputs/iso/ ) Status: GREEN Executed on VIRTUAL SIMPLEX Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210731T013530Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] Regards, Nicolae Jascanu, Ph.D. Software Engineer INTEL IOTG Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Mon Aug 2 11:14:54 2021 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Mon, 2 Aug 2021 11:14:54 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210731T013530Z Message-ID: Sanity Test from 2021-July-31 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210731T013530Z/outputs/iso/ ) Status: GREEN Executed on VIRTUAL DUPLEX Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210731T013530Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Virtual Environment AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Regards, Nicolae Jascanu, Ph.D. Software Engineer INTEL IOTG Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Mon Aug 2 12:59:13 2021 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 2 Aug 2021 12:59:13 +0000 Subject: [Starlingx-discuss] Please review the patch "Separate CA for k8s and etcd" In-Reply-To: References: Message-ID: +Andy From: Yu, Chengde Sent: Monday, August 2, 2021 4:10 AM To: starlingx-discuss at lists.starlingx.io; Church, Robert ; Ngo, Tee ; Khalil, Ghada ; Victor Portal, Joao Cc: Liu, ZhipengS Subject: [Starlingx-discuss] Please review the patch "Separate CA for k8s and etcd" [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Bob, Tee, Ghada, Joao: Starlingx shares same certificate between kubernetes-ca and etcd-ca. It will dramatically increase the complexity of updating etcd-ca cert. Therefore do the separating CA work. Need your help to check and review. Thanks Please refer to patches below https://review.opendev.org/c/starlingx/ansible-playbooks/+/800412 https://review.opendev.org/c/starlingx/stx-puppet/+/799569 Best Regard Chant Yu -------------- next part -------------- An HTML attachment was scrubbed... URL: From chengde.yu at intel.com Tue Aug 3 00:32:27 2021 From: chengde.yu at intel.com (Yu, Chengde) Date: Tue, 3 Aug 2021 00:32:27 +0000 Subject: [Starlingx-discuss] Please review the patch "Separate CA for k8s and etcd" In-Reply-To: References: Message-ID: Confirm Add Andy in review loop From: Waines, Greg Sent: Monday, August 2, 2021 8:59 PM To: Yu, Chengde ; starlingx-discuss at lists.starlingx.io; Church, Robert ; Ngo, Tee ; Khalil, Ghada ; Victor Portal, Joao ; Ning, Antai (Andy) Cc: Liu, ZhipengS Subject: RE: [Starlingx-discuss] Please review the patch "Separate CA for k8s and etcd" +Andy From: Yu, Chengde > Sent: Monday, August 2, 2021 4:10 AM To: starlingx-discuss at lists.starlingx.io; Church, Robert >; Ngo, Tee >; Khalil, Ghada >; Victor Portal, Joao > Cc: Liu, ZhipengS > Subject: [Starlingx-discuss] Please review the patch "Separate CA for k8s and etcd" [Please note: This e-mail is from an EXTERNAL e-mail address] Hi Bob, Tee, Ghada, Joao: Starlingx shares same certificate between kubernetes-ca and etcd-ca. It will dramatically increase the complexity of updating etcd-ca cert. Therefore do the separating CA work. Need your help to check and review. Thanks Please refer to patches below https://review.opendev.org/c/starlingx/ansible-playbooks/+/800412 https://review.opendev.org/c/starlingx/stx-puppet/+/799569 Best Regard Chant Yu -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Tue Aug 3 04:42:41 2021 From: openinfradn at gmail.com (open infra) Date: Tue, 3 Aug 2021 10:12:41 +0530 Subject: [Starlingx-discuss] Openstack applying failed and nova-compute-worker-0 pod with CrashLoopBackOff staus In-Reply-To: References: Message-ID: I have uploaded all the files yesterday. On Mon, Aug 2, 2021 at 6:15 AM Sun, Austin wrote: > suggest you split to small files and upload. > > > > > > > > *From:* open infra > *Sent:* Friday, July 30, 2021 9:17 PM > *To:* Sun, Austin > *Cc:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Openstack applying failed and > nova-compute-worker-0 pod with CrashLoopBackOff staus > > > > I am unable to upload the file. > > > > > > On Fri, Jul 30, 2021 at 2:15 PM open infra wrote: > > Just asked, as the file size is almost 1GB. > > Let me try. > > > > On Fri, Jul 30, 2021 at 1:30 PM Sun, Austin wrote: > > You can directly Click “Add attachment or patch > ” in > bottom of bug link . > > > > > > *From:* open infra > *Sent:* Friday, July 30, 2021 3:46 PM > *To:* Sun, Austin > *Cc:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Openstack applying failed and > nova-compute-worker-0 pod with CrashLoopBackOff staus > > > > Hi Austin, > > > > Sorry for the delay. Bug ID is 1938508. > > Is there Google Drive or similar location available to upload the tar file > of the 'collect' output? > > > > Regards, > > Danishka > > > > On Fri, Jul 30, 2021 at 5:58 AM Sun, Austin wrote: > > Hi Danishka: > > Would you like know the bug number once you created ? > > > > Thanks. > > BR > Austin Sun. > > > > *From:* open infra > *Sent:* Thursday, July 29, 2021 11:16 AM > *To:* Sun, Austin > *Cc:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Openstack applying failed and > nova-compute-worker-0 pod with CrashLoopBackOff staus > > > > Thanks, Austin. I will file a bug. > > > > On Thu, Jul 29, 2021 at 6:25 AM Sun, Austin wrote: > > Hi Danishka: > > I checked the three pieces log you shared, but it’s hard to find any hint > to triage the issue. > > But most likely some wrong in worker nodes. > > Would you like report a bug [1] and upload all logs for > controller/workers. > > > > FYI: One way to collect log is to run “collect –all” from controller-0 > which will collect all necessary info from system. > > > > [1] https://bugs.launchpad.net/starlingx/+bugs > > > > > > Thanks. > > BR > Austin Sun. > > > > *From:* open infra > *Sent:* Monday, July 26, 2021 8:58 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Openstack applying failed and > nova-compute-worker-0 pod with CrashLoopBackOff staus > > > > Hi, > > > > After rebooting the entire stx (r5 standard dedicated storage) > environment, noticed that OpenStack vm can not start and hypervisor status > is down (we have only one worker node). > > > > Furthermore, openstack-apply was failed as > nova-compute-worker-0-13cc482d-7t9kq pod was not ready [1] and status is > CrashLoopBackOff [2]. Here is the description of the pod [3]. > > > > > > VMs were created using nova-local and mounted a shared volume, which is a > ceph based volume. Lock and Unlocking + re-applying of stx-openstack didn't > fix the issue. > > > > I would like to know any hint or suggestion to fix this issue and avoid > similar issue in future. > > > > [1] https://paste.opendev.org/show/807707/ > > [2] https://paste.opendev.org/show/807705/ > > [3] https://paste.opendev.org/show/807704/ > > > > Regards, > > Danishka > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Aug 3 05:04:14 2021 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 3 Aug 2021 05:04:14 +0000 Subject: [Starlingx-discuss] Agenda StarlingX Distro-OpenStack: Bi-weekly Project Meeting -- 08/03 Message-ID: Hi All: As planned , we will have openstack distro meeting 08/03 2021 The topic will be : - Bugs go through High/Medium bugs https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack and New bugs - Open topic If anything need discuss , please put into https://etherpad.opendev.org/p/stx-distro-openstack-meetings Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Charles.Short at windriver.com Tue Aug 3 12:14:36 2021 From: Charles.Short at windriver.com (Short, Charles) Date: Tue, 3 Aug 2021 12:14:36 +0000 Subject: [Starlingx-discuss] Merging python3 changes onto master branch In-Reply-To: References: Message-ID: Hello, We ran the sanity tests ran, passed, and all the commits in the following review URL are mergeable: https://review.opendev.org/q/topic:%2522py3%2522+(status:open+OR+status:merged+and+author:charles.short%2540windriver.com) If you have any questions please let me know. Regards chuck From: Miller, Frank Sent: Tuesday, July 27, 2021 11:18 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Merging python3 changes onto master branch StarlingX Cores: A team of developers has been working on the f/centos8 branch to convert StarlingX python code to use python3. We're now at the point where most of those changes are ready to merge onto the master branch. Chuck Short has volunteered to gather the commits and merge them onto master [1] and you will see these commits now up for reviews. By tomorrow we expect to be ready for you to review and allow these commits to merge. This email is to let you know of the testing that is being done on these commits so you can have confidence in the changes. * Testing was completed on the f/centos8 branch as much as possible on an AIO-SX system * All the commits [1] were built into a master branch ISO which was brought up in VBox and confirmed the controller went enabled, applications applied, no alarms present * The same ISO was installed on an AIO-SX hardware lab * Sanity is in progress on 2 hardware labs, simplex and duplex, and results expected today * Some functional testing is underway for some domains (eg: SM, FM). If you have any questions let Chuck or I know. We look forward to these commits merging as python3 is a requirement for the project to be able to move to Debian. Frank PL for Build and Containers projects [1] https://review.opendev.org/q/topic:%2522py3%2522+(status:open) -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Aug 3 13:21:51 2021 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 3 Aug 2021 13:21:51 +0000 Subject: [Starlingx-discuss] MoM StarlingX Distro-OpenStack: Bi-weekly Project Meeting -- 08/03 Message-ID: Hi All: MoM of today’s meeting: 08/03/2021 Meeting - Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack #LP 1918090: --- check w/ author if it still valid issue. #LP 1918093: --- check w/ author if it still valid issue. #LP 1938508: --- assign to Chart for triage #LP1931535: --- no root cause yet #LP 1921934: --- Close it. # LP 1866311: --- Close as long time no feedback. Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.asselstine at windriver.com Tue Aug 3 14:32:25 2021 From: mark.asselstine at windriver.com (Mark Asselstine) Date: Tue, 3 Aug 2021 10:32:25 -0400 Subject: [Starlingx-discuss] [Debian Build]: Layout of the debian folder In-Reply-To: References: <61fc5f83-49dd-5c31-d9db-5e4d986ab2c6@windriver.com> Message-ID: <4ea46fa4-1056-5a4b-74ef-b14bd135453f@windriver.com> On 2021-07-31 10:04 a.m., Tao, Yue wrote: > Hi > > Exactly, --download-version specify a version to download, but the > restriction of uscan is the url in debian/watch must be a regex expression > > $cat isc-dhcp-4.4.1/debian/watch > > version=3 > > opts="uversionmangle=s/(rc|a|b|c)/~$1/,pgpsigurlmangle=s/$/.sha512.asc/" \ > > http://ftp.isc.org/isc/dhcp/(\d.\d.\d*)/dhcp-(\d.*)\.(?:tgz|tbz2|txz|tar\.(?:gz|bz2|xz)) > > > As I mentioned before, some urls of 3^rd part packages can’t be > converted to a regex expression, so I think uscan may not suitable for > downloading 3^rd part packages. But uscan is a very powerful tool, > probably we use it in other places. Let's keep it in mind as we refine things. If it is possible to detect when it may not function as expected, or only allow its use when we are 100% sure it will function as expected it might help be a good assist to have in place. MarkA > > FYI the special urls. > > http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/snapshot/linux-yocto-b44437fb32fe50b5664afd12098d928e1aaee111.tar.bz2 > > > https://api.github.com/repos/ceph/jerasure/tarball/96c76b89d661c163f65a014b8042c9354ccf7f31 > > > BTW, I attach a revision layout, which updates md5 checksum in dl_patch. > > Thanks, > > Ytao > > *From:*Short, Charles > *Sent:* Friday, July 30, 2021 9:07 PM > *To:* Tao, Yue ; > starlingx-discuss at lists.starlingx.io; Asselstine, Mark > ; Bai, Haiqing > ; Panech, Davlet > *Subject:* RE: [Starlingx-discuss] [Debian Build]: Layout of the debian > folder > > Hi, > > You can specify the version you wish to download, I did the following: > > * apt-get source isc-dhcp > * cd isc-dhcp-4.4.1 > * uscan –download-version 4.3.5 > * > > Regards > > chuck > > *From:*Tao, Yue > > *Sent:* Friday, July 30, 2021 6:50 AM > *To:* Tao, Yue >; > Short, Charles >; > starlingx-discuss at lists.starlingx.io > ; Asselstine, Mark > >; > Bai, Haiqing >; Panech, Davlet > > > *Subject:* RE: [Starlingx-discuss] [Debian Build]: Layout of the debian > folder > > Hi Charles: > > I did some investigation of debian/watch file, which is the input file > for uscan command. It’s purpose is to detect if upstream has a newer > release. I tried the uscan, which is limited to run with a full debian > folder, not only a dedbian/watch. I also try to the option “—watchfile” > to specify a watch file, but it still checks the debian/changelog file. > > $uscan –watchfile path/watch > > uscan die: Are you in the source code tree? > >    Cannot find readable debian/changelog anywhere! at > > And the url in watch file must be a regex expression, for example, > > Allow > > http://ftp.isc.org/isc/dhcp/(\d.\d.\d*)/dhcp-(\d.*)\.(?:tgz|tbz2|txz|tar\.(?:gz|bz2|xz)) > > > Not allow > > http://ftp.isc.org/isc/dhcp/4.4.2/dhcp-4.4.2.tar.gz > > > A developer only care about a special version, but he has to build a > regex expression, of cause uscan has –download-version to specify a > version, but watch file can’t meet a unregular url, like > https://api.github.com/repos/ceph/jerasure/tarball/96c76b89d661c163f65a014b8042c9354ccf7f31 > , > which is a downloading url in Starlingx repositories. I think it’s > better not to use the uscan+watch  to download 3^rd part packages. > > Thanks, > > ytao > > *From:*Tao, Yue > > *Sent:* Tuesday, July 27, 2021 10:53 AM > *To:* Short, Charles >; > starlingx-discuss at lists.starlingx.io > ; Asselstine, Mark > >; > Bai, Haiqing >; Panech, Davlet > > > *Subject:* Re: [Starlingx-discuss] [Debian Build]: Layout of the debian > folder > > On 7/27/21 7:05 AM, Short, Charles wrote: > > Hi, > >       First of all, I'm appreciated for your input. > > I had a look through the document and it looks okay. I just have a > couple of comments/questions about the folder content: > > * **debver** - This is the package version of the debian package? > This is generated from the debian/changelog when the package is > built. I guess the problem is that you want to differentiate > from a starlingx package and native package? My suggestion would > be what the Ubuntu developers do. For example, if we have > patches to apply for systemd, the debian version would be > 247.3-3, while the StarlingX package would be 247.3-3stx0. Then > a user or developer can quickly see that they are working with a > native debian package or a starlingx modified package. > >        For a Debian native package, the *debver* is the debian version. > We use it to download the src via "apt-source packagname=debver", for a > starlingx package, it is up to the developer. I observed in CentOS > version, they added a patch to change the package version, for example > integ/base/lighttpd/centos/meta_patches/Update-package-versioning-for-TIS-format.patch, > which appends a 'tis' to package version, that requests developer to > update the version manually. After transiting to debian, OBS can achieve > it automatically. It can append 'tis' or 'stx' to a package, so don't > need developers to update it manually. > > * **deb_patches** - As a developer, if the package has its > debian/patches I would rather use the debian/patches directory. > If the directory doesnt exist I am more likely to create a > debian/patches directory and then send a patch to debian to fix > a problem. > >        Exactly, we should send a fix to debian community and then uprev > the package to get the fix, but we also need to consider local changes. > The *patches" folder contains the local change for source codes, that > will be copied to debian/patches (or create it if doesn't exist), and > update the debian/patches/series. The *deb_patches* contains the patches > to change debian folder, for example, we want to customize the > installation of a package, we need to update override_dh_install stage > in debian/rules. The patches will be applied to package/debian folder > directly. > >        The *deb_patches* is similar with centos/meta_patches > >        The *patches* is similar with centos/patches > > * > * **dl_path** - Debian already does this for you already, the > debian/watch file keeps track of where to download a tarball, or > a zip file, or a python wheel for you. You can use uscan(1), > which is a part of devscripts package. Debian/Ubuntu developers > have been doing this for years. > (https://wiki.debian.org/debian/watch > ) > >          Thanks you for pointing me the debian/watch. I will take some > time to learn about debian/watch and go back soon. It looks a debian > file for monitoring the upstream version change. I am not sure if it is > suitable for a no debian package. In our internal discussion, Davlet > told me a special case, that the url of a tar ball likes this > https://api.github.com/repos/ceph/jerasure/tarball/96c76b89d661c163f65a014b8042c9354ccf7f31 > > >           As Davlet's suggestion, the *dl_path* refers to example file > > and the script that parses it > . > I will do assessment for debian/watch. > > Thanks, > > ytao > > If you have any questions please let me know. > > Regards > > chuck > > debian/watch - Debian Wiki > > debian/watch. The file named watch in the debian directory is used > to check for newer versions of upstream software is available and to > download it if necessary. The download itself will be performed with > the uscan program from the devscripts package. It takes the path to > the debian directory that uses the watch file as an argument or > searches the directories underneath the current working ... > > wiki.debian.org > > ------------------------------------------------------------------------ > > *From:* ytao > *Sent:* July 26, 2021 3:33 AM > *To:* starlingx-discuss at lists.starlingx.io > > > ; Asselstine, Mark > > *Subject:* [Starlingx-discuss] [Debian Build]: Layout of the debian > folder > > Hello Everyone: > > You may have known Wind River team is working on the transition to > Debian OS, more details of the project can be found at > https://docs.starlingx.io/specs/specs/stx-6.0/ > . My purpose is > launching > a discussion about the userspace packages transition to Debian. The > spec > can be found at > https://docs.starlingx.io/specs/specs/stx-6.0/approved/starlingx_2008704_debian_transition.html > > > In order to inherit the existing userspace construction as much as > possible, our proposal is creating a 'debian' folder in same directory > with 'centos' folder for each package. For example, the dhcp package in > integ repo, it's centos folder is at: > > https://opendev.org/starlingx/integ/src/branch/master/base/dhcp/centos > > > We will create a debian folder in same location > > https://opendev.org/starlingx/integ/src/branch/master/base/dhcp/debian > . > > All materials in this folder control building dhcp under Debian host. > The "stx_deb_folder_layout.rst" is the layout of debian folder. I also > attach a couple of samples to demonstrate how to fill the debian folder > for a debian package and a 3rd package. > > This layout is not the final version, I'm appreciated for any > suggestion > from you. > > > Thanks, > > ytao > From alexandru.dimofte at intel.com Tue Aug 3 16:18:29 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 3 Aug 2021 16:18:29 +0000 Subject: [Starlingx-discuss] Daily sanity reports are not available, we encountered some issues on our BareMetal setups Message-ID: Hello guys, We didn't sent Validation Sanity Reports yesterday and today because we started to see some issues on our setups from Karlsruhe, DE. The colleagues from IT department knows about the problem and they are working on solving it ASAP. We will starts to run again the Daily Sanity immediately when the issue is fixed. Sorry for this situation! Kind regards, Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 5155 bytes Desc: image003.png URL: From Bill.Zvonar at windriver.com Wed Aug 4 13:34:11 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 4 Aug 2021 13:34:11 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Aug 4, 2021) Message-ID: Hi all, reminder of the weekly TSC/Community calls coming up shortly. Please feel free to add other items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210804T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From Bill.Zvonar at windriver.com Wed Aug 4 14:16:20 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 4 Aug 2021 14:16:20 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Aug 4, 2021) In-Reply-To: References: Message-ID: >From today's meeting: * Standing Topics * Build/Sanity * Build with new kernel - green sanity on 7/31 build - so we're good - nice * Daily sanity reports are not available as of 8/3 * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-August/011858.html * Gerrit Reviews in Need of Attention * none this week * Topics for this Week * Python 3 status * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-August/011855.html * further updates on hold now until we have the Debian builds in place (diminishing returns now on CentOS as most issues seem to be OS-specific) * ARs from Previous Meetings * DockerHub - Bill to follow up on pending Admin changes * CENGN Backups - per Anthony, this is still pending with CENGN * Open Requests for Help * none this week -----Original Message----- From: Zvonar, Bill Sent: Wednesday, August 4, 2021 9:34 AM To: StarlingX ML Subject: Community (& TSC) Call (Aug 4, 2021) Hi all, reminder of the weekly TSC/Community calls coming up shortly. Please feel free to add other items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210804T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From maryx.camp at intel.com Wed Aug 4 20:13:12 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 4 Aug 2021 20:13:12 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 04-Aug-21 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, Mary Camp ========== Note that the 11 Aug and 18 Aug meetings are cancelled. 04-Aug-21 Upcoming vacations: Ron & Mary are both OOO next week (11 Aug). Ron & Juanita both out the week after (18 Aug). We agreed to cancel the next 2 meetings. 25 Aug we should all be back. We can discuss how we want to gather and work through retrospective feedback. Mary look around for STX customer survey, was there one done a while ago? Mary look for "this is a stub page" and identify topics that have been replaced by upstreamed guides. Could be deleted or redirect to the big guide? example: https://docs.starlingx.io/operations/dist_cloud_management.html From maryx.camp at intel.com Wed Aug 4 20:14:21 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 4 Aug 2021 20:14:21 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Docs Team Call Message-ID: Cancelled 11 Aug 21 ===== Extending the meeting series through 29-Sep-21 - 3:30 pm Eastern - 12:30 pm Pacific - Docs Team Call Call details * https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 * Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o Passcode: 419405 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes * The agenda and notes for each call are kept here: https://etherpad.openstack.org/p/stx-documentation * Call recordings: https://wiki.openstack.org/wiki/Starlingx/Meeting_Logs#Docs_Team_Call -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 5055 bytes Desc: not available URL: From maryx.camp at intel.com Wed Aug 4 20:14:56 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 4 Aug 2021 20:14:56 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Docs Team Call Message-ID: Cancelled 18 Aug 21 ==== Extending the meeting series through 29-Sep-21 - 3:30 pm Eastern - 12:30 pm Pacific - Docs Team Call Call details * https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 * Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o Passcode: 419405 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes * The agenda and notes for each call are kept here: https://etherpad.openstack.org/p/stx-documentation * Call recordings: https://wiki.openstack.org/wiki/Starlingx/Meeting_Logs#Docs_Team_Call -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 5056 bytes Desc: not available URL: From zekeriya.mansuroglu at iis.fraunhofer.de Thu Aug 5 10:39:28 2021 From: zekeriya.mansuroglu at iis.fraunhofer.de (Mansuroglu, Zekeriya) Date: Thu, 5 Aug 2021 10:39:28 +0000 Subject: [Starlingx-discuss] Integration of a private 5G core Net Message-ID: Dear StarlingX community, I'm interested in the integration of a commercial 5G core with StarlingX. In the documentation I couldn't find any descriptions about how it should be done. Is there any description of the interfaces of StarlingX from/to the 5g core and RAN? Thanks, Zekeriya -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Fri Aug 6 06:58:34 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 6 Aug 2021 02:58:34 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 411 - Failure! Message-ID: <741866122.364.1628233119696.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 411 Status: Failure Timestamp: 20210806T032140Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210806T023440Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210806T023440Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20210806T023440Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210806T023440Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210806T023440Z/logs PUBLISH_TIMESTAMP: 20210806T023440Z FLOCK_VERSION: master-centos-stable-20210806T023440Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20210806T023440Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210806T023440Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Fri Aug 6 06:58:41 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 6 Aug 2021 02:58:41 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 159 - Failure! Message-ID: <196263353.367.1628233121752.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 159 Status: Failure Timestamp: 20210806T025248Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210806T023440Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210806T023440Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210806T023440Z/logs MASTER_BUILD_NUMBER: 166 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210806T023440Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210806T023440Z DOCKER_BUILD_ID: jenkins-master-containers-20210806T023440Z-builder TIMESTAMP: 20210806T023440Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210806T023440Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210806T023440Z/outputs From build.starlingx at gmail.com Fri Aug 6 06:58:43 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 6 Aug 2021 02:58:43 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 166 - Failure! Message-ID: <1810282639.370.1628233123736.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 166 Status: Failure Timestamp: 20210806T023440Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210806T023440Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From openinfradn at gmail.com Fri Aug 6 11:14:52 2021 From: openinfradn at gmail.com (open infra) Date: Fri, 6 Aug 2021 16:44:52 +0530 Subject: [Starlingx-discuss] host system reboots with switch reboot Message-ID: Hi, I am using StarlingX release 5, dedicated storage environment. A couple of times we noticed all nodes except the active controller rebooted after reboot of the switch. When we purposely reboot the switch, only one storage node rebooted. I understand the importance of the redundant switch, but is this possible with starlingX? (Maybe an issue related to heartbeats). Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Sat Aug 7 08:02:10 2021 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Sat, 7 Aug 2021 08:02:10 +0000 Subject: [Starlingx-discuss] Daily sanity reports for bare metal are still not available Message-ID: Hi All, We still have issues with our bare metal infrastructure. We are working on it, but for a while we will send reports only for Virtual configurations. Regards, Nicolae Jascanu, Ph.D. Software Engineer INTEL IOTG Galati, Romania From: Dimofte, Alexandru Sent: Tuesday, August 3, 2021 19:18 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Daily sanity reports are not available, we encountered some issues on our BareMetal setups Hello guys, We didn't sent Validation Sanity Reports yesterday and today because we started to see some issues on our setups from Karlsruhe, DE. The colleagues from IT department knows about the problem and they are working on solving it ASAP. We will starts to run again the Daily Sanity immediately when the issue is fixed. Sorry for this situation! Kind regards, Validation Team [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 4730 bytes Desc: image002.png URL: From nicolae.jascanu at intel.com Sat Aug 7 08:04:32 2021 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Sat, 7 Aug 2021 08:04:32 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210804T013543Z Message-ID: Sanity Test from 2021-August-04 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210804T013543Z/outputs/iso/ ) Status: GREEN Executed on VIRTUAL SIMPLEX Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210804T013543Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] Regards, Nicolae Jascanu, Ph.D. Software Engineer INTEL IOTG Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Sat Aug 7 08:08:24 2021 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Sat, 7 Aug 2021 08:08:24 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210805T021001Z Message-ID: Sanity Test from 2021-August-05 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210805T021001Z/outputs/iso/ ) Status: GREEN Executed on VIRTUAL DUPLEX Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210805T021001Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Virtual Environment AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Regards, Nicolae Jascanu, Ph.D. Software Engineer INTEL IOTG Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Sun Aug 8 09:49:38 2021 From: austin.sun at intel.com (Sun, Austin) Date: Sun, 8 Aug 2021 09:49:38 +0000 Subject: [Starlingx-discuss] host system reboots with switch reboot In-Reply-To: References: Message-ID: Hi Danishka: Yes. I think this is related to Heartbeat. If Heartbeat miss count reaches threshold, node will graceful recovery , which reboot the node. BR Austin Sun. From: open infra Sent: Friday, August 6, 2021 7:15 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] host system reboots with switch reboot Hi, I am using StarlingX release 5, dedicated storage environment. A couple of times we noticed all nodes except the active controller rebooted after reboot of the switch. When we purposely reboot the switch, only one storage node rebooted. I understand the importance of the redundant switch, but is this possible with starlingX? (Maybe an issue related to heartbeats). Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Mon Aug 9 05:43:40 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Mon, 9 Aug 2021 05:43:40 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210807T013626Z Message-ID: Sanity Test from 2021-August-09 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210807T013626Z/outputs/iso/) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210807T013626Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz All baremetal configurations failed because of: https://bugs.launchpad.net/starlingx/+bug/1938559 =========================================== Sanity Test executed on BareMetal Environment Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Kind Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 5155 bytes Desc: image003.png URL: From austin.sun at intel.com Mon Aug 9 06:57:36 2021 From: austin.sun at intel.com (Sun, Austin) Date: Mon, 9 Aug 2021 06:57:36 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210807T013626Z In-Reply-To: References: Message-ID: Hi Alex: It seems the boot failure because root partition is not recognized. Please share the HW info such as RAID controller etc. Thanks. BR Austin Sun. From: Dimofte, Alexandru Sent: Monday, August 9, 2021 1:44 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210807T013626Z Sanity Test from 2021-August-09 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210807T013626Z/outputs/iso/) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210807T013626Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz All baremetal configurations failed because of: https://bugs.launchpad.net/starlingx/+bug/1938559 =========================================== Sanity Test executed on BareMetal Environment Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Kind Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5155 bytes Desc: image001.png URL: From build.starlingx at gmail.com Mon Aug 9 17:24:54 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 9 Aug 2021 13:24:54 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 412 - Still Failing! In-Reply-To: <1856799268.362.1628233102794.JavaMail.javamailuser@localhost> References: <1856799268.362.1628233102794.JavaMail.javamailuser@localhost> Message-ID: <1919517563.373.1628529895724.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 412 Status: Still Failing Timestamp: 20210809T141039Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210809T132443Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210809T132443Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20210809T132443Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210809T132443Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210809T132443Z/logs PUBLISH_TIMESTAMP: 20210809T132443Z FLOCK_VERSION: master-centos-stable-20210809T132443Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20210809T132443Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210809T132443Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Mon Aug 9 17:24:57 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 9 Aug 2021 13:24:57 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 160 - Still Failing! In-Reply-To: <1528202893.365.1628233120215.JavaMail.javamailuser@localhost> References: <1528202893.365.1628233120215.JavaMail.javamailuser@localhost> Message-ID: <1170456667.376.1628529898619.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 160 Status: Still Failing Timestamp: 20210809T134410Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210809T132443Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210809T132443Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210809T132443Z/logs MASTER_BUILD_NUMBER: 167 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210809T132443Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210809T132443Z DOCKER_BUILD_ID: jenkins-master-containers-20210809T132443Z-builder TIMESTAMP: 20210809T132443Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210809T132443Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210809T132443Z/outputs From build.starlingx at gmail.com Mon Aug 9 17:25:00 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 9 Aug 2021 13:25:00 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 167 - Still Failing! In-Reply-To: <909581986.368.1628233122270.JavaMail.javamailuser@localhost> References: <909581986.368.1628233122270.JavaMail.javamailuser@localhost> Message-ID: <1553708156.379.1628529901093.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 167 Status: Still Failing Timestamp: 20210809T132443Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210809T132443Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From build.starlingx at gmail.com Tue Aug 10 04:09:13 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 10 Aug 2021 00:09:13 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 413 - Still Failing! In-Reply-To: <644756290.371.1628529892517.JavaMail.javamailuser@localhost> References: <644756290.371.1628529892517.JavaMail.javamailuser@localhost> Message-ID: <1481204958.382.1628568557409.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 413 Status: Still Failing Timestamp: 20210810T005123Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210810T000447Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210810T000447Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20210810T000447Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210810T000447Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210810T000447Z/logs PUBLISH_TIMESTAMP: 20210810T000447Z FLOCK_VERSION: master-centos-stable-20210810T000447Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20210810T000447Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210810T000447Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Tue Aug 10 04:09:18 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 10 Aug 2021 00:09:18 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 161 - Still Failing! In-Reply-To: <1665503504.374.1628529897052.JavaMail.javamailuser@localhost> References: <1665503504.374.1628529897052.JavaMail.javamailuser@localhost> Message-ID: <1302871151.385.1628568559714.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 161 Status: Still Failing Timestamp: 20210810T002448Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210810T000447Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210810T000447Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210810T000447Z/logs MASTER_BUILD_NUMBER: 168 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210810T000447Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210810T000447Z DOCKER_BUILD_ID: jenkins-master-containers-20210810T000447Z-builder TIMESTAMP: 20210810T000447Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210810T000447Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210810T000447Z/outputs From build.starlingx at gmail.com Tue Aug 10 04:09:21 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 10 Aug 2021 00:09:21 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 168 - Still Failing! In-Reply-To: <1326011447.377.1628529899213.JavaMail.javamailuser@localhost> References: <1326011447.377.1628529899213.JavaMail.javamailuser@localhost> Message-ID: <1567353368.388.1628568561719.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 168 Status: Still Failing Timestamp: 20210810T000447Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210810T000447Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Charles.Short at windriver.com Tue Aug 10 15:33:18 2021 From: Charles.Short at windriver.com (Short, Charles) Date: Tue, 10 Aug 2021 15:33:18 +0000 Subject: [Starlingx-discuss] Support for Python3.9 Message-ID: Hello, Recently it was decided to move from Centos to Debian as a base operating system for the StarlingX project [1]. Debian bullseye uses python3.9 as a base version for Python. In order to help the integration of python3.9 we have been adding new python3.9 gating jobs to gerrit.[2] Once the python3.9 gates start passing we remove the python3.6 gates and only support python2.7 and python3.9. In order to facilitate developers access to python3.9 we have created as dockerfile[3] that developers can use to build a python3.9 docker container. The container uses Ubuntu Focal, with python2.7, python3.6, and python3.9 installed. If you have any questions please let me know. chuck [1] https://review.opendev.org/c/starlingx/specs/+/780332 [2] https://review.opendev.org/q/topic:py39-gate [3] https://github.com/zulcss/stx-python -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Aug 11 12:28:35 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 11 Aug 2021 12:28:35 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Aug 11, 2021) Message-ID: Hi all, reminder of the weekly TSC/Community calls coming up later today. Please feel free to add other items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210811T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From scott.little at windriver.com Wed Aug 11 13:07:47 2021 From: scott.little at windriver.com (Scott Little) Date: Wed, 11 Aug 2021 09:07:47 -0400 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 168 - Still Failing! In-Reply-To: <1567353368.388.1628568561719.JavaMail.javamailuser@localhost> References: <1326011447.377.1628529899213.JavaMail.javamailuser@localhost> <1567353368.388.1628568561719.JavaMail.javamailuser@localhost> Message-ID: Container builds are currently failing on a ClearLinux download due to SSL certificate issue. We are investigating the issue. Scott On 2021-08-10 12:09 a.m., build.starlingx at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_layer_containers_master_master > Build #: 168 > Status: Still Failing > Timestamp: 20210810T000447Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210810T000447Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: true > FORCE_BUILD: false > > _______________________________________________ > 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 Bill.Zvonar at windriver.com Wed Aug 11 14:38:00 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 11 Aug 2021 14:38:00 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Aug 11, 2021) In-Reply-To: References: Message-ID: >From today's call... * Standing Topics * Build/Sanity * Daily sanity reports for bare metal are still not available * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-August/011870.html * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-August/011875.html * per Austin & Frank, it appears that we've never had a successful sanity on bare metal w/ the new kernel (which went in on July 28) * Austin has suggested on https://bugs.launchpad.net/starlingx/+bug/1938559 that Nic/Alex try installing from the ISO rather than PXE Boot * Austin to send an update to the mailing list on the status & next steps, to make sure the kernel team is aware & involved * container builds failing * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-August/011884.html * Davlet investigating, has posted review for fix to go back to previous version of ClearLinux * https://review.opendev.org/c/starlingx/integ/+/804133 * Gerrit Reviews in Need of Attention * Python 3 * https://review.opendev.org/q/topic:%2522py3%2522+(status:open) * multiple versions of Golang (to support K8s upgrade) * https://review.opendev.org/c/starlingx/compile/+/804123 * https://review.opendev.org/c/starlingx/containers/+/804130 * https://review.opendev.org/c/starlingx/integ/+/804131/1 * Topics for this Week * Zuul Gates for Python 3 * this is coming to (most) repos - your code will need to work for Python 3 otherwise you won't be able to merge * first email on the topic: http://lists.starlingx.io/pipermail/starlingx-discuss/2021-August/011882.html * ARs from Previous Meetings * DockerHub - no update yet, Bill send a chaser in to DockerHub * CENGN Backups - per Anthony, active discussion on this, asked for 8TB of space * Open Requests for Help * Integration of a private 5G core Net * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-August/011865.html * Greg will send some follow-up questions -----Original Message----- From: Zvonar, Bill Sent: Wednesday, August 11, 2021 8:29 AM To: StarlingX ML Subject: Community (& TSC) Call (Aug 11, 2021) Hi all, reminder of the weekly TSC/Community calls coming up later today. Please feel free to add other items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210811T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From pilon.dayo at gmail.com Wed Aug 11 16:07:59 2021 From: pilon.dayo at gmail.com (Dayo Pilon) Date: Wed, 11 Aug 2021 18:07:59 +0200 Subject: [Starlingx-discuss] AIO upgrade Message-ID: Hi, I would like to know if it is possible to upgrade from an All-in-one Simplex to an All-in-one Duplex without reinstalling the controller nodes? And from a AIO-DX, is it possible to upgrade to a standard deployment ? Regards, Dayo -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Thu Aug 12 01:04:56 2021 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 12 Aug 2021 01:04:56 +0000 Subject: [Starlingx-discuss] Bare metal install failure after kernel upgrade Message-ID: Hi Kernel Team: As you may know, after kernel upgrade patches were merged, we haven't yet any test pass on Bare metal . Virtual test environment test pass. Short summary about LP [1] : 1) Bare Metal Sanity Test environment is using pxe to install controller-0, which failed install after July-30 , July 29 iso is OK on Same Setup. 2) Network is fine , the initrd.img etc can be get from jumper server. 3) If manually use ISO to install controller-0 , controller-0 can be installed. 4) The log show Initramfs is corrupted, but initrd.img which is on pxeserver unzip successfully. If any clue to debug , please let us know. [1] https://bugs.launchpad.net/starlingx/+bug/1938559 Thanks. BR Austin Sun. From: Sun, Austin Sent: Monday, August 9, 2021 2:58 PM To: Dimofte, Alexandru ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210807T013626Z Hi Alex: It seems the boot failure because root partition is not recognized. Please share the HW info such as RAID controller etc. Thanks. BR Austin Sun. From: Dimofte, Alexandru > Sent: Monday, August 9, 2021 1:44 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210807T013626Z Sanity Test from 2021-August-09 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210807T013626Z/outputs/iso/) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210807T013626Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz All baremetal configurations failed because of: https://bugs.launchpad.net/starlingx/+bug/1938559 =========================================== Sanity Test executed on BareMetal Environment Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Kind Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 5155 bytes Desc: image003.png URL: From captain_tx at 163.com Thu Aug 12 08:55:50 2021 From: captain_tx at 163.com (Captain) Date: Thu, 12 Aug 2021 16:55:50 +0800 (CST) Subject: [Starlingx-discuss] Download images and push to local registry Failed Message-ID: <46e0585b.8faa.17b399328f4.Coremail.captain_tx@163.com> Hi, I deploy starlingx according to the tutorial(https://docs.starlingx.io/r/stx.5.0/deploy_install_guides/r5_release/bare_metal/bootstrapping-from-a-private-docker-registry.html), which is always stuck where the docker image is downloaded.Could you please help me? Thanks. Issues: 1. When I run `ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap.yml`, the task `[common/push-docker-images: Download images and push to local registry]` will always stay here for a long time. Kind regards, Xurong Zhang -------------- next part -------------- An HTML attachment was scrubbed... URL: From Steve.Geary at windriver.com Thu Aug 12 13:31:45 2021 From: Steve.Geary at windriver.com (Geary, Stephen (Steve)) Date: Thu, 12 Aug 2021 13:31:45 +0000 Subject: [Starlingx-discuss] Guiding Technical Influencers Message-ID: Hello StarlingX Community, I would like propose an initiative to more effectively appeal to technical influencers' search and evaluation flow. My belief is that technical influencers searching for an answer to a challenge they, or their company, have will avoid over-investing in early evaluation. I believe that quickly experienced proof-points of starlingx claims play directly into how a technical influencer researches possibilities. My initial idea would be to create 5 minute video that are guided experiences through demonstrating each of the 6 claims asserted on the sites page: reliable, scalable, small footprint, ultra-low latency, secure, and lifecycle management. I am sure there are other possibilities and ideas too! Let's hear them. Steve Geary Director, Open Source ________________________________ [Wind River] M/ +1 970.776.0218 LinkedIn -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 6850 bytes Desc: image002.png URL: From openinfradn at gmail.com Thu Aug 12 14:05:51 2021 From: openinfradn at gmail.com (open infra) Date: Thu, 12 Aug 2021 19:35:51 +0530 Subject: [Starlingx-discuss] Edge Worker Provision Failed at 'Set hostname' Message-ID: Hi, I was provisioning Ubuntu 20.04 (has python 3.8) based Edge Worker but failed at 'Set hostname' python interpreter set as ansible_python_interpreter: /usr/bin/python3. https://paste.opendev.org/show/808036/ Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Thu Aug 12 14:35:04 2021 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 12 Aug 2021 14:35:04 +0000 Subject: [Starlingx-discuss] Integration of a private 5G core Net In-Reply-To: References: Message-ID: ... see in-lined comments below, Greg. From: Mansuroglu, Zekeriya Sent: Thursday, August 5, 2021 6:39 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Integration of a private 5G core Net [Please note: This e-mail is from an EXTERNAL e-mail address] Dear StarlingX community, I'm interested in the integration of a commercial 5G core with StarlingX. In the documentation I couldn't find any descriptions about how it should be done. [Greg] StarlingX is a Kubernetes/OpenStack platform for hosting containerized/virtualized applications. StarlingX can host a variety of applications, 5G, Other Telecom Services, Industrial Services, etc. . StarlingX Documentation currently does not provide descriptions of example application deployments/architectures on top of StarlingX. Is there any description of the interfaces of StarlingX from/to the 5g core and RAN? [Greg] The interfaces of StarlingX from/to Applications (such as 5g core and RAN) generally include - generic helm/kuberentes interfaces for managing the application in the kubernetes cluster, > this includes indirect interfaces with network and storage backends - interfaces with services provided by StarlingX in support of applications ... e.g. Cert-Manager, Vault, MetricsServer, etc. ... i.e. they are more kubernetes platform-level interfaces. Greg. Thanks, Zekeriya -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Thu Aug 12 16:30:31 2021 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 12 Aug 2021 16:30:31 +0000 Subject: [Starlingx-discuss] AIO upgrade In-Reply-To: References: Message-ID: This capability was added for Subclouds in a Distributed Cloud environment. https://docs.starlingx.io/dist_cloud/kubernetes/migrate-an-aiosx-subcloud-to-an-aiodx-subcloud.html … but believe it works for standalone clouds (with some minor issues) … extensive testing and debugging was not done in this area. Greg. From: Dayo Pilon Sent: Wednesday, August 11, 2021 12:08 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] AIO upgrade [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I would like to know if it is possible to upgrade from an All-in-one Simplex to an All-in-one Duplex without reinstalling the controller nodes? And from a AIO-DX, is it possible to upgrade to a standard deployment ? Regards, Dayo -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Fri Aug 13 01:48:18 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 13 Aug 2021 01:48:18 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Aug 11/2021 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.6.0 - References: - Release Planning Spreadsheet: https://docs.google.com/spreadsheets/d/13p0BMlBgJXUVForOFsblAJq9jA1-FMBlmhV5TIc70IE/edit#gid=1107209846 - Test Planning: https://drive.google.com/drive/folders/1lfm073XaFGxHZSAf0RPS1DGK6QCReO9u - Milestone-1 declared on July 12 - Next milestone: Milestone-2 is planned for August 23 - Milestone Criteria: - Feature plans defined and feature development well underway - Release test plan defined - including test automation deliverables - Feature plans are in good shape; just need to continue tracking against the provided milestones - From Michiel, Release test planning is progressing well - New Features - Prep features in support of Debian - Migrate Flock Services to Debian: https://storyboard.openstack.org/#!/story/2009101 - will start in stx.6.0 and only fully deliver in stx.7.0 - Upversion DRBD: https://storyboard.openstack.org/#!/story/2009067 - Expected to land in the stx.6.0 time-frame - Upversion Ceph: https://storyboard.openstack.org/#!/story/2009074 - Prep for stx.7.0 - Upversion puppet: SB To Be Created - Prep for stx.7.0 - Other - AIO-SX: Support for pci device/NIC replacement without host reinstall: https://storyboard.openstack.org/#!/story/2009112 - Small operational enhancement for card replacements; planning in progress From alexandru.dimofte at intel.com Fri Aug 13 13:37:47 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 13 Aug 2021 13:37:47 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210813T021017Z Message-ID: Sanity Test from 2021-August-13 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210813T021017Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210813T021017Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Virtual Environment Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Kind Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5155 bytes Desc: image001.png URL: From openinfradn at gmail.com Sat Aug 14 06:27:10 2021 From: openinfradn at gmail.com (open infra) Date: Sat, 14 Aug 2021 11:57:10 +0530 Subject: [Starlingx-discuss] Need a help to recover Openstack Inbox | specific pod is failing Message-ID: Hi, Openstack was failed and noticed that mariadb-server-1 pod is failing. openstack mariadb-server-0 0/1 Running openstack mariadb-server-1 0/1 CrashLoopBackOff I managed to get logs of each pod. mariadb-server-0 log: https://paste.opendev.org/show/808070/ and https://paste.opendev.org/show/808071/ mariadb-server-1 log: https://paste.opendev.org/show/808067/ I highly appreciate if I can get a hint or steps to resolve this issue. Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Sun Aug 15 01:34:33 2021 From: austin.sun at intel.com (Sun, Austin) Date: Sun, 15 Aug 2021 01:34:33 +0000 Subject: [Starlingx-discuss] Need a help to recover Openstack Inbox | specific pod is failing In-Reply-To: References: Message-ID: Hi Danishka: Mariadb-server-0 is new leading , but I did find any clue of server-1 crash info from log [1]. Are controllers available and any alarms ? [1] https://paste.opendev.org/show/808067/ Thanks. BR Austin Sun. From: open infra Sent: Saturday, August 14, 2021 2:27 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Need a help to recover Openstack Inbox | specific pod is failing Hi, Openstack was failed and noticed that mariadb-server-1 pod is failing. openstack mariadb-server-0 0/1 Running openstack mariadb-server-1 0/1 CrashLoopBackOff I managed to get logs of each pod. mariadb-server-0 log: https://paste.opendev.org/show/808070/ and https://paste.opendev.org/show/808071/ mariadb-server-1 log: https://paste.opendev.org/show/808067/ I highly appreciate if I can get a hint or steps to resolve this issue. Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Sun Aug 15 08:17:45 2021 From: openinfradn at gmail.com (open infra) Date: Sun, 15 Aug 2021 13:47:45 +0530 Subject: [Starlingx-discuss] Need a help to recover Openstack Inbox | specific pod is failing In-Reply-To: References: Message-ID: Hi Austin, On Sun, Aug 15, 2021 at 7:04 AM Sun, Austin wrote: > Hi Danishka: > > Mariadb-server-0 is new leading , but I did find any clue of server-1 > crash info from log [1]. > > > > Are controllers available and any alarms ? > > > Both controllers active and no alarms against controllers but 'Application Apply Failure' (stx -openstack) I have deleted all MariaDB pods, expecting new pods to be created by Kubernetes. But same result. > > > > [1] https://paste.opendev.org/show/808067/ > > > > > > Thanks. > BR > Austin Sun. > > *From:* open infra > *Sent:* Saturday, August 14, 2021 2:27 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Need a help to recover Openstack Inbox | > specific pod is failing > > > > Hi, > > > > > > Openstack was failed and noticed that mariadb-server-1 pod is failing. > > > > openstack mariadb-server-0 0/1 Running > > openstack mariadb-server-1 0/1 CrashLoopBackOff > > > > I managed to get logs of each pod. > > > > > > mariadb-server-0 log: > > https://paste.opendev.org/show/808070/ > > and > > https://paste.opendev.org/show/808071/ > > > > mariadb-server-1 log: > > https://paste.opendev.org/show/808067/ > > > > I highly appreciate if I can get a hint or steps to resolve this issue. > > > > > > > > > > Regards, > > Danishka > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yue.tao at windriver.com Mon Aug 16 03:17:35 2021 From: yue.tao at windriver.com (ytao) Date: Mon, 16 Aug 2021 11:17:35 +0800 Subject: [Starlingx-discuss] [Debian Build]: Layout of the debian folder In-Reply-To: <61fc5f83-49dd-5c31-d9db-5e4d986ab2c6@windriver.com> References: <61fc5f83-49dd-5c31-d9db-5e4d986ab2c6@windriver.com> Message-ID: <906ae3ea-b25e-4ed8-a55a-e43860f40322@windriver.com> On 7/27/21 10:52 AM, ytao wrote: > > > On 7/27/21 7:05 AM, Short, Charles wrote: >> Hi, > >       First of all, I'm appreciated for your input. > >> >> I had a look through the document and it looks okay. I just have a >> couple of comments/questions about the folder content: >> >> * **debver** - This is the package version of the debian package? >> This is generated from the debian/changelog when the package is >> built. I guess the problem is that you want to differentiate from >> a starlingx package and native package? My suggestion would be >> what the Ubuntu developers do. For example, if we have patches to >> apply for systemd, the debian version would be 247.3-3, while the >> StarlingX package would be 247.3-3stx0. Then a user or developer >> can quickly see that they are working with a native debian >> package or a starlingx modified package. >> >        For a Debian native package, the *debver* is the debian > version. We use it to download the src via "apt-source > packagname=debver", for a starlingx package, it is up to the > developer. I observed in CentOS version, they added a patch to change > the package version, for example > integ/base/lighttpd/centos/meta_patches/Update-package-versioning-for-TIS-format.patch, > which appends a 'tis' to package version, that requests developer to > update the version manually. After transiting to debian, OBS can > achieve it automatically. It can append 'tis' or 'stx' to a package, > so don't need developers to update it manually. > Recently, we found an issue related to "--append-to-version" option of sbuild, via which we append the ".stx" to a built package version, so that we don't need to involve a developer to modify revision manually. A upstream commit https://salsa.debian.org/debian/sbuild/commit/9741ec6eb018d500a93e607f998dda8af52c9ce0 forces the "--append-to-version"implies "--no-arch-all", which causes the packages with --arch-all are skipped by sbuild, for example, most of the python modules, so we have to give up the "--append-to-version" option. After reviewing the function "srpm_source_build_data()" in|| https://opendev.org/starlingx/root/src/branch/master/build-tools/srpm-utils in depth, we decide to inherit the PKG_GITREVCOUNT/SRC_GITREVCOUNT/ PKG_BASE_SRCREV/SRC_BASE_SRCREV 4 macros from CentOS version to increase the revision automatically. Difference with CentOS version is using a yaml file instead of build_srpm.data.  And we define a new environment variable $STX_DIST (default value is ".stx"), which is appended to built package version. A new yaml file is involved, why not to merge other files into the yaml file? Hence, we merge the dl_path/src_path/debver/debname into meta_data.yaml, a sample of the meta_data_yaml $cat integ/base/libfdt/debian/meta_data.yaml ================== debver: 1.4.4-1 debname: libfdt dl_path:   name: dtc-1.4.4.tar.gz   url: https://www.kernel.org/pub/software/utils/dtc/dtc-1.4.4.tar.gz   md5sum: e558cd0e244f122bcb4ebaca166aea4e revision:   dist: $STX_DIST   PKG_GITREVCOUNT: ================== More details please see the stx_deb_folder_layout.rst file. Thanks, ytao > >> * **deb_patches** - As a developer, if the package has its >> debian/patches I would rather use the debian/patches directory. >> If the directory doesnt exist I am more likely to create a >> debian/patches directory and then send a patch to debian to fix a >> problem. >> >        Exactly, we should send a fix to debian community and then > uprev the package to get the fix, but we also need to consider local > changes. The *patches" folder contains the local change for source > codes, that will be copied to debian/patches (or create it if doesn't > exist), and update the debian/patches/series. The *deb_patches* > contains the patches to change debian folder, for example, we want to > customize the installation of a package, we need to update > override_dh_install stage in debian/rules. The patches will be applied > to package/debian folder directly. > > >        The *deb_patches* is similar with centos/meta_patches > >        The *patches* is similar with centos/patches > >> * >> >> >> * **dl_path** - Debian already does this for you already, the >> debian/watch file keeps track of where to download a tarball, or >> a zip file, or a python wheel for you. You can use uscan(1), >> which is a part of devscripts package. Debian/Ubuntu developers >> have been doing this for years. >> (https://wiki.debian.org/debian/watch) >> > >          Thanks you for pointing me the debian/watch. I will take some > time to learn about debian/watch and go back soon. It looks a debian > file for monitoring the upstream version change. I am not sure if it > is suitable for a no debian package. In our internal discussion, > Davlet told me a special case, that the url of a tar ball likes this > https://api.github.com/repos/ceph/jerasure/tarball/96c76b89d661c163f65a014b8042c9354ccf7f31 > > >           As Davlet's suggestion, the *dl_path* refers to example file > > and the script that parses it > . > I will do assessment for debian/watch. > > > Thanks, > > ytao > > >> If you have any questions please let me know. >> >> Regards >> chuck >> >> debian/watch - Debian Wiki >> debian/watch. The file named watch in the debian directory is >> used to check for newer versions of upstream software is >> available and to download it if necessary. The download itself >> will be performed with the uscan program from the devscripts >> package. It takes the path to the debian directory that uses the >> watch file as an argument or searches the directories underneath >> the current working ... >> wiki.debian.org >> >> >> >> >> >> >> >> ------------------------------------------------------------------------ >> *From:* ytao >> *Sent:* July 26, 2021 3:33 AM >> *To:* starlingx-discuss at lists.starlingx.io >> ; Asselstine, Mark >> >> *Subject:* [Starlingx-discuss] [Debian Build]: Layout of the debian >> folder >> Hello Everyone: >> >> You may have known Wind River team is working on the transition to >> Debian OS, more details of the project can be found at >> https://docs.starlingx.io/specs/specs/stx-6.0/. My purpose is launching >> a discussion about the userspace packages transition to Debian. The spec >> can be found at >> https://docs.starlingx.io/specs/specs/stx-6.0/approved/starlingx_2008704_debian_transition.html >> >> In order to inherit the existing userspace construction as much as >> possible, our proposal is creating a 'debian' folder in same directory >> with 'centos' folder for each package. For example, the dhcp package in >> integ repo, it's centos folder is at: >> >> https://opendev.org/starlingx/integ/src/branch/master/base/dhcp/centos >> >> We will create a debian folder in same location >> >> https://opendev.org/starlingx/integ/src/branch/master/base/dhcp/debian. >> >> All materials in this folder control building dhcp under Debian host. >> The "stx_deb_folder_layout.rst" is the layout of debian folder. I also >> attach a couple of samples to demonstrate how to fill the debian folder >> for a debian package and a 3rd package. >> >> This layout is not the final version, I'm appreciated for any suggestion >> from you. >> >> >> Thanks, >> >> ytao >> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: stx_deb_folder_layout.rst Type: text/x-rst Size: 9452 bytes Desc: not available URL: From austin.sun at intel.com Mon Aug 16 07:22:11 2021 From: austin.sun at intel.com (Sun, Austin) Date: Mon, 16 Aug 2021 07:22:11 +0000 Subject: [Starlingx-discuss] Cancel StarlingX Distro-OpenStack: Bi-weekly Project Meeting -- 08/17 Message-ID: Hi All: Cancel 08/17 meeting. Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Mon Aug 16 07:28:57 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Mon, 16 Aug 2021 07:28:57 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210814T013527Z Message-ID: Sanity Test from 2021-August-14 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210814T013527Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210814T013527Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Virtual Environment AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Kind Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5155 bytes Desc: image001.png URL: From Charles.Short at windriver.com Mon Aug 16 12:44:37 2021 From: Charles.Short at windriver.com (Short, Charles) Date: Mon, 16 Aug 2021 12:44:37 +0000 Subject: [Starlingx-discuss] [Debian Build]: Layout of the debian folder In-Reply-To: <906ae3ea-b25e-4ed8-a55a-e43860f40322@windriver.com> References: <61fc5f83-49dd-5c31-d9db-5e4d986ab2c6@windriver.com> <906ae3ea-b25e-4ed8-a55a-e43860f40322@windriver.com> Message-ID: Hi, Comments in line From: Tao, Yue Sent: Sunday, August 15, 2021 11:18 PM To: Short, Charles ; starlingx-discuss at lists.starlingx.io; Asselstine, Mark ; Bai, Haiqing ; Panech, Davlet Subject: Re: [Starlingx-discuss] [Debian Build]: Layout of the debian folder On 7/27/21 10:52 AM, ytao wrote: On 7/27/21 7:05 AM, Short, Charles wrote: Hi, First of all, I'm appreciated for your input. I had a look through the document and it looks okay. I just have a couple of comments/questions about the folder content: * **debver** - This is the package version of the debian package? This is generated from the debian/changelog when the package is built. I guess the problem is that you want to differentiate from a starlingx package and native package? My suggestion would be what the Ubuntu developers do. For example, if we have patches to apply for systemd, the debian version would be 247.3-3, while the StarlingX package would be 247.3-3stx0. Then a user or developer can quickly see that they are working with a native debian package or a starlingx modified package. For a Debian native package, the *debver* is the debian version. We use it to download the src via "apt-source packagname=debver", for a starlingx package, it is up to the developer. I observed in CentOS version, they added a patch to change the package version, for example integ/base/lighttpd/centos/meta_patches/Update-package-versioning-for-TIS-format.patch, which appends a 'tis' to package version, that requests developer to update the version manually. After transiting to debian, OBS can achieve it automatically. It can append 'tis' or 'stx' to a package, so don't need developers to update it manually. Recently, we found an issue related to "--append-to-version" option of sbuild, via which we append the ".stx" to a built package version, so that we don't need to involve a developer to modify revision manually. A upstream commit https://salsa.debian.org/debian/sbuild/commit/9741ec6eb018d500a93e607f998dda8af52c9ce0 forces the "--append-to-version"implies "--no-arch-all", which causes the packages with --arch-all are skipped by sbuild, for example, most of the python modules, so we have to give up the "--append-to-version" option. Yeah I don’t think we should be using sbuild in this manner. To change the version of the package you should be using the “dch” command. Sbuild is akin to mock for fedora, and it should be really only used for building packages. After reviewing the function "srpm_source_build_data()" in https://opendev.org/starlingx/root/src/branch/master/build-tools/srpm-utils in depth, we decide to inherit the PKG_GITREVCOUNT/SRC_GITREVCOUNT/ PKG_BASE_SRCREV/SRC_BASE_SRCREV 4 macros from CentOS version to increase the revision automatically. Difference with CentOS version is using a yaml file instead of build_srpm.data. And we define a new environment variable $STX_DIST (default value is ".stx"), which is appended to built package version. A new yaml file is involved, why not to merge other files into the yaml file? Hence, we merge the dl_path/src_path/debver/debname into meta_data.yaml, a sample of the meta_data_yaml $cat integ/base/libfdt/debian/meta_data.yaml ================== debver: 1.4.4-1 debname: libfdt dl_path: name: dtc-1.4.4.tar.gz url: https://www.kernel.org/pub/software/utils/dtc/dtc-1.4.4.tar.gz md5sum: e558cd0e244f122bcb4ebaca166aea4e revision: dist: $STX_DIST PKG_GITREVCOUNT: ================== More details please see the stx_deb_folder_layout.rst file. Thanks, ytao * **deb_patches** - As a developer, if the package has its debian/patches I would rather use the debian/patches directory. If the directory doesnt exist I am more likely to create a debian/patches directory and then send a patch to debian to fix a problem. Exactly, we should send a fix to debian community and then uprev the package to get the fix, but we also need to consider local changes. The *patches" folder contains the local change for source codes, that will be copied to debian/patches (or create it if doesn't exist), and update the debian/patches/series. The *deb_patches* contains the patches to change debian folder, for example, we want to customize the installation of a package, we need to update override_dh_install stage in debian/rules. The patches will be applied to package/debian folder directly. The *deb_patches* is similar with centos/meta_patches The *patches* is similar with centos/patches * * **dl_path** - Debian already does this for you already, the debian/watch file keeps track of where to download a tarball, or a zip file, or a python wheel for you. You can use uscan(1), which is a part of devscripts package. Debian/Ubuntu developers have been doing this for years. (https://wiki.debian.org/debian/watch) Thanks you for pointing me the debian/watch. I will take some time to learn about debian/watch and go back soon. It looks a debian file for monitoring the upstream version change. I am not sure if it is suitable for a no debian package. In our internal discussion, Davlet told me a special case, that the url of a tar ball likes this https://api.github.com/repos/ceph/jerasure/tarball/96c76b89d661c163f65a014b8042c9354ccf7f31 As Davlet's suggestion, the *dl_path* refers to example file and the script that parses it. I will do assessment for debian/watch. Thanks, ytao If you have any questions please let me know. Regards chuck debian/watch - Debian Wiki debian/watch. The file named watch in the debian directory is used to check for newer versions of upstream software is available and to download it if necessary. The download itself will be performed with the uscan program from the devscripts package. It takes the path to the debian directory that uses the watch file as an argument or searches the directories underneath the current working ... wiki.debian.org ________________________________ From: ytao Sent: July 26, 2021 3:33 AM To: starlingx-discuss at lists.starlingx.io ; Asselstine, Mark Subject: [Starlingx-discuss] [Debian Build]: Layout of the debian folder Hello Everyone: You may have known Wind River team is working on the transition to Debian OS, more details of the project can be found at https://docs.starlingx.io/specs/specs/stx-6.0/. My purpose is launching a discussion about the userspace packages transition to Debian. The spec can be found at https://docs.starlingx.io/specs/specs/stx-6.0/approved/starlingx_2008704_debian_transition.html In order to inherit the existing userspace construction as much as possible, our proposal is creating a 'debian' folder in same directory with 'centos' folder for each package. For example, the dhcp package in integ repo, it's centos folder is at: https://opendev.org/starlingx/integ/src/branch/master/base/dhcp/centos We will create a debian folder in same location https://opendev.org/starlingx/integ/src/branch/master/base/dhcp/debian. All materials in this folder control building dhcp under Debian host. The "stx_deb_folder_layout.rst" is the layout of debian folder. I also attach a couple of samples to demonstrate how to fill the debian folder for a debian package and a 3rd package. This layout is not the final version, I'm appreciated for any suggestion from you. Thanks, ytao -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon Aug 16 23:59:12 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 16 Aug 2021 19:59:12 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1944 - Failure! Message-ID: <1586393393.6.1629158355449.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1944 Status: Failure Timestamp: 20210816T235033Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210816T233815Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20210816T233815Z DOCKER_BUILD_ID: jenkins-master-flock-20210816T233815Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210816T233815Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20210816T233815Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From build.starlingx at gmail.com Mon Aug 16 23:59:17 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 16 Aug 2021 19:59:17 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 582 - Failure! Message-ID: <1466287050.9.1629158357855.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 582 Status: Failure Timestamp: 20210816T233815Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210816T233815Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From yue.tao at windriver.com Tue Aug 17 01:32:27 2021 From: yue.tao at windriver.com (ytao) Date: Tue, 17 Aug 2021 09:32:27 +0800 Subject: [Starlingx-discuss] [Debian Build]: Layout of the debian folder In-Reply-To: References: <61fc5f83-49dd-5c31-d9db-5e4d986ab2c6@windriver.com> <906ae3ea-b25e-4ed8-a55a-e43860f40322@windriver.com> Message-ID: On 8/16/21 8:44 PM, Short, Charles wrote: > > Hi, > > Comments in line > > *From:*Tao, Yue > *Sent:* Sunday, August 15, 2021 11:18 PM > *To:* Short, Charles ; > starlingx-discuss at lists.starlingx.io; Asselstine, Mark > ; Bai, Haiqing > ; Panech, Davlet > *Subject:* Re: [Starlingx-discuss] [Debian Build]: Layout of the > debian folder > > On 7/27/21 10:52 AM, ytao wrote: > > On 7/27/21 7:05 AM, Short, Charles wrote: > > Hi, > >       First of all, I'm appreciated for your input. > > I had a look through the document and it looks okay. I just > have a couple of comments/questions about the folder content: > > * **debver** - This is the package version of the debian > package? This is generated from the debian/changelog when > the package is built. I guess the problem is that you want > to differentiate from a starlingx package and native > package? My suggestion would be what the Ubuntu developers > do. For example, if we have patches to apply for systemd, > the debian version would be 247.3-3, while the StarlingX > package would be 247.3-3stx0. Then a user or developer can > quickly see that they are working with a native debian > package or a starlingx modified package. > >        For a Debian native package, the *debver* is the debian > version. We use it to download the src via "apt-source > packagname=debver", for a starlingx package, it is up to the > developer. I observed in CentOS version, they added a patch to > change the package version, for example > integ/base/lighttpd/centos/meta_patches/Update-package-versioning-for-TIS-format.patch, > which appends a 'tis' to package version, that requests developer > to update the version manually. After transiting to debian, OBS > can achieve it automatically. It can append 'tis' or 'stx' to a > package, so don't need developers to update it manually. > > Recently, we found an issue related to "--append-to-version" option of > sbuild, via which we append the ".stx" to a built package version, so > that we don't need to involve a developer to modify revision manually. > A upstream commit > https://salsa.debian.org/debian/sbuild/commit/9741ec6eb018d500a93e607f998dda8af52c9ce0 > forces the "--append-to-version"implies "--no-arch-all", which causes > the packages with --arch-all are skipped by sbuild, for example, most > of the python modules, so we have to give up the "--append-to-version" > option. > > Yeah I don’t think we should be using sbuild in this manner. To change > the version of the package you should be using the “dch” command. > Sbuild is akin to mock for fedora, and it should be really only used > for building packages. > Yeah, new method is using "dch" command to update changelog by parsing the "revision" of meta_data.yaml. ytao > After reviewing the function "srpm_source_build_data()" in > https://opendev.org/starlingx/root/src/branch/master/build-tools/srpm-utils > in depth, we decide to inherit the PKG_GITREVCOUNT/SRC_GITREVCOUNT/ > > PKG_BASE_SRCREV/SRC_BASE_SRCREV 4 macros from CentOS version to > increase the revision automatically. Difference with CentOS version is > using a yaml file instead of build_srpm.data.  And we define a new > environment variable $STX_DIST (default value is ".stx"), which is > appended to built package version. > > A new yaml file is involved, why not to merge other files into the > yaml file? Hence, we merge the dl_path/src_path/debver/debname into > meta_data.yaml, a sample of the meta_data_yaml > > $cat integ/base/libfdt/debian/meta_data.yaml > > ================== > > debver: 1.4.4-1 > debname: libfdt > dl_path: >   name: dtc-1.4.4.tar.gz >   url: https://www.kernel.org/pub/software/utils/dtc/dtc-1.4.4.tar.gz >   md5sum: e558cd0e244f122bcb4ebaca166aea4e > revision: >   dist: $STX_DIST >   PKG_GITREVCOUNT: > > ================== > > More details please see the stx_deb_folder_layout.rst file. > > Thanks, > > ytao > > * **deb_patches** - As a developer, if the package has its > debian/patches I would rather use the debian/patches > directory. If the directory doesnt exist I am more likely > to create a debian/patches directory and then send a patch > to debian to fix a problem. > >        Exactly, we should send a fix to debian community and then > uprev the package to get the fix, but we also need to consider > local changes. The *patches" folder contains the local change for > source codes, that will be copied to debian/patches (or create it > if doesn't exist), and update the debian/patches/series. The > *deb_patches* contains the patches to change debian folder, for > example, we want to customize the installation of a package, we > need to update override_dh_install stage in debian/rules. The > patches will be applied to package/debian folder directly. > >        The *deb_patches* is similar with centos/meta_patches > >        The *patches* is similar with centos/patches > > * > * **dl_path** - Debian already does this for you already, > the debian/watch file keeps track of where to download a > tarball, or a zip file, or a python wheel for you. You can > use uscan(1), which is a part of devscripts package. > Debian/Ubuntu developers have been doing this for years. > (https://wiki.debian.org/debian/watch) > >          Thanks you for pointing me the debian/watch. I will take > some time to learn about debian/watch and go back soon. It looks a > debian file for monitoring the upstream version change. I am not > sure if it is suitable for a no debian package. In our internal > discussion, Davlet told me a special case, that the url of a tar > ball likes this > https://api.github.com/repos/ceph/jerasure/tarball/96c76b89d661c163f65a014b8042c9354ccf7f31 > >           As Davlet's suggestion, the *dl_path* refers to example > file > > and the script that parses it > . > I will do assessment for debian/watch. > > Thanks, > > ytao > > If you have any questions please let me know. > > Regards > > chuck > > debian/watch - Debian Wiki > > debian/watch. The file named watch in the debian directory is > used to check for newer versions of upstream software is > available and to download it if necessary. The download itself > will be performed with the uscan program from the devscripts > package. It takes the path to the debian directory that uses > the watch file as an argument or searches the directories > underneath the current working ... > > wiki.debian.org > > ------------------------------------------------------------------------ > > *From:* ytao > > *Sent:* July 26, 2021 3:33 AM > *To:* starlingx-discuss at lists.starlingx.io > > > ; Asselstine, > Mark > > *Subject:* [Starlingx-discuss] [Debian Build]: Layout of the > debian folder > > Hello Everyone: > > You may have known Wind River team is working on the > transition to > Debian OS, more details of the project can be found at > https://docs.starlingx.io/specs/specs/stx-6.0/. My purpose is > launching > a discussion about the userspace packages transition to > Debian. The spec > can be found at > https://docs.starlingx.io/specs/specs/stx-6.0/approved/starlingx_2008704_debian_transition.html > > In order to inherit the existing userspace construction as > much as > possible, our proposal is creating a 'debian' folder in same > directory > with 'centos' folder for each package. For example, the dhcp > package in > integ repo, it's centos folder is at: > > https://opendev.org/starlingx/integ/src/branch/master/base/dhcp/centos > > We will create a debian folder in same location > > https://opendev.org/starlingx/integ/src/branch/master/base/dhcp/debian. > > All materials in this folder control building dhcp under > Debian host. > The "stx_deb_folder_layout.rst" is the layout of debian > folder. I also > attach a couple of samples to demonstrate how to fill the > debian folder > for a debian package and a 3rd package. > > This layout is not the final version, I'm appreciated for any > suggestion > from you. > > > Thanks, > > ytao > -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Aug 17 04:43:31 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 17 Aug 2021 00:43:31 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_download_mirror - Build # 1340 - Failure! Message-ID: <2063395696.12.1629175412124.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 1340 Status: Failure Timestamp: 20210817T043626Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210817T043000Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master DOCKER_BUILD_ID: jenkins-master-20210817T043000Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210817T043000Z/logs MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210817T043000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Tue Aug 17 04:43:33 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 17 Aug 2021 00:43:33 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1017 - Failure! Message-ID: <417432235.15.1629175414260.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1017 Status: Failure Timestamp: 20210817T043000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210817T043000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From openinfradn at gmail.com Tue Aug 17 11:25:38 2021 From: openinfradn at gmail.com (open infra) Date: Tue, 17 Aug 2021 16:55:38 +0530 Subject: [Starlingx-discuss] Need a help to recover Openstack Inbox | specific pod is failing In-Reply-To: References: Message-ID: In the logs of the pod (mariadb-server-1) [4], I noticed issues related to mariadb tables but only in the failed pod. This pod keeps rebooting and also stx-openstack applying keep fails each time. 2021-08-17 00:19:12,237 - OpenStack-Helm Mariadb - INFO - Recovering wsrep position: 2021-08-17 0:19:10 140357388367552 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded 2021-08-17 00:19:12,237 - OpenStack-Helm Mariadb - INFO - Recovering wsrep position: 2021-08-17 0:19:10 140357388367552 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist [1] https://paste.opendev.org/show/808124/ [2] https://paste.opendev.org/show/808125/ [3] https://paste.opendev.org/show/808126/ [4] https://paste.opendev.org/show/808127/ [5] https://paste.opendev.org/show/808128/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From douglas.pereira at windriver.com Tue Aug 17 12:07:33 2021 From: douglas.pereira at windriver.com (Douglas Lopes Pereira) Date: Tue, 17 Aug 2021 09:07:33 -0300 Subject: [Starlingx-discuss] Need a help to recover Openstack Inbox | specific pod is failing In-Reply-To: References: Message-ID: Hi Danishka, can you confirm there is enough disk space in your controller for the MariaDB pod to recover? Regards, Doug On Tue, Aug 17, 2021 at 8:25 AM open infra wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > In the logs of the pod (mariadb-server-1) [4], I noticed issues related to > mariadb tables but only in the failed pod. > This pod keeps rebooting and also stx-openstack applying keep fails each > time. > > 2021-08-17 00:19:12,237 - OpenStack-Helm Mariadb - INFO - Recovering wsrep position: 2021-08-17 0:19:10 140357388367552 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded > 2021-08-17 00:19:12,237 - OpenStack-Helm Mariadb - INFO - Recovering wsrep position: 2021-08-17 0:19:10 140357388367552 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist > > > [1] https://paste.opendev.org/show/808124/ > > [2] https://paste.opendev.org/show/808125/ > > [3] https://paste.opendev.org/show/808126/ > > [4] https://paste.opendev.org/show/808127/ > > [5] https://paste.opendev.org/show/808128/ > > > _______________________________________________ > 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 austin.sun at intel.com Mon Aug 16 07:21:02 2021 From: austin.sun at intel.com (Sun, Austin) Date: Mon, 16 Aug 2021 07:21:02 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Distro-OpenStack: Bi-weekly Project Meeting(Summer Time) Message-ID: Hi folks, This is a new series of bi-weekly project meeting on StarlingX Distro-OpenStack. Your participation to this meeting and/or other offline contribution by all means are highly appreciated! Project Team Etherpad: https://etherpad.openstack.org/p/stx-distro-openstack-meetings The Summer Time Slot for this meeting : CST: 9:00 PM (China, Shanghai ) PST: 7:00 AM (US West , US, Oregon) EST: 9:00 AM (East Canada , Canada Ottawa) Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3783 bytes Desc: not available URL: From Linda.Wang at windriver.com Tue Aug 17 14:24:48 2021 From: Linda.Wang at windriver.com (Linda Wang) Date: Tue, 17 Aug 2021 07:24:48 -0700 Subject: [Starlingx-discuss] Bi-Weekly StarlingX OS Distro & Multi-OS Meeting Minutes: August 4, 2021 Message-ID: <42980620-eb93-8b3e-2701-9dc01c4e0deb@windriver.com> 08/04/2021 Attendess:Frank Miller, Anthony Nowell, Bill Zvonar, Bob Church, Steve Gearym Charles Short, Mark Asseslstine Agenda items: 1. OS Distro (Mark) * Python Status o Stop the python porting until we get a debian OS build * 5.10 kernel is now on master o 7/30's build has included the 5.10 kernel o it's important get to latest update o crashdump boot cmdline parameter needs to be evaluated since crashdump=auto is not there in the 5.10 kernel. * Demo of Debian OS build system last week. o more review sent out this week. * Feedback coming in on Debian folder structure o Debian utility can track upstream status * Individual offload container, from core containers to offload has been demo'ed. o worked on updated OS packages from CentOS to Debian packages o do we have a list of packages that we can needs update? + yes, Saul has that list from previously upstream + see the "New Plan" tab of https://docs.google.com/spreadsheets/d/1QhS8fnBCQCqPCO_bXg1shwlcHfBEv1W7Lk1EovHV0qg/edit#gid=531255817 # Dev Backlog column # N/A: patch is not applicable to Debian (i.e. mostly RPM specfile changes to add the patches themselves) # yes: patch is required to bring up a simplex IPv4 host # no: patch is probably required for other configurations (e.g. IPv6, multiple nodes, secure boot) # drop: patch not required on Debian + Further breakdown between OS and non-OS has only been done for the teams working on the transition in WR and does not impact the community * Review of patches is still on-going, and number 1 priority o container and repo patches are out for review.. o roughly 10-15 patches are out for review at the moment. 2. Multi-OS * N/A -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Aug 17 15:46:37 2021 From: scott.little at windriver.com (Scott Little) Date: Tue, 17 Aug 2021 11:46:37 -0400 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 582 - Failure! In-Reply-To: <1466287050.9.1629158357855.JavaMail.javamailuser@localhost> References: <1466287050.9.1629158357855.JavaMail.javamailuser@localhost> Message-ID: A build failure in fm-common http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210816T233815Z/logs/std/failed-packages/fm-common-1.0-55.tis/ Fix has merged https://review.opendev.org/c/starlingx/fault/+/802721 I will start a new build shortly ... On 2021-08-16 7:59 p.m., build.starlingx at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_layer_flock_master_master > Build #: 582 > Status: Failure > Timestamp: 20210816T233815Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210816T233815Z/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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Wed Aug 18 04:44:20 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 18 Aug 2021 00:44:20 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_download_mirror - Build # 1341 - Still Failing! In-Reply-To: <1249216912.10.1629175407903.JavaMail.javamailuser@localhost> References: <1249216912.10.1629175407903.JavaMail.javamailuser@localhost> Message-ID: <1074544215.20.1629261862196.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 1341 Status: Still Failing Timestamp: 20210818T043632Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210818T043000Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master DOCKER_BUILD_ID: jenkins-master-20210818T043000Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210818T043000Z/logs MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20210818T043000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Wed Aug 18 04:44:24 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 18 Aug 2021 00:44:24 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_master_master - Build # 1018 - Still Failing! In-Reply-To: <215523687.13.1629175412603.JavaMail.javamailuser@localhost> References: <215523687.13.1629175412603.JavaMail.javamailuser@localhost> Message-ID: <946361154.23.1629261866610.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 1018 Status: Still Failing Timestamp: 20210818T043000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20210818T043000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From Bill.Zvonar at windriver.com Wed Aug 18 12:24:14 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 18 Aug 2021 12:24:14 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Aug 18, 2021) Message-ID: Hi all, reminder of the weekly TSC/Community calls coming up later today. Please feel free to add other items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210818T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From openinfradn at gmail.com Wed Aug 18 14:13:08 2021 From: openinfradn at gmail.com (open infra) Date: Wed, 18 Aug 2021 19:43:08 +0530 Subject: [Starlingx-discuss] Need a help to recover Openstack Inbox | specific pod is failing In-Reply-To: References: Message-ID: cleared disks of controller-0 and reinstall. make controller-0 as the active controller (controller-1 was the active controller) deleted and added stx-openstack but still failing the same pod. https://paste.opendev.org/show/808170/ On Tue, Aug 17, 2021 at 6:30 PM open infra wrote: > Hi Douglas, > > Both pods have similar disk usage and 4.4GB remaining space out of 4.8GB > in /var/lib/mysql directory. > https://paste.opendev.org/show/808142/ > > I have allocated 200GB for docker-lv > Regards, > Danishka > > On Tue, Aug 17, 2021 at 5:38 PM Douglas Lopes Pereira < > douglas.pereira at windriver.com> wrote: > >> Hi Danishka, >> >> can you confirm there is enough disk space in your controller for the >> MariaDB pod to recover? >> >> Regards, >> Doug >> >> On Tue, Aug 17, 2021 at 8:25 AM open infra wrote: >> >>> [Please note: This e-mail is from an EXTERNAL e-mail address] >>> >>> In the logs of the pod (mariadb-server-1) [4], I noticed issues related >>> to mariadb tables but only in the failed pod. >>> This pod keeps rebooting and also stx-openstack applying keep fails each >>> time. >>> >>> 2021-08-17 00:19:12,237 - OpenStack-Helm Mariadb - INFO - Recovering wsrep position: 2021-08-17 0:19:10 140357388367552 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded >>> 2021-08-17 00:19:12,237 - OpenStack-Helm Mariadb - INFO - Recovering wsrep position: 2021-08-17 0:19:10 140357388367552 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist >>> >>> >>> [1] https://paste.opendev.org/show/808124/ >>> >>> [2] https://paste.opendev.org/show/808125/ >>> >>> [3] https://paste.opendev.org/show/808126/ >>> >>> [4] https://paste.opendev.org/show/808127/ >>> >>> [5] https://paste.opendev.org/show/808128/ >>> >>> >>> _______________________________________________ >>> 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 ildiko.vancsa at gmail.com Wed Aug 18 14:45:17 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 18 Aug 2021 07:45:17 -0700 Subject: [Starlingx-discuss] Upcoming TSC and PL/TL elections Message-ID: Hi StarlingX Community, It is a friendly reminder that the time for the fall election[1] period is coming up fast and therefore we need to start planning the process. We need to decide on timeframe for the elections. For TSC we have a nomination, a campaign and a voting period, while for PL/TL elections we have a nomination and a voting period defined officially. We are looking for a 3-week timeframe in the fall that doesn’t collide with any major holidays or milestones in the release process. We also plan to run an interim TSC election period this time around as we have 5 seats for the TSC and the terms of the current 3 members are up[2] in H2, 2021. We will run the regular election period to (re)elect these positions and we will also run an interim election to fill the remaining 2 seats for a half year period to grow the group back to the desired number and to support the staggered election process. The interim elections need separate dates to avoid confusions with the regular process. Please think about your preference about the election process to make sure that people are available to submit nominations as well as to be able to vote in the election process. If you have any questions or comments please reply to this thread or reach out to the election officials[3]. Thanks, [1] https://docs.starlingx.io/election/ [2] https://docs.starlingx.io/governance/reference/tsc/index.html [3] https://docs.starlingx.io/election/#election-officials From Bill.Zvonar at windriver.com Wed Aug 18 14:55:32 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 18 Aug 2021 14:55:32 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Aug 18, 2021) In-Reply-To: References: Message-ID: >From today's call... * Standing Topics * Build/Sanity * sanity on bare metal? * Austin said that Nic/Alex confirmed that the sanity was ok in their environment with an older ISO (pre-5.10 kernel) * Austin will follow up on the latest questions raised by Vefa in https://bugs.launchpad.net/starlingx/+bug/1938559, and will pull in Nic/Alex as needed * build issues * layered build issue late last week * fixed now, the issue was https://review.opendev.org/c/starlingx/fault/+/802721 -- something that could be caught by the Python 3 Zuul gate in future? * monolithic build issue yesterday * Scott investigated - was due to cherry-picking content from the CentOS 8 / Python 3 branch * container builds seem to be ok since the issue that was fixed last week * Gerrit Reviews in Need of Attention * nothing this week * Topics for this Week * Guiding Technical Influencers (Steve Geary) * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-August/011889.html * feedback welcome! * ARs from Previous Meetings * CENGN Backups - per Anthony, this is ongoing, we're not blocked at this point (setting up NFS from CENGN to somewhere, working through specs of the 8TB disk) * Open Requests for Help * Download images and push to local registry Failed (Xurong Zhang) * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-August/011888.html * Greg will respond * Edge Worker Provision Failed at 'Set hostname' (Danishka) * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-August/011890.html * Mingyuan will follow up with Danishka * OpenStack / mariadb Issue (Danishka) * issues around not fully removing / cleaning up mariadb when OpenStack is shut down * Thiago Brito has been helping, Danishka will raise a Launchpad for this -----Original Message----- From: Zvonar, Bill Sent: Wednesday, August 18, 2021 8:24 AM To: StarlingX ML Subject: Community (& TSC) Call (Aug 18, 2021) Hi all, reminder of the weekly TSC/Community calls coming up later today. Please feel free to add other items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210818T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 From Thiago.Brito at windriver.com Wed Aug 18 14:58:09 2021 From: Thiago.Brito at windriver.com (Brito, Thiago) Date: Wed, 18 Aug 2021 14:58:09 +0000 Subject: [Starlingx-discuss] Need a help to recover Openstack Inbox | specific pod is failing In-Reply-To: References: , Message-ID: Hi Danishka, Looking at your logs it seems like the missing table 'mysql.servers' is preventing the system to come up. Would you please raise a LP with those logs so we can dig deeper into this problem? It would be useful to have the full logs from these attempts. Once you do that, you might wanna try to "application-remove" stx-openstack and check if the PVC of mariadb is still on the system with "kubectl get pvc -n openstack". If that is the case, the app is probably trying to reuse the old "broken" database. Deleting that pvc and appling stx-openstack again should get your system up. Thiago ________________________________ From: open infra Sent: Wednesday, August 18, 2021 11:13 AM To: Pereira, Douglas ; starlingx-discuss at lists.starlingx.io ; Sun, Austin Subject: Re: [Starlingx-discuss] Need a help to recover Openstack Inbox | specific pod is failing [Please note: This e-mail is from an EXTERNAL e-mail address] cleared disks of controller-0 and reinstall. make controller-0 as the active controller (controller-1 was the active controller) deleted and added stx-openstack but still failing the same pod. https://paste.opendev.org/show/808170/ On Tue, Aug 17, 2021 at 6:30 PM open infra > wrote: Hi Douglas, Both pods have similar disk usage and 4.4GB remaining space out of 4.8GB in /var/lib/mysql directory. https://paste.opendev.org/show/808142/ I have allocated 200GB for docker-lv Regards, Danishka On Tue, Aug 17, 2021 at 5:38 PM Douglas Lopes Pereira > wrote: Hi Danishka, can you confirm there is enough disk space in your controller for the MariaDB pod to recover? Regards, Doug On Tue, Aug 17, 2021 at 8:25 AM open infra > wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] In the logs of the pod (mariadb-server-1) [4], I noticed issues related to mariadb tables but only in the failed pod. This pod keeps rebooting and also stx-openstack applying keep fails each time. 2021-08-17 00:19:12,237 - OpenStack-Helm Mariadb - INFO - Recovering wsrep position: 2021-08-17 0:19:10 140357388367552 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded 2021-08-17 00:19:12,237 - OpenStack-Helm Mariadb - INFO - Recovering wsrep position: 2021-08-17 0:19:10 140357388367552 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist [1] https://paste.opendev.org/show/808124/ [2] https://paste.opendev.org/show/808125/ [3] https://paste.opendev.org/show/808126/ [4] https://paste.opendev.org/show/808127/ [5] https://paste.opendev.org/show/808128/ _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Wed Aug 18 15:54:46 2021 From: openinfradn at gmail.com (open infra) Date: Wed, 18 Aug 2021 21:24:46 +0530 Subject: [Starlingx-discuss] Need a help to recover Openstack Inbox | specific pod is failing In-Reply-To: References: Message-ID: Hi Thiago, Please find my inline comments. On Wed, Aug 18, 2021 at 8:28 PM Brito, Thiago wrote: > Hi Danishka, > > Looking at your logs it seems like the missing table 'mysql.servers' is > preventing the system to come up. Would you please raise a LP with those > logs so we can dig deeper into this problem? It would be useful to have the > full logs from these attempts. > > Sure, I will raise a LP. > Once you do that, you might wanna try to "application-remove" > stx-openstack and check if the PVC of mariadb is still on the system with > "kubectl get pvc -n openstack". If that is the case, the app is probably > trying to reuse the old "broken" database. Deleting that pvc and appling > stx-openstack again should get your system up. > [sysadmin at controller-0 ~(keystone_admin)]$ kubectl get pvc -n openstack No resources found in openstack namespace. [sysadmin at controller-0 ~(keystone_admin)]$ kubectl get pods -n openstack -o wide No resources found in openstack namespace. https://paste.opendev.org/show/808178/ > > Thiago > ------------------------------ > *From:* open infra > *Sent:* Wednesday, August 18, 2021 11:13 AM > *To:* Pereira, Douglas ; > starlingx-discuss at lists.starlingx.io ; > Sun, Austin > *Subject:* Re: [Starlingx-discuss] Need a help to recover Openstack Inbox > | specific pod is failing > > > [Please note: This e-mail is from an EXTERNAL e-mail address] > cleared disks of controller-0 and reinstall. > make controller-0 as the active controller (controller-1 was the active > controller) > deleted and added stx-openstack but still failing the same pod. > > https://paste.opendev.org/show/808170/ > > > On Tue, Aug 17, 2021 at 6:30 PM open infra wrote: > > Hi Douglas, > > Both pods have similar disk usage and 4.4GB remaining space out of 4.8GB > in /var/lib/mysql directory. > https://paste.opendev.org/show/808142/ > > > I have allocated 200GB for docker-lv > Regards, > Danishka > > On Tue, Aug 17, 2021 at 5:38 PM Douglas Lopes Pereira < > douglas.pereira at windriver.com> wrote: > > Hi Danishka, > > can you confirm there is enough disk space in your controller for the > MariaDB pod to recover? > > Regards, > Doug > > On Tue, Aug 17, 2021 at 8:25 AM open infra wrote: > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > In the logs of the pod (mariadb-server-1) [4], I noticed issues related to > mariadb tables but only in the failed pod. > This pod keeps rebooting and also stx-openstack applying keep fails each > time. > > 2021-08-17 00:19:12,237 - OpenStack-Helm Mariadb - INFO - Recovering wsrep position: 2021-08-17 0:19:10 140357388367552 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded > 2021-08-17 00:19:12,237 - OpenStack-Helm Mariadb - INFO - Recovering wsrep position: 2021-08-17 0:19:10 140357388367552 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist > > > [1] https://paste.opendev.org/show/808124/ > > [2] https://paste.opendev.org/show/808125/ > > [3] https://paste.opendev.org/show/808126/ > > [4] https://paste.opendev.org/show/808127/ > > [5] https://paste.opendev.org/show/808128/ > > > _______________________________________________ > 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 charlesboyo at gmail.com Wed Aug 18 20:17:51 2021 From: charlesboyo at gmail.com (Charles Oluwaseun Oluboyo) Date: Wed, 18 Aug 2021 21:17:51 +0100 Subject: [Starlingx-discuss] Bootstrap of controller-0 failing due to missing tag in gcr.io registry Message-ID: Hi, I am unable to complete the bootstrap of controller-0 in a Virtual AIO-DX setup because 'gcr.io/kubernetes-helm/tiller:v2.16.1' no longer exists. Reviewing the image - https://console.cloud.google.com/gcr/images/kubernetes-helm/global/tiller - shows that all tags before v2.16.5 are missing (or have been removed). Please advise on how I can workaround this. Regards, Oluwaseun -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Fri Aug 20 05:55:30 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 20 Aug 2021 05:55:30 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210819T184902Z Message-ID: Sanity Test from 2021-August-19 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210819T184902Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210819T184902Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Virtual Environment Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 76 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 89 TCs ] Kind Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5155 bytes Desc: image001.png URL: From haochuan.z.chen at intel.com Fri Aug 20 06:55:01 2021 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 20 Aug 2021 06:55:01 +0000 Subject: [Starlingx-discuss] Need a help to recover Openstack Inbox | specific pod is failing In-Reply-To: References: Message-ID: Hi Danishka: You can check again, by firstly deleting this configmap and then delete mariadb pod to check. kubectl delete configmap -n openstack osh-openstack-mariadb-mariadb-state kubectl delete po mariadb-server-0 mariadb-server-1 -n openstack BR! From: open infra > Sent: Sunday, August 15, 2021 4:18 PM To: Sun, Austin > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Need a help to recover Openstack Inbox | specific pod is failing Hi Austin, On Sun, Aug 15, 2021 at 7:04 AM Sun, Austin > wrote: Hi Danishka: Mariadb-server-0 is new leading , but I did find any clue of server-1 crash info from log [1]. Are controllers available and any alarms ? Both controllers active and no alarms against controllers but 'Application Apply Failure' (stx -openstack) I have deleted all MariaDB pods, expecting new pods to be created by Kubernetes. But same result. [1] https://paste.opendev.org/show/808067/ Thanks. BR Austin Sun. From: open infra > Sent: Saturday, August 14, 2021 2:27 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Need a help to recover Openstack Inbox | specific pod is failing Hi, Openstack was failed and noticed that mariadb-server-1 pod is failing. openstack mariadb-server-0 0/1 Running openstack mariadb-server-1 0/1 CrashLoopBackOff I managed to get logs of each pod. mariadb-server-0 log: https://paste.opendev.org/show/808070/ and https://paste.opendev.org/show/808071/ mariadb-server-1 log: https://paste.opendev.org/show/808067/ I highly appreciate if I can get a hint or steps to resolve this issue. Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From pvmpublic at gmail.com Fri Aug 20 09:08:51 2021 From: pvmpublic at gmail.com (Pratik M.) Date: Fri, 20 Aug 2021 14:38:51 +0530 Subject: [Starlingx-discuss] Bootstrap of controller-0 failing due to missing tag in gcr.io registry In-Reply-To: References: Message-ID: Hi, This causes the R5.0 install to fail. Pl. raise a bug. You may try changing the tag here: /usr/share/ansible/stx-ansible/playbooks/roles/common/load-images-information/vars/k8s-v1.18.1/system-images.yml I used tiller:v2.16.10 and it went ahead but is now stuck in armada pod restart. BR On Thu, Aug 19, 2021 at 1:52 AM Charles Oluwaseun Oluboyo < charlesboyo at gmail.com> wrote: > Hi, > > I am unable to complete the bootstrap of controller-0 in a Virtual AIO-DX > setup because 'gcr.io/kubernetes-helm/tiller:v2.16.1' no longer exists. > > Reviewing the image - > https://console.cloud.google.com/gcr/images/kubernetes-helm/global/tiller > - shows that all tags before v2.16.5 are missing (or have been removed). > > Please advise on how I can workaround this. > > Regards, > > Oluwaseun > _______________________________________________ > 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 pvmpublic at gmail.com Fri Aug 20 10:54:19 2021 From: pvmpublic at gmail.com (Pratik M.) Date: Fri, 20 Aug 2021 16:24:19 +0530 Subject: [Starlingx-discuss] Bootstrap of controller-0 failing due to missing tag in gcr.io registry In-Reply-To: References: Message-ID: Hi, You would also need to change the tag in stx-ansible/playbooks/roles/common/armada-helm/templates/armada-overrides.yaml.j2 On Fri, Aug 20, 2021 at 2:38 PM Pratik M. wrote: > Hi, > This causes the R5.0 install to fail. Pl. raise a bug. > > You may try changing the tag here: > /usr/share/ansible/stx-ansible/playbooks/roles/common/load-images-information/vars/k8s-v1.18.1/system-images.yml > > > I used tiller:v2.16.10 and it went ahead but is now stuck in armada pod > restart. > > BR > > On Thu, Aug 19, 2021 at 1:52 AM Charles Oluwaseun Oluboyo < > charlesboyo at gmail.com> wrote: > >> Hi, >> >> I am unable to complete the bootstrap of controller-0 in a Virtual AIO-DX >> setup because 'gcr.io/kubernetes-helm/tiller:v2.16.1' no longer exists. >> >> Reviewing the image - >> https://console.cloud.google.com/gcr/images/kubernetes-helm/global/tiller >> - shows that all tags before v2.16.5 are missing (or have been removed). >> >> Please advise on how I can workaround this. >> >> Regards, >> >> Oluwaseun >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Fri Aug 20 16:56:10 2021 From: openinfradn at gmail.com (open infra) Date: Fri, 20 Aug 2021 22:26:10 +0530 Subject: [Starlingx-discuss] Bootstrap of controller-0 failing due to missing tag in gcr.io registry In-Reply-To: References: Message-ID: Hi Pratik, I experienced the same issue today morning. I managed to complete the bootstrap with your fix. I have created a bug [1]. Please close it if Charles already created it. https://bugs.launchpad.net/starlingx/+bug/1940696 Thank you! Regards, Danishka On Fri, Aug 20, 2021 at 4:26 PM Pratik M. wrote: > Hi, > You would also need to change the tag in > > stx-ansible/playbooks/roles/common/armada-helm/templates/armada-overrides.yaml.j2 > > On Fri, Aug 20, 2021 at 2:38 PM Pratik M. wrote: > >> Hi, >> This causes the R5.0 install to fail. Pl. raise a bug. >> >> You may try changing the tag here: >> /usr/share/ansible/stx-ansible/playbooks/roles/common/load-images-information/vars/k8s-v1.18.1/system-images.yml >> >> >> I used tiller:v2.16.10 and it went ahead but is now stuck in armada pod >> restart. >> >> BR >> >> On Thu, Aug 19, 2021 at 1:52 AM Charles Oluwaseun Oluboyo < >> charlesboyo at gmail.com> wrote: >> >>> Hi, >>> >>> I am unable to complete the bootstrap of controller-0 in a Virtual >>> AIO-DX setup because 'gcr.io/kubernetes-helm/tiller:v2.16.1' no longer >>> exists. >>> >>> Reviewing the image - >>> https://console.cloud.google.com/gcr/images/kubernetes-helm/global/tiller >>> - shows that all tags before v2.16.5 are missing (or have been removed). >>> >>> Please advise on how I can workaround this. >>> >>> Regards, >>> >>> Oluwaseun >>> _______________________________________________ >>> 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Fri Aug 20 19:21:00 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 20 Aug 2021 19:21:00 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210820T013615Z Message-ID: Sanity Test from 2021-August-20 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210820T013615Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210820T013615Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] Kind Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5155 bytes Desc: image001.png URL: From charlesboyo at gmail.com Fri Aug 20 20:10:46 2021 From: charlesboyo at gmail.com (Charles Oluwaseun Oluboyo) Date: Fri, 20 Aug 2021 21:10:46 +0100 Subject: [Starlingx-discuss] Bootstrap of controller-0 failing due to missing tag in gcr.io registry In-Reply-To: References: Message-ID: Thank you Pratik and Danishka. That worked. Regards, Charles On Fri, Aug 20, 2021 at 5:56 PM open infra wrote: > Hi Pratik, > > I experienced the same issue today morning. > I managed to complete the bootstrap with your fix. > > I have created a bug [1]. > Please close it if Charles already created it. > > https://bugs.launchpad.net/starlingx/+bug/1940696 > > Thank you! > > Regards, > Danishka > > On Fri, Aug 20, 2021 at 4:26 PM Pratik M. wrote: > >> Hi, >> You would also need to change the tag in >> >> stx-ansible/playbooks/roles/common/armada-helm/templates/armada-overrides.yaml.j2 >> >> On Fri, Aug 20, 2021 at 2:38 PM Pratik M. wrote: >> >>> Hi, >>> This causes the R5.0 install to fail. Pl. raise a bug. >>> >>> You may try changing the tag here: >>> /usr/share/ansible/stx-ansible/playbooks/roles/common/load-images-information/vars/k8s-v1.18.1/system-images.yml >>> >>> >>> I used tiller:v2.16.10 and it went ahead but is now stuck in armada pod >>> restart. >>> >>> BR >>> >>> On Thu, Aug 19, 2021 at 1:52 AM Charles Oluwaseun Oluboyo < >>> charlesboyo at gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I am unable to complete the bootstrap of controller-0 in a Virtual >>>> AIO-DX setup because 'gcr.io/kubernetes-helm/tiller:v2.16.1' no longer >>>> exists. >>>> >>>> Reviewing the image - >>>> https://console.cloud.google.com/gcr/images/kubernetes-helm/global/tiller >>>> - shows that all tags before v2.16.5 are missing (or have been removed). >>>> >>>> Please advise on how I can workaround this. >>>> >>>> Regards, >>>> >>>> Oluwaseun >>>> _______________________________________________ >>>> 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 >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Mon Aug 23 17:35:08 2021 From: openinfradn at gmail.com (open infra) Date: Mon, 23 Aug 2021 23:05:08 +0530 Subject: [Starlingx-discuss] platform-integ-apps stx-rbd-provisioner failed Message-ID: Hi, During the provision of STX release 5 ( standard dedicated storage), I noticed that platform-integ-apps was failed. I have re-apply but failed. [1] This is the first time I have noticed it with release 5. No such failure during the previous deployment. Only changed I did was, updating gcr.io/kubernetes-helm/tiller tag to 16.10. Already configured Ceph storage backend. Both controllers and worker node is labeled as in the installation guide. Ceph health is also ok. [sysadmin at controller-0 ~(keystone_admin)]$ ceph health detail HEALTH_OK Am I missing something? [1] https://paste.opendev.org/show/808244/ Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Mon Aug 23 18:31:15 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 23 Aug 2021 18:31:15 +0000 Subject: [Starlingx-discuss] stx.6.0 Feature Update Requested for MS-2 Message-ID: Hello stx.6.0 Feature Leads, In preparation for the stx.6.0 Milestone-2 review (which we will review in the upcoming Release Meeting on Wednesday August 25), please take the time to update the status of your feature in the release tracking spreadsheet (column V - I've added a prefix: 8/25: ...for each feature). Please also update any changed or missing dates (code merge, feature tested, doc impact, etc.). Feature Tracking spreadsheet: https://docs.google.com/spreadsheets/d/13p0BMlBgJXUVForOFsblAJq9jA1-FMBlmhV5TIc70IE/edit#gid=1107209846 Thanks, Ghada StartlingX Release PL -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Mon Aug 23 19:37:10 2021 From: Robert.Church at windriver.com (Church, Robert) Date: Mon, 23 Aug 2021 19:37:10 +0000 Subject: [Starlingx-discuss] platform-integ-apps stx-rbd-provisioner failed In-Reply-To: References: Message-ID: <8F23D769-F023-4EA5-A4BC-67BCEFFCB0B8@windriver.com> You will need the content from the following commits. https://bugs.launchpad.net/starlingx/+bug/1940696/comments/3 We are going to be doing some testing to make sure that these are the only commits that are needed and then will proceed to cherry-pick these to the r/stx.5.0 branch. At that point we’ll proceed with some formal sanity testing and generating a maintenance release. Bob From: open infra Date: Monday, August 23, 2021 at 12:37 PM To: "'starlingx-discuss at lists.starlingx.io'" Subject: [Starlingx-discuss] platform-integ-apps stx-rbd-provisioner failed [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, During the provision of STX release 5 ( standard dedicated storage), I noticed that platform-integ-apps was failed. I have re-apply but failed. [1] This is the first time I have noticed it with release 5. No such failure during the previous deployment. Only changed I did was, updating gcr.io/kubernetes-helm/tiller tag to 16.10. Already configured Ceph storage backend. Both controllers and worker node is labeled as in the installation guide. Ceph health is also ok. [sysadmin at controller-0 ~(keystone_admin)]$ ceph health detail HEALTH_OK Am I missing something? [1] https://paste.opendev.org/showYOu /808244/ Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Tue Aug 24 04:49:07 2021 From: openinfradn at gmail.com (open infra) Date: Tue, 24 Aug 2021 10:19:07 +0530 Subject: [Starlingx-discuss] platform-integ-apps stx-rbd-provisioner failed In-Reply-To: <8F23D769-F023-4EA5-A4BC-67BCEFFCB0B8@windriver.com> References: <8F23D769-F023-4EA5-A4BC-67BCEFFCB0B8@windriver.com> Message-ID: Hi Robert, I have updated both files manually and tried to apply platform-integ-apps but still fail. On Tue, Aug 24, 2021 at 1:07 AM Church, Robert wrote: > You will need the content from the following commits. > https://bugs.launchpad.net/starlingx/+bug/1940696/comments/3 > > > > We are going to be doing some testing to make sure that these are the only > commits that are needed and then will proceed to cherry-pick these to the > r/stx.5.0 branch. At that point we’ll proceed with some formal sanity > testing and generating a maintenance release. > There is a small typo in the deployment.yml as mentioned in [1]. [1] https://bugs.launchpad.net/starlingx/+bug/1940696/comments/5 Regards, Danishka > > > Bob > > > > *From: *open infra > *Date: *Monday, August 23, 2021 at 12:37 PM > *To: *"'starlingx-discuss at lists.starlingx.io'" < > starlingx-discuss at lists.starlingx.io> > *Subject: *[Starlingx-discuss] platform-integ-apps stx-rbd-provisioner > failed > > > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi, > > > > During the provision of STX release 5 ( standard dedicated storage), I > noticed that platform-integ-apps was failed. I have re-apply but failed. > [1] > > This is the first time I have noticed it with release 5. > > No such failure during the previous deployment. > > > > Only changed I did was, updating gcr.io/kubernetes-helm/tiller > > tag to 16.10. > > > > Already configured Ceph storage backend. > > > > Both controllers and worker node is labeled as in the installation guide. > > Ceph health is also ok. > > > > [sysadmin at controller-0 ~(keystone_admin)]$ ceph health detail > > HEALTH_OK > > > > Am I missing something? > > > > [1] https://paste.opendev.org/showYOu /808244/ > > > > Regards, > > Danishka > -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Tue Aug 24 13:00:59 2021 From: openinfradn at gmail.com (open infra) Date: Tue, 24 Aug 2021 18:30:59 +0530 Subject: [Starlingx-discuss] How to deploy a stable release? Message-ID: Hi, I have deployed STX r5.0 on end of May 2021 but same ISO [1] was used few days ago, but the deployment failed [2]. Is this the same scenario if you install using the same OS image? You can still install and use both Ubuntu 16.04 and Fedora 30 despite missing security updates. You can upgrade the OS step by step if needed. I would like to know the purpose of removing the v2.16.1 tag (mentioned in the [2]) caused bootstrap fail. It would be good if bootimage.iso and playbooks run smoothly, but introduce an additional step to get enhancements/updates in the installation guide. For example, if there is a new tag or configuration changes required, it should be reflected in the installation guide. In a situation where the bootsrap playbook must point to a new container set, a new boot image can be introduced by replacing the previous bootimage.iso. [1] http://mirror.starlingx.cengn.ca/mirror/starlingx/release/latest_release/centos/flock/outputs/iso/ [2] https://bugs.launchpad.net/starlingx/+bug/1940696 [3] https://wiki.openstack.org/wiki/StarlingX/Release_Plan#List_of_Releases Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Tue Aug 24 17:02:50 2021 From: Greg.Waines at windriver.com (Waines, Greg) Date: Tue, 24 Aug 2021 17:02:50 +0000 Subject: [Starlingx-discuss] Download images and push to local registry Failed In-Reply-To: <46e0585b.8faa.17b399328f4.Coremail.captain_tx@163.com> References: <46e0585b.8faa.17b399328f4.Coremail.captain_tx@163.com> Message-ID: hey ... sorry for the slow reply, You're likely having a connectivity or permissions issue with the registry. Best way to debug this is ... after `ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap.yml` fails ... Try to docker login and docker pull manually from the shell of controller-0 e.g. sudo docker pull docker.io/starlingx/k8s-plugins-sriov-network-device:stx.4.0-v3.2-16-g4e0302ae ... I'm assuming you're using docker hub. Greg. From: Captain Sent: Thursday, August 12, 2021 4:56 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Download images and push to local registry Failed [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I deploy starlingx according to the tutorial(https://docs.starlingx.io/r/stx.5.0/deploy_install_guides/r5_release/bare_metal/bootstrapping-from-a-private-docker-registry.html), which is always stuck where the docker image is downloaded.Could you please help me? Thanks. Issues: 1. When I run `ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap.yml`, the task `[common/push-docker-images: Download images and push to local registry]` will always stay here for a long time. Kind regards, Xurong Zhang -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Wed Aug 25 07:25:05 2021 From: openinfradn at gmail.com (open infra) Date: Wed, 25 Aug 2021 12:55:05 +0530 Subject: [Starlingx-discuss] platform-integ-apps stx-rbd-provisioner failed In-Reply-To: <8F23D769-F023-4EA5-A4BC-67BCEFFCB0B8@windriver.com> References: <8F23D769-F023-4EA5-A4BC-67BCEFFCB0B8@windriver.com> Message-ID: How to apply those changes to freshly installed controllers? On Tue, Aug 24, 2021 at 1:07 AM Church, Robert wrote: > You will need the content from the following commits. > https://bugs.launchpad.net/starlingx/+bug/1940696/comments/3 > > > > We are going to be doing some testing to make sure that these are the only > commits that are needed and then will proceed to cherry-pick these to the > r/stx.5.0 branch. At that point we’ll proceed with some formal sanity > testing and generating a maintenance release. > > > > Bob > > > > *From: *open infra > *Date: *Monday, August 23, 2021 at 12:37 PM > *To: *"'starlingx-discuss at lists.starlingx.io'" < > starlingx-discuss at lists.starlingx.io> > *Subject: *[Starlingx-discuss] platform-integ-apps stx-rbd-provisioner > failed > > > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi, > > > > During the provision of STX release 5 ( standard dedicated storage), I > noticed that platform-integ-apps was failed. I have re-apply but failed. > [1] > > This is the first time I have noticed it with release 5. > > No such failure during the previous deployment. > > > > Only changed I did was, updating gcr.io/kubernetes-helm/tiller > > tag to 16.10. > > > > Already configured Ceph storage backend. > > > > Both controllers and worker node is labeled as in the installation guide. > > Ceph health is also ok. > > > > [sysadmin at controller-0 ~(keystone_admin)]$ ceph health detail > > HEALTH_OK > > > > Am I missing something? > > > > [1] https://paste.opendev.org/showYOu /808244/ > > > > Regards, > > Danishka > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Aug 25 13:18:08 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 25 Aug 2021 13:18:08 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Aug 25, 2021) Message-ID: Hi all, reminder of the weekly TSC/Community calls coming up shortly. Please feel free to add other items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210825T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Wed Aug 25 13:56:24 2021 From: Robert.Church at windriver.com (Church, Robert) Date: Wed, 25 Aug 2021 13:56:24 +0000 Subject: [Starlingx-discuss] platform-integ-apps stx-rbd-provisioner failed In-Reply-To: References: <8F23D769-F023-4EA5-A4BC-67BCEFFCB0B8@windriver.com> Message-ID: After installing, prior to running the bootstrap playbook on controller-0: * Make the changes to the ansible playbook in /usr/share/ansible/stx-ansible/playbooks * Update the helm chart in /usr/local/share/applications/helm/platform-integ-apps-*.tgz Then run the playbook Bob From: open infra Date: Wednesday, August 25, 2021 at 2:25 AM To: Robert Church Cc: "'starlingx-discuss at lists.starlingx.io'" Subject: Re: [Starlingx-discuss] platform-integ-apps stx-rbd-provisioner failed [Please note: This e-mail is from an EXTERNAL e-mail address] How to apply those changes to freshly installed controllers? On Tue, Aug 24, 2021 at 1:07 AM Church, Robert > wrote: You will need the content from the following commits. https://bugs.launchpad.net/starlingx/+bug/1940696/comments/3 We are going to be doing some testing to make sure that these are the only commits that are needed and then will proceed to cherry-pick these to the r/stx.5.0 branch. At that point we’ll proceed with some formal sanity testing and generating a maintenance release. Bob From: open infra > Date: Monday, August 23, 2021 at 12:37 PM To: "'starlingx-discuss at lists.starlingx.io'" > Subject: [Starlingx-discuss] platform-integ-apps stx-rbd-provisioner failed [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, During the provision of STX release 5 ( standard dedicated storage), I noticed that platform-integ-apps was failed. I have re-apply but failed. [1] This is the first time I have noticed it with release 5. No such failure during the previous deployment. Only changed I did was, updating gcr.io/kubernetes-helm/tiller tag to 16.10. Already configured Ceph storage backend. Both controllers and worker node is labeled as in the installation guide. Ceph health is also ok. [sysadmin at controller-0 ~(keystone_admin)]$ ceph health detail HEALTH_OK Am I missing something? [1] https://paste.opendev.org/showYOu /808244/ Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Aug 25 14:53:23 2021 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 25 Aug 2021 14:53:23 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Aug 25, 2021) In-Reply-To: References: Message-ID: >From today's meeting: * Standing Topics * Build/Sanity * progress on build with 5.10 kernel * https://bugs.launchpad.net/starlingx/+bug/1938559 * Mark A will check in on next steps re: this bug * no build issues, but no Sanity reports since last Friday (Aug 20) * Bill to ping Nic/Alex re: whether there are any issues preventing Sanity from being run * Gerrit Reviews in Need of Attention * nothing this week * Topics for this Week * Introduction of Test Plan Section in Git Commit Message (Ramaswamy Subramanian) * Proposed Changes: * Wiki: https://wiki.openstack.org/wiki/GitCommitMessages * Starlingx documentation code submissions guide: https://review.opendev.org/c/starlingx/docs/+/805055 * StarlingX Doc preview site: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_597/805055/6/check/openstack-tox-docs/597762a/docs/developer_resources/code-submission-guide.html * stx.5.0 Maintenance Release * due to https://bugs.launchpad.net/starlingx/+bug/1940696/ * see http://lists.starlingx.io/pipermail/starlingx-discuss/2021-August/011932.html * added new checklist item for MS-3 re: Docs / Blog Posts collateral * see https://etherpad.opendev.org/p/stx-releases * ARs from Previous Meetings * CENGN Backups - Anthony continuing to follow up with CENGN * Open Requests for Help * see http://lists.starlingx.io/pipermail/starlingx-discuss/2021-August/011932.html, discussed above From: Zvonar, Bill Sent: Wednesday, August 25, 2021 9:18 AM To: StarlingX ML Subject: Community (& TSC) Call (Aug 25, 2021) Hi all, reminder of the weekly TSC/Community calls coming up shortly. Please feel free to add other items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210825T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Wed Aug 25 15:49:06 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 25 Aug 2021 15:49:06 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210823T230545Z Message-ID: Sanity Test from 2021-August-24 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210823T230545Z/outputs/iso/) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210823T230545Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz All baremetal configurations failed because of: https://bugs.launchpad.net/starlingx/+bug/1938559 Kind Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5155 bytes Desc: image001.png URL: From alexandru.dimofte at intel.com Wed Aug 25 15:50:44 2021 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 25 Aug 2021 15:50:44 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210825T013529Z Message-ID: Sanity Test from 2021-August-25 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210825T013529Z/outputs/iso/) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210825T013529Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz All baremetal configurations failed because of: https://bugs.launchpad.net/starlingx/+bug/1938559 Kind Regards, Alexandru Dimofte [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5155 bytes Desc: image001.png URL: From maryx.camp at intel.com Wed Aug 25 20:15:02 2021 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 25 Aug 2021 20:15:02 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 25-Aug-21 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, Mary Camp ========== 25-Aug-21 All -- reviews merged since last meeting: 7 All -- bug status -- 17 total - team agrees to defer all low priority LP until the upstreaming effort is completed. Status/questions/opens We have noticed duplicate headings on all the STX doc pages, seems like it started in July? Found this WIP review against the openstackdocstheme: https://review.opendev.org/c/openstack/openstackdocstheme/+/798897 Asked when this will be merged, hopefully it fixes our issue. Changing relative paths: We are still using an older version of sphinx for the Wind River internal docs. This is because symlinks are not handled correctly in recent/current versions. We can avoid the errors and move into lockstep with StarlingX by changing some relative paths to avoid '..' (parent dir) notation. Ron is working on this now, using doc labels. Keep an eye out for the incoming review, will be tagged DNM so can be verified with downstream WR builds. We really need to get a handle on what needs to be cherry picked into R5 branch, plus there were a lot of last-minute change to the Install guides that really should be copied into the R6 guides. We agreed that this is a goal. Ideally, the link on main page for R5 installs should/will point to R5 branch of installs << link change Ron will contact Greg to sort out any potential issues for downstream docs, what to cherry pick, when to stop making changes in R5, etc. Retrospective We will discuss in our meeting next week. From build.starlingx at gmail.com Wed Aug 25 20:47:38 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 25 Aug 2021 16:47:38 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_publish - Build # 3189 - Failure! Message-ID: <1907134395.35.1629924460059.JavaMail.javamailuser@localhost> Project: STX_publish Build #: 3189 Status: Failure Timestamp: 20210825T194735Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/compiler/20210825T190223Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-5.0-compiler/20210825T190223Z OS: centos PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/compiler/20210825T190223Z/logs RETRIES: 13 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/5.0/centos/compiler/20210825T190223Z/logs MASTER_JOB_NAME: STX_5.0_build_layer_compiler RETRY_INTERVAL_SEC: 300 MY_REPO_ROOT: /localdisk/designer/jenkins/rc-5.0-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/5.0/centos/compiler TIMESTAMP: 20210825T190223Z PUBLISH_INPUTS_BASE: /export/mirror/starlingx/rc/5.0/centos/compiler/20210825T190223Z/inputs LAYER: compiler PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/5.0/centos/compiler/20210825T190223Z/outputs From build.starlingx at gmail.com Wed Aug 25 20:47:41 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 25 Aug 2021 16:47:41 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.5.0 STX_5.0_build_layer_compiler - Build # 49 - Failure! Message-ID: <1136780847.38.1629924462680.JavaMail.javamailuser@localhost> Project: STX_5.0_build_layer_compiler Build #: 49 Status: Failure Timestamp: 20210825T190223Z Branch: r/stx.5.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/compiler/20210825T190223Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true From ildiko.vancsa at gmail.com Wed Aug 25 23:40:47 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 25 Aug 2021 16:40:47 -0700 Subject: [Starlingx-discuss] Upcoming TSC and PL/TL elections In-Reply-To: References: Message-ID: <2ECDB71D-2A42-4E8F-ADEC-90514C48EAB3@gmail.com> Hi, Based on the discussion on today’s TSC call I created a patch to update the election website with the fall TSC/PL/TL election dates: https://review.opendev.org/c/starlingx/election/+/806059 Please let me know if you have any concerns with those dates here or by leaving a comment on the review. For the TSC elections part we have 3 seats this round that are up for re-election, but we also have two open seats with a 6-month term that we need to fill. We will hold interim elections to attempt to fill these seats. The proposal for the second round of election is to run it right after the regular fall election round. In that sense the dates for the interim election would be: * Interim TSC Nominations: November 16, 2021, 20:45 UTC - November 23, 2021, 20:45 UTC * Interim TSC Campaign: November 23, 2021, 20:45 UTC - November 30, 2021, 20:45 UTC * Interim TSC Election: November 30, 2021, 20:45 UTC - December 07, 2021, 20:45 UTC Would that work for the community? Thanks, Ildikó > On Aug 18, 2021, at 07:45, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > It is a friendly reminder that the time for the fall election[1] period is coming up fast and therefore we need to start planning the process. > > We need to decide on timeframe for the elections. For TSC we have a nomination, a campaign and a voting period, while for PL/TL elections we have a nomination and a voting period defined officially. > > We are looking for a 3-week timeframe in the fall that doesn’t collide with any major holidays or milestones in the release process. > > > We also plan to run an interim TSC election period this time around as we have 5 seats for the TSC and the terms of the current 3 members are up[2] in H2, 2021. We will run the regular election period to (re)elect these positions and we will also run an interim election to fill the remaining 2 seats for a half year period to grow the group back to the desired number and to support the staggered election process. The interim elections need separate dates to avoid confusions with the regular process. > > Please think about your preference about the election process to make sure that people are available to submit nominations as well as to be able to vote in the election process. > > If you have any questions or comments please reply to this thread or reach out to the election officials[3]. > > Thanks, > > [1] https://docs.starlingx.io/election/ > [2] https://docs.starlingx.io/governance/reference/tsc/index.html > [3] https://docs.starlingx.io/election/#election-officials > > From Ghada.Khalil at windriver.com Wed Aug 25 23:40:52 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 25 Aug 2021 23:40:52 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Aug 25/2021 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.6.0 - References: - Release Planning Spreadsheet: https://docs.google.com/spreadsheets/d/13p0BMlBgJXUVForOFsblAJq9jA1-FMBlmhV5TIc70IE/edit#gid=1107209846 - Test Planning: https://drive.google.com/drive/folders/1lfm073XaFGxHZSAf0RPS1DGK6QCReO9u - MS-2 is planned for this week - Everything looks in order to declare the milestone as per plan. Details are below. - Agreed to declare MS2 this week based on review on the info below. - Feature Planning - Latest Code Merged Date is: Oct 28 (excluding prep features) / Planned MS3 Date: Oct 4 - 6 features out of 16 have a Code Merge date > Oct 4 (i.e. 38% of features) - Proposal: Move the MS3 Date to Oct 28 to reflect the actual feature plans - Proposal Accepted - Latest Feature Tested Date is: Dec 9 for DC Scaling & Nov 23 for others / Planned Feature Tested MS (MS3+2wks): Oct 18 - Proposal: - Consider DC Scaling Feature Test as an exception; testing is ongoing from now. - Adjust Feature Test Complete to Nov 22 to reflect the actual feature plans. - As per Michiel Seuren (Test PL), these are the dates that the team can meet. - Proposal Accepted. Note: The scaling is a target and will not hold up the stx release - Note: Even based on the latest Code Merged Date, the Feature Tested Dates are more than 2wks beyond that date. - Proposal: Consider expanding that duration when planning for stx.7.0 from 2wks to 4wks to better align w/ historic release data. - Release Regression - Key Dates for MS-2: - Regression Start: Plan: Oct 25 / Forecast: same - Regression Complete: Plan: Nov 15 / Forecast: same - From Michiel - plan is to continue with the above Regression Test Dates. This will allow us to keep the current YE Release Date for stx.6.0 - Note: Regression and Feature Test will overlap - Regression will be executed by both the WR and Intel teams - Alex (Intel) indicated that they are pulling in resources from China to help with the regression testing. They are also migrating their Robot regression tests to Pytest (less than half done). - Intel's goal is also to go back to running sanity daily instead of one configuration/day. - Blog Posts / Doc Collateral - Agreed to add as a checklist item for MS-3 - Responsibility is with the Feature PLs to make a recommendation whether their feature warrants a blog post and provide the material - Status: Complete. https://wiki.openstack.org/wiki/StarlingX/Release_Plan#Release_Milestones updated stx.5.0 - Maintenance Release is needed due to https://bugs.launchpad.net/starlingx/+bug/1940696/ - Required fixes are posted in r/stx.5.0 for review - https://review.opendev.org/c/starlingx/platform-armada-app/+/805812 - https://review.opendev.org/c/starlingx/ansible-playbooks/+/805813 - Build team is on standby to start the build process once the above changes are merged. From ildiko.vancsa at gmail.com Wed Aug 25 23:49:57 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 25 Aug 2021 16:49:57 -0700 Subject: [Starlingx-discuss] Updating active contributors in projects.yaml - ACTION NEEDED Message-ID: <43DCBA53-DE60-43CA-8828-9CBD081266F5@gmail.com> Hi, We have a list of active contributors maintained in the projects.yaml file in the governance repository to list those contributors who are not identified through querying Git already. Currently we use this list when we pull the electorate list for elections and therefore it is very important to keep that list up to date to make sure the scripts work correctly. I just recognized that the term expired last November for contributors currently listed and therefore we need to update the list to capture those who are still actively contributing, but can’t be identified through our semi-automated process. You can see the lists maintained for each project here: https://opendev.org/starlingx/governance/src/branch/master/reference/tsc/projects.yaml I would like to ask the PLs to look into the list of contributors in the file above for their project team(s) and update the list(s): * Add new contributors - ONLY those people who do NOT have any merged patches in a sub-project they are contributing to * Remove contributors who haven’t been active since November, 2020 * Update the term of still active contributors to November, 2022 __Please start updating the list(s) as soon as possible so we can use the data for the upcoming elections.__ Please let me know if you have any questions. Thanks and Best Regards, Ildikó From ildiko.vancsa at gmail.com Thu Aug 26 16:50:11 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 26 Aug 2021 09:50:11 -0700 Subject: [Starlingx-discuss] StarlingX and Tungsten Fabric Message-ID: Hi, I have a quick question. I was chatting with a company yesterday about their edge use case and needs and we touched on StarlingX. They were interested if they could use StarlingX with Tungsten Fabric as SDN controller to provide networking for the platform. Does StarlingX support Tungsten Fabric? And/or has anyone tried to set up the two together already and maybe have some information about the experience? Thanks, Ildikó From build.starlingx at gmail.com Thu Aug 26 18:10:46 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 26 Aug 2021 14:10:46 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_wheels_layered - Build # 165 - Failure! Message-ID: <1645399783.45.1630001448149.JavaMail.javamailuser@localhost> Project: STX_build_wheels_layered Build #: 165 Status: Failure Timestamp: 20210826T175000Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210826T173128Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-5.0-containers/20210826T173128Z OS: centos DOCKER_BUILD_ID: jenkins-rc-5.0-containers-20210826T173128Z-builder MY_REPO: /localdisk/designer/jenkins/rc-5.0-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210826T173128Z/logs OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210826T173128Z/logs From build.starlingx at gmail.com Thu Aug 26 18:10:49 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 26 Aug 2021 14:10:49 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] r/stx.5.0 STX_build_docker_images_layered - Build # 169 - Failure! Message-ID: <2144699176.48.1630001450582.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 169 Status: Failure Timestamp: 20210826T174437Z Branch: r/stx.5.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210826T173128Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: r/stx.5.0 MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-5.0-containers/20210826T173128Z OS: centos MUNGED_BRANCH: rc-5.0 MY_REPO: /localdisk/designer/jenkins/rc-5.0-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210826T173128Z/logs MASTER_BUILD_NUMBER: 22 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210826T173128Z/logs MASTER_JOB_NAME: STX_5.0_build_layer_containers MY_REPO_ROOT: /localdisk/designer/jenkins/rc-5.0-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/5.0/centos/containers PUBLISH_TIMESTAMP: 20210826T173128Z DOCKER_BUILD_ID: jenkins-rc-5.0-containers-20210826T173128Z-builder TIMESTAMP: 20210826T173128Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210826T173128Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/5.0/centos/containers/20210826T173128Z/outputs From build.starlingx at gmail.com Thu Aug 26 18:10:52 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 26 Aug 2021 14:10:52 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] r/stx.5.0 STX_5.0_build_layer_containers - Build # 22 - Failure! Message-ID: <701341234.51.1630001452614.JavaMail.javamailuser@localhost> Project: STX_5.0_build_layer_containers Build #: 22 Status: Failure Timestamp: 20210826T173128Z Branch: r/stx.5.0 Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/containers/20210826T173128Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From Matt.Peters at windriver.com Thu Aug 26 21:32:37 2021 From: Matt.Peters at windriver.com (Peters, Matt) Date: Thu, 26 Aug 2021 21:32:37 +0000 Subject: [Starlingx-discuss] StarlingX and Tungsten Fabric In-Reply-To: References: Message-ID: Hi Ildikó, Support for Tungsten Fabric was investigated previously, but it did not proceed beyond that initial investigation. A summary of the findings are attached. It isn't very detailed, so I'm not sure it will be of great help, but figured I would share what I had on this topic. Regards, Matt -----Original Message----- From: Ildiko Vancsa Sent: Thursday, August 26, 2021 12:50 PM To: StarlingX ML Subject: [Starlingx-discuss] StarlingX and Tungsten Fabric [Please note: This e-mail is from an EXTERNAL e-mail address] Hi, I have a quick question. I was chatting with a company yesterday about their edge use case and needs and we touched on StarlingX. They were interested if they could use StarlingX with Tungsten Fabric as SDN controller to provide networking for the platform. Does StarlingX support Tungsten Fabric? And/or has anyone tried to set up the two together already and maybe have some information about the experience? Thanks, Ildikó _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- A non-text attachment was scrubbed... Name: StarlingX - Tungsten Fabric.pdf Type: application/pdf Size: 364070 bytes Desc: StarlingX - Tungsten Fabric.pdf URL: From ildiko.vancsa at gmail.com Thu Aug 26 21:37:32 2021 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 26 Aug 2021 14:37:32 -0700 Subject: [Starlingx-discuss] StarlingX and Tungsten Fabric In-Reply-To: References: Message-ID: Hi Matt, No worries, I appreciate all the info. Thank you for sharing! Best Regards, Ildikó > On Aug 26, 2021, at 14:32, Peters, Matt wrote: > > Hi Ildikó, > Support for Tungsten Fabric was investigated previously, but it did not proceed beyond that initial investigation. A summary of the findings are attached. It isn't very detailed, so I'm not sure it will be of great help, but figured I would share what I had on this topic. > > Regards, Matt > > -----Original Message----- > From: Ildiko Vancsa > Sent: Thursday, August 26, 2021 12:50 PM > To: StarlingX ML > Subject: [Starlingx-discuss] StarlingX and Tungsten Fabric > > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Hi, > > I have a quick question. > > I was chatting with a company yesterday about their edge use case and needs and we touched on StarlingX. They were interested if they could use StarlingX with Tungsten Fabric as SDN controller to provide networking for the platform. > > Does StarlingX support Tungsten Fabric? And/or has anyone tried to set up the two together already and maybe have some information about the experience? > > Thanks, > Ildikó > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Ghada.Khalil at windriver.com Thu Aug 26 21:55:58 2021 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 26 Aug 2021 21:55:58 +0000 Subject: [Starlingx-discuss] stx.6.0 Milestone-2 Declared Message-ID: Hello all, Based on the stx.6.0 release review on Aug 25/2021, we are declaring Milestone-2. For the detailed minutes, please see the release planning etherpad: https://etherpad.openstack.org/p/stx-releases Milestone-2 Criteria: https://wiki.openstack.org/wiki/StarlingX/Release_Plan#Release_Milestones - Feature plans defined and feature development well underway - Release test plan defined - including test automation deliverables A list of features and plan dates is available at: https://docs.google.com/spreadsheets/d/13p0BMlBgJXUVForOFsblAJq9jA1-FMBlmhV5TIc70IE/edit#gid=1107209846 Thank you to all community members who helped achieve this milestone. Regards, Ghada & the stx release team From build.starlingx at gmail.com Fri Aug 27 04:05:55 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 27 Aug 2021 00:05:55 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_wheels_layered - Build # 166 - Still Failing! In-Reply-To: <2011917191.43.1630001445134.JavaMail.javamailuser@localhost> References: <2011917191.43.1630001445134.JavaMail.javamailuser@localhost> Message-ID: <123277193.54.1630037166308.JavaMail.javamailuser@localhost> Project: STX_build_wheels_layered Build #: 166 Status: Still Failing Timestamp: 20210827T034321Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210827T031507Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210827T031507Z OS: centos DOCKER_BUILD_ID: jenkins-master-containers-20210827T031507Z-builder MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210827T031507Z/logs OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210827T031507Z/logs From build.starlingx at gmail.com Fri Aug 27 04:06:14 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 27 Aug 2021 00:06:14 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 170 - Still Failing! In-Reply-To: <1697570729.46.1630001448805.JavaMail.javamailuser@localhost> References: <1697570729.46.1630001448805.JavaMail.javamailuser@localhost> Message-ID: <60218171.57.1630037176549.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 170 Status: Still Failing Timestamp: 20210827T033537Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210827T031507Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210827T031507Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210827T031507Z/logs MASTER_BUILD_NUMBER: 176 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210827T031507Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210827T031507Z DOCKER_BUILD_ID: jenkins-master-containers-20210827T031507Z-builder TIMESTAMP: 20210827T031507Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210827T031507Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210827T031507Z/outputs From build.starlingx at gmail.com Fri Aug 27 04:06:27 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 27 Aug 2021 00:06:27 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 176 - Failure! Message-ID: <1272654460.60.1630037190772.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 176 Status: Failure Timestamp: 20210827T031507Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210827T031507Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From scott.little at windriver.com Fri Aug 27 13:53:43 2021 From: scott.little at windriver.com (Scott Little) Date: Fri, 27 Aug 2021 09:53:43 -0400 Subject: [Starlingx-discuss] [stable] [build-report] STX_build_wheels_layered - Build # 166 - Still Failing! In-Reply-To: <123277193.54.1630037166308.JavaMail.javamailuser@localhost> References: <2011917191.43.1630001445134.JavaMail.javamailuser@localhost> <123277193.54.1630037166308.JavaMail.javamailuser@localhost> Message-ID: Wheel building is currently broken on package lz4. I appeas to be an upstream change to setuptools Davlet is investigating Scott On 2021-08-27 12:05 a.m., build.starlingx at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_wheels_layered > Build #: 166 > Status: Still Failing > Timestamp: 20210827T034321Z > Branch: > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210827T031507Z/logs > -------------------------------------------------------------------------------- > Parameters > > MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210827T031507Z > OS: centos > DOCKER_BUILD_ID: jenkins-master-containers-20210827T031507Z-builder > MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root > PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210827T031507Z/logs > OS_VERSION: 7.5.1804 > BUILD_STREAM: stable > PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210827T031507Z/logs > > _______________________________________________ > 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 Fri Aug 27 18:29:17 2021 From: scott.little at windriver.com (Scott Little) Date: Fri, 27 Aug 2021 14:29:17 -0400 Subject: [Starlingx-discuss] [stable] [build-report] STX_build_wheels_layered - Build # 166 - Still Failing! In-Reply-To: References: <2011917191.43.1630001445134.JavaMail.javamailuser@localhost> <123277193.54.1630037166308.JavaMail.javamailuser@localhost> Message-ID: <30e1c09c-9ba0-ef70-ad22-b9457a0763ba@windriver.com> The issue has been fixed https://review.opendev.org/c/starlingx/root/+/806425 Thanks Davlet Scott On 2021-08-27 9:53 a.m., Scott Little wrote: > Wheel building is currently broken on package lz4. > > I appeas to be an upstream change to setuptools > > Davlet is investigating > > Scott > > > On 2021-08-27 12:05 a.m., build.starlingx at gmail.com wrote: >> [Please note: This e-mail is from an EXTERNAL e-mail address] >> >> Project: STX_build_wheels_layered >> Build #: 166 >> Status: Still Failing >> Timestamp: 20210827T034321Z >> Branch: >> >> Check logs at: >> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210827T031507Z/logs >> -------------------------------------------------------------------------------- >> Parameters >> >> MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210827T031507Z >> OS: centos >> DOCKER_BUILD_ID: jenkins-master-containers-20210827T031507Z-builder >> MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root >> PUBLISH_LOGS_URL:http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210827T031507Z/logs >> OS_VERSION: 7.5.1804 >> BUILD_STREAM: stable >> PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210827T031507Z/logs >> >> _______________________________________________ >> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Davlet.Panech at windriver.com Fri Aug 27 20:04:14 2021 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Fri, 27 Aug 2021 20:04:14 +0000 Subject: [Starlingx-discuss] StarlingX 5.0.1 RC build ready Message-ID: The 5.0.1 candidate build is available here: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/20210826T162717Z/outputs/iso/ @Dimofte, Alexandru: please proceed with sanity testing. Thank you, D. -------------- next part -------------- An HTML attachment was scrubbed... URL: From john at cplaneai.com Sun Aug 29 17:31:35 2021 From: john at cplaneai.com (John Casey) Date: Sun, 29 Aug 2021 17:31:35 +0000 Subject: [Starlingx-discuss] StarlingX 5.0 installation problem tiller version Message-ID: Hi all - Noob here. Not sure where to post this too. Installation of 5.0 fails because of tiller version out of date - system-images.yml tiller_img: gcr.io/kubernetes-helm/tiller:v2.16.1 fix requires changing to version v2.17.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pvmpublic at gmail.com Mon Aug 30 01:46:02 2021 From: pvmpublic at gmail.com (Pratik M.) Date: Mon, 30 Aug 2021 07:16:02 +0530 Subject: [Starlingx-discuss] StarlingX 5.0 installation problem tiller version In-Reply-To: References: Message-ID: Hi John, Pl. use the 5.0.1 ISO, which should have a fix. Or see this for a workaround: http://lists.starlingx.io/pipermail/starlingx-discuss/2021-August/011927.html BR On Mon, Aug 30, 2021, 00:05 John Casey wrote: > Hi all – > > > > Noob here. Not sure where to post this too. > > > > Installation of 5.0 fails because of tiller version out of date – > system-images.yml > > tiller_img: gcr.io/kubernetes-helm/tiller:v2.16.1 > > > > fix requires changing to version v2.17.0 > > > > > > > _______________________________________________ > 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 austin.sun at intel.com Mon Aug 30 01:56:26 2021 From: austin.sun at intel.com (Sun, Austin) Date: Mon, 30 Aug 2021 01:56:26 +0000 Subject: [Starlingx-discuss] Cancel StarlingX Distro-OpenStack: Bi-weekly Project Meeting -- 08/31 Message-ID: Hi All: Cancel 08/31 openstack distro meeting due to personal affairs as no new bug and other topic. Thanks. BR Austin Sun -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Mon Aug 30 01:55:43 2021 From: austin.sun at intel.com (Sun, Austin) Date: Mon, 30 Aug 2021 01:55:43 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Distro-OpenStack: Bi-weekly Project Meeting(Summer Time) Message-ID: Hi folks, This is a new series of bi-weekly project meeting on StarlingX Distro-OpenStack. Your participation to this meeting and/or other offline contribution by all means are highly appreciated! Project Team Etherpad: https://etherpad.openstack.org/p/stx-distro-openstack-meetings The Summer Time Slot for this meeting : CST: 9:00 PM (China, Shanghai ) PST: 7:00 AM (US West , US, Oregon) EST: 9:00 AM (East Canada , Canada Ottawa) Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3785 bytes Desc: not available URL: From captain_tx at 163.com Mon Aug 30 08:11:45 2021 From: captain_tx at 163.com (Captain) Date: Mon, 30 Aug 2021 16:11:45 +0800 (CST) Subject: [Starlingx-discuss] bootstrap/bringup-bootstrap-applications : Upload and apply applications Message-ID: <33a973ac.6c18.17b961d4247.Coremail.captain_tx@163.com> Hi, I deploy starlingx according to the tutorial(https://docs.starlingx.io/r/stx.5.0/deploy_install_guides/r5_release/bare_metal/bootstrapping-from-a-private-docker-registry.html). I'm always stuck in the following step: task [bootstrap/bringup-bootstrap-applications : Wait until application is in the applied state] failed. Could you please help me? Thanks. Steps: 1. Bare metal All-in-oneDuplex Installation R5.0 2. Configure IP connectivity 3. I setup a private HUAWEI Docker registry to use for bootstrapping. ( reference: http://lists.starlingx.io/pipermail/starlingx-discuss/2021-April/011249.html ) 4. ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap.yml The following error occurred during step 4. Issues: TASK [bootstrap/bringup-bootstrap-applications : Upload and apply applications] ******************************************************************************************************************** included: /usr/share/ansible/stx-ansible/playbooks/roles/bootstrap/bringup-bootstrap-applications/tasks/upload_and_apply_application.yml for localhost => (item={'/usr/local/share/applications/helm/nginx-ingress-controller-1.1-15.tgz': None}) included: /usr/share/ansible/stx-ansible/playbooks/roles/bootstrap/bringup-bootstrap-applications/tasks/upload_and_apply_application.yml for localhost => (item={'/usr/local/share/applications/helm/cert-manager-1.0-15.tgz': None}) TASK [bootstrap/bringup-bootstrap-applications : Wait until application is in the uploaded state] ************************************************************************************************** FAILED - RETRYING: Wait until application is in the uploaded state (3 retries left).changed: [localhost] TASK [bootstrap/bringup-bootstrap-applications : Wait until application is in the applied state] *************************************************************************************************** FAILED - RETRYING: Wait until application is in the applied state (30 retries left). FAILED - RETRYING: Wait until application is in the applied state (29 retries left). FAILED - RETRYING: Wait until application is in the applied state (28 retries left). When I checked the ansible playbook, I found an error in "upload and apply applications]". Nginx ingress controller is always created unsuccessfully, which shows that the image pulling fails. Is this a network problem and how to solve it? Kind regards, Xurong Zhang -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Mon Aug 30 17:12:10 2021 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Mon, 30 Aug 2021 17:12:10 +0000 Subject: [Starlingx-discuss] Validation delays Message-ID: Hi All, In the next two weeks, the validation reports might encounter delays because Alex is on vacation. Also, there are some issues with the validation setups. I will try to provide reports for Standard bare-metal setup after we solve the infrastructure problems. Regards, Nicolae Jascanu, Ph.D. Software Engineer INTEL IOTG Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Mon Aug 30 18:19:13 2021 From: scott.little at windriver.com (Scott Little) Date: Mon, 30 Aug 2021 14:19:13 -0400 Subject: [Starlingx-discuss] mirror.starlingx.cengn.ca is currently having issues Message-ID: I have reported the outage to CENGN. They estimate 30 min to restore service. So ~2:45 pm EST Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Aug 31 01:17:23 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 30 Aug 2021 21:17:23 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_base_image - Build # 478 - Failure! Message-ID: <2026372530.66.1630372647120.JavaMail.javamailuser@localhost> Project: STX_build_docker_base_image Build #: 478 Status: Failure Timestamp: 20210831T010727Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210831T001651Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210831T001651Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20210831T001651Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210831T001651Z/logs REGISTRY_USERID: slittlewrs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210831T001651Z/logs WEB_HOST_PORT: 80 OS_VERSION: 7.5.1804 BUILD_STREAM: stable REGISTRY_ORG: starlingx BASE_LATEST_TAG: master-stable-latest PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210831T001651Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210831T001651Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Tue Aug 31 01:17:28 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 30 Aug 2021 21:17:28 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 172 - Failure! Message-ID: <804308219.69.1630372649407.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 172 Status: Failure Timestamp: 20210831T010727Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210831T001651Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210831T001651Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210831T001651Z/logs MASTER_BUILD_NUMBER: 178 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210831T001651Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210831T001651Z DOCKER_BUILD_ID: jenkins-master-containers-20210831T001651Z-builder TIMESTAMP: 20210831T001651Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210831T001651Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210831T001651Z/outputs From build.starlingx at gmail.com Tue Aug 31 01:17:30 2021 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 30 Aug 2021 21:17:30 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 178 - Failure! Message-ID: <1683152744.72.1630372651397.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 178 Status: Failure Timestamp: 20210831T001651Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210831T001651Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From openinfradn at gmail.com Tue Aug 31 03:35:52 2021 From: openinfradn at gmail.com (open infra) Date: Tue, 31 Aug 2021 09:05:52 +0530 Subject: [Starlingx-discuss] mirror.starlingx.cengn.ca is currently having issues In-Reply-To: References: Message-ID: Can't we use sf.net and ibiblio.org as alternative? On Mon, Aug 30, 2021 at 11:54 PM Scott Little wrote: > I have reported the outage to CENGN. They estimate 30 min to restore > service. So ~2:45 pm EST > > Scott > > _______________________________________________ > 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 Tue Aug 31 13:20:59 2021 From: scott.little at windriver.com (Scott Little) Date: Tue, 31 Aug 2021 09:20:59 -0400 Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 178 - Failure! In-Reply-To: <1683152744.72.1630372651397.JavaMail.javamailuser@localhost> References: <1683152744.72.1630372651397.JavaMail.javamailuser@localhost> Message-ID: <7efa3a84-2c66-7461-a628-508bfdee684d@windriver.com> Build failed due to the outage of mirror.starlingx.cengn.ca Service has been restored to mirror.starlingx.cengn.ca based on a temporary fix. When the root cause has been identified, a second outage will likely be required to implement the proper fix.  CENGN apologizes for the disruption. Scott On 2021-08-30 9:17 p.m., build.starlingx at gmail.com wrote: > [Please note: This e-mail is from an EXTERNAL e-mail address] > > Project: STX_build_layer_containers_master_master > Build #: 178 > Status: Failure > Timestamp: 20210831T001651Z > Branch: master > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20210831T001651Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: true > FORCE_BUILD: false > > _______________________________________________ > 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: