From Ian.Jolliffe at windriver.com Sun Mar 1 19:03:06 2020 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Sun, 1 Mar 2020 19:03:06 +0000 Subject: [Starlingx-discuss] [TSC] Minutes 2/26 and F2F agenda Message-ID: <8D268759-0C79-436B-914F-2661B46294F5@windriver.com> Hi all; We spent most of the time on the agenda for the F2F meeting in Chandler. There is a zoom meeting available for those who want to join remotely. Zoom link: https://zoom.us/j/8341652381 I have spent some time updating the etherpad to organize topics across the 2 days. We will do our best to keep to the agenda. https://etherpad.openstack.org/p/starlingX-winter-2020-meetup Regards; Ian -------------- next part -------------- An HTML attachment was scrubbed... URL: From litao7050 at fiberhome.com Mon Mar 2 09:05:44 2020 From: litao7050 at fiberhome.com (=?UTF-8?B?5p2O5rab?=) Date: Mon, 2 Mar 2020 17:05:44 +0800 Subject: [Starlingx-discuss] Configuring Openstack SSL Certificates In-Reply-To: <77a14c79-b890-8e78-3584-261e9d4a46be@windriver.com> References: <77a14c79-b890-8e78-3584-261e9d4a46be@windriver.com> Message-ID: <60bbc9a4-3a67-4c1e-6c6a-973a8a8e3b2a@fiberhome.com> Hi Andy, Currently, I configured the https for containerized openstack. As what you said, "system certificate-install -m ssl " will enable both them, I found Openstack Horizon and Openstack APIs don't work  by your method, so do you have more detailed document to help me? And what are the meanings for mode 'openstack' and 'openstack_ca'  in 'system certificate-install -m ' command. I am a little confused,please provide more details in which scene to use these two modes. Tao Li Thanks 在 2019/12/18 22:43, Andy Ning 写道: > > > > On 2019-12-18 09:32 AM, Austin Gillmann wrote: >> Bumping this again; if this is unsupported do let me know. >> >> Thanks! >> Austin Gillmann >> >> On Fri, Dec 6, 2019 at 8:31 PM Austin Gillmann > > wrote: >> >> Hello all, >> >> First off thank you Robert and Martin for the assistance re: my >> question about enabling swift. I found about the helm chart overrides >> on my own but forgot about the extra service. >> >> I since successfully deployed and all is working as intended, one >> minor question is how would I go about adding ssl certificates to the >> Openstack API's and Horizon. I found a stub page relating to it, but >> no other references except for stx-config docs that may just be for >> platform services. >> > > I believe that "system certificate-install -m ssl " will > enable both platform as well as containerized openstack APIs and > Horizon with that certificate. The openstack APIs and Horizon would > then be accessible by https://:443 > > Andy > >> Do let me know and thanks again; have a great weekend everyone! >> -Austin Gillmann >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > -- > Andy Ning > Cube: 3071 > Tel: 613-9631408 (int: 4408) > Skype: andy.ning.wr > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- 李涛 烽火通信科技股份有限公司 Wuhan FiberHome Information Integration Technologies Co., Ltd. 云计算研发中心 Tel: +18091818853 Email: litao7050 at fiberhome.com Address:西安市雁塔区团结南路中晶科技广场A座8层 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Mon Mar 2 15:41:04 2020 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 2 Mar 2020 07:41:04 -0800 Subject: [Starlingx-discuss] Multiple GCC support for 4.18 kernel in Master In-Reply-To: <9700A18779F35F49AF027300A49E7C766395FE19@SHSMSX104.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C766395FE19@SHSMSX104.ccr.corp.intel.com> Message-ID: <5d549501-7ae7-5ab2-91b9-fce6c184e737@linux.intel.com> Scott, Don: Not sure if you saw this email? Can you guys take a look and comment on if there is a solution to providing 2 different GCC versions? Thanks Sau! -------- Forwarded Message -------- Subject: Re: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 2/12/2020 Date: Thu, 13 Feb 2020 12:04:48 +0000 From: Lin, Shuicheng To: Sun, Austin , 'starlingx-discuss at lists.starlingx.io' Hi BUILD team and all, In yesterday's meeting, we prefer to build CentOS 8 kernel with gcc-8.2.1, while keep other packages with gcc-4.8.5. But current build system doesn't support gcc switch during package build. First, gcc is a base package defined in mock config, and gcc with latest version(8.2.1) will be auto installed to mock environment when mock init, before any package building. This will lead to all packages build with gcc-8.2.1. Another problem is, mock environment is reused for all packages build. There is no mock environment clean between packages build. To support different packages with different gcc, we need have two mock environment with different gcc version, and accept build for corresponding packages build only. It will be a big change for current build system. Do you know how could we handle the case better? Base on upper problem, I prefer to go with option 2, gcc-4.8.5 for CentOS 8 kernel and other CentOS 7 packages. GCC upgrade will be done later along with CentOS 8 base OS packages upgrade. Please share me your suggestion. Thanks. Best Regards Shuicheng -----Original Message----- From: Sun, Austin Sent: Wednesday, February 12, 2020 11:08 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 2/12/2020 Hi All: Thanks join the call. MoM for 2/12 meeting: - Ceph containerization status and comments address (Martin) http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007731.html [1] rook is integrating into application-app currently , if use remove/delete platform-application, ceph-cluster will be destory. this is admin choose if they want to do it. [2] only will consolated app (sysinv or rook) to controller ceph to discuss further in maillist. - Pbr update ( JITStack-Wesley) build-time issue address http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007676.html , Wesley will update result by End of Week to maillist. reply the email and do an exmplaination - CentOS8 update ( Austin/Shuicheng) Strategy discuss 1) kernel 4.18 uprade only , which new gcc 8.2 is using new gcc will cause compile el7 rpms failure. 2) use old gcc(4.x) to compile new kernel + master rpms 3) mixing gcc using (kernel will use new gcc , and other use old gcc) , -- prefer this way , but current mock does not support 2 gcc co-worker. work item update kernel-rt. use kernel 4.18.x.147 , std and rt which is using centos8.1, as much as using current rpm. kubeadm (kube-proxy) issue update. keep legacy mode binary in iptables. drbd8 --- fix compile issues, and worked. puppet 4.8 w/ ruby 2.5 --worked , send result python2/python3 bring python3 to master , and start python2to3 converting for example nfv. Opens - Vista Creek (FPGA card) support still need confirm i40e drivers New OPEA driver will be released by end of this week. SRIOV device plugin https://github.com/intel/sriov-network-device-plugin/pull/196 -Open Thanks. BR Austin Sun. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Frank.Miller at windriver.com Mon Mar 2 16:17:18 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 2 Mar 2020 16:17:18 +0000 Subject: [Starlingx-discuss] StarlingX Containerization meeting cancelled for March 3rd Message-ID: Due to the meetup occurring this week, I will cancel the weekly containerization meeting scheduled for Tuesday March 3rd. The next meeting will be on St. Patrick's Day March 17th. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Mon Mar 2 16:56:52 2020 From: scott.little at windriver.com (Scott Little) Date: Mon, 2 Mar 2020 11:56:52 -0500 Subject: [Starlingx-discuss] Multiple GCC support for 4.18 kernel in Master In-Reply-To: <5d549501-7ae7-5ab2-91b9-fce6c184e737@linux.intel.com> References: <9700A18779F35F49AF027300A49E7C766395FE19@SHSMSX104.ccr.corp.intel.com> <5d549501-7ae7-5ab2-91b9-fce6c184e737@linux.intel.com> Message-ID: I did reply to another thread on the same subject. In short ... The only way to make this work is to place the kernel and out-of-tree kernel modules into a layer of their own. Scott On 2020-03-02 10:41 a.m., Saul Wold wrote: > > Scott, Don: > > Not sure if you saw this email?  Can you guys take a look and comment > on if there is a solution to providing 2 different GCC versions? > > Thanks >    Sau! > > > > -------- Forwarded Message -------- > Subject: Re: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack > distro meeting, 2/12/2020 > Date: Thu, 13 Feb 2020 12:04:48 +0000 > From: Lin, Shuicheng > To: Sun, Austin , > 'starlingx-discuss at lists.starlingx.io' > > > Hi BUILD team and all, > In yesterday's meeting, we prefer to build CentOS 8 kernel with > gcc-8.2.1, while keep other packages with gcc-4.8.5. > But current build system doesn't support gcc switch during package build. > First, gcc is a base package defined in mock config, and gcc with > latest version(8.2.1) will be auto installed to mock environment when > mock init, before any package building. > This will lead to all packages build with gcc-8.2.1. > Another problem is, mock environment is reused for all packages build. > There is no mock environment clean between packages build. To support > different packages with different gcc, we need have two mock > environment with different gcc version, and accept build for > corresponding packages build only. > It will be a big change for current build system. > Do you know how could we handle the case better? > > Base on upper problem, I prefer to go with option 2, gcc-4.8.5 for > CentOS 8 kernel and other CentOS 7 packages. > GCC upgrade will be done later along with CentOS 8 base OS packages > upgrade.  Please share me your suggestion. > Thanks. > > Best Regards > Shuicheng > > -----Original Message----- > From: Sun, Austin Sent: Wednesday, February 12, > 2020 11:08 PM > To: 'starlingx-discuss at lists.starlingx.io' > > Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack > distro meeting, 2/12/2020 > > Hi All: >   Thanks join the call. MoM for 2/12 meeting: >     -  Ceph containerization status and comments address (Martin) > http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007731.html > >        [1]  rook is integrating into application-app currently , if > use remove/delete platform-application, ceph-cluster will be destory. > this is admin choose if they want to do it.        [2] only will > consolated app (sysinv or rook) to controller ceph  to discuss further > in maillist.     -  Pbr update      ( JITStack-Wesley) >       build-time issue address > http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007676.html > , Wesley will update result by End of Week to maillist. reply the > email and do an exmplaination     - CentOS8  update ( > Austin/Shuicheng)       Strategy discuss                 1) kernel > 4.18 uprade only , which new gcc 8.2 is using   new gcc will cause > compile el7 rpms failure.                  2) use old gcc(4.x) to > compile new kernel + master rpms                 3) mixing gcc using > (kernel will use new gcc , and other use old gcc)  ,  -- prefer this > way , but current mock does not support 2 gcc > co-worker.                  work item update kernel-rt.  use kernel > 4.18.x.147 ,  std and rt which is using centos8.1, as much as using > current rpm.        kubeadm (kube-proxy) issue update. keep legacy > mode binary in iptables.        drbd8  --- fix compile issues,  and > worked.       puppet 4.8 w/ ruby 2.5 --worked , send result        > python2/python3  bring python3 to master , and start python2to3 > converting for example nfv.  Opens    -  Vista Creek (FPGA card) > support          still need confirm i40e drivers          New OPEA > driver will be released by end of this week.          SRIOV device > plugin https://github.com/intel/sriov-network-device-plugin/pull/196 >    -Open > > Thanks. > BR > Austin Sun. _______________________________________________ > 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 Ghada.Khalil at windriver.com Mon Mar 2 17:08:26 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 2 Mar 2020 17:08:26 +0000 Subject: [Starlingx-discuss] FW: stx.4.0 Release Planning -- Action Required: Feature Primes to update plans In-Reply-To: <151EE31B9FCCA54397A757BC674650F0C1673D71@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0C1673D71@ALA-MBD.corp.ad.wrs.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0C1687049@ALA-MBD.corp.ad.wrs.com> Reminder to PLs / Feature Primes to update their feature dates: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=1107209846 Work Sheet: Release Candidates Thanks, Ghada -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, February 19, 2020 8:55 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] FW: stx.4.0 Release Planning -- Action Required: Feature Primes to update plans Re-sending as the original message was moderated with "Too many recipients to the message". -----Original Message----- From: Khalil, Ghada Sent: Wednesday, February 19, 2020 8:45 PM To: Sun, Austin; Miller, Frank; Khalil, Ghada; 'Hu, Yong'; 张鲲鹏; Eslimi, Dariush; 'Saul Wold' Cc: 'Jones, Bruce E'; Zvonar, Bill; starlingx-discuss at lists.starlingx.io Subject: stx.4.0 Release Planning -- Action Required: Feature Primes to update plans Hello stx.4.0 feature primes, In preparation of the mid-cycle StarlingX meeting in early March and the upcoming stx.4.0 Milestone-2 (planned for March 27), I'd like to ask each feature prime to update their Feature Dates by Feb 26 in: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=110720984 Work Sheet: Release Candidates Please update the following columns with your plan dates: - Column I: Plan Available. This is especially important if you don't have planned dates for the subsequent milestones. - Column L: Spec Approved or mark as N/A if no spec is planned - Column O: Code merged in master Please also update Column G (Green, Yellow, Red) w/ Risk. Please use Column V for comments. For more details on each field, see the "Field Definitions" tab in the spreadsheet. If you need any help, please feel free to reach out to me, Bruce or Bill. For reference: Milestone-2 Criteria: https://wiki.openstack.org/wiki/StarlingX/Release_Plan#Release_Milestones - Spec freeze; no new specs accepted for the release. The focus is on closing current specs - Feature plans defined and feature development well underway - Release test plan defined - including test automation deliverables Thanks, Ghada _______________________________________________ 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 Mon Mar 2 18:32:48 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 2 Mar 2020 18:32:48 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Feb 27/2020 Message-ID: <151EE31B9FCCA54397A757BC674650F0C168709C@ALA-MBD.corp.ad.wrs.com> Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Test Team Update - Team in Europe is ramping up - First task is to convert the robot sanity test into the pyTest - 30 TCs converted so far - Still working on re-factoring code - Yang can help answer questions about pytest - Nick's team is also visiting Ada's team for training and ramp up activities - Waiting for hardware - Currently testing on two virtual environments - No ETA for when this hardware will arrive. Expect to have an ETA for some of the equipment by EOW. - Bruce expects another 4-6 weeks until there is a fully equipped hardware lab - This would put this to the middle of April - Current start for Release Regression is end of April, so this is a bit tight. - This also pauses a risk for Feature Testing (done by the test team). - Expect to be able to use Ada's team hardware for another 3 weeks - Weekly test meetings are due to start the week of March 9. stx.4.0 - Unassigned Documentation Tasks - per Kristal's update on Feb 19 Community Call - Kris: unassigned documentation tasks for r4 features - AR: Bill will add these to the agenda for the release team meeting... - Starlingx/integ - https://storyboard.openstack.org/#!/story/2006711 >> Teresa Ho - https://storyboard.openstack.org/#!/story/2006740 >> Vinay V - https://storyboard.openstack.org/#!/story/2005496 >> this is no longer part of stx.4.0. Left unasigned. - https://storyboard.openstack.org/#!/story/2006588 >> should be: Tao Liu / Dariush to confirm - Starlingx/config - https://storyboard.openstack.org/#!/story/2006781 >> should be: Angie Wang / Dariush to confirm - https://storyboard.openstack.org/#!/story/2006770 >> Frank to assign - https://storyboard.openstack.org/#!/story/2006145 >> Shuicheng Lin - https://storyboard.openstack.org/#!/story/2006746 >> Yong to assign - Unit Tests & Functional (API) Tests - Story Board: https://storyboard.openstack.org/#!/story/2007082 - A number of reviews are still open: - https://review.opendev.org/#/c/702597/ - https://review.opendev.org/#/c/702372/ - https://review.opendev.org/#/c/703031/ - https://review.opendev.org/#/c/703010/ - https://review.opendev.org/#/c/702823/ - https://review.opendev.org/#/c/703020/ - Bruce talked to Yong to make progress on these, but his resourcing is limited at this time. Commitments for CentOS8, Ceph, ..etc are higher priority. - There are also a large number of tasks still to do. How do we keep the momentum going? - Feature Planning - https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 - Most plans are still not updated. Ghada to send a reminder to the PLs / Feature Prime - Kata Containers - Main functionality merged. - Remaining items: - switch armada to run with containerd - Document for config and usage (needs to be done in stx4.0) - IPv6 >> this went into Kata master, but isn't in the release that StarlingX is using - Current proposal is to delay the ream until stx.5.0 as Shuicheng is focused on CentOS8 now. - No feature testing done -- only testing by the developer - Open Bugs - https://bugs.launchpad.net/starlingx/+bug/1864383 - https://bugs.launchpad.net/starlingx/+bug/1864382 - https://bugs.launchpad.net/starlingx/+bug/1864372 - Action: Bruce to follow up with Yong on the plan to complete the kata work - Layered Build - Sanity is reporting issues in some labs; still unclear what the root-cause is. Scott is trying to reproduce. - https://bugs.launchpad.net/starlingx/+bug/1864221 - If the issue cannot be reproduced in WR, we need to dig into what is different about the Intel env. From maria.g.perez.ibarra at intel.com Tue Mar 3 01:16:35 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 3 Mar 2020 01:16:35 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200302 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-02 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Mar 3 02:09:04 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 3 Mar 2020 02:09:04 +0000 Subject: [Starlingx-discuss] Canceled Weekly StarlingX non-OpenStack distro meeting, 3/4/2020 Message-ID: Cancel 3/04/2020 meeting as meetup. Thanks. BR Austin Sun. From mingyuan.qi at intel.com Tue Mar 3 05:53:06 2020 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Tue, 3 Mar 2020 05:53:06 +0000 Subject: [Starlingx-discuss] [docs]Provide doc input for 2006781 In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1C15B4C@ALA-MBD.corp.ad.wrs.com> References: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1C15B4C@ALA-MBD.corp.ad.wrs.com> Message-ID: Thanks Bart, all clear. Mingyuan From: Wensley, Barton Sent: Friday, February 28, 2020 22:25 To: Qi, Mingyuan ; Wang, Jing (Angie) ; starlingx-discuss at lists.starlingx.io Cc: Dale, Kristal Subject: RE: [docs]Provide doc input for 2006781 Good questions Mingyuan. Since I did the original design for k8s upgrades I'll reply to your questions (see below). Bart From: Qi, Mingyuan [mailto:mingyuan.qi at intel.com] Sent: February 28, 2020 5:01 AM To: Wang, Jing (Angie); starlingx-discuss at lists.starlingx.io Cc: Dale, Kristal Subject: Re: [Starlingx-discuss] [docs]Provide doc input for 2006781 Hi Angie, The feature looks great that we can now upgrade the k8s cluster at runtime. Regarding the details, I and other folks have several questions that we didn't find clues in the doc. Could you please give us the info from designer's view? * Why the upgrade complete cmd line needed? Any essential checks? [Bart] This command does a final check to verify that all the k8s components are now running the new release and then updates the state to upgrade-complete. * If the first master node upgrade completed on the active controller, that means the active control plane is upgraded to the new version. Then how to ensure the compatibility between upgraded controller plane and un-upgraded kubelet before step 12? [Bart] The k8s version skew policy (https://kubernetes.io/docs/setup/release/version-skew-policy) specifies that the kubelet may be up to two minor versions older than the kube-apiserver. Any k8s upgrades done to StarlingX deployments must respect those rules. * What will happen if some nodes restart unexpectedly between step 11 and 12? [Bart] The kubelet on the node that restarts would come up running the new version, but would be reading the old format of the kubelet config file. This should be supported (new values in the config file will be defaulted). The user can still run the kube-host-upgrade command after this to upgrade the kubelet config file. * How to deal with the certificates and keys of Kubernetes during upgrading? [Bart] As mentioned in the spec (https://docs.starlingx.io/specs/specs/stx-4.0/approved/containerization-2006781-kubernetes-upgrades.html), we are using the kubeadm command to perform the upgrade. It will take care of anything certificate and key related. * Is upgrade rollback supported regardless the upgrade completion? [Bart] There is no support for rollback. I'm not sure if we will add this in the future - the general consensus in the k8s community is that k8s downgrades are not supported. * Is kubelet/kubectl patch marked as in-service patch or reboot-required patch? [Bart] It is an in-service patch. * Why lock/unlock is needed to upgrade kubelet? Is there a way to avoid that? Since this will impact the running pods on all nodes. [Bart] It is not safe to upgrade the kubelet while there are pods running on the node. The lock will move the pods off the node. In the future, when we add orchestration of k8s upgrades (with the VIM), we will likely add support to move the pods off the node without locking it, which would avoid the reboot of the node when the kubelet was upgraded. Thanks, Mingyuan From: Wang, Jing (Angie) > Sent: Thursday, February 27, 2020 23:17 To: starlingx-discuss at lists.starlingx.io Cc: Dale, Kristal > Subject: [Starlingx-discuss] [docs]Provide doc input for 2006781 Hi All, The attached file is the documentation changes required for the story "Kubernetes upgrade support in StarlingX" (https://storyboard.openstack.org/#!/story/2006781). Thanks, Angie -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhaos at neusoft.com Tue Mar 3 06:55:06 2020 From: zhaos at neusoft.com (Shuai) Date: Tue, 3 Mar 2020 14:55:06 +0800 Subject: [Starlingx-discuss] [docs]Regarding the StarlingX Build Guide Message-ID: <001001d5f128$b35f97f0$1a1ec7d0$@neusoft.com> Hi Communityer Regarding the StarlingX Build Guide: When we built the latest version of StarlingX, we found some build guide issues and raised them here.: Guide Path:https://docs.starlingx.io/developer_resources/build_guide.html ★Issues (1). Paragraph: Build the CentOS mirror repository cd $HOME/tools/centos-mirror-tools/ docker run -it --volume $(pwd):/localdisk local/$USER-stx-builder:7.4 bash cd localdisk && bash download_mirror.sh The above steps are no longer applicable to the current StarlingX Master environment construction. At the same time, this step will directly lead to the following download error. [root at 5fc5c5f5f610 /]# cd localdisk && bash download_mirror.sh download_mirror.sh: line 8: /localdisk/../toCOPY/lst_utils.sh: No such file or directory download_mirror.sh: line 232: merge_lst: command not found download_mirror.sh: line 233: merge_lst: command not found download_mirror.sh: line 234: merge_lst: command not found download_mirror.sh: line 235: merge_lst: command not found download_mirror.sh: line 236: merge_lst: command not found -------------------------------------------------------------- WARNING: this script HAS TO access internet (http/https/ftp), so please make sure your network working properly!! step #0: Configuring yum repos ... download_mirror.sh: line 345: [: !=: unary operator expected As the result, the compilation and construction of StarlingX could not be implemented. Temporary countermeasure: In order for download_mirror.sh to run normally, we have adopted the following methods to deal with it, Methods as below: cd $HOME/tools bash tb.sh run bash tb.sh exec -------------------------- [zs at af1b85270819 /]$ cd $MY_REPO_ROOT_DIR [zs at af1b85270819 starlingx]$ cd stx-tools/centos-mirror-tools/ [zs at af1b85270819 centos-mirror-tools]$sudo MY_REPO=/localdisk/designer/zs/starlingx/cgcs-root ./download_mirror.sh Although this solution can currently solve the download_mirror.sh Error problem temporarily. However,We hope the community can provide better solutions to share, Thank you! -------------- From: Neusoft - Shuai --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Mar 3 10:02:19 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 3 Mar 2020 05:02:19 -0500 (EST) Subject: [Starlingx-discuss] [dev] [build-report] STX_build_wheels - Build # 173 - Failure! Message-ID: <258562986.914.1583229740914.JavaMail.javamailuser@localhost> Project: STX_build_wheels Build #: 173 Status: Failure Timestamp: 20200303T095453Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200303T090309Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200303T090309Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200303T090309Z/logs OS_VERSION: 7.5.1804 BUILD_STREAM: dev PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200303T090309Z/logs From build.starlingx at gmail.com Tue Mar 3 10:02:23 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 3 Mar 2020 05:02:23 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 31 - Failure! Message-ID: <519732673.917.1583229744371.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 31 Status: Failure Timestamp: 20200303T090309Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200303T090309Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: false From maria.g.perez.ibarra at intel.com Tue Mar 3 17:14:40 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 3 Mar 2020 17:14:40 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200303 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-03 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Tue Mar 3 17:21:39 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 3 Mar 2020 17:21:39 +0000 Subject: [Starlingx-discuss] No community call this week... Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007BA83E6@ALA-MBD.corp.ad.wrs.com> Note that there won't be a Community Call tomorrow as the mini-PTG is in progress... -----Original Message----- From: Zvonar, Bill Sent: Wednesday, February 26, 2020 10:49 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: RE: Community (& TSC) Call (Feb 26, 2020) >From today's call... - Standing Topics - Sanity - both Monolithic & Layered builds are happening now - per Nicolae, both look green now - currently, to know which one it is, check the part that says "Status of the Sanity Test" - if the link references ../outputs/iso, then it's a monolithic build - if the link references ../flock/../outputs, then it's a layered build - should start seeing sanity reports for both, they will run alternately - Reviews - nothing new this week - CentOS 8 - progressing towards sanitizing with the new kernel (std & rt) - Topics for This Week - Validation team - Robot vs Pytest Q&A - some questions to bring to Test Meeting and/or Yang (Test PL) - R4 Doc Tasks - will be covered in *this* week's release team meeting (we didn't have the meeting last week) - Open Requests for Help - nothing new this week (well, a couple of very recent ones, but we'll let the Community review) -----Original Message----- From: Zvonar, Bill Sent: Wednesday, February 26, 2020 8:30 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: Community (& TSC) Call (Feb 26, 2020) Hi all, reminder of today's TSC/Community call [2]. We'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200226T1500 From kristal.dale at intel.com Tue Mar 3 17:53:08 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Tue, 3 Mar 2020 17:53:08 +0000 Subject: [Starlingx-discuss] StarlingX Documentation meeting cancelled for March 4th Message-ID: Hello All, Due to the meetup March 3rd and 4th this week, I am cancelling the weekly docs meeting scheduled for Wednesday March 4th. The next meeting will be on March 11th. If there are any questions or issues related to docs before the next meeting, please post to the discuss list or ping me directly. Cheers, Kris -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Tue Mar 3 22:37:56 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 3 Mar 2020 14:37:56 -0800 Subject: [Starlingx-discuss] PBR Changes With review comment In-Reply-To: References: <5f55cb03-5360-3e11-fcc9-46f6dc24d6f8@linux.intel.com> <060f01d5db34$f5e38a50$e1aa9ef0$@jitstack.com> <42960858-5122-4de5-b4c9-6d5619f4d692@linux.intel.com> Message-ID: <4d8a6543-c74c-5d14-e3b4-d20d6def0753@linux.intel.com> Hi JITStack folks working on PBR: Not sure who is doing the follow-up work, there are a number of pending reviews with comments on them. Testing has been requested to validate that packages install and operate correctly. In some cases, it's not clear to me what was done to check that the packages are getting built and versioned correctly. We want to get this work completed fairly soon. Thanks Sau! From bruce.e.jones at intel.com Wed Mar 4 00:20:16 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 4 Mar 2020 00:20:16 +0000 Subject: [Starlingx-discuss] Community Meetup day one notes Message-ID: <9A85D2917C58154C960D95352B22818BF1679FBF@fmsmsx123.amr.corp.intel.com> We had good discussions today on a number of topics and actually covered everything on the planned agenda. We kept the etherpad updated, you can find all of our notes on the discussions here: https://etherpad.openstack.org/p/starlingX-winter-2020-meetup brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Wed Mar 4 01:56:46 2020 From: yong.hu at intel.com (Yong Hu) Date: Wed, 4 Mar 2020 09:56:46 +0800 Subject: [Starlingx-discuss] Community Meetup day one notes In-Reply-To: <9A85D2917C58154C960D95352B22818BF1679FBF@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BF1679FBF@fmsmsx123.amr.corp.intel.com> Message-ID: <9933efa8-cbb8-6d91-942a-f93c5248b309@intel.com> FYI. Austin and I made a few comments inline. On 2020/3/4 8:20 AM, Jones, Bruce E wrote: > We had good discussions today on a number of topics and actually covered > everything on the planned agenda. > > We kept the etherpad updated, you can find all of our notes on the > discussions here: > https://etherpad.openstack.org/p/starlingX-winter-2020-meetup > >      brucej > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From build.starlingx at gmail.com Wed Mar 4 05:36:34 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 4 Mar 2020 00:36:34 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 629 - Failure! Message-ID: <2012370766.920.1583300195838.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 629 Status: Failure Timestamp: 20200304T023939Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200304T023004Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200304T023004Z DOCKER_BUILD_ID: jenkins-master-20200304T023004Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200304T023004Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200304T023004Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Wed Mar 4 05:36:38 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 4 Mar 2020 00:36:38 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 458 - Failure! Message-ID: <1566322636.923.1583300198997.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 458 Status: Failure Timestamp: 20200304T023004Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200304T023004Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From yan.chen at intel.com Wed Mar 4 08:50:52 2020 From: yan.chen at intel.com (Chen, Yan) Date: Wed, 4 Mar 2020 08:50:52 +0000 Subject: [Starlingx-discuss] Met issue when configuring IPv6 duplex system Message-ID: Hi, Matt and all, I met an strange issue when deploying an IPv6 duplex system. I need your help to check if anything I missed during the deployment. I setup a container to run NAT64/DNS64 gateway on my test machine and 2 vms for a duplex system. Except the gateway and the localhost.yml I followed everything as a normal ipv4 duplex system setup. The controller-0 was unlocked and controller-1 can be installed via PXE, but when controller-1 finished installing and rebooted for the first time, mgmt network can only get the PXE IP from DHCP server. Attached /var/log/anaconda/journal.log. If I config the mgmt network on controller-1 with ipv6 IP manually, it can ping to controller-0 successfully. Is there any special thing I need to do for a IPv6 setup? And here's my localhost.yml: --- system_mode: duplex management_subnet: fd01::/96 management_start_address: fd01::2 management_end_address: fd01::50 management_multicast_subnet: ff08::1:1:0/124 cluster_host_subnet: fd02::/96 cluster_pod_subnet: fd03::/96 cluster_service_subnet: fd04::/112 external_oam_subnet: fd00::/96 external_oam_gateway_address: fd00::1 external_oam_floating_address: fd00::2 external_oam_node_0_address: fd00::3 external_oam_node_1_address: fd00::4 admin_username: admin admin_password: Local.123 dns_servers: - fd00::1 Thanks! Yan -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: screen.png Type: image/png Size: 51779 bytes Desc: screen.png URL: From build.starlingx at gmail.com Wed Mar 4 09:32:26 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 4 Mar 2020 04:32:26 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 87 - Failure! Message-ID: <1324797578.926.1583314347509.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 87 Status: Failure Timestamp: 20200304T091359Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200304T090229Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200304T090229Z DOCKER_BUILD_ID: jenkins-master-flock-20200304T090229Z-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/20200304T090229Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200304T090229Z/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 Wed Mar 4 09:32:29 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 4 Mar 2020 04:32:29 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 32 - Still Failing! In-Reply-To: <2018928085.915.1583229741874.JavaMail.javamailuser@localhost> References: <2018928085.915.1583229741874.JavaMail.javamailuser@localhost> Message-ID: <82606709.929.1583314353783.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 32 Status: Still Failing Timestamp: 20200304T090229Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200304T090229Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: false From sgw at linux.intel.com Wed Mar 4 13:36:12 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 4 Mar 2020 05:36:12 -0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSNOiBQQlIgQ2hhbmdlcyBXaXRo?= =?utf-8?q?_review_comment?= In-Reply-To: <00b501d5f20b$17d78520$47868f60$@jitstack.com> References: <00b501d5f20b$17d78520$47868f60$@jitstack.com> Message-ID: On 3/4/20 1:55 AM, cherish.cao at jitstack.com wrote: > Hi Saul: > > Nice to meet you! > > We are sorry for the delay of PBR task. Engineer in charge of the > StarlingX project  is unable to resume work because of SARS-CoV, China > is seriously affected by the virus. > Yes, I am aware, I hope all your team are doing OK and will recover from this horrible event. > We have to arrange new engineers to take over the StarlingX project from > this week, then we need to complete the task handover in 1-2 weeks. For > that reason,we had already delayed task. > > However,due to join a new engineer,we are confident that we will solve > the current difficulties as soon as possible. > Understood, please keep us posted about and if the the new team members have any questions don't hesitate to ask for help. > This is new engineer's contact information: > > Helen (helen.gui at jitstack.com ) > > Yipeng.He(yipeng.he at jitstack.com > > Cherish.Cao > > Best Regads. > Thanks Sau! From build.starlingx at gmail.com Wed Mar 4 17:46:09 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 4 Mar 2020 12:46:09 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 459 - Still Failing! In-Reply-To: <533963696.921.1583300196691.JavaMail.javamailuser@localhost> References: <533963696.921.1583300196691.JavaMail.javamailuser@localhost> Message-ID: <1315331726.933.1583343970275.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 459 Status: Still Failing Timestamp: 20200304T173605Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200304T173605Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From bruce.e.jones at intel.com Wed Mar 4 19:49:41 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 4 Mar 2020 19:49:41 +0000 Subject: [Starlingx-discuss] CPU Affinity Kernel Patch In-Reply-To: <8E5740EC88EF3E4BA3196F2545DC8625C13978E0@ALA-MBD.corp.ad.wrs.com> References: <7faf0389-20be-898e-581b-54063f6023b9@intel.com> <8E5740EC88EF3E4BA3196F2545DC8625C13978E0@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BF167A4EF@fmsmsx123.amr.corp.intel.com> + StarlingX community James, thank you! brucej -----Original Message----- From: Gauld, James [mailto:James.Gauld at windriver.com] Sent: Wednesday, March 4, 2020 8:21 AM To: Somerville, Jim ; Wold, Saul ; Rowsell, Brent ; Jones, Bruce E Subject: RE: CPU Affinity Kernel Patch Regarding CPU affinity specific configuration: We need to keep the functionality provided by the following kernel patches: - affine-compute-kernel-threads.patch - Affine-irqs-and-workqueues-with-kthread_cpus.patch These ensure kernel threads and all IRQs get the specified 'kthread_cpus=' kernel option at boot, and IRQs have this affinity as new devices are inserted. In addition to the above, we configure settings at runtime via: workqueue settings for writeback and virtual devices, /sys/bus/workqueue/devices/writeback/cpumask and /sys/bus/virtual/workqueue/cpumask irq affinity settings for pci devices, /proc/irq/*/smp_affinity_list -jim -----Original Message----- From: Jim Somerville [mailto:jim.somerville at windriver.com] Sent: March-03-20 3:18 PM To: Saul Wold; Rowsell, Brent; Jones, Bruce E; Gauld, James Subject: Re: CPU Affinity Kernel Patch I'm adding the other Jim, our cpu affinity guy. -Jim On 2020-03-03 3:11 p.m., Saul Wold wrote: > > Hi Jim, > > As we are moving to CentOS8 and the 4.18 kernel, I wanted to > double/triple check regarding the CPU affinity work.  I seem to recall > that StarlingX now uses the /sys workqueue masks. We we still need the > kernel patches? > > I hope this is making some sense. > > Thanks > Sau! From build.starlingx at gmail.com Wed Mar 4 20:05:35 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 4 Mar 2020 15:05:35 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 460 - Still Failing! In-Reply-To: <745939596.931.1583343967792.JavaMail.javamailuser@localhost> References: <745939596.931.1583343967792.JavaMail.javamailuser@localhost> Message-ID: <140140503.937.1583352336895.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 460 Status: Still Failing Timestamp: 20200304T200501Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200304T200501Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From build.starlingx at gmail.com Wed Mar 4 21:58:04 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 4 Mar 2020 16:58:04 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 461 - Still Failing! In-Reply-To: <1269057193.935.1583352334255.JavaMail.javamailuser@localhost> References: <1269057193.935.1583352334255.JavaMail.javamailuser@localhost> Message-ID: <1131755185.941.1583359085914.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 461 Status: Still Failing Timestamp: 20200304T212811Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200304T212811Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From zhipengs.liu at intel.com Thu Mar 5 06:06:00 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 5 Mar 2020 06:06:00 +0000 Subject: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Message-ID: <93814834B4855241994F290E959305C75314CC61@SHSMSX104.ccr.corp.intel.com> Hi Penney, We just used OpenStack master branch and upper-constraint file below https://raw.githubusercontent.com/openstack/requirements/master/upper-constraints.txt libvirt-python===5.10.0;python_version=='2.7' libvirt-python===6.0.0;python_version=='3.6' libvirt-python===6.0.0;python_version=='3.7' In nova setup.cfg. it adds python require info. python-requires = >=3.6 Then we built python3 related packages to the base image and rebuilt nova image to fix python3 issue. But there is still an error below. collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) ERROR: Could not find a version that satisfies the requirement libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) (from versions: none) ERROR: No matching distribution found for libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 From code, I saw that we already built libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl through a patch which Seems related to python2. cgcs-root/stx/integ/virt/libvirt-python/centos/meta_patches$ 0002-Build-python-wheel.patch It needs libvirt-python whl for python3, right? Do we have plan to upgrade libvirt-python to 6.0.0? Any comment? Thanks a lot! Zhipeng From: Penney, Don Sent: 2020年2月27日 0:25 To: YuChengDe ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I was able to successfully build stx-nova image in master with no changes. Do you have any customizations in your environment? From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 26, 2020 10:38 AM To: YuChengDe; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 [Image removed by sender.] -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From scott.little at windriver.com Thu Mar 5 18:48:05 2020 From: scott.little at windriver.com (Scott Little) Date: Thu, 5 Mar 2020 13:48:05 -0500 Subject: [Starlingx-discuss] [docs]Regarding the StarlingX Build Guide In-Reply-To: <001001d5f128$b35f97f0$1a1ec7d0$@neusoft.com> References: <001001d5f128$b35f97f0$1a1ec7d0$@neusoft.com> Message-ID: The short answer .... The $MY_REPO variable must now be defined before you run download_mirror.sh. I'll check the docs ... Scott On 2020-03-03 1:55 a.m., Shuai wrote: > > Hi Communityer > > Regarding the StarlingX Build Guide: > > When we built the latest version of StarlingX, we found some build > guide issues and raised them here.: > > Guide Path:https://docs.starlingx.io/developer_resources/build_guide.html > > ★Issues*(1).**Paragraph: Build the CentOS mirror repository* > > cd $HOME/tools/centos-mirror-tools/ > docker run -it --volume $(pwd):/localdisk local/$USER-stx-builder:7.4 bash > cdlocaldisk&&bashdownload_mirror.sh > > *The above steps are no longer applicable to the current StarlingX > Master environment construction.* > > *At the same time, this step will directly lead to the following > download error.* > > [root at 5fc5c5f5f610 /]# cd localdisk && bash download_mirror.sh > download_mirror.sh: line 8: /localdisk/../toCOPY/lst_utils.sh: No such > file or directory > download_mirror.sh: line 232: merge_lst: command not found > download_mirror.sh: line 233: merge_lst: command not found > download_mirror.sh: line 234: merge_lst: command not found > download_mirror.sh: line 235: merge_lst: command not found > download_mirror.sh: line 236: merge_lst: command not found > -------------------------------------------------------------- > WARNING: this script HAS TO access internet (http/https/ftp), > so please make sure your network working properly!! > step #0: Configuring yum repos ... > download_mirror.sh: line 345: [: !=: unary operator expected > > As the result, the compilation and construction of StarlingX could not > be implemented. > > *Temporary countermeasure:* > > *In order for download_mirror.sh to run normally, we have adopted the > following methods to deal with it, Methods as below:* > > cd $HOME/tools > bash tb.sh run > bash tb.sh exec > -------------------------- > [zs at af1b85270819 /]$ cd $MY_REPO_ROOT_DIR > [zs at af1b85270819 starlingx]$ cd stx-tools/centos-mirror-tools/ > [zs at af1b85270819 centos-mirror-tools]$sudo > MY_REPO=/localdisk/designer/zs/starlingx/cgcs-root ./download_mirror.sh > > Although this solution can currently solve the download_mirror.sh > Error problem temporarily. > > However,We hope the community can provide better solutions to share, > Thank you! > > -------------- > > From: Neusoft - Shuai > > > --------------------------------------------------------------------------------------------------- > Confidentiality Notice: The information contained in this e-mail and > any accompanying attachment(s) > is intended only for the use of the intended recipient and may be > confidential and/or privileged of > Neusoft Corporation, its subsidiaries and/or its affiliates. If any > reader of this communication is > not the intended recipient, unauthorized use, forwarding, printing,  > storing, disclosure or copying > is strictly prohibited, and may be unlawful.If you have received this > communication in error,please > immediately notify the sender by return e-mail, and delete the > original message and all copies from > your system. Thank you. > --------------------------------------------------------------------------------------------------- > > > _______________________________________________ > 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 sgw at linux.intel.com Thu Mar 5 20:54:53 2020 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 5 Mar 2020 12:54:53 -0800 Subject: [Starlingx-discuss] Chrony vs NTP in CentOS-8 Message-ID: <66be1eb1-2d76-9b0a-0359-1f98aef2fca8@linux.intel.com> Hi Don, Bart: Great to see you guys the last couple of days here in Chandler. I was reviewing some CentOS-8 work and saw that team was getting NTP from a non-standard repo and then checked that NTP has been replaced with Chrony. Is there a hard dependency in StarlingX for NTP or can Chrony be used as a valid replacement as it's part of the core CentOS-8 distro? Thanks Sau! From ildiko.vancsa at gmail.com Thu Mar 5 21:32:55 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 5 Mar 2020 13:32:55 -0800 Subject: [Starlingx-discuss] K8s conformance application question Message-ID: <99EB2033-00A9-477A-BC82-4F0D38D2189D@gmail.com> Hi StarlingX Community, During the preparation of the K8s conformance application package I came across an item on one of the forms I wanted to bring up before submitting. One of the forms[1] require to list 'Participant Kubernetes Combinations’, e.g. "XYZ Kubernetes" or "XYZ Kubernetes Platform”. As StarlingX is not a targeted Kubernetes distribution but rather an edge platform that has Kubernetes as one of the components to deliver functionality to fulfill the needs of the different use cases this section is not applicable in my understanding. In order to avoid future confusions and issues with using the conformance mark I wanted to double check that my understanding is correct before submitting the form. Please raise any concerns before the end of this week or let me know if you agree with the above. Thanks, Ildikó [1] https://github.com/cncf/k8s-conformance/blob/master/participation-form/Certified_Kubernetes_Form.md From Ghada.Khalil at windriver.com Thu Mar 5 21:34:21 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 5 Mar 2020 21:34:21 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 03/05 Message-ID: <151EE31B9FCCA54397A757BC674650F0C1689DFD@ALA-MBD.corp.ad.wrs.com> Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Attendees: Ghada Khalil, Joseph Richard, Steve Webster, Sabeel Ansari, Chris Winnicki, Yi Wang, Nicolae Jascanu stx.4.0 Features - TSN support in Container - Prime: Shuicheng / Yi C - Story: https://storyboard.openstack.org/#!/story/2006746 - Status: Starting - setting up environment, but not much progress on feature yet - The hard dependency on the host kernel being 4.19 is required for regular containers, but not kata containers. Can proceed with work for kata containers. - From Yi C: - NIC driver should be okay given IGB (Intel I210) is already there. To support TSN, we still need some kernel features, for example, - Qdisc TAPRIO: implemented TSN protocol 802.1Qbv and was introduced in Linux 4.20 - Qdisc CBS: implemented 802.1Qav and was introduced in Linux 4.15 - probably other features like AF_XDP socket family which was introduced in Linux 4.18. - For the feature of " TSN support in Kata", since Kata container has its own kernel, there is not hard dependency with CentOS 8 upgrade task - Is there any code for this? or just a procedure? - IPv6 PXE boot network support - Prime: Kunpeng Zhang - 99cloud - Story: https://storyboard.openstack.org/#!/story/2006442 - Status: Not Started - Received email from Kunpeng on March 5 indicating that he will provide the plan for this feature shortly. - OVS-DPDK Containerization in StarlingX - Story: https://storyboard.openstack.org/#!/story/2005496 - Status: Out of stx.4.0 - As per Huifeng Le, the detailed status when the feature was put on hold is as follows: - Openstack-helm: - Wait for merge: - Override configurations more than conf section.( https://review.opendev.org/#/c/701676/) - Ongoing: - 1. Make more sections in daemonset overridable.( https://review.opendev.org/#/c/707788/) ? code ready, work on CI - 2. Modify files related to overrides.( https://review.opendev.org/#/c/707775/) ? code ready, work on CI - 3. Ovs per-host overrides support. (https://review.opendev.org/#/c/703639/) ? 50% done - Starlingx: - Ongoing: - Add dpdk parameters for openvswitch.(https://review.opendev.org/#/c/694188/) - This patch depends on the openstack-helm patch. - Todo: - Add dpdk parameters for NEUTRON. stx.4.0 Bugs - Total: 4 - https://bugs.launchpad.net/starlingx/+bug/1862651 -- IPv6 DC: 100.113 alarm "'DATA-NETWORK0' interface failed" raised at both system controller and subclouds after installation - New. Issue appears to be related to having multiple data ports. Not assigned yet. - https://bugs.launchpad.net/starlingx/+bug/1833463 -- armada-manifest upload failed when configuring bond with OVS container (vswitch-type=none) - Needs to be re-assigned. Action with Yong. Work is related to openstack-helm - https://bugs.launchpad.net/starlingx/+bug/1850438 -- The sriov device plugin pod may start before it's config manifest is written - Steve. On hold. As per Steve, he hasn't been seeing this issue in recent testing. The race condition still exists, but is happening at a much lower frequency. - Agreed to keep as gating for stx.4.0 for now, but as a lower priority item. - https://bugs.launchpad.net/starlingx/+bug/1859641 - IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status" - This is related to IPv6. Review in progress, but it only addresses a mariadb issue. As per Zhipeng, another issue related to rabbitmq is hit after that. stx.3.0 Bugs - Total: 1 - https://bugs.launchpad.net/starlingx/+bug/1821026 -- Containers: Resolving hostname fails within nova containers leading to config_drive VM migration failures - Confirmed to be an issue in stx master (stx.4.0) as well. One code review is posted, but Marvin had issues w/ testing (and is transitioning out of StarlingX) - https://review.opendev.org/#/c/700100/ - Bug transferred to Joseph Richard; not started yet. stx.2.0 Bugs - Total: 0 Low Priority Bugs - Total: 9 - 3 bugs are in progress with reviews posted Test Team Update - Still ramping up the team on the StarlingX project in general. - Nobody has been specifically assigned to the networking domain yet. Expect this to happen in the future after ramp. From Ghada.Khalil at windriver.com Thu Mar 5 21:44:43 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 5 Mar 2020 21:44:43 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Mar 5/2020 Message-ID: <151EE31B9FCCA54397A757BC674650F0C1689E2D@ALA-MBD.corp.ad.wrs.com> Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.4.0 - CentOS Upgrade (update from Bruce based on F2F) - Getting close on 4.18 kernel - Will likely stop after that. Decided not to attempt to do user-space piecemeal. Dependencies are still missing and RH schedule in unknown. - Ceph (update from Bruce based on F2F) - Add containerized ceph to starlingx (this will be the same version as the platform ceph), but keep the platform ceph in there as well - Will work on a procedure to migrate the ceph data from the platform ceph to the containerized ceph - This will require downtime during the upgrade - Remove the platform ceph in stx.5.0 - BlueStore (update from Bruce) - Bluestore is a new filesystem backend for ceph which is optimized for SSD access and provides a significant performance improvement - Decided to take this out of stx.4.0 to reduce risk - Feature Planning - https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 - A number of plans/dates have been updated. See the above spreadsheet for details. - Missing items are highlighted in yellow - Summary - Features In stx.4.0: 16 - Intel FPGA support for K8s - N3000 - Kata Containers - Containerize Ceph - Rook Integration - Decoupling Container Apps - Active Directory Integration for K8s APIs - Fault Containerization - TSN support in kata container - Upversion Kubernetes and container platform components - Cert Manager Integration - OS Rebase to CentOS 8 - Kernel / Module Upgrade - Backup & Restore - k8s (etcd) portion - Kubernetes Upgrade Support - Flock Versioning - Redfish virtual media support - Layered Build - Unit Tests & Functional (API) Tests - Ongoing - Features Awaiting Confirmation / Updates: 10 - Python2>>3 Migration - Ongoing? - Upversion Openstack to Ussuris release - Upversion Openstack services used by flock components on host - Distributed Cloud - openstack - Containerize Openstack clients - System Upgrade support - IPv6 support for PXE boot network - Regression Test Automation - Performance Test Automation - Code Scans using Bandit & Coverity - Features Out of stx.4.0: 8 - Enable Ceph BlueStore based on containerized Ceph - stx-sysinv agent and stx-mtce agent containerization - Multi-OS Support (Prep) - OS Rebase to CentOS 8 - User space Upgrade - Update the kernel to 4.19 or newer (to enable TSN in Containers) - Openstack Live Upgrade Support - Containerize OVS-DPDK - Sysvinit >> systemd Conversion/Cleanup From bruce.e.jones at intel.com Thu Mar 5 22:02:11 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 5 Mar 2020 22:02:11 +0000 Subject: [Starlingx-discuss] Great mid-cycle meetup Message-ID: <9A85D2917C58154C960D95352B22818BF167B108@fmsmsx123.amr.corp.intel.com> I'd like to thank the folks who attended our mid-cycle meetup this week. We had very good discussions on a number of topics which helped clarify our plans for the next two releases. Our notes on the discussion are on the etherpad: https://etherpad.openstack.org/p/starlingX-winter-2020-meetup. Please review them and please ask any questions or raise any issues you see in them. Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Thu Mar 5 22:42:21 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 5 Mar 2020 22:42:21 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200305 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-05 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard External - Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] There are no results for standard baremetal, reproduced this bug during the Initial Setup: https://bugs.launchpad.net/starlingx/+bug/1856078 , we applied the workaround, however, the sanity didn't completed on time. Regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Fri Mar 6 12:22:11 2020 From: Greg.Waines at windriver.com (Waines, Greg) Date: Fri, 6 Mar 2020 12:22:11 +0000 Subject: [Starlingx-discuss] FW: REMINDER about updating STX REST API DOCUMENTATION In-Reply-To: <4FAE7C47-63CB-46A3-9619-AA901C72EC90@windriver.com> References: <4FAE7C47-63CB-46A3-9619-AA901C72EC90@windriver.com> Message-ID: <8C572BC7-19D2-4924-8931-A662E7629B0A@windriver.com> I thought I would send out this “nag” email again because I believe some starlingx contributors have been forgetting to update STX REST API DOCUMENTATION ... not 100% sure, just a hunch. It is the responsibility of the contributor who changes / updates / creates STX REST APIs to also update the STX REST API DOCUMENTATION. The HOWTO info on updating the new REST API DOCS can be found here: https://docs.starlingx.io/contributor/api_contribute_guide.html thanks, Greg. From: Greg Waines Date: Thursday, January 10, 2019 at 3:19 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] REMINDER about updating STX REST API DOCUMENTATION ALL StarlingX-Contributors, This email is probably about 5 months too late ... apologies. ATTENTION back in ~ September 2018, the StarlingX Documentation Team converted all of our StarlingX REST API Documents from those ugly wadl and yaml files into .rst / restructuredText files; basically aligning with the way all the other services in OpenStack are documenting REST APIs. The new API DOCS (.rst files) are now located under the applicable repos (or sub-repos). It is the responsibility of the contributor who changes / updates / creates STX REST APIs to also update the STX REST API DOCUMENTATION. ( ... again, apologies for telling you this 5 months late ... ) The HOWTO info on updating the new REST API DOCS can be found here: https://docs.starlingx.io/contributor/api_contribute_guide.html Greg. p.s. If you do know that you've changed an STX API in the last 5 months and know that you have NOT done the corresponding STX API DOC change, then minimally you need to raise a StarlingX Launchpad Bug on the issue with the details of the missing changes. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Fri Mar 6 12:58:52 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Fri, 6 Mar 2020 12:58:52 +0000 Subject: [Starlingx-discuss] StarlingX - update to bug 1864221 Message-ID: Hi Franck, Cristopher updated the https://bugs.launchpad.net/starlingx/+bug/1864221 with the information below. We used the latest layered build: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200305T111629Z/ However, we still face the exact same issue with Simplex and Duplex LOGS ======= Simplex: Some outputs: http://paste.openstack.org/show/790365/ Collect: https://files.starlingx.kube.cengn.ca/download_file/54 Duplex: Some outputs: http://paste.openstack.org/show/790368/ Collect: https://files.starlingx.kube.cengn.ca/download_file/55 HARDWARE DETAILS ======= Here are some hardware details for our simplex system: http://paste.openstack.org/show/790370/ Both duplex systems have the same hardware specs. COMMANDS EXECUTED ======= These are the commands that we ran against the simplex system before doing the unlock: http://paste.openstack.org/show/790373/ After that, the system boots, but that's when we receive the error "Openstack Admin credentials can only be loaded from the active controller." NOTE: The exact same steps are followed up for both, monolithic and layered build. Is there a different command that needs to be executed? QUESTIONS ======= So regarding the questions: - We are using the exact same server for Simplex on Monolithic and Layered build. - Another pair of servers is used on Duplex for Monolithic and Layered build. - Latest monolithic build doesn't face this error on Simplex, neither on Duplex, Sanity report was sent as green. - We can arrange the meeting, however, could you please let us know at which point do you want the servers to be left? Just with the Image installed? Or, will it be better to execute every command, just before the "system host-unlock controller-0"? In that way, we can check the status before the unlock and monitor how it progress. Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From Barton.Wensley at windriver.com Fri Mar 6 15:57:21 2020 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Fri, 6 Mar 2020 15:57:21 +0000 Subject: [Starlingx-discuss] Chrony vs NTP in CentOS-8 In-Reply-To: <66be1eb1-2d76-9b0a-0359-1f98aef2fca8@linux.intel.com> References: <66be1eb1-2d76-9b0a-0359-1f98aef2fca8@linux.intel.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1C234E0@ALA-MBD.corp.ad.wrs.com> Hey Saul. NTP is currently a hard dependency as we have NTP specific CLIs/database/configuration entries in StarlingX. It is possible we could move to chrony in the future (if we decided that was the way to go), but we would likely have to support both ntp and chrony for at least a release as we'd need to allow a migration path for existing users of ntp. So... short answer is there is a hard dependency. Bart -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: March 5, 2020 3:55 PM To: starlingx-discuss at lists.starlingx.io; Penney, Don; Wensley, Barton; Church, Robert Subject: Chrony vs NTP in CentOS-8 Hi Don, Bart: Great to see you guys the last couple of days here in Chandler. I was reviewing some CentOS-8 work and saw that team was getting NTP from a non-standard repo and then checked that NTP has been replaced with Chrony. Is there a hard dependency in StarlingX for NTP or can Chrony be used as a valid replacement as it's part of the core CentOS-8 distro? Thanks Sau! From mihail-laurentiu.trica at intel.com Fri Mar 6 16:09:04 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Fri, 6 Mar 2020 16:09:04 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200306 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-06 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers – 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 ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard External - Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] There are no results for the standard virtual setup, we are investigating the issue. Regards, STX Validation Team Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Mon Mar 9 08:42:31 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Mon, 9 Mar 2020 08:42:31 +0000 Subject: [Starlingx-discuss] Pytest tests from WindRiver Message-ID: Hi All, As a Validation Team we need to convert the Validation robot tests into pytest specific tests. We have several questions regarding the pytests and the workflows for committing those tests. We need some contact persons to talk about these. Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From mihail-laurentiu.trica at intel.com Mon Mar 9 13:13:04 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Mon, 9 Mar 2020 13:13:04 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build - ISO 20200308 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-08 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers – 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 ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards, STX Validation Team Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dariush.Eslimi at windriver.com Mon Mar 9 13:47:39 2020 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Mon, 9 Mar 2020 13:47:39 +0000 Subject: [Starlingx-discuss] StarlingX Flock meeting conflict for March 10 Message-ID: All, Due to conflicts with some internal meetings occurring this week, I will not be able to host the bi-weekly flock meeting scheduled for Tuesday March 10. I will host the next meeting on March 24. If there is community interest, I would encourage you to use this window and meet and discuss issues with rest of the community members, but PL & TL for this sub-project will not be present. Thanks, Dariush -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Mar 9 14:26:08 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 9 Mar 2020 14:26:08 +0000 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton Message-ID: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> Hi scott As last week sync with brent, we will create a new application for ceph containeration. Could you help to create this new git project for me? Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Mon Mar 9 14:40:13 2020 From: scott.little at windriver.com (Scott Little) Date: Mon, 9 Mar 2020 10:40:13 -0400 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> Message-ID: Yes, I can help with that.  I can't create the new git myself, but can help with the process of submitting the request to the opendev admins First we'll need 1) unique and descriptive name for the new git. 2) A description of the project for the comment section.  A sentence or two. 3) The url and branch of any upstream git used to seed the content for the new git. 4) is this a python project that needs to publish to PYPI ? Scott PS: The process is described out here [1] [1] https://docs.openstack.org/infra/manual/creators.html On 2020-03-09 10:26 a.m., Chen, Haochuan Z wrote: > > Hi scott > > As last week sync with brent, we will create a new application for > ceph containeration. Could you help to create this new git project for > me? > > Thanks! > > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dejan.muhamedagic at tttech-industrial.com Mon Mar 9 15:06:04 2020 From: dejan.muhamedagic at tttech-industrial.com (Dejan Muhamedagic) Date: Mon, 9 Mar 2020 15:06:04 +0000 Subject: [Starlingx-discuss] oam address In-Reply-To: <7E4792BA14B1DE4BAB354DF77FE0233AC4376097@ALA-MBD.corp.ad.wrs.com> References: <737e35859c115f6a9511a95677a1f9161cbfb68a.camel@tttech-industrial.com> <7E4792BA14B1DE4BAB354DF77FE0233AC4376097@ALA-MBD.corp.ad.wrs.com> Message-ID: <96a200331d5aa269a0291094b2035d7119a41f36.camel@tttech-industrial.com> Hi, Changing the OAM IP address did work, sort of, but there is a problem with some certificate which apparently needs to be recreated. Applications cannot be applied anymore: | platform-integ-apps | 1.0-8 | platform- integration-manifest | manifest.yaml | apply-failed | Deployment of application platform-integ-apps (1.0-8) failed: failed to download one or more image(s). | The error message I found in sysinv.log: sysinv 2020-03-09 14:57:45.903 83083 ERROR sysinv.conductor.kube_app [-] Image registry.local:9001/docker.io/starlingx/ceph-config- helper:v1.15.0 dow nload failed from local registry: 500 Server Error: Internal Server Error ("Get https://registry.local:9001/v2/docker.io/starlingx/ceph-config-helper/manifests/ v1.15.0: Get https://10.107.8.255:9002/token/?account=admin&scope=repository%3Ad ocker.io%2Fstarlingx%2Fceph-config- helper%3Apull&service=192.168.204.1%3A9001: x 509: certificate is valid for 192.168.204.1, 10.107.10.21, not 10.107.8.255"): A PIError: 500 Server Error: Internal Server Error ("Get https://registry.local:90 01/v2/docker.io/starlingx/ceph-config-helper/manifests/v1.15.0: Get https://10.1 07.8.255:9002/token/?account=admin&scope=repository%3Adocker.io%2Fstarl ingx%2Fce ph-config-helper%3Apull&service=192.168.204.1%3A9001: x509: certificate is valid for 192.168.204.1, 10.107.10.21, not 10.107.8.255") (Sorry about the formatting!) The OAM IP address changed from 10.107.10.21/22 to 10.107.8.255/22. Is it possible to fix this? Best regards, Dejan On Mon, 2020-02-24 at 15:05 +0000, Winnicki, Chris wrote: > Hi Dejan > > It's absolutely possible to change the OAM IP address after the > installation is completed. > * One thing to watch out for is make sure that: > 1) oam_gateway_ip is updated if you're changing networks > 2) That your machine (which you're using to access the StarlinX > system) can route to the new network (in case the networks were > changed) > > > Regards, > > Chris Winnicki > chris.winnicki at windriver.com > 613-963-1329 > ________________________________________ > From: Dejan Muhamedagic [dejan.muhamedagic at tttech-industrial.com] > Sent: Monday, February 24, 2020 9:48 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] oam address > > Hi, > > Is it possible to change the OAM IP address after the installation? > There is a "system oam-modify", but the installation guide warns: > > "Some Ansible bootstrap parameters cannot be changed or are very > difficult to change after installation is complete." > > The reason I'm asking is that this installation may have to run in > different environments and possibly in different networks. > > Thanks, > > Dejan > > CONFIDENTIALITY: The contents of this e-mail are confidential and > intended only for the above addressee(s). If you are not the intended > recipient, or the person responsible for delivering it to the > intended recipient, copying or delivering it to anyone else or using > it in any unauthorized manner is prohibited and may be unlawful. If > you receive this e-mail by mistake, please notify the sender and the > systems administrator at straymail at tttech.com immediately. > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail at tttech.com immediately. From Don.Penney at windriver.com Mon Mar 9 15:17:57 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 9 Mar 2020 15:17:57 +0000 Subject: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images In-Reply-To: <93814834B4855241994F290E959305C75314CC61@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C75314CC61@SHSMSX104.ccr.corp.intel.com> Message-ID: I think building the openstack master branch will require moving the images to python3. This has implications to the base image, to how we build the base wheels tarball, and possibly to arguments passed to loci (as well as moving to a newer loci SHA). I believe Al started looking at this last week, but got pulled off to look at some other issues. From your reply, it sounds like maybe you’ve also done some of this? When we explicitly add wheels to the tarball, we update the upper-constraints file to align with the module we’ve included. This would be why the build is looking for 4.7.0 here. There is an upper-constraints.txt file in the tarball itself which you can check. The libvirt wheel building is python2 only, currently. So it would need to be built for python3 - if that’s possible for 4.7.0. If a newer version of libvirt-python is needed for python3 support, then it will need to be updated. I don’t know how big that effort will be. From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, March 05, 2020 1:06 AM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Penney, We just used OpenStack master branch and upper-constraint file below https://raw.githubusercontent.com/openstack/requirements/master/upper-constraints.txt libvirt-python===5.10.0;python_version=='2.7' libvirt-python===6.0.0;python_version=='3.6' libvirt-python===6.0.0;python_version=='3.7' In nova setup.cfg. it adds python require info. python-requires = >=3.6 Then we built python3 related packages to the base image and rebuilt nova image to fix python3 issue. But there is still an error below. collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) ERROR: Could not find a version that satisfies the requirement libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) (from versions: none) ERROR: No matching distribution found for libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 From code, I saw that we already built libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl through a patch which Seems related to python2. cgcs-root/stx/integ/virt/libvirt-python/centos/meta_patches$ 0002-Build-python-wheel.patch It needs libvirt-python whl for python3, right? Do we have plan to upgrade libvirt-python to 6.0.0? Any comment? Thanks a lot! Zhipeng From: Penney, Don Sent: 2020年2月27日 0:25 To: YuChengDe ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I was able to successfully build stx-nova image in master with no changes. Do you have any customizations in your environment? From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 26, 2020 10:38 AM To: YuChengDe; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 [Image removed by sender.] -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From zhipengs.liu at intel.com Mon Mar 9 15:43:35 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Mon, 9 Mar 2020 15:43:35 +0000 Subject: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images In-Reply-To: References: <93814834B4855241994F290E959305C75314CC61@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C75314D245@SHSMSX104.ccr.corp.intel.com> Thanks Don! See my inline comments. From: Penney, Don Sent: 2020年3月9日 23:18 To: Liu, ZhipengS ; YuChengDe ; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I think building the openstack master branch will require moving the images to python3. This has implications to the base image, to how we build the base wheels tarball, and possibly to arguments passed to loci (as well as moving to a newer loci SHA). >> Yes, we have to set python3 = true to loci and also fix a small known bug. I believe Al started looking at this last week, but got pulled off to look at some other issues. From your reply, it sounds like maybe you’ve also done some of this? >> Yes When we explicitly add wheels to the tarball, we update the upper-constraints file to align with the module we’ve included. This would be why the build is looking for 4.7.0 here. There is an upper-constraints.txt file in the tarball itself which you can check. >> Yes, in our script, if we have 4.7.0 in stx repo, it will change the version to 4.7.0 from other versions specified in upper-constraints.txt The libvirt wheel building is python2 only, currently. So it would need to be built for python3 - if that’s possible for 4.7.0. If a newer version of libvirt-python is needed for python3 support, then it will need to be updated. I don’t know how big that effort will be. >> From code, libvirt-python 4.7.0 can support both python2 and python3, but in our code, we just add patch to let it build out python2 whl. >> libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, March 05, 2020 1:06 AM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Penney, We just used OpenStack master branch and upper-constraint file below https://raw.githubusercontent.com/openstack/requirements/master/upper-constraints.txt libvirt-python===5.10.0;python_version=='2.7' libvirt-python===6.0.0;python_version=='3.6' libvirt-python===6.0.0;python_version=='3.7' In nova setup.cfg. it adds python require info. python-requires = >=3.6 Then we built python3 related packages to the base image and rebuilt nova image to fix python3 issue. But there is still an error below. collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) ERROR: Could not find a version that satisfies the requirement libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) (from versions: none) ERROR: No matching distribution found for libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 From code, I saw that we already built libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl through a patch which Seems related to python2. cgcs-root/stx/integ/virt/libvirt-python/centos/meta_patches$ 0002-Build-python-wheel.patch It needs libvirt-python whl for python3, right? Do we have plan to upgrade libvirt-python to 6.0.0? Any comment? Thanks a lot! Zhipeng From: Penney, Don > Sent: 2020年2月27日 0:25 To: YuChengDe >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I was able to successfully build stx-nova image in master with no changes. Do you have any customizations in your environment? From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 26, 2020 10:38 AM To: YuChengDe; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 [Image removed by sender.] -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From zhipengs.liu at intel.com Mon Mar 9 16:06:24 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Mon, 9 Mar 2020 16:06:24 +0000 Subject: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images In-Reply-To: <93814834B4855241994F290E959305C75314D245@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C75314CC61@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314D245@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C75314D262@SHSMSX104.ccr.corp.intel.com> We also had below issue during build other service image. Looking in links: /tmp/wheels/ Collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) Collecting PyMySQL===0.9.3 Downloading PyMySQL-0.9.3-py2.py3-none-any.whl (47 kB) Processing /tmp/wheels/python_memcached-1.59-py2.py3-none-any.whl Collecting six===1.14.0 Downloading six-1.14.0-py2.py3-none-any.whl (10 kB) Collecting cffi===1.14.0 Downloading cffi-1.14.0-cp36-cp36m-manylinux1_x86_64.whl (399 kB) ERROR: Could not find a version that satisfies the requirement uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) (from versions: none) ERROR: No matching distribution found for uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) Actually, we get uWSGI-2.0.17.1-cp27-cp27mu-linux_x86_64.whl through the link in stable-config file. So far, not sure how many python3 packages we need. From: Liu, ZhipengS Sent: 2020年3月9日 23:44 To: Penney, Don ; YuChengDe ; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: Re: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! See my inline comments. From: Penney, Don > Sent: 2020年3月9日 23:18 To: Liu, ZhipengS >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I think building the openstack master branch will require moving the images to python3. This has implications to the base image, to how we build the base wheels tarball, and possibly to arguments passed to loci (as well as moving to a newer loci SHA). >> Yes, we have to set python3 = true to loci and also fix a small known bug. I believe Al started looking at this last week, but got pulled off to look at some other issues. From your reply, it sounds like maybe you’ve also done some of this? >> Yes When we explicitly add wheels to the tarball, we update the upper-constraints file to align with the module we’ve included. This would be why the build is looking for 4.7.0 here. There is an upper-constraints.txt file in the tarball itself which you can check. >> Yes, in our script, if we have 4.7.0 in stx repo, it will change the version to 4.7.0 from other versions specified in upper-constraints.txt The libvirt wheel building is python2 only, currently. So it would need to be built for python3 - if that’s possible for 4.7.0. If a newer version of libvirt-python is needed for python3 support, then it will need to be updated. I don’t know how big that effort will be. >> From code, libvirt-python 4.7.0 can support both python2 and python3, but in our code, we just add patch to let it build out python2 whl. >> libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, March 05, 2020 1:06 AM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Penney, We just used OpenStack master branch and upper-constraint file below https://raw.githubusercontent.com/openstack/requirements/master/upper-constraints.txt libvirt-python===5.10.0;python_version=='2.7' libvirt-python===6.0.0;python_version=='3.6' libvirt-python===6.0.0;python_version=='3.7' In nova setup.cfg. it adds python require info. python-requires = >=3.6 Then we built python3 related packages to the base image and rebuilt nova image to fix python3 issue. But there is still an error below. collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) ERROR: Could not find a version that satisfies the requirement libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) (from versions: none) ERROR: No matching distribution found for libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 From code, I saw that we already built libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl through a patch which Seems related to python2. cgcs-root/stx/integ/virt/libvirt-python/centos/meta_patches$ 0002-Build-python-wheel.patch It needs libvirt-python whl for python3, right? Do we have plan to upgrade libvirt-python to 6.0.0? Any comment? Thanks a lot! Zhipeng From: Penney, Don > Sent: 2020年2月27日 0:25 To: YuChengDe >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I was able to successfully build stx-nova image in master with no changes. Do you have any customizations in your environment? From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 26, 2020 10:38 AM To: YuChengDe; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 [Image removed by sender.] -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From yang.liu at windriver.com Mon Mar 9 16:34:13 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Mon, 9 Mar 2020 16:34:13 +0000 Subject: [Starlingx-discuss] Pytest tests from WindRiver In-Reply-To: References: Message-ID: <19C65A6E92EA384D809B1772130CD7F8693CEB13@ALA-MBD.corp.ad.wrs.com> Hi Nicolae, You can forward the questions to myself, and I will help distribute to other folks if needed. Thanks, Yang From: Jascanu, Nicolae [mailto:nicolae.jascanu at intel.com] Sent: March-09-20 4:43 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Pytest tests from WindRiver Hi All, As a Validation Team we need to convert the Validation robot tests into pytest specific tests. We have several questions regarding the pytests and the workflows for committing those tests. We need some contact persons to talk about these. Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From Dariush.Eslimi at windriver.com Mon Mar 9 16:56:07 2020 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Mon, 9 Mar 2020 16:56:07 +0000 Subject: [Starlingx-discuss] Pytest tests from WindRiver In-Reply-To: <19C65A6E92EA384D809B1772130CD7F8693CEB13@ALA-MBD.corp.ad.wrs.com> References: <19C65A6E92EA384D809B1772130CD7F8693CEB13@ALA-MBD.corp.ad.wrs.com> Message-ID: To follow the spirit of four open : https://governance.openstack.org/tc/reference/opens.html Please keep this communication in the mailing list, as this could benefits the whole community. Thanks, Dariush From: Liu, Yang (YOW) [mailto:yang.liu at windriver.com] Sent: March-09-20 12:34 PM To: Jascanu, Nicolae ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Pytest tests from WindRiver Hi Nicolae, You can forward the questions to myself, and I will help distribute to other folks if needed. Thanks, Yang From: Jascanu, Nicolae [mailto:nicolae.jascanu at intel.com] Sent: March-09-20 4:43 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Pytest tests from WindRiver Hi All, As a Validation Team we need to convert the Validation robot tests into pytest specific tests. We have several questions regarding the pytests and the workflows for committing those tests. We need some contact persons to talk about these. Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From build.starlingx at gmail.com Mon Mar 9 17:37:49 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 9 Mar 2020 13:37:49 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_repo_sync_layered - Build # 125 - Failure! Message-ID: <436621900.950.1583775470720.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 125 Status: Failure Timestamp: 20200309T173742Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/container/20200309T173732Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MANIFEST: container.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/container/20200309T173732Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/container/20200309T173732Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master-container From yang.liu at windriver.com Mon Mar 9 20:21:21 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Mon, 9 Mar 2020 20:21:21 +0000 Subject: [Starlingx-discuss] Weekly StarlingX Test meeting Message-ID: <19C65A6E92EA384D809B1772130CD7F8693CEE21@ALA-MBD.corp.ad.wrs.com> Weekly meeting on Tuesday 8AM PT / 1500 UTC Zoom Link: https://zoom.us/j/342730236 Meeting agenda/minutes: https://etherpad.openstack.org/p/stx-test -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1742 bytes Desc: not available URL: From sgw at linux.intel.com Tue Mar 10 00:31:47 2020 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 9 Mar 2020 17:31:47 -0700 Subject: [Starlingx-discuss] Newer NUC8 now require nomodeset Message-ID: <5d339020-bd80-2bf2-e6c4-034566b6b199@linux.intel.com> Hi Folks, I have been chasing down an issue with the newer NUC8 (NUC8i7HVK, these are the dual NIC nucs with a skull on them). When we switched from the 3.10.0-957 kernel to the 3.10.0-1062 kernel in master the system started to hang. The initial kernel boot was hanging after during what seemed like the Framebuffer initialization. The following message was the last line: fb: conflicting fb hw usage amdgpudrmfb vs EFI VGA - removing generic driver After some investigation, I set the "nomodeset" kernel cmdline parameter and that seems to have solved the problem. I have not investigated this any further today, but we might want to see what changes went happened between the 957 and 1062 kernel in the Framebuffer and Video drivers area. Sau! From yong.hu at intel.com Tue Mar 10 00:53:54 2020 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 10 Mar 2020 00:53:54 +0000 Subject: [Starlingx-discuss] StarlingX Distro-OpenStack: Bi-weekly Project Meeting Message-ID: When: Occurs on Tuesday every other week from 9:00 PM to 9:30 PM effective 3/10/2020 until 9/29/2020. (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi Where: https://zoom.us/j/342730236 *~*~*~*~*~*~*~*~*~* 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! Join the meeting: https://zoom.us/j/342730236 Project Team Etherpad: https://etherpad.openstack.org/p/stx-distro-openstack-meetings PS: from now to next summer early, we are going to keep this time slot to accommodate US standard time (6:00 AM in the morning). regards, Yong Hu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2304 bytes Desc: not available URL: From build.starlingx at gmail.com Tue Mar 10 01:45:53 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 9 Mar 2020 21:45:53 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_wheels - Build # 175 - Failure! Message-ID: <232139185.962.1583804754678.JavaMail.javamailuser@localhost> Project: STX_build_wheels Build #: 175 Status: Failure Timestamp: 20200310T013300Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200309T202049Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20200309T202049Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200309T202049Z/logs OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20200309T202049Z/logs From build.starlingx at gmail.com Tue Mar 10 01:46:01 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 9 Mar 2020 21:46:01 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 172 - Failure! Message-ID: <695506676.965.1583804762599.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 172 Status: Failure Timestamp: 20200310T012825Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200309T202049Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20200309T202049Z 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/20200309T202049Z/logs MASTER_BUILD_NUMBER: 6 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20200309T202049Z/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: 20200309T202049Z DOCKER_BUILD_ID: jenkins-master-containers-20200309T202049Z-builder TIMESTAMP: 20200309T202049Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20200309T202049Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20200309T202049Z/outputs From haochuan.z.chen at intel.com Tue Mar 10 01:57:26 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 10 Mar 2020 01:57:26 +0000 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> Hi Scott Check my answer and wait for your comment. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Scott Little Sent: Monday, March 9, 2020 10:40 PM To: Chen, Haochuan Z ; Rowsell, Brent Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: create a new project for ceph containerizaiton Yes, I can help with that. I can't create the new git myself, but can help with the process of submitting the request to the opendev admins First we'll need 1) unique and descriptive name for the new git. Rook storage application 2) A description of the project for the comment section. A sentence or two. This is starlingx application to deploy rook helm chart, which provide storage as starlingx storage backend 3) The url and branch of any upstream git used to seed the content for the new git. https://review.opendev.org/starlingx/rook-storage-app 4) is this a python project that needs to publish to PYPI ? No Scott PS: The process is described out here [1] [1] https://docs.openstack.org/infra/manual/creators.html On 2020-03-09 10:26 a.m., Chen, Haochuan Z wrote: Hi scott As last week sync with brent, we will create a new application for ceph containeration. Could you help to create this new git project for me? Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mingyuan.qi at intel.com Tue Mar 10 02:35:20 2020 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Tue, 10 Mar 2020 02:35:20 +0000 Subject: [Starlingx-discuss] oam address In-Reply-To: <96a200331d5aa269a0291094b2035d7119a41f36.camel@tttech-industrial.com> References: <737e35859c115f6a9511a95677a1f9161cbfb68a.camel@tttech-industrial.com> <7E4792BA14B1DE4BAB354DF77FE0233AC4376097@ALA-MBD.corp.ad.wrs.com> <96a200331d5aa269a0291094b2035d7119a41f36.camel@tttech-industrial.com> Message-ID: Dejan, This issue is caused by new oam ip missing in registry/registry token server certificate SAN. But...normally the registry.local is resolved to mgmt ip which will not trigger this issue. From the log, it seems registry.local was resolved to oam ip. Better to check /etc/hosts and "nslookup registry.local" output. Mingyuan -----Original Message----- From: Dejan Muhamedagic Sent: Monday, March 9, 2020 23:06 To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] oam address Hi, Changing the OAM IP address did work, sort of, but there is a problem with some certificate which apparently needs to be recreated. Applications cannot be applied anymore: | platform-integ-apps | 1.0-8 | platform- integration-manifest | manifest.yaml | apply-failed | Deployment of application platform-integ-apps (1.0-8) failed: failed to download one or more image(s). | The error message I found in sysinv.log: sysinv 2020-03-09 14:57:45.903 83083 ERROR sysinv.conductor.kube_app [-] Image registry.local:9001/docker.io/starlingx/ceph-config- helper:v1.15.0 dow nload failed from local registry: 500 Server Error: Internal Server Error ("Get https://registry.local:9001/v2/docker.io/starlingx/ceph-config-helper/manifests/ v1.15.0: Get https://10.107.8.255:9002/token/?account=admin&scope=repository%3Ad ocker.io%2Fstarlingx%2Fceph-config- helper%3Apull&service=192.168.204.1%3A9001: x 509: certificate is valid for 192.168.204.1, 10.107.10.21, not 10.107.8.255"): A PIError: 500 Server Error: Internal Server Error ("Get https://registry.local:90 01/v2/docker.io/starlingx/ceph-config-helper/manifests/v1.15.0: Get https://10.1 07.8.255:9002/token/?account=admin&scope=repository%3Adocker.io%2Fstarl ingx%2Fce ph-config-helper%3Apull&service=192.168.204.1%3A9001: x509: certificate is valid for 192.168.204.1, 10.107.10.21, not 10.107.8.255") (Sorry about the formatting!) The OAM IP address changed from 10.107.10.21/22 to 10.107.8.255/22. Is it possible to fix this? Best regards, Dejan On Mon, 2020-02-24 at 15:05 +0000, Winnicki, Chris wrote: > Hi Dejan > > It's absolutely possible to change the OAM IP address after the > installation is completed. > * One thing to watch out for is make sure that: > 1) oam_gateway_ip is updated if you're changing networks > 2) That your machine (which you're using to access the StarlinX > system) can route to the new network (in case the networks were > changed) > > > Regards, > > Chris Winnicki > chris.winnicki at windriver.com > 613-963-1329 > ________________________________________ > From: Dejan Muhamedagic [dejan.muhamedagic at tttech-industrial.com] > Sent: Monday, February 24, 2020 9:48 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] oam address > > Hi, > > Is it possible to change the OAM IP address after the installation? > There is a "system oam-modify", but the installation guide warns: > > "Some Ansible bootstrap parameters cannot be changed or are very > difficult to change after installation is complete." > > The reason I'm asking is that this installation may have to run in > different environments and possibly in different networks. > > Thanks, > > Dejan > > CONFIDENTIALITY: The contents of this e-mail are confidential and > intended only for the above addressee(s). If you are not the intended > recipient, or the person responsible for delivering it to the intended > recipient, copying or delivering it to anyone else or using it in any > unauthorized manner is prohibited and may be unlawful. If you receive > this e-mail by mistake, please notify the sender and the systems > administrator at straymail at tttech.com immediately. > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail at tttech.com immediately. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From austin.sun at intel.com Tue Mar 10 08:38:14 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 10 Mar 2020 08:38:14 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 3/11/2020 Message-ID: Hi All: Reminder US/Canada Shift one hours , the meeting will start @9:00 PM china. US/Canada time is same. Agenda for 3/11 meeting: - PBR - Ceph containerization (martin) conclusion result from meet up - CentOS8 upgrade (shuicheng/Austin) as discussed in meet up , stx.4.0 will focus on kernel upgrade. ---- kernel on master * Patch list: https://review.opendev.org/#/q/status:open+project:starlingx/integ+branch:master+topic:4.18_kernel * installer update - python3 upgrade. - open If have any other topic, feel free to add to https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. From dejan.muhamedagic at tttech-industrial.com Tue Mar 10 08:50:25 2020 From: dejan.muhamedagic at tttech-industrial.com (Dejan Muhamedagic) Date: Tue, 10 Mar 2020 08:50:25 +0000 Subject: [Starlingx-discuss] oam address In-Reply-To: References: <737e35859c115f6a9511a95677a1f9161cbfb68a.camel@tttech-industrial.com> <7E4792BA14B1DE4BAB354DF77FE0233AC4376097@ALA-MBD.corp.ad.wrs.com> <96a200331d5aa269a0291094b2035d7119a41f36.camel@tttech-industrial.com> Message-ID: Hi, There's no mgmt, I guess because this is a simplex all-in-one installation. Here's the output from nslookup: controller-0:~$ nslookup mgmt Server:192.168.204.1 Address:192.168.204.1#53 ** server can't find mgmt: NXDOMAIN controller-0:~$ grep mgmt /etc/hosts controller-0:~$ nslookup registry.local Server:192.168.204.1 Address:192.168.204.1#53 registry.localcanonical name = controller. Name:controller Address: 192.168.204.1 The internal server error suggests that the registry itself gets offended by the new IP address. Thanks, Dejan On Tue, 2020-03-10 at 02:35 +0000, Qi, Mingyuan wrote: > Dejan, > > This issue is caused by new oam ip missing in registry/registry token > server certificate SAN. > But...normally the registry.local is resolved to mgmt ip which will > not trigger this issue. From the log, it seems registry.local was > resolved to oam ip. > Better to check /etc/hosts and "nslookup registry.local" output. > > Mingyuan > > -----Original Message----- > From: Dejan Muhamedagic > Sent: Monday, March 9, 2020 23:06 > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] oam address > > Hi, > > Changing the OAM IP address did work, sort of, but there is a problem > with some certificate which apparently needs to be recreated. > Applications cannot be applied anymore: > > > platform-integ-apps | 1.0-8 | platform- > integration-manifest | manifest.yaml | apply-failed | Deployment > of application platform-integ-apps (1.0-8) failed: failed to download > one or more image(s). | > > The error message I found in sysinv.log: > > sysinv 2020-03-09 14:57:45.903 83083 ERROR sysinv.conductor.kube_app > [-] Image registry.local:9001/docker.io/starlingx/ceph-config- > helper:v1.15.0 dow > nload failed from local registry: 500 Server Error: Internal Server > Error ("Get > https://registry.local:9001/v2/docker.io/starlingx/ceph-config-helper/manifests/ > v1.15.0: Get > https://10.107.8.255:9002/token/?account=admin&scope=repository%3Ad > ocker.io%2Fstarlingx%2Fceph-config- > helper%3Apull&service=192.168.204.1%3A9001: x > 509: certificate is valid for 192.168.204.1, 10.107.10.21, not > 10.107.8.255"): A > PIError: 500 Server Error: Internal Server Error ("Get > https://registry.local:90 > 01/v2/docker.io/starlingx/ceph-config-helper/manifests/v1.15.0: Get > https://10.1 > 07.8.255:9002/token/?account=admin&scope=repository%3Adocker.io%2Fsta > rl > ingx%2Fce > ph-config-helper%3Apull&service=192.168.204.1%3A9001: x509: > certificate is valid for 192.168.204.1, 10.107.10.21, not > 10.107.8.255") > > (Sorry about the formatting!) > > The OAM IP address changed from 10.107.10.21/22 to 10.107.8.255/22. > > Is it possible to fix this? > > Best regards, > > Dejan > > > On Mon, 2020-02-24 at 15:05 +0000, Winnicki, Chris wrote: > > Hi Dejan > > > > It's absolutely possible to change the OAM IP address after the > > installation is completed. > > * One thing to watch out for is make sure that: > > 1) oam_gateway_ip is updated if you're changing networks > > 2) That your machine (which you're using to access the StarlinX > > system) can route to the new network (in case the networks were > > changed) > > > > > > Regards, > > > > Chris Winnicki > > chris.winnicki at windriver.com > > 613-963-1329 > > ________________________________________ > > From: Dejan Muhamedagic [dejan.muhamedagic at tttech-industrial.com] > > Sent: Monday, February 24, 2020 9:48 AM > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] oam address > > > > Hi, > > > > Is it possible to change the OAM IP address after the installation? > > There is a "system oam-modify", but the installation guide warns: > > > > "Some Ansible bootstrap parameters cannot be changed or are very > > difficult to change after installation is complete." > > > > The reason I'm asking is that this installation may have to run in > > different environments and possibly in different networks. > > > > Thanks, > > > > Dejan > > > > CONFIDENTIALITY: The contents of this e-mail are confidential and > > intended only for the above addressee(s). If you are not the > > intended > > recipient, or the person responsible for delivering it to the > > intended > > recipient, copying or delivering it to anyone else or using it in > > any > > unauthorized manner is prohibited and may be unlawful. If you > > receive > > this e-mail by mistake, please notify the sender and the systems > > administrator at straymail at tttech.com immediately. > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > CONFIDENTIALITY: The contents of this e-mail are confidential and > intended only for the above addressee(s). If you are not the intended > recipient, or the person responsible for delivering it to the > intended recipient, copying or delivering it to anyone else or using > it in any unauthorized manner is prohibited and may be unlawful. If > you receive this e-mail by mistake, please notify the sender and the > systems administrator at straymail at tttech.com immediately. > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail at tttech.com immediately. From zhipengs.liu at intel.com Tue Mar 10 13:00:22 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 10 Mar 2020 13:00:22 +0000 Subject: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images In-Reply-To: <93814834B4855241994F290E959305C75314D262@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C75314CC61@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314D245@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314D262@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C75314D9F9@SHSMSX104.ccr.corp.intel.com> Hi Don, Chant and I already fixed this issue and other related dependent packages. We modified docker file and related script for wheel build, and rebuilt out all python3 wheels for the packages in stable-wheels.cfg. As for libvirt-python, we still use 4.7.0 version and rebuilt out python3 wheel currently. Will let you know the status after finishing all image build. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 0:06 To: 'Liu, ZhipengS' ; Penney, Don ; YuChengDe ; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images We also had below issue during build other service image. Looking in links: /tmp/wheels/ Collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) Collecting PyMySQL===0.9.3 Downloading PyMySQL-0.9.3-py2.py3-none-any.whl (47 kB) Processing /tmp/wheels/python_memcached-1.59-py2.py3-none-any.whl Collecting six===1.14.0 Downloading six-1.14.0-py2.py3-none-any.whl (10 kB) Collecting cffi===1.14.0 Downloading cffi-1.14.0-cp36-cp36m-manylinux1_x86_64.whl (399 kB) ERROR: Could not find a version that satisfies the requirement uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) (from versions: none) ERROR: No matching distribution found for uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) Actually, we get uWSGI-2.0.17.1-cp27-cp27mu-linux_x86_64.whl through the link in stable-config file. So far, not sure how many python3 packages we need. From: Liu, ZhipengS > Sent: 2020年3月9日 23:44 To: Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: Re: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! See my inline comments. From: Penney, Don > Sent: 2020年3月9日 23:18 To: Liu, ZhipengS >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I think building the openstack master branch will require moving the images to python3. This has implications to the base image, to how we build the base wheels tarball, and possibly to arguments passed to loci (as well as moving to a newer loci SHA). >> Yes, we have to set python3 = true to loci and also fix a small known bug. I believe Al started looking at this last week, but got pulled off to look at some other issues. From your reply, it sounds like maybe you’ve also done some of this? >> Yes When we explicitly add wheels to the tarball, we update the upper-constraints file to align with the module we’ve included. This would be why the build is looking for 4.7.0 here. There is an upper-constraints.txt file in the tarball itself which you can check. >> Yes, in our script, if we have 4.7.0 in stx repo, it will change the version to 4.7.0 from other versions specified in upper-constraints.txt The libvirt wheel building is python2 only, currently. So it would need to be built for python3 - if that’s possible for 4.7.0. If a newer version of libvirt-python is needed for python3 support, then it will need to be updated. I don’t know how big that effort will be. >> From code, libvirt-python 4.7.0 can support both python2 and python3, but in our code, we just add patch to let it build out python2 whl. >> libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, March 05, 2020 1:06 AM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Penney, We just used OpenStack master branch and upper-constraint file below https://raw.githubusercontent.com/openstack/requirements/master/upper-constraints.txt libvirt-python===5.10.0;python_version=='2.7' libvirt-python===6.0.0;python_version=='3.6' libvirt-python===6.0.0;python_version=='3.7' In nova setup.cfg. it adds python require info. python-requires = >=3.6 Then we built python3 related packages to the base image and rebuilt nova image to fix python3 issue. But there is still an error below. collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) ERROR: Could not find a version that satisfies the requirement libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) (from versions: none) ERROR: No matching distribution found for libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 From code, I saw that we already built libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl through a patch which Seems related to python2. cgcs-root/stx/integ/virt/libvirt-python/centos/meta_patches$ 0002-Build-python-wheel.patch It needs libvirt-python whl for python3, right? Do we have plan to upgrade libvirt-python to 6.0.0? Any comment? Thanks a lot! Zhipeng From: Penney, Don > Sent: 2020年2月27日 0:25 To: YuChengDe >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I was able to successfully build stx-nova image in master with no changes. Do you have any customizations in your environment? From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 26, 2020 10:38 AM To: YuChengDe; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 [Image removed by sender.] -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From yang.liu at windriver.com Tue Mar 10 13:04:29 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Tue, 10 Mar 2020 13:04:29 +0000 Subject: [Starlingx-discuss] Pytest tests from WindRiver In-Reply-To: References: <19C65A6E92EA384D809B1772130CD7F8693CEB13@ALA-MBD.corp.ad.wrs.com> Message-ID: Good point Dariush. Nicolae, We will have a stx testing meeting today at 8am PT, and you can either bring up the questions there or through mailing list. Thanks, Yang From: Eslimi, Dariush [mailto:Dariush.Eslimi at windriver.com] Sent: March-09-20 12:56 PM To: Liu, Yang (YOW); Jascanu, Nicolae; starlingx-discuss at lists.starlingx.io Subject: RE: Pytest tests from WindRiver To follow the spirit of four open : https://governance.openstack.org/tc/reference/opens.html Please keep this communication in the mailing list, as this could benefits the whole community. Thanks, Dariush From: Liu, Yang (YOW) [mailto:yang.liu at windriver.com] Sent: March-09-20 12:34 PM To: Jascanu, Nicolae ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Pytest tests from WindRiver Hi Nicolae, You can forward the questions to myself, and I will help distribute to other folks if needed. Thanks, Yang From: Jascanu, Nicolae [mailto:nicolae.jascanu at intel.com] Sent: March-09-20 4:43 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Pytest tests from WindRiver Hi All, As a Validation Team we need to convert the Validation robot tests into pytest specific tests. We have several questions regarding the pytests and the workflows for committing those tests. We need some contact persons to talk about these. Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From yang.liu at windriver.com Tue Mar 10 15:07:47 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Tue, 10 Mar 2020 15:07:47 +0000 Subject: [Starlingx-discuss] Weekly StarlingX Test meeting In-Reply-To: <19C65A6E92EA384D809B1772130CD7F8693CEE38@ALA-MBD.corp.ad.wrs.com> References: <19C65A6E92EA384D809B1772130CD7F8693CEE38@ALA-MBD.corp.ad.wrs.com> Message-ID: Sorry for the inconvenience. Please use following zoom for today's test meeting. Topic: STX-Test Meeting - 03/10 Time: Mar 10, 2020 11:00 AM Eastern Time (US and Canada) Join Zoom Meeting https://windriver.zoom.us/j/677538858 Meeting ID: 677 538 858 -------------- next part -------------- An HTML attachment was scrubbed... URL: From yu.chengde at 99cloud.net Tue Mar 10 15:51:08 2020 From: yu.chengde at 99cloud.net (YuChengDe) Date: Tue, 10 Mar 2020 23:51:08 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?=5BOpenStack_Upgrade=5D_Built_the_m?= =?utf-8?q?aster_branch_of_stx-heat?= Message-ID: Hi: I have built a stx-heat image for moving a new version of OpensStack in StarlingX. Welcome to apply image into your system. If there is any problem during usage, please let me know. Many thanks. Note: Get the image from docker hub P.S.: tag = [git branch]-[based on python3 or python2 built environment]-[image created day] docker pull chantyu/stx-heat:master-python3-20200310 PROJECT_REPO= https://opendev.org/openstack/heat.git PROJECT_REF= master BUILDER= loci -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Tue Mar 10 16:09:27 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 10 Mar 2020 16:09:27 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Mar 11, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007BABEB5@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of tomorrow's TSC/Community call. *** Note that since NA has moved to EDT, the start time may change for you - please check [2] *** *** @Distro non-Openstack team - I believe we currently have a conflict - I'm open to ideas on how to resolve it. *** We'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200311T1400 From yang.liu at windriver.com Tue Mar 10 16:35:23 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Tue, 10 Mar 2020 16:35:23 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 03/10/2020 Message-ID: Agenda/meeting notes are posted here: https://etherpad.openstack.org/p/stx-test Agenda for 03/10/2020 Attendees: Yang, George P, Mihail, Nicolae, Chris, Alex, Oliver, Ruediger, Cosmin 1. Sanity Status: * Some issues on layered build when provisioning stx - Mihail will follow up and investigate further * https://bugs.launchpad.net/starlingx/+bug/1855474 - OpenStack pods were not recovered after force reboot active controller 2. stx4.0 Testing * Feature testing: * Feature test owner discussed and identified: * https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=0 * Feature test plan can be uploaded to stx test repo in rst format or in shared google docs * Regression testing: * Will discuss in next meeting. * Other activities: * Regression Test Automation ? * Based on Bruce, the goal is to automate regression test cases as much as possible. * Low priority for Intel for now until Nicolae's team caught up on other priorities. * WR plans to automate some regression test cases in Q1. Target on ~30 test cases cross 4-5 areas. * Performance Test Automation ? * Existing documents from Ada's team on how to run performance test manually. * No automation is done yet. * Nicolae's team will try to share the documents with community first. 3. Unified Sanity * Getting some help from Ada's team. Running on Ada's hardware using robot framework. * Converting robot tests to pytest with the goal to upload the changes in stx pytest repo * Started from Jose's existing work in another repo that was built off stx pytest * pytest link: * https://opendev.org/starlingx/test/src/branch/master/automated-pytest-suite * According to Jose, some existing test cases will fail with his change * Could use feature branch to make the changes available to community before merging to master 4. Opens * Test documents location * https://opendev.org/starlingx/test/src/branch/master/doc/source/manual_tests * Manual test plan only * https://drive.google.com/drive/folders/1nab5AW18HIxpbkjAR6-dwk-kt1rv_8HQ * Manual test plan * Milestone testing - execution status * Any other testing related documents -------------- next part -------------- An HTML attachment was scrubbed... URL: From mihail-laurentiu.trica at intel.com Tue Mar 10 16:41:38 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Tue, 10 Mar 2020 16:41:38 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build - ISO 20200309 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-09 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers – 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 ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard configuration on bare metal and standard external on virtual environment tests failed because of an existing bug https://bugs.launchpad.net/starlingx/+bug/1856078. We removed those tests from the report. Regards, STX Validation Team Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From mihail-laurentiu.trica at intel.com Tue Mar 10 16:56:26 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Tue, 10 Mar 2020 16:56:26 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200310 - LAYERED BUILD Message-ID: Status of the Sanity Test for last LAYERED BUILD - CENGN ISO: bootimage.iso from 2020-March-10 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200310T095731Z/outputs/iso/) Status: RED =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO - Simplex Setup 04 TCs [BLOCKED] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [BLOCKED] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] The bug that was created for the issue with Simplex and Duplex is still reproducible with the latest build: https://bugs.launchpad.net/starlingx/+bug/1864221. Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Mar 10 18:02:19 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 10 Mar 2020 18:02:19 +0000 Subject: [Starlingx-discuss] Customer question: CoroSync Message-ID: <9A85D2917C58154C960D95352B22818BF168F23C@fmsmsx123.amr.corp.intel.com> I had a call with part of our field team today, and they asked if we have ever looked into Corosync as an HA framework. And if we have any data on how it compares to the Service Manager within StarlingX. There is some basic background on Corosync here: https://en.wikipedia.org/wiki/Corosync_Cluster_Engine. Has anyone ever looked into this technology? Are we using it? brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jerry.Sun at windriver.com Tue Mar 10 20:10:59 2020 From: Jerry.Sun at windriver.com (Sun, Yicheng (Jerry)) Date: Tue, 10 Mar 2020 20:10:59 +0000 Subject: [Starlingx-discuss] stx docs input:2006711 Message-ID: Hi All, We have just added the ability to configure oidc auth related parameters post-bootstrap: system service-parameter-add kubernetes kube_apiserver oidc_client_id=value system service-parameter-add kubernetes kube_apiserver oidc_groups_claim=value system service-parameter-add kubernetes kube_apiserver oidc_issuer_url=value system service-parameter-add kubernetes kube_apiserver oidc_username_claim=value they used to be configurable only at boostrap time in localhost.yml: apiserver_oidc: client_id: stx-oidc-client-app issuer_url: https://:30556/dex username_claim: email groups_claim: group Apply the service parameters with "system service-parameter-apply kubernetes", or no changes will take place. The valid configurations for the service parameters are the same as during bootstrap: none of the parameters or oidc_issuer_url, oidc_client_id, oidc_username_claim or the above 3 and oidc_groups_claim Thanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: From yu.chengde at 99cloud.net Wed Mar 11 11:00:37 2020 From: yu.chengde at 99cloud.net (YuChengDe) Date: Wed, 11 Mar 2020 19:00:37 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?=5BOpenStack_Upgrade=5D_Built_the_m?= =?utf-8?q?aster_branch_of_stx-opesntack?= Message-ID: Hi: I have built a stx-nova ; stx-keystone ; stx-neutron ; stx-placement ; stx-aodh ; stx-ironic ; stx-panko ; stx-barbican ; stx-ceilometer image for moving a new version of OpensStack in StarlingX. Welcome to apply image into your system. If there is any problem during usage, please let me know. Many thanks. Note: Get the image from docker hub P.S.: tag = [git branch]-[based on python3 or python2 built environment]-[image created day] docker pull chantyu/stx-nova:master-python3-20200310 docker pull chantyu/stx-keystone:master-python3-20200310 docker pull chantyu/stx-neutron:master-python3-20200310 docker pull chantyu/stx-placement:master-python3-20200310 docker pull chantyu/stx-aodh:master-python3-20200310 docker pull chantyu/stx-ironic:master-python3-20200310 docker pull chantyu/stx-panko:master-python3-20200310 docker pull chantyu/stx-barbican:master-python3-20200310 docker pull chantyu/stx-ceilometer:master-python3-20200310 PROJECT_REF= master BUILDER= loci -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dariush.Eslimi at windriver.com Wed Mar 11 12:51:03 2020 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Wed, 11 Mar 2020 12:51:03 +0000 Subject: [Starlingx-discuss] Customer question: CoroSync In-Reply-To: <9A85D2917C58154C960D95352B22818BF168F23C@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BF168F23C@fmsmsx123.amr.corp.intel.com> Message-ID: I believe we have looked at it initially but that is before my time in this project and I have no data to share. Thanks, Dariush P.S: Did you scan the link for virus before clicking on the link, it starts with Coro? From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: March-10-20 2:02 PM To: Eslimi, Dariush ; Rowsell, Brent Cc: starlingx-discuss at lists.starlingx.io Subject: Customer question: CoroSync I had a call with part of our field team today, and they asked if we have ever looked into Corosync as an HA framework. And if we have any data on how it compares to the Service Manager within StarlingX. There is some basic background on Corosync here: https://en.wikipedia.org/wiki/Corosync_Cluster_Engine. Has anyone ever looked into this technology? Are we using it? brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Mar 11 14:40:45 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 11 Mar 2020 14:40:45 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Mar 11, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007BAC494@ALA-MBD.corp.ad.wrs.com> >From today's call... * Standing Topics * Sanity * nice touch indicating MONOLITHIC or LAYERED in the sanity report subject * all green until 20200310 - LAYERED BUILD * report http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/007977.html * issue is https://bugs.launchpad.net/starlingx/+bug/1864221, the fix seems to be understood, targeting a fix in a day or so * Reviews * nothing this week * CentOS 8 * focus on kernel upgrade now * some new patches sent for review today * need some help testing out of tree driver updates - on specific hardware - Austin will bring details to the Test & Networking teams * Topics for this Week * key readouts from the mid-cycle meetup last week? * https://etherpad.openstack.org/p/starlingX-winter-2020-meetup * Dariush mentioned a couple of actions he took from the meeting * Upgrades Spec: this is in progress, John Kung authoring * Upgrades Storyboard: this has been created * Ildiko is working up a blog post * DST switch (ildikov) * Do we still want to stick to the US time slots? * we agreed to stick with the current slots * Mary Camp - Docs team * taking over for the Docs sub-project from Kristal Dale * Open Requests for Help * nothing this week -----Original Message----- From: Zvonar, Bill Sent: Tuesday, March 10, 2020 12:09 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: Community (& TSC) Call (Mar 11, 2020) Hi all, reminder of tomorrow's TSC/Community call. *** Note that since NA has moved to EDT, the start time may change for you - please check [2] *** *** @Distro non-Openstack team - I believe we currently have a conflict - I'm open to ideas on how to resolve it. *** We'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200311T1400 From ildiko.vancsa at gmail.com Wed Mar 11 14:57:36 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 11 Mar 2020 15:57:36 +0100 Subject: [Starlingx-discuss] Project confirmation review Message-ID: <1098851F-AF29-4AB3-A66C-176CFCE9231C@gmail.com> Hi StarlingX Community, The project is reaching the point in its lifecycle where it can apply to become a confirmed project supported by the OpenStack Foundation. Becoming a confirmed project has a list of criteria to comply with that will be reviewed by several groups including the OSF Board of Directors. You can check the process description here: https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmationGuidelines The current plan is to target the board meeting scheduled co-located with the Vancouver event in June for the review with asking the board to allow for a pre-review meeting that has been the precedent with some other projects earlier which can ensure that the community can address questions or concerns if there is any by the final review. Before arranging the reviews I would like to make sure that no one has any objections against going through the process with the above timeline. Please reply to this thread if you have any objections towards the timeline __by the end of this week__. I will make steps to set up the schedule early next week if there are no unresolved comments or objections. Please let me know if you have any questions. Thanks, Ildikó From km.giuseppesannino at gmail.com Wed Mar 11 15:56:37 2020 From: km.giuseppesannino at gmail.com (Giuseppe Sannino) Date: Wed, 11 Mar 2020 16:56:37 +0100 Subject: [Starlingx-discuss] Stx 3.0 Distributed Cloud - "platform-integ-apps" apply-filed Message-ID: Hi all, I need a small support from you. I'm trying to deploy a StarlingX 3.0 Distributed Cloud. The idea is to go for the following configuration: System Controller: Baremetal AIO Duplex Subcloud: AIO Simplex I'm facing an issue during the bootstrap of controller-1. The installation of controller-1 proceeds slowly but pretty fine till the procedure tries to apply the "platform-integ-apps" application. [sysadmin at controller-0 ~(keystone_admin)]$ system application-list +---------------------+---------+-------------------------------+---------------+--------------+------------------------------------------+ | application | version | manifest name | manifest file | status | progress | +---------------------+---------+-------------------------------+---------------+--------------+------------------------------------------+ | platform-integ-apps | 1.0-8 | platform-integration-manifest | manifest.yaml | apply-failed | operation aborted, check logs for detail | +---------------------+---------+-------------------------------+---------------+--------------+------------------------------------------+ Looking at the sysinv.log I notice the following error: sysinv 2020-03-11 15:43:13.643 134388 ERROR sysinv.openstack.common.periodic_task [-] Error during ConductorManager._conductor_audit: HTTPSConnectionPool(host='192.168.206.1', port=6443): Max retries exceeded with url: /api/v1/nodes (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] ECONNREFUSED',)): MaxRetryError: HTTPSConnectionPool(host='192.168.206.1', port=6443): Max retries exceeded with url: /api/v1/nodes (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] ECONNREFUSED',)) 2020-03-11 15:43:13.643 134388 ERROR sysinv.openstack.common.periodic_task Traceback (most recent call last): : : omitted : 20-03-11 15:43:13.643 134388 ERROR sysinv.openstack.common.periodic_task raise MaxRetryError(_pool, url, error or ResponseError(cause)) 2020-03-11 15:43:13.643 134388 ERROR sysinv.openstack.common.periodic_task MaxRetryError: HTTPSConnectionPool(host='192.168.206.1', port=6443): Max retries exceeded with url: /api/v1/nodes (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] ECONNREFUSED',)) >From controller-0 I can succesfully ping 192.168.206.1. It seems more a problem with some certificates. May I ask some guide/suggestion for addressing this issue ? Many thanks in advance /Giuseppe -------------- next part -------------- An HTML attachment was scrubbed... URL: From mihail-laurentiu.trica at intel.com Wed Mar 11 16:05:38 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Wed, 11 Mar 2020 16:05:38 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build - ISO 20200311 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-11 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers – 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 ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Duplex configuration on bare metal tests failed because of an existing bug 1856078 and this is the reason we do not have results for it with today’s build. Regards, STX Validation Team Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joseph.Richard at windriver.com Wed Mar 11 21:05:56 2020 From: Joseph.Richard at windriver.com (Richard, Joseph) Date: Wed, 11 Mar 2020 21:05:56 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. In-Reply-To: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> Message-ID: I see a similar issue online here: https://groups.google.com/forum/#!topic/rabbitmq-users/9ir1WK-nYBA [http://www.google.com/images/icons/product/groups-128.png] epmd fails to start in IPv6 environment Posted 7/15/19 9:43 PM, 12 messages groups.google.com I expect that you are going to have to update rabbmitmq docker images to 3.7.16(currently 3.7.13), and then modify the helm plugin to pass in these values when using ipv6: SERVER_ADDITIONAL_ERL_ARGS='-proto_dist inet6_tcp' CTL_ERL_ARGS='-proto_dist inet6_tcp' Not sure if this is possible right now, or if you will need to modify openstack-helm-infra/rabbitmq in order to be able to pass these environment variables in. ________________________________ From: Liu, ZhipengS Sent: Thursday, February 27, 2020 8:00 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi all, For below LP IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status" https://bugs.launchpad.net/starlingx/+bug/1859641 I provided a patch which can fix the known issue in LP. However, it still failed later when starting rabbitmq pod. controller-0:~$ kubectl -n openstack get po NAME READY STATUS RESTARTS AGE ingress-c74489c96-jsb7n 1/1 Running 0 17h ingress-error-pages-5889bfcf6c-h8kl6 1/1 Running 0 17h mariadb-ingress-b5cd65f4b-sq46c 1/1 Running 0 17h mariadb-ingress-error-pages-6d8b79b74f-9zmpc 1/1 Running 0 17h mariadb-server-0 1/1 Running 0 17h osh-openstack-memcached-memcached-545668bdbd-9jkv2 1/1 Running 0 17h osh-openstack-rabbitmq-cluster-wait-wbnwp 0/1 Init:0/2 0 17h osh-openstack-rabbitmq-rabbitmq-0 0/1 CrashLoopBackOff 207 17h There are below error logs 2020-02-26T07:43:36.451103975Z stderr F ++ echo osh-openstack-rabbitmq-rabbitmq-0 2020-02-26T07:43:36.45142814Z stderr F ++ awk -F - '{print $NF}' 2020-02-26T07:43:36.454160452Z stderr F + POD_INCREMENT=0 2020-02-26T07:43:36.454757022Z stderr F + '[' 0 -eq 0 ']' 2020-02-26T07:43:36.454795721Z stderr F + exec rabbitmq-server 2020-02-26T07:43:36.849021551Z stdout F ERROR: epmd error for host osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local: nxdomain (non-existing domain) In /etc/hosts file below, I just found localhost4, no localhost6. Is it expected? I added below line manually after the line of 127.0.0.1. However, it didn’t work☹ ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 # HEADER: This file was autogenerated at 2020-02-26 09:00:35 +0000 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 fd01::1 controller 169.254.202.1 pxecontroller fd00::3 oamcontroller fd01::4 controller-platform-nfs fd01::3 controller-1 fd01::2 controller-0 fd02::3 controller-1-cluster-host fd02::2 controller-0-cluster-host fd01::e8b6:66fe storage-0 I saw that in ./stx-puppet/puppet-manifests/src/modules/platform/manifests/config.pp:215 class platform::config::hosts inherits ::platform::config::params { # The localhost should resolve to the IPv4 loopback address only, therefore # ensure the IPv6 address is removed from configured hosts resources { 'host': purge => true } $localhost = { 'localhost' => { ip => '127.0.0.1', host_aliases => ['localhost.localdomain', 'localhost4', 'localhost4.localdomain4'] }, } $merged_hosts = merge($localhost, $hosts) create_resources('host', $merged_hosts, {}) } Any one can give some help? Thanks! Zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Wed Mar 11 21:33:27 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Wed, 11 Mar 2020 21:33:27 +0000 Subject: [Starlingx-discuss] StarlingX docs team - new addition Message-ID: Hello All, Following up to the community call this morning, I wanted to introduce the newest member of the docs team: Mary Camp! Mary has previously contributed to the StarlingX docs and I have worked with her on other Intel projects - she's a great addition to the team. This will be my last week on the StarlingX docs project - it has been a great experience working with you all! And, starting this week Mary will be taking my place on the docs team. Any questions, issues, etc. that were previously directed to me should now be directed to Mary. Thanks everyone - and welcome Mary! Cheers, Kris -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Mar 11 21:46:48 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 11 Mar 2020 21:46:48 +0000 Subject: [Starlingx-discuss] StarlingX docs team - new addition In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BF169117C@fmsmsx123.amr.corp.intel.com> Kris, thank you so much for all of your contributions to StarlingX. Thanks to your efforts, the project has made enormous progress in the quality of our documentation. Your can-do attitude, your drive and your passion are a joy to be around. You will be missed! brucej From: Dale, Kristal [mailto:kristal.dale at intel.com] Sent: Wednesday, March 11, 2020 2:33 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX docs team - new addition Hello All, Following up to the community call this morning, I wanted to introduce the newest member of the docs team: Mary Camp! Mary has previously contributed to the StarlingX docs and I have worked with her on other Intel projects - she's a great addition to the team. This will be my last week on the StarlingX docs project - it has been a great experience working with you all! And, starting this week Mary will be taking my place on the docs team. Any questions, issues, etc. that were previously directed to me should now be directed to Mary. Thanks everyone - and welcome Mary! Cheers, Kris -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.a.cobbley at intel.com Wed Mar 11 23:44:36 2020 From: david.a.cobbley at intel.com (Cobbley, David A) Date: Wed, 11 Mar 2020 23:44:36 +0000 Subject: [Starlingx-discuss] StarlingX docs team - new addition Message-ID: <387E6828-2F10-4815-86E9-44E61E5F9847@intel.com> I second that; your work has been amazing, and the team will miss you! -- David C From: "Jones, Bruce E" Date: Wednesday, March 11, 2020 at 2:48 PM To: "Dale, Kristal" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] StarlingX docs team - new addition Kris, thank you so much for all of your contributions to StarlingX. Thanks to your efforts, the project has made enormous progress in the quality of our documentation. Your can-do attitude, your drive and your passion are a joy to be around. You will be missed! brucej From: Dale, Kristal [mailto:kristal.dale at intel.com] Sent: Wednesday, March 11, 2020 2:33 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX docs team - new addition Hello All, Following up to the community call this morning, I wanted to introduce the newest member of the docs team: Mary Camp! Mary has previously contributed to the StarlingX docs and I have worked with her on other Intel projects – she’s a great addition to the team. This will be my last week on the StarlingX docs project – it has been a great experience working with you all! And, starting this week Mary will be taking my place on the docs team. Any questions, issues, etc. that were previously directed to me should now be directed to Mary. Thanks everyone – and welcome Mary! Cheers, Kris -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Thu Mar 12 01:52:30 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 12 Mar 2020 01:52:30 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. In-Reply-To: References: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C75314F6B2@SHSMSX104.ccr.corp.intel.com> Hi Joseph, Thank you so much! 😊 I will work further based on your provided clue. Best Regards, Zhipeng From: Richard, Joseph Sent: 2020年3月12日 5:06 To: Liu, ZhipengS ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. I see a similar issue online here: https://groups.google.com/forum/#!topic/rabbitmq-users/9ir1WK-nYBA [http://www.google.com/images/icons/product/groups-128.png] epmd fails to start in IPv6 environment Posted 7/15/19 9:43 PM, 12 messages groups.google.com I expect that you are going to have to update rabbmitmq docker images to 3.7.16(currently 3.7.13), and then modify the helm plugin to pass in these values when using ipv6: SERVER_ADDITIONAL_ERL_ARGS='-proto_dist inet6_tcp' CTL_ERL_ARGS='-proto_dist inet6_tcp' Not sure if this is possible right now, or if you will need to modify openstack-helm-infra/rabbitmq in order to be able to pass these environment variables in. ________________________________ From: Liu, ZhipengS > Sent: Thursday, February 27, 2020 8:00 AM To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi all, For below LP IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status" https://bugs.launchpad.net/starlingx/+bug/1859641 I provided a patch which can fix the known issue in LP. However, it still failed later when starting rabbitmq pod. controller-0:~$ kubectl -n openstack get po NAME READY STATUS RESTARTS AGE ingress-c74489c96-jsb7n 1/1 Running 0 17h ingress-error-pages-5889bfcf6c-h8kl6 1/1 Running 0 17h mariadb-ingress-b5cd65f4b-sq46c 1/1 Running 0 17h mariadb-ingress-error-pages-6d8b79b74f-9zmpc 1/1 Running 0 17h mariadb-server-0 1/1 Running 0 17h osh-openstack-memcached-memcached-545668bdbd-9jkv2 1/1 Running 0 17h osh-openstack-rabbitmq-cluster-wait-wbnwp 0/1 Init:0/2 0 17h osh-openstack-rabbitmq-rabbitmq-0 0/1 CrashLoopBackOff 207 17h There are below error logs 2020-02-26T07:43:36.451103975Z stderr F ++ echo osh-openstack-rabbitmq-rabbitmq-0 2020-02-26T07:43:36.45142814Z stderr F ++ awk -F - '{print $NF}' 2020-02-26T07:43:36.454160452Z stderr F + POD_INCREMENT=0 2020-02-26T07:43:36.454757022Z stderr F + '[' 0 -eq 0 ']' 2020-02-26T07:43:36.454795721Z stderr F + exec rabbitmq-server 2020-02-26T07:43:36.849021551Z stdout F ERROR: epmd error for host osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local: nxdomain (non-existing domain) In /etc/hosts file below, I just found localhost4, no localhost6. Is it expected? I added below line manually after the line of 127.0.0.1. However, it didn’t work☹ ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 # HEADER: This file was autogenerated at 2020-02-26 09:00:35 +0000 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 fd01::1 controller 169.254.202.1 pxecontroller fd00::3 oamcontroller fd01::4 controller-platform-nfs fd01::3 controller-1 fd01::2 controller-0 fd02::3 controller-1-cluster-host fd02::2 controller-0-cluster-host fd01::e8b6:66fe storage-0 I saw that in ./stx-puppet/puppet-manifests/src/modules/platform/manifests/config.pp:215 class platform::config::hosts inherits ::platform::config::params { # The localhost should resolve to the IPv4 loopback address only, therefore # ensure the IPv6 address is removed from configured hosts resources { 'host': purge => true } $localhost = { 'localhost' => { ip => '127.0.0.1', host_aliases => ['localhost.localdomain', 'localhost4', 'localhost4.localdomain4'] }, } $merged_hosts = merge($localhost, $hosts) create_resources('host', $merged_hosts, {}) } Any one can give some help? Thanks! Zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From ran1.an at intel.com Thu Mar 12 06:18:36 2020 From: ran1.an at intel.com (An, Ran1) Date: Thu, 12 Mar 2020 06:18:36 +0000 Subject: [Starlingx-discuss] [Python3] Analysis of nfv using python3 Message-ID: <9BAB5B7CAF57C3459E4636391F1071CE053A1249@shsmsx102.ccr.corp.intel.com> Hi all: I’m working on task “upgrade project nfv to support python3 runtime env”. By analyzing and testing, there will be 32 new python3 rpms, which may impact current system. · 16 new rpms from official centos7 repo; · 12 new stx-rpms rebuilt with srpms from official centos7 repo (turn on python3 supported switch in spec); · 4 stx-rpms built from tar.gz files. Details including pkg dependency trees and current status could be found in [1] With patches [2], we could get an iso with nfv services (vim,vim-api, vim-webserver) running in python3. However, there is an run-time issues. Model “fm_api” in python3 is required to support vim service reporting alarms/event_logs to fault manager (service fm-mgr). It brings following issues: 1. to build python3 "fm-api" rpm, pkg “python3-rpm-generators” is required. But it is conflict with pkg “rpm-build” built in the compile layer, because both of them have file (/usr/lib/rpm/pythondistdeps.py). 2. as other flock services, like sysinv, are still running in python2, so it require fm-api to both run in python2 env and python3 env. It introduces a new topic: ensure it is safe to run python2-fm-api and python3-fm-api at the same time. The scope of this task seems expand. Is there any suggestions? [1] https://bugs.launchpad.net/starlingx/+bug/1808073/+attachment/5335996/+files/nfv%20python%20dependency%20analysis.xlsx [2] patches: https://review.opendev.org/709958; https://review.opendev.org/709960; https://review.opendev.org/709983/1 ; https://review.opendev.org/709980 Thanks Ran -------------- next part -------------- An HTML attachment was scrubbed... URL: From mingyuan.qi at intel.com Thu Mar 12 08:17:43 2020 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Thu, 12 Mar 2020 08:17:43 +0000 Subject: [Starlingx-discuss] oam address In-Reply-To: References: <737e35859c115f6a9511a95677a1f9161cbfb68a.camel@tttech-industrial.com> <7E4792BA14B1DE4BAB354DF77FE0233AC4376097@ALA-MBD.corp.ad.wrs.com> <96a200331d5aa269a0291094b2035d7119a41f36.camel@tttech-industrial.com> Message-ID: Hi Dejan, In simplex mode, mgmt network is assigned to loopback(lo), you can check with " system addrpool-list" and "ip a". The dns resolve is ok, You will need to add the new oam ip as a new SAN to /etc/docker/certs.d/registry.local:9001/registry-cert.crt Hi Tee, I saw a potential issue in registry service config file, /etc/docker-distribution/registry/config.yaml auth: token: realm: "xxx/token" It is set to https://{oam ip}/token, not {mgmt ip}, is it expected? Mingyuan -----Original Message----- From: Dejan Muhamedagic Sent: Tuesday, March 10, 2020 16:50 To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] oam address Hi, There's no mgmt, I guess because this is a simplex all-in-one installation. Here's the output from nslookup: controller-0:~$ nslookup mgmt Server:192.168.204.1 Address:192.168.204.1#53 ** server can't find mgmt: NXDOMAIN controller-0:~$ grep mgmt /etc/hosts controller-0:~$ nslookup registry.local Server:192.168.204.1 Address:192.168.204.1#53 registry.localcanonical name = controller. Name:controller Address: 192.168.204.1 The internal server error suggests that the registry itself gets offended by the new IP address. Thanks, Dejan On Tue, 2020-03-10 at 02:35 +0000, Qi, Mingyuan wrote: > Dejan, > > This issue is caused by new oam ip missing in registry/registry token > server certificate SAN. > But...normally the registry.local is resolved to mgmt ip which will > not trigger this issue. From the log, it seems registry.local was > resolved to oam ip. > Better to check /etc/hosts and "nslookup registry.local" output. > > Mingyuan > > -----Original Message----- > From: Dejan Muhamedagic > Sent: Monday, March 9, 2020 23:06 > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] oam address > > Hi, > > Changing the OAM IP address did work, sort of, but there is a problem > with some certificate which apparently needs to be recreated. > Applications cannot be applied anymore: > > > platform-integ-apps | 1.0-8 | platform- > integration-manifest | manifest.yaml | apply-failed | Deployment > of application platform-integ-apps (1.0-8) failed: failed to download > one or more image(s). | > > The error message I found in sysinv.log: > > sysinv 2020-03-09 14:57:45.903 83083 ERROR sysinv.conductor.kube_app > [-] Image registry.local:9001/docker.io/starlingx/ceph-config- > helper:v1.15.0 dow > nload failed from local registry: 500 Server Error: Internal Server > Error ("Get > https://registry.local:9001/v2/docker.io/starlingx/ceph-config-helper/ > manifests/ > v1.15.0: Get > https://10.107.8.255:9002/token/?account=admin&scope=repository%3Ad > ocker.io%2Fstarlingx%2Fceph-config- > helper%3Apull&service=192.168.204.1%3A9001: x > 509: certificate is valid for 192.168.204.1, 10.107.10.21, not > 10.107.8.255"): A > PIError: 500 Server Error: Internal Server Error ("Get > https://registry.local:90 > 01/v2/docker.io/starlingx/ceph-config-helper/manifests/v1.15.0: Get > https://10.1 > 07.8.255:9002/token/?account=admin&scope=repository%3Adocker.io%2Fsta > rl > ingx%2Fce > ph-config-helper%3Apull&service=192.168.204.1%3A9001: x509: > certificate is valid for 192.168.204.1, 10.107.10.21, not > 10.107.8.255") > > (Sorry about the formatting!) > > The OAM IP address changed from 10.107.10.21/22 to 10.107.8.255/22. > > Is it possible to fix this? > > Best regards, > > Dejan > > > On Mon, 2020-02-24 at 15:05 +0000, Winnicki, Chris wrote: > > Hi Dejan > > > > It's absolutely possible to change the OAM IP address after the > > installation is completed. > > * One thing to watch out for is make sure that: > > 1) oam_gateway_ip is updated if you're changing networks > > 2) That your machine (which you're using to access the StarlinX > > system) can route to the new network (in case the networks were > > changed) > > > > > > Regards, > > > > Chris Winnicki > > chris.winnicki at windriver.com > > 613-963-1329 > > ________________________________________ > > From: Dejan Muhamedagic [dejan.muhamedagic at tttech-industrial.com] > > Sent: Monday, February 24, 2020 9:48 AM > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] oam address > > > > Hi, > > > > Is it possible to change the OAM IP address after the installation? > > There is a "system oam-modify", but the installation guide warns: > > > > "Some Ansible bootstrap parameters cannot be changed or are very > > difficult to change after installation is complete." > > > > The reason I'm asking is that this installation may have to run in > > different environments and possibly in different networks. > > > > Thanks, > > > > Dejan > > > > CONFIDENTIALITY: The contents of this e-mail are confidential and > > intended only for the above addressee(s). If you are not the > > intended recipient, or the person responsible for delivering it to > > the intended recipient, copying or delivering it to anyone else or > > using it in any unauthorized manner is prohibited and may be > > unlawful. If you receive this e-mail by mistake, please notify the > > sender and the systems administrator at straymail at tttech.com > > immediately. > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > CONFIDENTIALITY: The contents of this e-mail are confidential and > intended only for the above addressee(s). If you are not the intended > recipient, or the person responsible for delivering it to the intended > recipient, copying or delivering it to anyone else or using it in any > unauthorized manner is prohibited and may be unlawful. If you receive > this e-mail by mistake, please notify the sender and the systems > administrator at straymail at tttech.com immediately. > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail at tttech.com immediately. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From abhideodhar at gmail.com Thu Mar 12 10:15:39 2020 From: abhideodhar at gmail.com (Abhijit Deodhar) Date: Thu, 12 Mar 2020 15:45:39 +0530 Subject: [Starlingx-discuss] StarlingX and EdgeX foundry Message-ID: Hi, I recently came across the video titled "StarlingX IOT Integration with EdgeX Foundry". I wanted to recreate this demo in my environment. Where can I find detailed instructions (hardware/software requirements and steps) to setup this demo? Regards Abhijit -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Mar 3 02:04:21 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 3 Mar 2020 02:04:21 +0000 Subject: [Starlingx-discuss] Canceled: Weekly StarlingX non-OpenStack distro meeting Message-ID: Hi All: New Series of non-Openstack disto meeting invitation , Agenda for each will be sent individual email. * Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) * Call Details: o Zoom link: https://zoom.us/j/342730236 o 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 International numbers available: https://zoom.us/u/ed95sU7aQ * Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other 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: 4676 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT80267 1.jpg Type: image/jpeg Size: 8279 bytes Desc: ATT80267 1.jpg URL: From cherish.cao at jitstack.com Wed Mar 4 09:55:52 2020 From: cherish.cao at jitstack.com (cherish.cao at jitstack.com) Date: Wed, 4 Mar 2020 17:55:52 +0800 Subject: [Starlingx-discuss] =?gb2312?b?u9i4tDogUEJSIENoYW5nZXMgV2l0aCBy?= =?gb2312?b?ZXZpZXcgY29tbWVudA==?= Message-ID: <00b501d5f20b$17d78520$47868f60$@jitstack.com>+D35FB9471384C578 Hi Saul: Nice to meet you! We are sorry for the delay of PBR task. Engineer in charge of the StarlingX project is unable to resume work because of SARS-CoV, China is seriously affected by the virus. We have to arrange new engineers to take over the StarlingX project from this week, then we need to complete the task handover in 1-2 weeks. For that reason,we had already delayed task. However,due to join a new engineer,we are confident that we will solve the current difficulties as soon as possible. This is new engineer's contact information: Helen (helen.gui at jitstack.com ) Yipeng.He(yipeng.he at jitstack.com Cherish.Cao Best Regads. -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Thu Mar 5 03:51:22 2020 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 5 Mar 2020 03:51:22 +0000 Subject: [Starlingx-discuss] user-space upgrade on starlingx Message-ID: Hi All: Our team made some work to show how complex dependencies among services/RPMs . The images is attached for your reference . We are taking mtce , sysinv and fm-rest-api 3 flock services as sources. >From this picture , it is not easy to figure out which rpm can be upgraded currently or not . If anyone have suggestion , please share with us. Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: figure1_full.png Type: image/png Size: 985968 bytes Desc: figure1_full.png URL: From shailesh83 at gmail.com Thu Mar 5 16:00:42 2020 From: shailesh83 at gmail.com (Shailesh Pandey) Date: Thu, 5 Mar 2020 17:00:42 +0100 Subject: [Starlingx-discuss] Intel canyon haydes Nuc kernel panic Message-ID: [image: image.png] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 22794932 bytes Desc: not available URL: From shailesh83 at gmail.com Thu Mar 5 16:28:06 2020 From: shailesh83 at gmail.com (Shailesh Pandey) Date: Thu, 5 Mar 2020 17:28:06 +0100 Subject: [Starlingx-discuss] Error for StarlingX 3.0 on NuC using nvme Message-ID: [image: error_Starlingx.gif] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: error_Starlingx.gif Type: image/gif Size: 4907620 bytes Desc: not available URL: From zhang.kunpeng at 99cloud.net Mon Mar 9 10:40:54 2020 From: zhang.kunpeng at 99cloud.net (=?gb2312?B?1cX278X0?=) Date: Mon, 9 Mar 2020 18:40:54 +0800 Subject: [Starlingx-discuss] iPXE for IPv6 In-Reply-To: <151EE31B9FCCA54397A757BC674650F0C1689226@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0C15FF245@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0C1655A1D@ALA-MBD.corp.ad.wrs.com> <4BB34F6B-CF07-4AC0-9049-3A5AB51A0F69@99cloud.net> <151EE31B9FCCA54397A757BC674650F0C1689226@ALA-MBD.corp.ad.wrs.com> Message-ID: <1EDF4B46-F06D-4834-ADBD-6DBAB3C22E3E@99cloud.net> Hi Ghada, I have tried to boot from ipxe with ipv6 pxeboot network. Dhcp server worked well and ipv6 address was auto set in the second host. But ipxe boot failed with “no such file or directory”. BTW it is ok when I fetch the boot script with ipxe shell (boot.ipxe is my testing boot script): ipxe> chain tftp://pxecontroller/boot.ipxe It blocks, any help could be appreciated. Follows are dnsmasq config file Thanks Kunpeng > 在 2020年3月5日,07:58,Khalil, Ghada 写道: > > Hello Kunpeng, > Can you please share the plans for this features? Are you still targeting stx.4.0? > As per my email to the stx-discuss mailing list [1], please update the feature dates. > > Thanks, > Ghada > > [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/007913.html > > > From: Khalil, Ghada > Sent: Wednesday, February 12, 2020 6:15 PM > To: 'Shuquan Huang'; 张鲲鹏 > Cc: Jolliffe, Ian; Peters, Matt; Le, Huifeng; Yong Hu > Subject: RE: iPXE for IPv6 > > Thank you for the update Shuquan. > > Welcome Kunpeng. Please have a look at the story and let us know when you plan to start and if you need any clarification. > > Regards, > Ghada > > From: Shuquan Huang [mailto:huang.shuquan at 99cloud.net ] > Sent: Tuesday, February 11, 2020 3:21 AM > To: Khalil, Ghada; 张鲲鹏 > Cc: Jolliffe, Ian; Peters, Matt; Le, Huifeng; Yong Hu > Subject: Re: iPXE for IPv6 > > Hi Ghada, > > Xiangdong left 99Cloud last month. Kunpeng will take over this task. Sorry about the change and the impact to the task. > > > On Feb 7, 2020, at 6:50 AM, Khalil, Ghada > wrote: > > Hi Xiangdong, > Happy New Year! > > I’m following up on the IPv6 pxeboot support in stx.4.0: > https://storyboard.openstack.org/#!/story/2006442 > > Are you on track to start this work shortly as per your original plan? > > Please let us know if you need any clarification on the scope or if you want to discuss any technical details. > > Regards, > Ghada > > From: 黄向东 [mailto:huang.xiangdong at 99cloud.net ] > Sent: Sunday, December 01, 2019 8:48 PM > To: Khalil, Ghada > Cc: Shuquan Huang; Jolliffe, Ian; Peters, Matt; Le, Huifeng > Subject: Re:RE: Re:RE: iPXE for IPv6 > > Hi, Ghada > > Sorry for the late reply, I plan to start in February. > > > > > -- > ————————————————————————————— > 九州云信息科技有限公司 99CLOUD Inc. > > 黄向东 产品开发部 > 邮箱(Email): huang.xiangdong at 99cloud.net > 手机(Mobile): 15221772173 > 地址(Addr): 上海市局门路427号1号楼206 > Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China > 网址(Site): http://www.99cloud.net > > 发件人:"Khalil, Ghada" > > 发送日期:2019-11-28 22:48:41 > 收件人:"黄向东" > > 抄送人:Shuquan Huang >,"Jolliffe, Ian" >,"Peters, Matt" >,"Le, Huifeng" > > 主题:RE: Re:RE: iPXE for IPv6 > > > That’s great. Thank you. > Please let us know when you plan to start this work and if there is anything we can do to help. > > Regards, > Ghada > > From: 黄向东 [mailto:huang.xiangdong at 99cloud.net ] > Sent: Tuesday, November 26, 2019 5:10 AM > To: Khalil, Ghada > Cc: Shuquan Huang; Jolliffe, Ian; Peters, Matt; Le, Huifeng > Subject: Re:RE: iPXE for IPv6 > > > Yes, I will work on this story for 4.0 > > > -- > ————————————————————————————— > 九州云信息科技有限公司 99CLOUD Inc. > > 黄向东 产品开发部 > 邮箱(Email): huang.xiangdong at 99cloud.net > 手机(Mobile): 15221772173 > 地址(Addr): 上海市局门路427号1号楼206 > Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China > 网址(Site): http://www.99cloud.net > > 发件人:"Khalil, Ghada" > > 发送日期:2019-11-26 04:04:02 > 收件人:"黄向东" >,Shuquan Huang > > 抄送人:"Jolliffe, Ian" >,"Peters, Matt" >,"Le, Huifeng" > > 主题:RE: iPXE for IPv6 > > Hi Xiangdong, > We are working on stx.4.0 release planning. I’m following up on this story: > https://storyboard.openstack.org/#!/story/2006442 > > Can you please confirm that you plan to work on this story for stx.4.0? > > Thanks, > Ghada > > PS: I’d also like to take this opportunity to introduce our new stx networking PL – Huifeng Le (copied) > > From: Khalil, Ghada > Sent: Friday, October 18, 2019 11:48 AM > To: '黄向东'; Shuquan Huang > Cc: Jolliffe, Ian; Peters, Matt > Subject: RE: Re:Re: iPXE for IPv6 > > Hi Xiangdong, > Thank you for your response. I updated the story. > > Matt also added a comment to clarify the scope. Please have a look and let us know if you have any questions. > > We also hold a starlingx networking call every two weeks where we discuss networking-related features and bugs. You are more than welcome to attend. The information is on the StarlingX wiki:https://wiki.openstack.org/wiki/Starlingx/Meetings#0615am_Pacific_-_Networking_Team_Call_.28Bi-weekly.29 > The next meeting is on October 31. > > Regards, > Ghada > > From: 黄向东 [mailto:huang.xiangdong at 99cloud.net ] > Sent: Thursday, October 17, 2019 11:02 PM > To: Shuquan Huang > Cc: Khalil, Ghada; Jolliffe, Ian; Peters, Matt > Subject: Re:Re: iPXE for IPv6 > > Hi Ghada, > > IPv6 PXE boot network support now only works in ipv4 + ipv6 dual-stack env, pure ipv6 env testing and deploy > intergration still need some works. So I would like to put this feature on stx 4.0 list instead. > > Regards > > Xiangdong > > > -- > ————————————————————————————— > 九州云信息科技有限公司 99CLOUD Inc. > > 黄向东 产品开发部 > 邮箱(Email): huang.xiangdong at 99cloud.net > 手机(Mobile): 15221772173 > 地址(Addr): 上海市局门路427号1号楼206 > Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China > 网址(Site): http://www.99cloud.net > > 发件人:Shuquan Huang > > 发送日期:2019-10-18 10:36:49 > 收件人:"Khalil, Ghada" > > 抄送人:"Jolliffe, Ian" >,"黄向东" >,"Peters, Matt" > > 主题:Re: iPXE for IPv6 > > 向东, > > 你来回复一下 > > > On Oct 18, 2019, at 06:03, Khalil, Ghada > wrote: > > Hi Shuquan, > I see that Xiangdong recently added a few comments to the storyboard with the experiments he’s done to date. I’ve asked Matt, the stx networking TL, to have a look. > > Is there a target date for when this feature would be ready? > stx.3.0 milestone-3 (feature freeze) is planned for next week. We can make an exception for this feature if you give me an idea of the dates you are targeting and a view of the risk of the required changes. RC1 is planned for Nov 20; that would be the absolute latest although we don’t like to wait until the very end for feature code to merge. Otherwise we will have to put this on the stx.4.0 list instead. > > Please let me know. > > Thanks, > Ghada > > From: Shuquan Huang [mailto:huang.shuquan at 99cloud.net ] > Sent: Thursday, October 10, 2019 12:41 AM > To: Jolliffe, Ian; 黄向东 > Cc: Khalil, Ghada > Subject: Re: iPXE for IPv6 > > Hi Ian, > > Sorry for the late reply. I’m just back from the vacation due to national day holiday. > > Xiangdong from my team is working on it. He just kicked off some testing and will update it to the story board later. > > On Oct 8, 2019, at 4:26 AM, Jolliffe, Ian > wrote: > > Hi Shuquan; > > I hope you are doing well and I look forward to seeing you in Shanghai. It was great to have a call with you and your team members on the phone a couple of weeks ago. Please let us know if we can help you get started in some way on IPXE for IPv6. Maybe you have started, and we don’t have visibility. > > Here is the link to the story board: > > https://storyboard.openstack.org/#!/story/2006442 > > It was very nice to meet your team members over the phone as well. > > Regards; > > Ian -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-1.jpeg Type: image/jpeg Size: 50715 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-2.png Type: image/png Size: 60497 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-3.png Type: image/png Size: 57599 bytes Desc: not available URL: From yang.liu at windriver.com Tue Mar 10 15:04:54 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Tue, 10 Mar 2020 15:04:54 +0000 Subject: [Starlingx-discuss] Weekly StarlingX Test meeting In-Reply-To: <19C65A6E92EA384D809B1772130CD7F8693CEE38@ALA-MBD.corp.ad.wrs.com> References: <19C65A6E92EA384D809B1772130CD7F8693CEE38@ALA-MBD.corp.ad.wrs.com> Message-ID: Sorry for the inconvenience. Please use following zoom id for today. Topic: STX-Test Meeting - 03/10 Time: Mar 10, 2020 11:00 AM Eastern Time (US and Canada) Join Zoom Meeting https://windriver.zoom.us/j/677538858 Meeting ID: 677 538 858 -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Wed Mar 11 22:49:52 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 11 Mar 2020 22:49:52 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team meeting minutes 2020-03-11 Message-ID: Hello All, Thanks to Kris for setting up such great processes for STX docs and making my transition as smooth as possible. I'll do my best to continue what you started! Here are this week's docs team meeting minutes. Join us if you have interest in StarlingX docs! We meet Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Mary Camp ========== 2020-03-11 * All -- reviews merged since last week: 2 * All -- bug status -- no change * All -- R4 target content: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.4.0&project_id=1046 * Windows Active Dir content -- ready to add -- http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007710.html ? Add to config section under K8s (follow up with reference from R4 install guides, likely Remote CLIs for Access K8s) ? Review available: https://review.opendev.org/#/c/712111/ * Upgrade Kubernetes version -- http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007901.html (R4 new content) ? Asked Greg where should this go? https://docs.starlingx.io/configuration/index.html Kubernetes configuration section. ? FYI, in the future there will be an upgrade feature for the whole STX. Probably K8s first, then STX, then orchestration for dist cloud. ? Email thread has more questions/answers. Mary to include the folks commenting on the review. * Assignment of R4 doc tasks -- will be discussed in this weeks build meeting -- confirm ownership (KRIS) ? These stories have no assigned person: ? Bring to Community call as opens/need owners. Email Bill Z with these links on Tues. so he can add to agenda for call. * https://storyboard.openstack.org/#!/story/2006770 (How to use Backup & Restore) * https://storyboard.openstack.org/#!/story/2006781 (K8s upgrade support) [Angie supplied content, do I assign task to her? Yes after kickoff review] * https://storyboard.openstack.org/#!/story/2007223 (update build guide w/ layered build info) * https://storyboard.openstack.org/#!/story/2007222 (update dist cloud bare metal install w/ redfish info) * https://storyboard.openstack.org/#!/story/2006588 (updates for Dist Cloud) * https://storyboard.openstack.org/#!/story/2006866 (Cert config & management guide) * All -- Changes needed? [Deferred discussion till next week] * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007847.html - possible Ceph storage updates needed? * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007891.html - asking for more detail on AIO Simplex install * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/007909.html - asking after OpenStack SSL cert config. We have a general cert stub page.... * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/007918.html - possible build guide updates needed? * All -- Opens * Welcome Mary ? Make Mary core reviewer on Docs. (Bruce completed this during the meeting.) ? New role, mirroring Kris in transition ? Thanks to Kris for setting up such great processes and making the transition as smooth as possible. You will be missed! * Kris -- Transition plan: https://etherpad.openstack.org/p/docs-transition-plan ? Need to update team page on the wiki: https://wiki.openstack.org/wiki/StarlingX/Docs_and_Infra ? TSC has to formally approve this election. AR Bruce to take to TSC tomorrow. AR Mary/Kris update wiki afterwards to make the change. * All -- Wiki status ? Revisit planned migration of wiki content: lets close this out (see yellow). https://docs.google.com/spreadsheets/d/1UJjUttsWQRyauATrip0wKGIxSO7DvyetDKmPwvEIDaA/edit?usp=sharing ? Virtual Box wiki converted to RST file. Review available: https://review.opendev.org/#/c/711769/ * When this gets merged, the old wiki topic will be removed, noted as deprecated. Keep going through to get these last few topics migrated. * New reviews submitted: ? https://review.opendev.org/#/c/712025/ Adds sentence about using a proxy. Needs wordsmithing. ? https://review.opendev.org/#/c/712232/ Adds words around the download mirror text, but is specific to R3. ? Mary look into genericizing text and/or add example? See how many release-specfic URLs are there. Could add an RST comment/label to ID the release-specific changes. * New topics for us to document. Both are coming from Intel field teams supporting customers (brucej) ? Start by emailing Ghada for folks to contact for help on these topics: * High availability and failover mechanisms for applications and for SM. [SM we may have in training in wiki, but HA and failover need more info (for industrial customers) Good idea to document best practices how to build these. ] * Networking - how to bridge / combine K8S and OpenStack networks for applications [Need to capture this info, but unclear who could provide this info. Need diagrams to show how it works externally.] * Kris: here are two items she didn't have time to get to during her time on the STX project, might be interesting for us to dig into. ? Suggestion to revisit the R4 content list/plan (stories) to see if anything was overlooked OR features have been added/removed? Don't want to be rigidly attached to the list. Do the real users have these concerns? How to prioritize? Get input from users via survey or another means, question on STX discuss. What are the undocumented areas? Someone who reps the doc team could attend each sub-team meeting to ask for docs feedback, gaps, areas of struggle, etc. Couple of questions, enlist key folks to bring it up. ? Investigate if there are any analytics on the docs site, to see what's clicked most, what are folks searching for (incoming from Google). * All -- Ongoing tasks: * STX in a box: (https://storyboard.openstack.org/#!/story/2006622) ? Draft in review https://review.opendev.org/#/c/692202/ ? During meeting we discussed this idea and agreed it should be put on hold. Scott Little & Greg tried this, but were unable to make progress. ? AR Kris to ping Sai and let him know the status. Thank him for his work, we're unable to close on this now. -------------- next part -------------- An HTML attachment was scrubbed... URL: From shailesh.pandey at intel.com Mon Mar 9 20:23:34 2020 From: shailesh.pandey at intel.com (Pandey, Shailesh) Date: Mon, 9 Mar 2020 20:23:34 +0000 Subject: [Starlingx-discuss] FW: StarlingX 3.0 on Intel Haydes Canynon Nuc on NVME flashing issue In-Reply-To: References: Message-ID: Hi All, Good Morning, Please find attached the crash log images for StarlingX 3.0 on Intel Haydes Canynon NUC running on nvme. I have managed to flash Ubunttu 18.04 on this NUC on nvme. I have managed to flash CentOS 7.0 using USB bootable USB and than booted CentOS and managed to Burned in Hard drive i.e nvme in this case. I have amended kernel commandline paramteter : boot_device=nvme0n1 rootfs_device=nvme0n1 StarlingX 3.0 boot_image.iso used : http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso Please let me know if you have tried above image on Intel NUC8i7HVK/NUC8iHVB. Please help me out what can I do here. Regards, Shailesh Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Crash_StarlingX_NVME_3.JPG Type: image/jpeg Size: 113656 bytes Desc: Crash_StarlingX_NVME_3.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Crash_StarlingX_NVME_4.JPG Type: image/jpeg Size: 139128 bytes Desc: Crash_StarlingX_NVME_4.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Crash_StarlingX_NVME_5.JPG Type: image/jpeg Size: 128459 bytes Desc: Crash_StarlingX_NVME_5.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Crash_StarlingX_NVME_6.JPG Type: image/jpeg Size: 129794 bytes Desc: Crash_StarlingX_NVME_6.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Crash_StarlingX_NVME_1.JPG Type: image/jpeg Size: 108122 bytes Desc: Crash_StarlingX_NVME_1.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Crash_StarlingX_NVME_2.JPG Type: image/jpeg Size: 117714 bytes Desc: Crash_StarlingX_NVME_2.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Kernel_cmdline.jpg Type: image/jpeg Size: 4601769 bytes Desc: Kernel_cmdline.jpg URL: From austin.sun at intel.com Tue Mar 10 05:03:14 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 10 Mar 2020 05:03:14 +0000 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting Message-ID: Hi All: Update time since summer is coming. New Series of non-Openstack disto meeting invitation , Agenda for each will be sent individual email. * Cadence and time slot: o Wednesday 9AM Summer time EDT (9PM China time, US PDT Summer time 6AM) * Call Details: o Zoom link: https://zoom.us/j/342730236 o 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 International numbers available: https://zoom.us/u/ed95sU7aQ * Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other 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: 4925 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT61562 1.jpg Type: image/jpeg Size: 6370 bytes Desc: ATT61562 1.jpg URL: From Dariush.Eslimi at windriver.com Thu Mar 12 14:35:49 2020 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Thu, 12 Mar 2020 14:35:49 +0000 Subject: [Starlingx-discuss] StarlingX docs team - new addition In-Reply-To: <387E6828-2F10-4815-86E9-44E61E5F9847@intel.com> References: <387E6828-2F10-4815-86E9-44E61E5F9847@intel.com> Message-ID: +2, should I submit a gerrit review for this ? ☺ Thanks for all the help and lots of positive energy. Dariush From: Cobbley, David A [mailto:david.a.cobbley at intel.com] Sent: March-11-20 7:45 PM To: Jones, Bruce E ; Dale, Kristal Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX docs team - new addition I second that; your work has been amazing, and the team will miss you! -- David C From: "Jones, Bruce E" > Date: Wednesday, March 11, 2020 at 2:48 PM To: "Dale, Kristal" > Cc: "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] StarlingX docs team - new addition Kris, thank you so much for all of your contributions to StarlingX. Thanks to your efforts, the project has made enormous progress in the quality of our documentation. Your can-do attitude, your drive and your passion are a joy to be around. You will be missed! brucej From: Dale, Kristal [mailto:kristal.dale at intel.com] Sent: Wednesday, March 11, 2020 2:33 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX docs team - new addition Hello All, Following up to the community call this morning, I wanted to introduce the newest member of the docs team: Mary Camp! Mary has previously contributed to the StarlingX docs and I have worked with her on other Intel projects – she’s a great addition to the team. This will be my last week on the StarlingX docs project – it has been a great experience working with you all! And, starting this week Mary will be taking my place on the docs team. Any questions, issues, etc. that were previously directed to me should now be directed to Mary. Thanks everyone – and welcome Mary! Cheers, Kris -------------- next part -------------- An HTML attachment was scrubbed... URL: From jack at jento.io Thu Mar 12 16:17:05 2020 From: jack at jento.io (Jack Morgan) Date: Thu, 12 Mar 2020 09:17:05 -0700 Subject: [Starlingx-discuss] FW: StarlingX 3.0 on Intel Haydes Canynon Nuc on NVME flashing issue In-Reply-To: References: Message-ID: <47be8abe-4bd7-47d0-921f-a868da6715f8@jento.io> Shailesh, For what it's worth, I have the same system running Fedora 31 with an older bios (12/17/2018). You might try adding *nomodeset* to your kernel commandline parameters as this has fixed some kernel call traces issues I had on my other Intel Nuks. On 3/9/20 1:23 PM, Pandey, Shailesh wrote: > > Hi All, > >   > > Good Morning, > >   > > Please find attached the crash log images for StarlingX 3.0 on *Intel > Haydes Canynon NUC* running on nvme. > >   > > I have *managed to* *flash Ubunttu 18.04 on this NUC on nvme*. > >   > > I have *managed to flash CentOS 7.0 using USB bootable USB and than > booted CentOS and managed to Burned in Hard drive i.e nvme in this case*. > >   > > I have amended kernel commandline paramteter : *boot_device*=nvme0n1 > *rootfs_device*=nvme0n1 > >   > > StarlingX 3.0 boot_image.iso used : > > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso > >   > > Please let me know if you have tried above image on Intel > *NUC8i7HVK/NUC8iHVB.* > >   > > Please help me out what can I do here. > >   > > Regards, > > Shailesh > >   > >   > >   > >   > > Intel Deutschland GmbH > Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany > Tel: +49 89 99 8853-0, www.intel.de > Managing Directors: Christin Eisenschmid, Gary Kershaw > Chairperson of the Supervisory Board: Nicole Lau > Registered Office: Munich > Commercial Register: Amtsgericht Muenchen HRB 186928 > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Jack Morgan -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: OpenPGP digital signature URL: From mihail-laurentiu.trica at intel.com Thu Mar 12 16:44:58 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Thu, 12 Mar 2020 16:44:58 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build - ISO 20200312 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-12 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers – 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 ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Simplex setup on bare metal failed because of an automation issue (simplex setup on virtual environment was successful). Regards, STX Validation Team Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu Mar 12 18:53:58 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 12 Mar 2020 19:53:58 +0100 Subject: [Starlingx-discuss] [OpenDev] We want your discussion ideas! Message-ID: <9CDDBF2C-9FBD-44A1-AA77-7D8812D70917@gmail.com> Hi everyone, We still need your help shaping the discussion content for OpenDev + PTG[1], June 8-11, 2020! Our vision is for the content to be programmed by you-- the community. Programming Committees for each Track have begun meeting to discuss potential topics for the event, but they need your ideas and input to make sure all of the content is relevant and interesting to the community. The Programming Committee will also select moderators who will lead interactive discussions on a particular topic within the Track, so make sure to volunteer through the form below if you’re interested in that as well. Check out this etherpad[2] to see what topics the Committees are currently discussing. If you’re interested in volunteering as an OpenDev discussion moderator, or would like to suggest topics for moderated discussions within a particular Track, please read the details below, and then fill out this form[3]. We’re looking for discussion topics and Moderators for the following OpenDev Tracks: - Hardware Automation - Large-scale Usage of Open Source Infrastructure Software - Containers in Production - Key Challenges for Open Source in 2020 OpenDev Discussion Moderators will: - Be appointed by the Programming Committees - Facilitate discussions within a particular Track - Have adequate knowledge and experience to lead and moderate discussion around certain topics during the event - Work with Programming Committee to decide focal point of discussion Moderators need to be available to attend OpenDev, June 8 - 10, 2020. Volunteer to be a moderator or suggest discussion topics here __before March 20__: https://openstackfoundation.formstack.com/forms/opendev_vancouver2020_volunteer Thanks, Ildikó [1] https://www.openstack.org/events/opendev-ptg-2020/ [2] https://etherpad.openstack.org/p/r.961497ec02b63da123fbda235a7ba02e [3] https://openstackfoundation.formstack.com/forms/opendev_vancouver2020_volunteer From maryx.camp at intel.com Thu Mar 12 20:18:15 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Thu, 12 Mar 2020 20:18:15 +0000 Subject: [Starlingx-discuss] stx docs input:2006711 In-Reply-To: References: Message-ID: Thanks Jerry for the info. Please have a look at the current review for this topic: https://review.opendev.org/#/c/712111/ Since I am new to this role, I'd appreciate your guidance - do you recommend adding this new info to the WIP review or should we wait and make a new review for this text? thanks, Mary Camp PTIGlobal Technical Writer | maryx.camp at intel.com From: Sun, Yicheng (Jerry) Sent: Tuesday, March 10, 2020 4:11 PM To: starlingx-discuss at lists.starlingx.io; Camp, MaryX Subject: stx docs input:2006711 Hi All, We have just added the ability to configure oidc auth related parameters post-bootstrap: system service-parameter-add kubernetes kube_apiserver oidc_client_id=value system service-parameter-add kubernetes kube_apiserver oidc_groups_claim=value system service-parameter-add kubernetes kube_apiserver oidc_issuer_url=value system service-parameter-add kubernetes kube_apiserver oidc_username_claim=value they used to be configurable only at boostrap time in localhost.yml: apiserver_oidc: client_id: stx-oidc-client-app issuer_url: https://:30556/dex username_claim: email groups_claim: group Apply the service parameters with "system service-parameter-apply kubernetes", or no changes will take place. The valid configurations for the service parameters are the same as during bootstrap: none of the parameters or oidc_issuer_url, oidc_client_id, oidc_username_claim or the above 3 and oidc_groups_claim Thanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Fri Mar 13 00:05:46 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 13 Mar 2020 00:05:46 +0000 Subject: [Starlingx-discuss] ceph containerization patch review Message-ID: Hi Brent & Frank I already finish my new application and helm plugin for rook-ceph. But still two concern to discuss. 1, decouple ceph backend with sysinv. Now ceph backend has been removed as default storage backend. And I plan to add rook-ceph as another storage backend which user could enable by his provision. So what about decouple ceph backend with sysinv-conductor, which is beneficial for more storage backend enabling. 2, change restriction for volume group creation in sysinv Currently sysinv has restriction for volume group creation, only permit create volume group with "nova-local", "cinder-volumes", "cgts-vg". What about remove this restriction? For containerized ceph cluster deployment, osd is provisioned by ceph-volume, which is based on logical volume. It will create a volume group, with "ceph" name prefixed. I prefer this newly created volume group could also be managed by sysinv. Currenlty ceph cluster is deployed by ceph-disk in puppet-ceph. This tool is depreciated. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Friday, February 21, 2020 11:14 PM To: 'Miller, Frank' >; 'starlingx-discuss at lists.starlingx.io' >; 'Rowsell, Brent' >; 'Greg.Waines at windriver.com' > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan >; 'Church, Robert' > Subject: RE: ceph containerization patch review Hi Frank & Bob & Greg & Brent To deploy, it is same as any other helm chart. Wait for you opinion for current solution. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Wednesday, February 19, 2020 12:53 PM To: 'Miller, Frank' >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent >; 'Greg.Waines at windriver.com' > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan >; Church, Robert > Subject: RE: ceph containerization patch review Hi folks Answer the question, with only k8s, how to deploy rook. $ helm-upload stx-platform rook-ceph-0.1.0.tga $ helm install stx-platform/rook-ceph -n rook-ceph-cluster -n kube-system -f value.yaml BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Tuesday, February 18, 2020 10:06 PM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan >; Church, Robert > Subject: RE: ceph containerization patch review +Bob who is the containers TL From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Monday, February 17, 2020 8:46 AM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan > Subject: RE: ceph containerization patch review Hi Frank & Brent For rook manage configuration, after introduce rook-ceph, current ceph cluster deployed by puppet will keep or be removed? If removed, containerized ceph cluster deployed by rook-ceph will take the role of provisioner for stx-openstack. If keeps, helm chart rbd-provisioner in platform-integ-app also keeps and takes the role of provisioner for stx-openstack. Containerized ceph cluster deployed by rook-ceph only serve as csi provider for k8s. BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, February 10, 2020 11:47 PM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan > Subject: RE: ceph containerization patch review Hi Frank: As synced with Tingjie, this is my understanding for Rook manage the configuration instead of sysinv. 1, Remove ceph config and status query from sysinv 2, create another tool, like rook-client to launch and provision ceph cluster 3, one helm plugin like rbd-provision, which depends on newly created tool BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Saturday, February 8, 2020 4:16 AM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: ceph containerization patch review Martin: Thanks for posting your reviews and the update on the current status for this feature. I was unable to attend the containerization meeting this week so wasn't able to have Tingjie or you give an update on the open actions for the feature. From the Jan 14 minutes [1] one of the actions is to determine "how can you have Rook do all the configuration and not have sysinv involved" For now I suggest you add an additional item to your Tasks to do list to identify a design that does not require sysinv for the configuration and instead has Rook manage the configuration. I would like to ask that we discuss further at the next containerization meeting and if possible review a proposal from yourself and Austin for this item. Frank [1] https://etherpad.openstack.org/p/stx-containerization From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Thursday, February 06, 2020 11:02 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] ceph containerization patch review Hi folks I enabled containerized ceph cluster with simplex. You can begin to review my patch. I propose to build an image and deploy a simplex system with these patch to check. https://review.opendev.org/#/c/681457/ https://review.opendev.org/#/c/687340/ https://review.opendev.org/#/c/706256/ https://review.opendev.org/#/c/699557/ https://review.opendev.org/#/c/699556/ And I know there is other story, like remove ceph as default backend storage, maybe some conflict, we can discuss together. Tash Done: 1, disable native ceph cluster in ceph.pp 2, disable ceph daemon monitoring in service manager 3, add rook-ceph helm chart to launch ceph cluster 4, add override in stx-config to generate override with starlingx system config 5, sysinv add label in provision stage, to make containerized ceph mon and ceph mgr on designed host 6, add rook-ceph-provisioner helm chart to generate storage class, secret, config and pool for stx-application 7, enabled stx-openstack with containerized ceph 8, update ceph wrapper in stx-config to set or get containerized ceph cluster All these tasks done is enabled with simplex only. Task to do: 1, enable add osd runtime, after system provisioned 2, fix know issue, if system reboot, ceph cluster launch fail 3, enable bluestore and filestore, currently there is only bluestore 4, enable multi-node and duplex 5, enable swift with containerized ceph 6, enable fm alarm for containerized ceph 7, check backup and restore for containerized ceph 8, check system upgrade or how to transit from native ceph cluster to containerized ceph cluster 9, code cleanup 10, update unit test in stx-config BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From yu.chengde at 99cloud.net Fri Mar 13 10:30:32 2020 From: yu.chengde at 99cloud.net (YuChengDe) Date: Fri, 13 Mar 2020 18:30:32 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?=5BOpenStack_Upgrade=5D_Built_the_m?= =?utf-8?q?aster_branch_of_stx-cinder?= Message-ID: Hi: I have built a stx-cinder image for moving a new version of OpensStack in StarlingX. Welcome to apply image into your system. If there is any problem during usage, please let me know. Many thanks. Note: Get the image from docker hub P.S.: tag = [git branch]-[based on python3 or python built environment]-[image created day] docker pull chantyu/stx-cinder:master-python3-20200313 PROJECT_REPO= https://opendev.org/openstack/heat.git PROJECT_REF= master BUILDER= loci -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From mihail-laurentiu.trica at intel.com Fri Mar 13 12:54:09 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Fri, 13 Mar 2020 12:54:09 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build - ISO 20200313 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-13 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers – 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 ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard external setup in the virtual environment failed because of an automation issue (the corresponding job on bare metal was successful). Regards, STX Validation Team Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Fri Mar 13 16:19:56 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Fri, 13 Mar 2020 16:19:56 +0000 Subject: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images In-Reply-To: <93814834B4855241994F290E959305C75314D9F9@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C75314CC61@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314D245@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314D262@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314D9F9@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Don, We have finished 11/13 images build except for horizon and glance. For horizon, it needs starlingx-dashboard python3 whl. However, in our current build, we just build out starlingx-dashboard python2 whl. Do you have any proposal on how to get the required python3 whl. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 21:00 To: 'Liu, ZhipengS' ; 'Penney, Don' ; 'YuChengDe' ; 'starlingx-discuss at lists.starlingx.io' Cc: 'Somerville, Jim' Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, Chant and I already fixed this issue and other related dependent packages. We modified docker file and related script for wheel build, and rebuilt out all python3 wheels for the packages in stable-wheels.cfg. As for libvirt-python, we still use 4.7.0 version and rebuilt out python3 wheel currently. Will let you know the status after finishing all image build. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 0:06 To: 'Liu, ZhipengS' >; Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images We also had below issue during build other service image. Looking in links: /tmp/wheels/ Collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) Collecting PyMySQL===0.9.3 Downloading PyMySQL-0.9.3-py2.py3-none-any.whl (47 kB) Processing /tmp/wheels/python_memcached-1.59-py2.py3-none-any.whl Collecting six===1.14.0 Downloading six-1.14.0-py2.py3-none-any.whl (10 kB) Collecting cffi===1.14.0 Downloading cffi-1.14.0-cp36-cp36m-manylinux1_x86_64.whl (399 kB) ERROR: Could not find a version that satisfies the requirement uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) (from versions: none) ERROR: No matching distribution found for uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) Actually, we get uWSGI-2.0.17.1-cp27-cp27mu-linux_x86_64.whl through the link in stable-config file. So far, not sure how many python3 packages we need. From: Liu, ZhipengS > Sent: 2020年3月9日 23:44 To: Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: Re: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! See my inline comments. From: Penney, Don > Sent: 2020年3月9日 23:18 To: Liu, ZhipengS >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I think building the openstack master branch will require moving the images to python3. This has implications to the base image, to how we build the base wheels tarball, and possibly to arguments passed to loci (as well as moving to a newer loci SHA). >> Yes, we have to set python3 = true to loci and also fix a small known bug. I believe Al started looking at this last week, but got pulled off to look at some other issues. From your reply, it sounds like maybe you’ve also done some of this? >> Yes When we explicitly add wheels to the tarball, we update the upper-constraints file to align with the module we’ve included. This would be why the build is looking for 4.7.0 here. There is an upper-constraints.txt file in the tarball itself which you can check. >> Yes, in our script, if we have 4.7.0 in stx repo, it will change the version to 4.7.0 from other versions specified in upper-constraints.txt The libvirt wheel building is python2 only, currently. So it would need to be built for python3 - if that’s possible for 4.7.0. If a newer version of libvirt-python is needed for python3 support, then it will need to be updated. I don’t know how big that effort will be. >> From code, libvirt-python 4.7.0 can support both python2 and python3, but in our code, we just add patch to let it build out python2 whl. >> libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, March 05, 2020 1:06 AM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Penney, We just used OpenStack master branch and upper-constraint file below https://raw.githubusercontent.com/openstack/requirements/master/upper-constraints.txt libvirt-python===5.10.0;python_version=='2.7' libvirt-python===6.0.0;python_version=='3.6' libvirt-python===6.0.0;python_version=='3.7' In nova setup.cfg. it adds python require info. python-requires = >=3.6 Then we built python3 related packages to the base image and rebuilt nova image to fix python3 issue. But there is still an error below. collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) ERROR: Could not find a version that satisfies the requirement libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) (from versions: none) ERROR: No matching distribution found for libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 From code, I saw that we already built libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl through a patch which Seems related to python2. cgcs-root/stx/integ/virt/libvirt-python/centos/meta_patches$ 0002-Build-python-wheel.patch It needs libvirt-python whl for python3, right? Do we have plan to upgrade libvirt-python to 6.0.0? Any comment? Thanks a lot! Zhipeng From: Penney, Don > Sent: 2020年2月27日 0:25 To: YuChengDe >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I was able to successfully build stx-nova image in master with no changes. Do you have any customizations in your environment? From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 26, 2020 10:38 AM To: YuChengDe; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 [Image removed by sender.] -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From Don.Penney at windriver.com Fri Mar 13 16:23:59 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Fri, 13 Mar 2020 16:23:59 +0000 Subject: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images In-Reply-To: References: <93814834B4855241994F290E959305C75314CC61@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314D245@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314D262@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314D9F9@SHSMSX104.ccr.corp.intel.com> Message-ID: I believe this has dependencies on a variety of StarlingX modules which are currently python2 only. You’ll probably need to exclude starlingx-dashboard for your initial builds, until all the required modules are available for python3. That said, it would be using only small components of these. So an initial effort to get python3 wheels for all the required modules may be small. Smaller than the effort to get these running as python3 on-host, certainly. From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Friday, March 13, 2020 12:20 PM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, We have finished 11/13 images build except for horizon and glance. For horizon, it needs starlingx-dashboard python3 whl. However, in our current build, we just build out starlingx-dashboard python2 whl. Do you have any proposal on how to get the required python3 whl. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 21:00 To: 'Liu, ZhipengS' ; 'Penney, Don' ; 'YuChengDe' ; 'starlingx-discuss at lists.starlingx.io' Cc: 'Somerville, Jim' Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, Chant and I already fixed this issue and other related dependent packages. We modified docker file and related script for wheel build, and rebuilt out all python3 wheels for the packages in stable-wheels.cfg. As for libvirt-python, we still use 4.7.0 version and rebuilt out python3 wheel currently. Will let you know the status after finishing all image build. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 0:06 To: 'Liu, ZhipengS' >; Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images We also had below issue during build other service image. Looking in links: /tmp/wheels/ Collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) Collecting PyMySQL===0.9.3 Downloading PyMySQL-0.9.3-py2.py3-none-any.whl (47 kB) Processing /tmp/wheels/python_memcached-1.59-py2.py3-none-any.whl Collecting six===1.14.0 Downloading six-1.14.0-py2.py3-none-any.whl (10 kB) Collecting cffi===1.14.0 Downloading cffi-1.14.0-cp36-cp36m-manylinux1_x86_64.whl (399 kB) ERROR: Could not find a version that satisfies the requirement uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) (from versions: none) ERROR: No matching distribution found for uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) Actually, we get uWSGI-2.0.17.1-cp27-cp27mu-linux_x86_64.whl through the link in stable-config file. So far, not sure how many python3 packages we need. From: Liu, ZhipengS > Sent: 2020年3月9日 23:44 To: Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: Re: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! See my inline comments. From: Penney, Don > Sent: 2020年3月9日 23:18 To: Liu, ZhipengS >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I think building the openstack master branch will require moving the images to python3. This has implications to the base image, to how we build the base wheels tarball, and possibly to arguments passed to loci (as well as moving to a newer loci SHA). >> Yes, we have to set python3 = true to loci and also fix a small known bug. I believe Al started looking at this last week, but got pulled off to look at some other issues. From your reply, it sounds like maybe you’ve also done some of this? >> Yes When we explicitly add wheels to the tarball, we update the upper-constraints file to align with the module we’ve included. This would be why the build is looking for 4.7.0 here. There is an upper-constraints.txt file in the tarball itself which you can check. >> Yes, in our script, if we have 4.7.0 in stx repo, it will change the version to 4.7.0 from other versions specified in upper-constraints.txt The libvirt wheel building is python2 only, currently. So it would need to be built for python3 - if that’s possible for 4.7.0. If a newer version of libvirt-python is needed for python3 support, then it will need to be updated. I don’t know how big that effort will be. >> From code, libvirt-python 4.7.0 can support both python2 and python3, but in our code, we just add patch to let it build out python2 whl. >> libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, March 05, 2020 1:06 AM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Penney, We just used OpenStack master branch and upper-constraint file below https://raw.githubusercontent.com/openstack/requirements/master/upper-constraints.txt libvirt-python===5.10.0;python_version=='2.7' libvirt-python===6.0.0;python_version=='3.6' libvirt-python===6.0.0;python_version=='3.7' In nova setup.cfg. it adds python require info. python-requires = >=3.6 Then we built python3 related packages to the base image and rebuilt nova image to fix python3 issue. But there is still an error below. collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) ERROR: Could not find a version that satisfies the requirement libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) (from versions: none) ERROR: No matching distribution found for libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 From code, I saw that we already built libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl through a patch which Seems related to python2. cgcs-root/stx/integ/virt/libvirt-python/centos/meta_patches$ 0002-Build-python-wheel.patch It needs libvirt-python whl for python3, right? Do we have plan to upgrade libvirt-python to 6.0.0? Any comment? Thanks a lot! Zhipeng From: Penney, Don > Sent: 2020年2月27日 0:25 To: YuChengDe >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I was able to successfully build stx-nova image in master with no changes. Do you have any customizations in your environment? From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 26, 2020 10:38 AM To: YuChengDe; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 [Image removed by sender.] -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From kristal.dale at intel.com Fri Mar 13 17:11:25 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Fri, 13 Mar 2020 17:11:25 +0000 Subject: [Starlingx-discuss] StarlingX docs team - new addition In-Reply-To: References: <387E6828-2F10-4815-86E9-44E61E5F9847@intel.com> Message-ID: Aww thanks everyone! I’m blushing :D It has been a real pleasure to work on the project and with all the awesome StarlingX folks (Ask Mary, I have sung the groups praises…). I’ll miss being a part of it. Hopefully our paths with cross again! Kris From: Eslimi, Dariush Sent: Thursday, March 12, 2020 7:36 AM To: Cobbley, David A ; Jones, Bruce E ; Dale, Kristal Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX docs team - new addition +2, should I submit a gerrit review for this ? ☺ Thanks for all the help and lots of positive energy. Dariush From: Cobbley, David A [mailto:david.a.cobbley at intel.com] Sent: March-11-20 7:45 PM To: Jones, Bruce E >; Dale, Kristal > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX docs team - new addition I second that; your work has been amazing, and the team will miss you! -- David C From: "Jones, Bruce E" > Date: Wednesday, March 11, 2020 at 2:48 PM To: "Dale, Kristal" > Cc: "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] StarlingX docs team - new addition Kris, thank you so much for all of your contributions to StarlingX. Thanks to your efforts, the project has made enormous progress in the quality of our documentation. Your can-do attitude, your drive and your passion are a joy to be around. You will be missed! brucej From: Dale, Kristal [mailto:kristal.dale at intel.com] Sent: Wednesday, March 11, 2020 2:33 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX docs team - new addition Hello All, Following up to the community call this morning, I wanted to introduce the newest member of the docs team: Mary Camp! Mary has previously contributed to the StarlingX docs and I have worked with her on other Intel projects – she’s a great addition to the team. This will be my last week on the StarlingX docs project – it has been a great experience working with you all! And, starting this week Mary will be taking my place on the docs team. Any questions, issues, etc. that were previously directed to me should now be directed to Mary. Thanks everyone – and welcome Mary! Cheers, Kris -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Fri Mar 13 20:53:21 2020 From: jimmy at openstack.org (Jimmy McArthur) Date: Fri, 13 Mar 2020 15:53:21 -0500 Subject: [Starlingx-discuss] [starlingx.io] SEO Improvements Message-ID: <5E6BF2C1.9000506@openstack.org> Hi all - We've contracted a professional SEO firm to help improve search placement for all OSF projects. I'd like to crowd source this on each of the project mailing lists, so the community is able to be involved. Could you all help out in providing the below: “Wish List” of keywords: 8-12 big terms you think fit your domain (if you only have 4-5 to share, fewer is okay) - container-based infrastructure - edge computing - ? At least 3 competitors - ? Any other input on positioning, offerings, etc. that you think will help best filter for relevance - ? Cheers, Jimmy -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Sat Mar 14 02:30:32 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Sat, 14 Mar 2020 02:30:32 +0000 Subject: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images In-Reply-To: References: <93814834B4855241994F290E959305C75314CC61@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314D245@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314D262@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314D9F9@SHSMSX104.ccr.corp.intel.com> Message-ID: Thanks Don! We will try to do it further according to your proposal. Zhipeng From: Penney, Don Sent: 2020年3月14日 0:24 To: Liu, ZhipengS ; YuChengDe ; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I believe this has dependencies on a variety of StarlingX modules which are currently python2 only. You’ll probably need to exclude starlingx-dashboard for your initial builds, until all the required modules are available for python3. That said, it would be using only small components of these. So an initial effort to get python3 wheels for all the required modules may be small. Smaller than the effort to get these running as python3 on-host, certainly. From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Friday, March 13, 2020 12:20 PM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, We have finished 11/13 images build except for horizon and glance. For horizon, it needs starlingx-dashboard python3 whl. However, in our current build, we just build out starlingx-dashboard python2 whl. Do you have any proposal on how to get the required python3 whl. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 21:00 To: 'Liu, ZhipengS' >; 'Penney, Don' >; 'YuChengDe' >; 'starlingx-discuss at lists.starlingx.io' > Cc: 'Somerville, Jim' > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, Chant and I already fixed this issue and other related dependent packages. We modified docker file and related script for wheel build, and rebuilt out all python3 wheels for the packages in stable-wheels.cfg. As for libvirt-python, we still use 4.7.0 version and rebuilt out python3 wheel currently. Will let you know the status after finishing all image build. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 0:06 To: 'Liu, ZhipengS' >; Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images We also had below issue during build other service image. Looking in links: /tmp/wheels/ Collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) Collecting PyMySQL===0.9.3 Downloading PyMySQL-0.9.3-py2.py3-none-any.whl (47 kB) Processing /tmp/wheels/python_memcached-1.59-py2.py3-none-any.whl Collecting six===1.14.0 Downloading six-1.14.0-py2.py3-none-any.whl (10 kB) Collecting cffi===1.14.0 Downloading cffi-1.14.0-cp36-cp36m-manylinux1_x86_64.whl (399 kB) ERROR: Could not find a version that satisfies the requirement uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) (from versions: none) ERROR: No matching distribution found for uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) Actually, we get uWSGI-2.0.17.1-cp27-cp27mu-linux_x86_64.whl through the link in stable-config file. So far, not sure how many python3 packages we need. From: Liu, ZhipengS > Sent: 2020年3月9日 23:44 To: Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: Re: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! See my inline comments. From: Penney, Don > Sent: 2020年3月9日 23:18 To: Liu, ZhipengS >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I think building the openstack master branch will require moving the images to python3. This has implications to the base image, to how we build the base wheels tarball, and possibly to arguments passed to loci (as well as moving to a newer loci SHA). >> Yes, we have to set python3 = true to loci and also fix a small known bug. I believe Al started looking at this last week, but got pulled off to look at some other issues. From your reply, it sounds like maybe you’ve also done some of this? >> Yes When we explicitly add wheels to the tarball, we update the upper-constraints file to align with the module we’ve included. This would be why the build is looking for 4.7.0 here. There is an upper-constraints.txt file in the tarball itself which you can check. >> Yes, in our script, if we have 4.7.0 in stx repo, it will change the version to 4.7.0 from other versions specified in upper-constraints.txt The libvirt wheel building is python2 only, currently. So it would need to be built for python3 - if that’s possible for 4.7.0. If a newer version of libvirt-python is needed for python3 support, then it will need to be updated. I don’t know how big that effort will be. >> From code, libvirt-python 4.7.0 can support both python2 and python3, but in our code, we just add patch to let it build out python2 whl. >> libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, March 05, 2020 1:06 AM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Penney, We just used OpenStack master branch and upper-constraint file below https://raw.githubusercontent.com/openstack/requirements/master/upper-constraints.txt libvirt-python===5.10.0;python_version=='2.7' libvirt-python===6.0.0;python_version=='3.6' libvirt-python===6.0.0;python_version=='3.7' In nova setup.cfg. it adds python require info. python-requires = >=3.6 Then we built python3 related packages to the base image and rebuilt nova image to fix python3 issue. But there is still an error below. collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) ERROR: Could not find a version that satisfies the requirement libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) (from versions: none) ERROR: No matching distribution found for libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 From code, I saw that we already built libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl through a patch which Seems related to python2. cgcs-root/stx/integ/virt/libvirt-python/centos/meta_patches$ 0002-Build-python-wheel.patch It needs libvirt-python whl for python3, right? Do we have plan to upgrade libvirt-python to 6.0.0? Any comment? Thanks a lot! Zhipeng From: Penney, Don > Sent: 2020年2月27日 0:25 To: YuChengDe >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I was able to successfully build stx-nova image in master with no changes. Do you have any customizations in your environment? From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 26, 2020 10:38 AM To: YuChengDe; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 [Image removed by sender.] -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From poornima.y.n at intel.com Sat Mar 14 21:42:07 2020 From: poornima.y.n at intel.com (N, Poornima Y) Date: Sat, 14 Mar 2020 21:42:07 +0000 Subject: [Starlingx-discuss] Unable to download all RPMs of CENTOS Message-ID: <337CF5EE66FD714294A89A3DB1597BA28CA66047@BGSMSX101.gar.corp.intel.com> Hi all, When I do bash download_mirror.sh to download all the required packages. I see that so many missing rpms, using the command cat logs/*_missing_*.log. I tried to download individually. But, the list is huge to do manually! When I checked the log file, I see below error for missing packages. failure: repodata/repomd.xml from CENGN_centos-openstack-queens: [Errno 256] No more mirrors to try. http://mirror.starlingx.cengn.ca:80/mirror/centos/centos/mirror.centos.org/centos/7/cloud/x86_64/openstack-queens/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found --> start searching /tmp/tmp_lst_dir_lLSxhN/rpms_centos3rdparties.lst now the rpm will come from: centos3rdparties Looking for adwaita-cursor-theme-3.28.0-1.el7.noarch.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_qGNZG9/yum.conf --releasever=7 --exclude='*.i686' --archlist=noarch,x86_64 adwaita-cursor-theme-3.28.0-1.el7 Caching enabled but no local cache of /tmp/stx_mirror_qGNZG9/cache/yum/x86_64/7/CENGN_Starlingx-C7.2.1511-cloud-newton/20861a4d958e087c6954094053b3ea90bc2ac5d9efe5b4a751f3c55f19ee430c-primary.sqlite.bz2 from CENGN_Starlingx-C7.2.1511-cloud-newton Warning: adwaita-cursor-theme-3.28.0-1.el7.noarch.rpm not found Looking for adwaita-cursor-theme-3.28.0-1.el7.noarch.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_qGNZG9/yum.conf --releasever=7 --exclude='*.i686' --archlist=noarch,x86_64 adwaita-cursor-theme-3.28.0-1.el7 Caching enabled but no local cache of /tmp/stx_mirror_qGNZG9/cache/yum/x86_64/7/CENGN_Starlingx-C7.2.1511-cloud-newton/20861a4d958e087c6954094053b3ea90bc2ac5d9efe5b4a751f3c55f19ee430c-primary.sqlite.bz2 from CENGN_Starlingx-C7.2.1511-cloud-newton Warning: adwaita-cursor-theme-3.28.0-1.el7.noarch.rpm not found Error: adwaita-cursor-theme-3.28.0-1.el7.noarch.rpm not found Can anyone please suggest as to how to resolve the issue? Thanks and Regards, Poornima -------------- next part -------------- An HTML attachment was scrubbed... URL: From ji at sibyl.li Sun Mar 15 01:12:56 2020 From: ji at sibyl.li (Austin Gillmann) Date: Sat, 14 Mar 2020 20:12:56 -0500 Subject: [Starlingx-discuss] Openstack reapply failing In-Reply-To: References: Message-ID: Hello again Mingyuan and team, While this workaround still works fine for me, the issue of applying still persists and can get annoying having to wipe network and disk images to make a helm edit. As said before it seems like it's not just PDB that is out of helms control, but everything including secrets, service accounts, and RBAC. I am curious if running SAS disks on my OSD has anything to do with this... If there is a possible fix or an associated bug I can track please let me know! Thank you! Austin Gillmann On Thu, Feb 13, 2020 at 9:51 PM Qi, Mingyuan wrote: > > Yes, you can always remove the stx-openstack application if you do not need to keep the data within mariadb database. > > > > Mingyuan > > > > From: Austin Gillmann > Sent: Friday, February 14, 2020 8:36 > To: Qi, Mingyuan ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Openstack reapply failing > > > > Hi again! > > > > Seems I found a workaround to my issue, by removing the application that seems to clean up everything well enough to apply successfully again! Albeit destructive it seems to have worked well. > > > > Best regards, > > Austin > > > > On Thu, Feb 13, 2020 at 8:28 AM Austin Gillmann wrote: > > Hi Mingyuan, > > I checked the PDB list and neutron-server was indeed listed so I > deleted it, however it seems kubernetes is playing whack-a-mole with > me; so far I had to delete secrets, serviceaccounts, and RBAC roles as > it seems like helm does not have control on *any* neutron related > items > > Best regards, > Austin > > On Thu, Feb 13, 2020 at 6:42 AM Qi, Mingyuan wrote: > > > > Hi Austin, > > > > Could you check the pdb resources in openstack namespace when reapplying the opentack app? `$ Kubectl -n openstack get pdb` > > I suspect that neutron-server pdb is out of helm chart's control for some reason. And you could try to delete it only and re-apply the app again. > > > > Mingyuan > > > > -----Original Message----- > > From: Austin Gillmann > > Sent: Sunday, February 9, 2020 2:00 > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] Openstack reapply failing > > > > Hi all, > > > > My earlier email was never replied to so I will try to re-word it: > > > > I recently deployed StarlingX 3.0 under a dedicated storage standard cluster (the storage servers running on dell r740xd's with HDD's and compute/controllers running on HP bl460c G8 blades with 2 SSD's) the stx-openstack application applies successfully on the first try, but will abort upon reapply for a config change or such. > > > > The errors armada puts out is details = "release osh-openstack-neutron > > failed: poddisruptionbudgets.policy "neutron-server" already exists" > > and "getting deployed release "osh-openstack-neutron": release: > > "osh-openstack-neutron" not found" > > > > Everything else in logs look normal to me, but let me know if you need any files attached! If anyone has any idea how to get past this please let me know! > > > > Best wishes, > > Austin Gillmann > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ji at sibyl.li Sun Mar 15 03:04:10 2020 From: ji at sibyl.li (Austin Gillmann) Date: Sat, 14 Mar 2020 22:04:10 -0500 Subject: [Starlingx-discuss] Openstack reapply failing In-Reply-To: References: Message-ID: Furthermore, I get the following traceback when attempting to apply or delete the application after letting the cluster sit: ``` sysinv 2020-03-15 02:43:38.049 1094205 INFO sysinv.conductor.kube_app [-] Application stx-openstack (1.0-19-centos-stable-latest) apply started. sysinv 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app [-] File does not exists: /tmp/tmpz3U7_z: ConfigException: File does not exists: /tmp/tmpz3U7_z 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app Traceback (most recent call last): 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app File "/usr/lib64/python2.7/site-packages/sysinv/conductor/kube_app.py", line 1947, in perform_app_apply 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app self._create_local_registry_secrets(app.name) 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app File "/usr/lib64/python2.7/site-packages/sysinv/conductor/kube_app.py", line 1002, in _create_local_registry_secrets 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app self._kube.kube_get_secret(DOCKER_REGISTRY_SECRET, ns)): 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app File "/usr/lib64/python2.7/site-packages/sysinv/common/kubernetes.py", line 192, in kube_get_secret 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app c = self._get_kubernetesclient_core() 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app File "/usr/lib64/python2.7/site-packages/sysinv/common/kubernetes.py", line 78, in _get_kubernetesclient_core 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app self._load_kube_config() 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app File "/usr/lib64/python2.7/site-packages/sysinv/common/kubernetes.py", line 63, in _load_kube_config 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app config.load_kube_config('/etc/kubernetes/admin.conf') 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app File "/usr/lib/python2.7/site-packages/kubernetes/config/kube_config.py", line 531, in load_kube_config 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app loader.load_and_set(config) 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app File "/usr/lib/python2.7/site-packages/kubernetes/config/kube_config.py", line 413, in load_and_set 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app self._load_cluster_info() 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app File "/usr/lib/python2.7/site-packages/kubernetes/config/kube_config.py", line 392, in _load_cluster_info 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app file_base_path=self._config_base_path).as_file() 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app File "/usr/lib/python2.7/site-packages/kubernetes/config/kube_config.py", line 116, in as_file 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app raise ConfigException("File does not exists: %s" % self._file) 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app ConfigException: File does not exists: /tmp/tmpz3U7_z 2020-03-15 02:43:38.832 1094205 ERROR sysinv.conductor.kube_app ``` On Sat, Mar 14, 2020 at 8:12 PM Austin Gillmann wrote: > > Hello again Mingyuan and team, > > While this workaround still works fine for me, the issue of applying > still persists and can get annoying having to wipe network and disk > images to make a helm edit. As said before it seems like it's not just > PDB that is out of helms control, but everything including secrets, > service accounts, and RBAC. I am curious if running SAS disks on my > OSD has anything to do with this... If there is a possible fix or an > associated bug I can track please let me know! > > Thank you! > Austin Gillmann > > On Thu, Feb 13, 2020 at 9:51 PM Qi, Mingyuan wrote: > > > > Yes, you can always remove the stx-openstack application if you do not need to keep the data within mariadb database. > > > > > > > > Mingyuan > > > > > > > > From: Austin Gillmann > > Sent: Friday, February 14, 2020 8:36 > > To: Qi, Mingyuan ; starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] Openstack reapply failing > > > > > > > > Hi again! > > > > > > > > Seems I found a workaround to my issue, by removing the application that seems to clean up everything well enough to apply successfully again! Albeit destructive it seems to have worked well. > > > > > > > > Best regards, > > > > Austin > > > > > > > > On Thu, Feb 13, 2020 at 8:28 AM Austin Gillmann wrote: > > > > Hi Mingyuan, > > > > I checked the PDB list and neutron-server was indeed listed so I > > deleted it, however it seems kubernetes is playing whack-a-mole with > > me; so far I had to delete secrets, serviceaccounts, and RBAC roles as > > it seems like helm does not have control on *any* neutron related > > items > > > > Best regards, > > Austin > > > > On Thu, Feb 13, 2020 at 6:42 AM Qi, Mingyuan wrote: > > > > > > Hi Austin, > > > > > > Could you check the pdb resources in openstack namespace when reapplying the opentack app? `$ Kubectl -n openstack get pdb` > > > I suspect that neutron-server pdb is out of helm chart's control for some reason. And you could try to delete it only and re-apply the app again. > > > > > > Mingyuan > > > > > > -----Original Message----- > > > From: Austin Gillmann > > > Sent: Sunday, February 9, 2020 2:00 > > > To: starlingx-discuss at lists.starlingx.io > > > Subject: [Starlingx-discuss] Openstack reapply failing > > > > > > Hi all, > > > > > > My earlier email was never replied to so I will try to re-word it: > > > > > > I recently deployed StarlingX 3.0 under a dedicated storage standard cluster (the storage servers running on dell r740xd's with HDD's and compute/controllers running on HP bl460c G8 blades with 2 SSD's) the stx-openstack application applies successfully on the first try, but will abort upon reapply for a config change or such. > > > > > > The errors armada puts out is details = "release osh-openstack-neutron > > > failed: poddisruptionbudgets.policy "neutron-server" already exists" > > > and "getting deployed release "osh-openstack-neutron": release: > > > "osh-openstack-neutron" not found" > > > > > > Everything else in logs look normal to me, but let me know if you need any files attached! If anyone has any idea how to get past this please let me know! > > > > > > Best wishes, > > > Austin Gillmann > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From chen.dq at neusoft.com Mon Mar 16 01:43:19 2020 From: chen.dq at neusoft.com (chen.dq at neusoft.com) Date: Mon, 16 Mar 2020 01:43:19 +0000 Subject: [Starlingx-discuss] =?gb2312?b?tPC4tDogVW5hYmxlIHRvIGRvd25sb2Fk?= =?gb2312?b?IGFsbCBSUE1zIG9mIENFTlRPUw==?= In-Reply-To: <337CF5EE66FD714294A89A3DB1597BA28CA66047@BGSMSX101.gar.corp.intel.com> References: <337CF5EE66FD714294A89A3DB1597BA28CA66047@BGSMSX101.gar.corp.intel.com> Message-ID: Hi Poornima: I also encountered the same problem, and my solution was to delete StarlingX_CentOS-OpenStack-queens.repo, StarlingX_CentOS-OpenStack-rocky.repo. This is a temporary method. As the website http://mirror.starlingx.cengn.ca:80/mirror/centos/centos/mirror.centos.org/centos/7/cloud/x86_64/openstack-queens was modified, repomd.xml was not found. ________________________________ 发件人: N, Poornima Y 发送时间: 2020年3月15日 5:42:07 收件人: starlingx-discuss at lists.starlingx.io 主题: [Starlingx-discuss] Unable to download all RPMs of CENTOS Hi all, When I do bash download_mirror.sh to download all the required packages. I see that so many missing rpms, using the command cat logs/*_missing_*.log. I tried to download individually. But, the list is huge to do manually! When I checked the log file, I see below error for missing packages. failure: repodata/repomd.xml from CENGN_centos-openstack-queens: [Errno 256] No more mirrors to try. http://mirror.starlingx.cengn.ca:80/mirror/centos/centos/mirror.centos.org/centos/7/cloud/x86_64/openstack-queens/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found --> start searching /tmp/tmp_lst_dir_lLSxhN/rpms_centos3rdparties.lst now the rpm will come from: centos3rdparties Looking for adwaita-cursor-theme-3.28.0-1.el7.noarch.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_qGNZG9/yum.conf --releasever=7 --exclude='*.i686' --archlist=noarch,x86_64 adwaita-cursor-theme-3.28.0-1.el7 Caching enabled but no local cache of /tmp/stx_mirror_qGNZG9/cache/yum/x86_64/7/CENGN_Starlingx-C7.2.1511-cloud-newton/20861a4d958e087c6954094053b3ea90bc2ac5d9efe5b4a751f3c55f19ee430c-primary.sqlite.bz2 from CENGN_Starlingx-C7.2.1511-cloud-newton Warning: adwaita-cursor-theme-3.28.0-1.el7.noarch.rpm not found Looking for adwaita-cursor-theme-3.28.0-1.el7.noarch.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_qGNZG9/yum.conf --releasever=7 --exclude='*.i686' --archlist=noarch,x86_64 adwaita-cursor-theme-3.28.0-1.el7 Caching enabled but no local cache of /tmp/stx_mirror_qGNZG9/cache/yum/x86_64/7/CENGN_Starlingx-C7.2.1511-cloud-newton/20861a4d958e087c6954094053b3ea90bc2ac5d9efe5b4a751f3c55f19ee430c-primary.sqlite.bz2 from CENGN_Starlingx-C7.2.1511-cloud-newton Warning: adwaita-cursor-theme-3.28.0-1.el7.noarch.rpm not found Error: adwaita-cursor-theme-3.28.0-1.el7.noarch.rpm not found Can anyone please suggest as to how to resolve the issue? Thanks and Regards, Poornima --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Mon Mar 16 07:11:40 2020 From: austin.sun at intel.com (Sun, Austin) Date: Mon, 16 Mar 2020 07:11:40 +0000 Subject: [Starlingx-discuss] kernel upgrade call for tests Message-ID: Hi community and test team: As you may know, kernel will be upgraded to 4.18 topic is in [1] , and some drivers are upgraded according. Need function tests are needed for some specific HW. HW/Drivers are upgraded and needed to be tested : ixgbe & ixgbevf tpm/integrity e1000e Mellanox drivers HW/Drivers are not upgraded , but it is better to test. iavf opae-fpga HW/Drivers are not upgraded and sanity test passed. drbd i40e qat [1] https://review.opendev.org/#/q/status:open+project:starlingx/integ+branch:master+topic:4.18_kernel Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mingyuan.qi at intel.com Mon Mar 16 07:43:42 2020 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Mon, 16 Mar 2020 07:43:42 +0000 Subject: [Starlingx-discuss] Openstack reapply failing In-Reply-To: References: Message-ID: You can file a new bug or search for similar issues on https://bugs.launchpad.net/starlingx Mingyuan -----Original Message----- From: Austin Gillmann Sent: Sunday, March 15, 2020 9:13 To: Qi, Mingyuan Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Openstack reapply failing Hello again Mingyuan and team, While this workaround still works fine for me, the issue of applying still persists and can get annoying having to wipe network and disk images to make a helm edit. As said before it seems like it's not just PDB that is out of helms control, but everything including secrets, service accounts, and RBAC. I am curious if running SAS disks on my OSD has anything to do with this... If there is a possible fix or an associated bug I can track please let me know! Thank you! Austin Gillmann On Thu, Feb 13, 2020 at 9:51 PM Qi, Mingyuan wrote: > > Yes, you can always remove the stx-openstack application if you do not need to keep the data within mariadb database. > > > > Mingyuan > > > > From: Austin Gillmann > Sent: Friday, February 14, 2020 8:36 > To: Qi, Mingyuan ; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Openstack reapply failing > > > > Hi again! > > > > Seems I found a workaround to my issue, by removing the application that seems to clean up everything well enough to apply successfully again! Albeit destructive it seems to have worked well. > > > > Best regards, > > Austin > > > > On Thu, Feb 13, 2020 at 8:28 AM Austin Gillmann wrote: > > Hi Mingyuan, > > I checked the PDB list and neutron-server was indeed listed so I > deleted it, however it seems kubernetes is playing whack-a-mole with > me; so far I had to delete secrets, serviceaccounts, and RBAC roles as > it seems like helm does not have control on *any* neutron related > items > > Best regards, > Austin > > On Thu, Feb 13, 2020 at 6:42 AM Qi, Mingyuan wrote: > > > > Hi Austin, > > > > Could you check the pdb resources in openstack namespace when > > reapplying the opentack app? `$ Kubectl -n openstack get pdb` I suspect that neutron-server pdb is out of helm chart's control for some reason. And you could try to delete it only and re-apply the app again. > > > > Mingyuan > > > > -----Original Message----- > > From: Austin Gillmann > > Sent: Sunday, February 9, 2020 2:00 > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] Openstack reapply failing > > > > Hi all, > > > > My earlier email was never replied to so I will try to re-word it: > > > > I recently deployed StarlingX 3.0 under a dedicated storage standard cluster (the storage servers running on dell r740xd's with HDD's and compute/controllers running on HP bl460c G8 blades with 2 SSD's) the stx-openstack application applies successfully on the first try, but will abort upon reapply for a config change or such. > > > > The errors armada puts out is details = "release > > osh-openstack-neutron > > failed: poddisruptionbudgets.policy "neutron-server" already exists" > > and "getting deployed release "osh-openstack-neutron": release: > > "osh-openstack-neutron" not found" > > > > Everything else in logs look normal to me, but let me know if you need any files attached! If anyone has any idea how to get past this please let me know! > > > > Best wishes, > > Austin Gillmann > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From yong.hu at intel.com Mon Mar 16 08:09:59 2020 From: yong.hu at intel.com (Hu, Yong) Date: Mon, 16 Mar 2020 08:09:59 +0000 Subject: [Starlingx-discuss] about upgrading 3 OpenStack services on platform Message-ID: Hi community members, Here is a topic I like to get your feedback. Currently we are using 3 OpenStack services on StarlingX platform natively, besides those containerized OpenStack services. They are keystone, barbican and horizon for stx-gui, which are still with version “Stein” as of today. Previously when we were making plan for stx.4.0 release, we aimed at upgrading these 3 services from “Stein” to “U”, to align with containerized services (in progress of upgrading to “U”). However, now we have to give up this upgrade for stx.4.0, because: 1). CentOS 7.x doesn’t have plan to provide packages for OpenStack “U”, so we cannot make the upgrade based on CentOS 7.x. 2). CentOS 8.x has the plan to provide packages for OpenStack “U”, but we won’t go there for stx.4.0 accordingly the decision from the meet-up in AZ two weeks ago. Alternatively, we have some options: 1). For stx.4.0, we upgrade these 3 services from “Stein” to “Train”, which CentOS 7.x has already supported. It’s not perfect, but we are 1 step ahead. And then in stx.5.0, we move on from “Train” to “U”. Question: *Is this valuable??** 2). We simply defer this upgrade to stx.5.0, by when we expect we can get full support base packages on CentOS 8.x for OpenStack “U”. Please share your feedback if you care this matter. Regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Mon Mar 16 08:56:50 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Mon, 16 Mar 2020 08:56:50 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. In-Reply-To: <93814834B4855241994F290E959305C75314F6B2@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314F6B2@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Joseph, I tried many methods, but still not fixed the issue. I found there are some related issued fixed in upstream, but not yet merged to formal release. I’m discussing with them. Do you have any comment? https://github.com/rabbitmq/rabbitmq-peer-discovery-k8s/issues/55 Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月12日 9:53 To: 'Richard, Joseph' ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, Thank you so much! 😊 I will work further based on your provided clue. Best Regards, Zhipeng From: Richard, Joseph > Sent: 2020年3月12日 5:06 To: Liu, ZhipengS >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. I see a similar issue online here: https://groups.google.com/forum/#!topic/rabbitmq-users/9ir1WK-nYBA [http://www.google.com/images/icons/product/groups-128.png] epmd fails to start in IPv6 environment Posted 7/15/19 9:43 PM, 12 messages groups.google.com I expect that you are going to have to update rabbmitmq docker images to 3.7.16(currently 3.7.13), and then modify the helm plugin to pass in these values when using ipv6: SERVER_ADDITIONAL_ERL_ARGS='-proto_dist inet6_tcp' CTL_ERL_ARGS='-proto_dist inet6_tcp' Not sure if this is possible right now, or if you will need to modify openstack-helm-infra/rabbitmq in order to be able to pass these environment variables in. ________________________________ From: Liu, ZhipengS > Sent: Thursday, February 27, 2020 8:00 AM To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi all, For below LP IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status" https://bugs.launchpad.net/starlingx/+bug/1859641 I provided a patch which can fix the known issue in LP. However, it still failed later when starting rabbitmq pod. controller-0:~$ kubectl -n openstack get po NAME READY STATUS RESTARTS AGE ingress-c74489c96-jsb7n 1/1 Running 0 17h ingress-error-pages-5889bfcf6c-h8kl6 1/1 Running 0 17h mariadb-ingress-b5cd65f4b-sq46c 1/1 Running 0 17h mariadb-ingress-error-pages-6d8b79b74f-9zmpc 1/1 Running 0 17h mariadb-server-0 1/1 Running 0 17h osh-openstack-memcached-memcached-545668bdbd-9jkv2 1/1 Running 0 17h osh-openstack-rabbitmq-cluster-wait-wbnwp 0/1 Init:0/2 0 17h osh-openstack-rabbitmq-rabbitmq-0 0/1 CrashLoopBackOff 207 17h There are below error logs 2020-02-26T07:43:36.451103975Z stderr F ++ echo osh-openstack-rabbitmq-rabbitmq-0 2020-02-26T07:43:36.45142814Z stderr F ++ awk -F - '{print $NF}' 2020-02-26T07:43:36.454160452Z stderr F + POD_INCREMENT=0 2020-02-26T07:43:36.454757022Z stderr F + '[' 0 -eq 0 ']' 2020-02-26T07:43:36.454795721Z stderr F + exec rabbitmq-server 2020-02-26T07:43:36.849021551Z stdout F ERROR: epmd error for host osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local: nxdomain (non-existing domain) In /etc/hosts file below, I just found localhost4, no localhost6. Is it expected? I added below line manually after the line of 127.0.0.1. However, it didn’t work☹ ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 # HEADER: This file was autogenerated at 2020-02-26 09:00:35 +0000 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 fd01::1 controller 169.254.202.1 pxecontroller fd00::3 oamcontroller fd01::4 controller-platform-nfs fd01::3 controller-1 fd01::2 controller-0 fd02::3 controller-1-cluster-host fd02::2 controller-0-cluster-host fd01::e8b6:66fe storage-0 I saw that in ./stx-puppet/puppet-manifests/src/modules/platform/manifests/config.pp:215 class platform::config::hosts inherits ::platform::config::params { # The localhost should resolve to the IPv4 loopback address only, therefore # ensure the IPv6 address is removed from configured hosts resources { 'host': purge => true } $localhost = { 'localhost' => { ip => '127.0.0.1', host_aliases => ['localhost.localdomain', 'localhost4', 'localhost4.localdomain4'] }, } $merged_hosts = merge($localhost, $hosts) create_resources('host', $merged_hosts, {}) } Any one can give some help? Thanks! Zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From mihail-laurentiu.trica at intel.com Mon Mar 16 12:04:47 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Mon, 16 Mar 2020 12:04:47 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build - ISO 20200313 In-Reply-To: References: Message-ID: Hello Bjoern, We are not creating the images present on CENGN. What do you mean by “not labeling the results as GREEN”? The results for the image created today are not yet available and we are not sending emails for images create during the weekend. Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer From: Bruecher, Bjoern Sent: Monday, March 16, 2020 1:44 PM To: Trica, Mihail-Laurentiu Cc: Wagner, Marcel ; Shashi, Yatindra Subject: RE: [Starlingx-discuss] Sanity Master Test MONOLITHIC build - ISO 20200313 Hi, Are we no longer labeling the results as GREEN in the output directory? Do we no longer propagate the known GREEN images to the http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_green_build/ folder? Thanks, Bjoern From: Trica, Mihail-Laurentiu > Sent: Friday, March 13, 2020 13:54 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build - ISO 20200313 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-13 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers – 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 ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard external setup in the virtual environment failed because of an automation issue (the corresponding job on bare metal was successful). Regards, STX Validation Team Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From abhideodhar at gmail.com Mon Mar 16 12:21:35 2020 From: abhideodhar at gmail.com (Abhijit Deodhar) Date: Mon, 16 Mar 2020 17:51:35 +0530 Subject: [Starlingx-discuss] StarlingX and Openstack installation Message-ID: I am trying to install Openstack with StarlingX by following the instructions mentioned here: https://docs.starlingx.io/deploy_install_guides/r3_release/openstack/install.html I completed the above steps and then I tried to access the local CLI using these steps: https://docs.starlingx.io/deploy_install_guides/r3_release/openstack/access.html The document has this step: Configure helm endpoint domain For a lab setup where I dont expect any queries from outside the localhost, Is this step required? I skipped the above step and configured the clouds.yaml. I hit few issues: 1) I cannot access the GUI using the :31000 port from the browser? 2) The local CLI commands such as "openstack image list" keep failing with controller-0:~$ openstack image list Failed to discover available identity versions when contacting http://keystone.openstack.svc.cluster.local/v3. Attempting to parse version from URL. Service Unavailable (HTTP 503) controller-0:~$ source /etc/platform/openrc [sysadmin at controller-0 ~(keystone_admin)]$ export OS_CLOUD=openstack_helm [sysadmin at controller-0 ~(keystone_admin)]$ openstack image list The request you have made requires authentication. (HTTP 401) (Request-ID: req-ed0117db-5fc2-4d21-9175-d8fcd6434fb7) I am not sure what exactly I am missing wrt the configuration. Can someone please help me by providing any pointers ? Thanks Abhijit -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Mon Mar 16 13:31:27 2020 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Mon, 16 Mar 2020 13:31:27 +0000 Subject: [Starlingx-discuss] ceph containerization patch review In-Reply-To: References: Message-ID: Martin, At the mid cycle meeting we established: 1) We have to keep the existing ceph implementation to allow existing users to transition post stx.4.0. The existing implementation would then be removed in stx.5.0. Therefore I do not understand what you are proposing in point 1 below. 2) We did not want to couple the rook/ceph implementation to sysinv. Therefore why would we have it manage the volume groups for rook ? Brent From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Thursday, March 12, 2020 8:06 PM To: Miller, Frank ; 'starlingx-discuss at lists.starlingx.io' ; Rowsell, Brent ; Waines, Greg Cc: Chen, Tingjie ; Sun, Austin ; Qi, Mingyuan ; Church, Robert Subject: ceph containerization patch review Hi Brent & Frank I already finish my new application and helm plugin for rook-ceph. But still two concern to discuss. 1, decouple ceph backend with sysinv. Now ceph backend has been removed as default storage backend. And I plan to add rook-ceph as another storage backend which user could enable by his provision. So what about decouple ceph backend with sysinv-conductor, which is beneficial for more storage backend enabling. 2, change restriction for volume group creation in sysinv Currently sysinv has restriction for volume group creation, only permit create volume group with "nova-local", "cinder-volumes", "cgts-vg". What about remove this restriction? For containerized ceph cluster deployment, osd is provisioned by ceph-volume, which is based on logical volume. It will create a volume group, with "ceph" name prefixed. I prefer this newly created volume group could also be managed by sysinv. Currenlty ceph cluster is deployed by ceph-disk in puppet-ceph. This tool is depreciated. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Friday, February 21, 2020 11:14 PM To: 'Miller, Frank' >; 'starlingx-discuss at lists.starlingx.io' >; 'Rowsell, Brent' >; 'Greg.Waines at windriver.com' > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan >; 'Church, Robert' > Subject: RE: ceph containerization patch review Hi Frank & Bob & Greg & Brent To deploy, it is same as any other helm chart. Wait for you opinion for current solution. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Wednesday, February 19, 2020 12:53 PM To: 'Miller, Frank' >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent >; 'Greg.Waines at windriver.com' > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan >; Church, Robert > Subject: RE: ceph containerization patch review Hi folks Answer the question, with only k8s, how to deploy rook. $ helm-upload stx-platform rook-ceph-0.1.0.tga $ helm install stx-platform/rook-ceph -n rook-ceph-cluster -n kube-system -f value.yaml BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Tuesday, February 18, 2020 10:06 PM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan >; Church, Robert > Subject: RE: ceph containerization patch review +Bob who is the containers TL From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Monday, February 17, 2020 8:46 AM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan > Subject: RE: ceph containerization patch review Hi Frank & Brent For rook manage configuration, after introduce rook-ceph, current ceph cluster deployed by puppet will keep or be removed? If removed, containerized ceph cluster deployed by rook-ceph will take the role of provisioner for stx-openstack. If keeps, helm chart rbd-provisioner in platform-integ-app also keeps and takes the role of provisioner for stx-openstack. Containerized ceph cluster deployed by rook-ceph only serve as csi provider for k8s. BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, February 10, 2020 11:47 PM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan > Subject: RE: ceph containerization patch review Hi Frank: As synced with Tingjie, this is my understanding for Rook manage the configuration instead of sysinv. 1, Remove ceph config and status query from sysinv 2, create another tool, like rook-client to launch and provision ceph cluster 3, one helm plugin like rbd-provision, which depends on newly created tool BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Saturday, February 8, 2020 4:16 AM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: ceph containerization patch review Martin: Thanks for posting your reviews and the update on the current status for this feature. I was unable to attend the containerization meeting this week so wasn't able to have Tingjie or you give an update on the open actions for the feature. From the Jan 14 minutes [1] one of the actions is to determine "how can you have Rook do all the configuration and not have sysinv involved" For now I suggest you add an additional item to your Tasks to do list to identify a design that does not require sysinv for the configuration and instead has Rook manage the configuration. I would like to ask that we discuss further at the next containerization meeting and if possible review a proposal from yourself and Austin for this item. Frank [1] https://etherpad.openstack.org/p/stx-containerization From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Thursday, February 06, 2020 11:02 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] ceph containerization patch review Hi folks I enabled containerized ceph cluster with simplex. You can begin to review my patch. I propose to build an image and deploy a simplex system with these patch to check. https://review.opendev.org/#/c/681457/ https://review.opendev.org/#/c/687340/ https://review.opendev.org/#/c/706256/ https://review.opendev.org/#/c/699557/ https://review.opendev.org/#/c/699556/ And I know there is other story, like remove ceph as default backend storage, maybe some conflict, we can discuss together. Tash Done: 1, disable native ceph cluster in ceph.pp 2, disable ceph daemon monitoring in service manager 3, add rook-ceph helm chart to launch ceph cluster 4, add override in stx-config to generate override with starlingx system config 5, sysinv add label in provision stage, to make containerized ceph mon and ceph mgr on designed host 6, add rook-ceph-provisioner helm chart to generate storage class, secret, config and pool for stx-application 7, enabled stx-openstack with containerized ceph 8, update ceph wrapper in stx-config to set or get containerized ceph cluster All these tasks done is enabled with simplex only. Task to do: 1, enable add osd runtime, after system provisioned 2, fix know issue, if system reboot, ceph cluster launch fail 3, enable bluestore and filestore, currently there is only bluestore 4, enable multi-node and duplex 5, enable swift with containerized ceph 6, enable fm alarm for containerized ceph 7, check backup and restore for containerized ceph 8, check system upgrade or how to transit from native ceph cluster to containerized ceph cluster 9, code cleanup 10, update unit test in stx-config BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Thu Mar 12 14:44:33 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Thu, 12 Mar 2020 14:44:33 +0000 Subject: [Starlingx-discuss] ceph containerization patch review In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D8562ACFCA@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D8562A76F5@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A7E32@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A9371@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A97A4@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562ACFCA@CDSMSX102.ccr.corp.intel.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D859EEC857@CDSMSX102.ccr.corp.intel.com> Hi Brent & Frank I already finish my new application and helm plugin for rook-ceph. But still two concern to discuss. 1, decouple ceph backend with sysinv. Now ceph backend has been removed as default storage backend. And I plan to add rook-ceph as another storage backend which user could enable by his provision. So what about decouple ceph backend with sysinv-conductor, which is beneficial for more storage backend enabling. 2, change restriction for volume group creation in sysinv Currently sysinv has restriction for volume group creation, only permit create volume group with "nova-local", "cinder-volumes", "cgts-vg". What about remove this restriction? For containerized ceph cluster deployment, osd is provisioned by ceph-volume, which is based on logical volume. It will create a volume group, with "ceph" name prefixed. I prefer this newly created volume group could also be managed by sysinv. Currenlty ceph cluster is deployed by ceph-disk in puppet-ceph. This tool is depreciated. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Friday, February 21, 2020 11:14 PM To: 'Miller, Frank' ; 'starlingx-discuss at lists.starlingx.io' ; 'Rowsell, Brent' ; 'Greg.Waines at windriver.com' Cc: Chen, Tingjie ; Sun, Austin ; Qi, Mingyuan ; 'Church, Robert' Subject: RE: ceph containerization patch review Hi Frank & Bob & Greg & Brent To deploy, it is same as any other helm chart. Wait for you opinion for current solution. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Wednesday, February 19, 2020 12:53 PM To: 'Miller, Frank' >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent >; 'Greg.Waines at windriver.com' > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan >; Church, Robert > Subject: RE: ceph containerization patch review Hi folks Answer the question, with only k8s, how to deploy rook. $ helm-upload stx-platform rook-ceph-0.1.0.tga $ helm install stx-platform/rook-ceph -n rook-ceph-cluster -n kube-system -f value.yaml BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Tuesday, February 18, 2020 10:06 PM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan >; Church, Robert > Subject: RE: ceph containerization patch review +Bob who is the containers TL From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Monday, February 17, 2020 8:46 AM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan > Subject: RE: ceph containerization patch review Hi Frank & Brent For rook manage configuration, after introduce rook-ceph, current ceph cluster deployed by puppet will keep or be removed? If removed, containerized ceph cluster deployed by rook-ceph will take the role of provisioner for stx-openstack. If keeps, helm chart rbd-provisioner in platform-integ-app also keeps and takes the role of provisioner for stx-openstack. Containerized ceph cluster deployed by rook-ceph only serve as csi provider for k8s. BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, February 10, 2020 11:47 PM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan > Subject: RE: ceph containerization patch review Hi Frank: As synced with Tingjie, this is my understanding for Rook manage the configuration instead of sysinv. 1, Remove ceph config and status query from sysinv 2, create another tool, like rook-client to launch and provision ceph cluster 3, one helm plugin like rbd-provision, which depends on newly created tool BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Saturday, February 8, 2020 4:16 AM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: ceph containerization patch review Martin: Thanks for posting your reviews and the update on the current status for this feature. I was unable to attend the containerization meeting this week so wasn't able to have Tingjie or you give an update on the open actions for the feature. From the Jan 14 minutes [1] one of the actions is to determine "how can you have Rook do all the configuration and not have sysinv involved" For now I suggest you add an additional item to your Tasks to do list to identify a design that does not require sysinv for the configuration and instead has Rook manage the configuration. I would like to ask that we discuss further at the next containerization meeting and if possible review a proposal from yourself and Austin for this item. Frank [1] https://etherpad.openstack.org/p/stx-containerization From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Thursday, February 06, 2020 11:02 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] ceph containerization patch review Hi folks I enabled containerized ceph cluster with simplex. You can begin to review my patch. I propose to build an image and deploy a simplex system with these patch to check. https://review.opendev.org/#/c/681457/ https://review.opendev.org/#/c/687340/ https://review.opendev.org/#/c/706256/ https://review.opendev.org/#/c/699557/ https://review.opendev.org/#/c/699556/ And I know there is other story, like remove ceph as default backend storage, maybe some conflict, we can discuss together. Tash Done: 1, disable native ceph cluster in ceph.pp 2, disable ceph daemon monitoring in service manager 3, add rook-ceph helm chart to launch ceph cluster 4, add override in stx-config to generate override with starlingx system config 5, sysinv add label in provision stage, to make containerized ceph mon and ceph mgr on designed host 6, add rook-ceph-provisioner helm chart to generate storage class, secret, config and pool for stx-application 7, enabled stx-openstack with containerized ceph 8, update ceph wrapper in stx-config to set or get containerized ceph cluster All these tasks done is enabled with simplex only. Task to do: 1, enable add osd runtime, after system provisioned 2, fix know issue, if system reboot, ceph cluster launch fail 3, enable bluestore and filestore, currently there is only bluestore 4, enable multi-node and duplex 5, enable swift with containerized ceph 6, enable fm alarm for containerized ceph 7, check backup and restore for containerized ceph 8, check system upgrade or how to transit from native ceph cluster to containerized ceph cluster 9, code cleanup 10, update unit test in stx-config BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joseph.Richard at windriver.com Thu Mar 12 22:10:36 2020 From: Joseph.Richard at windriver.com (Richard, Joseph) Date: Thu, 12 Mar 2020 22:10:36 +0000 Subject: [Starlingx-discuss] iPXE for IPv6 In-Reply-To: <1EDF4B46-F06D-4834-ADBD-6DBAB3C22E3E@99cloud.net> References: <151EE31B9FCCA54397A757BC674650F0C15FF245@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0C1655A1D@ALA-MBD.corp.ad.wrs.com> <4BB34F6B-CF07-4AC0-9049-3A5AB51A0F69@99cloud.net> <151EE31B9FCCA54397A757BC674650F0C1689226@ALA-MBD.corp.ad.wrs.com>, <1EDF4B46-F06D-4834-ADBD-6DBAB3C22E3E@99cloud.net> Message-ID: Are there any error logs from sysinv or dnsmasq(daemon.log) from this time frame on the active controller? What do you see when you do a tcpdump on the active controller when this is booting? ________________________________ From: ������ Sent: Monday, March 9, 2020 6:40:54 AM To: Khalil, Ghada Cc: ����Ȫ ; Jolliffe, Ian ; Peters, Matt ; Le, Huifeng ; Yong Hu ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] iPXE for IPv6 Hi Ghada, I have tried to boot from ipxe with ipv6 pxeboot network. Dhcp server worked well and ipv6 address was auto set in the second host. But ipxe boot failed with ��no such file or directory��. BTW it is ok when I fetch the boot script with ipxe shell (boot.ipxe is my testing boot script): ipxe> chain tftp://pxecontroller/boot.ipxe It blocks, any help could be appreciated. [cid:2BA89EB8-AED7-4ED9-8CDE-D49B348DA7D9] Follows are dnsmasq config file [cid:2AFEDF4C-C861-4753-A851-C314DAEDC801] [cid:957348FB-40A5-4BB9-858C-CAE86BB9ABAF] Thanks Kunpeng �� 2020��3��5�գ�07:58��Khalil, Ghada > д���� Hello Kunpeng, Can you please share the plans for this features? Are you still targeting stx.4.0? As per my email to the stx-discuss mailing list [1], please update the feature dates. Thanks, Ghada [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/007913.html From: Khalil, Ghada Sent: Wednesday, February 12, 2020 6:15 PM To: 'Shuquan Huang'; ������ Cc: Jolliffe, Ian; Peters, Matt; Le, Huifeng; Yong Hu Subject: RE: iPXE for IPv6 Thank you for the update Shuquan. Welcome Kunpeng. Please have a look at the story and let us know when you plan to start and if you need any clarification. Regards, Ghada From: Shuquan Huang [mailto:huang.shuquan at 99cloud.net] Sent: Tuesday, February 11, 2020 3:21 AM To: Khalil, Ghada; ������ Cc: Jolliffe, Ian; Peters, Matt; Le, Huifeng; Yong Hu Subject: Re: iPXE for IPv6 Hi Ghada, Xiangdong left 99Cloud last month. Kunpeng will take over this task. Sorry about the change and the impact to the task. On Feb 7, 2020, at 6:50 AM, Khalil, Ghada > wrote: Hi Xiangdong, Happy New Year! I��m following up on the IPv6 pxeboot support in stx.4.0: https://storyboard.openstack.org/#!/story/2006442 Are you on track to start this work shortly as per your original plan? Please let us know if you need any clarification on the scope or if you want to discuss any technical details. Regards, Ghada From: ���� [mailto:huang.xiangdong at 99cloud.net] Sent: Sunday, December 01, 2019 8:48 PM To: Khalil, Ghada Cc: Shuquan Huang; Jolliffe, Ian; Peters, Matt; Le, Huifeng Subject: Re:RE: Re:RE: iPXE for IPv6 Hi, Ghada Sorry for the late reply, I plan to start in February. -- ���������������������������������������������������������� ��������Ϣ�Ƽ����޹�˾ 99CLOUD Inc. ���� ��Ʒ������ ����(Email): huang.xiangdong at 99cloud.net �ֻ�(Mobile): 15221772173 ��ַ(Addr): �Ϻ��о���·427��1��¥206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China ��ַ(Site): http://www.99cloud.net �����ˣ�"Khalil, Ghada" > �������ڣ�2019-11-28 22:48:41 �ռ��ˣ�"����" > �����ˣ�Shuquan Huang >,"Jolliffe, Ian" >,"Peters, Matt" >,"Le, Huifeng" > ���⣺RE: Re:RE: iPXE for IPv6 That��s great. Thank you. Please let us know when you plan to start this work and if there is anything we can do to help. Regards, Ghada From: ���� [mailto:huang.xiangdong at 99cloud.net] Sent: Tuesday, November 26, 2019 5:10 AM To: Khalil, Ghada Cc: Shuquan Huang; Jolliffe, Ian; Peters, Matt; Le, Huifeng Subject: Re:RE: iPXE for IPv6 Yes, I will work on this story for 4.0 -- ���������������������������������������������������������� ��������Ϣ�Ƽ����޹�˾ 99CLOUD Inc. ���� ��Ʒ������ ����(Email): huang.xiangdong at 99cloud.net �ֻ�(Mobile): 15221772173 ��ַ(Addr): �Ϻ��о���·427��1��¥206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China ��ַ(Site): http://www.99cloud.net �����ˣ�"Khalil, Ghada" > �������ڣ�2019-11-26 04:04:02 �ռ��ˣ�"����" >,Shuquan Huang > �����ˣ�"Jolliffe, Ian" >,"Peters, Matt" >,"Le, Huifeng" > ���⣺RE: iPXE for IPv6 Hi Xiangdong, We are working on stx.4.0 release planning. I��m following up on this story: https://storyboard.openstack.org/#!/story/2006442 Can you please confirm that you plan to work on this story for stx.4.0? Thanks, Ghada PS: I��d also like to take this opportunity to introduce our new stx networking PL �C Huifeng Le (copied) From: Khalil, Ghada Sent: Friday, October 18, 2019 11:48 AM To: '����'; Shuquan Huang Cc: Jolliffe, Ian; Peters, Matt Subject: RE: Re:Re: iPXE for IPv6 Hi Xiangdong, Thank you for your response. I updated the story. Matt also added a comment to clarify the scope. Please have a look and let us know if you have any questions. We also hold a starlingx networking call every two weeks where we discuss networking-related features and bugs. You are more than welcome to attend. The information is on the StarlingX wiki:https://wiki.openstack.org/wiki/Starlingx/Meetings#0615am_Pacific_-_Networking_Team_Call_.28Bi-weekly.29 The next meeting is on October 31. Regards, Ghada From: ���� [mailto:huang.xiangdong at 99cloud.net] Sent: Thursday, October 17, 2019 11:02 PM To: Shuquan Huang Cc: Khalil, Ghada; Jolliffe, Ian; Peters, Matt Subject: Re:Re: iPXE for IPv6 Hi Ghada, IPv6 PXE boot network support now only works in ipv4 + ipv6 dual-stack env, pure ipv6 env testing and deploy intergration still need some works. So I would like to put this feature on stx 4.0 list instead. Regards Xiangdong -- ���������������������������������������������������������� ��������Ϣ�Ƽ����޹�˾ 99CLOUD Inc. ���� ��Ʒ������ ����(Email): huang.xiangdong at 99cloud.net �ֻ�(Mobile): 15221772173 ��ַ(Addr): �Ϻ��о���·427��1��¥206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China ��ַ(Site): http://www.99cloud.net �����ˣ�Shuquan Huang > �������ڣ�2019-10-18 10:36:49 �ռ��ˣ�"Khalil, Ghada" > �����ˣ�"Jolliffe, Ian" >,"����" >,"Peters, Matt" > ���⣺Re: iPXE for IPv6 �򶫣� �����ظ�һ�� On Oct 18, 2019, at 06:03, Khalil, Ghada > wrote: Hi Shuquan, I see that Xiangdong recently added a few comments to the storyboard with the experiments he��s done to date. I��ve asked Matt, the stx networking TL, to have a look. Is there a target date for when this feature would be ready? stx.3.0 milestone-3 (feature freeze) is planned for next week. We can make an exception for this feature if you give me an idea of the dates you are targeting and a view of the risk of the required changes. RC1 is planned for Nov 20; that would be the absolute latest although we don��t like to wait until the very end for feature code to merge. Otherwise we will have to put this on the stx.4.0 list instead. Please let me know. Thanks, Ghada From: Shuquan Huang [mailto:huang.shuquan at 99cloud.net] Sent: Thursday, October 10, 2019 12:41 AM To: Jolliffe, Ian; ���� Cc: Khalil, Ghada Subject: Re: iPXE for IPv6 Hi Ian, Sorry for the late reply. I��m just back from the vacation due to national day holiday. Xiangdong from my team is working on it. He just kicked off some testing and will update it to the story board later. On Oct 8, 2019, at 4:26 AM, Jolliffe, Ian > wrote: Hi Shuquan; I hope you are doing well and I look forward to seeing you in Shanghai. It was great to have a call with you and your team members on the phone a couple of weeks ago. Please let us know if we can help you get started in some way on IPXE for IPv6. Maybe you have started, and we don��t have visibility. Here is the link to the story board: https://storyboard.openstack.org/#!/story/2006442 It was very nice to meet your team members over the phone as well. Regards; Ian -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-1.jpeg Type: image/jpeg Size: 50715 bytes Desc: PastedGraphic-1.jpeg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-2.png Type: image/png Size: 60497 bytes Desc: PastedGraphic-2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-3.png Type: image/png Size: 57599 bytes Desc: PastedGraphic-3.png URL: From ruediger.stock at intel.com Mon Mar 16 15:49:28 2020 From: ruediger.stock at intel.com (Stock, Ruediger) Date: Mon, 16 Mar 2020 15:49:28 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build - ISO 20200315 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-15 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200315T230004Z/outputs/iso/) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard external setup in the virtual environment failed because of an automation issue (the corresponding job on bare metal was successful). Some issues were seen about "Rebuild Cirros instances." which seem to be related to an unstable network. We are investigating these. Regards, STX Validation Team Rüdiger Stock Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Mon Mar 16 17:04:14 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 16 Mar 2020 17:04:14 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Mar 12/2020 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.4.0 - Milestone-2 is planned for March 27 - Milestone-2 Criteria - Spec freeze; no new specs accepted for the release. The focus is on closing current specs - Feature plans defined and feature development well underway - See Feature Plans google sheet: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 - See Feature Notes for a subset of features below - Release test plan defined - including test automation deliverables - There is risk regarding test in Intel due to hardware availability. Current target date is middle of April. - Server dates are committed, but still working on switching and other infrastructure - Servers can be utilized to setup a virtual environment to start - Features Awaiting Confirmation / Updates: - Python2>>3 Migration - Ongoing? - There are no python3 packages for everything we need. - This is Partial at best, but would likely be considered out - As of now, there is no python3 environment on the host yet. This would be the absolute first required step to move - Action: Bruce to follow up with Austin. - Don: We have a couple of modules/daemons that should be straightforward to move to python3. - I would start with tsconfig, creating and installing both a python2-tsconfig and a python3-tsconfig. This module is mostly constants, shared amongst STX services, along with a config file parser, and would be needed by most STX python services. - Simple daemons like utilities/logmgmt and update/patch-alarm are probably good choices for early conversion, although patch-alarm would have a dependency on FM. - Upversion Openstack to Ussuris release - From Yong (3/16): For Containerized OpenStack Services upgrading to "U", it's started and made good progress in past 2 weeks, so it will be a GO for stx.4.0. - Upversion Openstack services used by flock components on host - From Yong (3/16): For 3 OpenStack services (keystone, horizon and barbican) on platform, we have no way to upgrade it to "U" because of the dependencies on CentOS 8 user space packages, which we decided 2 weeks ago in the meet-up not to upgrade in stx.4.0. The alternative could be we upgrade to "Train" from the current "Stein". I will send a mail to the mailing-list to ask if everybody thinks it's valuable and worthy for stx.4.0. - Distributed Cloud - openstack - This is Out. Resources are focused on upgrades - Containerize Openstack clients - As per Bruce, TBD. Still need to look at resourcing - System Upgrade support - Actively being worked. Consider as In w/ Risk. - Currently working on spec and will update merge/feature test dates - IPv6 support for PXE boot network - Appears that 99cloud prime is starting to investigate. Questions posted to mailing list. - Regression Test Automation - This is an ongoing initiative. WR is planning to contribute some additional test-cases. These TCs can be run by anyone in the open once they setup the required env. - Performance Test Automation - Best effort for Intel, but should be considered out due to focus on other release test activities. - Code Scans using Bandit & Coverity - This has been transitioned to the Intel Bangalore team. At a minimum, would like to get initial results for review/analysis. - Timeline is TBD From bruce.e.jones at intel.com Mon Mar 16 20:34:12 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 16 Mar 2020 20:34:12 +0000 Subject: [Starlingx-discuss] [starlingx.io] SEO Improvements In-Reply-To: <5E6BF2C1.9000506@openstack.org> References: <5E6BF2C1.9000506@openstack.org> Message-ID: <9A85D2917C58154C960D95352B22818BF169699C@fmsmsx123.amr.corp.intel.com> My $0.02: Key words: Edge Computing, Real Time Edge Computing, OpenStack deployment, Kubernetes deployment Competitors: Kubeedge, K3S (maybe) From: Jimmy McArthur [mailto:jimmy at openstack.org] Sent: Friday, March 13, 2020 1:53 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [starlingx.io] SEO Improvements Hi all - We've contracted a professional SEO firm to help improve search placement for all OSF projects. I'd like to crowd source this on each of the project mailing lists, so the community is able to be involved. Could you all help out in providing the below: “Wish List” of keywords: 8-12 big terms you think fit your domain (if you only have 4-5 to share, fewer is okay) - container-based infrastructure - edge computing - ? At least 3 competitors - ? Any other input on positioning, offerings, etc. that you think will help best filter for relevance - ? Cheers, Jimmy -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Mon Mar 16 20:44:12 2020 From: jimmy at openstack.org (Jimmy McArthur) Date: Mon, 16 Mar 2020 15:44:12 -0500 Subject: [Starlingx-discuss] [starlingx.io] SEO Improvements In-Reply-To: <9A85D2917C58154C960D95352B22818BF169699C@fmsmsx123.amr.corp.intel.com> References: <5E6BF2C1.9000506@openstack.org> <9A85D2917C58154C960D95352B22818BF169699C@fmsmsx123.amr.corp.intel.com> Message-ID: <5E6FE51C.5000109@openstack.org> Awesome! Thanks for the feedback, Bruce! > Jones, Bruce E > March 16, 2020 at 3:34 PM > > My $0.02: > > Key words: Edge Computing, Real Time Edge Computing, OpenStack > deployment, Kubernetes deployment > > Competitors: Kubeedge, K3S (maybe) > > *From:*Jimmy McArthur [mailto:jimmy at openstack.org] > *Sent:* Friday, March 13, 2020 1:53 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] [starlingx.io] SEO Improvements > > Hi all - > > We've contracted a professional SEO firm to help improve search > placement for all OSF projects. I'd like to crowd source this on each > of the project mailing lists, so the community is able to be > involved. Could you all help out in providing the below: > > “Wish List” of keywords: 8-12 big terms you think fit your domain (if > you only have 4-5 to share, fewer is okay) > - container-based infrastructure > - edge computing > - ? > > At least 3 competitors > - ? > > Any other input on positioning, offerings, etc. that you think will > help best filter for relevance > - ? > > Cheers, > Jimmy > > Jimmy McArthur > March 13, 2020 at 3:53 PM > Hi all - > > We've contracted a professional SEO firm to help improve search > placement for all OSF projects. I'd like to crowd source this on each > of the project mailing lists, so the community is able to be > involved. Could you all help out in providing the below: > > “Wish List” of keywords: 8-12 big terms you think fit your domain (if > you only have 4-5 to share, fewer is okay) > - container-based infrastructure > - edge computing > - ? > > At least 3 competitors > - ? > > Any other input on positioning, offerings, etc. that you think will > help best filter for relevance > - ? > > Cheers, > Jimmy -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Mon Mar 16 23:31:06 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 16 Mar 2020 23:31:06 +0000 Subject: [Starlingx-discuss] Containerization meeting cancelled this week Message-ID: Please note that I need to cancel the meeting that was planned for Tuesday March 17. If there are any containerization topics please post to the mailing list and we'll discuss over email. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Mar 17 02:40:57 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 16 Mar 2020 22:40:57 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 475 - Failure! Message-ID: <2131272092.991.1584412858164.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 475 Status: Failure Timestamp: 20200316T230002Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200316T230002Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From haochuan.z.chen at intel.com Tue Mar 17 02:44:36 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 17 Mar 2020 02:44:36 +0000 Subject: [Starlingx-discuss] ceph containerization patch review In-Reply-To: References: Message-ID: Hi Brent Thanks for your comment. This is my idea. 1) We have to keep the existing ceph implementation to allow existing users to transition post stx.4.0. The existing implementation would then be removed in stx.5.0. Therefore I do not understand what you are proposing in point 1 below. I already write an application, which is no submitted as wait for Scott could create a new project for me. The helm plugin for this application is https://review.opendev.org/#/c/713084/. $ system application-list --nowrap +---------------------+---------+-------------------------------+---------------+----------+-----------+ | application | version | manifest name | manifest file | status | progress | +---------------------+---------+-------------------------------+---------------+----------+-----------+ | oidc-auth-apps | 1.0-0 | oidc-auth-manifest | manifest.yaml | uploaded | completed | | platform-integ-apps | 1.0-8 | platform-integration-manifest | manifest.yaml | uploaded | completed | | rook-ceph-apps | 1.0-1 | rook-ceph-manifest | manifest.yaml | uploaded | completed | +---------------------+---------+-------------------------------+---------------+----------+-----------+ $ system helm-override-update rook-ceph-apps rook-ceph kube-system --value storageValue.yaml $ system application-apply rook-ceph-apps This is values yaml file, by which rook will provision /dev/sdd. This is newly deploy case. cluster: storage: nodes: - devices: - config: journalSizeMB: 1024 storeType: bluestore name: sdd name: controller-0 This is my current implementation for rook. 2) We did not want to couple the rook/ceph implementation to sysinv. Therefore why would we have it manage the volume groups for rook ? 1, rook ceph will create a ceph name prefixed volume group "ceph-xxxxx" rook provision osd by ceph-volume, a new ceph provision tool to replace ceph-disk which is current starlingx deploy tool. Ceph-disk is depreciated, there is such log in /var/log/puppet, "This tool is now deprecated in favor of ceph-volume" For provision by ceph-volume, it will look up any volume-group, prefixed with "ceph-xxxxx", and pv to this volume group, and then create lv for ceph-osd This rook created volume group will be filtered by setting in /etc/lvm/lvm.conf, as it is not managed by sysinv. 2, Without considering rook, as ceph-disk is depreciated, if puppet-ceph upgrade, it will also turn to use ceph-volume for ceph provision. There is also such issue, a volume group name prefixed with ceph created by ceph-volume. BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Rowsell, Brent Sent: Monday, March 16, 2020 9:31 PM To: Chen, Haochuan Z ; Miller, Frank ; 'starlingx-discuss at lists.starlingx.io' ; Waines, Greg Cc: Chen, Tingjie ; Sun, Austin ; Qi, Mingyuan ; Church, Robert Subject: RE: ceph containerization patch review Martin, At the mid cycle meeting we established: 1. We have to keep the existing ceph implementation to allow existing users to transition post stx.4.0. The existing implementation would then be removed in stx.5.0. Therefore I do not understand what you are proposing in point 1 below. 2. We did not want to couple the rook/ceph implementation to sysinv. Therefore why would we have it manage the volume groups for rook ? Brent From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Thursday, March 12, 2020 8:06 PM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent >; Waines, Greg > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan >; Church, Robert > Subject: ceph containerization patch review Hi Brent & Frank I already finish my new application and helm plugin for rook-ceph. But still two concern to discuss. 1, decouple ceph backend with sysinv. Now ceph backend has been removed as default storage backend. And I plan to add rook-ceph as another storage backend which user could enable by his provision. So what about decouple ceph backend with sysinv-conductor, which is beneficial for more storage backend enabling. 2, change restriction for volume group creation in sysinv Currently sysinv has restriction for volume group creation, only permit create volume group with "nova-local", "cinder-volumes", "cgts-vg". What about remove this restriction? For containerized ceph cluster deployment, osd is provisioned by ceph-volume, which is based on logical volume. It will create a volume group, with "ceph" name prefixed. I prefer this newly created volume group could also be managed by sysinv. Currenlty ceph cluster is deployed by ceph-disk in puppet-ceph. This tool is depreciated. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Friday, February 21, 2020 11:14 PM To: 'Miller, Frank' >; 'starlingx-discuss at lists.starlingx.io' >; 'Rowsell, Brent' >; 'Greg.Waines at windriver.com' > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan >; 'Church, Robert' > Subject: RE: ceph containerization patch review Hi Frank & Bob & Greg & Brent To deploy, it is same as any other helm chart. Wait for you opinion for current solution. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Wednesday, February 19, 2020 12:53 PM To: 'Miller, Frank' >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent >; 'Greg.Waines at windriver.com' > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan >; Church, Robert > Subject: RE: ceph containerization patch review Hi folks Answer the question, with only k8s, how to deploy rook. $ helm-upload stx-platform rook-ceph-0.1.0.tga $ helm install stx-platform/rook-ceph -n rook-ceph-cluster -n kube-system -f value.yaml BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Tuesday, February 18, 2020 10:06 PM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan >; Church, Robert > Subject: RE: ceph containerization patch review +Bob who is the containers TL From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Monday, February 17, 2020 8:46 AM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan > Subject: RE: ceph containerization patch review Hi Frank & Brent For rook manage configuration, after introduce rook-ceph, current ceph cluster deployed by puppet will keep or be removed? If removed, containerized ceph cluster deployed by rook-ceph will take the role of provisioner for stx-openstack. If keeps, helm chart rbd-provisioner in platform-integ-app also keeps and takes the role of provisioner for stx-openstack. Containerized ceph cluster deployed by rook-ceph only serve as csi provider for k8s. BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, February 10, 2020 11:47 PM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan > Subject: RE: ceph containerization patch review Hi Frank: As synced with Tingjie, this is my understanding for Rook manage the configuration instead of sysinv. 1, Remove ceph config and status query from sysinv 2, create another tool, like rook-client to launch and provision ceph cluster 3, one helm plugin like rbd-provision, which depends on newly created tool BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Saturday, February 8, 2020 4:16 AM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: ceph containerization patch review Martin: Thanks for posting your reviews and the update on the current status for this feature. I was unable to attend the containerization meeting this week so wasn't able to have Tingjie or you give an update on the open actions for the feature. From the Jan 14 minutes [1] one of the actions is to determine "how can you have Rook do all the configuration and not have sysinv involved" For now I suggest you add an additional item to your Tasks to do list to identify a design that does not require sysinv for the configuration and instead has Rook manage the configuration. I would like to ask that we discuss further at the next containerization meeting and if possible review a proposal from yourself and Austin for this item. Frank [1] https://etherpad.openstack.org/p/stx-containerization From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Thursday, February 06, 2020 11:02 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] ceph containerization patch review Hi folks I enabled containerized ceph cluster with simplex. You can begin to review my patch. I propose to build an image and deploy a simplex system with these patch to check. https://review.opendev.org/#/c/681457/ https://review.opendev.org/#/c/687340/ https://review.opendev.org/#/c/706256/ https://review.opendev.org/#/c/699557/ https://review.opendev.org/#/c/699556/ And I know there is other story, like remove ceph as default backend storage, maybe some conflict, we can discuss together. Tash Done: 1, disable native ceph cluster in ceph.pp 2, disable ceph daemon monitoring in service manager 3, add rook-ceph helm chart to launch ceph cluster 4, add override in stx-config to generate override with starlingx system config 5, sysinv add label in provision stage, to make containerized ceph mon and ceph mgr on designed host 6, add rook-ceph-provisioner helm chart to generate storage class, secret, config and pool for stx-application 7, enabled stx-openstack with containerized ceph 8, update ceph wrapper in stx-config to set or get containerized ceph cluster All these tasks done is enabled with simplex only. Task to do: 1, enable add osd runtime, after system provisioned 2, fix know issue, if system reboot, ceph cluster launch fail 3, enable bluestore and filestore, currently there is only bluestore 4, enable multi-node and duplex 5, enable swift with containerized ceph 6, enable fm alarm for containerized ceph 7, check backup and restore for containerized ceph 8, check system upgrade or how to transit from native ceph cluster to containerized ceph cluster 9, code cleanup 10, update unit test in stx-config BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From 00100011f at gmail.com Tue Mar 17 06:38:04 2020 From: 00100011f at gmail.com (r b) Date: Tue, 17 Mar 2020 14:38:04 +0800 Subject: [Starlingx-discuss] Issue with registry.local when applying platform-integ-app Message-ID: Hi, I'm deploying platform-integ-app with command: ``` system application-apply platform-integ-app ``` but it fails with log `failed to download one or more image`. The environment is `All in One` deployment of StarlingX; there is only one node named `simplex-controller-0`. The registry.local is resolved to 192.168.204.2 and the lo:1 on controller-0 is 192.168.204.3. `system application-list` shows: [root at controller-0 ~(keystone_admin)]# system application-list +---------------------+---------+-------------------------------+-----------+--------------+--------------------------------+ | application | version | manifest name | manifest | status | progress | | | | | file | | | +---------------------+---------+-------------------------------+-----------+--------------+--------------------------------+ | platform-integ-apps | 1.0-7 | platform-integration-manifest | manifest. | apply-failed | Deployment of application | | | | | yaml | | platform-integ-apps (1.0-7) | | | | | | | failed: failed to download one | | | | | | | or more image(s). | | | | | | | | +---------------------+---------+-------------------------------+-----------+--------------+--------------------------------+ `/var/log/sysinv.log` shows: 2020-03-10 04:19:02.336 92570 ERROR sysinv.conductor.kube_app [-] Image registry.local:9001/docker.io/port/ceph-config-helper:v1.10.3 download failed from local registry: 500 Server Error: Internal Server Error ("Get https://registry.local:9001/v2/: Forbidden") And I can not use `docker pull registry.local:9001/docker.io/port/ceph-config-helper:v1.10.3 ` manually: Error response from daemon: Get https://registry.local:9001/v2/: Forbidden BTY, I found one similar issue here (https://bugs.launchpad.net/starlingx/+bug/1850592 ), which mainly is `"Get https://registry.local:9001/v2/ : dial tcp: lookup registry.local: no such host"`. So, is there any extra step should I do to configure the local registry? I have followed the official installation guide step by step. Or is it possible for me just to edit the configurations to remove the `registry.local:9001` prefix of images' address? I tried to modify the .yml files in /opt/platform/armada/19.08/platform-integ-apps/1.0-7/ but it makes no sense. (Firstly my goal is to deploy stx-openstack but it stucks with the state of `applying` for a few days and there is no error log in /var/log/, and I find that the platform-integ-apps failed, so maybe I should deploy the platform-integ-apps at first...) Thanks, Bonan -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Mar 17 08:37:15 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 17 Mar 2020 08:37:15 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 3/18/2020 Message-ID: Hi All: Agenda for 3/18 meeting: - Ceph containerization (martin) - Kata remaining work (shuicheng) a) upgrade new kata for IPV6 https://storyboard.openstack.org/#!/story/2006145 . Task 39077 b) switch armada to run with containerd - PBR: (JITStack Wesley) - centos8 upgrade (shuicheng/Austin ) ---- kernel on master patch list:https://review.opendev.org/#/q/status:open+project:starlingx/integ+branch:master+topic:4.18_kernel call for test: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008022.html ---- python3 upgrade: NFV analysis result http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/007991.html - open If have any other topic, feel free to add to https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. From dejan.muhamedagic at tttech-industrial.com Tue Mar 17 10:00:56 2020 From: dejan.muhamedagic at tttech-industrial.com (Dejan Muhamedagic) Date: Tue, 17 Mar 2020 10:00:56 +0000 Subject: [Starlingx-discuss] StarlingX and Openstack installation In-Reply-To: References: Message-ID: <05add645057a2463f0c4aa8c1531d6b00b8e70dc.camel@tttech-industrial.com> Hi, On Mon, 2020-03-16 at 17:51 +0530, Abhijit Deodhar wrote: > I am trying to install Openstack with StarlingX by following the > instructions mentioned here: > https://docs.starlingx.io/deploy_install_guides/r3_release/openstack/install.html > > I completed the above steps and then I tried to access the local CLI > using these steps: > https://docs.starlingx.io/deploy_install_guides/r3_release/openstack/access.html > > The document has this step: > Configure helm endpoint domain¶ > > For a lab setup where I dont expect any queries from outside the > localhost, Is this step required? > No. > I skipped the above step and configured the clouds.yaml. I hit few > issues: > > 1) I cannot access the GUI using the :31000 port > from the browser? > 2) The local CLI commands such as "openstack image list" keep failing > with > Make sure that stx-openstack application has been applied (system application-apply stx-openstack). > controller-0:~$ openstack image list > Failed to discover available identity versions when contacting > http://keystone.openstack.svc.cluster.local/v3. Attempting to parse > version from URL. > Service Unavailable (HTTP 503) > controller-0:~$ source /etc/platform/openrc > [sysadmin at controller-0 ~(keystone_admin)]$ export > OS_CLOUD=openstack_helm If you "source /etc/platform/openrc" then you cannot use the openstack command line tools. Admittedly a bit confusing. So, just do the "export OS_CLOUD=openstack_helm" in your terminal session and you should be OK (providing that you created /etc/openstack/cloud.yaml). Thanks, Dejan > [sysadmin at controller-0 ~(keystone_admin)]$ openstack image list > The request you have made requires authentication. (HTTP 401) > (Request-ID: req-ed0117db-5fc2-4d21-9175-d8fcd6434fb7) > > I am not sure what exactly I am missing wrt the configuration. > Can someone please help me by providing any pointers ? > > Thanks > Abhijit > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail at tttech.com immediately. From Teresa.Ho at windriver.com Tue Mar 17 12:43:07 2020 From: Teresa.Ho at windriver.com (Ho, Teresa) Date: Tue, 17 Mar 2020 12:43:07 +0000 Subject: [Starlingx-discuss] additional stx docs input:2006711 Message-ID: Hi, Additional doc info, regarding oidc-auth shell script, is provided in the attached file which was previously sent. Thanks, Teresa From: Sun, Yicheng (Jerry) [mailto:Jerry.Sun at windriver.com] Sent: Tuesday, March 10, 2020 4:11 PM To: starlingx-discuss at lists.starlingx.io; maryx.camp at intel.com Subject: [Starlingx-discuss] stx docs input:2006711 Hi All, We have just added the ability to configure oidc auth related parameters post-bootstrap: system service-parameter-add kubernetes kube_apiserver oidc_client_id=value system service-parameter-add kubernetes kube_apiserver oidc_groups_claim=value system service-parameter-add kubernetes kube_apiserver oidc_issuer_url=value system service-parameter-add kubernetes kube_apiserver oidc_username_claim=value they used to be configurable only at boostrap time in localhost.yml: apiserver_oidc: client_id: stx-oidc-client-app issuer_url: https://:30556/dex username_claim: email groups_claim: group Apply the service parameters with "system service-parameter-apply kubernetes", or no changes will take place. The valid configurations for the service parameters are the same as during bootstrap: none of the parameters or oidc_issuer_url, oidc_client_id, oidc_username_claim or the above 3 and oidc_groups_claim Thanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: StarlingX Windows Active Directory documentation.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 37767 bytes Desc: StarlingX Windows Active Directory documentation.docx URL: From Frank.Miller at windriver.com Tue Mar 17 12:56:17 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 17 Mar 2020 12:56:17 +0000 Subject: [Starlingx-discuss] about upgrading 3 OpenStack services on platform In-Reply-To: References: Message-ID: Yong: Going with option 1 (move keystone, barbican, horizon) to Train makes sense as Stein is no longer going to be maintained later this year. Then when the move to CentOS 8.x happens in a future release these 3 packages should be upversioned to align with the rest of the openstack services. Frank From: Hu, Yong Sent: Monday, March 16, 2020 4:10 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] about upgrading 3 OpenStack services on platform Hi community members, Here is a topic I like to get your feedback. Currently we are using 3 OpenStack services on StarlingX platform natively, besides those containerized OpenStack services. They are keystone, barbican and horizon for stx-gui, which are still with version “Stein” as of today. Previously when we were making plan for stx.4.0 release, we aimed at upgrading these 3 services from “Stein” to “U”, to align with containerized services (in progress of upgrading to “U”). However, now we have to give up this upgrade for stx.4.0, because: 1). CentOS 7.x doesn’t have plan to provide packages for OpenStack “U”, so we cannot make the upgrade based on CentOS 7.x. 2). CentOS 8.x has the plan to provide packages for OpenStack “U”, but we won’t go there for stx.4.0 accordingly the decision from the meet-up in AZ two weeks ago. Alternatively, we have some options: 1). For stx.4.0, we upgrade these 3 services from “Stein” to “Train”, which CentOS 7.x has already supported. It’s not perfect, but we are 1 step ahead. And then in stx.5.0, we move on from “Train” to “U”. Question: *Is this valuable??** 2). We simply defer this upgrade to stx.5.0, by when we expect we can get full support base packages on CentOS 8.x for OpenStack “U”. Please share your feedback if you care this matter. Regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Tue Mar 17 13:57:20 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 17 Mar 2020 13:57:20 +0000 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> Message-ID: Hi Scott What about create a new application project for rook-ceph? Thanks for you help! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, March 10, 2020 9:57 AM To: 'Scott Little' ; Rowsell, Brent Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: create a new project for ceph containerizaiton Hi Scott Check my answer and wait for your comment. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Scott Little > Sent: Monday, March 9, 2020 10:40 PM To: Chen, Haochuan Z >; Rowsell, Brent > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: Re: create a new project for ceph containerizaiton Yes, I can help with that. I can't create the new git myself, but can help with the process of submitting the request to the opendev admins First we'll need 1) unique and descriptive name for the new git. Rook storage application 2) A description of the project for the comment section. A sentence or two. This is starlingx application to deploy rook helm chart, which provide storage as starlingx storage backend 3) The url and branch of any upstream git used to seed the content for the new git. https://review.opendev.org/starlingx/rook-storage-app 4) is this a python project that needs to publish to PYPI ? No Scott PS: The process is described out here [1] [1] https://docs.openstack.org/infra/manual/creators.html On 2020-03-09 10:26 a.m., Chen, Haochuan Z wrote: Hi scott As last week sync with brent, we will create a new application for ceph containeration. Could you help to create this new git project for me? Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Tue Mar 17 14:22:30 2020 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 17 Mar 2020 14:22:30 +0000 Subject: [Starlingx-discuss] about upgrading 3 OpenStack services on platform In-Reply-To: References: Message-ID: <5DB547C1-878B-41AD-9424-5EA9703D8276@intel.com> Thanks Frank. If there is no objection from others, we can go with this option. From: "Miller, Frank" Date: Tuesday, March 17, 2020 at 8:56 PM To: "Hu, Yong" , "starlingx-discuss at lists.starlingx.io" Subject: RE: about upgrading 3 OpenStack services on platform Yong: Going with option 1 (move keystone, barbican, horizon) to Train makes sense as Stein is no longer going to be maintained later this year. Then when the move to CentOS 8.x happens in a future release these 3 packages should be upversioned to align with the rest of the openstack services. Frank From: Hu, Yong Sent: Monday, March 16, 2020 4:10 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] about upgrading 3 OpenStack services on platform Hi community members, Here is a topic I like to get your feedback. Currently we are using 3 OpenStack services on StarlingX platform natively, besides those containerized OpenStack services. They are keystone, barbican and horizon for stx-gui, which are still with version “Stein” as of today. Previously when we were making plan for stx.4.0 release, we aimed at upgrading these 3 services from “Stein” to “U”, to align with containerized services (in progress of upgrading to “U”). However, now we have to give up this upgrade for stx.4.0, because: 1). CentOS 7.x doesn’t have plan to provide packages for OpenStack “U”, so we cannot make the upgrade based on CentOS 7.x. 2). CentOS 8.x has the plan to provide packages for OpenStack “U”, but we won’t go there for stx.4.0 accordingly the decision from the meet-up in AZ two weeks ago. Alternatively, we have some options: 1). For stx.4.0, we upgrade these 3 services from “Stein” to “Train”, which CentOS 7.x has already supported. It’s not perfect, but we are 1 step ahead. And then in stx.5.0, we move on from “Train” to “U”. Question: *Is this valuable??** 2). We simply defer this upgrade to stx.5.0, by when we expect we can get full support base packages on CentOS 8.x for OpenStack “U”. Please share your feedback if you care this matter. Regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Tue Mar 17 15:24:19 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 17 Mar 2020 15:24:19 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Mar 18, 2020) Message-ID: Hi all, reminder of tomorrow's TSC/Community call. We'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200318T1400 From ruediger.stock at intel.com Tue Mar 17 16:30:32 2020 From: ruediger.stock at intel.com (Stock, Ruediger) Date: Tue, 17 Mar 2020 16:30:32 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build - ISO 20200316 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-15 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200316T230002Z/outputs/iso/) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard external setup in the virtual environment failed because of an automation issue (the corresponding job on bare metal was successful). Regards, STX Validation Team Rüdiger Stock Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ruediger.stock at intel.com Tue Mar 17 16:32:44 2020 From: ruediger.stock at intel.com (Stock, Ruediger) Date: Tue, 17 Mar 2020 16:32:44 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build - ISO 20200316 In-Reply-To: References: Message-ID: The prior mail has a typo in the date of the bootimage. The tests ran on the current one. Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-16 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200316T230002Z/outputs/iso/) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard external setup in the virtual environment failed because of an automation issue (the corresponding job on bare metal was successful). Regards, STX Validation Team Rüdiger Stock Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From yang.liu at windriver.com Tue Mar 17 16:50:00 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Tue, 17 Mar 2020 16:50:00 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 03/17/2020 In-Reply-To: References: Message-ID: Agenda/meeting notes are posted here: https://etherpad.openstack.org/p/stx-test Agenda for 03/17/2020 Attendees: Yang, George P, Mihail, Nicolae, Alex, Oliver, Ruediger, Cosmin, Sharath, 1. Sanity Status: * Sanity issues reported by WR: * 1858659 - VM live migration in error status * 1855474 - OpenStack pods were not recovered after force reboot active controller * 1859645 - platform-integ-apps fail to apply initially due to could not find the requested resource (get configmaps) * Nic's team are investigating sanity results, but both hardware and virtual sanity are still done on Ada's machines. 2. stx4.0 testing * Feature testing: * https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=0 * Nic's team started to understand the features from dev and make test plan * WR feature testing on track * Regression testing: * Spreadsheet created - test cases to be selected * https://docs.google.com/spreadsheets/d/1gA3bnLS7aY2y8dKxm4MuqpWyELq3PVJMYtiHn4IWiAk/edit#gid=1921715792 * Nic's team will run automated robot test to prepare for stx4.0 regression testing 3. Unified santiy * George is looking to upload change to pytest framework * He had issue with signing the agreement, but got help from Sharath. * He will send email to maling list for further questions if any. 4. Opens * Servers/test environment setup within Nic's team * Servers were shipped out on March 14th to Nic's team (not yet arrived) - some will be used for virtual setup. * Switch not yet shipped -------------- next part -------------- An HTML attachment was scrubbed... URL: From cboylan at sapwetik.org Tue Mar 17 20:30:14 2020 From: cboylan at sapwetik.org (Clark Boylan) Date: Tue, 17 Mar 2020 13:30:14 -0700 Subject: [Starlingx-discuss] OpenDev now using #opendev on Freenode for Discussions Message-ID: <7406ee4f-2e6f-40f1-b742-8052c54b8779@www.fastmail.com> Hello all, We are now using #opendev on Freenode to discuss the OpenDev Infrastructure. We hope this gives you all a more friendly neutral location to discuss the tools we use to develop our software. Feel free to join us and bring your ideas and questions. Hope to see you there, Clark From cboylan at sapwetik.org Tue Mar 17 21:09:20 2020 From: cboylan at sapwetik.org (Clark Boylan) Date: Tue, 17 Mar 2020 14:09:20 -0700 Subject: [Starlingx-discuss] review.opendev.org Downtime March 20, 2020 at 1400UTC Message-ID: <55a65607-5e2a-43fe-a5ba-aa06be11d22b@www.fastmail.com> The OpenDev team is planning to take a short downtime March 20, 2020 from 14:00UTC to 15:00UTC. This outage will enable us to rename a few projects and redeploy Gerrit using containers. The container based deployment is an important first step in our longer term plan for upgrading Gerrit to a modern version. We recognize that this will be a disruption during an already disrupted week for many. We feel this is worthwhile as it fits into project release schedules and sets us up well for the future. Thank you for your patience. Feel free to ask us any questions you may have on this thread or in #opendev on Freenode. Clark From dtroyer at gmail.com Tue Mar 17 21:19:41 2020 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 17 Mar 2020 16:19:41 -0500 Subject: [Starlingx-discuss] Stepping down from TSC Message-ID: Hi all, With the recent changes at Intel I find myself beginning the next phase of my career and for the first time in 10 years it unfortunately does not include OpenStack. I saw OpenStack grow from the marriage of early Swift and barely-old-enough-to-walk Nova to a very mature and successful platform. I met countless interesting and wonderful and talented people along the way and learned more than I ever imagined I would. It has also been a pleasure and an honor to be part of StarlingX from almost the beginning of Intel's involvement, including being part of forming the Technical Steering Committee. While the change of employer does not require me to do this I feel it is in the best interest of the StarlingX TSC and the community to step down effective immediately. I have already been noticeably absent for a while and there will not be time for me to contribute in my new role. I submitted the review to make this official a few minutes ago: https://review.opendev.org/713541. Just for completeness I have also stepped away from OpenStackClient as that project was folded into the OpenStack SDK led by Monty Taylor in the last week or so. Thank you all and may our paths cross again for all of the right reasons. dt -- Dean Troyer dtroyer at gmail.com From scott.little at windriver.com Tue Mar 17 23:40:53 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 17 Mar 2020 19:40:53 -0400 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> Message-ID: <0bbec920-0556-15ab-5d4e-635b36a8cc89@windriver.com> Sorry, I missed your answer I think.  Where/ when did you send it?  Or am I looking for a code review? Scott On 2020-03-09 9:57 p.m., Chen, Haochuan Z wrote: > > Hi Scott > > Check my answer and wait for your comment. > > Thanks! > > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > > *From:*Scott Little > *Sent:* Monday, March 9, 2020 10:40 PM > *To:* Chen, Haochuan Z ; Rowsell, Brent > > *Cc:* 'starlingx-discuss at lists.starlingx.io' > > *Subject:* Re: create a new project for ceph containerizaiton > > Yes, I can help with that.  I can't create the new git myself, but can > help with the process of submitting the request to the opendev admins > > First we'll need > > 1) unique and descriptive name for the new git. > >     Rook storage application > > 2) A description of the project for the comment section.  A sentence > or two. > >     This is starlingx application to deploy rook helm chart, which > provide storage as starlingx storage backend > > 3) The url and branch of any upstream git used to seed the content for > the new git. > > https://review.opendev.org/starlingx/rook-storage-app > > 4) is this a python project that needs to publish to PYPI ? > >     No > > Scott > > PS: The process is described out here [1] > > [1] https://docs.openstack.org/infra/manual/creators.html > > > On 2020-03-09 10:26 a.m., Chen, Haochuan Z wrote: > > Hi scott > > As last week sync with brent, we will create a new application for > ceph containeration. Could you help to create this new git project > for me? > > Thanks! > > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Tue Mar 17 23:54:07 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 17 Mar 2020 23:54:07 +0000 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: <0bbec920-0556-15ab-5d4e-635b36a8cc89@windriver.com> References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> <0bbec920-0556-15ab-5d4e-635b36a8cc89@windriver.com> Message-ID: ok, here is my answer. 1) unique and descriptive name for the new git. Rook storage application 2) A description of the project for the comment section. A sentence or two. This is starlingx application to deploy rook helm chart, which provide storage as starlingx storage backend 3) The url and branch of any upstream git used to seed the content for the new git. https://review.opendev.org/starlingx/rook-storage-app 4) is this a python project that needs to publish to PYPI ? No Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Scott Little Sent: Wednesday, March 18, 2020 7:41 AM To: Chen, Haochuan Z ; Rowsell, Brent Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: create a new project for ceph containerizaiton Sorry, I missed your answer I think. Where/ when did you send it? Or am I looking for a code review? Scott On 2020-03-09 9:57 p.m., Chen, Haochuan Z wrote: Hi Scott Check my answer and wait for your comment. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Scott Little Sent: Monday, March 9, 2020 10:40 PM To: Chen, Haochuan Z ; Rowsell, Brent Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: create a new project for ceph containerizaiton Yes, I can help with that. I can't create the new git myself, but can help with the process of submitting the request to the opendev admins First we'll need 1) unique and descriptive name for the new git. Rook storage application 2) A description of the project for the comment section. A sentence or two. This is starlingx application to deploy rook helm chart, which provide storage as starlingx storage backend 3) The url and branch of any upstream git used to seed the content for the new git. https://review.opendev.org/starlingx/rook-storage-app 4) is this a python project that needs to publish to PYPI ? No Scott PS: The process is described out here [1] [1] https://docs.openstack.org/infra/manual/creators.html On 2020-03-09 10:26 a.m., Chen, Haochuan Z wrote: Hi scott As last week sync with brent, we will create a new application for ceph containeration. Could you help to create this new git project for me? Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Wed Mar 18 01:11:10 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 18 Mar 2020 01:11:10 +0000 Subject: [Starlingx-discuss] additional stx docs input:2006711 In-Reply-To: References: Message-ID: Thanks Theresa for following up. I have created a review with your source file here: https://review.opendev.org/#/c/712111/ Apologies for not adding you as a reviewer till now. I am new to this role and I welcome feedback from you and Jerry about how to move forward with the review. thanks, Mary Camp PTIGlobal Technical Writer | maryx.camp at intel.com From: Ho, Teresa Sent: Tuesday, March 17, 2020 8:43 AM To: starlingx-discuss at lists.starlingx.io; Camp, MaryX Subject: RE: additional stx docs input:2006711 Hi, Additional doc info, regarding oidc-auth shell script, is provided in the attached file which was previously sent. Thanks, Teresa From: Sun, Yicheng (Jerry) [mailto:Jerry.Sun at windriver.com] Sent: Tuesday, March 10, 2020 4:11 PM To: starlingx-discuss at lists.starlingx.io; maryx.camp at intel.com Subject: [Starlingx-discuss] stx docs input:2006711 Hi All, We have just added the ability to configure oidc auth related parameters post-bootstrap: system service-parameter-add kubernetes kube_apiserver oidc_client_id=value system service-parameter-add kubernetes kube_apiserver oidc_groups_claim=value system service-parameter-add kubernetes kube_apiserver oidc_issuer_url=value system service-parameter-add kubernetes kube_apiserver oidc_username_claim=value they used to be configurable only at boostrap time in localhost.yml: apiserver_oidc: client_id: stx-oidc-client-app issuer_url: https://:30556/dex username_claim: email groups_claim: group Apply the service parameters with "system service-parameter-apply kubernetes", or no changes will take place. The valid configurations for the service parameters are the same as during bootstrap: none of the parameters or oidc_issuer_url, oidc_client_id, oidc_username_claim or the above 3 and oidc_groups_claim Thanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Wed Mar 18 01:46:01 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 18 Mar 2020 01:46:01 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. In-Reply-To: References: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314F6B2@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Joseph, After did some changes in rabbitmq helm chart, I have fixed nxdomain issue in my ipv6 simplex setup. Below two pods can run up. osh-openstack-rabbitmq-cluster-wait-9rw6p 1/1 Running 0 17m osh-openstack-rabbitmq-rabbitmq-0 1/1 Running 0 17m However, still have another issue. In pod osh-openstack-rabbitmq-cluster-wait, it will use rabbitmqadmin to connect rabbitmq, but always get error. ++ active_rabbit_nodes 2020-03-17T10:31:12.124589385Z stderr F ++ wc -w 2020-03-17T10:31:12.134367271Z stderr F ++ rabbitmqadmin_authed list nodes -f bash 2020-03-17T10:31:12.134427089Z stderr F ++ set +x 2020-03-17T10:31:12.179073378Z stderr F Traceback (most recent call last): 2020-03-17T10:31:12.179644557Z stderr F error: [Errno 111] Connection refused 2020-03-17T10:31:12.17964969Z stderr F *** Could not connect: [Errno 111] Connection refused In the log of rabbitmq node, I can see below. 2020-03-17T15:40:27.762196613Z stdout F 2020-03-17 15:40:27.761 [info] <0.495.0> started TCP listener on [::]:5672 2020-03-17T15:40:27.807886117Z stdout F 2020-03-17 15:40:27.807 [info] <0.552.0> Management plugin: HTTP (non-TLS) listener started on port 15672 2020-03-17T15:40:27.895551288Z stdout F 2020-03-17 15:40:27.895 [info] <0.8.0> Server startup complete; 5 plugins started. 2020-03-17T15:40:27.895555144Z stdout F * rabbitmq_peer_discovery_k8s 2020-03-17T15:40:27.895557288Z stdout F * rabbitmq_management 2020-03-17T15:40:27.895559593Z stdout F * rabbitmq_management_agent 2020-03-17T15:40:27.895561807Z stdout F * rabbitmq_web_dispatch 2020-03-17T15:40:27.895564619Z stdout F * rabbitmq_peer_discovery_common I’m still working on this issue. Any comment or proposal, thanks! Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月16日 16:57 To: 'Richard, Joseph' ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, I tried many methods, but still not fixed the issue. I found there are some related issued fixed in upstream, but not yet merged to formal release. I’m discussing with them. Do you have any comment? https://github.com/rabbitmq/rabbitmq-peer-discovery-k8s/issues/55 Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月12日 9:53 To: 'Richard, Joseph' >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, Thank you so much! 😊 I will work further based on your provided clue. Best Regards, Zhipeng From: Richard, Joseph > Sent: 2020年3月12日 5:06 To: Liu, ZhipengS >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. I see a similar issue online here: https://groups.google.com/forum/#!topic/rabbitmq-users/9ir1WK-nYBA [http://www.google.com/images/icons/product/groups-128.png] epmd fails to start in IPv6 environment Posted 7/15/19 9:43 PM, 12 messages groups.google.com I expect that you are going to have to update rabbmitmq docker images to 3.7.16(currently 3.7.13), and then modify the helm plugin to pass in these values when using ipv6: SERVER_ADDITIONAL_ERL_ARGS='-proto_dist inet6_tcp' CTL_ERL_ARGS='-proto_dist inet6_tcp' Not sure if this is possible right now, or if you will need to modify openstack-helm-infra/rabbitmq in order to be able to pass these environment variables in. ________________________________ From: Liu, ZhipengS > Sent: Thursday, February 27, 2020 8:00 AM To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi all, For below LP IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status" https://bugs.launchpad.net/starlingx/+bug/1859641 I provided a patch which can fix the known issue in LP. However, it still failed later when starting rabbitmq pod. controller-0:~$ kubectl -n openstack get po NAME READY STATUS RESTARTS AGE ingress-c74489c96-jsb7n 1/1 Running 0 17h ingress-error-pages-5889bfcf6c-h8kl6 1/1 Running 0 17h mariadb-ingress-b5cd65f4b-sq46c 1/1 Running 0 17h mariadb-ingress-error-pages-6d8b79b74f-9zmpc 1/1 Running 0 17h mariadb-server-0 1/1 Running 0 17h osh-openstack-memcached-memcached-545668bdbd-9jkv2 1/1 Running 0 17h osh-openstack-rabbitmq-cluster-wait-wbnwp 0/1 Init:0/2 0 17h osh-openstack-rabbitmq-rabbitmq-0 0/1 CrashLoopBackOff 207 17h There are below error logs 2020-02-26T07:43:36.451103975Z stderr F ++ echo osh-openstack-rabbitmq-rabbitmq-0 2020-02-26T07:43:36.45142814Z stderr F ++ awk -F - '{print $NF}' 2020-02-26T07:43:36.454160452Z stderr F + POD_INCREMENT=0 2020-02-26T07:43:36.454757022Z stderr F + '[' 0 -eq 0 ']' 2020-02-26T07:43:36.454795721Z stderr F + exec rabbitmq-server 2020-02-26T07:43:36.849021551Z stdout F ERROR: epmd error for host osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local: nxdomain (non-existing domain) In /etc/hosts file below, I just found localhost4, no localhost6. Is it expected? I added below line manually after the line of 127.0.0.1. However, it didn’t work☹ ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 # HEADER: This file was autogenerated at 2020-02-26 09:00:35 +0000 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 fd01::1 controller 169.254.202.1 pxecontroller fd00::3 oamcontroller fd01::4 controller-platform-nfs fd01::3 controller-1 fd01::2 controller-0 fd02::3 controller-1-cluster-host fd02::2 controller-0-cluster-host fd01::e8b6:66fe storage-0 I saw that in ./stx-puppet/puppet-manifests/src/modules/platform/manifests/config.pp:215 class platform::config::hosts inherits ::platform::config::params { # The localhost should resolve to the IPv4 loopback address only, therefore # ensure the IPv6 address is removed from configured hosts resources { 'host': purge => true } $localhost = { 'localhost' => { ip => '127.0.0.1', host_aliases => ['localhost.localdomain', 'localhost4', 'localhost4.localdomain4'] }, } $merged_hosts = merge($localhost, $hosts) create_resources('host', $merged_hosts, {}) } Any one can give some help? Thanks! Zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jolliffe at windriver.com Wed Mar 18 13:18:15 2020 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Wed, 18 Mar 2020 13:18:15 +0000 Subject: [Starlingx-discuss] [TSC] Minutes 3/18/2020 Message-ID: Hi all; Elections (ildikov, Bruce, Bill) - Open PL spots - Networking - Ian will reach out to a few people to see who could fill this post - Docs - Bruce has a candidate Upcoming TSC elections Reducing the number of TSC seats? - Plan to reduce the size of the TSC - 6 or 7 - Ildiko will post a review - done Timeframe of the next elections? - 3rd week of May Project confirmation review timing (ildikov) Is the project comfortable with the Vancouver timeframe? - this is the proposal, Ildiko sent out a note to the mailing list to get additional input from the community FYI - One of the discussions from the meet up was the need for an upgrades spec. We agreed that there will be a spec posted for Upgrades. Regards; Ian From austin.sun at intel.com Wed Mar 18 13:28:20 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 18 Mar 2020 13:28:20 +0000 Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 3/18/2020 Message-ID: MoM for 3/18 meeting: - Ceph containerization (martin) waiting new repo to create and upload application change. is working on diagram to describe how to decouple w/ sysinv - Kata remaining work (shuicheng) a) upgrade new kata for IPV6 https://storyboard.openstack.org/#!/story/2006145 . Task 39077 b) switch armada to run with containerd armada is running docker currently , but crictl will run container in pod, it means running container in k8s. c) document for the kata. - PBR: (JITStack Wesley) building iso. Yipeng sent email to community. - centos8 upgrade (shuicheng ) ---- kernel on master patch list:https://review.opendev.org/#/q/status:open+project:starlingx/integ+branch:master+topic:4.18_kernel call for test: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008022.html waitting HW and test from Nicolae's team. ---- python3 upgrade: NFV analysis result http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/007991.html after anlysis these services are doable for python3 engtools ----> require python3 model psutil, six logmgmt ------> require python3 model daemon platform-util ------> require python3 model oslo_i18n nfv-client sm-tools - open Thanks. BR Austin Sun. From ruediger.stock at intel.com Wed Mar 18 13:28:58 2020 From: ruediger.stock at intel.com (Stock, Ruediger) Date: Wed, 18 Mar 2020 13:28:58 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build - ISO 20200318 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-18 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200318T013004Z/outputs/iso/) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard external setup in the virtual environment failed because of an automation issue (the corresponding job on bare metal was successful). Regards, STX Validation Team Rüdiger Stock Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joseph.Richard at windriver.com Wed Mar 18 13:48:16 2020 From: Joseph.Richard at windriver.com (Richard, Joseph) Date: Wed, 18 Mar 2020 13:48:16 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. In-Reply-To: References: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314F6B2@SHSMSX104.ccr.corp.intel.com> , Message-ID: Can you open a review with the change you made to fix the nxdomain issue? Is rabbitmqadmin able to connect if you run it from within osh-openstack-rabbitmq-rabbitmq-0? I see from your logs that the osh-openstack-rabbitmq-cluster-wait is from before rabbitmq was running. Can you see anything in the rabbitmq when the cluster-wait pod fails? ________________________________ From: Liu, ZhipengS Sent: Tuesday, March 17, 2020 9:46 PM To: Richard, Joseph ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, After did some changes in rabbitmq helm chart, I have fixed nxdomain issue in my ipv6 simplex setup. Below two pods can run up. osh-openstack-rabbitmq-cluster-wait-9rw6p 1/1 Running 0 17m osh-openstack-rabbitmq-rabbitmq-0 1/1 Running 0 17m However, still have another issue. In pod osh-openstack-rabbitmq-cluster-wait, it will use rabbitmqadmin to connect rabbitmq, but always get error. ++ active_rabbit_nodes 2020-03-17T10:31:12.124589385Z stderr F ++ wc -w 2020-03-17T10:31:12.134367271Z stderr F ++ rabbitmqadmin_authed list nodes -f bash 2020-03-17T10:31:12.134427089Z stderr F ++ set +x 2020-03-17T10:31:12.179073378Z stderr F Traceback (most recent call last): 2020-03-17T10:31:12.179644557Z stderr F error: [Errno 111] Connection refused 2020-03-17T10:31:12.17964969Z stderr F *** Could not connect: [Errno 111] Connection refused In the log of rabbitmq node, I can see below. 2020-03-17T15:40:27.762196613Z stdout F 2020-03-17 15:40:27.761 [info] <0.495.0> started TCP listener on [::]:5672 2020-03-17T15:40:27.807886117Z stdout F 2020-03-17 15:40:27.807 [info] <0.552.0> Management plugin: HTTP (non-TLS) listener started on port 15672 2020-03-17T15:40:27.895551288Z stdout F 2020-03-17 15:40:27.895 [info] <0.8.0> Server startup complete; 5 plugins started. 2020-03-17T15:40:27.895555144Z stdout F * rabbitmq_peer_discovery_k8s 2020-03-17T15:40:27.895557288Z stdout F * rabbitmq_management 2020-03-17T15:40:27.895559593Z stdout F * rabbitmq_management_agent 2020-03-17T15:40:27.895561807Z stdout F * rabbitmq_web_dispatch 2020-03-17T15:40:27.895564619Z stdout F * rabbitmq_peer_discovery_common I’m still working on this issue. Any comment or proposal, thanks! Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月16日 16:57 To: 'Richard, Joseph' ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, I tried many methods, but still not fixed the issue. I found there are some related issued fixed in upstream, but not yet merged to formal release. I’m discussing with them. Do you have any comment? https://github.com/rabbitmq/rabbitmq-peer-discovery-k8s/issues/55 Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月12日 9:53 To: 'Richard, Joseph' >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, Thank you so much! 😊 I will work further based on your provided clue. Best Regards, Zhipeng From: Richard, Joseph > Sent: 2020年3月12日 5:06 To: Liu, ZhipengS >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. I see a similar issue online here: https://groups.google.com/forum/#!topic/rabbitmq-users/9ir1WK-nYBA [http://www.google.com/images/icons/product/groups-128.png] epmd fails to start in IPv6 environment Posted 7/15/19 9:43 PM, 12 messages groups.google.com I expect that you are going to have to update rabbmitmq docker images to 3.7.16(currently 3.7.13), and then modify the helm plugin to pass in these values when using ipv6: SERVER_ADDITIONAL_ERL_ARGS='-proto_dist inet6_tcp' CTL_ERL_ARGS='-proto_dist inet6_tcp' Not sure if this is possible right now, or if you will need to modify openstack-helm-infra/rabbitmq in order to be able to pass these environment variables in. ________________________________ From: Liu, ZhipengS > Sent: Thursday, February 27, 2020 8:00 AM To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi all, For below LP IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status" https://bugs.launchpad.net/starlingx/+bug/1859641 I provided a patch which can fix the known issue in LP. However, it still failed later when starting rabbitmq pod. controller-0:~$ kubectl -n openstack get po NAME READY STATUS RESTARTS AGE ingress-c74489c96-jsb7n 1/1 Running 0 17h ingress-error-pages-5889bfcf6c-h8kl6 1/1 Running 0 17h mariadb-ingress-b5cd65f4b-sq46c 1/1 Running 0 17h mariadb-ingress-error-pages-6d8b79b74f-9zmpc 1/1 Running 0 17h mariadb-server-0 1/1 Running 0 17h osh-openstack-memcached-memcached-545668bdbd-9jkv2 1/1 Running 0 17h osh-openstack-rabbitmq-cluster-wait-wbnwp 0/1 Init:0/2 0 17h osh-openstack-rabbitmq-rabbitmq-0 0/1 CrashLoopBackOff 207 17h There are below error logs 2020-02-26T07:43:36.451103975Z stderr F ++ echo osh-openstack-rabbitmq-rabbitmq-0 2020-02-26T07:43:36.45142814Z stderr F ++ awk -F - '{print $NF}' 2020-02-26T07:43:36.454160452Z stderr F + POD_INCREMENT=0 2020-02-26T07:43:36.454757022Z stderr F + '[' 0 -eq 0 ']' 2020-02-26T07:43:36.454795721Z stderr F + exec rabbitmq-server 2020-02-26T07:43:36.849021551Z stdout F ERROR: epmd error for host osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local: nxdomain (non-existing domain) In /etc/hosts file below, I just found localhost4, no localhost6. Is it expected? I added below line manually after the line of 127.0.0.1. However, it didn’t work☹ ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 # HEADER: This file was autogenerated at 2020-02-26 09:00:35 +0000 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 fd01::1 controller 169.254.202.1 pxecontroller fd00::3 oamcontroller fd01::4 controller-platform-nfs fd01::3 controller-1 fd01::2 controller-0 fd02::3 controller-1-cluster-host fd02::2 controller-0-cluster-host fd01::e8b6:66fe storage-0 I saw that in ./stx-puppet/puppet-manifests/src/modules/platform/manifests/config.pp:215 class platform::config::hosts inherits ::platform::config::params { # The localhost should resolve to the IPv4 loopback address only, therefore # ensure the IPv6 address is removed from configured hosts resources { 'host': purge => true } $localhost = { 'localhost' => { ip => '127.0.0.1', host_aliases => ['localhost.localdomain', 'localhost4', 'localhost4.localdomain4'] }, } $merged_hosts = merge($localhost, $hosts) create_resources('host', $merged_hosts, {}) } Any one can give some help? Thanks! Zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Mar 18 13:52:00 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 18 Mar 2020 09:52:00 -0400 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> <0bbec920-0556-15ab-5d4e-635b36a8cc89@windriver.com> Message-ID: I submitted https://review.opendev.org/#/c/713650/ on your behalf. Who will be the cores? What compile layer does it belong in?   Probably 'distro' Whet governance group? On 2020-03-17 7:54 p.m., Chen, Haochuan Z wrote: > > ok, here is my answer. > > 1) unique and descriptive name for the new git. > >     Rook storage application > > 2) A description of the project for the comment section.  A sentence > or two. > >     This is starlingx application to deploy rook helm chart, which > provide storage as starlingx storage backend > > 3) The url and branch of any upstream git used to seed the content for > the new git. > > https://review.opendev.org/starlingx/rook-storage-app > > > 4) is this a python project that needs to publish to PYPI ? > >     No > > Thanks! > > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > > *From:*Scott Little > *Sent:* Wednesday, March 18, 2020 7:41 AM > *To:* Chen, Haochuan Z ; Rowsell, Brent > > *Cc:* 'starlingx-discuss at lists.starlingx.io' > > *Subject:* Re: create a new project for ceph containerizaiton > > Sorry, I missed your answer I think.  Where/ when did you send it?  Or > am I looking for a code review? > > Scott > > On 2020-03-09 9:57 p.m., Chen, Haochuan Z wrote: > > Hi Scott > > Check my answer and wait for your comment. > > Thanks! > > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > > *From:*Scott Little > > *Sent:* Monday, March 9, 2020 10:40 PM > *To:* Chen, Haochuan Z > ; Rowsell, Brent > > *Cc:* 'starlingx-discuss at lists.starlingx.io > ' > > > *Subject:* Re: create a new project for ceph containerizaiton > > Yes, I can help with that.  I can't create the new git myself, but > can help with the process of submitting the request to the opendev > admins > > First we'll need > > 1) unique and descriptive name for the new git. > >     Rook storage application > > 2) A description of the project for the comment section.  A > sentence or two. > >     This is starlingx application to deploy rook helm chart, which > provide storage as starlingx storage backend > > 3) The url and branch of any upstream git used to seed the content > for the new git. > > https://review.opendev.org/starlingx/rook-storage-app > > > 4) is this a python project that needs to publish to PYPI ? > >     No > > Scott > > PS: The process is described out here [1] > > [1] https://docs.openstack.org/infra/manual/creators.html > > > On 2020-03-09 10:26 a.m., Chen, Haochuan Z wrote: > > Hi scott > > As last week sync with brent, we will create a new application > for ceph containeration. Could you help to create this new git > project for me? > > Thanks! > > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Wed Mar 18 13:57:46 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Wed, 18 Mar 2020 13:57:46 +0000 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> <0bbec920-0556-15ab-5d4e-635b36a8cc89@windriver.com> Message-ID: Thanks Scott. Core: mingyuan.qi at intel.com austin.sun at intel.com haochuan.z.chen at intel.com This project belongs to flock layer What's the meaning of group? Thanks Martin, Chen IOTG, Software Engineer 021-61164330 From: Scott Little Sent: Wednesday, March 18, 2020 9:52 PM To: Chen, Haochuan Z ; Rowsell, Brent Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: create a new project for ceph containerizaiton I submitted https://review.opendev.org/#/c/713650/ on your behalf. Who will be the cores? What compile layer does it belong in? Probably 'distro' Whet governance group? On 2020-03-17 7:54 p.m., Chen, Haochuan Z wrote: ok, here is my answer. 1) unique and descriptive name for the new git. Rook storage application 2) A description of the project for the comment section. A sentence or two. This is starlingx application to deploy rook helm chart, which provide storage as starlingx storage backend 3) The url and branch of any upstream git used to seed the content for the new git. https://review.opendev.org/starlingx/rook-storage-app 4) is this a python project that needs to publish to PYPI ? No Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Scott Little Sent: Wednesday, March 18, 2020 7:41 AM To: Chen, Haochuan Z ; Rowsell, Brent Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: create a new project for ceph containerizaiton Sorry, I missed your answer I think. Where/ when did you send it? Or am I looking for a code review? Scott On 2020-03-09 9:57 p.m., Chen, Haochuan Z wrote: Hi Scott Check my answer and wait for your comment. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Scott Little Sent: Monday, March 9, 2020 10:40 PM To: Chen, Haochuan Z ; Rowsell, Brent Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: create a new project for ceph containerizaiton Yes, I can help with that. I can't create the new git myself, but can help with the process of submitting the request to the opendev admins First we'll need 1) unique and descriptive name for the new git. Rook storage application 2) A description of the project for the comment section. A sentence or two. This is starlingx application to deploy rook helm chart, which provide storage as starlingx storage backend 3) The url and branch of any upstream git used to seed the content for the new git. https://review.opendev.org/starlingx/rook-storage-app 4) is this a python project that needs to publish to PYPI ? No Scott PS: The process is described out here [1] [1] https://docs.openstack.org/infra/manual/creators.html On 2020-03-09 10:26 a.m., Chen, Haochuan Z wrote: Hi scott As last week sync with brent, we will create a new application for ceph containeration. Could you help to create this new git project for me? Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jolliffe at windriver.com Wed Mar 18 14:39:45 2020 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Wed, 18 Mar 2020 14:39:45 +0000 Subject: [Starlingx-discuss] Stepping down from TSC In-Reply-To: References: Message-ID: Hi Dean; It has truly been a pleasure working with you over the past two years. Your guidance and leadership in the launch of StarlingX was instrumental. When I started working on OpenStack I saw this Dean guy who was widely respected, involved from day 1 and knew everyone in the community. It has been great to have an opportunity to work with you. The community will miss your contributions to OpenStack Client and all the other areas you have played a role. I look forward to working with you again in the future. Wishing you all the best in your new adventure. Best Regards; Ian On 2020-03-17, 5:21 PM, "Dean Troyer" wrote: Hi all, With the recent changes at Intel I find myself beginning the next phase of my career and for the first time in 10 years it unfortunately does not include OpenStack. I saw OpenStack grow from the marriage of early Swift and barely-old-enough-to-walk Nova to a very mature and successful platform. I met countless interesting and wonderful and talented people along the way and learned more than I ever imagined I would. It has also been a pleasure and an honor to be part of StarlingX from almost the beginning of Intel's involvement, including being part of forming the Technical Steering Committee. While the change of employer does not require me to do this I feel it is in the best interest of the StarlingX TSC and the community to step down effective immediately. I have already been noticeably absent for a while and there will not be time for me to contribute in my new role. I submitted the review to make this official a few minutes ago: https://review.opendev.org/713541. Just for completeness I have also stepped away from OpenStackClient as that project was folded into the OpenStack SDK led by Monty Taylor in the last week or so. Thank you all and may our paths cross again for all of the right reasons. dt -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From zhipengs.liu at intel.com Wed Mar 18 14:53:21 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 18 Mar 2020 14:53:21 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. In-Reply-To: References: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314F6B2@SHSMSX104.ccr.corp.intel.com> , Message-ID: Hi Joseph, I will submit one patch for helm chart change later after fixing current issue. BTW, Seems we have no rabbitmqadmin in rabbitmq pod but rabbitmq-cluster-wait job. I have done below test and have some conclusion now. 1) Rabbtimq already started normally, and start listen on [::]:5672/15672/25672 port 2) It seems 15672 port access blocked for ipv6 (5672 is OK). In ipv4 simplex setup, same test below are all OK. Any idea? rabbitmq at osh-openstack-rabbitmq-rabbitmq-0:/usr/local$ rabbitmqctl status Status of node rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local ... Runtime OS PID: 303 OS: Linux Uptime (seconds): 6752 RabbitMQ version: 3.8.3 Node name: rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local Erlang configuration: Erlang/OTP 22 [erts-10.7] [source] [64-bit] [smp:6:6] [ds:6:6:10] [async-threads:128] Erlang processes: 426 used, 1048576 limit Scheduler run queue: 1 Cluster heartbeat timeout (net_ticktime): 60 Plugins Enabled plugin file: /etc/rabbitmq/enabled_plugins Enabled plugins: * rabbitmq_management * rabbitmq_web_dispatch * rabbitmq_peer_discovery_k8s * rabbitmq_peer_discovery_common * rabbitmq_management_agent * amqp_client * cowboy * cowlib Totals Connection count: 0 Queue count: 0 Virtual host count: 0 Listeners Interface: [::], port: 25672, protocol: clustering, purpose: inter-node and CLI tool communication Interface: [::], port: 5672, protocol: amqp, purpose: AMQP 0-9-1 and AMQP 1.0 Interface: [::], port: 15672, protocol: http, purpose: HTTP API controller-0:~$ wget http://rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local:15672/ --2020-03-18 14:37:45-- http://rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local:15672/ Resolving osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local (osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local)... fd03::1e6d:6abf Connecting to osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local (osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local)|fd03::1e6d:6abf|:15672... failed: Connection refused. //same as we see in the log of Rabbitmq-cluster-wait pod. controller-0:~$ wget http://rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local:5672/ --2020-03-18 14:37:53-- http://rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local:5672/ Resolving osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local (osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local)... fd03::1e6d:6abf Connecting to osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local (osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local)|fd03::1e6d:6abf|:5672... connected. controller-0:~$ wget http://[fd03::1e6d:6abf]:15672/ --2020-03-18 14:38:56-- http://[fd03::1e6d:6abf]:15672/ Connecting to [fd03::1e6d:6abf]:15672... failed: Connection refused. controller-0:~$ wget http://[fd03::1e6d:6abf]:5672/ --2020-03-18 14:39:00-- http://[fd03::1e6d:6abf]:5672/ Connecting to [fd03::1e6d:6abf]:5672... connected. Thanks! Zhipeng From: Richard, Joseph Sent: 2020年3月18日 21:48 To: Liu, ZhipengS ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Can you open a review with the change you made to fix the nxdomain issue? Is rabbitmqadmin able to connect if you run it from within osh-openstack-rabbitmq-rabbitmq-0? I see from your logs that the osh-openstack-rabbitmq-cluster-wait is from before rabbitmq was running. Can you see anything in the rabbitmq when the cluster-wait pod fails? ________________________________ From: Liu, ZhipengS > Sent: Tuesday, March 17, 2020 9:46 PM To: Richard, Joseph >; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, After did some changes in rabbitmq helm chart, I have fixed nxdomain issue in my ipv6 simplex setup. Below two pods can run up. osh-openstack-rabbitmq-cluster-wait-9rw6p 1/1 Running 0 17m osh-openstack-rabbitmq-rabbitmq-0 1/1 Running 0 17m However, still have another issue. In pod osh-openstack-rabbitmq-cluster-wait, it will use rabbitmqadmin to connect rabbitmq, but always get error. ++ active_rabbit_nodes 2020-03-17T10:31:12.124589385Z stderr F ++ wc -w 2020-03-17T10:31:12.134367271Z stderr F ++ rabbitmqadmin_authed list nodes -f bash 2020-03-17T10:31:12.134427089Z stderr F ++ set +x 2020-03-17T10:31:12.179073378Z stderr F Traceback (most recent call last): 2020-03-17T10:31:12.179644557Z stderr F error: [Errno 111] Connection refused 2020-03-17T10:31:12.17964969Z stderr F *** Could not connect: [Errno 111] Connection refused In the log of rabbitmq node, I can see below. 2020-03-17T15:40:27.762196613Z stdout F 2020-03-17 15:40:27.761 [info] <0.495.0> started TCP listener on [::]:5672 2020-03-17T15:40:27.807886117Z stdout F 2020-03-17 15:40:27.807 [info] <0.552.0> Management plugin: HTTP (non-TLS) listener started on port 15672 2020-03-17T15:40:27.895551288Z stdout F 2020-03-17 15:40:27.895 [info] <0.8.0> Server startup complete; 5 plugins started. 2020-03-17T15:40:27.895555144Z stdout F * rabbitmq_peer_discovery_k8s 2020-03-17T15:40:27.895557288Z stdout F * rabbitmq_management 2020-03-17T15:40:27.895559593Z stdout F * rabbitmq_management_agent 2020-03-17T15:40:27.895561807Z stdout F * rabbitmq_web_dispatch 2020-03-17T15:40:27.895564619Z stdout F * rabbitmq_peer_discovery_common I’m still working on this issue. Any comment or proposal, thanks! Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月16日 16:57 To: 'Richard, Joseph' >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, I tried many methods, but still not fixed the issue. I found there are some related issued fixed in upstream, but not yet merged to formal release. I’m discussing with them. Do you have any comment? https://github.com/rabbitmq/rabbitmq-peer-discovery-k8s/issues/55 Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月12日 9:53 To: 'Richard, Joseph' >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, Thank you so much! 😊 I will work further based on your provided clue. Best Regards, Zhipeng From: Richard, Joseph > Sent: 2020年3月12日 5:06 To: Liu, ZhipengS >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. I see a similar issue online here: https://groups.google.com/forum/#!topic/rabbitmq-users/9ir1WK-nYBA [http://www.google.com/images/icons/product/groups-128.png] epmd fails to start in IPv6 environment Posted 7/15/19 9:43 PM, 12 messages groups.google.com I expect that you are going to have to update rabbmitmq docker images to 3.7.16(currently 3.7.13), and then modify the helm plugin to pass in these values when using ipv6: SERVER_ADDITIONAL_ERL_ARGS='-proto_dist inet6_tcp' CTL_ERL_ARGS='-proto_dist inet6_tcp' Not sure if this is possible right now, or if you will need to modify openstack-helm-infra/rabbitmq in order to be able to pass these environment variables in. ________________________________ From: Liu, ZhipengS > Sent: Thursday, February 27, 2020 8:00 AM To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi all, For below LP IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status" https://bugs.launchpad.net/starlingx/+bug/1859641 I provided a patch which can fix the known issue in LP. However, it still failed later when starting rabbitmq pod. controller-0:~$ kubectl -n openstack get po NAME READY STATUS RESTARTS AGE ingress-c74489c96-jsb7n 1/1 Running 0 17h ingress-error-pages-5889bfcf6c-h8kl6 1/1 Running 0 17h mariadb-ingress-b5cd65f4b-sq46c 1/1 Running 0 17h mariadb-ingress-error-pages-6d8b79b74f-9zmpc 1/1 Running 0 17h mariadb-server-0 1/1 Running 0 17h osh-openstack-memcached-memcached-545668bdbd-9jkv2 1/1 Running 0 17h osh-openstack-rabbitmq-cluster-wait-wbnwp 0/1 Init:0/2 0 17h osh-openstack-rabbitmq-rabbitmq-0 0/1 CrashLoopBackOff 207 17h There are below error logs 2020-02-26T07:43:36.451103975Z stderr F ++ echo osh-openstack-rabbitmq-rabbitmq-0 2020-02-26T07:43:36.45142814Z stderr F ++ awk -F - '{print $NF}' 2020-02-26T07:43:36.454160452Z stderr F + POD_INCREMENT=0 2020-02-26T07:43:36.454757022Z stderr F + '[' 0 -eq 0 ']' 2020-02-26T07:43:36.454795721Z stderr F + exec rabbitmq-server 2020-02-26T07:43:36.849021551Z stdout F ERROR: epmd error for host osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local: nxdomain (non-existing domain) In /etc/hosts file below, I just found localhost4, no localhost6. Is it expected? I added below line manually after the line of 127.0.0.1. However, it didn’t work☹ ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 # HEADER: This file was autogenerated at 2020-02-26 09:00:35 +0000 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 fd01::1 controller 169.254.202.1 pxecontroller fd00::3 oamcontroller fd01::4 controller-platform-nfs fd01::3 controller-1 fd01::2 controller-0 fd02::3 controller-1-cluster-host fd02::2 controller-0-cluster-host fd01::e8b6:66fe storage-0 I saw that in ./stx-puppet/puppet-manifests/src/modules/platform/manifests/config.pp:215 class platform::config::hosts inherits ::platform::config::params { # The localhost should resolve to the IPv4 loopback address only, therefore # ensure the IPv6 address is removed from configured hosts resources { 'host': purge => true } $localhost = { 'localhost' => { ip => '127.0.0.1', host_aliases => ['localhost.localdomain', 'localhost4', 'localhost4.localdomain4'] }, } $merged_hosts = merge($localhost, $hosts) create_resources('host', $merged_hosts, {}) } Any one can give some help? Thanks! Zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Mar 18 16:30:39 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 18 Mar 2020 16:30:39 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Mar 18, 2020) In-Reply-To: References: Message-ID: >From today's meeting... * Standing Topics * Sanity * for Monolithic builds, all Green since last week * seeing these 3 issues though * https://bugs.launchpad.net/starlingx/+bug/1858659 * per Zipeng, the latest logs from Peng don't show this issue * https://bugs.launchpad.net/starlingx/+bug/1855474 * pending https://review.opendev.org/#/c/699532/ * Angie & Chris F to review * https://bugs.launchpad.net/starlingx/+bug/1859645 * will be fixed when Helm v3 is in, there's a StoryBoard * for Layered Builds... * https://bugs.launchpad.net/starlingx/+bug/1864221 * Scott targeting to be done by early next week * question about 'latest green build' * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008026.html * Scott will look into it - likely due to having MONOLITHIC or LAYERED in report name * Gerrit Reviews that Need Attention * none this week * CentOS 8 * reviews are underway * kernel upgrade call for tests http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008022.html * key risk now is the current inability to test tpm/integrity driver * Nic to confirm that they will be able to test this in early April * Topics for this Week * do we still have meeting record? * from https://wiki.openstack.org/wiki/Starlingx/Meeting_Logs#StarlingX_Infrastructure_Containerization_Team_Call only 2019 record. * Yes we do, I just need to find the time to sit down and sort out the real recordings and put up the links - Ildiko * Ildiko asked who's using these & what - no responses * Austin said he really just needs the Container meeting from Feb 4 since there was a demo * Ildiko said she'd dig this out * Open Requests for Help * documentation tasks (Mary) * Backup & Restore: https://storyboard.openstack.org/#!/story/2006770 (How to use Backup & Restore) * Layered Build: https://storyboard.openstack.org/#!/story/2007223 (update build guide w/ layered build info) * Redfish: https://storyboard.openstack.org/#!/story/2007222 (update dist cloud bare metal install w/ redfish info) * Dist Cloud: https://storyboard.openstack.org/#!/story/2006588 (updates for Dist Cloud) * Analysis of nfv using python3 * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/007991.html * some talk about whether they might be missing some steps, per Don's analysis in the Release Team meeting * they have done the steps that Don identified, but there may be steps in general that are missing * Issue with registry.local when applying platform-integ-app * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008038.html * Stx 3.0 Distributed Cloud - "platform-integ-apps" apply-filed * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/007984.html -----Original Message----- From: Zvonar, Bill Sent: Tuesday, March 17, 2020 11:24 AM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Mar 18, 2020) Hi all, reminder of tomorrow's TSC/Community call. We'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200318T1400 From Joseph.Richard at windriver.com Wed Mar 18 16:34:56 2020 From: Joseph.Richard at windriver.com (Richard, Joseph) Date: Wed, 18 Mar 2020 16:34:56 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. In-Reply-To: References: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314F6B2@SHSMSX104.ccr.corp.intel.com> , , Message-ID: Have you tried changing envAll.Values.conf.rabbitmq.listeners.tcp? I'd need to see the changes you've made to get rabbitmq running to provide any other ideas. ________________________________ From: Liu, ZhipengS Sent: Wednesday, March 18, 2020 10:53 AM To: Richard, Joseph ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, I will submit one patch for helm chart change later after fixing current issue. BTW, Seems we have no rabbitmqadmin in rabbitmq pod but rabbitmq-cluster-wait job. I have done below test and have some conclusion now. 1) Rabbtimq already started normally, and start listen on [::]:5672/15672/25672 port 2) It seems 15672 port access blocked for ipv6 (5672 is OK). In ipv4 simplex setup, same test below are all OK. Any idea? rabbitmq at osh-openstack-rabbitmq-rabbitmq-0:/usr/local$ rabbitmqctl status Status of node rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local ... Runtime OS PID: 303 OS: Linux Uptime (seconds): 6752 RabbitMQ version: 3.8.3 Node name: rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local Erlang configuration: Erlang/OTP 22 [erts-10.7] [source] [64-bit] [smp:6:6] [ds:6:6:10] [async-threads:128] Erlang processes: 426 used, 1048576 limit Scheduler run queue: 1 Cluster heartbeat timeout (net_ticktime): 60 Plugins Enabled plugin file: /etc/rabbitmq/enabled_plugins Enabled plugins: * rabbitmq_management * rabbitmq_web_dispatch * rabbitmq_peer_discovery_k8s * rabbitmq_peer_discovery_common * rabbitmq_management_agent * amqp_client * cowboy * cowlib Totals Connection count: 0 Queue count: 0 Virtual host count: 0 Listeners Interface: [::], port: 25672, protocol: clustering, purpose: inter-node and CLI tool communication Interface: [::], port: 5672, protocol: amqp, purpose: AMQP 0-9-1 and AMQP 1.0 Interface: [::], port: 15672, protocol: http, purpose: HTTP API controller-0:~$ wget http://rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local:15672/ --2020-03-18 14:37:45-- http://rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local:15672/ Resolving osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local (osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local)... fd03::1e6d:6abf Connecting to osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local (osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local)|fd03::1e6d:6abf|:15672... failed: Connection refused. //same as we see in the log of Rabbitmq-cluster-wait pod. controller-0:~$ wget http://rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local:5672/ --2020-03-18 14:37:53-- http://rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local:5672/ Resolving osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local (osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local)... fd03::1e6d:6abf Connecting to osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local (osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local)|fd03::1e6d:6abf|:5672... connected. controller-0:~$ wget http://[fd03::1e6d:6abf]:15672/ --2020-03-18 14:38:56-- http://[fd03::1e6d:6abf]:15672/ Connecting to [fd03::1e6d:6abf]:15672... failed: Connection refused. controller-0:~$ wget http://[fd03::1e6d:6abf]:5672/ --2020-03-18 14:39:00-- http://[fd03::1e6d:6abf]:5672/ Connecting to [fd03::1e6d:6abf]:5672... connected. Thanks! Zhipeng From: Richard, Joseph Sent: 2020年3月18日 21:48 To: Liu, ZhipengS ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Can you open a review with the change you made to fix the nxdomain issue? Is rabbitmqadmin able to connect if you run it from within osh-openstack-rabbitmq-rabbitmq-0? I see from your logs that the osh-openstack-rabbitmq-cluster-wait is from before rabbitmq was running. Can you see anything in the rabbitmq when the cluster-wait pod fails? ________________________________ From: Liu, ZhipengS > Sent: Tuesday, March 17, 2020 9:46 PM To: Richard, Joseph >; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, After did some changes in rabbitmq helm chart, I have fixed nxdomain issue in my ipv6 simplex setup. Below two pods can run up. osh-openstack-rabbitmq-cluster-wait-9rw6p 1/1 Running 0 17m osh-openstack-rabbitmq-rabbitmq-0 1/1 Running 0 17m However, still have another issue. In pod osh-openstack-rabbitmq-cluster-wait, it will use rabbitmqadmin to connect rabbitmq, but always get error. ++ active_rabbit_nodes 2020-03-17T10:31:12.124589385Z stderr F ++ wc -w 2020-03-17T10:31:12.134367271Z stderr F ++ rabbitmqadmin_authed list nodes -f bash 2020-03-17T10:31:12.134427089Z stderr F ++ set +x 2020-03-17T10:31:12.179073378Z stderr F Traceback (most recent call last): 2020-03-17T10:31:12.179644557Z stderr F error: [Errno 111] Connection refused 2020-03-17T10:31:12.17964969Z stderr F *** Could not connect: [Errno 111] Connection refused In the log of rabbitmq node, I can see below. 2020-03-17T15:40:27.762196613Z stdout F 2020-03-17 15:40:27.761 [info] <0.495.0> started TCP listener on [::]:5672 2020-03-17T15:40:27.807886117Z stdout F 2020-03-17 15:40:27.807 [info] <0.552.0> Management plugin: HTTP (non-TLS) listener started on port 15672 2020-03-17T15:40:27.895551288Z stdout F 2020-03-17 15:40:27.895 [info] <0.8.0> Server startup complete; 5 plugins started. 2020-03-17T15:40:27.895555144Z stdout F * rabbitmq_peer_discovery_k8s 2020-03-17T15:40:27.895557288Z stdout F * rabbitmq_management 2020-03-17T15:40:27.895559593Z stdout F * rabbitmq_management_agent 2020-03-17T15:40:27.895561807Z stdout F * rabbitmq_web_dispatch 2020-03-17T15:40:27.895564619Z stdout F * rabbitmq_peer_discovery_common I’m still working on this issue. Any comment or proposal, thanks! Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月16日 16:57 To: 'Richard, Joseph' >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, I tried many methods, but still not fixed the issue. I found there are some related issued fixed in upstream, but not yet merged to formal release. I’m discussing with them. Do you have any comment? https://github.com/rabbitmq/rabbitmq-peer-discovery-k8s/issues/55 Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月12日 9:53 To: 'Richard, Joseph' >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, Thank you so much! 😊 I will work further based on your provided clue. Best Regards, Zhipeng From: Richard, Joseph > Sent: 2020年3月12日 5:06 To: Liu, ZhipengS >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. I see a similar issue online here: https://groups.google.com/forum/#!topic/rabbitmq-users/9ir1WK-nYBA [http://www.google.com/images/icons/product/groups-128.png] epmd fails to start in IPv6 environment Posted 7/15/19 9:43 PM, 12 messages groups.google.com I expect that you are going to have to update rabbmitmq docker images to 3.7.16(currently 3.7.13), and then modify the helm plugin to pass in these values when using ipv6: SERVER_ADDITIONAL_ERL_ARGS='-proto_dist inet6_tcp' CTL_ERL_ARGS='-proto_dist inet6_tcp' Not sure if this is possible right now, or if you will need to modify openstack-helm-infra/rabbitmq in order to be able to pass these environment variables in. ________________________________ From: Liu, ZhipengS > Sent: Thursday, February 27, 2020 8:00 AM To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi all, For below LP IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status" https://bugs.launchpad.net/starlingx/+bug/1859641 I provided a patch which can fix the known issue in LP. However, it still failed later when starting rabbitmq pod. controller-0:~$ kubectl -n openstack get po NAME READY STATUS RESTARTS AGE ingress-c74489c96-jsb7n 1/1 Running 0 17h ingress-error-pages-5889bfcf6c-h8kl6 1/1 Running 0 17h mariadb-ingress-b5cd65f4b-sq46c 1/1 Running 0 17h mariadb-ingress-error-pages-6d8b79b74f-9zmpc 1/1 Running 0 17h mariadb-server-0 1/1 Running 0 17h osh-openstack-memcached-memcached-545668bdbd-9jkv2 1/1 Running 0 17h osh-openstack-rabbitmq-cluster-wait-wbnwp 0/1 Init:0/2 0 17h osh-openstack-rabbitmq-rabbitmq-0 0/1 CrashLoopBackOff 207 17h There are below error logs 2020-02-26T07:43:36.451103975Z stderr F ++ echo osh-openstack-rabbitmq-rabbitmq-0 2020-02-26T07:43:36.45142814Z stderr F ++ awk -F - '{print $NF}' 2020-02-26T07:43:36.454160452Z stderr F + POD_INCREMENT=0 2020-02-26T07:43:36.454757022Z stderr F + '[' 0 -eq 0 ']' 2020-02-26T07:43:36.454795721Z stderr F + exec rabbitmq-server 2020-02-26T07:43:36.849021551Z stdout F ERROR: epmd error for host osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local: nxdomain (non-existing domain) In /etc/hosts file below, I just found localhost4, no localhost6. Is it expected? I added below line manually after the line of 127.0.0.1. However, it didn’t work☹ ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 # HEADER: This file was autogenerated at 2020-02-26 09:00:35 +0000 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 fd01::1 controller 169.254.202.1 pxecontroller fd00::3 oamcontroller fd01::4 controller-platform-nfs fd01::3 controller-1 fd01::2 controller-0 fd02::3 controller-1-cluster-host fd02::2 controller-0-cluster-host fd01::e8b6:66fe storage-0 I saw that in ./stx-puppet/puppet-manifests/src/modules/platform/manifests/config.pp:215 class platform::config::hosts inherits ::platform::config::params { # The localhost should resolve to the IPv4 loopback address only, therefore # ensure the IPv6 address is removed from configured hosts resources { 'host': purge => true } $localhost = { 'localhost' => { ip => '127.0.0.1', host_aliases => ['localhost.localdomain', 'localhost4', 'localhost4.localdomain4'] }, } $merged_hosts = merge($localhost, $hosts) create_resources('host', $merged_hosts, {}) } Any one can give some help? Thanks! Zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Wed Mar 18 20:43:26 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 18 Mar 2020 21:43:26 +0100 Subject: [Starlingx-discuss] Fwd: [OpenStack Foundation] Update on OpenDev + PTG (Vancouver) References: <1584563593.8598643@emailsrvr.com> Message-ID: <1B236C76-6B21-4472-9AEB-0E880964B9F4@gmail.com> Hi StarlingX Community, In case you are not subscribed to the OpenStack Foundation mailing list please see below the update from Mark Collier about the OpenDev + PTG event that is planned for this June. Thanks and Best Regards, Ildikó > Begin forwarded message: > > From: "Mark Collier" > Subject: [OpenStack Foundation] Update on OpenDev + PTG (Vancouver) > Date: March 18, 2020 at 21:33:13 GMT+1 > To: foundation at lists.openstack.org > > Hi everyone, > > Based on the input from the community, board, and the latest information available from the health experts, we've made the decision not to hold the OpenDev + PTG in Vancouver this June. Instead, we're exploring ways to turn it into a virtual event and would love the help of everyone in the community. > > We will be reaching out to participants who have already registered to issue full refunds. > > We have always aimed to produce events "of the community, by the community," and this change for OpenDev + PTG is no exception. We would like to virtualize the PTG, since it is critical to producing the next release, targeting the same timeframe. We would like to recruit community volunteers to form a Virtual PTG Organization Team to collaborate with the OSF staff to incorporate best practices and ensure the event continues to meet the goals of the upstream community. We will need to begin pulling this plan together soon, so please add your name ot this etherpad if you are interested in helping: https://etherpad.openstack.org/p/Virtual_PTG_Planning. > > For OpenDev, discussions are also meant to be collaborative and free-flowing but are less time bound by the release schedule, so rather than trying to recreate that during a single virtual event at the same time as the virtual PTG, we are thinking about other ways to accomplish the same goals. We've already assembled an awesome team of Program Committee volunteers who have received proposals for moderated discussions, and we will be working with them on some ideas on the best way to move forward. > > For the time being, we are continuing with the plan for the Open Infrastructure Summit in Berlin October 19-23. For updates on OpenDev + PTG and the Summit, please continue to read and bookmark this status page which we will continue to update: https://www.openstack.org/events/covid-19-coronavirus-disease-updates > > Mark Collier > COO, OpenStack Foundation > > > _______________________________________________ > Foundation mailing list > Foundation at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Wed Mar 18 21:15:21 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 18 Mar 2020 17:15:21 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 47 - Failure! Message-ID: <666486847.999.1584566122648.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 47 Status: Failure Timestamp: 20200318T210947Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200318T210947Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: false From scott.little at windriver.com Wed Mar 18 22:28:25 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 18 Mar 2020 18:28:25 -0400 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> <0bbec920-0556-15ab-5d4e-635b36a8cc89@windriver.com> Message-ID: <1987cc45-e57f-4d99-a482-2a1ab293b143@windriver.com> The governance group.  i.e. who is the PL and TL. Probably 'distro' You can look over the existing choices here ...    git clone ssh://slittle1 at review.opendev.org:29418/starlingx/governance.git    cd governance    cat reference/tsc/projects.yaml ... note, this doc is rather out of date. On 2020-03-18 9:57 a.m., Chen, Haochuan Z wrote: > > Thanks Scott. > > Core: > > mingyuan.qi at intel.com > > austin.sun at intel.com > > haochuan.z.chen at intel.com > > This project belongs to flock layer > > What’s the meaning of group? > > Thanks > > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > > *From:*Scott Little > *Sent:* Wednesday, March 18, 2020 9:52 PM > *To:* Chen, Haochuan Z ; Rowsell, Brent > > *Cc:* 'starlingx-discuss at lists.starlingx.io' > > *Subject:* Re: create a new project for ceph containerizaiton > > I submitted https://review.opendev.org/#/c/713650/ on your behalf. > > Who will be the cores? > > What compile layer does it belong in?   Probably 'distro' > > Whet governance group? > > On 2020-03-17 7:54 p.m., Chen, Haochuan Z wrote: > > ok, here is my answer. > > 1) unique and descriptive name for the new git. > >     Rook storage application > > 2) A description of the project for the comment section.  A > sentence or two. > >     This is starlingx application to deploy rook helm chart, which > provide storage as starlingx storage backend > > 3) The url and branch of any upstream git used to seed the content > for the new git. > > https://review.opendev.org/starlingx/rook-storage-app > > > 4) is this a python project that needs to publish to PYPI ? > >     No > > Thanks! > > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > > *From:*Scott Little > > *Sent:* Wednesday, March 18, 2020 7:41 AM > *To:* Chen, Haochuan Z > ; Rowsell, Brent > > *Cc:* 'starlingx-discuss at lists.starlingx.io > ' > > > *Subject:* Re: create a new project for ceph containerizaiton > > Sorry, I missed your answer I think.  Where/ when did you send > it?  Or am I looking for a code review? > > Scott > > On 2020-03-09 9:57 p.m., Chen, Haochuan Z wrote: > > Hi Scott > > Check my answer and wait for your comment. > > Thanks! > > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > > *From:*Scott Little > > *Sent:* Monday, March 9, 2020 10:40 PM > *To:* Chen, Haochuan Z > ; Rowsell, Brent > > *Cc:* 'starlingx-discuss at lists.starlingx.io > ' > > > *Subject:* Re: create a new project for ceph containerizaiton > > Yes, I can help with that.  I can't create the new git myself, > but can help with the process of submitting the request to the > opendev admins > > First we'll need > > 1) unique and descriptive name for the new git. > > Rook storage application > > 2) A description of the project for the comment section.  A > sentence or two. > > This is starlingx application to deploy rook helm chart, which > provide storage as starlingx storage backend > > 3) The url and branch of any upstream git used to seed the > content for the new git. > > https://review.opendev.org/starlingx/rook-storage-app > > 4) is this a python project that needs to publish to PYPI ? > >     No > > Scott > > PS: The process is described out here [1] > > [1] https://docs.openstack.org/infra/manual/creators.html > > > On 2020-03-09 10:26 a.m., Chen, Haochuan Z wrote: > > Hi scott > > As last week sync with brent, we will create a new > application for ceph containeration. Could you help to > create this new git project for me? > > Thanks! > > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenw66 at chinaunicom.cn Thu Mar 19 03:48:15 2020 From: chenw66 at chinaunicom.cn (=?gb2312?B?V2VpIENoZW4owarNqLyvzcXBqs2o1MbK/b7d09DP3rmry76xvrK/KQ==?=) Date: Thu, 19 Mar 2020 03:48:15 +0000 Subject: [Starlingx-discuss] Question about openstack support on central cloud In-Reply-To: <1577772988426.88956@chinaunicom.cn> References: <1577772988426.88956@chinaunicom.cn> Message-ID: <1584589629867.31157@chinaunicom.cn> Dear Sir/Madam, We have a requirement that need to support virtual machine on the central cloud. In our structure, the central cloud is as a center with strong power which could do large scale compute. Our application only could be run on virtual machine or bare metal, and the virtual machine is the best choice. I tried to install stx-openstack and original openstack, both failed. Could anyone give some suggestion or solution? Thanks & Regards, Wei 如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 hqs-spmc at chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc at chinaunicom.cn ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yipeng.he at jitstack.com Thu Mar 19 07:21:19 2020 From: yipeng.he at jitstack.com (=?utf-8?B?5L2V5LmJ6bmP?=) Date: Thu, 19 Mar 2020 15:21:19 +0800 Subject: [Starlingx-discuss] enable pbr version Message-ID: Hello Saul I'm Yipeng He from JITStack, and I'm taking over the tasks of PBR. I encountered the following issue when trying to build iso: It fails when the suffix of the version generated by the PBR tool ended with number, for instance the building fails if the version id is 2.999.9999.rc1.dev23, and when I replaced it with 2.999.9999.rc1.dev, the ISO building was successful. I don't knwo why this happens, could please support and advice the solution for this issue. Yipeng.He -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Thu Mar 19 08:38:52 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Thu, 19 Mar 2020 08:38:52 +0000 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: <1987cc45-e57f-4d99-a482-2a1ab293b143@windriver.com> References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> <0bbec920-0556-15ab-5d4e-635b36a8cc89@windriver.com> <1987cc45-e57f-4d99-a482-2a1ab293b143@windriver.com> Message-ID: Hi Scott Yes, it should be 'distro '. PL is Austin, TL is saul. distro: pl: name: Austin Sun irc: email: austin.sun at intel.com tl: name: Saul Wold irc: sgw email: sgw at linux.intel.com BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Scott Little Sent: Thursday, March 19, 2020 6:28 AM To: Chen, Haochuan Z ; Rowsell, Brent Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: create a new project for ceph containerizaiton The governance group. i.e. who is the PL and TL. Probably 'distro' You can look over the existing choices here ... git clone ssh://slittle1 at review.opendev.org:29418/starlingx/governance.git cd governance cat reference/tsc/projects.yaml ... note, this doc is rather out of date. On 2020-03-18 9:57 a.m., Chen, Haochuan Z wrote: Thanks Scott. Core: mingyuan.qi at intel.com austin.sun at intel.com haochuan.z.chen at intel.com This project belongs to flock layer What's the meaning of group? Thanks Martin, Chen IOTG, Software Engineer 021-61164330 From: Scott Little Sent: Wednesday, March 18, 2020 9:52 PM To: Chen, Haochuan Z ; Rowsell, Brent Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: create a new project for ceph containerizaiton I submitted https://review.opendev.org/#/c/713650/ on your behalf. Who will be the cores? What compile layer does it belong in? Probably 'distro' Whet governance group? On 2020-03-17 7:54 p.m., Chen, Haochuan Z wrote: ok, here is my answer. 1) unique and descriptive name for the new git. Rook storage application 2) A description of the project for the comment section. A sentence or two. This is starlingx application to deploy rook helm chart, which provide storage as starlingx storage backend 3) The url and branch of any upstream git used to seed the content for the new git. https://review.opendev.org/starlingx/rook-storage-app 4) is this a python project that needs to publish to PYPI ? No Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Scott Little Sent: Wednesday, March 18, 2020 7:41 AM To: Chen, Haochuan Z ; Rowsell, Brent Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: create a new project for ceph containerizaiton Sorry, I missed your answer I think. Where/ when did you send it? Or am I looking for a code review? Scott On 2020-03-09 9:57 p.m., Chen, Haochuan Z wrote: Hi Scott Check my answer and wait for your comment. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Scott Little Sent: Monday, March 9, 2020 10:40 PM To: Chen, Haochuan Z ; Rowsell, Brent Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: create a new project for ceph containerizaiton Yes, I can help with that. I can't create the new git myself, but can help with the process of submitting the request to the opendev admins First we'll need 1) unique and descriptive name for the new git. Rook storage application 2) A description of the project for the comment section. A sentence or two. This is starlingx application to deploy rook helm chart, which provide storage as starlingx storage backend 3) The url and branch of any upstream git used to seed the content for the new git. https://review.opendev.org/starlingx/rook-storage-app 4) is this a python project that needs to publish to PYPI ? No Scott PS: The process is described out here [1] [1] https://docs.openstack.org/infra/manual/creators.html On 2020-03-09 10:26 a.m., Chen, Haochuan Z wrote: Hi scott As last week sync with brent, we will create a new application for ceph containeration. Could you help to create this new git project for me? Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Thu Mar 19 09:21:38 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 19 Mar 2020 09:21:38 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. In-Reply-To: References: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314F6B2@SHSMSX104.ccr.corp.intel.com> , Message-ID: Hi Joseph, I fixed this issue now!! After check port status by sudo ip -all netns exec lsof -I, it shows that Rabbitmq only bind 15672 to ipv4. I add below changes and pass the rabbitmq deployment. conf: rabbitmq: management.listener.port: 15672 management.listener.ip: "::" Next step: I have to think how to submit this patch to support both ipv4 and ipv6 BTW, are you sure we passed this test before using OpenStack- train version? If not change helm chart, how can we pass it? Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月19日 10:07 To: Richard, Joseph >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, Below is my patch to make rabbitmq pod start in ipv6 setup.(This is not a formal patch) From 99fc5aff8d70645c3130552789ea51d82cd287b2 Mon Sep 17 00:00:00 2001 From: Zhipeng Liu > Date: Thu, 19 Mar 2020 18:53:07 +0800 Subject: [PATCH] Fix rabbtimq pod not starting issue in IPv6 setup Signed-off-by: Zhipeng Liu > --- rabbitmq/templates/configmap-etc.yaml | 8 +++++++- rabbitmq/templates/job-cluster-wait.yaml | 2 ++ rabbitmq/templates/statefulset.yaml | 8 ++++++++ 3 files changed, 17 insertions(+), 1 deletion(-) diff --git a/rabbitmq/templates/configmap-etc.yaml b/rabbitmq/templates/configmap-etc.yaml index 87f25f5..18e2145 100644 --- a/rabbitmq/templates/configmap-etc.yaml +++ b/rabbitmq/templates/configmap-etc.yaml @@ -21,7 +21,8 @@ limitations under the License. {{- $_ := print "kubernetes.default.svc." $envAll.Values.endpoints.cluster_domain_suffix | set $envAll.Values.conf.rabbitmq.cluster_formation.k8s "host" -}} {{- end -}} -{{- $_ := print "0.0.0.0:" ( tuple "oslo_messaging" "internal" "amqp" . | include "helm-toolkit.endpoints.endpoint_port_lookup") | set $envAll.Values.conf.rabbitmq.listeners.tcp "1" -}} +{{- $_ := print ":::" ( tuple "oslo_messaging" "internal" "amqp" . | include "helm-toolkit.endpoints.endpoint_port_lookup") | set $envAll.Values.conf.rabbitmq.listeners.tcp "1" -}} + --- apiVersion: v1 @@ -33,4 +34,9 @@ data: {{ tuple "etc/_enabled_plugins.tpl" . | include "helm-toolkit.utils.template" | indent 4 }} rabbitmq.conf: | {{ include "rabbitmq.utils.to_rabbit_config" $envAll.Values.conf.rabbitmq | indent 4 }} + rabbitmq-env.conf: | + SERVER_ADDITIONAL_ERL_ARGS="+A 128 -kernel inetrc '/etc/rabbitmq/erl_inetrc' -proto_dist inet6_tcp" + CTL_ERL_ARGS="-proto_dist inet6_tcp" + erl_inetrc: | + {inet6, true}. {{ end }} diff --git a/rabbitmq/templates/job-cluster-wait.yaml b/rabbitmq/templates/job-cluster-wait.yaml index bf8e710..24a30a3 100644 --- a/rabbitmq/templates/job-cluster-wait.yaml +++ b/rabbitmq/templates/job-cluster-wait.yaml @@ -66,6 +66,8 @@ spec: env: - name: RABBITMQ_ADMIN_CONNECTION value: {{ tuple "oslo_messaging" "internal" "user" "http" $envAll | include "helm-toolkit.endpoints.authenticated_endpoint_uri_lookup" | quote }} + - name: RABBITMQ_CTL_ERL_ARGS + value: "-proto_dist inet6_tcp" - name: RABBIT_REPLICA_COUNT value: {{ $envAll.Values.pod.replicas.server | quote }} command: diff --git a/rabbitmq/templates/statefulset.yaml b/rabbitmq/templates/statefulset.yaml index 41dc198..64fc1cf 100644 --- a/rabbitmq/templates/statefulset.yaml +++ b/rabbitmq/templates/statefulset.yaml @@ -228,6 +228,14 @@ spec: mountPath: /etc/rabbitmq/rabbitmq.conf subPath: rabbitmq.conf readOnly: true + - name: rabbitmq-etc + mountPath: /etc/rabbitmq/rabbitmq-env.conf + subPath: rabbitmq-env.conf + readOnly: true + - name: rabbitmq-etc + mountPath: /etc/rabbitmq/erl_inetrc + subPath: erl_inetrc + readOnly: true volumes: - name: pod-tmp emptyDir: {} -- 2.7.4 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joseph.Richard at windriver.com Thu Mar 19 13:20:19 2020 From: Joseph.Richard at windriver.com (Richard, Joseph) Date: Thu, 19 Mar 2020 13:20:19 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. In-Reply-To: References: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314F6B2@SHSMSX104.ccr.corp.intel.com> , , Message-ID: Great! We definitely did support this before openstack-helm and openstack-helm-infra were upversioned around December. You should be able to control this in the rabbitmq helm plugin, so you can modify the behaviour based on ip version. https://github.com/starlingx/config/blob/master/sysinv/sysinv/sysinv/sysinv/helm/rabbitmq.py Once you get passed this point, does everything else come up as well? Does the app successfully apply? ________________________________ From: Liu, ZhipengS Sent: Thursday, March 19, 2020 5:21 AM To: Richard, Joseph Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, I fixed this issue now!! After check port status by sudo ip -all netns exec lsof -I, it shows that Rabbitmq only bind 15672 to ipv4. I add below changes and pass the rabbitmq deployment. conf: rabbitmq: management.listener.port: 15672 management.listener.ip: "::" Next step: I have to think how to submit this patch to support both ipv4 and ipv6 BTW, are you sure we passed this test before using OpenStack- train version? If not change helm chart, how can we pass it? Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月19日 10:07 To: Richard, Joseph >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, Below is my patch to make rabbitmq pod start in ipv6 setup.(This is not a formal patch) >From 99fc5aff8d70645c3130552789ea51d82cd287b2 Mon Sep 17 00:00:00 2001 From: Zhipeng Liu > Date: Thu, 19 Mar 2020 18:53:07 +0800 Subject: [PATCH] Fix rabbtimq pod not starting issue in IPv6 setup Signed-off-by: Zhipeng Liu > --- rabbitmq/templates/configmap-etc.yaml | 8 +++++++- rabbitmq/templates/job-cluster-wait.yaml | 2 ++ rabbitmq/templates/statefulset.yaml | 8 ++++++++ 3 files changed, 17 insertions(+), 1 deletion(-) diff --git a/rabbitmq/templates/configmap-etc.yaml b/rabbitmq/templates/configmap-etc.yaml index 87f25f5..18e2145 100644 --- a/rabbitmq/templates/configmap-etc.yaml +++ b/rabbitmq/templates/configmap-etc.yaml @@ -21,7 +21,8 @@ limitations under the License. {{- $_ := print "kubernetes.default.svc." $envAll.Values.endpoints.cluster_domain_suffix | set $envAll.Values.conf.rabbitmq.cluster_formation.k8s "host" -}} {{- end -}} -{{- $_ := print "0.0.0.0:" ( tuple "oslo_messaging" "internal" "amqp" . | include "helm-toolkit.endpoints.endpoint_port_lookup") | set $envAll.Values.conf.rabbitmq.listeners.tcp "1" -}} +{{- $_ := print ":::" ( tuple "oslo_messaging" "internal" "amqp" . | include "helm-toolkit.endpoints.endpoint_port_lookup") | set $envAll.Values.conf.rabbitmq.listeners.tcp "1" -}} + --- apiVersion: v1 @@ -33,4 +34,9 @@ data: {{ tuple "etc/_enabled_plugins.tpl" . | include "helm-toolkit.utils.template" | indent 4 }} rabbitmq.conf: | {{ include "rabbitmq.utils.to_rabbit_config" $envAll.Values.conf.rabbitmq | indent 4 }} + rabbitmq-env.conf: | + SERVER_ADDITIONAL_ERL_ARGS="+A 128 -kernel inetrc '/etc/rabbitmq/erl_inetrc' -proto_dist inet6_tcp" + CTL_ERL_ARGS="-proto_dist inet6_tcp" + erl_inetrc: | + {inet6, true}. {{ end }} diff --git a/rabbitmq/templates/job-cluster-wait.yaml b/rabbitmq/templates/job-cluster-wait.yaml index bf8e710..24a30a3 100644 --- a/rabbitmq/templates/job-cluster-wait.yaml +++ b/rabbitmq/templates/job-cluster-wait.yaml @@ -66,6 +66,8 @@ spec: env: - name: RABBITMQ_ADMIN_CONNECTION value: {{ tuple "oslo_messaging" "internal" "user" "http" $envAll | include "helm-toolkit.endpoints.authenticated_endpoint_uri_lookup" | quote }} + - name: RABBITMQ_CTL_ERL_ARGS + value: "-proto_dist inet6_tcp" - name: RABBIT_REPLICA_COUNT value: {{ $envAll.Values.pod.replicas.server | quote }} command: diff --git a/rabbitmq/templates/statefulset.yaml b/rabbitmq/templates/statefulset.yaml index 41dc198..64fc1cf 100644 --- a/rabbitmq/templates/statefulset.yaml +++ b/rabbitmq/templates/statefulset.yaml @@ -228,6 +228,14 @@ spec: mountPath: /etc/rabbitmq/rabbitmq.conf subPath: rabbitmq.conf readOnly: true + - name: rabbitmq-etc + mountPath: /etc/rabbitmq/rabbitmq-env.conf + subPath: rabbitmq-env.conf + readOnly: true + - name: rabbitmq-etc + mountPath: /etc/rabbitmq/erl_inetrc + subPath: erl_inetrc + readOnly: true volumes: - name: pod-tmp emptyDir: {} -- 2.7.4 -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Thu Mar 19 14:00:15 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 19 Mar 2020 14:00:15 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. In-Reply-To: References: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314F6B2@SHSMSX104.ccr.corp.intel.com> , , Message-ID: Thanks Joseph! I guess it can go further. But keystone-db failed, which is the same as I met in my another ipv4 setup. I will build an EB based on a latest green daily build. The patch will come soon for your review. Thanks! Zhipeng From: Richard, Joseph Sent: 2020年3月19日 21:20 To: Liu, ZhipengS Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Great! We definitely did support this before openstack-helm and openstack-helm-infra were upversioned around December. You should be able to control this in the rabbitmq helm plugin, so you can modify the behaviour based on ip version. https://github.com/starlingx/config/blob/master/sysinv/sysinv/sysinv/sysinv/helm/rabbitmq.py Once you get passed this point, does everything else come up as well? Does the app successfully apply? ________________________________ From: Liu, ZhipengS > Sent: Thursday, March 19, 2020 5:21 AM To: Richard, Joseph > Cc: starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, I fixed this issue now!! After check port status by sudo ip -all netns exec lsof -I, it shows that Rabbitmq only bind 15672 to ipv4. I add below changes and pass the rabbitmq deployment. conf: rabbitmq: management.listener.port: 15672 management.listener.ip: "::" Next step: I have to think how to submit this patch to support both ipv4 and ipv6 BTW, are you sure we passed this test before using OpenStack- train version? If not change helm chart, how can we pass it? Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月19日 10:07 To: Richard, Joseph >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, Below is my patch to make rabbitmq pod start in ipv6 setup.(This is not a formal patch) >From 99fc5aff8d70645c3130552789ea51d82cd287b2 Mon Sep 17 00:00:00 2001 From: Zhipeng Liu > Date: Thu, 19 Mar 2020 18:53:07 +0800 Subject: [PATCH] Fix rabbtimq pod not starting issue in IPv6 setup Signed-off-by: Zhipeng Liu > --- rabbitmq/templates/configmap-etc.yaml | 8 +++++++- rabbitmq/templates/job-cluster-wait.yaml | 2 ++ rabbitmq/templates/statefulset.yaml | 8 ++++++++ 3 files changed, 17 insertions(+), 1 deletion(-) diff --git a/rabbitmq/templates/configmap-etc.yaml b/rabbitmq/templates/configmap-etc.yaml index 87f25f5..18e2145 100644 --- a/rabbitmq/templates/configmap-etc.yaml +++ b/rabbitmq/templates/configmap-etc.yaml @@ -21,7 +21,8 @@ limitations under the License. {{- $_ := print "kubernetes.default.svc." $envAll.Values.endpoints.cluster_domain_suffix | set $envAll.Values.conf.rabbitmq.cluster_formation.k8s "host" -}} {{- end -}} -{{- $_ := print "0.0.0.0:" ( tuple "oslo_messaging" "internal" "amqp" . | include "helm-toolkit.endpoints.endpoint_port_lookup") | set $envAll.Values.conf.rabbitmq.listeners.tcp "1" -}} +{{- $_ := print ":::" ( tuple "oslo_messaging" "internal" "amqp" . | include "helm-toolkit.endpoints.endpoint_port_lookup") | set $envAll.Values.conf.rabbitmq.listeners.tcp "1" -}} + --- apiVersion: v1 @@ -33,4 +34,9 @@ data: {{ tuple "etc/_enabled_plugins.tpl" . | include "helm-toolkit.utils.template" | indent 4 }} rabbitmq.conf: | {{ include "rabbitmq.utils.to_rabbit_config" $envAll.Values.conf.rabbitmq | indent 4 }} + rabbitmq-env.conf: | + SERVER_ADDITIONAL_ERL_ARGS="+A 128 -kernel inetrc '/etc/rabbitmq/erl_inetrc' -proto_dist inet6_tcp" + CTL_ERL_ARGS="-proto_dist inet6_tcp" + erl_inetrc: | + {inet6, true}. {{ end }} diff --git a/rabbitmq/templates/job-cluster-wait.yaml b/rabbitmq/templates/job-cluster-wait.yaml index bf8e710..24a30a3 100644 --- a/rabbitmq/templates/job-cluster-wait.yaml +++ b/rabbitmq/templates/job-cluster-wait.yaml @@ -66,6 +66,8 @@ spec: env: - name: RABBITMQ_ADMIN_CONNECTION value: {{ tuple "oslo_messaging" "internal" "user" "http" $envAll | include "helm-toolkit.endpoints.authenticated_endpoint_uri_lookup" | quote }} + - name: RABBITMQ_CTL_ERL_ARGS + value: "-proto_dist inet6_tcp" - name: RABBIT_REPLICA_COUNT value: {{ $envAll.Values.pod.replicas.server | quote }} command: diff --git a/rabbitmq/templates/statefulset.yaml b/rabbitmq/templates/statefulset.yaml index 41dc198..64fc1cf 100644 --- a/rabbitmq/templates/statefulset.yaml +++ b/rabbitmq/templates/statefulset.yaml @@ -228,6 +228,14 @@ spec: mountPath: /etc/rabbitmq/rabbitmq.conf subPath: rabbitmq.conf readOnly: true + - name: rabbitmq-etc + mountPath: /etc/rabbitmq/rabbitmq-env.conf + subPath: rabbitmq-env.conf + readOnly: true + - name: rabbitmq-etc + mountPath: /etc/rabbitmq/erl_inetrc + subPath: erl_inetrc + readOnly: true volumes: - name: pod-tmp emptyDir: {} -- 2.7.4 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ruediger.stock at intel.com Thu Mar 19 15:58:47 2020 From: ruediger.stock at intel.com (Stock, Ruediger) Date: Thu, 19 Mar 2020 15:58:47 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build - ISO 20200318 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-18 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200318T225117Z/outputs/iso/) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [BLOCKED] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [BLOCKED] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== The bug that was created for the issue with Simplex and Duplex is still reproducible with the latest build: https://bugs.launchpad.net/starlingx/+bug/1864221. Regards, STX Validation Team Rüdiger Stock Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Thu Mar 19 17:43:12 2020 From: scott.little at windriver.com (Scott Little) Date: Thu, 19 Mar 2020 13:43:12 -0400 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> <0bbec920-0556-15ab-5d4e-635b36a8cc89@windriver.com> Message-ID: <0492432b-cf8c-9d66-f08a-a4df0e826bd7@windriver.com> The URL https://review.opendev.org/starlingx/rook-storage-app is invalid Please provide a valid upstream url. Scott On 2020-03-17 7:54 p.m., Chen, Haochuan Z wrote: > > 3) The url and branch of any upstream git used to seed the content for > the new git. > > https://review.opendev.org/starlingx/rook-storage-app > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Thu Mar 19 18:35:39 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 19 Mar 2020 18:35:39 +0000 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: <0492432b-cf8c-9d66-f08a-a4df0e826bd7@windriver.com> References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> <0bbec920-0556-15ab-5d4e-635b36a8cc89@windriver.com> <0492432b-cf8c-9d66-f08a-a4df0e826bd7@windriver.com> Message-ID: <20200319183538.bknvzsdhmr3w42kz@yuggoth.org> On 2020-03-19 13:43:12 -0400 (-0400), Scott Little wrote: > The URL https://review.opendev.org/starlingx/rook-storage-app is > invalid > > Please provide a valid upstream url. [...] Alternatively, if you want to start with an empty repository and propose all the source additions to it via code review from the very beginning, you can just leave out the "upstream" parameter and the project creation automation will do a simple `git init` and commit a properly-formatted .gitreview file into the master branch for you. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From build.starlingx at gmail.com Thu Mar 19 20:09:15 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 19 Mar 2020 16:09:15 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 478 - Failure! Message-ID: <403265487.1008.1584648556795.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 478 Status: Failure Timestamp: 20200319T162221Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200319T162221Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Thu Mar 19 20:22:24 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 19 Mar 2020 16:22:24 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 50 - Failure! Message-ID: <1302831499.1012.1584649345839.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 50 Status: Failure Timestamp: 20200319T193039Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200319T193039Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From Ghada.Khalil at windriver.com Thu Mar 19 22:29:39 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 19 Mar 2020 22:29:39 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 03/19 Message-ID: Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking - Attendees: Ghada Khalil, Joseph Richard, Steve Webster, Chris Winnicki, Yi Wang, Alexandru Dimofte, Cosmin Albescu, Mihal-Laurentiu Trica, Nicolae Jascanu - Steve Webster has taken on the role of networking PL. He will chair the meetings moving forward. stx.4.0 Features - TSN support in kata container - Question: Is there any code for this? or just a procedure? - As per Yi, the kernel will need be upgraded in the kata container. At a minimum, the 4.20 kernel is needed. Currently, the kata runtime in stx uses a 4.18 or 4.19 kernel. - kata upstream (currently alpha release) is now using a 5.x kernel - Not sure when this release of kata will be officially available - Ghada will check w/ Yong if we can get schedule information - As per Steve, he expects stx will need to build a custom kata runtime to pick up additional drivers - Reference: https://bugs.launchpad.net/starlingx/+bug/1867927 - Yi is currently setting up a TSN network - First step is to setup a generic Ubunutu node w/ a TSN switch - Once that is working, will proceed to setup a StarlingX node. - Yi will be working closely with Shuicheng to coordinate efforts on kata upgrade. - Will target code merge (feature ready for test) by milestone-3 (May 15) - Test Status - The plan is to test Kata containers first, then test TSN after. - The test team in Romainia is ordering Extreme Network switches. Nick will verify if they have TSN capabilities. - IPv6 PXE boot network support - Kunpeng is investigating. He's sent some questions to the stx mailing list. Joseph is helping with responses. - Feature plan / timing: TBD - Test Update - Received some servers in Galati and will start setup. - Right now, test activities rely on the infrastructure in Mexico stx.4.0 Bugs - Total: 5 - https://bugs.launchpad.net/starlingx/+bug/1867927 - Kata container runtime does not include support for SR-IOV devices - New. Assigned to Shuicheng as he is the prime for the kata container feature - https://bugs.launchpad.net/starlingx/+bug/1866230 - Tracebacks related to LLPD neighbor (INSERT INTO lldp_tlvs) filling sysinv.log - New, Assigned to Thomas. This is a simple fix to avoid a sysinv exception in the lldp tlv is too long. - https://bugs.launchpad.net/starlingx/+bug/1862651 -- IPv6 DC: 100.113 alarm "'DATA-NETWORK0' interface failed" raised at both system controller and subclouds after installation - No update. Still not assigned. Issue appears to be related to having multiple data ports. - https://bugs.launchpad.net/starlingx/+bug/1850438 -- The sriov device plugin pod may start before it's config manifest is written - No update: Still on hold. Intermittent happening at a much lower frequency. Agreed to keep as gating for stx.4.0 for now, but as a lower priority item - https://bugs.launchpad.net/starlingx/+bug/1833463 -- armada-manifest upload failed when configuring bond with OVS container (vswitch-type=none) - No update. Action with Yong to re-assign. Work is related to openstack-helm - https://bugs.launchpad.net/starlingx/+bug/1859641 - IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status" - One fix merged. Zhipeng is making progress on the next issue related to rabbitmq stx.3.0 Bugs - Total: 1 - https://bugs.launchpad.net/starlingx/+bug/1821026 -- Containers: Resolving hostname fails within nova containers leading to config_drive VM migration failures - No Update. Work has not resumed Low Priority Bugs - Total: 6 - 2 bugs merged. 1 in progress (code review posted) From Ghada.Khalil at windriver.com Thu Mar 19 23:04:29 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 19 Mar 2020 23:04:29 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Mar 19/2020 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.4.0 - Feature Update - Feature plans continue to be updated/refined. Thank you everyone! - Summary: - In / Ongoing: 20 - Out: 10 - TBD: 5 - Feature Plans: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 - Test Update - Plans started for Feature Testing and Regression Testing - Feature Testing: https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=968103774 - Regression Testing: https://docs.google.com/spreadsheets/d/1gA3bnLS7aY2y8dKxm4MuqpWyELq3PVJMYtiHn4IWiAk/edit#gid=1921715792 - Action: Test PL to confirm test status for milestone-2 From haochuan.z.chen at intel.com Fri Mar 20 00:33:46 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 20 Mar 2020 00:33:46 +0000 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: <0492432b-cf8c-9d66-f08a-a4df0e826bd7@windriver.com> References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> <0bbec920-0556-15ab-5d4e-635b36a8cc89@windriver.com> <0492432b-cf8c-9d66-f08a-a4df0e826bd7@windriver.com> Message-ID: I prefer create a blank project with this link. Then I will upstream. Martin, Chen IOTG, Software Engineer 021-61164330 From: Scott Little Sent: Friday, March 20, 2020 1:43 AM To: Chen, Haochuan Z ; Rowsell, Brent Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: create a new project for ceph containerizaiton The URL https://review.opendev.org/starlingx/rook-storage-app is invalid Please provide a valid upstream url. Scott On 2020-03-17 7:54 p.m., Chen, Haochuan Z wrote: 3) The url and branch of any upstream git used to seed the content for the new git. https://review.opendev.org/starlingx/rook-storage-app -------------- next part -------------- An HTML attachment was scrubbed... URL: From lianhao.lu at intel.com Fri Mar 20 07:57:44 2020 From: lianhao.lu at intel.com (Lu, Lianhao) Date: Fri, 20 Mar 2020 07:57:44 +0000 Subject: [Starlingx-discuss] STX3 heartbeat lost causing controller and worker nodes rebooting Message-ID: <857BE142E5399E46B20FD45B9DB8A7BC4D2B67E4@SHSMSX104.ccr.corp.intel.com> Hi STX gurus, Currently I met an issue of standby controller and worker nodes keep rebooting due to the lost of heartbeat in STX3, hope someone could give me some help. Thanks very much! My system contains the following configuration: Controllers: Two Inspur nf8260m5 servers each with 2 Intel X550T NICs, 1 X550 NIC for OAM network and the other for mgmt network. Worker node: one x86_64 server with 2 Intel X722 NICs, 1 X722 NIC for mgmt. network and the other for data. The 2 OAM network NICs are all connected to a switch, and the 3 mgmt NICs are connected to another switch. I follow the STX installation guide of the deployment option Standard with Controller Storage, but now I'm facing an issue of the controller-0(stand-by controller) and worker-0(the only work node) keeps rebooting. Though I can successfully ping to controller-0 and worker-0 from my active controller-1, and vice versa. I still see the following log in /var/log/mtcAgent.log. ------ log excerpt from mtcAgent.log ----- 2020-03-20T07:42:02.837 [2285790.01035] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat minor set (Mgmnt) 2020-03-20T07:42:02.837 [2285790.01036] controller-1 mtcAgent --- mtcNodeMnfa.cpp ( 131) mnfa_add_host : Info : controller-0 MNFA new candidate (Mgmnt) 1 enabled hosts (threshold:2) (1:Mgmnt:10) (0:Clstr:0) 2020-03-20T07:42:03.047 [2285790.01037] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat degrade set (Mgmnt) 2020-03-20T07:42:03.047 [2285790.01038] controller-1 mtcAgent hbs nodeClass.cpp (5060) manage_heartbeat_degrade: Warn : controller-0 Mgmnt *** Heartbeat Miss *** 2020-03-20T07:42:03.047 [2285790.01039] controller-1 mtcAgent inv mtcInvApi.cpp (1119) mtcInvApi_update_state : Info : controller-0 degraded (seq:97) 2020-03-20T07:42:03.468 [2285790.01040] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat loss (Mgmnt) 2020-03-20T07:42:03.468 [2285790.01041] controller-1 mtcAgent hbs nodeClass.cpp (4941) manage_heartbeat_failure:Error : controller-0 Mgmnt *** Heartbeat Loss *** 2020-03-20T07:42:03.468 [2285790.01042] controller-1 mtcAgent hbs nodeClass.cpp (4952) manage_heartbeat_failure:Error : controller-0 Mgmnt network heartbeat failure 2020-03-20T07:42:03.468 [2285790.01043] controller-1 mtcAgent inv mtcInvApi.cpp (1119) mtcInvApi_update_state : Info : controller-0 failed (seq:98) 2020-03-20T07:42:03.468 [2285790.01044] controller-1 mtcAgent hbs nodeClass.cpp (4965) manage_heartbeat_failure: Warn : controller-0 starting graceful recovery 2020-03-20T07:42:03.468 [2285790.01045] controller-1 mtcAgent |-| mtcNodeHdlrs.cpp (1643) recovery_handler : Info : controller-0 Graceful Recovery (uptime was 473) 2020-03-20T07:42:03.468 [2285790.01046] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 stop host service sent to controller-0 hbsAgent 2020-03-20T07:42:03.468 [2285790.01047] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 stop host service sent to controller-1 hbsAgent 2020-03-20T07:42:03.468 [2285790.01048] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1684) recovery_handler : Warn : controller-0 Graceful Recovery (1 of 3) 2020-03-20T07:42:03.468 [2285790.01049] controller-1 mtcAgent inv mtcInvApi.cpp ( 334) mtcInvApi_update_task : Info : controller-0 Task: Graceful Recovery (seq:99) 2020-03-20T07:42:03.468 [2285790.01050] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat minor clear (Mgmnt) 2020-03-20T07:42:03.468 [2285790.01051] controller-1 mtcAgent hbs nodeClass.cpp (4833) hbs_minor_clear : Warn : controller-0 MNFA host tally (Mgmnt:0) 2020-03-20T07:42:03.468 [2285790.01052] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat degrade clear (Mgmnt) 2020-03-20T07:42:05.473 [2285790.01053] controller-1 mtcAgent |-| nodeClass.cpp (2542) start_offline_handler : Info : controller-0 starting offline handler (unlocked-enabled-failed) (stage:0) 2020-03-20T07:42:05.473 [2285790.01054] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1729) recovery_handler : Info : controller-0 requesting mtcAlive with 5 sec timeout 2020-03-20T07:42:05.473 [2285790.01055] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (3242) offline_handler : Info : controller-0 starting 100 msec offline audit (enabled-failed) 2020-03-20T07:42:05.473 [2285790.01056] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1747) recovery_handler : Info : controller-0 got requested mtcAlive 2020-03-20T07:42:05.473 [2285790.01057] controller-1 mtcAgent |-| nodeClass.cpp (2555) stop_offline_handler : Info : controller-0 stopping offline handler (unlocked-enabled-failed) (stage:3) 2020-03-20T07:42:05.473 [2285790.01058] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1814) recovery_handler : Warn : controller-0 Connectivity Recovered ; host did not reset 2020-03-20T07:42:05.473 [2285790.01059] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1816) recovery_handler : Warn : controller-0 ... continuing with graceful recovery 2020-03-20T07:42:05.473 [2285790.01060] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1817) recovery_handler : Warn : controller-0 ... with no affect to host services 2020-03-20T07:42:05.473 [2285790.01061] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 start host service sent to controller-0 hbsAgent 2020-03-20T07:42:05.473 [2285790.01062] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 start host service sent to controller-1 hbsAgent 2020-03-20T07:42:05.473 [2285790.01063] controller-1 mtcAgent |-| mtcNodeHdlrs.cpp (2489) recovery_handler : Info : controller-0 Starting 11 sec Heartbeat Soak (with ready event) 2020-03-20T07:42:05.474 [2285790.01064] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat minor clear (Mgmnt) 2020-03-20T07:42:05.474 [2285790.01065] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat degrade clear (Mgmnt) 2020-03-20T07:42:05.985 [2285790.01066] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat minor set (Mgmnt) 2020-03-20T07:42:05.985 [2285790.01067] controller-1 mtcAgent --- mtcNodeMnfa.cpp ( 131) mnfa_add_host : Info : controller-0 MNFA new candidate (Mgmnt) 1 enabled hosts (threshold:2) (1:Mgmnt:11) (0:Clstr:0) 2020-03-20T07:42:06.196 [2285790.01068] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat degrade set (Mgmnt) 2020-03-20T07:42:06.196 [2285790.01069] controller-1 mtcAgent hbs nodeClass.cpp (5060) manage_heartbeat_degrade: Warn : controller-0 Mgmnt *** Heartbeat Miss *** 2020-03-20T07:42:06.616 [2285790.01070] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat loss (Mgmnt) 2020-03-20T07:42:06.616 [2285790.01071] controller-1 mtcAgent hbs nodeClass.cpp (4941) manage_heartbeat_failure:Error : controller-0 Mgmnt *** Heartbeat Loss *** 2020-03-20T07:42:06.616 [2285790.01072] controller-1 mtcAgent hbs nodeClass.cpp (4952) manage_heartbeat_failure:Error : controller-0 Mgmnt network heartbeat failure 2020-03-20T07:42:06.616 [2285790.01073] controller-1 mtcAgent hbs nodeClass.cpp (4961) manage_heartbeat_failure: Warn : controller-0 restarting graceful recovery 2020-03-20T07:42:06.616 [2285790.01074] controller-1 mtcAgent |-| mtcNodeHdlrs.cpp (1643) recovery_handler : Info : controller-0 Graceful Recovery (uptime was 478) 2020-03-20T07:42:06.616 [2285790.01075] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 stop host service sent to controller-0 hbsAgent 2020-03-20T07:42:06.616 [2285790.01076] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 stop host service sent to controller-1 hbsAgent 2020-03-20T07:42:06.616 [2285790.01077] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1684) recovery_handler : Warn : controller-0 Graceful Recovery (2 of 3) 2020-03-20T07:42:06.616 [2285790.01078] controller-1 mtcAgent inv mtcInvApi.cpp ( 334) mtcInvApi_update_task : Info : controller-0 Task: Graceful Recovery Retry (seq:100) 2020-03-20T07:42:06.616 [2285790.01079] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat minor clear (Mgmnt) 2020-03-20T07:42:06.616 [2285790.01080] controller-1 mtcAgent hbs nodeClass.cpp (4833) hbs_minor_clear : Warn : controller-0 MNFA host tally (Mgmnt:0) 2020-03-20T07:42:06.616 [2285790.01081] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat degrade clear (Mgmnt) 2020-03-20T07:42:08.569 [2285790.01082] controller-1 mtcAgent |-| mtcNodeHdlrs.cpp (1421) enable_handler : Info : worker-0 heartbeating 2020-03-20T07:42:08.574 [2285790.01083] controller-1 mtcAgent inv mtcInvApi.cpp ( 437) mtcInvApi_force_task : Info : worker-0 task clear (seq:96) (was:Enabling) 2020-03-20T07:42:08.574 fmAPI.cpp(490): Enqueue raise alarm request: UUID (b24f0d21-6c0d-4862-99de-6e8ad1f04b99) alarm id (200.022) instant id (host=worker-0.state=enabled) 2020-03-20T07:42:08.574 [2285790.01084] controller-1 mtcAgent hbs nodeClass.cpp (6188) allStateChange : Info : worker-0 unlocked-enabled-degraded (seq:97) 2020-03-20T07:42:08.605 fmAlarmUtils.cpp(624): Sending FM raise alarm request: alarm_id (200.022), entity_id (host=worker-0.state=enabled) 2020-03-20T07:42:08.620 [2285790.01085] controller-1 mtcAgent |-| nodeClass.cpp (2542) start_offline_handler : Info : controller-0 starting offline handler (unlocked-enabled-failed) (stage:0) 2020-03-20T07:42:08.620 [2285790.01086] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1729) recovery_handler : Info : controller-0 requesting mtcAlive with 5 sec timeout 2020-03-20T07:42:08.620 [2285790.01087] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (3242) offline_handler : Info : controller-0 starting 100 msec offline audit (enabled-failed) 2020-03-20T07:42:08.620 [2285790.01088] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1747) recovery_handler : Info : controller-0 got requested mtcAlive 2020-03-20T07:42:08.620 [2285790.01089] controller-1 mtcAgent |-| nodeClass.cpp (2555) stop_offline_handler : Info : controller-0 stopping offline handler (unlocked-enabled-failed) (stage:3) 2020-03-20T07:42:08.620 [2285790.01090] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1814) recovery_handler : Warn : controller-0 Connectivity Recovered ; host did not reset 2020-03-20T07:42:08.620 [2285790.01091] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1816) recovery_handler : Warn : controller-0 ... continuing with graceful recovery 2020-03-20T07:42:08.620 [2285790.01092] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1817) recovery_handler : Warn : controller-0 ... with no affect to host services 2020-03-20T07:42:08.621 [2285790.01093] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 start host service sent to controller-0 hbsAgent 2020-03-20T07:42:08.621 [2285790.01094] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 start host service sent to controller-1 hbsAgent 2020-03-20T07:42:08.621 [2285790.01095] controller-1 mtcAgent |-| mtcNodeHdlrs.cpp (2489) recovery_handler : Info : controller-0 Starting 11 sec Heartbeat Soak (with ready event) 2020-03-20T07:42:08.621 [2285790.01096] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat minor clear (Mgmnt) 2020-03-20T07:42:09.134 [2285790.01104] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat minor set (Mgmnt) 2020-03-20T07:42:09.134 [2285790.01105] controller-1 mtcAgent --- mtcNodeMnfa.cpp ( 131) mnfa_add_host : Info : controller-0 MNFA new candidate (Mgmnt) 2 enabled hosts (threshold:2) (1:Mgmnt:12) (0:Clstr:0) 2020-03-20T07:42:09.344 [2285790.01106] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat degrade set (Mgmnt) 2020-03-20T07:42:09.344 [2285790.01107] controller-1 mtcAgent hbs nodeClass.cpp (5060) manage_heartbeat_degrade: Warn : controller-0 Mgmnt *** Heartbeat Miss *** 2020-03-20T07:42:09.764 [2285790.01108] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat loss (Mgmnt) 2020-03-20T07:42:09.764 [2285790.01109] controller-1 mtcAgent hbs nodeClass.cpp (4941) manage_heartbeat_failure:Error : controller-0 Mgmnt *** Heartbeat Loss *** 2020-03-20T07:42:09.764 [2285790.01110] controller-1 mtcAgent hbs nodeClass.cpp (4952) manage_heartbeat_failure:Error : controller-0 Mgmnt network heartbeat failure 2020-03-20T07:42:09.764 [2285790.01111] controller-1 mtcAgent hbs nodeClass.cpp (4961) manage_heartbeat_failure: Warn : controller-0 restarting graceful recovery 2020-03-20T07:42:09.765 [2285790.01112] controller-1 mtcAgent |-| mtcNodeHdlrs.cpp (1643) recovery_handler : Info : controller-0 Graceful Recovery (uptime was 481) 2020-03-20T07:42:09.765 [2285790.01113] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 stop host service sent to controller-0 hbsAgent 2020-03-20T07:42:09.765 [2285790.01114] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 stop host service sent to controller-1 hbsAgent 2020-03-20T07:42:09.765 [2285790.01115] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1684) recovery_handler : Warn : controller-0 Graceful Recovery (3 of 3) 2020-03-20T07:42:09.765 [2285790.01116] controller-1 mtcAgent inv mtcInvApi.cpp ( 334) mtcInvApi_update_task : Info : controller-0 Task: Graceful Recovery Retry (seq:101) 2020-03-20T07:42:09.765 [2285790.01117] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat minor clear (Mgmnt) 2020-03-20T07:42:09.765 [2285790.01118] controller-1 mtcAgent hbs nodeClass.cpp (4833) hbs_minor_clear : Warn : controller-0 MNFA host tally (Mgmnt:0) 2020-03-20T07:42:09.765 [2285790.01119] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat degrade clear (Mgmnt) 2020-03-20T07:42:10.468 [2285790.01120] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (3473) online_handler : Info : controller-0 mtcAlive ; going 'online' 2020-03-20T07:42:10.468 [2285790.01121] controller-1 mtcAgent inv mtcInvApi.cpp (1119) mtcInvApi_update_state : Info : controller-0 online (seq:102) 2020-03-20T07:42:11.770 [2285790.01122] controller-1 mtcAgent |-| nodeClass.cpp (2542) start_offline_handler : Info : controller-0 starting offline handler (unlocked-enabled-online) (stage:0) 2020-03-20T07:42:11.770 [2285790.01123] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1729) recovery_handler : Info : controller-0 requesting mtcAlive with 5 sec timeout 2020-03-20T07:42:11.770 [2285790.01124] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (3242) offline_handler : Info : controller-0 starting 100 msec offline audit (enabled-online) 2020-03-20T07:42:11.770 [2285790.01125] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1747) recovery_handler : Info : controller-0 got requested mtcAlive 2020-03-20T07:42:11.770 [2285790.01126] controller-1 mtcAgent |-| nodeClass.cpp (2555) stop_offline_handler : Info : controller-0 stopping offline handler (unlocked-enabled-online) (stage:3) 2020-03-20T07:42:11.770 [2285790.01127] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1814) recovery_handler : Warn : controller-0 Connectivity Recovered ; host did not reset 2020-03-20T07:42:11.770 [2285790.01128] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1816) recovery_handler : Warn : controller-0 ... continuing with graceful recovery 2020-03-20T07:42:11.770 [2285790.01129] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1817) recovery_handler : Warn : controller-0 ... with no affect to host services 2020-03-20T07:42:11.770 [2285790.01130] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 start host service sent to controller-0 hbsAgent 2020-03-20T07:42:11.770 [2285790.01131] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 start host service sent to controller-1 hbsAgent 2020-03-20T07:42:11.770 [2285790.01132] controller-1 mtcAgent |-| mtcNodeHdlrs.cpp (2489) recovery_handler : Info : controller-0 Starting 11 sec Heartbeat Soak (with ready event) 2020-03-20T07:42:11.770 [2285790.01133] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat minor clear (Mgmnt) 2020-03-20T07:42:11.770 [2285790.01134] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat degrade clear (Mgmnt) 2020-03-20T07:42:12.282 [2285790.01135] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat minor set (Mgmnt) 2020-03-20T07:42:12.282 [2285790.01136] controller-1 mtcAgent --- mtcNodeMnfa.cpp ( 131) mnfa_add_host : Info : controller-0 MNFA new candidate (Mgmnt) 2 enabled hosts (threshold:2) (1:Mgmnt:13) (0:Clstr:0) 2020-03-20T07:42:12.493 [2285790.01137] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat degrade set (Mgmnt) 2020-03-20T07:42:12.493 [2285790.01138] controller-1 mtcAgent hbs nodeClass.cpp (5060) manage_heartbeat_degrade: Warn : controller-0 Mgmnt *** Heartbeat Miss *** 2020-03-20T07:42:12.913 [2285790.01139] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat loss (Mgmnt) 2020-03-20T07:42:12.913 [2285790.01140] controller-1 mtcAgent hbs nodeClass.cpp (4941) manage_heartbeat_failure:Error : controller-0 Mgmnt *** Heartbeat Loss *** 2020-03-20T07:42:12.913 [2285790.01141] controller-1 mtcAgent hbs nodeClass.cpp (4952) manage_heartbeat_failure:Error : controller-0 Mgmnt network heartbeat failure 2020-03-20T07:42:12.913 [2285790.01142] controller-1 mtcAgent inv mtcInvApi.cpp (1119) mtcInvApi_update_state : Info : controller-0 failed (seq:103) 2020-03-20T07:42:12.914 [2285790.01143] controller-1 mtcAgent hbs nodeClass.cpp (4961) manage_heartbeat_failure: Warn : controller-0 restarting graceful recovery 2020-03-20T07:42:12.914 [2285790.01144] controller-1 mtcAgent |-| mtcNodeHdlrs.cpp (1643) recovery_handler : Info : controller-0 Graceful Recovery (uptime was 484) 2020-03-20T07:42:12.914 [2285790.01145] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 stop host service sent to controller-0 hbsAgent 2020-03-20T07:42:12.914 [2285790.01146] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 stop host service sent to controller-1 hbsAgent 2020-03-20T07:42:12.914 [2285790.01147] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (1671) recovery_handler :Error : controller-0 Graceful Recovery Failed (retries=4) 2020-03-20T07:42:12.914 [2285790.01148] controller-1 mtcAgent |-| nodeClass.cpp (7590) force_full_enable : Info : controller-0 Forcing Full Enable Sequence 2020-03-20T07:42:12.914 [2285790.01149] controller-1 mtcAgent hbs nodeClass.cpp (1681) alarm_enabled_failure :Error : controller-0 critical enable failure 2020-03-20T07:42:12.914 [2285790.01150] controller-1 mtcAgent alm mtcAlarm.cpp ( 417) mtcAlarm_critical :Error : controller-0 setting critical 'In-Service' failure alarm (200.004 ) 2020-03-20T07:42:12.914 fmAPI.cpp(490): Enqueue raise alarm request: UUID (4f1c52ab-098d-4b87-aafc-acfdd2c7ac7a) alarm id (200.004) instant id (host=controller-0) 2020-03-20T07:42:12.914 fmAPI.cpp(490): Enqueue raise alarm request: UUID (d6a99af3-2e3b-4bf4-b0db-07f966fafea2) alarm id (200.022) instant id (host=controller-0.state=disabled) 2020-03-20T07:42:12.914 [2285790.01151] controller-1 mtcAgent hbs nodeClass.cpp (6188) allStateChange : Info : controller-0 unlocked-disabled-failed (seq:104) 2020-03-20T07:42:12.914 [2285790.01152] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat minor clear (Mgmnt) 2020-03-20T07:42:12.914 [2285790.01153] controller-1 mtcAgent hbs nodeClass.cpp (4833) hbs_minor_clear : Warn : controller-0 MNFA host tally (Mgmnt:0) 2020-03-20T07:42:12.914 [2285790.01154] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp ( 573) enable_handler :Error : controller-0 Main Enable FSM (from failed) 2020-03-20T07:42:12.914 [2285790.01155] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 stop host service sent to controller-0 hbsAgent 2020-03-20T07:42:12.914 [2285790.01156] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 stop host service sent to controller-1 hbsAgent 2020-03-20T07:42:12.914 [2285790.01157] controller-1 mtcAgent vim mtcVimApi.cpp ( 251) mtcVimApi_state_change :Error : controller-0 {"state-change": {"administrative":"unlocked","operational":"disabled","availability":"failed","subfunction_oper":"disabled","subfunction_avail":"not-installed"},"hostname":"controller-0","uuid":"28412a2d-fb95-472d-9797-c2ef4b18752f","subfunctions":"controller","personality":"controller"} 2020-03-20T07:42:12.914 [2285790.01158] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat degrade clear (Mgmnt) 2020-03-20T07:42:12.914 [2285790.01159] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat minor clear (Mgmnt) 2020-03-20T07:42:12.914 [2285790.01160] controller-1 mtcAgent |-| mtcNodeHdlrs.cpp ( 769) enable_handler : Info : controller-0 Main Enable FSM (from start) 2020-03-20T07:42:12.914 [2285790.01161] controller-1 mtcAgent --- mtcWorkQueue.cpp ( 750) workQueue_purge : Warn : controller-0 purging 4 items from workQueue 2020-03-20T07:42:12.914 [2285790.01162] controller-1 mtcAgent --- mtcWorkQueue.cpp ( 764) workQueue_purge : Warn : controller-0 mtcInvApi_update_state seq:103 ... did not complete (Wait) 2020-03-20T07:42:12.914 [2285790.01163] controller-1 mtcAgent --- mtcWorkQueue.cpp ( 758) workQueue_purge : Warn : controller-0 mtcInvApi_force_states seq:104 ... was not executed 2020-03-20T07:42:12.914 [2285790.01164] controller-1 mtcAgent --- mtcWorkQueue.cpp ( 758) workQueue_purge : Warn : controller-0 mtcInvApi_force_states seq:105 ... was not executed 2020-03-20T07:42:12.914 [2285790.01165] controller-1 mtcAgent --- mtcWorkQueue.cpp ( 758) workQueue_purge : Warn : controller-0 mtcVimApi_state_change seq:106 ... was not executed 2020-03-20T07:42:12.914 [2285790.01166] controller-1 mtcAgent mgr mtcSmgrApi.cpp ( 209) mtcSmgrApi_request : Info : controller-0 sending 'unlocked-disabled' request to HA Service Manager 2020-03-20T07:42:12.919 [2285790.01167] controller-1 mtcAgent mgr mtcSmgrApi.cpp ( 300) mtcSmgrApi_request : Info : controller-0 is 'disabled' to Service Management 2020-03-20T07:42:12.919 [2285790.01168] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat degrade clear (Mgmnt) 2020-03-20T07:42:12.919 [2285790.01169] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 stop host service sent to controller-0 hbsAgent 2020-03-20T07:42:12.919 [2285790.01170] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 878) send_hbs_command : Info : controller-0 stop host service sent to controller-1 hbsAgent 2020-03-20T07:42:12.919 [2285790.01171] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat minor clear (Mgmnt) 2020-03-20T07:42:12.919 [2285790.01172] controller-1 mtcAgent |-| mtcNodeHdlrs.cpp ( 963) enable_handler : Info : controller-0 reboot 2020-03-20T07:42:12.919 [2285790.01173] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp ( 91) calc_reset_prog_timeout : Info : controller-0 Reboot/Reset progression has 40 sec 'wait for offline' timeout 2020-03-20T07:42:12.919 [2285790.01174] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp ( 95) calc_reset_prog_timeout : Info : controller-0 ... sources - mgmnt:Yes clstr:No bmc:No 2020-03-20T07:42:12.919 [2285790.01175] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 971) service_events : Info : controller-0 heartbeat degrade clear (Mgmnt) 2020-03-20T07:42:12.924 [2285790.01176] controller-1 mtcAgent inv mtcInvApi.cpp ( 334) mtcInvApi_update_task : Info : controller-0 Task: Reboot Request (seq:108) 2020-03-20T07:42:12.924 [2285790.01177] controller-1 mtcAgent |-| nodeClass.cpp (2542) start_offline_handler : Info : controller-0 starting offline handler (unlocked-disabled-failed) (stage:0) 2020-03-20T07:42:12.924 [2285790.01178] controller-1 mtcAgent hdl mtcNodeHdlrs.cpp (3242) offline_handler : Info : controller-0 starting 100 msec offline audit (disabled-failed) 2020-03-20T07:42:12.924 [2285790.01179] controller-1 mtcAgent msg mtcCtrlMsg.cpp ( 629) send_mtc_cmd : Info : controller-0 sending 'reboot' request (Mgmnt network) 2020-03-20T07:42:12.924 [2285790.01180] controller-1 mtcAgent cmd mtcCmdHdlr.cpp ( 403) cmd_handler : Info : controller-0 waiting for REBOOT ACK 2020-03-20T07:42:12.924 [2285790.01181] controller-1 mtcAgent |-| mtcCmdHdlr.cpp ( 437) cmd_handler : Info : controller-0 REBOOT Request Succeeded 2020-03-20T07:42:12.924 [2285790.01182] controller-1 mtcAgent inv mtcInvApi.cpp ( 334) mtcInvApi_update_task : Info : controller-0 Task: Rebooting (seq:109) 2020-03-20T07:42:12.924 [2285790.01183] controller-1 mtcAgent cmd mtcCmdHdlr.cpp ( 459) cmd_handler : Info : controller-0 searching for offline ; next reboot attempt in 7 seconds BR, -Lianhao -------------- next part -------------- An HTML attachment was scrubbed... URL: From ran1.an at intel.com Fri Mar 20 08:57:29 2020 From: ran1.an at intel.com (An, Ran1) Date: Fri, 20 Mar 2020 08:57:29 +0000 Subject: [Starlingx-discuss] [Python3] Analysis of nfv using python3 In-Reply-To: <9BAB5B7CAF57C3459E4636391F1071CE053A1249@shsmsx102.ccr.corp.intel.com> References: <9BAB5B7CAF57C3459E4636391F1071CE053A1249@shsmsx102.ccr.corp.intel.com> Message-ID: Hi all Last week, I sent a mail listed issues I met during upgrading nfv to support python3 task. With further investigating, here is my solution of the issues: 1. to build python3 "fm-api" rpm, pkg "python3-rpm-generators" is required. But it is conflict with pkg "rpm-build" built in the compile layer, because both of them have file (/usr/lib/rpm/pythondistdeps.py). // this is a general issue which will be met each time we build rpm pkg with requirement(build requirement) of python3-devel, such as python3-deamon required by logmgmt. My workaround is: rebuild python3-rpm-generators pkg from official srpm with file (usr/lib/rpm/pythondistdeps.py) removed. Pkg "rpm-build" will be the build requirement of python3-rpm-generators pkg to ensure file (usr/lib/rpm/pythondistdeps.py) is existed after python3-rpm-generators pkg is built. 2. as other flock services, like sysinv, are still running in python2, so it require fm-api to both run in python2 env and python3 env. It introduces a new topic: ensure it is safe to run python2-fm-api and python3-fm-api at the same time. // the methods fm_api provides are thread safe. So it should be safe to run python2-fm-api and python3-fm-api at the same time. I'll start to build python3 "fm-api" rpm, then model "fm-api" will supported both in python2 and python3. Thanks Ran From: An, Ran1 Sent: Thursday, March 12, 2020 2:19 PM To: starlingx-discuss at lists.starlingx.io; Tao Liu ; Al Bailey ; Bart Wensley Cc: Sun, Austin Subject: [Starlingx-discuss] [Python3] Analysis of nfv using python3 Hi all: I'm working on task "upgrade project nfv to support python3 runtime env". By analyzing and testing, there will be 32 new python3 rpms, which may impact current system. * 16 new rpms from official centos7 repo; * 12 new stx-rpms rebuilt with srpms from official centos7 repo (turn on python3 supported switch in spec); * 4 stx-rpms built from tar.gz files. Details including pkg dependency trees and current status could be found in [1] With patches [2], we could get an iso with nfv services (vim,vim-api, vim-webserver) running in python3. However, there is an run-time issues. Model "fm_api" in python3 is required to support vim service reporting alarms/event_logs to fault manager (service fm-mgr). It brings following issues: 1. to build python3 "fm-api" rpm, pkg "python3-rpm-generators" is required. But it is conflict with pkg "rpm-build" built in the compile layer, because both of them have file (/usr/lib/rpm/pythondistdeps.py). 2. as other flock services, like sysinv, are still running in python2, so it require fm-api to both run in python2 env and python3 env. It introduces a new topic: ensure it is safe to run python2-fm-api and python3-fm-api at the same time. The scope of this task seems expand. Is there any suggestions? [1] https://bugs.launchpad.net/starlingx/+bug/1808073/+attachment/5335996/+files/nfv%20python%20dependency%20analysis.xlsx [2] patches: https://review.opendev.org/709958; https://review.opendev.org/709960; https://review.opendev.org/709983/1 ; https://review.opendev.org/709980 Thanks Ran -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Fri Mar 20 11:13:13 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 20 Mar 2020 12:13:13 +0100 Subject: [Starlingx-discuss] StarlingX feedback Message-ID: Hi StarlingX Community, As you may already know we have a user survey continuously open to see interest and receive feedback from people who evaluate and deploy StarlingX. I received a more detailed feedback through the survey recently that I would like to share with you below. The person who provided the feedback has good experience with the Wind River Titanium platform and that is why he decided to look into StarlingX and try it out. He marked MEC as his primary use case in the survey. With limited time and resources he had a small test environment to play with that included controller nodes on 2 VM's and 4 physical compute nodes as the following: * Controllers: * 1x HPE DL360 Gen8 (1x12core CPU, 32GB RAM) * Computes: * 2x HPE DL360 Gen9 (2x10core CPU, 128GB RAM) * 2x HPE DL380 Gen9 (2x18core CPU, 192GB RAM) Starling X versions tested: * 2.0 * 3.0 Installation experience: As it is very similar to the Titanium platform the installation of controllers and computes went pretty smooth and there weren’t too many issues. Most of the challenges came from controlling the containers in the new environment which was an expected experience. Due to the lack of documentation at that time about configuration steps the required steps were performed as experimental steps until finding the right ones. Challenges: The way how OpenStack networking was propagated over data networks turned out to be very problematic and caused hitting the wall a few times. In details you have to configure data networks over the platform management components, but then you have to set VLAN's you are going to use over data networks on the OpenStack side. This was not documented anywhere. Once data network is set up it was also a challenge to get VM’s running and connecting to networks since computes would become unstable. In summary he is not a fan of decoupling the platform parts from the OpenStack part. Issues with stability: - controllers going out of sync (maybe due to running them in VM's on the same host that was a bit limited with resources) - computes loosing Openstack helm packages after reboot - computes had random Neutron or Nova services crash when deploying VM’s Overall summary: At this point StarlingX doesn't feel stable enough for critical loads but there is a lot of potential in the platform. It is good to be able to have 2 controller nodes instead of 4 as some other OpenStack deployments demand. Also architecture choices done under the hood are quite nice and simple which he liked. Big plus is having no hassle with writing bunch of deployment templates. Platform monitoring is great and patching also looks promising but he never got the time to test it. The person who provided the feedback currently has very limited time to look into StarlingX but hoping to be able to get back to it in the future. In case you have follow up questions please provide that on this mail thread or if there’s a demand for it I will check if he would be available to join one of the community calls to follow up on the above. Thanks and Best Regards, Ildikó From Joseph.Richard at windriver.com Fri Mar 20 14:44:50 2020 From: Joseph.Richard at windriver.com (Richard, Joseph) Date: Fri, 20 Mar 2020 14:44:50 +0000 Subject: [Starlingx-discuss] iPXE for IPv6 In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0C15FF245@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0C1655A1D@ALA-MBD.corp.ad.wrs.com> <4BB34F6B-CF07-4AC0-9049-3A5AB51A0F69@99cloud.net> <151EE31B9FCCA54397A757BC674650F0C1689226@ALA-MBD.corp.ad.wrs.com> <1EDF4B46-F06D-4834-ADBD-6DBAB3C22E3E@99cloud.net> , Message-ID: From the tcpdump it shows that it still tries sending a boot over ipv4 after getting an ipv6 address. I don't see any indication that the controller is doing anything incorrectly, so it is probably something with the configuration on the node you are trying to bring up. What sort of config is this? Is this on hardware(which) or virtualbox(which version)? What steps are you following to setup the initial install of the node that you are trying to boot? ________________________________ From: 张鲲鹏 Sent: Monday, March 16, 2020 11:27 PM To: Richard, Joseph Cc: Khalil, Ghada ; 黄舒泉 ; Jolliffe, Ian ; Peters, Matt ; Le, Huifeng ; Yong Hu Subject: Re: [Starlingx-discuss] iPXE for IPv6 Hi Joseph, Following are the logs when boot a host from ipxe. No errors to be found. And the boot file are not sent as the tcpdump show. sysinv.log sysinv 2020-03-17 02:51:52.977 959934 INFO sysinv.cmd.dnsmasq_lease_update [-] Called 'add' for mac '00:68:27:6e:8a:42' with ip 'fd00::3f' sysinv 2020-03-17 02:51:53.217 959934 INFO sysinv.openstack.common.rpc.common [-] Connected to AMQP server on 192.168.204.1:5672 sysinv 2020-03-17 02:51:53.229 95238 INFO sysinv.conductor.manager [-] receiving dhcp_lease: pxeboot dhcpv6 enp2s2 00:68:27:6e:8a:42 fd00::3f None sysinv 2020-03-17 02:51:53.261 95238 INFO sysinv.conductor.manager [-] Not creating ihost for mac: 00:68:27:6e:8a:42 because it already exists with uuid: 4e8ebd40-11a6-4d8e-8a8e-b2f8a703bc7e sysinv 2020-03-17 02:52:27.718 95238 INFO sysinv.conductor.manager [-] Platform managed application platform-integ-apps: Prerequisites not met. deamon.log 2020-03-17T02:51:49.000 controller-0 collectd[81838]: info ovs interface plugin failed to initial because pid file for ovs-vswitchd doesn't exist 2020-03-17T02:51:51.000 controller-0 dnsmasq-dhcp[4093358]: info DHCPDISCOVER(enp2s2) 52:54:00:0e:6a:02 no address available 2020-03-17T02:51:51.000 controller-0 dnsmasq-dhcp[4093358]: info RTR-SOLICIT(enp2s2) 52:54:00:0e:6a:02 2020-03-17T02:51:51.000 controller-0 dnsmasq-dhcp[4093358]: info RTR-ADVERT(enp2s2) fd00:: 2020-03-17T02:51:51.000 controller-0 dnsmasq-dhcp[4093358]: info DHCPSOLICIT(enp2s2) 00:04:2c:7e:7b:71:b2:c5:49:df:a6:53:00:68:27:6e:8a:42 2020-03-17T02:51:51.000 controller-0 dnsmasq-dhcp[4093358]: info DHCPADVERTISE(enp2s2) fd00::3f 00:04:2c:7e:7b:71:b2:c5:49:df:a6:53:00:68:27:6e:8a:42 2020-03-17T02:51:51.000 controller-0 dnsmasq-dhcp[4093358]: info DHCPREQUEST(enp2s2) 00:04:2c:7e:7b:71:b2:c5:49:df:a6:53:00:68:27:6e:8a:42 2020-03-17T02:51:51.000 controller-0 dnsmasq-dhcp[4093358]: info DHCPREPLY(enp2s2) fd00::3f 00:04:2c:7e:7b:71:b2:c5:49:df:a6:53:00:68:27:6e:8a:42 2020-03-17T02:51:52.000 controller-0 dnsmasq-dhcp[4093358]: info DHCPDISCOVER(enp2s2) 52:54:00:0e:6a:02 no address available 2020-03-17T02:51:52.000 controller-0 dnsmasq-script[4093358]: debug sysinv 2020-03-17 02:51:52.977 959934 INFO sysinv.cmd.dnsmasq_lease_update [-] Called 'add' for mac '00:68:27:6e:8a:42' with ip 'fd00::3f'^[[00m 2020-03-17T02:51:53.000 controller-0 dnsmasq-script[4093358]: debug sysinv 2020-03-17 02:51:53.217 959934 INFO sysinv.openstack.common.rpc.common [-] Connected to AMQP server on 192.168.204.1:5672^[[00m 2020-03-17T02:51:54.000 controller-0 dnsmasq-dhcp[4093358]: info DHCPDISCOVER(enp2s2) 52:54:00:0e:6a:02 no address available 2020-03-17T02:51:58.000 controller-0 dnsmasq-dhcp[4093358]: info DHCPDISCOVER(enp2s2) 52:54:00:0e:6a:02 no address available tcpdump -i enp2s2 03:03:37.966202 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:38.471640 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:38.501756 ARP, Request who-has controller-1 tell controller-0, length 28 03:03:38.977102 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:39.333447 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 52:54:00:0e:6a:02 (oui Unknown), length 402 03:03:39.333541 IP6 fe80::5054:ff:fe0e:6a02 > ff02::2: ICMP6, router solicitation, length 16 03:03:39.334408 IP6 fe80::5054:ff:fe5c:f3d7 > fe80::5054:ff:fe0e:6a02: ICMP6, router advertisement, length 88 03:03:39.345812 IP6 fe80::5054:ff:fe0e:6a02.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 solicit 03:03:39.346207 IP6 fe80::5054:ff:fe5c:f3d7.dhcpv6-server > fe80::5054:ff:fe0e:6a02.dhcpv6-client: dhcp6 advertise 03:03:39.346488 IP6 fe80::5054:ff:fe0e:6a02.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 request 03:03:39.349335 IP6 fe80::5054:ff:fe5c:f3d7.dhcpv6-server > fe80::5054:ff:fe0e:6a02.dhcpv6-client: dhcp6 reply 03:03:39.482543 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:39.503651 ARP, Request who-has controller-1 tell controller-0, length 28 03:03:39.988061 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:40.311669 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 52:54:00:0e:6a:02 (oui Unknown), length 402 03:03:40.493543 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:40.505647 ARP, Request who-has controller-1 tell controller-0, length 28 03:03:40.999049 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:41.504513 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:41.507747 ARP, Request who-has controller-1 tell controller-0, length 28 03:03:42.010033 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:42.288943 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 52:54:00:0e:6a:02 (oui Unknown), length 402 03:03:42.509638 ARP, Request who-has controller-1 tell controller-0, length 28 03:03:42.515480 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:43.020834 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:43.511663 ARP, Request who-has controller-1 tell controller-0, length 28 03:03:43.526277 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:44.031727 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:44.345728 IP6 fe80::5054:ff:fe5c:f3d7 > fe80::5054:ff:fe0e:6a02: ICMP6, neighbor solicitation, who has fe80::5054:ff:fe0e:6a02, length 32 03:03:44.345968 IP6 fe80::5054:ff:fe0e:6a02 > fe80::5054:ff:fe5c:f3d7: ICMP6, neighbor advertisement, tgt is fe80::5054:ff:fe0e:6a02, length 32 03:03:44.513797 ARP, Request who-has controller-1 tell controller-0, length 28 03:03:44.537218 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:45.042730 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:45.515707 ARP, Request who-has controller-1 tell controller-0, length 28 03:03:45.548183 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:46.053802 IP controller-0.51259 > 239.1.1.2.mzap: UDP, length 75 03:03:46.243493 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 52:54:00:0e:6a:02 (oui Unknown), length 402 03:03:46.517640 ARP, Request who-has controller-1 tell controller-0, length 28 在 2020年3月13日,06:10,Richard, Joseph > 写道: _______________________________________________ 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 bruce.e.jones at intel.com Fri Mar 20 15:05:45 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 20 Mar 2020 15:05:45 +0000 Subject: [Starlingx-discuss] error access docker registry.. Message-ID: <9A85D2917C58154C960D95352B22818BF1698EEC@fmsmsx123.amr.corp.intel.com> We have a user who is hitting this error. Any idea what might be going on? TASK [common/push-docker-images : Log in to local registry] ******************************************************************************************************************************************************** fatal: [localhost]: FAILED! => {"changed": false, "msg": "Logging into registry.local:9001 for user admin failed - 500 Server Error: Internal Server Error (\"Get https://registry.local:9001/v2/: Get https://192.168.204.1:9002/token/?account=admin&client_id=docker&offline_token=true&service=192.168.204.1%3A9001: net/http: TLS handshake timeout\")"} Thanks! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Mar 20 15:52:33 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 20 Mar 2020 15:52:33 +0000 Subject: [Starlingx-discuss] StarlingX feedback In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BF1698FDA@fmsmsx123.amr.corp.intel.com> Ildiko, thank you for sharing this with the community. Feedback is a gift, and this kind of feedback is especially helpful. It tells us what we need to work on to improve both the software and its documentation. If you can, please thank this user on behalf of our community. bruej -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: Friday, March 20, 2020 4:13 AM To: starlingx Subject: [Starlingx-discuss] StarlingX feedback Hi StarlingX Community, As you may already know we have a user survey continuously open to see interest and receive feedback from people who evaluate and deploy StarlingX. I received a more detailed feedback through the survey recently that I would like to share with you below. The person who provided the feedback has good experience with the Wind River Titanium platform and that is why he decided to look into StarlingX and try it out. He marked MEC as his primary use case in the survey. With limited time and resources he had a small test environment to play with that included controller nodes on 2 VM's and 4 physical compute nodes as the following: * Controllers: * 1x HPE DL360 Gen8 (1x12core CPU, 32GB RAM) * Computes: * 2x HPE DL360 Gen9 (2x10core CPU, 128GB RAM) * 2x HPE DL380 Gen9 (2x18core CPU, 192GB RAM) Starling X versions tested: * 2.0 * 3.0 Installation experience: As it is very similar to the Titanium platform the installation of controllers and computes went pretty smooth and there weren’t too many issues. Most of the challenges came from controlling the containers in the new environment which was an expected experience. Due to the lack of documentation at that time about configuration steps the required steps were performed as experimental steps until finding the right ones. Challenges: The way how OpenStack networking was propagated over data networks turned out to be very problematic and caused hitting the wall a few times. In details you have to configure data networks over the platform management components, but then you have to set VLAN's you are going to use over data networks on the OpenStack side. This was not documented anywhere. Once data network is set up it was also a challenge to get VM’s running and connecting to networks since computes would become unstable. In summary he is not a fan of decoupling the platform parts from the OpenStack part. Issues with stability: - controllers going out of sync (maybe due to running them in VM's on the same host that was a bit limited with resources) - computes loosing Openstack helm packages after reboot - computes had random Neutron or Nova services crash when deploying VM’s Overall summary: At this point StarlingX doesn't feel stable enough for critical loads but there is a lot of potential in the platform. It is good to be able to have 2 controller nodes instead of 4 as some other OpenStack deployments demand. Also architecture choices done under the hood are quite nice and simple which he liked. Big plus is having no hassle with writing bunch of deployment templates. Platform monitoring is great and patching also looks promising but he never got the time to test it. The person who provided the feedback currently has very limited time to look into StarlingX but hoping to be able to get back to it in the future. In case you have follow up questions please provide that on this mail thread or if there’s a demand for it I will check if he would be available to join one of the community calls to follow up on the above. Thanks and Best Regards, Ildikó _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ruediger.stock at intel.com Fri Mar 20 15:55:31 2020 From: ruediger.stock at intel.com (Stock, Ruediger) Date: Fri, 20 Mar 2020 15:55:31 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build - ISO 20200320 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-20 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200320T013000Z/outputs/iso/) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex [BLOCKED] Setup 04 TCs [BLOCKED] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 ] AIO - Duplex [BLOCKED] Setup 04 TCs [BLOCKED] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Both sanity tests on duplex hit the issue https://bugs.launchpad.net/starlingx/+bug/1856078 Regards, STX Validation Team Rüdiger Stock Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Andy.Ning at windriver.com Fri Mar 20 18:11:39 2020 From: Andy.Ning at windriver.com (Ning, Antai (Andy)) Date: Fri, 20 Mar 2020 18:11:39 +0000 Subject: [Starlingx-discuss] stx docs input: 1861438, 1860995 Message-ID: Hi All, We have enhanced system's certificate configuration ability to be able to: - Install multiple CA certificates by "system certificate-install -m ssl_ca " The file may contains one or more CA certificates in X.509 PEM format. - Uninstall a particular CA certificate by its uuid by "system certificate-uninstall -m ssl_ca " The uninstall supports only CA (mode ssl_ca) certificate. The enhancement is for US1861438, US1860995. The changes are merged as reviews: https://review.opendev.org/#/c/711538 https://review.opendev.org/#/c/712152 https://review.opendev.org/#/c/711633 Please let me know if you need further information. Thanks, Andy Gerrit Code Review ID: Subject: Status: Owner: Project: Branch: Updated: Size: CR: RP: V: W: 713711 [WIP] Support Redfish Auth review.opendev.org Gerrit Code Review ID: Subject: Status: Owner: Project: Branch: Updated: Size: CR: RP: V: W: 713711 [WIP] Support Redfish Auth review.opendev.org Gerrit Code Review ID: Subject: Status: Owner: Project: Branch: Updated: Size: CR: RP: V: W: 713711 [WIP] Support Redfish Auth review.opendev.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From Andy.Ning at windriver.com Fri Mar 20 18:22:50 2020 From: Andy.Ning at windriver.com (Ning, Antai (Andy)) Date: Fri, 20 Mar 2020 18:22:50 +0000 Subject: [Starlingx-discuss] stx docs input: 1861438, 1860995 In-Reply-To: References: Message-ID: I should make some corrections to my previous email: The enhancement is for LP1861438, LP1860995 (not user stories): https://bugs.launchpad.net/starlingx/+bug/1860995 https://bugs.launchpad.net/starlingx/+bug/1861438 Sorry for the confusion. Andy ________________________________ From: Ning, Antai (Andy) Sent: Friday, March 20, 2020 2:11 PM To: starlingx-discuss at lists.starlingx.io ; maryx.camp at intel.com ; Balaraj, Juanita Subject: [Starlingx-discuss] stx docs input: 1861438, 1860995 Hi All, We have enhanced system's certificate configuration ability to be able to: - Install multiple CA certificates by "system certificate-install -m ssl_ca " The file may contains one or more CA certificates in X.509 PEM format. - Uninstall a particular CA certificate by its uuid by "system certificate-uninstall -m ssl_ca " The uninstall supports only CA (mode ssl_ca) certificate. The enhancement is for US1861438, US1860995. The changes are merged as reviews: https://review.opendev.org/#/c/711538 https://review.opendev.org/#/c/712152 https://review.opendev.org/#/c/711633 Please let me know if you need further information. Thanks, Andy Gerrit Code Review ID: Subject: Status: Owner: Project: Branch: Updated: Size: CR: RP: V: W: 713711 [WIP] Support Redfish Auth review.opendev.org Gerrit Code Review ID: Subject: Status: Owner: Project: Branch: Updated: Size: CR: RP: V: W: 713711 [WIP] Support Redfish Auth review.opendev.org Gerrit Code Review ID: Subject: Status: Owner: Project: Branch: Updated: Size: CR: RP: V: W: 713711 [WIP] Support Redfish Auth review.opendev.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Sat Mar 21 10:17:39 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 21 Mar 2020 06:17:39 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_post_installer - Build # 616 - Failure! Message-ID: <2063832347.1018.1584785860983.JavaMail.javamailuser@localhost> Project: STX_build_post_installer Build #: 616 Status: Failure Timestamp: 20200321T095849Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200321T054453Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200321T054453Z DOCKER_BUILD_ID: jenkins-master-20200321T054453Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200321T054453Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200321T054453Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Sat Mar 21 10:17:43 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 21 Mar 2020 06:17:43 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 481 - Failure! Message-ID: <1634065621.1021.1584785864464.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 481 Status: Failure Timestamp: 20200321T054453Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200321T054453Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Sat Mar 21 12:28:27 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 21 Mar 2020 08:28:27 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 147 - Failure! Message-ID: <1613181962.1024.1584793708947.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 147 Status: Failure Timestamp: 20200321T121612Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200321T114452Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200321T114452Z DOCKER_BUILD_ID: jenkins-master-flock-20200321T114452Z-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/20200321T114452Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200321T114452Z/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 Sat Mar 21 12:28:31 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 21 Mar 2020 08:28:31 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 53 - Failure! Message-ID: <1193277226.1027.1584793712387.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 53 Status: Failure Timestamp: 20200321T114452Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200321T114452Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: false From build.starlingx at gmail.com Sat Mar 21 14:04:25 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 21 Mar 2020 10:04:25 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_post_installer - Build # 617 - Still Failing! In-Reply-To: <1379889310.1016.1584785857192.JavaMail.javamailuser@localhost> References: <1379889310.1016.1584785857192.JavaMail.javamailuser@localhost> Message-ID: <791041226.1031.1584799466974.JavaMail.javamailuser@localhost> Project: STX_build_post_installer Build #: 617 Status: Still Failing Timestamp: 20200321T140423Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200321T054453Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200321T054453Z DOCKER_BUILD_ID: jenkins-master-20200321T054453Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200321T054453Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200321T054453Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Sun Mar 22 01:32:18 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 21 Mar 2020 21:32:18 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 483 - Failure! Message-ID: <842667844.1041.1584840739436.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 483 Status: Failure Timestamp: 20200322T013002Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200322T013002Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From build.starlingx at gmail.com Sun Mar 22 11:15:08 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 22 Mar 2020 07:15:08 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 150 - Failure! Message-ID: <417940035.1046.1584875709801.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 150 Status: Failure Timestamp: 20200322T110228Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200322T080223Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200322T080223Z DOCKER_BUILD_ID: jenkins-master-flock-20200322T080223Z-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/20200322T080223Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200322T080223Z/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 Sun Mar 22 11:15:12 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 22 Mar 2020 07:15:12 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 54 - Still Failing! In-Reply-To: <928327318.1025.1584793709888.JavaMail.javamailuser@localhost> References: <928327318.1025.1584793709888.JavaMail.javamailuser@localhost> Message-ID: <1965150514.1049.1584875713599.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 54 Status: Still Failing Timestamp: 20200322T080223Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200322T080223Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: false From fuyong at neusoft.com Mon Mar 23 03:10:50 2020 From: fuyong at neusoft.com (Yong.Fu) Date: Mon, 23 Mar 2020 03:10:50 +0000 Subject: [Starlingx-discuss] [TPM] TPM test documentation Message-ID: <9b0dddd21a82463fa244a6410259fe6b@neusoft.com> Hi all: I updated the relevant test documentation for TPM2.0 devices with tpm2-tools, https://wiki.openstack.org/wiki/StarlingX/Distro/tpm-verify If you have any questions and good suggestions, please contact me. Thank you Yong --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Mon Mar 23 08:10:05 2020 From: austin.sun at intel.com (Sun, Austin) Date: Mon, 23 Mar 2020 08:10:05 +0000 Subject: [Starlingx-discuss] [TPM] TPM test documentation In-Reply-To: <9b0dddd21a82463fa244a6410259fe6b@neusoft.com> References: <9b0dddd21a82463fa244a6410259fe6b@neusoft.com> Message-ID: Thanks a lot Fu yong for sharing. @all, kernel3.10 and kernel 4.18 have been tested based on these test steps. would you like to review this documents ? is this good enough for tpm driver ? Thanks. BR Austin Sun. From: Yong.Fu Sent: Monday, March 23, 2020 11:11 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [TPM] TPM test documentation Hi all: I updated the relevant test documentation for TPM2.0 devices with tpm2-tools, https://wiki.openstack.org/wiki/StarlingX/Distro/tpm-verify If you have any questions and good suggestions, please contact me. Thank you Yong --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon Mar 23 08:30:27 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 23 Mar 2020 04:30:27 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 153 - Failure! Message-ID: <679024016.1056.1584952228214.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 153 Status: Failure Timestamp: 20200323T081747Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200323T080227Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200323T080227Z DOCKER_BUILD_ID: jenkins-master-flock-20200323T080227Z-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/20200323T080227Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200323T080227Z/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 Mar 23 08:30:30 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 23 Mar 2020 04:30:30 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 55 - Still Failing! In-Reply-To: <1777218576.1047.1584875710660.JavaMail.javamailuser@localhost> References: <1777218576.1047.1584875710660.JavaMail.javamailuser@localhost> Message-ID: <274775540.1059.1584952231883.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 55 Status: Still Failing Timestamp: 20200323T080227Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200323T080227Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: false From yu.chengde at 99cloud.net Mon Mar 23 10:31:03 2020 From: yu.chengde at 99cloud.net (YuChengDe) Date: Mon, 23 Mar 2020 18:31:03 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?=5BOpenStack_Upgrade=5D_Built_the_m?= =?utf-8?q?aster_branch_of_stx-horizon?= Message-ID: Hi: We have built a stx-horizon image for Ussuri version Welcome to apply image into your system. If there is any problem during usage, please let me know. Many thanks. Note: Get the image from docker hub P.S.: tag = [git branch]-[based on python3 or python built environment]-[image created day] docker pull chantyu/stx-horizon:ussuri-python3-20200323 PROJECT_REPO= https://opendev.org/openstack/horizon.git PROJECT_REF= master BUILDER= loci -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From yu.chengde at 99cloud.net Mon Mar 23 10:54:34 2020 From: yu.chengde at 99cloud.net (YuChengDe) Date: Mon, 23 Mar 2020 18:54:34 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?=5BOpenStack_Upgrade=5DFailed_when_?= =?utf-8?q?build_StarlingX_docker_images?= In-Reply-To: Message-ID: Hi Don: Thank for your suggestion. After exclude the starlingx_dashboard from initial building, we built the stx-horizon successfully. For now, we have the 12/13 openstack image for Ussuri version. The last should be stx-glance. It needs python3-rbd package during building. However, we just have python-rbd package for our enviroment. Do you have any proposal for how to get the required python3-rbd? + yum -y --setopt=skip_missing_names_on_install=False install ceph-common libxml2 python3-rbd postgresql-libs ^[[0mLoaded plugins: fastestmirror, ovl Loading mirror speeds from cached hostfile * base: ftp.sjtu.edu.cn * extras: mirrors.ustc.edu.cn * updates: ftp.sjtu.edu.cn Package libxml2-2.9.1-6.el7_2.3.x86_64 already installed and latest version No package python3-rbd available. ^[[91mError: Not tolerating missing names on install, stopping. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 1 of 1. -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net 发件人:"Liu, ZhipengS" 发送日期:2020-03-14 10:30:32 收件人:"Penney, Don" ,YuChengDe ,"starlingx-discuss at lists.starlingx.io" 抄送人:"Somerville, Jim" 主题:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! We will try to do it further according to your proposal. Zhipeng From: Penney, Don Sent: 2020年3月14日 0:24 To: Liu, ZhipengS ; YuChengDe ; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I believe this has dependencies on a variety of StarlingX modules which are currently python2 only. You’ll probably need to exclude starlingx-dashboard for your initial builds, until all the required modules are available for python3. That said, it would be using only small components of these. So an initial effort to get python3 wheels for all the required modules may be small. Smaller than the effort to get these running as python3 on-host, certainly. From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Friday, March 13, 2020 12:20 PM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, We have finished 11/13 images build except for horizon and glance. For horizon, it needs starlingx-dashboard python3 whl. However, in our current build, we just build out starlingx-dashboard python2 whl. Do you have any proposal on how to get the required python3 whl. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 21:00 To: 'Liu, ZhipengS' ; 'Penney, Don' ; 'YuChengDe' ; 'starlingx-discuss at lists.starlingx.io' Cc: 'Somerville, Jim' Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, Chant and I already fixed this issue and other related dependent packages. We modified docker file and related script for wheel build, and rebuilt out all python3 wheels for the packages in stable-wheels.cfg. As for libvirt-python, we still use 4.7.0 version and rebuilt out python3 wheel currently. Will let you know the status after finishing all image build. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 0:06 To: 'Liu, ZhipengS' ; Penney, Don ; YuChengDe ; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images We also had below issue during build other service image. Looking in links: /tmp/wheels/ Collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) Collecting PyMySQL===0.9.3 Downloading PyMySQL-0.9.3-py2.py3-none-any.whl (47 kB) Processing /tmp/wheels/python_memcached-1.59-py2.py3-none-any.whl Collecting six===1.14.0 Downloading six-1.14.0-py2.py3-none-any.whl (10 kB) Collecting cffi===1.14.0 Downloading cffi-1.14.0-cp36-cp36m-manylinux1_x86_64.whl (399 kB) ERROR: Could not find a version that satisfies the requirement uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) (from versions: none) ERROR: No matching distribution found for uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) Actually, we get uWSGI-2.0.17.1-cp27-cp27mu-linux_x86_64.whl through the link in stable-config file. So far, not sure how many python3 packages we need. From: Liu, ZhipengS Sent: 2020年3月9日 23:44 To: Penney, Don ; YuChengDe ; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: Re: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! See my inline comments. From: Penney, Don Sent: 2020年3月9日 23:18 To: Liu, ZhipengS ; YuChengDe ; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I think building the openstack master branch will require moving the images to python3. This has implications to the base image, to how we build the base wheels tarball, and possibly to arguments passed to loci (as well as moving to a newer loci SHA). >> Yes, we have to set python3 = true to loci and also fix a small known bug. I believe Al started looking at this last week, but got pulled off to look at some other issues. From your reply, it sounds like maybe you’ve also done some of this? >> Yes When we explicitly add wheels to the tarball, we update the upper-constraints file to align with the module we’ve included. This would be why the build is looking for 4.7.0 here. There is an upper-constraints.txt file in the tarball itself which you can check. >> Yes, in our script, if we have 4.7.0 in stx repo, it will change the version to 4.7.0 from other versions specified in upper-constraints.txt The libvirt wheel building is python2 only, currently. So it would need to be built for python3 - if that’s possible for 4.7.0. If a newer version of libvirt-python is needed for python3 support, then it will need to be updated. I don’t know how big that effort will be. >> From code, libvirt-python 4.7.0 can support both python2 and python3, but in our code, we just add patch to let it build out python2 whl. >> libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, March 05, 2020 1:06 AM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Penney, We just used OpenStack master branch and upper-constraint file below https://raw.githubusercontent.com/openstack/requirements/master/upper-constraints.txt libvirt-python===5.10.0;python_version=='2.7' libvirt-python===6.0.0;python_version=='3.6' libvirt-python===6.0.0;python_version=='3.7' In nova setup.cfg. it adds python require info. python-requires = >=3.6 Then we built python3 related packages to the base image and rebuilt nova image to fix python3 issue. But there is still an error below. collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) ERROR: Could not find a version that satisfies the requirement libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) (from versions: none) ERROR: No matching distribution found for libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 From code, I saw that we already built libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl through a patch which Seems related to python2. cgcs-root/stx/integ/virt/libvirt-python/centos/meta_patches$ 0002-Build-python-wheel.patch It needs libvirt-python whl for python3, right? Do we have plan to upgrade libvirt-python to 6.0.0? Any comment? Thanks a lot! Zhipeng From: Penney, Don Sent: 2020年2月27日 0:25 To: YuChengDe ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I was able to successfully build stx-nova image in master with no changes. Do you have any customizations in your environment? From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 26, 2020 10:38 AM To: YuChengDe; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: not available URL: From zhipengs.liu at intel.com Mon Mar 23 13:49:37 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Mon, 23 Mar 2020 13:49:37 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. In-Reply-To: References: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314F6B2@SHSMSX104.ccr.corp.intel.com> , , Message-ID: Hi Joseph, I have updated my 2 patches, both tested on ipv4 and ipv6 setup. https://review.opendev.org/#/c/714034/ https://review.opendev.org/#/c/714038/ But still failed when deploy keystone, glance, cinder later. Common failure causes are found that need to bind host to :: instead of 0.0.0.0. Otherwise, it will only bind port to ipv4 address, which causes db connect failure or pod probe failure. After below changes, it can run until deploying cinder. 1)Change mariadb value.yaml conf: bind adress from 0.0.0.0 to :: 2) Change keystone value.yaml wsgi_keystone: | {{- $portInt := tuple "identity" "internal" "api" $ | include "helm-toolkit.endpoints.endpoint_port_lookup" }} Listen 0.0.0.0:{{ $portInt }} change to Listen :::{{ $portInt }} 3) Change glance value.yaml Conf.Default: add bind_host = "::" I have to check these services deploy one by one. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月19日 22:00 To: 'Richard, Joseph' Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Thanks Joseph! I guess it can go further. But keystone-db failed, which is the same as I met in my another ipv4 setup. I will build an EB based on a latest green daily build. The patch will come soon for your review. Thanks! Zhipeng From: Richard, Joseph > Sent: 2020年3月19日 21:20 To: Liu, ZhipengS > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Great! We definitely did support this before openstack-helm and openstack-helm-infra were upversioned around December. You should be able to control this in the rabbitmq helm plugin, so you can modify the behaviour based on ip version. https://github.com/starlingx/config/blob/master/sysinv/sysinv/sysinv/sysinv/helm/rabbitmq.py Once you get passed this point, does everything else come up as well? Does the app successfully apply? ________________________________ From: Liu, ZhipengS > Sent: Thursday, March 19, 2020 5:21 AM To: Richard, Joseph > Cc: starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, I fixed this issue now!! After check port status by sudo ip -all netns exec lsof -I, it shows that Rabbitmq only bind 15672 to ipv4. I add below changes and pass the rabbitmq deployment. conf: rabbitmq: management.listener.port: 15672 management.listener.ip: "::" Next step: I have to think how to submit this patch to support both ipv4 and ipv6 BTW, are you sure we passed this test before using OpenStack- train version? If not change helm chart, how can we pass it? Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月19日 10:07 To: Richard, Joseph >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, Below is my patch to make rabbitmq pod start in ipv6 setup.(This is not a formal patch) >From 99fc5aff8d70645c3130552789ea51d82cd287b2 Mon Sep 17 00:00:00 2001 From: Zhipeng Liu > Date: Thu, 19 Mar 2020 18:53:07 +0800 Subject: [PATCH] Fix rabbtimq pod not starting issue in IPv6 setup Signed-off-by: Zhipeng Liu > --- rabbitmq/templates/configmap-etc.yaml | 8 +++++++- rabbitmq/templates/job-cluster-wait.yaml | 2 ++ rabbitmq/templates/statefulset.yaml | 8 ++++++++ 3 files changed, 17 insertions(+), 1 deletion(-) diff --git a/rabbitmq/templates/configmap-etc.yaml b/rabbitmq/templates/configmap-etc.yaml index 87f25f5..18e2145 100644 --- a/rabbitmq/templates/configmap-etc.yaml +++ b/rabbitmq/templates/configmap-etc.yaml @@ -21,7 +21,8 @@ limitations under the License. {{- $_ := print "kubernetes.default.svc." $envAll.Values.endpoints.cluster_domain_suffix | set $envAll.Values.conf.rabbitmq.cluster_formation.k8s "host" -}} {{- end -}} -{{- $_ := print "0.0.0.0:" ( tuple "oslo_messaging" "internal" "amqp" . | include "helm-toolkit.endpoints.endpoint_port_lookup") | set $envAll.Values.conf.rabbitmq.listeners.tcp "1" -}} +{{- $_ := print ":::" ( tuple "oslo_messaging" "internal" "amqp" . | include "helm-toolkit.endpoints.endpoint_port_lookup") | set $envAll.Values.conf.rabbitmq.listeners.tcp "1" -}} + --- apiVersion: v1 @@ -33,4 +34,9 @@ data: {{ tuple "etc/_enabled_plugins.tpl" . | include "helm-toolkit.utils.template" | indent 4 }} rabbitmq.conf: | {{ include "rabbitmq.utils.to_rabbit_config" $envAll.Values.conf.rabbitmq | indent 4 }} + rabbitmq-env.conf: | + SERVER_ADDITIONAL_ERL_ARGS="+A 128 -kernel inetrc '/etc/rabbitmq/erl_inetrc' -proto_dist inet6_tcp" + CTL_ERL_ARGS="-proto_dist inet6_tcp" + erl_inetrc: | + {inet6, true}. {{ end }} diff --git a/rabbitmq/templates/job-cluster-wait.yaml b/rabbitmq/templates/job-cluster-wait.yaml index bf8e710..24a30a3 100644 --- a/rabbitmq/templates/job-cluster-wait.yaml +++ b/rabbitmq/templates/job-cluster-wait.yaml @@ -66,6 +66,8 @@ spec: env: - name: RABBITMQ_ADMIN_CONNECTION value: {{ tuple "oslo_messaging" "internal" "user" "http" $envAll | include "helm-toolkit.endpoints.authenticated_endpoint_uri_lookup" | quote }} + - name: RABBITMQ_CTL_ERL_ARGS + value: "-proto_dist inet6_tcp" - name: RABBIT_REPLICA_COUNT value: {{ $envAll.Values.pod.replicas.server | quote }} command: diff --git a/rabbitmq/templates/statefulset.yaml b/rabbitmq/templates/statefulset.yaml index 41dc198..64fc1cf 100644 --- a/rabbitmq/templates/statefulset.yaml +++ b/rabbitmq/templates/statefulset.yaml @@ -228,6 +228,14 @@ spec: mountPath: /etc/rabbitmq/rabbitmq.conf subPath: rabbitmq.conf readOnly: true + - name: rabbitmq-etc + mountPath: /etc/rabbitmq/rabbitmq-env.conf + subPath: rabbitmq-env.conf + readOnly: true + - name: rabbitmq-etc + mountPath: /etc/rabbitmq/erl_inetrc + subPath: erl_inetrc + readOnly: true volumes: - name: pod-tmp emptyDir: {} -- 2.7.4 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Mon Mar 23 14:18:52 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Mon, 23 Mar 2020 14:18:52 +0000 Subject: [Starlingx-discuss] [TPM] TPM test documentation In-Reply-To: References: <9b0dddd21a82463fa244a6410259fe6b@neusoft.com> Message-ID: Hi Austin - you mentioned last week on the community call that tpm testing is a risk for this upgrade. Does this update mean that risk is lowered/gone now? Thanks, Bill... From: Sun, Austin Sent: Monday, March 23, 2020 4:10 AM To: Yong.Fu ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [TPM] TPM test documentation Thanks a lot Fu yong for sharing. @all, kernel3.10 and kernel 4.18 have been tested based on these test steps. would you like to review this documents ? is this good enough for tpm driver ? Thanks. BR Austin Sun. From: Yong.Fu > Sent: Monday, March 23, 2020 11:11 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [TPM] TPM test documentation Hi all: I updated the relevant test documentation for TPM2.0 devices with tpm2-tools, https://wiki.openstack.org/wiki/StarlingX/Distro/tpm-verify If you have any questions and good suggestions, please contact me. Thank you Yong --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Mon Mar 23 14:28:11 2020 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 23 Mar 2020 07:28:11 -0700 Subject: [Starlingx-discuss] Stepping down from TSC In-Reply-To: References: Message-ID: <323b6e3f-9d6e-3c8f-03ee-0a5bee92145f@linux.intel.com> Dean, It was great working with you, you provided some great support and grounding to the team. Don't be a stranger! Sau! On 3/17/20 2:19 PM, Dean Troyer wrote: > Hi all, > > With the recent changes at Intel I find myself beginning the next > phase of my career and for the first time in 10 years it unfortunately > does not include OpenStack. I saw OpenStack grow from the marriage of > early Swift and barely-old-enough-to-walk Nova to a very mature and > successful platform. I met countless interesting and wonderful and > talented people along the way and learned more than I ever imagined I > would. > > It has also been a pleasure and an honor to be part of StarlingX from > almost the beginning of Intel's involvement, including being part of > forming the Technical Steering Committee. > > While the change of employer does not require me to do this I feel it > is in the best interest of the StarlingX TSC and the community to step > down effective immediately. I have already been noticeably absent for > a while and there will not be time for me to contribute in my new > role. I submitted the review to make this official a few minutes ago: > https://review.opendev.org/713541. > > Just for completeness I have also stepped away from OpenStackClient as > that project was folded into the OpenStack SDK led by Monty Taylor in > the last week or so. > > Thank you all and may our paths cross again for all of the right reasons. > > dt > From sgw at linux.intel.com Mon Mar 23 14:28:21 2020 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 23 Mar 2020 07:28:21 -0700 Subject: [Starlingx-discuss] Status Check on Layered Build Message-ID: Hi Scott, Frank: I am just getting back to work this morning and noticed many build failures looks like both in the monolithic and layered builds, can you provide some updates? Also, it looks like Layered build Sanity is still Red, any idea what's going on with that? Thanks Sau! From Ghada.Khalil at windriver.com Mon Mar 23 14:34:21 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 23 Mar 2020 14:34:21 +0000 Subject: [Starlingx-discuss] StarlingX Production Feasibility Discussion In-Reply-To: References: Message-ID: Hi Anirudh, I suggest you bring the topic to one of the community meetings, held on Wednesdays at 10:30am Eastern time. At the meeting, we can decide as a community whether to review your findings on the spot or schedule a follow-up meeting. Please add the topic to the community etherpad: https://etherpad.openstack.org/p/stx-status Regards, Ghada From: Anirudh Gupta [mailto:Anirudh.Gupta at hsc.com] Sent: Monday, March 23, 2020 8:18 AM To: Khalil, Ghada Cc: Harpreet Kaur; Amit Mahajan Subject: StarlingX Production Feasibility Discussion Hi Ghada, We have been using StarlingX as a solution for our Edge based deployments since Release 1 (2018.10) and also have reported many issues which we have faced time and again. Further we need to evaluate and understand StarlingX's feasibility in the Production Environment. Is there a possibility we can establish a call over web-ex to discuss further? If yes, please suggest a suitable date and time, so that we'll send an invite for the same. Regards Anirudh Gupta DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Mon Mar 23 17:33:24 2020 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 23 Mar 2020 10:33:24 -0700 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> <0bbec920-0556-15ab-5d4e-635b36a8cc89@windriver.com> <0492432b-cf8c-9d66-f08a-a4df0e826bd7@windriver.com> Message-ID: <600cbc76-2834-7d82-2344-e870d2e62564@linux.intel.com> On 3/19/20 5:33 PM, Chen, Haochuan Z wrote: > I prefer create a blank project with this link. Then I will upstream. > I pushed a change for this and will keep an eye on the Zuul status. Sau! > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > > *From:*Scott Little > *Sent:* Friday, March 20, 2020 1:43 AM > *To:* Chen, Haochuan Z ; Rowsell, Brent > > *Cc:* 'starlingx-discuss at lists.starlingx.io' > > *Subject:* Re: create a new project for ceph containerizaiton > > The URL https://review.opendev.org/starlingx/rook-storage-app is invalid > > Please provide a valid upstream url. > > Scott > > On 2020-03-17 7:54 p.m., Chen, Haochuan Z wrote: > > 3) The url and branch of any upstream git used to seed the content > for the new git. > > https://review.opendev.org/starlingx/rook-storage-app > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From nicolae.jascanu at intel.com Mon Mar 23 19:40:12 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Mon, 23 Mar 2020 19:40:12 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build - ISO 20200322 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-22 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200322T230000Z/outputs/iso/ ) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 ] AIO - Duplex [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Regards, STX Validation Team Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From scott.little at windriver.com Mon Mar 23 19:50:53 2020 From: scott.little at windriver.com (Scott Little) Date: Mon, 23 Mar 2020 15:50:53 -0400 Subject: [Starlingx-discuss] Status Check on Layered Build In-Reply-To: References: Message-ID: monolithic build failed due to disk space exhaustion on the root fs.  Tracked to stall docker images that I manually pruned.  The odd part was that I could see the jenkins logs where it stops and rm's the image successfully. I also looked into why the images were so big... 2.2 GB Yum cache.  I'm temped to use 'volume' to redirect guest:/var/cache/ to host:/localdisk.  I suspect this isn't the correct answer for everyone however, so it might be something cengn/jenkins must pass in via command line, rather than a generic fix we could commit to stx-tools. Flock layer build seems to relate to a kernel update on friday. Distro built the new kernel, but flock isn't downloading it. Yumdownloader isn't providing a valid url that curl can use to download it.  Still working on why... Scott On 2020-03-23 10:28 a.m., Saul Wold wrote: > > Hi Scott, Frank: > > I am just getting back to work this morning and noticed many build > failures looks like both in the monolithic and layered builds, can you > provide some updates? > > Also, it looks like Layered build Sanity is still Red, any idea what's > going on with that? > > Thanks >    Sau! From nicolae.jascanu at intel.com Mon Mar 23 19:59:42 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Mon, 23 Mar 2020 19:59:42 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build - ISO 20200320 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-20 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200320T170813Z/outputs/iso/ ) Status: RED We've got the same error for all controllers 23:21:12.373 INFO Logging into '192.168.200.76:22' as 'sysadmin'. 23:21:15.448 FAIL NoValidConnectionsError: [Errno None] Unable to connect to port 22 on 192.168.200.76 Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From sgw at linux.intel.com Mon Mar 23 22:45:24 2020 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 23 Mar 2020 15:45:24 -0700 Subject: [Starlingx-discuss] enable pbr version In-Reply-To: References: Message-ID: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> Hi Yipeng, I was out last week on vacation, so I am catching up now. I think you would have to investigate build-iso and associated scripts and tools to see if there is an awk, sed or some other command that is not parsing the extended version. I have not investigated this further, that's my initial assessment. Can you be more specific about what the error is or provide a log file of the build-iso process? Thanks for working on this project. Sau! On 3/19/20 12:21 AM, 何义鹏 wrote: > Hello Saul > > I'm Yipeng He from JITStack, and I'm taking over the tasks of PBR. > I encountered the following issue when trying to build iso: > It fails when the suffix of the version generated by the PBR tool ended > with number, for instance the building fails if the version id is > 2.999.9999.rc1.dev23, > and when I replaced it with 2.999.9999.rc1.dev, the ISO building was > successful. > I don't knwo why this happens, could please support and advice the > solution for this issue. > > > Yipeng.He > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From austin.sun at intel.com Tue Mar 24 00:42:25 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 24 Mar 2020 00:42:25 +0000 Subject: [Starlingx-discuss] [TPM] TPM test documentation In-Reply-To: References: <9b0dddd21a82463fa244a6410259fe6b@neusoft.com> Message-ID: Hi Bill: This is only TPM part, Integrity part is not tested yet. If anyone know if any specific HW is needed for Integrity and how to verify integrity function . Please share with us. Thanks. BR Austin Sun. From: Zvonar, Bill Sent: Monday, March 23, 2020 10:19 PM To: Sun, Austin ; Yong.Fu ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [TPM] TPM test documentation Hi Austin - you mentioned last week on the community call that tpm testing is a risk for this upgrade. Does this update mean that risk is lowered/gone now? Thanks, Bill... From: Sun, Austin > Sent: Monday, March 23, 2020 4:10 AM To: Yong.Fu >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [TPM] TPM test documentation Thanks a lot Fu yong for sharing. @all, kernel3.10 and kernel 4.18 have been tested based on these test steps. would you like to review this documents ? is this good enough for tpm driver ? Thanks. BR Austin Sun. From: Yong.Fu > Sent: Monday, March 23, 2020 11:11 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [TPM] TPM test documentation Hi all: I updated the relevant test documentation for TPM2.0 devices with tpm2-tools, https://wiki.openstack.org/wiki/StarlingX/Distro/tpm-verify If you have any questions and good suggestions, please contact me. Thank you Yong --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Tue Mar 24 04:22:10 2020 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 24 Mar 2020 04:22:10 +0000 Subject: [Starlingx-discuss] agenda for stx-distro-openstack project meeting - 03/24/2020 Message-ID: <6BB51019-F630-4332-AC18-D4DD998B72CA@intel.com> Agenda for 03/24/2020 meeting 1. Containerized OpenStack Services Upgrade - Kunpeng, Chant @99Cloud and Zhipeng @ Intel. 2. OpenStack clients and platform services - Yan @ Intel 3. LaunchPad [1] review - ALL [0]:upgrade plan in details: https://docs.google.com/spreadsheets/d/1BEHR7kFxbnN4h2IN0O5tJS7WJlYaET7eoUiDtOmsOtE/edit#gid=568723700 [1] OPEN LPs on distro.openstack: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack Join the meeting: https://zoom.us/j/342730236 Project Team Etherpad: https://etherpad.openstack.org/p/stx-distro-openstack-meetings Time: PST 6:00 AM, PRC 21:00 Regards, Yong From build.starlingx at gmail.com Tue Mar 24 08:29:44 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 24 Mar 2020 04:29:44 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 156 - Failure! Message-ID: <1321018691.1067.1585038585074.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 156 Status: Failure Timestamp: 20200324T081659Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200324T080229Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200324T080229Z DOCKER_BUILD_ID: jenkins-master-flock-20200324T080229Z-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/20200324T080229Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200324T080229Z/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 Tue Mar 24 08:29:47 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 24 Mar 2020 04:29:47 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 56 - Still Failing! In-Reply-To: <2013810928.1057.1584952229079.JavaMail.javamailuser@localhost> References: <2013810928.1057.1584952229079.JavaMail.javamailuser@localhost> Message-ID: <2010199334.1070.1585038588324.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 56 Status: Still Failing Timestamp: 20200324T080229Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200324T080229Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: false From austin.sun at intel.com Tue Mar 24 12:56:15 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 24 Mar 2020 12:56:15 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 3/25/2020 Message-ID: Hi All: Agenda for 3/25 meeting: - Ceph containerization (martin) - Kata remaining work (shuicheng) a) upgrade new kata for IPV6 https://storyboard.openstack.org/#!/story/2006145 . Task 39077 b) switch armada to run with containerd c) document for the kata. - PBR: (JITStack Wesley) issue: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008115.html - centos8 upgrade (shuicheng /Austin) ---- kernel on master patches rebase TPM test is done, Rt cyclictest is done , similar result as 3.10-rt . ---- python3 upgrade: NFV analysis result http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/007991.html after anlysis these services are doable for python3 engtools ----> https://review.opendev.org/#/c/714075/ platform-util ------> https://review.opendev.org/#/c/714085/ https://review.opendev.org/#/c/714072/ - open If have any other topic, feel free to add to https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. From zhipengs.liu at intel.com Tue Mar 24 13:33:00 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 24 Mar 2020 13:33:00 +0000 Subject: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images In-Reply-To: References: Message-ID: Hi Don, Could you help on this python3-rbd dependency issue? We have to fix this issue to finish cinder image build. Thanks a lot! Zhipeng From: YuChengDe Sent: 2020年3月23日 18:55 To: don.penney Cc: starlingx-discuss ; Somerville, Jim ; Liu, ZhipengS Subject: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don: Thank for your suggestion. After exclude the starlingx_dashboard from initial building, we built the stx-horizon successfully. For now, we have the 12/13 openstack image for Ussuri version. The last should be stx-glance. It needs python3-rbd package during building. However, we just have python-rbd package for our enviroment. Do you have any proposal for how to get the required python3-rbd? + yum -y --setopt=skip_missing_names_on_install=False install ceph-common libxml2 python3-rbd postgresql-libs ^[[0mLoaded plugins: fastestmirror, ovl Loading mirror speeds from cached hostfile * base: ftp.sjtu.edu.cn * extras: mirrors.ustc.edu.cn * updates: ftp.sjtu.edu.cn Package libxml2-2.9.1-6.el7_2.3.x86_64 already installed and latest version No package python3-rbd available. ^[[91mError: Not tolerating missing names on install, stopping. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 1 of 1. [http://mailhz.qiye.163.com/qiyeimage/logo/60511048/1576638602260.jpg] -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net 发件人:"Liu, ZhipengS" > 发送日期:2020-03-14 10:30:32 收件人:"Penney, Don" >,YuChengDe >,"starlingx-discuss at lists.starlingx.io" > 抄送人:"Somerville, Jim" > 主题:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! We will try to do it further according to your proposal. Zhipeng From: Penney, Don > Sent: 2020年3月14日 0:24 To: Liu, ZhipengS >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I believe this has dependencies on a variety of StarlingX modules which are currently python2 only. You’ll probably need to exclude starlingx-dashboard for your initial builds, until all the required modules are available for python3. That said, it would be using only small components of these. So an initial effort to get python3 wheels for all the required modules may be small. Smaller than the effort to get these running as python3 on-host, certainly. From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Friday, March 13, 2020 12:20 PM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, We have finished 11/13 images build except for horizon and glance. For horizon, it needs starlingx-dashboard python3 whl. However, in our current build, we just build out starlingx-dashboard python2 whl. Do you have any proposal on how to get the required python3 whl. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 21:00 To: 'Liu, ZhipengS' >; 'Penney, Don' >; 'YuChengDe' >; 'starlingx-discuss at lists.starlingx.io' > Cc: 'Somerville, Jim' > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, Chant and I already fixed this issue and other related dependent packages. We modified docker file and related script for wheel build, and rebuilt out all python3 wheels for the packages in stable-wheels.cfg. As for libvirt-python, we still use 4.7.0 version and rebuilt out python3 wheel currently. Will let you know the status after finishing all image build. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 0:06 To: 'Liu, ZhipengS' >; Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images We also had below issue during build other service image. Looking in links: /tmp/wheels/ Collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) Collecting PyMySQL===0.9.3 Downloading PyMySQL-0.9.3-py2.py3-none-any.whl (47 kB) Processing /tmp/wheels/python_memcached-1.59-py2.py3-none-any.whl Collecting six===1.14.0 Downloading six-1.14.0-py2.py3-none-any.whl (10 kB) Collecting cffi===1.14.0 Downloading cffi-1.14.0-cp36-cp36m-manylinux1_x86_64.whl (399 kB) ERROR: Could not find a version that satisfies the requirement uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) (from versions: none) ERROR: No matching distribution found for uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) Actually, we get uWSGI-2.0.17.1-cp27-cp27mu-linux_x86_64.whl through the link in stable-config file. So far, not sure how many python3 packages we need. From: Liu, ZhipengS > Sent: 2020年3月9日 23:44 To: Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: Re: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! See my inline comments. From: Penney, Don > Sent: 2020年3月9日 23:18 To: Liu, ZhipengS >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I think building the openstack master branch will require moving the images to python3. This has implications to the base image, to how we build the base wheels tarball, and possibly to arguments passed to loci (as well as moving to a newer loci SHA). >> Yes, we have to set python3 = true to loci and also fix a small known bug. I believe Al started looking at this last week, but got pulled off to look at some other issues. From your reply, it sounds like maybe you’ve also done some of this? >> Yes When we explicitly add wheels to the tarball, we update the upper-constraints file to align with the module we’ve included. This would be why the build is looking for 4.7.0 here. There is an upper-constraints.txt file in the tarball itself which you can check. >> Yes, in our script, if we have 4.7.0 in stx repo, it will change the version to 4.7.0 from other versions specified in upper-constraints.txt The libvirt wheel building is python2 only, currently. So it would need to be built for python3 - if that’s possible for 4.7.0. If a newer version of libvirt-python is needed for python3 support, then it will need to be updated. I don’t know how big that effort will be. >> From code, libvirt-python 4.7.0 can support both python2 and python3, but in our code, we just add patch to let it build out python2 whl. >> libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, March 05, 2020 1:06 AM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Penney, We just used OpenStack master branch and upper-constraint file below https://raw.githubusercontent.com/openstack/requirements/master/upper-constraints.txt libvirt-python===5.10.0;python_version=='2.7' libvirt-python===6.0.0;python_version=='3.6' libvirt-python===6.0.0;python_version=='3.7' In nova setup.cfg. it adds python require info. python-requires = >=3.6 Then we built python3 related packages to the base image and rebuilt nova image to fix python3 issue. But there is still an error below. collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) ERROR: Could not find a version that satisfies the requirement libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) (from versions: none) ERROR: No matching distribution found for libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 From code, I saw that we already built libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl through a patch which Seems related to python2. cgcs-root/stx/integ/virt/libvirt-python/centos/meta_patches$ 0002-Build-python-wheel.patch It needs libvirt-python whl for python3, right? Do we have plan to upgrade libvirt-python to 6.0.0? Any comment? Thanks a lot! Zhipeng From: Penney, Don > Sent: 2020年2月27日 0:25 To: YuChengDe >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I was able to successfully build stx-nova image in master with no changes. Do you have any customizations in your environment? From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 26, 2020 10:38 AM To: YuChengDe; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 [Image removed by sender.] -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From yipeng.he at jitstack.com Tue Mar 17 05:20:31 2020 From: yipeng.he at jitstack.com (=?utf-8?B?5L2V5LmJ6bmP?=) Date: Tue, 17 Mar 2020 13:20:31 +0800 Subject: [Starlingx-discuss] enable pbr version Message-ID: Hello Saul I'm Yipeng He from JITStack, and I'm taking over the tasks of PBR. I encountered the following issue when trying to build iso: It fails when the suffix of the version generated by the PBR tool ended with number, for instance the building fails if the version id is 2.999.9999.rc1.dev23, and when I replaced it with 2.999.9999.rc1.dev, the ISO building was successful. I don't knwo why this happens, could please support and advice the solution for this issue. Yipeng.He -------------- next part -------------- An HTML attachment was scrubbed... URL: From wesley.yang at jitstack.com Wed Mar 18 02:34:00 2020 From: wesley.yang at jitstack.com (wesley.yang at jitstack.com) Date: Wed, 18 Mar 2020 10:34:00 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSNOiBlbmFibGUgcGJyIHZlcnNp?= =?utf-8?q?on?= In-Reply-To: References: Message-ID: <06f701d5fccd$b0b75dc0$12261940$@jitstack.com>+A8AAF03B775A9BD6 Hi team It seems to prevent us from moving forward, please help to look into this case. Wesley Yang 发件人: 何义鹏 发送时间: 2020年3月17日 13:21 收件人: Saul Wold 抄送: 桂来军 ; 杨永金 ; 曹明晓 ; starlingx-discuss 主题: enable pbr version Hello Saul I'm Yipeng He from JITStack, and I'm taking over the tasks of PBR. I encountered the following issue when trying to build iso: It fails when the suffix of the version generated by the PBR tool ended with number, for instance the building fails if the version id is 2.999.9999.rc1.dev23, and when I replaced it with 2.999.9999.rc1.dev, the ISO building was successful. I don't knwo why this happens, could please support and advice the solution for this issue. Yipeng.He -------------- next part -------------- An HTML attachment was scrubbed... URL: From yipeng.he at jitstack.com Wed Mar 18 03:14:05 2020 From: yipeng.he at jitstack.com (=?utf-8?B?5L2V5LmJ6bmP?=) Date: Wed, 18 Mar 2020 11:14:05 +0800 Subject: [Starlingx-discuss] Fw:Change in starlingx/metal[master]: mtce:enable pbr version In-Reply-To: References: Message-ID:     ------------------ Original ------------------ From:  "Eric MacDonald (Code Review)" From austin.sun at intel.com Wed Mar 18 08:49:39 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 18 Mar 2020 08:49:39 +0000 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting Message-ID: Hi All: New Series of non-Openstack disto meeting invitation , Agenda for each will be sent individual email. * Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) * Call Details: o Zoom link: https://zoom.us/j/342730236 o 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 International numbers available: https://zoom.us/u/ed95sU7aQ * Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other 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: 5008 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT67013 1.jpg Type: image/jpeg Size: 7963 bytes Desc: ATT67013 1.jpg URL: From maryx.camp at intel.com Thu Mar 19 01:39:11 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Thu, 19 Mar 2020 01:39:11 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-03-18 Message-ID: Hello all, Here are this week's docs team meeting minutes. Join us if you have interest in StarlingX docs! We meet Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2020-03-18 * All -- reviews merged since last week: 4 * All -- bug status -- no change * All -- R4 target content: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.4.0&project_id=1046 * Windows Active Dir content -- Review available: https://review.opendev.org/#/c/712111/ ? AR Greg to update the review to incorporate latest Discuss emails from Jerry Sun and Teresa Ho. * Upgrade Kubernetes version -- Review available: https://review.opendev.org/#/c/712583/ ? http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007901.html (R4 new content) ? Greg added comments to the review. AR Mary email Angie Wang asking for more detail on the 3 patches (what's in them, how to build them). * Assignment of R4 doc tasks -- will be discussed in this weeks build meeting -- confirm ownership (KRIS) ? These stories have no assigned person: ? Bring to Community call as opens/need owners. Bill Z shared these links in the community call on 18Mar20. * https://storyboard.openstack.org/#!/story/2006770 (How to use Backup & Restore) * https://storyboard.openstack.org/#!/story/2007223 (update build guide w/ layered build info) * https://storyboard.openstack.org/#!/story/2007222 (update dist cloud bare metal install w/ redfish info) * https://storyboard.openstack.org/#!/story/2006588 (updates for Dist Cloud) * https://storyboard.openstack.org/#!/story/2006866 (Cert config & management guide) Don't send to Bill Z, this is an AR for Greg, see below. * All -- Changes needed? * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007847.html - possible Ceph storage updates needed? ? ceph is optional now. if you want to use it, you must use the new command. This doc is correct: https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/aio_simplex_install_kubernetes.html ? AR Mary update patch set. Greg sent additional language to add to section "Config controller-0" step 4. Step 6 same section is OK now. * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007891.html - asking for more detail on AIO Simplex install ? Greg emailed the author for more specifics about what he was doing. * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/007909.html - asking after OpenStack SSL cert config. We have a general cert stub page.... ? AR Mary create review using Greg's email text. * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/007918.html - possible build guide updates needed? [[didn't discuss yet]] * All -- Opens * Mary -- Need to update team page on the wiki: https://wiki.openstack.org/wiki/StarlingX/Docs_and_Infra ? TSC has to formally approve this election. Bruce says OK to update now. * All -- Wiki status ? Revisit planned migration of wiki content: lets close this out (see yellow). https://docs.google.com/spreadsheets/d/1UJjUttsWQRyauATrip0wKGIxSO7DvyetDKmPwvEIDaA/edit?usp=sharing ? Virtual Box wiki converted to RST file. Review available: https://review.opendev.org/#/c/711769/ ? AR Greg to review latest patch set and Bart's comments. Most likely we'll add Bart's steps as separate method in the NAT network guide. ? When this gets merged, the old wiki topic will be removed, noted as deprecated. Keep going through to get these last few topics migrated. * New reviews submitted: ? None this week. * New topics for us to document. Both are coming from Intel field teams supporting customers (brucej) ? Mary emailed Ghada on 17Mar20, asking for folks to contact for help on these topics: * High availability and failover mechanisms for applications and for SM. [SM we may have in training in wiki, but HA and failover need more info (for industrial customers) Good idea to document best practices how to build these. ] * Networking - how to bridge / combine K8S and OpenStack networks for applications [Need to capture this info, but unclear who could provide this info. Need diagrams to show how it works externally.] * Kris: here are two items she didn't have time to get to during her time on the STX project, might be interesting for us to dig into. ? Suggestion to revisit the R4 content list/plan (stories) to see if anything was overlooked OR features have been added/removed? Don't want to be rigidly attached to the list. Do the real users have these concerns? How to prioritize? Get input from users via survey or another means, question on STX discuss. What are the undocumented areas? Someone who reps the doc team could attend each sub-team meeting to ask for docs feedback, gaps, areas of struggle, etc. Couple of questions, enlist key folks to bring it up. ? Investigate if there are any analytics on the docs site, to see what's clicked most, what are folks searching for (incoming from Google). * Mary: I'm sending my "STX tasks cheatsheet" to new STX folks (Sharath and Poornima) as a reference. Bruce & Greg confirmed that a browser is required to view the HTML output after the tox -e docs command and to view the Zuul docs preview site. * All -- Ongoing tasks: * STX in a box: (https://storyboard.openstack.org/#!/story/2006622) ? Draft in review https://review.opendev.org/#/c/692202/ ? During meeting we discussed this idea and agreed it should be put on hold. Scott Little & Greg tried this, but were unable to make progress. ? AR Kris to ping Sai and let him know the status. Thank him for his work, we're unable to close on this now. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yipeng_he1 at 163.com Thu Mar 19 01:51:21 2020 From: yipeng_he1 at 163.com (yipeng.he) Date: Thu, 19 Mar 2020 09:51:21 +0800 (CST) Subject: [Starlingx-discuss] enable pbr version Message-ID: <45819964.1acd.170f07ce398.Coremail.yipeng_he1@163.com> Hello Saul I'm Yipeng He from JITStack, and I'm taking over the tasks of PBR. I encountered the following issue when trying to build iso: It fails when the suffix of the version generated by the PBR tool ended with number, for instance the building fails if the version id is 2.999.9999.rc1.dev23, and when I replaced it with 2.999.9999.rc1.dev, the ISO building was successful. I don't knwo why this happens, could please support and advice the solution for this issue. Yipeng.He -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Thu Mar 19 02:07:19 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 19 Mar 2020 02:07:19 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. In-Reply-To: References: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314F6B2@SHSMSX104.ccr.corp.intel.com> , , Message-ID: Hi Joseph, Below is my patch to make rabbitmq pod start in ipv6 setup.(This is not a formal patch) From 99fc5aff8d70645c3130552789ea51d82cd287b2 Mon Sep 17 00:00:00 2001 From: Zhipeng Liu Date: Thu, 19 Mar 2020 18:53:07 +0800 Subject: [PATCH] Fix rabbtimq pod not starting issue in IPv6 setup Signed-off-by: Zhipeng Liu --- rabbitmq/templates/configmap-etc.yaml | 8 +++++++- rabbitmq/templates/job-cluster-wait.yaml | 2 ++ rabbitmq/templates/statefulset.yaml | 8 ++++++++ 3 files changed, 17 insertions(+), 1 deletion(-) diff --git a/rabbitmq/templates/configmap-etc.yaml b/rabbitmq/templates/configmap-etc.yaml index 87f25f5..18e2145 100644 --- a/rabbitmq/templates/configmap-etc.yaml +++ b/rabbitmq/templates/configmap-etc.yaml @@ -21,7 +21,8 @@ limitations under the License. {{- $_ := print "kubernetes.default.svc." $envAll.Values.endpoints.cluster_domain_suffix | set $envAll.Values.conf.rabbitmq.cluster_formation.k8s "host" -}} {{- end -}} -{{- $_ := print "0.0.0.0:" ( tuple "oslo_messaging" "internal" "amqp" . | include "helm-toolkit.endpoints.endpoint_port_lookup") | set $envAll.Values.conf.rabbitmq.listeners.tcp "1" -}} +{{- $_ := print ":::" ( tuple "oslo_messaging" "internal" "amqp" . | include "helm-toolkit.endpoints.endpoint_port_lookup") | set $envAll.Values.conf.rabbitmq.listeners.tcp "1" -}} + --- apiVersion: v1 @@ -33,4 +34,9 @@ data: {{ tuple "etc/_enabled_plugins.tpl" . | include "helm-toolkit.utils.template" | indent 4 }} rabbitmq.conf: | {{ include "rabbitmq.utils.to_rabbit_config" $envAll.Values.conf.rabbitmq | indent 4 }} + rabbitmq-env.conf: | + SERVER_ADDITIONAL_ERL_ARGS="+A 128 -kernel inetrc '/etc/rabbitmq/erl_inetrc' -proto_dist inet6_tcp" + CTL_ERL_ARGS="-proto_dist inet6_tcp" + erl_inetrc: | + {inet6, true}. {{ end }} diff --git a/rabbitmq/templates/job-cluster-wait.yaml b/rabbitmq/templates/job-cluster-wait.yaml index bf8e710..24a30a3 100644 --- a/rabbitmq/templates/job-cluster-wait.yaml +++ b/rabbitmq/templates/job-cluster-wait.yaml @@ -66,6 +66,8 @@ spec: env: - name: RABBITMQ_ADMIN_CONNECTION value: {{ tuple "oslo_messaging" "internal" "user" "http" $envAll | include "helm-toolkit.endpoints.authenticated_endpoint_uri_lookup" | quote }} + - name: RABBITMQ_CTL_ERL_ARGS + value: "-proto_dist inet6_tcp" - name: RABBIT_REPLICA_COUNT value: {{ $envAll.Values.pod.replicas.server | quote }} command: diff --git a/rabbitmq/templates/statefulset.yaml b/rabbitmq/templates/statefulset.yaml index 41dc198..64fc1cf 100644 --- a/rabbitmq/templates/statefulset.yaml +++ b/rabbitmq/templates/statefulset.yaml @@ -228,6 +228,14 @@ spec: mountPath: /etc/rabbitmq/rabbitmq.conf subPath: rabbitmq.conf readOnly: true + - name: rabbitmq-etc + mountPath: /etc/rabbitmq/rabbitmq-env.conf + subPath: rabbitmq-env.conf + readOnly: true + - name: rabbitmq-etc + mountPath: /etc/rabbitmq/erl_inetrc + subPath: erl_inetrc + readOnly: true volumes: - name: pod-tmp emptyDir: {} -- 2.7.4 From: Richard, Joseph Sent: 2020年3月19日 0:35 To: Liu, ZhipengS ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Have you tried changing envAll.Values.conf.rabbitmq.listeners.tcp? I'd need to see the changes you've made to get rabbitmq running to provide any other ideas. ________________________________ From: Liu, ZhipengS > Sent: Wednesday, March 18, 2020 10:53 AM To: Richard, Joseph >; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, I will submit one patch for helm chart change later after fixing current issue. BTW, Seems we have no rabbitmqadmin in rabbitmq pod but rabbitmq-cluster-wait job. I have done below test and have some conclusion now. 1) Rabbtimq already started normally, and start listen on [::]:5672/15672/25672 port 2) It seems 15672 port access blocked for ipv6 (5672 is OK). In ipv4 simplex setup, same test below are all OK. Any idea? rabbitmq at osh-openstack-rabbitmq-rabbitmq-0:/usr/local$ rabbitmqctl status Status of node rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local ... Runtime OS PID: 303 OS: Linux Uptime (seconds): 6752 RabbitMQ version: 3.8.3 Node name: rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local Erlang configuration: Erlang/OTP 22 [erts-10.7] [source] [64-bit] [smp:6:6] [ds:6:6:10] [async-threads:128] Erlang processes: 426 used, 1048576 limit Scheduler run queue: 1 Cluster heartbeat timeout (net_ticktime): 60 Plugins Enabled plugin file: /etc/rabbitmq/enabled_plugins Enabled plugins: * rabbitmq_management * rabbitmq_web_dispatch * rabbitmq_peer_discovery_k8s * rabbitmq_peer_discovery_common * rabbitmq_management_agent * amqp_client * cowboy * cowlib Totals Connection count: 0 Queue count: 0 Virtual host count: 0 Listeners Interface: [::], port: 25672, protocol: clustering, purpose: inter-node and CLI tool communication Interface: [::], port: 5672, protocol: amqp, purpose: AMQP 0-9-1 and AMQP 1.0 Interface: [::], port: 15672, protocol: http, purpose: HTTP API controller-0:~$ wget http://rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local:15672/ --2020-03-18 14:37:45-- http://rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local:15672/ Resolving osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local (osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local)... fd03::1e6d:6abf Connecting to osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local (osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local)|fd03::1e6d:6abf|:15672... failed: Connection refused. //same as we see in the log of Rabbitmq-cluster-wait pod. controller-0:~$ wget http://rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local:5672/ --2020-03-18 14:37:53-- http://rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local:5672/ Resolving osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local (osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local)... fd03::1e6d:6abf Connecting to osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local (osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local)|fd03::1e6d:6abf|:5672... connected. controller-0:~$ wget http://[fd03::1e6d:6abf]:15672/ --2020-03-18 14:38:56-- http://[fd03::1e6d:6abf]:15672/ Connecting to [fd03::1e6d:6abf]:15672... failed: Connection refused. controller-0:~$ wget http://[fd03::1e6d:6abf]:5672/ --2020-03-18 14:39:00-- http://[fd03::1e6d:6abf]:5672/ Connecting to [fd03::1e6d:6abf]:5672... connected. Thanks! Zhipeng From: Richard, Joseph > Sent: 2020年3月18日 21:48 To: Liu, ZhipengS >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Can you open a review with the change you made to fix the nxdomain issue? Is rabbitmqadmin able to connect if you run it from within osh-openstack-rabbitmq-rabbitmq-0? I see from your logs that the osh-openstack-rabbitmq-cluster-wait is from before rabbitmq was running. Can you see anything in the rabbitmq when the cluster-wait pod fails? ________________________________ From: Liu, ZhipengS > Sent: Tuesday, March 17, 2020 9:46 PM To: Richard, Joseph >; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, After did some changes in rabbitmq helm chart, I have fixed nxdomain issue in my ipv6 simplex setup. Below two pods can run up. osh-openstack-rabbitmq-cluster-wait-9rw6p 1/1 Running 0 17m osh-openstack-rabbitmq-rabbitmq-0 1/1 Running 0 17m However, still have another issue. In pod osh-openstack-rabbitmq-cluster-wait, it will use rabbitmqadmin to connect rabbitmq, but always get error. ++ active_rabbit_nodes 2020-03-17T10:31:12.124589385Z stderr F ++ wc -w 2020-03-17T10:31:12.134367271Z stderr F ++ rabbitmqadmin_authed list nodes -f bash 2020-03-17T10:31:12.134427089Z stderr F ++ set +x 2020-03-17T10:31:12.179073378Z stderr F Traceback (most recent call last): 2020-03-17T10:31:12.179644557Z stderr F error: [Errno 111] Connection refused 2020-03-17T10:31:12.17964969Z stderr F *** Could not connect: [Errno 111] Connection refused In the log of rabbitmq node, I can see below. 2020-03-17T15:40:27.762196613Z stdout F 2020-03-17 15:40:27.761 [info] <0.495.0> started TCP listener on [::]:5672 2020-03-17T15:40:27.807886117Z stdout F 2020-03-17 15:40:27.807 [info] <0.552.0> Management plugin: HTTP (non-TLS) listener started on port 15672 2020-03-17T15:40:27.895551288Z stdout F 2020-03-17 15:40:27.895 [info] <0.8.0> Server startup complete; 5 plugins started. 2020-03-17T15:40:27.895555144Z stdout F * rabbitmq_peer_discovery_k8s 2020-03-17T15:40:27.895557288Z stdout F * rabbitmq_management 2020-03-17T15:40:27.895559593Z stdout F * rabbitmq_management_agent 2020-03-17T15:40:27.895561807Z stdout F * rabbitmq_web_dispatch 2020-03-17T15:40:27.895564619Z stdout F * rabbitmq_peer_discovery_common I’m still working on this issue. Any comment or proposal, thanks! Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月16日 16:57 To: 'Richard, Joseph' >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, I tried many methods, but still not fixed the issue. I found there are some related issued fixed in upstream, but not yet merged to formal release. I’m discussing with them. Do you have any comment? https://github.com/rabbitmq/rabbitmq-peer-discovery-k8s/issues/55 Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月12日 9:53 To: 'Richard, Joseph' >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, Thank you so much! 😊 I will work further based on your provided clue. Best Regards, Zhipeng From: Richard, Joseph > Sent: 2020年3月12日 5:06 To: Liu, ZhipengS >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. I see a similar issue online here: https://groups.google.com/forum/#!topic/rabbitmq-users/9ir1WK-nYBA [http://www.google.com/images/icons/product/groups-128.png] epmd fails to start in IPv6 environment Posted 7/15/19 9:43 PM, 12 messages groups.google.com I expect that you are going to have to update rabbmitmq docker images to 3.7.16(currently 3.7.13), and then modify the helm plugin to pass in these values when using ipv6: SERVER_ADDITIONAL_ERL_ARGS='-proto_dist inet6_tcp' CTL_ERL_ARGS='-proto_dist inet6_tcp' Not sure if this is possible right now, or if you will need to modify openstack-helm-infra/rabbitmq in order to be able to pass these environment variables in. ________________________________ From: Liu, ZhipengS > Sent: Thursday, February 27, 2020 8:00 AM To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi all, For below LP IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status" https://bugs.launchpad.net/starlingx/+bug/1859641 I provided a patch which can fix the known issue in LP. However, it still failed later when starting rabbitmq pod. controller-0:~$ kubectl -n openstack get po NAME READY STATUS RESTARTS AGE ingress-c74489c96-jsb7n 1/1 Running 0 17h ingress-error-pages-5889bfcf6c-h8kl6 1/1 Running 0 17h mariadb-ingress-b5cd65f4b-sq46c 1/1 Running 0 17h mariadb-ingress-error-pages-6d8b79b74f-9zmpc 1/1 Running 0 17h mariadb-server-0 1/1 Running 0 17h osh-openstack-memcached-memcached-545668bdbd-9jkv2 1/1 Running 0 17h osh-openstack-rabbitmq-cluster-wait-wbnwp 0/1 Init:0/2 0 17h osh-openstack-rabbitmq-rabbitmq-0 0/1 CrashLoopBackOff 207 17h There are below error logs 2020-02-26T07:43:36.451103975Z stderr F ++ echo osh-openstack-rabbitmq-rabbitmq-0 2020-02-26T07:43:36.45142814Z stderr F ++ awk -F - '{print $NF}' 2020-02-26T07:43:36.454160452Z stderr F + POD_INCREMENT=0 2020-02-26T07:43:36.454757022Z stderr F + '[' 0 -eq 0 ']' 2020-02-26T07:43:36.454795721Z stderr F + exec rabbitmq-server 2020-02-26T07:43:36.849021551Z stdout F ERROR: epmd error for host osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local: nxdomain (non-existing domain) In /etc/hosts file below, I just found localhost4, no localhost6. Is it expected? I added below line manually after the line of 127.0.0.1. However, it didn’t work☹ ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 # HEADER: This file was autogenerated at 2020-02-26 09:00:35 +0000 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 fd01::1 controller 169.254.202.1 pxecontroller fd00::3 oamcontroller fd01::4 controller-platform-nfs fd01::3 controller-1 fd01::2 controller-0 fd02::3 controller-1-cluster-host fd02::2 controller-0-cluster-host fd01::e8b6:66fe storage-0 I saw that in ./stx-puppet/puppet-manifests/src/modules/platform/manifests/config.pp:215 class platform::config::hosts inherits ::platform::config::params { # The localhost should resolve to the IPv4 loopback address only, therefore # ensure the IPv6 address is removed from configured hosts resources { 'host': purge => true } $localhost = { 'localhost' => { ip => '127.0.0.1', host_aliases => ['localhost.localdomain', 'localhost4', 'localhost4.localdomain4'] }, } $merged_hosts = merge($localhost, $hosts) create_resources('host', $merged_hosts, {}) } Any one can give some help? Thanks! Zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Thu Mar 19 09:18:08 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 19 Mar 2020 09:18:08 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. In-Reply-To: References: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314F6B2@SHSMSX104.ccr.corp.intel.com> , , Message-ID: Hi Joseph, I fixed this issue now!! After check port status by sudo ip -all netns exec lsof -I, it shows that Rabbitmq only bind 15672 to ipv4. I add below changes and pass the rabbitmq deployment. conf: rabbitmq: management.listener.port: 15672 management.listener.ip: "::" Next step: I have to think how to submit this patch to support both ipv4 and ipv6 BTW, are you sure we passed this test before using OpenStack- train version? If not change helm chart, how can we pass it? Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月19日 10:07 To: Richard, Joseph ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, Below is my patch to make rabbitmq pod start in ipv6 setup.(This is not a formal patch) From 99fc5aff8d70645c3130552789ea51d82cd287b2 Mon Sep 17 00:00:00 2001 From: Zhipeng Liu > Date: Thu, 19 Mar 2020 18:53:07 +0800 Subject: [PATCH] Fix rabbtimq pod not starting issue in IPv6 setup Signed-off-by: Zhipeng Liu > --- rabbitmq/templates/configmap-etc.yaml | 8 +++++++- rabbitmq/templates/job-cluster-wait.yaml | 2 ++ rabbitmq/templates/statefulset.yaml | 8 ++++++++ 3 files changed, 17 insertions(+), 1 deletion(-) diff --git a/rabbitmq/templates/configmap-etc.yaml b/rabbitmq/templates/configmap-etc.yaml index 87f25f5..18e2145 100644 --- a/rabbitmq/templates/configmap-etc.yaml +++ b/rabbitmq/templates/configmap-etc.yaml @@ -21,7 +21,8 @@ limitations under the License. {{- $_ := print "kubernetes.default.svc." $envAll.Values.endpoints.cluster_domain_suffix | set $envAll.Values.conf.rabbitmq.cluster_formation.k8s "host" -}} {{- end -}} -{{- $_ := print "0.0.0.0:" ( tuple "oslo_messaging" "internal" "amqp" . | include "helm-toolkit.endpoints.endpoint_port_lookup") | set $envAll.Values.conf.rabbitmq.listeners.tcp "1" -}} +{{- $_ := print ":::" ( tuple "oslo_messaging" "internal" "amqp" . | include "helm-toolkit.endpoints.endpoint_port_lookup") | set $envAll.Values.conf.rabbitmq.listeners.tcp "1" -}} + --- apiVersion: v1 @@ -33,4 +34,9 @@ data: {{ tuple "etc/_enabled_plugins.tpl" . | include "helm-toolkit.utils.template" | indent 4 }} rabbitmq.conf: | {{ include "rabbitmq.utils.to_rabbit_config" $envAll.Values.conf.rabbitmq | indent 4 }} + rabbitmq-env.conf: | + SERVER_ADDITIONAL_ERL_ARGS="+A 128 -kernel inetrc '/etc/rabbitmq/erl_inetrc' -proto_dist inet6_tcp" + CTL_ERL_ARGS="-proto_dist inet6_tcp" + erl_inetrc: | + {inet6, true}. {{ end }} diff --git a/rabbitmq/templates/job-cluster-wait.yaml b/rabbitmq/templates/job-cluster-wait.yaml index bf8e710..24a30a3 100644 --- a/rabbitmq/templates/job-cluster-wait.yaml +++ b/rabbitmq/templates/job-cluster-wait.yaml @@ -66,6 +66,8 @@ spec: env: - name: RABBITMQ_ADMIN_CONNECTION value: {{ tuple "oslo_messaging" "internal" "user" "http" $envAll | include "helm-toolkit.endpoints.authenticated_endpoint_uri_lookup" | quote }} + - name: RABBITMQ_CTL_ERL_ARGS + value: "-proto_dist inet6_tcp" - name: RABBIT_REPLICA_COUNT value: {{ $envAll.Values.pod.replicas.server | quote }} command: diff --git a/rabbitmq/templates/statefulset.yaml b/rabbitmq/templates/statefulset.yaml index 41dc198..64fc1cf 100644 --- a/rabbitmq/templates/statefulset.yaml +++ b/rabbitmq/templates/statefulset.yaml @@ -228,6 +228,14 @@ spec: mountPath: /etc/rabbitmq/rabbitmq.conf subPath: rabbitmq.conf readOnly: true + - name: rabbitmq-etc + mountPath: /etc/rabbitmq/rabbitmq-env.conf + subPath: rabbitmq-env.conf + readOnly: true + - name: rabbitmq-etc + mountPath: /etc/rabbitmq/erl_inetrc + subPath: erl_inetrc + readOnly: true volumes: - name: pod-tmp emptyDir: {} -- 2.7.4 From: Richard, Joseph > Sent: 2020年3月19日 0:35 To: Liu, ZhipengS >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Have you tried changing envAll.Values.conf.rabbitmq.listeners.tcp? I'd need to see the changes you've made to get rabbitmq running to provide any other ideas. ________________________________ From: Liu, ZhipengS > Sent: Wednesday, March 18, 2020 10:53 AM To: Richard, Joseph >; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, I will submit one patch for helm chart change later after fixing current issue. BTW, Seems we have no rabbitmqadmin in rabbitmq pod but rabbitmq-cluster-wait job. I have done below test and have some conclusion now. 1) Rabbtimq already started normally, and start listen on [::]:5672/15672/25672 port 2) It seems 15672 port access blocked for ipv6 (5672 is OK). In ipv4 simplex setup, same test below are all OK. Any idea? rabbitmq at osh-openstack-rabbitmq-rabbitmq-0:/usr/local$ rabbitmqctl status Status of node rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local ... Runtime OS PID: 303 OS: Linux Uptime (seconds): 6752 RabbitMQ version: 3.8.3 Node name: rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local Erlang configuration: Erlang/OTP 22 [erts-10.7] [source] [64-bit] [smp:6:6] [ds:6:6:10] [async-threads:128] Erlang processes: 426 used, 1048576 limit Scheduler run queue: 1 Cluster heartbeat timeout (net_ticktime): 60 Plugins Enabled plugin file: /etc/rabbitmq/enabled_plugins Enabled plugins: * rabbitmq_management * rabbitmq_web_dispatch * rabbitmq_peer_discovery_k8s * rabbitmq_peer_discovery_common * rabbitmq_management_agent * amqp_client * cowboy * cowlib Totals Connection count: 0 Queue count: 0 Virtual host count: 0 Listeners Interface: [::], port: 25672, protocol: clustering, purpose: inter-node and CLI tool communication Interface: [::], port: 5672, protocol: amqp, purpose: AMQP 0-9-1 and AMQP 1.0 Interface: [::], port: 15672, protocol: http, purpose: HTTP API controller-0:~$ wget http://rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local:15672/ --2020-03-18 14:37:45-- http://rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local:15672/ Resolving osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local (osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local)... fd03::1e6d:6abf Connecting to osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local (osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local)|fd03::1e6d:6abf|:15672... failed: Connection refused. //same as we see in the log of Rabbitmq-cluster-wait pod. controller-0:~$ wget http://rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local:5672/ --2020-03-18 14:37:53-- http://rabbit at osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local:5672/ Resolving osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local (osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local)... fd03::1e6d:6abf Connecting to osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local (osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local)|fd03::1e6d:6abf|:5672... connected. controller-0:~$ wget http://[fd03::1e6d:6abf]:15672/ --2020-03-18 14:38:56-- http://[fd03::1e6d:6abf]:15672/ Connecting to [fd03::1e6d:6abf]:15672... failed: Connection refused. controller-0:~$ wget http://[fd03::1e6d:6abf]:5672/ --2020-03-18 14:39:00-- http://[fd03::1e6d:6abf]:5672/ Connecting to [fd03::1e6d:6abf]:5672... connected. Thanks! Zhipeng From: Richard, Joseph > Sent: 2020年3月18日 21:48 To: Liu, ZhipengS >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Can you open a review with the change you made to fix the nxdomain issue? Is rabbitmqadmin able to connect if you run it from within osh-openstack-rabbitmq-rabbitmq-0? I see from your logs that the osh-openstack-rabbitmq-cluster-wait is from before rabbitmq was running. Can you see anything in the rabbitmq when the cluster-wait pod fails? ________________________________ From: Liu, ZhipengS > Sent: Tuesday, March 17, 2020 9:46 PM To: Richard, Joseph >; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, After did some changes in rabbitmq helm chart, I have fixed nxdomain issue in my ipv6 simplex setup. Below two pods can run up. osh-openstack-rabbitmq-cluster-wait-9rw6p 1/1 Running 0 17m osh-openstack-rabbitmq-rabbitmq-0 1/1 Running 0 17m However, still have another issue. In pod osh-openstack-rabbitmq-cluster-wait, it will use rabbitmqadmin to connect rabbitmq, but always get error. ++ active_rabbit_nodes 2020-03-17T10:31:12.124589385Z stderr F ++ wc -w 2020-03-17T10:31:12.134367271Z stderr F ++ rabbitmqadmin_authed list nodes -f bash 2020-03-17T10:31:12.134427089Z stderr F ++ set +x 2020-03-17T10:31:12.179073378Z stderr F Traceback (most recent call last): 2020-03-17T10:31:12.179644557Z stderr F error: [Errno 111] Connection refused 2020-03-17T10:31:12.17964969Z stderr F *** Could not connect: [Errno 111] Connection refused In the log of rabbitmq node, I can see below. 2020-03-17T15:40:27.762196613Z stdout F 2020-03-17 15:40:27.761 [info] <0.495.0> started TCP listener on [::]:5672 2020-03-17T15:40:27.807886117Z stdout F 2020-03-17 15:40:27.807 [info] <0.552.0> Management plugin: HTTP (non-TLS) listener started on port 15672 2020-03-17T15:40:27.895551288Z stdout F 2020-03-17 15:40:27.895 [info] <0.8.0> Server startup complete; 5 plugins started. 2020-03-17T15:40:27.895555144Z stdout F * rabbitmq_peer_discovery_k8s 2020-03-17T15:40:27.895557288Z stdout F * rabbitmq_management 2020-03-17T15:40:27.895559593Z stdout F * rabbitmq_management_agent 2020-03-17T15:40:27.895561807Z stdout F * rabbitmq_web_dispatch 2020-03-17T15:40:27.895564619Z stdout F * rabbitmq_peer_discovery_common I’m still working on this issue. Any comment or proposal, thanks! Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月16日 16:57 To: 'Richard, Joseph' >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, I tried many methods, but still not fixed the issue. I found there are some related issued fixed in upstream, but not yet merged to formal release. I’m discussing with them. Do you have any comment? https://github.com/rabbitmq/rabbitmq-peer-discovery-k8s/issues/55 Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月12日 9:53 To: 'Richard, Joseph' >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, Thank you so much! 😊 I will work further based on your provided clue. Best Regards, Zhipeng From: Richard, Joseph > Sent: 2020年3月12日 5:06 To: Liu, ZhipengS >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. I see a similar issue online here: https://groups.google.com/forum/#!topic/rabbitmq-users/9ir1WK-nYBA [http://www.google.com/images/icons/product/groups-128.png] epmd fails to start in IPv6 environment Posted 7/15/19 9:43 PM, 12 messages groups.google.com I expect that you are going to have to update rabbmitmq docker images to 3.7.16(currently 3.7.13), and then modify the helm plugin to pass in these values when using ipv6: SERVER_ADDITIONAL_ERL_ARGS='-proto_dist inet6_tcp' CTL_ERL_ARGS='-proto_dist inet6_tcp' Not sure if this is possible right now, or if you will need to modify openstack-helm-infra/rabbitmq in order to be able to pass these environment variables in. ________________________________ From: Liu, ZhipengS > Sent: Thursday, February 27, 2020 8:00 AM To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi all, For below LP IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status" https://bugs.launchpad.net/starlingx/+bug/1859641 I provided a patch which can fix the known issue in LP. However, it still failed later when starting rabbitmq pod. controller-0:~$ kubectl -n openstack get po NAME READY STATUS RESTARTS AGE ingress-c74489c96-jsb7n 1/1 Running 0 17h ingress-error-pages-5889bfcf6c-h8kl6 1/1 Running 0 17h mariadb-ingress-b5cd65f4b-sq46c 1/1 Running 0 17h mariadb-ingress-error-pages-6d8b79b74f-9zmpc 1/1 Running 0 17h mariadb-server-0 1/1 Running 0 17h osh-openstack-memcached-memcached-545668bdbd-9jkv2 1/1 Running 0 17h osh-openstack-rabbitmq-cluster-wait-wbnwp 0/1 Init:0/2 0 17h osh-openstack-rabbitmq-rabbitmq-0 0/1 CrashLoopBackOff 207 17h There are below error logs 2020-02-26T07:43:36.451103975Z stderr F ++ echo osh-openstack-rabbitmq-rabbitmq-0 2020-02-26T07:43:36.45142814Z stderr F ++ awk -F - '{print $NF}' 2020-02-26T07:43:36.454160452Z stderr F + POD_INCREMENT=0 2020-02-26T07:43:36.454757022Z stderr F + '[' 0 -eq 0 ']' 2020-02-26T07:43:36.454795721Z stderr F + exec rabbitmq-server 2020-02-26T07:43:36.849021551Z stdout F ERROR: epmd error for host osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local: nxdomain (non-existing domain) In /etc/hosts file below, I just found localhost4, no localhost6. Is it expected? I added below line manually after the line of 127.0.0.1. However, it didn’t work☹ ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 # HEADER: This file was autogenerated at 2020-02-26 09:00:35 +0000 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 fd01::1 controller 169.254.202.1 pxecontroller fd00::3 oamcontroller fd01::4 controller-platform-nfs fd01::3 controller-1 fd01::2 controller-0 fd02::3 controller-1-cluster-host fd02::2 controller-0-cluster-host fd01::e8b6:66fe storage-0 I saw that in ./stx-puppet/puppet-manifests/src/modules/platform/manifests/config.pp:215 class platform::config::hosts inherits ::platform::config::params { # The localhost should resolve to the IPv4 loopback address only, therefore # ensure the IPv6 address is removed from configured hosts resources { 'host': purge => true } $localhost = { 'localhost' => { ip => '127.0.0.1', host_aliases => ['localhost.localdomain', 'localhost4', 'localhost4.localdomain4'] }, } $merged_hosts = merge($localhost, $hosts) create_resources('host', $merged_hosts, {}) } Any one can give some help? Thanks! Zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Anirudh.Gupta at hsc.com Tue Mar 24 08:50:11 2020 From: Anirudh.Gupta at hsc.com (Anirudh Gupta) Date: Tue, 24 Mar 2020 08:50:11 +0000 Subject: [Starlingx-discuss] StarlingX Production Feasibility Discussion In-Reply-To: References: Message-ID: Hi Ghada, I have added the topic to the community etherpad. As per the meeting plan https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call We would be connecting with the below details on Wednesday (tomorrow): 7am Pacific - Technical Steering Committee & Community Call Call details * Zoom link: https://zoom.us/j/342730236 * Dialing in from phone: * Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 * Meeting ID: 342 730 236 * International numbers available: https://zoom.us/u/ed95sU7aQ Please do inform in case of any change in the schedule. Regards Anirudh Gupta From: Khalil, Ghada Sent: 23 March 2020 20:04 To: Anirudh Gupta ; starlingx-discuss at lists.starlingx.io Cc: Harpreet Kaur ; Amit Mahajan ; Zvonar, Bill Subject: RE: StarlingX Production Feasibility Discussion CAUTION:This email originated from an external organization Hi Anirudh, I suggest you bring the topic to one of the community meetings, held on Wednesdays at 10:30am Eastern time. At the meeting, we can decide as a community whether to review your findings on the spot or schedule a follow-up meeting. Please add the topic to the community etherpad: https://etherpad.openstack.org/p/stx-status Regards, Ghada From: Anirudh Gupta [mailto:Anirudh.Gupta at hsc.com] Sent: Monday, March 23, 2020 8:18 AM To: Khalil, Ghada Cc: Harpreet Kaur; Amit Mahajan Subject: StarlingX Production Feasibility Discussion Hi Ghada, We have been using StarlingX as a solution for our Edge based deployments since Release 1 (2018.10) and also have reported many issues which we have faced time and again. Further we need to evaluate and understand StarlingX’s feasibility in the Production Environment. Is there a possibility we can establish a call over web-ex to discuss further? If yes, please suggest a suitable date and time, so that we’ll send an invite for the same. Regards Anirudh Gupta DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Mar 24 13:42:27 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 24 Mar 2020 13:42:27 +0000 Subject: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images In-Reply-To: References: Message-ID: python-rbd is coming from the ceph package. It looks like the spec has support for building python3-rbd, but disabled: https://opendev.org/starlingx/integ/src/branch/master/ceph/ceph/centos/ceph.spec#L861 So you could try enabling it. The other option, of course, would be to drop “ceph” from the PROFILES list: https://opendev.org/starlingx/upstream/src/branch/master/openstack/python-glance/centos/stx-glance.stable_docker_image#L8 From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Tuesday, March 24, 2020 9:33 AM To: YuChengDe; Penney, Don Cc: starlingx-discuss; Somerville, Jim Subject: RE: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, Could you help on this python3-rbd dependency issue? We have to fix this issue to finish cinder image build. Thanks a lot! Zhipeng From: YuChengDe Sent: 2020年3月23日 18:55 To: don.penney Cc: starlingx-discuss ; Somerville, Jim ; Liu, ZhipengS Subject: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don: Thank for your suggestion. After exclude the starlingx_dashboard from initial building, we built the stx-horizon successfully. For now, we have the 12/13 openstack image for Ussuri version. The last should be stx-glance. It needs python3-rbd package during building. However, we just have python-rbd package for our enviroment. Do you have any proposal for how to get the required python3-rbd? + yum -y --setopt=skip_missing_names_on_install=False install ceph-common libxml2 python3-rbd postgresql-libs ^[[0mLoaded plugins: fastestmirror, ovl Loading mirror speeds from cached hostfile * base: ftp.sjtu.edu.cn * extras: mirrors.ustc.edu.cn * updates: ftp.sjtu.edu.cn Package libxml2-2.9.1-6.el7_2.3.x86_64 already installed and latest version No package python3-rbd available. ^[[91mError: Not tolerating missing names on install, stopping. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 1 of 1. [http://mailhz.qiye.163.com/qiyeimage/logo/60511048/1576638602260.jpg] -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net 发件人:"Liu, ZhipengS" > 发送日期:2020-03-14 10:30:32 收件人:"Penney, Don" >,YuChengDe >,"starlingx-discuss at lists.starlingx.io" > 抄送人:"Somerville, Jim" > 主题:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! We will try to do it further according to your proposal. Zhipeng From: Penney, Don > Sent: 2020年3月14日 0:24 To: Liu, ZhipengS >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I believe this has dependencies on a variety of StarlingX modules which are currently python2 only. You’ll probably need to exclude starlingx-dashboard for your initial builds, until all the required modules are available for python3. That said, it would be using only small components of these. So an initial effort to get python3 wheels for all the required modules may be small. Smaller than the effort to get these running as python3 on-host, certainly. From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Friday, March 13, 2020 12:20 PM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, We have finished 11/13 images build except for horizon and glance. For horizon, it needs starlingx-dashboard python3 whl. However, in our current build, we just build out starlingx-dashboard python2 whl. Do you have any proposal on how to get the required python3 whl. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 21:00 To: 'Liu, ZhipengS' >; 'Penney, Don' >; 'YuChengDe' >; 'starlingx-discuss at lists.starlingx.io' > Cc: 'Somerville, Jim' > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, Chant and I already fixed this issue and other related dependent packages. We modified docker file and related script for wheel build, and rebuilt out all python3 wheels for the packages in stable-wheels.cfg. As for libvirt-python, we still use 4.7.0 version and rebuilt out python3 wheel currently. Will let you know the status after finishing all image build. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 0:06 To: 'Liu, ZhipengS' >; Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images We also had below issue during build other service image. Looking in links: /tmp/wheels/ Collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) Collecting PyMySQL===0.9.3 Downloading PyMySQL-0.9.3-py2.py3-none-any.whl (47 kB) Processing /tmp/wheels/python_memcached-1.59-py2.py3-none-any.whl Collecting six===1.14.0 Downloading six-1.14.0-py2.py3-none-any.whl (10 kB) Collecting cffi===1.14.0 Downloading cffi-1.14.0-cp36-cp36m-manylinux1_x86_64.whl (399 kB) ERROR: Could not find a version that satisfies the requirement uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) (from versions: none) ERROR: No matching distribution found for uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) Actually, we get uWSGI-2.0.17.1-cp27-cp27mu-linux_x86_64.whl through the link in stable-config file. So far, not sure how many python3 packages we need. From: Liu, ZhipengS > Sent: 2020年3月9日 23:44 To: Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: Re: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! See my inline comments. From: Penney, Don > Sent: 2020年3月9日 23:18 To: Liu, ZhipengS >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I think building the openstack master branch will require moving the images to python3. This has implications to the base image, to how we build the base wheels tarball, and possibly to arguments passed to loci (as well as moving to a newer loci SHA). >> Yes, we have to set python3 = true to loci and also fix a small known bug. I believe Al started looking at this last week, but got pulled off to look at some other issues. From your reply, it sounds like maybe you’ve also done some of this? >> Yes When we explicitly add wheels to the tarball, we update the upper-constraints file to align with the module we’ve included. This would be why the build is looking for 4.7.0 here. There is an upper-constraints.txt file in the tarball itself which you can check. >> Yes, in our script, if we have 4.7.0 in stx repo, it will change the version to 4.7.0 from other versions specified in upper-constraints.txt The libvirt wheel building is python2 only, currently. So it would need to be built for python3 - if that’s possible for 4.7.0. If a newer version of libvirt-python is needed for python3 support, then it will need to be updated. I don’t know how big that effort will be. >> From code, libvirt-python 4.7.0 can support both python2 and python3, but in our code, we just add patch to let it build out python2 whl. >> libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, March 05, 2020 1:06 AM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Penney, We just used OpenStack master branch and upper-constraint file below https://raw.githubusercontent.com/openstack/requirements/master/upper-constraints.txt libvirt-python===5.10.0;python_version=='2.7' libvirt-python===6.0.0;python_version=='3.6' libvirt-python===6.0.0;python_version=='3.7' In nova setup.cfg. it adds python require info. python-requires = >=3.6 Then we built python3 related packages to the base image and rebuilt nova image to fix python3 issue. But there is still an error below. collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) ERROR: Could not find a version that satisfies the requirement libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) (from versions: none) ERROR: No matching distribution found for libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 From code, I saw that we already built libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl through a patch which Seems related to python2. cgcs-root/stx/integ/virt/libvirt-python/centos/meta_patches$ 0002-Build-python-wheel.patch It needs libvirt-python whl for python3, right? Do we have plan to upgrade libvirt-python to 6.0.0? Any comment? Thanks a lot! Zhipeng From: Penney, Don > Sent: 2020年2月27日 0:25 To: YuChengDe >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I was able to successfully build stx-nova image in master with no changes. Do you have any customizations in your environment? From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 26, 2020 10:38 AM To: YuChengDe; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 [Image removed by sender.] -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From yang.liu at windriver.com Tue Mar 24 15:45:13 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Tue, 24 Mar 2020 15:45:13 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 03/24/2020 Message-ID: Agenda/meeting notes are posted here: https://etherpad.openstack.org/p/stx-test Agenda for 03/24/2020 Attendees: Yang, George P, Mihail, Nicolae, Alex, Oliver, Ruediger, Cosmin, Sharath, Bruce 1. Sanity Status: · Sanity issues: * 1855474 - OpenStack pods were not recovered after force reboot active controller * 1859645 - platform-integ-apps fail to apply initially due to could not find the requested resource (get configmaps) · Nic's team running hardware and virtual sanity on Ada's machines. 2. stx4.0 testing · Feature testing: * https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=0 * Nic's team: § Oliver is reading test cases for kata containers and trying to understand · ipv6 support is not yet in § Alex is working on Ceph Nook integration · Encountered environment issue · Trying to learn the feature and updating test cases § Centos8 upgrade: · Starting from Ada's test plan, and will come up with test plan * WR: § Active Directory - in good progress § FPGA - partially tested. Orchestration portion is not ready. § k8s upgrade - in progress · Regression testing: * Spreadsheet created - test cases to be selected § https://docs.google.com/spreadsheets/d/1gA3bnLS7aY2y8dKxm4MuqpWyELq3PVJMYtiHn4IWiAk/edit#gid=1921715792 * Testers are encouraged to add selective new feature test cases to regression while running new feature testing. * For regression, the load does not have to be refreshed everyday, can refresh the load every 3-5 days. 3. Unified santiy · George will add couple of core reviewers from WR to review his commit 4. Opens · Servers arrived at Nic's team, more to come * Currently setting up the servers for baremetal environment - may take couple of weeks with support from Ada's team · Nic will select couple of core reviewers from his team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Tue Mar 24 16:31:54 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 24 Mar 2020 16:31:54 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Mar 25, 2020) Message-ID: Hi all, reminder of tomorrow's TSC/Community call. We'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200325T1400 From nicolae.jascanu at intel.com Tue Mar 24 19:40:48 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Tue, 24 Mar 2020 19:40:48 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build - ISO 20200323 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-23 ( http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200323T230003Z/outputs/iso/ ) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 ] AIO - Duplex [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Regards, STX Validation Team Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From Don.Penney at windriver.com Tue Mar 24 20:24:13 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 24 Mar 2020 20:24:13 +0000 Subject: [Starlingx-discuss] enable pbr version In-Reply-To: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> Message-ID: Hi Yipeng, Can you provide more info? What was the error you saw from build-iso? -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Monday, March 23, 2020 6:45 PM To: 何义鹏 Cc: 桂来军; 杨永金; 曹明晓; starlingx-discuss Subject: Re: [Starlingx-discuss] enable pbr version Hi Yipeng, I was out last week on vacation, so I am catching up now. I think you would have to investigate build-iso and associated scripts and tools to see if there is an awk, sed or some other command that is not parsing the extended version. I have not investigated this further, that's my initial assessment. Can you be more specific about what the error is or provide a log file of the build-iso process? Thanks for working on this project. Sau! On 3/19/20 12:21 AM, 何义鹏 wrote: > Hello Saul > > I'm Yipeng He from JITStack, and I'm taking over the tasks of PBR. > I encountered the following issue when trying to build iso: > It fails when the suffix of the version generated by the PBR tool ended > with number, for instance the building fails if the version id is > 2.999.9999.rc1.dev23, > and when I replaced it with 2.999.9999.rc1.dev, the ISO building was > successful. > I don't knwo why this happens, could please support and advice the > solution for this issue. > > > Yipeng.He > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From yu.chengde at 99cloud.net Wed Mar 25 06:53:08 2020 From: yu.chengde at 99cloud.net (YuChengDe) Date: Wed, 25 Mar 2020 14:53:08 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?=5BOpenStack_Upgrade=5D_Built_the_s?= =?utf-8?q?tx-glance_for_stable/ussuri?= Message-ID: Hi: We have built a stx-horizon image for Ussuri version Welcome to apply image into your system. If there is any problem during usage, please let me know. Many thanks. Note: Get the image from docker hub P.S.: tag = [git branch]-[based on python3 or python built environment]-[image created day] docker pull chantyu/stx-glance:ussuri-python3-20200323 PROJECT_REPO= https://opendev.org/openstack/glance.git PROJECT_REF= master BUILDER= loci -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From yu.chengde at 99cloud.net Wed Mar 25 06:53:50 2020 From: yu.chengde at 99cloud.net (YuChengDe) Date: Wed, 25 Mar 2020 14:53:50 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?=5BOpenStack_Upgrade=5D_Built_the_s?= =?utf-8?q?tx-glance_for_stable/ussuri?= Message-ID: Hi: We have built a stx-glance image for Ussuri version Welcome to apply image into your system. If there is any problem during usage, please let me know. Many thanks. Note: Get the image from docker hub P.S.: tag = [git branch]-[based on python3 or python built environment]-[image created day] docker pull chantyu/stx-glance:ussuri-python3-20200323 PROJECT_REPO= https://opendev.org/openstack/glance.git PROJECT_REF= master BUILDER= loci -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Wed Mar 25 08:29:00 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 25 Mar 2020 04:29:00 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 159 - Failure! Message-ID: <2084035145.1080.1585124945508.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 159 Status: Failure Timestamp: 20200325T081627Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200325T080227Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200325T080227Z DOCKER_BUILD_ID: jenkins-master-flock-20200325T080227Z-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/20200325T080227Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200325T080227Z/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 Wed Mar 25 08:29:07 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 25 Mar 2020 04:29:07 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 57 - Still Failing! In-Reply-To: <944693054.1068.1585038585997.JavaMail.javamailuser@localhost> References: <944693054.1068.1585038585997.JavaMail.javamailuser@localhost> Message-ID: <109900857.1083.1585124948695.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 57 Status: Still Failing Timestamp: 20200325T080227Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200325T080227Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: false From zhipengs.liu at intel.com Wed Mar 25 09:19:19 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 25 Mar 2020 09:19:19 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. In-Reply-To: References: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314F6B2@SHSMSX104.ccr.corp.intel.com> , , Message-ID: Hi Josesh, I have added 2 more patches for your review. https://review.opendev.org/714894 https://review.opendev.org/714898 So far, it can deploy services until heat. But I still have an intermittent issue that ***-ks-user jobs always need restart several times to get task finished. Sometimes, it may cause endpoint job failure and block deployment procedure. Log looks like below, still not find the root cause. Could you help on this point? Thanks! Failed to discover available identity versions when contacting http://keystone-api.openstack.svc.cluster.local:5000/v3. Attempting to parse version from URL. Unable to establish connection to http://keystone-api.openstack.svc.cluster.local:5000/v3/auth/tokens: HTTPConnectionPool(host='keystone-api.openstack.svc.cluster.local', port=5000): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 101] Network is unreachable',)) Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月23日 21:50 To: 'Richard, Joseph' Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, I have updated my 2 patches, both tested on ipv4 and ipv6 setup. https://review.opendev.org/#/c/714034/ https://review.opendev.org/#/c/714038/ But still failed when deploy keystone, glance, cinder later. Common failure causes are found that need to bind host to :: instead of 0.0.0.0. Otherwise, it will only bind port to ipv4 address, which causes db connect failure or pod probe failure. After below changes, it can run until deploying cinder. 1)Change mariadb value.yaml conf: bind adress from 0.0.0.0 to :: 2) Change keystone value.yaml wsgi_keystone: | {{- $portInt := tuple "identity" "internal" "api" $ | include "helm-toolkit.endpoints.endpoint_port_lookup" }} Listen 0.0.0.0:{{ $portInt }} change to Listen :::{{ $portInt }} 3) Change glance value.yaml Conf.Default: add bind_host = "::" I have to check these services deploy one by one. Thanks! Zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Tue Mar 24 15:07:19 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 24 Mar 2020 15:07:19 +0000 Subject: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images In-Reply-To: References: Message-ID: Thanks Don! We will work further according to your guidance. Zhipeng From: Penney, Don Sent: 2020年3月24日 21:42 To: Liu, ZhipengS ; YuChengDe Cc: starlingx-discuss ; Somerville, Jim Subject: RE: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images python-rbd is coming from the ceph package. It looks like the spec has support for building python3-rbd, but disabled: https://opendev.org/starlingx/integ/src/branch/master/ceph/ceph/centos/ceph.spec#L861 So you could try enabling it. The other option, of course, would be to drop “ceph” from the PROFILES list: https://opendev.org/starlingx/upstream/src/branch/master/openstack/python-glance/centos/stx-glance.stable_docker_image#L8 From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Tuesday, March 24, 2020 9:33 AM To: YuChengDe; Penney, Don Cc: starlingx-discuss; Somerville, Jim Subject: RE: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, Could you help on this python3-rbd dependency issue? We have to fix this issue to finish cinder image build. Thanks a lot! Zhipeng From: YuChengDe > Sent: 2020年3月23日 18:55 To: don.penney > Cc: starlingx-discuss >; Somerville, Jim >; Liu, ZhipengS > Subject: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don: Thank for your suggestion. After exclude the starlingx_dashboard from initial building, we built the stx-horizon successfully. For now, we have the 12/13 openstack image for Ussuri version. The last should be stx-glance. It needs python3-rbd package during building. However, we just have python-rbd package for our enviroment. Do you have any proposal for how to get the required python3-rbd? + yum -y --setopt=skip_missing_names_on_install=False install ceph-common libxml2 python3-rbd postgresql-libs ^[[0mLoaded plugins: fastestmirror, ovl Loading mirror speeds from cached hostfile * base: ftp.sjtu.edu.cn * extras: mirrors.ustc.edu.cn * updates: ftp.sjtu.edu.cn Package libxml2-2.9.1-6.el7_2.3.x86_64 already installed and latest version No package python3-rbd available. ^[[91mError: Not tolerating missing names on install, stopping. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 1 of 1. [http://mailhz.qiye.163.com/qiyeimage/logo/60511048/1576638602260.jpg] -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net 发件人:"Liu, ZhipengS" > 发送日期:2020-03-14 10:30:32 收件人:"Penney, Don" >,YuChengDe >,"starlingx-discuss at lists.starlingx.io" > 抄送人:"Somerville, Jim" > 主题:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! We will try to do it further according to your proposal. Zhipeng From: Penney, Don > Sent: 2020年3月14日 0:24 To: Liu, ZhipengS >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I believe this has dependencies on a variety of StarlingX modules which are currently python2 only. You’ll probably need to exclude starlingx-dashboard for your initial builds, until all the required modules are available for python3. That said, it would be using only small components of these. So an initial effort to get python3 wheels for all the required modules may be small. Smaller than the effort to get these running as python3 on-host, certainly. From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Friday, March 13, 2020 12:20 PM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, We have finished 11/13 images build except for horizon and glance. For horizon, it needs starlingx-dashboard python3 whl. However, in our current build, we just build out starlingx-dashboard python2 whl. Do you have any proposal on how to get the required python3 whl. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 21:00 To: 'Liu, ZhipengS' >; 'Penney, Don' >; 'YuChengDe' >; 'starlingx-discuss at lists.starlingx.io' > Cc: 'Somerville, Jim' > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, Chant and I already fixed this issue and other related dependent packages. We modified docker file and related script for wheel build, and rebuilt out all python3 wheels for the packages in stable-wheels.cfg. As for libvirt-python, we still use 4.7.0 version and rebuilt out python3 wheel currently. Will let you know the status after finishing all image build. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 0:06 To: 'Liu, ZhipengS' >; Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images We also had below issue during build other service image. Looking in links: /tmp/wheels/ Collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) Collecting PyMySQL===0.9.3 Downloading PyMySQL-0.9.3-py2.py3-none-any.whl (47 kB) Processing /tmp/wheels/python_memcached-1.59-py2.py3-none-any.whl Collecting six===1.14.0 Downloading six-1.14.0-py2.py3-none-any.whl (10 kB) Collecting cffi===1.14.0 Downloading cffi-1.14.0-cp36-cp36m-manylinux1_x86_64.whl (399 kB) ERROR: Could not find a version that satisfies the requirement uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) (from versions: none) ERROR: No matching distribution found for uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) Actually, we get uWSGI-2.0.17.1-cp27-cp27mu-linux_x86_64.whl through the link in stable-config file. So far, not sure how many python3 packages we need. From: Liu, ZhipengS > Sent: 2020年3月9日 23:44 To: Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: Re: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! See my inline comments. From: Penney, Don > Sent: 2020年3月9日 23:18 To: Liu, ZhipengS >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I think building the openstack master branch will require moving the images to python3. This has implications to the base image, to how we build the base wheels tarball, and possibly to arguments passed to loci (as well as moving to a newer loci SHA). >> Yes, we have to set python3 = true to loci and also fix a small known bug. I believe Al started looking at this last week, but got pulled off to look at some other issues. From your reply, it sounds like maybe you’ve also done some of this? >> Yes When we explicitly add wheels to the tarball, we update the upper-constraints file to align with the module we’ve included. This would be why the build is looking for 4.7.0 here. There is an upper-constraints.txt file in the tarball itself which you can check. >> Yes, in our script, if we have 4.7.0 in stx repo, it will change the version to 4.7.0 from other versions specified in upper-constraints.txt The libvirt wheel building is python2 only, currently. So it would need to be built for python3 - if that’s possible for 4.7.0. If a newer version of libvirt-python is needed for python3 support, then it will need to be updated. I don’t know how big that effort will be. >> From code, libvirt-python 4.7.0 can support both python2 and python3, but in our code, we just add patch to let it build out python2 whl. >> libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, March 05, 2020 1:06 AM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Penney, We just used OpenStack master branch and upper-constraint file below https://raw.githubusercontent.com/openstack/requirements/master/upper-constraints.txt libvirt-python===5.10.0;python_version=='2.7' libvirt-python===6.0.0;python_version=='3.6' libvirt-python===6.0.0;python_version=='3.7' In nova setup.cfg. it adds python require info. python-requires = >=3.6 Then we built python3 related packages to the base image and rebuilt nova image to fix python3 issue. But there is still an error below. collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) ERROR: Could not find a version that satisfies the requirement libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) (from versions: none) ERROR: No matching distribution found for libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 From code, I saw that we already built libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl through a patch which Seems related to python2. cgcs-root/stx/integ/virt/libvirt-python/centos/meta_patches$ 0002-Build-python-wheel.patch It needs libvirt-python whl for python3, right? Do we have plan to upgrade libvirt-python to 6.0.0? Any comment? Thanks a lot! Zhipeng From: Penney, Don > Sent: 2020年2月27日 0:25 To: YuChengDe >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I was able to successfully build stx-nova image in master with no changes. Do you have any customizations in your environment? From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 26, 2020 10:38 AM To: YuChengDe; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 [Image removed by sender.] -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From yu.chengde at 99cloud.net Wed Mar 25 07:20:46 2020 From: yu.chengde at 99cloud.net (YuChengDe) Date: Wed, 25 Mar 2020 15:20:46 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?=5BOpenStack_Upgrade=5DFailed_when_?= =?utf-8?q?build_StarlingX_docker_images?= In-Reply-To: Message-ID: Hi Don, Thanks for your suggestion. I chose to drop "ceph" from the profiles list in stx-glance.stable_docker_image ,and build the stx-glacne successfully. For your information. -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net 发件人:"Penney, Don" 发送日期:2020-03-24 21:42:27 收件人:"Liu, ZhipengS" ,YuChengDe 抄送人:starlingx-discuss ,"Somerville, Jim" 主题:RE: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images python-rbd is coming from the ceph package. It looks like the spec has support for building python3-rbd, but disabled: https://opendev.org/starlingx/integ/src/branch/master/ceph/ceph/centos/ceph.spec#L861 So you could try enabling it. The other option, of course, would be to drop “ceph” from the PROFILES list: https://opendev.org/starlingx/upstream/src/branch/master/openstack/python-glance/centos/stx-glance.stable_docker_image#L8 From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Tuesday, March 24, 2020 9:33 AM To: YuChengDe; Penney, Don Cc: starlingx-discuss; Somerville, Jim Subject: RE: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, Could you help on this python3-rbd dependency issue? We have to fix this issue to finish cinder image build. Thanks a lot! Zhipeng From: YuChengDe Sent: 2020年3月23日 18:55 To: don.penney Cc: starlingx-discuss ; Somerville, Jim ; Liu, ZhipengS Subject: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don: Thank for your suggestion. After exclude the starlingx_dashboard from initial building, we built the stx-horizon successfully. For now, we have the 12/13 openstack image for Ussuri version. The last should be stx-glance. It needs python3-rbd package during building. However, we just have python-rbd package for our enviroment. Do you have any proposal for how to get the required python3-rbd? + yum -y --setopt=skip_missing_names_on_install=False install ceph-common libxml2 python3-rbd postgresql-libs ^[[0mLoaded plugins: fastestmirror, ovl Loading mirror speeds from cached hostfile * base: ftp.sjtu.edu.cn * extras: mirrors.ustc.edu.cn * updates: ftp.sjtu.edu.cn Package libxml2-2.9.1-6.el7_2.3.x86_64 already installed and latest version No package python3-rbd available. ^[[91mError: Not tolerating missing names on install, stopping. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 1 of 1. -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net 发件人:"Liu, ZhipengS" 发送日期:2020-03-14 10:30:32 收件人:"Penney, Don" ,YuChengDe ,"starlingx-discuss at lists.starlingx.io" 抄送人:"Somerville, Jim" 主题:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! We will try to do it further according to your proposal. Zhipeng From: Penney, Don Sent: 2020年3月14日 0:24 To: Liu, ZhipengS ; YuChengDe ; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I believe this has dependencies on a variety of StarlingX modules which are currently python2 only. You’ll probably need to exclude starlingx-dashboard for your initial builds, until all the required modules are available for python3. That said, it would be using only small components of these. So an initial effort to get python3 wheels for all the required modules may be small. Smaller than the effort to get these running as python3 on-host, certainly. From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Friday, March 13, 2020 12:20 PM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, We have finished 11/13 images build except for horizon and glance. For horizon, it needs starlingx-dashboard python3 whl. However, in our current build, we just build out starlingx-dashboard python2 whl. Do you have any proposal on how to get the required python3 whl. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 21:00 To: 'Liu, ZhipengS' ; 'Penney, Don' ; 'YuChengDe' ; 'starlingx-discuss at lists.starlingx.io' Cc: 'Somerville, Jim' Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, Chant and I already fixed this issue and other related dependent packages. We modified docker file and related script for wheel build, and rebuilt out all python3 wheels for the packages in stable-wheels.cfg. As for libvirt-python, we still use 4.7.0 version and rebuilt out python3 wheel currently. Will let you know the status after finishing all image build. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 0:06 To: 'Liu, ZhipengS' ; Penney, Don ; YuChengDe ; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images We also had below issue during build other service image. Looking in links: /tmp/wheels/ Collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) Collecting PyMySQL===0.9.3 Downloading PyMySQL-0.9.3-py2.py3-none-any.whl (47 kB) Processing /tmp/wheels/python_memcached-1.59-py2.py3-none-any.whl Collecting six===1.14.0 Downloading six-1.14.0-py2.py3-none-any.whl (10 kB) Collecting cffi===1.14.0 Downloading cffi-1.14.0-cp36-cp36m-manylinux1_x86_64.whl (399 kB) ERROR: Could not find a version that satisfies the requirement uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) (from versions: none) ERROR: No matching distribution found for uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) Actually, we get uWSGI-2.0.17.1-cp27-cp27mu-linux_x86_64.whl through the link in stable-config file. So far, not sure how many python3 packages we need. From: Liu, ZhipengS Sent: 2020年3月9日 23:44 To: Penney, Don ; YuChengDe ; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: Re: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! See my inline comments. From: Penney, Don Sent: 2020年3月9日 23:18 To: Liu, ZhipengS ; YuChengDe ; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I think building the openstack master branch will require moving the images to python3. This has implications to the base image, to how we build the base wheels tarball, and possibly to arguments passed to loci (as well as moving to a newer loci SHA). >> Yes, we have to set python3 = true to loci and also fix a small known bug. I believe Al started looking at this last week, but got pulled off to look at some other issues. From your reply, it sounds like maybe you’ve also done some of this? >> Yes When we explicitly add wheels to the tarball, we update the upper-constraints file to align with the module we’ve included. This would be why the build is looking for 4.7.0 here. There is an upper-constraints.txt file in the tarball itself which you can check. >> Yes, in our script, if we have 4.7.0 in stx repo, it will change the version to 4.7.0 from other versions specified in upper-constraints.txt The libvirt wheel building is python2 only, currently. So it would need to be built for python3 - if that’s possible for 4.7.0. If a newer version of libvirt-python is needed for python3 support, then it will need to be updated. I don’t know how big that effort will be. >> From code, libvirt-python 4.7.0 can support both python2 and python3, but in our code, we just add patch to let it build out python2 whl. >> libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, March 05, 2020 1:06 AM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Penney, We just used OpenStack master branch and upper-constraint file below https://raw.githubusercontent.com/openstack/requirements/master/upper-constraints.txt libvirt-python===5.10.0;python_version=='2.7' libvirt-python===6.0.0;python_version=='3.6' libvirt-python===6.0.0;python_version=='3.7' In nova setup.cfg. it adds python require info. python-requires = >=3.6 Then we built python3 related packages to the base image and rebuilt nova image to fix python3 issue. But there is still an error below. collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) ERROR: Could not find a version that satisfies the requirement libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) (from versions: none) ERROR: No matching distribution found for libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 From code, I saw that we already built libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl through a patch which Seems related to python2. cgcs-root/stx/integ/virt/libvirt-python/centos/meta_patches$ 0002-Build-python-wheel.patch It needs libvirt-python whl for python3, right? Do we have plan to upgrade libvirt-python to 6.0.0? Any comment? Thanks a lot! Zhipeng From: Penney, Don Sent: 2020年2月27日 0:25 To: YuChengDe ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I was able to successfully build stx-nova image in master with no changes. Do you have any customizations in your environment? From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 26, 2020 10:38 AM To: YuChengDe; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: not available URL: From Stefan.Dinescu at windriver.com Wed Mar 25 14:02:02 2020 From: Stefan.Dinescu at windriver.com (Dinescu, Stefan) Date: Wed, 25 Mar 2020 14:02:02 +0000 Subject: [Starlingx-discuss] New remote client changes Message-ID: Hello, In an effort to add greater customizability and offer better debugging support, some changes have been made to remote clients. Until now, remote clients were built weekly by the CENGN build and a tarball provided at [1]. This tarball had the location of the docker images embedded inside them; while users could open the file that contained the links to these docker images and edit them, no official support was provided for this. With the latest changes that just merged, you can override the pulled images when you configure the clients. The review that added the changes is at [2]. The commit added two new optional parameters: "-p" and "-a". As stated, they are optional and if don't use them the used images will be the default ones mentioned in the tarball. The "-p" parameter is used to override the platformclients image and "-a" is used to override the openstack application image. Examples of usage: 1. ./configure_client.sh (without any parameters given, the defaults will be used) 2. ./configure_client.sh -p docker.io/randomrepo/randomimage:latest (this will use the docker image given as parameter for platform client operations) 3. ./configure_client.sh -a docker.io/anotherrepo/anotherimage:tag(this will use the docker image given as parameter for openstack clients operations) 4. ./configure_client -p docker.io/randomrepo/randomimage:latest -a docker.io/anotherrepo/anotherimage:tag (it will override both) For full instruction about how to configure and use remote clients for StarlingX, you can read the full readme at [3] [1]: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/remote-cli/ [2]: https://review.opendev.org/#/c/714897/ [3]: https://opendev.org/starlingx/clients/src/branch/master/remote_cli/README -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joseph.Richard at windriver.com Wed Mar 25 14:07:59 2020 From: Joseph.Richard at windriver.com (Richard, Joseph) Date: Wed, 25 Mar 2020 14:07:59 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. In-Reply-To: References: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314F6B2@SHSMSX104.ccr.corp.intel.com> , , , Message-ID: I see at least one place [1] where keystone is configured to listen on 0.0.0.0, so that's probably why. [1] https://github.com/openstack/openstack-helm/blob/master/keystone/values.yaml#L949 ________________________________ From: Liu, ZhipengS Sent: Wednesday, March 25, 2020 5:19 AM To: Richard, Joseph Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Josesh, I have added 2 more patches for your review. https://review.opendev.org/714894 https://review.opendev.org/714898 So far, it can deploy services until heat. But I still have an intermittent issue that ***-ks-user jobs always need restart several times to get task finished. Sometimes, it may cause endpoint job failure and block deployment procedure. Log looks like below, still not find the root cause. Could you help on this point? Thanks! Failed to discover available identity versions when contacting http://keystone-api.openstack.svc.cluster.local:5000/v3. Attempting to parse version from URL. Unable to establish connection to http://keystone-api.openstack.svc.cluster.local:5000/v3/auth/tokens: HTTPConnectionPool(host='keystone-api.openstack.svc.cluster.local', port=5000): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 101] Network is unreachable',)) Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月23日 21:50 To: 'Richard, Joseph' Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, I have updated my 2 patches, both tested on ipv4 and ipv6 setup. https://review.opendev.org/#/c/714034/ https://review.opendev.org/#/c/714038/ But still failed when deploy keystone, glance, cinder later. Common failure causes are found that need to bind host to :: instead of 0.0.0.0. Otherwise, it will only bind port to ipv4 address, which causes db connect failure or pod probe failure. After below changes, it can run until deploying cinder. 1)Change mariadb value.yaml conf: bind adress from 0.0.0.0 to :: 2) Change keystone value.yaml wsgi_keystone: | {{- $portInt := tuple "identity" "internal" "api" $ | include "helm-toolkit.endpoints.endpoint_port_lookup" }} Listen 0.0.0.0:{{ $portInt }} change to Listen :::{{ $portInt }} 3) Change glance value.yaml Conf.Default: add bind_host = "::" I have to check these services deploy one by one. Thanks! Zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Wed Mar 25 14:11:51 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 25 Mar 2020 14:11:51 +0000 Subject: [Starlingx-discuss] enable pbr version In-Reply-To: References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> Message-ID: Please keep starlingx-discuss on the receiver list. You had indicated build-iso was failing, but the build.log you provided appears to be the RPM build log for starlingx-dashboard. Processing files: starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.noarch error: File not found: /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9999.9999.rc1.dev23*.egg-info RPM build errors: File not found: /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9999.9999.rc1.dev23*.egg-info Child return code was: 1 EXCEPTION: [Error()] Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", line 95, in trace result = func(*args, **kw) File "/usr/lib/python3.6/site-packages/mockbuild/util.py", line 746, in do_with_status raise exception.Error("Command failed: \n # %s\n%s" % (command, output), child.returncode) mockbuild.exception.Error: Command failed: # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/starlingx-dashboard.spec Looking through the build.log, I see the following: Copying starlingx_dashboard.egg-info to build/bdist.linux-x86_64/wheel/starlingx_dashboard-2.9999.9999rc1.dev23-py2.7.egg-info So in the build, it’s creating the egg with the version set to 2.9999.9999rc1.dev23, while the %files is expecting it to be 2.9999.9999.rc1.dev23. Looking further through the build.log, there’s the following: + /usr/bin/python2 setup.py install -O1 --skip-build --root /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64 /usr/lib/python2.7/site-packages/setuptools/dist.py:355: UserWarning: Normalizing '2.9999.9999.rc1.dev23' to '2.9999.9999rc1.dev23' normalized_version, running install Maybe the python build only allows 4 version components? From: 何义鹏 [mailto:yipeng.he at jitstack.com] Sent: Tuesday, March 24, 2020 9:59 PM To: Penney, Don Subject: Re:RE: [Starlingx-discuss] enable pbr version Hi Saul, I added the error log to the attachment. Do you need other files for analysis? Thank you for your help. yipeng.he! ------------------ Original ------------------ From: "Penney, Don"; Date: Wed, Mar 25, 2020 04:24 AM To: "Saul Wold"; "何义鹏"; Cc: "桂来军"; "杨永金"; "曹明晓"; "starlingx-discuss"; Subject: RE: [Starlingx-discuss] enable pbr version Hi Yipeng, Can you provide more info? What was the error you saw from build-iso? -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Monday, March 23, 2020 6:45 PM To: 何义鹏 Cc: 桂来军; 杨永金; 曹明晓; starlingx-discuss Subject: Re: [Starlingx-discuss] enable pbr version Hi Yipeng, I was out last week on vacation, so I am catching up now. I think you would have to investigate build-iso and associated scripts and tools to see if there is an awk, sed or some other command that is not parsing the extended version. I have not investigated this further, that's my initial assessment. Can you be more specific about what the error is or provide a log file of the build-iso process? Thanks for working on this project. Sau! On 3/19/20 12:21 AM, 何义鹏 wrote: > Hello Saul > > I'm Yipeng He from JITStack, and I'm taking over the tasks of PBR. > I encountered the following issue when trying to build iso: > It fails when the suffix of the version generated by the PBR tool ended > with number, for instance the building fails if the version id is > 2.999.9999.rc1.dev23, > and when I replaced it with 2.999.9999.rc1.dev, the ISO building was > successful. > I don't knwo why this happens, could please support and advice the > solution for this issue. > > > Yipeng.He > > _______________________________________________ > 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 Ian.Jolliffe at windriver.com Wed Mar 25 14:15:29 2020 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Wed, 25 Mar 2020 14:15:29 +0000 Subject: [Starlingx-discuss] [TPM] TPM test documentation In-Reply-To: References: <9b0dddd21a82463fa244a6410259fe6b@neusoft.com> Message-ID: Hi Austin; You will need access to a server with a TPM device installed. Regards; Ian From: "Sun, Austin" Date: Monday, March 23, 2020 at 8:44 PM To: Bill Zvonar , "Yong.Fu" , StarlingX ML Subject: Re: [Starlingx-discuss] [TPM] TPM test documentation Hi Bill: This is only TPM part, Integrity part is not tested yet. If anyone know if any specific HW is needed for Integrity and how to verify integrity function . Please share with us. Thanks. BR Austin Sun. From: Zvonar, Bill Sent: Monday, March 23, 2020 10:19 PM To: Sun, Austin ; Yong.Fu ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [TPM] TPM test documentation Hi Austin – you mentioned last week on the community call that tpm testing is a risk for this upgrade. Does this update mean that risk is lowered/gone now? Thanks, Bill... From: Sun, Austin > Sent: Monday, March 23, 2020 4:10 AM To: Yong.Fu >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [TPM] TPM test documentation Thanks a lot Fu yong for sharing. @all, kernel3.10 and kernel 4.18 have been tested based on these test steps. would you like to review this documents ? is this good enough for tpm driver ? Thanks. BR Austin Sun. From: Yong.Fu > Sent: Monday, March 23, 2020 11:11 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [TPM] TPM test documentation Hi all: I updated the relevant test documentation for TPM2.0 devices with tpm2-tools, https://wiki.openstack.org/wiki/StarlingX/Distro/tpm-verify If you have any questions and good suggestions, please contact me. Thank you Yong --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Wed Mar 25 14:47:01 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 25 Mar 2020 14:47:01 +0000 Subject: [Starlingx-discuss] [TPM] TPM test documentation In-Reply-To: References: <9b0dddd21a82463fa244a6410259fe6b@neusoft.com> Message-ID: Hi Ian: Thanks your feedback. Would you like to share how to verify integrity module on HW w/ tpm ? Thanks. BR Austin Sun. From: Jolliffe, Ian Sent: Wednesday, March 25, 2020 10:15 PM To: Sun, Austin ; Zvonar, Bill ; Yong.Fu ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [TPM] TPM test documentation Hi Austin; You will need access to a server with a TPM device installed. Regards; Ian From: "Sun, Austin" > Date: Monday, March 23, 2020 at 8:44 PM To: Bill Zvonar >, "Yong.Fu" >, StarlingX ML > Subject: Re: [Starlingx-discuss] [TPM] TPM test documentation Hi Bill: This is only TPM part, Integrity part is not tested yet. If anyone know if any specific HW is needed for Integrity and how to verify integrity function . Please share with us. Thanks. BR Austin Sun. From: Zvonar, Bill > Sent: Monday, March 23, 2020 10:19 PM To: Sun, Austin >; Yong.Fu >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [TPM] TPM test documentation Hi Austin – you mentioned last week on the community call that tpm testing is a risk for this upgrade. Does this update mean that risk is lowered/gone now? Thanks, Bill... From: Sun, Austin > Sent: Monday, March 23, 2020 4:10 AM To: Yong.Fu >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [TPM] TPM test documentation Thanks a lot Fu yong for sharing. @all, kernel3.10 and kernel 4.18 have been tested based on these test steps. would you like to review this documents ? is this good enough for tpm driver ? Thanks. BR Austin Sun. From: Yong.Fu > Sent: Monday, March 23, 2020 11:11 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [TPM] TPM test documentation Hi all: I updated the relevant test documentation for TPM2.0 devices with tpm2-tools, https://wiki.openstack.org/wiki/StarlingX/Distro/tpm-verify If you have any questions and good suggestions, please contact me. Thank you Yong --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Mar 25 14:54:27 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 25 Mar 2020 14:54:27 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Mar 25, 2020) In-Reply-To: References: Message-ID: Standing Topics * Sanity * Monolithic: all green since last week * Layered: two red sanities, still working through the layered build issues - root cause understood, solution is being worked * Gerrit Review in need of Attention * nothing this week * CentOS 8 * Austin/Nic to provide plan for testing the Integrity driver by EOW & an overall view of the kernel upgrade introduction/test plan (what's been tested, what's pending, what is not planned to be tested) This Week's Topics * StarlingX feedback: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008085.html * StarlingX User survey link: https://www.surveymonkey.com/r/StarlingX * StarlingX Production Feasability and Bug Status * Functional Issues * https://bugs.launchpad.net/starlingx/+bug/1867731 (Cinder Public Endpoint Not Reachable with FQDN enabled) * HA Related issues * https://bugs.launchpad.net/starlingx/+bug/1852734 (System takes 25-30 minutes to stablize) * https://bugs.launchpad.net/starlingx/+bug/1852395 (Openstack horizon not available for 4-5 mins when any node get reboot/shutdown) * StarlingX Upgrade Functionality * notes from discussion * evaluating Stx for one of their customers, edge node deployment * raised 3 issues, LPs above * want to move StarlingX to a production environment * best advice re: bug priority/plan is to approach the sub-project teams * for upgrades, community is working on 3.0 to 4.0 * exact version to be determined * welcomed them to help out if they want/can * there's also the upgrade spec for 3.0 to 4.0 * and we invited them to take the survey, link is above Open Requests for Help * the way to enable swift in starlingx: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007758.html * Volker has asked if the community can consider this request again - anybody up for having a look? * no takers in today's call * question about 'latest green build' * still open, Frank will bring this up again on the build call tomorrow * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008026.html -----Original Message----- From: Zvonar, Bill Sent: Tuesday, March 24, 2020 12:32 PM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Mar 25, 2020) Hi all, reminder of tomorrow's TSC/Community call. We'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200325T1400 From fungi at yuggoth.org Wed Mar 25 17:26:03 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 25 Mar 2020 17:26:03 +0000 Subject: [Starlingx-discuss] enable pbr version In-Reply-To: References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> Message-ID: <20200325172603.t33y4xjf5qxiguff@yuggoth.org> On 2020-03-25 14:11:51 +0000 (+0000), Penney, Don wrote: [...] > Looking further through the build.log, there’s the following: > + /usr/bin/python2 setup.py install -O1 --skip-build --root /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64 > /usr/lib/python2.7/site-packages/setuptools/dist.py:355: UserWarning: Normalizing '2.9999.9999.rc1.dev23' to '2.9999.9999rc1.dev23' > normalized_version, > running install > > Maybe the python build only allows 4 version components? [...] The number of components is not the problem. If you want that rc1 to be a separate component it needs to be 2.9999.9999.0rc1.dev23 since PEP 440 normalization considers 2.9999.9999rc1.dev23 to be the canonical form of 2.9999.9999.rc1.dev23 and Setuptools is therefore correcting it for you: https://www.python.org/dev/peps/pep-0440/#pre-release-separators -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From nicolae.jascanu at intel.com Wed Mar 25 18:50:36 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Wed, 25 Mar 2020 18:50:36 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200325 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-March-25 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200325T013010Z/outputs/iso/ ) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 ] AIO - Duplex [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Regards, STX Validation Team Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From ildiko.vancsa at gmail.com Wed Mar 25 18:51:46 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 25 Mar 2020 19:51:46 +0100 Subject: [Starlingx-discuss] [tsc] Repo for CNCF landscape Message-ID: Hi, As the community decided to go through CNCF conformance process I have a PR open for StarlingX: https://github.com/cncf/k8s-conformance/pull/891 I got one last minor comment to fix which I wanted to confirm with you which is the following: “In order to show as open source on the Cloud Native landscape, you'd have to pick one repo to use. People normally use either the main code or an installer.” The review comment suggests the config repo (https://github.com/starlingx/config). Would the TSC and the community agree with that pick or you have another preference? Thanks, Ildikó From scott.little at windriver.com Wed Mar 25 18:53:11 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 25 Mar 2020 14:53:11 -0400 Subject: [Starlingx-discuss] Fwd: Re: Sanity Master Test MONOLITHIC build - ISO 20200313 In-Reply-To: References: Message-ID: <77c1fffc-a238-a58e-99a4-30eef4349fc8@windriver.com> Fixed the scraper again.  Both this and the prior issue centered on subtle changes to whitespace usage. I propose the following convention ... 1)  e-mail subject starts with on of ...     "[Starlingx-discuss] Sanity Master Test MONOLITHIC"    "[Starlingx-discuss] Sanity Master Test LAYERED" ... where whitespace consists of a single space. The remainder of the subject line should not contain and special regex or glob characters other than '[' and ']' 2) The first line of text in the body should include a link the build output directory enclosed in parenthesis '()', or angle brackets '<' '>', or angle brackets within parenthesis. Spaces are permitted within the enclosing parenthesis. Test is permited outside the innermost enclosing parenthesis or anglebracket pair. e.g.    blah blah ( http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200323T230003Z/outputs/iso/ ) blah blah or    blah blah (blah) blah blah. This must be the first link in the body of the email. 3) The declaration of sanity status. The body shall contain a line of text starting with 'Status: ' (a single space included) followed by one of 'RED' 'YELLOW' or 'GREEN', in caps and without quotes.  The line should contain no other text. e.g. Status: RED Status: YELLOW Status: GREEN Scott On 2020-03-25 3:34 a.m., Bruecher, Bjoern wrote: > > Mihail, > > I haven’t seen a response here and the process is still broken. Your > last email is already one week old. I am also adding Nicolae here in > response to the last GREEN release. I see the problem with the latest > release. > > What is the ETA for a solution. I don’t think that it would be that > difficult to fix. Can you please drive this and respond by eo week > with a solution? > > Thanks & Best, > > Bjoern > > *From:* Trica, Mihail-Laurentiu > *Sent:* Tuesday, March 17, 2020 17:25 > *To:* Demezzi, Marco ; Bruecher, Bjoern > ; iotg_starlingx_validation > > *Cc:* Wagner, Marcel ; Shashi, Yatindra > ; Scott Little > *Subject:* RE: [Starlingx-discuss] Sanity Master Test MONOLITHIC build > - ISO 20200313 > > Hello Scott, > > I apologize for adding you directly to this thread, but an Intel > colleague (Bjoern Bruechner) asked me about an issue with the > “latest_green_build” folder on CENGN server which now has the build > from March 6^th . He asked a question on the mailing list, but I did > not see an answer yet. Can you please help with this issue? Something > must have gotten broken. > > Toate cele bune/Kind regards/Mit freundlichen > Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem > > よろしくお願いいたします > > 此致 > > 敬礼 > > Mihail-Laurenţiu Trică, Software Engineer > > *From:* Demezzi, Marco > *Sent:* Monday, March 16, 2020 6:01 PM > *To:* Trica, Mihail-Laurentiu >; Bruecher, Bjoern > >; > iotg_starlingx_validation > > *Cc:* Wagner, Marcel >; Shashi, Yatindra > > > *Subject:* RE: [Starlingx-discuss] Sanity Master Test MONOLITHIC build > - ISO 20200313 > > Hi Mihail, > > It would be good to understand why this has not been happening after > March.6^th , maybe some automated mechanism is broken > > Regards, > > Marco > > *From:* Trica, Mihail-Laurentiu > > *Sent:* Monday, March 16, 2020 4:59 PM > *To:* Demezzi, Marco >; Bruecher, Bjoern > >; > iotg_starlingx_validation > > *Cc:* Wagner, Marcel >; Shashi, Yatindra > > > *Subject:* RE: [Starlingx-discuss] Sanity Master Test MONOLITHIC build > - ISO 20200313 > > Hello, > > I have already had a discussion with Bjoern. We are not in charge of > the CENGN builds or the build machine. I advised Bjoern to ask the > community, this is the best way to get information (and the proper way > too). We have to wait until someone has information and comes forward > with it. > > Toate cele bune/Kind regards/Mit freundlichen > Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem > > よろしくお願いいたします > > 此致 > > 敬礼 > > Mihail-Laurenţiu Trică, Software Engineer > > *From:* Demezzi, Marco > *Sent:* Monday, March 16, 2020 5:55 PM > *To:* Bruecher, Bjoern >; iotg_starlingx_validation > > > *Cc:* Wagner, Marcel >; Shashi, Yatindra > >; Trica, > Mihail-Laurentiu > > *Subject:* RE: [Starlingx-discuss] Sanity Master Test MONOLITHIC build > - ISO 20200313 > > Hey Bjoern, > > The validation is team is new and probably nobody told them this is a > task they had to perform. Great that you tell us this is a gap. > > @Mihail: can you please follow up with Nic & Ada on this point to > understand where the gap is? > > Regards, > > Marco > > *From:* Bruecher, Bjoern > > *Sent:* Monday, March 16, 2020 4:19 PM > *To:* iotg_starlingx_validation > > *Cc:* Wagner, Marcel >; Shashi, Yatindra > >; Trica, > Mihail-Laurentiu > > *Subject:* RE: [Starlingx-discuss] Sanity Master Test MONOLITHIC build > - ISO 20200313 > > Hi, > > Are we no longer labeling making the latest GREEN build available here > > as in the past? The lasted “GREEN” build in that folder is from March > 6^th . All validated builds > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/202003xxxx/outputs/ > do not include a file called “GREEN“ which might have been used as a > validation stamp and triggered the copy in the past. Can we get this > flag back so we know the validation status? > > We are using the file named “GREEN” as a trigger for downloading your > validated ISO image to our cluster. > > Thanks, > > Bjoern > > *From:* Trica, Mihail-Laurentiu > > *Sent:* Friday, March 13, 2020 13:54 > *To:* starlingx-discuss at lists.starlingx.io > > *Subject:* [Starlingx-discuss] Sanity Master Test MONOLITHIC build - > ISO 20200313 > > *Status of the Sanity Test for last CENGN ISO: */bootimage.iso from > 2020-March-13 /(link > ) > > Status:*GREEN* > > =========================================== > > Sanity Test is executed in a /_Containers – Bare Metal Environment_/ > > *AIO – Simplex* > > Setup                                 04 TCs [PASS] > > Provisioning                     01 TCs [PASS] > > Sanity OpenStack            49 TCs [PASS] > > Sanity Platform               07 TCs [PASS] > > TOTAL: [ 61 TCs ] > > *AIO – Duplex* > > Setup                                 04 TCs [PASS] > > Provisioning                     01 TCs [PASS] > > Sanity OpenStack            52 TCs [PASS] > > Sanity Platform                07 TCs [PASS] > > TOTAL: [ 64 TCs ] > > *Standard - Local Storage (2+2)* > > Setup  04 TCs [PASS] > > Provisioning                      01 TCs [PASS] > > Sanity OpenStack             52 TCs [PASS] > > Sanity Platform                 08 TCs [PASS] > > TOTAL: [ 65 TCs ] > > *Standard External - Dedicated Storage (2+2+2)* > > Setup 04 TCs [PASS] > > Provisioning                     01 TCs [PASS] > > Sanity OpenStack            52 TCs [PASS] > > Sanity Platform                09 TCs [PASS] > > TOTAL: [ 66 TCs ] > > =========================================== > > Sanity Test is executed in a /_Containers – 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 ] > > *AIO – Duplex* > > Setup                                 04 TCs [PASS] > > Provisioning                     01 TCs [PASS] > > Sanity OpenStack            52 TCs [PASS] > > Sanity Platform                07 TCs [PASS] > > TOTAL: [ 64 TCs ] > > *Standard -  Storage (2+2)* > > Setup 04 TCs [PASS] > > Provisioning                     01 TCs [PASS] > > Sanity OpenStack            52 TCs [PASS] > > Sanity Platform                08 TCs [PASS] > > TOTAL: [ 65 TCs ] > > Standard external setup in the virtual environment failed because of > an automation issue (the corresponding job on bare metal was successful). > > Regards, > > STX Validation Team > > Toate cele bune/Kind regards/Mit freundlichen > Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem > > よろしくお願いいたします > > 此致 > > 敬礼 > > *Mihail-Laurenţiu Trică*, Software Engineer > > Intel Deutschland GmbH > Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany > Tel: +49 89 99 8853-0, www.intel.de > Managing Directors: Christin Eisenschmid, Gary Kershaw > Chairperson of the Supervisory Board: Nicole Lau > Registered Office: Munich > Commercial Register: Amtsgericht Muenchen HRB 186928 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Mar 25 19:03:03 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 25 Mar 2020 19:03:03 +0000 Subject: [Starlingx-discuss] [tsc] Repo for CNCF landscape In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BFB06DF86@fmsmsx123.amr.corp.intel.com> +1 from me. Thank you for pushing this through! brucej -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: Wednesday, March 25, 2020 11:52 AM To: starlingx Subject: [Starlingx-discuss] [tsc] Repo for CNCF landscape Hi, As the community decided to go through CNCF conformance process I have a PR open for StarlingX: https://github.com/cncf/k8s-conformance/pull/891 I got one last minor comment to fix which I wanted to confirm with you which is the following: “In order to show as open source on the Cloud Native landscape, you'd have to pick one repo to use. People normally use either the main code or an installer.” The review comment suggests the config repo (https://github.com/starlingx/config). Would the TSC and the community agree with that pick or you have another preference? Thanks, Ildikó _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From zhipengs.liu at intel.com Thu Mar 26 01:38:38 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 26 Mar 2020 01:38:38 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. In-Reply-To: References: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314F6B2@SHSMSX104.ccr.corp.intel.com> , , , Message-ID: But this place has already been changed in my patch https://review.opendev.org/714894 Zhipeng From: Richard, Joseph Sent: 2020年3月25日 22:08 To: Liu, ZhipengS Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. I see at least one place [1] where keystone is configured to listen on 0.0.0.0, so that's probably why. [1] https://github.com/openstack/openstack-helm/blob/master/keystone/values.yaml#L949 ________________________________ From: Liu, ZhipengS > Sent: Wednesday, March 25, 2020 5:19 AM To: Richard, Joseph > Cc: starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Josesh, I have added 2 more patches for your review. https://review.opendev.org/714894 https://review.opendev.org/714898 So far, it can deploy services until heat. But I still have an intermittent issue that ***-ks-user jobs always need restart several times to get task finished. Sometimes, it may cause endpoint job failure and block deployment procedure. Log looks like below, still not find the root cause. Could you help on this point? Thanks! Failed to discover available identity versions when contacting http://keystone-api.openstack.svc.cluster.local:5000/v3. Attempting to parse version from URL. Unable to establish connection to http://keystone-api.openstack.svc.cluster.local:5000/v3/auth/tokens: HTTPConnectionPool(host='keystone-api.openstack.svc.cluster.local', port=5000): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 101] Network is unreachable',)) Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月23日 21:50 To: 'Richard, Joseph' > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, I have updated my 2 patches, both tested on ipv4 and ipv6 setup. https://review.opendev.org/#/c/714034/ https://review.opendev.org/#/c/714038/ But still failed when deploy keystone, glance, cinder later. Common failure causes are found that need to bind host to :: instead of 0.0.0.0. Otherwise, it will only bind port to ipv4 address, which causes db connect failure or pod probe failure. After below changes, it can run until deploying cinder. 1)Change mariadb value.yaml conf: bind adress from 0.0.0.0 to :: 2) Change keystone value.yaml wsgi_keystone: | {{- $portInt := tuple "identity" "internal" "api" $ | include "helm-toolkit.endpoints.endpoint_port_lookup" }} Listen 0.0.0.0:{{ $portInt }} change to Listen :::{{ $portInt }} 3) Change glance value.yaml Conf.Default: add bind_host = "::" I have to check these services deploy one by one. Thanks! Zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Thu Mar 26 06:54:47 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 26 Mar 2020 06:54:47 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. In-Reply-To: References: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C75314F6B2@SHSMSX104.ccr.corp.intel.com> , , , Message-ID: Hi Joseph and all, So far, OpenStack can be deployed successfully in my ipv6 simplex setup! I have fixed the intermittent issue I mentioned below. Need to increase process from 1 to 5 for wsgi_keystone! 2 related patches under review, test pass on both ipv4 and ipv6 simplex setup. https://review.opendev.org/714894 https://review.opendev.org/714898 Appreciate for your comment! Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月26日 9:39 To: Richard, Joseph Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. But this place has already been changed in my patch https://review.opendev.org/714894 Zhipeng From: Richard, Joseph > Sent: 2020年3月25日 22:08 To: Liu, ZhipengS > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. I see at least one place [1] where keystone is configured to listen on 0.0.0.0, so that's probably why. [1] https://github.com/openstack/openstack-helm/blob/master/keystone/values.yaml#L949 ________________________________ From: Liu, ZhipengS > Sent: Wednesday, March 25, 2020 5:19 AM To: Richard, Joseph > Cc: starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Josesh, I have added 2 more patches for your review. https://review.opendev.org/714894 https://review.opendev.org/714898 So far, it can deploy services until heat. But I still have an intermittent issue that ***-ks-user jobs always need restart several times to get task finished. Sometimes, it may cause endpoint job failure and block deployment procedure. Log looks like below, still not find the root cause. Could you help on this point? Thanks! Failed to discover available identity versions when contacting http://keystone-api.openstack.svc.cluster.local:5000/v3. Attempting to parse version from URL. Unable to establish connection to http://keystone-api.openstack.svc.cluster.local:5000/v3/auth/tokens: HTTPConnectionPool(host='keystone-api.openstack.svc.cluster.local', port=5000): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 101] Network is unreachable',)) Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月23日 21:50 To: 'Richard, Joseph' > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Hi Joseph, I have updated my 2 patches, both tested on ipv4 and ipv6 setup. https://review.opendev.org/#/c/714034/ https://review.opendev.org/#/c/714038/ But still failed when deploy keystone, glance, cinder later. Common failure causes are found that need to bind host to :: instead of 0.0.0.0. Otherwise, it will only bind port to ipv4 address, which causes db connect failure or pod probe failure. After below changes, it can run until deploying cinder. 1)Change mariadb value.yaml conf: bind adress from 0.0.0.0 to :: 2) Change keystone value.yaml wsgi_keystone: | {{- $portInt := tuple "identity" "internal" "api" $ | include "helm-toolkit.endpoints.endpoint_port_lookup" }} Listen 0.0.0.0:{{ $portInt }} change to Listen :::{{ $portInt }} 3) Change glance value.yaml Conf.Default: add bind_host = "::" I have to check these services deploy one by one. Thanks! Zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Mar 26 08:29:58 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 26 Mar 2020 04:29:58 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 162 - Failure! Message-ID: <630587006.1091.1585211406463.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 162 Status: Failure Timestamp: 20200326T081712Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200326T080237Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200326T080237Z DOCKER_BUILD_ID: jenkins-master-flock-20200326T080237Z-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/20200326T080237Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200326T080237Z/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 Thu Mar 26 08:30:08 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 26 Mar 2020 04:30:08 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 58 - Still Failing! In-Reply-To: <988340026.1081.1585124946348.JavaMail.javamailuser@localhost> References: <988340026.1081.1585124946348.JavaMail.javamailuser@localhost> Message-ID: <2131097064.1094.1585211409987.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 58 Status: Still Failing Timestamp: 20200326T080237Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200326T080237Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: false From abhideodhar at gmail.com Thu Mar 26 15:24:48 2020 From: abhideodhar at gmail.com (Abhijit Deodhar) Date: Thu, 26 Mar 2020 20:54:48 +0530 Subject: [Starlingx-discuss] Disaster recovery in StarlingX Message-ID: Does StarlingX have a disaster recovery feature between two StarlingX clusters? I couldn't find info on it in the documentation...any plans of adding it in the future? Regards Abhijit -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Thu Mar 26 18:51:28 2020 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 26 Mar 2020 11:51:28 -0700 Subject: [Starlingx-discuss] error access docker registry.. TLS handshake issue In-Reply-To: <9A85D2917C58154C960D95352B22818BF1698EEC@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BF1698EEC@fmsmsx123.amr.corp.intel.com> Message-ID: <53b3e5f4-d531-905d-26ed-54dedf9abd49@linux.intel.com> Folks, Can anyone help with moving this question forward? I understand from the user that they are adding additional certificates in order to enable their proxy connections. I am not sure if this is part of the problem with the TLS Handshake or not. Thanks Sau! On 3/20/20 8:05 AM, Jones, Bruce E wrote: > We have a user who is hitting this error.  Any idea what might be going on? > > TASK [common/push-docker-images : Log in to local registry] > ******************************************************************************************************************************************************** > > fatal: [localhost]: FAILED! => {"changed": false, "msg": "Logging into > registry.local:9001 for user admin failed - 500 Server Error: Internal > Server Error (\"Get https://registry.local:9001/v2/: Get > https://192.168.204.1:9002/token/?account=admin&client_id=docker&offline_token=true&service=192.168.204.1%3A9001: > net/http: TLS handshake timeout\")"} > > Thanks! > >              brucej > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From nicolae.jascanu at intel.com Thu Mar 26 19:27:19 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Thu, 26 Mar 2020 19:27:19 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC Message-ID: Sanity Test from 2020-March-25 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200326T013013Z/outputs/iso/) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 ] AIO - Duplex [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Regards, STX Validation Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Fri Mar 27 00:00:52 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Fri, 27 Mar 2020 00:00:52 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-03-25 Message-ID: Hello all, Here are this week's docs team meeting minutes. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2020-03-25 * All -- reviews merged since last week: 0 * All -- bug status -- no change * All -- R4 target content: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.4.0&project_id=1046 * Windows Active Dir content -- Review available: https://review.opendev.org/#/c/712111/ * Upgrade Kubernetes version -- Review available: https://review.opendev.org/#/c/712583/ * Assignment of R4 doc tasks ? These stories have no assigned person: * https://storyboard.openstack.org/#!/story/2006770 (How to use Backup & Restore) AR Mary ping Frank Miller . * https://storyboard.openstack.org/#!/story/2007223 (update build guide w/ layered build info) SME Scott Little but too busy at the moment. Wait a while. * https://storyboard.openstack.org/#!/story/2007222 (update dist cloud bare metal install w/ redfish info) AR Mary check discuss archive, may be covered already? If not ask Tao Liu. * https://storyboard.openstack.org/#!/story/2006588 (updates for Dist Cloud) AR Mary ask Dariush (reference the story). Do we need doc updates? * All -- Opens * Greg: Bill Z asked how do we want to receive input? Discuss email list is pretty generic, things can get lost. * Raise a launchpad (bug tracking system) - this has a record, becomes a task assignment. << We like this option best, but will take input in any form. * Brucej -- Intel / GEHC Edison recurring sync call email. 3rd menu is disabled per Saul. Greg confirmed. AR Mary delete "third menu" step in R3 and R4 install guides. * Brucej -- let's discuss Ildiko's email, esp. network documentation (STX feedback): http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008088.html ? AR Greg to make a story - ask for help from networking team. We need overview of how to configure networking in STX. ? Mapping between STX networking, how we differ from OpenStack behavior, then point to OpenStack for more details. * Mary updated team page on the wiki, let's confirm: https://wiki.openstack.org/wiki/StarlingX/Docs_and_Infra AR Mary add Bart. * All -- Wiki status ? Virtual Box wiki converted to RST file. Review available: https://review.opendev.org/#/c/711769/ * New reviews submitted: ? https://review.opendev.org/#/c/714762/ Ritu Raj - adds text and diagrams to improve AIO Simplex installation. AR Mary follow up. ? https://review.opendev.org/#/c/714821/ Mary - Certificate config and management * New topics for us to document. Both are coming from Intel field teams supporting customers (brucej) ? AR Mary send email to folks Ghada pointed to. Asking for help on these topics: * High availability and failover mechanisms for applications and for SM. * Networking - how to bridge / combine K8S and OpenStack networks for applications * All -- Changes needed? * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007847.html - possible Ceph storage updates needed? ? AR Mary update doc. Greg sent additional language to add to section "Config controller-0" step 4. Step 6 same section is OK now. * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007891.html - asking for more detail on AIO Simplex install. No update this week. * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/007918.html - possible build guide updates needed? [[didn't discuss yet]] -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Fri Mar 27 00:05:04 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 27 Mar 2020 00:05:04 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meetng - Mar 26/2020 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.4.0 - Milestone-2 re-scheduled to next week (April 7) - Review readiness against criteria - Spec freeze; no new specs accepted for the release. The focus is on closing current specs - There are currently 3 specs that are still in progress. These will continue as per plan and aren't impacted by the milestone criteria - StarlingX Upgrades - N3000 FPGA Image Update Orchestration - Cert-Manager - Intel team is looking at some new feature proposals, but these will likely be for stx.5.0 - Small Footprint spec would fall into this category - WR team is also looking at some security-related items which were discussed in the face-to-face meeting - The scope of these are fairly small - small config changes. - We can also entertain an exception if something comes up - For this criterion, team feels comfortable to move forward with the milestone - Feature plans defined and feature development well underway - Summary: - In / Ongoing: 20 - Out: 10 - TBD: 5 - Feature Plans: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 - For this criterion, team feels comfortable that we have enough content secured for the release to move forward with the milestone - Release test plan defined - including test automation deliverables - Feature Test - Risk is around environment setup in Romainia. In the meantime, the team is focused on test plan definition and perhaps virtual configuration. - Action: Test team to finalize plans in the next test team; including assumptions and risks. Fcst: April - Regression Test - Regression duration for stx.3.0 was around 6wks. The current plan for stx.4.0 shows around 7wks; assuming testing can start on April 27. - Risk is around the majority of the Intel test team being new to the project and requiring ramp. - Most training with the Mexico team has been focused on daily sanity and not the detailed regression - Agreed to re-schedule the milestone by a week to refine the release test plan From yong.hu at intel.com Fri Mar 27 00:50:49 2020 From: yong.hu at intel.com (Hu, Yong) Date: Fri, 27 Mar 2020 00:50:49 +0000 Subject: [Starlingx-discuss] Disaster recovery in StarlingX In-Reply-To: References: Message-ID: <8389AE6A-31D3-414D-AE6C-ADABC77D1E73@intel.com> Hi Abhijit, Could you describe a bit more about the disaster recovery? What are your use cases? We have some designs about the high availability, under several circumstances: 1. If some “worker” (compute) node goes down, the workloads (VMs) or K8S pods could be migrated to other available worker nodes. 2. If one of storage node goes down, the data in Ceph cluster will keep uncorrupted, thanks to the replications in other storage nodes. 3. If one controller goes down, the other one will take over the active responsibility, to sustain the system working, though with fault warnings. However, if both controllers are shutdown, the StarlingX cluster will not stand it anymore. Mostly these are “software” features. With regard to the HW, it relies on your servers in my opinion. Regards, Yong From: Abhijit Deodhar Date: Thursday, March 26, 2020 at 11:26 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Disaster recovery in StarlingX Does StarlingX have a disaster recovery feature between two StarlingX clusters? I couldn't find info on it in the documentation...any plans of adding it in the future? Regards Abhijit -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Fri Mar 27 01:32:28 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 26 Mar 2020 21:32:28 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 489 - Failure! Message-ID: <557779028.1103.1585272749235.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 489 Status: Failure Timestamp: 20200327T013010Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200327T013010Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From sgw at linux.intel.com Fri Mar 27 02:10:35 2020 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 26 Mar 2020 19:10:35 -0700 Subject: [Starlingx-discuss] enable pbr version In-Reply-To: <20200325172603.t33y4xjf5qxiguff@yuggoth.org> References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> <20200325172603.t33y4xjf5qxiguff@yuggoth.org> Message-ID: <1be79137-b909-f750-f218-736973144bd9@linux.intel.com> Yipeng, I want to double check you are just testing the current gerrit review you have in the GUI repo? Do you have any other changes to that review that you have not pushed? I am trying to recreate this and want to be sure I ahve the latest. Sau! On 3/25/20 10:26 AM, Jeremy Stanley wrote: > On 2020-03-25 14:11:51 +0000 (+0000), Penney, Don wrote: > [...] >> Looking further through the build.log, there’s the following: >> + /usr/bin/python2 setup.py install -O1 --skip-build --root /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64 >> /usr/lib/python2.7/site-packages/setuptools/dist.py:355: UserWarning: Normalizing '2.9999.9999.rc1.dev23' to '2.9999.9999rc1.dev23' >> normalized_version, >> running install >> >> Maybe the python build only allows 4 version components? > [...] > > The number of components is not the problem. If you want that rc1 to > be a separate component it needs to be 2.9999.9999.0rc1.dev23 since > PEP 440 normalization considers 2.9999.9999rc1.dev23 to be the > canonical form of 2.9999.9999.rc1.dev23 and Setuptools is therefore > correcting it for you: > > https://www.python.org/dev/peps/pep-0440/#pre-release-separators > Thanks for this clarification. > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From yipeng.he at jitstack.com Fri Mar 27 02:26:17 2020 From: yipeng.he at jitstack.com (=?utf-8?B?5L2V5LmJ6bmP?=) Date: Fri, 27 Mar 2020 10:26:17 +0800 Subject: [Starlingx-discuss] enable pbr version In-Reply-To: References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> Message-ID: Yes, building the rpm of the starlingx dashboard is a necessary step for my build-iso. Maybe Saul can respond to the question that python builds allow several versions of components. ------------------ Original ------------------ From:  "Penney, Don" From abhideodhar at gmail.com Fri Mar 27 05:01:45 2020 From: abhideodhar at gmail.com (Abhijit Deodhar) Date: Fri, 27 Mar 2020 10:31:45 +0530 Subject: [Starlingx-discuss] Disaster recovery in StarlingX In-Reply-To: <8389AE6A-31D3-414D-AE6C-ADABC77D1E73@intel.com> References: <8389AE6A-31D3-414D-AE6C-ADABC77D1E73@intel.com> Message-ID: Yong, Thanks for the information. The HA aspect of StarlingX looks solid. My question is w.r.t. an entire cluster/site failure... is there a way to recover data in such scenarios either by means of a snapshot or bringing up a backup copy as the live one in case of a site disaster? Regards Abhijit On Fri, Mar 27, 2020 at 6:20 AM Hu, Yong wrote: > Hi Abhijit, > > Could you describe a bit more about the disaster recovery? What are your > use cases? > > We have some designs about the high availability, under several > circumstances: > > 1. If some “worker” (compute) node goes down, the workloads (VMs) or > K8S pods could be migrated to other available worker nodes. > 2. If one of storage node goes down, the data in Ceph cluster will > keep uncorrupted, thanks to the replications in other storage nodes. > 3. If one controller goes down, the other one will take over the > active responsibility, to sustain the system working, though with fault > warnings. However, if both controllers are shutdown, the StarlingX cluster > will not stand it anymore. > > > > Mostly these are “software” features. With regard to the HW, it relies on > your servers in my opinion. > > > > Regards, > > Yong > > *From: *Abhijit Deodhar > *Date: *Thursday, March 26, 2020 at 11:26 PM > *To: *"starlingx-discuss at lists.starlingx.io" < > starlingx-discuss at lists.starlingx.io> > *Subject: *[Starlingx-discuss] Disaster recovery in StarlingX > > > > Does StarlingX have a disaster recovery feature between two StarlingX > clusters? I couldn't find info on it in the documentation...any plans of > adding it in the future? > > > > Regards > > Abhijit > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Fri Mar 27 05:36:19 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 27 Mar 2020 05:36:19 +0000 Subject: [Starlingx-discuss] Disaster recovery in StarlingX In-Reply-To: References: <8389AE6A-31D3-414D-AE6C-ADABC77D1E73@intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C7663977582@SHSMSX104.ccr.corp.intel.com> Hi Abhijit, STX supports “Backup and Restore” feature. Here is the details of the feature: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006419.html Best Regards Shuicheng From: Abhijit Deodhar Sent: Friday, March 27, 2020 1:02 PM To: Hu, Yong Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Disaster recovery in StarlingX Yong, Thanks for the information. The HA aspect of StarlingX looks solid. My question is w.r.t. an entire cluster/site failure... is there a way to recover data in such scenarios either by means of a snapshot or bringing up a backup copy as the live one in case of a site disaster? Regards Abhijit On Fri, Mar 27, 2020 at 6:20 AM Hu, Yong > wrote: Hi Abhijit, Could you describe a bit more about the disaster recovery? What are your use cases? We have some designs about the high availability, under several circumstances: 1. If some “worker” (compute) node goes down, the workloads (VMs) or K8S pods could be migrated to other available worker nodes. 2. If one of storage node goes down, the data in Ceph cluster will keep uncorrupted, thanks to the replications in other storage nodes. 3. If one controller goes down, the other one will take over the active responsibility, to sustain the system working, though with fault warnings. However, if both controllers are shutdown, the StarlingX cluster will not stand it anymore. Mostly these are “software” features. With regard to the HW, it relies on your servers in my opinion. Regards, Yong From: Abhijit Deodhar > Date: Thursday, March 26, 2020 at 11:26 PM To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] Disaster recovery in StarlingX Does StarlingX have a disaster recovery feature between two StarlingX clusters? I couldn't find info on it in the documentation...any plans of adding it in the future? Regards Abhijit -------------- next part -------------- An HTML attachment was scrubbed... URL: From abhideodhar at gmail.com Fri Mar 27 06:01:10 2020 From: abhideodhar at gmail.com (Abhijit Deodhar) Date: Fri, 27 Mar 2020 11:31:10 +0530 Subject: [Starlingx-discuss] App upgrades in StarlingX Message-ID: Hi, Does StarlingX provide any mechanism for zero-touch management of applications? for example: in order to support the CI/CD pipeline, if a developer wants to upgrade an existing app in StarlingX, what is the workflow? Also - is there a secure way to deploy the patch for the application? Regards Abhijit -------------- next part -------------- An HTML attachment was scrubbed... URL: From abhideodhar at gmail.com Fri Mar 27 06:03:53 2020 From: abhideodhar at gmail.com (Abhijit Deodhar) Date: Fri, 27 Mar 2020 11:33:53 +0530 Subject: [Starlingx-discuss] Disaster recovery in StarlingX In-Reply-To: <9700A18779F35F49AF027300A49E7C7663977582@SHSMSX104.ccr.corp.intel.com> References: <8389AE6A-31D3-414D-AE6C-ADABC77D1E73@intel.com> <9700A18779F35F49AF027300A49E7C7663977582@SHSMSX104.ccr.corp.intel.com> Message-ID: Thanks a lot for the link - its what I was looking for. Regards Abhijit On Fri, Mar 27, 2020 at 11:06 AM Lin, Shuicheng wrote: > Hi Abhijit, > > STX supports “Backup and Restore” feature. > > Here is the details of the feature: > > > http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006419.html > > > > Best Regards > > Shuicheng > > > > *From:* Abhijit Deodhar > *Sent:* Friday, March 27, 2020 1:02 PM > *To:* Hu, Yong > *Cc:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Disaster recovery in StarlingX > > > > Yong, > > > > Thanks for the information. The HA aspect of StarlingX looks solid. > > > > My question is w.r.t. an entire cluster/site failure... is there a way to > recover data in such scenarios either by means of a snapshot or bringing up > a backup copy as the live one in case of a site disaster? > > > > Regards > > Abhijit > > > > On Fri, Mar 27, 2020 at 6:20 AM Hu, Yong wrote: > > Hi Abhijit, > > Could you describe a bit more about the disaster recovery? What are your > use cases? > > We have some designs about the high availability, under several > circumstances: > > 1. If some “worker” (compute) node goes down, the workloads (VMs) or > K8S pods could be migrated to other available worker nodes. > 2. If one of storage node goes down, the data in Ceph cluster will > keep uncorrupted, thanks to the replications in other storage nodes. > 3. If one controller goes down, the other one will take over the > active responsibility, to sustain the system working, though with fault > warnings. However, if both controllers are shutdown, the StarlingX cluster > will not stand it anymore. > > > > Mostly these are “software” features. With regard to the HW, it relies on > your servers in my opinion. > > > > Regards, > > Yong > > *From: *Abhijit Deodhar > *Date: *Thursday, March 26, 2020 at 11:26 PM > *To: *"starlingx-discuss at lists.starlingx.io" < > starlingx-discuss at lists.starlingx.io> > *Subject: *[Starlingx-discuss] Disaster recovery in StarlingX > > > > Does StarlingX have a disaster recovery feature between two StarlingX > clusters? I couldn't find info on it in the documentation...any plans of > adding it in the future? > > > > Regards > > Abhijit > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Fri Mar 27 07:49:28 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 27 Mar 2020 07:49:28 +0000 Subject: [Starlingx-discuss] error access docker registry.. TLS handshake issue In-Reply-To: <53b3e5f4-d531-905d-26ed-54dedf9abd49@linux.intel.com> References: <9A85D2917C58154C960D95352B22818BF1698EEC@fmsmsx123.amr.corp.intel.com> <53b3e5f4-d531-905d-26ed-54dedf9abd49@linux.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C76639776D1@SHSMSX104.ccr.corp.intel.com> Hi Saul, If possible, please ask the user to help provide the whole ansible.log and /var/log/daemon.log. From the log it seems docker fail to login to registry.local. Here is some debug method: 1. Try to login with docker cmd, username is "admin", password is "admin_password" defined in localhost.yml: controller-0:~$ sudo docker login registry.local:9001 Username: admin Password: ...... Login Succeeded 2. If cannot login success, have a check with docker proxy setting in /etc/systemd/system/docker.service.d/http-proxy.conf "registry.local" should be at NO_PROXY line like below: controller-0:/home/sysadmin# cat /etc/systemd/system/docker.service.d/http-proxy.conf [Service] Environment="HTTP_PROXY=PROXY_XXX" Environment="HTTPS_PROXY=PROXY_XXX " Environment="NO_PROXY=localhost,127.0.0.1,registry.local,10.96.0.1,192.188.204.2,192.188.204.3,192.192.192.2,192.192.192.3,192.188.204.4,192.192.192.4,registry.dcp-dev.intel.com" Best Regards Shuicheng -----Original Message----- From: Saul Wold Sent: Friday, March 27, 2020 2:51 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] error access docker registry.. TLS handshake issue Folks, Can anyone help with moving this question forward? I understand from the user that they are adding additional certificates in order to enable their proxy connections. I am not sure if this is part of the problem with the TLS Handshake or not. Thanks Sau! On 3/20/20 8:05 AM, Jones, Bruce E wrote: > We have a user who is hitting this error.  Any idea what might be going on? > > TASK [common/push-docker-images : Log in to local registry] > ********************************************************************** > ********************************************************************** > ************ > > fatal: [localhost]: FAILED! => {"changed": false, "msg": "Logging into > registry.local:9001 for user admin failed - 500 Server Error: Internal > Server Error (\"Get https://registry.local:9001/v2/: Get > https://192.168.204.1:9002/token/?account=admin&client_id=docker&offline_token=true&service=192.168.204.1%3A9001: > net/http: TLS handshake timeout\")"} > > Thanks! > >              brucej > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From shuicheng.lin at intel.com Fri Mar 27 07:54:34 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 27 Mar 2020 07:54:34 +0000 Subject: [Starlingx-discuss] App upgrades in StarlingX In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C7663977707@SHSMSX104.ccr.corp.intel.com> Hi Abhijit, Host module upgrade is supported by “patch” in StarlingX. You could have a check with below link: https://docs.starlingx.io/developer_resources/starlingx_patching.html Best Regards Shuicheng From: Abhijit Deodhar Sent: Friday, March 27, 2020 2:01 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] App upgrades in StarlingX Hi, Does StarlingX provide any mechanism for zero-touch management of applications? for example: in order to support the CI/CD pipeline, if a developer wants to upgrade an existing app in StarlingX, what is the workflow? Also - is there a secure way to deploy the patch for the application? Regards Abhijit -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jolliffe at windriver.com Fri Mar 27 13:10:26 2020 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Fri, 27 Mar 2020 13:10:26 +0000 Subject: [Starlingx-discuss] [tsc] Repo for CNCF landscape In-Reply-To: <9A85D2917C58154C960D95352B22818BFB06DF86@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BFB06DF86@fmsmsx123.amr.corp.intel.com> Message-ID: Agreed +1 from me. Makes sense. Thanks; Ian On 2020-03-25, 3:04 PM, "Jones, Bruce E" wrote: +1 from me. Thank you for pushing this through! brucej -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: Wednesday, March 25, 2020 11:52 AM To: starlingx Subject: [Starlingx-discuss] [tsc] Repo for CNCF landscape Hi, As the community decided to go through CNCF conformance process I have a PR open for StarlingX: https://github.com/cncf/k8s-conformance/pull/891 I got one last minor comment to fix which I wanted to confirm with you which is the following: “In order to show as open source on the Cloud Native landscape, you'd have to pick one repo to use. People normally use either the main code or an installer.” The review comment suggests the config repo (https://github.com/starlingx/config). Would the TSC and the community agree with that pick or you have another preference? Thanks, Ildikó _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Fri Mar 27 14:58:08 2020 From: scott.little at windriver.com (Scott Little) Date: Fri, 27 Mar 2020 10:58:08 -0400 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 489 - Failure! In-Reply-To: <557779028.1103.1585272749235.JavaMail.javamailuser@localhost> References: <557779028.1103.1585272749235.JavaMail.javamailuser@localhost> Message-ID: <5bf49f44-c286-580a-97ea-98f0348b7241@windriver.com> Several jobs last night had problems downloading from opendev.org. Scott On 2020-03-26 9:32 p.m., build.starlingx at gmail.com wrote: > Project: STX_build_master_master > Build #: 489 > Status: Failure > Timestamp: 20200327T013010Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200327T013010Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: false > FORCE_BUILD: true > > _______________________________________________ > 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 nicolae.jascanu at intel.com Fri Mar 27 18:10:01 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Fri, 27 Mar 2020 18:10:01 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED Message-ID: Sanity Test from 2020-March-26 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200326T163133Z/) Status: RED We were not able to run the sanity tests due to an internal infrastructure issue related to our local docker mirror registry. We are working at fixing the issue. We will restart the validation on Sunday. Regards, STX Validation Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From allison at openstack.org Fri Mar 27 18:17:42 2020 From: allison at openstack.org (Allison Price) Date: Fri, 27 Mar 2020 13:17:42 -0500 Subject: [Starlingx-discuss] How to Contribute to the StarlingX Blog & Superuser Magazine Message-ID: <34C2C518-5F64-4C21-AE76-CBEF5E19B6D6@openstack.org> Hi everyone, Apologies for missing the StarlingX community marketing call last week. I synced with Ildiko and think that there are a lot of great ideas to gain more visibility for what the community is doing. Accompanied by the amount of events that have been transformed to virtual experiences, we have been working on ways for the community to centrally share learnings online, and create a place where the community can send software and overall community updates. Here’s how you can contribute: StarlingX Blog  The StarlingX blog is a great place for updates that are more related to the software releases, including bug fixes or changes that may affect users who are running StarlingX in production. By putting it on the blog—even if it’s a short update—the content lasts much longer and is easier to find by users and contributors. Once you have an idea of what you would like to write, you can submit a pull request here . If you have questions or want to share your idea before drafting, please email info at starlingx.io . We can also keep track of a running list of ideas / calls for content for people who have questions that would be great to get answered on the blog. Superuser Superuser has evolved to cover the open infrastructure landscape covering different use cases and open source projects. Whether it’s a video or an article, this content is typically more in depth than what you would see on a project blog and includes things like hands on tutorials, case studies, thought leadership articles, Q&As with open source community leaders, and updates and highlights from open source events around the world. If you have an idea you would like to share, fill out this form and the editorial team will reach out. If you have questions about whether your topic is the right fit, email editor at openstack.org . You can also attend the OSF community meeting next week to learn more about how you can get involved and contribute! Thanks! Allison Allison Price OpenStack Foundation allison at openstack.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Fri Mar 27 23:02:32 2020 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 27 Mar 2020 16:02:32 -0700 Subject: [Starlingx-discuss] enable pbr version In-Reply-To: References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> Message-ID: <21008692-fe6b-3b65-ab7a-70b80f73ce78@linux.intel.com> Yipeng, I replied the other day, wanting to confirm if you have any additional changes in your local git repo? It seems that we need to consider a couple of options to possibly "pre-tag" 4.0 or use the "Sem_Ver: feature" tag in a commit to move the pbr versioning forward. BUILD Team (Don, Scott, Frank): Here's the general issue, we tag on the release branches, not master (although we have a v3.0.0.rc0 tag on master), we need to either add a Sem_Ver: feature tag to increment version's major number, or add a pre-tag of the 4.0 release. Thoughts from the build team? I think we discussed part of the before, but want to do a quick revisit of the thread back in Nov [1], I think we had agreed to use Sem_Ver but it's not in the email thread [0] http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006790.html On 3/26/20 7:26 PM, 何义鹏 wrote: > > Yes, building the rpm of the starlingx dashboard is a necessary step for > my build-iso. > > Maybe Saul can respond to the question that python builds allow several > versions of components. > Jeremy replied to this earlier in the week, the issue appears to be the way we tagged rc0, we might need to have change our tagging. He also stated that the number of components is not a limiting factor. Sau! > ------------------ Original ------------------ > *From: * "Penney, Don"; > *Date: * Wed, Mar 25, 2020 10:11 PM > *To: * "何义鹏"; "Saul > Wold(sgw at linux.intel.com)"; > *Cc: > * "'starlingx-discuss at lists.starlingx.io'(starlingx-discuss at lists.starlingx.io)"; > > *Subject: * RE: Re:RE: [Starlingx-discuss] enable pbr version > > Please keep starlingx-discuss on the receiver list. > > You had indicated build-iso was failing, but the build.log you provided > appears to be the RPM build log for starlingx-dashboard. > > Processing files: starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.noarch > > error: File not found: > /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9999.9999.rc1.dev23*.egg-info > > RPM build errors: > >     File not found: > /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9999.9999.rc1.dev23*.egg-info > > Child return code was: 1 > > EXCEPTION: [Error()] > > Traceback (most recent call last): > >   File "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", > line 95, in trace > >     result = func(*args, **kw) > >   File "/usr/lib/python3.6/site-packages/mockbuild/util.py", line 746, > in do_with_status > >     raise exception.Error("Command failed: \n # %s\n%s" % (command, > output), child.returncode) > > mockbuild.exception.Error: Command failed: > >  # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps > /builddir/build/SPECS/starlingx-dashboard.spec > > Looking through the build.log, I see the following: > > Copying starlingx_dashboard.egg-info to > build/bdist.linux-x86_64/wheel/starlingx_dashboard-2.9999.9999rc1.dev23-py2.7.egg-info > > So in the build, it’s creating the egg with the version set to > 2.9999.9999rc1.dev23, while the %files is expecting it to be > 2.9999.9999.rc1.dev23. > > Looking further through the build.log, there’s the following: > > + /usr/bin/python2 setup.py install -O1 --skip-build --root > /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64 > > /usr/lib/python2.7/site-packages/setuptools/dist.py:355: UserWarning: > Normalizing '2.9999.9999.rc1.dev23' to '2.9999.9999rc1.dev23' > >   normalized_version, > > running install > > Maybe the python build only allows 4 version components? > > *From:*何义鹏[mailto:yipeng.he at jitstack.com] > *Sent:* Tuesday, March 24, 2020 9:59 PM > *To:* Penney, Don > *Subject:* Re:RE: [Starlingx-discuss] enable pbr version > > Hi Saul, > > I added the error log to the attachment. Do you need other files for > analysis? > > Thank you for your help. > >    yipeng.he! > > ------------------ Original ------------------ > > *From: * "Penney, Don"; > > *Date: * Wed, Mar 25, 2020 04:24 AM > > *To: * "Saul Wold"; "何义鹏"; > > *Cc: * "桂来军"; "杨永金" > ; "曹明晓"; > "starlingx-discuss"; > > *Subject: * RE: [Starlingx-discuss] enable pbr version > > Hi Yipeng, > > Can you provide more info? What was the error you saw from build-iso? > > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Monday, March 23, 2020 6:45 PM > To: 何义鹏 > Cc: 桂来军; 杨永金; 曹明晓; starlingx-discuss > Subject: Re: [Starlingx-discuss] enable pbr version > > > Hi Yipeng, > > I was out last week on vacation, so I am catching up now. > > I think you would have to investigate build-iso and associated scripts > and tools to see if there is an awk, sed or some other command that is > not parsing the extended version.  I have not investigated this further, > that's my initial assessment. > > Can you be more specific about what the error is or provide a log file > of the build-iso process? > > Thanks for working on this project. > >   Sau! > > > > On 3/19/20 12:21 AM, 何义鹏wrote: >> Hello Saul >> >> I'm Yipeng He from JITStack, and I'm taking over the tasks of PBR. >> I encountered the following issue when trying to build iso: >> It fails when the suffix of the version generated by the PBR tool ended >> with number, for instance the building fails if the version id is >> 2.999.9999.rc1.dev23, >> and when I replaced it with 2.999.9999.rc1.dev, the ISO building was >> successful. >> I don't knwo why this happens, could please support and advice the >> solution for this issue. >> >> >> Yipeng.He >> >> _______________________________________________ >> 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 > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Don.Penney at windriver.com Sun Mar 29 18:45:28 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Sun, 29 Mar 2020 18:45:28 +0000 Subject: [Starlingx-discuss] enable pbr version In-Reply-To: <21008692-fe6b-3b65-ab7a-70b80f73ce78@linux.intel.com> References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> <21008692-fe6b-3b65-ab7a-70b80f73ce78@linux.intel.com> Message-ID: So the idea being that when we create a release branch, like r/stx.4.0 for example, we would upversion master and add a SemVer tag to increment it to 5.0.0? I don't have a lot of experience with git tags and semver... if we create a branch at SHA XYZ for r/stx.4.0 and then tag XYZ as 5.0.0, is it possible the r/stx.4.0 branch would see 5.0.0 as the semver (since it has XYZ, which has been tagged)? -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Friday, March 27, 2020 7:03 PM To: 何义鹏; Penney, Don; Little, Scott; Miller, Frank Cc: 曹明晓; 杨永金; 桂来军; starlingx-discuss Subject: Re: [Starlingx-discuss] enable pbr version Yipeng, I replied the other day, wanting to confirm if you have any additional changes in your local git repo? It seems that we need to consider a couple of options to possibly "pre-tag" 4.0 or use the "Sem_Ver: feature" tag in a commit to move the pbr versioning forward. BUILD Team (Don, Scott, Frank): Here's the general issue, we tag on the release branches, not master (although we have a v3.0.0.rc0 tag on master), we need to either add a Sem_Ver: feature tag to increment version's major number, or add a pre-tag of the 4.0 release. Thoughts from the build team? I think we discussed part of the before, but want to do a quick revisit of the thread back in Nov [1], I think we had agreed to use Sem_Ver but it's not in the email thread [0] http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006790.html On 3/26/20 7:26 PM, 何义鹏 wrote: > > Yes, building the rpm of the starlingx dashboard is a necessary step for > my build-iso. > > Maybe Saul can respond to the question that python builds allow several > versions of components. > Jeremy replied to this earlier in the week, the issue appears to be the way we tagged rc0, we might need to have change our tagging. He also stated that the number of components is not a limiting factor. Sau! > ------------------ Original ------------------ > *From: * "Penney, Don"; > *Date: * Wed, Mar 25, 2020 10:11 PM > *To: * "何义鹏"; "Saul > Wold(sgw at linux.intel.com)"; > *Cc: > * "'starlingx-discuss at lists.starlingx.io'(starlingx-discuss at lists.starlingx.io)"; > > *Subject: * RE: Re:RE: [Starlingx-discuss] enable pbr version > > Please keep starlingx-discuss on the receiver list. > > You had indicated build-iso was failing, but the build.log you provided > appears to be the RPM build log for starlingx-dashboard. > > Processing files: starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.noarch > > error: File not found: > /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9999.9999.rc1.dev23*.egg-info > > RPM build errors: > >     File not found: > /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9999.9999.rc1.dev23*.egg-info > > Child return code was: 1 > > EXCEPTION: [Error()] > > Traceback (most recent call last): > >   File "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", > line 95, in trace > >     result = func(*args, **kw) > >   File "/usr/lib/python3.6/site-packages/mockbuild/util.py", line 746, > in do_with_status > >     raise exception.Error("Command failed: \n # %s\n%s" % (command, > output), child.returncode) > > mockbuild.exception.Error: Command failed: > >  # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps > /builddir/build/SPECS/starlingx-dashboard.spec > > Looking through the build.log, I see the following: > > Copying starlingx_dashboard.egg-info to > build/bdist.linux-x86_64/wheel/starlingx_dashboard-2.9999.9999rc1.dev23-py2.7.egg-info > > So in the build, it’s creating the egg with the version set to > 2.9999.9999rc1.dev23, while the %files is expecting it to be > 2.9999.9999.rc1.dev23. > > Looking further through the build.log, there’s the following: > > + /usr/bin/python2 setup.py install -O1 --skip-build --root > /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64 > > /usr/lib/python2.7/site-packages/setuptools/dist.py:355: UserWarning: > Normalizing '2.9999.9999.rc1.dev23' to '2.9999.9999rc1.dev23' > >   normalized_version, > > running install > > Maybe the python build only allows 4 version components? > > *From:*何义鹏[mailto:yipeng.he at jitstack.com] > *Sent:* Tuesday, March 24, 2020 9:59 PM > *To:* Penney, Don > *Subject:* Re:RE: [Starlingx-discuss] enable pbr version > > Hi Saul, > > I added the error log to the attachment. Do you need other files for > analysis? > > Thank you for your help. > >    yipeng.he! > > ------------------ Original ------------------ > > *From: * "Penney, Don"; > > *Date: * Wed, Mar 25, 2020 04:24 AM > > *To: * "Saul Wold"; "何义鹏"; > > *Cc: * "桂来军"; "杨永金" > ; "曹明晓"; > "starlingx-discuss"; > > *Subject: * RE: [Starlingx-discuss] enable pbr version > > Hi Yipeng, > > Can you provide more info? What was the error you saw from build-iso? > > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Monday, March 23, 2020 6:45 PM > To: 何义鹏 > Cc: 桂来军; 杨永金; 曹明晓; starlingx-discuss > Subject: Re: [Starlingx-discuss] enable pbr version > > > Hi Yipeng, > > I was out last week on vacation, so I am catching up now. > > I think you would have to investigate build-iso and associated scripts > and tools to see if there is an awk, sed or some other command that is > not parsing the extended version.  I have not investigated this further, > that's my initial assessment. > > Can you be more specific about what the error is or provide a log file > of the build-iso process? > > Thanks for working on this project. > >   Sau! > > > > On 3/19/20 12:21 AM, 何义鹏wrote: >> Hello Saul >> >> I'm Yipeng He from JITStack, and I'm taking over the tasks of PBR. >> I encountered the following issue when trying to build iso: >> It fails when the suffix of the version generated by the PBR tool ended >> with number, for instance the building fails if the version id is >> 2.999.9999.rc1.dev23, >> and when I replaced it with 2.999.9999.rc1.dev, the ISO building was >> successful. >> I don't knwo why this happens, could please support and advice the >> solution for this issue. >> >> >> Yipeng.He >> >> _______________________________________________ >> 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 > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From build.starlingx at gmail.com Sun Mar 29 18:52:01 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 29 Mar 2020 14:52:01 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 176 - Failure! Message-ID: <1487295776.1110.1585507922085.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 176 Status: Failure Timestamp: 20200329T185158Z Check logs at: https://127.0.0.1/ -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: DOCKER_BUILD_ID: builder OS: centos MY_REPO: PUBLISH_LOGS_URL: https://127.0.0.1/ PUBLISH_LOGS_BASE: /tmp/logs MASTER_JOB_NAME: LAYER: MY_REPO_ROOT: BUILD_ISO: false From fungi at yuggoth.org Sun Mar 29 19:18:36 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Sun, 29 Mar 2020 19:18:36 +0000 Subject: [Starlingx-discuss] enable pbr version In-Reply-To: References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> <21008692-fe6b-3b65-ab7a-70b80f73ce78@linux.intel.com> Message-ID: <20200329191835.yp7tdswimb2brl5f@yuggoth.org> On 2020-03-29 18:45:28 +0000 (+0000), Penney, Don wrote: > So the idea being that when we create a release branch, like > r/stx.4.0 for example, we would upversion master and add a SemVer > tag to increment it to 5.0.0? > > I don't have a lot of experience with git tags and semver... if we > create a branch at SHA XYZ for r/stx.4.0 and then tag XYZ as > 5.0.0, is it possible the r/stx.4.0 branch would see 5.0.0 as the > semver (since it has XYZ, which has been tagged)? [...] The idea is that following creation of the r/stx.4.0 branch, one of the next (if not the very next) commits to the master branch includes a commit message footer hinting at a SemVer break so that PBR starts assuming the next tag on that branch will (eventually) be 5.0.0 (or 4.1.0 depending on which indicator you use), and so starts autoversioning on master with versions higher than anything you'll ever use on the r/stx.4.0 branch. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From build.starlingx at gmail.com Mon Mar 30 08:00:32 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 30 Mar 2020 04:00:32 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_repo_sync_layered - Build # 177 - Failure! Message-ID: <990828052.1116.1585555233153.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 177 Status: Failure Timestamp: 20200330T080026Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200330T080016Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MANIFEST: compile.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200330T080016Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200330T080016Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler From build.starlingx at gmail.com Mon Mar 30 08:00:35 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 30 Mar 2020 04:00:35 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_master - Build # 80 - Failure! Message-ID: <757056525.1119.1585555236275.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 80 Status: Failure Timestamp: 20200330T080016Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200330T080016Z/logs -------------------------------------------------------------------------------- Parameters FORCE_BUILD: false From sgw at linux.intel.com Mon Mar 30 16:01:04 2020 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 30 Mar 2020 09:01:04 -0700 Subject: [Starlingx-discuss] Docker Proxy Setup Message-ID: Hi There, I am reviewing the Docker Proxy Configuration page [0]. I tried to run the service-parameter-modify and get the following error message: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify platform docker http_proxy http://my.proxy.com:1080 Service Parameter not found: service platform, section docker, name http_proxy Service Parameter not found: service platform, section docker, name http://my.proxy.com:1080 I also tried using name=value: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify platform docker http_proxy=http://my.proxy.com:1080 Service Parameter not found: service platform, section docker, name http_proxy I looked at service-parameter-list and there is no docker section as part of the platform service, so I tried to use service-parameter-add and got the following error: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-add platform docker http_proxy=http://my.proxy.com:1080 Invalid service section docker. It seems that the Docker Proxy Config docs page it out of date and/or not working correctly, can someone let me know what I am doing wrong? [0] https://docs.starlingx.io/configuration/docker_proxy_config.html Thanks Sau! From alexandru.dimofte at intel.com Mon Mar 30 16:01:51 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Mon, 30 Mar 2020 16:01:51 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC Message-ID: Sanity Test from 2020-March-30 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200329T230014Z/outputs/iso/) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) [BLOCKED] Setup 04 TCs [PASS] The sanity was blocked because we faced this issue: https://bugs.launchpad.net/starlingx/+bug/1856078 TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 ] AIO - Duplex [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards, STX Validation Team [cid:image003.png at 01D606C5.A8B6E210] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20507 bytes Desc: image003.png URL: From yu.chengde at 99cloud.net Mon Mar 30 18:56:42 2020 From: yu.chengde at 99cloud.net (YuChengDe) Date: Tue, 31 Mar 2020 02:56:42 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?=5BOpenStack_Upgrade=5D_Built_the_s?= =?utf-8?q?tx-glance_for_stable/ussuri?= In-Reply-To: Message-ID: Hi, Last time I have built the stx-glance image for stable/ussuri I dropped ceph from profiles in stx-glance.stable_docker_image temporarily. It is because that a python3-rbd.rpm package which depends on ceph is not supported by current building environment (Docker CentOS 7.4). Therefore, I would like to know if stx-glance builds without ceph, what impact will occur? And, If it is necessary to stx-glance, could you teach me how to build the python3-rbd.rpm? Many thanks. P.S.1 stx-glance.stable_docker_image BUILDER=loci LABEL=stx-glance PROJECT=glance PROJECT_REPO=https://opendev.org/openstack/glance.git PROJECT_REF=stable/ussuri PIP_PACKAGES="pycrypto python-swiftclient psutil pylint" DIST_PACKAGES="postgresql-libs" PROFILES="fluent glance ceph" PYTHON3=yes P.S.2 error log Failed: No package python3-rbd available. ^[[91mError: Not tolerating missing names on install, stopping. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net 发件人:YuChengDe 发送日期:2020-03-25 14:53:50 收件人:starlingx-discuss 主题:[OpenStack Upgrade] Built the stx-glance for stable/ussuri Hi: We have built a stx-glance image for Ussuri version Welcome to apply image into your system. If there is any problem during usage, please let me know. Many thanks. Note: Get the image from docker hub P.S.: tag = [git branch]-[based on python3 or python built environment]-[image created day] docker pull chantyu/stx-glance:ussuri-python3-20200323 PROJECT_REPO= https://opendev.org/openstack/glance.git PROJECT_REF= master BUILDER= loci -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From yu.chengde at 99cloud.net Mon Mar 30 19:10:24 2020 From: yu.chengde at 99cloud.net (YuChengDe) Date: Tue, 31 Mar 2020 03:10:24 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?=5BOpenStack_Upgrade=5D_Built_the_U?= =?utf-8?q?ssuri_branch_of_stx-horizon?= In-Reply-To: Message-ID: Hello, Last time I have built the stx-horizon image for stable/ussuri I dropped starlingx_dashboard from customization in stx-horizon.stable_docker_image temporarily. It is because that there are too many dependence needed to add into stable_wheels.cfg(P.S.2). Therefore, I would like to know if stx-horizon builds without starlingx_dashboard, what impact on starlingx? Many thanks. P.S.1 stx-horizon.stable_docker_image BUILDER=loci LABEL=stx-horizon PROJECT=horizon PROJECT_REPO=https://opendev.org/openstack/horizon.git PROJECT_REF=stable/ussuri PIP_PACKAGES="pycrypto python-ceilometerclient \ coverage pyudev \ ldap starlingx-dashboard pylint" PROFILES="fluent horizon apache" CUSTOMIZATION="\ ln -s /bin/true /usr/bin/a2enmod && \ sed -i 's/Listen 80/#Listen 80/' /etc/httpd/conf/httpd.conf && \ ln -s /var/lib/openstack/lib/python2.7/site-packages/starlingx_dashboard/themes/starlingx /var/lib/openstack/lib/python2.7/site-packages/openstack_dashboard/themes/starlingx \ " P.S.2 requirements of starlingx-dashboard pbr>=1.6 # Apache-2.0 python-neutronclient>=5.1.0 # Apache-2.0 fmclient>=1.0 cgcs-patch>=1.0 distributedcloud-client>=1.0.0 cgtsclient>=1.0 sysinv>=1.0 nfv-client>=1.0.0 sm-client>=1.0.0 python-cephclient>=13.2.2.0 pytz>=2013.6 # MIT requests-toolbelt>=0.5 six>=1.9.0 # MIT XStatic-Angular>=1.3.7 # MIT License XStatic-D3>=3.1.6.2 # BSD License (3 clause) XStatic-jQuery>=1.7.2 # MIT License -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net 发件人:YuChengDe 发送日期:2020-03-23 18:31:03 收件人:starlingx-discuss at lists.starlingx.io 主题:[OpenStack Upgrade] Built the master branch of stx-horizon Hi: We have built a stx-horizon image for Ussuri version Welcome to apply image into your system. If there is any problem during usage, please let me know. Many thanks. Note: Get the image from docker hub P.S.: tag = [git branch]-[based on python3 or python built environment]-[image created day] docker pull chantyu/stx-horizon:ussuri-python3-20200323 PROJECT_REPO= https://opendev.org/openstack/horizon.git PROJECT_REF= master BUILDER= loci -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Mon Mar 30 22:24:12 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 30 Mar 2020 22:24:12 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Meeting Message-ID: The next containerization meeting is scheduled for Tuesday Mar 31st. Agenda: 1. STX4.0 features: Kata containers [2006145] - update on remaining work items -- Shuicheng Lin - switch armada to run with containerd - upgrade kata packages newer than 1.11.0-alpha0 to include ipv6 fixes - Documentation for config and usage of Kata containers in STX Decouple container applications from platform [2006537] -- Angie Wang - what work items remain? - Updated forecast for feature complete? Upversion container components [2006999] -- Bob Church - upversion of calico to 3.12 & multus to 3.4 - upversion of kubernetes to 1.18 Add support for Helm v3 [2007000] - Jim Gauld - current status Ceph containerization [2005527] -- Martin Chen - review Martin's proposal email from March 16 Etherpad: https://etherpad.openstack.org/p/stx-containerization Call details: zoom link: https://zoom.us/j/342730236 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2832 bytes Desc: not available URL: From kennelson11 at gmail.com Mon Mar 30 22:42:59 2020 From: kennelson11 at gmail.com (Kendall Nelson) Date: Mon, 30 Mar 2020 15:42:59 -0700 Subject: [Starlingx-discuss] Fwd: [all] Virtualized PTG Brainstorming Community Meetings In-Reply-To: References: Message-ID: Hello Everyone! So! After Marks initial email[1] that announced we would be virtualizing the PTG and collected volunteers[2] to help brainstorm the best way to hold the PTG virtually, we polled the volunteers for the best times to meet. In trying to be the most inclusive we have settled on three meetings to brainstorm together as a community. They are as follows: - April 2nd at 12:00 UTC - April 6th at 17:00 UTC - April 7th at 2:00 UTC We will be using my zoom[3] and continue using the same etherpad [2] that we collected volunteers in for all the notes from all three meetings. All are welcome! And if you can attend more than one meeting, please do! The more overlap we have the more cohesive discussions we will have. Hope to see you all there! -Kendall Nelson (diablo_rojo) [1] http://lists.openstack.org/pipermail/foundation/2020-March/002854.html [2] https://etherpad.openstack.org/p/Virtual_PTG_Planning [3] https://zoom.us/my/diablorojo -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Tue Mar 31 00:38:07 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 31 Mar 2020 00:38:07 +0000 Subject: [Starlingx-discuss] Docker Proxy Setup In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C766397BCA9@SHSMSX104.ccr.corp.intel.com> Hi Saul, It seems the cmd has been updated. You could use "system service-parameter-list" to get the list first. Then you could modify it like below cmd: system service-parameter-modify docker proxy http_proxy=HTTP_PROXY In my test, the modification will not be applied until you lock&unlock controller. You could find there is "Configuration is out-of-date" message with "fm alarm-list". Best Regards Shuicheng -----Original Message----- From: Saul Wold Sent: Tuesday, March 31, 2020 12:01 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Docker Proxy Setup Hi There, I am reviewing the Docker Proxy Configuration page [0]. I tried to run the service-parameter-modify and get the following error message: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify platform docker http_proxy http://my.proxy.com:1080 Service Parameter not found: service platform, section docker, name http_proxy Service Parameter not found: service platform, section docker, name http://my.proxy.com:1080 I also tried using name=value: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify platform docker http_proxy=http://my.proxy.com:1080 Service Parameter not found: service platform, section docker, name http_proxy I looked at service-parameter-list and there is no docker section as part of the platform service, so I tried to use service-parameter-add and got the following error: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-add platform docker http_proxy=http://my.proxy.com:1080 Invalid service section docker. It seems that the Docker Proxy Config docs page it out of date and/or not working correctly, can someone let me know what I am doing wrong? [0] https://docs.starlingx.io/configuration/docker_proxy_config.html Thanks Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From yipeng.he at jitstack.com Tue Mar 31 01:52:36 2020 From: yipeng.he at jitstack.com (=?utf-8?B?5L2V5LmJ6bmP?=) Date: Tue, 31 Mar 2020 09:52:36 +0800 Subject: [Starlingx-discuss] enable pbr version In-Reply-To: <21008692-fe6b-3b65-ab7a-70b80f73ce78@linux.intel.com> References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> <21008692-fe6b-3b65-ab7a-70b80f73ce78@linux.intel.com> Message-ID:  Saul! Thank you for your answer! But how should I use the semMem-ver tag?   ------------------ Original ------------------ From:  "Saul Wold" From build.starlingx at gmail.com Tue Mar 31 05:40:59 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 31 Mar 2020 01:40:59 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 494 - Failure! Message-ID: <2040061285.1126.1585633259991.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 494 Status: Failure Timestamp: 20200330T230011Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200330T230011Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From shuicheng.lin at intel.com Tue Mar 31 08:26:57 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 31 Mar 2020 08:26:57 +0000 Subject: [Starlingx-discuss] call for review for patches merge master into centos8 feature branch Message-ID: <9700A18779F35F49AF027300A49E7C766397C151@SHSMSX104.ccr.corp.intel.com> Hi core reviewers, I merged all master changes to centos8 feature branch with below patch list. Please help review them. After the patches get merged, we will try to enable layer build for centos8 feature branch, and continue CentOS 8.1 upgrade task. (There is Zuul failure with fault git, I will update the patch after fix is merged in master) https://review.opendev.org/#/q/topic:centos8-rebase+(status:open+OR+status:merged) Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Mar 31 08:35:39 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 31 Mar 2020 08:35:39 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 4/1/2020 Message-ID: Hi All: Agenda for 4/1 meeting: - Ceph containerization (martin) - Kata remaining work (shuicheng) - PBR: (JITStack Wesley) - centos8 upgrade (shuicheng/Austin) kernel upgrade on master centos8 branch rebase - python3 upgrade status (An Ran) -open If have any other topic, feel free to add to https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. From haochuan.z.chen at intel.com Tue Mar 31 12:11:52 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 31 Mar 2020 12:11:52 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Meeting Message-ID: Hi Frank I prepare some slide for today's ceph containerization topic https://docs.google.com/presentation/d/16xI-woOIvMtM6aL7Nlmo1ICtZPDzSl2OvD3p6lrPsVY/edit?usp=sharing BR! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Tuesday, March 31, 2020 8:38 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 22, Issue 124 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. StarlingX Containerization Meeting (Miller, Frank) 2. Fwd: [all] Virtualized PTG Brainstorming Community Meetings (Kendall Nelson) 3. Re: Docker Proxy Setup (Lin, Shuicheng) ---------------------------------------------------------------------- Message: 1 Date: Mon, 30 Mar 2020 22:24:12 +0000 From: "Miller, Frank" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] StarlingX Containerization Meeting Message-ID: Content-Type: text/plain; charset="iso-8859-1" The next containerization meeting is scheduled for Tuesday Mar 31st. Agenda: 1. STX4.0 features: Kata containers [2006145] - update on remaining work items -- Shuicheng Lin - switch armada to run with containerd - upgrade kata packages newer than 1.11.0-alpha0 to include ipv6 fixes - Documentation for config and usage of Kata containers in STX Decouple container applications from platform [2006537] -- Angie Wang - what work items remain? - Updated forecast for feature complete? Upversion container components [2006999] -- Bob Church - upversion of calico to 3.12 & multus to 3.4 - upversion of kubernetes to 1.18 Add support for Helm v3 [2007000] - Jim Gauld - current status Ceph containerization [2005527] -- Martin Chen - review Martin's proposal email from March 16 Etherpad: https://etherpad.openstack.org/p/stx-containerization Call details: zoom link: https://zoom.us/j/342730236 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2832 bytes Desc: not available URL: ------------------------------ Message: 2 Date: Mon, 30 Mar 2020 15:42:59 -0700 From: Kendall Nelson To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Fwd: [all] Virtualized PTG Brainstorming Community Meetings Message-ID: Content-Type: text/plain; charset="utf-8" Hello Everyone! So! After Marks initial email[1] that announced we would be virtualizing the PTG and collected volunteers[2] to help brainstorm the best way to hold the PTG virtually, we polled the volunteers for the best times to meet. In trying to be the most inclusive we have settled on three meetings to brainstorm together as a community. They are as follows: - April 2nd at 12:00 UTC - April 6th at 17:00 UTC - April 7th at 2:00 UTC We will be using my zoom[3] and continue using the same etherpad [2] that we collected volunteers in for all the notes from all three meetings. All are welcome! And if you can attend more than one meeting, please do! The more overlap we have the more cohesive discussions we will have. Hope to see you all there! -Kendall Nelson (diablo_rojo) [1] http://lists.openstack.org/pipermail/foundation/2020-March/002854.html [2] https://etherpad.openstack.org/p/Virtual_PTG_Planning [3] https://zoom.us/my/diablorojo -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Tue, 31 Mar 2020 00:38:07 +0000 From: "Lin, Shuicheng" To: Saul Wold , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Docker Proxy Setup Message-ID: <9700A18779F35F49AF027300A49E7C766397BCA9 at SHSMSX104.ccr.corp.intel.com> Content-Type: text/plain; charset="utf-8" Hi Saul, It seems the cmd has been updated. You could use "system service-parameter-list" to get the list first. Then you could modify it like below cmd: system service-parameter-modify docker proxy http_proxy=HTTP_PROXY In my test, the modification will not be applied until you lock&unlock controller. You could find there is "Configuration is out-of-date" message with "fm alarm-list". Best Regards Shuicheng -----Original Message----- From: Saul Wold Sent: Tuesday, March 31, 2020 12:01 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Docker Proxy Setup Hi There, I am reviewing the Docker Proxy Configuration page [0]. I tried to run the service-parameter-modify and get the following error message: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify platform docker http_proxy http://my.proxy.com:1080 Service Parameter not found: service platform, section docker, name http_proxy Service Parameter not found: service platform, section docker, name http://my.proxy.com:1080 I also tried using name=value: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify platform docker http_proxy=http://my.proxy.com:1080 Service Parameter not found: service platform, section docker, name http_proxy I looked at service-parameter-list and there is no docker section as part of the platform service, so I tried to use service-parameter-add and got the following error: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-add platform docker http_proxy=http://my.proxy.com:1080 Invalid service section docker. It seems that the Docker Proxy Config docs page it out of date and/or not working correctly, can someone let me know what I am doing wrong? [0] https://docs.starlingx.io/configuration/docker_proxy_config.html Thanks Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 22, Issue 124 ************************************************** From fungi at yuggoth.org Tue Mar 31 13:14:04 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Tue, 31 Mar 2020 13:14:04 +0000 Subject: [Starlingx-discuss] enable pbr version In-Reply-To: References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> <21008692-fe6b-3b65-ab7a-70b80f73ce78@linux.intel.com> Message-ID: <20200331131403.34jacihh4aeq4ymf@yuggoth.org> On 2020-03-31 09:52:36 +0800 (+0800), 何义鹏 wrote: [...] > how should I use the semMem-ver tag? [...] The way the OpenStack release managers do it is, as soon as a new stable branch is created from a release candidate tag on the master branch, they propose a change like this to master: https://review.opendev.org/685258 Note the "Sem-Ver: feature" in the footer of the commit message, that hints PBR to assume the next tag will at least increase the "minor" (second) part of the version number. If you want to hint at a coming increase for the "major" (first) part of the version number next you would instead put "Sem-Ver: api-break" there. You can find a brief description of this functionality in PBR's documentation: https://docs.openstack.org/pbr/latest/user/features.html#version There's also a lot more underlying detail in the spec from when that capability was first being added: https://specs.openstack.org/openstack/oslo-specs/specs/juno/pbr-semver.html Hopefully this helps. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From haochuan.z.chen at intel.com Tue Mar 31 13:28:22 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 31 Mar 2020 13:28:22 +0000 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> <0bbec920-0556-15ab-5d4e-635b36a8cc89@windriver.com> <0492432b-cf8c-9d66-f08a-a4df0e826bd7@windriver.com> Message-ID: Hi scott I find a new project created with this link https://opendev.org/starlingx/rook-ceph But this is the link we usually used to submit patch for review. https://review.opendev.org/starlingx/root we need any other step? Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Friday, March 20, 2020 8:34 AM To: 'Scott Little' ; Rowsell, Brent Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: create a new project for ceph containerizaiton I prefer create a blank project with this link. Then I will upstream. Martin, Chen IOTG, Software Engineer 021-61164330 From: Scott Little > Sent: Friday, March 20, 2020 1:43 AM To: Chen, Haochuan Z >; Rowsell, Brent > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: Re: create a new project for ceph containerizaiton The URL https://review.opendev.org/starlingx/rook-storage-app is invalid Please provide a valid upstream url. Scott On 2020-03-17 7:54 p.m., Chen, Haochuan Z wrote: 3) The url and branch of any upstream git used to seed the content for the new git. https://review.opendev.org/starlingx/rook-storage-app -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Tue Mar 31 14:05:34 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 31 Mar 2020 07:05:34 -0700 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> <0bbec920-0556-15ab-5d4e-635b36a8cc89@windriver.com> <0492432b-cf8c-9d66-f08a-a4df0e826bd7@windriver.com> Message-ID: You need to request a new group called starlingx-rook-ceph via the Infra channel (#openstack-infra) and then you need to submit the initial review with the .gitreview template. Did you review the Project Creator's Guide [0]? Sau! [0] https://docs.opendev.org/opendev/infra-manual/latest/creators.html On 3/31/20 6:28 AM, Chen, Haochuan Z wrote: > Hi scott > > I find a new project created with this link > > https://opendev.org/starlingx/rook-ceph > > But this is the link we usually used to submit patch for review. > > https://review.opendev.org/starlingx/root > > we need any other step? > > Thanks! > > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > > *From:*Chen, Haochuan Z > *Sent:* Friday, March 20, 2020 8:34 AM > *To:* 'Scott Little' ; Rowsell, Brent > > *Cc:* 'starlingx-discuss at lists.starlingx.io' > > *Subject:* RE: create a new project for ceph containerizaiton > > I prefer create a blank project with this link. Then I will upstream. > > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > > *From:*Scott Little > > *Sent:* Friday, March 20, 2020 1:43 AM > *To:* Chen, Haochuan Z >; Rowsell, Brent > > > *Cc:* 'starlingx-discuss at lists.starlingx.io' > > > *Subject:* Re: create a new project for ceph containerizaiton > > The URL https://review.opendev.org/starlingx/rook-storage-app is invalid > > Please provide a valid upstream url. > > Scott > > On 2020-03-17 7:54 p.m., Chen, Haochuan Z wrote: > > 3) The url and branch of any upstream git used to seed the content > for the new git. > > https://review.opendev.org/starlingx/rook-storage-app > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From haochuan.z.chen at intel.com Tue Mar 31 14:10:01 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 31 Mar 2020 14:10:01 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Meeting In-Reply-To: References: Message-ID: Hi Frank I share on google drive, with anyone could access with this link https://drive.google.com/file/d/1GFO6-72lmVt5av_pX1EfXocibSEcPDJJ/view?usp=sharing BR! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: Chen, Haochuan Z Sent: Tuesday, March 31, 2020 8:12 PM To: Miller, Frank Cc: starlingx-discuss at lists.starlingx.io Subject: StarlingX Containerization Meeting Hi Frank I prepare some slide for today's ceph containerization topic https://docs.google.com/presentation/d/16xI-woOIvMtM6aL7Nlmo1ICtZPDzSl2OvD3p6lrPsVY/edit?usp=sharing BR! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Tuesday, March 31, 2020 8:38 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 22, Issue 124 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. StarlingX Containerization Meeting (Miller, Frank) 2. Fwd: [all] Virtualized PTG Brainstorming Community Meetings (Kendall Nelson) 3. Re: Docker Proxy Setup (Lin, Shuicheng) ---------------------------------------------------------------------- Message: 1 Date: Mon, 30 Mar 2020 22:24:12 +0000 From: "Miller, Frank" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] StarlingX Containerization Meeting Message-ID: Content-Type: text/plain; charset="iso-8859-1" The next containerization meeting is scheduled for Tuesday Mar 31st. Agenda: 1. STX4.0 features: Kata containers [2006145] - update on remaining work items -- Shuicheng Lin - switch armada to run with containerd - upgrade kata packages newer than 1.11.0-alpha0 to include ipv6 fixes - Documentation for config and usage of Kata containers in STX Decouple container applications from platform [2006537] -- Angie Wang - what work items remain? - Updated forecast for feature complete? Upversion container components [2006999] -- Bob Church - upversion of calico to 3.12 & multus to 3.4 - upversion of kubernetes to 1.18 Add support for Helm v3 [2007000] - Jim Gauld - current status Ceph containerization [2005527] -- Martin Chen - review Martin's proposal email from March 16 Etherpad: https://etherpad.openstack.org/p/stx-containerization Call details: zoom link: https://zoom.us/j/342730236 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2832 bytes Desc: not available URL: ------------------------------ Message: 2 Date: Mon, 30 Mar 2020 15:42:59 -0700 From: Kendall Nelson To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Fwd: [all] Virtualized PTG Brainstorming Community Meetings Message-ID: Content-Type: text/plain; charset="utf-8" Hello Everyone! So! After Marks initial email[1] that announced we would be virtualizing the PTG and collected volunteers[2] to help brainstorm the best way to hold the PTG virtually, we polled the volunteers for the best times to meet. In trying to be the most inclusive we have settled on three meetings to brainstorm together as a community. They are as follows: - April 2nd at 12:00 UTC - April 6th at 17:00 UTC - April 7th at 2:00 UTC We will be using my zoom[3] and continue using the same etherpad [2] that we collected volunteers in for all the notes from all three meetings. All are welcome! And if you can attend more than one meeting, please do! The more overlap we have the more cohesive discussions we will have. Hope to see you all there! -Kendall Nelson (diablo_rojo) [1] http://lists.openstack.org/pipermail/foundation/2020-March/002854.html [2] https://etherpad.openstack.org/p/Virtual_PTG_Planning [3] https://zoom.us/my/diablorojo -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Tue, 31 Mar 2020 00:38:07 +0000 From: "Lin, Shuicheng" To: Saul Wold , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Docker Proxy Setup Message-ID: <9700A18779F35F49AF027300A49E7C766397BCA9 at SHSMSX104.ccr.corp.intel.com> Content-Type: text/plain; charset="utf-8" Hi Saul, It seems the cmd has been updated. You could use "system service-parameter-list" to get the list first. Then you could modify it like below cmd: system service-parameter-modify docker proxy http_proxy=HTTP_PROXY In my test, the modification will not be applied until you lock&unlock controller. You could find there is "Configuration is out-of-date" message with "fm alarm-list". Best Regards Shuicheng -----Original Message----- From: Saul Wold Sent: Tuesday, March 31, 2020 12:01 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Docker Proxy Setup Hi There, I am reviewing the Docker Proxy Configuration page [0]. I tried to run the service-parameter-modify and get the following error message: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify platform docker http_proxy http://my.proxy.com:1080 Service Parameter not found: service platform, section docker, name http_proxy Service Parameter not found: service platform, section docker, name http://my.proxy.com:1080 I also tried using name=value: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify platform docker http_proxy=http://my.proxy.com:1080 Service Parameter not found: service platform, section docker, name http_proxy I looked at service-parameter-list and there is no docker section as part of the platform service, so I tried to use service-parameter-add and got the following error: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-add platform docker http_proxy=http://my.proxy.com:1080 Invalid service section docker. It seems that the Docker Proxy Config docs page it out of date and/or not working correctly, can someone let me know what I am doing wrong? [0] https://docs.starlingx.io/configuration/docker_proxy_config.html Thanks Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 22, Issue 124 ************************************************** From scott.little at windriver.com Tue Mar 31 14:41:23 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 31 Mar 2020 10:41:23 -0400 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> <0bbec920-0556-15ab-5d4e-635b36a8cc89@windriver.com> <0492432b-cf8c-9d66-f08a-a4df0e826bd7@windriver.com> Message-ID: <1e7de432-f219-977c-2929-484ba26084fd@windriver.com> Looks like the new opendev infrastructure to process the new repo request didn't work as expected. They are looking into it. FYI, their IRC location has moved from #openstack-infra to #opendev . Scott On 2020-03-31 9:28 a.m., Chen, Haochuan Z wrote: > > Hi scott > > I find a new project created with this link > > https://opendev.org/starlingx/rook-ceph > > But this is the link we usually used to submit patch for review. > > https://review.opendev.org/starlingx/root > > we need any other step? > > Thanks! > > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > > *From:*Chen, Haochuan Z > *Sent:* Friday, March 20, 2020 8:34 AM > *To:* 'Scott Little' ; Rowsell, Brent > > *Cc:* 'starlingx-discuss at lists.starlingx.io' > > *Subject:* RE: create a new project for ceph containerizaiton > > I prefer create a blank project with this link. Then I will upstream. > > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > > *From:*Scott Little > > *Sent:* Friday, March 20, 2020 1:43 AM > *To:* Chen, Haochuan Z >; Rowsell, Brent > > > *Cc:* 'starlingx-discuss at lists.starlingx.io' > > > *Subject:* Re: create a new project for ceph containerizaiton > > The URL https://review.opendev.org/starlingx/rook-storage-app is invalid > > Please provide a valid upstream url. > > Scott > > On 2020-03-17 7:54 p.m., Chen, Haochuan Z wrote: > > 3) The url and branch of any upstream git used to seed the content > for the new git. > > https://review.opendev.org/starlingx/rook-storage-app > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Tue Mar 31 15:15:44 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Tue, 31 Mar 2020 15:15:44 +0000 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: <1e7de432-f219-977c-2929-484ba26084fd@windriver.com> References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> <0bbec920-0556-15ab-5d4e-635b36a8cc89@windriver.com> <0492432b-cf8c-9d66-f08a-a4df0e826bd7@windriver.com> <1e7de432-f219-977c-2929-484ba26084fd@windriver.com> Message-ID: <20200331151543.ll74sfbgglgfnb4q@yuggoth.org> On 2020-03-31 10:41:23 -0400 (-0400), Scott Little wrote: > Looks like the new opendev infrastructure to process the new repo > request didn't work as expected. > > They are looking into it. [...] Yes, we merged a change roughly 19 hours ago which broke an untested code path in our project creation automation, so we didn't notice we'd stopped provisioning anything in Gerrit. We've manually processed the pending project creations for changes which merged in that timeframe (including yours) so you should be all set now, and the proper fix to our tooling is on its way to merging now as well. Just let us know what initial member you want added to which groups and we can take care of that, and thanks for giving us a heads up. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From alexandru.dimofte at intel.com Tue Mar 31 15:28:43 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 31 Mar 2020 15:28:43 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC Message-ID: Sanity Test from 2020-March-31 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200330T230011Z/outputs/iso/) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment [FAIL] Unfortunately, we don't have results for today's Virtual Environment because we experienced a crush in our side, if there will be the case we will open a defect but till now nothing relevant. Regards, STX Validation Team [cid:image002.png at 01D6078A.33873AB0] Dimofte Alexandru Software Engineer Transportation Solutions Division 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: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20513 bytes Desc: image002.png URL: From scott.little at windriver.com Tue Mar 31 16:11:27 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 31 Mar 2020 12:11:27 -0400 Subject: [Starlingx-discuss] Need core reviewers for new projects Message-ID: <77f73501-19f0-0889-c977-6841658c543b@windriver.com> The following new projects have now been created after a few growing pains for the newly deployed opendev infrastructure.    starlingx/cert-manager-armada-app    starlingx/nginx-ingress-controller-armada-app    starlingx/rook-ceph *I need to know who the core reviewers should be for the new projects. * I'll start with myself and the project requester until I hear from the community*. * Next step for project leads is to set up your zuul configs.  Look to other projects base on the same language as a guide. You'll need the following files...    .zuul.yaml    test-requirements.txt    tox.ini Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Mar 31 16:16:16 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 31 Mar 2020 12:16:16 -0400 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: <1e7de432-f219-977c-2929-484ba26084fd@windriver.com> References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> <0bbec920-0556-15ab-5d4e-635b36a8cc89@windriver.com> <0492432b-cf8c-9d66-f08a-a4df0e826bd7@windriver.com> <1e7de432-f219-977c-2929-484ba26084fd@windriver.com> Message-ID: <3f4aaa46-b30d-7716-b7d2-0ed1bfb07ee1@windriver.com> Are new repos are ready to clone.  Git review should work, but we need a list of core reviewers for each. I'd like to see a zuul config for each, but I'll leave that to the project leads. Scott On 2020-03-31 10:41 a.m., Scott Little wrote: > > Looks like the new opendev infrastructure to process the new repo > request didn't work as expected. > > They are looking into it. > > FYI, their IRC location has moved from #openstack-infra to #opendev . > > Scott > > > On 2020-03-31 9:28 a.m., Chen, Haochuan Z wrote: >> >> Hi scott >> >> I find a new project created with this link >> >> https://opendev.org/starlingx/rook-ceph >> >> But this is the link we usually used to submit patch for review. >> >> https://review.opendev.org/starlingx/root >> >> we need any other step? >> >> Thanks! >> >> Martin, Chen >> >> IOTG, Software Engineer >> >> 021-61164330 >> >> *From:*Chen, Haochuan Z >> *Sent:* Friday, March 20, 2020 8:34 AM >> *To:* 'Scott Little' ; Rowsell, Brent >> >> *Cc:* 'starlingx-discuss at lists.starlingx.io' >> >> *Subject:* RE: create a new project for ceph containerizaiton >> >> I prefer create a blank project with this link. Then I will upstream. >> >> Martin, Chen >> >> IOTG, Software Engineer >> >> 021-61164330 >> >> *From:*Scott Little > > >> *Sent:* Friday, March 20, 2020 1:43 AM >> *To:* Chen, Haochuan Z > >; Rowsell, Brent >> > >> *Cc:* 'starlingx-discuss at lists.starlingx.io' >> > > >> *Subject:* Re: create a new project for ceph containerizaiton >> >> The URL https://review.opendev.org/starlingx/rook-storage-app is invalid >> >> Please provide a valid upstream url. >> >> Scott >> >> On 2020-03-17 7:54 p.m., Chen, Haochuan Z wrote: >> >> 3) The url and branch of any upstream git used to seed the >> content for the new git. >> >> https://review.opendev.org/starlingx/rook-storage-app >> > > _______________________________________________ > 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 Mar 31 17:09:58 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 31 Mar 2020 13:09:58 -0400 Subject: [Starlingx-discuss] create a new project for ceph containerizaiton In-Reply-To: References: <56829C2A36C2E542B0CCB9854828E4D8562C3D26@CDSMSX101.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562C3E64@CDSMSX101.ccr.corp.intel.com> <0bbec920-0556-15ab-5d4e-635b36a8cc89@windriver.com> <0492432b-cf8c-9d66-f08a-a4df0e826bd7@windriver.com> Message-ID: <783b373a-9724-5a85-ee95-3ed870f5e426@windriver.com> I've set you and I up as core reviewers for the moment We can add/remove others via https://review.opendev.org/#/admin/groups/2084,members . Scott On 2020-03-31 9:28 a.m., Chen, Haochuan Z wrote: > > Hi scott > > I find a new project created with this link > > https://opendev.org/starlingx/rook-ceph > > But this is the link we usually used to submit patch for review. > > https://review.opendev.org/starlingx/root > > we need any other step? > > Thanks! > > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > > *From:*Chen, Haochuan Z > *Sent:* Friday, March 20, 2020 8:34 AM > *To:* 'Scott Little' ; Rowsell, Brent > > *Cc:* 'starlingx-discuss at lists.starlingx.io' > > *Subject:* RE: create a new project for ceph containerizaiton > > I prefer create a blank project with this link. Then I will upstream. > > Martin, Chen > > IOTG, Software Engineer > > 021-61164330 > > *From:*Scott Little > > *Sent:* Friday, March 20, 2020 1:43 AM > *To:* Chen, Haochuan Z >; Rowsell, Brent > > > *Cc:* 'starlingx-discuss at lists.starlingx.io' > > > *Subject:* Re: create a new project for ceph containerizaiton > > The URL https://review.opendev.org/starlingx/rook-storage-app is invalid > > Please provide a valid upstream url. > > Scott > > On 2020-03-17 7:54 p.m., Chen, Haochuan Z wrote: > > 3) The url and branch of any upstream git used to seed the content > for the new git. > > https://review.opendev.org/starlingx/rook-storage-app > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Mar 31 18:21:37 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 31 Mar 2020 14:21:37 -0400 Subject: [Starlingx-discuss] [ Build ] Layered build challenges Message-ID: <87354fc1-c64d-7b84-7934-8b5785abf13f@windriver.com> Layered builds relies on an authoritative source (e.g. CENGN) publishing an RPM repo with all the RPMS produced by a single build, and an lst file enumerating those RPMS.  There are new config files describing the url's for those repos that use the latest_build symlink.  The client, a higher layer we wish to build, must download the new lst file and repo data, and use those to download all new/updates rpms. Issue identified early on where. 1) The outputs of a specific build might not endure on CENGN as long as a designers build context. 2) The latest_build symlink might change in the middle of a download season.  Packages version may have changes during between builds.  The old version specified by the pre-update lst file might no longer be available. So the next step is for CENGN to mirror those build outputs in a cumulative fashion, like any other repo.  It's a default for download_mirror.sh to look for a CENGN mirror of any url it uses, and its a default behavior for CENGN to mirror it.  The mirror would accumulate all the versions from all the builds.  So changing symlinks and deletion of old builds shouldn't impact the end user. All this hinged on two assumptions. 1) If a package was not upversioned between builds, there would not be significant changes to the content of the RPM. 2) yum repodata has checksums and timestamps for all packages.  I expected yum to use that data to flag a changed rpm for re-download. Recent experience has proven both assumptions turned out to be wrong. 1) Kernel modules were the first example of a violation of this asumption.  The mkod implicitly changes when the kernel changes. The most obvious is that the installation path to the kmod change, embedding the kernel version it was compiled against.  There are deeper differences not worth enumerating. 2) Yum will throw error over inconsistancies between new repodata and old, our new repodata and rpms already downloaded, but will not re-download the updated packages.  I have not been able to override this behavious with command line options, config files, or even cleaning all yum cache.  It appears to be a defense against mirrors that are slow to update, and perhaps against malicious hacks of an upstream repo. The broken assumptions affected both the CENGN mirroring process, and the final download by upper layer builders.  Neither was updating rpms that have changed if the file name did not also change. Is this only an important matter for kmods.  Exploration with rpmdiff reveals that the majority of RPMS change when rebuilt, even with zero source code changes to any package.  Excluding the timestamps on files embedded within the rpms lefts a list greater than 25% of the repo reporting differences.  Spent some time trying to figure out a way to filter out paths that embed the build time stamp, but the list remained stubbornly large. So how to fix it. Several methods have been explored.  Some solutions only apply if the downloader retains the file structure of the upstream repo, or if the download capture the entire repo.   True for the cengn mirror, not for the output of download_mirror.sh. 1) reposync: An rpm repo mirroring tool.  It's built on yum, and has the same behaviour as yum.  Can't use that. 2) verifytree:  This tool validates the checksums in the repodata vs the current set of rpms.  It's a tool aimed at rpm mirror operators. It requires that the download directory structure is a faithful replica of upstream.  So I can manually download the repodata, then validate it vs the previously downloaded set of rpms.  RPM's that it flags as having the wrong checksum need to be re-downloaded.  The actual re-download could be accomplished in two ways. 2a) Replicate the current repo in a temporary working directory, delete the updated rpms, use yum (either reposync or yumdownloader) with clean cache to re-download the missing files. Finally exchange the temporary directory with regular one.  This gives an atomic cutover to the new content.  This is what CENGN mirror is using now.   This doesn't entirely solve the problem for downloaders that were actively updated their local snapshot when such a mirror update goes live.  Ideally the download_mirror tool has a retry loop.  If the last pass downloaded files, try again until a pass reports there are no further files to update. 2b) curl:  Use curl rather than yum.  Requires that we somehow know the URL for the rpm we intend to download.  'yumdownloader --url' can tell use the upstream url. 3) curl:  Use curl rather than yum, but do so directly without verifytree.  Rely entirely on timestamps.  If we can give curl the download url for the rpm, it can be given options that compare the local and remote file timestamps and only downloads if the remote copy is newer.  Also it preserves the file timestamp on download. We can use 'yumdownloader --url' to tell us which repo to use, and what the download url is from that repo. This was my solution for the download_mirror.sh users. 4) rsync: Requires CENGN to expose an rsync port to the world. Not my first choice.  File sharing pirates would love to compromise a machine with an open rsync port. New issues. 1) 'yumdownloader --url' is SLOW.  It takes more than a second per package to produce an answer.  since lower layer rpms are handled by the same tools as all other rpms, we have over 2000 packages to check.  This slowness largely persists in batch mode where I query a large set of packages at once (3/4 sec per package).  It'll take an hour to process them all, even if the result is 'nothing to update' 2) As noted above, most rpms are showing subtle changes between builds even though the source has not changed.  This is undesirable, triggering a huge number of needless downloads. New solutions? 1) Download rpms from lower layers using a different tool than 'download_mirror.sh' or at least a different sub-function than dl-rpms.  First, this mean that we only need to run 'yumdownloader -url' vs a smaller list of rpms.  Also this would allow us to use reposync and verify tree for the download functions, removing 'yumdownloader -url' entirely. 2) Use build avoidance.  Copies rpms from previous build into current build environment and then use an incremental build.  This avoids needlessly rebuilding rpms. RPMS retain the same checksum and timestamp if not rebuilt.  Cut the problem off at the source. Concern with this solution is that I still like to force a non-build avoidance build from time to time to ensure we haven't diverged from reality in some new and unexpected way. From Bill.Zvonar at windriver.com Tue Mar 31 20:28:44 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 31 Mar 2020 20:28:44 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Apr 1, 2020) Message-ID: Hi all, reminder of tomorrow's TSC/Community call. We'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200401T1400 From yang.liu at windriver.com Tue Mar 31 16:09:12 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Tue, 31 Mar 2020 16:09:12 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 03/31/2020 Message-ID: Agenda/meeting notes are posted here: https://etherpad.openstack.org/p/stx-test Agenda for 03/31/2020 Attendees: Yang, Mihail, Nicolae, George, Cosmin, Sharath, Claudiu, Bruce, ChrisW, Wendy 1. Sanity Status: · Sanity issues reported by WR: * 1855474 - OpenStack pods were not recovered after force reboot active controller * 1859645 - platform-integ-apps fail to apply initially due to could not find the requested resource (get configmaps) * https://bugs.launchpad.net/starlingx/+bug/1863795 - "helm list" failed by network is unreachable after host-unlock * https://bugs.launchpad.net/starlingx/+bug/1868567 - CMD application-delete failed by Timeout while waiting on RPC response * https://bugs.launchpad.net/starlingx/+bug/1869739 - 250.001 controller Configuration is out-of-date alarm not cleared after system installation · Sanity issues reported by Intel: * Green * Private registry used by Intel: some container images changed and not picked up in private registry - now resolved * May look into adding ipv6 configs for the long term 2. stx4.0 testing · Release plan: * https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 * Kata: intend to start early. target test complete by 05/08 * Rook: intend to start early. target test complete by 05/22 * Fault containerization: target test complete by 05/29 * Centos8: no server with TPM, mellanox cards; integrity may not be testable * TSN support in kata container: target test complete by 05/29 * OpenStack clients and platform services: eng build will be available in a week. testing: 04-13 - 05-04 * OpenStack upversion: § automated and manual test update needed, may be time consuming § target 06-05 * Layered build is tested daily with issues being found and resolved § image did not build - fixed § 03-31 build still failed, but went further · Targeted feature completion date: 06-08 * Risk: OpenStack upversion to Ussuris coming in late, and requires large amount of testing · Targeted regression completion date: 06-15 (pushing out 1 week) * Propose no openstack regression between 06-08 to 06-15 3. Unified santiy * Intel will bring in robot sanity as is into pytest framework * For feature test cases porting from robot framework in future, should look into organizing/porting by feature, and porting only the missing ones * Need to look into external traffic to/from openstack vm via neutron router in future to enable neutron testing in Intel environment 4. Opens · Servers/test environment setup within Nic's team: * In progress - cabling, configuring ports, etc * Will know more by end of week. * Risk reduced compared to last week. -------------- next part -------------- An HTML attachment was scrubbed... URL: