From sgw at linux.intel.com Tue Oct 1 00:00:21 2019 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 30 Sep 2019 17:00:21 -0700 Subject: [Starlingx-discuss] [fault][gui][ha][metal][nfv][update] Project operations - RESPONSE NEEDED In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F3606FB02@SHSMSX104.ccr.corp.intel.com> References: <4C6705C0-D0FD-4C01-9B61-972C84CF71E4@gmail.com> <9A85D2917C58154C960D95352B22818BD07EC256@fmsmsx123.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F3606FB02@SHSMSX104.ccr.corp.intel.com> Message-ID: <7dac6c47-9401-776a-a0a7-02fdcc493938@linux.intel.com> On 9/30/19 3:52 PM, Xie, Cindy wrote: > We have one customer in China evaluated these "Flocks" services, and they want to use them as building blocks into their product, but will do it one by one. Will the repo merge impact the possibility of customer of doing so? > I think this needs to be clarified, I do not think that the repos are being merged, just the project team so that there will be one "Flock" meeting wit a common PL / TL pair. Sau! > Thx. - cindy > > -----Original Message----- > From: Jones, Bruce E > Sent: Tuesday, October 1, 2019 5:47 AM > To: Ildiko Vancsa ; starlingx > Subject: Re: [Starlingx-discuss] [fault][gui][ha][metal][nfv][update] Project operations - RESPONSE NEEDED > > I have no objection to merging these projects. I think it makes sense, for now. Long term I think there is value in making the "Flock" projects more separate, and maybe even stand-alone, someday. > > I think it would also be good for the teams working on these projects to hold public meetings and post agenda & minutes to the list. > > brucej > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: Monday, September 30, 2019 5:38 AM > To: starlingx > Subject: [Starlingx-discuss] [fault][gui][ha][metal][nfv][update] Project operations - RESPONSE NEEDED > > Hi, > > I’m reaching out about an open review that proposes to merge six of the StarlingX projects into one: https://review.opendev.org/#/c/683410/ > > As this proposal affects 1/3 of the project teams I would like to have a community discussion about this rearrangement. > > I have a few questions to discuss: > > * Are all of these projects still active? > * From functionality perspective the project teams cover very different areas. What are the motivating factors behind the proposed change? > * Does this proposal help with organizing work and onboarding new contributors? > > I would like to have feedback from the project team members and community members on the above questions as well as in general in response to the proposed change. Please respond to this thread and share your views. > > > I also checked some details and based on the StarlingX wiki the projects listed in the subject have no meetings and their wiki pages are also very brief in providing information about what they do and how to participate. I think this is something to look into in general and it should be the responsibility of all project teams and contributors. > > I propose to have a liaison from every team to look into addressing this topic to make sure this is an ongoing activity along with the technical development work. What do you think about this idea? > > > 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 > _______________________________________________ > 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 ildiko.vancsa at gmail.com Tue Oct 1 08:37:19 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 1 Oct 2019 10:37:19 +0200 Subject: [Starlingx-discuss] [fault][gui][ha][metal][nfv][update] Project operations - RESPONSE NEEDED In-Reply-To: <7dac6c47-9401-776a-a0a7-02fdcc493938@linux.intel.com> References: <4C6705C0-D0FD-4C01-9B61-972C84CF71E4@gmail.com> <9A85D2917C58154C960D95352B22818BD07EC256@fmsmsx123.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F3606FB02@SHSMSX104.ccr.corp.intel.com> <7dac6c47-9401-776a-a0a7-02fdcc493938@linux.intel.com> Message-ID: <5C386174-F493-4AB8-941A-4811890D325F@gmail.com> Hi, I got feedback from users as well on the desire of having the flock services available standalone. I know it is not a priority at this point, but in my understanding we all acknowledged that this is something we would like to achieve. It makes me wonder if merging the project teams will make it harder to start that process and reach that goal? The current setup covers quite separate areas from functionality point of view which could make it harder for new contributors to find where to contribute once the teams are merged to cover all these areas. In that sense I think we should give it some thought how to name the new team if that is the move where the community and affected team members are leaning towards. I think ‘platform' is misleading as StarlingX itself is an integrated platform which means that we could merge a couple more teams into this one like networking for instance that does not have a dedicated repository at this point. Looking at the list of project teams it also doesn’t look like a match to the flock services either. Any thoughts on this from others? Once the teams and the community come to a decision we should make sure the wiki is updated accordingly and I also agree to setup weekly meetings to improve communication and visibility. Thanks, Ildikó > On 2019. Oct 1., at 2:00, Saul Wold wrote: > > > > On 9/30/19 3:52 PM, Xie, Cindy wrote: >> We have one customer in China evaluated these "Flocks" services, and they want to use them as building blocks into their product, but will do it one by one. Will the repo merge impact the possibility of customer of doing so? > I think this needs to be clarified, I do not think that the repos are being merged, just the project team so that there will be one "Flock" meeting wit a common PL / TL pair. > > > Sau! > > >> Thx. - cindy >> -----Original Message----- >> From: Jones, Bruce E >> Sent: Tuesday, October 1, 2019 5:47 AM >> To: Ildiko Vancsa ; starlingx >> Subject: Re: [Starlingx-discuss] [fault][gui][ha][metal][nfv][update] Project operations - RESPONSE NEEDED >> I have no objection to merging these projects. I think it makes sense, for now. Long term I think there is value in making the "Flock" projects more separate, and maybe even stand-alone, someday. >> I think it would also be good for the teams working on these projects to hold public meetings and post agenda & minutes to the list. >> brucej >> -----Original Message----- >> From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] >> Sent: Monday, September 30, 2019 5:38 AM >> To: starlingx >> Subject: [Starlingx-discuss] [fault][gui][ha][metal][nfv][update] Project operations - RESPONSE NEEDED >> Hi, >> I’m reaching out about an open review that proposes to merge six of the StarlingX projects into one: https://review.opendev.org/#/c/683410/ >> As this proposal affects 1/3 of the project teams I would like to have a community discussion about this rearrangement. >> I have a few questions to discuss: >> * Are all of these projects still active? >> * From functionality perspective the project teams cover very different areas. What are the motivating factors behind the proposed change? >> * Does this proposal help with organizing work and onboarding new contributors? >> I would like to have feedback from the project team members and community members on the above questions as well as in general in response to the proposed change. Please respond to this thread and share your views. >> I also checked some details and based on the StarlingX wiki the projects listed in the subject have no meetings and their wiki pages are also very brief in providing information about what they do and how to participate. I think this is something to look into in general and it should be the responsibility of all project teams and contributors. >> I propose to have a liaison from every team to look into addressing this topic to make sure this is an ongoing activity along with the technical development work. What do you think about this idea? >> 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 >> _______________________________________________ >> 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 ildiko.vancsa at gmail.com Tue Oct 1 10:10:51 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 1 Oct 2019 12:10:51 +0200 Subject: [Starlingx-discuss] Cancelling this week's community marketing planning call Message-ID: Hi, Due to conflicts I won’t be available to run this week’s community marketing call and decided to cancel. We have an ongoing discussion on the project overview slides that needs some input from anyone interested in contributing that activity. You can find all the pointers and notes on the meeting etherpad: https://etherpad.openstack.org/p/2019_StarlingX_Marketing_Plans Please chime in to the discussions on the etherpad and let me know if you have any questions prior to the next meeting. Thanks, Ildikó From cindy.xie at intel.com Tue Oct 1 11:03:22 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 1 Oct 2019 11:03:22 +0000 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35F28711@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F35F28711@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F36070616@SHSMSX104.ccr.corp.intel.com> All, As China team is on National Holiday this week, I am going to cancel this week's non-OpenStack distro meeting. Thanks! - cindy -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, October 2, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 * 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From lw2dht at gmail.com Tue Oct 1 13:21:43 2019 From: lw2dht at gmail.com (Mariano Ucha) Date: Tue, 1 Oct 2019 10:21:43 -0300 Subject: [Starlingx-discuss] Cannot allocate a VM - STX2.0-AIO-SX - Error500 In-Reply-To: <78e18725-6733-5d27-973c-4b58ee5eb890@windriver.com> References: <5d8eb3ac.1c69fb81.b2c36.3e40@mx.google.com> <78e18725-6733-5d27-973c-4b58ee5eb890@windriver.com> Message-ID: Thank you very much Chris, now my VM is running. I have one question because i try to allocate a vm with 512Mb and fails. But now i create a new flavor with 1Gb of RAM. My question is, Do I have to allocate so much hugepages like RAM i'll use in my VM. Thank you in advance. Mariano El lun., 30 sept. 2019 a las 13:11, Chris Friesen (< chris.friesen at windriver.com>) escribió: > It looks like you don't have any hugepages allocated. Lock the node, then > use the dashboard or the CLI (running something like "system > host-memory-modify controller-0 0 -1G 2" to allocate two 1G hugepages to > NUMA node 0). Then unlock the node. > > Kubernetes only allows a single size of hugepage, so whatever size we use > for the OpenStack guests has to match the hugepage size used for vswitch > (which defaults to 1G but can be changed to 2MB). > > Chris > > On 9/27/2019 7:13 PM, Mariano Ucha wrote: > > Hi Chris! Thank you for your answer. > > > > I have a All in One Simplex installation. I made it in a HW with 128Mb and > 2 socket with 8 core each. > > > > Do you prefer to crear a launchpad to keep logs and tracking? > > > > Outputs > > > > *What does "virsh capabilities|grep -C5 pages" show on the compute node?* > > > > controller-0:~$ virsh capabilities|grep -C5 pages > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > 67073312 > > 16506184 > > 0 > > 1 > > > > > > > > > > > > -- > > > > > > > > > > 67108860 > > 16515071 > > 0 > > 1 > > > > > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Tue Oct 1 14:39:44 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 1 Oct 2019 14:39:44 +0000 Subject: [Starlingx-discuss] K8S 1.16 version coming soon Message-ID: Giving people a heads up. The reviews for upversioning kubernetes from 1.15 to 1.16 are nearing completion and will be merging shortly. This likely will not have any impact on most people. If, however you have written or are using a custom kubernetes application that uses older configuration APIs, you may need to upgrade them. Information about that can be found here: https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/ Also note, the multus/cni docker image has been updated to contain the latest multus k8s 1.16 fixes here: https://github.com/intel/multus-cni/tree/kube-1.16-change The previous image was: nfvpe/multus:v3.2 The new image is pullable from: starlingx/multus:v3.2.16 Anyone behind a firewall who pulls docker images into a local repository will need to grab that. Al -------------- next part -------------- An HTML attachment was scrubbed... URL: From jose.perez.carranza at intel.com Tue Oct 1 15:50:33 2019 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Tue, 1 Oct 2019 15:50:33 +0000 Subject: [Starlingx-discuss] [Tets] New branch and Python3 support on robot suite Message-ID: <75B23001-FF21-4549-9949-14CB2F2E36EC@intel.com> Hi Last week a new branch (r/stx.2.0) was created on Test repo [1] in order to align it with the rest of StarlingX repos, also a series of patches were merged to enable the automated-robot-suite to be executed using python3. 1. https://opendev.org/starlingx/test Regards Jose -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Oct 1 15:56:25 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 1 Oct 2019 15:56:25 +0000 Subject: [Starlingx-discuss] Distro.openstack meeting nodes Oct 1 2019 Message-ID: <9A85D2917C58154C960D95352B22818BD07ECAE9@fmsmsx123.amr.corp.intel.com> We had limited attendance due to the Chinese holiday day. I received a brief update from Yong on the status of the Train migration but we did not have the right people in attendance to discuss the other topics. Brucej 10/1/2019 meeting * Upgrade to Train - Shuicheng suggests deferring Keystone upgrade until the CentOS RPM is available. Is this OK, will we hit compatibility issues? Not discussed * Test plan update - Yong - not discussed * Train migration update https://storyboard.openstack.org/#!/story/2006544 o Yong: Regarding Train upgrade, we are making some progress and very likely we will work out an EB for testing by Oct 11th, next Friday. And will try to catch up making patches ready before Feature Freeze Milestone Oct 16. * Upstream progress - not discussed * Opens - none -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcela.a.rosales.jimenez at intel.com Tue Oct 1 19:28:31 2019 From: marcela.a.rosales.jimenez at intel.com (Rosales Jimenez, Marcela A) Date: Tue, 1 Oct 2019 19:28:31 +0000 Subject: [Starlingx-discuss] [MultiOS] Team meeting 9/30/19 Message-ID: <34B537D7-F222-47C9-AA5C-5268932333B7@intel.com> Hi team, Here’s this week MultiOS minutes: https://etherpad.openstack.org/p/stx-multios Multi-OS team meeting - 9/30/2019 Agenda: openSUSE specs on gerrit: - maintenance - done - config - done - HA - WIP - NFV - review open - Fault - done - Ansible playbook - WIP - spec file not working as expected openSUSE specs integration with OBS: - maintenance - WIP - Waiting for mtce patch to be merged. - bsp-files to have spec, LICENSE, because build-iso needs bsp-files directory, also pxe-network uses this directory. - Not work for now on platform-kickstarts. - send rpmlintrc - config - done - HA - WIP - NFV - ready to be send - Fault - change in version 1.0.0 - StarlingX Puppet Where to keep rpmlintrc file? - on gerrit Versioning standardization for openSUSE - use 1.0.0 Review puppet dependendencies on openSUSE - Dominig sent an email - Test if puppet package works Auto-trigger OBS - gerrit hook or zuul ? - WIP, it is being discussed on the mailing list Yocto - kubernetes, docker and ceph almost finished as standalone services - next step: keystone, and running ansible playbook Marcela -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Tue Oct 1 20:08:34 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Tue, 01 Oct 2019 15:08:34 -0500 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: List of docker images required for "platform-integ-apps": BUILD_ID="20190930T230000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.15.3 k8s.gcr.io/kube-apiserver:v1.15.3 k8s.gcr.io/kube-scheduler:v1.15.3 k8s.gcr.io/kube-controller-manager:v1.15.3 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 nfvpe/multus:v3.2 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 k8s.gcr.io/coredns:1.3.1 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From Bill.Zvonar at windriver.com Tue Oct 1 20:39:03 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 1 Oct 2019 20:39:03 +0000 Subject: [Starlingx-discuss] Community Call (Oct 2, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007AFF122@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of the Community call tomorrow. Reminder that we're going to continue our 2.0 Retrospective tomorrow - what went well & areas for improvement. Feel free to add to the agenda at [0]... - upcoming elections and project/repo restructuring - 2.0 retrospective discussion - Brucej: The recent updates to Kubernetes 1.16 and to add Redfish support are both great candidates for Release Notes for 3.0, for docs.starlingX.io and maybe even a blog post. Can the teams doing the development also make the doc updates (with the help of the Docs team of course)? Are new tests or changes to existing tests needed? - and the usual standing topics... - Gerrit reviews that need attention - Red sanity learnings - unanswered requests for help in the mailing list - open AR review 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=20191002T1400 From maria.g.perez.ibarra at intel.com Tue Oct 1 22:27:39 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 1 Oct 2019 22:27:39 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191001 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-01 (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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Wed Oct 2 07:55:36 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Wed, 02 Oct 2019 02:55:36 -0500 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: List of docker images required for "platform-integ-apps": BUILD_ID="20191002T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.15.3 k8s.gcr.io/kube-apiserver:v1.15.3 k8s.gcr.io/kube-controller-manager:v1.15.3 k8s.gcr.io/kube-scheduler:v1.15.3 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 nfvpe/multus:v3.2 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 k8s.gcr.io/coredns:1.3.1 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From dominig.arfoll at fridu.net Wed Oct 2 08:55:58 2019 From: dominig.arfoll at fridu.net (Dominig ar Foll (Intel Open Source)) Date: Wed, 2 Oct 2019 10:55:58 +0200 Subject: [Starlingx-discuss] Call for contributors: CentOS 8.0 upgrade for StarlingX 4.0 In-Reply-To: <017efc5b-a425-8f1d-3469-9ce158908f5b@intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F35F28711@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F36055028@SHSMSX104.ccr.corp.intel.com> <2f1cd7b4-8f2c-9c0f-b1e6-34a08ffb237e@intel.com> <2FD5DDB5A04D264C80D42CA35194914F3605625F@SHSMSX104.ccr.corp.intel.com> <017efc5b-a425-8f1d-3469-9ce158908f5b@intel.com> Message-ID: <84e768ad-2360-1493-2868-513733d39d6d@fridu.net> Hello, most likely, the work done to port StarlingX on OpenSUSE should be a good reference to you. CentOS 8 and OpenSUSE 15.1 are both recent distros with newer kernel (4.12 for 15.1 and 5.3 for the soon to come 15.2). As I work currently on OpenSUSE, I can tell you that Python is not the most urgent issue as 2.7 can be installed in one single dnf command. This initialisations which are based on Ansible and Puppet is more likely going to be an issue as well as as systemD. If you look for ideas on how we progress on OpenSUSE you can have a check at our main build repo.   https://build.opensuse.org/project/show/Cloud:StarlingX:2.0 You will also find many back ports that I had to do in order to progress without breaking to many dependencies.     https://build.opensuse.org/project/subprojects/home:dominig:fedora-kickstart-sandbox As CentOS 8 is available on OpenSUSE build system (OBS), and that your spec files are located on git, I could create a CentOS 8 test build which most likely would break :-( Please let me know if that would be of any help to you. Regards. Dominig   On 27/09/2019 03:07, Yong Hu wrote: > Hi community members, > > Early this week, we saw RedHat has started releasing CentOS 8.0, which > is one of big commitments we made to StarlingX 4.0. > > As this upgrade from 7.6 to 8.0 is a non-trivial update, we might have > to address several aspects, such as: >   1). SRPM/RPM impacts to current build system. >   2). StarlingX patches on top of CentOS packages. >   3). Kernel (3.10.x to 4.18.x) and driver, standard and RT version >   4). Security fixes cumulatively merged >   5). Python 3.x support and >   6). Impacts to flocks and other services directly running on top of > CentOS. >   7). more others? > > > Here we would like to *call for contributors* to sign up this task and > kick off tech analysis and engineering efforts ASAP (better before TSC > officially approving this upgrade for Stx.4.0). > > On the other hand, if you are interested in this important mission but > with a bit concerns, NO worries at all. Anytime you reach out to > myself and Shuicheng (who is quite skillful and experienced in this > area after running through 2 rounds of CentOS upgrade successfully in > the past). > As a community, we are always around and supporting you. > > Thanks in advance! > Yong > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre From dominig.arfoll at fridu.net Wed Oct 2 10:59:33 2019 From: dominig.arfoll at fridu.net (Dominig ar Foll (Intel Open Source)) Date: Wed, 2 Oct 2019 12:59:33 +0200 Subject: [Starlingx-discuss] MultiOS: Image creation Cobbler a viable alternative ? Message-ID: Hello, while looking at the best option to create startlingX iso for OpenSUSE, I found the Redhat Cobbler project. Cobbler is seems to be able to create preconfigured iso from kickstart config files and present the advantage to run on multiple distro including CentOS and OpenSUSE. Could it be a viable model to unify our iso creation tasks for MultiOS ? Obviously some differences, such as packages naming would remain, but the process could be unified. As anyone some experience and feedback about that tool ? Could it be a viable solution ? Regards -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre From Bill.Zvonar at windriver.com Wed Oct 2 15:04:23 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 2 Oct 2019 15:04:23 +0000 Subject: [Starlingx-discuss] Community Call (Oct 2, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007AFF376@ALA-MBD.corp.ad.wrs.com> >From today's Community Call... - standing topics - any Gerrit reviews that need attention? - per Saul, there are a bunch of Multi-OS reviews out there, some are languishing - general request for the cores to take a look - sanity - any reds since last call? - no, all green - any unanswered calls for assistance on the mailing list? - nothing major since last time - Brucej: The recent updates to Kubernetes 1.16 and to add Redfish support are both great candidates for Release Notes for 3.0, for docs.starlingX.io and maybe even a blog post. - Can the teams doing the development also make the doc updates (with the help of the Docs team of course)? Are new tests or changes to existing tests needed? - general PSA about these changes - for Kubernetes 1.16, there are some Kubernetes API changes - MultiOS - openSUSE Status - Saul - mostly covered by the note above re: Gerrit reviews that need attention - generally making good progress - Project Consolidation - the review: https://review.opendev.org/#/c/683410/1 - Ildiko's email: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/006348.html - Bruce - how active are the projects in question? - Dariush - all active, not necessarily at the same time - with consolidation, there could be a regular meeting/minutes, like other projects - Bart - this would help get the Community involved, as such it wouldn't make sense to have regular meetings/communication for each of the current projects - the name - platform is too vague/confusing - we agreed to go with flock-services instead - Election - Ildiko will send a mail out reminding folks that the nomination period starts next week - 2.0 Retrospective - part two - Frank - a 'good thing' was how members of the Community picked up some of the Containerization work - Saul - documentation is key to enable this - Bruce - we need to make it easier for Community members to find work items that need to be done (we started using the 'help wanted' tag bug) - Bill - maybe add this as a standing item to the Community meeting? - Frank - the willingness to take this on, by the Community members that did, was important - Bruce - we have to improve on how to predict the content for the release - Mike - we could use more input from the Community on the content of a given topic - Ada - the test team could have been more involved, earlier, with the features - which they're doing now - the split between the 2 test teams was good for focus - AR Updates - Sep 25, 2019 -- Doc Team -- find a place for Sai Chandu's images/documentation - Oct 2: We believe this will go into our StarlingX-in-a-box topic as captured in https://storyboard.openstack.org/#!/story/2006622. - Bruce has volunteered to help Sai with the contribution: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/006316.html - Sep 11, 2019 -- TEAM -- complete project sub-team re-alignment, need to finish this before we start the PL/TL election cycle, per TSC and https://review.opendev.org/#/c/680514/ - Oct 2: feels like we're convering in time, per Project Consolidation topic above - Sep 11, 2019 -- Abraham/Build -- sort out how/when to finish this off the renaming of the to-be-renamed system-client (nee: cgcs-client) - Oct 2: help wanted - Sep 11, 2019 -- Bruce -- identify the feature documentation gaps - Oct 2: Mike will provide a top 5 list - July 31, 2019 -- Ada/Yang -- combine sanity runs/reports - Oct 2: per Ada, their target for this is Oct 28 - June 26, 2019 -- Abraham -- provide a forecast for providing a Docker image list - Oct 2: for now Christopher will send the list separately, and will get the info included in the sanity report - May 8, 2019 -- Frank -- follow up with CENGN on storage for really large files for reference in Launchpads - Oct 2: internal testing of web i/f is in progress -----Original Message----- From: Zvonar, Bill Sent: Tuesday, October 1, 2019 4:39 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: Community Call (Oct 2, 2019) Hi all, reminder of the Community call tomorrow. Reminder that we're going to continue our 2.0 Retrospective tomorrow - what went well & areas for improvement. Feel free to add to the agenda at [0]... - upcoming elections and project/repo restructuring - 2.0 retrospective discussion - Brucej: The recent updates to Kubernetes 1.16 and to add Redfish support are both great candidates for Release Notes for 3.0, for docs.starlingX.io and maybe even a blog post. Can the teams doing the development also make the doc updates (with the help of the Docs team of course)? Are new tests or changes to existing tests needed? - and the usual standing topics... - Gerrit reviews that need attention - Red sanity learnings - unanswered requests for help in the mailing list - open AR review 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=20191002T1400 From ada.cabrales at intel.com Wed Oct 2 20:37:19 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Wed, 2 Oct 2019 20:37:19 +0000 Subject: [Starlingx-discuss] [ Test ] Meeting notes for 10/01 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CEE53FB@FMSMSX114.amr.corp.intel.com> Agenda for 10/01 Attendees: Elio, JC, Richo, Yang, Cristopher, Fernando, Jose, Ada, Maria P 1. Sanity status - Cristopher / Yang Green status since last week On today's sanity: Bare metal is OK, virtual is not finishing deployment. Cristopher to debug. Yang - Having and alarm 800.11 in simplex after a fresh install. Cristopher has this one too - a launchpad will be created. On stand-by controller, after lock/unlock a application is re-applied. platform-integ-apps is being re-applied after locking standby controller - https://bugs.launchpad.net/starlingx/+bug/1846056 Unified sanity - JC Full list of test cases from both suites were compared. We could begin with the split of execution of sanity on 10/28. JC will have a meeting with Yang to close on details. We were not able to solve the natbox configuration. We work around it using a jump server. 2. stx.3.0 testing Tracker - https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit?usp=sharing Feature testing Backup and restore - Yang On going. Several configurations tested. Some duplex launchpads created. Distributed cloud - Yang Looks like the configuration has been figured out - dist cloud up and being monitored. Up-version openstack to train - JC The testing will be the same as in stx.2.0 (stein). Cindy's team will check on differences and will propose new/additional tests. No date defined yet. JC to check the story for getting a start date. GPU for K8 - Richo Having contact with Ran. Doing experiments and searching for hardware to test this one. We don't have hardware available locally. We are getting hardware lent by China team (to be accessed remotely) (around the first week of October). Trying to setup a NUC to begin with it, but not able to download the ISO built in China. TSN - Elio Testing is Done. Documentation is on the wiki. https://wiki.openstack.org/wiki/StarlingX/Networking/TSN R2 to R3 upgrades - Yang Not staffed - out? Redfish - Cristopher to begin next week Feature is available. Cristopher has started to review the documentation. Infrastructure and cluster monitoring - Yang Not started yet. Performance tuning going on. Will begin later. Please keep the tracker updated. Regression Plan ready - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit?usp=sharing Yang is reviewing the plan and will provide feedback. Ada to send this plan to the community asking for reviews. 3. stx.2.0 maintenance release ISO to be built on 10/3 Automated regression starting on 10/4 - report next week Elio and Yang are aware this is coming. Yang will have someone ready to launch the regression on Friday. 4. Requests status Testing on fix for - https://bugs.launchpad.net/starlingx/+bug/1817936 - Elio to work on this. Testing done in standard. Running now in simplex. The goal is to finish today. Provide a list of docker images downloaded at runtime - https://bugs.launchpad.net/starlingx/+bug/1834504 - Cristopher to take this one. Done. The list is taken after the setup is done (before starting sanity) and sent to the mailing list. Please update the storyboard. 5. Opens None From ada.cabrales at intel.com Wed Oct 2 20:52:29 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Wed, 2 Oct 2019 20:52:29 +0000 Subject: [Starlingx-discuss] [ Test ] stx.3.0 regression test plan Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CEE5416@FMSMSX114.amr.corp.intel.com> Hello, The regression test plan (automated and manual) is in [0]. Please let us know your comments. Thanks Ada [0] https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit?usp=sharing From michael.l.tullis at intel.com Wed Oct 2 21:50:12 2019 From: michael.l.tullis at intel.com (Tullis, Michael L) Date: Wed, 2 Oct 2019 21:50:12 +0000 Subject: [Starlingx-discuss] [docs][meetings] docs team meeting minutes 2019-10-02 Message-ID: <3808363B39586544A6839C76CF81445EA1BE2E71@ORSMSX104.amr.corp.intel.com> Join us if you have interest in StarlingX docs! We meet Wednesdays, and call logistics are here: https://wiki.openstack.org/wiki/Starlingx/Meetings. Our etherpad is here: https://etherpad.openstack.org/p/stx-documentation. -- Mike Current agenda and notes 2019-10-02 * Mike -- welcome Mary Camp to the doc team -- * All -- reviews in progress and recent merges -- § See summary at https://review.opendev.org/#/q/project:starlingx/docs. § Recent merges. Great job team! · https://review.opendev.org/#/c/686036/ -- Fix error in AIO-SX baremetal install guide closing bug #1845139 -- MERGED · https://review.opendev.org/#/c/685863/ -- Add new sections to Ansible bootstrap configs -- MERGED · https://review.opendev.org/#/c/685470/ -- Update Ansible bootstrap info for clarity -- MERGED · https://review.opendev.org/#/c/685179/ -- Implement persistent URLs in versioned docs -- MERGED · https://review.opendev.org/#/c/684857/ -- Update install guides landing page -- MERGED · https://review.opendev.org/#/c/684852/ -- Minor updates to R2 install section -- MERGED · https://review.opendev.org/#/c/684148/ -- Improve readability of install guides R2 -- MERGED § We have 2 open. Let's take a look to see how we can push these through. · https://review.opendev.org/#/c/679896/ tied to https://bugs.launchpad.net/starlingx/+bug/1837931 -- Add instructions for remote CLI access to Openstack -- This bug is not fully resolved with the current review, but we now have what we need in https://drive.google.com/file/d/1yOK2jQ1ozUNtneObv87CVPajqCVGNkBC/. Kris will retire https://review.opendev.org/#/c/679896/ and create a new review for the REST API. Erich's CLI contribution is now under https://storyboard.openstack.org/#!/story/2006289 as subtask 36280. · https://review.opendev.org/#/c/684820/ -- Introduction editorial updates -- This is Mary's sandbox for Gerrit familiarity and is set to workflow -1 on purpose. No urgency. * Abraham and all -- bug status -- https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs § Resolution for all current bugs should be pushed to the R2 docs, not versioned for R3. § Current status: 3 bugs open, 1 high, 1 med, 1 low. § https://bugs.launchpad.net/starlingx/+bug/1844656 -- Kris will verified that https://review.opendev.org/#/c/682967/ should have fixed it, but then there were a bunch of follow-on comments that we need to look at again. Kris/Mary will open a review to address comment #7 in the launchpad. § https://bugs.launchpad.net/starlingx/+bug/1837931 -- Greg has provided the content for the bug fix. Thanks greg! See https://drive.google.com/file/d/1yOK2jQ1ozUNtneObv87CVPajqCVGNkBC/. § https://bugs.launchpad.net/starlingx/+bug/1835207 -- Abraham will ask for help in the community meeting to get this closed. * Mike -- update to misc. guides -- § The contributor guide at https://docs.starlingx.io/contributor/doc_contribute_guide.html needs another look. KM will address. § Do we need versioned build guides? See https://drive.google.com/file/d/1qeVdyQJ0GlmGzmcIhJtDpKVrdfYiN3ZS. After team discussion and line-by-line comparison, we see that likely no versioning is required. We'll try to close before R3 so we don't unnecessarily create a versioned build guide for R3. * Mike -- future/planned reviews for installation/deployment guides -- § A recent code change will impact bare metal use cases (and possibly others). · See https://drive.google.com/file/d/1pic5wr_69fJb94-o3JM7U2xKMJ0HpGJZ for details. · This is for R3 and should not be rolled into R2 docs. So it will be rolled into the "upcoming release" section. § Erich Cordoba Malibran wrote an installation/deployment guide that mostly overlaps with our own. · We need to review it to see if we can pull any goodness into our official docs. Greg will review. Could be the starting point for StarlingX in a box. · See https://ericho.github.io/2019-09-12-deploy-virtual-starlingx/ and http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/006059.html for details. * Mike -- report out on any progress or plans for R3 stories -- § Where we can add the most value right now is to add the stubbed out landing page for https://storyboard.openstack.org/#!/story/2006289. See http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/006127.html for more info. We've discussed this in the community meeting and on the mailing list. We'll start this after the latest retrofitted changes to the R2 guides merge. This fits into the "gap" discussion from community. § We need to get more help from the community. In the meeting this morning, they suggested we provide an explicit "top 5" list as an invitation. This should be stories or sub-tasks of stories. Kris, Mary, and Mike will meet offline to refine this list and link to stories: · Distributed Cloud · GPU Kubernetes Plugin · TSN · Redfish · Infrastructure and cluster § Background: · R3 release is currently planned for early December. · Current R3 doc stories are here. We'll add to this list -- https://storyboard.openstack.org/#!/story/list?tags=stx.docs&tags=stx.3.0 -- · The community team is tracking top stories. I submitted these two for the doc team -- https://drive.google.com/file/d/1dXFLc6f4d5MA2l7rRBMnfyk4X6wZ07wX Action required (AR) summary Completed ARs are archived here: https://etherpad.openstack.org/p/stx-documentation-files-003 · -- -- · 2019-05-15 -- Abraham -- Review these code and terminology changes impacting user docs -- https://drive.google.com/file/d/1sCB-lrWhDIJLNAGWBt7wJ1_JxY21m71p -- and report back on specific actions required. · 2019-09-18 -- Greg -- Review Erich's contribution at https://ericho.github.io/2019-09-12-deploy-virtual-starlingx/ to see if we need to retrofit anything into our existing guides. Also recommend anything toward "StarlingX in a box." · 2019-10-02 -- Kris -- Retire https://review.opendev.org/#/c/679896/ and create a new review for the REST API to close https://bugs.launchpad.net/starlingx/+bug/1837931 using Greg's info at https://drive.google.com/file/d/1yOK2jQ1ozUNtneObv87CVPajqCVGNkBC/. · 2019-10-02 -- Kris/Mary -- Open a review to address comment #7 in https://bugs.launchpad.net/starlingx/+bug/1844656. · 2019-10-02 -- Abraham -- Ask for help in the community meeting to get https://bugs.launchpad.net/starlingx/+bug/1835207 closed. · 2019-10-02 -- Kris, Mary, Mike -- Meet Monday to refine R3 stories, especially the subtasks for the new config guide. Also finish identifying the top 5 areas where the community could help us. -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Wed Oct 2 22:57:43 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Wed, 2 Oct 2019 22:57:43 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191002 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Oct 3 15:28:57 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 3 Oct 2019 15:28:57 +0000 Subject: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested Message-ID: <151EE31B9FCCA54397A757BC674650F0C15C8A58@ALA-MBD.corp.ad.wrs.com> Hi Scott, All the fixes expected for the stx.2.0.1 maintenance release have now been merged. Please trigger an RC build for the branch. Ada's team is ready to perform the sanity/regression on the build. Once testing is completed successfully, please label the build and branch as 2.0.1 -- the first maintenance release for stx.2.0. Core reviewers, Please do not allow any code merges on the r/stx.2.0 branch until the testing and labeling are done. References: - stx.2.0 branch: https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.2.0 Thanks, Ghada On behalf of the StarlingX release team From scott.little at windriver.com Thu Oct 3 15:31:04 2019 From: scott.little at windriver.com (Scott Little) Date: Thu, 3 Oct 2019 11:31:04 -0400 Subject: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested In-Reply-To: <151EE31B9FCCA54397A757BC674650F0C15C8A58@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0C15C8A58@ALA-MBD.corp.ad.wrs.com> Message-ID: <83f6f90a-58af-a109-836c-e26558343841@windriver.com> Is this to be an ISO only build?   Or should I generate a full set of docker images as well ? Scott On 2019-10-03 11:28 a.m., Khalil, Ghada wrote: > Hi Scott, > All the fixes expected for the stx.2.0.1 maintenance release have now been merged. Please trigger an RC build for the branch. > Ada's team is ready to perform the sanity/regression on the build. Once testing is completed successfully, please label the build and branch as 2.0.1 -- the first maintenance release for stx.2.0. > > Core reviewers, > Please do not allow any code merges on the r/stx.2.0 branch until the testing and labeling are done. > > References: > - stx.2.0 branch: https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.2.0 > > > Thanks, > Ghada > On behalf of the StarlingX release team From Ghada.Khalil at windriver.com Thu Oct 3 15:41:08 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 3 Oct 2019 15:41:08 +0000 Subject: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested In-Reply-To: <83f6f90a-58af-a109-836c-e26558343841@windriver.com> References: <151EE31B9FCCA54397A757BC674650F0C15C8A58@ALA-MBD.corp.ad.wrs.com> <83f6f90a-58af-a109-836c-e26558343841@windriver.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0C15C8A91@ALA-MBD.corp.ad.wrs.com> Please generate a full set of docker images as well as the ISO. Thank you. Ghada -----Original Message----- From: Little, Scott Sent: Thursday, October 03, 2019 11:31 AM To: Khalil, Ghada; Cabrales, Ada; starlingx-discuss at lists.starlingx.io Subject: Re: stx.2.0.1 maintenance RC build Requested Is this to be an ISO only build?   Or should I generate a full set of docker images as well ? Scott On 2019-10-03 11:28 a.m., Khalil, Ghada wrote: > Hi Scott, > All the fixes expected for the stx.2.0.1 maintenance release have now been merged. Please trigger an RC build for the branch. > Ada's team is ready to perform the sanity/regression on the build. Once testing is completed successfully, please label the build and branch as 2.0.1 -- the first maintenance release for stx.2.0. > > Core reviewers, > Please do not allow any code merges on the r/stx.2.0 branch until the testing and labeling are done. > > References: > - stx.2.0 branch: > https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.2.0 > > > Thanks, > Ghada > On behalf of the StarlingX release team From jimmy at openstack.org Thu Oct 3 16:43:26 2019 From: jimmy at openstack.org (Jimmy McArthur) Date: Thu, 03 Oct 2019 11:43:26 -0500 Subject: [Starlingx-discuss] Proposed Forum Schedule Message-ID: <5D96252E.3000404@openstack.org> Hello! I'm attaching a PDF of the proposed Shanghai Forum Schedule. I'll publish the same on the actual website later this afternoon. However, there is still time for feedback/time changes, assuming there aren't conflicts for speakers/moderators. This is also available for download here: https://drive.google.com/file/d/1qp0I9xnyOK3mhBitQnk2a7VuS9XClvyF/view?usp=sharing Please respond to this thread with any concerns. Cheers, Jimmy -------------- next part -------------- A non-text attachment was scrubbed... Name: Forum Mock Schedule.pdf Type: application/pdf Size: 88937 bytes Desc: not available URL: From scott.little at windriver.com Thu Oct 3 18:41:12 2019 From: scott.little at windriver.com (Scott Little) Date: Thu, 3 Oct 2019 14:41:12 -0400 Subject: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested In-Reply-To: <151EE31B9FCCA54397A757BC674650F0C15C8A91@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0C15C8A58@ALA-MBD.corp.ad.wrs.com> <83f6f90a-58af-a109-836c-e26558343841@windriver.com> <151EE31B9FCCA54397A757BC674650F0C15C8A91@ALA-MBD.corp.ad.wrs.com> Message-ID: Build underway.  ETA 9pm EST Scott On 2019-10-03 11:41 a.m., Khalil, Ghada wrote: > Please generate a full set of docker images as well as the ISO. Thank you. > > Ghada > > -----Original Message----- > From: Little, Scott > Sent: Thursday, October 03, 2019 11:31 AM > To: Khalil, Ghada; Cabrales, Ada; starlingx-discuss at lists.starlingx.io > Subject: Re: stx.2.0.1 maintenance RC build Requested > > Is this to be an ISO only build?   Or should I generate a full set of docker images as well ? > > Scott > > > > On 2019-10-03 11:28 a.m., Khalil, Ghada wrote: >> Hi Scott, >> All the fixes expected for the stx.2.0.1 maintenance release have now been merged. Please trigger an RC build for the branch. >> Ada's team is ready to perform the sanity/regression on the build. Once testing is completed successfully, please label the build and branch as 2.0.1 -- the first maintenance release for stx.2.0. >> >> Core reviewers, >> Please do not allow any code merges on the r/stx.2.0 branch until the testing and labeling are done. >> >> References: >> - stx.2.0 branch: >> https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.2.0 >> >> >> Thanks, >> Ghada >> On behalf of the StarlingX release team > From build.starlingx at gmail.com Thu Oct 3 18:47:46 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 3 Oct 2019 14:47:46 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_BUILD_2.0 - Build # 41 - Failure! Message-ID: <246849216.283.1570128467788.JavaMail.javamailuser@localhost> Project: STX_BUILD_2.0 Build #: 41 Status: Failure Timestamp: 20191003T184022Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191003T184022Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true From build.starlingx at gmail.com Thu Oct 3 19:21:40 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 3 Oct 2019 15:21:40 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_BUILD_2.0 - Build # 42 - Still Failing! In-Reply-To: <1316144683.281.1570128465013.JavaMail.javamailuser@localhost> References: <1316144683.281.1570128465013.JavaMail.javamailuser@localhost> Message-ID: <2047496670.288.1570130501356.JavaMail.javamailuser@localhost> Project: STX_BUILD_2.0 Build #: 42 Status: Still Failing Timestamp: 20191003T191516Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191003T191516Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true From cindy.xie at intel.com Tue Oct 1 11:03:33 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 1 Oct 2019 11:03:33 +0000 Subject: [Starlingx-discuss] Canceled: Weekly StarlingX non-OpenStack distro meeting Message-ID: <2FD5DDB5A04D264C80D42CA35194914F3607063B@SHSMSX104.ccr.corp.intel.com> * 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4054 bytes Desc: not available URL: From build.starlingx at gmail.com Thu Oct 3 19:33:41 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 3 Oct 2019 15:33:41 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_BUILD_2.0 - Build # 43 - Still Failing! In-Reply-To: <1830062816.286.1570130498810.JavaMail.javamailuser@localhost> References: <1830062816.286.1570130498810.JavaMail.javamailuser@localhost> Message-ID: <697743267.292.1570131222894.JavaMail.javamailuser@localhost> Project: STX_BUILD_2.0 Build #: 43 Status: Still Failing Timestamp: 20191003T192736Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191003T192736Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true From build.starlingx at gmail.com Thu Oct 3 20:00:15 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 3 Oct 2019 16:00:15 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_BUILD_2.0 - Build # 44 - Still Failing! In-Reply-To: <1688636550.290.1570131220242.JavaMail.javamailuser@localhost> References: <1688636550.290.1570131220242.JavaMail.javamailuser@localhost> Message-ID: <369979094.296.1570132816693.JavaMail.javamailuser@localhost> Project: STX_BUILD_2.0 Build #: 44 Status: Still Failing Timestamp: 20191003T195419Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191003T195419Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true From build.starlingx at gmail.com Thu Oct 3 20:54:11 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 3 Oct 2019 16:54:11 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_BUILD_2.0 - Build # 45 - Still Failing! In-Reply-To: <1059093717.294.1570132813781.JavaMail.javamailuser@localhost> References: <1059093717.294.1570132813781.JavaMail.javamailuser@localhost> Message-ID: <1938668745.300.1570136052605.JavaMail.javamailuser@localhost> Project: STX_BUILD_2.0 Build #: 45 Status: Still Failing Timestamp: 20191003T204720Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191003T204720Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true From scott.little at windriver.com Thu Oct 3 21:08:37 2019 From: scott.little at windriver.com (Scott Little) Date: Thu, 3 Oct 2019 17:08:37 -0400 Subject: [Starlingx-discuss] [build-report] STX_BUILD_2.0 - Build # 41 - Failure! In-Reply-To: <246849216.283.1570128467788.JavaMail.javamailuser@localhost> References: <246849216.283.1570128467788.JavaMail.javamailuser@localhost> Message-ID: <5410b3e3-229e-9eff-aec2-7558f0799b2d@windriver.com> Repos again.  Gotta get that repos update in stx-tools approved and propagated to 2.0 stream.  I'll jury rig it for now. Scott On 2019-10-03 2:47 p.m., build.starlingx at gmail.com wrote: > Project: STX_BUILD_2.0 > Build #: 41 > Status: Failure > Timestamp: 20191003T184022Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191003T184022Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: 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 bruce.e.jones at intel.com Thu Oct 3 21:44:45 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 3 Oct 2019 21:44:45 +0000 Subject: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested In-Reply-To: <151EE31B9FCCA54397A757BC674650F0C15C8A58@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0C15C8A58@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BD07EE54A@fmsmsx123.amr.corp.intel.com> I might have missed this today since I was late to the release meeting. There are still bugs open against stx.2.0. Is the plan to move those to 3.0? Thanks! brucej -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, October 3, 2019 8:29 AM To: Little, Scott ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested Importance: High Hi Scott, All the fixes expected for the stx.2.0.1 maintenance release have now been merged. Please trigger an RC build for the branch. Ada's team is ready to perform the sanity/regression on the build. Once testing is completed successfully, please label the build and branch as 2.0.1 -- the first maintenance release for stx.2.0. Core reviewers, Please do not allow any code merges on the r/stx.2.0 branch until the testing and labeling are done. References: - stx.2.0 branch: https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.2.0 Thanks, Ghada On behalf of the StarlingX release team _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From maria.g.perez.ibarra at intel.com Thu Oct 3 21:45:32 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 3 Oct 2019 21:45:32 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191003 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-03 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [FAIL] 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 [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [FAIL] 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 [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] Ansible bootstrap fails - https://kubernetes-charts.storage.googleapis.com cannot be reached https://bugs.launchpad.net/starlingx/+bug/1846540 Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Oct 3 21:52:02 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 3 Oct 2019 21:52:02 +0000 Subject: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested In-Reply-To: <9A85D2917C58154C960D95352B22818BD07EE54A@fmsmsx123.amr.corp.intel.com> References: <151EE31B9FCCA54397A757BC674650F0C15C8A58@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BD07EE54A@fmsmsx123.amr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0C15C90F5@ALA-MBD.corp.ad.wrs.com> No, the plan is to have additional maintenance releases when stx.2.0 gating bug fixes and CVE fixes are available. Nominal cadence is every 4-6wks, assuming there are fixes to warrant a build. That being said, the domain PL can review with the TL and they can decide to re-gate bugs from stx.2.0 to stx.3.0 depending on some rationale (risk, frequency, etc). This needs to be done on an individual bug basis. There is no plan for a general re-gate. Hope this clarifies things. Ghada -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, October 03, 2019 5:45 PM To: Khalil, Ghada Cc: Little, Scott; Cabrales, Ada; starlingx-discuss at lists.starlingx.io Subject: RE: stx.2.0.1 maintenance RC build Requested I might have missed this today since I was late to the release meeting. There are still bugs open against stx.2.0. Is the plan to move those to 3.0? Thanks! brucej -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, October 3, 2019 8:29 AM To: Little, Scott ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested Importance: High Hi Scott, All the fixes expected for the stx.2.0.1 maintenance release have now been merged. Please trigger an RC build for the branch. Ada's team is ready to perform the sanity/regression on the build. Once testing is completed successfully, please label the build and branch as 2.0.1 -- the first maintenance release for stx.2.0. Core reviewers, Please do not allow any code merges on the r/stx.2.0 branch until the testing and labeling are done. References: - stx.2.0 branch: https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.2.0 Thanks, Ghada On behalf of the StarlingX release team _______________________________________________ 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 Fri Oct 4 02:29:19 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 3 Oct 2019 22:29:19 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 128 - Failure! Message-ID: <373435987.306.1570156160450.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 128 Status: Failure Timestamp: 20191003T234444Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191003T205840Z/logs -------------------------------------------------------------------------------- Parameters HOST_PORT: 80 MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-2.0/20191003T205840Z OS: centos MY_REPO: /localdisk/designer/jenkins/rc-2.0/cgcs-root BASE_VERSION: rc-2.0-stable-20191003T205840Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191003T205840Z/logs REGISTRY_USERID: slittlewrs HOST: build.starlingx.cengn.ca LATEST_PREFIX: rc-2.0 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/2.0/centos/20191003T205840Z/logs PUBLISH_TIMESTAMP: 20191003T205840Z FLOCK_VERSION: rc-2.0-centos-stable-20191003T205840Z PREFIX: rc-2.0 TIMESTAMP: 20191003T205840Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/2.0/centos/20191003T205840Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Fri Oct 4 02:29:23 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 3 Oct 2019 22:29:23 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 134 - Failure! Message-ID: <1099471486.309.1570156164174.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 134 Status: Failure Timestamp: 20191003T232721Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191003T205840Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: r/stx.2.0 MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-2.0/20191003T205840Z OS: centos MUNGED_BRANCH: rc-2.0 MY_REPO: /localdisk/designer/jenkins/rc-2.0/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191003T205840Z/logs MASTER_BUILD_NUMBER: 46 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/2.0/centos/20191003T205840Z/logs MASTER_JOB_NAME: STX_BUILD_2.0 MY_REPO_ROOT: /localdisk/designer/jenkins/rc-2.0 PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/2.0/centos PUBLISH_TIMESTAMP: 20191003T205840Z DOCKER_BUILD_ID: jenkins-rc-2.0-20191003T205840Z-builder TIMESTAMP: 20191003T205840Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/rc/2.0/centos/20191003T205840Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/2.0/centos/20191003T205840Z/outputs From build.starlingx at gmail.com Fri Oct 4 02:29:27 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 3 Oct 2019 22:29:27 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_BUILD_2.0 - Build # 46 - Still Failing! In-Reply-To: <960478227.298.1570136049839.JavaMail.javamailuser@localhost> References: <960478227.298.1570136049839.JavaMail.javamailuser@localhost> Message-ID: <1038983121.312.1570156167817.JavaMail.javamailuser@localhost> Project: STX_BUILD_2.0 Build #: 46 Status: Still Failing Timestamp: 20191003T205840Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191003T205840Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true From Ghada.Khalil at windriver.com Fri Oct 4 12:51:37 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 4 Oct 2019 12:51:37 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Oct 3/2019 Message-ID: <151EE31B9FCCA54397A757BC674650F0C15C9224@ALA-MBD.corp.ad.wrs.com> Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.2.0 - Maintenance Release stx.2.0.1 RC build requested - Ada confirmed that her team will start testing tomorrow (once the build is available) - October 4 - Expect to be on track to release stx.2.0.1 by October 11 - Open Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2.0 - Count: 9 stx.3.0 - Feature plans are updated in the google sheet - Regression Test Plan Tracker: - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 - Regression starting next week - October 7 - Feature Test Plan Tracker: - https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit#gid=968103774 Kata Container work - what's going on with this? https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) - Cindy said that her team is trying to get this info stx.3.0 MS-3 - Need to understand the impact of the changes on the code base -- risk to the current regression / release dates - Ada's team is unable to cover feature testing, so Cindy indicated that her team can cover the testing. - Action: Discuss further in the next distro.other meeting When do we start planning for stx.4.0? - Open Infra Summit: Nov 2-4 -- limited attendance from stx members due to location - Bruce: Should we have a community gathering somewhere else? 2.0 Retrospective - what tangible actions do we want to take for 3.0? - Agreed to prepare draft Release Notes at RC1 ...instead of after the release - Documentation - Prioritize the documentation gaps/asks earlier in the release cycle -- at MS-3 - Release team to take a more active role in facilitating this Regards, Ghada From jimmy at openstack.org Fri Oct 4 12:55:29 2019 From: jimmy at openstack.org (Jimmy McArthur) Date: Fri, 04 Oct 2019 07:55:29 -0500 Subject: [Starlingx-discuss] Proposed Forum Schedule Message-ID: <5D974141.5060006@openstack.org> The forum schedule is now live: https://www.openstack.org/summit/shanghai-2019/summit-schedule/global-search?t=forum If you'd prefer to use the spreadsheet view: https://drive.google.com/file/d/1qp0I9xnyOK3mhBitQnk2a7VuS9XClvyF Please let Kendall Nelson or myself know as soon as possible if you see any conflicts. Cheers, Jimmy Jimmy McArthur wrote: > Hello! > > I'm attaching a PDF of the proposed Shanghai Forum Schedule. I'll > publish the same on the actual website later this afternoon. However, > there is still time for feedback/time changes, assuming there aren't > conflicts for speakers/moderators. > > This is also available for download here: > https://drive.google.com/file/d/1qp0I9xnyOK3mhBitQnk2a7VuS9XClvyF/view?usp=sharing > > > Please respond to this thread with any concerns. > > Cheers, > Jimmy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Fri Oct 4 15:16:28 2019 From: scott.little at windriver.com (Scott Little) Date: Fri, 4 Oct 2019 11:16:28 -0400 Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 128 - Failure! In-Reply-To: <373435987.306.1570156160450.JavaMail.javamailuser@localhost> References: <373435987.306.1570156160450.JavaMail.javamailuser@localhost> Message-ID: Error message suggests we ran out of space on /tmp within the docker building stx-nova mkdir -p /tmp/wheels/ tar xf /tmp/wheels.tar.gz '--exclude=.*' -C /tmp/wheels/ PuLP-1.6.9-py2-none-any.whl: Wrote only 512 of 10240 bytes pycadf-2.9.0-py2.py3-none-any.whl: Cannot open: No space left on device pycparser-2.19-py2.py3-none-any.whl: Cannot open: No space left on device /dev on build host was down to a 64 M Cleaning some old docker containers/images and restarting the build... Scott On 2019-10-03 10:29 p.m., build.starlingx at gmail.com wrote: > Project: STX_build_docker_flock_images > Build #: 128 > Status: Failure > Timestamp: 20191003T234444Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191003T205840Z/logs > -------------------------------------------------------------------------------- > Parameters > > HOST_PORT: 80 > MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-2.0/20191003T205840Z > OS: centos > MY_REPO: /localdisk/designer/jenkins/rc-2.0/cgcs-root > BASE_VERSION: rc-2.0-stable-20191003T205840Z > PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191003T205840Z/logs > REGISTRY_USERID: slittlewrs > HOST: build.starlingx.cengn.ca > LATEST_PREFIX: rc-2.0 > PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/2.0/centos/20191003T205840Z/logs > PUBLISH_TIMESTAMP: 20191003T205840Z > FLOCK_VERSION: rc-2.0-centos-stable-20191003T205840Z > PREFIX: rc-2.0 > TIMESTAMP: 20191003T205840Z > BUILD_STREAM: stable > REGISTRY_ORG: starlingx > PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/2.0/centos/20191003T205840Z/outputs > REGISTRY: docker.io > > _______________________________________________ > 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 Angie.Wang at windriver.com Fri Oct 4 16:48:20 2019 From: Angie.Wang at windriver.com (Wang, Jing (Angie)) Date: Fri, 4 Oct 2019 16:48:20 +0000 Subject: [Starlingx-discuss] [docs]Changing Ansible docker_registries's "unified" key Message-ID: Hi All, I am changing the Ansible docker_registries's "unified" key to "defaults". From docker_registries: unified: url: to docker_registries: defaults: url: And the semantics for "defaults" is a bit different as before. The "defaults" now defines common values that to be applied to all override-able public registries but the values under the specific registries, if specified, will take precedence over the values under defaults registry. If you only use defaults key, it will apply url, username and password for all registries (docker.io, quay.io, gcr.io, k8s.gcr.io, docker.elastic.co) e.g. docker_registries: defaults: url: unified.io username: adminUser password: adminPass If you have something special for some particular registry/registries, you can override the values by specifying them under its own entry. e.g. docker_registries: docker.io: username: dockerUser password: dockerPass k8s.gcr.io: username: k8sUser password: k8sPass defaults: url: unified.io username: adminUser password: adminPass This affects anyone with a setup that specifies alternate docker registries that using "unified" key as they will need to change their Ansible localhost.yml files to use "defaults" after this commit. The change is currently under review: https://review.opendev.org/#/c/686057/ Thanks, -Angie -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.l.tullis at intel.com Fri Oct 4 17:00:42 2019 From: michael.l.tullis at intel.com (Tullis, Michael L) Date: Fri, 4 Oct 2019 17:00:42 +0000 Subject: [Starlingx-discuss] [docs]Changing Ansible docker_registries's "unified" key In-Reply-To: References: Message-ID: <3808363B39586544A6839C76CF81445EA1BE484B@ORSMSX104.amr.corp.intel.com> Thanks Angie. I'll put this on the agenda for our upcoming doc team meeting. We'll assess impact to existing and future docs. Thx. -- Mike From: Wang, Jing (Angie) Sent: Friday, October 4, 2019 10:48 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [docs]Changing Ansible docker_registries's "unified" key Hi All, I am changing the Ansible docker_registries's "unified" key to "defaults". From docker_registries: unified: url: to docker_registries: defaults: url: And the semantics for "defaults" is a bit different as before. The "defaults" now defines common values that to be applied to all override-able public registries but the values under the specific registries, if specified, will take precedence over the values under defaults registry. If you only use defaults key, it will apply url, username and password for all registries (docker.io, quay.io, gcr.io, k8s.gcr.io, docker.elastic.co) e.g. docker_registries: defaults: url: unified.io username: adminUser password: adminPass If you have something special for some particular registry/registries, you can override the values by specifying them under its own entry. e.g. docker_registries: docker.io: username: dockerUser password: dockerPass k8s.gcr.io: username: k8sUser password: k8sPass defaults: url: unified.io username: adminUser password: adminPass This affects anyone with a setup that specifies alternate docker registries that using "unified" key as they will need to change their Ansible localhost.yml files to use "defaults" after this commit. The change is currently under review: https://review.opendev.org/#/c/686057/ Thanks, -Angie -------------- next part -------------- An HTML attachment was scrubbed... URL: From Angie.Wang at windriver.com Fri Oct 4 18:21:07 2019 From: Angie.Wang at windriver.com (Wang, Jing (Angie)) Date: Fri, 4 Oct 2019 18:21:07 +0000 Subject: [Starlingx-discuss] [docs]Changing Ansible docker_registries's "unified" key In-Reply-To: References: Message-ID: Hi All, The commit https://review.opendev.org/#/c/686057/ has been merged into master. Thanks -Angie From: Wang, Jing (Angie) [mailto:Angie.Wang at windriver.com] Sent: October-04-19 12:48 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [docs]Changing Ansible docker_registries's "unified" key Hi All, I am changing the Ansible docker_registries's "unified" key to "defaults". From docker_registries: unified: url: to docker_registries: defaults: url: And the semantics for "defaults" is a bit different as before. The "defaults" now defines common values that to be applied to all override-able public registries but the values under the specific registries, if specified, will take precedence over the values under defaults registry. If you only use defaults key, it will apply url, username and password for all registries (docker.io, quay.io, gcr.io, k8s.gcr.io, docker.elastic.co) e.g. docker_registries: defaults: url: unified.io username: adminUser password: adminPass If you have something special for some particular registry/registries, you can override the values by specifying them under its own entry. e.g. docker_registries: docker.io: username: dockerUser password: dockerPass k8s.gcr.io: username: k8sUser password: k8sPass defaults: url: unified.io username: adminUser password: adminPass This affects anyone with a setup that specifies alternate docker registries that using "unified" key as they will need to change their Ansible localhost.yml files to use "defaults" after this commit. The change is currently under review: https://review.opendev.org/#/c/686057/ Thanks, -Angie -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Fri Oct 4 18:48:16 2019 From: scott.little at windriver.com (Scott Little) Date: Fri, 4 Oct 2019 14:48:16 -0400 Subject: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0C15C8A58@ALA-MBD.corp.ad.wrs.com> <83f6f90a-58af-a109-836c-e26558343841@windriver.com> <151EE31B9FCCA54397A757BC674650F0C15C8A91@ALA-MBD.corp.ad.wrs.com> Message-ID: ETA on the latest build attempt is 5pm EST (Friday, Oct 4) Scott On 2019-10-03 2:41 p.m., Scott Little wrote: > Build underway.  ETA 9pm EST > > Scott > > > On 2019-10-03 11:41 a.m., Khalil, Ghada wrote: >> Please generate a full set of docker images as well as the ISO. Thank >> you. >> >> Ghada >> >> -----Original Message----- >> From: Little, Scott >> Sent: Thursday, October 03, 2019 11:31 AM >> To: Khalil, Ghada; Cabrales, Ada; starlingx-discuss at lists.starlingx.io >> Subject: Re: stx.2.0.1 maintenance RC build Requested >> >> Is this to be an ISO only build?   Or should I generate a full set of >> docker images as well ? >> >> Scott >> >> >> >> On 2019-10-03 11:28 a.m., Khalil, Ghada wrote: >>> Hi Scott, >>> All the fixes expected for the stx.2.0.1 maintenance release have >>> now been merged. Please trigger an RC build for the branch. >>> Ada's team is ready to perform the sanity/regression on the build. >>> Once testing is completed successfully, please label the build and >>> branch as 2.0.1 -- the first maintenance release for stx.2.0. >>> >>> Core reviewers, >>> Please do not allow any code merges on the r/stx.2.0 branch until >>> the testing and labeling are done. >>> >>> References: >>> - stx.2.0 branch: >>> https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.2.0 >>> >>> >>> Thanks, >>> Ghada >>> On behalf of the StarlingX release team >> > > > _______________________________________________ > 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 Fri Oct 4 20:53:37 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 4 Oct 2019 16:53:37 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 135 - Still Failing! In-Reply-To: <1978509564.307.1570156161363.JavaMail.javamailuser@localhost> References: <1978509564.307.1570156161363.JavaMail.javamailuser@localhost> Message-ID: <1652183827.319.1570222418398.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 135 Status: Still Failing Timestamp: 20191004T180546Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191004T151732Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: r/stx.2.0 MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-2.0/20191004T151732Z OS: centos MUNGED_BRANCH: rc-2.0 MY_REPO: /localdisk/designer/jenkins/rc-2.0/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191004T151732Z/logs MASTER_BUILD_NUMBER: 47 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/2.0/centos/20191004T151732Z/logs MASTER_JOB_NAME: STX_BUILD_2.0 MY_REPO_ROOT: /localdisk/designer/jenkins/rc-2.0 PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/2.0/centos PUBLISH_TIMESTAMP: 20191004T151732Z DOCKER_BUILD_ID: jenkins-rc-2.0-20191004T151732Z-builder TIMESTAMP: 20191004T151732Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/rc/2.0/centos/20191004T151732Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/2.0/centos/20191004T151732Z/outputs From build.starlingx at gmail.com Fri Oct 4 20:53:41 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 4 Oct 2019 16:53:41 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_BUILD_2.0 - Build # 47 - Still Failing! In-Reply-To: <694004979.310.1570156165207.JavaMail.javamailuser@localhost> References: <694004979.310.1570156165207.JavaMail.javamailuser@localhost> Message-ID: <444258009.322.1570222422067.JavaMail.javamailuser@localhost> Project: STX_BUILD_2.0 Build #: 47 Status: Still Failing Timestamp: 20191004T151732Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191004T151732Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true From Frank.Miller at windriver.com Fri Oct 4 21:40:34 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Fri, 4 Oct 2019 21:40:34 +0000 Subject: [Starlingx-discuss] StarlingX Bi-Weekly Containerization Meeting Message-ID: For all who are working containerization features or LPs please join for our bi-weekly meeting. Agenda for October 7 meeting: 1. stx3.0 feature status: o 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] - last fcst from Cindy was 9/27 - require updated forecast o 2005860: Upversion container components [Al Bailey] o 2004761: Integrate Backup & Restore with Containers [Ovidiu Poncea] o 2006536 Collect tool enhancements for containers [Dan Voiculeasa] o 2006537: Decouple Container Applications from Platform [Bob Church] o 2004008: [Feature] Create HELM chart for Fault project [An Ran] - one commit needs a new approach - discuss in item #2 2. Design discussion for FM containerization Horizon implementation issue: https://review.opendev.org/#/c/661423/ o Review options for approach where a running container image is not updated on the fly [Ran, Don, Tyler, etc] * 3. STX gating LPs (25, 5 High, 20 Medium) - down 4 from last meeting - THANKS! o Updates or discussion as needed from any primes Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 11am EST / 8am PDT / 1600 UTC Call details * Zoom link: https://zoom.us/j/342730236 * 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 Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3339 bytes Desc: not available URL: From maria.g.perez.ibarra at intel.com Fri Oct 4 22:00:56 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Fri, 4 Oct 2019 22:00:56 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191004 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-04 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [FAIL] 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 [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [FAIL] 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 [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] Ansible bootstrap fails - https://kubernetes-charts.storage.googleapis.com cannot be reached https://bugs.launchpad.net/starlingx/+bug/1846540 Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Fri Oct 4 22:04:21 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 4 Oct 2019 22:04:21 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191004 In-Reply-To: References: Message-ID: <151EE31B9FCCA54397A757BC674650F0C15CA533@ALA-MBD.corp.ad.wrs.com> The fix for https://bugs.launchpad.net/starlingx/+bug/1846540 merged a few hours ago. It should be in tonight's build. Regards, Ghada From: Perez Ibarra, Maria G [mailto:maria.g.perez.ibarra at intel.com] Sent: Friday, October 04, 2019 6:01 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191004 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-04 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [FAIL] 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 [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [FAIL] 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 [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [FAIL] Provisioning 01 TCs [BLOCKED] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] Ansible bootstrap fails - https://kubernetes-charts.storage.googleapis.com cannot be reached https://bugs.launchpad.net/starlingx/+bug/1846540 Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Sun Oct 6 17:08:14 2019 From: scott.little at windriver.com (Scott Little) Date: Sun, 6 Oct 2019 13:08:14 -0400 Subject: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0C15C8A58@ALA-MBD.corp.ad.wrs.com> <83f6f90a-58af-a109-836c-e26558343841@windriver.com> <151EE31B9FCCA54397A757BC674650F0C15C8A91@ALA-MBD.corp.ad.wrs.com> Message-ID: <3a73dd18-6421-96c1-3023-8010ea8c7e64@windriver.com> We finally have a good build! Happy Testing. Scott On 2019-10-04 2:48 p.m., Scott Little wrote: > ETA on the latest build attempt is 5pm EST (Friday, Oct 4) > > Scott > > > On 2019-10-03 2:41 p.m., Scott Little wrote: >> Build underway.  ETA 9pm EST >> >> Scott >> >> >> On 2019-10-03 11:41 a.m., Khalil, Ghada wrote: >>> Please generate a full set of docker images as well as the ISO. >>> Thank you. >>> >>> Ghada >>> >>> -----Original Message----- >>> From: Little, Scott >>> Sent: Thursday, October 03, 2019 11:31 AM >>> To: Khalil, Ghada; Cabrales, Ada; starlingx-discuss at lists.starlingx.io >>> Subject: Re: stx.2.0.1 maintenance RC build Requested >>> >>> Is this to be an ISO only build?   Or should I generate a full set >>> of docker images as well ? >>> >>> Scott >>> >>> >>> >>> On 2019-10-03 11:28 a.m., Khalil, Ghada wrote: >>>> Hi Scott, >>>> All the fixes expected for the stx.2.0.1 maintenance release have >>>> now been merged. Please trigger an RC build for the branch. >>>> Ada's team is ready to perform the sanity/regression on the build. >>>> Once testing is completed successfully, please label the build and >>>> branch as 2.0.1 -- the first maintenance release for stx.2.0. >>>> >>>> Core reviewers, >>>> Please do not allow any code merges on the r/stx.2.0 branch until >>>> the testing and labeling are done. >>>> >>>> References: >>>> - stx.2.0 branch: >>>> https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.2.0 >>>> >>>> >>>> Thanks, >>>> Ghada >>>> On behalf of the StarlingX release team >>> >> >> >> _______________________________________________ >> 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 ildiko.vancsa at gmail.com Sun Oct 6 20:45:03 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Sun, 6 Oct 2019 22:45:03 +0200 Subject: [Starlingx-discuss] StarlingX TSC, PL, TL election - Nomination period started Message-ID: <8DA21B26-746F-4638-818D-E17FC56C1711@gmail.com> Hi StarlingX Community, Nominations for the 5 Technical Steering Committee positions and all PL/TL positions are now open and will remain open until __October 13, 2019 20:45 UTC__. All nominations must be submitted as a text file to the starlingx/election repository as explained on the election website[1]. Please note that the name of the file should match the email address in your Gerrit configuration. Candidates for the Technical Steering Committee Positions: Any contributing community member who is an individual member of the Foundation can propose their candidacy for an available, directly-elected TSC seat. Candidates for the Project Lead Positions: Any contributing community member who is an individual member of the Foundation can propose their candidacy for the project PL seat. Candidates for the Technical Lead Positions: Any contributing community member who is an individual member of the Foundation and is a core reviewer to the given project can propose their candidacy for the project TL seat. The election will be held from October 20, 2019 20:45 UTC through to October 27, 2019 20:45 UTC. The electorate of the TSC election are the community members that are also contributors for one of the official teams[2] or served in a leadership role (TSC, PL, TL) over the 12-month timeframe October 6, 2018 to October 6, 2019, as well as the contributors who are acknowledged by the TSC. The electorate of the PL/TL election are the community members that are contributors for the given official team[2] over the 12-month timeframe October 6, 2018 to October 6, 2019, as well as the contributors who are acknowledged by the TSC. Please see the website[3] for additional details about this election. Please find below the timeline: TSC nomination starts @ October 6, 2019 20:45 UTC TSC nomination ends @ October 13, 2019 20:45 UTC PL/TL nomination starts @ October 6, 2019 20:45 UTC PL/TL nomination ends @ October 13, 2019 20:45 UTC TSC campaigning starts @ October 13, 2019 20:45 UTC TSC campaigning ends @ October 20, 2019 20:45 UTC TSC election starts @ October 20, 2019 20:45 UTC TSC election ends @ October 27, 2019 20:45 UTC PL/TL election starts @ October 20, 2019 20:45 UTC PL/TL election ends @ October 27, 2019 20:45 UTC If you have any questions please be sure to either ask them on the mailing list or to the elections officials[4]. Thank you, [1] https://docs.starlingx.io/election/#how-to-submit-a-candidacy [2] https://docs.starlingx.io/governance/reference/tsc/projects/index.html [3] https://docs.starlingx.io/election/ [4] https://docs.starlingx.io/election/#election-officials From cristopher.j.lemus.contreras at intel.com Mon Oct 7 08:00:56 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Mon, 07 Oct 2019 03:00:56 -0500 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <412985$5erp1s@orsmga007.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191006T230000Z" rabbitmq:3.7-management k8s.gcr.io/kube-apiserver:v1.16.0 k8s.gcr.io/kube-controller-manager:v1.16.0 k8s.gcr.io/kube-proxy:v1.16.0 k8s.gcr.io/kube-scheduler:v1.16.0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From Stefan.Dinescu at windriver.com Mon Oct 7 14:36:54 2019 From: Stefan.Dinescu at windriver.com (Dinescu, Stefan) Date: Mon, 7 Oct 2019 14:36:54 +0000 Subject: [Starlingx-discuss] [docs] Remote CLI details Message-ID: Hello, A remote CLI solution has been merged into master and is not available to be used by the community. The current solution requires users have docker installed on their system (Linux, MacOS and Windows). For windows, CygWin is also a requirement in order to interpret bash scripts. A tarball containing the remote-cli scripts is published weekly as part of the build that also includes building docker images. You can find the latest published tarball from the cengn build at [0]. Basic steps for using remote-cli: - download and extract tarball - download from horizon the RC file for the desider users - configure kubernetes user for remote access and download generated authentication configuration - configure remote client with the above information - use the remote client For a more detailed description there is a README included in the tarball or at [1]. If you have any questions regarding remote-cli, feel free to email me. Notes: - try to use a remote-cli from the same build date to ensure maximum compatibility - there is a build script for anyone who wants to package their own remote-cli tarball at [2] Thanks, Stefan [0]: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/remote-cli/ [1]: https://opendev.org/starlingx/clients/src/branch/master/remote_cli [2]: https://opendev.org/starlingx/root/src/branch/master/build-tools/build-remote-cli.sh -------------- next part -------------- An HTML attachment was scrubbed... URL: From Stefan.Dinescu at windriver.com Mon Oct 7 14:43:19 2019 From: Stefan.Dinescu at windriver.com (Dinescu, Stefan) Date: Mon, 7 Oct 2019 14:43:19 +0000 Subject: [Starlingx-discuss] [docs] Remote CLI details In-Reply-To: References: Message-ID: Small correction. Original quote: A remote CLI solution has been merged into master and is not available to be used by the community. What I meant to say: A remote CLI solution has been merged into master and is now available to be used by the community. Sorry about that :) ________________________________ From: Dinescu, Stefan [Stefan.Dinescu at windriver.com] Sent: Monday, October 07, 2019 5:36 PM To: starlingx-discuss at lists.starlingx.io Cc: Tullis, Michael L Subject: [Starlingx-discuss] [docs] Remote CLI details Hello, A remote CLI solution has been merged into master and is not available to be used by the community. The current solution requires users have docker installed on their system (Linux, MacOS and Windows). For windows, CygWin is also a requirement in order to interpret bash scripts. A tarball containing the remote-cli scripts is published weekly as part of the build that also includes building docker images. You can find the latest published tarball from the cengn build at [0]. Basic steps for using remote-cli: - download and extract tarball - download from horizon the RC file for the desider users - configure kubernetes user for remote access and download generated authentication configuration - configure remote client with the above information - use the remote client For a more detailed description there is a README included in the tarball or at [1]. If you have any questions regarding remote-cli, feel free to email me. Notes: - try to use a remote-cli from the same build date to ensure maximum compatibility - there is a build script for anyone who wants to package their own remote-cli tarball at [2] Thanks, Stefan [0]: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/remote-cli/ [1]: https://opendev.org/starlingx/clients/src/branch/master/remote_cli [2]: https://opendev.org/starlingx/root/src/branch/master/build-tools/build-remote-cli.sh -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ovidiu.Poncea at windriver.com Mon Oct 7 14:44:00 2019 From: Ovidiu.Poncea at windriver.com (Poncea, Ovidiu) Date: Mon, 7 Oct 2019 14:44:00 +0000 Subject: [Starlingx-discuss] New feature available: StarlingX Platform Backup & Restore Message-ID: <4C60D9C5C8176C47874FFF36647AA19EA4717359@ALA-MBD.corp.ad.wrs.com> Hi Folks, Last piece of the Backup & Restore StarlingX feature has been merged on Friday (also known as B&R). This feature provides us with a last resort disaster recovery option in cases where the StarlingX software and/or data are compromised. The feature provides a backup utility to create a tarball containing a snapshot with the deployment state. This tarball contains all that's needed to restore the deployment to a previously good working state. This feature provides two B&R options: I. Platform B&R - backup and restores the platform configuration and data. This step takes care of the platform data: nodes, their configuration and user data. II. Openstack Application - backup and restores the stx-openstack application The Platform B&R supports two modes: I. Keep all Ceph cluster data (to recover from platform software or data corruption) II. Wipe all Ceph cluster data (to perform a full system restore for software and/or application corruption) In both cases, the restore will re-build all platform data required. Applications will require additional steps. For the case where the user decides to keep the Ceph data (eg: application data is preserved) some effort may be required by the applications to re-use the preserved data. For the case where the user decides to start with a clean Ceph, the user will need to recover application data through other means (e.g. snapshot and use rbd export commands for block devices). The backup and restore is done through Ansible and the restore process involves reinstalling each node in the system. The backup is run from the active controller and the restore is run from controller-0 (local play) or remotely by running Ansible and pointing it to controller-0 (remote play). This email describe the Platform B&R procedure. The Openstack procedure will be described in a later mail. Backing up the platform ========================== Local play method ~~~~~~~~~~~~~~~~~~~ Run: ansible-playbook /usr/share/ansible/stx-ansible/playbooks/backup.yml -e "ansible_become_pass= admin_password=" The and need to be set correctly via the “-e” option on the command line or an override file or in the ansible secret file. This will output a file named in this format: _platform_backup_.tgz. The prefix and can be overridden via the “-e” option on the command line or an override file. The generated backup tar files will look like this: localhost_platform_backup_2019_08_08_15_25_36.tgz and localhost_openstack_backup_2019_08_08_15_25_36.tgz. They are located in /opt/backups directory on controller-0. Remote play method ~~~~~~~~~~~~~~~~~~~~ 1. Login to the host where ansible is installed and clone the playbook code from opendev at https://opendev.org/starlingx/ansible-playbooks.git 2. Provide an inventory file, either a customized one that is specified via the ‘-i’ option or the default one which resides in Ansible configuration directory (i.e. /etc/ansible/hosts), must specify the IP of the controller host. For example, if the host-name is my_vbox, the inventory-file should have an entry called my_vbox : --- all: hosts: wc68: ansible_host: 128.222.100.02 my_vbox: ansible_host: 128.224.141.74 3. Run ansible: ansible-playbook --limit host-name -i -e The generated backup tar files can be found in which is $HOME by default. It can be overridden by “-e” option on the command line or in an override file. The generated backup tar have naming convention as in a local play. Example: ansible-playbook /localdisk/designer/repo/cgcs-root/stx/stx-ansible-playbooks/playbookconfig/src/playbooks/backup-restore/backup.yml --limit my_vbox -i $HOME/br_test/hosts -e "host_backup_dir=$HOME/br_test ansible_become_pass=Li69nux* admin_password=Li69nux* ansible_ssh_pass=Li69nux* ansible_ssh_pass=Li69nux*" Detailed information of the contents of the backup ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - Postgresql config: Backup roles, table spaces and schemas for databases - Postgresql data: o template1, sysinv, barbican db data, fm db data, o keystone db for primary region, o dcmanager db for dc controller, o dcorch db for dc controller - LDAP db - Ceph crushmap - DNS server list - System Inventory network overrides. These are needed at restore to correctly set up the OS configuration: o addrpool o pxeboot_subnet o management_subnet o management_start_address o cluster_host_subnet o cluster_pod_subnet o cluster_service_subnet o external_oam_subnet o external_oam_gateway_address o external_oam_floating_address - Docker registries on controller - Docker no=proxy - Backup up data: o OS configuration ok: [localhost] => (item=/etc) - note although everything here is backed up, not all of the content will be restored. o Home directory ‘sysadmin’ user and all LDAP user accounts ok: [localhost] => (item=/home) o Geberated platform configuration ok: [localhost] => (item=/opt/platform/config/19.09) ok: [localhost] => (item=/opt/platform/puppet/19.09/hieradata) - All the hieradata under is backed-up. However only the static hieradata (static.yaml and secure_static.yaml) will be restored to bootstrap controller-0. o Keyring ok: [localhost] => (item=/opt/platform/.keyring/19.09) o Patching and package repositories ok: [localhost] => (item=/opt/patching) ok: [localhost] => (item=/www/pages/updates) o Extension filesystem ok: [localhost] => (item=/opt/extension) o atch-vault filesystem for distributed cloud system-controller ok: [localhost] => (item=/opt/patch-vault) o Armada manifests ok: [localhost] => (item=/opt/platform/armada/19.09) o Helm charts ok: [localhost] => (item=/opt/platform/helm_charts) Restoring ============= I. Platform Restore ---------------------- Platform restore can be done in two modes: A. By keeping the ceph cluster data intact - after restore previous Ceph data will remain in place. B. By wiping Ceph cluster entireley - Ceph cluster has to be recreated. Warning: - The StarlingX system data backup can only be used to restore the system from which the backup was made. You cannot use the system data backup to restore the system on different hardware. - Restore has to use the exact same version of boot image (iso) that was used at the time of the original installation. Prerequisite: a backup file stored externally and StarlingX iso Prepare for the procedure: - Power down all nodes. If you have a storage setup and want to keep Ceph data then power down all the nodes except the storage ones; cluster has to be functional during restore. - Install iso on controller-0 (boot from ISO and reinstall it) The restore procedure has multiple steps, dependent on the system type. The first step of the procedure is identical for all: run the ansible playbook with the backup file as input. For this step, similar to the backup procedure, we have two options: local and remote play. Local play ~~~~~~~~~~~~ First download the backup to the controller (you can also use an external storage device, e.g. an USB drive). Then run the command: ansible-playbook /usr/share/ansible/stx-ansible/playbooks/restore_platform.yml -e "initial_backup_dir= ansible_become_pass= admin_password= backup_filename=" Optional: o set to wipe_ceph_osds=true or wipe_ceph_osds=false (default to false). This will select one of the two restore modes: A. keep Ceph data intact (false) or B. start with an empty ceph cluster (true). Example for a backup file in /home/sysadmin: ansible-playbook /usr/share/ansible/stx-ansible/playbooks/restore_platform.yml -e "initial_backup_dir=/home/sysadmin ansible_become_pass=Li69nux* admin_password=Li69nux* backup_filename=localhost_platform_backup_2019_09_27_07_48_48.tgz" Remote play ~~~~~~~~~~~~~~ 1. Login to the host where ansible is installed and clone the playbook code from OpenDev at https://opendev.org/starlingx/ansible-playbooks.git 2. Provide an inventory file, either a customized one that is specified via the ‘-i’ option or the default one which resides in Ansible configuration directory (i.e. /etc/ansible/hosts), must specify the IP of the controller host. For example, if the host-name is my_vbox, the inventory-file should have an entry called my_vbox : --- all: hosts: wc68: ansible_host: 128.222.100.02 my_vbox: ansible_host: 128.224.141.74 3. Run ansible: ansible-playbook --limit host-name -i -e Where optional-extra-vars can be: o set to wipe_ceph_osds=true or wipe_ceph_osds=false (default to false). This will select if the user wants to keep Ceph data intact (false) or start with an empty ceph cluster (true) o The is the platform backup tar file. It must be provided via the “-e” option on the command line, e.g. -e “backup_filename= localhost_platform_backup_2019_07_15_14_46_37.tgz” o The is the location on the Ansible control machine where the platform backup tar file is placed to restore the platform. It must be provided via “-e” option on the command line. o The , and need to be set correctly via the “-e” option on the command line or in the ansible secret file. is the password to the sysadmin user on controller-0. o The should be set to a new directory (no need to create it ahead of time) under /home/sysadmin on controller-0 via the “-e” option on the command line e.g. ansible-playbook /localdisk/designer/jenkins/tis-stx-dev/cgcs-root/stx/ansible-playbooks/playbookconfig/src/playbooks/restore_platform.yml --limit my_vbox -i $HOME/br_test/hosts -e " ansible_become_pass=Li69nux* admin_password=Li69nux* ansible_ssh_pass=Li69nux* initial_backup_dir=$HOME/br_test backup_filename=my_vbox_system_backup_2019_08_08_15_25_36.tgz ansible_remote_tmp=/home/sysadmin/ansible-restore" After ansible is exectued then the following steps are based on the deployment mode: AIO-SX ~~~~~~~~~ 1. Unlock controller-0 & wait for it to boot AIO-DX ~~~~~~~~~ 1. Unlock controller-0 & wait for it to boot 2. Reinstall controller-1 (boot it from PXE, wait for it to become 'online') 3. Unlock controller-1 Standard with controller storage ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. Unlock controller-0 & wait for it to boot 2. Reinstall controller-1 and all computes (boot them from PXE, wait for them to become 'online') 3. Unlock controller-1 and wait for it to be available 4. Unlock compute nodes Standard with storage nodes ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This depends on wipe_ceph_osds configuration. A. If wipe_ceph_osd is false (default option): 1. Unlock controller-0 & wait for it to boot. Afer unlock you will see storage nodes as available and ceph operational. 2. Reinstall controller-1 and all computes (boot them from PXE, wait for them to become 'online') 3. Unlock controller-1 and wait for it to be available 4. Unlock compute nodes Storage nodes do not need reinstall. B. If wipe_ceph_osd is false (default option): 1. Unlock controller-0 & wait for it to boot. Afer unlock you will see all nodes, including storage nodes as offline. 2. Reinstall controller-1, all storage and compute nodes (boot them from PXE, wait for them to become 'online') 3. Unlock controller-1 and wait for it to be available 4. Unlock storage nodes and wait for them to be available 5. Unlock compute nodes and wait for them to be available Regards, Ovidiu Poncea -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcela.a.rosales.jimenez at intel.com Mon Oct 7 15:34:06 2019 From: marcela.a.rosales.jimenez at intel.com (Rosales Jimenez, Marcela A) Date: Mon, 7 Oct 2019 15:34:06 +0000 Subject: [Starlingx-discuss] [multi-os] What is the correct workflow to submit requests in OBS In-Reply-To: <1bfe9216-388c-ac0f-f35c-4ef0a6ce56dc@fridu.net> References: <1bfe9216-388c-ac0f-f35c-4ef0a6ce56dc@fridu.net> Message-ID: Hi team, I'm starting to update _service files for Maintenance in OBS and I'm also seeing many extra obscpio files. Here is an example https://build.opensuse.org/request/show/735890 Erich, how did you solve this replicated files? Or is it expected to have those obscpio files in my submission? I run the osc ls -u home:marcelarosalesj:branches:Cloud:StarlingX:2.0 mtce-control And I got only two files _link and _service Thanks. Marcela On 9/30/19, 3:17 PM, "Dominig ar Foll (Intel Open Source)" wrote: On 30/09/2019 19:04, Cordoba Malibran, Erich wrote: > Hi, > > I'm trying to send a request to the fm-common project in OBS, however apparently the workflow I follow is incorrect and creates unexpected results > > What I do is: > > - From the project's web page[0] I click on "Branch package", this creates a branched package in my account[1] > - Checkout the project, I do this with: `osc co home:erichcm:branches:Cloud:StarlingX:1.0/fm-common` > - For this task I'm editing the _service file and testing locally with `osc service run` and `osc build --local-package --no-verify openSUSE_Leap_15.1` > - I delete all the non-needed files and keep only the _service file. Then I do a `osc ar` to make this changes If you did not add or remove files (often the case) the delete and osc ar is not required. > - I commit the changes with `osc commit`. At this point, I see in the web page of my branched project that a set of files were created. It's easier to do osc ci -m "commit comment" > > - I click on "Submit package". The created request[2] not only contains the diff of the _service, it contains the diff of all files created after I did a `osc commit`. Most likely a small error either in not deleting the .obsinfo files before your command osc ar or OBS (stupidly) showing the diff between locally created files. If you have to run the osc ar, it's important to remove before all the files except _service .rpmlintrc* .spec* .patches and special config files* * if not downloaded from git via _service. To know what files are really in your project dir use the command osc ls -u project_name package_name osc ls -u home:erichcm:branches:Cloud:StarlingX:2.0 fm-mgr Your first submission is OK. -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre _______________________________________________ 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 Oct 7 15:43:50 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 7 Oct 2019 15:43:50 +0000 Subject: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested In-Reply-To: <3a73dd18-6421-96c1-3023-8010ea8c7e64@windriver.com> References: <151EE31B9FCCA54397A757BC674650F0C15C8A58@ALA-MBD.corp.ad.wrs.com> <83f6f90a-58af-a109-836c-e26558343841@windriver.com> <151EE31B9FCCA54397A757BC674650F0C15C8A91@ALA-MBD.corp.ad.wrs.com> <3a73dd18-6421-96c1-3023-8010ea8c7e64@windriver.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0C15CA873@ALA-MBD.corp.ad.wrs.com> Thanks Scott. Hi da/team, Can you please start the planned sanity/regression testing? Thanks, Ghada -----Original Message----- From: Scott Little [mailto:scott.little at windriver.com] Sent: Sunday, October 06, 2019 1:08 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested We finally have a good build! Happy Testing. Scott From ada.cabrales at intel.com Mon Oct 7 15:55:38 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Mon, 7 Oct 2019 15:55:38 +0000 Subject: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested In-Reply-To: <151EE31B9FCCA54397A757BC674650F0C15CA873@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0C15C8A58@ALA-MBD.corp.ad.wrs.com> <83f6f90a-58af-a109-836c-e26558343841@windriver.com> <151EE31B9FCCA54397A757BC674650F0C15C8A91@ALA-MBD.corp.ad.wrs.com> <3a73dd18-6421-96c1-3023-8010ea8c7e64@windriver.com> <151EE31B9FCCA54397A757BC674650F0C15CA873@ALA-MBD.corp.ad.wrs.com> Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CEE6F47@FMSMSX114.amr.corp.intel.com> Sure! :) A. > -----Original Message----- > From: Khalil, Ghada > Sent: Monday, October 7, 2019 10:44 AM > To: Little, Scott ; starlingx- > discuss at lists.starlingx.io; Cabrales, Ada > Subject: RE: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested > > Thanks Scott. > > Hi da/team, > Can you please start the planned sanity/regression testing? > > Thanks, > Ghada > > > -----Original Message----- > From: Scott Little [mailto:scott.little at windriver.com] > Sent: Sunday, October 06, 2019 1:08 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested > > We finally have a good build! > > Happy Testing. > > Scott > From marcela.a.rosales.jimenez at intel.com Mon Oct 7 16:29:55 2019 From: marcela.a.rosales.jimenez at intel.com (Rosales Jimenez, Marcela A) Date: Mon, 7 Oct 2019 16:29:55 +0000 Subject: [Starlingx-discuss] [MultiOS] Team meeting 10/7/19 Message-ID: MultiOS team meeting - 10/7/2019 Agenda openSUSE specs integration with OBS - maintenance - 6 openSUSE spec files already in gerrit and WIP integration with OBS - mtce.spec will be sent after this patch is merged https://review.opendev.org/#/c/678627/ - config - complete - HA - Service manager (sm) bug not seen in latest build, it seems it was a setup issue as suggested by Bin http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/006327.html - Service manager patchset sent, all 6 components https://review.opendev.org/#/c/679686/ - Working with service manager meta package as suggested by Dominig to install runtime dependencies http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/006313.html Analysis in progress, it seems meta package might not be needed. - Will send a documentation patch with service manager terminology - NFV - patches sent, but a refactor is required, _service files accepted in OBS - Fault - sent patch to remove file replication - Ansible - there is a package existing - Puppet - they are available on OBS - next step: install ansible and puppet rpms, and run starlingx playbook kickstart file - not compatible with openSUSE - there is not any tool to convert kickstart to autoYaST, this should be done manually cobbler - it's an interesting tool because it works for different distros what's the next spec after spec integration with OBS? - make them work, install, start them, fix hardwired dependencies, fix hidden dependencies - define functionality test cases - run binary manually, without using systemd or SM systemd - still on hold - we need to add to SM the support for systemd - not priority right now target - openSUSE 15.1 metapackages - to solve run time dependencies You can find the minutes here https://etherpad.openstack.org/p/stx-multios Thanks! Marcela -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Mon Oct 7 18:08:00 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 7 Oct 2019 18:08:00 +0000 Subject: [Starlingx-discuss] Distro.openstack Oct 8th meeting agenda Message-ID: <9A85D2917C58154C960D95352B22818BDFBE39DF@fmsmsx121.amr.corp.intel.com> 10/1/2019 meeting * Test plan update - Yong * Testing for this? https://governance.openstack.org/tc/goals/selected/train/ipv6-support-and-testing.html * Train migration update https://storyboard.openstack.org/#!/story/2006544 * Upstream progress * Opens -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Mon Oct 7 19:30:32 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 7 Oct 2019 19:30:32 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting Message-ID: Minutes from today's session: Minutes for October 7 meeting: 1. Proposed new meeting day and time to accommodate the team in China: * Would Tuesdays at 6:30AM Pacific work? Bruce indicates the distro.openstack meeting only needs 30 minutes so this timeslot is available. 2. stx3.0 feature status: Note: Stx.3.0 MS3 = Oct 16 RC1 = Nov 13 * 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] - last fcst from Cindy was 9/27 - require updated forecast * 2005514: QAT K8S device plugin support in StarlingX o Bruce: Code is out for review; Frank to follow-up with CIndy for updated forecast * 2005860: Upversion container components [Al Bailey] o k8s v1.16 delivered last week, sanity issue with proxy identified and fix merged last week --> Christopher confirmed this issue is not seen in today's sanity o k8s v1.16.1 is now available and contains FD leak fix + a couple other panic issues addressed - looks like some key bug fixes that we would want o Plan is to move to either v1.16.1 or v1.16.2 for stx.3.0 * 2004761: Integrate Backup & Restore with Containers [Ovidiu Poncea] o Feature commits now merged. Platform B&R is complete and ready for testing. o B&R with stx-openstack code is complete but some designer level test and doc still required. * 2006536 Collect tool enhancements for containers [Dan Voiculeasa] --> DONE * 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] o Bob has pushed a set of reviews to enable plug-ins; additional reviews to use plug-ins and decouple pending o Spec is getting some reviews; reminder to TSC primes to please review * 2004008: [Feature] Create HELM chart for Fault project [An Ran] - one commit needs a new approach - discussed in item #2 3. Design discussion for FM containerization Horizon implementation issue: https://review.opendev.org/#/c/661423/ * Reviewed options for approach where a running container image is not updated on the fly [Ran, Don, Tyler, etc] * Without this commit, the openstack Horizon would not show VM alarms (but would be visible via CLI); ie: No GUI panel for showing any openstack alarms * To solve this would require one of 2 options: 1. Split GUI plugin into 2: one with shared panels, the other with the platform panels (preferred option), Tyler estimate: 2 weeks but Tyler tied up with distributed cloud 2. In horizon image add in needed dependencies (was tried and wasn't working - additional debug will be required) * Frank to review with TL (Brent) and decide if in stx.3.0 we can live without GUI alarms for openstack. If we decide we need the GUI panel, then we have to re-enable the code to turn off FM containerization until this issue is solved. 4. STX gating LPs (24, 5 High, 19 Medium) - down 5 from last meeting - THANKS! * No updates or discussion required at this meeting. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Mon Oct 7 19:53:50 2019 From: kennelson11 at gmail.com (Kendall Nelson) Date: Mon, 7 Oct 2019 12:53:50 -0700 Subject: [Starlingx-discuss] [all] Final PTG Schedule Message-ID: Hello Everyone! After a few weeks of shuffling and changes, we have a final schedule! It can be seen here on the 'Schedule' tab[1]. -Kendall (diablo_rojo) [1] https://www.openstack.org/PTG -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.l.tullis at intel.com Mon Oct 7 20:50:56 2019 From: michael.l.tullis at intel.com (Tullis, Michael L) Date: Mon, 7 Oct 2019 20:50:56 +0000 Subject: [Starlingx-discuss] [docs] Remote CLI details In-Reply-To: References: Message-ID: <3808363B39586544A6839C76CF81445EA1BE5491@ORSMSX104.amr.corp.intel.com> Thanks for this. From the doc perspective, this is subtask 36280 in https://storyboard.openstack.org/#!/story/2006289. -- Mike From: Dinescu, Stefan Sent: Monday, October 7, 2019 8:43 AM To: starlingx-discuss at lists.starlingx.io Cc: Tullis, Michael L Subject: RE: [docs] Remote CLI details Small correction. Original quote: A remote CLI solution has been merged into master and is not available to be used by the community. What I meant to say: A remote CLI solution has been merged into master and is now available to be used by the community. Sorry about that :) ________________________________ From: Dinescu, Stefan [Stefan.Dinescu at windriver.com] Sent: Monday, October 07, 2019 5:36 PM To: starlingx-discuss at lists.starlingx.io Cc: Tullis, Michael L Subject: [Starlingx-discuss] [docs] Remote CLI details Hello, A remote CLI solution has been merged into master and is not available to be used by the community. The current solution requires users have docker installed on their system (Linux, MacOS and Windows). For windows, CygWin is also a requirement in order to interpret bash scripts. A tarball containing the remote-cli scripts is published weekly as part of the build that also includes building docker images. You can find the latest published tarball from the cengn build at [0]. Basic steps for using remote-cli: - download and extract tarball - download from horizon the RC file for the desider users - configure kubernetes user for remote access and download generated authentication configuration - configure remote client with the above information - use the remote client For a more detailed description there is a README included in the tarball or at [1]. If you have any questions regarding remote-cli, feel free to email me. Notes: - try to use a remote-cli from the same build date to ensure maximum compatibility - there is a build script for anyone who wants to package their own remote-cli tarball at [2] Thanks, Stefan [0]: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/remote-cli/ [1]: https://opendev.org/starlingx/clients/src/branch/master/remote_cli [2]: https://opendev.org/starlingx/root/src/branch/master/build-tools/build-remote-cli.sh -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Mon Oct 7 21:05:59 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Mon, 7 Oct 2019 21:05:59 +0000 Subject: [Starlingx-discuss] [Test] Meeting agenda for 10/08 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CEE73B2@FMSMSX114.amr.corp.intel.com> Agenda for 10/08 1. Sanity status 2. stx.3.0 testing updates Feature testing Regression testing 3. stx.2.0 maintenance testing 4. Opens Regards Ada From maria.g.perez.ibarra at intel.com Mon Oct 7 22:55:19 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Mon, 7 Oct 2019 22:55:19 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191007 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-07 (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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006416.html Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcela.a.rosales.jimenez at intel.com Tue Oct 8 00:14:36 2019 From: marcela.a.rosales.jimenez at intel.com (Rosales Jimenez, Marcela A) Date: Tue, 8 Oct 2019 00:14:36 +0000 Subject: [Starlingx-discuss] [MultiOS] Maintenance enabling on openSUSE - first steps and errors Message-ID: <27EFF557-BB99-4D0B-90CF-02FBE335E78D@intel.com> Hi team, As you may know, we have all the StarlingX flock packaged and available for openSUSE in OBS [1], but we still need to make it run and work correctly. For StarlingX Maintenance services enabling on openSUSE I am doing the following experiment: 1. Identify MTCE appropriate projects to enable on openSUSE (all except kickstart and pxe-network-installer) 2. Identify per repo, the packages generated 3. Identify per package, its services provided 4. Install one by one the MTCE packages 5. After an installation, run the service’s binary manually (without systemd or Service Manager, as all that flow is not supported in openSUSE yet) My goal is to run all services and see if they have common problems, so I can start asking questions and solving the ones that impact more services first. So, I mapped everything into a list here [2], and started the step 4 and 5. I installed mtce-1.0-lp151.10.2.x86_64.rpm and libamon1-1.0-lp151.10.2.x86_64.rpm on an openSUSE vagrant VM, I have my working flow documented in a github repo [3]. Here are the results I have for now: project: mtce package: libamon1-1.0-lp151.10.2.x86_64.rpm (184 KB) / this is pmon [SUCCESSFUL INSTALLATION] service: pmon.service - Missing /etc/platform/platform.conf package: mtce-1.0-lp151.10.2.x86_64.rpm (902 KB) [SUCCESSFUL INSTALLATION] service: fsmon.service - Missing /etc/platform/platform.conf service: goenabled.service - failed to write state file /var/run/.goenabled, but returns an exit status 0 if it runs with sudo service: hbsClient.service - Missing /etc/platform/platform.conf service: hwclock.service - exit status 0, but it has some errors about /usr/lib/locale/en_US.UTF-8/ not existing, in openSUSE is /usr/lib/locale/en_US.utf8/ service: mtcClient.service - Missing /etc/platform/platform.conf service: mtcalarm.service - Missing /etc/platform/platform.conf service: mtclog.service - Missing /etc/platform/platform.conf My questions: * At least for now I see that most of the errors are about not having /etc/platform/platform.conf file. Who provides that file? How do I satisfy that dependency? In the spec file? * Also, I don’t know what are the expected results of each service. Is it enough to get an exit status of 0? Dominig, Saul, do you think this is a good experiment? Do you have any suggestion for me? Thanks! Marcela [1] https://build.opensuse.org/project/show/Cloud:StarlingX:2.0 [2] https://github.com/marcelarosalesj/learning-starlingx/blob/master/roadmap/opensuse-mtce-enabling.md [3] https://github.com/marcelarosalesj/suse-starlingx/tree/master/vagrant -------------- next part -------------- An HTML attachment was scrubbed... URL: From vm.rod25 at gmail.com Tue Oct 8 00:28:31 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Mon, 7 Oct 2019 19:28:31 -0500 Subject: [Starlingx-discuss] [MultiOS] Maintenance enabling on openSUSE - first steps and errors In-Reply-To: <27EFF557-BB99-4D0B-90CF-02FBE335E78D@intel.com> References: <27EFF557-BB99-4D0B-90CF-02FBE335E78D@intel.com> Message-ID: On Mon, Oct 7, 2019 at 7:15 PM Rosales Jimenez, Marcela A wrote: > > Hi team, > > > > As you may know, we have all the StarlingX flock packaged and available for openSUSE in OBS [1], but we still need to make it run and work correctly. > > > > For StarlingX Maintenance services enabling on openSUSE I am doing the following experiment: > > > > Identify MTCE appropriate projects to enable on openSUSE (all except kickstart and pxe-network-installer) > Identify per repo, the packages generated > Identify per package, its services provided > Install one by one the MTCE packages > After an installation, run the service’s binary manually (without systemd or Service Manager, as all that flow is not supported in openSUSE yet) > > > > My goal is to run all services and see if they have common problems, so I can start asking questions and solving the ones that impact more services first. > > > > So, I mapped everything into a list here [2], and started the step 4 and 5. > > I installed mtce-1.0-lp151.10.2.x86_64.rpm and libamon1-1.0-lp151.10.2.x86_64.rpm on an openSUSE vagrant VM, I have my working flow documented in a github repo [3]. > > > > Here are the results I have for now: > > project: mtce > > package: libamon1-1.0-lp151.10.2.x86_64.rpm (184 KB) / this is pmon [SUCCESSFUL INSTALLATION] > > service: pmon.service - Missing /etc/platform/platform.conf > > package: mtce-1.0-lp151.10.2.x86_64.rpm (902 KB) [SUCCESSFUL INSTALLATION] > > service: fsmon.service - Missing /etc/platform/platform.conf > > service: goenabled.service - failed to write state file /var/run/.goenabled, but returns an exit status 0 if it runs with sudo > > service: hbsClient.service - Missing /etc/platform/platform.conf > > service: hwclock.service - exit status 0, but it has some errors about /usr/lib/locale/en_US.UTF-8/ not existing, in openSUSE is /usr/lib/locale/en_US.utf8/ > > service: mtcClient.service - Missing /etc/platform/platform.conf > > service: mtcalarm.service - Missing /etc/platform/platform.conf > > service: mtclog.service - Missing /etc/platform/platform.conf > > > > My questions: > > At least for now I see that most of the errors are about not having /etc/platform/platform.conf file. Who provides that file? How do I satisfy that dependency? In the spec file? Have you try dnf provides /etc/platform/platform.conf DNF has this feature: https://dnf.readthedocs.io/en/latest/command_ref.html#provides-command-label > Also, I don’t know what are the expected results of each service. Is it enough to get an exit status of 0? I don't think that exit status is good enough, I think we need to work on a test plan for each flock service. Originally each service should be documented about what are the expected functions it should perform. Based on that anyone could develop the test case. We can work on a test plan for the flock services as part of R4 but not sure if is already in the plan or not Regards > > > > Dominig, Saul, do you think this is a good experiment? Do you have any suggestion for me? > > > > Thanks! > > > > Marcela > > > > [1] https://build.opensuse.org/project/show/Cloud:StarlingX:2.0 > > [2] https://github.com/marcelarosalesj/learning-starlingx/blob/master/roadmap/opensuse-mtce-enabling.md > > [3] https://github.com/marcelarosalesj/suse-starlingx/tree/master/vagrant > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cristopher.j.lemus.contreras at intel.com Tue Oct 8 08:01:20 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Tue, 08 Oct 2019 03:01:20 -0500 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: List of docker images required for "platform-integ-apps": BUILD_ID="20191007T230000Z" rabbitmq:3.7-management k8s.gcr.io/kube-apiserver:v1.16.0 k8s.gcr.io/kube-controller-manager:v1.16.0 k8s.gcr.io/kube-proxy:v1.16.0 k8s.gcr.io/kube-scheduler:v1.16.0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From Bill.Zvonar at windriver.com Tue Oct 8 12:27:49 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 8 Oct 2019 12:27:49 +0000 Subject: [Starlingx-discuss] Community Call (Oct 9, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B01362@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of the Community call tomorrow. Feel free to add to the agenda at [0]... - upcoming elections and project/repo restructuring - and the usual standing topics... - Gerrit reviews that need attention - Red sanity learnings - unanswered requests for help in the mailing list - open AR review 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=20191009T1400 From cindy.xie at intel.com Tue Oct 8 12:56:46 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 8 Oct 2019 12:56:46 +0000 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35F28711@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F35F28711@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F3607B6C2@SHSMSX104.ccr.corp.intel.com> All, We will have non-openstack distri meeting tomorrow. But due to the conflict, I am not able to host the meeting. Yong is kindly helping me to cover this week. Yong will send out the agenda soon and you can let him know if you have any open topics. Thx. - cindy -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, October 9, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 * 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Oct 8 13:30:07 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 8 Oct 2019 13:30:07 +0000 Subject: [Starlingx-discuss] distro.openstack meeting minutes Oct 8 2019 Message-ID: <9A85D2917C58154C960D95352B22818BDFBE412B@fmsmsx121.amr.corp.intel.com> Overall plan and status tracking document: https://etherpad.openstack.org/p/stx-openstack-patch-refactoring * Details: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?usp=sharing Story boards: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.distro.openstack&project_group_id=86 10/8/2019 meeting * Upgrade to Train - Shuicheng suggests deferring Keystone upgrade until the CentOS RPM is available. Is this OK, will we hit compatibility issues? * Still planning to wait for CentOS - could be a month or two - will run tests to verify functionality. Risk should be low and we can always build the sRPM ourselves. Dean says that the API changes are mainly in changes we pushed. * Test plan update - Yong * Testing for this? https://governance.openstack.org/tc/goals/selected/train/ipv6-support-and-testing.html. Dean has been testing ipv6 OpenStack but is seeing problems outside of O.S. that make running only ipv6 hard - e.g. github & gitlab don't support it at all. Some customers want ipv6 only. There is a setup in the SH lab for ipv6 we could use to start this. Yong thinks we should start testing this feature sooner rather than later. JC (with help from Elio who has tested this in the past) could use the SH setup to run a few basic tests eg. Sanity. * Train migration update https://storyboard.openstack.org/#!/story/2006544 * Yong: Regarding Train upgrade, we are making some progress (docker image creation is done, a helm issue has been addressed and the manifest is ready) and very likely we will work out an EB for testing by Oct 11th, next Friday. And will try to catch up making patches ready before Feature Freeze Milestone Oct 16. The patches are small and easy to review. * Opens * Nova patch to detect failed VMs - big performance increase - do we want to push upstream? Carry the patch? ? Patch is visible here: https://gist.github.com/VictorRodriguez/e137a8cd87cf821f8076e9acc02ce195 ? Dean: Nova might not be the best place to land this feature. Nova isn't designed (now) to support this and is unlikely to accept the changes - indeed they have already been rejected. If we need sub-second response times for detecting failed VMs we should find a place to land this somewhere else. Could also be added to libvirt (maybe - might need libvirt changes). Will require some architecture work to figure out the best path forward. * Will shorten this meeting to 30 minutes going forward so Frank can have the bottom of the hour time slot for the container meeting. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Tue Oct 8 13:30:09 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 8 Oct 2019 13:30:09 +0000 Subject: [Starlingx-discuss] [MultiOS] Maintenance enabling on openSUSE - first steps and errors In-Reply-To: References: <27EFF557-BB99-4D0B-90CF-02FBE335E78D@intel.com> Message-ID: Nearly all those files are written through ansible, stx-puppet and sysinv as part of provisioning steps before maintenance can run. /etc/platform/platform.conf is written through puppet here https://opendev.org/starlingx/stx-puppet/src/branch/master/puppet-manifests/src/modules/platform/manifests/config.pp#L50 The /var/run/.goenabled is written when this line is executed https://opendev.org/starlingx/metal/src/branch/master/mtce/src/scripts/goenabled.service#L9 Al -----Original Message----- From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] Sent: Monday, October 07, 2019 8:29 PM To: Rosales Jimenez, Marcela A; Miller, Frank Cc: Dominig ar Foll (Intel Open Source); Wold, Saul; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [MultiOS] Maintenance enabling on openSUSE - first steps and errors On Mon, Oct 7, 2019 at 7:15 PM Rosales Jimenez, Marcela A wrote: > > Hi team, > > > > As you may know, we have all the StarlingX flock packaged and available for openSUSE in OBS [1], but we still need to make it run and work correctly. > > > > For StarlingX Maintenance services enabling on openSUSE I am doing the following experiment: > > > > Identify MTCE appropriate projects to enable on openSUSE (all except kickstart and pxe-network-installer) > Identify per repo, the packages generated > Identify per package, its services provided > Install one by one the MTCE packages > After an installation, run the service’s binary manually (without systemd or Service Manager, as all that flow is not supported in openSUSE yet) > > > > My goal is to run all services and see if they have common problems, so I can start asking questions and solving the ones that impact more services first. > > > > So, I mapped everything into a list here [2], and started the step 4 and 5. > > I installed mtce-1.0-lp151.10.2.x86_64.rpm and libamon1-1.0-lp151.10.2.x86_64.rpm on an openSUSE vagrant VM, I have my working flow documented in a github repo [3]. > > > > Here are the results I have for now: > > project: mtce > > package: libamon1-1.0-lp151.10.2.x86_64.rpm (184 KB) / this is pmon [SUCCESSFUL INSTALLATION] > > service: pmon.service - Missing /etc/platform/platform.conf > > package: mtce-1.0-lp151.10.2.x86_64.rpm (902 KB) [SUCCESSFUL INSTALLATION] > > service: fsmon.service - Missing /etc/platform/platform.conf > > service: goenabled.service - failed to write state file /var/run/.goenabled, but returns an exit status 0 if it runs with sudo > > service: hbsClient.service - Missing /etc/platform/platform.conf > > service: hwclock.service - exit status 0, but it has some errors about /usr/lib/locale/en_US.UTF-8/ not existing, in openSUSE is /usr/lib/locale/en_US.utf8/ > > service: mtcClient.service - Missing /etc/platform/platform.conf > > service: mtcalarm.service - Missing /etc/platform/platform.conf > > service: mtclog.service - Missing /etc/platform/platform.conf > > > > My questions: > > At least for now I see that most of the errors are about not having /etc/platform/platform.conf file. Who provides that file? How do I satisfy that dependency? In the spec file? Have you try dnf provides /etc/platform/platform.conf DNF has this feature: https://dnf.readthedocs.io/en/latest/command_ref.html#provides-command-label > Also, I don’t know what are the expected results of each service. Is it enough to get an exit status of 0? I don't think that exit status is good enough, I think we need to work on a test plan for each flock service. Originally each service should be documented about what are the expected functions it should perform. Based on that anyone could develop the test case. We can work on a test plan for the flock services as part of R4 but not sure if is already in the plan or not Regards > > > > Dominig, Saul, do you think this is a good experiment? Do you have any suggestion for me? > > > > Thanks! > > > > Marcela > > > > [1] https://build.opensuse.org/project/show/Cloud:StarlingX:2.0 > > [2] https://github.com/marcelarosalesj/learning-starlingx/blob/master/roadmap/opensuse-mtce-enabling.md > > [3] https://github.com/marcelarosalesj/suse-starlingx/tree/master/vagrant > > > > _______________________________________________ > 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 marcela.a.rosales.jimenez at intel.com Tue Oct 8 16:24:23 2019 From: marcela.a.rosales.jimenez at intel.com (Rosales Jimenez, Marcela A) Date: Tue, 8 Oct 2019 16:24:23 +0000 Subject: [Starlingx-discuss] [MultiOS] Maintenance enabling on openSUSE - first steps and errors In-Reply-To: References: <27EFF557-BB99-4D0B-90CF-02FBE335E78D@intel.com> Message-ID: Thanks Victor and Al, that's very useful. Just to let you know, I completed the experiment I described, you can see the results in my repo [1]. Most of the errors are because of the missing platform.conf. As I am blocked right now I'll be working with Dominig to do the porting of the Kickstarts to AutoYaST. Thanks! Marcela [1] https://github.com/marcelarosalesj/learning-starlingx/blob/master/roadmap/opensuse-mtce-enabling.md On 10/8/19, 8:30 AM, "Bailey, Henry Albert (Al)" wrote: Nearly all those files are written through ansible, stx-puppet and sysinv as part of provisioning steps before maintenance can run. /etc/platform/platform.conf is written through puppet here https://opendev.org/starlingx/stx-puppet/src/branch/master/puppet-manifests/src/modules/platform/manifests/config.pp#L50 The /var/run/.goenabled is written when this line is executed https://opendev.org/starlingx/metal/src/branch/master/mtce/src/scripts/goenabled.service#L9 Al -----Original Message----- From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] Sent: Monday, October 07, 2019 8:29 PM To: Rosales Jimenez, Marcela A; Miller, Frank Cc: Dominig ar Foll (Intel Open Source); Wold, Saul; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [MultiOS] Maintenance enabling on openSUSE - first steps and errors On Mon, Oct 7, 2019 at 7:15 PM Rosales Jimenez, Marcela A wrote: > > Hi team, > > > > As you may know, we have all the StarlingX flock packaged and available for openSUSE in OBS [1], but we still need to make it run and work correctly. > > > > For StarlingX Maintenance services enabling on openSUSE I am doing the following experiment: > > > > Identify MTCE appropriate projects to enable on openSUSE (all except kickstart and pxe-network-installer) > Identify per repo, the packages generated > Identify per package, its services provided > Install one by one the MTCE packages > After an installation, run the service’s binary manually (without systemd or Service Manager, as all that flow is not supported in openSUSE yet) > > > > My goal is to run all services and see if they have common problems, so I can start asking questions and solving the ones that impact more services first. > > > > So, I mapped everything into a list here [2], and started the step 4 and 5. > > I installed mtce-1.0-lp151.10.2.x86_64.rpm and libamon1-1.0-lp151.10.2.x86_64.rpm on an openSUSE vagrant VM, I have my working flow documented in a github repo [3]. > > > > Here are the results I have for now: > > project: mtce > > package: libamon1-1.0-lp151.10.2.x86_64.rpm (184 KB) / this is pmon [SUCCESSFUL INSTALLATION] > > service: pmon.service - Missing /etc/platform/platform.conf > > package: mtce-1.0-lp151.10.2.x86_64.rpm (902 KB) [SUCCESSFUL INSTALLATION] > > service: fsmon.service - Missing /etc/platform/platform.conf > > service: goenabled.service - failed to write state file /var/run/.goenabled, but returns an exit status 0 if it runs with sudo > > service: hbsClient.service - Missing /etc/platform/platform.conf > > service: hwclock.service - exit status 0, but it has some errors about /usr/lib/locale/en_US.UTF-8/ not existing, in openSUSE is /usr/lib/locale/en_US.utf8/ > > service: mtcClient.service - Missing /etc/platform/platform.conf > > service: mtcalarm.service - Missing /etc/platform/platform.conf > > service: mtclog.service - Missing /etc/platform/platform.conf > > > > My questions: > > At least for now I see that most of the errors are about not having /etc/platform/platform.conf file. Who provides that file? How do I satisfy that dependency? In the spec file? Have you try dnf provides /etc/platform/platform.conf DNF has this feature: https://dnf.readthedocs.io/en/latest/command_ref.html#provides-command-label > Also, I don’t know what are the expected results of each service. Is it enough to get an exit status of 0? I don't think that exit status is good enough, I think we need to work on a test plan for each flock service. Originally each service should be documented about what are the expected functions it should perform. Based on that anyone could develop the test case. We can work on a test plan for the flock services as part of R4 but not sure if is already in the plan or not Regards > > > > Dominig, Saul, do you think this is a good experiment? Do you have any suggestion for me? > > > > Thanks! > > > > Marcela > > > > [1] https://build.opensuse.org/project/show/Cloud:StarlingX:2.0 > > [2] https://github.com/marcelarosalesj/learning-starlingx/blob/master/roadmap/opensuse-mtce-enabling.md > > [3] https://github.com/marcelarosalesj/suse-starlingx/tree/master/vagrant > > > > _______________________________________________ > 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 ada.cabrales at intel.com Tue Oct 8 20:29:42 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 8 Oct 2019 20:29:42 +0000 Subject: [Starlingx-discuss] [Test] Meeting notes for 10/08 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CEF5E4F@FMSMSX114.amr.corp.intel.com> Agenda for 10/08 Attendees: Cristopher, JC, JP, Maria P, Ada, Fer, Elio, Yang, JP, Chris 1. Sanity status Intel environment https://bugs.launchpad.net/starlingx/+bug/1846287 - False alarm created on AIO. Fix released today. https://bugs.launchpad.net/starlingx/+bug/1846540 - Bootstrap tried to connect to kubernetes-charts.storage.googleapis.com (Internet), not compatible with proxy nor private registry. Fixed on Friday Oct/04 build. For today's build: virtual looks good. For baremetal we had problems downloading the image, but that is fixed now. Test in progress. WR environment https://bugs.launchpad.net/starlingx/+bug/1847147 - IPv6: ansible playbook bootstrap failed by kubelet isn't running or healthy Seen on IPv6 so far, keep an eye on it for IPv4. This also happened on a standard system today. Using redfish there are some BMC alarms after hosts operations. Launchpad will be open later. https://bugs.launchpad.net/starlingx/+bug/1841444 - nova.exception.CinderConnectionFailed' when boot VM from volume ERROR (ClientException): Unexpected API Error Needs more investigation. https://bugs.launchpad.net/starlingx/+bug/1846520 - IPv6 DX plus, system cmd connection refused for a short period after standby controller reboot. Yang to confirm the but with developers. 2. stx.3.0 testing updates Feature testing Tracker - https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit?usp=sharing Backup and restore - Yang Testing in progress. Tests added to the tracker. Working on the platform side. Distributed cloud - Yang Test in progress, tests are in the tracker. Looks good so far. DC is working on the platform side only (it was a limited scope defined by development). Up-version openstack to train - JC Will use lab in China to begin with testing, this will be for running test on IPv6 (lab already set). Waiting for the upversion to be finished. No forecasted date yet. GPU for K8 - Richo R2 to R3 upgrades - Yang Not staffed - out? Not heard of anything related to this. Redfish - Cristopher Started to take a look. Suggestion is to execute reboot hosts (due to the issue mentioned earlier in the sanity). Infrastructure and cluster monitoring - Yang Not started yet. Regression testing Tracker - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit?usp=sharing Official date for starting regression was yesterday (10/07) Yang to update the regression tracker with suggestions. Started and OK so far. Intel: configs are assigned and set, people to begin with testing today. 3. stx.2.0 maintenance testing Testing on Intel lab has started. - We have to fix some things due to the change we made from python2 -> python3. Expectation is to finish by EOW. Running on all configs, virtual env. On WindRiver lab the ISO is being installed and test will begin after that. Running automated regression is enough. Release team agreed on this. 4. Opens Ada: PL/TL elections - Ildiko sent an email with the things required to be running for the election. Please go and postulate yourself. -- Ada From abraham.arce.moreno at intel.com Tue Oct 8 21:58:56 2019 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 8 Oct 2019 21:58:56 +0000 Subject: [Starlingx-discuss] openSUSE: High Availability Installation Update In-Reply-To: <31d28eb3-73d8-81b9-aab0-ef46c2ecd714@fridu.net> References: <265084f0-e806-a351-b9e7-701fa020a9db@fridu.net> <31d28eb3-73d8-81b9-aab0-ef46c2ecd714@fridu.net> Message-ID: Dominig, > > The steps were finally installed in one Leap 15.0 based. My Documentation > > needs to be updated. > Good. A non issue then. I have moved to openSUSE 15.1 > Not very well documented feature but you can look at my personal project. > https://build.opensuse.org/package/show/Application:Geo:OpenCPN/OpenCPN-5.x Since the missing runtime dependencies were not that many and not common across the different components, I decided to include directly into the specfiles and not use meta package. From abraham.arce.moreno at intel.com Tue Oct 8 22:33:27 2019 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 8 Oct 2019 22:33:27 +0000 Subject: [Starlingx-discuss] openSUSE: High Availability Update Message-ID: Dear high availability community: Here you have the first level of tests for each of the service manager components to confirm there are no more package dependencies missing, all command were successful: sm-common: na sm: na sm-db aka libsm_db1: consult sm.db via sqlite3 and .tables commands sm-client: executed smc command sm-tools: executed sm-dump and sm-query commands sm-api: executed sm-api command Your feedback is welcome for the following reviews so this activity can be completed: - [0] openSUSE: Runtime Dependencies - [1] openSUSE: Open Build Service Artifacts I will continue with the next level of installation tests still undefined, if you have any suggestion, please let me know so I can incorporate it into this testing process. In addition, I would like to get your initial comments in the sm-db terminology: - [2] Service Manager Baseline Documentation This is a work in progress review of what it will be the general documentation for high availability, to be published under our official docs starlingx ha section [3], see in [4] the rendered example. If you have existing ha documentation, I can port it into the rst format to speed up its completion. [0] https://review.opendev.org/#/c/687429/ [1] https://review.opendev.org/#/c/679686/ [2] https://review.opendev.org/#/c/687120/ [3] https://docs.starlingx.io/ha/index.html [4] https://4dfdbb36ff3ed7154f58-be76b9eef9539745164f256be896c2d6.ssl.cf2.rackcdn.com/687120/1/check/openstack-tox-docs/546f003/docs/ From maria.g.perez.ibarra at intel.com Tue Oct 8 22:36:29 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 8 Oct 2019 22:36:29 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191008 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006432.html Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Tue Oct 8 23:01:41 2019 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 8 Oct 2019 16:01:41 -0700 Subject: [Starlingx-discuss] Debranding mirror and local repo Message-ID: Folks, I am starting the debranding of the cento-mirror creation and build tools that read from the cgcs-centos-repo and cgcs-tis-repo. These will be renamed centos-repo and local-repo respectively. I know this will also affect the CENGN build. We may want to have a discussion about if this should continue for 3.0 or just wait to post 3.0, I am open to others thoughts on this. This will also require some documentation changes, I will help out with the docs changes, but I would like to make sure I am doing it in the correct place, and for the correct release (master). There are other changes that I have proposed that can be handled stand-alone apart from the repo renaming. Sau! From shuicheng.lin at intel.com Wed Oct 9 05:49:50 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Wed, 9 Oct 2019 05:49:50 +0000 Subject: [Starlingx-discuss] [docs]Changing Ansible docker_registries's "unified" key In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C76608D5CA5@SHSMSX105.ccr.corp.intel.com> Hi Angie, This commit causes private registry with port cannot work. It is due to ":" is not allowed in image name part. Below cmd will fail due to the red colon ":" is invalid. docker tag REGISTRY:PORT/kube-apiserver:v1.16.0 registry.local:9001/REGISTRY:PORT/kube-apiserver:v1.16.0 I just opened below LP for it. Please help have a look. https://bugs.launchpad.net/starlingx/+bug/1847409 Best Regards Shuicheng From: Wang, Jing (Angie) Sent: Saturday, October 5, 2019 2:21 AM To: Wang, Jing (Angie) ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [docs]Changing Ansible docker_registries's "unified" key Hi All, The commit https://review.opendev.org/#/c/686057/ has been merged into master. Thanks -Angie From: Wang, Jing (Angie) [mailto:Angie.Wang at windriver.com] Sent: October-04-19 12:48 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [docs]Changing Ansible docker_registries's "unified" key Hi All, I am changing the Ansible docker_registries's "unified" key to "defaults". From docker_registries: unified: url: to docker_registries: defaults: url: And the semantics for "defaults" is a bit different as before. The "defaults" now defines common values that to be applied to all override-able public registries but the values under the specific registries, if specified, will take precedence over the values under defaults registry. If you only use defaults key, it will apply url, username and password for all registries (docker.io, quay.io, gcr.io, k8s.gcr.io, docker.elastic.co) e.g. docker_registries: defaults: url: unified.io username: adminUser password: adminPass If you have something special for some particular registry/registries, you can override the values by specifying them under its own entry. e.g. docker_registries: docker.io: username: dockerUser password: dockerPass k8s.gcr.io: username: k8sUser password: k8sPass defaults: url: unified.io username: adminUser password: adminPass This affects anyone with a setup that specifies alternate docker registries that using "unified" key as they will need to change their Ansible localhost.yml files to use "defaults" after this commit. The change is currently under review: https://review.opendev.org/#/c/686057/ Thanks, -Angie -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Wed Oct 9 06:27:43 2019 From: yong.hu at intel.com (Yong Hu) Date: Wed, 9 Oct 2019 14:27:43 +0800 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F3607B6C2@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F35F28711@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F3607B6C2@SHSMSX104.ccr.corp.intel.com> Message-ID: Folks, I've got this agenda so far: 1. Kata Container update 2. Ceph Containerization update 3. Call for action: nominating yourself for PL or TL on this distro.other project. 4. OPEN: Any outstanding issues for stx.2.0.1 and/or 3.0 release? Please feel free to append your items into the current agenda if any more. regards, Yong On 2019/10/8 8:56 PM, Xie, Cindy wrote: > All, > We will have non-openstack distri meeting tomorrow. But due to the > conflict, I am not able to host the meeting. Yong is kindly helping me > to cover this week. > Yong will send out the agenda soon and you can let him know if you have > any open topics. > Thx. - cindy > -----Original Appointment----- > *From:* Xie, Cindy > *Sent:* Thursday, April 25, 2019 5:42 PM > *To:* Xie, Cindy; 'zhaos'; Wold, Saul; > 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' > *Cc:* Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; > 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, > Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; > 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W > *Subject:* Weekly StarlingX non-OpenStack distro meeting > *When:* Wednesday, October 9, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, > Chongqing, Hong Kong, Urumqi. > *Where:* https://zoom.us/j/342730236 > > * Cadence and time slot: > > * Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) > > * 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 > > * Meeting Agenda and Minutes: > > * https://etherpad.openstack.org/p/stx-distro-other > From cristopher.j.lemus.contreras at intel.com Wed Oct 9 07:59:23 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Wed, 09 Oct 2019 02:59:23 -0500 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: List of docker images required for "platform-integ-apps": BUILD_ID="20191009T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-apiserver:v1.16.0 k8s.gcr.io/kube-controller-manager:v1.16.0 k8s.gcr.io/kube-proxy:v1.16.0 k8s.gcr.io/kube-scheduler:v1.16.0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From dominig.arfoll at fridu.net Wed Oct 9 08:00:19 2019 From: dominig.arfoll at fridu.net (Dominig ar Foll (Intel Open Source)) Date: Wed, 9 Oct 2019 10:00:19 +0200 Subject: [Starlingx-discuss] [multi-os] What is the correct workflow to submit requests in OBS In-Reply-To: References: <1bfe9216-388c-ac0f-f35c-4ef0a6ce56dc@fridu.net> Message-ID: <98986cb2-8da7-4cdf-f215-eb008ad4f29e@fridu.net> Marcela, those extra files will always be visible on OBS. They are created by the "service run" You just want to be careful not to 'add' them in your check-in. If you have a doubt before making your change request submission:    - delete all no required files (you should only have _service)    - run the command osc ar    - run your submission command". For info the command bellow, will list what are the actual 'real' files in an OBS project.     osc ls -u project_name package_name Dominig On 07/10/2019 17:34, Rosales Jimenez, Marcela A wrote: > Hi team, > > I'm starting to update _service files for Maintenance in OBS and I'm also seeing many extra obscpio files. > Here is an example https://build.opensuse.org/request/show/735890 > > Erich, how did you solve this replicated files? Or is it expected to have those obscpio files in my submission? > > I run the osc ls -u home:marcelarosalesj:branches:Cloud:StarlingX:2.0 mtce-control > And I got only two files _link and _service > > Thanks. > > Marcela > > > On 9/30/19, 3:17 PM, "Dominig ar Foll (Intel Open Source)" wrote: > > On 30/09/2019 19:04, Cordoba Malibran, Erich wrote: > > Hi, > > > > I'm trying to send a request to the fm-common project in OBS, however apparently the workflow I follow is incorrect and creates unexpected results osc ls -u project_name package_name > > > > > What I do is: > > > > - From the project's web page[0] I click on "Branch package", this creates a branched package in my account[1] > > - Checkout the project, I do this with: `osc co home:erichcm:branches:Cloud:StarlingX:1.0/fm-common` > > - For this task I'm editing the _service file and testing locally with `osc service run` and `osc build --local-package --no-verify openSUSE_Leap_15.1` > > - I delete all the non-needed files and keep only the _service file. Then I do a `osc ar` to make this changes > If you did not add or remove files (often the case) the delete and osc > ar is not required. > > - I commit the changes with `osc commit`. At this point, I see in the web page of my branched project that a set of files were created. > It's easier to do osc ci -m "commit comment" > > > > - I click on "Submit package". The created request[2] not only contains the diff of the _service, it contains the diff of all files created after I did a `osc commit`. > Most likely a small error either in not deleting the .obsinfo files > before your command osc ar > or OBS (stupidly) showing the diff between locally created files. > > If you have to run the osc ar, it's important to remove before all the > files except > _service > .rpmlintrc* > .spec* > .patches and special config files* > > * if not downloaded from git via _service. > > To know what files are really in your project dir use the command > osc ls -u project_name package_name > osc ls -u home:erichcm:branches:Cloud:StarlingX:2.0 fm-mgr > > Your first submission is OK. > > > -- > Dominig ar Foll > Senior Software Architect > Intel Open Source Technology Centre > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre From Bill.Zvonar at windriver.com Wed Oct 9 14:59:54 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 9 Oct 2019 14:59:54 +0000 Subject: [Starlingx-discuss] Community Call (Oct 9, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B01C65@ALA-MBD.corp.ad.wrs.com> Notes from today's meeting... - standing topics - any Gerrit reviews that need attention? - nothing specific, but Saul noted that cores should be checking for reviews on a regular basis - general agreement w/ this - AR: Dean to present an overview of cool things you can do in Gerrit to watch/monitor your reviews (sneak preview: https://opendev.org/x/gerrit-dash-creator) - sanity - any reds since last call? - ISO 20191003 was red: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006397.html - same issue as next day? - yes - ISO 20191004 was red: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006412.html - fixed by https://bugs.launchpad.net/starlingx/+bug/1846540 - per Ghada, it was due to the K8s upversion not being tested in the air-gapped proxy environment - agreement that it was not unreasonable for Sanity to pick this up - any unanswered calls for assistance on the mailing list? - nothing this week (add note here re: Sai Chandu's email) - debranding mirror and local repo (Saul), see http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006442.html - Saul to bring this to the next build meeting - AR: Frank is going to see if the CENGN access can be opened up to other folks besides Scott & Don so we've got more options to get stuff like this done - election - self-nomination period is underway - Ildiko's email: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006415.html - Identifying project team contributors for projects without repos (ildikov) - Utilizing the projects.yaml file under starlingx/governance - PLs to provide a list of contributors - Affected project teams - MultiOS - Networking - Openstack-distro - Release - Security - do we want to maintain a contributor list to all projects? - today's discussion... - we need to ask each PL for a list of contributors for their project - then maintain this in the projects.yaml file - see the 'extra-atcs' field that OpenStack uses (active technical contributors) - https://opendev.org/openstack/governance/src/commit/69d2ef8c1c79323a3d9eb0b1f7d741cef3d2c59f/reference/projects.yaml#L651-L795 - there's also apcs, for project contributors - Bart: is this for all contributors, or just the ones that didn't do commits - Ildiko: could do it either way - Bart: would be better if we just do it for those that aren't committers - everyone seemed to agree with this - actions... - Bill send out the lists that did get generated for each sub-project - PLs/TLs review & add - add to the projects.yaml file otherwise send to the election officials - TSC to push that through by end of next week - Ildiko: going forward, PLs/TLs maintain this Open Action Required (AR) Updates - Sep 25, 2019 -- Release Team -- add release notes to the RC1 checklist - Oct 9: done - Sep 25, 2019 -- Doc Team -- find a place for Sai Chandu's images/documentation - Oct 9: done, per last week's udpate - Sep 11, 2019 -- TEAM -- complete project sub-team re-alignment, need to finish this before we start the PL/TL election cycle, per TSC and https://review.opendev.org/#/c/680514/ - Oct 8: this is done - Sep 11, 2019 -- Ildiko -- look into documenting the process of having documentation part of the development process to the contributor guide - Oct 9: Release Team has added a checklist item for the feature PL @Milestone-3 that user documentation input for a given feature has been provided - Sep 11, 2019 -- Bruce -- identify the feature documentation gaps - Oct. 9: Because the test team is currently working on the items below, Abraham proposes collaboration between QA and Developers to write the corresponding guides. If the test team simply writes down the steps they are using to execute the tests and fills in a few blanks, handing off to the doc team, that would be a huge head start. - Distributed Cloud -- https://storyboard.openstack.org/#!/story/2005181 - GPU Kubernetes Plugin - TSN -- subtask 36405 in https://storyboard.openstack.org/#!/story/2006289 - Redfish - Infrastructure and cluster - June 26, 2019 -- Abraham -- provide a forecast for providing a Docker image list - Oct 9: done, Maria now linking Christopher's container list at the bottom of the sanity reports -----Original Message----- From: Zvonar, Bill Sent: Tuesday, October 8, 2019 8:28 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: Community Call (Oct 9, 2019) Hi all, reminder of the Community call tomorrow. Feel free to add to the agenda at [0]... - upcoming elections and project/repo restructuring - and the usual standing topics... - Gerrit reviews that need attention - Red sanity learnings - unanswered requests for help in the mailing list - open AR review 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=20191009T1400 From dominig.arfoll at fridu.net Wed Oct 9 15:19:57 2019 From: dominig.arfoll at fridu.net (Dominig ar Foll (Intel Open Source)) Date: Wed, 9 Oct 2019 17:19:57 +0200 Subject: [Starlingx-discuss] MultiOS: extractng lvm config from CentOS Message-ID: <90939da6-d184-1d83-a1b7-41bede210983@fridu.net> Hello, following our chat during the last meeting, I pass you the command that I would like to be run on a startlingX CentOS based running config (all in one). It will help me to understand what config is expected by flock services.    sudo lvmdiskscan    sudo pvs    sudo vgs -o +lv_size,lv_name Thanks. -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre From erich.cordoba.malibran at intel.com Wed Oct 9 16:03:51 2019 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Wed, 9 Oct 2019 16:03:51 +0000 Subject: [Starlingx-discuss] MultiOS: extractng lvm config from CentOS In-Reply-To: <90939da6-d184-1d83-a1b7-41bede210983@fridu.net> References: <90939da6-d184-1d83-a1b7-41bede210983@fridu.net> Message-ID: <908ab4c3198721ab29d79ec8eb81b0503052aec7.camel@intel.com> Hi, Here is the output I get from such commands in a AIO system. controller-0:~$ sudo lvmdiskscan /dev/sda4 [ 229.00 GiB] LVM physical volume /dev/sda5 [ 100.00 GiB] LVM physical volume /dev/sda6 [ 20.00 GiB] LVM physical volume 0 disks 0 partitions 0 LVM physical volume whole disks 3 LVM physical volumes controller-0:~$ sudo pvs PV VG Fmt Attr PSize PFree /dev/sda4 cgts-vg lvm2 a-- <228.97g <29.16g /dev/sda5 nova-local lvm2 a-- <100.00g 0 /dev/sda6 nova-local lvm2 a-- <20.00g 0 controller-0:~$ sudo vgs -o +lv_size,lv_name VG #PV #LV #SN Attr VSize VFree LSize LV cgts-vg 1 12 0 wz--n- <228.97g <29.16g 8.00g scratch-lv cgts-vg 1 12 0 wz--n- <228.97g <29.16g 7.81g log-lv cgts-vg 1 12 0 wz--n- <228.97g <29.16g 1.00g extension-lv cgts-vg 1 12 0 wz--n- <228.97g <29.16g 40.00g pgsql-lv cgts-vg 1 12 0 wz--n- <228.97g <29.16g 30.00g docker-lv cgts-vg 1 12 0 wz--n- <228.97g <29.16g 10.00g kubelet-lv cgts-vg 1 12 0 wz--n- <228.97g <29.16g 5.00g etcd-lv cgts-vg 1 12 0 wz--n- <228.97g <29.16g 50.00g backup-lv cgts-vg 1 12 0 wz--n- <228.97g <29.16g 16.00g dockerdistribution-lv cgts-vg 1 12 0 wz--n- <228.97g <29.16g 2.00g rabbit-lv cgts-vg 1 12 0 wz--n- <228.97g <29.16g 10.00g platform-lv cgts-vg 1 12 0 wz--n- <228.97g <29.16g 20.00g ceph-mon-lv nova-local 2 1 0 wz--n- 119.99g 0 119.99g instances_lv On Wed, 2019-10-09 at 17:19 +0200, Dominig ar Foll (Intel Open Source) wrote: > Hello, > > following our chat during the last meeting, I pass you the command > that > I would like to be run on a startlingX CentOS based running config > (all > in one). > It will help me to understand what config is expected by flock > services. > sudo lvmdiskscan > sudo pvs > sudo vgs -o +lv_size,lv_name > > Thanks. > From tingjie.chen at intel.com Wed Oct 9 16:08:45 2019 From: tingjie.chen at intel.com (Chen, Tingjie) Date: Wed, 9 Oct 2019 16:08:45 +0000 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting In-Reply-To: References: <2FD5DDB5A04D264C80D42CA35194914F35F28711@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F3607B6C2@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Yong, I am on business trip and will back in Oct 12th, Ceph containerization status will send later. Thanks, Tingjie -----Original Message----- From: Yong Hu Sent: Wednesday, October 9, 2019 2:28 PM To: Xie, Cindy ; Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; 'Rowsell, Brent' Cc: Jones, Bruce E Subject: Re: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting Folks, I've got this agenda so far: 1. Kata Container update 2. Ceph Containerization update 3. Call for action: nominating yourself for PL or TL on this distro.other project. 4. OPEN: Any outstanding issues for stx.2.0.1 and/or 3.0 release? Please feel free to append your items into the current agenda if any more. regards, Yong On 2019/10/8 8:56 PM, Xie, Cindy wrote: > All, > We will have non-openstack distri meeting tomorrow. But due to the > conflict, I am not able to host the meeting. Yong is kindly helping me > to cover this week. > Yong will send out the agenda soon and you can let him know if you > have any open topics. > Thx. - cindy > -----Original Appointment----- > *From:* Xie, Cindy > *Sent:* Thursday, April 25, 2019 5:42 PM > *To:* Xie, Cindy; 'zhaos'; Wold, Saul; > 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' > *Cc:* Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; > 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, > Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, > Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W > *Subject:* Weekly StarlingX non-OpenStack distro meeting > *When:* Wednesday, October 9, 2019 9:00 PM-10:00 PM (UTC+08:00) > Beijing, Chongqing, Hong Kong, Urumqi. > *Where:* https://zoom.us/j/342730236 > > * Cadence and time slot: > > * Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) > > * 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 > > * Meeting Agenda and Minutes: > > * https://etherpad.openstack.org/p/stx-distro-other > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From kennelson11 at gmail.com Wed Oct 9 17:26:39 2019 From: kennelson11 at gmail.com (Kendall Nelson) Date: Wed, 9 Oct 2019 10:26:39 -0700 Subject: [Starlingx-discuss] Fwd: Important Shanghai PTG Information In-Reply-To: <9FDF61D8-22A5-4CA6-8F5B-BAF8122121BA@openstack.org> References: <9FDF61D8-22A5-4CA6-8F5B-BAF8122121BA@openstack.org> Message-ID: Wanted to make sure you all saw this too :) -Kendall (diablo_rojo) ---------- Forwarded message --------- From: Kendall Waters Date: Wed, Oct 9, 2019 at 10:09 AM Subject: Important Shanghai PTG Information To: OpenStack Discuss Hello Everyone! As I’m sure you already know, the Shanghai PTG is going to be a very different event from PTGs in the past so we wanted to spell out the differences so you can be better prepared. Registration & Badges Registration for the PTG is included in the cost of the Summit. It is a single registration for both events. Since there is a single registration for the event, there is also one badge for both events. You will pick it up when you check in for the Summit and keep it until the end of the PTG. The Space Rooms The space we are contracted to have for the PTG will be laid out differently. We only have a couple dedicated rooms which are allocated to those groups with the largest numbers of people. The rest of the teams will be in a single larger room together. To help people gather teams in an organized fashion, we will be naming the arrangements of tables after OpenStack releases (Austin, Bexar, Cactus, etc). Food & Beverage Rules Unfortunately, the venue does not allow ANY food or drink in any of the rooms. This includes coffee and tea. Lunch will be from 12:30 to 1:30 in the beautiful pre-function space outside of the Blue Hall. Moving Furniture You are allowed to! Yay! If the table arrangements your project/team/group lead requested don’t work for you, feel free to move the furniture around. That being said, try to keep the tables marked with their names so that others can find them during their time slots. There will also be extra chairs stacked in the corner if your team needs them. Hours This venue is particularly strict about the hours we are allowed to be there. The PTG is scheduled to run from 9:00 in the morning to 4:30 in the evening. Its reasonably likely that if you try to come early or stay late, security will talk to you. So please be kind and respectfully leave if they ask you to. Resources Power While we have been working with the venue to accomodate our power needs, we won’t have as many power strips as we have had in the past. For this reason, we want to remind everyone to charge all their devices every night and share the power strips we do have during the day. Sharing is caring! Flipcharts While we won’t have projection available, we will have some flipcharts around. Each dedicated room will have one flipchart and the big main room will have a few to share. Please feel free to grab one when you need it, but put it back when you are finished so that others can use it if they need. Again, sharing is caring! :) Onboarding A lot of the usual PTG attendees won’t be able to attend this event, but we will also have a lot of new faces. With this in mind, we have decided to add project onboarding to the PTG so that the new contributors can get up to speed with the projects meeting that week. The teams gathering that will be doing onboarding will have that denoted on the print and digital schedule on site. They have also been encouraged to promote when they will be doing their onboarding via the PTGBot and on the mailing lists. If you have any questions, please let us know! Cheers, The Kendalls (wendallkaters & diablo_rojo) -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Oct 9 17:56:22 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 9 Oct 2019 17:56:22 +0000 Subject: [Starlingx-discuss] Voters for PL/TL election... Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B01E81@ALA-MBD.corp.ad.wrs.com> As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). Bill... build - don.penney at windriver.com - scott.little at windriver.com - dtroyer at gmail.com - al.bailey at windriver.com - tyler.smith at windriver.com - daniel.badea at windriver.com - sgw at linux.intel.com - erich.cordoba.malibran at intel.com - stefan.dinescu at windriver.com - ran1.an at intel.com - tao.liu at windriver.com - joseph.richard at windriver.com - felipe.de.jesus.ruiz.garcia at intel.com - angie.wang at windriver.com - Kristine.Bujold at windriver.com - jesus.ornelas.aguayo at intel.com - lihaijing at fiberhome.com - jason.mckenna at windriver.com - zhangyangyang at unionpay.com - jerry.sun at windriver.com - alex.kozyrev at windriver.com - steven.webster at windriver.com - jaegerandi at gmail.com - longx.li at intel.com - john.kung at windriver.com - maria.yousaf at windriver.com - zhipengs.liu at intel.com - lihang0166 at fiberhome.com - zhiguox.zhang at intel.com - bin.yang at intel.com - iwienand at redhat.com - marcela.a.rosales.jimenez at intel.com - tee.ngo at windriver.com - haochuan.z.chen at intel.com - caoran at fiberhome.com - zhang.kunpeng at 99cloud.net - Paul-Emile.Element at windriver.com config - angie.wang at windriver.com - tingjie.chen at intel.com - kevin.smith at windriver.com - ovidiu.poncea at windriver.com - bin.qian at windriver.com - joseph.richard at windriver.com - Kristine.Bujold at windriver.com - al.bailey at windriver.com - andy.ning at windriver.com - david.sullivan at windriver.com - daniel.badea at windriver.com - zhipengs.liu at intel.com - tao.liu at windriver.com - haochuan.z.chen at intel.com - lihang0166 at fiberhome.com - stefan.dinescu at windriver.com - ran1.an at intel.com - sgw at linux.intel.com - teresa.ho at windriver.com - eric.macdonald at windriver.com - alex.kozyrev at windriver.com - erich.cordoba.malibran at intel.com - scott.little at windriver.com - tee.ngo at windriver.com - tyler.smith at windriver.com - bin.yang at intel.com - john.kung at windriver.com - jaegerandi at gmail.com - mingyuan.qi at intel.com - eric.barrett at windriver.com - zhang.kunpeng at 99cloud.net - wei.zhou at windriver.com - steven.webster at windriver.com - jerry.sun at windriver.com - dtroyer at gmail.com - barton.wensley at windriver.com - matt.peters at windriver.com - zhu.boxiang at 99cloud.net - don.penney at windriver.com - James.Gauld at windriver.com - junbo85.li at gmail.com - chris.friesen at windriver.com - marcela.a.rosales.jimenez at intel.com - cheng1.li at intel.com - chenjie.xu at intel.com - allain.legacy at windriver.com - yan.chen at intel.com - elena.taivan at windriver.com - yizhoux.xu at intel.com - iwienand at redhat.com - irina.mihai at windriver.com - wzj334965317 at outlook.com - ma.lei at 99cloud.net - eric.zhang at windriver.com - Paul-Emile.Element at windriver.com - zhangyangyang at unionpay.com - daniel.chavolla at windriver.com - lachlan.plant at windriver.com - srifenbark at gmail.com - shoaib.nasir at windriver.com - singh.surya64mnnit at gmail.com containers - al.bailey at windriver.com - kevin.smith at windriver.com - zhipengs.liu at intel.com - ran1.an at intel.com distcloud - andy.ning at windriver.com - tyler.smith at windriver.com - scott.little at windriver.com - xiefp88 at sina.com - jaegerandi at gmail.com - dtroyer at gmail.com - tao.liu at windriver.com - don.penney at windriver.com - al.bailey at windriver.com - Kristine.Bujold at windriver.com - cao.yuan at 99cloud.net - wzj334965317 at outlook.com - alex.kozyrev at windriver.com - lachlan.plant at windriver.com - junbo85.li at gmail.com - srifenbark at gmail.com - barton.wensley at windriver.com distro - al.bailey at windriver.com - alex.kozyrev at windriver.com - jerry.sun at windriver.com - erich.cordoba.malibran at intel.com - daniel.badea at windriver.com - Kristine.Bujold at windriver.com - scott.little at windriver.com - jaegerandi at gmail.com - bin.qian at windriver.com - zhipengs.liu at intel.com - ran1.an at intel.com - eric.macdonald at windriver.com - john.kung at windriver.com - andy.ning at windriver.com - dtroyer at gmail.com - stefan.dinescu at windriver.com - bin.yang at intel.com - don.penney at windriver.com - eric.barrett at windriver.com - barton.wensley at windriver.com - junbo85.li at gmail.com - angie.wang at windriver.com - teresa.ho at windriver.com - sgw at linux.intel.com - tao.liu at windriver.com - zhiguox.zhang at intel.com - steven.webster at windriver.com - chenjie.xu at intel.com - James.Gauld at windriver.com - longx.li at intel.com - tyler.smith at windriver.com - chenlx at fiberhome.com - corvus at inaugust.com - chris.friesen at windriver.com - haochuan.z.chen at intel.com - daniel.chavolla at windriver.com - wei.zhou at windriver.com - ovidiu.poncea at windriver.com - joseph.richard at windriver.com - jason.mckenna at windriver.com - louie.kwan at windriver.com - Paul-Emile.Element at windriver.com - zhangyangyang at unionpay.com - tee.ngo at windriver.com - ma.lei at 99cloud.net docs - bruce.e.jones at intel.com - jaegerandi at gmail.com - chenlx at fiberhome.com - lihang0166 at fiberhome.com - srifenbark at gmail.com - xiefp88 at sina.com - liuyamin at fiberhome.com - lipan7195 at fiberhome.com - fungi at yuggoth.org - curtis at serverascode.com - iwienand at redhat.com - erich.cordoba.malibran at intel.com - li.xiaoli at 99cloud.net - zhang.kunpeng at 99cloud.net - dtroyer at gmail.com flock-services - tyler.smith at windriver.com - david.sullivan at windriver.com - Kristine.Bujold at windriver.com - al.bailey at windriver.com - jaegerandi at gmail.com - haochuan.z.chen at intel.com - dtroyer at gmail.com - teresa.ho at windriver.com - junbo85.li at gmail.com - ovidiu.poncea at windriver.com - yan.chen at intel.com - sgw at linux.intel.com - steven.webster at windriver.com - zhipengs.liu at intel.com - don.penney at windriver.com - eric.barrett at windriver.com - erich.cordoba.malibran at intel.com - scott.little at windriver.com - john.kung at windriver.com - wzj334965317 at outlook.com - tao.liu at windriver.com - stefan.dinescu at windriver.com - wei.zhou at windriver.com - James.Gauld at windriver.com - angie.wang at windriver.com - guozhen.she at intel.com - bin.qian at windriver.com - zqhsh527 at 163.com - andy.ning at windriver.com - mingyuan.qi at intel.com - xiefp88 at sina.com - daniel.badea at windriver.com - chris.friesen at windriver.com - elena.taivan at windriver.com - jerry.sun at windriver.com - marcela.a.rosales.jimenez at intel.com - xbyan at fiberhome.com - ran1.an at intel.com - alex.kozyrev at windriver.com - eric.macdonald at windriver.com - matt.peters at windriver.com - barton.wensley at windriver.com - kevin.smith at windriver.com - zhanglf01 at inspur.com - lachlan.plant at windriver.com - zhaowei7146 at fiberhome.com - lvcy at fiberhome.com - sxmatch1986 at gmail.com - ma.lei at 99cloud.net - lijunjie at cloudin.cn - jason.mckenna at windriver.com - srifenbark at gmail.com - tee.ngo at windriver.com - zhangzhaoshan at inspur.com - zhaolong at inspur.com - lihang0166 at fiberhome.com multios networking networking openstack_distro release security test - lihang0166 at fiberhome.com - dtroyer at gmail.com - erich.cordoba.malibran at intel.com - yang.liu at windriver.com - al.bailey at windriver.com - juan.p.gomez at intel.com - anujeyan.manokeran at windriver.com - maria.yousaf at windriver.com - peng.peng at windriver.com - marvin.huang at windriver.com [0] https://etherpad.openstack.org/p/stx-status From kennelson11 at gmail.com Wed Oct 9 18:06:38 2019 From: kennelson11 at gmail.com (Kendall Nelson) Date: Wed, 9 Oct 2019 11:06:38 -0700 Subject: [Starlingx-discuss] PTG Team Photos Message-ID: Hello Everyone! We are excited to see you in a few weeks at the PTG and wanted to share that we will be taking team photos again! Here is an ethercalc signup for the available time slots [1]. We will be providing time on Thursday Morning/Afternoon and Friday morning to come as a team to get your photo taken. Slots are only ten minutes so its *important that everyone be on time*! The location is TBD at this point, but it will likely be in the prefunction space near registration. Thanks, -Kendall Nelson (diablo_rojo) [1] https://ethercalc.openstack.org/lnupu1sx6ljl -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openstack.org Wed Oct 9 18:22:17 2019 From: ildiko at openstack.org (Ildiko Vancsa) Date: Wed, 9 Oct 2019 20:22:17 +0200 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC007B01E81@ALA-MBD.corp.ad.wrs.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B01E81@ALA-MBD.corp.ad.wrs.com> Message-ID: <7F4B4ABE-C604-4C28-87DF-75290233FAF2@openstack.org> Hi, I created patches to capture contributors to the projects where we cannot use the repositories to generate the data. I would like to ask PLs and TLs for MultiOS, Networking, OpenStack-Distro, Release and Security to check the list of names as well as contributors to these projects to check if the lists of names are correct: * MultiOS: https://review.opendev.org/#/c/687631/ * Networking: https://review.opendev.org/#/c/687630/ * OpenStack-Distro: https://review.opendev.org/#/c/687632/ * Release: https://review.opendev.org/#/c/687633/ * Security: https://review.opendev.org/#/c/687635/ Thanks, Ildikó > On 2019. Oct 9., at 19:56, Zvonar, Bill wrote: > > As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. > > The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. > > If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). > > Bill... > > build > > - don.penney at windriver.com > - scott.little at windriver.com > - dtroyer at gmail.com > - al.bailey at windriver.com > - tyler.smith at windriver.com > - daniel.badea at windriver.com > - sgw at linux.intel.com > - erich.cordoba.malibran at intel.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - tao.liu at windriver.com > - joseph.richard at windriver.com > - felipe.de.jesus.ruiz.garcia at intel.com > - angie.wang at windriver.com > - Kristine.Bujold at windriver.com > - jesus.ornelas.aguayo at intel.com > - lihaijing at fiberhome.com > - jason.mckenna at windriver.com > - zhangyangyang at unionpay.com > - jerry.sun at windriver.com > - alex.kozyrev at windriver.com > - steven.webster at windriver.com > - jaegerandi at gmail.com > - longx.li at intel.com > - john.kung at windriver.com > - maria.yousaf at windriver.com > - zhipengs.liu at intel.com > - lihang0166 at fiberhome.com > - zhiguox.zhang at intel.com > - bin.yang at intel.com > - iwienand at redhat.com > - marcela.a.rosales.jimenez at intel.com > - tee.ngo at windriver.com > - haochuan.z.chen at intel.com > - caoran at fiberhome.com > - zhang.kunpeng at 99cloud.net > - Paul-Emile.Element at windriver.com > > config > > - angie.wang at windriver.com > - tingjie.chen at intel.com > - kevin.smith at windriver.com > - ovidiu.poncea at windriver.com > - bin.qian at windriver.com > - joseph.richard at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - andy.ning at windriver.com > - david.sullivan at windriver.com > - daniel.badea at windriver.com > - zhipengs.liu at intel.com > - tao.liu at windriver.com > - haochuan.z.chen at intel.com > - lihang0166 at fiberhome.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - sgw at linux.intel.com > - teresa.ho at windriver.com > - eric.macdonald at windriver.com > - alex.kozyrev at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - tee.ngo at windriver.com > - tyler.smith at windriver.com > - bin.yang at intel.com > - john.kung at windriver.com > - jaegerandi at gmail.com > - mingyuan.qi at intel.com > - eric.barrett at windriver.com > - zhang.kunpeng at 99cloud.net > - wei.zhou at windriver.com > - steven.webster at windriver.com > - jerry.sun at windriver.com > - dtroyer at gmail.com > - barton.wensley at windriver.com > - matt.peters at windriver.com > - zhu.boxiang at 99cloud.net > - don.penney at windriver.com > - James.Gauld at windriver.com > - junbo85.li at gmail.com > - chris.friesen at windriver.com > - marcela.a.rosales.jimenez at intel.com > - cheng1.li at intel.com > - chenjie.xu at intel.com > - allain.legacy at windriver.com > - yan.chen at intel.com > - elena.taivan at windriver.com > - yizhoux.xu at intel.com > - iwienand at redhat.com > - irina.mihai at windriver.com > - wzj334965317 at outlook.com > - ma.lei at 99cloud.net > - eric.zhang at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - daniel.chavolla at windriver.com > - lachlan.plant at windriver.com > - srifenbark at gmail.com > - shoaib.nasir at windriver.com > - singh.surya64mnnit at gmail.com > > containers > > - al.bailey at windriver.com > - kevin.smith at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > > distcloud > > - andy.ning at windriver.com > - tyler.smith at windriver.com > - scott.little at windriver.com > - xiefp88 at sina.com > - jaegerandi at gmail.com > - dtroyer at gmail.com > - tao.liu at windriver.com > - don.penney at windriver.com > - al.bailey at windriver.com > - Kristine.Bujold at windriver.com > - cao.yuan at 99cloud.net > - wzj334965317 at outlook.com > - alex.kozyrev at windriver.com > - lachlan.plant at windriver.com > - junbo85.li at gmail.com > - srifenbark at gmail.com > - barton.wensley at windriver.com > > distro > > - al.bailey at windriver.com > - alex.kozyrev at windriver.com > - jerry.sun at windriver.com > - erich.cordoba.malibran at intel.com > - daniel.badea at windriver.com > - Kristine.Bujold at windriver.com > - scott.little at windriver.com > - jaegerandi at gmail.com > - bin.qian at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > - eric.macdonald at windriver.com > - john.kung at windriver.com > - andy.ning at windriver.com > - dtroyer at gmail.com > - stefan.dinescu at windriver.com > - bin.yang at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - barton.wensley at windriver.com > - junbo85.li at gmail.com > - angie.wang at windriver.com > - teresa.ho at windriver.com > - sgw at linux.intel.com > - tao.liu at windriver.com > - zhiguox.zhang at intel.com > - steven.webster at windriver.com > - chenjie.xu at intel.com > - James.Gauld at windriver.com > - longx.li at intel.com > - tyler.smith at windriver.com > - chenlx at fiberhome.com > - corvus at inaugust.com > - chris.friesen at windriver.com > - haochuan.z.chen at intel.com > - daniel.chavolla at windriver.com > - wei.zhou at windriver.com > - ovidiu.poncea at windriver.com > - joseph.richard at windriver.com > - jason.mckenna at windriver.com > - louie.kwan at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - tee.ngo at windriver.com > - ma.lei at 99cloud.net > > docs > > - bruce.e.jones at intel.com > - jaegerandi at gmail.com > - chenlx at fiberhome.com > - lihang0166 at fiberhome.com > - srifenbark at gmail.com > - xiefp88 at sina.com > - liuyamin at fiberhome.com > - lipan7195 at fiberhome.com > - fungi at yuggoth.org > - curtis at serverascode.com > - iwienand at redhat.com > - erich.cordoba.malibran at intel.com > - li.xiaoli at 99cloud.net > - zhang.kunpeng at 99cloud.net > - dtroyer at gmail.com > > flock-services > > - tyler.smith at windriver.com > - david.sullivan at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - jaegerandi at gmail.com > - haochuan.z.chen at intel.com > - dtroyer at gmail.com > - teresa.ho at windriver.com > - junbo85.li at gmail.com > - ovidiu.poncea at windriver.com > - yan.chen at intel.com > - sgw at linux.intel.com > - steven.webster at windriver.com > - zhipengs.liu at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - john.kung at windriver.com > - wzj334965317 at outlook.com > - tao.liu at windriver.com > - stefan.dinescu at windriver.com > - wei.zhou at windriver.com > - James.Gauld at windriver.com > - angie.wang at windriver.com > - guozhen.she at intel.com > - bin.qian at windriver.com > - zqhsh527 at 163.com > - andy.ning at windriver.com > - mingyuan.qi at intel.com > - xiefp88 at sina.com > - daniel.badea at windriver.com > - chris.friesen at windriver.com > - elena.taivan at windriver.com > - jerry.sun at windriver.com > - marcela.a.rosales.jimenez at intel.com > - xbyan at fiberhome.com > - ran1.an at intel.com > - alex.kozyrev at windriver.com > - eric.macdonald at windriver.com > - matt.peters at windriver.com > - barton.wensley at windriver.com > - kevin.smith at windriver.com > - zhanglf01 at inspur.com > - lachlan.plant at windriver.com > - zhaowei7146 at fiberhome.com > - lvcy at fiberhome.com > - sxmatch1986 at gmail.com > - ma.lei at 99cloud.net > - lijunjie at cloudin.cn > - jason.mckenna at windriver.com > - srifenbark at gmail.com > - tee.ngo at windriver.com > - zhangzhaoshan at inspur.com > - zhaolong at inspur.com > - lihang0166 at fiberhome.com > > multios > > > > networking > > > > networking > > > > openstack_distro > > > > release > > > > security > > > > test > > - lihang0166 at fiberhome.com > - dtroyer at gmail.com > - erich.cordoba.malibran at intel.com > - yang.liu at windriver.com > - al.bailey at windriver.com > - juan.p.gomez at intel.com > - anujeyan.manokeran at windriver.com > - maria.yousaf at windriver.com > - peng.peng at windriver.com > - marvin.huang at windriver.com > > [0] https://etherpad.openstack.org/p/stx-status > > _______________________________________________ > 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 Wed Oct 9 18:45:04 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Wed, 9 Oct 2019 18:45:04 +0000 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: <7F4B4ABE-C604-4C28-87DF-75290233FAF2@openstack.org> References: <586E8B730EA0DA4A9D6A80A10E486BC007B01E81@ALA-MBD.corp.ad.wrs.com> <7F4B4ABE-C604-4C28-87DF-75290233FAF2@openstack.org> Message-ID: Bill/Ildiko: The list of contributors for containers is incorrect as it is only listing contributors for the last month which was when these repos were split out from the flock repos. The algorithm should instead be to check all the files in these repos and then go back to the beginning of the project to see who make commits to those files. Can this be done? Frank -----Original Message----- From: Ildiko Vancsa [mailto:ildiko at openstack.org] Sent: Wednesday, October 09, 2019 2:22 PM To: starlingx-discuss at lists.starlingx.io Cc: Jones, Bruce E ; Zvonar, Bill Subject: Re: [Starlingx-discuss] Voters for PL/TL election... Hi, I created patches to capture contributors to the projects where we cannot use the repositories to generate the data. I would like to ask PLs and TLs for MultiOS, Networking, OpenStack-Distro, Release and Security to check the list of names as well as contributors to these projects to check if the lists of names are correct: * MultiOS: https://review.opendev.org/#/c/687631/ * Networking: https://review.opendev.org/#/c/687630/ * OpenStack-Distro: https://review.opendev.org/#/c/687632/ * Release: https://review.opendev.org/#/c/687633/ * Security: https://review.opendev.org/#/c/687635/ Thanks, Ildikó > On 2019. Oct 9., at 19:56, Zvonar, Bill wrote: > > As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. > > The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. > > If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). > > Bill... > > build > > - don.penney at windriver.com > - scott.little at windriver.com > - dtroyer at gmail.com > - al.bailey at windriver.com > - tyler.smith at windriver.com > - daniel.badea at windriver.com > - sgw at linux.intel.com > - erich.cordoba.malibran at intel.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - tao.liu at windriver.com > - joseph.richard at windriver.com > - felipe.de.jesus.ruiz.garcia at intel.com > - angie.wang at windriver.com > - Kristine.Bujold at windriver.com > - jesus.ornelas.aguayo at intel.com > - lihaijing at fiberhome.com > - jason.mckenna at windriver.com > - zhangyangyang at unionpay.com > - jerry.sun at windriver.com > - alex.kozyrev at windriver.com > - steven.webster at windriver.com > - jaegerandi at gmail.com > - longx.li at intel.com > - john.kung at windriver.com > - maria.yousaf at windriver.com > - zhipengs.liu at intel.com > - lihang0166 at fiberhome.com > - zhiguox.zhang at intel.com > - bin.yang at intel.com > - iwienand at redhat.com > - marcela.a.rosales.jimenez at intel.com > - tee.ngo at windriver.com > - haochuan.z.chen at intel.com > - caoran at fiberhome.com > - zhang.kunpeng at 99cloud.net > - Paul-Emile.Element at windriver.com > > config > > - angie.wang at windriver.com > - tingjie.chen at intel.com > - kevin.smith at windriver.com > - ovidiu.poncea at windriver.com > - bin.qian at windriver.com > - joseph.richard at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - andy.ning at windriver.com > - david.sullivan at windriver.com > - daniel.badea at windriver.com > - zhipengs.liu at intel.com > - tao.liu at windriver.com > - haochuan.z.chen at intel.com > - lihang0166 at fiberhome.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - sgw at linux.intel.com > - teresa.ho at windriver.com > - eric.macdonald at windriver.com > - alex.kozyrev at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - tee.ngo at windriver.com > - tyler.smith at windriver.com > - bin.yang at intel.com > - john.kung at windriver.com > - jaegerandi at gmail.com > - mingyuan.qi at intel.com > - eric.barrett at windriver.com > - zhang.kunpeng at 99cloud.net > - wei.zhou at windriver.com > - steven.webster at windriver.com > - jerry.sun at windriver.com > - dtroyer at gmail.com > - barton.wensley at windriver.com > - matt.peters at windriver.com > - zhu.boxiang at 99cloud.net > - don.penney at windriver.com > - James.Gauld at windriver.com > - junbo85.li at gmail.com > - chris.friesen at windriver.com > - marcela.a.rosales.jimenez at intel.com > - cheng1.li at intel.com > - chenjie.xu at intel.com > - allain.legacy at windriver.com > - yan.chen at intel.com > - elena.taivan at windriver.com > - yizhoux.xu at intel.com > - iwienand at redhat.com > - irina.mihai at windriver.com > - wzj334965317 at outlook.com > - ma.lei at 99cloud.net > - eric.zhang at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - daniel.chavolla at windriver.com > - lachlan.plant at windriver.com > - srifenbark at gmail.com > - shoaib.nasir at windriver.com > - singh.surya64mnnit at gmail.com > > containers > > - al.bailey at windriver.com > - kevin.smith at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > > distcloud > > - andy.ning at windriver.com > - tyler.smith at windriver.com > - scott.little at windriver.com > - xiefp88 at sina.com > - jaegerandi at gmail.com > - dtroyer at gmail.com > - tao.liu at windriver.com > - don.penney at windriver.com > - al.bailey at windriver.com > - Kristine.Bujold at windriver.com > - cao.yuan at 99cloud.net > - wzj334965317 at outlook.com > - alex.kozyrev at windriver.com > - lachlan.plant at windriver.com > - junbo85.li at gmail.com > - srifenbark at gmail.com > - barton.wensley at windriver.com > > distro > > - al.bailey at windriver.com > - alex.kozyrev at windriver.com > - jerry.sun at windriver.com > - erich.cordoba.malibran at intel.com > - daniel.badea at windriver.com > - Kristine.Bujold at windriver.com > - scott.little at windriver.com > - jaegerandi at gmail.com > - bin.qian at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > - eric.macdonald at windriver.com > - john.kung at windriver.com > - andy.ning at windriver.com > - dtroyer at gmail.com > - stefan.dinescu at windriver.com > - bin.yang at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - barton.wensley at windriver.com > - junbo85.li at gmail.com > - angie.wang at windriver.com > - teresa.ho at windriver.com > - sgw at linux.intel.com > - tao.liu at windriver.com > - zhiguox.zhang at intel.com > - steven.webster at windriver.com > - chenjie.xu at intel.com > - James.Gauld at windriver.com > - longx.li at intel.com > - tyler.smith at windriver.com > - chenlx at fiberhome.com > - corvus at inaugust.com > - chris.friesen at windriver.com > - haochuan.z.chen at intel.com > - daniel.chavolla at windriver.com > - wei.zhou at windriver.com > - ovidiu.poncea at windriver.com > - joseph.richard at windriver.com > - jason.mckenna at windriver.com > - louie.kwan at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - tee.ngo at windriver.com > - ma.lei at 99cloud.net > > docs > > - bruce.e.jones at intel.com > - jaegerandi at gmail.com > - chenlx at fiberhome.com > - lihang0166 at fiberhome.com > - srifenbark at gmail.com > - xiefp88 at sina.com > - liuyamin at fiberhome.com > - lipan7195 at fiberhome.com > - fungi at yuggoth.org > - curtis at serverascode.com > - iwienand at redhat.com > - erich.cordoba.malibran at intel.com > - li.xiaoli at 99cloud.net > - zhang.kunpeng at 99cloud.net > - dtroyer at gmail.com > > flock-services > > - tyler.smith at windriver.com > - david.sullivan at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - jaegerandi at gmail.com > - haochuan.z.chen at intel.com > - dtroyer at gmail.com > - teresa.ho at windriver.com > - junbo85.li at gmail.com > - ovidiu.poncea at windriver.com > - yan.chen at intel.com > - sgw at linux.intel.com > - steven.webster at windriver.com > - zhipengs.liu at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - john.kung at windriver.com > - wzj334965317 at outlook.com > - tao.liu at windriver.com > - stefan.dinescu at windriver.com > - wei.zhou at windriver.com > - James.Gauld at windriver.com > - angie.wang at windriver.com > - guozhen.she at intel.com > - bin.qian at windriver.com > - zqhsh527 at 163.com > - andy.ning at windriver.com > - mingyuan.qi at intel.com > - xiefp88 at sina.com > - daniel.badea at windriver.com > - chris.friesen at windriver.com > - elena.taivan at windriver.com > - jerry.sun at windriver.com > - marcela.a.rosales.jimenez at intel.com > - xbyan at fiberhome.com > - ran1.an at intel.com > - alex.kozyrev at windriver.com > - eric.macdonald at windriver.com > - matt.peters at windriver.com > - barton.wensley at windriver.com > - kevin.smith at windriver.com > - zhanglf01 at inspur.com > - lachlan.plant at windriver.com > - zhaowei7146 at fiberhome.com > - lvcy at fiberhome.com > - sxmatch1986 at gmail.com > - ma.lei at 99cloud.net > - lijunjie at cloudin.cn > - jason.mckenna at windriver.com > - srifenbark at gmail.com > - tee.ngo at windriver.com > - zhangzhaoshan at inspur.com > - zhaolong at inspur.com > - lihang0166 at fiberhome.com > > multios > > > > networking > > > > networking > > > > openstack_distro > > > > release > > > > security > > > > test > > - lihang0166 at fiberhome.com > - dtroyer at gmail.com > - erich.cordoba.malibran at intel.com > - yang.liu at windriver.com > - al.bailey at windriver.com > - juan.p.gomez at intel.com > - anujeyan.manokeran at windriver.com > - maria.yousaf at windriver.com > - peng.peng at windriver.com > - marvin.huang at windriver.com > > [0] https://etherpad.openstack.org/p/stx-status > > _______________________________________________ > 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 Wed Oct 9 19:06:24 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 9 Oct 2019 19:06:24 +0000 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: References: <586E8B730EA0DA4A9D6A80A10E486BC007B01E81@ALA-MBD.corp.ad.wrs.com> <7F4B4ABE-C604-4C28-87DF-75290233FAF2@openstack.org> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15957B2@ALA-MBD.corp.ad.wrs.com> A query of specific repos for "containers" in the master branch, of commits in a given date range, getting the Committer for the reviews: $ for d in containers helm-charts monitor-armada-app openstack-armada-app platform-armada-app ; do cd $d; git log --pretty=fuller --after="Oct 6 00:00:00 2018" --before="Oct 7 00:00:00 2019" |grep Commit: | sort -u |grep -v review at openstack.org ; cd ..; done | sed -r 's/.*<(.*)>/\1/' | sort -u -t'@' -k2,2 -k1,1 dtroyer at gmail.com austin.sun at intel.com bin.yang at intel.com cheng1.li at intel.com chenjie.xu at intel.com haochuan.z.chen at intel.com kailun.qin at intel.com mario.alfredo.c.arevalo at intel.com mingyuan.qi at intel.com ran1.an at intel.com shuicheng.lin at intel.com weifei.yu at intel.com yi.c.wang at intel.com yong.hu at intel.com zhipengs.liu at intel.com sgw at linux.intel.com al.bailey at windriver.com Al.Bailey at windriver.com alex.kozyrev at windriver.com angie.wang at windriver.com barton.wensley at windriver.com chris.friesen at windriver.com daniel.badea at windriver.com david.sullivan at windriver.com don.penney at windriver.com elena.taivan at windriver.com gerry.kopec at windriver.com Gerry.Kopec at windriver.com irina.mihai at windriver.com jason.mckenna at windriver.com jerry.sun at windriver.com john.kung at windriver.com joseph.richard at windriver.com kevin.smith at windriver.com kristine.bujold at windriver.com matt.peters at windriver.com ovidiu.poncea at windriver.com robert.church at windriver.com scott.little at windriver.com stefan.dinescu at windriver.com tao.liu at windriver.com teresa.ho at windriver.com tyler.smith at windriver.com -----Original Message----- From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Wednesday, October 09, 2019 2:45 PM To: Ildiko Vancsa; starlingx-discuss at lists.starlingx.io Cc: Jones, Bruce E; Zvonar, Bill Subject: Re: [Starlingx-discuss] Voters for PL/TL election... Bill/Ildiko: The list of contributors for containers is incorrect as it is only listing contributors for the last month which was when these repos were split out from the flock repos. The algorithm should instead be to check all the files in these repos and then go back to the beginning of the project to see who make commits to those files. Can this be done? Frank -----Original Message----- From: Ildiko Vancsa [mailto:ildiko at openstack.org] Sent: Wednesday, October 09, 2019 2:22 PM To: starlingx-discuss at lists.starlingx.io Cc: Jones, Bruce E ; Zvonar, Bill Subject: Re: [Starlingx-discuss] Voters for PL/TL election... Hi, I created patches to capture contributors to the projects where we cannot use the repositories to generate the data. I would like to ask PLs and TLs for MultiOS, Networking, OpenStack-Distro, Release and Security to check the list of names as well as contributors to these projects to check if the lists of names are correct: * MultiOS: https://review.opendev.org/#/c/687631/ * Networking: https://review.opendev.org/#/c/687630/ * OpenStack-Distro: https://review.opendev.org/#/c/687632/ * Release: https://review.opendev.org/#/c/687633/ * Security: https://review.opendev.org/#/c/687635/ Thanks, Ildikó > On 2019. Oct 9., at 19:56, Zvonar, Bill wrote: > > As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. > > The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. > > If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). > > Bill... > > build > > - don.penney at windriver.com > - scott.little at windriver.com > - dtroyer at gmail.com > - al.bailey at windriver.com > - tyler.smith at windriver.com > - daniel.badea at windriver.com > - sgw at linux.intel.com > - erich.cordoba.malibran at intel.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - tao.liu at windriver.com > - joseph.richard at windriver.com > - felipe.de.jesus.ruiz.garcia at intel.com > - angie.wang at windriver.com > - Kristine.Bujold at windriver.com > - jesus.ornelas.aguayo at intel.com > - lihaijing at fiberhome.com > - jason.mckenna at windriver.com > - zhangyangyang at unionpay.com > - jerry.sun at windriver.com > - alex.kozyrev at windriver.com > - steven.webster at windriver.com > - jaegerandi at gmail.com > - longx.li at intel.com > - john.kung at windriver.com > - maria.yousaf at windriver.com > - zhipengs.liu at intel.com > - lihang0166 at fiberhome.com > - zhiguox.zhang at intel.com > - bin.yang at intel.com > - iwienand at redhat.com > - marcela.a.rosales.jimenez at intel.com > - tee.ngo at windriver.com > - haochuan.z.chen at intel.com > - caoran at fiberhome.com > - zhang.kunpeng at 99cloud.net > - Paul-Emile.Element at windriver.com > > config > > - angie.wang at windriver.com > - tingjie.chen at intel.com > - kevin.smith at windriver.com > - ovidiu.poncea at windriver.com > - bin.qian at windriver.com > - joseph.richard at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - andy.ning at windriver.com > - david.sullivan at windriver.com > - daniel.badea at windriver.com > - zhipengs.liu at intel.com > - tao.liu at windriver.com > - haochuan.z.chen at intel.com > - lihang0166 at fiberhome.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - sgw at linux.intel.com > - teresa.ho at windriver.com > - eric.macdonald at windriver.com > - alex.kozyrev at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - tee.ngo at windriver.com > - tyler.smith at windriver.com > - bin.yang at intel.com > - john.kung at windriver.com > - jaegerandi at gmail.com > - mingyuan.qi at intel.com > - eric.barrett at windriver.com > - zhang.kunpeng at 99cloud.net > - wei.zhou at windriver.com > - steven.webster at windriver.com > - jerry.sun at windriver.com > - dtroyer at gmail.com > - barton.wensley at windriver.com > - matt.peters at windriver.com > - zhu.boxiang at 99cloud.net > - don.penney at windriver.com > - James.Gauld at windriver.com > - junbo85.li at gmail.com > - chris.friesen at windriver.com > - marcela.a.rosales.jimenez at intel.com > - cheng1.li at intel.com > - chenjie.xu at intel.com > - allain.legacy at windriver.com > - yan.chen at intel.com > - elena.taivan at windriver.com > - yizhoux.xu at intel.com > - iwienand at redhat.com > - irina.mihai at windriver.com > - wzj334965317 at outlook.com > - ma.lei at 99cloud.net > - eric.zhang at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - daniel.chavolla at windriver.com > - lachlan.plant at windriver.com > - srifenbark at gmail.com > - shoaib.nasir at windriver.com > - singh.surya64mnnit at gmail.com > > containers > > - al.bailey at windriver.com > - kevin.smith at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > > distcloud > > - andy.ning at windriver.com > - tyler.smith at windriver.com > - scott.little at windriver.com > - xiefp88 at sina.com > - jaegerandi at gmail.com > - dtroyer at gmail.com > - tao.liu at windriver.com > - don.penney at windriver.com > - al.bailey at windriver.com > - Kristine.Bujold at windriver.com > - cao.yuan at 99cloud.net > - wzj334965317 at outlook.com > - alex.kozyrev at windriver.com > - lachlan.plant at windriver.com > - junbo85.li at gmail.com > - srifenbark at gmail.com > - barton.wensley at windriver.com > > distro > > - al.bailey at windriver.com > - alex.kozyrev at windriver.com > - jerry.sun at windriver.com > - erich.cordoba.malibran at intel.com > - daniel.badea at windriver.com > - Kristine.Bujold at windriver.com > - scott.little at windriver.com > - jaegerandi at gmail.com > - bin.qian at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > - eric.macdonald at windriver.com > - john.kung at windriver.com > - andy.ning at windriver.com > - dtroyer at gmail.com > - stefan.dinescu at windriver.com > - bin.yang at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - barton.wensley at windriver.com > - junbo85.li at gmail.com > - angie.wang at windriver.com > - teresa.ho at windriver.com > - sgw at linux.intel.com > - tao.liu at windriver.com > - zhiguox.zhang at intel.com > - steven.webster at windriver.com > - chenjie.xu at intel.com > - James.Gauld at windriver.com > - longx.li at intel.com > - tyler.smith at windriver.com > - chenlx at fiberhome.com > - corvus at inaugust.com > - chris.friesen at windriver.com > - haochuan.z.chen at intel.com > - daniel.chavolla at windriver.com > - wei.zhou at windriver.com > - ovidiu.poncea at windriver.com > - joseph.richard at windriver.com > - jason.mckenna at windriver.com > - louie.kwan at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - tee.ngo at windriver.com > - ma.lei at 99cloud.net > > docs > > - bruce.e.jones at intel.com > - jaegerandi at gmail.com > - chenlx at fiberhome.com > - lihang0166 at fiberhome.com > - srifenbark at gmail.com > - xiefp88 at sina.com > - liuyamin at fiberhome.com > - lipan7195 at fiberhome.com > - fungi at yuggoth.org > - curtis at serverascode.com > - iwienand at redhat.com > - erich.cordoba.malibran at intel.com > - li.xiaoli at 99cloud.net > - zhang.kunpeng at 99cloud.net > - dtroyer at gmail.com > > flock-services > > - tyler.smith at windriver.com > - david.sullivan at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - jaegerandi at gmail.com > - haochuan.z.chen at intel.com > - dtroyer at gmail.com > - teresa.ho at windriver.com > - junbo85.li at gmail.com > - ovidiu.poncea at windriver.com > - yan.chen at intel.com > - sgw at linux.intel.com > - steven.webster at windriver.com > - zhipengs.liu at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - john.kung at windriver.com > - wzj334965317 at outlook.com > - tao.liu at windriver.com > - stefan.dinescu at windriver.com > - wei.zhou at windriver.com > - James.Gauld at windriver.com > - angie.wang at windriver.com > - guozhen.she at intel.com > - bin.qian at windriver.com > - zqhsh527 at 163.com > - andy.ning at windriver.com > - mingyuan.qi at intel.com > - xiefp88 at sina.com > - daniel.badea at windriver.com > - chris.friesen at windriver.com > - elena.taivan at windriver.com > - jerry.sun at windriver.com > - marcela.a.rosales.jimenez at intel.com > - xbyan at fiberhome.com > - ran1.an at intel.com > - alex.kozyrev at windriver.com > - eric.macdonald at windriver.com > - matt.peters at windriver.com > - barton.wensley at windriver.com > - kevin.smith at windriver.com > - zhanglf01 at inspur.com > - lachlan.plant at windriver.com > - zhaowei7146 at fiberhome.com > - lvcy at fiberhome.com > - sxmatch1986 at gmail.com > - ma.lei at 99cloud.net > - lijunjie at cloudin.cn > - jason.mckenna at windriver.com > - srifenbark at gmail.com > - tee.ngo at windriver.com > - zhangzhaoshan at inspur.com > - zhaolong at inspur.com > - lihang0166 at fiberhome.com > > multios > > > > networking > > > > networking > > > > openstack_distro > > > > release > > > > security > > > > test > > - lihang0166 at fiberhome.com > - dtroyer at gmail.com > - erich.cordoba.malibran at intel.com > - yang.liu at windriver.com > - al.bailey at windriver.com > - juan.p.gomez at intel.com > - anujeyan.manokeran at windriver.com > - maria.yousaf at windriver.com > - peng.peng at windriver.com > - marvin.huang at windriver.com > > [0] https://etherpad.openstack.org/p/stx-status > > _______________________________________________ > 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 dtroyer at gmail.com Wed Oct 9 19:06:37 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 9 Oct 2019 14:06:37 -0500 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: References: <586E8B730EA0DA4A9D6A80A10E486BC007B01E81@ALA-MBD.corp.ad.wrs.com> <7F4B4ABE-C604-4C28-87DF-75290233FAF2@openstack.org> Message-ID: On Wed, Oct 9, 2019 at 1:46 PM Miller, Frank wrote: > The list of contributors for containers is incorrect as it is only listing contributors for the last month which was when these repos were split out from the flock repos. The algorithm should instead be to check all the files in these repos and then go back to the beginning of the project to see who make commits to those files. Can this be done? If the history of those files was preserved when they were extracted you would have all of that information in the new repos. It sounds like that is not the case, if so you would have to do the extraction again, this time preserving history to produce a repo that can then be used with the election tooling to get the contributors. dt -- Dean Troyer dtroyer at gmail.com From Don.Penney at windriver.com Wed Oct 9 19:08:25 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 9 Oct 2019 19:08:25 +0000 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: References: <586E8B730EA0DA4A9D6A80A10E486BC007B01E81@ALA-MBD.corp.ad.wrs.com> <7F4B4ABE-C604-4C28-87DF-75290233FAF2@openstack.org> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15957CA@ALA-MBD.corp.ad.wrs.com> The original list came from a gerrit query, not a git query. The git history was maintained -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Wednesday, October 09, 2019 3:07 PM To: Miller, Frank Cc: Ildiko Vancsa; starlingx-discuss at lists.starlingx.io; Jones, Bruce E; Zvonar, Bill Subject: Re: [Starlingx-discuss] Voters for PL/TL election... On Wed, Oct 9, 2019 at 1:46 PM Miller, Frank wrote: > The list of contributors for containers is incorrect as it is only listing contributors for the last month which was when these repos were split out from the flock repos. The algorithm should instead be to check all the files in these repos and then go back to the beginning of the project to see who make commits to those files. Can this be done? If the history of those files was preserved when they were extracted you would have all of that information in the new repos. It sounds like that is not the case, if so you would have to do the extraction again, this time preserving history to produce a repo that can then be used with the election tooling to get the contributors. 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 dtroyer at gmail.com Wed Oct 9 19:14:12 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 9 Oct 2019 14:14:12 -0500 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15957CA@ALA-MBD.corp.ad.wrs.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B01E81@ALA-MBD.corp.ad.wrs.com> <7F4B4ABE-C604-4C28-87DF-75290233FAF2@openstack.org> <6703202FD9FDFF4A8DA9ACF104AE129FC15957CA@ALA-MBD.corp.ad.wrs.com> Message-ID: On Wed, Oct 9, 2019 at 2:08 PM Penney, Don wrote: > The original list came from a gerrit query, not a git query. The git history was maintained I thought it was all there. Yup, Gerrit doesn't have that, only the repo itself does. Thanks Don dt -- Dean Troyer dtroyer at gmail.com From fungi at yuggoth.org Wed Oct 9 19:17:39 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 9 Oct 2019 19:17:39 +0000 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15957CA@ALA-MBD.corp.ad.wrs.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B01E81@ALA-MBD.corp.ad.wrs.com> <7F4B4ABE-C604-4C28-87DF-75290233FAF2@openstack.org> <6703202FD9FDFF4A8DA9ACF104AE129FC15957CA@ALA-MBD.corp.ad.wrs.com> Message-ID: <20191009191738.x2lqhxdp34sk7ycm@yuggoth.org> On 2019-10-09 19:08:25 +0000 (+0000), Penney, Don wrote: > The original list came from a gerrit query, not a git query. The > git history was maintained [...] Right, the base contributor data is obtained by checking what repositories a change originally merged in, not what forks of a repository those corresponding commits may appear in. This has come up in the past for OpenStack, for example when nova-baremetal driver work was reimported from the Ironic team, and so the Nova team identified contributors to the files which they imported and listed them as extra-atcs entries in governance to reflect that contribution. If this is being used to determine per-team electoral rolls for team-specific leadership elections and seat eligibility, then it's probably a good idea to identify code you've imported from other teams' repositories and credit the contributors as extra-atcs entries in the importing team. If on the other hand this is all in service of generating a single StarlingX-wide electorate then it's probably not so necessary, as those contributions are still reflected in their original teams anyway. -- 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 bruce.e.jones at intel.com Wed Oct 9 20:29:42 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 9 Oct 2019 20:29:42 +0000 Subject: [Starlingx-discuss] Distro.openstack - Confirming contributor list Message-ID: <9A85D2917C58154C960D95352B22818BDFBE52E9@fmsmsx121.amr.corp.intel.com> If you have not contributed to the Distro.openstack project in the last year, you can ignore this message. If you have contributed and your name is not on the list below, please reply to me with a brief reminder of your contribution(s) so I can add you to the Electorate list for the TL and PL election. These contributions can include check-ins to a StarlingX repository and also check-ins to upstream repos on behalf of StarlingX. I know there are several people e.g. the 99Cloud folks are missing from this list. Brucej bruce.e.jones at Intel.com kailun.qin at intel.com Allain.legacy at windriver.com chenjie.xu at intel.com liang.a.fang at intel.com jack.ding at windriver.com louie.kwan at windriver.com qi.ni at intel.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.l.tullis at intel.com Wed Oct 9 22:10:39 2019 From: michael.l.tullis at intel.com (Tullis, Michael L) Date: Wed, 9 Oct 2019 22:10:39 +0000 Subject: [Starlingx-discuss] [docs][meetings] docs team meeting minutes 2019-10-09 Message-ID: <3808363B39586544A6839C76CF81445EA1BF425F@ORSMSX104.amr.corp.intel.com> Join us if you have interest in StarlingX docs! We meet Wednesdays, and call logistics are here: https://wiki.openstack.org/wiki/Starlingx/Meetings. Our etherpad is here: https://etherpad.openstack.org/p/stx-documentation. -- Mike Current agenda and notes 2019-10-09 * Mike -- upcoming elections -- * Need to update the team list at https://opendev.org/openstack/governance/src/commit/69d2ef8c1c79323a3d9eb0b1f7d741cef3d2c59f/reference/projects.yaml#L651-L795 * Those in the list above will elect the doc team PL, which is the role Mike is playing now. Any and all are invited to self-nominate for the job for the upcoming election! Deadline is 10/13. * The self-nomination process is described here: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006415.html * What happens if nobody self-nominates? * All -- reviews in progress and recent merges -- * See summary at https://review.opendev.org/#/q/project:starlingx/docs. * Recent merges. Great job team! * https://review.opendev.org/#/c/686465/ -- Fix commands in section Configure controller-1 -- Closes-Bug: #1844656 -- MERGED * https://review.opendev.org/#/c/686490/ -- Add content to Access OpenStack doc -- Closes-Bug: #1837931 -- MERGED * https://review.opendev.org/#/c/686851/ -- Remove never ending while loops from R2 install guides -- MERGED * https://review.opendev.org/#/c/687170/ -- Initial setup for R3 docs -- MERGED * https://review.opendev.org/#/c/687431/ -- Minor wording updates for clarity capturing feedback from Bill Zvonar after he installed -- MERGED -- a follow-on PR is in progress to capture a few additional comments from Greg * We have 2 open: * https://review.opendev.org/#/c/687627/ -- Minor editorial revisions (R2, R3 install guides) -- follow-on to https://review.opendev.org/#/c/687431/ above. * https://review.opendev.org/#/c/684820/ -- Introduction editorial updates -- This is Mary's sandbox for Gerrit familiarity and is set to workflow -1 on purpose. No urgency. * Abraham and all -- bug status -- https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs * Only one bug is open, and it's low-priority! We've closed several higher priority bugs recently. * https://bugs.launchpad.net/starlingx/+bug/1835207 -- Abraham will ask for help in the community meeting to get this closed. * Kris -- validate structure and plans for new config guide -- * Let's walk through this -- https://docs.google.com/document/d/1LsRk_h8-35QjtmDqjhaY_C1fDtC71S673bq1wVSKtC0 * Outcome of this discussion should be a good idea of what should go into the new config guide and what the landing page will look like. * Kris will follow up with Greg on some open questions. * Mike -- triage with intent to create new R3 stories (or update existing stories) as needed -- * A recent code change will impact R3 bare metal use cases (and possibly others). See https://drive.google.com/file/d/1pic5wr_69fJb94-o3JM7U2xKMJ0HpGJZ for details. Kris will create a PR. * Change to Ansible Docker registry keys -- https://drive.google.com/file/d/1surBx44zzN3P3D13SUdc9m8tKDVQdAK2. Should go into config guide. Mike will create a subtask. * New back up and restore feature -- https://drive.google.com/file/d/15fsxLL-Xw2a5hftJrN6_Bboi7Q1kPo0_. Should go into what may be a new admin/maintenance guide. Mike create story. * This change to "manager.py" looks like a code change, not a doc issue. See https://storyboard.openstack.org/#!/story/2004707. Remove stx.docs tag? YES * https://storyboard.openstack.org/#!/story/2004601 -- Change to conf.py suggested in https://review.opendev.org/#/c/624848/. Added +1. Tools repo. * https://drive.google.com/file/d/1jDQOR0Nprjd4NPhxy-vPWFxb3YUrWZs8 -- STX project versioning -- lower priority but tagged now for stx.3.0. Mostly done. * Bruce -- StarlingX-in-a-box -- We have two vectors on this -- * Erich's contribution -- https://drive.google.com/file/d/19127DWvfrSvpd9QNjHlbNX2-OEbruxKx * Calsoft's contribution -- http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/006316.html -- We believe this will go into our StarlingX-in-a-box topic as captured in https://storyboard.openstack.org/#!/story/2006622. Bruce has volunteered to help Sai with the contribution. * Abraham -- help from the Q/A team -- * Distributed Cloud -- https://storyboard.openstack.org/#!/story/2005181 * GPU Kubernetes Plugin * TSN -- subtask 36405 in https://storyboard.openstack.org/#!/story/2006289 * Redfish * Infrastructure and cluster Action required (AR) summary Completed ARs are archived here: https://etherpad.openstack.org/p/stx-documentation-files-003 * -- -- * 2019-05-15 -- Abraham -- Review these code and terminology changes impacting user docs -- https://drive.google.com/file/d/1sCB-lrWhDIJLNAGWBt7wJ1_JxY21m71p -- and report back on specific actions required. * 2019-10-02 -- Abraham -- Ask for help in the community meeting to get https://bugs.launchpad.net/starlingx/+bug/1835207 closed. * 2019-10-02 -- Kris and Mary -- Update the contributor guide at https://docs.starlingx.io/contributor/doc_contribute_guide.html to reflect our current doc schema. * 2019-10-09 -- Kris -- Follow up with Greg to close open questions as called out in https://docs.google.com/document/d/1LsRk_h8-35QjtmDqjhaY_C1fDtC71S673bq1wVSKtC0. * 2019-10-09 -- Kris -- Create a one-line PR for this change -- https://drive.google.com/file/d/1pic5wr_69fJb94-o3JM7U2xKMJ0HpGJZ. -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Wed Oct 9 23:05:03 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Wed, 9 Oct 2019 23:05:03 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191009 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006445.html Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wang.ya at 99cloud.net Thu Oct 10 03:01:43 2019 From: wang.ya at 99cloud.net (wang.ya) Date: Thu, 10 Oct 2019 11:01:43 +0800 Subject: [Starlingx-discuss] Distro.openstack - Confirming contributor list Message-ID: <7E4C9398-DC1C-43F3-838D-C0DDD4C6C076@99cloud.net> Hi, Bruce: Here is the list from 99Cloud :) wang.ya at 99cloud.net zhu.boxiang at 99cloud.net From: on behalf of "Jones, Bruce E" Date: Thursday, October 10, 2019 at 4:30 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Distro.openstack - Confirming contributor list If you have not contributed to the Distro.openstack project in the last year, you can ignore this message. If you have contributed and your name is not on the list below, please reply to me with a brief reminder of your contribution(s) so I can add you to the Electorate list for the TL and PL election. These contributions can include check-ins to a StarlingX repository and also check-ins to upstream repos on behalf of StarlingX. I know there are several people e.g. the 99Cloud folks are missing from this list. Brucej bruce.e.jones at Intel.com kailun.qin at intel.com Allain.legacy at windriver.com chenjie.xu at intel.com liang.a.fang at intel.com jack.ding at windriver.com louie.kwan at windriver.com qi.ni at intel.com _______________________________________________ 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 zhang.kunpeng at 99cloud.net Thu Oct 10 03:35:04 2019 From: zhang.kunpeng at 99cloud.net (=?UTF-8?B?5byg6bKy6bmP?=) Date: Thu, 10 Oct 2019 11:35:04 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?Distro=2Eopenstack_-_Confirming_con?= =?utf-8?q?tributor_list?= In-Reply-To: <7E4C9398-DC1C-43F3-838D-C0DDD4C6C076@99cloud.net> Message-ID: +1 zhang.kunpeng at 99cloud.net for https://bugs.launchpad.net/starlingx/+bug/1837232 发件人:"wang.ya" 发送日期:2019-10-10 11:01:43 收件人:"Jones, Bruce E" ,"starlingx-discuss at lists.starlingx.io" 主题:Re: [Starlingx-discuss] Distro.openstack - Confirming contributor list Hi, Bruce: Here is the list from 99Cloud :) wang.ya at 99cloud.net zhu.boxiang at 99cloud.net From: on behalf of "Jones, Bruce E" Date: Thursday, October 10, 2019 at 4:30 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Distro.openstack - Confirming contributor list If you have not contributed to the Distro.openstack project in the last year, you can ignore this message. If you have contributed and your name is not on the list below, please reply to me with a brief reminder of your contribution(s) so I can add you to the Electorate list for the TL and PL election. These contributions can include check-ins to a StarlingX repository and also check-ins to upstream repos on behalf of StarlingX. I know there are several people e.g. the 99Cloud folks are missing from this list. Brucej bruce.e.jones at Intel.com kailun.qin at intel.com Allain.legacy at windriver.com chenjie.xu at intel.com liang.a.fang at intel.com jack.ding at windriver.com louie.kwan at windriver.com qi.ni at intel.com _______________________________________________ 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 cristopher.j.lemus.contreras at intel.com Thu Oct 10 08:06:51 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Thu, 10 Oct 2019 03:06:51 -0500 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: List of docker images required for "platform-integ-apps": BUILD_ID="20191010T013559Z" rabbitmq:3.7-management k8s.gcr.io/kube-apiserver:v1.16.0 k8s.gcr.io/kube-proxy:v1.16.0 k8s.gcr.io/kube-controller-manager:v1.16.0 k8s.gcr.io/kube-scheduler:v1.16.0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From Volker.Hoesslin at swsn.de Thu Oct 10 09:38:03 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Thu, 10 Oct 2019 09:38:03 +0000 Subject: [Starlingx-discuss] move storage node in replication group In-Reply-To: References: , , Message-ID: hi, is this command also valid for stx2.0 ? > I think the "system" command for it should be: > system storage-backend-add ceph -s cinder,glance,swift,nova replication=3 --confirmed volker ________________________________ Von: Dinescu, Stefan [Stefan.Dinescu at windriver.com] Gesendet: Dienstag, 30. Oktober 2018 13:02 An: von Hoesslin, Volker; 'starlingx-discuss at lists.starlingx.io' Betreff: RE: move storage node in replication group Check the "capabilities" parameter for adding the ceph backend [1]. you need to set replication to 3 (min_replication should automatically be set to 2). I think the "system" command for it should be: system storage-backend-add ceph -s cinder,glance,swift,nova replication=3 --confirmed The help of the command states: $ system help storage-backend-add usage: system storage-backend-add [-s ] [-n ] [-t ] [-c ] [--confirmed] [--ceph-mon-gib ] [ [ ...]] Replication should be given as a . Storage nodes inside a replication group all share the same (replicated) data. So if one node fails for any reason, the data is still being served by the remaining nodes. As, I said, nodes are assigned automatically to a group based on replication, so you cannot manually assign each node to a different group. It is recommended that your number of storage nodes be a multiple of your replication factor. So for replication 2, you should use 2,4,6.... storage nodes and for replication 3 you should use 3,6,9... storage nodes. [1]: https://docs.starlingx.io/api-ref/stx-config/api-ref-sysinv-v1-config.html?expanded=add-a-ceph-storage-backend-detail#add-a-ceph-storage-backend ________________________________ From: von Hoesslin, Volker [Volker.Hoesslin at swsn.de] Sent: Tuesday, October 30, 2018 1:34 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] move storage node in replication group Ok, I understand. how can I define this when creating a storage node? neither cli nor gui can I find corresponding options. how are the "replication-groups" to be understood? is it desirable to put all three storage-nodes into one group or should each storage-node have its own group? greez & thx, volker... Von: Dinescu, Stefan [mailto:Stefan.Dinescu at windriver.com] Gesendet: Dienstag, 30. Oktober 2018 10:48 An: von Hoesslin, Volker; 'starlingx-discuss at lists.starlingx.io' Betreff: RE: move storage node in replication group Hello, The default replication of ceph is 2. Nodes are assigned to each group automatically and cannot be manually changed. if you want replication 3, you need you set that before installing storage nodes. ________________________________ From: von Hoesslin, Volker [Volker.Hoesslin at swsn.de] Sent: Monday, October 29, 2018 5:43 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] move storage node in replication group hello, i have 3 storage nodes and after provisioning nodes 1+2 are in replication group 0 and node 3 are in replication group 1?! how can i move node 3 to group 0? greetings, volker -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jolliffe at windriver.com Thu Oct 10 15:26:11 2019 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Thu, 10 Oct 2019 15:26:11 +0000 Subject: [Starlingx-discuss] [TSC] Meeting minutes - 10/10 Message-ID: <81FD9CA3-90AA-4EF0-8C5E-687A2D03FDD6@windriver.com> 10/10/2019: Election update Need to capture contributors to projects besides what we can extract from Gerrit Some projects don't have repositories assigned In some case there might be other contributors than those who committed code or documentation to the project Nomination period is now open - closes UTC evening Sunday - see election site PL and TL elections - contributors who are electing in case of a need for a formal election 5 projects don't have repos at this point or people who haven't made a commit but are making contributions. Making additions to recognize ATC's who weren't picked up by the automation How to automate - for projects without repos? Make this easier next time around. Other topics: Summit - who's going Saul, Ian, Shuquan, Brent, others? Project onboarding - yes - need someone to present Project update - Shuquan - anyone else to present. Saul. PTG - agenda and plans - 1.5 days - we are looking for input from the community for the agenda, please see what we have already below. Test - and test evolution Growing the community - and interactions Plans for Release 4.0 Documentation Cross project - Kata Containers others Working sessions - contributor guides, workflows, start on community calls other hands on items - test frameworks, coding something? From dominig.arfoll at fridu.net Thu Oct 10 17:25:22 2019 From: dominig.arfoll at fridu.net (Dominig ar Foll (Intel Open Source)) Date: Thu, 10 Oct 2019 19:25:22 +0200 Subject: [Starlingx-discuss] MultiOS: Short cut to create compliant logical volumes to ease StartlingX testing Message-ID: <4c81fae9-db5f-52bd-b563-838213e46cc0@fridu.net> Hello, I have created a small script that can be used to recreate the set of logical volumes expected by StartlingX. It can be handy to manually create compatible LV environment. WARNING: Please note that it will wipe out all pointed devices. Size repartition is done in automatically % of the available space following CentOS provided example. It might not be realistic is a real environment but still good enough for test. Enjoy. Dominig --------- syntax ------------------- sudo sh create-lvm.sh -f -c /dev/sda1,/dev/sda2 -n /dev/sda3,/dev/sda4^C dominig at dominig-t480:~/starlingx/scripts> sudo sh create-lvm.sh -h Creates multiple Logical Volume as required by StartlinX project WARNING: it will wipe out ALL devices pointed by the command Usage: create-lvm.sh [-v] [-f] [-t fstype] -c Device1[,Device2] -n DeviceA[,DeviceB]        -v: Verbose debug        -f: Format logical vomumes after creation        -t fstype change the default fstype from btrfs        -c harddrive device comma seprated list (no space) to be used for cgts logical drive        -n harddrive device comma seprated list (no space) to be used for nova logical drive NOTE: Requires to be run as root and all targetted devices to be unmounted ex:    sudo sh create-lvm.sh -v -c /dev/sda1 -n /dev/sda3    sudo sh create-lvm.sh -f -t ext4 -c /dev/sda1,/dev/sda2 -n /dev/sda3,/dev/sda4 -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre -------------- next part -------------- A non-text attachment was scrubbed... Name: create-lvm.sh Type: application/x-shellscript Size: 8716 bytes Desc: not available URL: From Frank.Miller at windriver.com Thu Oct 10 18:53:51 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 10 Oct 2019 18:53:51 +0000 Subject: [Starlingx-discuss] Distro.openstack - Confirming contributor list In-Reply-To: <9A85D2917C58154C960D95352B22818BDFBE52E9@fmsmsx121.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BDFBE52E9@fmsmsx121.amr.corp.intel.com> Message-ID: Bruce: I also think these folks contributed: * Gerry.kopec at windriver.com (involved in testing and finding issues with Artom's numa awareness changes; consult to 99cloud team as part of patch elimination) * Tyler.smith at windriver.com (involved in StarlingX upversion to stein for keystone, barbican, horizon) * Al.bailey at windriver.com (involved in moving StarlingX openstack clients to stein) * James.gauld at windriver.com (consult to Yong Li, others as part of patch elimination) * Chris.friesen at windriver.com (vTPM spec in nova as part of patch elimination) * Alex.kozyrev at windriver.com (Integrated barbican with StarlingX) * Dean.troyer at intel.com (lots of consult, managed the git repos, rebases, etc) * zhipengs.liu at intel.com (nova placement changes, PCI IRQ affinity commits as part of patch elimination, etc) Frank From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, October 09, 2019 4:30 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Distro.openstack - Confirming contributor list If you have not contributed to the Distro.openstack project in the last year, you can ignore this message. If you have contributed and your name is not on the list below, please reply to me with a brief reminder of your contribution(s) so I can add you to the Electorate list for the TL and PL election. These contributions can include check-ins to a StarlingX repository and also check-ins to upstream repos on behalf of StarlingX. I know there are several people e.g. the 99Cloud folks are missing from this list. Brucej bruce.e.jones at Intel.com kailun.qin at intel.com Allain.legacy at windriver.com chenjie.xu at intel.com liang.a.fang at intel.com jack.ding at windriver.com louie.kwan at windriver.com qi.ni at intel.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Oct 10 20:08:13 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 10 Oct 2019 20:08:13 +0000 Subject: [Starlingx-discuss] Distro.openstack - Confirming contributor list In-Reply-To: References: <9A85D2917C58154C960D95352B22818BDFBE52E9@fmsmsx121.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BDFBE6019@fmsmsx121.amr.corp.intel.com> Thank you, Frank! I think Brent should be on the list as well, for the leadership he provided in the patch elimination effort. I will post the review tomorrow AM. The current draft list is here: https://etherpad.openstack.org/p/stx-distro-openstack-meetings brucej From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Thursday, October 10, 2019 11:54 AM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: Distro.openstack - Confirming contributor list Bruce: I also think these folks contributed: * Gerry.kopec at windriver.com (involved in testing and finding issues with Artom's numa awareness changes; consult to 99cloud team as part of patch elimination) * Tyler.smith at windriver.com (involved in StarlingX upversion to stein for keystone, barbican, horizon) * Al.bailey at windriver.com (involved in moving StarlingX openstack clients to stein) * James.gauld at windriver.com (consult to Yong Li, others as part of patch elimination) * Chris.friesen at windriver.com (vTPM spec in nova as part of patch elimination) * Alex.kozyrev at windriver.com (Integrated barbican with StarlingX) * Dean.troyer at intel.com (lots of consult, managed the git repos, rebases, etc) * zhipengs.liu at intel.com (nova placement changes, PCI IRQ affinity commits as part of patch elimination, etc) Frank From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, October 09, 2019 4:30 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Distro.openstack - Confirming contributor list If you have not contributed to the Distro.openstack project in the last year, you can ignore this message. If you have contributed and your name is not on the list below, please reply to me with a brief reminder of your contribution(s) so I can add you to the Electorate list for the TL and PL election. These contributions can include check-ins to a StarlingX repository and also check-ins to upstream repos on behalf of StarlingX. I know there are several people e.g. the 99Cloud folks are missing from this list. Brucej bruce.e.jones at Intel.com kailun.qin at intel.com Allain.legacy at windriver.com chenjie.xu at intel.com liang.a.fang at intel.com jack.ding at windriver.com louie.kwan at windriver.com qi.ni at intel.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.l.tullis at intel.com Thu Oct 10 20:41:58 2019 From: michael.l.tullis at intel.com (Tullis, Michael L) Date: Thu, 10 Oct 2019 20:41:58 +0000 Subject: [Starlingx-discuss] [DOCS] New location of Ansible bootstrap playbook (bootstrap.yml) In-Reply-To: <3808363B39586544A6839C76CF81445EA1BDD54E@ORSMSX104.amr.corp.intel.com> References: <65F1E5C9D184934EB1576B5CCD6C643B2BC3187C@ALA-MBD.corp.ad.wrs.com> <3808363B39586544A6839C76CF81445EA1BDD54E@ORSMSX104.amr.corp.intel.com> Message-ID: <3808363B39586544A6839C76CF81445EA1BF4A1F@ORSMSX104.amr.corp.intel.com> This change is now merged for R3 docs: https://review.opendev.org/#/c/687689 Thx. -- Mike From: Tullis, Michael L Sent: Wednesday, September 18, 2019 3:59 PM To: Zhou, Wei ; starlingx-discuss at lists.starlingx.io Cc: Balaraj, Juanita Subject: Re: [Starlingx-discuss] [DOCS] New location of Ansible bootstrap playbook (bootstrap.yml) Thanks again. This is now https://storyboard.openstack.org/#!/story/2006576. We'll roll this change out to new docs versioned for R3 after our latest retrofitted changes for R2 merge. -- Mike From: Zhou, Wei > Sent: Wednesday, September 18, 2019 10:23 AM To: starlingx-discuss at lists.starlingx.io Cc: Balaraj, Juanita > Subject: [Starlingx-discuss] [DOCS] New location of Ansible bootstrap playbook (bootstrap.yml) Hi, My following commit is merged today. It restructures StarlingX ansible-playbooks repo. https://opendev.org/starlingx/ansible-playbooks/commit/6e6e564a4f5a92020f8220f95fe8e5fa5f27bc1c As a result, the deployment/installation guild (e.g. for AIO-SX https://docs.starlingx.io/deploy_install_guides/current/bare_metal_aio_simplex.html#bootstrap-system-on-controller-0) needs to be updated to address the new location of bootstrap playbook. The path for the bootstrap playbook (bootstrap.yml) is changed from /usr/share/ansible/stx-ansible/playbooks/bootstrap/bootstrap.yml to /usr/share/ansible/stx-ansible/playbooks/bootstrap.yml. Thanks, -Wei -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Thu Oct 10 22:25:27 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 10 Oct 2019 22:25:27 +0000 Subject: [Starlingx-discuss] [ Regression testing - stx3.0 ] Report for 10/10/2019 Message-ID: StarlingX 3.0 Release Status: ISO: BUILD_ID=" 20191006T230000Z" from (link) ---------------------------------------------------------------------- MANUAL EXECUTION ---------------------------------------------------------------------- Overall Results: Total = 230 Pass = 22 Fail = 0 Blocked = 0 Not Run = 207 Obsolete = 1 Deferred = 0 Total executed = 22 Pass Rate = 100% Formula used : Pass Rate = (pass * 100) / (pass + fail) --------------------------------------------------------------------------- AUTOMATED ROBOT - INTEL --------------------------------------------------------------------------- Overall Results: Total = 202 Pass = 0 Fail = 0 Blocked = 0 Not Run = 202 Obsolete = 0 Deferred = 0 Total executed = 0 Pass Rate = Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- AUTOMATED PYTEST - WR --------------------------------------------------------------------------- Overall Results: Total = 467 Pass = 0 Fail = 0 Blocked = 0 Not Run = 467 Obsolete = 0 Deferred = 0 Total executed = 0 Pass Rate = Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- BUGS --------------------------------------------------------------------------- For more detail of the tests: https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 Regards! Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Thu Oct 10 22:54:20 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 10 Oct 2019 22:54:20 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191010 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-10 (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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006466.html Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From hu.tianhao at 99cloud.net Fri Oct 11 01:30:36 2019 From: hu.tianhao at 99cloud.net (=?UTF-8?B?6IOh5aSp5piK?=) Date: Fri, 11 Oct 2019 09:30:36 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?How_to_add_magnum_service_in_Starli?= =?utf-8?q?ngx_R2=2E0?= Message-ID: Hi guys, I want to add magnum service in Starlingx R2.0. Can I change config of magnum in stx-openstack-1.0-17-centos-stable-latest.tgz file and apply the stx-openstack application? Or are there other method to add magnum service? Thanks Hu Tianhao -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Fri Oct 11 01:39:27 2019 From: yong.hu at intel.com (Yong Hu) Date: Fri, 11 Oct 2019 09:39:27 +0800 Subject: [Starlingx-discuss] How to add magnum service in Starlingx R2.0 In-Reply-To: References: Message-ID: I think it's a right way to make magnum run in containers same as other Openstack services do on StarlingX. In this sense, you can extend the current stx-openstack application. On 2019/10/11 9:30 AM, 胡天昊 wrote: > Hi guys, > > I want to add magnum service in Starlingx R2.0. Can I change config of > magnum in stx-openstack-1.0-17-centos-stable-latest.tgz file and apply > the stx-openstack application? > Or are there other method to add magnum service? > > Thanks > Hu Tianhao > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From hu.tianhao at 99cloud.net Fri Oct 11 01:44:22 2019 From: hu.tianhao at 99cloud.net (=?utf-8?B?6IOh5aSp5piK?=) Date: Fri, 11 Oct 2019 09:44:22 +0800 Subject: [Starlingx-discuss] How to add magnum service in Starlingx R2.0 In-Reply-To: References: Message-ID: <87EF1444-8472-4A0C-ACDE-C9D2ECBADCAB@99cloud.net> An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Fri Oct 11 07:54:27 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Fri, 11 Oct 2019 02:54:27 -0500 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <029d15$5jgi7q@orsmga008.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191011T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-apiserver:v1.16.0 k8s.gcr.io/kube-controller-manager:v1.16.0 k8s.gcr.io/kube-proxy:v1.16.0 k8s.gcr.io/kube-scheduler:v1.16.0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From zhipengs.liu at intel.com Fri Oct 11 12:42:42 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Fri, 11 Oct 2019 12:42:42 +0000 Subject: [Starlingx-discuss] About EB verification for openstack train upgrade Message-ID: <93814834B4855241994F290E959305C7530E161C@SHSMSX104.ccr.corp.intel.com> Hi Ada and Bruce, So far, I have finished openstack train upgrade and openstack-helm/helm-infra upgrade. Story: https://storyboard.openstack.org/#!/story/2006544 Basic deployment and VM creation/remove test pass in AIO setup! @Ada, Could you help to arrange sanity test with below EB, thanks! http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/290/outputs/ Current status summarized as below. 1) Openstack upgrade Finished 13 services upgrade, including nova, neutron, keystone, cinder, glance, placement, aodh, ironic, panko, barbican, ceilometer, heat, horizon. 2) Openstack-helm/helm-infra upgrade Upgrade openstack-helm to below version. 13 patches removed commit 82c72367c85ca94270f702661c7b984899c1ae38 //Date: Sat Sep 14 06:40:03 2019 +0000 Upgrade openstack-helm-infra to below version. 1 patch removed commit c9d6676bf9a5aceb311dc31dadd07cba6a3d6392 //Date: Mon Sep 16 17:15:12 2019 +0000 6 patches submitted for review, your comments are appreciated, thanks! https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ Thanks! zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Fri Oct 11 12:55:10 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 11 Oct 2019 14:55:10 +0200 Subject: [Starlingx-discuss] Marketing planning call overview slide deck Message-ID: <54A18B44-B5BB-487A-ACBF-7702992FDE49@gmail.com> Hi, It is a friendly reminder that we will have the next community marketing planning call next Wednesday (October 16). The agenda items include a discussion about the overview slide deck and overview diagrams as well as start planning for the release 3.0 communications. Anyone who is interested in participating you can find links to the slide deck alternatives as well as further details on previous discussions: https://etherpad.openstack.org/p/2019_StarlingX_Marketing_Plans Please add your thoughts and ideas to the etherpad so we can elaborate on them further on the call. Please let me know if you have any questions. Thanks and Best Regards, Ildikó From cindy.xie at intel.com Fri Oct 11 12:56:09 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Fri, 11 Oct 2019 12:56:09 +0000 Subject: [Starlingx-discuss] Distro.openstack - Confirming contributor list In-Reply-To: <9A85D2917C58154C960D95352B22818BDFBE6019@fmsmsx121.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BDFBE52E9@fmsmsx121.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BDFBE6019@fmsmsx121.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F360810FB@SHSMSX104.ccr.corp.intel.com> I propose the following people: Yan.chen at intel.com (Horizon) Yong.hu at intel.com (PL coverage) Bin.yang at intel.com (RabbitMQ config change) Yi.c.wang at intel.com (mariadb ingress) Thx. - cindy From: Jones, Bruce E Sent: Friday, October 11, 2019 4:08 AM To: Miller, Frank ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Distro.openstack - Confirming contributor list Thank you, Frank! I think Brent should be on the list as well, for the leadership he provided in the patch elimination effort. I will post the review tomorrow AM. The current draft list is here: https://etherpad.openstack.org/p/stx-distro-openstack-meetings brucej From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Thursday, October 10, 2019 11:54 AM To: Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: RE: Distro.openstack - Confirming contributor list Bruce: I also think these folks contributed: * Gerry.kopec at windriver.com (involved in testing and finding issues with Artom's numa awareness changes; consult to 99cloud team as part of patch elimination) * Tyler.smith at windriver.com (involved in StarlingX upversion to stein for keystone, barbican, horizon) * Al.bailey at windriver.com (involved in moving StarlingX openstack clients to stein) * James.gauld at windriver.com (consult to Yong Li, others as part of patch elimination) * Chris.friesen at windriver.com (vTPM spec in nova as part of patch elimination) * Alex.kozyrev at windriver.com (Integrated barbican with StarlingX) * Dean.troyer at intel.com (lots of consult, managed the git repos, rebases, etc) * zhipengs.liu at intel.com (nova placement changes, PCI IRQ affinity commits as part of patch elimination, etc) Frank From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, October 09, 2019 4:30 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Distro.openstack - Confirming contributor list If you have not contributed to the Distro.openstack project in the last year, you can ignore this message. If you have contributed and your name is not on the list below, please reply to me with a brief reminder of your contribution(s) so I can add you to the Electorate list for the TL and PL election. These contributions can include check-ins to a StarlingX repository and also check-ins to upstream repos on behalf of StarlingX. I know there are several people e.g. the 99Cloud folks are missing from this list. Brucej bruce.e.jones at Intel.com kailun.qin at intel.com Allain.legacy at windriver.com chenjie.xu at intel.com liang.a.fang at intel.com jack.ding at windriver.com louie.kwan at windriver.com qi.ni at intel.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Fri Oct 11 13:23:00 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 11 Oct 2019 15:23:00 +0200 Subject: [Starlingx-discuss] StarlingX TSC, PL, TL election - Nomination period started In-Reply-To: <8DA21B26-746F-4638-818D-E17FC56C1711@gmail.com> References: <8DA21B26-746F-4638-818D-E17FC56C1711@gmail.com> Message-ID: Hi StarlingX Community, It is a friendly reminder that the nomination period of the 2019 H2 StarlingX TSC/PL/TL election is open until __October 13, 2019 20:45 UTC__. If you would like to run for one of the 5 open TSC seats or project PL or TL position you can find details on how to submit your candidacy on the election web page[1]. In case you have any questions please respond to this thread or reach out to the election officials[2]. Thank you, [1] https://docs.starlingx.io/election/#how-to-submit-a-candidacy [2] https://docs.starlingx.io/election/#election-officials > On 2019. Oct 6., at 22:45, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > Nominations for the 5 Technical Steering Committee positions and all PL/TL positions are now open and will remain open until __October 13, 2019 20:45 UTC__. > > All nominations must be submitted as a text file to the starlingx/election repository as explained on the election website[1]. > > Please note that the name of the file should match the email address in your Gerrit configuration. > > Candidates for the Technical Steering Committee Positions: Any contributing community member who is an individual member of the Foundation can propose their candidacy for an available, directly-elected TSC seat. > > Candidates for the Project Lead Positions: Any contributing community member who is an individual member of the Foundation can propose their candidacy for the project PL seat. > > Candidates for the Technical Lead Positions: Any contributing community member who is an individual member of the Foundation and is a core reviewer to the given project can propose their candidacy for the project TL seat. > > The election will be held from October 20, 2019 20:45 UTC through to October 27, 2019 20:45 UTC. > > The electorate of the TSC election are the community members that are also contributors for one of the official teams[2] or served in a leadership role (TSC, PL, TL) over the 12-month timeframe October 6, 2018 to October 6, 2019, as well as the contributors who are acknowledged by the TSC. > > The electorate of the PL/TL election are the community members that are contributors for the given official team[2] over the 12-month timeframe October 6, 2018 to October 6, 2019, as well as the contributors who are acknowledged by the TSC. > > Please see the website[3] for additional details about this election. > Please find below the timeline: > > TSC nomination starts @ October 6, 2019 20:45 UTC > TSC nomination ends @ October 13, 2019 20:45 UTC > PL/TL nomination starts @ October 6, 2019 20:45 UTC > PL/TL nomination ends @ October 13, 2019 20:45 UTC > > TSC campaigning starts @ October 13, 2019 20:45 UTC > TSC campaigning ends @ October 20, 2019 20:45 UTC > > TSC election starts @ October 20, 2019 20:45 UTC > TSC election ends @ October 27, 2019 20:45 UTC > PL/TL election starts @ October 20, 2019 20:45 UTC > PL/TL election ends @ October 27, 2019 20:45 UTC > > If you have any questions please be sure to either ask them on the mailing list or to the elections officials[4]. > > Thank you, > > [1] https://docs.starlingx.io/election/#how-to-submit-a-candidacy > [2] https://docs.starlingx.io/governance/reference/tsc/projects/index.html > [3] https://docs.starlingx.io/election/ > [4] https://docs.starlingx.io/election/#election-officials > > From Frank.Miller at windriver.com Fri Oct 11 13:54:32 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Fri, 11 Oct 2019 13:54:32 +0000 Subject: [Starlingx-discuss] Request update to containers contributor list (was RE: Voters for PL/TL election...) Message-ID: Ildiko: Can you add the people below listed in Don's email to the extra-atcs for the containers subproject? As Don indicates, the git query used took into account the history of the containers code since the repos were created last month by moving existing files from other repos into the new containers repos. Thank-you Frank -----Original Message----- From: Penney, Don Sent: Wednesday, October 09, 2019 3:06 PM To: Miller, Frank ; Ildiko Vancsa ; starlingx-discuss at lists.starlingx.io Cc: Jones, Bruce E ; Zvonar, Bill Subject: RE: [Starlingx-discuss] Voters for PL/TL election... A query of specific repos for "containers" in the master branch, of commits in a given date range, getting the Committer for the reviews: $ for d in containers helm-charts monitor-armada-app openstack-armada-app platform-armada-app ; do cd $d; git log --pretty=fuller --after="Oct 6 00:00:00 2018" --before="Oct 7 00:00:00 2019" |grep Commit: | sort -u |grep -v review at openstack.org ; cd ..; done | sed -r 's/.*<(.*)>/\1/' | sort -u -t'@' -k2,2 -k1,1 dtroyer at gmail.com austin.sun at intel.com bin.yang at intel.com cheng1.li at intel.com chenjie.xu at intel.com haochuan.z.chen at intel.com kailun.qin at intel.com mario.alfredo.c.arevalo at intel.com mingyuan.qi at intel.com ran1.an at intel.com shuicheng.lin at intel.com weifei.yu at intel.com yi.c.wang at intel.com yong.hu at intel.com zhipengs.liu at intel.com sgw at linux.intel.com al.bailey at windriver.com Al.Bailey at windriver.com alex.kozyrev at windriver.com angie.wang at windriver.com barton.wensley at windriver.com chris.friesen at windriver.com daniel.badea at windriver.com david.sullivan at windriver.com don.penney at windriver.com elena.taivan at windriver.com gerry.kopec at windriver.com Gerry.Kopec at windriver.com irina.mihai at windriver.com jason.mckenna at windriver.com jerry.sun at windriver.com john.kung at windriver.com joseph.richard at windriver.com kevin.smith at windriver.com kristine.bujold at windriver.com matt.peters at windriver.com ovidiu.poncea at windriver.com robert.church at windriver.com scott.little at windriver.com stefan.dinescu at windriver.com tao.liu at windriver.com teresa.ho at windriver.com tyler.smith at windriver.com -----Original Message----- From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Wednesday, October 09, 2019 2:45 PM To: Ildiko Vancsa; starlingx-discuss at lists.starlingx.io Cc: Jones, Bruce E; Zvonar, Bill Subject: Re: [Starlingx-discuss] Voters for PL/TL election... Bill/Ildiko: The list of contributors for containers is incorrect as it is only listing contributors for the last month which was when these repos were split out from the flock repos. The algorithm should instead be to check all the files in these repos and then go back to the beginning of the project to see who make commits to those files. Can this be done? Frank -----Original Message----- From: Ildiko Vancsa [mailto:ildiko at openstack.org] Sent: Wednesday, October 09, 2019 2:22 PM To: starlingx-discuss at lists.starlingx.io Cc: Jones, Bruce E ; Zvonar, Bill Subject: Re: [Starlingx-discuss] Voters for PL/TL election... Hi, I created patches to capture contributors to the projects where we cannot use the repositories to generate the data. I would like to ask PLs and TLs for MultiOS, Networking, OpenStack-Distro, Release and Security to check the list of names as well as contributors to these projects to check if the lists of names are correct: * MultiOS: https://review.opendev.org/#/c/687631/ * Networking: https://review.opendev.org/#/c/687630/ * OpenStack-Distro: https://review.opendev.org/#/c/687632/ * Release: https://review.opendev.org/#/c/687633/ * Security: https://review.opendev.org/#/c/687635/ Thanks, Ildikó > On 2019. Oct 9., at 19:56, Zvonar, Bill wrote: > > As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. > > The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. > > If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). > > Bill... > > build > > - don.penney at windriver.com > - scott.little at windriver.com > - dtroyer at gmail.com > - al.bailey at windriver.com > - tyler.smith at windriver.com > - daniel.badea at windriver.com > - sgw at linux.intel.com > - erich.cordoba.malibran at intel.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - tao.liu at windriver.com > - joseph.richard at windriver.com > - felipe.de.jesus.ruiz.garcia at intel.com > - angie.wang at windriver.com > - Kristine.Bujold at windriver.com > - jesus.ornelas.aguayo at intel.com > - lihaijing at fiberhome.com > - jason.mckenna at windriver.com > - zhangyangyang at unionpay.com > - jerry.sun at windriver.com > - alex.kozyrev at windriver.com > - steven.webster at windriver.com > - jaegerandi at gmail.com > - longx.li at intel.com > - john.kung at windriver.com > - maria.yousaf at windriver.com > - zhipengs.liu at intel.com > - lihang0166 at fiberhome.com > - zhiguox.zhang at intel.com > - bin.yang at intel.com > - iwienand at redhat.com > - marcela.a.rosales.jimenez at intel.com > - tee.ngo at windriver.com > - haochuan.z.chen at intel.com > - caoran at fiberhome.com > - zhang.kunpeng at 99cloud.net > - Paul-Emile.Element at windriver.com > > config > > - angie.wang at windriver.com > - tingjie.chen at intel.com > - kevin.smith at windriver.com > - ovidiu.poncea at windriver.com > - bin.qian at windriver.com > - joseph.richard at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - andy.ning at windriver.com > - david.sullivan at windriver.com > - daniel.badea at windriver.com > - zhipengs.liu at intel.com > - tao.liu at windriver.com > - haochuan.z.chen at intel.com > - lihang0166 at fiberhome.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - sgw at linux.intel.com > - teresa.ho at windriver.com > - eric.macdonald at windriver.com > - alex.kozyrev at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - tee.ngo at windriver.com > - tyler.smith at windriver.com > - bin.yang at intel.com > - john.kung at windriver.com > - jaegerandi at gmail.com > - mingyuan.qi at intel.com > - eric.barrett at windriver.com > - zhang.kunpeng at 99cloud.net > - wei.zhou at windriver.com > - steven.webster at windriver.com > - jerry.sun at windriver.com > - dtroyer at gmail.com > - barton.wensley at windriver.com > - matt.peters at windriver.com > - zhu.boxiang at 99cloud.net > - don.penney at windriver.com > - James.Gauld at windriver.com > - junbo85.li at gmail.com > - chris.friesen at windriver.com > - marcela.a.rosales.jimenez at intel.com > - cheng1.li at intel.com > - chenjie.xu at intel.com > - allain.legacy at windriver.com > - yan.chen at intel.com > - elena.taivan at windriver.com > - yizhoux.xu at intel.com > - iwienand at redhat.com > - irina.mihai at windriver.com > - wzj334965317 at outlook.com > - ma.lei at 99cloud.net > - eric.zhang at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - daniel.chavolla at windriver.com > - lachlan.plant at windriver.com > - srifenbark at gmail.com > - shoaib.nasir at windriver.com > - singh.surya64mnnit at gmail.com > > containers > > - al.bailey at windriver.com > - kevin.smith at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > > distcloud > > - andy.ning at windriver.com > - tyler.smith at windriver.com > - scott.little at windriver.com > - xiefp88 at sina.com > - jaegerandi at gmail.com > - dtroyer at gmail.com > - tao.liu at windriver.com > - don.penney at windriver.com > - al.bailey at windriver.com > - Kristine.Bujold at windriver.com > - cao.yuan at 99cloud.net > - wzj334965317 at outlook.com > - alex.kozyrev at windriver.com > - lachlan.plant at windriver.com > - junbo85.li at gmail.com > - srifenbark at gmail.com > - barton.wensley at windriver.com > > distro > > - al.bailey at windriver.com > - alex.kozyrev at windriver.com > - jerry.sun at windriver.com > - erich.cordoba.malibran at intel.com > - daniel.badea at windriver.com > - Kristine.Bujold at windriver.com > - scott.little at windriver.com > - jaegerandi at gmail.com > - bin.qian at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > - eric.macdonald at windriver.com > - john.kung at windriver.com > - andy.ning at windriver.com > - dtroyer at gmail.com > - stefan.dinescu at windriver.com > - bin.yang at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - barton.wensley at windriver.com > - junbo85.li at gmail.com > - angie.wang at windriver.com > - teresa.ho at windriver.com > - sgw at linux.intel.com > - tao.liu at windriver.com > - zhiguox.zhang at intel.com > - steven.webster at windriver.com > - chenjie.xu at intel.com > - James.Gauld at windriver.com > - longx.li at intel.com > - tyler.smith at windriver.com > - chenlx at fiberhome.com > - corvus at inaugust.com > - chris.friesen at windriver.com > - haochuan.z.chen at intel.com > - daniel.chavolla at windriver.com > - wei.zhou at windriver.com > - ovidiu.poncea at windriver.com > - joseph.richard at windriver.com > - jason.mckenna at windriver.com > - louie.kwan at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - tee.ngo at windriver.com > - ma.lei at 99cloud.net > > docs > > - bruce.e.jones at intel.com > - jaegerandi at gmail.com > - chenlx at fiberhome.com > - lihang0166 at fiberhome.com > - srifenbark at gmail.com > - xiefp88 at sina.com > - liuyamin at fiberhome.com > - lipan7195 at fiberhome.com > - fungi at yuggoth.org > - curtis at serverascode.com > - iwienand at redhat.com > - erich.cordoba.malibran at intel.com > - li.xiaoli at 99cloud.net > - zhang.kunpeng at 99cloud.net > - dtroyer at gmail.com > > flock-services > > - tyler.smith at windriver.com > - david.sullivan at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - jaegerandi at gmail.com > - haochuan.z.chen at intel.com > - dtroyer at gmail.com > - teresa.ho at windriver.com > - junbo85.li at gmail.com > - ovidiu.poncea at windriver.com > - yan.chen at intel.com > - sgw at linux.intel.com > - steven.webster at windriver.com > - zhipengs.liu at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - john.kung at windriver.com > - wzj334965317 at outlook.com > - tao.liu at windriver.com > - stefan.dinescu at windriver.com > - wei.zhou at windriver.com > - James.Gauld at windriver.com > - angie.wang at windriver.com > - guozhen.she at intel.com > - bin.qian at windriver.com > - zqhsh527 at 163.com > - andy.ning at windriver.com > - mingyuan.qi at intel.com > - xiefp88 at sina.com > - daniel.badea at windriver.com > - chris.friesen at windriver.com > - elena.taivan at windriver.com > - jerry.sun at windriver.com > - marcela.a.rosales.jimenez at intel.com > - xbyan at fiberhome.com > - ran1.an at intel.com > - alex.kozyrev at windriver.com > - eric.macdonald at windriver.com > - matt.peters at windriver.com > - barton.wensley at windriver.com > - kevin.smith at windriver.com > - zhanglf01 at inspur.com > - lachlan.plant at windriver.com > - zhaowei7146 at fiberhome.com > - lvcy at fiberhome.com > - sxmatch1986 at gmail.com > - ma.lei at 99cloud.net > - lijunjie at cloudin.cn > - jason.mckenna at windriver.com > - srifenbark at gmail.com > - tee.ngo at windriver.com > - zhangzhaoshan at inspur.com > - zhaolong at inspur.com > - lihang0166 at fiberhome.com > > multios > > > > networking > > > > networking > > > > openstack_distro > > > > release > > > > security > > > > test > > - lihang0166 at fiberhome.com > - dtroyer at gmail.com > - erich.cordoba.malibran at intel.com > - yang.liu at windriver.com > - al.bailey at windriver.com > - juan.p.gomez at intel.com > - anujeyan.manokeran at windriver.com > - maria.yousaf at windriver.com > - peng.peng at windriver.com > - marvin.huang at windriver.com > > [0] https://etherpad.openstack.org/p/stx-status > > _______________________________________________ > 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 Frank.Miller at windriver.com Fri Oct 11 13:58:08 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Fri, 11 Oct 2019 13:58:08 +0000 Subject: [Starlingx-discuss] StarlingX Bi-Weekly Containerization Meeting Message-ID: Note: We agreed to a new day and time for these meetings. For all who are working containerization features or LPs please join for our bi-weekly meeting. Agenda for October 15 meeting: 1. Review KATA containers feature with container Cores. Shuicheng to present feature overview and current status. - Shuicheng's commits: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) 2.Updates on other stx.3.0 container features for MS3 milestone: o 2004008: [Feature] Create HELM chart for Fault project [An Ran] - one commit needs a new approach - discussed in item #2 * Decision to be made about Horizon issue - do we keep FM containers enabled without Horizon for VM alarms? Or do we disable in stx.3.0 until issue can be addressed in stx.4.0? o 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] - require updated forecast o 2005514: QAT K8S device plugin support in StarlingX * Bruce: Code is out for review; Frank to follow-up with Cindy or feature primes for updated forecasts o 2005860: Upversion container components [Al Bailey] o 2004761: Integrate Backup & Restore with Containers [Ovidiu Poncea] 3. Update on stx.4.0 features: o 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC Call details * Zoom link: https://zoom.us/j/342730236 * 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 Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3622 bytes Desc: not available URL: From Frank.Miller at windriver.com Fri Oct 11 14:45:37 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Fri, 11 Oct 2019 14:45:37 +0000 Subject: [Starlingx-discuss] StarlingX Bi-Weekly Containerization Meeting Message-ID: Apologies, re-sending without etherpad formatting. Note: We agreed to a new day and time for these meetings. For all who are working containerization features or LPs please join for our bi-weekly meeting. Agenda for October 15 meeting: 1. Review KATA containers feature with container Cores. Shuicheng to present feature overview and current status. - Shuicheng's commits: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) 2. Updates on other stx.3.0 container features for MS3 milestone: - 2004008: [Feature] Create HELM chart for Fault project [An Ran] - one commit needs a new approach - discussed in item #2 - Decision to be made about Horizon issue - do we keep FM containers enabled without Horizon for VM alarms? Or do we disable in stx.3.0 until issue can be addressed in stx.4.0? - 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] - require updated forecast - 2005514: QAT K8S device plugin support in StarlingX - Bruce: Code is out for review; Frank to follow-up with Cindy or feature primes for updated forecasts - 2005860: Upversion container components [Al Bailey] - 2004761: Integrate Backup & Restore with Containers [Ovidiu Poncea] 3. Update on stx.4.0 features: - 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC Call details * Zoom link: https://zoom.us/j/342730236 * 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 Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3659 bytes Desc: not available URL: From ildiko at openstack.org Fri Oct 11 14:47:56 2019 From: ildiko at openstack.org (Ildiko Vancsa) Date: Fri, 11 Oct 2019 16:47:56 +0200 Subject: [Starlingx-discuss] Request update to containers contributor list (was RE: Voters for PL/TL election...) In-Reply-To: References: Message-ID: Hi Frank, Yes, I can help you with that. Please find the patch that adds the contributors to the projects.yaml file here: https://review.opendev.org/#/c/688136/ Thanks, Ildikó > On 2019. Oct 11., at 15:54, Miller, Frank wrote: > > Ildiko: > > Can you add the people below listed in Don's email to the extra-atcs for the containers subproject? As Don indicates, the git query used took into account the history of the containers code since the repos were created last month by moving existing files from other repos into the new containers repos. > > Thank-you > > Frank > > -----Original Message----- > From: Penney, Don > Sent: Wednesday, October 09, 2019 3:06 PM > To: Miller, Frank ; Ildiko Vancsa ; starlingx-discuss at lists.starlingx.io > Cc: Jones, Bruce E ; Zvonar, Bill > Subject: RE: [Starlingx-discuss] Voters for PL/TL election... > > A query of specific repos for "containers" in the master branch, of commits in a given date range, getting the Committer for the reviews: > > $ for d in containers helm-charts monitor-armada-app openstack-armada-app platform-armada-app ; do cd $d; git log --pretty=fuller --after="Oct 6 00:00:00 2018" --before="Oct 7 00:00:00 2019" |grep Commit: | sort -u |grep -v review at openstack.org ; cd ..; done | sed -r 's/.*<(.*)>/\1/' | sort -u -t'@' -k2,2 -k1,1 > > > dtroyer at gmail.com > austin.sun at intel.com > bin.yang at intel.com > cheng1.li at intel.com > chenjie.xu at intel.com > haochuan.z.chen at intel.com > kailun.qin at intel.com > mario.alfredo.c.arevalo at intel.com > mingyuan.qi at intel.com > ran1.an at intel.com > shuicheng.lin at intel.com > weifei.yu at intel.com > yi.c.wang at intel.com > yong.hu at intel.com > zhipengs.liu at intel.com > sgw at linux.intel.com > al.bailey at windriver.com > Al.Bailey at windriver.com > alex.kozyrev at windriver.com > angie.wang at windriver.com > barton.wensley at windriver.com > chris.friesen at windriver.com > daniel.badea at windriver.com > david.sullivan at windriver.com > don.penney at windriver.com > elena.taivan at windriver.com > gerry.kopec at windriver.com > Gerry.Kopec at windriver.com > irina.mihai at windriver.com > jason.mckenna at windriver.com > jerry.sun at windriver.com > john.kung at windriver.com > joseph.richard at windriver.com > kevin.smith at windriver.com > kristine.bujold at windriver.com > matt.peters at windriver.com > ovidiu.poncea at windriver.com > robert.church at windriver.com > scott.little at windriver.com > stefan.dinescu at windriver.com > tao.liu at windriver.com > teresa.ho at windriver.com > tyler.smith at windriver.com > > > > > > -----Original Message----- > From: Miller, Frank [mailto:Frank.Miller at windriver.com] > Sent: Wednesday, October 09, 2019 2:45 PM > To: Ildiko Vancsa; starlingx-discuss at lists.starlingx.io > Cc: Jones, Bruce E; Zvonar, Bill > Subject: Re: [Starlingx-discuss] Voters for PL/TL election... > > Bill/Ildiko: > > The list of contributors for containers is incorrect as it is only listing contributors for the last month which was when these repos were split out from the flock repos. The algorithm should instead be to check all the files in these repos and then go back to the beginning of the project to see who make commits to those files. Can this be done? > > Frank > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko at openstack.org] > Sent: Wednesday, October 09, 2019 2:22 PM > To: starlingx-discuss at lists.starlingx.io > Cc: Jones, Bruce E ; Zvonar, Bill > Subject: Re: [Starlingx-discuss] Voters for PL/TL election... > > Hi, > > I created patches to capture contributors to the projects where we cannot use the repositories to generate the data. > > I would like to ask PLs and TLs for MultiOS, Networking, OpenStack-Distro, Release and Security to check the list of names as well as contributors to these projects to check if the lists of names are correct: > > * MultiOS: https://review.opendev.org/#/c/687631/ > * Networking: https://review.opendev.org/#/c/687630/ > * OpenStack-Distro: https://review.opendev.org/#/c/687632/ > * Release: https://review.opendev.org/#/c/687633/ > * Security: https://review.opendev.org/#/c/687635/ > > Thanks, > Ildikó > > >> On 2019. Oct 9., at 19:56, Zvonar, Bill wrote: >> >> As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. >> >> The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. >> >> If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). >> >> Bill... >> >> build >> >> - don.penney at windriver.com >> - scott.little at windriver.com >> - dtroyer at gmail.com >> - al.bailey at windriver.com >> - tyler.smith at windriver.com >> - daniel.badea at windriver.com >> - sgw at linux.intel.com >> - erich.cordoba.malibran at intel.com >> - stefan.dinescu at windriver.com >> - ran1.an at intel.com >> - tao.liu at windriver.com >> - joseph.richard at windriver.com >> - felipe.de.jesus.ruiz.garcia at intel.com >> - angie.wang at windriver.com >> - Kristine.Bujold at windriver.com >> - jesus.ornelas.aguayo at intel.com >> - lihaijing at fiberhome.com >> - jason.mckenna at windriver.com >> - zhangyangyang at unionpay.com >> - jerry.sun at windriver.com >> - alex.kozyrev at windriver.com >> - steven.webster at windriver.com >> - jaegerandi at gmail.com >> - longx.li at intel.com >> - john.kung at windriver.com >> - maria.yousaf at windriver.com >> - zhipengs.liu at intel.com >> - lihang0166 at fiberhome.com >> - zhiguox.zhang at intel.com >> - bin.yang at intel.com >> - iwienand at redhat.com >> - marcela.a.rosales.jimenez at intel.com >> - tee.ngo at windriver.com >> - haochuan.z.chen at intel.com >> - caoran at fiberhome.com >> - zhang.kunpeng at 99cloud.net >> - Paul-Emile.Element at windriver.com >> >> config >> >> - angie.wang at windriver.com >> - tingjie.chen at intel.com >> - kevin.smith at windriver.com >> - ovidiu.poncea at windriver.com >> - bin.qian at windriver.com >> - joseph.richard at windriver.com >> - Kristine.Bujold at windriver.com >> - al.bailey at windriver.com >> - andy.ning at windriver.com >> - david.sullivan at windriver.com >> - daniel.badea at windriver.com >> - zhipengs.liu at intel.com >> - tao.liu at windriver.com >> - haochuan.z.chen at intel.com >> - lihang0166 at fiberhome.com >> - stefan.dinescu at windriver.com >> - ran1.an at intel.com >> - sgw at linux.intel.com >> - teresa.ho at windriver.com >> - eric.macdonald at windriver.com >> - alex.kozyrev at windriver.com >> - erich.cordoba.malibran at intel.com >> - scott.little at windriver.com >> - tee.ngo at windriver.com >> - tyler.smith at windriver.com >> - bin.yang at intel.com >> - john.kung at windriver.com >> - jaegerandi at gmail.com >> - mingyuan.qi at intel.com >> - eric.barrett at windriver.com >> - zhang.kunpeng at 99cloud.net >> - wei.zhou at windriver.com >> - steven.webster at windriver.com >> - jerry.sun at windriver.com >> - dtroyer at gmail.com >> - barton.wensley at windriver.com >> - matt.peters at windriver.com >> - zhu.boxiang at 99cloud.net >> - don.penney at windriver.com >> - James.Gauld at windriver.com >> - junbo85.li at gmail.com >> - chris.friesen at windriver.com >> - marcela.a.rosales.jimenez at intel.com >> - cheng1.li at intel.com >> - chenjie.xu at intel.com >> - allain.legacy at windriver.com >> - yan.chen at intel.com >> - elena.taivan at windriver.com >> - yizhoux.xu at intel.com >> - iwienand at redhat.com >> - irina.mihai at windriver.com >> - wzj334965317 at outlook.com >> - ma.lei at 99cloud.net >> - eric.zhang at windriver.com >> - Paul-Emile.Element at windriver.com >> - zhangyangyang at unionpay.com >> - daniel.chavolla at windriver.com >> - lachlan.plant at windriver.com >> - srifenbark at gmail.com >> - shoaib.nasir at windriver.com >> - singh.surya64mnnit at gmail.com >> >> containers >> >> - al.bailey at windriver.com >> - kevin.smith at windriver.com >> - zhipengs.liu at intel.com >> - ran1.an at intel.com >> >> distcloud >> >> - andy.ning at windriver.com >> - tyler.smith at windriver.com >> - scott.little at windriver.com >> - xiefp88 at sina.com >> - jaegerandi at gmail.com >> - dtroyer at gmail.com >> - tao.liu at windriver.com >> - don.penney at windriver.com >> - al.bailey at windriver.com >> - Kristine.Bujold at windriver.com >> - cao.yuan at 99cloud.net >> - wzj334965317 at outlook.com >> - alex.kozyrev at windriver.com >> - lachlan.plant at windriver.com >> - junbo85.li at gmail.com >> - srifenbark at gmail.com >> - barton.wensley at windriver.com >> >> distro >> >> - al.bailey at windriver.com >> - alex.kozyrev at windriver.com >> - jerry.sun at windriver.com >> - erich.cordoba.malibran at intel.com >> - daniel.badea at windriver.com >> - Kristine.Bujold at windriver.com >> - scott.little at windriver.com >> - jaegerandi at gmail.com >> - bin.qian at windriver.com >> - zhipengs.liu at intel.com >> - ran1.an at intel.com >> - eric.macdonald at windriver.com >> - john.kung at windriver.com >> - andy.ning at windriver.com >> - dtroyer at gmail.com >> - stefan.dinescu at windriver.com >> - bin.yang at intel.com >> - don.penney at windriver.com >> - eric.barrett at windriver.com >> - barton.wensley at windriver.com >> - junbo85.li at gmail.com >> - angie.wang at windriver.com >> - teresa.ho at windriver.com >> - sgw at linux.intel.com >> - tao.liu at windriver.com >> - zhiguox.zhang at intel.com >> - steven.webster at windriver.com >> - chenjie.xu at intel.com >> - James.Gauld at windriver.com >> - longx.li at intel.com >> - tyler.smith at windriver.com >> - chenlx at fiberhome.com >> - corvus at inaugust.com >> - chris.friesen at windriver.com >> - haochuan.z.chen at intel.com >> - daniel.chavolla at windriver.com >> - wei.zhou at windriver.com >> - ovidiu.poncea at windriver.com >> - joseph.richard at windriver.com >> - jason.mckenna at windriver.com >> - louie.kwan at windriver.com >> - Paul-Emile.Element at windriver.com >> - zhangyangyang at unionpay.com >> - tee.ngo at windriver.com >> - ma.lei at 99cloud.net >> >> docs >> >> - bruce.e.jones at intel.com >> - jaegerandi at gmail.com >> - chenlx at fiberhome.com >> - lihang0166 at fiberhome.com >> - srifenbark at gmail.com >> - xiefp88 at sina.com >> - liuyamin at fiberhome.com >> - lipan7195 at fiberhome.com >> - fungi at yuggoth.org >> - curtis at serverascode.com >> - iwienand at redhat.com >> - erich.cordoba.malibran at intel.com >> - li.xiaoli at 99cloud.net >> - zhang.kunpeng at 99cloud.net >> - dtroyer at gmail.com >> >> flock-services >> >> - tyler.smith at windriver.com >> - david.sullivan at windriver.com >> - Kristine.Bujold at windriver.com >> - al.bailey at windriver.com >> - jaegerandi at gmail.com >> - haochuan.z.chen at intel.com >> - dtroyer at gmail.com >> - teresa.ho at windriver.com >> - junbo85.li at gmail.com >> - ovidiu.poncea at windriver.com >> - yan.chen at intel.com >> - sgw at linux.intel.com >> - steven.webster at windriver.com >> - zhipengs.liu at intel.com >> - don.penney at windriver.com >> - eric.barrett at windriver.com >> - erich.cordoba.malibran at intel.com >> - scott.little at windriver.com >> - john.kung at windriver.com >> - wzj334965317 at outlook.com >> - tao.liu at windriver.com >> - stefan.dinescu at windriver.com >> - wei.zhou at windriver.com >> - James.Gauld at windriver.com >> - angie.wang at windriver.com >> - guozhen.she at intel.com >> - bin.qian at windriver.com >> - zqhsh527 at 163.com >> - andy.ning at windriver.com >> - mingyuan.qi at intel.com >> - xiefp88 at sina.com >> - daniel.badea at windriver.com >> - chris.friesen at windriver.com >> - elena.taivan at windriver.com >> - jerry.sun at windriver.com >> - marcela.a.rosales.jimenez at intel.com >> - xbyan at fiberhome.com >> - ran1.an at intel.com >> - alex.kozyrev at windriver.com >> - eric.macdonald at windriver.com >> - matt.peters at windriver.com >> - barton.wensley at windriver.com >> - kevin.smith at windriver.com >> - zhanglf01 at inspur.com >> - lachlan.plant at windriver.com >> - zhaowei7146 at fiberhome.com >> - lvcy at fiberhome.com >> - sxmatch1986 at gmail.com >> - ma.lei at 99cloud.net >> - lijunjie at cloudin.cn >> - jason.mckenna at windriver.com >> - srifenbark at gmail.com >> - tee.ngo at windriver.com >> - zhangzhaoshan at inspur.com >> - zhaolong at inspur.com >> - lihang0166 at fiberhome.com >> >> multios >> >> >> >> networking >> >> >> >> networking >> >> >> >> openstack_distro >> >> >> >> release >> >> >> >> security >> >> >> >> test >> >> - lihang0166 at fiberhome.com >> - dtroyer at gmail.com >> - erich.cordoba.malibran at intel.com >> - yang.liu at windriver.com >> - al.bailey at windriver.com >> - juan.p.gomez at intel.com >> - anujeyan.manokeran at windriver.com >> - maria.yousaf at windriver.com >> - peng.peng at windriver.com >> - marvin.huang at windriver.com >> >> [0] https://etherpad.openstack.org/p/stx-status >> >> _______________________________________________ >> 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 > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Fri Oct 11 18:49:57 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 11 Oct 2019 18:49:57 +0000 Subject: [Starlingx-discuss] About EB verification for openstack train upgrade In-Reply-To: <93814834B4855241994F290E959305C7530E161C@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C7530E161C@SHSMSX104.ccr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BDFBE8032@fmsmsx121.amr.corp.intel.com> Zhipeng - thank you! Community - please help review the changes below and thank you too! brucej From: Liu, ZhipengS Sent: Friday, October 11, 2019 5:43 AM To: Cabrales, Ada ; Jones, Bruce E Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Ada and Bruce, So far, I have finished openstack train upgrade and openstack-helm/helm-infra upgrade. Story: https://storyboard.openstack.org/#!/story/2006544 Basic deployment and VM creation/remove test pass in AIO setup! @Ada, Could you help to arrange sanity test with below EB, thanks! http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/290/outputs/ Current status summarized as below. 1) Openstack upgrade Finished 13 services upgrade, including nova, neutron, keystone, cinder, glance, placement, aodh, ironic, panko, barbican, ceilometer, heat, horizon. 2) Openstack-helm/helm-infra upgrade Upgrade openstack-helm to below version. 13 patches removed commit 82c72367c85ca94270f702661c7b984899c1ae38 //Date: Sat Sep 14 06:40:03 2019 +0000 Upgrade openstack-helm-infra to below version. 1 patch removed commit c9d6676bf9a5aceb311dc31dadd07cba6a3d6392 //Date: Mon Sep 16 17:15:12 2019 +0000 6 patches submitted for review, your comments are appreciated, thanks! https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ Thanks! zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Fri Oct 11 21:24:40 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Fri, 11 Oct 2019 21:24:40 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191011 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006478.html Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Sat Oct 12 08:01:43 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Sat, 12 Oct 2019 03:01:43 -0500 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: List of docker images required for "platform-integ-apps": BUILD_ID="20191012T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-apiserver:v1.16.0 k8s.gcr.io/kube-controller-manager:v1.16.0 k8s.gcr.io/kube-proxy:v1.16.0 k8s.gcr.io/kube-scheduler:v1.16.0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From cristopher.j.lemus.contreras at intel.com Sun Oct 13 07:55:06 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Sun, 13 Oct 2019 02:55:06 -0500 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: List of docker images required for "platform-integ-apps": BUILD_ID="20191013T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-apiserver:v1.16.0 k8s.gcr.io/kube-controller-manager:v1.16.0 k8s.gcr.io/kube-proxy:v1.16.0 k8s.gcr.io/kube-scheduler:v1.16.0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From ildiko.vancsa at gmail.com Sun Oct 13 20:47:52 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Sun, 13 Oct 2019 22:47:52 +0200 Subject: [Starlingx-discuss] StarlingX TSC/PL/TL election - Nomination period ended Message-ID: <2F005242-498C-4E7E-B7E4-546454764432@gmail.com> Hi StarlingX Community, I would like to inform you that the nomination period[1] for the StarlingX TSC/PL/TL election has ended. Thank you to all candidates who submitted their nominations into this round. The election officials[2] are still finalizing some details and will come back with further updates shortly. Thank you, [1] https://docs.starlingx.io/election/ [2] https://docs.starlingx.io/election/#election-officials From cristopher.j.lemus.contreras at intel.com Mon Oct 14 08:02:58 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Mon, 14 Oct 2019 03:02:58 -0500 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <8c37da$5t1hmq@orsmga003.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191013T230000Z" rabbitmq:3.7-management k8s.gcr.io/kube-apiserver:v1.16.0 k8s.gcr.io/kube-controller-manager:v1.16.0 k8s.gcr.io/kube-proxy:v1.16.0 k8s.gcr.io/kube-scheduler:v1.16.0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From ypd01018 at gmail.com Mon Oct 14 10:08:46 2019 From: ypd01018 at gmail.com (=?UTF-8?B?7Jy87JWEP+ycvOyeiT8=?=) Date: Mon, 14 Oct 2019 19:08:46 +0900 Subject: [Starlingx-discuss] Is there a way to use Raspberrypi as a worker node? Message-ID: I want to use RaspberryPi as a worker node in StarlingX. Can I know what I'm going to do? -------------- next part -------------- An HTML attachment was scrubbed... URL: From saichandu.behara at calsoftinc.com Mon Oct 14 11:15:19 2019 From: saichandu.behara at calsoftinc.com (Saichandu Behara) Date: Mon, 14 Oct 2019 16:45:19 +0530 Subject: [Starlingx-discuss] Calsoft's Contribution- StarlingX All-in-one EdgeX Deployment Message-ID: Hello All, The deployment of EdgeX in StarlingX all-in-one Simplex is done successfully. But we faced some challenges during whole process. Thus, to ease the process for a newbie, we have created ready-to-use qcow2 images. One can simply use this image to deploy the VM /(containing StarlingX with //K8//S and EdgeX//)/. Below are the links for StarlingX_all-in-one_Edgex setup Document and Image link. Setup Document: https://drive.google.com/open?id=1j0IBwKiwwD1Vju9_QltFo1oItMIa41x3 Image Link: https://drive.google.com/open?id=1ntQSILp4rg-L_CMQPLCPsvtYdAmQFHFp This is our very first step as contribution to this community and we would like to add more in future. Please let us know where can we upload these images and documents. -- Thanks & Regards Sai Chandu Behara -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Mon Oct 14 13:01:48 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 14 Oct 2019 13:01:48 +0000 Subject: [Starlingx-discuss] Calsoft's Contribution- StarlingX All-in-one EdgeX Deployment In-Reply-To: References: Message-ID: <2FD5DDB5A04D264C80D42CA35194914F36085072@SHSMSX104.ccr.corp.intel.com> Thanks Behara! Really appreciate to have EdgeX deployment steps documented. It will be nice if the changes can be updated on docs.starlingx.io. Please see the contribution guide here: https://docs.starlingx.io/contributor/doc_contribute_guide.html again, thanks very much for the effort! Cindy Xie IAGS [StarlingX] From: Saichandu Behara Sent: Monday, October 14, 2019 7:15 PM To: Bill.Zvonar at windriver.com; starlingx-discuss at lists.starlingx.io; Pavan Gupta Subject: [Starlingx-discuss] Calsoft's Contribution- StarlingX All-in-one EdgeX Deployment Hello All, The deployment of EdgeX in StarlingX all-in-one Simplex is done successfully. But we faced some challenges during whole process. Thus, to ease the process for a newbie, we have created ready-to-use qcow2 images. One can simply use this image to deploy the VM (containing StarlingX with K8S and EdgeX). Below are the links for StarlingX_all-in-one_Edgex setup Document and Image link. Setup Document: https://drive.google.com/open?id=1j0IBwKiwwD1Vju9_QltFo1oItMIa41x3 Image Link: https://drive.google.com/open?id=1ntQSILp4rg-L_CMQPLCPsvtYdAmQFHFp This is our very first step as contribution to this community and we would like to add more in future. Please let us know where can we upload these images and documents. -- Thanks & Regards Sai Chandu Behara -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 11582 bytes Desc: image002.png URL: From bruce.e.jones at intel.com Mon Oct 14 14:08:20 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 14 Oct 2019 14:08:20 +0000 Subject: [Starlingx-discuss] Is there a way to use Raspberrypi as a worker node? In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BDFBF13C9@fmsmsx123.amr.corp.intel.com> This is a capability that was demo’d at a conference recently but is not currently supported by the project. It’s something we’d like to do, long term. brucej From: 으아?으잉? [mailto:ypd01018 at gmail.com] Sent: Monday, October 14, 2019 3:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Is there a way to use Raspberrypi as a worker node? I want to use RaspberryPi as a worker node in StarlingX. Can I know what I'm going to do? -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Mon Oct 14 22:34:08 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Mon, 14 Oct 2019 22:34:08 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191014 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-14 (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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006492.html Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Mon Oct 14 22:35:47 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Mon, 14 Oct 2019 22:35:47 +0000 Subject: [Starlingx-discuss] [ Test ] Meeting agenda for 10/15 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CEF818A@FMSMSX114.amr.corp.intel.com> Agenda for 10/15 1. Sanity status 2. stx.3.0 testing updates Feature testing Distributed cloud - Yang Backup and restore - Yang Fault Containerization - Fer Upversion to train - JC GPU for K8 - Richo QAT for K8 - Richo Redfish - Cristopher Infra & Cluster monitoring - Yang Regression testing 3. stx.2.0 maintenance build 4. PL/TL elections - no candidates 5. Opens From bruce.e.jones at intel.com Mon Oct 14 23:21:34 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 14 Oct 2019 23:21:34 +0000 Subject: [Starlingx-discuss] Agenda for the Oct 15 2019 Distro.openstack meeting Message-ID: <9A85D2917C58154C960D95352B22818BDFBF6EAB@fmsmsx123.amr.corp.intel.com> * Train update status * Detection of a failed VM discussion * Election update -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Tue Oct 15 04:18:50 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 15 Oct 2019 04:18:50 +0000 Subject: [Starlingx-discuss] Please help to review STX Wiki for Time Sensitive Networking In-Reply-To: <4F6AACE4B0F173488D033B02A8BB5B7E7CEB5B1F@FMSMSX114.amr.corp.intel.com> References: <76647BD697F40748B1FA4F56DA02AA0B4D60F245@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F3601DBEE@SHSMSX104.ccr.corp.intel.com> <76647BD697F40748B1FA4F56DA02AA0B4D60F56B@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F3601DEA7@SHSMSX104.ccr.corp.intel.com> <4F6AACE4B0F173488D033B02A8BB5B7E7CEB5B1F@FMSMSX114.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F360861A0@SHSMSX104.ccr.corp.intel.com> Huifeng, In your wiki page: https://wiki.openstack.org/wiki/StarlingX/Networking/TSN, you're referring to "Deploying and Running TSN application in StarlingX Virtual Machine Workload Mode", do you have one example StarlingX TSN application that we can run? Cindy Xie IAGS [StarlingX] From: Cabrales, Ada Sent: Thursday, August 29, 2019 4:27 AM To: Xie, Cindy ; Le, Huifeng ; Rowsell, Brent ; Peters, Matt ; Guo, Ruijing ; Martinez Monroy, Elio Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Please help to review STX Wiki for Time Sensitive Networking Hello Cindy Yes, Elio will be the one. Thank you Ada From: Xie, Cindy Sent: Monday, August 26, 2019 2:42 AM To: Le, Huifeng >; Rowsell, Brent >; Peters, Matt >; Guo, Ruijing >; Cabrales, Ada > Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Please help to review STX Wiki for Time Sensitive Networking + Ada for feature testing. It's so nice to know that basic TSN support shall be already in 2.0 (even in 1.0). This is one of the critical features to support Industrial use case. As TSN spec got approved as 3.0 feature, I guess we may have to run full feature testing according to your wiki pages before we can claim the full support. @Ada, do you have engineer assigned to work w/ network team on this important feature? Thx. - cindy From: Le, Huifeng Sent: Monday, August 26, 2019 2:22 PM To: Xie, Cindy >; Rowsell, Brent >; Peters, Matt >; Guo, Ruijing > Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Please help to review STX Wiki for Time Sensitive Networking Cindy, There is no patches pending for merging. TSN PTP feature had already been supported in STX 1.0, and the wiki verified how other TSN features can be deployed in STX through PCI-Passthrough (But there may still be confliction with STX PTP feature, e.g. STX PTP feature requires Nic be available in host, but due to the Nic e.g. Intel i210 does not support SRIOV, in case it is pass-through into VM to support TSN application, it will be not available in host then the STX PTP feature will not work). I have no concern and Core/TSC team can review and determine how to claim if no more concern about the process, thanks much! Best Regards, Le, Huifeng From: Xie, Cindy Sent: Monday, August 26, 2019 12:49 PM To: Le, Huifeng >; Rowsell, Brent >; Peters, Matt >; Guo, Ruijing > Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Please help to review STX Wiki for Time Sensitive Networking Huifeng, Seems like TSN support is based on Nova PCI pass-through for i210 network adaptor. Do you have any Nova patches or StarlingX patches pending merge (and need cherry pick) to allow the procedures in wiki page to be successful? If there are no patches pending, can we claim that TSN feature is already supported in stx.2.0? Thx. - cindy From: Le, Huifeng [mailto:huifeng.le at intel.com] Sent: Sunday, August 25, 2019 2:39 PM To: Rowsell, Brent >; Peters, Matt >; Guo, Ruijing > Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Please help to review STX Wiki for Time Sensitive Networking Brent, Matt, Ruijing, As following up on story: [Feature] Time Sensitive Networking (https://storyboard.openstack.org/#!/story/2005516) and approved spec https://review.opendev.org/#/c/666768/, we had done the POC to deploy and run TSN application on STX environment, the detail process and learning are summarized at Wiki: https://wiki.openstack.org/wiki/StarlingX/Networking/TSN which can be served as deliverable of task "StarlingX user guide on how to deploy TSN in VM". Could you please help to review the Wiki and let me know if you have any comments. Thanks much! Best Regards, Le, Huifeng -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 11582 bytes Desc: image003.png URL: From huifeng.le at intel.com Tue Oct 15 04:55:05 2019 From: huifeng.le at intel.com (Le, Huifeng) Date: Tue, 15 Oct 2019 04:55:05 +0000 Subject: [Starlingx-discuss] Please help to review STX Wiki for Time Sensitive Networking In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F360861A0@SHSMSX104.ccr.corp.intel.com> References: <76647BD697F40748B1FA4F56DA02AA0B4D60F245@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F3601DBEE@SHSMSX104.ccr.corp.intel.com> <76647BD697F40748B1FA4F56DA02AA0B4D60F56B@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F3601DEA7@SHSMSX104.ccr.corp.intel.com> <4F6AACE4B0F173488D033B02A8BB5B7E7CEB5B1F@FMSMSX114.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F360861A0@SHSMSX104.ccr.corp.intel.com> Message-ID: <76647BD697F40748B1FA4F56DA02AA0B4D63161C@SHSMSX104.ccr.corp.intel.com> Cindy, We used the TSN application from https://github.com/intel/iotg_tsn_ref_sw to run in STX, and Elio verified the process based on the same application, thanks much! Best Regards, Le, Huifeng From: Xie, Cindy Sent: Tuesday, October 15, 2019 12:19 PM To: Cabrales, Ada ; Le, Huifeng ; Rowsell, Brent ; Peters, Matt ; Guo, Ruijing ; Martinez Monroy, Elio Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Please help to review STX Wiki for Time Sensitive Networking Huifeng, In your wiki page: https://wiki.openstack.org/wiki/StarlingX/Networking/TSN, you're referring to "Deploying and Running TSN application in StarlingX Virtual Machine Workload Mode", do you have one example StarlingX TSN application that we can run? Cindy Xie IAGS [StarlingX] From: Cabrales, Ada > Sent: Thursday, August 29, 2019 4:27 AM To: Xie, Cindy >; Le, Huifeng >; Rowsell, Brent >; Peters, Matt >; Guo, Ruijing >; Martinez Monroy, Elio > Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Please help to review STX Wiki for Time Sensitive Networking Hello Cindy Yes, Elio will be the one. Thank you Ada From: Xie, Cindy Sent: Monday, August 26, 2019 2:42 AM To: Le, Huifeng >; Rowsell, Brent >; Peters, Matt >; Guo, Ruijing >; Cabrales, Ada > Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Please help to review STX Wiki for Time Sensitive Networking + Ada for feature testing. It's so nice to know that basic TSN support shall be already in 2.0 (even in 1.0). This is one of the critical features to support Industrial use case. As TSN spec got approved as 3.0 feature, I guess we may have to run full feature testing according to your wiki pages before we can claim the full support. @Ada, do you have engineer assigned to work w/ network team on this important feature? Thx. - cindy From: Le, Huifeng Sent: Monday, August 26, 2019 2:22 PM To: Xie, Cindy >; Rowsell, Brent >; Peters, Matt >; Guo, Ruijing > Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Please help to review STX Wiki for Time Sensitive Networking Cindy, There is no patches pending for merging. TSN PTP feature had already been supported in STX 1.0, and the wiki verified how other TSN features can be deployed in STX through PCI-Passthrough (But there may still be confliction with STX PTP feature, e.g. STX PTP feature requires Nic be available in host, but due to the Nic e.g. Intel i210 does not support SRIOV, in case it is pass-through into VM to support TSN application, it will be not available in host then the STX PTP feature will not work). I have no concern and Core/TSC team can review and determine how to claim if no more concern about the process, thanks much! Best Regards, Le, Huifeng From: Xie, Cindy Sent: Monday, August 26, 2019 12:49 PM To: Le, Huifeng >; Rowsell, Brent >; Peters, Matt >; Guo, Ruijing > Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Please help to review STX Wiki for Time Sensitive Networking Huifeng, Seems like TSN support is based on Nova PCI pass-through for i210 network adaptor. Do you have any Nova patches or StarlingX patches pending merge (and need cherry pick) to allow the procedures in wiki page to be successful? If there are no patches pending, can we claim that TSN feature is already supported in stx.2.0? Thx. - cindy From: Le, Huifeng [mailto:huifeng.le at intel.com] Sent: Sunday, August 25, 2019 2:39 PM To: Rowsell, Brent >; Peters, Matt >; Guo, Ruijing > Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Please help to review STX Wiki for Time Sensitive Networking Brent, Matt, Ruijing, As following up on story: [Feature] Time Sensitive Networking (https://storyboard.openstack.org/#!/story/2005516) and approved spec https://review.opendev.org/#/c/666768/, we had done the POC to deploy and run TSN application on STX environment, the detail process and learning are summarized at Wiki: https://wiki.openstack.org/wiki/StarlingX/Networking/TSN which can be served as deliverable of task "StarlingX user guide on how to deploy TSN in VM". Could you please help to review the Wiki and let me know if you have any comments. Thanks much! Best Regards, Le, Huifeng -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 9473 bytes Desc: image003.png URL: From cristopher.j.lemus.contreras at intel.com Tue Oct 15 07:54:36 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Tue, 15 Oct 2019 02:54:36 -0500 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <0eeb65$60b27g@FMSMGA003.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191014T230000Z" rabbitmq:3.7-management k8s.gcr.io/kube-apiserver:v1.16.0 k8s.gcr.io/kube-proxy:v1.16.0 k8s.gcr.io/kube-controller-manager:v1.16.0 k8s.gcr.io/kube-scheduler:v1.16.0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From saul.wold at intel.com Tue Oct 8 22:49:31 2019 From: saul.wold at intel.com (Saul Wold) Date: Tue, 8 Oct 2019 15:49:31 -0700 Subject: [Starlingx-discuss] Debranding mirror and local repo Message-ID: Folks, I am starting the debranding of the cento-mirror creation and build tools that read from the cgcs-centos-repo and cgcs-tis-repo. These will be renamed centos-repo and local-repo respectively. I know this will also affect the CENGN build. We may want to have a discussion about if this should continue for 3.0 or just wait to post 3.0, I am open to others thoughts on this. This will also require some documentation changes, I will help out with the docs changes, but I would like to make sure I am doing it in the correct place, and for the correct release (master). There are other changes that I have proposed that can be handled stand-alone apart from the repo renaming. Sau! From denise at openstack.org Tue Oct 15 12:13:20 2019 From: denise at openstack.org (denise at openstack.org) Date: Tue, 15 Oct 2019 06:13:20 -0600 (MDT) Subject: [Starlingx-discuss] OSF booth at KubeCon+CloudNativeCon in San Diego Message-ID: <1571141600.054118968@apps.rackspace.com> Hello Everyone, We wanted to let you know that the OpenStack Foundation will have a booth at the upcoming KubeCon+CloudNativeCon event in San Diego, CA on November 18-21, 2019. We are in booth #S23 and we will be featuring the OpenStack Foundation in addition to all the projects - Airship, Kata Containers, StarlingX, OpenStack and Zuul. At the booth we will have stickers and educational collateral about each project to distribute. We would like to invite you to help us in the following areas: Represent your project by staffing the OSF booth If you can spare 1 hour/day (or any time at all!) to represent your specific project in the OSF booth Here is the [ link ]( https://docs.google.com/spreadsheets/d/1mZzK0GHm9OQ0IL9njTWLxPLuAeR6jqmyeM60T7sQQOc/edit#gid=0 ) to the google doc to sign up Project Demos in the OSF booth If you are interested in delivering a project-specific demo in the OSF booth, please contact [ Denise ]( http://denise at openstack.org ) Looking forward to seeing all of you in San Diego! Best regards, OSF Marketing team Denise, Claire, Allison and Ashlee -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Tue Oct 15 13:38:37 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 15 Oct 2019 13:38:37 +0000 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35F28711@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F35F28711@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F36086E35@SHSMSX104.ccr.corp.intel.com> Agenda: - Ceph containerization update (Tingjie) - Debranding update (Saul) - CentOS 8 upgrade planning (Cindy) - Opens Cindy Xie IAGS -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, October 16, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 * 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Picture (Device Independent Bitmap) 1.jpg Type: image/jpeg Size: 3183 bytes Desc: Picture (Device Independent Bitmap) 1.jpg URL: From Bill.Zvonar at windriver.com Tue Oct 15 14:04:43 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 15 Oct 2019 14:04:43 +0000 Subject: [Starlingx-discuss] Community Call (Oct 16, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B034B6@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of the Community call tomorrow. Please feel free to add new topics to the agenda at [0]. Currently, we have these topics... - next week's election for the flock-services PL role - unit test - how can we increase our coverage - and the usual standing topics... - Gerrit reviews that need attention - Red sanity learnings - unanswered requests for help in the mailing list - open AR review 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=20191016T1400 From shuicheng.lin at intel.com Tue Oct 15 14:08:21 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 15 Oct 2019 14:08:21 +0000 Subject: [Starlingx-discuss] StarlingX Bi-Weekly Containerization Meeting In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C76608D73EF@SHSMSX105.ccr.corp.intel.com> Hi all, Here is the slides for the Kata container integration in STX. And here is the patch list for it. https://review.opendev.org/#/q/topic:kata+(status:open) Thanks. Best Regards Shuicheng -----Original Appointment----- From: Miller, Frank Sent: Friday, October 11, 2019 9:58 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Bi-Weekly Containerization Meeting When: Tuesday, October 15, 2019 9:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236 Note: We agreed to a new day and time for these meetings. For all who are working containerization features or LPs please join for our bi-weekly meeting. Agenda for October 15 meeting: 1. Review KATA containers feature with container Cores. Shuicheng to present feature overview and current status. - Shuicheng's commits: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) 2.Updates on other stx.3.0 container features for MS3 milestone: * 2004008: [Feature] Create HELM chart for Fault project [An Ran] - one commit needs a new approach - discussed in item #2 * Decision to be made about Horizon issue - do we keep FM containers enabled without Horizon for VM alarms? Or do we disable in stx.3.0 until issue can be addressed in stx.4.0? * 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] - require updated forecast * 2005514: QAT K8S device plugin support in StarlingX * Bruce: Code is out for review; Frank to follow-up with Cindy or feature primes for updated forecasts * 2005860: Upversion container components [Al Bailey] * 2004761: Integrate Backup & Restore with Containers [Ovidiu Poncea] 3. Update on stx.4.0 features: * 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC 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 Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers << File: ATT00001.txt >> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Kata Integration in StarlingX.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 78823 bytes Desc: Kata Integration in StarlingX.pptx URL: From Frank.Miller at windriver.com Tue Oct 15 14:16:12 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 15 Oct 2019 14:16:12 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting Message-ID: Since we did not get through the whole agenda today, I will schedule the next meeting 1 week from today. Minutes for Oct 15 meeting: 1. Review KATA containers feature with container Cores. Shuicheng to present feature overview and current status. - Shuicheng's commits: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) - Shuicheng presented his feature and what has been done so far (see his charts in separate email) Actions identified: - Concerns: Interaction with registry, admin password is visible - Add a commit to make containerd the default CLI (and remove any docker code that is no longer needed) - Add a test case for local registry pull/push and authentication - Update code to ensure admin password is not visible - Frank to book a follow-up meeting to continue the review (Frank to book Tuesday Oct 22) Frank -----Original Appointment----- From: Miller, Frank Sent: Thursday, October 10, 2019 2:55 PM To: Miller, Frank; starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: StarlingX Bi-Weekly Containerization Meeting When: Tuesday, October 15, 2019 9:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236 Apologies, re-sending without etherpad formatting. Note: We agreed to a new day and time for these meetings. For all who are working containerization features or LPs please join for our bi-weekly meeting. Agenda for October 15 meeting: 1. Review KATA containers feature with container Cores. Shuicheng to present feature overview and current status. - Shuicheng's commits: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) 2. Updates on other stx.3.0 container features for MS3 milestone: - 2004008: [Feature] Create HELM chart for Fault project [An Ran] - one commit needs a new approach - discussed in item #2 - Decision to be made about Horizon issue - do we keep FM containers enabled without Horizon for VM alarms? Or do we disable in stx.3.0 until issue can be addressed in stx.4.0? - 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] - require updated forecast - 2005514: QAT K8S device plugin support in StarlingX - Bruce: Code is out for review; Frank to follow-up with Cindy or feature primes for updated forecasts - 2005860: Upversion container components [Al Bailey] - 2004761: Integrate Backup & Restore with Containers [Ovidiu Poncea] 3. Update on stx.4.0 features: - 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC Call details * Zoom link: https://zoom.us/j/342730236 * 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 Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Tue Oct 15 14:26:30 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 15 Oct 2019 14:26:30 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Meeting Message-ID: Our next meeting will be Tuesday Oct 22. Agenda: 1. Complete review of KATA containers feature with container Cores. - Shuicheng to update us on the actions from Oct 15 meeting - Cores to provide any additional input - Decision to be made on what content to allow in for stx.3.0 vs stx.4.0 2. Updates on stx.3.0 container features for MS3 milestone: 2004008: [Feature] Create HELM chart for Fault project [An Ran] - one commit needs a new approach - discussed in item #2 Decision to be made about Horizon issue - do we keep FM containers enabled without Horizon for VM alarms? Or do we disable in stx.3.0 until issue can be addressed in stx.4.0? 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] - require updated forecast Ran: Below 2 patches are for k8s device plugin enabling mechanism in ansible and sysinv, add intel gpu device plugin as well - https://review.opendev.org/#/c/666511/ - https://review.opendev.org/#/c/666510/ This patch needs further alignment with Matt for a format to enable all device plugins. Does not block above patches. - https://review.opendev.org/#/c/685592/ 2005514: QAT K8S device plugin support in StarlingX - code is out for review; require updated forecast Mingyuan: 3 patches: depends on Ran's 666510/666511 - https://review.opendev.org/684890 - https://review.opendev.org/688344 - https://review.opendev.org/688363 2005860: Upversion container components [Al Bailey] 2004761: Integrate Backup & Restore with Containers [Ovidiu Poncea] Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC Call details * Zoom link: https://zoom.us/j/342730236 * 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 Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3854 bytes Desc: not available URL: From haochuan.z.chen at intel.com Tue Oct 15 14:27:00 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 15 Oct 2019 14:27:00 +0000 Subject: [Starlingx-discuss] FW: [Build] Build layering reviews In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC158F833@ALA-MBD.corp.ad.wrs.com> References: <58efa3fb-9958-4af1-27f4-21db5a90da19@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F360482ED@SHSMSX104.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D856264A3B@CDSMSX102.ccr.corp.intel.com> <59676767-1870-b9a4-d256-77ff3a4148c8@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856265D08@CDSMSX102.ccr.corp.intel.com> <157958eb-6c13-318c-b087-a3d6b8a68662@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856266584@CDSMSX102.ccr.corp.intel.com> <92bad81a-e05f-6e1d-d83f-71263c01f29f@windriver.com> <56829C2A36C2E542B0CCB9854828E4D85626690A@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D85626EE06@CDSMSX102.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC158F833@ALA-MBD.corp.ad.wrs.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D856271BE0@CDSMSX102.ccr.corp.intel.com> Hi I have updated patch for layer build https://review.opendev.org/#/c/681821/ https://review.opendev.org/#/c/681823/ https://review.opendev.org/#/c/681824/ https://review.opendev.org/#/c/681828/ https://review.opendev.org/#/c/681832/ https://review.opendev.org/#/c/681834/ https://review.opendev.org/#/c/681835/ https://review.opendev.org/#/c/681836/ https://review.opendev.org/#/c/681842/ https://review.opendev.org/#/c/681847/ https://review.opendev.org/#/c/681848/ https://review.opendev.org/#/c/681851/ https://review.opendev.org/#/c/681852/ https://review.opendev.org/#/c/681854/ https://review.opendev.org/#/c/681856/ https://review.opendev.org/#/c/681890/ https://review.opendev.org/#/c/681892/ https://review.opendev.org/#/c/681894/ https://review.opendev.org/#/c/681898/ https://review.opendev.org/#/c/681900/ https://review.opendev.org/#/c/681901/ https://review.opendev.org/#/c/681902/ https://review.opendev.org/#/c/681914/ https://review.opendev.org/#/c/688598/ And I think we still left three issue. 1, request build-tools/build_iso/centos_required_build_layer.cfg Current for self validation, we could add a file with such content. But we should create a file depending on cenga update compile,file:///localdisk/loadbuild/martin/starlingx/centos_compile_iso_image.inc distro,file:///localdisk/loadbuild/martin/distro/centos_distro_iso_image.inc flock,file:///localdisk/loadbuild/martin/flock/centos_flock_iso_image.inc 2, propose use one copy of yum.conf.sample and yum.repo.d/* Currently there is 4 copies of yum.conf.sample and yum.repo.d/*. 3 copies in stx-tools/centos-mirror-tools/config/centos// and 1 copy in stx-tools/centos-mirror-tools/ Propose to remove 3 copies in stx-tools/centos-mirror-tools/config/centos//. To avoid user confusing 3, update script download_mirror.sh and generate-cgts-centos-repo Currently all rpm name in lst is listed with fixed rpm version, which makes layer build easily to be corrupted. For example, any time TIS_PATCH_VER in build_srpm.data update, rpm name in lst should be updated. Prefer rpm named with “tis” should be query candidate on cenga, which request download_mirror.sh and generate-cgts-centos-repo update. Prefer we could finish such update in this story, as I think this is a critical issue. Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Penney, Don Sent: Monday, September 30, 2019 11:33 PM To: Bailey, Henry Albert (Al) ; Chen, Haochuan Z ; Little, Scott ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] FW: [Build] Build layering reviews Is this the issue? openstack/python-horizon/centos/python-django-horizon.spec:BuildRequires: cgts-client I don’t see anything in this package that should need this dependency, and it should be safe to remove it. From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] Sent: Monday, September 30, 2019 10:56 AM To: Chen, Haochuan Z; Little, Scott; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] FW: [Build] Build layering reviews I think Cgts-client (renamed to system-client) should be in its own repo. Al From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Monday, September 30, 2019 2:06 AM To: Little, Scott; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] FW: [Build] Build layering reviews Hi Scott I think have some question or concern. 1, I find distro layer has dependency to cgts-client, as there is a addin for Horizon, which enables look up flock service info in Horizon. So there is task is must for layer building, which is out of my expectation. I begin to tackle these task. • Relocate from git 'config', subdir 'sysinv/cgts-client', to git 'utilities', subdir 'system-client', with full git history. • Rename rpm package from 'cgts-client' to 'system-client' • Fix rpm packages that list cgts-client as a require or build require • Rename python module from 'cgts-client' to 'system-client' • Scan function names and/or variables for any that contain 'cgts' ... replace with 'system' ... can we do this in a backward compatible way? • Fix users of the client to import using the new name, and reference any renamed functions/data. • Fix ISO and/or docker images that list this package for inclusion. 2, “all” layer maybe doesn’t work, warning! For current patch for generate-cgts-centos-repo.sh, all layer’s rpms_lst_file is generated by merge “compiler/distro/flock” three layers, config/centos/all doesn’t be referenced, which is none sense. Which means package such bash-4.2.46-31.el7.tis.4.x86_64.rpm, named with “tis” is also in mirror. This maybe interference source package building. I think request some fix in generate-cgts-centos-repo.sh to omit package with “tis” in name. 3, Layered build introduces rpms_cemtos.lst dependency on TIS_PATCH_VER in build_srpm.data, which make developer easily disrupt layered building mechanism. For distro and flock layer, it has dependency to starlingX customized package, for example, distro layer require bash.tis...rpm, which will be add in config/centos/distro/rpms_centos3rdparty.lst If new developer forget to update and build all package, it maybe disrupt layered building. BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Friday, September 27, 2019 4:40 PM To: Scott Little >; starlingx-discuss at lists.starlingx.io Subject: RE: FW: [Starlingx-discuss] [Build] Build layering reviews Thanks, Scott. I have studied so much. BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Scott Little > Sent: Thursday, September 26, 2019 11:39 PM To: Chen, Haochuan Z >; starlingx-discuss at lists.starlingx.io Subject: Re: FW: [Starlingx-discuss] [Build] Build layering reviews Returning this discussion to the mailing list. If possible, join the Build call next week. https://wiki.openstack.org/wiki/Starlingx/Meetings 1) When mock installs for the first time. it uses rpms that have been download via lst file. The mock pseudo-layer lst files capture reflect the rpms needed by mock. The mock lst's are merged with the layers lst's. In this way, the mock rpms don't have to be listed in each and every layer's lst. 2) Adding tools to generate an lst file reflacting the output of a build layer, and adding that lst for consumprion by higher layers, is indeed a possibility possibility I wanted to persue. Reference to that output lst could then be added to as a new arg to the download script when invoked by a higher layer, or a config file could specify where to find it (cengn is the likely default supplier). compile layer) The compile layer is a true layer, built prior to the distro layer. Only a few build related packages go here. Compilers, language interpreters, rpm. I wanted those packages in place so that all distro layer packages build with the same tools. Scott On 2019-09-25 10:24 p.m., Chen, Haochuan Z wrote: Still not clear about mock layer. 1, In build container, mock is already installed, why request to download mock required package firstly? 2, To build distro or flock layer, we could add compile layer’s tis rpm in distro and flock layer’s lst file. By download compile layer’s binary in mirror, it could also ensure user building package with same tool. Why introduces compile layer? Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Scott Little Sent: Thursday, September 26, 2019 12:25 AM To: Chen, Haochuan Z Subject: Re: FW: [Starlingx-discuss] [Build] Build layering reviews See inline ... Scott On 2019-09-23 11:00 a.m., Chen, Haochuan Z wrote: Hi Scott I studied your patch and some questions. 1, why there is mock and compile layer, what's usage or intention for these two layers? Build-pkgs uses a tool called mock to create a reproducible compilation sandbox. It is chroot like environmnet into which rpms are installed to construct a minimal build environment. The mock layer is not built. I created it as a placeholder for the lst files that downloads all the rpms that mock requires. Prior to building a layer, the lst files for both the layer being build, and the mock pseudo layer, need to be processed. Without the mock pseudo layer, we would have to replicate that list of mock required rpms in each and ever layer's lst files. The concept ran into a bit of trouble because some of the rpms needed by mock are themselves built by the compile or distro layers (with a newer revision). So the mock pseudo layer might actually omit those rpms from it's lst file, and they needed to be listed in the layer lst files instead. The compile layer is a true layer, built prior to the distro layer. Only a few build related packages go here. Compilers, language interpreters, rpm. I wanted those packages in place so that all distro layer packages build with the same tools. 2, for download_mirror.sh, it generate rpm list by merge file in config/centos// and rpm list file in stx/ But for generate-cgcs-centos-repo.sh, it use rpm list file in centos-mirror-tools folder. Rpm package should be added in two rpm list file. It is not good for maintenance. What about remove rpm list file in centos-mirror-tools folder rpms_centos.lst/rpms_centos3rdparties.lst/rpms_3rdparties.lst/other_downloads.lst/ tarball-dl.lst That was considered and debated. The concern was that the many git repos that make up the layer would list different versions of the same package. Then what do we do? Throw an error? Silently use the newest package? So we elected to keep binary rpms needed to satisfy dependencies listed in a central place. At some point we may want to explore allowing lst files specify required package but not version (beyond a possible minimum version) when on the master branch, and have a way to 'lock down' the versions only for a release branch. 3, Question about setup yum repo for rpm tailing with “tis” such as xxx.tis.x86_64.rpm or xxx.tis.noarch.rpm In this patch https://review.opendev.org/#/c/681821/1 There is such line in config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo [Starlingx-cengn_distro_layer] name=Starlingx-cengn_distro_layer baseurl=http://127.0.0.1:8088/localdisk/loadbuild/slittle1/restructure3b/std/rpmbuild/RPMS/ enabled=1 [Starlingx-cengn_distro_layer-rt] name=Starlingx-cengn_distro_layer baseurl=http://127.0.0.1:8088/localdisk/loadbuild/slittle1/restructure3b/rt/rpmbuild/RPMS/ enabled=1 also in config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo My understanding is rpm tailing with “tis” should also upload to cengn, rpm name listed in centos-mirror-tools/config/centos/flock/rpms_centos3rdparties.lst So these three files should be unnecessary, with cengn update for layered build. config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo For development testing, I had to hack together a simulated cengn by running lighttpd on 127.0.0.1:8088 and allowing it to serve up files from builds of lower layers restructure3a == layer-comiler layer build restructure3b == layer-distro layer build restructure3c == layer-flock layer build (although there shouldn't be a repo entry referring to that one) Finalizing the repo entries would have to wait until cengn was up an running. 4, In generate-cgcs-centos-repo.sh there is --layer-dir, and such content in your patch commit message generate-cgcs-centos-repo.sh \ --layer-dir=/localdisk/loadbuild/slittle1/layer-compile/std/rpmbuild/RPMS/ \ --layer-dir=/localdisk/loadbuild/slittle1/layer-distro/std/rpmbuild/RPMS/ \ --layer-dir=/localdisk/loadbuild/slittle1/layer-distro/rt/rpmbuild/RPMS/ \ /import/mirrors/starlingx For all rpm download from cengn, --layer-dir is unnecessary to generate link, correct? This is another way to do cross layer development testing without support from cengn. Again the goal is to allow an upper layer build to download rpms from a lower layer build on the same machine. 5, could you share build-tools/build-iso/centos_required_build_layer.cfg, share to me Did that not get published in my reviews? Content is very simple. compile,file:///localdisk/loadbuild/slittle1/restructure3a/centos_compile_iso_image.inc distro,file:///localdisk/loadbuild/slittle1/restructure3b/centos_distro_iso_image.inc flock,file:///localdisk/loadbuild/slittle1/restructure3c/centos_flock_iso_image.inc 6, For distro/compiler/flock, all are separate layer? Yes My current step repo init -u https://opendev.org/starlingx/manifest.git apply this patch to .repo/manifests https://review.opendev.org/#/c/681914/1 repo init -m compile.xml repo sync apply these to patch https://review.opendev.org/#/c/681821/1 https://review.opendev.org/#/c/681828/1 ./download_mirror.sh -n -g -l flock -c config/centos/compiler/yum.conf.sample -S ./toCopy/generate-cgts-centos-repo output/stx-r1/CentOS/pike/ build-pkgs build-iso BR! Martin, Chen SSP, Software Engineer 021-61164330 -----Original Message----- From: Scott Little Sent: Thursday, September 19, 2019 9:54 PM To: Chen, Haochuan Z Subject: Re: FW: [Starlingx-discuss] [Build] Build layering reviews Most of the required changes were already merged. I'll scan the spec when time permits to see if I missed anything. Scott On 2019-09-16 12:01 p.m., Chen, Haochuan Z wrote: > Hi Scott > > I read your patch for build layering, but could not find patch for build script. > > Description in spec https://review.opendev.org/#/c/672288/12/ > Modifications to package build scripts ... build-pkgs, > build-srpms-parallel, build-srpms-serial, build-rpms-parallel, build-rpms-serial (cgcs-root): > > Thanks > > Martin, Chen > SSP, Software Engineer > 021-61164330 > > -----Original Message----- > From: Xie, Cindy > Sent: Friday, September 13, 2019 12:24 PM > To: Chen, Haochuan Z > > Cc: Hu, Yong > > Subject: FW: [Starlingx-discuss] [Build] Build layering reviews > > Martin, > I am wondering if you will be interested to working on this task. To me, having layering build and provide efficiency to developers are very important for StarlingX. It also provide a chance that you and work together w/ WR folks being more close collaboration. Let me know your interested level. > > Thx. -cindy > > -----Original Message----- > From: Scott Little > > Sent: Friday, September 13, 2019 4:55 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [Build] Build layering reviews > > My prototype code for the layered build has been posted to gerrit. > (listed below) > > I was briefly able to build all layers, and produce an iso with the same package content as the cengn build. Then I was diverted by non-trivial changes to the restructuring work. What I have posted is now several weeks out of date and will almost certainly will not work. The devil is in keeping the lst files in sync with the ever changing master branch. > > Other commitments will prevent me from resuming this work until November. If anyone wants to whip the lst files into shape and try to get the build working again, be my guest. > > Final delivery will require changes to the CENGN build scripts (Don or Myself), and a freeze on packaging changes will likely be required for aprox 3 days to finalize the lst files. > > Scott > > ---------------- ---------------- > > https://review.opendev.org/#/c/681821/1 > > https://review.opendev.org/#/c/681914/1 > > https://review.opendev.org/#/c/681823/1 > > https://review.opendev.org/#/c/681824/1 > > https://review.opendev.org/#/c/681828/1 > > https://review.opendev.org/#/c/681832/2 > > https://review.opendev.org/#/c/681834/1 > > https://review.opendev.org/#/c/681836/1 > > https://review.opendev.org/#/c/681835/1 > > https://review.opendev.org/#/c/681842/1 > > https://review.opendev.org/#/c/681847/1 > > https://review.opendev.org/#/c/681848/1 > > https://review.opendev.org/#/c/681851/1 > > https://review.opendev.org/#/c/681852/1 > > https://review.opendev.org/#/c/681854/1 > > https://review.opendev.org/#/c/681856/1 > > https://review.opendev.org/#/c/681890/1 > > https://review.opendev.org/#/c/681892/1 > > https://review.opendev.org/#/c/681892/1 > > https://review.opendev.org/#/c/681898/1 > > https://review.opendev.org/#/c/681900/1 > > https://review.opendev.org/#/c/681901/1 > > https://review.opendev.org/#/c/681902/1 > > > > > _______________________________________________ > 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 Tue Oct 15 16:15:47 2019 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 15 Oct 2019 09:15:47 -0700 Subject: [Starlingx-discuss] FW: [Build] Build layering reviews In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D856271BE0@CDSMSX102.ccr.corp.intel.com> References: <58efa3fb-9958-4af1-27f4-21db5a90da19@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F360482ED@SHSMSX104.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D856264A3B@CDSMSX102.ccr.corp.intel.com> <59676767-1870-b9a4-d256-77ff3a4148c8@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856265D08@CDSMSX102.ccr.corp.intel.com> <157958eb-6c13-318c-b087-a3d6b8a68662@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856266584@CDSMSX102.ccr.corp.intel.com> <92bad81a-e05f-6e1d-d83f-71263c01f29f@windriver.com> <56829C2A36C2E542B0CCB9854828E4D85626690A@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D85626EE06@CDSMSX102.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC158F833@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D856271BE0@CDSMSX102.ccr.corp.intel.com> Message-ID: I am wondering if it would be easier to test and review this if we had all these changes on a branch and have an associated manifest. Sau! On 10/15/19 7:27 AM, Chen, Haochuan Z wrote: > Hi > > I have updated patch for layer build > > https://review.opendev.org/#/c/681821/ > > https://review.opendev.org/#/c/681823/ > > https://review.opendev.org/#/c/681824/ > > https://review.opendev.org/#/c/681828/ > > https://review.opendev.org/#/c/681832/ > > https://review.opendev.org/#/c/681834/ > > https://review.opendev.org/#/c/681835/ > > https://review.opendev.org/#/c/681836/ > > https://review.opendev.org/#/c/681842/ > > https://review.opendev.org/#/c/681847/ > > https://review.opendev.org/#/c/681848/ > > https://review.opendev.org/#/c/681851/ > > https://review.opendev.org/#/c/681852/ > > https://review.opendev.org/#/c/681854/ > > https://review.opendev.org/#/c/681856/ > > https://review.opendev.org/#/c/681890/ > > https://review.opendev.org/#/c/681892/ > > https://review.opendev.org/#/c/681894/ > > https://review.opendev.org/#/c/681898/ > > https://review.opendev.org/#/c/681900/ > > https://review.opendev.org/#/c/681901/ > > https://review.opendev.org/#/c/681902/ > > https://review.opendev.org/#/c/681914/ > > https://review.opendev.org/#/c/688598/ > > And I think we still left three issue. > > 1, request build-tools/build_iso/centos_required_build_layer.cfg > > Current for self validation, we could add a file with such content. But > we should create a file depending on cenga update > > compile,file:///localdisk/loadbuild/martin/starlingx/centos_compile_iso_image.inc > > distro,file:///localdisk/loadbuild/martin/distro/centos_distro_iso_image.inc > > flock,file:///localdisk/loadbuild/martin/flock/centos_flock_iso_image.inc > > 2, propose use one copy of yum.conf.sample and yum.repo.d/* > > Currently there is 4 copies of yum.conf.sample and yum.repo.d/*.  3 > copies in stx-tools/centos-mirror-tools/config/centos// and 1 > copy in stx-tools/centos-mirror-tools/ > >   Propose to remove 3 copies in > stx-tools/centos-mirror-tools/config/centos//. To avoid user > confusing > > 3, update script download_mirror.sh and generate-cgts-centos-repo > > Currently all rpm name in lst is listed with fixed rpm version, which > makes layer build easily to be corrupted. For example, any time > TIS_PATCH_VER in build_srpm.data update, rpm name in lst should be updated. > > Prefer rpm named with “tis” should be query candidate on cenga, which > request download_mirror.sh and generate-cgts-centos-repo update. Prefer > we could finish such update in this story, as I think this is a critical > issue. > > Thanks! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > *From:*Penney, Don > *Sent:* Monday, September 30, 2019 11:33 PM > *To:* Bailey, Henry Albert (Al) ; Chen, > Haochuan Z ; Little, Scott > ; 'starlingx-discuss at lists.starlingx.io' > > *Subject:* RE: [Starlingx-discuss] FW: [Build] Build layering reviews > > Is this the issue? > > openstack/python-horizon/centos/python-django-horizon.spec:BuildRequires: cgts-client > > I don’t see anything in this package that should need this dependency, > and it should be safe to remove it. > > *From:*Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] > *Sent:* Monday, September 30, 2019 10:56 AM > *To:* Chen, Haochuan Z; Little, Scott; > 'starlingx-discuss at lists.starlingx.io' > *Subject:* Re: [Starlingx-discuss] FW: [Build] Build layering reviews > > I think Cgts-client  (renamed to system-client)  should be in its own repo. > > Al > > *From:*Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] > *Sent:* Monday, September 30, 2019 2:06 AM > *To:* Little, Scott; 'starlingx-discuss at lists.starlingx.io' > *Subject:* Re: [Starlingx-discuss] FW: [Build] Build layering reviews > > Hi Scott > > I think have some question or concern. > > 1, I find distro layer has dependency to cgts-client, as there is a > addin for Horizon, which enables look up flock service info in Horizon. > > So there is task is must for layer building, which is out of my > expectation.  I begin to tackle these task. > > ·Relocate from git 'config', subdir 'sysinv/cgts-client', to git > 'utilities', subdir 'system-client', *with full git history.* > > ·Rename rpm package from 'cgts-client' to 'system-client' > > ·Fix rpm packages that list cgts-client as a require or build require > > ·Rename python module from 'cgts-client' to 'system-client' > > ·Scan function names and/or variables for any that contain 'cgts' ... > replace with 'system' ... can we do this in a backward compatible way? > > ·Fix users of the client to import using the new name, and reference any > renamed functions/data. > > ·Fix ISO and/or docker images that list this package for inclusion. > > 2, “all” layer maybe doesn’t work, warning! > > For current patch for generate-cgts-centos-repo.sh, all layer’s > rpms_lst_file is generated by merge “compiler/distro/flock” three > layers, config/centos/all doesn’t be referenced, which is none sense. > Which means package such bash-4.2.46-31.el7.tis.4.x86_64.rpm, named with > “tis” is also in mirror. This maybe interference source package > building. I think request some fix in generate-cgts-centos-repo.sh to > omit package with “tis” in name. > > 3, Layered build introduces rpms_cemtos.lst dependency on TIS_PATCH_VER > in build_srpm.data, which make developer easily disrupt layered building > mechanism. > > For distro and flock layer, it has dependency to starlingX customized > package, for example, distro layer require bash.tis. version>..rpm, which will be add in > config/centos/distro/rpms_centos3rdparty.lst > > If new developer forget to update and build all package, it maybe > disrupt layered building. > > BR! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > *From:*Chen, Haochuan Z > *Sent:* Friday, September 27, 2019 4:40 PM > *To:* Scott Little >; > starlingx-discuss at lists.starlingx.io > > *Subject:* RE: FW: [Starlingx-discuss] [Build] Build layering reviews > > Thanks, Scott. I have studied so much. > > BR! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > *From:*Scott Little > > *Sent:* Thursday, September 26, 2019 11:39 PM > *To:* Chen, Haochuan Z >; > starlingx-discuss at lists.starlingx.io > > *Subject:* Re: FW: [Starlingx-discuss] [Build] Build layering reviews > > Returning this discussion to the mailing list. > > If possible, join the Build call next week. > https://wiki.openstack.org/wiki/Starlingx/Meetings > > 1) > > When mock installs for the first time. it uses rpms that have been > download via lst file. The mock pseudo-layer lst files capture reflect > the rpms needed by mock.  The mock lst's are merged with the layers > lst's.  In this way, the mock rpms don't have to be listed in each and > every layer's lst. > > 2) > > Adding tools to generate an lst file reflacting the output of a build > layer, and adding that lst for consumprion by higher layers, is indeed a > possibility possibility I wanted to persue.  Reference to that output > lst could then be added to as a new arg to the download script when > invoked by a higher layer, or a config file could specify where to find > it (cengn is the likely default supplier). > > compile layer) > > The compile layer is a true layer, built prior to the distro layer. > Only a few build related packages go here.  Compilers, language > interpreters, rpm.  I wanted those packages in place so that all distro > layer packages build with the same tools. > > Scott > > On 2019-09-25 10:24 p.m., Chen, Haochuan Z wrote: > > Still not clear about mock layer. > > 1, In build container, mock is already installed, why request to > download mock required package firstly? > > 2, To build distro or flock layer, we could add compile layer’s tis > rpm in distro and flock layer’s lst file. By download compile > layer’s binary in mirror, it could also ensure user building package > with same tool. > > Why introduces compile layer? > > Thanks! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > *From:*Scott Little > > *Sent:* Thursday, September 26, 2019 12:25 AM > *To:* Chen, Haochuan Z > > *Subject:* Re: FW: [Starlingx-discuss] [Build] Build layering reviews > > See inline ... > > Scott > > On 2019-09-23 11:00 a.m., Chen, Haochuan Z wrote: > > Hi Scott > > I studied your patch and some questions. > > 1, why there is mock and compile layer, what's usage or > intention for these two layers? > > Build-pkgs uses a tool called mock to create a reproducible > compilation sandbox.  It is chroot like environmnet into which rpms > are installed to construct a minimal build environment. > > The mock layer is not built.  I created it as a placeholder for the > lst files that downloads all the rpms that mock requires.  Prior to > building a layer, the lst files for both the layer being build, and > the mock pseudo layer, need to be processed. Without the mock pseudo > layer, we would have to replicate that list of mock required rpms in > each and ever layer's lst files. > > The concept ran into a bit of trouble because some of the rpms > needed by mock are themselves built by the compile or distro layers > (with a newer revision).   So the > mock pseudo layer might actually omit those rpms from it's lst file, > and they needed to be listed in the layer lst files instead. > > The compile layer is a true layer, built prior to the distro layer. > Only a few build related packages go here.  Compilers, language > interpreters, rpm.  I wanted those packages in place so that all > distro layer packages build with the same tools. > > 2, for download_mirror.sh, it generate rpm list by merge file in > config/centos// and rpm list file in > stx/ > >    But for generate-cgcs-centos-repo.sh, it use rpm list file > in centos-mirror-tools folder. Rpm package should be added in > two rpm list file. > >    It is not good for maintenance. What about remove rpm list > file in centos-mirror-tools folder > > /rpms_centos.lst/rpms_centos3rdparties.lst/rpms_3rdparties.lst/other_downloads.lst/ > tarball-dl.lst/ > > That was considered and debated. The concern was that the many git > repos that make up the layer would list different versions of the > same package.  Then what do we do?  Throw an error?  Silently use > the newest package?  So we elected to keep binary rpms needed to > satisfy dependencies listed in a central place. > > At some point we may want to explore allowing lst files specify > required package but not version (beyond a possible minimum version) > when on the master branch, and have a way to 'lock down' the > versions only for a release branch. > > 3, Question about setup yum repo for rpm tailing with “tis” such > as xxx.*tis*.x86_64.rpm or xxx.*tis*.noarch.rpm > > In this patch https://review.opendev.org/#/c/681821/1 > > /There is such line in > config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo/ > > /[Starlingx-cengn_distro_layer]/ > > /name=Starlingx-cengn_distro_layer/ > > /baseurl=http://127.0.0.1:8088/localdisk/loadbuild//*/slittle1/restructure3b/*//std/rpmbuild/RPMS// > > /enabled=1/ > > /[Starlingx-cengn_distro_layer-rt]/ > > /name=Starlingx-cengn_distro_layer/ > > /baseurl=http://127.0.0.1:8088/localdisk/loadbuild//*/slittle1/restructure3b/*//rt/rpmbuild/RPMS// > > /enabled=1/ > > also in > > config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo > > config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo > > My understanding is rpm tailing with “tis” should also upload to > cengn, rpm name listed in > centos-mirror-tools/config/centos/flock/rpms_centos3rdparties.lst > > So these three files should be unnecessary, with cengn update > for layered build. > > config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo > > config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo > > config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo > > For development testing, I had to hack together a simulated cengn by > running lighttpd on 127.0.0.1:8088 and allowing it to serve up files > from builds of lower layers > > restructure3a == layer-comiler layer build > > restructure3b == layer-distro layer build > > restructure3c == layer-flock layer build  (although there shouldn't > be a repo entry referring to that one) > > Finalizing the repo entries would have to wait until cengn was up an > running. > > 4, In generate-cgcs-centos-repo.sh there is --layer-dir, and > such content in your patch commit message > > /generate-cgcs-centos-repo.sh \/ > > /--layer-dir=/localdisk/loadbuild/slittle1/layer-compile/std/rpmbuild/RPMS/ > \/ > > /--layer-dir=/localdisk/loadbuild/slittle1/layer-distro/std/rpmbuild/RPMS/ > \/ > > /--layer-dir=/localdisk/loadbuild/slittle1/layer-distro/rt/rpmbuild/RPMS/ > \/ > > //import/mirrors/starlingx/ > >    For all rpm download from cengn, --layer-dir is unnecessary > to generate link, correct? > > This is another way to do cross layer development testing without > support from cengn.  Again the goal is to allow an upper layer build > to download rpms from a lower layer build on the same machine. > > 5, could you share > build-tools/build-iso/centos_required_build_layer.cfg, share to me > > Did that not get published in my reviews?  Content is very simple. > > compile,file:///localdisk/loadbuild/slittle1/restructure3a/centos_compile_iso_image.inc > > distro,file:///localdisk/loadbuild/slittle1/restructure3b/centos_distro_iso_image.inc > > flock,file:///localdisk/loadbuild/slittle1/restructure3c/centos_flock_iso_image.inc > > > 6, For distro/compiler/flock, all are separate layer? > > Yes > > My current step > > /repo init -u https://opendev.org/starlingx/manifest.git/ > > /apply this patch to .repo/manifests/ > > /https://review.opendev.org/#/c/681914/1/ > > /repo init -m compile.xml/ > > /repo sync/ > > /apply these to patch/ > > /https://review.opendev.org/#/c/681821/1/ > > /https://review.opendev.org/#/c/681828/1/ > > /./download_mirror.sh  -n -g -l flock -c > config/centos/compiler/yum.conf.sample -S / > > /./toCopy/generate-cgts-centos-repo output/stx-r1/CentOS/pike// > > /build-pkgs/ > > /build-iso/ > > BR! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > -----Original Message----- > From: Scott Little > > Sent: Thursday, September 19, 2019 9:54 PM > To: Chen, Haochuan Z > > Subject: Re: FW: [Starlingx-discuss] [Build] Build layering reviews > > Most of the required changes were already merged. > > I'll scan the spec when time permits to see if I missed anything. > > Scott > > On 2019-09-16 12:01 p.m., Chen, Haochuan Z wrote: > > > Hi Scott > > > > > > I read your patch for build layering, but could not find > patch for build script. > > > > > > Description in spec https://review.opendev.org/#/c/672288/12/ > > > Modifications to package build scripts ... build-pkgs, > > > build-srpms-parallel, build-srpms-serial, > build-rpms-parallel, build-rpms-serial (cgcs-root): > > > > > > Thanks > > > > > > Martin, Chen > > > SSP, Software Engineer > > > 021-61164330 > > > > > > -----Original Message----- > > > From: Xie, Cindy > > > Sent: Friday, September 13, 2019 12:24 PM > > > To: Chen, Haochuan Z > > > > Cc: Hu, Yong > > > > Subject: FW: [Starlingx-discuss] [Build] Build layering reviews > > > > > > Martin, > > > I am wondering if you will be interested to working on this > task. To me, having layering build and provide efficiency to > developers are very important for StarlingX. It also provide a > chance that you and work together w/ WR folks being more close > collaboration. Let me know your interested level. > > > > > > Thx. -cindy > > > > > > -----Original Message----- > > > From: Scott Little > > > > Sent: Friday, September 13, 2019 4:55 AM > > > To: starlingx-discuss at lists.starlingx.io > > > > Subject: [Starlingx-discuss] [Build] Build layering reviews > > > > > > My prototype code for the layered build has been posted to > gerrit. > > > (listed below) > > > > > > I was briefly able to build all layers, and produce an iso > with the same package content as the cengn build.  Then I was > diverted by non-trivial changes to the restructuring work. What > I have posted is now several weeks out of date and will almost > certainly will not work.  The devil is in keeping the lst files > in sync with the ever changing master branch. > > > > > > Other commitments will prevent me from resuming this work > until November.  If anyone wants to whip the lst files into > shape and try to get the build working again, be my guest. > > > > > > Final delivery will require changes to the CENGN build > scripts (Don or Myself), and a freeze on packaging changes will > likely be required for aprox 3 days to finalize the lst files. > > > > > > Scott > > > > > > ---------------- ---------------- > > > > > > https://review.opendev.org/#/c/681821/1 > > > > > > https://review.opendev.org/#/c/681914/1 > > > > > > https://review.opendev.org/#/c/681823/1 > > > > > > https://review.opendev.org/#/c/681824/1 > > > > > > https://review.opendev.org/#/c/681828/1 > > > > > > https://review.opendev.org/#/c/681832/2 > > > > > > https://review.opendev.org/#/c/681834/1 > > > > > > https://review.opendev.org/#/c/681836/1 > > > > > > https://review.opendev.org/#/c/681835/1 > > > > > > https://review.opendev.org/#/c/681842/1 > > > > > > https://review.opendev.org/#/c/681847/1 > > > > > > https://review.opendev.org/#/c/681848/1 > > > > > > https://review.opendev.org/#/c/681851/1 > > > > > > https://review.opendev.org/#/c/681852/1 > > > > > > https://review.opendev.org/#/c/681854/1 > > > > > > https://review.opendev.org/#/c/681856/1 > > > > > > https://review.opendev.org/#/c/681890/1 > > > > > > https://review.opendev.org/#/c/681892/1 > > > > > > https://review.opendev.org/#/c/681892/1 > > > > > > https://review.opendev.org/#/c/681898/1 > > > > > > https://review.opendev.org/#/c/681900/1 > > > > > > https://review.opendev.org/#/c/681901/1 > > > > > > https://review.opendev.org/#/c/681902/1 > > > > > > > > > > > > > > > _______________________________________________ > > > 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 dtroyer at gmail.com Tue Oct 15 16:29:16 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 15 Oct 2019 11:29:16 -0500 Subject: [Starlingx-discuss] FW: [Build] Build layering reviews In-Reply-To: References: <58efa3fb-9958-4af1-27f4-21db5a90da19@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F360482ED@SHSMSX104.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D856264A3B@CDSMSX102.ccr.corp.intel.com> <59676767-1870-b9a4-d256-77ff3a4148c8@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856265D08@CDSMSX102.ccr.corp.intel.com> <157958eb-6c13-318c-b087-a3d6b8a68662@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856266584@CDSMSX102.ccr.corp.intel.com> <92bad81a-e05f-6e1d-d83f-71263c01f29f@windriver.com> <56829C2A36C2E542B0CCB9854828E4D85626690A@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D85626EE06@CDSMSX102.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC158F833@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D856271BE0@CDSMSX102.ccr.corp.intel.com> Message-ID: On Tue, Oct 15, 2019 at 11:17 AM Saul Wold wrote: > I am wondering if it would be easier to test and review this if we had > all these changes on a branch and have an associated manifest. You do not need branches to do that, repo knows how to pick specific reviews out of Gerrit to build its tree. You don't even need to merge the manifest, just propose a review with it and everyone can pull that directly. dt -- Dean Troyer dtroyer at gmail.com From fungi at yuggoth.org Tue Oct 15 17:08:02 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Tue, 15 Oct 2019 17:08:02 +0000 Subject: [Starlingx-discuss] FW: [Build] Build layering reviews In-Reply-To: References: <157958eb-6c13-318c-b087-a3d6b8a68662@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856266584@CDSMSX102.ccr.corp.intel.com> <92bad81a-e05f-6e1d-d83f-71263c01f29f@windriver.com> <56829C2A36C2E542B0CCB9854828E4D85626690A@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D85626EE06@CDSMSX102.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC158F833@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D856271BE0@CDSMSX102.ccr.corp.intel.com> Message-ID: <20191015170802.um556agqlss5lkb3@yuggoth.org> On 2019-10-15 11:29:16 -0500 (-0500), Dean Troyer wrote: > On Tue, Oct 15, 2019 at 11:17 AM Saul Wold wrote: > > I am wondering if it would be easier to test and review this if we had > > all these changes on a branch and have an associated manifest. > > You do not need branches to do that, repo knows how to pick specific > reviews out of Gerrit to build its tree. You don't even need to merge > the manifest, just propose a review with it and everyone can pull that > directly. I've often likened Gerrit to a solution for sharing lightweight, ephemeral topic branches. It works well for that purpose. We also replicate all Gerrit change refs (and associated Git notes) to the https://opendev.org/ Gitea service, so you can do things like: git clone https://opendev.org/starlingx/manifest cd manifest git fetch origin refs/changes/00/687200/1 git checkout -B stx_dashboard_train FETCH_HEAD ...or cherry-pick, or merge, or rebase, and never even have to communicate with the Gerrit server at all (as long as the change and patchset numbers are already known). Note that with checkout in particular, you'll automatically pick up any parent changes too if they're already in series. -- 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 marcela.a.rosales.jimenez at intel.com Tue Oct 15 17:28:52 2019 From: marcela.a.rosales.jimenez at intel.com (Rosales Jimenez, Marcela A) Date: Tue, 15 Oct 2019 17:28:52 +0000 Subject: [Starlingx-discuss] [MultiOS] Team meeting 10/14/19 Message-ID: Hi team, these are the MultiOS minutes https://etherpad.openstack.org/p/stx-multios Feel free to add any topic you want to discuss to next week’s agenda :) MultiOS team meeting - 10/14/2019 Agenda openSUSE specs integration with OBS - mtce - almost complete, only missing mtce pkg - config - complete, will work on installation - HA - complete, focus is to enable puppet - https://review.opendev.org/#/c/679686/ - https://review.opendev.org/#/c/687429/ - Community review request to core reviewers: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006479.html - NFV - complete - Fault - complete, working on installation openSUSE RPM test suite - POC: https://gitlab.com/erichcm/rpms-test-suite - install and uninstall RPMs - for testing functionality - right now testing is manual, this could be automated - configuration is done manually - intention: look puppet code and enable it instead of doing the configuration manually common infra using QEMU - try it, there is no reason we should not use this setup lvm script - suggestion: run it on real hardware Ansible and Puppet (Provisioning) - what is the status? how can we reproduce this provisioning work? - understand the puppet that is associated with each flock service, and solve for each one - where to document the findings? - send to the ML and post to the wiki, in the section for flock services kickstarts to autoYaST (Installation) - identify openSUSE packages https://github.com/marcelarosalesj/suse-starlingx/tree/master/centos-simplex-installation How can the mtce dependency on the provisioning can be stated in the spec file? or in another place? - if it depends on a configuration done by puppet, we add the puppet package as a dependency - we need more information about the dependencies Dependencies on openstack support? - SUSE is moving out from Openstack, but this doesn't necessary mean that openSUSE is going to stop the Openstack support Yocto - problems with the booting phase Marcela -------------- next part -------------- An HTML attachment was scrubbed... URL: From elio.martinez.monroy at intel.com Tue Oct 15 18:20:17 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Tue, 15 Oct 2019 18:20:17 +0000 Subject: [Starlingx-discuss] Consoolidated stx.2.0.1 maintenance RC build testing Message-ID: Consolidated Regression Automated Results Report Configuration: • Virtual Environment • 4 configurations (Simplex, Duplex, Standard, External) • ISO: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191005T150558Z/ Results: PASS 87.00 125.00 153.00 153.00 FAIL 6.00 11.00 12.00 9.00 TOTAL EXECUTED 93.00 136.00 165.00 162.00 PASS RATE 93.54 91.911 92.72 94.44 TP: • https://docs.google.com/spreadsheets/d/1r5VIUq-6z3I3nWB_Bo4a4ZnUhsVZfatPM4W8aaqg6Hc/edit?usp=sharing Ovservations: • Inestability in some scenarios because of WS resources, in some configurations passes and with larger configurations fails. • We are getting the following known issues o https://bugs.launchpad.net/starlingx/+bug/1836378 o https://bugs.launchpad.net/starlingx/+bug/1841660 o https://bugs.launchpad.net/starlingx/+bug/1835807 o https://bugs.launchpad.net/starlingx/+bug/1834512 Conclusions: • 2.0.1 Maintenance RC is healthy -----Original Message----- From: Khalil, Ghada Sent: Monday, October 7, 2019 10:44 AM To: Little, Scott ; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Subject: Re: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested Thanks Scott. Hi da/team, Can you please start the planned sanity/regression testing? Thanks, Ghada -----Original Message----- From: Scott Little [mailto:scott.little at windriver.com] Sent: Sunday, October 06, 2019 1:08 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested We finally have a good build! Happy Testing. Scott _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Tue Oct 15 20:41:53 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 15 Oct 2019 20:41:53 +0000 Subject: [Starlingx-discuss] Consoolidated stx.2.0.1 maintenance RC build testing In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BDFBF76E8@fmsmsx123.amr.corp.intel.com> Elio, thank you! Release team - Are we good to go for 2.0.1? One question: The last 3 of the 4 issues listed below are of High Importance. Should they be tagged for stx.2.0 and the fixes backported for a future 2.0.X release? brucej -----Original Message----- From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Tuesday, October 15, 2019 11:20 AM To: Khalil, Ghada ; Little, Scott ; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Subject: [Starlingx-discuss] Consoolidated stx.2.0.1 maintenance RC build testing Consolidated Regression Automated Results Report Configuration: • Virtual Environment • 4 configurations (Simplex, Duplex, Standard, External) • ISO: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191005T150558Z/ Results: PASS 87.00 125.00 153.00 153.00 FAIL 6.00 11.00 12.00 9.00 TOTAL EXECUTED 93.00 136.00 165.00 162.00 PASS RATE 93.54 91.911 92.72 94.44 TP: • https://docs.google.com/spreadsheets/d/1r5VIUq-6z3I3nWB_Bo4a4ZnUhsVZfatPM4W8aaqg6Hc/edit?usp=sharing Ovservations: • Inestability in some scenarios because of WS resources, in some configurations passes and with larger configurations fails. • We are getting the following known issues o https://bugs.launchpad.net/starlingx/+bug/1836378 o https://bugs.launchpad.net/starlingx/+bug/1841660 o https://bugs.launchpad.net/starlingx/+bug/1835807 o https://bugs.launchpad.net/starlingx/+bug/1834512 Conclusions: • 2.0.1 Maintenance RC is healthy -----Original Message----- From: Khalil, Ghada Sent: Monday, October 7, 2019 10:44 AM To: Little, Scott ; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Subject: Re: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested Thanks Scott. Hi da/team, Can you please start the planned sanity/regression testing? Thanks, Ghada -----Original Message----- From: Scott Little [mailto:scott.little at windriver.com] Sent: Sunday, October 06, 2019 1:08 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested We finally have a good build! Happy Testing. Scott _______________________________________________ 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 ada.cabrales at intel.com Tue Oct 15 20:51:07 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 15 Oct 2019 20:51:07 +0000 Subject: [Starlingx-discuss] [ Test ] Meeting notes for 10/15 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CEF9E06@FMSMSX114.amr.corp.intel.com> Agenda for 10/15 Attendees: Elio, Cristopher, Fernando, JC, Jose, JP, Maria P, Richo, Yang 1. Sanity status - Cristopher Intel Green sanities the whole week. WR https://bugs.launchpad.net/starlingx/+bug/1847324 - IPv6 DX Plus: 200.015 "board management controller sensor group read failures" raised after compute reboot https://bugs.launchpad.net/starlingx/+bug/1846287 - False alarm created on AIO. - fixed https://bugs.launchpad.net/starlingx/+bug/1847607 - IPv6 regular, 5 mins after swact calico-kube-controllers pod not getting ready There's another issue after lock/unlock a node, the system was not able to execute any command. Launchpad will be sent. 2. stx.3.0 testing updates Feature testing Tracker - https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit?usp=sharing Distributed cloud - Yang WIP - going well. Probably first round of test will be finished ~2 weeks. Backup and restore - Yang First round completed, launchpads created. There will be required to re-test once the launchpads are fixed. Fault Containerization - Fer The tests were run yesterday. One of the failed and a launchpad has been opened. The alarms are shown by horizon but cli is not working. https://bugs.launchpad.net/starlingx/+bug/1848094 Please add the tag for regression testing. Add a test for checking the FM container end point has switch to https. Upversion to train - JC Starting on duplex, got an EB to be installed using IPv6 Test on virtual env has started. Elio sent the list of tests for IPv6 New features have been added, JC will contact Yong for getting these. GPU for K8 - Richo A system already setup in China. Will try today to login remotely. Ran built an ISO for setting up a NUC, will try today too. QAT for K8 - Richo Will contact Mingyuan for updates. Redfish - Cristopher Looking better, tests in the plan have been updated (~70%) Will contact developers for getting more info and execute deeper tests. New tests cases to be created for provisioning (bulk installs). Let's work on setup an IPv6 lab for running test on this infra. Infra & Cluster monitoring - Yang Not started yet. Regression testing: Tracker - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit?usp=sharing Intel - 16% progress on manual. Automated will be started once maintenance release testing is finished WR - WIP, going well - progress around 30% Reporting out: Sending reports Tuesday and Thursday to the community. 3. stx.2.0 maintenance build Intel - automated tests are around 90% done. Checking gnocchi tests (failed almost all of them). WR is not running gnocchi tests, it's disabled by default. Elio to ask the developers for more information (Angie.Wang at windriver.com) WR - completed and found some issues already reported. Elio to consolidate the info and send the report to the mailing list. 4. PL/TL elections - no candidates No formal candidates, next step is the TSC deciding who should be taken these spots. 5. Opens None -- From erich.cordoba.malibran at intel.com Tue Oct 15 21:00:16 2019 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 15 Oct 2019 21:00:16 +0000 Subject: [Starlingx-discuss] fmClientCli and fm_core usage without keystone authentication Message-ID: <4b17090cdf7ebf796267b6e036bff4885b734959.camel@intel.com> Hi, I was playing around with fault components and I noticed that I'm able to query, create and delete alarms with fmClientCli and the fm_core python module. As I understand the `fm` cli (from python-fmclient) creates a request to keystone before connecting to the fm-rest-api to perform the operation. However this is not the case for fmClientCli, I can create an alarm with the following command. $ fmClientCli -c "blabla###100.114###set###host###host=controller-0.ntp###2019-10-14 02:28:09.5432###major###This is a dummy alarm created by hand###communication###not-applicable###Monitor and if condition persists, we are sorry###False###True###False###" and delete it with: $ fmClientCli -d "###100.114###host=controller-0.ntp" This without doing the `source /etc/platform/openrc`, I'm even allowed to create alarms from a non sysadmin user. The same case with the `fm_core` python module, which links with libfmcommon as fmClientCli does. >>> fm_core.get_by_eid("host=controller-0") ['c0d94f45-bc6d-4709-9cc6-6a937659c593###100.114###set###host###host=controller-0.ntp###2019-10-14 02:28:09.005432###major###This is a dummy alarm created by hand###communication###not-applicable###Monitor and if condition persists, we are sorry###False###True###False###'] So, I'm wondering if this an expected behavior or something is missing in libfmcommon to enable authentication. Also, do you know if the fmClientCli tool is really used? Thanks! -Erich From Ghada.Khalil at windriver.com Tue Oct 15 21:06:58 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 15 Oct 2019 21:06:58 +0000 Subject: [Starlingx-discuss] Consoolidated stx.2.0.1 maintenance RC build testing In-Reply-To: References: Message-ID: <151EE31B9FCCA54397A757BC674650F0C15CCEE0@ALA-MBD.corp.ad.wrs.com> Thanks Elio. I do have some questions below about the bugs, but they don't gate proceeding with the release/labeling. Scott, Please label the branch and update the CENGN build accordingly (move from rc to release). Please let us know when done. Thanks, Ghada -----Original Message----- From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Tuesday, October 15, 2019 2:20 PM To: Khalil, Ghada; Little, Scott; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Subject: Consoolidated stx.2.0.1 maintenance RC build testing Consolidated Regression Automated Results Report Configuration: • Virtual Environment • 4 configurations (Simplex, Duplex, Standard, External) • ISO: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/2.0/centos/20191005T150558Z/ Results: PASS 87.00 125.00 153.00 153.00 FAIL 6.00 11.00 12.00 9.00 TOTAL EXECUTED 93.00 136.00 165.00 162.00 PASS RATE 93.54 91.911 92.72 94.44 TP: • https://docs.google.com/spreadsheets/d/1r5VIUq-6z3I3nWB_Bo4a4ZnUhsVZfatPM4W8aaqg6Hc/edit?usp=sharing Ovservations: • Inestability in some scenarios because of WS resources, in some configurations passes and with larger configurations fails. • We are getting the following known issues o https://bugs.launchpad.net/starlingx/+bug/1836378 [[GK]] This was initially reported as a very intermittent issue and is currently not gating for stx.2.0. What's the frequency of occurrence? Does another lock/unlock attempt recover the issue? We need to decide if we should make this stx.2.0 gating and target a fix for a subsequent maintenance release. o https://bugs.launchpad.net/starlingx/+bug/1841660 [[GK]] Same as above. Is this an intermittent issue? What's the frequency of occurrence? Previously this was reported once and therefore is not currently marked as gating for stx.2.0. We need to decide if we should make this stx.2.0 gating and target a fix for a subsequent maintenance release. o https://bugs.launchpad.net/starlingx/+bug/1835807 [[GK]] This is already marked as stx.2.0 gating, but there is no fix in sight. It appears to be a rabbitmq issue. o https://bugs.launchpad.net/starlingx/+bug/1834512 [[GK]] This functionality was not implemented Conclusions: • 2.0.1 Maintenance RC is healthy -----Original Message----- From: Khalil, Ghada Sent: Monday, October 7, 2019 10:44 AM To: Little, Scott ; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Subject: Re: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested Thanks Scott. Hi da/team, Can you please start the planned sanity/regression testing? Thanks, Ghada -----Original Message----- From: Scott Little [mailto:scott.little at windriver.com] Sent: Sunday, October 06, 2019 1:08 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stx.2.0.1 maintenance RC build Requested We finally have a good build! Happy Testing. Scott _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Tao.Liu at windriver.com Tue Oct 15 21:43:19 2019 From: Tao.Liu at windriver.com (Liu, Tao) Date: Tue, 15 Oct 2019 21:43:19 +0000 Subject: [Starlingx-discuss] fmClientCli and fm_core usage without keystone authentication In-Reply-To: <4b17090cdf7ebf796267b6e036bff4885b734959.camel@intel.com> References: <4b17090cdf7ebf796267b6e036bff4885b734959.camel@intel.com> Message-ID: <7242A3DC72E453498E3D783BBB134C3EA4EAF9AE@ALA-MBD.corp.ad.wrs.com> Hi Erich The fmClientCli is not a customer interface and it does not require authentication. This tool is mainly used for debugging/testing and it requires access to a shell session. It is debatable whether this tool should be packaged in the load. The fm cli (from python-fmclient) that requires authentication is the fm shell and it supports the following subcommands: alarm-delete Delete an active alarm. alarm-list List all active alarms. alarm-show Show an active alarm. alarm-summary Show a summary of active alarms. event-list List event logs. event-show Show an event log. event-suppress Suppress specified Event ID's. event-suppress-list List Suppressed Event ID's event-unsuppress Unsuppress specified Event ID's. event-unsuppress-all Unsuppress all Event ID's. Tao -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Tuesday, October 15, 2019 5:00 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] fmClientCli and fm_core usage without keystone authentication Hi, I was playing around with fault components and I noticed that I'm able to query, create and delete alarms with fmClientCli and the fm_core python module. As I understand the `fm` cli (from python-fmclient) creates a request to keystone before connecting to the fm-rest-api to perform the operation. However this is not the case for fmClientCli, I can create an alarm with the following command. $ fmClientCli -c "blabla###100.114###set###host###host=controller-0.ntp###2019-10-14 02:28:09.5432###major###This is a dummy alarm created by hand###communication###not-applicable###Monitor and if condition persists, we are sorry###False###True###False###" and delete it with: $ fmClientCli -d "###100.114###host=controller-0.ntp" This without doing the `source /etc/platform/openrc`, I'm even allowed to create alarms from a non sysadmin user. The same case with the `fm_core` python module, which links with libfmcommon as fmClientCli does. >>> fm_core.get_by_eid("host=controller-0") ['c0d94f45-bc6d-4709-9cc6-6a937659c593###100.114###set###host###host=controller-0.ntp###2019-10-14 02:28:09.005432###major###This is a dummy alarm created by hand###communication###not-applicable###Monitor and if condition persists, we are sorry###False###True###False###'] So, I'm wondering if this an expected behavior or something is missing in libfmcommon to enable authentication. Also, do you know if the fmClientCli tool is really used? Thanks! -Erich _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Tue Oct 15 21:58:07 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 15 Oct 2019 21:58:07 +0000 Subject: [Starlingx-discuss] fmClientCli and fm_core usage without keystone authentication In-Reply-To: <7242A3DC72E453498E3D783BBB134C3EA4EAF9AE@ALA-MBD.corp.ad.wrs.com> References: <4b17090cdf7ebf796267b6e036bff4885b734959.camel@intel.com> <7242A3DC72E453498E3D783BBB134C3EA4EAF9AE@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BDFBF7778@fmsmsx123.amr.corp.intel.com> Bug https://bugs.launchpad.net/starlingx/+bug/1848280 filed for this issue. brucej -----Original Message----- From: Liu, Tao [mailto:Tao.Liu at windriver.com] Sent: Tuesday, October 15, 2019 2:43 PM To: Cordoba Malibran, Erich ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] fmClientCli and fm_core usage without keystone authentication Hi Erich The fmClientCli is not a customer interface and it does not require authentication. This tool is mainly used for debugging/testing and it requires access to a shell session. It is debatable whether this tool should be packaged in the load. The fm cli (from python-fmclient) that requires authentication is the fm shell and it supports the following subcommands: alarm-delete Delete an active alarm. alarm-list List all active alarms. alarm-show Show an active alarm. alarm-summary Show a summary of active alarms. event-list List event logs. event-show Show an event log. event-suppress Suppress specified Event ID's. event-suppress-list List Suppressed Event ID's event-unsuppress Unsuppress specified Event ID's. event-unsuppress-all Unsuppress all Event ID's. Tao -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Tuesday, October 15, 2019 5:00 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] fmClientCli and fm_core usage without keystone authentication Hi, I was playing around with fault components and I noticed that I'm able to query, create and delete alarms with fmClientCli and the fm_core python module. As I understand the `fm` cli (from python-fmclient) creates a request to keystone before connecting to the fm-rest-api to perform the operation. However this is not the case for fmClientCli, I can create an alarm with the following command. $ fmClientCli -c "blabla###100.114###set###host###host=controller-0.ntp###2019-10-14 02:28:09.5432###major###This is a dummy alarm created by hand###communication###not-applicable###Monitor and if condition persists, we are sorry###False###True###False###" and delete it with: $ fmClientCli -d "###100.114###host=controller-0.ntp" This without doing the `source /etc/platform/openrc`, I'm even allowed to create alarms from a non sysadmin user. The same case with the `fm_core` python module, which links with libfmcommon as fmClientCli does. >>> fm_core.get_by_eid("host=controller-0") ['c0d94f45-bc6d-4709-9cc6-6a937659c593###100.114###set###host###host=controller-0.ntp###2019-10-14 02:28:09.005432###major###This is a dummy alarm created by hand###communication###not-applicable###Monitor and if condition persists, we are sorry###False###True###False###'] So, I'm wondering if this an expected behavior or something is missing in libfmcommon to enable authentication. Also, do you know if the fmClientCli tool is really used? Thanks! -Erich _______________________________________________ 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 maria.g.perez.ibarra at intel.com Tue Oct 15 22:34:52 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 15 Oct 2019 22:34:52 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191015 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-15 (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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006502.html Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tao.Liu at windriver.com Tue Oct 15 22:37:20 2019 From: Tao.Liu at windriver.com (Liu, Tao) Date: Tue, 15 Oct 2019 22:37:20 +0000 Subject: [Starlingx-discuss] fmClientCli and fm_core usage without keystone authentication In-Reply-To: <9A85D2917C58154C960D95352B22818BDFBF7778@fmsmsx123.amr.corp.intel.com> References: <4b17090cdf7ebf796267b6e036bff4885b734959.camel@intel.com> <7242A3DC72E453498E3D783BBB134C3EA4EAF9AE@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BDFBF7778@fmsmsx123.amr.corp.intel.com> Message-ID: <7242A3DC72E453498E3D783BBB134C3EA4EAF9E6@ALA-MBD.corp.ad.wrs.com> If the decision is to remove the fmClientCli utility from the image, one or two dependencies will also need to be updated (i.e. IMA appraisal failure event is raised using this tool). Tao -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Tuesday, October 15, 2019 5:58 PM To: Liu, Tao; Cordoba Malibran, Erich; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] fmClientCli and fm_core usage without keystone authentication Bug https://bugs.launchpad.net/starlingx/+bug/1848280 filed for this issue. brucej -----Original Message----- From: Liu, Tao [mailto:Tao.Liu at windriver.com] Sent: Tuesday, October 15, 2019 2:43 PM To: Cordoba Malibran, Erich ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] fmClientCli and fm_core usage without keystone authentication Hi Erich The fmClientCli is not a customer interface and it does not require authentication. This tool is mainly used for debugging/testing and it requires access to a shell session. It is debatable whether this tool should be packaged in the load. The fm cli (from python-fmclient) that requires authentication is the fm shell and it supports the following subcommands: alarm-delete Delete an active alarm. alarm-list List all active alarms. alarm-show Show an active alarm. alarm-summary Show a summary of active alarms. event-list List event logs. event-show Show an event log. event-suppress Suppress specified Event ID's. event-suppress-list List Suppressed Event ID's event-unsuppress Unsuppress specified Event ID's. event-unsuppress-all Unsuppress all Event ID's. Tao -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Tuesday, October 15, 2019 5:00 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] fmClientCli and fm_core usage without keystone authentication Hi, I was playing around with fault components and I noticed that I'm able to query, create and delete alarms with fmClientCli and the fm_core python module. As I understand the `fm` cli (from python-fmclient) creates a request to keystone before connecting to the fm-rest-api to perform the operation. However this is not the case for fmClientCli, I can create an alarm with the following command. $ fmClientCli -c "blabla###100.114###set###host###host=controller-0.ntp###2019-10-14 02:28:09.5432###major###This is a dummy alarm created by hand###communication###not-applicable###Monitor and if condition persists, we are sorry###False###True###False###" and delete it with: $ fmClientCli -d "###100.114###host=controller-0.ntp" This without doing the `source /etc/platform/openrc`, I'm even allowed to create alarms from a non sysadmin user. The same case with the `fm_core` python module, which links with libfmcommon as fmClientCli does. >>> fm_core.get_by_eid("host=controller-0") ['c0d94f45-bc6d-4709-9cc6-6a937659c593###100.114###set###host###host=controller-0.ntp###2019-10-14 02:28:09.005432###major###This is a dummy alarm created by hand###communication###not-applicable###Monitor and if condition persists, we are sorry###False###True###False###'] So, I'm wondering if this an expected behavior or something is missing in libfmcommon to enable authentication. Also, do you know if the fmClientCli tool is really used? Thanks! -Erich _______________________________________________ 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 maria.g.perez.ibarra at intel.com Tue Oct 15 23:44:26 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 15 Oct 2019 23:44:26 +0000 Subject: [Starlingx-discuss] [ Regression testing - stx3.0 ] Report for 10/15/2019 Message-ID: StarlingX 3.0 Release Status: ISO: BUILD_ID="20191011T013000Z" from (link) ---------------------------------------------------------------------- MANUAL EXECUTION ---------------------------------------------------------------------- Overall Results: Total = 274 Pass = 61 Fail = 3 Blocked = 0 Not Run = 208 Obsolete = 2 Deferred = 0 Total executed = 84 Pass Rate = 95.3% Formula used : Pass Rate = (pass * 100) / (pass + fail) --------------------------------------------------------------------------- AUTOMATED ROBOT - INTEL --------------------------------------------------------------------------- Overall Results: Total = 202 Pass = 18 Fail = 0 Blocked = 15 Not Run = 169 Obsolete = 0 Deferred = 0 Total executed = 0 Pass Rate = 100% Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- AUTOMATED PYTEST - WR --------------------------------------------------------------------------- Overall Results: Total = 467 Pass = 0 Fail = 0 Blocked = 0 Not Run = 467 Obsolete = 0 Deferred = 0 Total executed = 0 Pass Rate = Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- BUGS Missing information --------------------------------------------------------------------------- For more detail of the tests: https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 Regards! Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Oct 16 01:41:55 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 16 Oct 2019 01:41:55 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Oct 9/2019 Message-ID: <151EE31B9FCCA54397A757BC674650F0C15CCFDB@ALA-MBD.corp.ad.wrs.com> Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - October 9 2019 Election - Reviewed voting members of the release team captured in the governance repo and agreed that the list was good stx.2.0 - Build was successful on October 4. - Sanity was good. - Regression is still running. No issues have been noted. Expect to deliver report by Tuesday October 15 - Open Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2.0 - Count: 7 - Action: ping PLs to see if issues are actively being worked and if they should continue to be gating for stx.2.0 stx.3.0 - Feature Status - https://docs.google.com/spreadsheets/d/1ZFR-9-riwhIwiBYBmWmi1qOVyHtgJ8Xk_FaF2jp5rY0/edit#gid=1010323020 - Done: 4 - Dev In Progress: 8 (2 are prep) - Test In Progress: 3 - General Risk: - MS-3 scheduled for Oct 18 and still a large % of features still has outstanding code to merge - Feature-specific Risks: - Upversion to Train: No projected dates provided. Some items are still unresourced. Unclear whether this can land. - Regression Test - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 - Completion Rate: 16% - Feature Test - https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit#gid=968103774 - Completion Rate: 60% stx.4.0 - Discussed at the TSC call to have stx.4.0 on the agenda for the upcoming Open Infra Summit in Nov - Openstack Ussuri tentative release schedule is available: https://releases.openstack.org/ussuri/schedule.html - Ghada to work out tentative dates for stx.4.0 (based on current formula to lag openstack by ~6 weeks) - https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 - one more retrospective / continuous improvement item to consider factoring into the release plan - unit tests! - Bill will bring this up on the community call From cindy.xie at intel.com Wed Oct 16 02:47:39 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 16 Oct 2019 02:47:39 +0000 Subject: [Starlingx-discuss] https://review.opendev.org/#/c/652000/3 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F36087CD9@SHSMSX104.ccr.corp.intel.com> Anybody has any idea why this patch was stuck there but with all required +1 and +2 already? Any issues in our CI pipeline? Cindy Xie IAGS [StarlingX] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 11582 bytes Desc: image002.png URL: From fungi at yuggoth.org Wed Oct 16 03:08:52 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 16 Oct 2019 03:08:52 +0000 Subject: [Starlingx-discuss] https://review.opendev.org/#/c/652000/3 In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F36087CD9@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F36087CD9@SHSMSX104.ccr.corp.intel.com> Message-ID: <20191016030852.dcmrrycynmd2adcy@yuggoth.org> On 2019-10-16 02:47:39 +0000 (+0000), Xie, Cindy wrote: > Anybody has any idea why this patch was stuck there but with all > required +1 and +2 already? Any issues in our CI pipeline? It depends (via Git parentage) on https://review.opendev.org/686456 which hasn't been approved (or even reviewed) yet. Zuul is unable to merge a change until all its dependencies also merge, so won't enqueue it if its dependencies aren't yet ready to themselves get enqueued. -- 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 yan.chen at intel.com Wed Oct 16 05:42:47 2019 From: yan.chen at intel.com (Chen, Yan) Date: Wed, 16 Oct 2019 05:42:47 +0000 Subject: [Starlingx-discuss] Train upgrade for openstack clients In-Reply-To: <72AD03D27224C74982BE13246D75B39739A64833@SHSMSX103.ccr.corp.intel.com> References: <72AD03D27224C74982BE13246D75B39739A64833@SHSMSX103.ccr.corp.intel.com> Message-ID: <72AD03D27224C74982BE13246D75B39739A651A3@SHSMSX103.ccr.corp.intel.com> Hi, I'm now trying to upgrade the openstack clients installed on StarlingX to Train version. Currently I see the clients are Stein version, but the puppet packages (for those modules that we need to config on StarlingX host) are still old versions. [See the list below.] But for Train, I met a problem when I wanted to upgrade python-openstackclient/keystone to Train (4.0.0), the old puppet packages cannot work with Train clients and failed when running puppet-manifest-apply.sh. See from Stein keystone log, some of the deprecated cmds and options are planned to be removed in Train. If we want to make Train clients work, we may need to do the following steps: 1. Upgrade puppet itself (required 5.x by Train) 2. Upgrade all the OpenStack related puppet packages accordingly, and update StarlingX patches. 3. If flock puppet pkgs are based on puppet 4.8.2, we also need to upgrade our code. 4. If other puppet pkgs are based on puppet 4.8.2, we also need to upgrade those pkgs. So is it possible that we keep on using Stein clients with limited test now (need test with Train images, but suppose old functions should still work)? Here's the list of the puppet packages and StarlingX patches (for Stein it should be 14.1.0 - 14.4.0, and for Train 15.0.0 - 15.4.0): Pkg Current Version Train Upgrade to Meta Patch Patch puppet 4.8.2 5.x 2 5 puppet-keystone 11.3.0 15.x 6 5 puppet-oslo 11.3.0 15.x 3 2 puppet-openstacklib 11.5.0 15.x 2 1 puppet-horizon 11.5.0 15.x 2 1 puppet-barbican 11.3.0 15.x 0 0 Stein Keystone client logs: keystone:log 2019-10-10 10:04:44.050 111346 WARNING keystone.server.flask.request_processing.middleware.auth_context [-] The use of the '[DEFAULT] admin_token' configurationoption presents a significant security risk and should not be set. This option is deprecated in favor of using 'keystone-manage bootstrap' and will be removed in a future release. Yan -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Wed Oct 16 08:02:01 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Wed, 16 Oct 2019 03:02:01 -0500 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <4417ee$bqm2lh@fmsmga006.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191016T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-apiserver:v1.16.0 k8s.gcr.io/kube-controller-manager:v1.16.0 k8s.gcr.io/kube-proxy:v1.16.0 k8s.gcr.io/kube-scheduler:v1.16.0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From cindy.xie at intel.com Wed Oct 16 13:53:35 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 16 Oct 2019 13:53:35 +0000 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F36086E35@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F35F28711@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F36086E35@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F36088FA4@SHSMSX104.ccr.corp.intel.com> Agenda & notes  for 10/16 meeting: . Ceph containerization     update (Tingjie) https://review.opendev.org/#/c/681457/ this is for Helm chart definition, can be review now. https://review.opendev.org/#/c/687340/ for Helm overrides framework, need to extend later. verified in AIO and multi-node provision.  configuration needs to be override according to STX parameters. Martin working on this for parameters to align w/ the native deployment. for stx.3.0: only to merge the implantation for Helm chart and override framework. and rook-plugin which support sysinv, this can co-exist w/ current native ceph deployment.  test case development is in progress, Tingjie will sync with Fernando.  for sysinv, still need to working on patches, not ready for upload/review. AR: Tingjie to send email to the mailing list for the current status & planning for include partial implementation without impacting the native Ceph functionality.    . Debranding update (Saul) Starting from the tools repo, the tools in the build area to debrand the mirroring process. Part of this is for ease of use for build steps. Very early stage. Not fit in stx.3.0 scope. https://storyboard.openstack.org/#!/story/2006387, call volunteer from the community.  . CentOS 8 upgrade planning     (Cindy) CentOS 8.0 2 stories created: https://storyboard.openstack.org/#!/story/2006728, the kernel inside CentOS 8 is 4.18, there is no RT kernel.  https://storyboard.openstack.org/#!/story/2006729 Shuai is working on new kernel onto build system. Need to understand each patches. there was an earlier analysis for kernel patches available. AR: Saul please share this analysis to Shuai. against 4.19 kernel some long time ago. See https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAugOWXMjB7VIrfc/edit#gid=311578025 Tab Kernel Patches Details https://github.com/xe1gyq/linux/commits/v4.19 https://github.com/xe1gyq/linux/commits/v4.18 AR: Shuai to provide an Excel sheet to compare RPM/sRPM in StarlingX and in CentOS 8.0 . Opens - none _____________________________________________ From: Xie, Cindy Sent: Tuesday, October 15, 2019 9:39 PM To: Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; 'Rowsell, Brent' Subject: RE: Weekly StarlingX non-OpenStack distro meeting Agenda: - Ceph containerization update (Tingjie) - Debranding update (Saul) - CentOS 8 upgrade planning (Cindy) - Opens Cindy Xie IAGS http://starlingx.io/ -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, October 16, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . 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 From Tao.Liu at windriver.com Wed Oct 16 15:27:28 2019 From: Tao.Liu at windriver.com (Liu, Tao) Date: Wed, 16 Oct 2019 15:27:28 +0000 Subject: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Message-ID: <7242A3DC72E453498E3D783BBB134C3EA4EAFB8F@ALA-MBD.corp.ad.wrs.com> Hi Docs Team, Please add Distributed Cloud Configuration Guide to StarlingX R3.0 Installation. Regards, Tao Liu, Member of Technical Staff, Engineering,, Wind River direct 613.963.1413 fax: 613.492.7870 skype: tao_at_home 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Distributed Cloud Configuration Guide.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 25216 bytes Desc: Distributed Cloud Configuration Guide.docx URL: From abraham.arce.moreno at intel.com Wed Oct 16 16:05:26 2019 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Wed, 16 Oct 2019 16:05:26 +0000 Subject: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 In-Reply-To: <7242A3DC72E453498E3D783BBB134C3EA4EAFB8F@ALA-MBD.corp.ad.wrs.com> References: <7242A3DC72E453498E3D783BBB134C3EA4EAFB8F@ALA-MBD.corp.ad.wrs.com> Message-ID: Thanks Tao for sharing, We are taking this guide to replicate the setup in our labs and translate to RST format. We will add you as reviewer, feel free to add as many people as required. Best Regards Docs Team From: Liu, Tao Sent: Wednesday, October 16, 2019 10:27 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi Docs Team, Please add Distributed Cloud Configuration Guide to StarlingX R3.0 Installation. Regards, Tao Liu, Member of Technical Staff, Engineering,, Wind River direct 613.963.1413 fax: 613.492.7870 skype: tao_at_home 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Oct 16 16:21:30 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 16 Oct 2019 16:21:30 +0000 Subject: [Starlingx-discuss] Community Call (Oct 16, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B05026@ALA-MBD.corp.ad.wrs.com> >From today's call... standing topics - any Gerrit reviews that need attention? - OpenStack Train upgrade stuff, see Zhipeng's email: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006479.html - reviews in the HA repo seem to be a bit stuck lately - need to put some focus there - some have +2s yet have been waiting for a week to get the second +2, assuming that's appropriate - https://review.opendev.org/#/q/project:starlingx/ha+status:open - metal: https://review.opendev.org/#/c/678627/ - sanity - any reds since last call? - nope, good work! - any unanswered calls for assistance on the mailing list? - maybe this one: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006467.html - AR: Frank/Stefan to respond to Volker's question election - there will be an election for the flock-services PL role - qualified voters will receive an email inviting them to vote - the emails will be sent out on Sunday night, so you will have your email by Monday - it'll go to your preferred email address - community members that are not on the current list should send their info to the election officials to be added to the electorate - to be confirmed by the current PL and the TSC - this is captured in the projects.yaml file: https://opendev.org/starlingx/governance/src/branch/master/reference/tsc/projects.yaml - candidates: https://opendev.org/starlingx/election/src/branch/master/candidates/2019_H2/flock-services/pl - all other PLs, TLs and TSC members that ran without opposition will be acclaimed - cases where no PL, TL or both, ran, have been brought to the TSC for next steps unit test - how we can increase our coverage - brute force - don't allow any commits without unit test(s) - but we have to lower the bar for doing this - not much point making unit tests mandatory if the committer doesn't know how to write the unit test - do we have numbers that tell us how much coverage we have - yes, those exist - could we draw a heat map to see where the bugs are landing? - how do we do that? - Ada will help here - who should prime this - test or dev? - one of the goals is to not continue to accumulate technical debt - should have sufficient framework in place so that this is manageable - AR: Bill to provide an update on this in next Community Call stx.3.0 MS-3 milestone - MS-3 is currently scheduled this week. There is risk to meeting this milestone - Status from last week's release meeting - https://docs.google.com/spreadsheets/d/1ZFR-9-riwhIwiBYBmWmi1qOVyHtgJ8Xk_FaF2jp5rY0/edit#gid=1010323020 - Done: 4 - Dev In Progress: 8 (2 are prep, so not required for MS-3) - Test In Progress: 3 - General Risk: - MS-3 scheduled for Oct 18 and still a large % of features still has outstanding code to merge - Feature-specific Risks: - Upversion to Train: No projected dates provided. Some items are still unresourced. Unclear whether this can land. - Call to PLs and teams to look at their feature status and share their plans in tomorrow's release meeting Open AR Updates - Oct 9, 2019 -- Dean -- present an overview of cool things you can do in Gerrit to watch/monitor your reviews (sneak preview: https://opendev.org/x/gerrit-dash-creator) - Oct 16: in progress - will target 'fun to show' stuff for next week - Oct 9, 2019 -- Frank -- see if the CENGN access can be opened up to other folks besides Scott & Don so we've got more options to get stuff like this done - Oct 16: topic for tomorrow's build meeting - Sep 11, 2019 -- Ildiko -- look into documenting the process of having documentation part of the development process to the contributor guide - Oct 16: possible topic for upcoming Community meeting - Sep 11, 2019 -- Abraham/Build -- sort out how/when to finish this off the renaming of the to-be-renamed system-client (nee: cgcs-client) - Oct 16: no update, likely still in the 'help wanted' phase, not likely to get done in 3.0 - Sep 11, 2019 -- Bruce -- identify the feature documentation gaps - Oct 16: in progress - May 8, 2019 -- Frank -- follow up with CENGN on storage for really large files for reference in Launchpads - Oct 16: in progress, Frank getting a demo this week -----Original Message----- From: Zvonar, Bill Sent: Tuesday, October 15, 2019 10:05 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: Community Call (Oct 16, 2019) Hi all, reminder of the Community call tomorrow. Please feel free to add new topics to the agenda at [0]. Currently, we have these topics... - next week's election for the flock-services PL role - unit test - how can we increase our coverage - and the usual standing topics... - Gerrit reviews that need attention - Red sanity learnings - unanswered requests for help in the mailing list - open AR review 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=20191016T1400 From bruce.e.jones at intel.com Tue Oct 15 13:38:24 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 15 Oct 2019 13:38:24 +0000 Subject: [Starlingx-discuss] distro.openstack meeting Oct 15 2019 Message-ID: <9A85D2917C58154C960D95352B22818BDFBF7008@fmsmsx123.amr.corp.intel.com> 10/15/2019 meeting TL;DR: The Train update is nearing completion. We need reviewers and Cores to review the changes below. Yong to provide the team with info on the puppet issues seen in upgrading the OpenStack clients. The team asks Chris F and Brent to read the thread below regarding "time to detect a failed VM" and provide any background or history they can. Yong will be the new PL for the sub-project, no nominations for the TL role were made. * Train update status - Zhipeng https://storyboard.openstack.org/#!/story/2006544 * Basic deployment and VM creation/remove test pass in AIO setup! * Eng build out for testing (Sanity requested) - one issue found and fixed, new image ready for Sanity * Current status summarized as below. * 1) Openstack upgrade ? Finished 13 services upgrade, including nova, neutron, keystone, cinder, glance, placement, aodh, ironic, panko, barbican, ceilometer, heat, horizon. * 2) Openstack-helm/helm-infra upgrade ? Upgrade openstack-helm to below version. 13 patches removed * Are these patches still in the stx-upstream repo? Patches look like they are removed in https://review.opendev.org/#/c/683886/ * commit 82c72367c85ca94270f702661c7b984899c1ae38 //Date: Sat Sep 14 06:40:03 2019 +0000 ? Upgrade openstack-helm-infra to below version. 1 patch removed * commit c9d6676bf9a5aceb311dc31dadd07cba6a3d6392 //Date: Mon Sep 16 17:15:12 2019 +0000 * 6 patches submitted for review, your comments are appreciated, thanks! ? https://review.opendev.org/#/c/683886/ ? https://review.opendev.org/#/c/683910/ ? https://review.opendev.org/#/c/684166/ ? https://review.opendev.org/#/c/687441/ ? https://review.opendev.org/#/c/687197/ ? https://review.opendev.org/#/c/688105/ * Test plan status - Yong ? Testing to include previous test plan plus ipv6 * Openstack clients - some of them depend on puppet versions that are not in CentOS 7 but are in CentOS 8. ? Yong to send details to Dean * Detection of a failed VM - re-architecture discussion * Victor has defined a set of performance tests (see the spec) and the Intel team has run then. * The overall resutls look good except for two issues, one of which is "time to detect a failed VM". StarlingX performance is poor on a performance test to measure this KPI relative to the original seed code. * We had an internal discussion with the Intel Nova team - here are the results. We are looking for @Chris and @Brent to provide some missing history of this work. * Eric Fried wrote: ? [Later] After skimming through the nova code, I can see where we're reacting to certain libvirt.VIR_DOMAIN_EVENT_*s by sending lifecycle events to the handler registered by the compute manager. That handler is set up to send notifications, and also to take actions in special cases. ? I'm only guessing, but I suspect the existing "special cases" are not something we necessarily want to be building on, so I kind of doubt the "take some action" part of the chain would be something nova would want to upstream. ? However, I think you could definitely make a case for adding support for a new lifecycle event type corresponding to one or more additional VIR_DOMAIN_EVENT_*s, and include those in notifications. At that point, an external orchestrator (is that what StarlingX is?) can listen for those notifications and react accordingly (by destroying the instance, rebooting it, whatever). ? I also think you could make a case for changing the VM's state when one of these new transitions occurs; though I'm not sure whether a new vm_state would be okay, or whether you would just have to use _STOPPED. ? I think the best way forward here is to propose a blueprint & spec to hammer out the details of the above. I think it should be a fairly straightforward thing to get technical agreement on. And resurrecting the code itself would be no big deal. * Yongli wrote: ? That all related to handle KVM server CRASHED status, and recover the compute, but depending on Tic VIM software. ? It contains following sub parts ? * 2d6afc9 US80863: Port KVM failure detection and recovery ? * f383c58 US80977: Fix handling of KVM failure in mitaka ? * 8cfdb1a CGTS-7054: synchronize _sync_instance_power_state() from LifeCycle events ? * cf95427 CGTS-7054: VMs remain in shutoff state after killing kvm process. ? BTW: weird, these features listed in Cinder section in PTG of Stein: https://etherpad.openstack.org/p/nova-ptg-stein * Dean wrote: ? For the record, this is in the released patch files as [0] which was a squash of at least six prior commits in earlier Titanium releases: ? * 0018.01 R3: 2d6afc9 Port KVM failure detection and recovery ? * 0018.01.01 R2: 7063b69 VIM: Refactor KVM failure detection and recovery ? * 0018.02 80cfc70 add audit to clean up orphan instances ? * 0018.02.01 6138f54c add audit to clean up orphan instances ? * 0018.02.02 5342042f Trouble destroying illegitimate instance ? * 0018.02.03 ac7b182d improve orphan audit robustness ? * 0018.03 f383c58 Fix handling of KVM failure in mitaka ? * 0018.04 8cfdb1a synchronize _sync_instance_power_state() from LifeCycle events ? * 0018.05 cf95427 VMs remain in shutoff state after killing kvm process. ? * 0018.06 d20e24a nova: Bug 272: orphan vm is not removed ? I have broken out the 0018 patch as shown above in [1] as 0018.XX[.YY]-* so they can be considered separately as required. ? Mario's patch appears to be basically 0018.01, 0018.03, 0018.04 and 0018.05. ? [0] https://github.com/starlingx-staging/stx-nova/blob/stx/old-master/stx-patches/0018-primary-KVM-failure-detection-recovery-and-orphan-in.patch ? [1] https://github.com/dtroyer/stx-nova/tree/stx-patch/stx-patches * No election is needed. Yong Hu will be the new PL for this project. No self-nominations for the TL position were made. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Oct 16 18:40:16 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 16 Oct 2019 18:40:16 +0000 Subject: [Starlingx-discuss] Voters for PL/TL election... Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B05280@ALA-MBD.corp.ad.wrs.com> As discussed on the Community Call today, there will be an election next week for the flock-services repo. Below is the (alphabetized) list of contributors who are currently eligible to vote on this position. Eligible voters will receive an invitation to vote this Sunday evening once the voting period begins. If you're not on this list but consider yourself to have contributed to this sub-project in the last 12 months and hence should be eligible to vote for this position, please say so here or directly to the election team (Ildiko, Bruce & myself). Bill... - al.bailey at windriver.com - alex.kozyrev at windriver.com - andy.ning at windriver.com - angie.wang at windriver.com - barton.wensley at windriver.com - bin.qian at windriver.com - chris.friesen at windriver.com - daniel.badea at windriver.com - david.sullivan at windriver.com - don.penney at windriver.com - dtroyer at gmail.com - elena.taivan at windriver.com - eric.barrett at windriver.com - eric.macdonald at windriver.com - erich.cordoba.malibran at intel.com - guozhen.she at intel.com - haochuan.z.chen at intel.com - jaegerandi at gmail.com - james.gauld at windriver.com - jason.mckenna at windriver.com - jerry.sun at windriver.com - john.kung at windriver.com - junbo85.li at gmail.com - kevin.smith at windriver.com - kristine.bujold at windriver.com - lachlan.plant at windriver.com - lihang0166 at fiberhome.com - lijunjie at cloudin.cn - lvcy at fiberhome.com - ma.lei at 99cloud.net - marcela.a.rosales.jimenez at intel.com - matt.peters at windriver.com - mingyuan.qi at intel.com - ovidiu.poncea at windriver.com - ran1.an at intel.com - scott.little at windriver.com - sgw at linux.intel.com - srifenbark at gmail.com - stefan.dinescu at windriver.com - steven.webster at windriver.com - sxmatch1986 at gmail.com - tao.liu at windriver.com - tee.ngo at windriver.com - teresa.ho at windriver.com - tyler.smith at windriver.com - wei.zhou at windriver.com - wzj334965317 at outlook.com - xbyan at fiberhome.com - xiefp88 at sina.com - yan.chen at intel.com - zhanglf01 at inspur.com - zhangzhaoshan at inspur.com - zhaolong at inspur.com - zhaowei7146 at fiberhome.com - zhipengs.liu at intel.com - zqhsh527 at 163.com -----Original Message----- From: Zvonar, Bill Sent: Wednesday, October 9, 2019 1:56 PM To: 'starlingx-discuss at lists.starlingx.io' Cc: Ildiko Vancsa ; 'Jones, Bruce E' Subject: Voters for PL/TL election... As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). Bill... build - don.penney at windriver.com - scott.little at windriver.com - dtroyer at gmail.com - al.bailey at windriver.com - tyler.smith at windriver.com - daniel.badea at windriver.com - sgw at linux.intel.com - erich.cordoba.malibran at intel.com - stefan.dinescu at windriver.com - ran1.an at intel.com - tao.liu at windriver.com - joseph.richard at windriver.com - felipe.de.jesus.ruiz.garcia at intel.com - angie.wang at windriver.com - Kristine.Bujold at windriver.com - jesus.ornelas.aguayo at intel.com - lihaijing at fiberhome.com - jason.mckenna at windriver.com - zhangyangyang at unionpay.com - jerry.sun at windriver.com - alex.kozyrev at windriver.com - steven.webster at windriver.com - jaegerandi at gmail.com - longx.li at intel.com - john.kung at windriver.com - maria.yousaf at windriver.com - zhipengs.liu at intel.com - lihang0166 at fiberhome.com - zhiguox.zhang at intel.com - bin.yang at intel.com - iwienand at redhat.com - marcela.a.rosales.jimenez at intel.com - tee.ngo at windriver.com - haochuan.z.chen at intel.com - caoran at fiberhome.com - zhang.kunpeng at 99cloud.net - Paul-Emile.Element at windriver.com config - angie.wang at windriver.com - tingjie.chen at intel.com - kevin.smith at windriver.com - ovidiu.poncea at windriver.com - bin.qian at windriver.com - joseph.richard at windriver.com - Kristine.Bujold at windriver.com - al.bailey at windriver.com - andy.ning at windriver.com - david.sullivan at windriver.com - daniel.badea at windriver.com - zhipengs.liu at intel.com - tao.liu at windriver.com - haochuan.z.chen at intel.com - lihang0166 at fiberhome.com - stefan.dinescu at windriver.com - ran1.an at intel.com - sgw at linux.intel.com - teresa.ho at windriver.com - eric.macdonald at windriver.com - alex.kozyrev at windriver.com - erich.cordoba.malibran at intel.com - scott.little at windriver.com - tee.ngo at windriver.com - tyler.smith at windriver.com - bin.yang at intel.com - john.kung at windriver.com - jaegerandi at gmail.com - mingyuan.qi at intel.com - eric.barrett at windriver.com - zhang.kunpeng at 99cloud.net - wei.zhou at windriver.com - steven.webster at windriver.com - jerry.sun at windriver.com - dtroyer at gmail.com - barton.wensley at windriver.com - matt.peters at windriver.com - zhu.boxiang at 99cloud.net - don.penney at windriver.com - James.Gauld at windriver.com - junbo85.li at gmail.com - chris.friesen at windriver.com - marcela.a.rosales.jimenez at intel.com - cheng1.li at intel.com - chenjie.xu at intel.com - allain.legacy at windriver.com - yan.chen at intel.com - elena.taivan at windriver.com - yizhoux.xu at intel.com - iwienand at redhat.com - irina.mihai at windriver.com - wzj334965317 at outlook.com - ma.lei at 99cloud.net - eric.zhang at windriver.com - Paul-Emile.Element at windriver.com - zhangyangyang at unionpay.com - daniel.chavolla at windriver.com - lachlan.plant at windriver.com - srifenbark at gmail.com - shoaib.nasir at windriver.com - singh.surya64mnnit at gmail.com containers - al.bailey at windriver.com - kevin.smith at windriver.com - zhipengs.liu at intel.com - ran1.an at intel.com distcloud - andy.ning at windriver.com - tyler.smith at windriver.com - scott.little at windriver.com - xiefp88 at sina.com - jaegerandi at gmail.com - dtroyer at gmail.com - tao.liu at windriver.com - don.penney at windriver.com - al.bailey at windriver.com - Kristine.Bujold at windriver.com - cao.yuan at 99cloud.net - wzj334965317 at outlook.com - alex.kozyrev at windriver.com - lachlan.plant at windriver.com - junbo85.li at gmail.com - srifenbark at gmail.com - barton.wensley at windriver.com distro - al.bailey at windriver.com - alex.kozyrev at windriver.com - jerry.sun at windriver.com - erich.cordoba.malibran at intel.com - daniel.badea at windriver.com - Kristine.Bujold at windriver.com - scott.little at windriver.com - jaegerandi at gmail.com - bin.qian at windriver.com - zhipengs.liu at intel.com - ran1.an at intel.com - eric.macdonald at windriver.com - john.kung at windriver.com - andy.ning at windriver.com - dtroyer at gmail.com - stefan.dinescu at windriver.com - bin.yang at intel.com - don.penney at windriver.com - eric.barrett at windriver.com - barton.wensley at windriver.com - junbo85.li at gmail.com - angie.wang at windriver.com - teresa.ho at windriver.com - sgw at linux.intel.com - tao.liu at windriver.com - zhiguox.zhang at intel.com - steven.webster at windriver.com - chenjie.xu at intel.com - James.Gauld at windriver.com - longx.li at intel.com - tyler.smith at windriver.com - chenlx at fiberhome.com - corvus at inaugust.com - chris.friesen at windriver.com - haochuan.z.chen at intel.com - daniel.chavolla at windriver.com - wei.zhou at windriver.com - ovidiu.poncea at windriver.com - joseph.richard at windriver.com - jason.mckenna at windriver.com - louie.kwan at windriver.com - Paul-Emile.Element at windriver.com - zhangyangyang at unionpay.com - tee.ngo at windriver.com - ma.lei at 99cloud.net docs - bruce.e.jones at intel.com - jaegerandi at gmail.com - chenlx at fiberhome.com - lihang0166 at fiberhome.com - srifenbark at gmail.com - xiefp88 at sina.com - liuyamin at fiberhome.com - lipan7195 at fiberhome.com - fungi at yuggoth.org - curtis at serverascode.com - iwienand at redhat.com - erich.cordoba.malibran at intel.com - li.xiaoli at 99cloud.net - zhang.kunpeng at 99cloud.net - dtroyer at gmail.com flock-services - tyler.smith at windriver.com - david.sullivan at windriver.com - Kristine.Bujold at windriver.com - al.bailey at windriver.com - jaegerandi at gmail.com - haochuan.z.chen at intel.com - dtroyer at gmail.com - teresa.ho at windriver.com - junbo85.li at gmail.com - ovidiu.poncea at windriver.com - yan.chen at intel.com - sgw at linux.intel.com - steven.webster at windriver.com - zhipengs.liu at intel.com - don.penney at windriver.com - eric.barrett at windriver.com - erich.cordoba.malibran at intel.com - scott.little at windriver.com - john.kung at windriver.com - wzj334965317 at outlook.com - tao.liu at windriver.com - stefan.dinescu at windriver.com - wei.zhou at windriver.com - James.Gauld at windriver.com - angie.wang at windriver.com - guozhen.she at intel.com - bin.qian at windriver.com - zqhsh527 at 163.com - andy.ning at windriver.com - mingyuan.qi at intel.com - xiefp88 at sina.com - daniel.badea at windriver.com - chris.friesen at windriver.com - elena.taivan at windriver.com - jerry.sun at windriver.com - marcela.a.rosales.jimenez at intel.com - xbyan at fiberhome.com - ran1.an at intel.com - alex.kozyrev at windriver.com - eric.macdonald at windriver.com - matt.peters at windriver.com - barton.wensley at windriver.com - kevin.smith at windriver.com - zhanglf01 at inspur.com - lachlan.plant at windriver.com - zhaowei7146 at fiberhome.com - lvcy at fiberhome.com - sxmatch1986 at gmail.com - ma.lei at 99cloud.net - lijunjie at cloudin.cn - jason.mckenna at windriver.com - srifenbark at gmail.com - tee.ngo at windriver.com - zhangzhaoshan at inspur.com - zhaolong at inspur.com - lihang0166 at fiberhome.com multios networking networking openstack_distro release security test - lihang0166 at fiberhome.com - dtroyer at gmail.com - erich.cordoba.malibran at intel.com - yang.liu at windriver.com - al.bailey at windriver.com - juan.p.gomez at intel.com - anujeyan.manokeran at windriver.com - maria.yousaf at windriver.com - peng.peng at windriver.com - marvin.huang at windriver.com [0] https://etherpad.openstack.org/p/stx-status From lw2dht at gmail.com Wed Oct 16 19:33:25 2019 From: lw2dht at gmail.com (Mariano Ucha) Date: Wed, 16 Oct 2019 16:33:25 -0300 Subject: [Starlingx-discuss] Integration Openstack and SRIOV - Cannot deploy a VM Message-ID: <5da77085.1c69fb81.4c052.65b4@mx.google.com> Hi guys, I’m trying to deploy a VM on a baremetal ST 2.0 STX AIO. I have a dual nic port with SRIOV Support. I didn’t find a documentation how to configure at openstack level in theDeployment guide. I use some config that i found in the wiki Network https://wiki.openstack.org/wiki/StarlingX/Networking I can configure networks, subnet and ports. But when i deploy a VM i got this error: Message Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures for instance add8e0d3-4ce0-4611-8f26-0032484fb8f8. Code 500 Details File "/var/lib/openstack/lib/python2.7/site-packages/nova/conductor/manager.py", line 627, in build_instances raise exception.MaxRetriesExceeded(reason=msg) Created Oct. 16, 2019, 4:06 p.m. I found more detailed error in nova-conductor 2019-10-16 19:06:57.076 1 ERROR nova.scheduler.utils [req-7f352cf5-d9b4-4478-abfc-f68d7298ea85 bc5015570893422bb07d9292ddfa1edc 77eaa44ce5124f6685fe27ac91758427 - default default] [instance: add8e0d3-4ce0-4611-8f26-0032484fb8f8] Error from last host: controller-0 (node controller-0): [u'Traceback (most recent call last):\n', u' File "/var/lib/openstack/lib/python2.7/site-packages/nova/compute/manager.py", line 1984, in _do_build_and_run_instance\n filter_properties, request_spec)\n', u' File "/var/lib/openstack/lib/python2.7/site-packages/nova/compute/manager.py", line 2354, in _build_and_run_instance\n instance_uuid=instance.uuid, reason=six.text_type(e))\n', u'RescheduledException: Build of instance add8e0d3-4ce0-4611-8f26-0032484fb8f8 was re-scheduled: Binding failed for port 3bfaeb9c-428c-45ed-9879-14214f55a967, please check neutron logs for more information.\n'] Neutron-server logs 2019-10-16 19:06:52.161 15 ERROR neutron.plugins.ml2.managers [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Failed to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 on host controller-0 for vnic_type normal using segments [{'network_id': '8a88d512-11e8-4938-847a-c8bed1e24fe0', 'segmentation_id': 10, 'physical_network': u'physnet0', 'id': '6bf6f798-b168-4845-983c-376fbcd07a35', 'network_type': u'vlan'}] 2019-10-16 19:06:52.161 15 ERROR neutron.plugins.ml2.managers [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Failed to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 on host controller-0 for vnic_type normal using segments [{'network_id': '8a88d512-11e8-4938-847a-c8bed1e24fe0', 'segmentation_id': 10, 'physical_network': u'physnet0', 'id': '6bf6f798-b168-4845-983c-376fbcd07a35', 'network_type': u'vlan'}] 2019-10-16 19:06:52.162 15 INFO neutron.plugins.ml2.plugin [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Attempt 10 to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 2019-10-16 19:06:52.162 15 INFO neutron.plugins.ml2.plugin [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Attempt 10 to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 2019-10-16 19:06:52.186 15 ERROR neutron.plugins.ml2.managers [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Failed to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 on host controller-0 for vnic_type normal using segments [{'network_id': '8a88d512-11e8-4938-847a-c8bed1e24fe0', 'segmentation_id': 10, 'physical_network': u'physnet0', 'id': '6bf6f798-b168-4845-983c-376fbcd07a35', 'network_type': u'vlan'}] 2019-10-16 19:06:52.186 15 ERROR neutron.plugins.ml2.managers [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Failed to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 on host controller-0 for vnic_type Anything i can check? Oror parhaps I miss some some configuration on the host. Thanks in advance. Regards, Mariano -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.l.tullis at intel.com Wed Oct 16 20:52:22 2019 From: michael.l.tullis at intel.com (Tullis, Michael L) Date: Wed, 16 Oct 2019 20:52:22 +0000 Subject: [Starlingx-discuss] [docs][meetings] docs team meeting minutes 2019-10-16 Message-ID: <3808363B39586544A6839C76CF81445EA1BF7A84@ORSMSX104.amr.corp.intel.com> Join us if you have interest in StarlingX docs! We meet Wednesdays, and call logistics are here: https://wiki.openstack.org/wiki/Starlingx/Meetings. Our etherpad is here: https://etherpad.openstack.org/p/stx-documentation. -- Mike Current agenda and notes 2019-10-16 * All -- reviews in progress and recent merges -- ? See summary at https://review.opendev.org/#/q/project:starlingx/docs. ? Recent merges. Great job team! * https://review.opendev.org/#/c/687687/ -- Add notice that R1 install docs may no longer work due to significant changes in StarlingX infrastructure -- MERGED * https://review.opendev.org/#/c/687948/ -- Fix commands and add missing information -- MERGED-- * https://review.opendev.org/#/c/687755/ -- Consolidate build guides into single guide -- MERGED * https://review.opendev.org/#/c/687689/ -- Update Ansible bootstrap path -- MERGED ? We have 1 open: * https://review.opendev.org/#/c/684820/ -- Introduction editorial updates -- This is Mary's sandbox for Gerrit familiarity and is set to workflow -1 on purpose. No urgency. * Abraham and all -- bug status -- https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs ? Only one bug is open, and it's low-priority! We've closed several higher priority bugs recently. ? https://bugs.launchpad.net/starlingx/+bug/1835207 -- Abraham will ask for help in the community meeting to get this closed. * Kris -- structure and plans for new config guide -- ? See this for background -- https://docs.google.com/document/d/1LsRk_h8-35QjtmDqjhaY_C1fDtC71S673bq1wVSKtC0 ? Kris followed up with Greg on some open questions as documented in the above link. Mike and Kris updated stories accordingly. * Bruce -- StarlingX-in-a-box -- We have two vectors on this -- ? Erich's contribution -- https://drive.google.com/file/d/19127DWvfrSvpd9QNjHlbNX2-OEbruxKx ? Calsoft's contribution -- http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/006316.html -- We believe this will go into our StarlingX-in-a-box topic as captured in https://storyboard.openstack.org/#!/story/2006622. Bruce has volunteered to help Sai with the contribution. Cindy recently confirmed that this does apply to StarlingX-in-a-box -- https://drive.google.com/file/d/1vzrx7G-G8yCYi3HgOh0FNJvenoisP2qd. ? Kris will get a 30-minute working meeting with Bruce to kick off next steps. Mike will send email with original attachment. * Abraham -- help from the Q/A team -- ? Distributed Cloud -- * https://storyboard.openstack.org/#!/story/2005181 * Nice progress! See latest status -- https://drive.google.com/file/d/1lpZKEKGbGx-J8EE_mVwPF-pSw2aoey0Y * Expect a Gerrit review maybe 10/23. ? GPU Kubernetes Plugin ? TSN -- subtask 36405 in https://storyboard.openstack.org/#!/story/2006289 ? Redfish ? Infrastructure and cluster ? Flock documentation * Tied to multi-OS -- this will go into component sections such as https://docs.starlingx.io/ha/index.html * See a recent Gerrit review -- https://4dfdbb36ff3ed7154f58-be76b9eef9539745164f256be896c2d6.ssl.cf2.rackcdn.com/687120/1/check/openstack-tox-docs/546f003/docs/ * Kris -- contributor guide -- * Would it be appropriate to incorporate parts of this "cheat sheet" into our contributor guide? -- https://drive.google.com/file/d/1a5XGPr5oTV42GPk8FWsFYWAVgltEQ3VR * The guide also needs updates to reflect our current doc schema. Probably best to make it generic so we don't have to update again. * Bruce -- Feedback from the Beijing meetup (Actual customer feedback & requirements!!!) * Improvements requested: ? Improve Documentation -- * What version/date were they using? * More specific feedback? ? UX/DX improvements * E.g Local network mirrors needed for e.g. docker registries * "The vitality of open source organizations is less cultivated in the superb technology than in the friendliness to beginners." Here is an example of impediments to beginners: https://review.opendev.org/#/c/685650/ ? Security ? Footprint reduction ? CNCF certification ? Support of legacy hosts and PC/Atom nodes ? Multiple name spaces for "system application apply" ? Multiple layers of logging, monitoring and metering (for different HW resources) * Improvements not requested: ? MultiOS * Most of these improvements are in progress. UX/DX improvements to make the project more accessible to beginners are very challenging. As we work through bringing up OpenSUSE we will find many opportunities to improve things. UX / DX improvements are a key priority for the project. Action required (AR) summary Completed ARs are archived here: https://etherpad.openstack.org/p/stx-documentation-files-003 * -- -- * 2019-05-15 -- Abraham -- Review these code and terminology changes impacting user docs -- https://drive.google.com/file/d/1sCB-lrWhDIJLNAGWBt7wJ1_JxY21m71p -- and report back on specific actions required. * 2019-10-02 -- Abraham -- Ask for help in the community meeting to get https://bugs.launchpad.net/starlingx/+bug/1835207 closed. * 2019-10-02 -- Kris and Mary -- Update the contributor guide at https://docs.starlingx.io/contributor/doc_contribute_guide.html to reflect our current doc schema and incorporate elements of the "cheat sheet." -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Wed Oct 16 21:31:33 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Wed, 16 Oct 2019 21:31:33 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191016 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-16 (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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006529.html Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcela.a.rosales.jimenez at intel.com Wed Oct 16 21:45:41 2019 From: marcela.a.rosales.jimenez at intel.com (Rosales Jimenez, Marcela A) Date: Wed, 16 Oct 2019 21:45:41 +0000 Subject: [Starlingx-discuss] [MultiOS] puppet-manifests.rpm on openSUSE missing dependencies Message-ID: <1923ADFB-6EEA-4003-9837-BB5F5DCDAD66@intel.com> Hi team, After this thread [1] I was interested on installing puppet-manifests.rpm that we have in our StarlingX openSUSE repository [2]. The first challenge I encounter was missing dependencies, these ones: # Openstack puppet modules Requires: puppet-barbican Requires: puppet-ceph Requires: puppet-horizon Requires: puppet-keystone Requires: puppet-openstacklib Requires: puppet-vswitch Requires: puppet-memcached # Puppetlabs puppet modules Requires: puppet-concat Requires: puppet-create_resources Requires: puppet-drbd Requires: puppet-firewall Requires: puppet-haproxy Requires: puppet-inifile Requires: puppet-lvm Requires: puppet-postgresql Requires: puppet-rabbitmq Requires: puppet-stdlib Requires: puppet-sysctl Requires: puppet-etcd # 3rdparty puppet modules Requires: puppet-boolean Requires: puppet-certmonger Requires: puppet-dnsmasq Requires: puppet-filemapper Requires: puppet-kmod Requires: puppet-ldap Requires: puppet-network Requires: puppet-nslcd Requires: puppet-nssdb Requires: puppet-puppi Requires: puppet-vlan Requires: puppet-collectd You can check the puppet-manifests spec here [3]. So, the question is, should we work on providing those packages in StarlingX openSUSE repo? Or what is the next step? Thanks. Marcela [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006436.html [2] https://build.opensuse.org/package/show/Cloud:StarlingX:2.0/puppet-manifests [3] https://opendev.org/starlingx/stx-puppet/src/branch/master/puppet-manifests/opensuse/puppet-manifests.spec -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcela.a.rosales.jimenez at intel.com Wed Oct 16 22:13:09 2019 From: marcela.a.rosales.jimenez at intel.com (Rosales Jimenez, Marcela A) Date: Wed, 16 Oct 2019 22:13:09 +0000 Subject: [Starlingx-discuss] [MultiOS] openSUSE auto-install question Message-ID: Hi team, Last MultiOS meeting [1] we discussed the idea of reusing the StarlingX Validation QEMU infra [2] for our experiments in openSUSE enabling. For doing that I’m using this command python qemu_setup.py -i //openSUSE-Leap-15.1-DVD-x86_64.iso -c configs/simplex.xml I follow the openSUSE installation manually, but I would like to do it automatically. I read about AutoYaST, and the two options I found were: 1. Use an installation server and send the AutoYaST config.xml through PXE 2. Compile an image using kiwi with AutoYaST config.xml. Though I’ve only found basic kiwi XML descriptions for Leap. Does someone know if there’s another way of ‘injecting’ an AutoYaST config.xml to an openSUSE DVD image? Or another way of automatically doing an openSUSE installation? Thanks! Marcela [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006514.html [2] https://opendev.org/starlingx/test/src/branch/master/automated-robot-suite/Qemu -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Wed Oct 16 22:42:09 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 16 Oct 2019 22:42:09 +0000 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC007B05280@ALA-MBD.corp.ad.wrs.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B05280@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F3608979C@SHSMSX104.ccr.corp.intel.com> Bill, I request below folks to be added: Cindy.xie at intel.com Yong.hu at intel.com Yi.c.wang at intel.com shuicheng.lin at intel.com hai.tao.wang at intel.com Austin.sun at intel.com zhaos at neusoft.com lilong-neu at neusoft.com dongqix.chen at intel.com zhiguox.zhang at intel.com yongx.fu at intel.com Cindy Xie IAGS -----Original Message----- From: Zvonar, Bill Sent: Thursday, October 17, 2019 2:40 AM To: starlingx-discuss at lists.starlingx.io Cc: Ildiko Vancsa ; Jones, Bruce E Subject: Re: [Starlingx-discuss] Voters for PL/TL election... As discussed on the Community Call today, there will be an election next week for the flock-services repo. Below is the (alphabetized) list of contributors who are currently eligible to vote on this position. Eligible voters will receive an invitation to vote this Sunday evening once the voting period begins. If you're not on this list but consider yourself to have contributed to this sub-project in the last 12 months and hence should be eligible to vote for this position, please say so here or directly to the election team (Ildiko, Bruce & myself). Bill... - al.bailey at windriver.com - alex.kozyrev at windriver.com - andy.ning at windriver.com - angie.wang at windriver.com - barton.wensley at windriver.com - bin.qian at windriver.com - chris.friesen at windriver.com - daniel.badea at windriver.com - david.sullivan at windriver.com - don.penney at windriver.com - dtroyer at gmail.com - elena.taivan at windriver.com - eric.barrett at windriver.com - eric.macdonald at windriver.com - erich.cordoba.malibran at intel.com - guozhen.she at intel.com - haochuan.z.chen at intel.com - jaegerandi at gmail.com - james.gauld at windriver.com - jason.mckenna at windriver.com - jerry.sun at windriver.com - john.kung at windriver.com - junbo85.li at gmail.com - kevin.smith at windriver.com - kristine.bujold at windriver.com - lachlan.plant at windriver.com - lihang0166 at fiberhome.com - lijunjie at cloudin.cn - lvcy at fiberhome.com - ma.lei at 99cloud.net - marcela.a.rosales.jimenez at intel.com - matt.peters at windriver.com - mingyuan.qi at intel.com - ovidiu.poncea at windriver.com - ran1.an at intel.com - scott.little at windriver.com - sgw at linux.intel.com - srifenbark at gmail.com - stefan.dinescu at windriver.com - steven.webster at windriver.com - sxmatch1986 at gmail.com - tao.liu at windriver.com - tee.ngo at windriver.com - teresa.ho at windriver.com - tyler.smith at windriver.com - wei.zhou at windriver.com - wzj334965317 at outlook.com - xbyan at fiberhome.com - xiefp88 at sina.com - yan.chen at intel.com - zhanglf01 at inspur.com - zhangzhaoshan at inspur.com - zhaolong at inspur.com - zhaowei7146 at fiberhome.com - zhipengs.liu at intel.com - zqhsh527 at 163.com -----Original Message----- From: Zvonar, Bill Sent: Wednesday, October 9, 2019 1:56 PM To: 'starlingx-discuss at lists.starlingx.io' Cc: Ildiko Vancsa ; 'Jones, Bruce E' Subject: Voters for PL/TL election... As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). Bill... build - don.penney at windriver.com - scott.little at windriver.com - dtroyer at gmail.com - al.bailey at windriver.com - tyler.smith at windriver.com - daniel.badea at windriver.com - sgw at linux.intel.com - erich.cordoba.malibran at intel.com - stefan.dinescu at windriver.com - ran1.an at intel.com - tao.liu at windriver.com - joseph.richard at windriver.com - felipe.de.jesus.ruiz.garcia at intel.com - angie.wang at windriver.com - Kristine.Bujold at windriver.com - jesus.ornelas.aguayo at intel.com - lihaijing at fiberhome.com - jason.mckenna at windriver.com - zhangyangyang at unionpay.com - jerry.sun at windriver.com - alex.kozyrev at windriver.com - steven.webster at windriver.com - jaegerandi at gmail.com - longx.li at intel.com - john.kung at windriver.com - maria.yousaf at windriver.com - zhipengs.liu at intel.com - lihang0166 at fiberhome.com - zhiguox.zhang at intel.com - bin.yang at intel.com - iwienand at redhat.com - marcela.a.rosales.jimenez at intel.com - tee.ngo at windriver.com - haochuan.z.chen at intel.com - caoran at fiberhome.com - zhang.kunpeng at 99cloud.net - Paul-Emile.Element at windriver.com config - angie.wang at windriver.com - tingjie.chen at intel.com - kevin.smith at windriver.com - ovidiu.poncea at windriver.com - bin.qian at windriver.com - joseph.richard at windriver.com - Kristine.Bujold at windriver.com - al.bailey at windriver.com - andy.ning at windriver.com - david.sullivan at windriver.com - daniel.badea at windriver.com - zhipengs.liu at intel.com - tao.liu at windriver.com - haochuan.z.chen at intel.com - lihang0166 at fiberhome.com - stefan.dinescu at windriver.com - ran1.an at intel.com - sgw at linux.intel.com - teresa.ho at windriver.com - eric.macdonald at windriver.com - alex.kozyrev at windriver.com - erich.cordoba.malibran at intel.com - scott.little at windriver.com - tee.ngo at windriver.com - tyler.smith at windriver.com - bin.yang at intel.com - john.kung at windriver.com - jaegerandi at gmail.com - mingyuan.qi at intel.com - eric.barrett at windriver.com - zhang.kunpeng at 99cloud.net - wei.zhou at windriver.com - steven.webster at windriver.com - jerry.sun at windriver.com - dtroyer at gmail.com - barton.wensley at windriver.com - matt.peters at windriver.com - zhu.boxiang at 99cloud.net - don.penney at windriver.com - James.Gauld at windriver.com - junbo85.li at gmail.com - chris.friesen at windriver.com - marcela.a.rosales.jimenez at intel.com - cheng1.li at intel.com - chenjie.xu at intel.com - allain.legacy at windriver.com - yan.chen at intel.com - elena.taivan at windriver.com - yizhoux.xu at intel.com - iwienand at redhat.com - irina.mihai at windriver.com - wzj334965317 at outlook.com - ma.lei at 99cloud.net - eric.zhang at windriver.com - Paul-Emile.Element at windriver.com - zhangyangyang at unionpay.com - daniel.chavolla at windriver.com - lachlan.plant at windriver.com - srifenbark at gmail.com - shoaib.nasir at windriver.com - singh.surya64mnnit at gmail.com containers - al.bailey at windriver.com - kevin.smith at windriver.com - zhipengs.liu at intel.com - ran1.an at intel.com distcloud - andy.ning at windriver.com - tyler.smith at windriver.com - scott.little at windriver.com - xiefp88 at sina.com - jaegerandi at gmail.com - dtroyer at gmail.com - tao.liu at windriver.com - don.penney at windriver.com - al.bailey at windriver.com - Kristine.Bujold at windriver.com - cao.yuan at 99cloud.net - wzj334965317 at outlook.com - alex.kozyrev at windriver.com - lachlan.plant at windriver.com - junbo85.li at gmail.com - srifenbark at gmail.com - barton.wensley at windriver.com distro - al.bailey at windriver.com - alex.kozyrev at windriver.com - jerry.sun at windriver.com - erich.cordoba.malibran at intel.com - daniel.badea at windriver.com - Kristine.Bujold at windriver.com - scott.little at windriver.com - jaegerandi at gmail.com - bin.qian at windriver.com - zhipengs.liu at intel.com - ran1.an at intel.com - eric.macdonald at windriver.com - john.kung at windriver.com - andy.ning at windriver.com - dtroyer at gmail.com - stefan.dinescu at windriver.com - bin.yang at intel.com - don.penney at windriver.com - eric.barrett at windriver.com - barton.wensley at windriver.com - junbo85.li at gmail.com - angie.wang at windriver.com - teresa.ho at windriver.com - sgw at linux.intel.com - tao.liu at windriver.com - zhiguox.zhang at intel.com - steven.webster at windriver.com - chenjie.xu at intel.com - James.Gauld at windriver.com - longx.li at intel.com - tyler.smith at windriver.com - chenlx at fiberhome.com - corvus at inaugust.com - chris.friesen at windriver.com - haochuan.z.chen at intel.com - daniel.chavolla at windriver.com - wei.zhou at windriver.com - ovidiu.poncea at windriver.com - joseph.richard at windriver.com - jason.mckenna at windriver.com - louie.kwan at windriver.com - Paul-Emile.Element at windriver.com - zhangyangyang at unionpay.com - tee.ngo at windriver.com - ma.lei at 99cloud.net docs - bruce.e.jones at intel.com - jaegerandi at gmail.com - chenlx at fiberhome.com - lihang0166 at fiberhome.com - srifenbark at gmail.com - xiefp88 at sina.com - liuyamin at fiberhome.com - lipan7195 at fiberhome.com - fungi at yuggoth.org - curtis at serverascode.com - iwienand at redhat.com - erich.cordoba.malibran at intel.com - li.xiaoli at 99cloud.net - zhang.kunpeng at 99cloud.net - dtroyer at gmail.com flock-services - tyler.smith at windriver.com - david.sullivan at windriver.com - Kristine.Bujold at windriver.com - al.bailey at windriver.com - jaegerandi at gmail.com - haochuan.z.chen at intel.com - dtroyer at gmail.com - teresa.ho at windriver.com - junbo85.li at gmail.com - ovidiu.poncea at windriver.com - yan.chen at intel.com - sgw at linux.intel.com - steven.webster at windriver.com - zhipengs.liu at intel.com - don.penney at windriver.com - eric.barrett at windriver.com - erich.cordoba.malibran at intel.com - scott.little at windriver.com - john.kung at windriver.com - wzj334965317 at outlook.com - tao.liu at windriver.com - stefan.dinescu at windriver.com - wei.zhou at windriver.com - James.Gauld at windriver.com - angie.wang at windriver.com - guozhen.she at intel.com - bin.qian at windriver.com - zqhsh527 at 163.com - andy.ning at windriver.com - mingyuan.qi at intel.com - xiefp88 at sina.com - daniel.badea at windriver.com - chris.friesen at windriver.com - elena.taivan at windriver.com - jerry.sun at windriver.com - marcela.a.rosales.jimenez at intel.com - xbyan at fiberhome.com - ran1.an at intel.com - alex.kozyrev at windriver.com - eric.macdonald at windriver.com - matt.peters at windriver.com - barton.wensley at windriver.com - kevin.smith at windriver.com - zhanglf01 at inspur.com - lachlan.plant at windriver.com - zhaowei7146 at fiberhome.com - lvcy at fiberhome.com - sxmatch1986 at gmail.com - ma.lei at 99cloud.net - lijunjie at cloudin.cn - jason.mckenna at windriver.com - srifenbark at gmail.com - tee.ngo at windriver.com - zhangzhaoshan at inspur.com - zhaolong at inspur.com - lihang0166 at fiberhome.com multios networking networking openstack_distro release security test - lihang0166 at fiberhome.com - dtroyer at gmail.com - erich.cordoba.malibran at intel.com - yang.liu at windriver.com - al.bailey at windriver.com - juan.p.gomez at intel.com - anujeyan.manokeran at windriver.com - maria.yousaf at windriver.com - peng.peng at windriver.com - marvin.huang at windriver.com [0] https://etherpad.openstack.org/p/stx-status _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Bill.Zvonar at windriver.com Wed Oct 16 23:24:02 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 16 Oct 2019 23:24:02 +0000 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F3608979C@SHSMSX104.ccr.corp.intel.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B05280@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F3608979C@SHSMSX104.ccr.corp.intel.com> Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B0547E@ALA-MBD.corp.ad.wrs.com> Thanks Cindy - I believe for each candidate elector, we need some justification. Ildiko/Bruce - is it a one-liner per person? -----Original Message----- From: Xie, Cindy Sent: Wednesday, October 16, 2019 6:42 PM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Cc: Ildiko Vancsa ; Jones, Bruce E Subject: RE: Voters for PL/TL election... Bill, I request below folks to be added: Cindy.xie at intel.com Yong.hu at intel.com Yi.c.wang at intel.com shuicheng.lin at intel.com hai.tao.wang at intel.com Austin.sun at intel.com zhaos at neusoft.com lilong-neu at neusoft.com dongqix.chen at intel.com zhiguox.zhang at intel.com yongx.fu at intel.com Cindy Xie IAGS -----Original Message----- From: Zvonar, Bill Sent: Thursday, October 17, 2019 2:40 AM To: starlingx-discuss at lists.starlingx.io Cc: Ildiko Vancsa ; Jones, Bruce E Subject: Re: [Starlingx-discuss] Voters for PL/TL election... As discussed on the Community Call today, there will be an election next week for the flock-services repo. Below is the (alphabetized) list of contributors who are currently eligible to vote on this position. Eligible voters will receive an invitation to vote this Sunday evening once the voting period begins. If you're not on this list but consider yourself to have contributed to this sub-project in the last 12 months and hence should be eligible to vote for this position, please say so here or directly to the election team (Ildiko, Bruce & myself). Bill... - al.bailey at windriver.com - alex.kozyrev at windriver.com - andy.ning at windriver.com - angie.wang at windriver.com - barton.wensley at windriver.com - bin.qian at windriver.com - chris.friesen at windriver.com - daniel.badea at windriver.com - david.sullivan at windriver.com - don.penney at windriver.com - dtroyer at gmail.com - elena.taivan at windriver.com - eric.barrett at windriver.com - eric.macdonald at windriver.com - erich.cordoba.malibran at intel.com - guozhen.she at intel.com - haochuan.z.chen at intel.com - jaegerandi at gmail.com - james.gauld at windriver.com - jason.mckenna at windriver.com - jerry.sun at windriver.com - john.kung at windriver.com - junbo85.li at gmail.com - kevin.smith at windriver.com - kristine.bujold at windriver.com - lachlan.plant at windriver.com - lihang0166 at fiberhome.com - lijunjie at cloudin.cn - lvcy at fiberhome.com - ma.lei at 99cloud.net - marcela.a.rosales.jimenez at intel.com - matt.peters at windriver.com - mingyuan.qi at intel.com - ovidiu.poncea at windriver.com - ran1.an at intel.com - scott.little at windriver.com - sgw at linux.intel.com - srifenbark at gmail.com - stefan.dinescu at windriver.com - steven.webster at windriver.com - sxmatch1986 at gmail.com - tao.liu at windriver.com - tee.ngo at windriver.com - teresa.ho at windriver.com - tyler.smith at windriver.com - wei.zhou at windriver.com - wzj334965317 at outlook.com - xbyan at fiberhome.com - xiefp88 at sina.com - yan.chen at intel.com - zhanglf01 at inspur.com - zhangzhaoshan at inspur.com - zhaolong at inspur.com - zhaowei7146 at fiberhome.com - zhipengs.liu at intel.com - zqhsh527 at 163.com -----Original Message----- From: Zvonar, Bill Sent: Wednesday, October 9, 2019 1:56 PM To: 'starlingx-discuss at lists.starlingx.io' Cc: Ildiko Vancsa ; 'Jones, Bruce E' Subject: Voters for PL/TL election... As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). Bill... build - don.penney at windriver.com - scott.little at windriver.com - dtroyer at gmail.com - al.bailey at windriver.com - tyler.smith at windriver.com - daniel.badea at windriver.com - sgw at linux.intel.com - erich.cordoba.malibran at intel.com - stefan.dinescu at windriver.com - ran1.an at intel.com - tao.liu at windriver.com - joseph.richard at windriver.com - felipe.de.jesus.ruiz.garcia at intel.com - angie.wang at windriver.com - Kristine.Bujold at windriver.com - jesus.ornelas.aguayo at intel.com - lihaijing at fiberhome.com - jason.mckenna at windriver.com - zhangyangyang at unionpay.com - jerry.sun at windriver.com - alex.kozyrev at windriver.com - steven.webster at windriver.com - jaegerandi at gmail.com - longx.li at intel.com - john.kung at windriver.com - maria.yousaf at windriver.com - zhipengs.liu at intel.com - lihang0166 at fiberhome.com - zhiguox.zhang at intel.com - bin.yang at intel.com - iwienand at redhat.com - marcela.a.rosales.jimenez at intel.com - tee.ngo at windriver.com - haochuan.z.chen at intel.com - caoran at fiberhome.com - zhang.kunpeng at 99cloud.net - Paul-Emile.Element at windriver.com config - angie.wang at windriver.com - tingjie.chen at intel.com - kevin.smith at windriver.com - ovidiu.poncea at windriver.com - bin.qian at windriver.com - joseph.richard at windriver.com - Kristine.Bujold at windriver.com - al.bailey at windriver.com - andy.ning at windriver.com - david.sullivan at windriver.com - daniel.badea at windriver.com - zhipengs.liu at intel.com - tao.liu at windriver.com - haochuan.z.chen at intel.com - lihang0166 at fiberhome.com - stefan.dinescu at windriver.com - ran1.an at intel.com - sgw at linux.intel.com - teresa.ho at windriver.com - eric.macdonald at windriver.com - alex.kozyrev at windriver.com - erich.cordoba.malibran at intel.com - scott.little at windriver.com - tee.ngo at windriver.com - tyler.smith at windriver.com - bin.yang at intel.com - john.kung at windriver.com - jaegerandi at gmail.com - mingyuan.qi at intel.com - eric.barrett at windriver.com - zhang.kunpeng at 99cloud.net - wei.zhou at windriver.com - steven.webster at windriver.com - jerry.sun at windriver.com - dtroyer at gmail.com - barton.wensley at windriver.com - matt.peters at windriver.com - zhu.boxiang at 99cloud.net - don.penney at windriver.com - James.Gauld at windriver.com - junbo85.li at gmail.com - chris.friesen at windriver.com - marcela.a.rosales.jimenez at intel.com - cheng1.li at intel.com - chenjie.xu at intel.com - allain.legacy at windriver.com - yan.chen at intel.com - elena.taivan at windriver.com - yizhoux.xu at intel.com - iwienand at redhat.com - irina.mihai at windriver.com - wzj334965317 at outlook.com - ma.lei at 99cloud.net - eric.zhang at windriver.com - Paul-Emile.Element at windriver.com - zhangyangyang at unionpay.com - daniel.chavolla at windriver.com - lachlan.plant at windriver.com - srifenbark at gmail.com - shoaib.nasir at windriver.com - singh.surya64mnnit at gmail.com containers - al.bailey at windriver.com - kevin.smith at windriver.com - zhipengs.liu at intel.com - ran1.an at intel.com distcloud - andy.ning at windriver.com - tyler.smith at windriver.com - scott.little at windriver.com - xiefp88 at sina.com - jaegerandi at gmail.com - dtroyer at gmail.com - tao.liu at windriver.com - don.penney at windriver.com - al.bailey at windriver.com - Kristine.Bujold at windriver.com - cao.yuan at 99cloud.net - wzj334965317 at outlook.com - alex.kozyrev at windriver.com - lachlan.plant at windriver.com - junbo85.li at gmail.com - srifenbark at gmail.com - barton.wensley at windriver.com distro - al.bailey at windriver.com - alex.kozyrev at windriver.com - jerry.sun at windriver.com - erich.cordoba.malibran at intel.com - daniel.badea at windriver.com - Kristine.Bujold at windriver.com - scott.little at windriver.com - jaegerandi at gmail.com - bin.qian at windriver.com - zhipengs.liu at intel.com - ran1.an at intel.com - eric.macdonald at windriver.com - john.kung at windriver.com - andy.ning at windriver.com - dtroyer at gmail.com - stefan.dinescu at windriver.com - bin.yang at intel.com - don.penney at windriver.com - eric.barrett at windriver.com - barton.wensley at windriver.com - junbo85.li at gmail.com - angie.wang at windriver.com - teresa.ho at windriver.com - sgw at linux.intel.com - tao.liu at windriver.com - zhiguox.zhang at intel.com - steven.webster at windriver.com - chenjie.xu at intel.com - James.Gauld at windriver.com - longx.li at intel.com - tyler.smith at windriver.com - chenlx at fiberhome.com - corvus at inaugust.com - chris.friesen at windriver.com - haochuan.z.chen at intel.com - daniel.chavolla at windriver.com - wei.zhou at windriver.com - ovidiu.poncea at windriver.com - joseph.richard at windriver.com - jason.mckenna at windriver.com - louie.kwan at windriver.com - Paul-Emile.Element at windriver.com - zhangyangyang at unionpay.com - tee.ngo at windriver.com - ma.lei at 99cloud.net docs - bruce.e.jones at intel.com - jaegerandi at gmail.com - chenlx at fiberhome.com - lihang0166 at fiberhome.com - srifenbark at gmail.com - xiefp88 at sina.com - liuyamin at fiberhome.com - lipan7195 at fiberhome.com - fungi at yuggoth.org - curtis at serverascode.com - iwienand at redhat.com - erich.cordoba.malibran at intel.com - li.xiaoli at 99cloud.net - zhang.kunpeng at 99cloud.net - dtroyer at gmail.com flock-services - tyler.smith at windriver.com - david.sullivan at windriver.com - Kristine.Bujold at windriver.com - al.bailey at windriver.com - jaegerandi at gmail.com - haochuan.z.chen at intel.com - dtroyer at gmail.com - teresa.ho at windriver.com - junbo85.li at gmail.com - ovidiu.poncea at windriver.com - yan.chen at intel.com - sgw at linux.intel.com - steven.webster at windriver.com - zhipengs.liu at intel.com - don.penney at windriver.com - eric.barrett at windriver.com - erich.cordoba.malibran at intel.com - scott.little at windriver.com - john.kung at windriver.com - wzj334965317 at outlook.com - tao.liu at windriver.com - stefan.dinescu at windriver.com - wei.zhou at windriver.com - James.Gauld at windriver.com - angie.wang at windriver.com - guozhen.she at intel.com - bin.qian at windriver.com - zqhsh527 at 163.com - andy.ning at windriver.com - mingyuan.qi at intel.com - xiefp88 at sina.com - daniel.badea at windriver.com - chris.friesen at windriver.com - elena.taivan at windriver.com - jerry.sun at windriver.com - marcela.a.rosales.jimenez at intel.com - xbyan at fiberhome.com - ran1.an at intel.com - alex.kozyrev at windriver.com - eric.macdonald at windriver.com - matt.peters at windriver.com - barton.wensley at windriver.com - kevin.smith at windriver.com - zhanglf01 at inspur.com - lachlan.plant at windriver.com - zhaowei7146 at fiberhome.com - lvcy at fiberhome.com - sxmatch1986 at gmail.com - ma.lei at 99cloud.net - lijunjie at cloudin.cn - jason.mckenna at windriver.com - srifenbark at gmail.com - tee.ngo at windriver.com - zhangzhaoshan at inspur.com - zhaolong at inspur.com - lihang0166 at fiberhome.com multios networking networking openstack_distro release security test - lihang0166 at fiberhome.com - dtroyer at gmail.com - erich.cordoba.malibran at intel.com - yang.liu at windriver.com - al.bailey at windriver.com - juan.p.gomez at intel.com - anujeyan.manokeran at windriver.com - maria.yousaf at windriver.com - peng.peng at windriver.com - marvin.huang at windriver.com [0] https://etherpad.openstack.org/p/stx-status _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Wed Oct 16 23:30:25 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 16 Oct 2019 23:30:25 +0000 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC007B0547E@ALA-MBD.corp.ad.wrs.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B05280@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F3608979C@SHSMSX104.ccr.corp.intel.com>, <586E8B730EA0DA4A9D6A80A10E486BC007B0547E@ALA-MBD.corp.ad.wrs.com> Message-ID: I am not sure how you get your list below, but by pulling their patches from StarlingX repo, you can find names for most of people. Anybody you cannot find patch, let me know, I can send you the justification. Sent from my iPhone > On Oct 17, 2019, at 07:24, Zvonar, Bill wrote: > > Thanks Cindy - I believe for each candidate elector, we need some justification. > > Ildiko/Bruce - is it a one-liner per person? > > -----Original Message----- > From: Xie, Cindy > Sent: Wednesday, October 16, 2019 6:42 PM > To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io > Cc: Ildiko Vancsa ; Jones, Bruce E > Subject: RE: Voters for PL/TL election... > > Bill, > I request below folks to be added: > Cindy.xie at intel.com > Yong.hu at intel.com > Yi.c.wang at intel.com > shuicheng.lin at intel.com > hai.tao.wang at intel.com > Austin.sun at intel.com > zhaos at neusoft.com > lilong-neu at neusoft.com > dongqix.chen at intel.com > zhiguox.zhang at intel.com > yongx.fu at intel.com > > Cindy Xie > IAGS > > > -----Original Message----- > From: Zvonar, Bill > Sent: Thursday, October 17, 2019 2:40 AM > To: starlingx-discuss at lists.starlingx.io > Cc: Ildiko Vancsa ; Jones, Bruce E > Subject: Re: [Starlingx-discuss] Voters for PL/TL election... > > As discussed on the Community Call today, there will be an election next week for the flock-services repo. > > Below is the (alphabetized) list of contributors who are currently eligible to vote on this position. > > Eligible voters will receive an invitation to vote this Sunday evening once the voting period begins. > > If you're not on this list but consider yourself to have contributed to this sub-project in the last 12 months and hence should be eligible to vote for this position, please say so here or directly to the election team (Ildiko, Bruce & myself). > > Bill... > > - al.bailey at windriver.com > - alex.kozyrev at windriver.com > - andy.ning at windriver.com > - angie.wang at windriver.com > - barton.wensley at windriver.com > - bin.qian at windriver.com > - chris.friesen at windriver.com > - daniel.badea at windriver.com > - david.sullivan at windriver.com > - don.penney at windriver.com > - dtroyer at gmail.com > - elena.taivan at windriver.com > - eric.barrett at windriver.com > - eric.macdonald at windriver.com > - erich.cordoba.malibran at intel.com > - guozhen.she at intel.com > - haochuan.z.chen at intel.com > - jaegerandi at gmail.com > - james.gauld at windriver.com > - jason.mckenna at windriver.com > - jerry.sun at windriver.com > - john.kung at windriver.com > - junbo85.li at gmail.com > - kevin.smith at windriver.com > - kristine.bujold at windriver.com > - lachlan.plant at windriver.com > - lihang0166 at fiberhome.com > - lijunjie at cloudin.cn > - lvcy at fiberhome.com > - ma.lei at 99cloud.net > - marcela.a.rosales.jimenez at intel.com > - matt.peters at windriver.com > - mingyuan.qi at intel.com > - ovidiu.poncea at windriver.com > - ran1.an at intel.com > - scott.little at windriver.com > - sgw at linux.intel.com > - srifenbark at gmail.com > - stefan.dinescu at windriver.com > - steven.webster at windriver.com > - sxmatch1986 at gmail.com > - tao.liu at windriver.com > - tee.ngo at windriver.com > - teresa.ho at windriver.com > - tyler.smith at windriver.com > - wei.zhou at windriver.com > - wzj334965317 at outlook.com > - xbyan at fiberhome.com > - xiefp88 at sina.com > - yan.chen at intel.com > - zhanglf01 at inspur.com > - zhangzhaoshan at inspur.com > - zhaolong at inspur.com > - zhaowei7146 at fiberhome.com > - zhipengs.liu at intel.com > - zqhsh527 at 163.com > > -----Original Message----- > From: Zvonar, Bill > Sent: Wednesday, October 9, 2019 1:56 PM > To: 'starlingx-discuss at lists.starlingx.io' > Cc: Ildiko Vancsa ; 'Jones, Bruce E' > Subject: Voters for PL/TL election... > > As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. > > The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. > > If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). > > Bill... > > build > > - don.penney at windriver.com > - scott.little at windriver.com > - dtroyer at gmail.com > - al.bailey at windriver.com > - tyler.smith at windriver.com > - daniel.badea at windriver.com > - sgw at linux.intel.com > - erich.cordoba.malibran at intel.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - tao.liu at windriver.com > - joseph.richard at windriver.com > - felipe.de.jesus.ruiz.garcia at intel.com > - angie.wang at windriver.com > - Kristine.Bujold at windriver.com > - jesus.ornelas.aguayo at intel.com > - lihaijing at fiberhome.com > - jason.mckenna at windriver.com > - zhangyangyang at unionpay.com > - jerry.sun at windriver.com > - alex.kozyrev at windriver.com > - steven.webster at windriver.com > - jaegerandi at gmail.com > - longx.li at intel.com > - john.kung at windriver.com > - maria.yousaf at windriver.com > - zhipengs.liu at intel.com > - lihang0166 at fiberhome.com > - zhiguox.zhang at intel.com > - bin.yang at intel.com > - iwienand at redhat.com > - marcela.a.rosales.jimenez at intel.com > - tee.ngo at windriver.com > - haochuan.z.chen at intel.com > - caoran at fiberhome.com > - zhang.kunpeng at 99cloud.net > - Paul-Emile.Element at windriver.com > > config > > - angie.wang at windriver.com > - tingjie.chen at intel.com > - kevin.smith at windriver.com > - ovidiu.poncea at windriver.com > - bin.qian at windriver.com > - joseph.richard at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - andy.ning at windriver.com > - david.sullivan at windriver.com > - daniel.badea at windriver.com > - zhipengs.liu at intel.com > - tao.liu at windriver.com > - haochuan.z.chen at intel.com > - lihang0166 at fiberhome.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - sgw at linux.intel.com > - teresa.ho at windriver.com > - eric.macdonald at windriver.com > - alex.kozyrev at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - tee.ngo at windriver.com > - tyler.smith at windriver.com > - bin.yang at intel.com > - john.kung at windriver.com > - jaegerandi at gmail.com > - mingyuan.qi at intel.com > - eric.barrett at windriver.com > - zhang.kunpeng at 99cloud.net > - wei.zhou at windriver.com > - steven.webster at windriver.com > - jerry.sun at windriver.com > - dtroyer at gmail.com > - barton.wensley at windriver.com > - matt.peters at windriver.com > - zhu.boxiang at 99cloud.net > - don.penney at windriver.com > - James.Gauld at windriver.com > - junbo85.li at gmail.com > - chris.friesen at windriver.com > - marcela.a.rosales.jimenez at intel.com > - cheng1.li at intel.com > - chenjie.xu at intel.com > - allain.legacy at windriver.com > - yan.chen at intel.com > - elena.taivan at windriver.com > - yizhoux.xu at intel.com > - iwienand at redhat.com > - irina.mihai at windriver.com > - wzj334965317 at outlook.com > - ma.lei at 99cloud.net > - eric.zhang at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - daniel.chavolla at windriver.com > - lachlan.plant at windriver.com > - srifenbark at gmail.com > - shoaib.nasir at windriver.com > - singh.surya64mnnit at gmail.com > > containers > > - al.bailey at windriver.com > - kevin.smith at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > > distcloud > > - andy.ning at windriver.com > - tyler.smith at windriver.com > - scott.little at windriver.com > - xiefp88 at sina.com > - jaegerandi at gmail.com > - dtroyer at gmail.com > - tao.liu at windriver.com > - don.penney at windriver.com > - al.bailey at windriver.com > - Kristine.Bujold at windriver.com > - cao.yuan at 99cloud.net > - wzj334965317 at outlook.com > - alex.kozyrev at windriver.com > - lachlan.plant at windriver.com > - junbo85.li at gmail.com > - srifenbark at gmail.com > - barton.wensley at windriver.com > > distro > > - al.bailey at windriver.com > - alex.kozyrev at windriver.com > - jerry.sun at windriver.com > - erich.cordoba.malibran at intel.com > - daniel.badea at windriver.com > - Kristine.Bujold at windriver.com > - scott.little at windriver.com > - jaegerandi at gmail.com > - bin.qian at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > - eric.macdonald at windriver.com > - john.kung at windriver.com > - andy.ning at windriver.com > - dtroyer at gmail.com > - stefan.dinescu at windriver.com > - bin.yang at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - barton.wensley at windriver.com > - junbo85.li at gmail.com > - angie.wang at windriver.com > - teresa.ho at windriver.com > - sgw at linux.intel.com > - tao.liu at windriver.com > - zhiguox.zhang at intel.com > - steven.webster at windriver.com > - chenjie.xu at intel.com > - James.Gauld at windriver.com > - longx.li at intel.com > - tyler.smith at windriver.com > - chenlx at fiberhome.com > - corvus at inaugust.com > - chris.friesen at windriver.com > - haochuan.z.chen at intel.com > - daniel.chavolla at windriver.com > - wei.zhou at windriver.com > - ovidiu.poncea at windriver.com > - joseph.richard at windriver.com > - jason.mckenna at windriver.com > - louie.kwan at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - tee.ngo at windriver.com > - ma.lei at 99cloud.net > > docs > > - bruce.e.jones at intel.com > - jaegerandi at gmail.com > - chenlx at fiberhome.com > - lihang0166 at fiberhome.com > - srifenbark at gmail.com > - xiefp88 at sina.com > - liuyamin at fiberhome.com > - lipan7195 at fiberhome.com > - fungi at yuggoth.org > - curtis at serverascode.com > - iwienand at redhat.com > - erich.cordoba.malibran at intel.com > - li.xiaoli at 99cloud.net > - zhang.kunpeng at 99cloud.net > - dtroyer at gmail.com > > flock-services > > - tyler.smith at windriver.com > - david.sullivan at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - jaegerandi at gmail.com > - haochuan.z.chen at intel.com > - dtroyer at gmail.com > - teresa.ho at windriver.com > - junbo85.li at gmail.com > - ovidiu.poncea at windriver.com > - yan.chen at intel.com > - sgw at linux.intel.com > - steven.webster at windriver.com > - zhipengs.liu at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - john.kung at windriver.com > - wzj334965317 at outlook.com > - tao.liu at windriver.com > - stefan.dinescu at windriver.com > - wei.zhou at windriver.com > - James.Gauld at windriver.com > - angie.wang at windriver.com > - guozhen.she at intel.com > - bin.qian at windriver.com > - zqhsh527 at 163.com > - andy.ning at windriver.com > - mingyuan.qi at intel.com > - xiefp88 at sina.com > - daniel.badea at windriver.com > - chris.friesen at windriver.com > - elena.taivan at windriver.com > - jerry.sun at windriver.com > - marcela.a.rosales.jimenez at intel.com > - xbyan at fiberhome.com > - ran1.an at intel.com > - alex.kozyrev at windriver.com > - eric.macdonald at windriver.com > - matt.peters at windriver.com > - barton.wensley at windriver.com > - kevin.smith at windriver.com > - zhanglf01 at inspur.com > - lachlan.plant at windriver.com > - zhaowei7146 at fiberhome.com > - lvcy at fiberhome.com > - sxmatch1986 at gmail.com > - ma.lei at 99cloud.net > - lijunjie at cloudin.cn > - jason.mckenna at windriver.com > - srifenbark at gmail.com > - tee.ngo at windriver.com > - zhangzhaoshan at inspur.com > - zhaolong at inspur.com > - lihang0166 at fiberhome.com > > multios > > > > networking > > > > networking > > > > openstack_distro > > > > release > > > > security > > > > test > > - lihang0166 at fiberhome.com > - dtroyer at gmail.com > - erich.cordoba.malibran at intel.com > - yang.liu at windriver.com > - al.bailey at windriver.com > - juan.p.gomez at intel.com > - anujeyan.manokeran at windriver.com > - maria.yousaf at windriver.com > - peng.peng at windriver.com > - marvin.huang at windriver.com > > [0] https://etherpad.openstack.org/p/stx-status > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Bill.Zvonar at windriver.com Wed Oct 16 23:45:27 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 16 Oct 2019 23:45:27 +0000 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: References: <586E8B730EA0DA4A9D6A80A10E486BC007B05280@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F3608979C@SHSMSX104.ccr.corp.intel.com>, <586E8B730EA0DA4A9D6A80A10E486BC007B0547E@ALA-MBD.corp.ad.wrs.com> Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B054B8@ALA-MBD.corp.ad.wrs.com> Hi Cindy - the original list was from Gerrit data. I assume that these candidates did in fact commit to flock-services repos, but the onus is on those who nominate folks who aren't on that list to provide the justification. So, please do provide that info for these folks. Thanks, Bill... -----Original Message----- From: Xie, Cindy Sent: Wednesday, October 16, 2019 7:30 PM To: Zvonar, Bill Cc: Ildiko Vancsa ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: Re: Voters for PL/TL election... I am not sure how you get your list below, but by pulling their patches from StarlingX repo, you can find names for most of people. Anybody you cannot find patch, let me know, I can send you the justification. Sent from my iPhone > On Oct 17, 2019, at 07:24, Zvonar, Bill wrote: > > Thanks Cindy - I believe for each candidate elector, we need some justification. > > Ildiko/Bruce - is it a one-liner per person? > > -----Original Message----- > From: Xie, Cindy > Sent: Wednesday, October 16, 2019 6:42 PM > To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io > Cc: Ildiko Vancsa ; Jones, Bruce E > Subject: RE: Voters for PL/TL election... > > Bill, > I request below folks to be added: > Cindy.xie at intel.com > Yong.hu at intel.com > Yi.c.wang at intel.com > shuicheng.lin at intel.com > hai.tao.wang at intel.com > Austin.sun at intel.com > zhaos at neusoft.com > lilong-neu at neusoft.com > dongqix.chen at intel.com > zhiguox.zhang at intel.com > yongx.fu at intel.com > > Cindy Xie > IAGS > > > -----Original Message----- > From: Zvonar, Bill > Sent: Thursday, October 17, 2019 2:40 AM > To: starlingx-discuss at lists.starlingx.io > Cc: Ildiko Vancsa ; Jones, Bruce E > Subject: Re: [Starlingx-discuss] Voters for PL/TL election... > > As discussed on the Community Call today, there will be an election next week for the flock-services repo. > > Below is the (alphabetized) list of contributors who are currently eligible to vote on this position. > > Eligible voters will receive an invitation to vote this Sunday evening once the voting period begins. > > If you're not on this list but consider yourself to have contributed to this sub-project in the last 12 months and hence should be eligible to vote for this position, please say so here or directly to the election team (Ildiko, Bruce & myself). > > Bill... > > - al.bailey at windriver.com > - alex.kozyrev at windriver.com > - andy.ning at windriver.com > - angie.wang at windriver.com > - barton.wensley at windriver.com > - bin.qian at windriver.com > - chris.friesen at windriver.com > - daniel.badea at windriver.com > - david.sullivan at windriver.com > - don.penney at windriver.com > - dtroyer at gmail.com > - elena.taivan at windriver.com > - eric.barrett at windriver.com > - eric.macdonald at windriver.com > - erich.cordoba.malibran at intel.com > - guozhen.she at intel.com > - haochuan.z.chen at intel.com > - jaegerandi at gmail.com > - james.gauld at windriver.com > - jason.mckenna at windriver.com > - jerry.sun at windriver.com > - john.kung at windriver.com > - junbo85.li at gmail.com > - kevin.smith at windriver.com > - kristine.bujold at windriver.com > - lachlan.plant at windriver.com > - lihang0166 at fiberhome.com > - lijunjie at cloudin.cn > - lvcy at fiberhome.com > - ma.lei at 99cloud.net > - marcela.a.rosales.jimenez at intel.com > - matt.peters at windriver.com > - mingyuan.qi at intel.com > - ovidiu.poncea at windriver.com > - ran1.an at intel.com > - scott.little at windriver.com > - sgw at linux.intel.com > - srifenbark at gmail.com > - stefan.dinescu at windriver.com > - steven.webster at windriver.com > - sxmatch1986 at gmail.com > - tao.liu at windriver.com > - tee.ngo at windriver.com > - teresa.ho at windriver.com > - tyler.smith at windriver.com > - wei.zhou at windriver.com > - wzj334965317 at outlook.com > - xbyan at fiberhome.com > - xiefp88 at sina.com > - yan.chen at intel.com > - zhanglf01 at inspur.com > - zhangzhaoshan at inspur.com > - zhaolong at inspur.com > - zhaowei7146 at fiberhome.com > - zhipengs.liu at intel.com > - zqhsh527 at 163.com > > -----Original Message----- > From: Zvonar, Bill > Sent: Wednesday, October 9, 2019 1:56 PM > To: 'starlingx-discuss at lists.starlingx.io' > Cc: Ildiko Vancsa ; 'Jones, Bruce E' > Subject: Voters for PL/TL election... > > As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. > > The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. > > If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). > > Bill... > > build > > - don.penney at windriver.com > - scott.little at windriver.com > - dtroyer at gmail.com > - al.bailey at windriver.com > - tyler.smith at windriver.com > - daniel.badea at windriver.com > - sgw at linux.intel.com > - erich.cordoba.malibran at intel.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - tao.liu at windriver.com > - joseph.richard at windriver.com > - felipe.de.jesus.ruiz.garcia at intel.com > - angie.wang at windriver.com > - Kristine.Bujold at windriver.com > - jesus.ornelas.aguayo at intel.com > - lihaijing at fiberhome.com > - jason.mckenna at windriver.com > - zhangyangyang at unionpay.com > - jerry.sun at windriver.com > - alex.kozyrev at windriver.com > - steven.webster at windriver.com > - jaegerandi at gmail.com > - longx.li at intel.com > - john.kung at windriver.com > - maria.yousaf at windriver.com > - zhipengs.liu at intel.com > - lihang0166 at fiberhome.com > - zhiguox.zhang at intel.com > - bin.yang at intel.com > - iwienand at redhat.com > - marcela.a.rosales.jimenez at intel.com > - tee.ngo at windriver.com > - haochuan.z.chen at intel.com > - caoran at fiberhome.com > - zhang.kunpeng at 99cloud.net > - Paul-Emile.Element at windriver.com > > config > > - angie.wang at windriver.com > - tingjie.chen at intel.com > - kevin.smith at windriver.com > - ovidiu.poncea at windriver.com > - bin.qian at windriver.com > - joseph.richard at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - andy.ning at windriver.com > - david.sullivan at windriver.com > - daniel.badea at windriver.com > - zhipengs.liu at intel.com > - tao.liu at windriver.com > - haochuan.z.chen at intel.com > - lihang0166 at fiberhome.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - sgw at linux.intel.com > - teresa.ho at windriver.com > - eric.macdonald at windriver.com > - alex.kozyrev at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - tee.ngo at windriver.com > - tyler.smith at windriver.com > - bin.yang at intel.com > - john.kung at windriver.com > - jaegerandi at gmail.com > - mingyuan.qi at intel.com > - eric.barrett at windriver.com > - zhang.kunpeng at 99cloud.net > - wei.zhou at windriver.com > - steven.webster at windriver.com > - jerry.sun at windriver.com > - dtroyer at gmail.com > - barton.wensley at windriver.com > - matt.peters at windriver.com > - zhu.boxiang at 99cloud.net > - don.penney at windriver.com > - James.Gauld at windriver.com > - junbo85.li at gmail.com > - chris.friesen at windriver.com > - marcela.a.rosales.jimenez at intel.com > - cheng1.li at intel.com > - chenjie.xu at intel.com > - allain.legacy at windriver.com > - yan.chen at intel.com > - elena.taivan at windriver.com > - yizhoux.xu at intel.com > - iwienand at redhat.com > - irina.mihai at windriver.com > - wzj334965317 at outlook.com > - ma.lei at 99cloud.net > - eric.zhang at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - daniel.chavolla at windriver.com > - lachlan.plant at windriver.com > - srifenbark at gmail.com > - shoaib.nasir at windriver.com > - singh.surya64mnnit at gmail.com > > containers > > - al.bailey at windriver.com > - kevin.smith at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > > distcloud > > - andy.ning at windriver.com > - tyler.smith at windriver.com > - scott.little at windriver.com > - xiefp88 at sina.com > - jaegerandi at gmail.com > - dtroyer at gmail.com > - tao.liu at windriver.com > - don.penney at windriver.com > - al.bailey at windriver.com > - Kristine.Bujold at windriver.com > - cao.yuan at 99cloud.net > - wzj334965317 at outlook.com > - alex.kozyrev at windriver.com > - lachlan.plant at windriver.com > - junbo85.li at gmail.com > - srifenbark at gmail.com > - barton.wensley at windriver.com > > distro > > - al.bailey at windriver.com > - alex.kozyrev at windriver.com > - jerry.sun at windriver.com > - erich.cordoba.malibran at intel.com > - daniel.badea at windriver.com > - Kristine.Bujold at windriver.com > - scott.little at windriver.com > - jaegerandi at gmail.com > - bin.qian at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > - eric.macdonald at windriver.com > - john.kung at windriver.com > - andy.ning at windriver.com > - dtroyer at gmail.com > - stefan.dinescu at windriver.com > - bin.yang at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - barton.wensley at windriver.com > - junbo85.li at gmail.com > - angie.wang at windriver.com > - teresa.ho at windriver.com > - sgw at linux.intel.com > - tao.liu at windriver.com > - zhiguox.zhang at intel.com > - steven.webster at windriver.com > - chenjie.xu at intel.com > - James.Gauld at windriver.com > - longx.li at intel.com > - tyler.smith at windriver.com > - chenlx at fiberhome.com > - corvus at inaugust.com > - chris.friesen at windriver.com > - haochuan.z.chen at intel.com > - daniel.chavolla at windriver.com > - wei.zhou at windriver.com > - ovidiu.poncea at windriver.com > - joseph.richard at windriver.com > - jason.mckenna at windriver.com > - louie.kwan at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - tee.ngo at windriver.com > - ma.lei at 99cloud.net > > docs > > - bruce.e.jones at intel.com > - jaegerandi at gmail.com > - chenlx at fiberhome.com > - lihang0166 at fiberhome.com > - srifenbark at gmail.com > - xiefp88 at sina.com > - liuyamin at fiberhome.com > - lipan7195 at fiberhome.com > - fungi at yuggoth.org > - curtis at serverascode.com > - iwienand at redhat.com > - erich.cordoba.malibran at intel.com > - li.xiaoli at 99cloud.net > - zhang.kunpeng at 99cloud.net > - dtroyer at gmail.com > > flock-services > > - tyler.smith at windriver.com > - david.sullivan at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - jaegerandi at gmail.com > - haochuan.z.chen at intel.com > - dtroyer at gmail.com > - teresa.ho at windriver.com > - junbo85.li at gmail.com > - ovidiu.poncea at windriver.com > - yan.chen at intel.com > - sgw at linux.intel.com > - steven.webster at windriver.com > - zhipengs.liu at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - john.kung at windriver.com > - wzj334965317 at outlook.com > - tao.liu at windriver.com > - stefan.dinescu at windriver.com > - wei.zhou at windriver.com > - James.Gauld at windriver.com > - angie.wang at windriver.com > - guozhen.she at intel.com > - bin.qian at windriver.com > - zqhsh527 at 163.com > - andy.ning at windriver.com > - mingyuan.qi at intel.com > - xiefp88 at sina.com > - daniel.badea at windriver.com > - chris.friesen at windriver.com > - elena.taivan at windriver.com > - jerry.sun at windriver.com > - marcela.a.rosales.jimenez at intel.com > - xbyan at fiberhome.com > - ran1.an at intel.com > - alex.kozyrev at windriver.com > - eric.macdonald at windriver.com > - matt.peters at windriver.com > - barton.wensley at windriver.com > - kevin.smith at windriver.com > - zhanglf01 at inspur.com > - lachlan.plant at windriver.com > - zhaowei7146 at fiberhome.com > - lvcy at fiberhome.com > - sxmatch1986 at gmail.com > - ma.lei at 99cloud.net > - lijunjie at cloudin.cn > - jason.mckenna at windriver.com > - srifenbark at gmail.com > - tee.ngo at windriver.com > - zhangzhaoshan at inspur.com > - zhaolong at inspur.com > - lihang0166 at fiberhome.com > > multios > > > > networking > > > > networking > > > > openstack_distro > > > > release > > > > security > > > > test > > - lihang0166 at fiberhome.com > - dtroyer at gmail.com > - erich.cordoba.malibran at intel.com > - yang.liu at windriver.com > - al.bailey at windriver.com > - juan.p.gomez at intel.com > - anujeyan.manokeran at windriver.com > - maria.yousaf at windriver.com > - peng.peng at windriver.com > - marvin.huang at windriver.com > > [0] https://etherpad.openstack.org/p/stx-status > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From fungi at yuggoth.org Wed Oct 16 23:54:35 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 16 Oct 2019 23:54:35 +0000 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC007B054B8@ALA-MBD.corp.ad.wrs.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B05280@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F3608979C@SHSMSX104.ccr.corp.intel.com> <586E8B730EA0DA4A9D6A80A10E486BC007B0547E@ALA-MBD.corp.ad.wrs.com> <586E8B730EA0DA4A9D6A80A10E486BC007B054B8@ALA-MBD.corp.ad.wrs.com> Message-ID: <20191016235435.oadks4xdxe62pgij@yuggoth.org> On 2019-10-16 23:45:27 +0000 (+0000), Zvonar, Bill wrote: > Hi Cindy - the original list was from Gerrit data. > > I assume that these candidates did in fact commit to > flock-services repos, but the onus is on those who nominate folks > who aren't on that list to provide the justification. [...] Keep in mind that the list I queried from Gerrit was then filtered by addresses for which there is a corresponding OSF Individual Membership on file, since that's what Ildiko requested. Presumably, if OSF membership is required criteria for voting in your elections, then any new addresses you add will also need to be cross-checked against the OpenStackID Resources API to see if it is associated with an active foundation membership. -- 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 cindy.xie at intel.com Thu Oct 17 00:36:58 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Thu, 17 Oct 2019 00:36:58 +0000 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC007B054B8@ALA-MBD.corp.ad.wrs.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B05280@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F3608979C@SHSMSX104.ccr.corp.intel.com>, <586E8B730EA0DA4A9D6A80A10E486BC007B0547E@ALA-MBD.corp.ad.wrs.com> <586E8B730EA0DA4A9D6A80A10E486BC007B054B8@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F36089A8D@SHSMSX104.ccr.corp.intel.com> Bill, Here is my statistic of the patches in 2019 for the below folks: Status Merged Count of Subject Column Labels Row Labels starlingx/config starlingx/nfv starlingx/metal starlingx/fault starlingx/gui starlingx/distcloud starlingx/ha starlingx/config-files openstack/horizon Grand Total Austin Sun 14 1 5 1 3 1 25 Yi Wang 7 6 5 18 zhipeng liu 11 1 4 1 1 18 Lin Shuicheng 7 2 4 1 1 15 Ran An 6 8 1 15 Mingyuan Qi 12 1 13 chen haochuan 6 2 2 1 11 Yan Chen 2 7 1 10 yong hu 2 2 Grand Total 67 17 12 11 11 3 3 2 1 127 I am not sure why your gerrit data didn't show the results. For the below folks, they didn't have patches in flocks repo, but they were working on porting flocks components to Clear Linux, they've worked on spec file and generating flocks service packages. The work is not on master yet. Not sure if this counts. > zhaos at neusoft.com > lilong-neu at neusoft.com > dongqix.chen at intel.com > zhiguox.zhang at intel.com > yongx.fu at intel.com > hai.tao.wang at intel.com Thx. - cindy -----Original Message----- From: Zvonar, Bill Sent: Thursday, October 17, 2019 7:45 AM To: Xie, Cindy Cc: Ildiko Vancsa ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: Voters for PL/TL election... Hi Cindy - the original list was from Gerrit data. I assume that these candidates did in fact commit to flock-services repos, but the onus is on those who nominate folks who aren't on that list to provide the justification. So, please do provide that info for these folks. Thanks, Bill... -----Original Message----- From: Xie, Cindy > Sent: Wednesday, October 16, 2019 7:30 PM To: Zvonar, Bill > Cc: Ildiko Vancsa >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: Re: Voters for PL/TL election... I am not sure how you get your list below, but by pulling their patches from StarlingX repo, you can find names for most of people. Anybody you cannot find patch, let me know, I can send you the justification. Sent from my iPhone > On Oct 17, 2019, at 07:24, Zvonar, Bill > wrote: > > Thanks Cindy - I believe for each candidate elector, we need some justification. > > Ildiko/Bruce - is it a one-liner per person? > > -----Original Message----- > From: Xie, Cindy > > Sent: Wednesday, October 16, 2019 6:42 PM > To: Zvonar, Bill >; starlingx-discuss at lists.starlingx.io > Cc: Ildiko Vancsa >; Jones, Bruce E > > Subject: RE: Voters for PL/TL election... > > Bill, > I request below folks to be added: > Cindy.xie at intel.com > Yong.hu at intel.com > Yi.c.wang at intel.com > shuicheng.lin at intel.com > hai.tao.wang at intel.com > Austin.sun at intel.com > zhaos at neusoft.com > lilong-neu at neusoft.com > dongqix.chen at intel.com > zhiguox.zhang at intel.com > yongx.fu at intel.com > > Cindy Xie > IAGS > > > -----Original Message----- > From: Zvonar, Bill > > Sent: Thursday, October 17, 2019 2:40 AM > To: starlingx-discuss at lists.starlingx.io > Cc: Ildiko Vancsa >; Jones, Bruce E > > Subject: Re: [Starlingx-discuss] Voters for PL/TL election... > > As discussed on the Community Call today, there will be an election next week for the flock-services repo. > > Below is the (alphabetized) list of contributors who are currently eligible to vote on this position. > > Eligible voters will receive an invitation to vote this Sunday evening once the voting period begins. > > If you're not on this list but consider yourself to have contributed to this sub-project in the last 12 months and hence should be eligible to vote for this position, please say so here or directly to the election team (Ildiko, Bruce & myself). > > Bill... > > - al.bailey at windriver.com > - alex.kozyrev at windriver.com > - andy.ning at windriver.com > - angie.wang at windriver.com > - barton.wensley at windriver.com > - bin.qian at windriver.com > - chris.friesen at windriver.com > - daniel.badea at windriver.com > - david.sullivan at windriver.com > - don.penney at windriver.com > - dtroyer at gmail.com > - elena.taivan at windriver.com > - eric.barrett at windriver.com > - eric.macdonald at windriver.com > - erich.cordoba.malibran at intel.com > - guozhen.she at intel.com > - haochuan.z.chen at intel.com > - jaegerandi at gmail.com > - james.gauld at windriver.com > - jason.mckenna at windriver.com > - jerry.sun at windriver.com > - john.kung at windriver.com > - junbo85.li at gmail.com > - kevin.smith at windriver.com > - kristine.bujold at windriver.com > - lachlan.plant at windriver.com > - lihang0166 at fiberhome.com > - lijunjie at cloudin.cn > - lvcy at fiberhome.com > - ma.lei at 99cloud.net > - marcela.a.rosales.jimenez at intel.com > - matt.peters at windriver.com > - mingyuan.qi at intel.com > - ovidiu.poncea at windriver.com > - ran1.an at intel.com > - scott.little at windriver.com > - sgw at linux.intel.com > - srifenbark at gmail.com > - stefan.dinescu at windriver.com > - steven.webster at windriver.com > - sxmatch1986 at gmail.com > - tao.liu at windriver.com > - tee.ngo at windriver.com > - teresa.ho at windriver.com > - tyler.smith at windriver.com > - wei.zhou at windriver.com > - wzj334965317 at outlook.com > - xbyan at fiberhome.com > - xiefp88 at sina.com > - yan.chen at intel.com > - zhanglf01 at inspur.com > - zhangzhaoshan at inspur.com > - zhaolong at inspur.com > - zhaowei7146 at fiberhome.com > - zhipengs.liu at intel.com > - zqhsh527 at 163.com > > -----Original Message----- > From: Zvonar, Bill > Sent: Wednesday, October 9, 2019 1:56 PM > To: 'starlingx-discuss at lists.starlingx.io' > > Cc: Ildiko Vancsa >; 'Jones, Bruce E' > > Subject: Voters for PL/TL election... > > As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. > > The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. > > If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). > > Bill... > > build > > - don.penney at windriver.com > - scott.little at windriver.com > - dtroyer at gmail.com > - al.bailey at windriver.com > - tyler.smith at windriver.com > - daniel.badea at windriver.com > - sgw at linux.intel.com > - erich.cordoba.malibran at intel.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - tao.liu at windriver.com > - joseph.richard at windriver.com > - felipe.de.jesus.ruiz.garcia at intel.com > - angie.wang at windriver.com > - Kristine.Bujold at windriver.com > - jesus.ornelas.aguayo at intel.com > - lihaijing at fiberhome.com > - jason.mckenna at windriver.com > - zhangyangyang at unionpay.com > - jerry.sun at windriver.com > - alex.kozyrev at windriver.com > - steven.webster at windriver.com > - jaegerandi at gmail.com > - longx.li at intel.com > - john.kung at windriver.com > - maria.yousaf at windriver.com > - zhipengs.liu at intel.com > - lihang0166 at fiberhome.com > - zhiguox.zhang at intel.com > - bin.yang at intel.com > - iwienand at redhat.com > - marcela.a.rosales.jimenez at intel.com > - tee.ngo at windriver.com > - haochuan.z.chen at intel.com > - caoran at fiberhome.com > - zhang.kunpeng at 99cloud.net > - Paul-Emile.Element at windriver.com > > config > > - angie.wang at windriver.com > - tingjie.chen at intel.com > - kevin.smith at windriver.com > - ovidiu.poncea at windriver.com > - bin.qian at windriver.com > - joseph.richard at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - andy.ning at windriver.com > - david.sullivan at windriver.com > - daniel.badea at windriver.com > - zhipengs.liu at intel.com > - tao.liu at windriver.com > - haochuan.z.chen at intel.com > - lihang0166 at fiberhome.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - sgw at linux.intel.com > - teresa.ho at windriver.com > - eric.macdonald at windriver.com > - alex.kozyrev at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - tee.ngo at windriver.com > - tyler.smith at windriver.com > - bin.yang at intel.com > - john.kung at windriver.com > - jaegerandi at gmail.com > - mingyuan.qi at intel.com > - eric.barrett at windriver.com > - zhang.kunpeng at 99cloud.net > - wei.zhou at windriver.com > - steven.webster at windriver.com > - jerry.sun at windriver.com > - dtroyer at gmail.com > - barton.wensley at windriver.com > - matt.peters at windriver.com > - zhu.boxiang at 99cloud.net > - don.penney at windriver.com > - James.Gauld at windriver.com > - junbo85.li at gmail.com > - chris.friesen at windriver.com > - marcela.a.rosales.jimenez at intel.com > - cheng1.li at intel.com > - chenjie.xu at intel.com > - allain.legacy at windriver.com > - yan.chen at intel.com > - elena.taivan at windriver.com > - yizhoux.xu at intel.com > - iwienand at redhat.com > - irina.mihai at windriver.com > - wzj334965317 at outlook.com > - ma.lei at 99cloud.net > - eric.zhang at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - daniel.chavolla at windriver.com > - lachlan.plant at windriver.com > - srifenbark at gmail.com > - shoaib.nasir at windriver.com > - singh.surya64mnnit at gmail.com > > containers > > - al.bailey at windriver.com > - kevin.smith at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > > distcloud > > - andy.ning at windriver.com > - tyler.smith at windriver.com > - scott.little at windriver.com > - xiefp88 at sina.com > - jaegerandi at gmail.com > - dtroyer at gmail.com > - tao.liu at windriver.com > - don.penney at windriver.com > - al.bailey at windriver.com > - Kristine.Bujold at windriver.com > - cao.yuan at 99cloud.net > - wzj334965317 at outlook.com > - alex.kozyrev at windriver.com > - lachlan.plant at windriver.com > - junbo85.li at gmail.com > - srifenbark at gmail.com > - barton.wensley at windriver.com > > distro > > - al.bailey at windriver.com > - alex.kozyrev at windriver.com > - jerry.sun at windriver.com > - erich.cordoba.malibran at intel.com > - daniel.badea at windriver.com > - Kristine.Bujold at windriver.com > - scott.little at windriver.com > - jaegerandi at gmail.com > - bin.qian at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > - eric.macdonald at windriver.com > - john.kung at windriver.com > - andy.ning at windriver.com > - dtroyer at gmail.com > - stefan.dinescu at windriver.com > - bin.yang at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - barton.wensley at windriver.com > - junbo85.li at gmail.com > - angie.wang at windriver.com > - teresa.ho at windriver.com > - sgw at linux.intel.com > - tao.liu at windriver.com > - zhiguox.zhang at intel.com > - steven.webster at windriver.com > - chenjie.xu at intel.com > - James.Gauld at windriver.com > - longx.li at intel.com > - tyler.smith at windriver.com > - chenlx at fiberhome.com > - corvus at inaugust.com > - chris.friesen at windriver.com > - haochuan.z.chen at intel.com > - daniel.chavolla at windriver.com > - wei.zhou at windriver.com > - ovidiu.poncea at windriver.com > - joseph.richard at windriver.com > - jason.mckenna at windriver.com > - louie.kwan at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - tee.ngo at windriver.com > - ma.lei at 99cloud.net > > docs > > - bruce.e.jones at intel.com > - jaegerandi at gmail.com > - chenlx at fiberhome.com > - lihang0166 at fiberhome.com > - srifenbark at gmail.com > - xiefp88 at sina.com > - liuyamin at fiberhome.com > - lipan7195 at fiberhome.com > - fungi at yuggoth.org > - curtis at serverascode.com > - iwienand at redhat.com > - erich.cordoba.malibran at intel.com > - li.xiaoli at 99cloud.net > - zhang.kunpeng at 99cloud.net > - dtroyer at gmail.com > > flock-services > > - tyler.smith at windriver.com > - david.sullivan at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - jaegerandi at gmail.com > - haochuan.z.chen at intel.com > - dtroyer at gmail.com > - teresa.ho at windriver.com > - junbo85.li at gmail.com > - ovidiu.poncea at windriver.com > - yan.chen at intel.com > - sgw at linux.intel.com > - steven.webster at windriver.com > - zhipengs.liu at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - john.kung at windriver.com > - wzj334965317 at outlook.com > - tao.liu at windriver.com > - stefan.dinescu at windriver.com > - wei.zhou at windriver.com > - James.Gauld at windriver.com > - angie.wang at windriver.com > - guozhen.she at intel.com > - bin.qian at windriver.com > - zqhsh527 at 163.com > - andy.ning at windriver.com > - mingyuan.qi at intel.com > - xiefp88 at sina.com > - daniel.badea at windriver.com > - chris.friesen at windriver.com > - elena.taivan at windriver.com > - jerry.sun at windriver.com > - marcela.a.rosales.jimenez at intel.com > - xbyan at fiberhome.com > - ran1.an at intel.com > - alex.kozyrev at windriver.com > - eric.macdonald at windriver.com > - matt.peters at windriver.com > - barton.wensley at windriver.com > - kevin.smith at windriver.com > - zhanglf01 at inspur.com > - lachlan.plant at windriver.com > - zhaowei7146 at fiberhome.com > - lvcy at fiberhome.com > - sxmatch1986 at gmail.com > - ma.lei at 99cloud.net > - lijunjie at cloudin.cn > - jason.mckenna at windriver.com > - srifenbark at gmail.com > - tee.ngo at windriver.com > - zhangzhaoshan at inspur.com > - zhaolong at inspur.com > - lihang0166 at fiberhome.com > > multios > > > > networking > > > > networking > > > > openstack_distro > > > > release > > > > security > > > > test > > - lihang0166 at fiberhome.com > - dtroyer at gmail.com > - erich.cordoba.malibran at intel.com > - yang.liu at windriver.com > - al.bailey at windriver.com > - juan.p.gomez at intel.com > - anujeyan.manokeran at windriver.com > - maria.yousaf at windriver.com > - peng.peng at windriver.com > - marvin.huang at windriver.com > > [0] https://etherpad.openstack.org/p/stx-status > > _______________________________________________ > 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 fungi at yuggoth.org Thu Oct 17 00:55:41 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 17 Oct 2019 00:55:41 +0000 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F36089A8D@SHSMSX104.ccr.corp.intel.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B05280@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F3608979C@SHSMSX104.ccr.corp.intel.com> <586E8B730EA0DA4A9D6A80A10E486BC007B0547E@ALA-MBD.corp.ad.wrs.com> <586E8B730EA0DA4A9D6A80A10E486BC007B054B8@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F36089A8D@SHSMSX104.ccr.corp.intel.com> Message-ID: <20191017005541.uj2i7r67mnkx5hqw@yuggoth.org> On 2019-10-17 00:36:58 +0000 (+0000), Xie, Cindy wrote: > Here is my statistic of the patches in 2019 for the below folks: [...] > I am not sure why your gerrit data didn't show the results. [...] If it helps, this is the list of names associated with the 41 Gerrit accounts for StarlingX code contributors from the qualifying 2018-10-06 through 2019-10-06 timeframe who were omitted from the original rolls I provided due to not having corresponding OSF Individual Memberships for their E-mail addresses when the list was generated on 2019-10-07: 98k Abraham Arce Ada Cabrales Austin Sun Bob Church Changcheng Intel Cristopher Lemus Dan Voiculeasa Dominig ar Foll (Intel Open Source) Elio Martinez Erick Cardona Fei Chao Fernando Hernandez Gonzalez Gao Zexu Gerry Kopec Hayde Martinez Jack Ding Jim Somerville Jose Perez Carranza Juan Carlos Alonso Kailun Qin Kristal Dale Liang Fang Lin Shuicheng Luis Botello Mariana González Mario Alfredo Carrillo Arevalo Mawrer Amed Ramirez Martinez Tao Li Victor Manuel Rodriguez Bahena YeHuiSheng Yi Wang ZHOU YAO Zhe Hu hutianhao27 marvin Yu yong hu zhangbei zhangyifan zhao.shuai zhaodan7597 This information is included in the structured data provided to the StarlingX election officials, in a file named starlingx-2019-10-06/_all_owners.yaml within the ZIP archive they received from me. -- 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 chenjie.xu at intel.com Thu Oct 17 01:48:28 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Thu, 17 Oct 2019 01:48:28 +0000 Subject: [Starlingx-discuss] Integration Openstack and SRIOV - Cannot deploy a VM In-Reply-To: <5da77085.1c69fb81.4c052.65b4@mx.google.com> References: <5da77085.1c69fb81.4c052.65b4@mx.google.com> Message-ID: Hi Mariano, What are you trying to deploy? 1. Normal VM. 2. Passthrough a physical NIC to VM 3. Passthrough a VF to VM Which configuration guide in the following link is used? https://wiki.openstack.org/wiki/StarlingX/Networking Best Regards, Xu, Chenjie From: Mariano Ucha Sent: Thursday, October 17, 2019 3:33 AM To: Discussion List StarlingX Subject: [Starlingx-discuss] Integration Openstack and SRIOV - Cannot deploy a VM Hi guys, I’m trying to deploy a VM on a baremetal ST 2.0 STX AIO. I have a dual nic port with SRIOV Support. I didn’t find a documentation how to configure at openstack level in theDeployment guide. I use some config that i found in the wiki Network https://wiki.openstack.org/wiki/StarlingX/Networking I can configure networks, subnet and ports. But when i deploy a VM i got this error: Message Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures for instance add8e0d3-4ce0-4611-8f26-0032484fb8f8. Code 500 Details File "/var/lib/openstack/lib/python2.7/site-packages/nova/conductor/manager.py", line 627, in build_instances raise exception.MaxRetriesExceeded(reason=msg) Created Oct. 16, 2019, 4:06 p.m. I found more detailed error in nova-conductor 2019-10-16 19:06:57.076 1 ERROR nova.scheduler.utils [req-7f352cf5-d9b4-4478-abfc-f68d7298ea85 bc5015570893422bb07d9292ddfa1edc 77eaa44ce5124f6685fe27ac91758427 - default default] [instance: add8e0d3-4ce0-4611-8f26-0032484fb8f8] Error from last host: controller-0 (node controller-0): [u'Traceback (most recent call last):\n', u' File "/var/lib/openstack/lib/python2.7/site-packages/nova/compute/manager.py", line 1984, in _do_build_and_run_instance\n filter_properties, request_spec)\n', u' File "/var/lib/openstack/lib/python2.7/site-packages/nova/compute/manager.py", line 2354, in _build_and_run_instance\n instance_uuid=instance.uuid, reason=six.text_type(e))\n', u'RescheduledException: Build of instance add8e0d3-4ce0-4611-8f26-0032484fb8f8 was re-scheduled: Binding failed for port 3bfaeb9c-428c-45ed-9879-14214f55a967, please check neutron logs for more information.\n'] Neutron-server logs 2019-10-16 19:06:52.161 15 ERROR neutron.plugins.ml2.managers [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Failed to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 on host controller-0 for vnic_type normal using segments [{'network_id': '8a88d512-11e8-4938-847a-c8bed1e24fe0', 'segmentation_id': 10, 'physical_network': u'physnet0', 'id': '6bf6f798-b168-4845-983c-376fbcd07a35', 'network_type': u'vlan'}] 2019-10-16 19:06:52.161 15 ERROR neutron.plugins.ml2.managers [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Failed to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 on host controller-0 for vnic_type normal using segments [{'network_id': '8a88d512-11e8-4938-847a-c8bed1e24fe0', 'segmentation_id': 10, 'physical_network': u'physnet0', 'id': '6bf6f798-b168-4845-983c-376fbcd07a35', 'network_type': u'vlan'}] 2019-10-16 19:06:52.162 15 INFO neutron.plugins.ml2.plugin [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Attempt 10 to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 2019-10-16 19:06:52.162 15 INFO neutron.plugins.ml2.plugin [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Attempt 10 to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 2019-10-16 19:06:52.186 15 ERROR neutron.plugins.ml2.managers [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Failed to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 on host controller-0 for vnic_type normal using segments [{'network_id': '8a88d512-11e8-4938-847a-c8bed1e24fe0', 'segmentation_id': 10, 'physical_network': u'physnet0', 'id': '6bf6f798-b168-4845-983c-376fbcd07a35', 'network_type': u'vlan'}] 2019-10-16 19:06:52.186 15 ERROR neutron.plugins.ml2.managers [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Failed to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 on host controller-0 for vnic_type Anything i can check? Oror parhaps I miss some some configuration on the host. Thanks in advance. Regards, Mariano -------------- next part -------------- An HTML attachment was scrubbed... URL: From lw2dht at gmail.com Thu Oct 17 02:05:02 2019 From: lw2dht at gmail.com (Mariano Ucha) Date: Wed, 16 Oct 2019 23:05:02 -0300 Subject: [Starlingx-discuss] Integration Openstack and SRIOV - Cannotdeploy a VM In-Reply-To: References: <5da77085.1c69fb81.4c052.65b4@mx.google.com> Message-ID: <5da7cc4e.1c69fb81.360e5.6433@mx.google.com> Hi Chenjie! I’m trying to deploy a CentOS VM with a SRIOV Port. I use this section of the link: Configure SR-IOV with OpenStack The only difference that i used openstack command instead of neutron port…. Regards, Mariano De: Xu, Chenjie Enviado: miércoles, 16 de octubre de 2019 22:48 Para: Mariano Ucha; Discussion List StarlingX Asunto: RE: [Starlingx-discuss] Integration Openstack and SRIOV - Cannotdeploy a VM Hi Mariano, What are you trying to deploy? 1. Normal VM. 2. Passthrough a physical NIC to VM 3. Passthrough a VF to VM Which configuration guide in the following link is used? https://wiki.openstack.org/wiki/StarlingX/Networking Best Regards, Xu, Chenjie From: Mariano Ucha Sent: Thursday, October 17, 2019 3:33 AM To: Discussion List StarlingX Subject: [Starlingx-discuss] Integration Openstack and SRIOV - Cannot deploy a VM Hi guys, I’m trying to deploy a VM on a baremetal ST 2.0 STX AIO. I have a dual nic port with SRIOV Support. I didn’t find a documentation how to configure at openstack level in theDeployment guide. I use some config that i found in the wiki Network https://wiki.openstack.org/wiki/StarlingX/Networking I can configure networks, subnet and ports. But when i deploy a VM i got this error: Message     Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures for instance add8e0d3-4ce0-4611-8f26-0032484fb8f8. Code     500 Details    File "/var/lib/openstack/lib/python2.7/site-packages/nova/conductor/manager.py", line 627, in build_instances raise exception.MaxRetriesExceeded(reason=msg) Created    Oct. 16, 2019, 4:06 p.m. I found more detailed error in nova-conductor 2019-10-16 19:06:57.076 1 ERROR nova.scheduler.utils [req-7f352cf5-d9b4-4478-abfc-f68d7298ea85 bc5015570893422bb07d9292ddfa1edc 77eaa44ce5124f6685fe27ac91758427 - default default] [instance: add8e0d3-4ce0-4611-8f26-0032484fb8f8] Error from last host: controller-0 (node controller-0): [u'Traceback (most recent call last):\n', u'  File "/var/lib/openstack/lib/python2.7/site-packages/nova/compute/manager.py", line 1984, in _do_build_and_run_instance\n    filter_properties, request_spec)\n', u'  File "/var/lib/openstack/lib/python2.7/site-packages/nova/compute/manager.py", line 2354, in _build_and_run_instance\n    instance_uuid=instance.uuid, reason=six.text_type(e))\n', u'RescheduledException: Build of instance add8e0d3-4ce0-4611-8f26-0032484fb8f8 was re-scheduled: Binding failed for port 3bfaeb9c-428c-45ed-9879-14214f55a967, please check neutron logs for more information.\n'] Neutron-server logs 2019-10-16 19:06:52.161 15 ERROR neutron.plugins.ml2.managers [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Failed to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 on host controller-0 for vnic_type normal using segments [{'network_id': '8a88d512-11e8-4938-847a-c8bed1e24fe0', 'segmentation_id': 10, 'physical_network': u'physnet0', 'id': '6bf6f798-b168-4845-983c-376fbcd07a35', 'network_type': u'vlan'}] 2019-10-16 19:06:52.161 15 ERROR neutron.plugins.ml2.managers [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Failed to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 on host controller-0 for vnic_type normal using segments [{'network_id': '8a88d512-11e8-4938-847a-c8bed1e24fe0', 'segmentation_id': 10, 'physical_network': u'physnet0', 'id': '6bf6f798-b168-4845-983c-376fbcd07a35', 'network_type': u'vlan'}] 2019-10-16 19:06:52.162 15 INFO neutron.plugins.ml2.plugin [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Attempt 10 to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 2019-10-16 19:06:52.162 15 INFO neutron.plugins.ml2.plugin [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Attempt 10 to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 2019-10-16 19:06:52.186 15 ERROR neutron.plugins.ml2.managers [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Failed to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 on host controller-0 for vnic_type normal using segments [{'network_id': '8a88d512-11e8-4938-847a-c8bed1e24fe0', 'segmentation_id': 10, 'physical_network': u'physnet0', 'id': '6bf6f798-b168-4845-983c-376fbcd07a35', 'network_type': u'vlan'}] 2019-10-16 19:06:52.186 15 ERROR neutron.plugins.ml2.managers [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Failed to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 on host controller-0 for vnic_type Anything i can check? Oror parhaps I miss some  some configuration on the host. Thanks in advance. Regards, Mariano -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenjie.xu at intel.com Thu Oct 17 02:21:33 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Thu, 17 Oct 2019 02:21:33 +0000 Subject: [Starlingx-discuss] Integration Openstack and SRIOV - Cannotdeploy a VM In-Reply-To: <5da7cc4e.1c69fb81.360e5.6433@mx.google.com> References: <5da77085.1c69fb81.4c052.65b4@mx.google.com> <5da7cc4e.1c69fb81.360e5.6433@mx.google.com> Message-ID: Hi Mariano, The openstack commands should be ok. From the below neutron logs, I think the port you are trying to bind has vnic_type normal. For SR-IOV, the vnic_type should be direct which means you wants the VM to use that port directly. 2019-10-16 19:06:52.161 15 ERROR neutron.plugins.ml2.managers [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Failed to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 on host controller-0 for vnic_type normal using segments [{'network_id': '8a88d512-11e8-4938-847a-c8bed1e24fe0', 'segmentation_id': 10, 'physical_network': u'physnet0', 'id': '6bf6f798-b168-4845-983c-376fbcd07a35', 'network_type': u'vlan'}] The below commands can be referenced: openstack port create --binding-profile vnic_type=direct --network ${PUBLICNET} sriov-port-2 Best Regards, Xu, Chenjie From: Mariano Ucha Sent: Thursday, October 17, 2019 10:05 AM To: Xu, Chenjie ; Discussion List StarlingX Subject: RE: [Starlingx-discuss] Integration Openstack and SRIOV - Cannotdeploy a VM Hi Chenjie! I’m trying to deploy a CentOS VM with a SRIOV Port. I use this section of the link: Configure SR-IOV with OpenStack The only difference that i used openstack command instead of neutron port…. Regards, Mariano De: Xu, Chenjie Enviado: miércoles, 16 de octubre de 2019 22:48 Para: Mariano Ucha; Discussion List StarlingX Asunto: RE: [Starlingx-discuss] Integration Openstack and SRIOV - Cannotdeploy a VM Hi Mariano, What are you trying to deploy? 1. Normal VM. 2. Passthrough a physical NIC to VM 3. Passthrough a VF to VM Which configuration guide in the following link is used? https://wiki.openstack.org/wiki/StarlingX/Networking Best Regards, Xu, Chenjie From: Mariano Ucha > Sent: Thursday, October 17, 2019 3:33 AM To: Discussion List StarlingX > Subject: [Starlingx-discuss] Integration Openstack and SRIOV - Cannot deploy a VM Hi guys, I’m trying to deploy a VM on a baremetal ST 2.0 STX AIO. I have a dual nic port with SRIOV Support. I didn’t find a documentation how to configure at openstack level in theDeployment guide. I use some config that i found in the wiki Network https://wiki.openstack.org/wiki/StarlingX/Networking I can configure networks, subnet and ports. But when i deploy a VM i got this error: Message Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures for instance add8e0d3-4ce0-4611-8f26-0032484fb8f8. Code 500 Details File "/var/lib/openstack/lib/python2.7/site-packages/nova/conductor/manager.py", line 627, in build_instances raise exception.MaxRetriesExceeded(reason=msg) Created Oct. 16, 2019, 4:06 p.m. I found more detailed error in nova-conductor 2019-10-16 19:06:57.076 1 ERROR nova.scheduler.utils [req-7f352cf5-d9b4-4478-abfc-f68d7298ea85 bc5015570893422bb07d9292ddfa1edc 77eaa44ce5124f6685fe27ac91758427 - default default] [instance: add8e0d3-4ce0-4611-8f26-0032484fb8f8] Error from last host: controller-0 (node controller-0): [u'Traceback (most recent call last):\n', u' File "/var/lib/openstack/lib/python2.7/site-packages/nova/compute/manager.py", line 1984, in _do_build_and_run_instance\n filter_properties, request_spec)\n', u' File "/var/lib/openstack/lib/python2.7/site-packages/nova/compute/manager.py", line 2354, in _build_and_run_instance\n instance_uuid=instance.uuid, reason=six.text_type(e))\n', u'RescheduledException: Build of instance add8e0d3-4ce0-4611-8f26-0032484fb8f8 was re-scheduled: Binding failed for port 3bfaeb9c-428c-45ed-9879-14214f55a967, please check neutron logs for more information.\n'] Neutron-server logs 2019-10-16 19:06:52.161 15 ERROR neutron.plugins.ml2.managers [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Failed to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 on host controller-0 for vnic_type normal using segments [{'network_id': '8a88d512-11e8-4938-847a-c8bed1e24fe0', 'segmentation_id': 10, 'physical_network': u'physnet0', 'id': '6bf6f798-b168-4845-983c-376fbcd07a35', 'network_type': u'vlan'}] 2019-10-16 19:06:52.161 15 ERROR neutron.plugins.ml2.managers [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Failed to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 on host controller-0 for vnic_type normal using segments [{'network_id': '8a88d512-11e8-4938-847a-c8bed1e24fe0', 'segmentation_id': 10, 'physical_network': u'physnet0', 'id': '6bf6f798-b168-4845-983c-376fbcd07a35', 'network_type': u'vlan'}] 2019-10-16 19:06:52.162 15 INFO neutron.plugins.ml2.plugin [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Attempt 10 to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 2019-10-16 19:06:52.162 15 INFO neutron.plugins.ml2.plugin [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Attempt 10 to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 2019-10-16 19:06:52.186 15 ERROR neutron.plugins.ml2.managers [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Failed to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 on host controller-0 for vnic_type normal using segments [{'network_id': '8a88d512-11e8-4938-847a-c8bed1e24fe0', 'segmentation_id': 10, 'physical_network': u'physnet0', 'id': '6bf6f798-b168-4845-983c-376fbcd07a35', 'network_type': u'vlan'}] 2019-10-16 19:06:52.186 15 ERROR neutron.plugins.ml2.managers [req-37355674-5d1f-4923-a2c4-2a6d28f6a39c 45b05cb1801d4c6e84cad7f33d37cdb5 253d07aff5f34a3caa9c4352e0e6070c - 8d7d355905a045ddaef6f8826cab5ad0 8d7d355905a045ddaef6f8826cab5ad0] Failed to bind port 3bfaeb9c-428c-45ed-9879-14214f55a967 on host controller-0 for vnic_type Anything i can check? Oror parhaps I miss some some configuration on the host. Thanks in advance. Regards, Mariano -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Thu Oct 17 07:57:49 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Thu, 17 Oct 2019 02:57:49 -0500 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <8c37da$5tv8l8@orsmga003.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191017T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-apiserver:v1.16.0 k8s.gcr.io/kube-proxy:v1.16.0 k8s.gcr.io/kube-controller-manager:v1.16.0 k8s.gcr.io/kube-scheduler:v1.16.0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From tingjie.chen at intel.com Thu Oct 17 08:49:44 2019 From: tingjie.chen at intel.com (Chen, Tingjie) Date: Thu, 17 Oct 2019 08:49:44 +0000 Subject: [Starlingx-discuss] About test cases in Ceph containerization Message-ID: Hi Ada & Fernando, I have file draft for test cases with Ceph containerization. https://ethercalc.openstack.org/81005mu7o1pg and steps described in: https://etherpad.openstack.org/p/stx-ceph-containerization-mimic-test-case Since in STX 3.0, we plan to integrate the Containerized Ceph deployment but not break current Native Ceph deployment. So some of traditional cases in STX 2.0 are not suitable, these cases are special for Kubernetes environment. We have 2 patches already submitted, and other changes are in progress. https://review.opendev.org/#/c/681457 https://review.opendev.org/#/c/687340/ Welcome to review and give comments to finalize. Thanks, Tingjie SSP NST Storage Tel: +86(21)88216699 Mobile: 15901876439 -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Thu Oct 17 12:59:30 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 17 Oct 2019 12:59:30 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C76608D7CA6@SHSMSX105.ccr.corp.intel.com> Hi Frank & Brent & all, I have updated my patches to remove the visible password for registry. Please help review the update in ansible-playbooks/stx-puppet. Here is the link for the patch list: https://review.opendev.org/#/q/topic:kata+(status:open) - Add a commit to make containerd the default CLI (and remove any docker code that is no longer needed) [shuicheng] do you mean change the "/var/lib/docker" directory to "/var/lib/containerd" for both docker and containerd? If the answer is yes, I prefer to do it later, after docker runtime is not used at all. Currently, armada is still using docker. - Add a test case for local registry pull/push and authentication [shuicheng] With the new patch, local registry still could be accessed both by Kubernetes and crictl. For crictl, username/password need be provided in CLI, similar to "docker login" for docker CLI. - Update code to ensure admin password is not visible [shuicheng] Done. Best Regards Shuicheng From: Miller, Frank Sent: Tuesday, October 15, 2019 10:16 PM To: starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting Since we did not get through the whole agenda today, I will schedule the next meeting 1 week from today. Minutes for Oct 15 meeting: 1. Review KATA containers feature with container Cores. Shuicheng to present feature overview and current status. - Shuicheng's commits: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) - Shuicheng presented his feature and what has been done so far (see his charts in separate email) Actions identified: - Concerns: Interaction with registry, admin password is visible - Add a commit to make containerd the default CLI (and remove any docker code that is no longer needed) - Add a test case for local registry pull/push and authentication - Update code to ensure admin password is not visible - Frank to book a follow-up meeting to continue the review (Frank to book Tuesday Oct 22) Frank -----Original Appointment----- From: Miller, Frank Sent: Thursday, October 10, 2019 2:55 PM To: Miller, Frank; starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: StarlingX Bi-Weekly Containerization Meeting When: Tuesday, October 15, 2019 9:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236 Apologies, re-sending without etherpad formatting. Note: We agreed to a new day and time for these meetings. For all who are working containerization features or LPs please join for our bi-weekly meeting. Agenda for October 15 meeting: 1. Review KATA containers feature with container Cores. Shuicheng to present feature overview and current status. - Shuicheng's commits: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) 2. Updates on other stx.3.0 container features for MS3 milestone: - 2004008: [Feature] Create HELM chart for Fault project [An Ran] - one commit needs a new approach - discussed in item #2 - Decision to be made about Horizon issue - do we keep FM containers enabled without Horizon for VM alarms? Or do we disable in stx.3.0 until issue can be addressed in stx.4.0? - 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] - require updated forecast - 2005514: QAT K8S device plugin support in StarlingX - Bruce: Code is out for review; Frank to follow-up with Cindy or feature primes for updated forecasts - 2005860: Upversion container components [Al Bailey] - 2004761: Integrate Backup & Restore with Containers [Ovidiu Poncea] 3. Update on stx.4.0 features: - 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC 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 Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Oct 17 13:43:15 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 17 Oct 2019 13:43:15 +0000 Subject: [Starlingx-discuss] Train upgrade for openstack clients In-Reply-To: <72AD03D27224C74982BE13246D75B39739A651A3@SHSMSX103.ccr.corp.intel.com> References: <72AD03D27224C74982BE13246D75B39739A64833@SHSMSX103.ccr.corp.intel.com> <72AD03D27224C74982BE13246D75B39739A651A3@SHSMSX103.ccr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BDFBF84E0@fmsmsx123.amr.corp.intel.com> Yan, thank you for making this very clear. As I read this, the puppet modules we use for the openstack clients are several releases old and the update to the Train version would be painful, er I mean lots of fun. I think we need some input from the broader community. What are the costs / risks of upgrading to puppet 5.0? Should we try to upgrade the client puppet modules ourselves (and contribute the changes upstream)? Or is there a better long way we should launch these clients, e.g. should we just write Ansible installers for them? My thanks to Dean for helping me understand what questions to ask :) brucej From: Chen, Yan [mailto:yan.chen at intel.com] Sent: Tuesday, October 15, 2019 10:43 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Train upgrade for openstack clients Hi, I'm now trying to upgrade the openstack clients installed on StarlingX to Train version. Currently I see the clients are Stein version, but the puppet packages (for those modules that we need to config on StarlingX host) are still old versions. [See the list below.] But for Train, I met a problem when I wanted to upgrade python-openstackclient/keystone to Train (4.0.0), the old puppet packages cannot work with Train clients and failed when running puppet-manifest-apply.sh. See from Stein keystone log, some of the deprecated cmds and options are planned to be removed in Train. If we want to make Train clients work, we may need to do the following steps: 1. Upgrade puppet itself (required 5.x by Train) 2. Upgrade all the OpenStack related puppet packages accordingly, and update StarlingX patches. 3. If flock puppet pkgs are based on puppet 4.8.2, we also need to upgrade our code. 4. If other puppet pkgs are based on puppet 4.8.2, we also need to upgrade those pkgs. So is it possible that we keep on using Stein clients with limited test now (need test with Train images, but suppose old functions should still work)? Here's the list of the puppet packages and StarlingX patches (for Stein it should be 14.1.0 - 14.4.0, and for Train 15.0.0 - 15.4.0): Pkg Current Version Train Upgrade to Meta Patch Patch puppet 4.8.2 5.x 2 5 puppet-keystone 11.3.0 15.x 6 5 puppet-oslo 11.3.0 15.x 3 2 puppet-openstacklib 11.5.0 15.x 2 1 puppet-horizon 11.5.0 15.x 2 1 puppet-barbican 11.3.0 15.x 0 0 Stein Keystone client logs: keystone:log 2019-10-10 10:04:44.050 111346 WARNING keystone.server.flask.request_processing.middleware.auth_context [-] The use of the '[DEFAULT] admin_token' configurationoption presents a significant security risk and should not be set. This option is deprecated in favor of using 'keystone-manage bootstrap' and will be removed in a future release. Yan -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Thu Oct 17 13:58:06 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 17 Oct 2019 13:58:06 +0000 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC007B05280@ALA-MBD.corp.ad.wrs.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B05280@ALA-MBD.corp.ad.wrs.com> Message-ID: Bill: In looking through the list the following people who have commits in the past 12 months are missing from the list. I recommend these be added: Patrick.bonnell at windriver.com Robert.church at windriver.com Gerry.kopec at windriver.com Allain.legacy at windriver.com Joseph.richard at windriver.com Frank -----Original Message----- From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Wednesday, October 16, 2019 2:40 PM To: starlingx-discuss at lists.starlingx.io Cc: Ildiko Vancsa ; Jones, Bruce E Subject: Re: [Starlingx-discuss] Voters for PL/TL election... As discussed on the Community Call today, there will be an election next week for the flock-services repo. Below is the (alphabetized) list of contributors who are currently eligible to vote on this position. Eligible voters will receive an invitation to vote this Sunday evening once the voting period begins. If you're not on this list but consider yourself to have contributed to this sub-project in the last 12 months and hence should be eligible to vote for this position, please say so here or directly to the election team (Ildiko, Bruce & myself). Bill... - al.bailey at windriver.com - alex.kozyrev at windriver.com - andy.ning at windriver.com - angie.wang at windriver.com - barton.wensley at windriver.com - bin.qian at windriver.com - chris.friesen at windriver.com - daniel.badea at windriver.com - david.sullivan at windriver.com - don.penney at windriver.com - dtroyer at gmail.com - elena.taivan at windriver.com - eric.barrett at windriver.com - eric.macdonald at windriver.com - erich.cordoba.malibran at intel.com - guozhen.she at intel.com - haochuan.z.chen at intel.com - jaegerandi at gmail.com - james.gauld at windriver.com - jason.mckenna at windriver.com - jerry.sun at windriver.com - john.kung at windriver.com - junbo85.li at gmail.com - kevin.smith at windriver.com - kristine.bujold at windriver.com - lachlan.plant at windriver.com - lihang0166 at fiberhome.com - lijunjie at cloudin.cn - lvcy at fiberhome.com - ma.lei at 99cloud.net - marcela.a.rosales.jimenez at intel.com - matt.peters at windriver.com - mingyuan.qi at intel.com - ovidiu.poncea at windriver.com - ran1.an at intel.com - scott.little at windriver.com - sgw at linux.intel.com - srifenbark at gmail.com - stefan.dinescu at windriver.com - steven.webster at windriver.com - sxmatch1986 at gmail.com - tao.liu at windriver.com - tee.ngo at windriver.com - teresa.ho at windriver.com - tyler.smith at windriver.com - wei.zhou at windriver.com - wzj334965317 at outlook.com - xbyan at fiberhome.com - xiefp88 at sina.com - yan.chen at intel.com - zhanglf01 at inspur.com - zhangzhaoshan at inspur.com - zhaolong at inspur.com - zhaowei7146 at fiberhome.com - zhipengs.liu at intel.com - zqhsh527 at 163.com -----Original Message----- From: Zvonar, Bill Sent: Wednesday, October 9, 2019 1:56 PM To: 'starlingx-discuss at lists.starlingx.io' Cc: Ildiko Vancsa ; 'Jones, Bruce E' Subject: Voters for PL/TL election... As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). Bill... build - don.penney at windriver.com - scott.little at windriver.com - dtroyer at gmail.com - al.bailey at windriver.com - tyler.smith at windriver.com - daniel.badea at windriver.com - sgw at linux.intel.com - erich.cordoba.malibran at intel.com - stefan.dinescu at windriver.com - ran1.an at intel.com - tao.liu at windriver.com - joseph.richard at windriver.com - felipe.de.jesus.ruiz.garcia at intel.com - angie.wang at windriver.com - Kristine.Bujold at windriver.com - jesus.ornelas.aguayo at intel.com - lihaijing at fiberhome.com - jason.mckenna at windriver.com - zhangyangyang at unionpay.com - jerry.sun at windriver.com - alex.kozyrev at windriver.com - steven.webster at windriver.com - jaegerandi at gmail.com - longx.li at intel.com - john.kung at windriver.com - maria.yousaf at windriver.com - zhipengs.liu at intel.com - lihang0166 at fiberhome.com - zhiguox.zhang at intel.com - bin.yang at intel.com - iwienand at redhat.com - marcela.a.rosales.jimenez at intel.com - tee.ngo at windriver.com - haochuan.z.chen at intel.com - caoran at fiberhome.com - zhang.kunpeng at 99cloud.net - Paul-Emile.Element at windriver.com config - angie.wang at windriver.com - tingjie.chen at intel.com - kevin.smith at windriver.com - ovidiu.poncea at windriver.com - bin.qian at windriver.com - joseph.richard at windriver.com - Kristine.Bujold at windriver.com - al.bailey at windriver.com - andy.ning at windriver.com - david.sullivan at windriver.com - daniel.badea at windriver.com - zhipengs.liu at intel.com - tao.liu at windriver.com - haochuan.z.chen at intel.com - lihang0166 at fiberhome.com - stefan.dinescu at windriver.com - ran1.an at intel.com - sgw at linux.intel.com - teresa.ho at windriver.com - eric.macdonald at windriver.com - alex.kozyrev at windriver.com - erich.cordoba.malibran at intel.com - scott.little at windriver.com - tee.ngo at windriver.com - tyler.smith at windriver.com - bin.yang at intel.com - john.kung at windriver.com - jaegerandi at gmail.com - mingyuan.qi at intel.com - eric.barrett at windriver.com - zhang.kunpeng at 99cloud.net - wei.zhou at windriver.com - steven.webster at windriver.com - jerry.sun at windriver.com - dtroyer at gmail.com - barton.wensley at windriver.com - matt.peters at windriver.com - zhu.boxiang at 99cloud.net - don.penney at windriver.com - James.Gauld at windriver.com - junbo85.li at gmail.com - chris.friesen at windriver.com - marcela.a.rosales.jimenez at intel.com - cheng1.li at intel.com - chenjie.xu at intel.com - allain.legacy at windriver.com - yan.chen at intel.com - elena.taivan at windriver.com - yizhoux.xu at intel.com - iwienand at redhat.com - irina.mihai at windriver.com - wzj334965317 at outlook.com - ma.lei at 99cloud.net - eric.zhang at windriver.com - Paul-Emile.Element at windriver.com - zhangyangyang at unionpay.com - daniel.chavolla at windriver.com - lachlan.plant at windriver.com - srifenbark at gmail.com - shoaib.nasir at windriver.com - singh.surya64mnnit at gmail.com containers - al.bailey at windriver.com - kevin.smith at windriver.com - zhipengs.liu at intel.com - ran1.an at intel.com distcloud - andy.ning at windriver.com - tyler.smith at windriver.com - scott.little at windriver.com - xiefp88 at sina.com - jaegerandi at gmail.com - dtroyer at gmail.com - tao.liu at windriver.com - don.penney at windriver.com - al.bailey at windriver.com - Kristine.Bujold at windriver.com - cao.yuan at 99cloud.net - wzj334965317 at outlook.com - alex.kozyrev at windriver.com - lachlan.plant at windriver.com - junbo85.li at gmail.com - srifenbark at gmail.com - barton.wensley at windriver.com distro - al.bailey at windriver.com - alex.kozyrev at windriver.com - jerry.sun at windriver.com - erich.cordoba.malibran at intel.com - daniel.badea at windriver.com - Kristine.Bujold at windriver.com - scott.little at windriver.com - jaegerandi at gmail.com - bin.qian at windriver.com - zhipengs.liu at intel.com - ran1.an at intel.com - eric.macdonald at windriver.com - john.kung at windriver.com - andy.ning at windriver.com - dtroyer at gmail.com - stefan.dinescu at windriver.com - bin.yang at intel.com - don.penney at windriver.com - eric.barrett at windriver.com - barton.wensley at windriver.com - junbo85.li at gmail.com - angie.wang at windriver.com - teresa.ho at windriver.com - sgw at linux.intel.com - tao.liu at windriver.com - zhiguox.zhang at intel.com - steven.webster at windriver.com - chenjie.xu at intel.com - James.Gauld at windriver.com - longx.li at intel.com - tyler.smith at windriver.com - chenlx at fiberhome.com - corvus at inaugust.com - chris.friesen at windriver.com - haochuan.z.chen at intel.com - daniel.chavolla at windriver.com - wei.zhou at windriver.com - ovidiu.poncea at windriver.com - joseph.richard at windriver.com - jason.mckenna at windriver.com - louie.kwan at windriver.com - Paul-Emile.Element at windriver.com - zhangyangyang at unionpay.com - tee.ngo at windriver.com - ma.lei at 99cloud.net docs - bruce.e.jones at intel.com - jaegerandi at gmail.com - chenlx at fiberhome.com - lihang0166 at fiberhome.com - srifenbark at gmail.com - xiefp88 at sina.com - liuyamin at fiberhome.com - lipan7195 at fiberhome.com - fungi at yuggoth.org - curtis at serverascode.com - iwienand at redhat.com - erich.cordoba.malibran at intel.com - li.xiaoli at 99cloud.net - zhang.kunpeng at 99cloud.net - dtroyer at gmail.com flock-services - tyler.smith at windriver.com - david.sullivan at windriver.com - Kristine.Bujold at windriver.com - al.bailey at windriver.com - jaegerandi at gmail.com - haochuan.z.chen at intel.com - dtroyer at gmail.com - teresa.ho at windriver.com - junbo85.li at gmail.com - ovidiu.poncea at windriver.com - yan.chen at intel.com - sgw at linux.intel.com - steven.webster at windriver.com - zhipengs.liu at intel.com - don.penney at windriver.com - eric.barrett at windriver.com - erich.cordoba.malibran at intel.com - scott.little at windriver.com - john.kung at windriver.com - wzj334965317 at outlook.com - tao.liu at windriver.com - stefan.dinescu at windriver.com - wei.zhou at windriver.com - James.Gauld at windriver.com - angie.wang at windriver.com - guozhen.she at intel.com - bin.qian at windriver.com - zqhsh527 at 163.com - andy.ning at windriver.com - mingyuan.qi at intel.com - xiefp88 at sina.com - daniel.badea at windriver.com - chris.friesen at windriver.com - elena.taivan at windriver.com - jerry.sun at windriver.com - marcela.a.rosales.jimenez at intel.com - xbyan at fiberhome.com - ran1.an at intel.com - alex.kozyrev at windriver.com - eric.macdonald at windriver.com - matt.peters at windriver.com - barton.wensley at windriver.com - kevin.smith at windriver.com - zhanglf01 at inspur.com - lachlan.plant at windriver.com - zhaowei7146 at fiberhome.com - lvcy at fiberhome.com - sxmatch1986 at gmail.com - ma.lei at 99cloud.net - lijunjie at cloudin.cn - jason.mckenna at windriver.com - srifenbark at gmail.com - tee.ngo at windriver.com - zhangzhaoshan at inspur.com - zhaolong at inspur.com - lihang0166 at fiberhome.com multios networking networking openstack_distro release security test - lihang0166 at fiberhome.com - dtroyer at gmail.com - erich.cordoba.malibran at intel.com - yang.liu at windriver.com - al.bailey at windriver.com - juan.p.gomez at intel.com - anujeyan.manokeran at windriver.com - maria.yousaf at windriver.com - peng.peng at windriver.com - marvin.huang at windriver.com [0] https://etherpad.openstack.org/p/stx-status _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Bill.Zvonar at windriver.com Thu Oct 17 14:06:57 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Thu, 17 Oct 2019 14:06:57 +0000 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: References: <586E8B730EA0DA4A9D6A80A10E486BC007B05280@ALA-MBD.corp.ad.wrs.com> Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B0575F@ALA-MBD.corp.ad.wrs.com> Can you specify which repos they made commits to? -----Original Message----- From: Miller, Frank Sent: Thursday, October 17, 2019 9:58 AM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Cc: Ildiko Vancsa ; Jones, Bruce E Subject: RE: Voters for PL/TL election... Bill: In looking through the list the following people who have commits in the past 12 months are missing from the list. I recommend these be added: Patrick.bonnell at windriver.com Robert.church at windriver.com Gerry.kopec at windriver.com Allain.legacy at windriver.com Joseph.richard at windriver.com Frank -----Original Message----- From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Wednesday, October 16, 2019 2:40 PM To: starlingx-discuss at lists.starlingx.io Cc: Ildiko Vancsa ; Jones, Bruce E Subject: Re: [Starlingx-discuss] Voters for PL/TL election... As discussed on the Community Call today, there will be an election next week for the flock-services repo. Below is the (alphabetized) list of contributors who are currently eligible to vote on this position. Eligible voters will receive an invitation to vote this Sunday evening once the voting period begins. If you're not on this list but consider yourself to have contributed to this sub-project in the last 12 months and hence should be eligible to vote for this position, please say so here or directly to the election team (Ildiko, Bruce & myself). Bill... - al.bailey at windriver.com - alex.kozyrev at windriver.com - andy.ning at windriver.com - angie.wang at windriver.com - barton.wensley at windriver.com - bin.qian at windriver.com - chris.friesen at windriver.com - daniel.badea at windriver.com - david.sullivan at windriver.com - don.penney at windriver.com - dtroyer at gmail.com - elena.taivan at windriver.com - eric.barrett at windriver.com - eric.macdonald at windriver.com - erich.cordoba.malibran at intel.com - guozhen.she at intel.com - haochuan.z.chen at intel.com - jaegerandi at gmail.com - james.gauld at windriver.com - jason.mckenna at windriver.com - jerry.sun at windriver.com - john.kung at windriver.com - junbo85.li at gmail.com - kevin.smith at windriver.com - kristine.bujold at windriver.com - lachlan.plant at windriver.com - lihang0166 at fiberhome.com - lijunjie at cloudin.cn - lvcy at fiberhome.com - ma.lei at 99cloud.net - marcela.a.rosales.jimenez at intel.com - matt.peters at windriver.com - mingyuan.qi at intel.com - ovidiu.poncea at windriver.com - ran1.an at intel.com - scott.little at windriver.com - sgw at linux.intel.com - srifenbark at gmail.com - stefan.dinescu at windriver.com - steven.webster at windriver.com - sxmatch1986 at gmail.com - tao.liu at windriver.com - tee.ngo at windriver.com - teresa.ho at windriver.com - tyler.smith at windriver.com - wei.zhou at windriver.com - wzj334965317 at outlook.com - xbyan at fiberhome.com - xiefp88 at sina.com - yan.chen at intel.com - zhanglf01 at inspur.com - zhangzhaoshan at inspur.com - zhaolong at inspur.com - zhaowei7146 at fiberhome.com - zhipengs.liu at intel.com - zqhsh527 at 163.com -----Original Message----- From: Zvonar, Bill Sent: Wednesday, October 9, 2019 1:56 PM To: 'starlingx-discuss at lists.starlingx.io' Cc: Ildiko Vancsa ; 'Jones, Bruce E' Subject: Voters for PL/TL election... As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). Bill... build - don.penney at windriver.com - scott.little at windriver.com - dtroyer at gmail.com - al.bailey at windriver.com - tyler.smith at windriver.com - daniel.badea at windriver.com - sgw at linux.intel.com - erich.cordoba.malibran at intel.com - stefan.dinescu at windriver.com - ran1.an at intel.com - tao.liu at windriver.com - joseph.richard at windriver.com - felipe.de.jesus.ruiz.garcia at intel.com - angie.wang at windriver.com - Kristine.Bujold at windriver.com - jesus.ornelas.aguayo at intel.com - lihaijing at fiberhome.com - jason.mckenna at windriver.com - zhangyangyang at unionpay.com - jerry.sun at windriver.com - alex.kozyrev at windriver.com - steven.webster at windriver.com - jaegerandi at gmail.com - longx.li at intel.com - john.kung at windriver.com - maria.yousaf at windriver.com - zhipengs.liu at intel.com - lihang0166 at fiberhome.com - zhiguox.zhang at intel.com - bin.yang at intel.com - iwienand at redhat.com - marcela.a.rosales.jimenez at intel.com - tee.ngo at windriver.com - haochuan.z.chen at intel.com - caoran at fiberhome.com - zhang.kunpeng at 99cloud.net - Paul-Emile.Element at windriver.com config - angie.wang at windriver.com - tingjie.chen at intel.com - kevin.smith at windriver.com - ovidiu.poncea at windriver.com - bin.qian at windriver.com - joseph.richard at windriver.com - Kristine.Bujold at windriver.com - al.bailey at windriver.com - andy.ning at windriver.com - david.sullivan at windriver.com - daniel.badea at windriver.com - zhipengs.liu at intel.com - tao.liu at windriver.com - haochuan.z.chen at intel.com - lihang0166 at fiberhome.com - stefan.dinescu at windriver.com - ran1.an at intel.com - sgw at linux.intel.com - teresa.ho at windriver.com - eric.macdonald at windriver.com - alex.kozyrev at windriver.com - erich.cordoba.malibran at intel.com - scott.little at windriver.com - tee.ngo at windriver.com - tyler.smith at windriver.com - bin.yang at intel.com - john.kung at windriver.com - jaegerandi at gmail.com - mingyuan.qi at intel.com - eric.barrett at windriver.com - zhang.kunpeng at 99cloud.net - wei.zhou at windriver.com - steven.webster at windriver.com - jerry.sun at windriver.com - dtroyer at gmail.com - barton.wensley at windriver.com - matt.peters at windriver.com - zhu.boxiang at 99cloud.net - don.penney at windriver.com - James.Gauld at windriver.com - junbo85.li at gmail.com - chris.friesen at windriver.com - marcela.a.rosales.jimenez at intel.com - cheng1.li at intel.com - chenjie.xu at intel.com - allain.legacy at windriver.com - yan.chen at intel.com - elena.taivan at windriver.com - yizhoux.xu at intel.com - iwienand at redhat.com - irina.mihai at windriver.com - wzj334965317 at outlook.com - ma.lei at 99cloud.net - eric.zhang at windriver.com - Paul-Emile.Element at windriver.com - zhangyangyang at unionpay.com - daniel.chavolla at windriver.com - lachlan.plant at windriver.com - srifenbark at gmail.com - shoaib.nasir at windriver.com - singh.surya64mnnit at gmail.com containers - al.bailey at windriver.com - kevin.smith at windriver.com - zhipengs.liu at intel.com - ran1.an at intel.com distcloud - andy.ning at windriver.com - tyler.smith at windriver.com - scott.little at windriver.com - xiefp88 at sina.com - jaegerandi at gmail.com - dtroyer at gmail.com - tao.liu at windriver.com - don.penney at windriver.com - al.bailey at windriver.com - Kristine.Bujold at windriver.com - cao.yuan at 99cloud.net - wzj334965317 at outlook.com - alex.kozyrev at windriver.com - lachlan.plant at windriver.com - junbo85.li at gmail.com - srifenbark at gmail.com - barton.wensley at windriver.com distro - al.bailey at windriver.com - alex.kozyrev at windriver.com - jerry.sun at windriver.com - erich.cordoba.malibran at intel.com - daniel.badea at windriver.com - Kristine.Bujold at windriver.com - scott.little at windriver.com - jaegerandi at gmail.com - bin.qian at windriver.com - zhipengs.liu at intel.com - ran1.an at intel.com - eric.macdonald at windriver.com - john.kung at windriver.com - andy.ning at windriver.com - dtroyer at gmail.com - stefan.dinescu at windriver.com - bin.yang at intel.com - don.penney at windriver.com - eric.barrett at windriver.com - barton.wensley at windriver.com - junbo85.li at gmail.com - angie.wang at windriver.com - teresa.ho at windriver.com - sgw at linux.intel.com - tao.liu at windriver.com - zhiguox.zhang at intel.com - steven.webster at windriver.com - chenjie.xu at intel.com - James.Gauld at windriver.com - longx.li at intel.com - tyler.smith at windriver.com - chenlx at fiberhome.com - corvus at inaugust.com - chris.friesen at windriver.com - haochuan.z.chen at intel.com - daniel.chavolla at windriver.com - wei.zhou at windriver.com - ovidiu.poncea at windriver.com - joseph.richard at windriver.com - jason.mckenna at windriver.com - louie.kwan at windriver.com - Paul-Emile.Element at windriver.com - zhangyangyang at unionpay.com - tee.ngo at windriver.com - ma.lei at 99cloud.net docs - bruce.e.jones at intel.com - jaegerandi at gmail.com - chenlx at fiberhome.com - lihang0166 at fiberhome.com - srifenbark at gmail.com - xiefp88 at sina.com - liuyamin at fiberhome.com - lipan7195 at fiberhome.com - fungi at yuggoth.org - curtis at serverascode.com - iwienand at redhat.com - erich.cordoba.malibran at intel.com - li.xiaoli at 99cloud.net - zhang.kunpeng at 99cloud.net - dtroyer at gmail.com flock-services - tyler.smith at windriver.com - david.sullivan at windriver.com - Kristine.Bujold at windriver.com - al.bailey at windriver.com - jaegerandi at gmail.com - haochuan.z.chen at intel.com - dtroyer at gmail.com - teresa.ho at windriver.com - junbo85.li at gmail.com - ovidiu.poncea at windriver.com - yan.chen at intel.com - sgw at linux.intel.com - steven.webster at windriver.com - zhipengs.liu at intel.com - don.penney at windriver.com - eric.barrett at windriver.com - erich.cordoba.malibran at intel.com - scott.little at windriver.com - john.kung at windriver.com - wzj334965317 at outlook.com - tao.liu at windriver.com - stefan.dinescu at windriver.com - wei.zhou at windriver.com - James.Gauld at windriver.com - angie.wang at windriver.com - guozhen.she at intel.com - bin.qian at windriver.com - zqhsh527 at 163.com - andy.ning at windriver.com - mingyuan.qi at intel.com - xiefp88 at sina.com - daniel.badea at windriver.com - chris.friesen at windriver.com - elena.taivan at windriver.com - jerry.sun at windriver.com - marcela.a.rosales.jimenez at intel.com - xbyan at fiberhome.com - ran1.an at intel.com - alex.kozyrev at windriver.com - eric.macdonald at windriver.com - matt.peters at windriver.com - barton.wensley at windriver.com - kevin.smith at windriver.com - zhanglf01 at inspur.com - lachlan.plant at windriver.com - zhaowei7146 at fiberhome.com - lvcy at fiberhome.com - sxmatch1986 at gmail.com - ma.lei at 99cloud.net - lijunjie at cloudin.cn - jason.mckenna at windriver.com - srifenbark at gmail.com - tee.ngo at windriver.com - zhangzhaoshan at inspur.com - zhaolong at inspur.com - lihang0166 at fiberhome.com multios networking networking openstack_distro release security test - lihang0166 at fiberhome.com - dtroyer at gmail.com - erich.cordoba.malibran at intel.com - yang.liu at windriver.com - al.bailey at windriver.com - juan.p.gomez at intel.com - anujeyan.manokeran at windriver.com - maria.yousaf at windriver.com - peng.peng at windriver.com - marvin.huang at windriver.com [0] https://etherpad.openstack.org/p/stx-status _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Al.Bailey at windriver.com Thu Oct 17 14:47:02 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Thu, 17 Oct 2019 14:47:02 +0000 Subject: [Starlingx-discuss] Train upgrade for openstack clients In-Reply-To: <9A85D2917C58154C960D95352B22818BDFBF84E0@fmsmsx123.amr.corp.intel.com> References: <72AD03D27224C74982BE13246D75B39739A64833@SHSMSX103.ccr.corp.intel.com> <72AD03D27224C74982BE13246D75B39739A651A3@SHSMSX103.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BDFBF84E0@fmsmsx123.amr.corp.intel.com> Message-ID: I think the puppet 5 upgrade ends up being one of the more complicated parts of this activity. It looks like for 5.0.x you need to be cautious about is all the deprecated features in 4 that were removed in 5. It would not surprise me if we were still using some of those deprecated parts. https://github.com/puppetlabs/docs-archive/blob/master/puppet/5.0/release_notes.markdown Puppet 5 also uses a newer ruby. We ship ruby 2.0 now. The notes for 5.0 indicate ruby 2.4, which is extra work and can take a while if existing ruby code needs to be changed. Puppet 5 also claims to have hiera 5 built in. I don't know what that means, we ship hiera 1.3.4 separarately, so there may be packaging concerns there as well. Last time when I upversioned puppet from puppet 3 to 4 the most unexpected thing was not the code changes required, but the runtime behavior was different. Example: https://opendev.org/starlingx/integ/src/branch/master/config/puppet-4.8.2/centos/patches/1005-Set-strict_variables-and-basemodulepath-in-puppet.co.patch Experiment with installing train keystone/barbican/horizon with the existing puppet modules. If a config value is incompatible, then it may require a local change, or an upversion. Al From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, October 17, 2019 9:43 AM To: Chen, Yan; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Train upgrade for openstack clients Yan, thank you for making this very clear. As I read this, the puppet modules we use for the openstack clients are several releases old and the update to the Train version would be painful, er I mean lots of fun. I think we need some input from the broader community. What are the costs / risks of upgrading to puppet 5.0? Should we try to upgrade the client puppet modules ourselves (and contribute the changes upstream)? Or is there a better long way we should launch these clients, e.g. should we just write Ansible installers for them? My thanks to Dean for helping me understand what questions to ask :) brucej From: Chen, Yan [mailto:yan.chen at intel.com] Sent: Tuesday, October 15, 2019 10:43 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Train upgrade for openstack clients Hi, I'm now trying to upgrade the openstack clients installed on StarlingX to Train version. Currently I see the clients are Stein version, but the puppet packages (for those modules that we need to config on StarlingX host) are still old versions. [See the list below.] But for Train, I met a problem when I wanted to upgrade python-openstackclient/keystone to Train (4.0.0), the old puppet packages cannot work with Train clients and failed when running puppet-manifest-apply.sh. See from Stein keystone log, some of the deprecated cmds and options are planned to be removed in Train. If we want to make Train clients work, we may need to do the following steps: 1. Upgrade puppet itself (required 5.x by Train) 2. Upgrade all the OpenStack related puppet packages accordingly, and update StarlingX patches. 3. If flock puppet pkgs are based on puppet 4.8.2, we also need to upgrade our code. 4. If other puppet pkgs are based on puppet 4.8.2, we also need to upgrade those pkgs. So is it possible that we keep on using Stein clients with limited test now (need test with Train images, but suppose old functions should still work)? Here's the list of the puppet packages and StarlingX patches (for Stein it should be 14.1.0 - 14.4.0, and for Train 15.0.0 - 15.4.0): Pkg Current Version Train Upgrade to Meta Patch Patch puppet 4.8.2 5.x 2 5 puppet-keystone 11.3.0 15.x 6 5 puppet-oslo 11.3.0 15.x 3 2 puppet-openstacklib 11.5.0 15.x 2 1 puppet-horizon 11.5.0 15.x 2 1 puppet-barbican 11.3.0 15.x 0 0 Stein Keystone client logs: keystone:log 2019-10-10 10:04:44.050 111346 WARNING keystone.server.flask.request_processing.middleware.auth_context [-] The use of the '[DEFAULT] admin_token' configurationoption presents a significant security risk and should not be set. This option is deprecated in favor of using 'keystone-manage bootstrap' and will be removed in a future release. Yan -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Thu Oct 17 14:52:21 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 17 Oct 2019 14:52:21 +0000 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC007B0575F@ALA-MBD.corp.ad.wrs.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B05280@ALA-MBD.corp.ad.wrs.com> <586E8B730EA0DA4A9D6A80A10E486BC007B0575F@ALA-MBD.corp.ad.wrs.com> Message-ID: See below inline with repos these folks have contributed to since Oct 2018 and the # of commits across those repos. Frank -----Original Message----- From: Zvonar, Bill Sent: Thursday, October 17, 2019 10:07 AM To: Miller, Frank ; starlingx-discuss at lists.starlingx.io Cc: Ildiko Vancsa ; Jones, Bruce E Subject: RE: Voters for PL/TL election... Can you specify which repos they made commits to? -----Original Message----- From: Miller, Frank Sent: Thursday, October 17, 2019 9:58 AM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Cc: Ildiko Vancsa ; Jones, Bruce E Subject: RE: Voters for PL/TL election... Bill: In looking through the list the following people who have commits in the past 12 months are missing from the list. I recommend these be added: Patrick.bonnell at windriver.com [config, gui, upstream] - 7 commits Robert.church at windriver.com [config, integ, metal, root, specs, tools, upstream] - 82 commits Gerry.kopec at windriver.com [config, integ, upstream] - 23 commits Allain.legacy at windriver.com [config] - 7 commits Joseph.richard at windriver.com [config, integ, metal, root, tools] - 17 commits Frank -----Original Message----- From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Wednesday, October 16, 2019 2:40 PM To: starlingx-discuss at lists.starlingx.io Cc: Ildiko Vancsa ; Jones, Bruce E Subject: Re: [Starlingx-discuss] Voters for PL/TL election... As discussed on the Community Call today, there will be an election next week for the flock-services repo. Below is the (alphabetized) list of contributors who are currently eligible to vote on this position. Eligible voters will receive an invitation to vote this Sunday evening once the voting period begins. If you're not on this list but consider yourself to have contributed to this sub-project in the last 12 months and hence should be eligible to vote for this position, please say so here or directly to the election team (Ildiko, Bruce & myself). Bill... - al.bailey at windriver.com - alex.kozyrev at windriver.com - andy.ning at windriver.com - angie.wang at windriver.com - barton.wensley at windriver.com - bin.qian at windriver.com - chris.friesen at windriver.com - daniel.badea at windriver.com - david.sullivan at windriver.com - don.penney at windriver.com - dtroyer at gmail.com - elena.taivan at windriver.com - eric.barrett at windriver.com - eric.macdonald at windriver.com - erich.cordoba.malibran at intel.com - guozhen.she at intel.com - haochuan.z.chen at intel.com - jaegerandi at gmail.com - james.gauld at windriver.com - jason.mckenna at windriver.com - jerry.sun at windriver.com - john.kung at windriver.com - junbo85.li at gmail.com - kevin.smith at windriver.com - kristine.bujold at windriver.com - lachlan.plant at windriver.com - lihang0166 at fiberhome.com - lijunjie at cloudin.cn - lvcy at fiberhome.com - ma.lei at 99cloud.net - marcela.a.rosales.jimenez at intel.com - matt.peters at windriver.com - mingyuan.qi at intel.com - ovidiu.poncea at windriver.com - ran1.an at intel.com - scott.little at windriver.com - sgw at linux.intel.com - srifenbark at gmail.com - stefan.dinescu at windriver.com - steven.webster at windriver.com - sxmatch1986 at gmail.com - tao.liu at windriver.com - tee.ngo at windriver.com - teresa.ho at windriver.com - tyler.smith at windriver.com - wei.zhou at windriver.com - wzj334965317 at outlook.com - xbyan at fiberhome.com - xiefp88 at sina.com - yan.chen at intel.com - zhanglf01 at inspur.com - zhangzhaoshan at inspur.com - zhaolong at inspur.com - zhaowei7146 at fiberhome.com - zhipengs.liu at intel.com - zqhsh527 at 163.com -----Original Message----- From: Zvonar, Bill Sent: Wednesday, October 9, 2019 1:56 PM To: 'starlingx-discuss at lists.starlingx.io' Cc: Ildiko Vancsa ; 'Jones, Bruce E' Subject: Voters for PL/TL election... As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). Bill... build - don.penney at windriver.com - scott.little at windriver.com - dtroyer at gmail.com - al.bailey at windriver.com - tyler.smith at windriver.com - daniel.badea at windriver.com - sgw at linux.intel.com - erich.cordoba.malibran at intel.com - stefan.dinescu at windriver.com - ran1.an at intel.com - tao.liu at windriver.com - joseph.richard at windriver.com - felipe.de.jesus.ruiz.garcia at intel.com - angie.wang at windriver.com - Kristine.Bujold at windriver.com - jesus.ornelas.aguayo at intel.com - lihaijing at fiberhome.com - jason.mckenna at windriver.com - zhangyangyang at unionpay.com - jerry.sun at windriver.com - alex.kozyrev at windriver.com - steven.webster at windriver.com - jaegerandi at gmail.com - longx.li at intel.com - john.kung at windriver.com - maria.yousaf at windriver.com - zhipengs.liu at intel.com - lihang0166 at fiberhome.com - zhiguox.zhang at intel.com - bin.yang at intel.com - iwienand at redhat.com - marcela.a.rosales.jimenez at intel.com - tee.ngo at windriver.com - haochuan.z.chen at intel.com - caoran at fiberhome.com - zhang.kunpeng at 99cloud.net - Paul-Emile.Element at windriver.com config - angie.wang at windriver.com - tingjie.chen at intel.com - kevin.smith at windriver.com - ovidiu.poncea at windriver.com - bin.qian at windriver.com - joseph.richard at windriver.com - Kristine.Bujold at windriver.com - al.bailey at windriver.com - andy.ning at windriver.com - david.sullivan at windriver.com - daniel.badea at windriver.com - zhipengs.liu at intel.com - tao.liu at windriver.com - haochuan.z.chen at intel.com - lihang0166 at fiberhome.com - stefan.dinescu at windriver.com - ran1.an at intel.com - sgw at linux.intel.com - teresa.ho at windriver.com - eric.macdonald at windriver.com - alex.kozyrev at windriver.com - erich.cordoba.malibran at intel.com - scott.little at windriver.com - tee.ngo at windriver.com - tyler.smith at windriver.com - bin.yang at intel.com - john.kung at windriver.com - jaegerandi at gmail.com - mingyuan.qi at intel.com - eric.barrett at windriver.com - zhang.kunpeng at 99cloud.net - wei.zhou at windriver.com - steven.webster at windriver.com - jerry.sun at windriver.com - dtroyer at gmail.com - barton.wensley at windriver.com - matt.peters at windriver.com - zhu.boxiang at 99cloud.net - don.penney at windriver.com - James.Gauld at windriver.com - junbo85.li at gmail.com - chris.friesen at windriver.com - marcela.a.rosales.jimenez at intel.com - cheng1.li at intel.com - chenjie.xu at intel.com - allain.legacy at windriver.com - yan.chen at intel.com - elena.taivan at windriver.com - yizhoux.xu at intel.com - iwienand at redhat.com - irina.mihai at windriver.com - wzj334965317 at outlook.com - ma.lei at 99cloud.net - eric.zhang at windriver.com - Paul-Emile.Element at windriver.com - zhangyangyang at unionpay.com - daniel.chavolla at windriver.com - lachlan.plant at windriver.com - srifenbark at gmail.com - shoaib.nasir at windriver.com - singh.surya64mnnit at gmail.com containers - al.bailey at windriver.com - kevin.smith at windriver.com - zhipengs.liu at intel.com - ran1.an at intel.com distcloud - andy.ning at windriver.com - tyler.smith at windriver.com - scott.little at windriver.com - xiefp88 at sina.com - jaegerandi at gmail.com - dtroyer at gmail.com - tao.liu at windriver.com - don.penney at windriver.com - al.bailey at windriver.com - Kristine.Bujold at windriver.com - cao.yuan at 99cloud.net - wzj334965317 at outlook.com - alex.kozyrev at windriver.com - lachlan.plant at windriver.com - junbo85.li at gmail.com - srifenbark at gmail.com - barton.wensley at windriver.com distro - al.bailey at windriver.com - alex.kozyrev at windriver.com - jerry.sun at windriver.com - erich.cordoba.malibran at intel.com - daniel.badea at windriver.com - Kristine.Bujold at windriver.com - scott.little at windriver.com - jaegerandi at gmail.com - bin.qian at windriver.com - zhipengs.liu at intel.com - ran1.an at intel.com - eric.macdonald at windriver.com - john.kung at windriver.com - andy.ning at windriver.com - dtroyer at gmail.com - stefan.dinescu at windriver.com - bin.yang at intel.com - don.penney at windriver.com - eric.barrett at windriver.com - barton.wensley at windriver.com - junbo85.li at gmail.com - angie.wang at windriver.com - teresa.ho at windriver.com - sgw at linux.intel.com - tao.liu at windriver.com - zhiguox.zhang at intel.com - steven.webster at windriver.com - chenjie.xu at intel.com - James.Gauld at windriver.com - longx.li at intel.com - tyler.smith at windriver.com - chenlx at fiberhome.com - corvus at inaugust.com - chris.friesen at windriver.com - haochuan.z.chen at intel.com - daniel.chavolla at windriver.com - wei.zhou at windriver.com - ovidiu.poncea at windriver.com - joseph.richard at windriver.com - jason.mckenna at windriver.com - louie.kwan at windriver.com - Paul-Emile.Element at windriver.com - zhangyangyang at unionpay.com - tee.ngo at windriver.com - ma.lei at 99cloud.net docs - bruce.e.jones at intel.com - jaegerandi at gmail.com - chenlx at fiberhome.com - lihang0166 at fiberhome.com - srifenbark at gmail.com - xiefp88 at sina.com - liuyamin at fiberhome.com - lipan7195 at fiberhome.com - fungi at yuggoth.org - curtis at serverascode.com - iwienand at redhat.com - erich.cordoba.malibran at intel.com - li.xiaoli at 99cloud.net - zhang.kunpeng at 99cloud.net - dtroyer at gmail.com flock-services - tyler.smith at windriver.com - david.sullivan at windriver.com - Kristine.Bujold at windriver.com - al.bailey at windriver.com - jaegerandi at gmail.com - haochuan.z.chen at intel.com - dtroyer at gmail.com - teresa.ho at windriver.com - junbo85.li at gmail.com - ovidiu.poncea at windriver.com - yan.chen at intel.com - sgw at linux.intel.com - steven.webster at windriver.com - zhipengs.liu at intel.com - don.penney at windriver.com - eric.barrett at windriver.com - erich.cordoba.malibran at intel.com - scott.little at windriver.com - john.kung at windriver.com - wzj334965317 at outlook.com - tao.liu at windriver.com - stefan.dinescu at windriver.com - wei.zhou at windriver.com - James.Gauld at windriver.com - angie.wang at windriver.com - guozhen.she at intel.com - bin.qian at windriver.com - zqhsh527 at 163.com - andy.ning at windriver.com - mingyuan.qi at intel.com - xiefp88 at sina.com - daniel.badea at windriver.com - chris.friesen at windriver.com - elena.taivan at windriver.com - jerry.sun at windriver.com - marcela.a.rosales.jimenez at intel.com - xbyan at fiberhome.com - ran1.an at intel.com - alex.kozyrev at windriver.com - eric.macdonald at windriver.com - matt.peters at windriver.com - barton.wensley at windriver.com - kevin.smith at windriver.com - zhanglf01 at inspur.com - lachlan.plant at windriver.com - zhaowei7146 at fiberhome.com - lvcy at fiberhome.com - sxmatch1986 at gmail.com - ma.lei at 99cloud.net - lijunjie at cloudin.cn - jason.mckenna at windriver.com - srifenbark at gmail.com - tee.ngo at windriver.com - zhangzhaoshan at inspur.com - zhaolong at inspur.com - lihang0166 at fiberhome.com multios networking networking openstack_distro release security test - lihang0166 at fiberhome.com - dtroyer at gmail.com - erich.cordoba.malibran at intel.com - yang.liu at windriver.com - al.bailey at windriver.com - juan.p.gomez at intel.com - anujeyan.manokeran at windriver.com - maria.yousaf at windriver.com - peng.peng at windriver.com - marvin.huang at windriver.com [0] https://etherpad.openstack.org/p/stx-status _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Thu Oct 17 16:14:30 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 17 Oct 2019 18:14:30 +0200 Subject: [Starlingx-discuss] Election update - Flock Services voting requires OSF Individual Membership - ACTION NEEDED Message-ID: <21B19FEC-7B45-4B7E-B217-1DF242FD36F5@gmail.com> Hi, We have two candidates for the Flock Services project PL position: https://opendev.org/starlingx/election/src/branch/master/candidates/2019_H2/flock-services/pl Electorate: Individuals who are Individual Members of the OpenStack Foundation and contributed to the project during the interval of October 6, 2018 - October 6, 2019 are eligible to vote in the voting period that starts this Sunday (October 20) at 2045 UTC. __If you do not have an active OpenStack Foundation Individual Member account you need to register/update your profile here: https://www.openstack.org/join__ If you fall under the group of electorates for the Flock Services elections please check and in case needed add/update your profile __before the voting period starts__. In case you have questions please reply to this thread or reach out to the election officials[1]. Thanks, [1] https://docs.starlingx.io/election/#election-officials From sgw at linux.intel.com Thu Oct 17 16:24:04 2019 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 17 Oct 2019 09:24:04 -0700 Subject: [Starlingx-discuss] Build Team Meeting - Notes 10/17/2019 Message-ID: <9ebca49a-6d66-ef19-f941-bb401df84f78@linux.intel.com> October 17, 2019 Tl/PL Elections Saul will be TL Frank stepped up as PL - Thanks Frank! Comment was Saul is TL for 3 projects so not PL also here! Build-Layering Being worked by Martin Reviews pending Scott AR: to check if reviews can go independantly Final cut-over has Cengn impact, so should be post 3.0 Saul to get testing manifiest Need Changes for DOCS on usage and setup. * Who owns the Docs update? Cengn Access Should not be a problem to add additional access Saul +1 (TBD) Must be careful about the work and well coordinated This is Jenkins based! Review Build model Jenkins First model vs Git First model Maybe get a containerized or vm version of CENGN for testing Versioning Started doing manual update of RPM Package %Version to 2.0.0 of CentOS packages Issues with older PKG-INFO Deprecate usage Some packages read VERSION from build_srpm.data Needs more investigation Used to generate SRPM in some cases, not all MAJOR/MINOR macros are set from specfile and passed to Makefile Not used constitently in Makefile! Makefile uses different macro for library Library version should not be connected to Package versioning (in all cases) Saul forgot some other smaller issues discovered. De-Branding Started to send patches for de-branding for mirroring and repo Some changes are standalone and can be merged in 3.0 Other changes will require cut-over change with Docs and CENGN Zuul/OBS Builds Currently setup for openSUSE as non-voting Need to add template to other services Currently non-voting as it's just starting the build Zuul job just starts the OBS build does not get actual result of OSB build N ext step will be to try and build a CentOS repo as a prototype 2.0.1 Status Almost complete Need to fix the manifest repo and it was tagged before the review was merged Need to get manifest re-tagged Scripts are fixed to prevent this in the future. From ildiko at openstack.org Thu Oct 17 17:00:33 2019 From: ildiko at openstack.org (Ildiko Vancsa) Date: Thu, 17 Oct 2019 19:00:33 +0200 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: References: <586E8B730EA0DA4A9D6A80A10E486BC007B05280@ALA-MBD.corp.ad.wrs.com> <586E8B730EA0DA4A9D6A80A10E486BC007B0575F@ALA-MBD.corp.ad.wrs.com> Message-ID: <8F979CFE-FC4A-41D6-8F29-53878B1BE83B@openstack.org> Hi Frank, Just a heads up that the ‘config’ repo is not under the Flock Services project. Thanks, Ildikó > On Oct 17, 2019, at 16:52, Miller, Frank wrote: > > See below inline with repos these folks have contributed to since Oct 2018 and the # of commits across those repos. > > Frank > > -----Original Message----- > From: Zvonar, Bill > Sent: Thursday, October 17, 2019 10:07 AM > To: Miller, Frank ; starlingx-discuss at lists.starlingx.io > Cc: Ildiko Vancsa ; Jones, Bruce E > Subject: RE: Voters for PL/TL election... > > Can you specify which repos they made commits to? > > -----Original Message----- > From: Miller, Frank > Sent: Thursday, October 17, 2019 9:58 AM > To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io > Cc: Ildiko Vancsa ; Jones, Bruce E > Subject: RE: Voters for PL/TL election... > > Bill: > > In looking through the list the following people who have commits in the past 12 months are missing from the list. I recommend these be added: > > Patrick.bonnell at windriver.com [config, gui, upstream] - 7 commits > Robert.church at windriver.com [config, integ, metal, root, specs, tools, upstream] - 82 commits > Gerry.kopec at windriver.com [config, integ, upstream] - 23 commits > Allain.legacy at windriver.com [config] - 7 commits > Joseph.richard at windriver.com [config, integ, metal, root, tools] - 17 commits > > > Frank > > -----Original Message----- > From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] > Sent: Wednesday, October 16, 2019 2:40 PM > To: starlingx-discuss at lists.starlingx.io > Cc: Ildiko Vancsa ; Jones, Bruce E > Subject: Re: [Starlingx-discuss] Voters for PL/TL election... > > As discussed on the Community Call today, there will be an election next week for the flock-services repo. > > Below is the (alphabetized) list of contributors who are currently eligible to vote on this position. > > Eligible voters will receive an invitation to vote this Sunday evening once the voting period begins. > > If you're not on this list but consider yourself to have contributed to this sub-project in the last 12 months and hence should be eligible to vote for this position, please say so here or directly to the election team (Ildiko, Bruce & myself). > > Bill... > > - al.bailey at windriver.com > - alex.kozyrev at windriver.com > - andy.ning at windriver.com > - angie.wang at windriver.com > - barton.wensley at windriver.com > - bin.qian at windriver.com > - chris.friesen at windriver.com > - daniel.badea at windriver.com > - david.sullivan at windriver.com > - don.penney at windriver.com > - dtroyer at gmail.com > - elena.taivan at windriver.com > - eric.barrett at windriver.com > - eric.macdonald at windriver.com > - erich.cordoba.malibran at intel.com > - guozhen.she at intel.com > - haochuan.z.chen at intel.com > - jaegerandi at gmail.com > - james.gauld at windriver.com > - jason.mckenna at windriver.com > - jerry.sun at windriver.com > - john.kung at windriver.com > - junbo85.li at gmail.com > - kevin.smith at windriver.com > - kristine.bujold at windriver.com > - lachlan.plant at windriver.com > - lihang0166 at fiberhome.com > - lijunjie at cloudin.cn > - lvcy at fiberhome.com > - ma.lei at 99cloud.net > - marcela.a.rosales.jimenez at intel.com > - matt.peters at windriver.com > - mingyuan.qi at intel.com > - ovidiu.poncea at windriver.com > - ran1.an at intel.com > - scott.little at windriver.com > - sgw at linux.intel.com > - srifenbark at gmail.com > - stefan.dinescu at windriver.com > - steven.webster at windriver.com > - sxmatch1986 at gmail.com > - tao.liu at windriver.com > - tee.ngo at windriver.com > - teresa.ho at windriver.com > - tyler.smith at windriver.com > - wei.zhou at windriver.com > - wzj334965317 at outlook.com > - xbyan at fiberhome.com > - xiefp88 at sina.com > - yan.chen at intel.com > - zhanglf01 at inspur.com > - zhangzhaoshan at inspur.com > - zhaolong at inspur.com > - zhaowei7146 at fiberhome.com > - zhipengs.liu at intel.com > - zqhsh527 at 163.com > > -----Original Message----- > From: Zvonar, Bill > Sent: Wednesday, October 9, 2019 1:56 PM > To: 'starlingx-discuss at lists.starlingx.io' > Cc: Ildiko Vancsa ; 'Jones, Bruce E' > Subject: Voters for PL/TL election... > > As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. > > The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. > > If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). > > Bill... > > build > > - don.penney at windriver.com > - scott.little at windriver.com > - dtroyer at gmail.com > - al.bailey at windriver.com > - tyler.smith at windriver.com > - daniel.badea at windriver.com > - sgw at linux.intel.com > - erich.cordoba.malibran at intel.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - tao.liu at windriver.com > - joseph.richard at windriver.com > - felipe.de.jesus.ruiz.garcia at intel.com > - angie.wang at windriver.com > - Kristine.Bujold at windriver.com > - jesus.ornelas.aguayo at intel.com > - lihaijing at fiberhome.com > - jason.mckenna at windriver.com > - zhangyangyang at unionpay.com > - jerry.sun at windriver.com > - alex.kozyrev at windriver.com > - steven.webster at windriver.com > - jaegerandi at gmail.com > - longx.li at intel.com > - john.kung at windriver.com > - maria.yousaf at windriver.com > - zhipengs.liu at intel.com > - lihang0166 at fiberhome.com > - zhiguox.zhang at intel.com > - bin.yang at intel.com > - iwienand at redhat.com > - marcela.a.rosales.jimenez at intel.com > - tee.ngo at windriver.com > - haochuan.z.chen at intel.com > - caoran at fiberhome.com > - zhang.kunpeng at 99cloud.net > - Paul-Emile.Element at windriver.com > > config > > - angie.wang at windriver.com > - tingjie.chen at intel.com > - kevin.smith at windriver.com > - ovidiu.poncea at windriver.com > - bin.qian at windriver.com > - joseph.richard at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - andy.ning at windriver.com > - david.sullivan at windriver.com > - daniel.badea at windriver.com > - zhipengs.liu at intel.com > - tao.liu at windriver.com > - haochuan.z.chen at intel.com > - lihang0166 at fiberhome.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - sgw at linux.intel.com > - teresa.ho at windriver.com > - eric.macdonald at windriver.com > - alex.kozyrev at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - tee.ngo at windriver.com > - tyler.smith at windriver.com > - bin.yang at intel.com > - john.kung at windriver.com > - jaegerandi at gmail.com > - mingyuan.qi at intel.com > - eric.barrett at windriver.com > - zhang.kunpeng at 99cloud.net > - wei.zhou at windriver.com > - steven.webster at windriver.com > - jerry.sun at windriver.com > - dtroyer at gmail.com > - barton.wensley at windriver.com > - matt.peters at windriver.com > - zhu.boxiang at 99cloud.net > - don.penney at windriver.com > - James.Gauld at windriver.com > - junbo85.li at gmail.com > - chris.friesen at windriver.com > - marcela.a.rosales.jimenez at intel.com > - cheng1.li at intel.com > - chenjie.xu at intel.com > - allain.legacy at windriver.com > - yan.chen at intel.com > - elena.taivan at windriver.com > - yizhoux.xu at intel.com > - iwienand at redhat.com > - irina.mihai at windriver.com > - wzj334965317 at outlook.com > - ma.lei at 99cloud.net > - eric.zhang at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - daniel.chavolla at windriver.com > - lachlan.plant at windriver.com > - srifenbark at gmail.com > - shoaib.nasir at windriver.com > - singh.surya64mnnit at gmail.com > > containers > > - al.bailey at windriver.com > - kevin.smith at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > > distcloud > > - andy.ning at windriver.com > - tyler.smith at windriver.com > - scott.little at windriver.com > - xiefp88 at sina.com > - jaegerandi at gmail.com > - dtroyer at gmail.com > - tao.liu at windriver.com > - don.penney at windriver.com > - al.bailey at windriver.com > - Kristine.Bujold at windriver.com > - cao.yuan at 99cloud.net > - wzj334965317 at outlook.com > - alex.kozyrev at windriver.com > - lachlan.plant at windriver.com > - junbo85.li at gmail.com > - srifenbark at gmail.com > - barton.wensley at windriver.com > > distro > > - al.bailey at windriver.com > - alex.kozyrev at windriver.com > - jerry.sun at windriver.com > - erich.cordoba.malibran at intel.com > - daniel.badea at windriver.com > - Kristine.Bujold at windriver.com > - scott.little at windriver.com > - jaegerandi at gmail.com > - bin.qian at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > - eric.macdonald at windriver.com > - john.kung at windriver.com > - andy.ning at windriver.com > - dtroyer at gmail.com > - stefan.dinescu at windriver.com > - bin.yang at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - barton.wensley at windriver.com > - junbo85.li at gmail.com > - angie.wang at windriver.com > - teresa.ho at windriver.com > - sgw at linux.intel.com > - tao.liu at windriver.com > - zhiguox.zhang at intel.com > - steven.webster at windriver.com > - chenjie.xu at intel.com > - James.Gauld at windriver.com > - longx.li at intel.com > - tyler.smith at windriver.com > - chenlx at fiberhome.com > - corvus at inaugust.com > - chris.friesen at windriver.com > - haochuan.z.chen at intel.com > - daniel.chavolla at windriver.com > - wei.zhou at windriver.com > - ovidiu.poncea at windriver.com > - joseph.richard at windriver.com > - jason.mckenna at windriver.com > - louie.kwan at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - tee.ngo at windriver.com > - ma.lei at 99cloud.net > > docs > > - bruce.e.jones at intel.com > - jaegerandi at gmail.com > - chenlx at fiberhome.com > - lihang0166 at fiberhome.com > - srifenbark at gmail.com > - xiefp88 at sina.com > - liuyamin at fiberhome.com > - lipan7195 at fiberhome.com > - fungi at yuggoth.org > - curtis at serverascode.com > - iwienand at redhat.com > - erich.cordoba.malibran at intel.com > - li.xiaoli at 99cloud.net > - zhang.kunpeng at 99cloud.net > - dtroyer at gmail.com > > flock-services > > - tyler.smith at windriver.com > - david.sullivan at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - jaegerandi at gmail.com > - haochuan.z.chen at intel.com > - dtroyer at gmail.com > - teresa.ho at windriver.com > - junbo85.li at gmail.com > - ovidiu.poncea at windriver.com > - yan.chen at intel.com > - sgw at linux.intel.com > - steven.webster at windriver.com > - zhipengs.liu at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - john.kung at windriver.com > - wzj334965317 at outlook.com > - tao.liu at windriver.com > - stefan.dinescu at windriver.com > - wei.zhou at windriver.com > - James.Gauld at windriver.com > - angie.wang at windriver.com > - guozhen.she at intel.com > - bin.qian at windriver.com > - zqhsh527 at 163.com > - andy.ning at windriver.com > - mingyuan.qi at intel.com > - xiefp88 at sina.com > - daniel.badea at windriver.com > - chris.friesen at windriver.com > - elena.taivan at windriver.com > - jerry.sun at windriver.com > - marcela.a.rosales.jimenez at intel.com > - xbyan at fiberhome.com > - ran1.an at intel.com > - alex.kozyrev at windriver.com > - eric.macdonald at windriver.com > - matt.peters at windriver.com > - barton.wensley at windriver.com > - kevin.smith at windriver.com > - zhanglf01 at inspur.com > - lachlan.plant at windriver.com > - zhaowei7146 at fiberhome.com > - lvcy at fiberhome.com > - sxmatch1986 at gmail.com > - ma.lei at 99cloud.net > - lijunjie at cloudin.cn > - jason.mckenna at windriver.com > - srifenbark at gmail.com > - tee.ngo at windriver.com > - zhangzhaoshan at inspur.com > - zhaolong at inspur.com > - lihang0166 at fiberhome.com > > multios > > > > networking > > > > networking > > > > openstack_distro > > > > release > > > > security > > > > test > > - lihang0166 at fiberhome.com > - dtroyer at gmail.com > - erich.cordoba.malibran at intel.com > - yang.liu at windriver.com > - al.bailey at windriver.com > - juan.p.gomez at intel.com > - anujeyan.manokeran at windriver.com > - maria.yousaf at windriver.com > - peng.peng at windriver.com > - marvin.huang at windriver.com > > [0] https://etherpad.openstack.org/p/stx-status > > _______________________________________________ > 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 ildiko at openstack.org Thu Oct 17 18:21:31 2019 From: ildiko at openstack.org (Ildiko Vancsa) Date: Thu, 17 Oct 2019 20:21:31 +0200 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: <8F979CFE-FC4A-41D6-8F29-53878B1BE83B@openstack.org> References: <586E8B730EA0DA4A9D6A80A10E486BC007B05280@ALA-MBD.corp.ad.wrs.com> <586E8B730EA0DA4A9D6A80A10E486BC007B0575F@ALA-MBD.corp.ad.wrs.com> <8F979CFE-FC4A-41D6-8F29-53878B1BE83B@openstack.org> Message-ID: Hi, As it didn’t read clearly from the election website I sent it out in a separate email to clarify the requirements to participate in the elections part of which you need to have an active OSF Individual Member account. The former list of contributors who we were able to identify with the scripts only contained people with the active account. We have a few people registered since we last pulled the data, and we also have a few people suggested to be added, here is a summary of the current state for Flock Services electorate: People, by email, who were identified by the scripts as contributors AND have an active OSF Individual Membership —> eligible to vote: al.bailey at windriver.com alex.kozyrev at windriver.com andy.ning at windriver.com angie.wang at windriver.com austin.sun at intel.com barton.wensley at windriver.com bin.qian at windriver.com chris.friesen at windriver.com daniel.badea at windriver.com david.sullivan at windriver.com don.penney at windriver.com dtroyer at gmail.com elena.taivan at windriver.com eric.barrett at windriver.com eric.macdonald at windriver.com erich.cordoba.malibran at intel.com guozhen.she at intel.com haochuan.z.chen at intel.com jaegerandi at gmail.com james.gauld at windriver.com jason.mckenna at windriver.com jerry.sun at windriver.com john.kung at windriver.com junbo85.li at gmail.com kevin.smith at windriver.com kristal.dale at intel.com kristine.bujold at windriver.com lachlan.plant at windriver.com lihang0166 at fiberhome.com lijunjie at cloudin.cn lvcy at fiberhome.com ma.lei at 99cloud.net marcela.a.rosales.jimenez at intel.com matt.peters at windriver.com mingyuan.qi at intel.com ovidiu.poncea at windriver.com ran1.an at intel.com scott.little at windriver.com sgw at linux.intel.com shuicheng.lin at intel.com srifenbark at gmail.com stefan.dinescu at windriver.com steven.webster at windriver.com sxmatch1986 at gmail.com tao.liu at windriver.com tee.ngo at windriver.com teresa.ho at windriver.com tyler.smith at windriver.com vm.rod25 at gmail.com wei.zhou at windriver.com wzj334965317 at outlook.com xbyan at fiberhome.com xiefp88 at sina.com yan.chen at intel.com yi.c.wang at intel.com yong.hu at intel.com zhanglf01 at inspur.com zhangzhaoshan at inspur.com zhaolong at inspur.com zhaowei7146 at fiberhome.com zhipengs.liu at intel.com zqhsh527 at 163.com People, by email, who were identified by the scripts as contributors AND DO NOT HAVE an active OSF Individual Membership with the below email —> currently not eligible to vote: 18552437190 at 163.com abraham.arce.moreno at intel.com dominig.arfoll at fridu.net erick.cardona.ruiz at intel.com hayde.martinez.landa at intel.com hsye at fiberhome.com jackding at gmail.com litao3721 at 126.com luis.botello.ortega at intel.com mario.alfredo.c.arevalo at intel.com zb11318 at 163.com zxgao at fiberhome.com People who were suggested to be added to the list of active project contributors (need to be verified, approved to be added to the projects.yaml file): Cindy.xie at intel.com People who were suggested but not qualify based on contribution data: Patrick.bonnell at windriver.com - last merged commit is October 4, 2018 which is out of the 12 months period: https://review.opendev.org/#/q/owner:patrick.bonnell%2540windriver.com+status:merged Robert.church at windriver.com - last merged commit in qualifying repo is October 4, 2018 which is out of the 12 months period: https://review.opendev.org/#/q/owner:robert.church%2540windriver.com+status:merged+project:starlingx/metal Joseph.richard at windriver.com - first merged commit in qualifying repo is October 16, 2019 which is after the elections have started: https://review.opendev.org/#/q/owner:joseph.richard%2540windriver.com+status:merged+project:starlingx/metal Contributions listed are in repositories that are not under Flock Services: Gerry.kopec at windriver.com - no OSF Individual Member entry found Allain.legacy at windriver.com On the TSC call we touched on the Clear Linux activity. The response was as it is not a community facing activity at the moment we cannot count that as contribution to the project and/or community participation: zhaos at neusoft.com lilong-neu at neusoft.com dongqix.chen at intel.com zhiguox.zhang at intel.com yongx.fu at intel.com hai.tao.wang at intel.com Hereby I would like to remind everyone to the ‘4 Opens’ which are the guiding principles of the OpenStack Foundation and OpenStack Foundation projects that provide guidance around the importance of keeping the whole deisgn and development process open and accessible to everyone: https://osf.dev/about/four-opens/ Thanks, Ildikó > On Oct 17, 2019, at 19:00, Ildiko Vancsa wrote: > > Hi Frank, > > Just a heads up that the ‘config’ repo is not under the Flock Services project. > > Thanks, > Ildikó > > >> On Oct 17, 2019, at 16:52, Miller, Frank wrote: >> >> See below inline with repos these folks have contributed to since Oct 2018 and the # of commits across those repos. >> >> Frank >> >> -----Original Message----- >> From: Zvonar, Bill >> Sent: Thursday, October 17, 2019 10:07 AM >> To: Miller, Frank ; starlingx-discuss at lists.starlingx.io >> Cc: Ildiko Vancsa ; Jones, Bruce E >> Subject: RE: Voters for PL/TL election... >> >> Can you specify which repos they made commits to? >> >> -----Original Message----- >> From: Miller, Frank >> Sent: Thursday, October 17, 2019 9:58 AM >> To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io >> Cc: Ildiko Vancsa ; Jones, Bruce E >> Subject: RE: Voters for PL/TL election... >> >> Bill: >> >> In looking through the list the following people who have commits in the past 12 months are missing from the list. I recommend these be added: >> >> Patrick.bonnell at windriver.com [config, gui, upstream] - 7 commits >> Robert.church at windriver.com [config, integ, metal, root, specs, tools, upstream] - 82 commits >> Gerry.kopec at windriver.com [config, integ, upstream] - 23 commits >> Allain.legacy at windriver.com [config] - 7 commits >> Joseph.richard at windriver.com [config, integ, metal, root, tools] - 17 commits >> >> >> Frank >> >> -----Original Message----- >> From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] >> Sent: Wednesday, October 16, 2019 2:40 PM >> To: starlingx-discuss at lists.starlingx.io >> Cc: Ildiko Vancsa ; Jones, Bruce E >> Subject: Re: [Starlingx-discuss] Voters for PL/TL election... >> >> As discussed on the Community Call today, there will be an election next week for the flock-services repo. >> >> Below is the (alphabetized) list of contributors who are currently eligible to vote on this position. >> >> Eligible voters will receive an invitation to vote this Sunday evening once the voting period begins. >> >> If you're not on this list but consider yourself to have contributed to this sub-project in the last 12 months and hence should be eligible to vote for this position, please say so here or directly to the election team (Ildiko, Bruce & myself). >> >> Bill... >> >> - al.bailey at windriver.com >> - alex.kozyrev at windriver.com >> - andy.ning at windriver.com >> - angie.wang at windriver.com >> - barton.wensley at windriver.com >> - bin.qian at windriver.com >> - chris.friesen at windriver.com >> - daniel.badea at windriver.com >> - david.sullivan at windriver.com >> - don.penney at windriver.com >> - dtroyer at gmail.com >> - elena.taivan at windriver.com >> - eric.barrett at windriver.com >> - eric.macdonald at windriver.com >> - erich.cordoba.malibran at intel.com >> - guozhen.she at intel.com >> - haochuan.z.chen at intel.com >> - jaegerandi at gmail.com >> - james.gauld at windriver.com >> - jason.mckenna at windriver.com >> - jerry.sun at windriver.com >> - john.kung at windriver.com >> - junbo85.li at gmail.com >> - kevin.smith at windriver.com >> - kristine.bujold at windriver.com >> - lachlan.plant at windriver.com >> - lihang0166 at fiberhome.com >> - lijunjie at cloudin.cn >> - lvcy at fiberhome.com >> - ma.lei at 99cloud.net >> - marcela.a.rosales.jimenez at intel.com >> - matt.peters at windriver.com >> - mingyuan.qi at intel.com >> - ovidiu.poncea at windriver.com >> - ran1.an at intel.com >> - scott.little at windriver.com >> - sgw at linux.intel.com >> - srifenbark at gmail.com >> - stefan.dinescu at windriver.com >> - steven.webster at windriver.com >> - sxmatch1986 at gmail.com >> - tao.liu at windriver.com >> - tee.ngo at windriver.com >> - teresa.ho at windriver.com >> - tyler.smith at windriver.com >> - wei.zhou at windriver.com >> - wzj334965317 at outlook.com >> - xbyan at fiberhome.com >> - xiefp88 at sina.com >> - yan.chen at intel.com >> - zhanglf01 at inspur.com >> - zhangzhaoshan at inspur.com >> - zhaolong at inspur.com >> - zhaowei7146 at fiberhome.com >> - zhipengs.liu at intel.com >> - zqhsh527 at 163.com >> >> -----Original Message----- >> From: Zvonar, Bill >> Sent: Wednesday, October 9, 2019 1:56 PM >> To: 'starlingx-discuss at lists.starlingx.io' >> Cc: Ildiko Vancsa ; 'Jones, Bruce E' >> Subject: Voters for PL/TL election... >> >> As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. >> >> The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. >> >> If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). >> >> Bill... >> >> build >> >> - don.penney at windriver.com >> - scott.little at windriver.com >> - dtroyer at gmail.com >> - al.bailey at windriver.com >> - tyler.smith at windriver.com >> - daniel.badea at windriver.com >> - sgw at linux.intel.com >> - erich.cordoba.malibran at intel.com >> - stefan.dinescu at windriver.com >> - ran1.an at intel.com >> - tao.liu at windriver.com >> - joseph.richard at windriver.com >> - felipe.de.jesus.ruiz.garcia at intel.com >> - angie.wang at windriver.com >> - Kristine.Bujold at windriver.com >> - jesus.ornelas.aguayo at intel.com >> - lihaijing at fiberhome.com >> - jason.mckenna at windriver.com >> - zhangyangyang at unionpay.com >> - jerry.sun at windriver.com >> - alex.kozyrev at windriver.com >> - steven.webster at windriver.com >> - jaegerandi at gmail.com >> - longx.li at intel.com >> - john.kung at windriver.com >> - maria.yousaf at windriver.com >> - zhipengs.liu at intel.com >> - lihang0166 at fiberhome.com >> - zhiguox.zhang at intel.com >> - bin.yang at intel.com >> - iwienand at redhat.com >> - marcela.a.rosales.jimenez at intel.com >> - tee.ngo at windriver.com >> - haochuan.z.chen at intel.com >> - caoran at fiberhome.com >> - zhang.kunpeng at 99cloud.net >> - Paul-Emile.Element at windriver.com >> >> config >> >> - angie.wang at windriver.com >> - tingjie.chen at intel.com >> - kevin.smith at windriver.com >> - ovidiu.poncea at windriver.com >> - bin.qian at windriver.com >> - joseph.richard at windriver.com >> - Kristine.Bujold at windriver.com >> - al.bailey at windriver.com >> - andy.ning at windriver.com >> - david.sullivan at windriver.com >> - daniel.badea at windriver.com >> - zhipengs.liu at intel.com >> - tao.liu at windriver.com >> - haochuan.z.chen at intel.com >> - lihang0166 at fiberhome.com >> - stefan.dinescu at windriver.com >> - ran1.an at intel.com >> - sgw at linux.intel.com >> - teresa.ho at windriver.com >> - eric.macdonald at windriver.com >> - alex.kozyrev at windriver.com >> - erich.cordoba.malibran at intel.com >> - scott.little at windriver.com >> - tee.ngo at windriver.com >> - tyler.smith at windriver.com >> - bin.yang at intel.com >> - john.kung at windriver.com >> - jaegerandi at gmail.com >> - mingyuan.qi at intel.com >> - eric.barrett at windriver.com >> - zhang.kunpeng at 99cloud.net >> - wei.zhou at windriver.com >> - steven.webster at windriver.com >> - jerry.sun at windriver.com >> - dtroyer at gmail.com >> - barton.wensley at windriver.com >> - matt.peters at windriver.com >> - zhu.boxiang at 99cloud.net >> - don.penney at windriver.com >> - James.Gauld at windriver.com >> - junbo85.li at gmail.com >> - chris.friesen at windriver.com >> - marcela.a.rosales.jimenez at intel.com >> - cheng1.li at intel.com >> - chenjie.xu at intel.com >> - allain.legacy at windriver.com >> - yan.chen at intel.com >> - elena.taivan at windriver.com >> - yizhoux.xu at intel.com >> - iwienand at redhat.com >> - irina.mihai at windriver.com >> - wzj334965317 at outlook.com >> - ma.lei at 99cloud.net >> - eric.zhang at windriver.com >> - Paul-Emile.Element at windriver.com >> - zhangyangyang at unionpay.com >> - daniel.chavolla at windriver.com >> - lachlan.plant at windriver.com >> - srifenbark at gmail.com >> - shoaib.nasir at windriver.com >> - singh.surya64mnnit at gmail.com >> >> containers >> >> - al.bailey at windriver.com >> - kevin.smith at windriver.com >> - zhipengs.liu at intel.com >> - ran1.an at intel.com >> >> distcloud >> >> - andy.ning at windriver.com >> - tyler.smith at windriver.com >> - scott.little at windriver.com >> - xiefp88 at sina.com >> - jaegerandi at gmail.com >> - dtroyer at gmail.com >> - tao.liu at windriver.com >> - don.penney at windriver.com >> - al.bailey at windriver.com >> - Kristine.Bujold at windriver.com >> - cao.yuan at 99cloud.net >> - wzj334965317 at outlook.com >> - alex.kozyrev at windriver.com >> - lachlan.plant at windriver.com >> - junbo85.li at gmail.com >> - srifenbark at gmail.com >> - barton.wensley at windriver.com >> >> distro >> >> - al.bailey at windriver.com >> - alex.kozyrev at windriver.com >> - jerry.sun at windriver.com >> - erich.cordoba.malibran at intel.com >> - daniel.badea at windriver.com >> - Kristine.Bujold at windriver.com >> - scott.little at windriver.com >> - jaegerandi at gmail.com >> - bin.qian at windriver.com >> - zhipengs.liu at intel.com >> - ran1.an at intel.com >> - eric.macdonald at windriver.com >> - john.kung at windriver.com >> - andy.ning at windriver.com >> - dtroyer at gmail.com >> - stefan.dinescu at windriver.com >> - bin.yang at intel.com >> - don.penney at windriver.com >> - eric.barrett at windriver.com >> - barton.wensley at windriver.com >> - junbo85.li at gmail.com >> - angie.wang at windriver.com >> - teresa.ho at windriver.com >> - sgw at linux.intel.com >> - tao.liu at windriver.com >> - zhiguox.zhang at intel.com >> - steven.webster at windriver.com >> - chenjie.xu at intel.com >> - James.Gauld at windriver.com >> - longx.li at intel.com >> - tyler.smith at windriver.com >> - chenlx at fiberhome.com >> - corvus at inaugust.com >> - chris.friesen at windriver.com >> - haochuan.z.chen at intel.com >> - daniel.chavolla at windriver.com >> - wei.zhou at windriver.com >> - ovidiu.poncea at windriver.com >> - joseph.richard at windriver.com >> - jason.mckenna at windriver.com >> - louie.kwan at windriver.com >> - Paul-Emile.Element at windriver.com >> - zhangyangyang at unionpay.com >> - tee.ngo at windriver.com >> - ma.lei at 99cloud.net >> >> docs >> >> - bruce.e.jones at intel.com >> - jaegerandi at gmail.com >> - chenlx at fiberhome.com >> - lihang0166 at fiberhome.com >> - srifenbark at gmail.com >> - xiefp88 at sina.com >> - liuyamin at fiberhome.com >> - lipan7195 at fiberhome.com >> - fungi at yuggoth.org >> - curtis at serverascode.com >> - iwienand at redhat.com >> - erich.cordoba.malibran at intel.com >> - li.xiaoli at 99cloud.net >> - zhang.kunpeng at 99cloud.net >> - dtroyer at gmail.com >> >> flock-services >> >> - tyler.smith at windriver.com >> - david.sullivan at windriver.com >> - Kristine.Bujold at windriver.com >> - al.bailey at windriver.com >> - jaegerandi at gmail.com >> - haochuan.z.chen at intel.com >> - dtroyer at gmail.com >> - teresa.ho at windriver.com >> - junbo85.li at gmail.com >> - ovidiu.poncea at windriver.com >> - yan.chen at intel.com >> - sgw at linux.intel.com >> - steven.webster at windriver.com >> - zhipengs.liu at intel.com >> - don.penney at windriver.com >> - eric.barrett at windriver.com >> - erich.cordoba.malibran at intel.com >> - scott.little at windriver.com >> - john.kung at windriver.com >> - wzj334965317 at outlook.com >> - tao.liu at windriver.com >> - stefan.dinescu at windriver.com >> - wei.zhou at windriver.com >> - James.Gauld at windriver.com >> - angie.wang at windriver.com >> - guozhen.she at intel.com >> - bin.qian at windriver.com >> - zqhsh527 at 163.com >> - andy.ning at windriver.com >> - mingyuan.qi at intel.com >> - xiefp88 at sina.com >> - daniel.badea at windriver.com >> - chris.friesen at windriver.com >> - elena.taivan at windriver.com >> - jerry.sun at windriver.com >> - marcela.a.rosales.jimenez at intel.com >> - xbyan at fiberhome.com >> - ran1.an at intel.com >> - alex.kozyrev at windriver.com >> - eric.macdonald at windriver.com >> - matt.peters at windriver.com >> - barton.wensley at windriver.com >> - kevin.smith at windriver.com >> - zhanglf01 at inspur.com >> - lachlan.plant at windriver.com >> - zhaowei7146 at fiberhome.com >> - lvcy at fiberhome.com >> - sxmatch1986 at gmail.com >> - ma.lei at 99cloud.net >> - lijunjie at cloudin.cn >> - jason.mckenna at windriver.com >> - srifenbark at gmail.com >> - tee.ngo at windriver.com >> - zhangzhaoshan at inspur.com >> - zhaolong at inspur.com >> - lihang0166 at fiberhome.com >> >> multios >> >> >> >> networking >> >> >> >> networking >> >> >> >> openstack_distro >> >> >> >> release >> >> >> >> security >> >> >> >> test >> >> - lihang0166 at fiberhome.com >> - dtroyer at gmail.com >> - erich.cordoba.malibran at intel.com >> - yang.liu at windriver.com >> - al.bailey at windriver.com >> - juan.p.gomez at intel.com >> - anujeyan.manokeran at windriver.com >> - maria.yousaf at windriver.com >> - peng.peng at windriver.com >> - marvin.huang at windriver.com >> >> [0] https://etherpad.openstack.org/p/stx-status >> >> _______________________________________________ >> 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 bruce.e.jones at intel.com Thu Oct 17 18:51:49 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 17 Oct 2019 18:51:49 +0000 Subject: [Starlingx-discuss] Train upgrade for openstack clients In-Reply-To: References: <72AD03D27224C74982BE13246D75B39739A64833@SHSMSX103.ccr.corp.intel.com> <72AD03D27224C74982BE13246D75B39739A651A3@SHSMSX103.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BDFBF84E0@fmsmsx123.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BDFBF93CF@fmsmsx123.amr.corp.intel.com> We discussed this topic at the Release meeting today. The conclusion was that we do not want to upgrade puppet or ruby for this release. It's too risky. As one of the last features gating our 3.0 release there is some urgency in figuring out the right approach to this upgrade. Where we need help is figuring out if it is possible to divide the OpenStack world into two parts and treat each part separately. Most of the OpenStack services running in StarlingX are in containers and should not depend on puppet at all. The 3 services that are not in containers (keystone, barbican and horizon) do depend on puppet. Is it possible / practical to run the Train versions of the containerized services, while still running the Stein versions of keystone, barbican and horizon in the platform layer? Or is there another creative solution to the problem? brucej From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] Sent: Thursday, October 17, 2019 7:47 AM To: Jones, Bruce E ; Chen, Yan ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Train upgrade for openstack clients I think the puppet 5 upgrade ends up being one of the more complicated parts of this activity. It looks like for 5.0.x you need to be cautious about is all the deprecated features in 4 that were removed in 5. It would not surprise me if we were still using some of those deprecated parts. https://github.com/puppetlabs/docs-archive/blob/master/puppet/5.0/release_notes.markdown Puppet 5 also uses a newer ruby. We ship ruby 2.0 now. The notes for 5.0 indicate ruby 2.4, which is extra work and can take a while if existing ruby code needs to be changed. Puppet 5 also claims to have hiera 5 built in. I don't know what that means, we ship hiera 1.3.4 separarately, so there may be packaging concerns there as well. Last time when I upversioned puppet from puppet 3 to 4 the most unexpected thing was not the code changes required, but the runtime behavior was different. Example: https://opendev.org/starlingx/integ/src/branch/master/config/puppet-4.8.2/centos/patches/1005-Set-strict_variables-and-basemodulepath-in-puppet.co.patch Experiment with installing train keystone/barbican/horizon with the existing puppet modules. If a config value is incompatible, then it may require a local change, or an upversion. Al From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, October 17, 2019 9:43 AM To: Chen, Yan; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Train upgrade for openstack clients Yan, thank you for making this very clear. As I read this, the puppet modules we use for the openstack clients are several releases old and the update to the Train version would be painful, er I mean lots of fun. I think we need some input from the broader community. What are the costs / risks of upgrading to puppet 5.0? Should we try to upgrade the client puppet modules ourselves (and contribute the changes upstream)? Or is there a better long way we should launch these clients, e.g. should we just write Ansible installers for them? My thanks to Dean for helping me understand what questions to ask :) brucej From: Chen, Yan [mailto:yan.chen at intel.com] Sent: Tuesday, October 15, 2019 10:43 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Train upgrade for openstack clients Hi, I'm now trying to upgrade the openstack clients installed on StarlingX to Train version. Currently I see the clients are Stein version, but the puppet packages (for those modules that we need to config on StarlingX host) are still old versions. [See the list below.] But for Train, I met a problem when I wanted to upgrade python-openstackclient/keystone to Train (4.0.0), the old puppet packages cannot work with Train clients and failed when running puppet-manifest-apply.sh. See from Stein keystone log, some of the deprecated cmds and options are planned to be removed in Train. If we want to make Train clients work, we may need to do the following steps: 1. Upgrade puppet itself (required 5.x by Train) 2. Upgrade all the OpenStack related puppet packages accordingly, and update StarlingX patches. 3. If flock puppet pkgs are based on puppet 4.8.2, we also need to upgrade our code. 4. If other puppet pkgs are based on puppet 4.8.2, we also need to upgrade those pkgs. So is it possible that we keep on using Stein clients with limited test now (need test with Train images, but suppose old functions should still work)? Here's the list of the puppet packages and StarlingX patches (for Stein it should be 14.1.0 - 14.4.0, and for Train 15.0.0 - 15.4.0): Pkg Current Version Train Upgrade to Meta Patch Patch puppet 4.8.2 5.x 2 5 puppet-keystone 11.3.0 15.x 6 5 puppet-oslo 11.3.0 15.x 3 2 puppet-openstacklib 11.5.0 15.x 2 1 puppet-horizon 11.5.0 15.x 2 1 puppet-barbican 11.3.0 15.x 0 0 Stein Keystone client logs: keystone:log 2019-10-10 10:04:44.050 111346 WARNING keystone.server.flask.request_processing.middleware.auth_context [-] The use of the '[DEFAULT] admin_token' configurationoption presents a significant security risk and should not be set. This option is deprecated in favor of using 'keystone-manage bootstrap' and will be removed in a future release. Yan -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Thu Oct 17 12:10:26 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Thu, 17 Oct 2019 12:10:26 +0000 Subject: [Starlingx-discuss] Voters for PL/TL election... In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F36089A8D@SHSMSX104.ccr.corp.intel.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B05280@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F3608979C@SHSMSX104.ccr.corp.intel.com>, <586E8B730EA0DA4A9D6A80A10E486BC007B0547E@ALA-MBD.corp.ad.wrs.com> <586E8B730EA0DA4A9D6A80A10E486BC007B054B8@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F36089A8D@SHSMSX104.ccr.corp.intel.com> Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B05688@ALA-MBD.corp.ad.wrs.com> Thanks Cindy. My understanding from the discussions last week is that the Gerrit data may be off due to repo moves/consolidations, etc. For the flock-services sub-project, the repos are these... - clients - fault - gui - ha - metal - monitoring - nfv - update So the folks that contributed to those repos in the last 12 months are eligible to vote, and we'll add their emails to the extra-atcs secion for the flock-services repo. For the others, we'll discuss it on the TSC call today. Thanks, Bill... From: Xie, Cindy Sent: Wednesday, October 16, 2019 8:37 PM To: Zvonar, Bill Cc: Ildiko Vancsa ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: Voters for PL/TL election... Bill, Here is my statistic of the patches in 2019 for the below folks: Status Merged Count of Subject Column Labels Row Labels starlingx/config starlingx/nfv starlingx/metal starlingx/fault starlingx/gui starlingx/distcloud starlingx/ha starlingx/config-files openstack/horizon Grand Total Austin Sun 14 1 5 1 3 1 25 Yi Wang 7 6 5 18 zhipeng liu 11 1 4 1 1 18 Lin Shuicheng 7 2 4 1 1 15 Ran An 6 8 1 15 Mingyuan Qi 12 1 13 chen haochuan 6 2 2 1 11 Yan Chen 2 7 1 10 yong hu 2 2 Grand Total 67 17 12 11 11 3 3 2 1 127 I am not sure why your gerrit data didn't show the results. For the below folks, they didn't have patches in flocks repo, but they were working on porting flocks components to Clear Linux, they've worked on spec file and generating flocks service packages. The work is not on master yet. Not sure if this counts. > zhaos at neusoft.com > lilong-neu at neusoft.com > dongqix.chen at intel.com > zhiguox.zhang at intel.com > yongx.fu at intel.com > hai.tao.wang at intel.com Thx. - cindy -----Original Message----- From: Zvonar, Bill > Sent: Thursday, October 17, 2019 7:45 AM To: Xie, Cindy > Cc: Ildiko Vancsa >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: RE: Voters for PL/TL election... Hi Cindy - the original list was from Gerrit data. I assume that these candidates did in fact commit to flock-services repos, but the onus is on those who nominate folks who aren't on that list to provide the justification. So, please do provide that info for these folks. Thanks, Bill... -----Original Message----- From: Xie, Cindy > Sent: Wednesday, October 16, 2019 7:30 PM To: Zvonar, Bill > Cc: Ildiko Vancsa >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: Re: Voters for PL/TL election... I am not sure how you get your list below, but by pulling their patches from StarlingX repo, you can find names for most of people. Anybody you cannot find patch, let me know, I can send you the justification. Sent from my iPhone > On Oct 17, 2019, at 07:24, Zvonar, Bill > wrote: > > Thanks Cindy - I believe for each candidate elector, we need some justification. > > Ildiko/Bruce - is it a one-liner per person? > > -----Original Message----- > From: Xie, Cindy > > Sent: Wednesday, October 16, 2019 6:42 PM > To: Zvonar, Bill >; starlingx-discuss at lists.starlingx.io > Cc: Ildiko Vancsa >; Jones, Bruce E > > Subject: RE: Voters for PL/TL election... > > Bill, > I request below folks to be added: > Cindy.xie at intel.com > Yong.hu at intel.com > Yi.c.wang at intel.com > shuicheng.lin at intel.com > hai.tao.wang at intel.com > Austin.sun at intel.com > zhaos at neusoft.com > lilong-neu at neusoft.com > dongqix.chen at intel.com > zhiguox.zhang at intel.com > yongx.fu at intel.com > > Cindy Xie > IAGS > > > -----Original Message----- > From: Zvonar, Bill > > Sent: Thursday, October 17, 2019 2:40 AM > To: starlingx-discuss at lists.starlingx.io > Cc: Ildiko Vancsa >; Jones, Bruce E > > Subject: Re: [Starlingx-discuss] Voters for PL/TL election... > > As discussed on the Community Call today, there will be an election next week for the flock-services repo. > > Below is the (alphabetized) list of contributors who are currently eligible to vote on this position. > > Eligible voters will receive an invitation to vote this Sunday evening once the voting period begins. > > If you're not on this list but consider yourself to have contributed to this sub-project in the last 12 months and hence should be eligible to vote for this position, please say so here or directly to the election team (Ildiko, Bruce & myself). > > Bill... > > - al.bailey at windriver.com > - alex.kozyrev at windriver.com > - andy.ning at windriver.com > - angie.wang at windriver.com > - barton.wensley at windriver.com > - bin.qian at windriver.com > - chris.friesen at windriver.com > - daniel.badea at windriver.com > - david.sullivan at windriver.com > - don.penney at windriver.com > - dtroyer at gmail.com > - elena.taivan at windriver.com > - eric.barrett at windriver.com > - eric.macdonald at windriver.com > - erich.cordoba.malibran at intel.com > - guozhen.she at intel.com > - haochuan.z.chen at intel.com > - jaegerandi at gmail.com > - james.gauld at windriver.com > - jason.mckenna at windriver.com > - jerry.sun at windriver.com > - john.kung at windriver.com > - junbo85.li at gmail.com > - kevin.smith at windriver.com > - kristine.bujold at windriver.com > - lachlan.plant at windriver.com > - lihang0166 at fiberhome.com > - lijunjie at cloudin.cn > - lvcy at fiberhome.com > - ma.lei at 99cloud.net > - marcela.a.rosales.jimenez at intel.com > - matt.peters at windriver.com > - mingyuan.qi at intel.com > - ovidiu.poncea at windriver.com > - ran1.an at intel.com > - scott.little at windriver.com > - sgw at linux.intel.com > - srifenbark at gmail.com > - stefan.dinescu at windriver.com > - steven.webster at windriver.com > - sxmatch1986 at gmail.com > - tao.liu at windriver.com > - tee.ngo at windriver.com > - teresa.ho at windriver.com > - tyler.smith at windriver.com > - wei.zhou at windriver.com > - wzj334965317 at outlook.com > - xbyan at fiberhome.com > - xiefp88 at sina.com > - yan.chen at intel.com > - zhanglf01 at inspur.com > - zhangzhaoshan at inspur.com > - zhaolong at inspur.com > - zhaowei7146 at fiberhome.com > - zhipengs.liu at intel.com > - zqhsh527 at 163.com > > -----Original Message----- > From: Zvonar, Bill > Sent: Wednesday, October 9, 2019 1:56 PM > To: 'starlingx-discuss at lists.starlingx.io' > > Cc: Ildiko Vancsa >; 'Jones, Bruce E' > > Subject: Voters for PL/TL election... > > As discussed on the Community Call today [0], this is a call to sub-project PLs to nominate valid voters for their sub-project in the upcoming PL/TL election. > > The lists below show who has contributed commits to each sub-project's repo(s) in the last 12 months - these individuals are considered valid voters for those sub-projects. > > If you would like to nominate others as valid voters for a given sub-project, please add them to the 'extra-atcs' section of the projects.yaml file or ask here for the election officials to do it (me, Bruce, Ildiko). > > Bill... > > build > > - don.penney at windriver.com > - scott.little at windriver.com > - dtroyer at gmail.com > - al.bailey at windriver.com > - tyler.smith at windriver.com > - daniel.badea at windriver.com > - sgw at linux.intel.com > - erich.cordoba.malibran at intel.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - tao.liu at windriver.com > - joseph.richard at windriver.com > - felipe.de.jesus.ruiz.garcia at intel.com > - angie.wang at windriver.com > - Kristine.Bujold at windriver.com > - jesus.ornelas.aguayo at intel.com > - lihaijing at fiberhome.com > - jason.mckenna at windriver.com > - zhangyangyang at unionpay.com > - jerry.sun at windriver.com > - alex.kozyrev at windriver.com > - steven.webster at windriver.com > - jaegerandi at gmail.com > - longx.li at intel.com > - john.kung at windriver.com > - maria.yousaf at windriver.com > - zhipengs.liu at intel.com > - lihang0166 at fiberhome.com > - zhiguox.zhang at intel.com > - bin.yang at intel.com > - iwienand at redhat.com > - marcela.a.rosales.jimenez at intel.com > - tee.ngo at windriver.com > - haochuan.z.chen at intel.com > - caoran at fiberhome.com > - zhang.kunpeng at 99cloud.net > - Paul-Emile.Element at windriver.com > > config > > - angie.wang at windriver.com > - tingjie.chen at intel.com > - kevin.smith at windriver.com > - ovidiu.poncea at windriver.com > - bin.qian at windriver.com > - joseph.richard at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - andy.ning at windriver.com > - david.sullivan at windriver.com > - daniel.badea at windriver.com > - zhipengs.liu at intel.com > - tao.liu at windriver.com > - haochuan.z.chen at intel.com > - lihang0166 at fiberhome.com > - stefan.dinescu at windriver.com > - ran1.an at intel.com > - sgw at linux.intel.com > - teresa.ho at windriver.com > - eric.macdonald at windriver.com > - alex.kozyrev at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - tee.ngo at windriver.com > - tyler.smith at windriver.com > - bin.yang at intel.com > - john.kung at windriver.com > - jaegerandi at gmail.com > - mingyuan.qi at intel.com > - eric.barrett at windriver.com > - zhang.kunpeng at 99cloud.net > - wei.zhou at windriver.com > - steven.webster at windriver.com > - jerry.sun at windriver.com > - dtroyer at gmail.com > - barton.wensley at windriver.com > - matt.peters at windriver.com > - zhu.boxiang at 99cloud.net > - don.penney at windriver.com > - James.Gauld at windriver.com > - junbo85.li at gmail.com > - chris.friesen at windriver.com > - marcela.a.rosales.jimenez at intel.com > - cheng1.li at intel.com > - chenjie.xu at intel.com > - allain.legacy at windriver.com > - yan.chen at intel.com > - elena.taivan at windriver.com > - yizhoux.xu at intel.com > - iwienand at redhat.com > - irina.mihai at windriver.com > - wzj334965317 at outlook.com > - ma.lei at 99cloud.net > - eric.zhang at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - daniel.chavolla at windriver.com > - lachlan.plant at windriver.com > - srifenbark at gmail.com > - shoaib.nasir at windriver.com > - singh.surya64mnnit at gmail.com > > containers > > - al.bailey at windriver.com > - kevin.smith at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > > distcloud > > - andy.ning at windriver.com > - tyler.smith at windriver.com > - scott.little at windriver.com > - xiefp88 at sina.com > - jaegerandi at gmail.com > - dtroyer at gmail.com > - tao.liu at windriver.com > - don.penney at windriver.com > - al.bailey at windriver.com > - Kristine.Bujold at windriver.com > - cao.yuan at 99cloud.net > - wzj334965317 at outlook.com > - alex.kozyrev at windriver.com > - lachlan.plant at windriver.com > - junbo85.li at gmail.com > - srifenbark at gmail.com > - barton.wensley at windriver.com > > distro > > - al.bailey at windriver.com > - alex.kozyrev at windriver.com > - jerry.sun at windriver.com > - erich.cordoba.malibran at intel.com > - daniel.badea at windriver.com > - Kristine.Bujold at windriver.com > - scott.little at windriver.com > - jaegerandi at gmail.com > - bin.qian at windriver.com > - zhipengs.liu at intel.com > - ran1.an at intel.com > - eric.macdonald at windriver.com > - john.kung at windriver.com > - andy.ning at windriver.com > - dtroyer at gmail.com > - stefan.dinescu at windriver.com > - bin.yang at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - barton.wensley at windriver.com > - junbo85.li at gmail.com > - angie.wang at windriver.com > - teresa.ho at windriver.com > - sgw at linux.intel.com > - tao.liu at windriver.com > - zhiguox.zhang at intel.com > - steven.webster at windriver.com > - chenjie.xu at intel.com > - James.Gauld at windriver.com > - longx.li at intel.com > - tyler.smith at windriver.com > - chenlx at fiberhome.com > - corvus at inaugust.com > - chris.friesen at windriver.com > - haochuan.z.chen at intel.com > - daniel.chavolla at windriver.com > - wei.zhou at windriver.com > - ovidiu.poncea at windriver.com > - joseph.richard at windriver.com > - jason.mckenna at windriver.com > - louie.kwan at windriver.com > - Paul-Emile.Element at windriver.com > - zhangyangyang at unionpay.com > - tee.ngo at windriver.com > - ma.lei at 99cloud.net > > docs > > - bruce.e.jones at intel.com > - jaegerandi at gmail.com > - chenlx at fiberhome.com > - lihang0166 at fiberhome.com > - srifenbark at gmail.com > - xiefp88 at sina.com > - liuyamin at fiberhome.com > - lipan7195 at fiberhome.com > - fungi at yuggoth.org > - curtis at serverascode.com > - iwienand at redhat.com > - erich.cordoba.malibran at intel.com > - li.xiaoli at 99cloud.net > - zhang.kunpeng at 99cloud.net > - dtroyer at gmail.com > > flock-services > > - tyler.smith at windriver.com > - david.sullivan at windriver.com > - Kristine.Bujold at windriver.com > - al.bailey at windriver.com > - jaegerandi at gmail.com > - haochuan.z.chen at intel.com > - dtroyer at gmail.com > - teresa.ho at windriver.com > - junbo85.li at gmail.com > - ovidiu.poncea at windriver.com > - yan.chen at intel.com > - sgw at linux.intel.com > - steven.webster at windriver.com > - zhipengs.liu at intel.com > - don.penney at windriver.com > - eric.barrett at windriver.com > - erich.cordoba.malibran at intel.com > - scott.little at windriver.com > - john.kung at windriver.com > - wzj334965317 at outlook.com > - tao.liu at windriver.com > - stefan.dinescu at windriver.com > - wei.zhou at windriver.com > - James.Gauld at windriver.com > - angie.wang at windriver.com > - guozhen.she at intel.com > - bin.qian at windriver.com > - zqhsh527 at 163.com > - andy.ning at windriver.com > - mingyuan.qi at intel.com > - xiefp88 at sina.com > - daniel.badea at windriver.com > - chris.friesen at windriver.com > - elena.taivan at windriver.com > - jerry.sun at windriver.com > - marcela.a.rosales.jimenez at intel.com > - xbyan at fiberhome.com > - ran1.an at intel.com > - alex.kozyrev at windriver.com > - eric.macdonald at windriver.com > - matt.peters at windriver.com > - barton.wensley at windriver.com > - kevin.smith at windriver.com > - zhanglf01 at inspur.com > - lachlan.plant at windriver.com > - zhaowei7146 at fiberhome.com > - lvcy at fiberhome.com > - sxmatch1986 at gmail.com > - ma.lei at 99cloud.net > - lijunjie at cloudin.cn > - jason.mckenna at windriver.com > - srifenbark at gmail.com > - tee.ngo at windriver.com > - zhangzhaoshan at inspur.com > - zhaolong at inspur.com > - lihang0166 at fiberhome.com > > multios > > > > networking > > > > networking > > > > openstack_distro > > > > release > > > > security > > > > test > > - lihang0166 at fiberhome.com > - dtroyer at gmail.com > - erich.cordoba.malibran at intel.com > - yang.liu at windriver.com > - al.bailey at windriver.com > - juan.p.gomez at intel.com > - anujeyan.manokeran at windriver.com > - maria.yousaf at windriver.com > - peng.peng at windriver.com > - marvin.huang at windriver.com > > [0] https://etherpad.openstack.org/p/stx-status > > _______________________________________________ > 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 Thu Oct 17 21:30:23 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 17 Oct 2019 21:30:23 +0000 Subject: [Starlingx-discuss] Cross checking projects and repos Message-ID: <9A85D2917C58154C960D95352B22818BDFBF9538@fmsmsx123.amr.corp.intel.com> TL;DR We have repos that are not listed in the projects.yaml file used for generating eligible voters. We have projects with a one-to-many relationship to repos, some of which are not part of StarlingX, which makes running scripts to find eligible voters a problem. We should fix both issues. As the (soon to be former) PL of the Openstack-distro project, and as one of the election officials, I've been busy the last few weeks trying to get my arms around figuring out who the eligible voters are for the project. Sadly, it's not as easy as it could be. The Openstack-distro project doesn't own any repos, instead the team contributes to repos owned by other projects. I thought I'd take a look at the similar projects see what the mapping of repos to projects looks like overall. I mapped our repos to projects using the projects.yaml file in the governance repo. The following starlingX repos are _not_ listed in projects.yaml by any sub-project: * Election - Cores are the Election officials, likely OK * Governance - Cores are the TSC, likely OK * Gplv2 - Not listed * Gplv3 - Not listed * Specs - Cores are the TSC, likely OK * Tis-repo - Not listed * Upstream - Not listed * Utils - Not listed Question: Are the repos shown as "Not listed" above still used? Should we add them to the projects.yaml file? If so, where? I then thought I'd take a look at the 3 projects that do not own any repos. I went through the project's Etherpads and looked at the reviews shown in them, to see where the code contributed by the team landed. Here is what I found: * Multi-OS - Contributed to ha, nfv, fault, metal, specs, config (expecting more as the project moves forward) * Networking - Contributed to monitoring, openstack-helm, specs, integ, config, openstack/neutron, openstack/neutron-specs, upstream, openstack/neutron-lib, openstack/neutron-tempest-plugin, openstack/python-openstackclient, openstack/openstacksdk * Openstack-distro - Contributed to openstack-armada-app, upstream, tools, root, openstack/python-openstackclient, openstack/nova, openstack/openstack-helm, openstack/python-novaclient, integ For most of our projects, we can generate the eligible voters by simply querying the repos. For Multi-OS, Networking and OpenStack-distro, that approach doesn't work and the PLs have to keep track of who commits on behalf of the project. I think that approach is far from ideal and would like to open a discussion about what we can do to help these PLs solve this problem for the next election. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Thu Oct 17 21:36:25 2019 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 17 Oct 2019 14:36:25 -0700 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F36088FA4@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F35F28711@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F36086E35@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F36088FA4@SHSMSX104.ccr.corp.intel.com> Message-ID: <95b0f80b-ed39-32b7-e2f8-aae644b081de@linux.intel.com> Please find attached the spreadsheet analyzing the Kernel patches to the existing CentOS 3.10 kernel. As mentioned, most of the patches can be dropped, except for the Notification of Death patch. My understanding is that changes have been made to StarlingX to support the Workqueue CPU affinity model with isolcpus instead of the kthread model that is in the 3.10 kernel. If this is actually the case then we can drop the cpu affinity related patches also. (this would be a good thing). Don't hesitate to reach out and ask for help with the kernel and/or CentOS 8 User space updates. Sau! On 10/16/19 6:53 AM, Xie, Cindy wrote: > Agenda & notes  for 10/16 meeting: > > . Ceph containerization     update (Tingjie) > https://review.opendev.org/#/c/681457/ this is for Helm chart definition, can be review now. > https://review.opendev.org/#/c/687340/ for Helm overrides framework, need to extend later. > verified in AIO and multi-node provision. > configuration needs to be override according to STX parameters. > Martin working on this for parameters to align w/ the native deployment. > for stx.3.0: only to merge the implantation for Helm chart and override framework. and rook-plugin which support sysinv, this can co-exist w/ current native ceph deployment. > test case development is in progress, Tingjie will sync with Fernando. > for sysinv, still need to working on patches, not ready for upload/review. > AR: Tingjie to send email to the mailing list for the current status & planning for include partial implementation without impacting the native Ceph functionality. > > . Debranding update (Saul) > Starting from the tools repo, the tools in the build area to debrand the mirroring process. Part of this is for ease of use for build steps. Very early stage. Not fit in stx.3.0 scope. > https://storyboard.openstack.org/#!/story/2006387, call volunteer from the community. > > . CentOS 8 upgrade planning     (Cindy) > CentOS 8.0 2 stories created: > https://storyboard.openstack.org/#!/story/2006728, the kernel inside CentOS 8 is 4.18, there is no RT kernel. > https://storyboard.openstack.org/#!/story/2006729 > Shuai is working on new kernel onto build system. Need to understand each patches. there was an earlier analysis for kernel patches available. > AR: Saul please share this analysis to Shuai. against 4.19 kernel some long time ago. > See > https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAugOWXMjB7VIrfc/edit#gid=311578025 Tab Kernel Patches Details > https://github.com/xe1gyq/linux/commits/v4.19 > https://github.com/xe1gyq/linux/commits/v4.18 > AR: Shuai to provide an Excel sheet to compare RPM/sRPM in StarlingX and in CentOS 8.0 > > . Opens - none > _____________________________________________ > From: Xie, Cindy > Sent: Tuesday, October 15, 2019 9:39 PM > To: Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; 'Rowsell, Brent' > Subject: RE: Weekly StarlingX non-OpenStack distro meeting > > > Agenda: > - Ceph containerization update (Tingjie) > - Debranding update (Saul) > - CentOS 8 upgrade planning (Cindy) > - Opens > > Cindy Xie > IAGS > > http://starlingx.io/ > > > -----Original Appointment----- > From: Xie, Cindy > Sent: Thursday, April 25, 2019 5:42 PM > To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' > Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W > Subject: Weekly StarlingX non-OpenStack distro meeting > When: Wednesday, October 16, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. > Where: https://zoom.us/j/342730236 > > > . 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 > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -------------- next part -------------- A non-text attachment was scrubbed... Name: Kernel_patch_analysis.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 29502 bytes Desc: not available URL: From sgw at linux.intel.com Thu Oct 17 21:39:13 2019 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 17 Oct 2019 14:39:13 -0700 Subject: [Starlingx-discuss] Cross checking projects and repos In-Reply-To: <9A85D2917C58154C960D95352B22818BDFBF9538@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BDFBF9538@fmsmsx123.amr.corp.intel.com> Message-ID: <2a873efd-4696-32f1-7e0b-48a37fcc0387@linux.intel.com> See comments about the repo list, we can drop 4 of them for sure. On 10/17/19 2:30 PM, Jones, Bruce E wrote: > TL;DR We have repos that are not listed in the projects.yaml file used > for generating eligible voters.  We have projects with a one-to-many > relationship to repos, some of which are not part of StarlingX, which > makes running scripts to find eligible voters a problem.  We should fix > both issues. > > As the (soon to be former) PL of the Openstack-distro project, and as > one of the election officials, I’ve been busy the last few weeks trying > to get my arms around figuring out who the eligible voters are for the > project.  Sadly, it’s not as easy as it could be.  The Openstack-distro > project doesn’t own any repos, instead the team contributes to repos > owned by other projects. > > I thought I’d take a look at the similar projects see what the mapping > of repos to projects looks like overall. > > I mapped our repos to projects using the projects.yaml file in the > governance repo.  The following starlingX repos are _/not/_ listed in > projects.yaml by any sub-project: > > ·Election                - Cores are the Election officials, likely OK > > ·Governance       - Cores are the TSC, likely OK > > ·Gplv2                    - Not listed > > ·Gplv3                    - Not listed > Not used any more, likely OK > ·Specs                    - Cores are the TSC, likely OK > > ·Tis-repo               - Not listed > Also not used > ·Upstream            - Not listed > This should be part of the Openstack Team > ·Utils                       - Not listed > Not used. > Question: Are the repos shown as “Not listed” above still used?   Should > we add them to the projects.yaml file?  If so, where? > > I then thought I’d take a look at the 3 projects that do not own any > repos.  I went through the project’s Etherpads and looked at the reviews > shown in them, to see where the code contributed by the team landed. > Here is what I found: > > ·Multi-OS                              - Contributed to ha, nfv, fault, > metal, specs, config (expecting more as the project moves forward) > > ·Networking                        - Contributed to monitoring, > openstack-helm, specs, integ, config, openstack/neutron, > openstack/neutron-specs, upstream, openstack/neutron-lib, > openstack/neutron-tempest-plugin, openstack/python-openstackclient, > openstack/openstacksdk > > ·Openstack-distro             - Contributed to openstack-armada-app, > upstream, tools, root, openstack/python-openstackclient, openstack/nova, > openstack/openstack-helm, openstack/python-novaclient, integ > > For most of our projects, we can generate the eligible voters by simply > querying the repos.  For Multi-OS, Networking and OpenStack-distro, that > approach doesn’t work and the PLs have to keep track of who commits on > behalf of the project. I think that approach is far from ideal and would > like to open a discussion about what we can do to help these PLs solve > this problem for the next election. > >           brucej > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From dtroyer at gmail.com Thu Oct 17 21:51:24 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 17 Oct 2019 16:51:24 -0500 Subject: [Starlingx-discuss] Train upgrade for openstack clients In-Reply-To: <9A85D2917C58154C960D95352B22818BDFBF93CF@fmsmsx123.amr.corp.intel.com> References: <72AD03D27224C74982BE13246D75B39739A64833@SHSMSX103.ccr.corp.intel.com> <72AD03D27224C74982BE13246D75B39739A651A3@SHSMSX103.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BDFBF84E0@fmsmsx123.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BDFBF93CF@fmsmsx123.amr.corp.intel.com> Message-ID: <4bb69570-5f5d-d5f8-d09d-8d8e97f05bf2@gmail.com> On 10/17/19 1:51 PM, Jones, Bruce E wrote: > We discussed this topic at the Release meeting today. The conclusion was that we do not want to upgrade puppet or ruby for this release. It's too risky. Agreed there. > As one of the last features gating our 3.0 release there is some urgency in figuring out the right approach to this upgrade. > > Where we need help is figuring out if it is possible to divide the OpenStack world into two parts and treat each part separately. > > Most of the OpenStack services running in StarlingX are in containers and should not depend on puppet at all. The 3 services that are not in containers (keystone, barbican and horizon) do depend on puppet. I still want to be really clear here, the services themselves do not depend on Puppet, the StarlingX deployment of them does. > Is it possible / practical to run the Train versions of the containerized services, while still running the Stein versions of keystone, barbican and horizon in the platform layer? I thought we had already decided to do that, but I may be behind in my news. OpenStack clients are all written with serious backward-compatibility in mind at the REST level.  OSC and the SDK both are known to still work on juno clouds for example, not all of the python-*client libs go that far back but most do. Forward compatibility is also reliable for most APIs, those that use microversioning especially so (Cinder, Ironic, Nova, etc). In the list at play here, Horizon is itself a client so it needs to be considered the same as the CLIs not as a service.  That leaves Barbican and Keystone.  I do not know much about the Barbican API other than it is not under heavy development.  I would be shocked if it did not work rolling forward a version or two.  Keystone also has a mostly-stable API, the risks here are if we need to make use of anything new in Keystone Train specifically around the distcloud functionality. I thought I saw a decision to wait on Train for the platform components until CentOS had packaging for Train available. Is that approach of just installing those packages a possibility? dt -- Dean Troyer dtroyer at gmail.com From Brent.Rowsell at windriver.com Thu Oct 17 22:29:00 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Thu, 17 Oct 2019 22:29:00 +0000 Subject: [Starlingx-discuss] Cross checking projects and repos In-Reply-To: <9A85D2917C58154C960D95352B22818BDFBF9538@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BDFBF9538@fmsmsx123.amr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EC26EA5A2@ALA-MBD.corp.ad.wrs.com> These were deprecated shortly after the project was launched. * Gplv2 - Not listed * Gplv3 - Not listed * Utils - Not listed Brent.... From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, October 17, 2019 5:30 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Cross checking projects and repos TL;DR We have repos that are not listed in the projects.yaml file used for generating eligible voters. We have projects with a one-to-many relationship to repos, some of which are not part of StarlingX, which makes running scripts to find eligible voters a problem. We should fix both issues. As the (soon to be former) PL of the Openstack-distro project, and as one of the election officials, I've been busy the last few weeks trying to get my arms around figuring out who the eligible voters are for the project. Sadly, it's not as easy as it could be. The Openstack-distro project doesn't own any repos, instead the team contributes to repos owned by other projects. I thought I'd take a look at the similar projects see what the mapping of repos to projects looks like overall. I mapped our repos to projects using the projects.yaml file in the governance repo. The following starlingX repos are _not_ listed in projects.yaml by any sub-project: * Election - Cores are the Election officials, likely OK * Governance - Cores are the TSC, likely OK * Gplv2 - Not listed * Gplv3 - Not listed * Specs - Cores are the TSC, likely OK * Tis-repo - Not listed * Upstream - Not listed * Utils - Not listed Question: Are the repos shown as "Not listed" above still used? Should we add them to the projects.yaml file? If so, where? I then thought I'd take a look at the 3 projects that do not own any repos. I went through the project's Etherpads and looked at the reviews shown in them, to see where the code contributed by the team landed. Here is what I found: * Multi-OS - Contributed to ha, nfv, fault, metal, specs, config (expecting more as the project moves forward) * Networking - Contributed to monitoring, openstack-helm, specs, integ, config, openstack/neutron, openstack/neutron-specs, upstream, openstack/neutron-lib, openstack/neutron-tempest-plugin, openstack/python-openstackclient, openstack/openstacksdk * Openstack-distro - Contributed to openstack-armada-app, upstream, tools, root, openstack/python-openstackclient, openstack/nova, openstack/openstack-helm, openstack/python-novaclient, integ For most of our projects, we can generate the eligible voters by simply querying the repos. For Multi-OS, Networking and OpenStack-distro, that approach doesn't work and the PLs have to keep track of who commits on behalf of the project. I think that approach is far from ideal and would like to open a discussion about what we can do to help these PLs solve this problem for the next election. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Thu Oct 17 22:30:49 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 17 Oct 2019 17:30:49 -0500 Subject: [Starlingx-discuss] Cross checking projects and repos In-Reply-To: <9A85D2917C58154C960D95352B22818BDFBF9538@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BDFBF9538@fmsmsx123.amr.corp.intel.com> Message-ID: <442b537a-43d1-9548-d58b-66dd009e2935@gmail.com> On 10/17/19 4:30 PM, Jones, Bruce E wrote: > I mapped our repos to projects using the projects.yaml file in the governance repo. The following starlingX repos are _not_ listed in projects.yaml by any sub-project: > * Gplv2 - Not listed > * Gplv3 - Not listed > * Tis-repo - Not listed > * Utils - Not listed These were in the original set and recombined into the flock repos soon after the initial public release. They remain in Gerrit because history. *(Actually tis-repo was never used by StarlingX, I have used it for running test jobs such as the github-based stx-nova unit and functional tests for our stable branch fork.) > * Upstream - Not listed Saul mentions below and I agree this actually is a repo for the OpenStack Distro team as that is what is in it. It should be added and its contributors checked. > For most of our projects, we can generate the eligible voters by simply querying the repos. For Multi-OS, Networking and OpenStack-distro, that approach doesn't work and the PLs have to keep track of who commits on behalf of the project. I think that approach is far from ideal and would like to open a discussion about what we can do to help these PLs solve this problem for the next election. PLs have the responsibility to track the Extra-ATCs already, that is essentially what this is when a team does not have a repo. In the end it is the team leadership (TL, PL, cores) who know who is making contributions to the goals of the team. The PL can always delegate that task to anyone they choose. The alternatives that I have thought about all require _someone_ to do more work, whether it is a team leader or the contributors themselves. Asking the contributors to do something to actively register their interest/participation would help with collecting an initial list but someone will still have to evaluate if I can get added to an electorate just by registering and lurking in the team meetings. (I wouldn't count that as a contribution.) So create a wiki page (it requires a login so can be somewhat trusted as to who is doing the editing) and ask contributors to add themselves to it to produce that initial list. Then the PL only needs to confirm foundation membership and evaluate the contribution that was made by the individuals. Or to go one step closer to what was suggested in the TSC meeting, ask the contributors to create a review adding themselves to extra-atcs and the team can +1 that for those they consider to have made sufficient contributions. dt -- Dean Troyer dtroyer at gmail.com From Brent.Rowsell at windriver.com Thu Oct 17 22:55:19 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Thu, 17 Oct 2019 22:55:19 +0000 Subject: [Starlingx-discuss] Train upgrade for openstack clients In-Reply-To: <9A85D2917C58154C960D95352B22818BDFBF93CF@fmsmsx123.amr.corp.intel.com> References: <72AD03D27224C74982BE13246D75B39739A64833@SHSMSX103.ccr.corp.intel.com> <72AD03D27224C74982BE13246D75B39739A651A3@SHSMSX103.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BDFBF84E0@fmsmsx123.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BDFBF93CF@fmsmsx123.amr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EC26EA68C@ALA-MBD.corp.ad.wrs.com> Bruce, To build on your point below, the problem should be split into 2 parts. 1) Openstack Cloud support. Openstack is containerized, it does not use puppet 2) There are a small set of openstack components that run on bare metal that provide services for the "flock" components. My 2 cents is #1 is the most important. There is no burning need to do #2 as there are no new capabilities in Train that are required. Brent From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, October 17, 2019 2:52 PM To: Bailey, Henry Albert (Al) ; Chen, Yan ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Train upgrade for openstack clients We discussed this topic at the Release meeting today. The conclusion was that we do not want to upgrade puppet or ruby for this release. It's too risky. As one of the last features gating our 3.0 release there is some urgency in figuring out the right approach to this upgrade. Where we need help is figuring out if it is possible to divide the OpenStack world into two parts and treat each part separately. Most of the OpenStack services running in StarlingX are in containers and should not depend on puppet at all. The 3 services that are not in containers (keystone, barbican and horizon) do depend on puppet. Is it possible / practical to run the Train versions of the containerized services, while still running the Stein versions of keystone, barbican and horizon in the platform layer? Or is there another creative solution to the problem? brucej From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] Sent: Thursday, October 17, 2019 7:47 AM To: Jones, Bruce E >; Chen, Yan >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Train upgrade for openstack clients I think the puppet 5 upgrade ends up being one of the more complicated parts of this activity. It looks like for 5.0.x you need to be cautious about is all the deprecated features in 4 that were removed in 5. It would not surprise me if we were still using some of those deprecated parts. https://github.com/puppetlabs/docs-archive/blob/master/puppet/5.0/release_notes.markdown Puppet 5 also uses a newer ruby. We ship ruby 2.0 now. The notes for 5.0 indicate ruby 2.4, which is extra work and can take a while if existing ruby code needs to be changed. Puppet 5 also claims to have hiera 5 built in. I don't know what that means, we ship hiera 1.3.4 separarately, so there may be packaging concerns there as well. Last time when I upversioned puppet from puppet 3 to 4 the most unexpected thing was not the code changes required, but the runtime behavior was different. Example: https://opendev.org/starlingx/integ/src/branch/master/config/puppet-4.8.2/centos/patches/1005-Set-strict_variables-and-basemodulepath-in-puppet.co.patch Experiment with installing train keystone/barbican/horizon with the existing puppet modules. If a config value is incompatible, then it may require a local change, or an upversion. Al From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, October 17, 2019 9:43 AM To: Chen, Yan; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Train upgrade for openstack clients Yan, thank you for making this very clear. As I read this, the puppet modules we use for the openstack clients are several releases old and the update to the Train version would be painful, er I mean lots of fun. I think we need some input from the broader community. What are the costs / risks of upgrading to puppet 5.0? Should we try to upgrade the client puppet modules ourselves (and contribute the changes upstream)? Or is there a better long way we should launch these clients, e.g. should we just write Ansible installers for them? My thanks to Dean for helping me understand what questions to ask :) brucej From: Chen, Yan [mailto:yan.chen at intel.com] Sent: Tuesday, October 15, 2019 10:43 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Train upgrade for openstack clients Hi, I'm now trying to upgrade the openstack clients installed on StarlingX to Train version. Currently I see the clients are Stein version, but the puppet packages (for those modules that we need to config on StarlingX host) are still old versions. [See the list below.] But for Train, I met a problem when I wanted to upgrade python-openstackclient/keystone to Train (4.0.0), the old puppet packages cannot work with Train clients and failed when running puppet-manifest-apply.sh. See from Stein keystone log, some of the deprecated cmds and options are planned to be removed in Train. If we want to make Train clients work, we may need to do the following steps: 1. Upgrade puppet itself (required 5.x by Train) 2. Upgrade all the OpenStack related puppet packages accordingly, and update StarlingX patches. 3. If flock puppet pkgs are based on puppet 4.8.2, we also need to upgrade our code. 4. If other puppet pkgs are based on puppet 4.8.2, we also need to upgrade those pkgs. So is it possible that we keep on using Stein clients with limited test now (need test with Train images, but suppose old functions should still work)? Here's the list of the puppet packages and StarlingX patches (for Stein it should be 14.1.0 - 14.4.0, and for Train 15.0.0 - 15.4.0): Pkg Current Version Train Upgrade to Meta Patch Patch puppet 4.8.2 5.x 2 5 puppet-keystone 11.3.0 15.x 6 5 puppet-oslo 11.3.0 15.x 3 2 puppet-openstacklib 11.5.0 15.x 2 1 puppet-horizon 11.5.0 15.x 2 1 puppet-barbican 11.3.0 15.x 0 0 Stein Keystone client logs: keystone:log 2019-10-10 10:04:44.050 111346 WARNING keystone.server.flask.request_processing.middleware.auth_context [-] The use of the '[DEFAULT] admin_token' configurationoption presents a significant security risk and should not be set. This option is deprecated in favor of using 'keystone-manage bootstrap' and will be removed in a future release. Yan -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Thu Oct 17 23:07:42 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 17 Oct 2019 23:07:42 +0000 Subject: [Starlingx-discuss] Cross checking projects and repos In-Reply-To: <442b537a-43d1-9548-d58b-66dd009e2935@gmail.com> References: <9A85D2917C58154C960D95352B22818BDFBF9538@fmsmsx123.amr.corp.intel.com> <442b537a-43d1-9548-d58b-66dd009e2935@gmail.com> Message-ID: <20191017230736.3wfmx3ktyhs7nhjo@yuggoth.org> On 2019-10-17 17:30:49 -0500 (-0500), Dean Troyer wrote: > On 10/17/19 4:30 PM, Jones, Bruce E wrote: > > I mapped our repos to projects using the projects.yaml file in the governance repo. The following starlingX repos are _not_ listed in projects.yaml by any sub-project: > > > * Gplv2 - Not listed > > * Gplv3 - Not listed > > * Tis-repo - Not listed > > * Utils - Not listed > > These were in the original set and recombined into the flock repos soon > after the initial public release. They remain in Gerrit because history. > *(Actually tis-repo was never used by StarlingX, I have used it for running > test jobs such as the github-based stx-nova unit and functional tests for > our stable branch fork.) [...] You might consider checking out the way OpenStack solved a similar tracking problem: https://opendev.org/openstack/governance/raw/branch/master/reference/legacy.yaml Basically create a shadow of projects.yaml where you move or record entries for repositories (and even entire teams) which were at one time official but no longer are, including information on when they ceased being in use and were retired. If you follow the same schema OpenStack does, the existing election tools can even evaluate contributions to repositories which were retired after the start of the qualifying window for an election (if any were still official for part of that time). -- 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 maria.g.perez.ibarra at intel.com Thu Oct 17 23:30:35 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 17 Oct 2019 23:30:35 +0000 Subject: [Starlingx-discuss] [ Regression testing - stx3.0 ] Report for 10/17/2019 Message-ID: StarlingX 3.0 Release Status: ISO: BUILD_ID="20191011T013000Z" from (link) ---------------------------------------------------------------------- MANUAL EXECUTION ---------------------------------------------------------------------- Overall Results: Total = 274 Pass = 116 Fail = 5 Blocked = 0 Not Run = 151 Obsolete = 2 Deferred = 0 Total executed = 215 Pass Rate = 95.8% Formula used : Pass Rate = (pass * 100) / (pass + fail) --------------------------------------------------------------------------- AUTOMATED ROBOT - INTEL --------------------------------------------------------------------------- Overall Results: Total = 202 Pass = 24 Fail = 6 Blocked = 36 Obsolete = 0 Deferred = 0 Not Valid = 1 Total executed = 30 Pass Rate = 80% Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- AUTOMATED PYTEST - WR --------------------------------------------------------------------------- Overall Results: Total = 467 Pass = 0 Fail = 0 Blocked = 0 Not Run = 467 Obsolete = 0 Deferred = 0 Total executed = 0 Pass Rate = Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- BUGS --------------------------------------------------------------------------- For more detail of the tests: https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 Regards! Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Thu Oct 17 23:32:28 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 17 Oct 2019 23:32:28 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191017 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-17 (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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006529.html Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Oct 17 23:45:04 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 17 Oct 2019 23:45:04 +0000 Subject: [Starlingx-discuss] Train upgrade for openstack clients In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EC26EA68C@ALA-MBD.corp.ad.wrs.com> References: <72AD03D27224C74982BE13246D75B39739A64833@SHSMSX103.ccr.corp.intel.com> <72AD03D27224C74982BE13246D75B39739A651A3@SHSMSX103.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BDFBF84E0@fmsmsx123.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BDFBF93CF@fmsmsx123.amr.corp.intel.com> <2588653EBDFFA34B982FAF00F1B4844EC26EA68C@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BDFBF95CF@fmsmsx123.amr.corp.intel.com> Brent, thank you, that makes sense. Yan & the openstack-distro team - please focus on 1) below -the containerized openstack services. brucej From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Thursday, October 17, 2019 3:55 PM To: Jones, Bruce E ; Bailey, Henry Albert (Al) ; Chen, Yan ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Train upgrade for openstack clients Bruce, To build on your point below, the problem should be split into 2 parts. 1) Openstack Cloud support. Openstack is containerized, it does not use puppet 2) There are a small set of openstack components that run on bare metal that provide services for the "flock" components. My 2 cents is #1 is the most important. There is no burning need to do #2 as there are no new capabilities in Train that are required. Brent From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, October 17, 2019 2:52 PM To: Bailey, Henry Albert (Al) >; Chen, Yan >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Train upgrade for openstack clients We discussed this topic at the Release meeting today. The conclusion was that we do not want to upgrade puppet or ruby for this release. It's too risky. As one of the last features gating our 3.0 release there is some urgency in figuring out the right approach to this upgrade. Where we need help is figuring out if it is possible to divide the OpenStack world into two parts and treat each part separately. Most of the OpenStack services running in StarlingX are in containers and should not depend on puppet at all. The 3 services that are not in containers (keystone, barbican and horizon) do depend on puppet. Is it possible / practical to run the Train versions of the containerized services, while still running the Stein versions of keystone, barbican and horizon in the platform layer? Or is there another creative solution to the problem? brucej From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] Sent: Thursday, October 17, 2019 7:47 AM To: Jones, Bruce E >; Chen, Yan >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Train upgrade for openstack clients I think the puppet 5 upgrade ends up being one of the more complicated parts of this activity. It looks like for 5.0.x you need to be cautious about is all the deprecated features in 4 that were removed in 5. It would not surprise me if we were still using some of those deprecated parts. https://github.com/puppetlabs/docs-archive/blob/master/puppet/5.0/release_notes.markdown Puppet 5 also uses a newer ruby. We ship ruby 2.0 now. The notes for 5.0 indicate ruby 2.4, which is extra work and can take a while if existing ruby code needs to be changed. Puppet 5 also claims to have hiera 5 built in. I don't know what that means, we ship hiera 1.3.4 separarately, so there may be packaging concerns there as well. Last time when I upversioned puppet from puppet 3 to 4 the most unexpected thing was not the code changes required, but the runtime behavior was different. Example: https://opendev.org/starlingx/integ/src/branch/master/config/puppet-4.8.2/centos/patches/1005-Set-strict_variables-and-basemodulepath-in-puppet.co.patch Experiment with installing train keystone/barbican/horizon with the existing puppet modules. If a config value is incompatible, then it may require a local change, or an upversion. Al From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, October 17, 2019 9:43 AM To: Chen, Yan; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Train upgrade for openstack clients Yan, thank you for making this very clear. As I read this, the puppet modules we use for the openstack clients are several releases old and the update to the Train version would be painful, er I mean lots of fun. I think we need some input from the broader community. What are the costs / risks of upgrading to puppet 5.0? Should we try to upgrade the client puppet modules ourselves (and contribute the changes upstream)? Or is there a better long way we should launch these clients, e.g. should we just write Ansible installers for them? My thanks to Dean for helping me understand what questions to ask :) brucej From: Chen, Yan [mailto:yan.chen at intel.com] Sent: Tuesday, October 15, 2019 10:43 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Train upgrade for openstack clients Hi, I'm now trying to upgrade the openstack clients installed on StarlingX to Train version. Currently I see the clients are Stein version, but the puppet packages (for those modules that we need to config on StarlingX host) are still old versions. [See the list below.] But for Train, I met a problem when I wanted to upgrade python-openstackclient/keystone to Train (4.0.0), the old puppet packages cannot work with Train clients and failed when running puppet-manifest-apply.sh. See from Stein keystone log, some of the deprecated cmds and options are planned to be removed in Train. If we want to make Train clients work, we may need to do the following steps: 1. Upgrade puppet itself (required 5.x by Train) 2. Upgrade all the OpenStack related puppet packages accordingly, and update StarlingX patches. 3. If flock puppet pkgs are based on puppet 4.8.2, we also need to upgrade our code. 4. If other puppet pkgs are based on puppet 4.8.2, we also need to upgrade those pkgs. So is it possible that we keep on using Stein clients with limited test now (need test with Train images, but suppose old functions should still work)? Here's the list of the puppet packages and StarlingX patches (for Stein it should be 14.1.0 - 14.4.0, and for Train 15.0.0 - 15.4.0): Pkg Current Version Train Upgrade to Meta Patch Patch puppet 4.8.2 5.x 2 5 puppet-keystone 11.3.0 15.x 6 5 puppet-oslo 11.3.0 15.x 3 2 puppet-openstacklib 11.5.0 15.x 2 1 puppet-horizon 11.5.0 15.x 2 1 puppet-barbican 11.3.0 15.x 0 0 Stein Keystone client logs: keystone:log 2019-10-10 10:04:44.050 111346 WARNING keystone.server.flask.request_processing.middleware.auth_context [-] The use of the '[DEFAULT] admin_token' configurationoption presents a significant security risk and should not be set. This option is deprecated in favor of using 'keystone-manage bootstrap' and will be removed in a future release. Yan -------------- next part -------------- An HTML attachment was scrubbed... URL: From yan.chen at intel.com Fri Oct 18 02:20:09 2019 From: yan.chen at intel.com (Chen, Yan) Date: Fri, 18 Oct 2019 02:20:09 +0000 Subject: [Starlingx-discuss] Train upgrade for openstack clients In-Reply-To: <9A85D2917C58154C960D95352B22818BDFBF95CF@fmsmsx123.amr.corp.intel.com> References: <72AD03D27224C74982BE13246D75B39739A64833@SHSMSX103.ccr.corp.intel.com> <72AD03D27224C74982BE13246D75B39739A651A3@SHSMSX103.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BDFBF84E0@fmsmsx123.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BDFBF93CF@fmsmsx123.amr.corp.intel.com> <2588653EBDFFA34B982FAF00F1B4844EC26EA68C@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BDFBF95CF@fmsmsx123.amr.corp.intel.com> Message-ID: <72AD03D27224C74982BE13246D75B39739A65576@SHSMSX103.ccr.corp.intel.com> Thank you all for making this clear. Currently Zhipeng is working on containerized OpenStack upgrade. And 3 patches for Horizon upgrade for StarlingX dashboard are also under review. Yan From: Jones, Bruce E Sent: Friday, October 18, 2019 07:45 To: Rowsell, Brent ; Bailey, Henry Albert (Al) ; Chen, Yan ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Train upgrade for openstack clients Brent, thank you, that makes sense. Yan & the openstack-distro team - please focus on 1) below -the containerized openstack services. brucej From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Thursday, October 17, 2019 3:55 PM To: Jones, Bruce E >; Bailey, Henry Albert (Al) >; Chen, Yan >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Train upgrade for openstack clients Bruce, To build on your point below, the problem should be split into 2 parts. 1. Openstack Cloud support. Openstack is containerized, it does not use puppet 2. There are a small set of openstack components that run on bare metal that provide services for the "flock" components. My 2 cents is #1 is the most important. There is no burning need to do #2 as there are no new capabilities in Train that are required. Brent From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, October 17, 2019 2:52 PM To: Bailey, Henry Albert (Al) >; Chen, Yan >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Train upgrade for openstack clients We discussed this topic at the Release meeting today. The conclusion was that we do not want to upgrade puppet or ruby for this release. It's too risky. As one of the last features gating our 3.0 release there is some urgency in figuring out the right approach to this upgrade. Where we need help is figuring out if it is possible to divide the OpenStack world into two parts and treat each part separately. Most of the OpenStack services running in StarlingX are in containers and should not depend on puppet at all. The 3 services that are not in containers (keystone, barbican and horizon) do depend on puppet. Is it possible / practical to run the Train versions of the containerized services, while still running the Stein versions of keystone, barbican and horizon in the platform layer? Or is there another creative solution to the problem? brucej From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] Sent: Thursday, October 17, 2019 7:47 AM To: Jones, Bruce E >; Chen, Yan >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Train upgrade for openstack clients I think the puppet 5 upgrade ends up being one of the more complicated parts of this activity. It looks like for 5.0.x you need to be cautious about is all the deprecated features in 4 that were removed in 5. It would not surprise me if we were still using some of those deprecated parts. https://github.com/puppetlabs/docs-archive/blob/master/puppet/5.0/release_notes.markdown Puppet 5 also uses a newer ruby. We ship ruby 2.0 now. The notes for 5.0 indicate ruby 2.4, which is extra work and can take a while if existing ruby code needs to be changed. Puppet 5 also claims to have hiera 5 built in. I don't know what that means, we ship hiera 1.3.4 separarately, so there may be packaging concerns there as well. Last time when I upversioned puppet from puppet 3 to 4 the most unexpected thing was not the code changes required, but the runtime behavior was different. Example: https://opendev.org/starlingx/integ/src/branch/master/config/puppet-4.8.2/centos/patches/1005-Set-strict_variables-and-basemodulepath-in-puppet.co.patch Experiment with installing train keystone/barbican/horizon with the existing puppet modules. If a config value is incompatible, then it may require a local change, or an upversion. Al From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, October 17, 2019 9:43 AM To: Chen, Yan; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Train upgrade for openstack clients Yan, thank you for making this very clear. As I read this, the puppet modules we use for the openstack clients are several releases old and the update to the Train version would be painful, er I mean lots of fun. I think we need some input from the broader community. What are the costs / risks of upgrading to puppet 5.0? Should we try to upgrade the client puppet modules ourselves (and contribute the changes upstream)? Or is there a better long way we should launch these clients, e.g. should we just write Ansible installers for them? My thanks to Dean for helping me understand what questions to ask :) brucej From: Chen, Yan [mailto:yan.chen at intel.com] Sent: Tuesday, October 15, 2019 10:43 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Train upgrade for openstack clients Hi, I'm now trying to upgrade the openstack clients installed on StarlingX to Train version. Currently I see the clients are Stein version, but the puppet packages (for those modules that we need to config on StarlingX host) are still old versions. [See the list below.] But for Train, I met a problem when I wanted to upgrade python-openstackclient/keystone to Train (4.0.0), the old puppet packages cannot work with Train clients and failed when running puppet-manifest-apply.sh. See from Stein keystone log, some of the deprecated cmds and options are planned to be removed in Train. If we want to make Train clients work, we may need to do the following steps: 1. Upgrade puppet itself (required 5.x by Train) 2. Upgrade all the OpenStack related puppet packages accordingly, and update StarlingX patches. 3. If flock puppet pkgs are based on puppet 4.8.2, we also need to upgrade our code. 4. If other puppet pkgs are based on puppet 4.8.2, we also need to upgrade those pkgs. So is it possible that we keep on using Stein clients with limited test now (need test with Train images, but suppose old functions should still work)? Here's the list of the puppet packages and StarlingX patches (for Stein it should be 14.1.0 - 14.4.0, and for Train 15.0.0 - 15.4.0): Pkg Current Version Train Upgrade to Meta Patch Patch puppet 4.8.2 5.x 2 5 puppet-keystone 11.3.0 15.x 6 5 puppet-oslo 11.3.0 15.x 3 2 puppet-openstacklib 11.5.0 15.x 2 1 puppet-horizon 11.5.0 15.x 2 1 puppet-barbican 11.3.0 15.x 0 0 Stein Keystone client logs: keystone:log 2019-10-10 10:04:44.050 111346 WARNING keystone.server.flask.request_processing.middleware.auth_context [-] The use of the '[DEFAULT] admin_token' configurationoption presents a significant security risk and should not be set. This option is deprecated in favor of using 'keystone-manage bootstrap' and will be removed in a future release. Yan -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Fri Oct 18 08:03:35 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Fri, 18 Oct 2019 03:03:35 -0500 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <4417ee$brdo2f@fmsmga006.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191018T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-apiserver:v1.16.0 k8s.gcr.io/kube-controller-manager:v1.16.0 k8s.gcr.io/kube-proxy:v1.16.0 k8s.gcr.io/kube-scheduler:v1.16.0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From Brent.Rowsell at windriver.com Fri Oct 18 13:20:02 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Fri, 18 Oct 2019 13:20:02 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting In-Reply-To: <9700A18779F35F49AF027300A49E7C76608D7CA6@SHSMSX105.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C76608D7CA6@SHSMSX105.ccr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EC26ED58D@ALA-MBD.corp.ad.wrs.com> Thanks. See inline Brent From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, October 17, 2019 9:00 AM To: Miller, Frank ; Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: RE: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting Hi Frank & Brent & all, I have updated my patches to remove the visible password for registry. Please help review the update in ansible-playbooks/stx-puppet. Here is the link for the patch list: https://review.opendev.org/#/q/topic:kata+(status:open) - Add a commit to make containerd the default CLI (and remove any docker code that is no longer needed) [shuicheng] do you mean change the "/var/lib/docker" directory to "/var/lib/containerd" for both docker and containerd? If the answer is yes, I prefer to do it later, after docker runtime is not used at all. Currently, armada is still using docker. - Add a test case for local registry pull/push and authentication [BR] What is the plan to remove dockerd ? [shuicheng] With the new patch, local registry still could be accessed both by Kubernetes and crictl. For crictl, username/password need be provided in CLI, similar to "docker login" for docker CLI. - Update code to ensure admin password is not visible [shuicheng] Done. Best Regards Shuicheng From: Miller, Frank > Sent: Tuesday, October 15, 2019 10:16 PM To: starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting Since we did not get through the whole agenda today, I will schedule the next meeting 1 week from today. Minutes for Oct 15 meeting: 1. Review KATA containers feature with container Cores. Shuicheng to present feature overview and current status. - Shuicheng's commits: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) - Shuicheng presented his feature and what has been done so far (see his charts in separate email) Actions identified: - Concerns: Interaction with registry, admin password is visible - Add a commit to make containerd the default CLI (and remove any docker code that is no longer needed) - Add a test case for local registry pull/push and authentication - Update code to ensure admin password is not visible - Frank to book a follow-up meeting to continue the review (Frank to book Tuesday Oct 22) Frank -----Original Appointment----- From: Miller, Frank Sent: Thursday, October 10, 2019 2:55 PM To: Miller, Frank; starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: StarlingX Bi-Weekly Containerization Meeting When: Tuesday, October 15, 2019 9:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236 Apologies, re-sending without etherpad formatting. Note: We agreed to a new day and time for these meetings. For all who are working containerization features or LPs please join for our bi-weekly meeting. Agenda for October 15 meeting: 1. Review KATA containers feature with container Cores. Shuicheng to present feature overview and current status. - Shuicheng's commits: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) 2. Updates on other stx.3.0 container features for MS3 milestone: - 2004008: [Feature] Create HELM chart for Fault project [An Ran] - one commit needs a new approach - discussed in item #2 - Decision to be made about Horizon issue - do we keep FM containers enabled without Horizon for VM alarms? Or do we disable in stx.3.0 until issue can be addressed in stx.4.0? - 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] - require updated forecast - 2005514: QAT K8S device plugin support in StarlingX - Bruce: Code is out for review; Frank to follow-up with Cindy or feature primes for updated forecasts - 2005860: Upversion container components [Al Bailey] - 2004761: Integrate Backup & Restore with Containers [Ovidiu Poncea] 3. Update on stx.4.0 features: - 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC 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 Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Fri Oct 18 14:14:43 2019 From: scott.little at windriver.com (Scott Little) Date: Fri, 18 Oct 2019 10:14:43 -0400 Subject: [Starlingx-discuss] StarlingX 2.0.1 Message-ID: <0a8fe7c2-e7b9-d494-7a7f-930ed56b4cd0@windriver.com> The official StarlingX 2.0.1 installation iso is available at the following URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/release/2.0.1/centos/outputs/iso/ Other build artifacts can be found under: http://mirror.starlingx.cengn.ca/mirror/starlingx/release/2.0.1/centos/ The exact source code can be cloned by:    repo init -u https://opendev.org/starlingx/manifest -b refs/tags/2.0.1b    repo sync --force-sync Scott Little PS.  Why 2.0.1b?  A scripting error on my part pushed the 2.0.1 tag before code reviews were complete on the manifest.  There were revisions, and deleting the erroneous tag requires some significant manual cleanup within the Zuul infrastructure. From thierry at openstack.org Fri Oct 18 14:29:07 2019 From: thierry at openstack.org (Thierry Carrez) Date: Fri, 18 Oct 2019 16:29:07 +0200 Subject: [Starlingx-discuss] [survey] StarlingX community dashboard Message-ID: <983fa25d-4e9c-1f29-fb03-6d85211d3058@openstack.org> Hi everyone, The community dashboard at starlingx.biterg.io helps provide insights on community activity and diversity for the StarlingX project. We created a short survey to help us assess how useful those dashboards are to the community, as well as define key areas for future improvements. It should take less than 2 minutes to complete. Please fill the survey at: https://www.surveymonkey.com/r/5KW9X8J -- Thierry Carrez (ttx) From Ghada.Khalil at windriver.com Fri Oct 18 15:38:59 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 18 Oct 2019 15:38:59 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 10/17 Message-ID: <151EE31B9FCCA54397A757BC674650F0C15CE1A0@ALA-MBD.corp.ad.wrs.com> Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Team Meeting Agenda/Notes - Oct 17/2019 stx.3.0 Features / Enhancements - Milestone-3 is this week, but is at risk - TSN Support for VM workloads - https://storyboard.openstack.org/#!/story/2005516 - Prime: Huifeng - Elio: Testing was complete two weeks ago - October 4 - This feature is considered Done. Action: Update the tasks in the story accordingly. - Cindy requested additional testing with kata containers. - This should be tracked separately. It's outside the scope of the current feature. - OVS collectd resource monitoring - Prime: Chenjie - https://storyboard.openstack.org/#!/story/2002948 / https://bugs.launchpad.net/starlingx/+bug/1834512 - Patch has been submitted and tested and is in review now: https://review.opendev.org/#/c/687025/ - New cni sriov plugin - https://bugs.launchpad.net/starlingx/+bug/1835020 - Prime: Steve - Done as of 2019-10-10 - Openstack Rebase to Train - This is in progress currently. No involvement from the networking team as of yet. - Action: Huifeng to follow up with Bruce (bruce.e.jones at intel.com) & Yong (yong.hu at intel.com) to see if anything is needed related to neutron. - Should participate in neutron basic testing as part of the rebase to ensure basic use-cases are working stx.4.0 Feature Proposals: - OVS-DPDK Containerization (Defered from stx.3.0) - Prime: Cheng Li - story link: https://storyboard.openstack.org/#!/story/2005496 - Openstack-helm community pathches are merged. Will work on stx projects. - Openstack Rebase to Ussuri - This is for neutron support - TSN Support for containers (??) - Any other ideas? - From Matt: - Baremetal Ingress Controllers - Contribute to the calico project since we are using it in stx - Action: Huifeng to follow-up with Ruijin about any other networking feature proposals stx.2.0 Bugs - Query: https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=stx.networking+stx.2.0&field.tags_combinator=ALL&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search - Current Count: 4 / In Progress: - https://bugs.launchpad.net/starlingx/+bug/1835807 - Joseph, on hold - https://bugs.launchpad.net/starlingx/+bug/1836252 - Joseph, on hold - https://bugs.launchpad.net/starlingx/+bug/1839181 - Chenjie, on hold for another reproduction where more data may be gathered. - https://bugs.launchpad.net/starlingx/+bug/1844223 - YaoLe, not a bug; appears to be a configuration issue. Continue to work with reporter. Expect to close shortly. - https://bugs.launchpad.net/starlingx/+bug/1847971 - New / Needs investigation stx.3.0 Bugs - Deadline for bug resolution: End of Nov - Query: https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=stx.networking+stx.3.0&field.tags_combinator=ALL&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search - Current count: 14 / In Progress: 5 - Agreed to do a scrub on our next call From maria.g.perez.ibarra at intel.com Fri Oct 18 22:12:28 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Fri, 18 Oct 2019 22:12:28 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191018 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-18 (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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006577.html Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Fri Oct 18 23:31:53 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Fri, 18 Oct 2019 23:31:53 +0000 Subject: [Starlingx-discuss] opendev statistics Message-ID: <2FD5DDB5A04D264C80D42CA35194914F3608C5AB@SHSMSX104.ccr.corp.intel.com> Jeremy, Do we have any statistics like github (# of watches, stars, etc) for opendev infra? Just curious to see it. Cindy Xie IAGS [StarlingX] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 11582 bytes Desc: image002.png URL: From fungi at yuggoth.org Fri Oct 18 23:40:52 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Fri, 18 Oct 2019 23:40:52 +0000 Subject: [Starlingx-discuss] opendev statistics In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F3608C5AB@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F3608C5AB@SHSMSX104.ccr.corp.intel.com> Message-ID: <20191018234052.ltrx54czpfcwp4kv@yuggoth.org> On 2019-10-18 23:31:53 +0000 (+0000), Xie, Cindy wrote: > Do we have any statistics like github (# of watches, stars, etc) > for opendev infra? Just curious to see it. There is a feature in Gerrit to "watch" specific repositories so that you receive E-mail notification when there are updates to change proposals for them. Also Gerrit has the ability to "star" individual changes you're keeping track of. These are utilitarian functions targeted at streamlining code review workflows, so not exposed as vanity stats the same way social media sites like GitHub do. I could probably find a way to query them if you could be specific as to the need. -- 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 cindy.xie at intel.com Sat Oct 19 00:08:04 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Sat, 19 Oct 2019 00:08:04 +0000 Subject: [Starlingx-discuss] opendev statistics In-Reply-To: <20191018234052.ltrx54czpfcwp4kv@yuggoth.org> References: <2FD5DDB5A04D264C80D42CA35194914F3608C5AB@SHSMSX104.ccr.corp.intel.com> <20191018234052.ltrx54czpfcwp4kv@yuggoth.org> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F3608C613@SHSMSX104.ccr.corp.intel.com> Normally github watches & stars are used to measure how the project is fitting the community interest. For myself, when somebody recommend an OSS project to me, I will go to github and see how popular it is, and there are what I am looking for. The feature you described below to me, not sure how often people are using them, but as it's not explicitly visible to observers, it is difficult to use judge the community fit I think. Cindy Xie IAGS -----Original Message----- From: Jeremy Stanley Sent: Saturday, October 19, 2019 7:41 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] opendev statistics On 2019-10-18 23:31:53 +0000 (+0000), Xie, Cindy wrote: > Do we have any statistics like github (# of watches, stars, etc) for > opendev infra? Just curious to see it. There is a feature in Gerrit to "watch" specific repositories so that you receive E-mail notification when there are updates to change proposals for them. Also Gerrit has the ability to "star" individual changes you're keeping track of. These are utilitarian functions targeted at streamlining code review workflows, so not exposed as vanity stats the same way social media sites like GitHub do. I could probably find a way to query them if you could be specific as to the need. -- Jeremy Stanley From fungi at yuggoth.org Sat Oct 19 00:34:13 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Sat, 19 Oct 2019 00:34:13 +0000 Subject: [Starlingx-discuss] opendev statistics In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F3608C613@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F3608C5AB@SHSMSX104.ccr.corp.intel.com> <20191018234052.ltrx54czpfcwp4kv@yuggoth.org> <2FD5DDB5A04D264C80D42CA35194914F3608C613@SHSMSX104.ccr.corp.intel.com> Message-ID: <20191019003412.wysmrx5eczqobt54@yuggoth.org> On 2019-10-19 00:08:04 +0000 (+0000), Xie, Cindy wrote: > Normally github watches & stars are used to measure how the > project is fitting the community interest. For myself, when > somebody recommend an OSS project to me, I will go to github and > see how popular it is, and there are what I am looking for. Usually I'm looking to see what Linux distributions are actively packaging the software, how readily its maintainers respond to defect reports, whether and where its security advisories are published, how often it produces releases, or similar quality and health indicators. I've never observed a correlation between GitHub watches/stars and software viability. Usually the only time I see them mentioned are in press releases or conference talks when someone is attempting to dupe an unwitting audience with seemingly-relevant statistics they don't understand. There's also apparently a thriving market for buying GitHub stars, watchers, forks and followers (just for amusement, the first hit from a quick Web search turns up a service who is willing to sell me stars in bulk at a going rate of us$0.70 each). That aside, the watches and stars on GitHub are social networking constructs which tend to only accrue with the network effect of a large social platform. OpenDev doesn't have much in the way of competing projects you're going to compare "likes" on to determine which one is the most popular, nor would comparing such values against those on another platform like GitHub be meaningful at all since they'd need to be scaled by the relative user-bases of each. > The feature you described below to me, not sure how often people > are using them, but as it's not explicitly visible to observers, > it is difficult to use judge the community fit I think. Correct, they are specifically for streamlining code review workflows, and the only people who are even likely to have accounts to be able to set them are people uploading patches and reviewing changes in OpenDev's Gerrit code review system. I wouldn't expect them to indicate anything aside from maybe habits of the developer and reviewer demographics of a project. -- 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 ricardo.o.perez at intel.com Sat Oct 19 02:29:44 2019 From: ricardo.o.perez at intel.com (Perez, Ricardo O) Date: Sat, 19 Oct 2019 02:29:44 +0000 Subject: [Starlingx-discuss] Is there any change to get SSH / Ping in VMs ? Message-ID: Hello Team, Currently I'm trying to launch a Cirros VM to perform the following operations (in a duplex config): * Ping / ssh / scp What I'm seeing is the following: * I have created a security group with the following settings: openstack security group create security1 openstack security group rule create --ingress --protocol icmp --remote-ip 0.0.0.0/0 security1 openstack security group rule create --ingress --protocol tcp --remote-ip 0.0.0.0/0 security1 openstack security group rule create --ingress --protocol udp --remote-ip 0.0.0.0/0 security1 * If I use any flavor with this property: --property hw:mem_page_size=large * I hit an error and the VM isn't launched: controller-0:~# openstack server list +--------------------------------------+-------+--------+----------+--------+---------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+-------+--------+----------+--------+---------+ | 8d22d73b-508c-478b-8d32-b9eb24e1b7a3 | richo | ERROR | | cirros | m1.tiny | +--------------------------------------+-------+--------+----------+--------+---------+ * However, if I use any flavor without the property mem_page_size I get a VM launched, with an IP, but I'm not able to ping it or ssh / scp to it, just login through virsh console. controller-0:~# openstack server list, and there is no IP inside of the VM, please see below: openstack server create --image cirros --flavor m1.tiny --network public-net0 --security-group security1 richo +--------------------------------------+-------+--------+----------------------------+--------+---------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+-------+--------+----------------------------+--------+---------+ | edf0896c-f9e3-4dbf-8a11-f0e5a84d4c02 | richo | ACTIVE | public-net0=192.168.101.49 | cirros | m1.tiny | +--------------------------------------+-------+--------+----------------------------+--------+---------+ controller-0:~# sudo virsh console 1 Connected to domain instance-00000003 Escape character is ^] login as 'cirros' user. default password: 'gocubsgo'. use 'sudo' for root. cirros login: cirros Password: $ ip a 1: lo: mtu 65536 qdisc noqueue qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:ca:a9:db brd ff:ff:ff:ff:ff:ff [ 1256.136730] random: nonblocking pool is initialized inet6 fe80::f816:3eff:feca:a9db/64 scope link valid_lft forever preferred_lft forever $ With the latest changes is there anything that I'm missing to get this working ? even the "ip netns" command isn't giving me any value. Thanks in advance -Ricardo -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Sat Oct 19 07:03:59 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Sat, 19 Oct 2019 07:03:59 +0000 Subject: [Starlingx-discuss] opendev statistics In-Reply-To: <20191019003412.wysmrx5eczqobt54@yuggoth.org> References: <2FD5DDB5A04D264C80D42CA35194914F3608C5AB@SHSMSX104.ccr.corp.intel.com> <20191018234052.ltrx54czpfcwp4kv@yuggoth.org> <2FD5DDB5A04D264C80D42CA35194914F3608C613@SHSMSX104.ccr.corp.intel.com> <20191019003412.wysmrx5eczqobt54@yuggoth.org> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F3608C86A@SHSMSX104.ccr.corp.intel.com> Thanks Jeremy for the detail explanation!! Cindy Xie IAGS -----Original Message----- From: Jeremy Stanley Sent: Saturday, October 19, 2019 8:34 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] opendev statistics On 2019-10-19 00:08:04 +0000 (+0000), Xie, Cindy wrote: > Normally github watches & stars are used to measure how the project is > fitting the community interest. For myself, when somebody recommend an > OSS project to me, I will go to github and see how popular it is, and > there are what I am looking for. Usually I'm looking to see what Linux distributions are actively packaging the software, how readily its maintainers respond to defect reports, whether and where its security advisories are published, how often it produces releases, or similar quality and health indicators. I've never observed a correlation between GitHub watches/stars and software viability. Usually the only time I see them mentioned are in press releases or conference talks when someone is attempting to dupe an unwitting audience with seemingly-relevant statistics they don't understand. There's also apparently a thriving market for buying GitHub stars, watchers, forks and followers (just for amusement, the first hit from a quick Web search turns up a service who is willing to sell me stars in bulk at a going rate of us$0.70 each). That aside, the watches and stars on GitHub are social networking constructs which tend to only accrue with the network effect of a large social platform. OpenDev doesn't have much in the way of competing projects you're going to compare "likes" on to determine which one is the most popular, nor would comparing such values against those on another platform like GitHub be meaningful at all since they'd need to be scaled by the relative user-bases of each. > The feature you described below to me, not sure how often people are > using them, but as it's not explicitly visible to observers, it is > difficult to use judge the community fit I think. Correct, they are specifically for streamlining code review workflows, and the only people who are even likely to have accounts to be able to set them are people uploading patches and reviewing changes in OpenDev's Gerrit code review system. I wouldn't expect them to indicate anything aside from maybe habits of the developer and reviewer demographics of a project. -- Jeremy Stanley From build.starlingx at gmail.com Sun Oct 20 02:00:58 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 19 Oct 2019 22:00:58 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 474 - Failure! Message-ID: <469537553.337.1571536859656.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 474 Status: Failure Timestamp: 20191020T015554Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191020T013000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20191020T013000Z DOCKER_BUILD_ID: jenkins-master-20191020T013000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191020T013000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20191020T013000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Sun Oct 20 02:01:01 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 19 Oct 2019 22:01:01 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 287 - Failure! Message-ID: <2006509118.340.1571536862751.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 287 Status: Failure Timestamp: 20191020T013000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191020T013000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false From austin.sun at intel.com Sun Oct 20 02:01:32 2019 From: austin.sun at intel.com (Sun, Austin) Date: Sun, 20 Oct 2019 02:01:32 +0000 Subject: [Starlingx-discuss] Is there any change to get SSH / Ping in VMs ? In-Reply-To: References: Message-ID: Hi Ricardo: I don't think StarlingX change some openstack setting recently. is it enabling DPDK in system ? could you check your duplex controller free memory ? Thanks. BR Austin Sun. From: Perez, Ricardo O Sent: Saturday, October 19, 2019 10:30 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Is there any change to get SSH / Ping in VMs ? Hello Team, Currently I'm trying to launch a Cirros VM to perform the following operations (in a duplex config): * Ping / ssh / scp What I'm seeing is the following: * I have created a security group with the following settings: openstack security group create security1 openstack security group rule create --ingress --protocol icmp --remote-ip 0.0.0.0/0 security1 openstack security group rule create --ingress --protocol tcp --remote-ip 0.0.0.0/0 security1 openstack security group rule create --ingress --protocol udp --remote-ip 0.0.0.0/0 security1 * If I use any flavor with this property: --property hw:mem_page_size=large * I hit an error and the VM isn't launched: controller-0:~# openstack server list +--------------------------------------+-------+--------+----------+--------+---------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+-------+--------+----------+--------+---------+ | 8d22d73b-508c-478b-8d32-b9eb24e1b7a3 | richo | ERROR | | cirros | m1.tiny | +--------------------------------------+-------+--------+----------+--------+---------+ * However, if I use any flavor without the property mem_page_size I get a VM launched, with an IP, but I'm not able to ping it or ssh / scp to it, just login through virsh console. controller-0:~# openstack server list, and there is no IP inside of the VM, please see below: openstack server create --image cirros --flavor m1.tiny --network public-net0 --security-group security1 richo +--------------------------------------+-------+--------+----------------------------+--------+---------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+-------+--------+----------------------------+--------+---------+ | edf0896c-f9e3-4dbf-8a11-f0e5a84d4c02 | richo | ACTIVE | public-net0=192.168.101.49 | cirros | m1.tiny | +--------------------------------------+-------+--------+----------------------------+--------+---------+ controller-0:~# sudo virsh console 1 Connected to domain instance-00000003 Escape character is ^] login as 'cirros' user. default password: 'gocubsgo'. use 'sudo' for root. cirros login: cirros Password: $ ip a 1: lo: mtu 65536 qdisc noqueue qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:ca:a9:db brd ff:ff:ff:ff:ff:ff [ 1256.136730] random: nonblocking pool is initialized inet6 fe80::f816:3eff:feca:a9db/64 scope link valid_lft forever preferred_lft forever $ With the latest changes is there anything that I'm missing to get this working ? even the "ip netns" command isn't giving me any value. Thanks in advance -Ricardo -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Sun Oct 20 02:01:22 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 19 Oct 2019 22:01:22 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 157 - Failure! Message-ID: <1649418860.343.1571536883227.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 157 Status: Failure Timestamp: 20191020T015604Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191020T013000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20191020T013000Z DOCKER_BUILD_ID: jenkins-master-20191020T013000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191020T013000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20191020T013000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos From ildiko at openstack.org Sun Oct 20 21:09:48 2019 From: ildiko at openstack.org (Ildiko Vancsa) Date: Sun, 20 Oct 2019 23:09:48 +0200 Subject: [Starlingx-discuss] Flock Services project PL role elections is now open Message-ID: Poll for the Flock Services project PL role elections is now open and will remain open for you to cast your vote until October 27, 2019, 2045 UTC. We are having elections for the Flock Services project PL position. If you are a Foundation individual member and had a commit in one of the team's deliverable repositories[0] over the last 12 months timeframe (October 6, 2018 to October 6, 2019) or listed as an extra atcs in the projects.yaml[1] file for the project then you are eligible to vote. You should find your email with a link to the Condorcet page to cast your vote in the inbox of your Gerrit preferred email[2]. What to do if you don't see the email and have a commit in at least one of the projects having an election: * check the trash or spam folders of your Gerrit Preferred Email address, in case it went into trash or spam * wait a bit and check again, in case your email server is a bit slow * find the sha of at least one commit from the project's deliverable repos[0] and email the election officials. If we can confirm that you are entitled to vote, we will add you to the voters list for the appropriate election. Our democratic process is important to the health of StarlingX, please exercise your right to vote! Candidate statements/platforms can be here: https://opendev.org/starlingx/election/src/branch/master/candidates/2019_H2/flock-services/pl Happy voting, [0] The list of the repositories eligible for electoral status: https://docs.starlingx.io/governance/reference/tsc/projects/flock-services.html#deliverables [1] https://opendev.org/starlingx/governance/src/branch/master/reference/tsc/projects.yaml [2] Sign into review.openstack.org: Go to Settings > Contact Information. Look at the email listed as your Preferred Email. That is where the ballot has been sent. From build.starlingx at gmail.com Sun Oct 20 23:32:56 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 20 Oct 2019 19:32:56 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 475 - Still Failing! In-Reply-To: <129623137.335.1571536855673.JavaMail.javamailuser@localhost> References: <129623137.335.1571536855673.JavaMail.javamailuser@localhost> Message-ID: <1302095551.346.1571614377473.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 475 Status: Still Failing Timestamp: 20191020T232733Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191020T230000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20191020T230000Z DOCKER_BUILD_ID: jenkins-master-20191020T230000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191020T230000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20191020T230000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Sun Oct 20 23:32:59 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 20 Oct 2019 19:32:59 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 288 - Still Failing! In-Reply-To: <323158634.338.1571536860484.JavaMail.javamailuser@localhost> References: <323158634.338.1571536860484.JavaMail.javamailuser@localhost> Message-ID: <238571778.349.1571614380681.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 288 Status: Still Failing Timestamp: 20191020T230000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191020T230000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false From build.starlingx at gmail.com Sun Oct 20 23:33:20 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 20 Oct 2019 19:33:20 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 158 - Still Failing! In-Reply-To: <170090340.341.1571536880842.JavaMail.javamailuser@localhost> References: <170090340.341.1571536880842.JavaMail.javamailuser@localhost> Message-ID: <1025003907.352.1571614401139.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 158 Status: Still Failing Timestamp: 20191020T232742Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191020T230000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20191020T230000Z DOCKER_BUILD_ID: jenkins-master-20191020T230000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191020T230000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20191020T230000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos From shuicheng.lin at intel.com Mon Oct 21 03:17:06 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Mon, 21 Oct 2019 03:17:06 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EC26ED58D@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C76608D7CA6@SHSMSX105.ccr.corp.intel.com> <2588653EBDFFA34B982FAF00F1B4844EC26ED58D@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C76608D847F@SHSMSX105.ccr.corp.intel.com> Hi Brent, [BR] What is the plan to remove dockerd ? [Shuicheng] We need switch armada to run with containerd first, then we should be able to remove dockerd. Task 37231 is created to track it under the same story[0]. Task 36981 is for switch armada to run with containerd. I prefer to do both task in later stage. [0]: https://storyboard.openstack.org/#!/story/2006145 Best Regards Shuicheng From: Rowsell, Brent Sent: Friday, October 18, 2019 9:20 PM To: Lin, Shuicheng ; Miller, Frank ; starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: RE: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting Thanks. See inline Brent From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, October 17, 2019 9:00 AM To: Miller, Frank >; Rowsell, Brent >; starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: RE: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting Hi Frank & Brent & all, I have updated my patches to remove the visible password for registry. Please help review the update in ansible-playbooks/stx-puppet. Here is the link for the patch list: https://review.opendev.org/#/q/topic:kata+(status:open) - Add a commit to make containerd the default CLI (and remove any docker code that is no longer needed) [shuicheng] do you mean change the "/var/lib/docker" directory to "/var/lib/containerd" for both docker and containerd? If the answer is yes, I prefer to do it later, after docker runtime is not used at all. Currently, armada is still using docker. - Add a test case for local registry pull/push and authentication [BR] What is the plan to remove dockerd ? [Shuicheng] No plan yet. We need switch armada to run with containerd first, then we should be able to remove dockerd. Task 37231 is created to track it under the same story[0]. Task 36981 is for switch armada to run with containerd. [shuicheng] With the new patch, local registry still could be accessed both by Kubernetes and crictl. For crictl, username/password need be provided in CLI, similar to "docker login" for docker CLI. - Update code to ensure admin password is not visible [shuicheng] Done. Best Regards Shuicheng From: Miller, Frank > Sent: Tuesday, October 15, 2019 10:16 PM To: starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting Since we did not get through the whole agenda today, I will schedule the next meeting 1 week from today. Minutes for Oct 15 meeting: 1. Review KATA containers feature with container Cores. Shuicheng to present feature overview and current status. - Shuicheng's commits: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) - Shuicheng presented his feature and what has been done so far (see his charts in separate email) Actions identified: - Concerns: Interaction with registry, admin password is visible - Add a commit to make containerd the default CLI (and remove any docker code that is no longer needed) - Add a test case for local registry pull/push and authentication - Update code to ensure admin password is not visible - Frank to book a follow-up meeting to continue the review (Frank to book Tuesday Oct 22) Frank -----Original Appointment----- From: Miller, Frank Sent: Thursday, October 10, 2019 2:55 PM To: Miller, Frank; starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: StarlingX Bi-Weekly Containerization Meeting When: Tuesday, October 15, 2019 9:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236 Apologies, re-sending without etherpad formatting. Note: We agreed to a new day and time for these meetings. For all who are working containerization features or LPs please join for our bi-weekly meeting. Agenda for October 15 meeting: 1. Review KATA containers feature with container Cores. Shuicheng to present feature overview and current status. - Shuicheng's commits: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) 2. Updates on other stx.3.0 container features for MS3 milestone: - 2004008: [Feature] Create HELM chart for Fault project [An Ran] - one commit needs a new approach - discussed in item #2 - Decision to be made about Horizon issue - do we keep FM containers enabled without Horizon for VM alarms? Or do we disable in stx.3.0 until issue can be addressed in stx.4.0? - 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] - require updated forecast - 2005514: QAT K8S device plugin support in StarlingX - Bruce: Code is out for review; Frank to follow-up with Cindy or feature primes for updated forecasts - 2005860: Upversion container components [Al Bailey] - 2004761: Integrate Backup & Restore with Containers [Ovidiu Poncea] 3. Update on stx.4.0 features: - 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC 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 Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Mon Oct 21 12:40:51 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Mon, 21 Oct 2019 12:40:51 +0000 Subject: [Starlingx-discuss] STX loads between Friday and this morning will likely fail ansible bootstrap Message-ID: A submission was merged on Friday which broke ansible bootstrap in some environments. Any loads with code synchronized since Friday will likely fail with an error during ansible in the "Saving config in sysinv database" phase. The failures are related to retry on failure, so if an environment does not encounter the failure, it will not retry, and may actually work. It has been reverted, here is the revert (which looks like it is merging now) https://review.opendev.org/#/c/689600/ Al -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Oct 21 14:20:16 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 21 Oct 2019 14:20:16 +0000 Subject: [Starlingx-discuss] FW: [Build] Build layering reviews In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D856271BE0@CDSMSX102.ccr.corp.intel.com> References: <58efa3fb-9958-4af1-27f4-21db5a90da19@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F360482ED@SHSMSX104.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D856264A3B@CDSMSX102.ccr.corp.intel.com> <59676767-1870-b9a4-d256-77ff3a4148c8@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856265D08@CDSMSX102.ccr.corp.intel.com> <157958eb-6c13-318c-b087-a3d6b8a68662@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856266584@CDSMSX102.ccr.corp.intel.com> <92bad81a-e05f-6e1d-d83f-71263c01f29f@windriver.com> <56829C2A36C2E542B0CCB9854828E4D85626690A@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D85626EE06@CDSMSX102.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC158F833@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D856271BE0@CDSMSX102.ccr.corp.intel.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D856272C86@CDSMSX102.ccr.corp.intel.com> Hi I have update patch again. Last week, I raise this concern 3, update script download_mirror.sh and generate-cgts-centos-repo Currently all rpm name in lst is listed with fixed rpm version, which makes layer build easily to be corrupted. For example, any time TIS_PATCH_VER in build_srpm.data update, rpm name in lst should be updated. Prefer rpm named with “tis” should be query candidate on cenga, which request download_mirror.sh and generate-cgts-centos-repo update. Prefer we could finish such update in this story, as I think this is a critical issue. So I update patch in stx-tools again to fix this issue. You can check download_mirror.sh I add a step to generate rpm_tis.lst for layer build case. In such case, it will download tis_pkg.lst from cenga. What listed in tis_pkg.lst is distro or compile layer’s built rpm with named xxx.tis.xxx.rpm. So no matter src rpm or tarball upgrade, rpm_centos3party.lst is unnecessary to update. And I update build-iso, image.inc should concatenate with distro and compile layer’s image.in. As image.inc not only for install package, but also request for generate comps.xml. Please check my update and review my patch Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, October 15, 2019 10:27 PM To: Penney, Don ; Bailey, Henry Albert (Al) ; Little, Scott ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] FW: [Build] Build layering reviews Hi I have updated patch for layer build https://review.opendev.org/#/c/681821/ https://review.opendev.org/#/c/681823/ https://review.opendev.org/#/c/681824/ https://review.opendev.org/#/c/681828/ https://review.opendev.org/#/c/681832/ https://review.opendev.org/#/c/681834/ https://review.opendev.org/#/c/681835/ https://review.opendev.org/#/c/681836/ https://review.opendev.org/#/c/681842/ https://review.opendev.org/#/c/681847/ https://review.opendev.org/#/c/681848/ https://review.opendev.org/#/c/681851/ https://review.opendev.org/#/c/681852/ https://review.opendev.org/#/c/681854/ https://review.opendev.org/#/c/681856/ https://review.opendev.org/#/c/681890/ https://review.opendev.org/#/c/681892/ https://review.opendev.org/#/c/681894/ https://review.opendev.org/#/c/681898/ https://review.opendev.org/#/c/681900/ https://review.opendev.org/#/c/681901/ https://review.opendev.org/#/c/681902/ https://review.opendev.org/#/c/681914/ https://review.opendev.org/#/c/688598/ And I think we still left three issue. 1, request build-tools/build_iso/centos_required_build_layer.cfg Current for self validation, we could add a file with such content. But we should create a file depending on cenga update compile,file:///localdisk/loadbuild/martin/starlingx/centos_compile_iso_image.inc distro,file:///localdisk/loadbuild/martin/distro/centos_distro_iso_image.inc flock,file:///localdisk/loadbuild/martin/flock/centos_flock_iso_image.inc 2, propose use one copy of yum.conf.sample and yum.repo.d/* Currently there is 4 copies of yum.conf.sample and yum.repo.d/*. 3 copies in stx-tools/centos-mirror-tools/config/centos// and 1 copy in stx-tools/centos-mirror-tools/ Propose to remove 3 copies in stx-tools/centos-mirror-tools/config/centos//. To avoid user confusing 3, update script download_mirror.sh and generate-cgts-centos-repo Currently all rpm name in lst is listed with fixed rpm version, which makes layer build easily to be corrupted. For example, any time TIS_PATCH_VER in build_srpm.data update, rpm name in lst should be updated. Prefer rpm named with “tis” should be query candidate on cenga, which request download_mirror.sh and generate-cgts-centos-repo update. Prefer we could finish such update in this story, as I think this is a critical issue. Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Penney, Don > Sent: Monday, September 30, 2019 11:33 PM To: Bailey, Henry Albert (Al) >; Chen, Haochuan Z >; Little, Scott >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] FW: [Build] Build layering reviews Is this the issue? openstack/python-horizon/centos/python-django-horizon.spec:BuildRequires: cgts-client I don’t see anything in this package that should need this dependency, and it should be safe to remove it. From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] Sent: Monday, September 30, 2019 10:56 AM To: Chen, Haochuan Z; Little, Scott; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] FW: [Build] Build layering reviews I think Cgts-client (renamed to system-client) should be in its own repo. Al From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Monday, September 30, 2019 2:06 AM To: Little, Scott; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] FW: [Build] Build layering reviews Hi Scott I think have some question or concern. 1, I find distro layer has dependency to cgts-client, as there is a addin for Horizon, which enables look up flock service info in Horizon. So there is task is must for layer building, which is out of my expectation. I begin to tackle these task. • Relocate from git 'config', subdir 'sysinv/cgts-client', to git 'utilities', subdir 'system-client', with full git history. • Rename rpm package from 'cgts-client' to 'system-client' • Fix rpm packages that list cgts-client as a require or build require • Rename python module from 'cgts-client' to 'system-client' • Scan function names and/or variables for any that contain 'cgts' ... replace with 'system' ... can we do this in a backward compatible way? • Fix users of the client to import using the new name, and reference any renamed functions/data. • Fix ISO and/or docker images that list this package for inclusion. 2, “all” layer maybe doesn’t work, warning! For current patch for generate-cgts-centos-repo.sh, all layer’s rpms_lst_file is generated by merge “compiler/distro/flock” three layers, config/centos/all doesn’t be referenced, which is none sense. Which means package such bash-4.2.46-31.el7.tis.4.x86_64.rpm, named with “tis” is also in mirror. This maybe interference source package building. I think request some fix in generate-cgts-centos-repo.sh to omit package with “tis” in name. 3, Layered build introduces rpms_cemtos.lst dependency on TIS_PATCH_VER in build_srpm.data, which make developer easily disrupt layered building mechanism. For distro and flock layer, it has dependency to starlingX customized package, for example, distro layer require bash.tis...rpm, which will be add in config/centos/distro/rpms_centos3rdparty.lst If new developer forget to update and build all package, it maybe disrupt layered building. BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Friday, September 27, 2019 4:40 PM To: Scott Little >; starlingx-discuss at lists.starlingx.io Subject: RE: FW: [Starlingx-discuss] [Build] Build layering reviews Thanks, Scott. I have studied so much. BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Scott Little > Sent: Thursday, September 26, 2019 11:39 PM To: Chen, Haochuan Z >; starlingx-discuss at lists.starlingx.io Subject: Re: FW: [Starlingx-discuss] [Build] Build layering reviews Returning this discussion to the mailing list. If possible, join the Build call next week. https://wiki.openstack.org/wiki/Starlingx/Meetings 1) When mock installs for the first time. it uses rpms that have been download via lst file. The mock pseudo-layer lst files capture reflect the rpms needed by mock. The mock lst's are merged with the layers lst's. In this way, the mock rpms don't have to be listed in each and every layer's lst. 2) Adding tools to generate an lst file reflacting the output of a build layer, and adding that lst for consumprion by higher layers, is indeed a possibility possibility I wanted to persue. Reference to that output lst could then be added to as a new arg to the download script when invoked by a higher layer, or a config file could specify where to find it (cengn is the likely default supplier). compile layer) The compile layer is a true layer, built prior to the distro layer. Only a few build related packages go here. Compilers, language interpreters, rpm. I wanted those packages in place so that all distro layer packages build with the same tools. Scott On 2019-09-25 10:24 p.m., Chen, Haochuan Z wrote: Still not clear about mock layer. 1, In build container, mock is already installed, why request to download mock required package firstly? 2, To build distro or flock layer, we could add compile layer’s tis rpm in distro and flock layer’s lst file. By download compile layer’s binary in mirror, it could also ensure user building package with same tool. Why introduces compile layer? Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Scott Little Sent: Thursday, September 26, 2019 12:25 AM To: Chen, Haochuan Z Subject: Re: FW: [Starlingx-discuss] [Build] Build layering reviews See inline ... Scott On 2019-09-23 11:00 a.m., Chen, Haochuan Z wrote: Hi Scott I studied your patch and some questions. 1, why there is mock and compile layer, what's usage or intention for these two layers? Build-pkgs uses a tool called mock to create a reproducible compilation sandbox. It is chroot like environmnet into which rpms are installed to construct a minimal build environment. The mock layer is not built. I created it as a placeholder for the lst files that downloads all the rpms that mock requires. Prior to building a layer, the lst files for both the layer being build, and the mock pseudo layer, need to be processed. Without the mock pseudo layer, we would have to replicate that list of mock required rpms in each and ever layer's lst files. The concept ran into a bit of trouble because some of the rpms needed by mock are themselves built by the compile or distro layers (with a newer revision). So the mock pseudo layer might actually omit those rpms from it's lst file, and they needed to be listed in the layer lst files instead. The compile layer is a true layer, built prior to the distro layer. Only a few build related packages go here. Compilers, language interpreters, rpm. I wanted those packages in place so that all distro layer packages build with the same tools. 2, for download_mirror.sh, it generate rpm list by merge file in config/centos// and rpm list file in stx/ But for generate-cgcs-centos-repo.sh, it use rpm list file in centos-mirror-tools folder. Rpm package should be added in two rpm list file. It is not good for maintenance. What about remove rpm list file in centos-mirror-tools folder rpms_centos.lst/rpms_centos3rdparties.lst/rpms_3rdparties.lst/other_downloads.lst/ tarball-dl.lst That was considered and debated. The concern was that the many git repos that make up the layer would list different versions of the same package. Then what do we do? Throw an error? Silently use the newest package? So we elected to keep binary rpms needed to satisfy dependencies listed in a central place. At some point we may want to explore allowing lst files specify required package but not version (beyond a possible minimum version) when on the master branch, and have a way to 'lock down' the versions only for a release branch. 3, Question about setup yum repo for rpm tailing with “tis” such as xxx.tis.x86_64.rpm or xxx.tis.noarch.rpm In this patch https://review.opendev.org/#/c/681821/1 There is such line in config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo [Starlingx-cengn_distro_layer] name=Starlingx-cengn_distro_layer baseurl=http://127.0.0.1:8088/localdisk/loadbuild/slittle1/restructure3b/std/rpmbuild/RPMS/ enabled=1 [Starlingx-cengn_distro_layer-rt] name=Starlingx-cengn_distro_layer baseurl=http://127.0.0.1:8088/localdisk/loadbuild/slittle1/restructure3b/rt/rpmbuild/RPMS/ enabled=1 also in config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo My understanding is rpm tailing with “tis” should also upload to cengn, rpm name listed in centos-mirror-tools/config/centos/flock/rpms_centos3rdparties.lst So these three files should be unnecessary, with cengn update for layered build. config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo For development testing, I had to hack together a simulated cengn by running lighttpd on 127.0.0.1:8088 and allowing it to serve up files from builds of lower layers restructure3a == layer-comiler layer build restructure3b == layer-distro layer build restructure3c == layer-flock layer build (although there shouldn't be a repo entry referring to that one) Finalizing the repo entries would have to wait until cengn was up an running. 4, In generate-cgcs-centos-repo.sh there is --layer-dir, and such content in your patch commit message generate-cgcs-centos-repo.sh \ --layer-dir=/localdisk/loadbuild/slittle1/layer-compile/std/rpmbuild/RPMS/ \ --layer-dir=/localdisk/loadbuild/slittle1/layer-distro/std/rpmbuild/RPMS/ \ --layer-dir=/localdisk/loadbuild/slittle1/layer-distro/rt/rpmbuild/RPMS/ \ /import/mirrors/starlingx For all rpm download from cengn, --layer-dir is unnecessary to generate link, correct? This is another way to do cross layer development testing without support from cengn. Again the goal is to allow an upper layer build to download rpms from a lower layer build on the same machine. 5, could you share build-tools/build-iso/centos_required_build_layer.cfg, share to me Did that not get published in my reviews? Content is very simple. compile,file:///localdisk/loadbuild/slittle1/restructure3a/centos_compile_iso_image.inc distro,file:///localdisk/loadbuild/slittle1/restructure3b/centos_distro_iso_image.inc flock,file:///localdisk/loadbuild/slittle1/restructure3c/centos_flock_iso_image.inc 6, For distro/compiler/flock, all are separate layer? Yes My current step repo init -u https://opendev.org/starlingx/manifest.git apply this patch to .repo/manifests https://review.opendev.org/#/c/681914/1 repo init -m compile.xml repo sync apply these to patch https://review.opendev.org/#/c/681821/1 https://review.opendev.org/#/c/681828/1 ./download_mirror.sh -n -g -l flock -c config/centos/compiler/yum.conf.sample -S ./toCopy/generate-cgts-centos-repo output/stx-r1/CentOS/pike/ build-pkgs build-iso BR! Martin, Chen SSP, Software Engineer 021-61164330 -----Original Message----- From: Scott Little Sent: Thursday, September 19, 2019 9:54 PM To: Chen, Haochuan Z Subject: Re: FW: [Starlingx-discuss] [Build] Build layering reviews Most of the required changes were already merged. I'll scan the spec when time permits to see if I missed anything. Scott On 2019-09-16 12:01 p.m., Chen, Haochuan Z wrote: > Hi Scott > > I read your patch for build layering, but could not find patch for build script. > > Description in spec https://review.opendev.org/#/c/672288/12/ > Modifications to package build scripts ... build-pkgs, > build-srpms-parallel, build-srpms-serial, build-rpms-parallel, build-rpms-serial (cgcs-root): > > Thanks > > Martin, Chen > SSP, Software Engineer > 021-61164330 > > -----Original Message----- > From: Xie, Cindy > Sent: Friday, September 13, 2019 12:24 PM > To: Chen, Haochuan Z > > Cc: Hu, Yong > > Subject: FW: [Starlingx-discuss] [Build] Build layering reviews > > Martin, > I am wondering if you will be interested to working on this task. To me, having layering build and provide efficiency to developers are very important for StarlingX. It also provide a chance that you and work together w/ WR folks being more close collaboration. Let me know your interested level. > > Thx. -cindy > > -----Original Message----- > From: Scott Little > > Sent: Friday, September 13, 2019 4:55 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [Build] Build layering reviews > > My prototype code for the layered build has been posted to gerrit. > (listed below) > > I was briefly able to build all layers, and produce an iso with the same package content as the cengn build. Then I was diverted by non-trivial changes to the restructuring work. What I have posted is now several weeks out of date and will almost certainly will not work. The devil is in keeping the lst files in sync with the ever changing master branch. > > Other commitments will prevent me from resuming this work until November. If anyone wants to whip the lst files into shape and try to get the build working again, be my guest. > > Final delivery will require changes to the CENGN build scripts (Don or Myself), and a freeze on packaging changes will likely be required for aprox 3 days to finalize the lst files. > > Scott > > ---------------- ---------------- > > https://review.opendev.org/#/c/681821/1 > > https://review.opendev.org/#/c/681914/1 > > https://review.opendev.org/#/c/681823/1 > > https://review.opendev.org/#/c/681824/1 > > https://review.opendev.org/#/c/681828/1 > > https://review.opendev.org/#/c/681832/2 > > https://review.opendev.org/#/c/681834/1 > > https://review.opendev.org/#/c/681836/1 > > https://review.opendev.org/#/c/681835/1 > > https://review.opendev.org/#/c/681842/1 > > https://review.opendev.org/#/c/681847/1 > > https://review.opendev.org/#/c/681848/1 > > https://review.opendev.org/#/c/681851/1 > > https://review.opendev.org/#/c/681852/1 > > https://review.opendev.org/#/c/681854/1 > > https://review.opendev.org/#/c/681856/1 > > https://review.opendev.org/#/c/681890/1 > > https://review.opendev.org/#/c/681892/1 > > https://review.opendev.org/#/c/681892/1 > > https://review.opendev.org/#/c/681898/1 > > https://review.opendev.org/#/c/681900/1 > > https://review.opendev.org/#/c/681901/1 > > https://review.opendev.org/#/c/681902/1 > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon Oct 21 14:27:02 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 21 Oct 2019 10:27:02 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup - Build # 501 - Failure! Message-ID: <1993829618.355.1571668023754.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup Build #: 501 Status: Failure Timestamp: 20191021T140855Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191021T140817Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20191021T140817Z DOCKER_BUILD_ID: jenkins-master-20191021T140817Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191021T140817Z/logs DOCKER_BUILD_TAG: master-20191021T140817Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20191021T140817Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Mon Oct 21 14:27:06 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 21 Oct 2019 10:27:06 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 289 - Still Failing! In-Reply-To: <161589547.347.1571614378281.JavaMail.javamailuser@localhost> References: <161589547.347.1571614378281.JavaMail.javamailuser@localhost> Message-ID: <805320431.358.1571668027046.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 289 Status: Still Failing Timestamp: 20191021T140817Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191021T140817Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true From build.starlingx at gmail.com Mon Oct 21 14:47:46 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 21 Oct 2019 10:47:46 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup - Build # 502 - Still Failing! In-Reply-To: <1702097585.353.1571668020762.JavaMail.javamailuser@localhost> References: <1702097585.353.1571668020762.JavaMail.javamailuser@localhost> Message-ID: <143511813.361.1571669267485.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup Build #: 502 Status: Still Failing Timestamp: 20191021T143006Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191021T142954Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20191021T142954Z DOCKER_BUILD_ID: jenkins-master-20191021T142954Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191021T142954Z/logs DOCKER_BUILD_TAG: master-20191021T142954Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20191021T142954Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Mon Oct 21 14:47:49 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 21 Oct 2019 10:47:49 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 290 - Still Failing! In-Reply-To: <1381889799.356.1571668024604.JavaMail.javamailuser@localhost> References: <1381889799.356.1571668024604.JavaMail.javamailuser@localhost> Message-ID: <424361921.364.1571669270589.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 290 Status: Still Failing Timestamp: 20191021T142954Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191021T142954Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true From Don.Penney at windriver.com Mon Oct 21 14:57:54 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 21 Oct 2019 14:57:54 +0000 Subject: [Starlingx-discuss] CENGN Build failures caused by new mock version 1.4.20 Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC159A01C@ALA-MBD.corp.ad.wrs.com> Hi folks, A new version of mock, 1.4.20, was recently released, and is getting picked up by the build container setup: https://opendev.org/starlingx/tools/src/branch/master/Dockerfile#L71 Unfortunately, our build tools are using a deprecated tool mockchain, which has now been dropped in this new mock-1.4.20, replaced with 'mock --chain'. This is causing the CENGN builds to fail. As a workaround, I'm trying to force the CENGN build to use mock-1.4.19. If this is successful, we could update the Dockerfile with this short-term workaround to unblock developers using a build container. The long-term solution, of course, would be to update the build tools to use 'mock --chain'. Cheers, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Mon Oct 21 17:24:03 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 21 Oct 2019 17:24:03 +0000 Subject: [Starlingx-discuss] Distro.openstack Oct 22 meeting Agenda Message-ID: <9A85D2917C58154C960D95352B22818BDFBFAB80@fmsmsx123.amr.corp.intel.com> * Update on upgrade to Train * Need a volunteer for a small change to the governance repo * Defect review https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack -------------- next part -------------- An HTML attachment was scrubbed... URL: From abraham.arce.moreno at intel.com Mon Oct 21 17:25:00 2019 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Mon, 21 Oct 2019 17:25:00 +0000 Subject: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Message-ID: > Please add Distributed Cloud Configuration Guide to StarlingX R3.0 > Installation. Hi Tao, Distributed Cloud team, Here you have an early review of Distributed Cloud: https://review.opendev.org/#/c/689847/ We will take it as our base documentation and do the installation in our labs starting today, some changes likely coming. For now, please let us know if we need to add more people as Co-Authored-By. From Don.Penney at windriver.com Mon Oct 21 19:07:57 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 21 Oct 2019 19:07:57 +0000 Subject: [Starlingx-discuss] CENGN Build failures caused by new mock version 1.4.20 In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC159A01C@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC159A01C@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC159A151@ALA-MBD.corp.ad.wrs.com> Review is posted for a build tool update to adapt to mock-1.4.20: https://review.opendev.org/689850 https://launchpad.net/bugs/1849147 From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Monday, October 21, 2019 10:58 AM To: 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: [Starlingx-discuss] CENGN Build failures caused by new mock version 1.4.20 Hi folks, A new version of mock, 1.4.20, was recently released, and is getting picked up by the build container setup: https://opendev.org/starlingx/tools/src/branch/master/Dockerfile#L71 Unfortunately, our build tools are using a deprecated tool mockchain, which has now been dropped in this new mock-1.4.20, replaced with 'mock --chain'. This is causing the CENGN builds to fail. As a workaround, I'm trying to force the CENGN build to use mock-1.4.19. If this is successful, we could update the Dockerfile with this short-term workaround to unblock developers using a build container. The long-term solution, of course, would be to update the build tools to use 'mock --chain'. Cheers, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Mon Oct 21 19:55:47 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 21 Oct 2019 19:55:47 +0000 Subject: [Starlingx-discuss] CENGN Build failures caused by new mock version 1.4.20 In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC159A151@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC159A01C@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC159A151@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC159A1F9@ALA-MBD.corp.ad.wrs.com> Thanks for the reviews... The update has merged. The following review is the cherry-pick to r/stx.2.0: https://review.opendev.org/689869 From: Penney, Don Sent: Monday, October 21, 2019 3:08 PM To: Penney, Don; 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: RE: [Starlingx-discuss] CENGN Build failures caused by new mock version 1.4.20 Review is posted for a build tool update to adapt to mock-1.4.20: https://review.opendev.org/689850 https://launchpad.net/bugs/1849147 From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Monday, October 21, 2019 10:58 AM To: 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: [Starlingx-discuss] CENGN Build failures caused by new mock version 1.4.20 Hi folks, A new version of mock, 1.4.20, was recently released, and is getting picked up by the build container setup: https://opendev.org/starlingx/tools/src/branch/master/Dockerfile#L71 Unfortunately, our build tools are using a deprecated tool mockchain, which has now been dropped in this new mock-1.4.20, replaced with 'mock --chain'. This is causing the CENGN builds to fail. As a workaround, I'm trying to force the CENGN build to use mock-1.4.19. If this is successful, we could update the Dockerfile with this short-term workaround to unblock developers using a build container. The long-term solution, of course, would be to update the build tools to use 'mock --chain'. Cheers, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Mon Oct 21 23:32:24 2019 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 21 Oct 2019 16:32:24 -0700 Subject: [Starlingx-discuss] FW: [Build] Build layering reviews In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D856272C86@CDSMSX102.ccr.corp.intel.com> References: <58efa3fb-9958-4af1-27f4-21db5a90da19@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F360482ED@SHSMSX104.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D856264A3B@CDSMSX102.ccr.corp.intel.com> <59676767-1870-b9a4-d256-77ff3a4148c8@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856265D08@CDSMSX102.ccr.corp.intel.com> <157958eb-6c13-318c-b087-a3d6b8a68662@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856266584@CDSMSX102.ccr.corp.intel.com> <92bad81a-e05f-6e1d-d83f-71263c01f29f@windriver.com> <56829C2A36C2E542B0CCB9854828E4D85626690A@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D85626EE06@CDSMSX102.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC158F833@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D856271BE0@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D856272C86@CDSMSX102.ccr.corp.intel.com> Message-ID: <1d6bf23c-0eaa-56dc-8154-bfb39a3be25e@linux.intel.com> Martin, I am still wondering how your testing this, if you have a completely updated manifest that points to all the updated gerrit reviews? As I mentioned in some reviews earlier I was having issues with building due to missing files. On 10/21/19 7:20 AM, Chen, Haochuan Z wrote: > Hi > > I have update patch again. Last week, I raise this concern// > > 3, update script download_mirror.sh and generate-cgts-centos-repo > > Currently all rpm name in lst is listed with fixed rpm version, which > makes layer build easily to be corrupted. For example, any time > TIS_PATCH_VER in build_srpm.data update, rpm name in lst should be updated. > > Prefer rpm named with “tis” should be query candidate on cenga, which > request download_mirror.sh and generate-cgts-centos-repo update. Prefer > we could finish such update in this story, as I think this is a critical > issue. > > So I update patch in stx-tools again to fix this issue. You can check > download_mirror.sh > > I add a step to generate rpm_tis.lst for layer build case. In such case, > it will download tis_pkg.lst from cenga. What listed in tis_pkg.lst is > distro or compile layer’s built rpm with named xxx.tis.xxx.rpm. > > So no matter src rpm or tarball upgrade, rpm_centos3party.lst is > unnecessary to update. > > And I update build-iso, image.inc should concatenate with distro and > compile layer’s image.in. As image.inc not only for install package, but > also request for generate comps.xml. > > Please check my update and review my patch > I am looking at this patch and doing some testing. Sau! > Thanks! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > *From:*Chen, Haochuan Z > *Sent:* Tuesday, October 15, 2019 10:27 PM > *To:* Penney, Don ; Bailey, Henry Albert (Al) > ; Little, Scott ; > 'starlingx-discuss at lists.starlingx.io' > > *Subject:* RE: [Starlingx-discuss] FW: [Build] Build layering reviews > > Hi > > I have updated patch for layer build > > https://review.opendev.org/#/c/681821/ > > https://review.opendev.org/#/c/681823/ > > https://review.opendev.org/#/c/681824/ > > https://review.opendev.org/#/c/681828/ > > https://review.opendev.org/#/c/681832/ > > https://review.opendev.org/#/c/681834/ > > https://review.opendev.org/#/c/681835/ > > https://review.opendev.org/#/c/681836/ > > https://review.opendev.org/#/c/681842/ > > https://review.opendev.org/#/c/681847/ > > https://review.opendev.org/#/c/681848/ > > https://review.opendev.org/#/c/681851/ > > https://review.opendev.org/#/c/681852/ > > https://review.opendev.org/#/c/681854/ > > https://review.opendev.org/#/c/681856/ > > https://review.opendev.org/#/c/681890/ > > https://review.opendev.org/#/c/681892/ > > https://review.opendev.org/#/c/681894/ > > https://review.opendev.org/#/c/681898/ > > https://review.opendev.org/#/c/681900/ > > https://review.opendev.org/#/c/681901/ > > https://review.opendev.org/#/c/681902/ > > https://review.opendev.org/#/c/681914/ > > https://review.opendev.org/#/c/688598/ > > And I think we still left three issue. > > 1, request build-tools/build_iso/centos_required_build_layer.cfg > > Current for self validation, we could add a file with such content. But > we should create a file depending on cenga update > > compile,file:///localdisk/loadbuild/martin/starlingx/centos_compile_iso_image.inc > > distro,file:///localdisk/loadbuild/martin/distro/centos_distro_iso_image.inc > > flock,file:///localdisk/loadbuild/martin/flock/centos_flock_iso_image.inc > > 2, propose use one copy of yum.conf.sample and yum.repo.d/* > > Currently there is 4 copies of yum.conf.sample and yum.repo.d/*.  3 > copies in stx-tools/centos-mirror-tools/config/centos// and 1 > copy in stx-tools/centos-mirror-tools/ > >   Propose to remove 3 copies in > stx-tools/centos-mirror-tools/config/centos//. To avoid user > confusing > > 3, update script download_mirror.sh and generate-cgts-centos-repo > > Currently all rpm name in lst is listed with fixed rpm version, which > makes layer build easily to be corrupted. For example, any time > TIS_PATCH_VER in build_srpm.data update, rpm name in lst should be updated. > > Prefer rpm named with “tis” should be query candidate on cenga, which > request download_mirror.sh and generate-cgts-centos-repo update. Prefer > we could finish such update in this story, as I think this is a critical > issue. > > Thanks! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > *From:*Penney, Don > > *Sent:* Monday, September 30, 2019 11:33 PM > *To:* Bailey, Henry Albert (Al) >; Chen, Haochuan Z > >; Little, > Scott >; > 'starlingx-discuss at lists.starlingx.io' > > > *Subject:* RE: [Starlingx-discuss] FW: [Build] Build layering reviews > > Is this the issue? > > openstack/python-horizon/centos/python-django-horizon.spec:BuildRequires: cgts-client > > I don’t see anything in this package that should need this dependency, > and it should be safe to remove it. > > *From:*Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] > *Sent:* Monday, September 30, 2019 10:56 AM > *To:* Chen, Haochuan Z; Little, Scott; > 'starlingx-discuss at lists.starlingx.io' > *Subject:* Re: [Starlingx-discuss] FW: [Build] Build layering reviews > > I think Cgts-client  (renamed to system-client)  should be in its own repo. > > Al > > *From:*Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] > *Sent:* Monday, September 30, 2019 2:06 AM > *To:* Little, Scott; 'starlingx-discuss at lists.starlingx.io' > *Subject:* Re: [Starlingx-discuss] FW: [Build] Build layering reviews > > Hi Scott > > I think have some question or concern. > > 1, I find distro layer has dependency to cgts-client, as there is a > addin for Horizon, which enables look up flock service info in Horizon. > > So there is task is must for layer building, which is out of my > expectation.  I begin to tackle these task. > > ·Relocate from git 'config', subdir 'sysinv/cgts-client', to git > 'utilities', subdir 'system-client', *with full git history.* > > ·Rename rpm package from 'cgts-client' to 'system-client' > > ·Fix rpm packages that list cgts-client as a require or build require > > ·Rename python module from 'cgts-client' to 'system-client' > > ·Scan function names and/or variables for any that contain 'cgts' ... > replace with 'system' ... can we do this in a backward compatible way? > > ·Fix users of the client to import using the new name, and reference any > renamed functions/data. > > ·Fix ISO and/or docker images that list this package for inclusion. > > 2, “all” layer maybe doesn’t work, warning! > > For current patch for generate-cgts-centos-repo.sh, all layer’s > rpms_lst_file is generated by merge “compiler/distro/flock” three > layers, config/centos/all doesn’t be referenced, which is none sense. > Which means package such bash-4.2.46-31.el7.tis.4.x86_64.rpm, named with > “tis” is also in mirror. This maybe interference source package > building. I think request some fix in generate-cgts-centos-repo.sh to > omit package with “tis” in name. > > 3, Layered build introduces rpms_cemtos.lst dependency on TIS_PATCH_VER > in build_srpm.data, which make developer easily disrupt layered building > mechanism. > > For distro and flock layer, it has dependency to starlingX customized > package, for example, distro layer require bash.tis. version>..rpm, which will be add in > config/centos/distro/rpms_centos3rdparty.lst > > If new developer forget to update and build all package, it maybe > disrupt layered building. > > BR! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > *From:*Chen, Haochuan Z > *Sent:* Friday, September 27, 2019 4:40 PM > *To:* Scott Little >; > starlingx-discuss at lists.starlingx.io > > *Subject:* RE: FW: [Starlingx-discuss] [Build] Build layering reviews > > Thanks, Scott. I have studied so much. > > BR! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > *From:*Scott Little > > *Sent:* Thursday, September 26, 2019 11:39 PM > *To:* Chen, Haochuan Z >; > starlingx-discuss at lists.starlingx.io > > *Subject:* Re: FW: [Starlingx-discuss] [Build] Build layering reviews > > Returning this discussion to the mailing list. > > If possible, join the Build call next week. > https://wiki.openstack.org/wiki/Starlingx/Meetings > > 1) > > When mock installs for the first time. it uses rpms that have been > download via lst file. The mock pseudo-layer lst files capture reflect > the rpms needed by mock.  The mock lst's are merged with the layers > lst's.  In this way, the mock rpms don't have to be listed in each and > every layer's lst. > > 2) > > Adding tools to generate an lst file reflacting the output of a build > layer, and adding that lst for consumprion by higher layers, is indeed a > possibility possibility I wanted to persue.  Reference to that output > lst could then be added to as a new arg to the download script when > invoked by a higher layer, or a config file could specify where to find > it (cengn is the likely default supplier). > > compile layer) > > The compile layer is a true layer, built prior to the distro layer. > Only a few build related packages go here.  Compilers, language > interpreters, rpm.  I wanted those packages in place so that all distro > layer packages build with the same tools. > > Scott > > On 2019-09-25 10:24 p.m., Chen, Haochuan Z wrote: > > Still not clear about mock layer. > > 1, In build container, mock is already installed, why request to > download mock required package firstly? > > 2, To build distro or flock layer, we could add compile layer’s tis > rpm in distro and flock layer’s lst file. By download compile > layer’s binary in mirror, it could also ensure user building package > with same tool. > > Why introduces compile layer? > > Thanks! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > *From:*Scott Little > > *Sent:* Thursday, September 26, 2019 12:25 AM > *To:* Chen, Haochuan Z > > *Subject:* Re: FW: [Starlingx-discuss] [Build] Build layering reviews > > See inline ... > > Scott > > On 2019-09-23 11:00 a.m., Chen, Haochuan Z wrote: > > Hi Scott > > I studied your patch and some questions. > > 1, why there is mock and compile layer, what's usage or > intention for these two layers? > > Build-pkgs uses a tool called mock to create a reproducible > compilation sandbox.  It is chroot like environmnet into which rpms > are installed to construct a minimal build environment. > > The mock layer is not built.  I created it as a placeholder for the > lst files that downloads all the rpms that mock requires.  Prior to > building a layer, the lst files for both the layer being build, and > the mock pseudo layer, need to be processed. Without the mock pseudo > layer, we would have to replicate that list of mock required rpms in > each and ever layer's lst files. > > The concept ran into a bit of trouble because some of the rpms > needed by mock are themselves built by the compile or distro layers > (with a newer revision).   So the > mock pseudo layer might actually omit those rpms from it's lst file, > and they needed to be listed in the layer lst files instead. > > The compile layer is a true layer, built prior to the distro layer. > Only a few build related packages go here.  Compilers, language > interpreters, rpm.  I wanted those packages in place so that all > distro layer packages build with the same tools. > > 2, for download_mirror.sh, it generate rpm list by merge file in > config/centos// and rpm list file in > stx/ > >    But for generate-cgcs-centos-repo.sh, it use rpm list file > in centos-mirror-tools folder. Rpm package should be added in > two rpm list file. > >    It is not good for maintenance. What about remove rpm list > file in centos-mirror-tools folder > > /rpms_centos.lst/rpms_centos3rdparties.lst/rpms_3rdparties.lst/other_downloads.lst/ > tarball-dl.lst/ > > That was considered and debated. The concern was that the many git > repos that make up the layer would list different versions of the > same package.  Then what do we do?  Throw an error?  Silently use > the newest package?  So we elected to keep binary rpms needed to > satisfy dependencies listed in a central place. > > At some point we may want to explore allowing lst files specify > required package but not version (beyond a possible minimum version) > when on the master branch, and have a way to 'lock down' the > versions only for a release branch. > > 3, Question about setup yum repo for rpm tailing with “tis” such > as xxx.*tis*.x86_64.rpm or xxx.*tis*.noarch.rpm > > In this patch https://review.opendev.org/#/c/681821/1 > > /There is such line in > config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo/ > > /[Starlingx-cengn_distro_layer]/ > > /name=Starlingx-cengn_distro_layer/ > > /baseurl=http://127.0.0.1:8088/localdisk/loadbuild//*/slittle1/restructure3b/*//std/rpmbuild/RPMS// > > /enabled=1/ > > /[Starlingx-cengn_distro_layer-rt]/ > > /name=Starlingx-cengn_distro_layer/ > > /baseurl=http://127.0.0.1:8088/localdisk/loadbuild//*/slittle1/restructure3b/*//rt/rpmbuild/RPMS// > > /enabled=1/ > > also in > > config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo > > config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo > > My understanding is rpm tailing with “tis” should also upload to > cengn, rpm name listed in > centos-mirror-tools/config/centos/flock/rpms_centos3rdparties.lst > > So these three files should be unnecessary, with cengn update > for layered build. > > config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo > > config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo > > config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo > > For development testing, I had to hack together a simulated cengn by > running lighttpd on 127.0.0.1:8088 and allowing it to serve up files > from builds of lower layers > > restructure3a == layer-comiler layer build > > restructure3b == layer-distro layer build > > restructure3c == layer-flock layer build  (although there shouldn't > be a repo entry referring to that one) > > Finalizing the repo entries would have to wait until cengn was up an > running. > > 4, In generate-cgcs-centos-repo.sh there is --layer-dir, and > such content in your patch commit message > > /generate-cgcs-centos-repo.sh \/ > > /--layer-dir=/localdisk/loadbuild/slittle1/layer-compile/std/rpmbuild/RPMS/ > \/ > > /--layer-dir=/localdisk/loadbuild/slittle1/layer-distro/std/rpmbuild/RPMS/ > \/ > > /--layer-dir=/localdisk/loadbuild/slittle1/layer-distro/rt/rpmbuild/RPMS/ > \/ > > //import/mirrors/starlingx/ > >    For all rpm download from cengn, --layer-dir is unnecessary > to generate link, correct? > > This is another way to do cross layer development testing without > support from cengn.  Again the goal is to allow an upper layer build > to download rpms from a lower layer build on the same machine. > > 5, could you share > build-tools/build-iso/centos_required_build_layer.cfg, share to me > > Did that not get published in my reviews?  Content is very simple. > > compile,file:///localdisk/loadbuild/slittle1/restructure3a/centos_compile_iso_image.inc > > distro,file:///localdisk/loadbuild/slittle1/restructure3b/centos_distro_iso_image.inc > > flock,file:///localdisk/loadbuild/slittle1/restructure3c/centos_flock_iso_image.inc > > > 6, For distro/compiler/flock, all are separate layer? > > Yes > > My current step > > /repo init -u https://opendev.org/starlingx/manifest.git/ > > /apply this patch to .repo/manifests/ > > /https://review.opendev.org/#/c/681914/1/ > > /repo init -m compile.xml/ > > /repo sync/ > > /apply these to patch/ > > /https://review.opendev.org/#/c/681821/1/ > > /https://review.opendev.org/#/c/681828/1/ > > /./download_mirror.sh  -n -g -l flock -c > config/centos/compiler/yum.conf.sample -S / > > /./toCopy/generate-cgts-centos-repo output/stx-r1/CentOS/pike// > > /build-pkgs/ > > /build-iso/ > > BR! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > -----Original Message----- > From: Scott Little > > Sent: Thursday, September 19, 2019 9:54 PM > To: Chen, Haochuan Z > > Subject: Re: FW: [Starlingx-discuss] [Build] Build layering reviews > > Most of the required changes were already merged. > > I'll scan the spec when time permits to see if I missed anything. > > Scott > > On 2019-09-16 12:01 p.m., Chen, Haochuan Z wrote: > > > Hi Scott > > > > > > I read your patch for build layering, but could not find > patch for build script. > > > > > > Description in spec https://review.opendev.org/#/c/672288/12/ > > > Modifications to package build scripts ... build-pkgs, > > > build-srpms-parallel, build-srpms-serial, > build-rpms-parallel, build-rpms-serial (cgcs-root): > > > > > > Thanks > > > > > > Martin, Chen > > > SSP, Software Engineer > > > 021-61164330 > > > > > > -----Original Message----- > > > From: Xie, Cindy > > > Sent: Friday, September 13, 2019 12:24 PM > > > To: Chen, Haochuan Z > > > > Cc: Hu, Yong > > > > Subject: FW: [Starlingx-discuss] [Build] Build layering reviews > > > > > > Martin, > > > I am wondering if you will be interested to working on this > task. To me, having layering build and provide efficiency to > developers are very important for StarlingX. It also provide a > chance that you and work together w/ WR folks being more close > collaboration. Let me know your interested level. > > > > > > Thx. -cindy > > > > > > -----Original Message----- > > > From: Scott Little > > > > Sent: Friday, September 13, 2019 4:55 AM > > > To: starlingx-discuss at lists.starlingx.io > > > > Subject: [Starlingx-discuss] [Build] Build layering reviews > > > > > > My prototype code for the layered build has been posted to > gerrit. > > > (listed below) > > > > > > I was briefly able to build all layers, and produce an iso > with the same package content as the cengn build.  Then I was > diverted by non-trivial changes to the restructuring work. What > I have posted is now several weeks out of date and will almost > certainly will not work.  The devil is in keeping the lst files > in sync with the ever changing master branch. > > > > > > Other commitments will prevent me from resuming this work > until November.  If anyone wants to whip the lst files into > shape and try to get the build working again, be my guest. > > > > > > Final delivery will require changes to the CENGN build > scripts (Don or Myself), and a freeze on packaging changes will > likely be required for aprox 3 days to finalize the lst files. > > > > > > Scott > > > > > > ---------------- ---------------- > > > > > > https://review.opendev.org/#/c/681821/1 > > > > > > https://review.opendev.org/#/c/681914/1 > > > > > > https://review.opendev.org/#/c/681823/1 > > > > > > https://review.opendev.org/#/c/681824/1 > > > > > > https://review.opendev.org/#/c/681828/1 > > > > > > https://review.opendev.org/#/c/681832/2 > > > > > > https://review.opendev.org/#/c/681834/1 > > > > > > https://review.opendev.org/#/c/681836/1 > > > > > > https://review.opendev.org/#/c/681835/1 > > > > > > https://review.opendev.org/#/c/681842/1 > > > > > > https://review.opendev.org/#/c/681847/1 > > > > > > https://review.opendev.org/#/c/681848/1 > > > > > > https://review.opendev.org/#/c/681851/1 > > > > > > https://review.opendev.org/#/c/681852/1 > > > > > > https://review.opendev.org/#/c/681854/1 > > > > > > https://review.opendev.org/#/c/681856/1 > > > > > > https://review.opendev.org/#/c/681890/1 > > > > > > https://review.opendev.org/#/c/681892/1 > > > > > > https://review.opendev.org/#/c/681892/1 > > > > > > https://review.opendev.org/#/c/681898/1 > > > > > > https://review.opendev.org/#/c/681900/1 > > > > > > https://review.opendev.org/#/c/681901/1 > > > > > > https://review.opendev.org/#/c/681902/1 > > > > > > > > > > > > > > > _______________________________________________ > > > 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 ada.cabrales at intel.com Tue Oct 22 00:58:22 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 22 Oct 2019 00:58:22 +0000 Subject: [Starlingx-discuss] [ Test ] meeting agenda for 10/22 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CEFCF32@FMSMSX114.amr.corp.intel.com> Agenda for 10/22 1. Sanity status Unified sanity On track for 10/28? 2. stx.3.0 testing updates Feature testing Tracker - https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit?usp=sharing Distributed cloud - Yang Backup and restore - Yang Fault Containerization - Fer Upversion to train - JC GPU for K8 - Richo QAT for K8 - Richo Redfish - Cristopher Infra & Cluster monitoring - Yang Regression testing: Tracker - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit?usp=sharing 3. Opens From haochuan.z.chen at intel.com Tue Oct 22 01:58:11 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 22 Oct 2019 01:58:11 +0000 Subject: [Starlingx-discuss] FW: [Build] Build layering reviews In-Reply-To: <1d6bf23c-0eaa-56dc-8154-bfb39a3be25e@linux.intel.com> References: <58efa3fb-9958-4af1-27f4-21db5a90da19@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F360482ED@SHSMSX104.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D856264A3B@CDSMSX102.ccr.corp.intel.com> <59676767-1870-b9a4-d256-77ff3a4148c8@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856265D08@CDSMSX102.ccr.corp.intel.com> <157958eb-6c13-318c-b087-a3d6b8a68662@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856266584@CDSMSX102.ccr.corp.intel.com> <92bad81a-e05f-6e1d-d83f-71263c01f29f@windriver.com> <56829C2A36C2E542B0CCB9854828E4D85626690A@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D85626EE06@CDSMSX102.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC158F833@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D856271BE0@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D856272C86@CDSMSX102.ccr.corp.intel.com> <1d6bf23c-0eaa-56dc-8154-bfb39a3be25e@linux.intel.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D856272E59@CDSMSX102.ccr.corp.intel.com> Hi Saul What's your error or missing? I could check for you. To verify, there are several cases and step. You should ready commit message in https://review.opendev.org/#/c/681821/ Case1, build all source code, this is same as currently building 1, sync code $ repo init -u https://opendev.org/starlingx/manifest.git -m default.xml 2, download rpm for flock layer $ ./download_mirror.sh -n -g -c yum.conf.sample -S 3, copy the downloaded to mirror folder, such as /import/mirrors/starlingx 4, create repo named "StxCentos7Distro" for building $ ./generate-cgcs-centos-repo.sh /import/mirrors/starlingx $ ./populate_downloads.sh /import/mirrors/starlingx Deploy with build iso and helm-chart Case2, build layer by layer Compile layer 1, sync code for compile layer $ repo init -u https://opendev.org/starlingx/manifest.git -m compile.xml 2, download rpm for flock layer $ ./download_mirror.sh -n -g -l compile -c yum.conf.sample -S 3, copy the downloaded to mirror folder, such as /import/mirrors/starlingx 4, create repo named "StxCentos7Distro" for building $ ./generate-cgcs-centos-repo.sh --layer=compile /import/mirrors/starlingx $ ./populate_downloads.sh /import/mirrors/starlingx 5, rpm package $ build-pkgs 6, create file for distro and compile layer build $ cd $MY_WORKSPACE $ cat std/image.inc rt/image.inc >> centos_compile_iso_image.inc $ ls std/rpmbuild/RPMS/ rt/rpmbuild/RPMS/ -l | awk '/tis\..*\.rpm/ {print $9}' > tis_pkg.lst Distro layer Before distro and flock layer building, must create a repo locally, as cenga is not update now. Edit stx-tools/centos-mirror-tools/config/centos/distro/required_build_tis_pkg.cfg Uncomment this line, and update with your compile layer build output folder #compile,file:///localdisk/loadbuild/martin/starlingx/tis_pkg.lst 1, sync code for compile layer $ repo init -u https://opendev.org/starlingx/manifest.git -m distro.xml 2, download rpm for flock layer $ ./download_mirror.sh -n -g -l distro -c yum.conf.sample -S 3, copy the downloaded to mirror folder, such as /import/mirrors/starlingx 4, create repo named "StxCentos7Distro" for building $ ./generate-cgcs-centos-repo.sh --layer=compile /import/mirrors/starlingx $ ./populate_downloads.sh /import/mirrors/starlingx 5, rpm package $ build-pkgs 6, create file for distro layer build $ cd $MY_WORKSPACE $ cat std/image.inc rt/image.inc >> centos_distro_iso_image.inc $ ls std/rpmbuild/RPMS/ rt/rpmbuild/RPMS/ -l | awk '/tis\..*\.rpm/ {print $9}' > tis_pkg.lst Flock layer Edit stx-tools/centos-mirror-tools/config/centos/flock/required_build_tis_pkg.cfg Uncomment these two line, and update with your distro layer build output folder #compile,file:///localdisk/loadbuild/martin/starlingx/tis_pkg.lst #distro,file:///localdisk/loadbuild/martin/distro/tis_pkg.lst 1, sync code for flock layer $ repo init -u https://opendev.org/starlingx/manifest.git -m flock.xml 2, download rpm for flock layer $ ./download_mirror.sh -n -g -l flock -c yum.conf.sample -S 3, copy the downloaded to mirror folder, such as /import/mirrors/starlingx 4, create repo named "StxCentos7Distro" for building $ ./generate-cgcs-centos-repo.sh --layer=flock /import/mirrors/starlingx $ ./populate_downloads.sh /import/mirrors/starlingx 5, rpm package and iso building $ build-pks && build-iso && build-helm-charts.sh Deploy with build iso and helm-chart Two case must build and deploy succeed. BR! Martin, Chen SSP, Software Engineer 021-61164330 -----Original Message----- From: Saul Wold Sent: Tuesday, October 22, 2019 7:32 AM To: Chen, Haochuan Z ; 'Penney, Don' ; 'Bailey, Henry Albert (Al)' ; 'Little, Scott' ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] FW: [Build] Build layering reviews Martin, I am still wondering how your testing this, if you have a completely updated manifest that points to all the updated gerrit reviews? As I mentioned in some reviews earlier I was having issues with building due to missing files. On 10/21/19 7:20 AM, Chen, Haochuan Z wrote: > Hi > > I have update patch again. Last week, I raise this concern// > > 3, update script download_mirror.sh and generate-cgts-centos-repo > > Currently all rpm name in lst is listed with fixed rpm version, which > makes layer build easily to be corrupted. For example, any time > TIS_PATCH_VER in build_srpm.data update, rpm name in lst should be updated. > > Prefer rpm named with “tis” should be query candidate on cenga, which > request download_mirror.sh and generate-cgts-centos-repo update. > Prefer we could finish such update in this story, as I think this is a > critical issue. > > So I update patch in stx-tools again to fix this issue. You can check > download_mirror.sh > > I add a step to generate rpm_tis.lst for layer build case. In such > case, it will download tis_pkg.lst from cenga. What listed in > tis_pkg.lst is distro or compile layer’s built rpm with named xxx.tis.xxx.rpm. > > So no matter src rpm or tarball upgrade, rpm_centos3party.lst is > unnecessary to update. > > And I update build-iso, image.inc should concatenate with distro and > compile layer’s image.in. As image.inc not only for install package, > but also request for generate comps.xml. > > Please check my update and review my patch > I am looking at this patch and doing some testing. Sau! > Thanks! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > *From:*Chen, Haochuan Z > *Sent:* Tuesday, October 15, 2019 10:27 PM > *To:* Penney, Don ; Bailey, Henry Albert > (Al) ; Little, Scott > ; 'starlingx-discuss at lists.starlingx.io' > > *Subject:* RE: [Starlingx-discuss] FW: [Build] Build layering reviews > > Hi > > I have updated patch for layer build > > https://review.opendev.org/#/c/681821/ > > https://review.opendev.org/#/c/681823/ > > https://review.opendev.org/#/c/681824/ > > https://review.opendev.org/#/c/681828/ > > https://review.opendev.org/#/c/681832/ > > https://review.opendev.org/#/c/681834/ > > https://review.opendev.org/#/c/681835/ > > https://review.opendev.org/#/c/681836/ > > https://review.opendev.org/#/c/681842/ > > https://review.opendev.org/#/c/681847/ > > https://review.opendev.org/#/c/681848/ > > https://review.opendev.org/#/c/681851/ > > https://review.opendev.org/#/c/681852/ > > https://review.opendev.org/#/c/681854/ > > https://review.opendev.org/#/c/681856/ > > https://review.opendev.org/#/c/681890/ > > https://review.opendev.org/#/c/681892/ > > https://review.opendev.org/#/c/681894/ > > https://review.opendev.org/#/c/681898/ > > https://review.opendev.org/#/c/681900/ > > https://review.opendev.org/#/c/681901/ > > https://review.opendev.org/#/c/681902/ > > https://review.opendev.org/#/c/681914/ > > https://review.opendev.org/#/c/688598/ > > And I think we still left three issue. > > 1, request build-tools/build_iso/centos_required_build_layer.cfg > > Current for self validation, we could add a file with such content. > But we should create a file depending on cenga update > > compile,file:///localdisk/loadbuild/martin/starlingx/centos_compile_is > o_image.inc > > distro,file:///localdisk/loadbuild/martin/distro/centos_distro_iso_ima > ge.inc > > flock,file:///localdisk/loadbuild/martin/flock/centos_flock_iso_image. > inc > > 2, propose use one copy of yum.conf.sample and yum.repo.d/* > > Currently there is 4 copies of yum.conf.sample and yum.repo.d/*.  3 > copies in stx-tools/centos-mirror-tools/config/centos// and 1 > copy in stx-tools/centos-mirror-tools/ > >   Propose to remove 3 copies in > stx-tools/centos-mirror-tools/config/centos//. To avoid user > confusing > > 3, update script download_mirror.sh and generate-cgts-centos-repo > > Currently all rpm name in lst is listed with fixed rpm version, which > makes layer build easily to be corrupted. For example, any time > TIS_PATCH_VER in build_srpm.data update, rpm name in lst should be updated. > > Prefer rpm named with “tis” should be query candidate on cenga, which > request download_mirror.sh and generate-cgts-centos-repo update. > Prefer we could finish such update in this story, as I think this is a > critical issue. > > Thanks! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > *From:*Penney, Don > > *Sent:* Monday, September 30, 2019 11:33 PM > *To:* Bailey, Henry Albert (Al) >; Chen, Haochuan Z > >; > Little, Scott >; > 'starlingx-discuss at lists.starlingx.io' > > > *Subject:* RE: [Starlingx-discuss] FW: [Build] Build layering reviews > > Is this the issue? > > openstack/python-horizon/centos/python-django-horizon.spec:BuildRequir > es: cgts-client > > I don’t see anything in this package that should need this dependency, > and it should be safe to remove it. > > *From:*Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] > *Sent:* Monday, September 30, 2019 10:56 AM > *To:* Chen, Haochuan Z; Little, Scott; > 'starlingx-discuss at lists.starlingx.io' > *Subject:* Re: [Starlingx-discuss] FW: [Build] Build layering reviews > > I think Cgts-client  (renamed to system-client)  should be in its own repo. > > Al > > *From:*Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] > *Sent:* Monday, September 30, 2019 2:06 AM > *To:* Little, Scott; 'starlingx-discuss at lists.starlingx.io' > *Subject:* Re: [Starlingx-discuss] FW: [Build] Build layering reviews > > Hi Scott > > I think have some question or concern. > > 1, I find distro layer has dependency to cgts-client, as there is a > addin for Horizon, which enables look up flock service info in Horizon. > > So there is task is must for layer building, which is out of my > expectation.  I begin to tackle these task. > > ·Relocate from git 'config', subdir 'sysinv/cgts-client', to git > 'utilities', subdir 'system-client', *with full git history.* > > ·Rename rpm package from 'cgts-client' to 'system-client' > > ·Fix rpm packages that list cgts-client as a require or build require > > ·Rename python module from 'cgts-client' to 'system-client' > > ·Scan function names and/or variables for any that contain 'cgts' ... > replace with 'system' ... can we do this in a backward compatible way? > > ·Fix users of the client to import using the new name, and reference > any renamed functions/data. > > ·Fix ISO and/or docker images that list this package for inclusion. > > 2, “all” layer maybe doesn’t work, warning! > > For current patch for generate-cgts-centos-repo.sh, all layer’s > rpms_lst_file is generated by merge “compiler/distro/flock” three > layers, config/centos/all doesn’t be referenced, which is none sense. > Which means package such bash-4.2.46-31.el7.tis.4.x86_64.rpm, named > with “tis” is also in mirror. This maybe interference source package > building. I think request some fix in generate-cgts-centos-repo.sh to > omit package with “tis” in name. > > 3, Layered build introduces rpms_cemtos.lst dependency on > TIS_PATCH_VER in build_srpm.data, which make developer easily disrupt > layered building mechanism. > > For distro and flock layer, it has dependency to starlingX customized > package, for example, distro layer require bash.tis. version>..rpm, which will be add in > config/centos/distro/rpms_centos3rdparty.lst > > If new developer forget to update and build all package, it maybe > disrupt layered building. > > BR! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > *From:*Chen, Haochuan Z > *Sent:* Friday, September 27, 2019 4:40 PM > *To:* Scott Little >; > starlingx-discuss at lists.starlingx.io > > *Subject:* RE: FW: [Starlingx-discuss] [Build] Build layering reviews > > Thanks, Scott. I have studied so much. > > BR! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > *From:*Scott Little > > *Sent:* Thursday, September 26, 2019 11:39 PM > *To:* Chen, Haochuan Z >; > starlingx-discuss at lists.starlingx.io > > *Subject:* Re: FW: [Starlingx-discuss] [Build] Build layering reviews > > Returning this discussion to the mailing list. > > If possible, join the Build call next week. > https://wiki.openstack.org/wiki/Starlingx/Meetings > > 1) > > When mock installs for the first time. it uses rpms that have been > download via lst file. The mock pseudo-layer lst files capture reflect > the rpms needed by mock.  The mock lst's are merged with the layers > lst's.  In this way, the mock rpms don't have to be listed in each and > every layer's lst. > > 2) > > Adding tools to generate an lst file reflacting the output of a build > layer, and adding that lst for consumprion by higher layers, is indeed > a possibility possibility I wanted to persue.  Reference to that > output lst could then be added to as a new arg to the download script > when invoked by a higher layer, or a config file could specify where > to find it (cengn is the likely default supplier). > > compile layer) > > The compile layer is a true layer, built prior to the distro layer. > Only a few build related packages go here.  Compilers, language > interpreters, rpm.  I wanted those packages in place so that all > distro layer packages build with the same tools. > > Scott > > On 2019-09-25 10:24 p.m., Chen, Haochuan Z wrote: > > Still not clear about mock layer. > > 1, In build container, mock is already installed, why request to > download mock required package firstly? > > 2, To build distro or flock layer, we could add compile layer’s tis > rpm in distro and flock layer’s lst file. By download compile > layer’s binary in mirror, it could also ensure user building package > with same tool. > > Why introduces compile layer? > > Thanks! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > *From:*Scott Little > > *Sent:* Thursday, September 26, 2019 12:25 AM > *To:* Chen, Haochuan Z > > *Subject:* Re: FW: [Starlingx-discuss] [Build] Build layering > reviews > > See inline ... > > Scott > > On 2019-09-23 11:00 a.m., Chen, Haochuan Z wrote: > > Hi Scott > > I studied your patch and some questions. > > 1, why there is mock and compile layer, what's usage or > intention for these two layers? > > Build-pkgs uses a tool called mock to create a reproducible > compilation sandbox.  It is chroot like environmnet into which rpms > are installed to construct a minimal build environment. > > The mock layer is not built.  I created it as a placeholder for the > lst files that downloads all the rpms that mock requires.  Prior to > building a layer, the lst files for both the layer being build, and > the mock pseudo layer, need to be processed. Without the mock pseudo > layer, we would have to replicate that list of mock required rpms in > each and ever layer's lst files. > > The concept ran into a bit of trouble because some of the rpms > needed by mock are themselves built by the compile or distro layers > (with a newer revision).   So the > mock pseudo layer might actually omit those rpms from it's lst file, > and they needed to be listed in the layer lst files instead. > > The compile layer is a true layer, built prior to the distro layer. > Only a few build related packages go here.  Compilers, language > interpreters, rpm.  I wanted those packages in place so that all > distro layer packages build with the same tools. > > 2, for download_mirror.sh, it generate rpm list by merge file in > config/centos// and rpm list file in > stx/ > >    But for generate-cgcs-centos-repo.sh, it use rpm list file > in centos-mirror-tools folder. Rpm package should be added in > two rpm list file. > >    It is not good for maintenance. What about remove rpm list > file in centos-mirror-tools folder > > /rpms_centos.lst/rpms_centos3rdparties.lst/rpms_3rdparties.lst/other_downloads.lst/ > tarball-dl.lst/ > > That was considered and debated. The concern was that the many git > repos that make up the layer would list different versions of the > same package.  Then what do we do?  Throw an error?  Silently use > the newest package?  So we elected to keep binary rpms needed to > satisfy dependencies listed in a central place. > > At some point we may want to explore allowing lst files specify > required package but not version (beyond a possible minimum version) > when on the master branch, and have a way to 'lock down' the > versions only for a release branch. > > 3, Question about setup yum repo for rpm tailing with “tis” such > as xxx.*tis*.x86_64.rpm or xxx.*tis*.noarch.rpm > > In this patch https://review.opendev.org/#/c/681821/1 > > /There is such line in > > config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo/ > > /[Starlingx-cengn_distro_layer]/ > > /name=Starlingx-cengn_distro_layer/ > > > /baseurl=http://127.0.0.1:8088/localdisk/loadbuild//*/slittle1/restruc > ture3b/*//std/rpmbuild/RPMS// > > /enabled=1/ > > /[Starlingx-cengn_distro_layer-rt]/ > > /name=Starlingx-cengn_distro_layer/ > > > /baseurl=http://127.0.0.1:8088/localdisk/loadbuild//*/slittle1/restruc > ture3b/*//rt/rpmbuild/RPMS// > > /enabled=1/ > > also in > > > config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo > > > config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo > > My understanding is rpm tailing with “tis” should also upload to > cengn, rpm name listed in > > centos-mirror-tools/config/centos/flock/rpms_centos3rdparties.lst > > So these three files should be unnecessary, with cengn update > for layered build. > > > config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo > > > config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo > > > config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo > > For development testing, I had to hack together a simulated cengn by > running lighttpd on 127.0.0.1:8088 and allowing it to serve up files > from builds of lower layers > > restructure3a == layer-comiler layer build > > restructure3b == layer-distro layer build > > restructure3c == layer-flock layer build  (although there shouldn't > be a repo entry referring to that one) > > Finalizing the repo entries would have to wait until cengn was up an > running. > > 4, In generate-cgcs-centos-repo.sh there is --layer-dir, and > such content in your patch commit message > > /generate-cgcs-centos-repo.sh \/ > > /--layer-dir=/localdisk/loadbuild/slittle1/layer-compile/std/rpmbuild/RPMS/ > \/ > > /--layer-dir=/localdisk/loadbuild/slittle1/layer-distro/std/rpmbuild/RPMS/ > \/ > > /--layer-dir=/localdisk/loadbuild/slittle1/layer-distro/rt/rpmbuild/RPMS/ > \/ > > //import/mirrors/starlingx/ > >    For all rpm download from cengn, --layer-dir is unnecessary > to generate link, correct? > > This is another way to do cross layer development testing without > support from cengn.  Again the goal is to allow an upper layer build > to download rpms from a lower layer build on the same machine. > > 5, could you share > build-tools/build-iso/centos_required_build_layer.cfg, share > to me > > Did that not get published in my reviews?  Content is very simple. > > compile,file:///localdisk/loadbuild/slittle1/restructure3a/centos_compile_iso_image.inc > > distro,file:///localdisk/loadbuild/slittle1/restructure3b/centos_distro_iso_image.inc > > flock,file:///localdisk/loadbuild/slittle1/restructure3c/centos_flock_iso_image.inc > > age.inc> > > 6, For distro/compiler/flock, all are separate layer? > > Yes > > My current step > > /repo init -u https://opendev.org/starlingx/manifest.git/ > > /apply this patch to .repo/manifests/ > > /https://review.opendev.org/#/c/681914/1/ > > /repo init -m compile.xml/ > > /repo sync/ > > /apply these to patch/ > > /https://review.opendev.org/#/c/681821/1/ > > /https://review.opendev.org/#/c/681828/1/ > > /./download_mirror.sh  -n -g -l flock -c > config/centos/compiler/yum.conf.sample -S / > > /./toCopy/generate-cgts-centos-repo > output/stx-r1/CentOS/pike// > > /build-pkgs/ > > /build-iso/ > > BR! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > -----Original Message----- > From: Scott Little > > Sent: Thursday, September 19, 2019 9:54 PM > To: Chen, Haochuan Z > > Subject: Re: FW: [Starlingx-discuss] [Build] Build layering > reviews > > Most of the required changes were already merged. > > I'll scan the spec when time permits to see if I missed anything. > > Scott > > On 2019-09-16 12:01 p.m., Chen, Haochuan Z wrote: > > > Hi Scott > > > > > > I read your patch for build layering, but could not find > patch for build script. > > > > > > Description in spec > https://review.opendev.org/#/c/672288/12/ > > > Modifications to package build scripts ... build-pkgs, > > > build-srpms-parallel, build-srpms-serial, > build-rpms-parallel, build-rpms-serial (cgcs-root): > > > > > > Thanks > > > > > > Martin, Chen > > > SSP, Software Engineer > > > 021-61164330 > > > > > > -----Original Message----- > > > From: Xie, Cindy > > > Sent: Friday, September 13, 2019 12:24 PM > > > To: Chen, Haochuan Z > > > > Cc: Hu, Yong > > > > Subject: FW: [Starlingx-discuss] [Build] Build layering > reviews > > > > > > Martin, > > > I am wondering if you will be interested to working on this > task. To me, having layering build and provide efficiency to > developers are very important for StarlingX. It also provide a > chance that you and work together w/ WR folks being more close > collaboration. Let me know your interested level. > > > > > > Thx. -cindy > > > > > > -----Original Message----- > > > From: Scott Little > > > > Sent: Friday, September 13, 2019 4:55 AM > > > To: starlingx-discuss at lists.starlingx.io > > > > Subject: [Starlingx-discuss] [Build] Build layering reviews > > > > > > My prototype code for the layered build has been posted to > gerrit. > > > (listed below) > > > > > > I was briefly able to build all layers, and produce an iso > with the same package content as the cengn build.  Then I was > diverted by non-trivial changes to the restructuring work. What > I have posted is now several weeks out of date and will almost > certainly will not work.  The devil is in keeping the lst files > in sync with the ever changing master branch. > > > > > > Other commitments will prevent me from resuming this work > until November.  If anyone wants to whip the lst files into > shape and try to get the build working again, be my guest. > > > > > > Final delivery will require changes to the CENGN build > scripts (Don or Myself), and a freeze on packaging changes will > likely be required for aprox 3 days to finalize the lst files. > > > > > > Scott > > > > > > ---------------- ---------------- > > > > > > https://review.opendev.org/#/c/681821/1 > > > > > > https://review.opendev.org/#/c/681914/1 > > > > > > https://review.opendev.org/#/c/681823/1 > > > > > > https://review.opendev.org/#/c/681824/1 > > > > > > https://review.opendev.org/#/c/681828/1 > > > > > > https://review.opendev.org/#/c/681832/2 > > > > > > https://review.opendev.org/#/c/681834/1 > > > > > > https://review.opendev.org/#/c/681836/1 > > > > > > https://review.opendev.org/#/c/681835/1 > > > > > > https://review.opendev.org/#/c/681842/1 > > > > > > https://review.opendev.org/#/c/681847/1 > > > > > > https://review.opendev.org/#/c/681848/1 > > > > > > https://review.opendev.org/#/c/681851/1 > > > > > > https://review.opendev.org/#/c/681852/1 > > > > > > https://review.opendev.org/#/c/681854/1 > > > > > > https://review.opendev.org/#/c/681856/1 > > > > > > https://review.opendev.org/#/c/681890/1 > > > > > > https://review.opendev.org/#/c/681892/1 > > > > > > https://review.opendev.org/#/c/681892/1 > > > > > > https://review.opendev.org/#/c/681898/1 > > > > > > https://review.opendev.org/#/c/681900/1 > > > > > > https://review.opendev.org/#/c/681901/1 > > > > > > https://review.opendev.org/#/c/681902/1 > > > > > > > > > > > > > > > _______________________________________________ > > > 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 tingjie.chen at intel.com Tue Oct 22 02:09:51 2019 From: tingjie.chen at intel.com (Chen, Tingjie) Date: Tue, 22 Oct 2019 02:09:51 +0000 Subject: [Starlingx-discuss] Status of Ceph containerization // RE: Weekly StarlingX non-OpenStack distro meeting In-Reply-To: References: Message-ID: Hi All, For the status of Ceph containerization, https://storyboard.openstack.org/#!/story/2005527 I list sub-tasks currently we are working on for STX 3.0 as following: 36441 & 36442: [MS2] [Subtask] Create helm-chart for Rook operator with CSI support [MS2] [Subtask] Create helm-chart for Ceph cluster patch: https://review.opendev.org/#/c/681457 in review, and received several comments, we plan to break into 2 patches with rook-ceph and ceph-cluster helm charts, since rook-ceph port from rook community and with customized patch, this need to rework with tarball with build.spec. 36443 & 36444 & 36576: [MS2] [Subtask] Bring up Rook & Ceph cluster with helm-charts in system service after ansible script [MS2] [Subtask] Override function for STX deployment configurations. [MS2] [Subtask] Investigate the ceph mon/osd policy with system configuration Actually there is patch: https://review.opendev.org/#/c/687340 but we also others parameters (as following table) to overrides, so will finished soon. Name Description Plan in phase ceph-mon count ceph monitor count have 2 policies: 1. for AIO, 1 monitor. Simplex have 1, and duplex is for drbd so show ceph-mon-list for 2 uuid. 2. for multi-node, 3 monitors. STX 3.0 ceph-mon affinity ceph monitor affinity: 1. for AIO, 1 monitor. Duplex is for drbd so show ceph-mon-list for 2 uuid, but deloyed in controller-0 2. for multi-node, There are 3 monitors, 2 in controllers and 1 in compute-0 by default. In 2+2+2, cannot config monitor STX 3.0 ceph-mgr modules modules configuration (pg_autoscaler etc) STX 3.0 ceph-osd location Since disk conflict with native Ceph deployment, current implementation is located in /var/lib/rook/storage-dir, will switch to each baremetal disk in STX 4.0 STX 4.0 36445: [MS2] [Subtask] Rook plugin implementation with several features support Create a new rookclient.py to interact with sysinv, implement the main framework, the patch is in dev and ready to review soon. In STX 3.0, the features mentioned in previous sub-tasks of Containerized Ceph will NOT break functionality & resource with native Ceph cluster & sysinv. Martin(Haochuan) and me are making efforts on the subtasks. Also I have filed test cases with current phase: https://ethercalc.openstack.org/81005mu7o1pg Welcome to give comments~ Thanks, Tingjie -----Original Message----- From: Xie, Cindy Sent: Wednesday, October 16, 2019 9:54 PM To: Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; 'Rowsell, Brent' Subject: Re: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting Agenda & notes for 10/16 meeting: . Ceph containerization update (Tingjie) https://review.opendev.org/#/c/681457/ this is for Helm chart definition, can be review now. https://review.opendev.org/#/c/687340/ for Helm overrides framework, need to extend later. verified in AIO and multi-node provision. configuration needs to be override according to STX parameters. Martin working on this for parameters to align w/ the native deployment. for stx.3.0: only to merge the implantation for Helm chart and override framework. and rook-plugin which support sysinv, this can co-exist w/ current native ceph deployment. test case development is in progress, Tingjie will sync with Fernando. for sysinv, still need to working on patches, not ready for upload/review. AR: Tingjie to send email to the mailing list for the current status & planning for include partial implementation without impacting the native Ceph functionality. . Debranding update (Saul) Starting from the tools repo, the tools in the build area to debrand the mirroring process. Part of this is for ease of use for build steps. Very early stage. Not fit in stx.3.0 scope. https://storyboard.openstack.org/#!/story/2006387, call volunteer from the community. . CentOS 8 upgrade planning (Cindy) CentOS 8.0 2 stories created: https://storyboard.openstack.org/#!/story/2006728, the kernel inside CentOS 8 is 4.18, there is no RT kernel. https://storyboard.openstack.org/#!/story/2006729 Shuai is working on new kernel onto build system. Need to understand each patches. there was an earlier analysis for kernel patches available. AR: Saul please share this analysis to Shuai. against 4.19 kernel some long time ago. See https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAugOWXMjB7VIrfc/edit#gid=311578025 Tab Kernel Patches Details https://github.com/xe1gyq/linux/commits/v4.19 https://github.com/xe1gyq/linux/commits/v4.18 AR: Shuai to provide an Excel sheet to compare RPM/sRPM in StarlingX and in CentOS 8.0 . Opens - none _____________________________________________ From: Xie, Cindy Sent: Tuesday, October 15, 2019 9:39 PM To: Wold, Saul >; 'starlingx-discuss at lists.starlingx.io' >; 'Rowsell, Brent' > Subject: RE: Weekly StarlingX non-OpenStack distro meeting Agenda: - Ceph containerization update (Tingjie) - Debranding update (Saul) - CentOS 8 upgrade planning (Cindy) - Opens Cindy Xie IAGS http://starlingx.io/ -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, October 16, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . 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 _______________________________________________ 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 Tue Oct 22 02:33:39 2019 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 21 Oct 2019 19:33:39 -0700 Subject: [Starlingx-discuss] FW: [Build] Build layering reviews In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D856272E59@CDSMSX102.ccr.corp.intel.com> References: <58efa3fb-9958-4af1-27f4-21db5a90da19@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856264A3B@CDSMSX102.ccr.corp.intel.com> <59676767-1870-b9a4-d256-77ff3a4148c8@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856265D08@CDSMSX102.ccr.corp.intel.com> <157958eb-6c13-318c-b087-a3d6b8a68662@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856266584@CDSMSX102.ccr.corp.intel.com> <92bad81a-e05f-6e1d-d83f-71263c01f29f@windriver.com> <56829C2A36C2E542B0CCB9854828E4D85626690A@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D85626EE06@CDSMSX102.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC158F833@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D856271BE0@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D856272C86@CDSMSX102.ccr.corp.intel.com> <1d6bf23c-0eaa-56dc-8154-bfb39a3be25e@linux.intel.com> <56829C2A36C2E542B0CCB9854828E4D856272E59@CDSMSX102.ccr.corp.intel.com> Message-ID: On 10/21/19 6:58 PM, Chen, Haochuan Z wrote: > Hi Saul > > What's your error or missing? I could check for you. > > To verify, there are several cases and step. You should ready commit message in https://review.opendev.org/#/c/681821/ > > Case1, build all source code, this is same as currently building > 1, sync code > $ repo init -u https://opendev.org/starlingx/manifest.git -m default.xml > When do you do a repo sync? Also, when you do a repo sync, the default.xml will contain the current HEAD not any of your changes to tools or to the root area. You need a manifest that has all the revisions set to the reviews. I will post something for testing shortly. Sau! > 2, download rpm for flock layer > $ ./download_mirror.sh -n -g -c yum.conf.sample -S > > 3, copy the downloaded to mirror folder, such as /import/mirrors/starlingx > > 4, create repo named "StxCentos7Distro" for building > $ ./generate-cgcs-centos-repo.sh /import/mirrors/starlingx > $ ./populate_downloads.sh /import/mirrors/starlingx > > Deploy with build iso and helm-chart > > > Case2, build layer by layer > Compile layer > 1, sync code for compile layer > $ repo init -u https://opendev.org/starlingx/manifest.git -m compile.xml > > 2, download rpm for flock layer > $ ./download_mirror.sh -n -g -l compile -c yum.conf.sample -S > There has to be some missing steps. > 3, copy the downloaded to mirror folder, such as /import/mirrors/starlingx > > 4, create repo named "StxCentos7Distro" for building > $ ./generate-cgcs-centos-repo.sh --layer=compile /import/mirrors/starlingx > $ ./populate_downloads.sh /import/mirrors/starlingx > > 5, rpm package > $ build-pkgs > > 6, create file for distro and compile layer build > $ cd $MY_WORKSPACE > $ cat std/image.inc rt/image.inc >> centos_compile_iso_image.inc > $ ls std/rpmbuild/RPMS/ rt/rpmbuild/RPMS/ -l | awk '/tis\..*\.rpm/ {print $9}' > tis_pkg.lst > > Distro layer > Before distro and flock layer building, must create a repo locally, as cenga is not update now. > Edit stx-tools/centos-mirror-tools/config/centos/distro/required_build_tis_pkg.cfg > Uncomment this line, and update with your compile layer build output folder > #compile,file:///localdisk/loadbuild/martin/starlingx/tis_pkg.lst > > 1, sync code for compile layer > $ repo init -u https://opendev.org/starlingx/manifest.git -m distro.xml > > 2, download rpm for flock layer > $ ./download_mirror.sh -n -g -l distro -c yum.conf.sample -S > > 3, copy the downloaded to mirror folder, such as /import/mirrors/starlingx > > 4, create repo named "StxCentos7Distro" for building > $ ./generate-cgcs-centos-repo.sh --layer=compile /import/mirrors/starlingx > $ ./populate_downloads.sh /import/mirrors/starlingx > > 5, rpm package > $ build-pkgs > > 6, create file for distro layer build > $ cd $MY_WORKSPACE > $ cat std/image.inc rt/image.inc >> centos_distro_iso_image.inc > $ ls std/rpmbuild/RPMS/ rt/rpmbuild/RPMS/ -l | awk '/tis\..*\.rpm/ {print $9}' > tis_pkg.lst > > Flock layer > Edit stx-tools/centos-mirror-tools/config/centos/flock/required_build_tis_pkg.cfg > Uncomment these two line, and update with your distro layer build output folder > #compile,file:///localdisk/loadbuild/martin/starlingx/tis_pkg.lst > #distro,file:///localdisk/loadbuild/martin/distro/tis_pkg.lst > > 1, sync code for flock layer > $ repo init -u https://opendev.org/starlingx/manifest.git -m flock.xml > > 2, download rpm for flock layer > $ ./download_mirror.sh -n -g -l flock -c yum.conf.sample -S > > 3, copy the downloaded to mirror folder, such as /import/mirrors/starlingx > > 4, create repo named "StxCentos7Distro" for building > $ ./generate-cgcs-centos-repo.sh --layer=flock /import/mirrors/starlingx > $ ./populate_downloads.sh /import/mirrors/starlingx > > 5, rpm package and iso building > $ build-pks && build-iso && build-helm-charts.sh > > Deploy with build iso and helm-chart > > Two case must build and deploy succeed. > > BR! > > Martin, Chen > SSP, Software Engineer > 021-61164330 > > -----Original Message----- > From: Saul Wold > Sent: Tuesday, October 22, 2019 7:32 AM > To: Chen, Haochuan Z ; 'Penney, Don' ; 'Bailey, Henry Albert (Al)' ; 'Little, Scott' ; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] FW: [Build] Build layering reviews > > Martin, > > I am still wondering how your testing this, if you have a completely updated manifest that points to all the updated gerrit reviews? > > As I mentioned in some reviews earlier I was having issues with building due to missing files. > > On 10/21/19 7:20 AM, Chen, Haochuan Z wrote: >> Hi >> >> I have update patch again. Last week, I raise this concern// >> >> 3, update script download_mirror.sh and generate-cgts-centos-repo >> >> Currently all rpm name in lst is listed with fixed rpm version, which >> makes layer build easily to be corrupted. For example, any time >> TIS_PATCH_VER in build_srpm.data update, rpm name in lst should be updated. >> >> Prefer rpm named with “tis” should be query candidate on cenga, which >> request download_mirror.sh and generate-cgts-centos-repo update. >> Prefer we could finish such update in this story, as I think this is a >> critical issue. >> >> So I update patch in stx-tools again to fix this issue. You can check >> download_mirror.sh >> >> I add a step to generate rpm_tis.lst for layer build case. In such >> case, it will download tis_pkg.lst from cenga. What listed in >> tis_pkg.lst is distro or compile layer’s built rpm with named xxx.tis.xxx.rpm. >> >> So no matter src rpm or tarball upgrade, rpm_centos3party.lst is >> unnecessary to update. >> >> And I update build-iso, image.inc should concatenate with distro and >> compile layer’s image.in. As image.inc not only for install package, >> but also request for generate comps.xml. >> >> Please check my update and review my patch >> > I am looking at this patch and doing some testing. > > Sau! > >> Thanks! >> >> Martin, Chen >> >> SSP, Software Engineer >> >> 021-61164330 >> >> *From:*Chen, Haochuan Z >> *Sent:* Tuesday, October 15, 2019 10:27 PM >> *To:* Penney, Don ; Bailey, Henry Albert >> (Al) ; Little, Scott >> ; 'starlingx-discuss at lists.starlingx.io' >> >> *Subject:* RE: [Starlingx-discuss] FW: [Build] Build layering reviews >> >> Hi >> >> I have updated patch for layer build >> >> https://review.opendev.org/#/c/681821/ >> >> https://review.opendev.org/#/c/681823/ >> >> https://review.opendev.org/#/c/681824/ >> >> https://review.opendev.org/#/c/681828/ >> >> https://review.opendev.org/#/c/681832/ >> >> https://review.opendev.org/#/c/681834/ >> >> https://review.opendev.org/#/c/681835/ >> >> https://review.opendev.org/#/c/681836/ >> >> https://review.opendev.org/#/c/681842/ >> >> https://review.opendev.org/#/c/681847/ >> >> https://review.opendev.org/#/c/681848/ >> >> https://review.opendev.org/#/c/681851/ >> >> https://review.opendev.org/#/c/681852/ >> >> https://review.opendev.org/#/c/681854/ >> >> https://review.opendev.org/#/c/681856/ >> >> https://review.opendev.org/#/c/681890/ >> >> https://review.opendev.org/#/c/681892/ >> >> https://review.opendev.org/#/c/681894/ >> >> https://review.opendev.org/#/c/681898/ >> >> https://review.opendev.org/#/c/681900/ >> >> https://review.opendev.org/#/c/681901/ >> >> https://review.opendev.org/#/c/681902/ >> >> https://review.opendev.org/#/c/681914/ >> >> https://review.opendev.org/#/c/688598/ >> >> And I think we still left three issue. >> >> 1, request build-tools/build_iso/centos_required_build_layer.cfg >> >> Current for self validation, we could add a file with such content. >> But we should create a file depending on cenga update >> >> compile,file:///localdisk/loadbuild/martin/starlingx/centos_compile_is >> o_image.inc >> >> distro,file:///localdisk/loadbuild/martin/distro/centos_distro_iso_ima >> ge.inc >> >> flock,file:///localdisk/loadbuild/martin/flock/centos_flock_iso_image. >> inc >> >> 2, propose use one copy of yum.conf.sample and yum.repo.d/* >> >> Currently there is 4 copies of yum.conf.sample and yum.repo.d/*.  3 >> copies in stx-tools/centos-mirror-tools/config/centos// and 1 >> copy in stx-tools/centos-mirror-tools/ >> >>   Propose to remove 3 copies in >> stx-tools/centos-mirror-tools/config/centos//. To avoid user >> confusing >> >> 3, update script download_mirror.sh and generate-cgts-centos-repo >> >> Currently all rpm name in lst is listed with fixed rpm version, which >> makes layer build easily to be corrupted. For example, any time >> TIS_PATCH_VER in build_srpm.data update, rpm name in lst should be updated. >> >> Prefer rpm named with “tis” should be query candidate on cenga, which >> request download_mirror.sh and generate-cgts-centos-repo update. >> Prefer we could finish such update in this story, as I think this is a >> critical issue. >> >> Thanks! >> >> Martin, Chen >> >> SSP, Software Engineer >> >> 021-61164330 >> >> *From:*Penney, Don > > >> *Sent:* Monday, September 30, 2019 11:33 PM >> *To:* Bailey, Henry Albert (Al) > >; Chen, Haochuan Z >> >; >> Little, Scott > >; >> 'starlingx-discuss at lists.starlingx.io' >> > > >> *Subject:* RE: [Starlingx-discuss] FW: [Build] Build layering reviews >> >> Is this the issue? >> >> openstack/python-horizon/centos/python-django-horizon.spec:BuildRequir >> es: cgts-client >> >> I don’t see anything in this package that should need this dependency, >> and it should be safe to remove it. >> >> *From:*Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] >> *Sent:* Monday, September 30, 2019 10:56 AM >> *To:* Chen, Haochuan Z; Little, Scott; >> 'starlingx-discuss at lists.starlingx.io' >> *Subject:* Re: [Starlingx-discuss] FW: [Build] Build layering reviews >> >> I think Cgts-client  (renamed to system-client)  should be in its own repo. >> >> Al >> >> *From:*Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] >> *Sent:* Monday, September 30, 2019 2:06 AM >> *To:* Little, Scott; 'starlingx-discuss at lists.starlingx.io' >> *Subject:* Re: [Starlingx-discuss] FW: [Build] Build layering reviews >> >> Hi Scott >> >> I think have some question or concern. >> >> 1, I find distro layer has dependency to cgts-client, as there is a >> addin for Horizon, which enables look up flock service info in Horizon. >> >> So there is task is must for layer building, which is out of my >> expectation.  I begin to tackle these task. >> >> ·Relocate from git 'config', subdir 'sysinv/cgts-client', to git >> 'utilities', subdir 'system-client', *with full git history.* >> >> ·Rename rpm package from 'cgts-client' to 'system-client' >> >> ·Fix rpm packages that list cgts-client as a require or build require >> >> ·Rename python module from 'cgts-client' to 'system-client' >> >> ·Scan function names and/or variables for any that contain 'cgts' ... >> replace with 'system' ... can we do this in a backward compatible way? >> >> ·Fix users of the client to import using the new name, and reference >> any renamed functions/data. >> >> ·Fix ISO and/or docker images that list this package for inclusion. >> >> 2, “all” layer maybe doesn’t work, warning! >> >> For current patch for generate-cgts-centos-repo.sh, all layer’s >> rpms_lst_file is generated by merge “compiler/distro/flock” three >> layers, config/centos/all doesn’t be referenced, which is none sense. >> Which means package such bash-4.2.46-31.el7.tis.4.x86_64.rpm, named >> with “tis” is also in mirror. This maybe interference source package >> building. I think request some fix in generate-cgts-centos-repo.sh to >> omit package with “tis” in name. >> >> 3, Layered build introduces rpms_cemtos.lst dependency on >> TIS_PATCH_VER in build_srpm.data, which make developer easily disrupt >> layered building mechanism. >> >> For distro and flock layer, it has dependency to starlingX customized >> package, for example, distro layer require bash.tis.> version>..rpm, which will be add in >> config/centos/distro/rpms_centos3rdparty.lst >> >> If new developer forget to update and build all package, it maybe >> disrupt layered building. >> >> BR! >> >> Martin, Chen >> >> SSP, Software Engineer >> >> 021-61164330 >> >> *From:*Chen, Haochuan Z >> *Sent:* Friday, September 27, 2019 4:40 PM >> *To:* Scott Little > >; >> starlingx-discuss at lists.starlingx.io >> >> *Subject:* RE: FW: [Starlingx-discuss] [Build] Build layering reviews >> >> Thanks, Scott. I have studied so much. >> >> BR! >> >> Martin, Chen >> >> SSP, Software Engineer >> >> 021-61164330 >> >> *From:*Scott Little > > >> *Sent:* Thursday, September 26, 2019 11:39 PM >> *To:* Chen, Haochuan Z > >; >> starlingx-discuss at lists.starlingx.io >> >> *Subject:* Re: FW: [Starlingx-discuss] [Build] Build layering reviews >> >> Returning this discussion to the mailing list. >> >> If possible, join the Build call next week. >> https://wiki.openstack.org/wiki/Starlingx/Meetings >> >> 1) >> >> When mock installs for the first time. it uses rpms that have been >> download via lst file. The mock pseudo-layer lst files capture reflect >> the rpms needed by mock.  The mock lst's are merged with the layers >> lst's.  In this way, the mock rpms don't have to be listed in each and >> every layer's lst. >> >> 2) >> >> Adding tools to generate an lst file reflacting the output of a build >> layer, and adding that lst for consumprion by higher layers, is indeed >> a possibility possibility I wanted to persue.  Reference to that >> output lst could then be added to as a new arg to the download script >> when invoked by a higher layer, or a config file could specify where >> to find it (cengn is the likely default supplier). >> >> compile layer) >> >> The compile layer is a true layer, built prior to the distro layer. >> Only a few build related packages go here.  Compilers, language >> interpreters, rpm.  I wanted those packages in place so that all >> distro layer packages build with the same tools. >> >> Scott >> >> On 2019-09-25 10:24 p.m., Chen, Haochuan Z wrote: >> >> Still not clear about mock layer. >> >> 1, In build container, mock is already installed, why request to >> download mock required package firstly? >> >> 2, To build distro or flock layer, we could add compile layer’s tis >> rpm in distro and flock layer’s lst file. By download compile >> layer’s binary in mirror, it could also ensure user building package >> with same tool. >> >> Why introduces compile layer? >> >> Thanks! >> >> Martin, Chen >> >> SSP, Software Engineer >> >> 021-61164330 >> >> *From:*Scott Little >> >> *Sent:* Thursday, September 26, 2019 12:25 AM >> *To:* Chen, Haochuan Z >> >> *Subject:* Re: FW: [Starlingx-discuss] [Build] Build layering >> reviews >> >> See inline ... >> >> Scott >> >> On 2019-09-23 11:00 a.m., Chen, Haochuan Z wrote: >> >> Hi Scott >> >> I studied your patch and some questions. >> >> 1, why there is mock and compile layer, what's usage or >> intention for these two layers? >> >> Build-pkgs uses a tool called mock to create a reproducible >> compilation sandbox.  It is chroot like environmnet into which rpms >> are installed to construct a minimal build environment. >> >> The mock layer is not built.  I created it as a placeholder for the >> lst files that downloads all the rpms that mock requires.  Prior to >> building a layer, the lst files for both the layer being build, and >> the mock pseudo layer, need to be processed. Without the mock pseudo >> layer, we would have to replicate that list of mock required rpms in >> each and ever layer's lst files. >> >> The concept ran into a bit of trouble because some of the rpms >> needed by mock are themselves built by the compile or distro layers >> (with a newer revision).   So the >> mock pseudo layer might actually omit those rpms from it's lst file, >> and they needed to be listed in the layer lst files instead. >> >> The compile layer is a true layer, built prior to the distro layer. >> Only a few build related packages go here.  Compilers, language >> interpreters, rpm.  I wanted those packages in place so that all >> distro layer packages build with the same tools. >> >> 2, for download_mirror.sh, it generate rpm list by merge file in >> config/centos// and rpm list file in >> stx/ >> >>    But for generate-cgcs-centos-repo.sh, it use rpm list file >> in centos-mirror-tools folder. Rpm package should be added in >> two rpm list file. >> >>    It is not good for maintenance. What about remove rpm list >> file in centos-mirror-tools folder >> >> /rpms_centos.lst/rpms_centos3rdparties.lst/rpms_3rdparties.lst/other_downloads.lst/ >> tarball-dl.lst/ >> >> That was considered and debated. The concern was that the many git >> repos that make up the layer would list different versions of the >> same package.  Then what do we do?  Throw an error?  Silently use >> the newest package?  So we elected to keep binary rpms needed to >> satisfy dependencies listed in a central place. >> >> At some point we may want to explore allowing lst files specify >> required package but not version (beyond a possible minimum version) >> when on the master branch, and have a way to 'lock down' the >> versions only for a release branch. >> >> 3, Question about setup yum repo for rpm tailing with “tis” such >> as xxx.*tis*.x86_64.rpm or xxx.*tis*.noarch.rpm >> >> In this patch https://review.opendev.org/#/c/681821/1 >> >> /There is such line in >> >> config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo/ >> >> /[Starlingx-cengn_distro_layer]/ >> >> /name=Starlingx-cengn_distro_layer/ >> >> >> /baseurl=http://127.0.0.1:8088/localdisk/loadbuild//*/slittle1/restruc >> ture3b/*//std/rpmbuild/RPMS// >> >> /enabled=1/ >> >> /[Starlingx-cengn_distro_layer-rt]/ >> >> /name=Starlingx-cengn_distro_layer/ >> >> >> /baseurl=http://127.0.0.1:8088/localdisk/loadbuild//*/slittle1/restruc >> ture3b/*//rt/rpmbuild/RPMS// >> >> /enabled=1/ >> >> also in >> >> >> config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo >> >> >> config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo >> >> My understanding is rpm tailing with “tis” should also upload to >> cengn, rpm name listed in >> >> centos-mirror-tools/config/centos/flock/rpms_centos3rdparties.lst >> >> So these three files should be unnecessary, with cengn update >> for layered build. >> >> >> config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo >> >> >> config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo >> >> >> config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo >> >> For development testing, I had to hack together a simulated cengn by >> running lighttpd on 127.0.0.1:8088 and allowing it to serve up files >> from builds of lower layers >> >> restructure3a == layer-comiler layer build >> >> restructure3b == layer-distro layer build >> >> restructure3c == layer-flock layer build  (although there shouldn't >> be a repo entry referring to that one) >> >> Finalizing the repo entries would have to wait until cengn was up an >> running. >> >> 4, In generate-cgcs-centos-repo.sh there is --layer-dir, and >> such content in your patch commit message >> >> /generate-cgcs-centos-repo.sh \/ >> >> /--layer-dir=/localdisk/loadbuild/slittle1/layer-compile/std/rpmbuild/RPMS/ >> \/ >> >> /--layer-dir=/localdisk/loadbuild/slittle1/layer-distro/std/rpmbuild/RPMS/ >> \/ >> >> /--layer-dir=/localdisk/loadbuild/slittle1/layer-distro/rt/rpmbuild/RPMS/ >> \/ >> >> //import/mirrors/starlingx/ >> >>    For all rpm download from cengn, --layer-dir is unnecessary >> to generate link, correct? >> >> This is another way to do cross layer development testing without >> support from cengn.  Again the goal is to allow an upper layer build >> to download rpms from a lower layer build on the same machine. >> >> 5, could you share >> build-tools/build-iso/centos_required_build_layer.cfg, share >> to me >> >> Did that not get published in my reviews?  Content is very simple. >> >> compile,file:///localdisk/loadbuild/slittle1/restructure3a/centos_compile_iso_image.inc >> >> distro,file:///localdisk/loadbuild/slittle1/restructure3b/centos_distro_iso_image.inc >> >> flock,file:///localdisk/loadbuild/slittle1/restructure3c/centos_flock_iso_image.inc >> >> > age.inc> >> >> 6, For distro/compiler/flock, all are separate layer? >> >> Yes >> >> My current step >> >> /repo init -u https://opendev.org/starlingx/manifest.git/ >> >> /apply this patch to .repo/manifests/ >> >> /https://review.opendev.org/#/c/681914/1/ >> >> /repo init -m compile.xml/ >> >> /repo sync/ >> >> /apply these to patch/ >> >> /https://review.opendev.org/#/c/681821/1/ >> >> /https://review.opendev.org/#/c/681828/1/ >> >> /./download_mirror.sh  -n -g -l flock -c >> config/centos/compiler/yum.conf.sample -S / >> >> /./toCopy/generate-cgts-centos-repo >> output/stx-r1/CentOS/pike// >> >> /build-pkgs/ >> >> /build-iso/ >> >> BR! >> >> Martin, Chen >> >> SSP, Software Engineer >> >> 021-61164330 >> >> -----Original Message----- >> From: Scott Little >> >> Sent: Thursday, September 19, 2019 9:54 PM >> To: Chen, Haochuan Z >> >> Subject: Re: FW: [Starlingx-discuss] [Build] Build layering >> reviews >> >> Most of the required changes were already merged. >> >> I'll scan the spec when time permits to see if I missed anything. >> >> Scott >> >> On 2019-09-16 12:01 p.m., Chen, Haochuan Z wrote: >> >> > Hi Scott >> >> > >> >> > I read your patch for build layering, but could not find >> patch for build script. >> >> > >> >> > Description in spec >> https://review.opendev.org/#/c/672288/12/ >> >> > Modifications to package build scripts ... build-pkgs, >> >> > build-srpms-parallel, build-srpms-serial, >> build-rpms-parallel, build-rpms-serial (cgcs-root): >> >> > >> >> > Thanks >> >> > >> >> > Martin, Chen >> >> > SSP, Software Engineer >> >> > 021-61164330 >> >> > >> >> > -----Original Message----- >> >> > From: Xie, Cindy >> >> > Sent: Friday, September 13, 2019 12:24 PM >> >> > To: Chen, Haochuan Z > > >> >> > Cc: Hu, Yong > >> >> > Subject: FW: [Starlingx-discuss] [Build] Build layering >> reviews >> >> > >> >> > Martin, >> >> > I am wondering if you will be interested to working on this >> task. To me, having layering build and provide efficiency to >> developers are very important for StarlingX. It also provide a >> chance that you and work together w/ WR folks being more close >> collaboration. Let me know your interested level. >> >> > >> >> > Thx. -cindy >> >> > >> >> > -----Original Message----- >> >> > From: Scott Little > > >> >> > Sent: Friday, September 13, 2019 4:55 AM >> >> > To: starlingx-discuss at lists.starlingx.io >> >> >> > Subject: [Starlingx-discuss] [Build] Build layering reviews >> >> > >> >> > My prototype code for the layered build has been posted to >> gerrit. >> >> > (listed below) >> >> > >> >> > I was briefly able to build all layers, and produce an iso >> with the same package content as the cengn build.  Then I was >> diverted by non-trivial changes to the restructuring work. What >> I have posted is now several weeks out of date and will almost >> certainly will not work.  The devil is in keeping the lst files >> in sync with the ever changing master branch. >> >> > >> >> > Other commitments will prevent me from resuming this work >> until November.  If anyone wants to whip the lst files into >> shape and try to get the build working again, be my guest. >> >> > >> >> > Final delivery will require changes to the CENGN build >> scripts (Don or Myself), and a freeze on packaging changes will >> likely be required for aprox 3 days to finalize the lst files. >> >> > >> >> > Scott >> >> > >> >> > ---------------- ---------------- >> >> > >> >> > https://review.opendev.org/#/c/681821/1 >> >> > >> >> > https://review.opendev.org/#/c/681914/1 >> >> > >> >> > https://review.opendev.org/#/c/681823/1 >> >> > >> >> > https://review.opendev.org/#/c/681824/1 >> >> > >> >> > https://review.opendev.org/#/c/681828/1 >> >> > >> >> > https://review.opendev.org/#/c/681832/2 >> >> > >> >> > https://review.opendev.org/#/c/681834/1 >> >> > >> >> > https://review.opendev.org/#/c/681836/1 >> >> > >> >> > https://review.opendev.org/#/c/681835/1 >> >> > >> >> > https://review.opendev.org/#/c/681842/1 >> >> > >> >> > https://review.opendev.org/#/c/681847/1 >> >> > >> >> > https://review.opendev.org/#/c/681848/1 >> >> > >> >> > https://review.opendev.org/#/c/681851/1 >> >> > >> >> > https://review.opendev.org/#/c/681852/1 >> >> > >> >> > https://review.opendev.org/#/c/681854/1 >> >> > >> >> > https://review.opendev.org/#/c/681856/1 >> >> > >> >> > https://review.opendev.org/#/c/681890/1 >> >> > >> >> > https://review.opendev.org/#/c/681892/1 >> >> > >> >> > https://review.opendev.org/#/c/681892/1 >> >> > >> >> > https://review.opendev.org/#/c/681898/1 >> >> > >> >> > https://review.opendev.org/#/c/681900/1 >> >> > >> >> > https://review.opendev.org/#/c/681901/1 >> >> > >> >> > https://review.opendev.org/#/c/681902/1 >> >> > >> >> > >> >> > >> >> > >> >> > _______________________________________________ >> >> > 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 haochuan.z.chen at intel.com Tue Oct 22 02:47:54 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 22 Oct 2019 02:47:54 +0000 Subject: [Starlingx-discuss] FW: [Build] Build layering reviews In-Reply-To: References: <58efa3fb-9958-4af1-27f4-21db5a90da19@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856264A3B@CDSMSX102.ccr.corp.intel.com> <59676767-1870-b9a4-d256-77ff3a4148c8@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856265D08@CDSMSX102.ccr.corp.intel.com> <157958eb-6c13-318c-b087-a3d6b8a68662@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856266584@CDSMSX102.ccr.corp.intel.com> <92bad81a-e05f-6e1d-d83f-71263c01f29f@windriver.com> <56829C2A36C2E542B0CCB9854828E4D85626690A@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D85626EE06@CDSMSX102.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC158F833@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D856271BE0@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D856272C86@CDSMSX102.ccr.corp.intel.com> <1d6bf23c-0eaa-56dc-8154-bfb39a3be25e@linux.intel.com> <56829C2A36C2E542B0CCB9854828E4D856272E59@CDSMSX102.ccr.corp.intel.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D856272F74@CDSMSX102.ccr.corp.intel.com> Hi saul When do you do a repo sync? Also, when you do a repo sync, the default.xml will contain the current HEAD not any of your changes to tools or to the root area. You need a manifest that has all the revisions set to the reviews. >> Yes, after "repo init", should use "repo sync" to sync code. And in commit message, that's the guide for build, after patch merged. To apply these patch by write a script with "repo download" https://source.android.com/setup/develop/repo BR! Martin, Chen SSP, Software Engineer 021-61164330 -----Original Message----- From: Saul Wold Sent: Tuesday, October 22, 2019 10:34 AM To: Chen, Haochuan Z ; 'Penney, Don' ; 'Bailey, Henry Albert (Al)' ; 'Little, Scott' ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] FW: [Build] Build layering reviews On 10/21/19 6:58 PM, Chen, Haochuan Z wrote: > Hi Saul > > What's your error or missing? I could check for you. > > To verify, there are several cases and step. You should ready commit > message in https://review.opendev.org/#/c/681821/ > > Case1, build all source code, this is same as currently building > 1, sync code > $ repo init -u https://opendev.org/starlingx/manifest.git -m > default.xml > When do you do a repo sync? Also, when you do a repo sync, the default.xml will contain the current HEAD not any of your changes to tools or to the root area. You need a manifest that has all the revisions set to the reviews. I will post something for testing shortly. Sau! > 2, download rpm for flock layer > $ ./download_mirror.sh -n -g -c yum.conf.sample -S > > 3, copy the downloaded to mirror folder, such as > /import/mirrors/starlingx > > 4, create repo named "StxCentos7Distro" for building > $ ./generate-cgcs-centos-repo.sh /import/mirrors/starlingx > $ ./populate_downloads.sh /import/mirrors/starlingx > > Deploy with build iso and helm-chart > > > Case2, build layer by layer > Compile layer > 1, sync code for compile layer > $ repo init -u https://opendev.org/starlingx/manifest.git -m > compile.xml > > 2, download rpm for flock layer > $ ./download_mirror.sh -n -g -l compile -c yum.conf.sample -S > There has to be some missing steps. > 3, copy the downloaded to mirror folder, such as > /import/mirrors/starlingx > > 4, create repo named "StxCentos7Distro" for building > $ ./generate-cgcs-centos-repo.sh --layer=compile /import/mirrors/starlingx > $ ./populate_downloads.sh /import/mirrors/starlingx > > 5, rpm package > $ build-pkgs > > 6, create file for distro and compile layer build > $ cd $MY_WORKSPACE > $ cat std/image.inc rt/image.inc >> centos_compile_iso_image.inc > $ ls std/rpmbuild/RPMS/ rt/rpmbuild/RPMS/ -l | awk > '/tis\..*\.rpm/ {print $9}' > tis_pkg.lst > > Distro layer > Before distro and flock layer building, must create a repo locally, as cenga is not update now. > Edit > stx-tools/centos-mirror-tools/config/centos/distro/required_build_tis_ > pkg.cfg Uncomment this line, and update with your compile layer build > output folder > #compile,file:///localdisk/loadbuild/martin/starlingx/tis_pkg.lst > > 1, sync code for compile layer > $ repo init -u https://opendev.org/starlingx/manifest.git -m > distro.xml > > 2, download rpm for flock layer > $ ./download_mirror.sh -n -g -l distro -c yum.conf.sample -S > > 3, copy the downloaded to mirror folder, such as > /import/mirrors/starlingx > > 4, create repo named "StxCentos7Distro" for building > $ ./generate-cgcs-centos-repo.sh --layer=compile /import/mirrors/starlingx > $ ./populate_downloads.sh /import/mirrors/starlingx > > 5, rpm package > $ build-pkgs > > 6, create file for distro layer build > $ cd $MY_WORKSPACE > $ cat std/image.inc rt/image.inc >> centos_distro_iso_image.inc > $ ls std/rpmbuild/RPMS/ rt/rpmbuild/RPMS/ -l | awk > '/tis\..*\.rpm/ {print $9}' > tis_pkg.lst > > Flock layer > Edit > stx-tools/centos-mirror-tools/config/centos/flock/required_build_tis_p > kg.cfg Uncomment these two line, and update with your distro layer > build output folder > #compile,file:///localdisk/loadbuild/martin/starlingx/tis_pkg.lst > #distro,file:///localdisk/loadbuild/martin/distro/tis_pkg.lst > > 1, sync code for flock layer > $ repo init -u https://opendev.org/starlingx/manifest.git -m > flock.xml > > 2, download rpm for flock layer > $ ./download_mirror.sh -n -g -l flock -c yum.conf.sample -S > > 3, copy the downloaded to mirror folder, such as > /import/mirrors/starlingx > > 4, create repo named "StxCentos7Distro" for building > $ ./generate-cgcs-centos-repo.sh --layer=flock /import/mirrors/starlingx > $ ./populate_downloads.sh /import/mirrors/starlingx > > 5, rpm package and iso building > $ build-pks && build-iso && build-helm-charts.sh > > Deploy with build iso and helm-chart > > Two case must build and deploy succeed. > > BR! > > Martin, Chen > SSP, Software Engineer > 021-61164330 > > -----Original Message----- > From: Saul Wold > Sent: Tuesday, October 22, 2019 7:32 AM > To: Chen, Haochuan Z ; 'Penney, Don' > ; 'Bailey, Henry Albert (Al)' > ; 'Little, Scott' > ; 'starlingx-discuss at lists.starlingx.io' > > Subject: Re: [Starlingx-discuss] FW: [Build] Build layering reviews > > Martin, > > I am still wondering how your testing this, if you have a completely updated manifest that points to all the updated gerrit reviews? > > As I mentioned in some reviews earlier I was having issues with building due to missing files. > > On 10/21/19 7:20 AM, Chen, Haochuan Z wrote: >> Hi >> >> I have update patch again. Last week, I raise this concern// >> >> 3, update script download_mirror.sh and generate-cgts-centos-repo >> >> Currently all rpm name in lst is listed with fixed rpm version, which >> makes layer build easily to be corrupted. For example, any time >> TIS_PATCH_VER in build_srpm.data update, rpm name in lst should be updated. >> >> Prefer rpm named with “tis” should be query candidate on cenga, which >> request download_mirror.sh and generate-cgts-centos-repo update. >> Prefer we could finish such update in this story, as I think this is >> a critical issue. >> >> So I update patch in stx-tools again to fix this issue. You can check >> download_mirror.sh >> >> I add a step to generate rpm_tis.lst for layer build case. In such >> case, it will download tis_pkg.lst from cenga. What listed in >> tis_pkg.lst is distro or compile layer’s built rpm with named xxx.tis.xxx.rpm. >> >> So no matter src rpm or tarball upgrade, rpm_centos3party.lst is >> unnecessary to update. >> >> And I update build-iso, image.inc should concatenate with distro and >> compile layer’s image.in. As image.inc not only for install package, >> but also request for generate comps.xml. >> >> Please check my update and review my patch >> > I am looking at this patch and doing some testing. > > Sau! > >> Thanks! >> >> Martin, Chen >> >> SSP, Software Engineer >> >> 021-61164330 >> >> *From:*Chen, Haochuan Z >> *Sent:* Tuesday, October 15, 2019 10:27 PM >> *To:* Penney, Don ; Bailey, Henry Albert >> (Al) ; Little, Scott >> ; 'starlingx-discuss at lists.starlingx.io' >> >> *Subject:* RE: [Starlingx-discuss] FW: [Build] Build layering reviews >> >> Hi >> >> I have updated patch for layer build >> >> https://review.opendev.org/#/c/681821/ >> >> https://review.opendev.org/#/c/681823/ >> >> https://review.opendev.org/#/c/681824/ >> >> https://review.opendev.org/#/c/681828/ >> >> https://review.opendev.org/#/c/681832/ >> >> https://review.opendev.org/#/c/681834/ >> >> https://review.opendev.org/#/c/681835/ >> >> https://review.opendev.org/#/c/681836/ >> >> https://review.opendev.org/#/c/681842/ >> >> https://review.opendev.org/#/c/681847/ >> >> https://review.opendev.org/#/c/681848/ >> >> https://review.opendev.org/#/c/681851/ >> >> https://review.opendev.org/#/c/681852/ >> >> https://review.opendev.org/#/c/681854/ >> >> https://review.opendev.org/#/c/681856/ >> >> https://review.opendev.org/#/c/681890/ >> >> https://review.opendev.org/#/c/681892/ >> >> https://review.opendev.org/#/c/681894/ >> >> https://review.opendev.org/#/c/681898/ >> >> https://review.opendev.org/#/c/681900/ >> >> https://review.opendev.org/#/c/681901/ >> >> https://review.opendev.org/#/c/681902/ >> >> https://review.opendev.org/#/c/681914/ >> >> https://review.opendev.org/#/c/688598/ >> >> And I think we still left three issue. >> >> 1, request build-tools/build_iso/centos_required_build_layer.cfg >> >> Current for self validation, we could add a file with such content. >> But we should create a file depending on cenga update >> >> compile,file:///localdisk/loadbuild/martin/starlingx/centos_compile_i >> s >> o_image.inc >> >> distro,file:///localdisk/loadbuild/martin/distro/centos_distro_iso_im >> a >> ge.inc >> >> flock,file:///localdisk/loadbuild/martin/flock/centos_flock_iso_image. >> inc >> >> 2, propose use one copy of yum.conf.sample and yum.repo.d/* >> >> Currently there is 4 copies of yum.conf.sample and yum.repo.d/*.  3 >> copies in stx-tools/centos-mirror-tools/config/centos// and 1 >> copy in stx-tools/centos-mirror-tools/ >> >>   Propose to remove 3 copies in >> stx-tools/centos-mirror-tools/config/centos//. To avoid user >> confusing >> >> 3, update script download_mirror.sh and generate-cgts-centos-repo >> >> Currently all rpm name in lst is listed with fixed rpm version, which >> makes layer build easily to be corrupted. For example, any time >> TIS_PATCH_VER in build_srpm.data update, rpm name in lst should be updated. >> >> Prefer rpm named with “tis” should be query candidate on cenga, which >> request download_mirror.sh and generate-cgts-centos-repo update. >> Prefer we could finish such update in this story, as I think this is >> a critical issue. >> >> Thanks! >> >> Martin, Chen >> >> SSP, Software Engineer >> >> 021-61164330 >> >> *From:*Penney, Don > > >> *Sent:* Monday, September 30, 2019 11:33 PM >> *To:* Bailey, Henry Albert (Al) > >; Chen, Haochuan Z >> >; >> Little, Scott > >; >> 'starlingx-discuss at lists.starlingx.io' >> > > >> *Subject:* RE: [Starlingx-discuss] FW: [Build] Build layering reviews >> >> Is this the issue? >> >> openstack/python-horizon/centos/python-django-horizon.spec:BuildRequi >> r >> es: cgts-client >> >> I don’t see anything in this package that should need this >> dependency, and it should be safe to remove it. >> >> *From:*Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] >> *Sent:* Monday, September 30, 2019 10:56 AM >> *To:* Chen, Haochuan Z; Little, Scott; >> 'starlingx-discuss at lists.starlingx.io' >> *Subject:* Re: [Starlingx-discuss] FW: [Build] Build layering reviews >> >> I think Cgts-client  (renamed to system-client)  should be in its own repo. >> >> Al >> >> *From:*Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] >> *Sent:* Monday, September 30, 2019 2:06 AM >> *To:* Little, Scott; 'starlingx-discuss at lists.starlingx.io' >> *Subject:* Re: [Starlingx-discuss] FW: [Build] Build layering reviews >> >> Hi Scott >> >> I think have some question or concern. >> >> 1, I find distro layer has dependency to cgts-client, as there is a >> addin for Horizon, which enables look up flock service info in Horizon. >> >> So there is task is must for layer building, which is out of my >> expectation.  I begin to tackle these task. >> >> ·Relocate from git 'config', subdir 'sysinv/cgts-client', to git >> 'utilities', subdir 'system-client', *with full git history.* >> >> ·Rename rpm package from 'cgts-client' to 'system-client' >> >> ·Fix rpm packages that list cgts-client as a require or build require >> >> ·Rename python module from 'cgts-client' to 'system-client' >> >> ·Scan function names and/or variables for any that contain 'cgts' ... >> replace with 'system' ... can we do this in a backward compatible way? >> >> ·Fix users of the client to import using the new name, and reference >> any renamed functions/data. >> >> ·Fix ISO and/or docker images that list this package for inclusion. >> >> 2, “all” layer maybe doesn’t work, warning! >> >> For current patch for generate-cgts-centos-repo.sh, all layer’s >> rpms_lst_file is generated by merge “compiler/distro/flock” three >> layers, config/centos/all doesn’t be referenced, which is none sense. >> Which means package such bash-4.2.46-31.el7.tis.4.x86_64.rpm, named >> with “tis” is also in mirror. This maybe interference source package >> building. I think request some fix in generate-cgts-centos-repo.sh to >> omit package with “tis” in name. >> >> 3, Layered build introduces rpms_cemtos.lst dependency on >> TIS_PATCH_VER in build_srpm.data, which make developer easily disrupt >> layered building mechanism. >> >> For distro and flock layer, it has dependency to starlingX customized >> package, for example, distro layer require bash.tis.> version>..rpm, which will be add in >> config/centos/distro/rpms_centos3rdparty.lst >> >> If new developer forget to update and build all package, it maybe >> disrupt layered building. >> >> BR! >> >> Martin, Chen >> >> SSP, Software Engineer >> >> 021-61164330 >> >> *From:*Chen, Haochuan Z >> *Sent:* Friday, September 27, 2019 4:40 PM >> *To:* Scott Little > >; >> starlingx-discuss at lists.starlingx.io >> >> *Subject:* RE: FW: [Starlingx-discuss] [Build] Build layering reviews >> >> Thanks, Scott. I have studied so much. >> >> BR! >> >> Martin, Chen >> >> SSP, Software Engineer >> >> 021-61164330 >> >> *From:*Scott Little > > >> *Sent:* Thursday, September 26, 2019 11:39 PM >> *To:* Chen, Haochuan Z > >; >> starlingx-discuss at lists.starlingx.io >> >> *Subject:* Re: FW: [Starlingx-discuss] [Build] Build layering reviews >> >> Returning this discussion to the mailing list. >> >> If possible, join the Build call next week. >> https://wiki.openstack.org/wiki/Starlingx/Meetings >> >> 1) >> >> When mock installs for the first time. it uses rpms that have been >> download via lst file. The mock pseudo-layer lst files capture >> reflect the rpms needed by mock.  The mock lst's are merged with the >> layers lst's.  In this way, the mock rpms don't have to be listed in >> each and every layer's lst. >> >> 2) >> >> Adding tools to generate an lst file reflacting the output of a build >> layer, and adding that lst for consumprion by higher layers, is >> indeed a possibility possibility I wanted to persue.  Reference to >> that output lst could then be added to as a new arg to the download >> script when invoked by a higher layer, or a config file could specify >> where to find it (cengn is the likely default supplier). >> >> compile layer) >> >> The compile layer is a true layer, built prior to the distro layer. >> Only a few build related packages go here.  Compilers, language >> interpreters, rpm.  I wanted those packages in place so that all >> distro layer packages build with the same tools. >> >> Scott >> >> On 2019-09-25 10:24 p.m., Chen, Haochuan Z wrote: >> >> Still not clear about mock layer. >> >> 1, In build container, mock is already installed, why request to >> download mock required package firstly? >> >> 2, To build distro or flock layer, we could add compile layer’s tis >> rpm in distro and flock layer’s lst file. By download compile >> layer’s binary in mirror, it could also ensure user building package >> with same tool. >> >> Why introduces compile layer? >> >> Thanks! >> >> Martin, Chen >> >> SSP, Software Engineer >> >> 021-61164330 >> >> *From:*Scott Little >> >> *Sent:* Thursday, September 26, 2019 12:25 AM >> *To:* Chen, Haochuan Z >> >> *Subject:* Re: FW: [Starlingx-discuss] [Build] Build layering >> reviews >> >> See inline ... >> >> Scott >> >> On 2019-09-23 11:00 a.m., Chen, Haochuan Z wrote: >> >> Hi Scott >> >> I studied your patch and some questions. >> >> 1, why there is mock and compile layer, what's usage or >> intention for these two layers? >> >> Build-pkgs uses a tool called mock to create a reproducible >> compilation sandbox.  It is chroot like environmnet into which rpms >> are installed to construct a minimal build environment. >> >> The mock layer is not built.  I created it as a placeholder for the >> lst files that downloads all the rpms that mock requires.  Prior to >> building a layer, the lst files for both the layer being build, and >> the mock pseudo layer, need to be processed. Without the mock pseudo >> layer, we would have to replicate that list of mock required rpms in >> each and ever layer's lst files. >> >> The concept ran into a bit of trouble because some of the rpms >> needed by mock are themselves built by the compile or distro layers >> (with a newer revision).   So the >> mock pseudo layer might actually omit those rpms from it's lst file, >> and they needed to be listed in the layer lst files instead. >> >> The compile layer is a true layer, built prior to the distro layer. >> Only a few build related packages go here.  Compilers, language >> interpreters, rpm.  I wanted those packages in place so that all >> distro layer packages build with the same tools. >> >> 2, for download_mirror.sh, it generate rpm list by merge file in >> config/centos// and rpm list file in >> stx/ >> >>    But for generate-cgcs-centos-repo.sh, it use rpm list file >> in centos-mirror-tools folder. Rpm package should be added in >> two rpm list file. >> >>    It is not good for maintenance. What about remove rpm list >> file in centos-mirror-tools folder >> >> /rpms_centos.lst/rpms_centos3rdparties.lst/rpms_3rdparties.lst/other_downloads.lst/ >> tarball-dl.lst/ >> >> That was considered and debated. The concern was that the many git >> repos that make up the layer would list different versions of the >> same package.  Then what do we do?  Throw an error?  Silently use >> the newest package?  So we elected to keep binary rpms needed to >> satisfy dependencies listed in a central place. >> >> At some point we may want to explore allowing lst files specify >> required package but not version (beyond a possible minimum version) >> when on the master branch, and have a way to 'lock down' the >> versions only for a release branch. >> >> 3, Question about setup yum repo for rpm tailing with “tis” such >> as xxx.*tis*.x86_64.rpm or xxx.*tis*.noarch.rpm >> >> In this patch https://review.opendev.org/#/c/681821/1 >> >> /There is such line in >> >> config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo/ >> >> /[Starlingx-cengn_distro_layer]/ >> >> /name=Starlingx-cengn_distro_layer/ >> >> >> /baseurl=http://127.0.0.1:8088/localdisk/loadbuild//*/slittle1/restru >> c >> ture3b/*//std/rpmbuild/RPMS// >> >> /enabled=1/ >> >> /[Starlingx-cengn_distro_layer-rt]/ >> >> /name=Starlingx-cengn_distro_layer/ >> >> >> /baseurl=http://127.0.0.1:8088/localdisk/loadbuild//*/slittle1/restru >> c >> ture3b/*//rt/rpmbuild/RPMS// >> >> /enabled=1/ >> >> also in >> >> >> config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo >> >> >> config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo >> >> My understanding is rpm tailing with “tis” should also upload to >> cengn, rpm name listed in >> >> centos-mirror-tools/config/centos/flock/rpms_centos3rdparties.lst >> >> So these three files should be unnecessary, with cengn update >> for layered build. >> >> >> config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo >> >> >> config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo >> >> >> config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo >> >> For development testing, I had to hack together a simulated cengn by >> running lighttpd on 127.0.0.1:8088 and allowing it to serve up files >> from builds of lower layers >> >> restructure3a == layer-comiler layer build >> >> restructure3b == layer-distro layer build >> >> restructure3c == layer-flock layer build  (although there shouldn't >> be a repo entry referring to that one) >> >> Finalizing the repo entries would have to wait until cengn was up an >> running. >> >> 4, In generate-cgcs-centos-repo.sh there is --layer-dir, and >> such content in your patch commit message >> >> /generate-cgcs-centos-repo.sh \/ >> >> /--layer-dir=/localdisk/loadbuild/slittle1/layer-compile/std/rpmbuild/RPMS/ >> \/ >> >> /--layer-dir=/localdisk/loadbuild/slittle1/layer-distro/std/rpmbuild/RPMS/ >> \/ >> >> /--layer-dir=/localdisk/loadbuild/slittle1/layer-distro/rt/rpmbuild/RPMS/ >> \/ >> >> //import/mirrors/starlingx/ >> >>    For all rpm download from cengn, --layer-dir is unnecessary >> to generate link, correct? >> >> This is another way to do cross layer development testing without >> support from cengn.  Again the goal is to allow an upper layer build >> to download rpms from a lower layer build on the same machine. >> >> 5, could you share >> build-tools/build-iso/centos_required_build_layer.cfg, share >> to me >> >> Did that not get published in my reviews?  Content is very simple. >> >> compile,file:///localdisk/loadbuild/slittle1/restructure3a/centos_compile_iso_image.inc >> >> distro,file:///localdisk/loadbuild/slittle1/restructure3b/centos_distro_iso_image.inc >> >> >> flock,file:///localdisk/loadbuild/slittle1/restructure3c/centos_flock >> _iso_image.inc >> >> > m >> age.inc> >> >> 6, For distro/compiler/flock, all are separate layer? >> >> Yes >> >> My current step >> >> /repo init -u https://opendev.org/starlingx/manifest.git/ >> >> /apply this patch to .repo/manifests/ >> >> /https://review.opendev.org/#/c/681914/1/ >> >> /repo init -m compile.xml/ >> >> /repo sync/ >> >> /apply these to patch/ >> >> /https://review.opendev.org/#/c/681821/1/ >> >> /https://review.opendev.org/#/c/681828/1/ >> >> /./download_mirror.sh  -n -g -l flock -c >> config/centos/compiler/yum.conf.sample -S / >> >> /./toCopy/generate-cgts-centos-repo >> output/stx-r1/CentOS/pike// >> >> /build-pkgs/ >> >> /build-iso/ >> >> BR! >> >> Martin, Chen >> >> SSP, Software Engineer >> >> 021-61164330 >> >> -----Original Message----- >> From: Scott Little >> >> Sent: Thursday, September 19, 2019 9:54 PM >> To: Chen, Haochuan Z >> >> Subject: Re: FW: [Starlingx-discuss] [Build] Build layering >> reviews >> >> Most of the required changes were already merged. >> >> I'll scan the spec when time permits to see if I missed anything. >> >> Scott >> >> On 2019-09-16 12:01 p.m., Chen, Haochuan Z wrote: >> >> > Hi Scott >> >> > >> >> > I read your patch for build layering, but could not find >> patch for build script. >> >> > >> >> > Description in spec >> https://review.opendev.org/#/c/672288/12/ >> >> > Modifications to package build scripts ... build-pkgs, >> >> > build-srpms-parallel, build-srpms-serial, >> build-rpms-parallel, build-rpms-serial (cgcs-root): >> >> > >> >> > Thanks >> >> > >> >> > Martin, Chen >> >> > SSP, Software Engineer >> >> > 021-61164330 >> >> > >> >> > -----Original Message----- >> >> > From: Xie, Cindy >> >> > Sent: Friday, September 13, 2019 12:24 PM >> >> > To: Chen, Haochuan Z > > >> >> > Cc: Hu, Yong > > >> >> > Subject: FW: [Starlingx-discuss] [Build] Build layering >> reviews >> >> > >> >> > Martin, >> >> > I am wondering if you will be interested to working on this >> task. To me, having layering build and provide efficiency to >> developers are very important for StarlingX. It also provide a >> chance that you and work together w/ WR folks being more close >> collaboration. Let me know your interested level. >> >> > >> >> > Thx. -cindy >> >> > >> >> > -----Original Message----- >> >> > From: Scott Little > > >> >> > Sent: Friday, September 13, 2019 4:55 AM >> >> > To: starlingx-discuss at lists.starlingx.io >> >> >> > Subject: [Starlingx-discuss] [Build] Build layering >> reviews >> >> > >> >> > My prototype code for the layered build has been posted to >> gerrit. >> >> > (listed below) >> >> > >> >> > I was briefly able to build all layers, and produce an iso >> with the same package content as the cengn build.  Then I was >> diverted by non-trivial changes to the restructuring work. What >> I have posted is now several weeks out of date and will almost >> certainly will not work.  The devil is in keeping the lst files >> in sync with the ever changing master branch. >> >> > >> >> > Other commitments will prevent me from resuming this work >> until November.  If anyone wants to whip the lst files into >> shape and try to get the build working again, be my guest. >> >> > >> >> > Final delivery will require changes to the CENGN build >> scripts (Don or Myself), and a freeze on packaging changes will >> likely be required for aprox 3 days to finalize the lst files. >> >> > >> >> > Scott >> >> > >> >> > ---------------- ---------------- >> >> > >> >> > https://review.opendev.org/#/c/681821/1 >> >> > >> >> > https://review.opendev.org/#/c/681914/1 >> >> > >> >> > https://review.opendev.org/#/c/681823/1 >> >> > >> >> > https://review.opendev.org/#/c/681824/1 >> >> > >> >> > https://review.opendev.org/#/c/681828/1 >> >> > >> >> > https://review.opendev.org/#/c/681832/2 >> >> > >> >> > https://review.opendev.org/#/c/681834/1 >> >> > >> >> > https://review.opendev.org/#/c/681836/1 >> >> > >> >> > https://review.opendev.org/#/c/681835/1 >> >> > >> >> > https://review.opendev.org/#/c/681842/1 >> >> > >> >> > https://review.opendev.org/#/c/681847/1 >> >> > >> >> > https://review.opendev.org/#/c/681848/1 >> >> > >> >> > https://review.opendev.org/#/c/681851/1 >> >> > >> >> > https://review.opendev.org/#/c/681852/1 >> >> > >> >> > https://review.opendev.org/#/c/681854/1 >> >> > >> >> > https://review.opendev.org/#/c/681856/1 >> >> > >> >> > https://review.opendev.org/#/c/681890/1 >> >> > >> >> > https://review.opendev.org/#/c/681892/1 >> >> > >> >> > https://review.opendev.org/#/c/681892/1 >> >> > >> >> > https://review.opendev.org/#/c/681898/1 >> >> > >> >> > https://review.opendev.org/#/c/681900/1 >> >> > >> >> > https://review.opendev.org/#/c/681901/1 >> >> > >> >> > https://review.opendev.org/#/c/681902/1 >> >> > >> >> > >> >> > >> >> > >> >> > _______________________________________________ >> >> > 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 Tue Oct 22 06:14:45 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 22 Oct 2019 06:14:45 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting In-Reply-To: <9700A18779F35F49AF027300A49E7C76608D847F@SHSMSX105.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C76608D7CA6@SHSMSX105.ccr.corp.intel.com> <2588653EBDFFA34B982FAF00F1B4844EC26ED58D@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C76608D847F@SHSMSX105.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C76608D8863@SHSMSX105.ccr.corp.intel.com> Hi all, Here is the latest test status for kata integration in StarlingX. 1. Pass Sanity test for AIO-SX/AIO-DX/Multi/Multi+Storage. 2. Tested private registry (insecure registry) enabled/disabled. 3. Tested docker proxy enabled/disabled. 4. Tested swact/lock & unlock/remove & apply application. 5. Tested local registry (registry.local:9001) with image pull/push, and access both from kubernetes and crictl (CLI). For regression test, I checked container related test cases in below doc, and executed most of them. No issue is found yet. https://docs.google.com/spreadsheets/d/1dwcBwY4Yq1Lo9Der4RylzQ6KYp0BsMHohhEmhwpauDo/edit?usp=sharing Currently, I meet a deploy issue with IPv6 environment, and the issue could be reproduced with master daily build also. I am checking whether it is caused by my environment or a real issue of master now. Here is the patch list waiting review: https://review.opendev.org/#/q/topic:kata+(status:open) Best Regards Shuicheng From: Lin, Shuicheng Sent: Monday, October 21, 2019 11:17 AM To: Rowsell, Brent ; Miller, Frank ; starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: RE: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting Hi Brent, [BR] What is the plan to remove dockerd ? [Shuicheng] We need switch armada to run with containerd first, then we should be able to remove dockerd. Task 37231 is created to track it under the same story[0]. Task 36981 is for switch armada to run with containerd. I prefer to do both task in later stage. [0]: https://storyboard.openstack.org/#!/story/2006145 Best Regards Shuicheng From: Rowsell, Brent > Sent: Friday, October 18, 2019 9:20 PM To: Lin, Shuicheng >; Miller, Frank >; starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: RE: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting Thanks. See inline Brent From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, October 17, 2019 9:00 AM To: Miller, Frank >; Rowsell, Brent >; starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: RE: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting Hi Frank & Brent & all, I have updated my patches to remove the visible password for registry. Please help review the update in ansible-playbooks/stx-puppet. Here is the link for the patch list: https://review.opendev.org/#/q/topic:kata+(status:open) - Add a commit to make containerd the default CLI (and remove any docker code that is no longer needed) [shuicheng] do you mean change the "/var/lib/docker" directory to "/var/lib/containerd" for both docker and containerd? If the answer is yes, I prefer to do it later, after docker runtime is not used at all. Currently, armada is still using docker. - Add a test case for local registry pull/push and authentication [BR] What is the plan to remove dockerd ? [Shuicheng] No plan yet. We need switch armada to run with containerd first, then we should be able to remove dockerd. Task 37231 is created to track it under the same story[0]. Task 36981 is for switch armada to run with containerd. [shuicheng] With the new patch, local registry still could be accessed both by Kubernetes and crictl. For crictl, username/password need be provided in CLI, similar to "docker login" for docker CLI. - Update code to ensure admin password is not visible [shuicheng] Done. Best Regards Shuicheng From: Miller, Frank > Sent: Tuesday, October 15, 2019 10:16 PM To: starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting Since we did not get through the whole agenda today, I will schedule the next meeting 1 week from today. Minutes for Oct 15 meeting: 1. Review KATA containers feature with container Cores. Shuicheng to present feature overview and current status. - Shuicheng's commits: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) - Shuicheng presented his feature and what has been done so far (see his charts in separate email) Actions identified: - Concerns: Interaction with registry, admin password is visible - Add a commit to make containerd the default CLI (and remove any docker code that is no longer needed) - Add a test case for local registry pull/push and authentication - Update code to ensure admin password is not visible - Frank to book a follow-up meeting to continue the review (Frank to book Tuesday Oct 22) Frank -----Original Appointment----- From: Miller, Frank Sent: Thursday, October 10, 2019 2:55 PM To: Miller, Frank; starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: StarlingX Bi-Weekly Containerization Meeting When: Tuesday, October 15, 2019 9:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236 Apologies, re-sending without etherpad formatting. Note: We agreed to a new day and time for these meetings. For all who are working containerization features or LPs please join for our bi-weekly meeting. Agenda for October 15 meeting: 1. Review KATA containers feature with container Cores. Shuicheng to present feature overview and current status. - Shuicheng's commits: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) 2. Updates on other stx.3.0 container features for MS3 milestone: - 2004008: [Feature] Create HELM chart for Fault project [An Ran] - one commit needs a new approach - discussed in item #2 - Decision to be made about Horizon issue - do we keep FM containers enabled without Horizon for VM alarms? Or do we disable in stx.3.0 until issue can be addressed in stx.4.0? - 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] - require updated forecast - 2005514: QAT K8S device plugin support in StarlingX - Bruce: Code is out for review; Frank to follow-up with Cindy or feature primes for updated forecasts - 2005860: Upversion container components [Al Bailey] - 2004761: Integrate Backup & Restore with Containers [Ovidiu Poncea] 3. Update on stx.4.0 features: - 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC 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 Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Tue Oct 22 13:05:16 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 22 Oct 2019 13:05:16 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F3608F98F@SHSMSX104.ccr.corp.intel.com> Agenda for 10/23 meeting: - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade planning (Shuai Zhao) - CVE LP fixing - call for contribution (Cindy) - Opens (all) Cindy Xie -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W; Sun, Austin Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, October 23, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . 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 From bruce.e.jones at intel.com Tue Oct 22 13:33:48 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 22 Oct 2019 13:33:48 +0000 Subject: [Starlingx-discuss] Openstack-distro meeting minutes Oct 22 2019 Message-ID: <9A85D2917C58154C960D95352B22818BDFBFB77F@fmsmsx123.amr.corp.intel.com> 10/22/2019 * Train upgrade only for the containerized services * Eng build failing Sanity testing failed in 4 configs during provisioning. On bare metal only during Sanity :( * 12 functional tests have been run (of 48) for network tests and they all pass (so far) on virtual. remaining tests need BM env. * Zhipeng tested on BM several times and saw one failure. ? Please send out logs to the mailing list! * ============================================================================== * Provision :: Tests for provisioning and unlocking controllers, computes and * ============================================================================== * Provisioning Standard Storage System :: Validates provisioning of ... | FAIL | * Maximum limit of started keywords exceeded. * 6 patches submitted for review, your comments are appreciated, thanks! ? https://review.opendev.org/#/c/683886/ ? https://review.opendev.org/#/c/683910/ ? https://review.opendev.org/#/c/684166/ ? https://review.opendev.org/#/c/687441/ ? https://review.opendev.org/#/c/687197/ ? https://review.opendev.org/#/c/688105/ * Zhipeng please add Saul and Don Penney to this review * Need a volunteer - someone to add the "starlingX/upstream" repo to the governance/reference/tsc/projects.yaml under the openstack-distro project. * Ya Wang will take this. Thank you! * Defects open: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack * 1841189: Bruce to ping Forrest and Gongjun -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Tue Oct 22 14:08:42 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Tue, 22 Oct 2019 14:08:42 +0000 Subject: [Starlingx-discuss] Installation of 2+2 and storage systems broken Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1B86BC0@ALA-MBD.corp.ad.wrs.com> Hey everyone. The following change broke the installation of 2+2 and storage systems: https://review.opendev.org/#/c/689438/ The "system host-stor-add" command will fail with an error: Only 1 storage monitor available. At least 2 unlocked and enabled hosts with monitors are required. Please ensure hosts with monitors are unlocked and enabled. The above commit went in on Friday (October 18). I have reverted it and that should be merged very soon. If you have a lab in this state, you can probably correct the issue by running the following command on both controllers: sudo chgrp sys_protected /etc/ceph/ceph.conf My apologies for any problems this caused you. Bart -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.l.tullis at intel.com Tue Oct 22 14:20:26 2019 From: michael.l.tullis at intel.com (Tullis, Michael L) Date: Tue, 22 Oct 2019 14:20:26 +0000 Subject: [Starlingx-discuss] [docs][meetings] docs team meeting cancelled for 10/23 Message-ID: <3808363B39586544A6839C76CF81445EA1BFB818@ORSMSX104.amr.corp.intel.com> All, The docs team will not meet as scheduled on October 23. We're canceling because most of us are tied up in conferences or other competing tasks that day. We'll meet again as scheduled on October 30. -- Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Tue Oct 22 14:50:54 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 22 Oct 2019 14:50:54 +0000 Subject: [Starlingx-discuss] FW: [Build] Build layering reviews References: <58efa3fb-9958-4af1-27f4-21db5a90da19@windriver.com> <2FD5DDB5A04D264C80D42CA35194914F360482ED@SHSMSX104.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D856264A3B@CDSMSX102.ccr.corp.intel.com> <59676767-1870-b9a4-d256-77ff3a4148c8@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856265D08@CDSMSX102.ccr.corp.intel.com> <157958eb-6c13-318c-b087-a3d6b8a68662@windriver.com> <56829C2A36C2E542B0CCB9854828E4D856266584@CDSMSX102.ccr.corp.intel.com> <92bad81a-e05f-6e1d-d83f-71263c01f29f@windriver.com> <56829C2A36C2E542B0CCB9854828E4D85626690A@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D85626EE06@CDSMSX102.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC158F833@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D856271BE0@CDSMSX102.ccr.corp.intel.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D856273198@CDSMSX102.ccr.corp.intel.com> Hi Penney and Scott 1, As I explained yesterday, you should update these file depending on your cenga setup tools/centos-mirror-tools/config/centos/flock/required_build_tis_pkg.cfg tools/centos-mirror-tools/config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo tools/centos-mirror-tools/config/centos/flock/yum.repos.d/ StarlingX_cengn_distro_layer.repo tools/centos-mirror-tools/config/centos/distro/required_build_tis_pkg.cfg tools/centos-mirror-tools/config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo root/build-tools/build_iso/centos_required_build_layer.cfg 2, I add a parameter for tools/toCOPY/generate-cgcs-centos-repo.sh, “—layer=”. Take attention. Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, October 21, 2019 10:20 PM To: 'Penney, Don' ; 'Bailey, Henry Albert (Al)' ; 'Little, Scott' ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] FW: [Build] Build layering reviews Hi I have update patch again. Last week, I raise this concern 3, update script download_mirror.sh and generate-cgts-centos-repo Currently all rpm name in lst is listed with fixed rpm version, which makes layer build easily to be corrupted. For example, any time TIS_PATCH_VER in build_srpm.data update, rpm name in lst should be updated. Prefer rpm named with “tis” should be query candidate on cenga, which request download_mirror.sh and generate-cgts-centos-repo update. Prefer we could finish such update in this story, as I think this is a critical issue. So I update patch in stx-tools again to fix this issue. You can check download_mirror.sh I add a step to generate rpm_tis.lst for layer build case. In such case, it will download tis_pkg.lst from cenga. What listed in tis_pkg.lst is distro or compile layer’s built rpm with named xxx.tis.xxx.rpm. So no matter src rpm or tarball upgrade, rpm_centos3party.lst is unnecessary to update. And I update build-iso, image.inc should concatenate with distro and compile layer’s image.in. As image.inc not only for install package, but also request for generate comps.xml. Please check my update and review my patch Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, October 15, 2019 10:27 PM To: Penney, Don >; Bailey, Henry Albert (Al) >; Little, Scott >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] FW: [Build] Build layering reviews Hi I have updated patch for layer build https://review.opendev.org/#/c/681821/ https://review.opendev.org/#/c/681823/ https://review.opendev.org/#/c/681824/ https://review.opendev.org/#/c/681828/ https://review.opendev.org/#/c/681832/ https://review.opendev.org/#/c/681834/ https://review.opendev.org/#/c/681835/ https://review.opendev.org/#/c/681836/ https://review.opendev.org/#/c/681842/ https://review.opendev.org/#/c/681847/ https://review.opendev.org/#/c/681848/ https://review.opendev.org/#/c/681851/ https://review.opendev.org/#/c/681852/ https://review.opendev.org/#/c/681854/ https://review.opendev.org/#/c/681856/ https://review.opendev.org/#/c/681890/ https://review.opendev.org/#/c/681892/ https://review.opendev.org/#/c/681894/ https://review.opendev.org/#/c/681898/ https://review.opendev.org/#/c/681900/ https://review.opendev.org/#/c/681901/ https://review.opendev.org/#/c/681902/ https://review.opendev.org/#/c/681914/ https://review.opendev.org/#/c/688598/ And I think we still left three issue. 1, request build-tools/build_iso/centos_required_build_layer.cfg Current for self validation, we could add a file with such content. But we should create a file depending on cenga update compile,file:///localdisk/loadbuild/martin/starlingx/centos_compile_iso_image.inc distro,file:///localdisk/loadbuild/martin/distro/centos_distro_iso_image.inc flock,file:///localdisk/loadbuild/martin/flock/centos_flock_iso_image.inc 2, propose use one copy of yum.conf.sample and yum.repo.d/* Currently there is 4 copies of yum.conf.sample and yum.repo.d/*. 3 copies in stx-tools/centos-mirror-tools/config/centos// and 1 copy in stx-tools/centos-mirror-tools/ Propose to remove 3 copies in stx-tools/centos-mirror-tools/config/centos//. To avoid user confusing 3, update script download_mirror.sh and generate-cgts-centos-repo Currently all rpm name in lst is listed with fixed rpm version, which makes layer build easily to be corrupted. For example, any time TIS_PATCH_VER in build_srpm.data update, rpm name in lst should be updated. Prefer rpm named with “tis” should be query candidate on cenga, which request download_mirror.sh and generate-cgts-centos-repo update. Prefer we could finish such update in this story, as I think this is a critical issue. Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Penney, Don > Sent: Monday, September 30, 2019 11:33 PM To: Bailey, Henry Albert (Al) >; Chen, Haochuan Z >; Little, Scott >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] FW: [Build] Build layering reviews Is this the issue? openstack/python-horizon/centos/python-django-horizon.spec:BuildRequires: cgts-client I don’t see anything in this package that should need this dependency, and it should be safe to remove it. From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] Sent: Monday, September 30, 2019 10:56 AM To: Chen, Haochuan Z; Little, Scott; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] FW: [Build] Build layering reviews I think Cgts-client (renamed to system-client) should be in its own repo. Al From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Monday, September 30, 2019 2:06 AM To: Little, Scott; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] FW: [Build] Build layering reviews Hi Scott I think have some question or concern. 1, I find distro layer has dependency to cgts-client, as there is a addin for Horizon, which enables look up flock service info in Horizon. So there is task is must for layer building, which is out of my expectation. I begin to tackle these task. • Relocate from git 'config', subdir 'sysinv/cgts-client', to git 'utilities', subdir 'system-client', with full git history. • Rename rpm package from 'cgts-client' to 'system-client' • Fix rpm packages that list cgts-client as a require or build require • Rename python module from 'cgts-client' to 'system-client' • Scan function names and/or variables for any that contain 'cgts' ... replace with 'system' ... can we do this in a backward compatible way? • Fix users of the client to import using the new name, and reference any renamed functions/data. • Fix ISO and/or docker images that list this package for inclusion. 2, “all” layer maybe doesn’t work, warning! For current patch for generate-cgts-centos-repo.sh, all layer’s rpms_lst_file is generated by merge “compiler/distro/flock” three layers, config/centos/all doesn’t be referenced, which is none sense. Which means package such bash-4.2.46-31.el7.tis.4.x86_64.rpm, named with “tis” is also in mirror. This maybe interference source package building. I think request some fix in generate-cgts-centos-repo.sh to omit package with “tis” in name. 3, Layered build introduces rpms_cemtos.lst dependency on TIS_PATCH_VER in build_srpm.data, which make developer easily disrupt layered building mechanism. For distro and flock layer, it has dependency to starlingX customized package, for example, distro layer require bash.tis...rpm, which will be add in config/centos/distro/rpms_centos3rdparty.lst If new developer forget to update and build all package, it maybe disrupt layered building. BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Friday, September 27, 2019 4:40 PM To: Scott Little >; starlingx-discuss at lists.starlingx.io Subject: RE: FW: [Starlingx-discuss] [Build] Build layering reviews Thanks, Scott. I have studied so much. BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Scott Little > Sent: Thursday, September 26, 2019 11:39 PM To: Chen, Haochuan Z >; starlingx-discuss at lists.starlingx.io Subject: Re: FW: [Starlingx-discuss] [Build] Build layering reviews Returning this discussion to the mailing list. If possible, join the Build call next week. https://wiki.openstack.org/wiki/Starlingx/Meetings 1) When mock installs for the first time. it uses rpms that have been download via lst file. The mock pseudo-layer lst files capture reflect the rpms needed by mock. The mock lst's are merged with the layers lst's. In this way, the mock rpms don't have to be listed in each and every layer's lst. 2) Adding tools to generate an lst file reflacting the output of a build layer, and adding that lst for consumprion by higher layers, is indeed a possibility possibility I wanted to persue. Reference to that output lst could then be added to as a new arg to the download script when invoked by a higher layer, or a config file could specify where to find it (cengn is the likely default supplier). compile layer) The compile layer is a true layer, built prior to the distro layer. Only a few build related packages go here. Compilers, language interpreters, rpm. I wanted those packages in place so that all distro layer packages build with the same tools. Scott On 2019-09-25 10:24 p.m., Chen, Haochuan Z wrote: Still not clear about mock layer. 1, In build container, mock is already installed, why request to download mock required package firstly? 2, To build distro or flock layer, we could add compile layer’s tis rpm in distro and flock layer’s lst file. By download compile layer’s binary in mirror, it could also ensure user building package with same tool. Why introduces compile layer? Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Scott Little Sent: Thursday, September 26, 2019 12:25 AM To: Chen, Haochuan Z Subject: Re: FW: [Starlingx-discuss] [Build] Build layering reviews See inline ... Scott On 2019-09-23 11:00 a.m., Chen, Haochuan Z wrote: Hi Scott I studied your patch and some questions. 1, why there is mock and compile layer, what's usage or intention for these two layers? Build-pkgs uses a tool called mock to create a reproducible compilation sandbox. It is chroot like environmnet into which rpms are installed to construct a minimal build environment. The mock layer is not built. I created it as a placeholder for the lst files that downloads all the rpms that mock requires. Prior to building a layer, the lst files for both the layer being build, and the mock pseudo layer, need to be processed. Without the mock pseudo layer, we would have to replicate that list of mock required rpms in each and ever layer's lst files. The concept ran into a bit of trouble because some of the rpms needed by mock are themselves built by the compile or distro layers (with a newer revision). So the mock pseudo layer might actually omit those rpms from it's lst file, and they needed to be listed in the layer lst files instead. The compile layer is a true layer, built prior to the distro layer. Only a few build related packages go here. Compilers, language interpreters, rpm. I wanted those packages in place so that all distro layer packages build with the same tools. 2, for download_mirror.sh, it generate rpm list by merge file in config/centos// and rpm list file in stx/ But for generate-cgcs-centos-repo.sh, it use rpm list file in centos-mirror-tools folder. Rpm package should be added in two rpm list file. It is not good for maintenance. What about remove rpm list file in centos-mirror-tools folder rpms_centos.lst/rpms_centos3rdparties.lst/rpms_3rdparties.lst/other_downloads.lst/ tarball-dl.lst That was considered and debated. The concern was that the many git repos that make up the layer would list different versions of the same package. Then what do we do? Throw an error? Silently use the newest package? So we elected to keep binary rpms needed to satisfy dependencies listed in a central place. At some point we may want to explore allowing lst files specify required package but not version (beyond a possible minimum version) when on the master branch, and have a way to 'lock down' the versions only for a release branch. 3, Question about setup yum repo for rpm tailing with “tis” such as xxx.tis.x86_64.rpm or xxx.tis.noarch.rpm In this patch https://review.opendev.org/#/c/681821/1 There is such line in config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo [Starlingx-cengn_distro_layer] name=Starlingx-cengn_distro_layer baseurl=http://127.0.0.1:8088/localdisk/loadbuild/slittle1/restructure3b/std/rpmbuild/RPMS/ enabled=1 [Starlingx-cengn_distro_layer-rt] name=Starlingx-cengn_distro_layer baseurl=http://127.0.0.1:8088/localdisk/loadbuild/slittle1/restructure3b/rt/rpmbuild/RPMS/ enabled=1 also in config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo My understanding is rpm tailing with “tis” should also upload to cengn, rpm name listed in centos-mirror-tools/config/centos/flock/rpms_centos3rdparties.lst So these three files should be unnecessary, with cengn update for layered build. config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo For development testing, I had to hack together a simulated cengn by running lighttpd on 127.0.0.1:8088 and allowing it to serve up files from builds of lower layers restructure3a == layer-comiler layer build restructure3b == layer-distro layer build restructure3c == layer-flock layer build (although there shouldn't be a repo entry referring to that one) Finalizing the repo entries would have to wait until cengn was up an running. 4, In generate-cgcs-centos-repo.sh there is --layer-dir, and such content in your patch commit message generate-cgcs-centos-repo.sh \ --layer-dir=/localdisk/loadbuild/slittle1/layer-compile/std/rpmbuild/RPMS/ \ --layer-dir=/localdisk/loadbuild/slittle1/layer-distro/std/rpmbuild/RPMS/ \ --layer-dir=/localdisk/loadbuild/slittle1/layer-distro/rt/rpmbuild/RPMS/ \ /import/mirrors/starlingx For all rpm download from cengn, --layer-dir is unnecessary to generate link, correct? This is another way to do cross layer development testing without support from cengn. Again the goal is to allow an upper layer build to download rpms from a lower layer build on the same machine. 5, could you share build-tools/build-iso/centos_required_build_layer.cfg, share to me Did that not get published in my reviews? Content is very simple. compile,file:///localdisk/loadbuild/slittle1/restructure3a/centos_compile_iso_image.inc distro,file:///localdisk/loadbuild/slittle1/restructure3b/centos_distro_iso_image.inc flock,file:///localdisk/loadbuild/slittle1/restructure3c/centos_flock_iso_image.inc 6, For distro/compiler/flock, all are separate layer? Yes My current step repo init -u https://opendev.org/starlingx/manifest.git apply this patch to .repo/manifests https://review.opendev.org/#/c/681914/1 repo init -m compile.xml repo sync apply these to patch https://review.opendev.org/#/c/681821/1 https://review.opendev.org/#/c/681828/1 ./download_mirror.sh -n -g -l flock -c config/centos/compiler/yum.conf.sample -S ./toCopy/generate-cgts-centos-repo output/stx-r1/CentOS/pike/ build-pkgs build-iso BR! Martin, Chen SSP, Software Engineer 021-61164330 -----Original Message----- From: Scott Little Sent: Thursday, September 19, 2019 9:54 PM To: Chen, Haochuan Z Subject: Re: FW: [Starlingx-discuss] [Build] Build layering reviews Most of the required changes were already merged. I'll scan the spec when time permits to see if I missed anything. Scott On 2019-09-16 12:01 p.m., Chen, Haochuan Z wrote: > Hi Scott > > I read your patch for build layering, but could not find patch for build script. > > Description in spec https://review.opendev.org/#/c/672288/12/ > Modifications to package build scripts ... build-pkgs, > build-srpms-parallel, build-srpms-serial, build-rpms-parallel, build-rpms-serial (cgcs-root): > > Thanks > > Martin, Chen > SSP, Software Engineer > 021-61164330 > > -----Original Message----- > From: Xie, Cindy > Sent: Friday, September 13, 2019 12:24 PM > To: Chen, Haochuan Z > > Cc: Hu, Yong > > Subject: FW: [Starlingx-discuss] [Build] Build layering reviews > > Martin, > I am wondering if you will be interested to working on this task. To me, having layering build and provide efficiency to developers are very important for StarlingX. It also provide a chance that you and work together w/ WR folks being more close collaboration. Let me know your interested level. > > Thx. -cindy > > -----Original Message----- > From: Scott Little > > Sent: Friday, September 13, 2019 4:55 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [Build] Build layering reviews > > My prototype code for the layered build has been posted to gerrit. > (listed below) > > I was briefly able to build all layers, and produce an iso with the same package content as the cengn build. Then I was diverted by non-trivial changes to the restructuring work. What I have posted is now several weeks out of date and will almost certainly will not work. The devil is in keeping the lst files in sync with the ever changing master branch. > > Other commitments will prevent me from resuming this work until November. If anyone wants to whip the lst files into shape and try to get the build working again, be my guest. > > Final delivery will require changes to the CENGN build scripts (Don or Myself), and a freeze on packaging changes will likely be required for aprox 3 days to finalize the lst files. > > Scott > > ---------------- ---------------- > > https://review.opendev.org/#/c/681821/1 > > https://review.opendev.org/#/c/681914/1 > > https://review.opendev.org/#/c/681823/1 > > https://review.opendev.org/#/c/681824/1 > > https://review.opendev.org/#/c/681828/1 > > https://review.opendev.org/#/c/681832/2 > > https://review.opendev.org/#/c/681834/1 > > https://review.opendev.org/#/c/681836/1 > > https://review.opendev.org/#/c/681835/1 > > https://review.opendev.org/#/c/681842/1 > > https://review.opendev.org/#/c/681847/1 > > https://review.opendev.org/#/c/681848/1 > > https://review.opendev.org/#/c/681851/1 > > https://review.opendev.org/#/c/681852/1 > > https://review.opendev.org/#/c/681854/1 > > https://review.opendev.org/#/c/681856/1 > > https://review.opendev.org/#/c/681890/1 > > https://review.opendev.org/#/c/681892/1 > > https://review.opendev.org/#/c/681892/1 > > https://review.opendev.org/#/c/681898/1 > > https://review.opendev.org/#/c/681900/1 > > https://review.opendev.org/#/c/681901/1 > > https://review.opendev.org/#/c/681902/1 > > > > > _______________________________________________ > 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 abraham.arce.moreno at intel.com Tue Oct 22 16:05:58 2019 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 22 Oct 2019 16:05:58 +0000 Subject: [Starlingx-discuss] Bug 1835207 Error links for starling project docs Message-ID: Dear Owners of test, distcloud* repositories, So we can close bug [0], can you please help us feedback / merge the following reviews: https://review.opendev.org/#/c/668891/ starlingx/distcloud https://review.opendev.org/#/c/668894/ starlingx/distcloud-client https://review.opendev.org/#/c/668906/ starlingx/test [0] https://bugs.launchpad.net/starlingx/+bug/1835207 Thanks all! Best Regards Docs Team From Bill.Zvonar at windriver.com Tue Oct 22 16:50:13 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 22 Oct 2019 16:50:13 +0000 Subject: [Starlingx-discuss] Community Call (Oct 23, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B06F84@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of the Community call tomorrow. Please feel free to add new topics to the agenda at [0]. 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=20191023T1400 From abraham.arce.moreno at intel.com Tue Oct 22 19:04:47 2019 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 22 Oct 2019 19:04:47 +0000 Subject: [Starlingx-discuss] openSUSE: High Availability Update Message-ID: Dear high availability community: Thanks you for your support to get the following reviews in place: - [0] openSUSE: Runtime Dependencies - [1] openSUSE: Open Build Service Artifacts After high availability rpm was successfully built and some runtime dependencies were fixed, as part of our task "make flock run", I started to understand its next level of details through DevStack installation and did a setup with the following order and components: 1. Virtual Box machine based on OpenSUSE Leap [2] - 2 CPUs / 24 GB RAM / 64 GB SSD Disk 2. DevStack, installed through provided installation instructions [3] 3. High Availability installed through OBS personal repository [4] In summary, next are the issues faced, in review, in the setup described above: Installation $ sudo zypper -n --no-gpg-checks install sm-common Problem: nothing provides libamon1 needed by sm-common-1.0.0-lp151.2.2.x86_64 $ sudo zypper -n --no-gpg-checks install sm-api Problem: nothing provides libamon1 needed by sm-api-1.0.0-lp151.3.1.x86_64 Keystone authentication $ source openrc $ nova flavor-list # Ok $ smc service-list # Failed Authorization failed: Not Found (HTTP 404) (Request-ID: req-770aff15-ff1f-4c63-a5c2-5ed088e7b487) Feel free to suggest path of research, specific activities to focus on, I will get back to this mailing list by the end of this week. All details (constantly updated) at personal github [5]. [0] https://review.opendev.org/#/c/687429/ [1] https://review.opendev.org/#/c/679686/ [2] https://software.opensuse.org/distributions/leap [3] https://docs.openstack.org/devstack/latest/ [4] https://download.opensuse.org/repositories/home:/xe1gyq/Cloud_StarlingX_2.0_openSUSE_Leap_15.1/home:xe1gyq.repo [5] https://github.com/xe1gyq/starlingx/blob/master/multios/opensuse_ha_install_devstack.md From abraham.arce.moreno at intel.com Tue Oct 22 19:20:43 2019 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 22 Oct 2019 19:20:43 +0000 Subject: [Starlingx-discuss] StarlingX TSN Application Message-ID: Dear StarlingX TSN team, As part of our story "Add an STX configuration guide" [0], can you please confirm we can start the translation this week of the guide in wiki format: "Deploying and Running TSN application in StarlingX Virtual Machine Workload Mode" [1] to our official documentation in rst format: "StarlingX R3.0 Installation Guides" [2] - We will submit the review with --author "Huifeng Le mailto:huifeng.le at intel.com", is there any other person that should be added as Co-Authored-By? - Is there any other consideration to stop this translation? [0] https://storyboard.openstack.org/#!/story/2006289 [1] https://wiki.openstack.org/wiki/StarlingX/Networking/TSN [2] https://docs.starlingx.io/deploy_install_guides/r3_release/index.html From Ghada.Khalil at windriver.com Tue Oct 22 19:26:13 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 22 Oct 2019 19:26:13 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Oct 17/2019 Message-ID: <151EE31B9FCCA54397A757BC674650F0C15CF1FD@ALA-MBD.corp.ad.wrs.com> Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - October 17 2019 Election - Agreed that the Release team does not need a TL. Bruce to make recommendation to the TSC. stx.2.0 - maintenance release: stx.2.0.1 - Regression completed as of 2019-10-05 - http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006515.html - No new issues found - Need to discuss two reported issues which are currently not gating for stx.2.0 - https://bugs.launchpad.net/starlingx/+bug/1836378 - [[GK]] This was initially reported as a very intermittent issue and is currently not gating for stx.2.0. What's the frequency of occurrence? Does another lock/unlock attempt recover the issue? We need to decide if we should make this stx.2.0 gating and target a fix for a subsequent maintenance release. - As per Elio, this was seen by Yosief in WR lab. Elio is not able to reproduce it as of yet. - Keep as is for now ...until it becomes a bigger problem - https://bugs.launchpad.net/starlingx/+bug/1841660 - [[GK]] Same as above. Is this an intermittent issue? What's the frequency of occurrence? Previously this was reported once and therefore is not currently marked as gating for stx.2.0. We need to decide if we should make this stx.2.0 gating and target a fix for a subsequent maintenance release. - Also seen in WR lab. - Keep as is for now ...until it becomes a bigger problem - Branch Labelling/CENGN Release Update - Forecast: 2019-10-18 >> COMPLETE - Open Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2.0 - Count: 7 - Action: ping PLs to see if issues are actively being worked and if they should continue to be gating for stx.2.0 stx.3.0 - Milestone-3 was scheduled for Oct 18. Based on current status, this will be delayed by one week - Feature Status - https://docs.google.com/spreadsheets/d/1ZFR-9-riwhIwiBYBmWmi1qOVyHtgJ8Xk_FaF2jp5rY0/edit#gid=1010323020 - Done: 5 - Dev In Progress: 6 (1 prep expected to complete by 10.30) - Test In Progress: 3 - Deferred/Continuing in stx.4.0: 3 (excluding others that were deferred earlier) - Most features have reasonable dates for code merge/feature testing. - Feature-specific Risks: - Upversion to Train: No projected dates provided. Some items are still unresourced. Unclear whether this can land. - Regression Test - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 - Completion Rate: 24% - Making good progress / no concerns - Feature Test - https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit#gid=968103774 - Completion Rate: 39% stx.4.0 - Tentative Dates (based on current formula to lag openstack by ~6 weeks) - https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 - Discussed if 6wks LAG from openstack is still the right duration - At this time, we feel it is. However, we just need to start the openstack rebase earlier in the cycle than was done for stx.3.0 From bruce.e.jones at intel.com Tue Oct 22 19:46:54 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 22 Oct 2019 19:46:54 +0000 Subject: [Starlingx-discuss] StarlingX TSN Application In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BDFBFBB5D@fmsmsx123.amr.corp.intel.com> Abraham, this is cool. But why not include Huifeng in the process? Huifeng, do you know how to write .rst documents? Would you like to learn? I think this review should come from you directly, and both Abraham and myself are available to help you as needed. brucej -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Tuesday, October 22, 2019 12:21 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX TSN Application Dear StarlingX TSN team, As part of our story "Add an STX configuration guide" [0], can you please confirm we can start the translation this week of the guide in wiki format: "Deploying and Running TSN application in StarlingX Virtual Machine Workload Mode" [1] to our official documentation in rst format: "StarlingX R3.0 Installation Guides" [2] - We will submit the review with --author "Huifeng Le mailto:huifeng.le at intel.com", is there any other person that should be added as Co-Authored-By? - Is there any other consideration to stop this translation? [0] https://storyboard.openstack.org/#!/story/2006289 [1] https://wiki.openstack.org/wiki/StarlingX/Networking/TSN [2] https://docs.starlingx.io/deploy_install_guides/r3_release/index.html _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From maria.g.perez.ibarra at intel.com Tue Oct 22 22:22:17 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 22 Oct 2019 22:22:17 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191022 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-22 (link) Status: RED =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 64 TCs PASS ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs PASS ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs PASS ] =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs PASS ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs PASS ] --------------------------------------------------------------------------- platform-integ-apps application apply failure https://bugs.launchpad.net/starlingx/+bug/1848721 Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Tue Oct 22 22:48:31 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 22 Oct 2019 22:48:31 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191022 In-Reply-To: References: Message-ID: ** The total number of the tests was incorrect in the last report, this is the correct one ** Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-22 (link) Status: RED =========================================== 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 [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 64 TCs ] FAIL: [1 TCs] BLOCKED: [59 TCs] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 60 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 61 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 [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 60 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 61 TCs ] --------------------------------------------------------------------------- platform-integ-apps application apply failure https://bugs.launchpad.net/starlingx/+bug/1848721 Regards Maria G. From: Perez Ibarra, Maria G Sent: Tuesday, October 22, 2019 5:22 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191022 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-22 (link) Status: RED =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 64 TCs PASS ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs PASS ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs PASS ] =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs PASS ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs PASS ] --------------------------------------------------------------------------- platform-integ-apps application apply failure https://bugs.launchpad.net/starlingx/+bug/1848721 Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Tue Oct 22 23:31:32 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 22 Oct 2019 23:31:32 +0000 Subject: [Starlingx-discuss] [ Regression testing - stx3.0 ] Report for 10/22/2019 Message-ID: StarlingX 3.0 Release Status: ISO: BUILD_ID=" 20191018T013000Z" from (link) ---------------------------------------------------------------------- MANUAL EXECUTION ---------------------------------------------------------------------- Overall Results: Total = 274 Pass = 135 Fail = 6 Blocked = 9 Not Run = 131 Obsolete = 2 Deferred = 0 Total executed = 143 Pass Rate = 95.7% Formula used : Pass Rate = (pass * 100) / (pass + fail) --------------------------------------------------------------------------- AUTOMATED ROBOT - INTEL --------------------------------------------------------------------------- Overall Results: Total = 202 Pass = 144 Fail = 19 Blocked = 38 Obsolete = 0 Deferred = 0 Not Valid = 1 Total executed = 164 Pass Rate = 88% Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- AUTOMATED PYTEST - WR --------------------------------------------------------------------------- Overall Results: Total = 467 Pass = 0 Fail = 0 Blocked = 0 Not Run = 467 Obsolete = 0 Deferred = 0 Total executed = 0 Pass Rate = Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- BUGS SSH / SCP to VM failed using NAMESPACE while IP is assigned by Horizon https://bugs.launchpad.net/starlingx/+bug/1849221 --------------------------------------------------------------------------- For more detail of the tests: https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 Regards! Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Wed Oct 23 00:11:00 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Wed, 23 Oct 2019 00:11:00 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting Message-ID: Thanks to all who participated in today's meeting. Good progress across the stx.3.0 features. Minutes for Oct 22: 1. Updates on stx.3.0 container features for MS3 milestone: 2004008: [Feature] Create HELM chart for Fault project [Ran An] - one horizon related commit needs a new approach which cannot be done in stx.3.0 timeframe Decision for stx.3.0 is to keep FM container code but disable it so that FM runs natively for stx.3.0 - then address horizon issue in stx.4.0 and re-enable FM containers. Ran has proposed doing this by bringing back the "fault_management_pod_disabled" flag that was introduced in stx.2.0 and removed in stx.3.0 Ran's forecast for completing this and posting gerrit review is end of week, ie Oct 25 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] - Ran confirmed this feature is now merged Below 2 patches are for k8s device plugin enabling mechanism in ansible and sysinv, add intel gpu device plugin as well --- merged - https://review.opendev.org/#/c/666511/ - https://review.opendev.org/#/c/666510/ This patch is for align all device plugins in one method. Will be revisit when default device plugins require to be align. --- abandoned - https://review.opendev.org/#/c/685592/ 2005514: QAT K8S device plugin support in StarlingX Mingyuan: status of 3 patches which depended on Ran's 666510/666511 - https://review.opendev.org/684890 --> merged - https://review.opendev.org/688344 --> Cores have +2'd -- just need WFL +1 - https://review.opendev.org/688363 --> Cores have +2'd -- just need WFL +1 2005860: Upversion container components [Al Bailey] --> merged 2004761: Integrate Backup & Restore with Containers (for platform) [Ovidiu Poncea] --> merged 2. Complete review of KATA containers feature with container Cores. - Shuicheng's update: Here is the latest test status for kata integration in StarlingX. (1) Pass Sanity test for AIO-SX/AIO-DX/Multi/Multi+Storage. (2) Tested private registry (insecure registry) enabled/disabled. (3) Tested docker proxy enabled/disabled. (4) Tested swact/lock & unlock/remove & apply application. (5) Tested local registry (registry.local:9001) with image pull/push, and access both from kubernetes and crictl (CLI). For regression test, I checked container related test cases in below doc, and executed most of them. No issue is found yet. https://docs.google.com/spreadsheets/d/1dwcBwY4Yq1Lo9Der4RylzQ6KYp0BsMHohhEmhwpauDo/edit?usp=sharing Currently, I meet a deploy issue with IPv6 environment, and the issue could be reproduced with master daily build also. I am checking whether it is caused by my environment or a real issue of master now. Here is the patch list waiting review: https://review.opendev.org/#/q/topic:kata+(status:open) Some questions/comments from TL/Brent: - Have we tested with external registry and where username/pwd is required? Answer: Not yet. Action: Request is for Shuicheng to test (maybe work with Yong) - What is the plan to remove dockerd? - Plan is to remove in a separate commit after the main code merges. Shuicheng plan is to wait till stx.4.0 to remove - is this acceptable? - Shuicheng plan is to have the dockerd removal commit ready by end of November. Plan then to merge this into stx.4.0 once it is open. - We agreed this would be acceptable. - Looks like there is one upstream patch we are carrying (in containerd and runc?). What is the plan to upstream these patches? - Action: Ensure there is a task to upversion docker distribution registry to remove the need to carry this patch. - This too will be done early in stx.4.0. Shuicheng to update us in 1 week on when this task can be completed. Decision to allow into stx.3.0? Three requirements: - Shuicheng to complete testing for IPv6 and external registry with username/pwd authentication - Cores to complete their reviews - Frank to confirm with Ada that testing of this feature can be done in time for stx.3.0 - Backup plan: If instability is seen in stx.3.0 or significant testing by Ada results in failures then the feature would need to be backed up and fixed/delivered in stx.4.0 Frank Miller, Manager, Engineering, Wind River direct 613.963.1389 zoom frank.miller at windriver.com 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 -------------- next part -------------- An HTML attachment was scrubbed... URL: From huifeng.le at intel.com Wed Oct 23 02:11:19 2019 From: huifeng.le at intel.com (Le, Huifeng) Date: Wed, 23 Oct 2019 02:11:19 +0000 Subject: [Starlingx-discuss] StarlingX TSN Application In-Reply-To: References: Message-ID: <76647BD697F40748B1FA4F56DA02AA0B4D6335C0@SHSMSX104.ccr.corp.intel.com> Abraham, Xu, Yizhou mailto: yizhoux.xu at intel.com should be added as Co-Authored-By. Thanks much! Best Regards, Le, Huifeng -----Original Message----- From: Arce Moreno, Abraham Sent: Wednesday, October 23, 2019 3:21 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX TSN Application Dear StarlingX TSN team, As part of our story "Add an STX configuration guide" [0], can you please confirm we can start the translation this week of the guide in wiki format: "Deploying and Running TSN application in StarlingX Virtual Machine Workload Mode" [1] to our official documentation in rst format: "StarlingX R3.0 Installation Guides" [2] - We will submit the review with --author "Huifeng Le mailto:huifeng.le at intel.com", is there any other person that should be added as Co-Authored-By? - Is there any other consideration to stop this translation? [0] https://storyboard.openstack.org/#!/story/2006289 [1] https://wiki.openstack.org/wiki/StarlingX/Networking/TSN [2] https://docs.starlingx.io/deploy_install_guides/r3_release/index.html _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From 18245043314 at 163.com Wed Oct 23 07:40:28 2019 From: 18245043314 at 163.com (=?GBK?B?1tzH5tH0?=) Date: Wed, 23 Oct 2019 15:40:28 +0800 (CST) Subject: [Starlingx-discuss] Starlingx code organization Message-ID: <64f36ae3.9627.16df78f5452.Coremail.18245043314@163.com> Hi I am new to the starlingx subject, and i am little confused about starlingx code organization from https://opendev.org/starlingx/manifest. I have some questions. 1. If I modify the cgcs-root in proper way, can I make it available on ubuntu? 2. What is the purpose of stx-tools folder, is it still in use? -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Wed Oct 23 08:05:49 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Wed, 23 Oct 2019 08:05:49 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting In-Reply-To: <9700A18779F35F49AF027300A49E7C76608D847F@SHSMSX105.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C76608D7CA6@SHSMSX105.ccr.corp.intel.com> <2588653EBDFFA34B982FAF00F1B4844EC26ED58D@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C76608D847F@SHSMSX105.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C76608D8CB3@SHSMSX105.ccr.corp.intel.com> Hi Brent & all, I am sorry to forgot we still need dockerd to pull & push image to local registry, due to crictl doesn't support push image [0]. So we cannot remove dockerd currently. There is another containerd CLI "ctr", which support pull & push image, but this tool is stated as "unsupported" [1]. So I prefer to keep use docker instead of ctr. What is your suggestion? Thanks. [0]: https://github.com/kubernetes-sigs/cri-tools/issues/438 [1]: https://github.com/containerd/containerd/blob/master/cmd/ctr/app/main.go#L61 Best Regards Shuicheng From: Lin, Shuicheng Sent: Monday, October 21, 2019 11:17 AM To: Rowsell, Brent ; Miller, Frank ; starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: RE: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting Hi Brent, [BR] What is the plan to remove dockerd ? [Shuicheng] We need switch armada to run with containerd first, then we should be able to remove dockerd. Task 37231 is created to track it under the same story[0]. Task 36981 is for switch armada to run with containerd. I prefer to do both task in later stage. [0]: https://storyboard.openstack.org/#!/story/2006145 Best Regards Shuicheng From: Rowsell, Brent > Sent: Friday, October 18, 2019 9:20 PM To: Lin, Shuicheng >; Miller, Frank >; starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: RE: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting Thanks. See inline Brent From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, October 17, 2019 9:00 AM To: Miller, Frank >; Rowsell, Brent >; starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: RE: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting Hi Frank & Brent & all, I have updated my patches to remove the visible password for registry. Please help review the update in ansible-playbooks/stx-puppet. Here is the link for the patch list: https://review.opendev.org/#/q/topic:kata+(status:open) - Add a commit to make containerd the default CLI (and remove any docker code that is no longer needed) [shuicheng] do you mean change the "/var/lib/docker" directory to "/var/lib/containerd" for both docker and containerd? If the answer is yes, I prefer to do it later, after docker runtime is not used at all. Currently, armada is still using docker. - Add a test case for local registry pull/push and authentication [BR] What is the plan to remove dockerd ? [Shuicheng] No plan yet. We need switch armada to run with containerd first, then we should be able to remove dockerd. Task 37231 is created to track it under the same story[0]. Task 36981 is for switch armada to run with containerd. [shuicheng] With the new patch, local registry still could be accessed both by Kubernetes and crictl. For crictl, username/password need be provided in CLI, similar to "docker login" for docker CLI. - Update code to ensure admin password is not visible [shuicheng] Done. Best Regards Shuicheng From: Miller, Frank > Sent: Tuesday, October 15, 2019 10:16 PM To: starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: [Starlingx-discuss] Minutes: StarlingX Bi-Weekly Containerization Meeting Since we did not get through the whole agenda today, I will schedule the next meeting 1 week from today. Minutes for Oct 15 meeting: 1. Review KATA containers feature with container Cores. Shuicheng to present feature overview and current status. - Shuicheng's commits: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) - Shuicheng presented his feature and what has been done so far (see his charts in separate email) Actions identified: - Concerns: Interaction with registry, admin password is visible - Add a commit to make containerd the default CLI (and remove any docker code that is no longer needed) - Add a test case for local registry pull/push and authentication - Update code to ensure admin password is not visible - Frank to book a follow-up meeting to continue the review (Frank to book Tuesday Oct 22) Frank -----Original Appointment----- From: Miller, Frank Sent: Thursday, October 10, 2019 2:55 PM To: Miller, Frank; starlingx-discuss at lists.starlingx.io Cc: vm.rod25 at gmail.com Subject: StarlingX Bi-Weekly Containerization Meeting When: Tuesday, October 15, 2019 9:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236 Apologies, re-sending without etherpad formatting. Note: We agreed to a new day and time for these meetings. For all who are working containerization features or LPs please join for our bi-weekly meeting. Agenda for October 15 meeting: 1. Review KATA containers feature with container Cores. Shuicheng to present feature overview and current status. - Shuicheng's commits: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) 2. Updates on other stx.3.0 container features for MS3 milestone: - 2004008: [Feature] Create HELM chart for Fault project [An Ran] - one commit needs a new approach - discussed in item #2 - Decision to be made about Horizon issue - do we keep FM containers enabled without Horizon for VM alarms? Or do we disable in stx.3.0 until issue can be addressed in stx.4.0? - 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] - require updated forecast - 2005514: QAT K8S device plugin support in StarlingX - Bruce: Code is out for review; Frank to follow-up with Cindy or feature primes for updated forecasts - 2005860: Upversion container components [Al Bailey] - 2004761: Integrate Backup & Restore with Containers [Ovidiu Poncea] 3. Update on stx.4.0 features: - 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC 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 Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Wed Oct 23 10:52:14 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Wed, 23 Oct 2019 10:52:14 +0000 Subject: [Starlingx-discuss] IPv6 deploy issue Message-ID: <9700A18779F35F49AF027300A49E7C76608D8D2E@SHSMSX105.ccr.corp.intel.com> Hi all, I am trying to deploy simplex with IPv6 environment, and fail at openstack application apply. It is due to pod "mariadb-ingress" fail to become ready. Here is the failure in the pod log: " Warning Unhealthy 142m kubelet, controller-0 Readiness probe failed: dial tcp [fd03::1e6d:6abe]:3306: connect: connection refused " And container log shows below error: " [emerg] 95#95: invalid port in upstream \"fd03::1e6d:6aac:3306\" in /tmp/nginx-cfg026066192:332 " The ISO I used is cengn 10/18 build, which pass sanity test. Does anyone try IPv6 deployment recently? And do you know what cause upper failure? Thanks. More log and my configuration info is attached in below link. http://paste.openstack.org/show/785508/ Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Wed Oct 23 10:59:41 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Wed, 23 Oct 2019 10:59:41 +0000 Subject: [Starlingx-discuss] Starlingx code organization In-Reply-To: <64f36ae3.9627.16df78f5452.Coremail.18245043314@163.com> References: <64f36ae3.9627.16df78f5452.Coremail.18245043314@163.com> Message-ID: <9700A18779F35F49AF027300A49E7C76608D8D42@SHSMSX105.ccr.corp.intel.com> Hi, For 1st question, what do you mean “available on ubuntu”? StarlingX is CentOS based, doesn’t support Ubuntu yet. For 2nd question, stx-tools is to create the build environment, if you want to build StarlingX from code, you will need it. Best Regards Shuicheng From: 周擎阳 <18245043314 at 163.com> Sent: Wednesday, October 23, 2019 3:40 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Starlingx code organization Hi I am new to the starlingx subject, and i am little confused about starlingx code organization from https://opendev.org/starlingx/manifest. I have some questions. 1. If I modify the cgcs-root in proper way, can I make it available on ubuntu? 2. What is the purpose of stx-tools folder, is it still in use? -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Wed Oct 23 13:49:15 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 23 Oct 2019 13:49:15 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F3608F98F@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F3608F98F@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F360909FA@SHSMSX104.ccr.corp.intel.com> Agenda & notes for 10/23 meeting: - Ceph containerization update (Tingjie) part#1: create helm-chart for rook and ceph-cluster: https://review.opendev.org/#/c/681457, feedback to seperate it into two patches. are you working w/ rook upstream community for the customization? Rook community is 1.1 version, backport the yaml files to StarlingX. Tingjie is not making any changes in the upstream rook component. AR: Tingjie/Martin: to update the patches into two patches. part#2: https://review.opendev.org/#/c/687340/ for configuration. Not completed yet, WIP test case is under development. part#3: rook plugin implementation w/ more features: still WIP, patch to be uploaded. Risk for stx.3.0 => goal is to have part#1 & part#2 finished. will review progress later. - CentOS 8.0 upgrade planning (Shuai) Shuai received xls sheet from Saul for kernel patch analysis against 4.19. RT kernel is not available for CentOS 8.0 yet - the RT kernel will release later on. Do not worry about RT kernel later. https://storyboard.openstack.org/#!/story/2006728 for kernel upgrade. Zhiguo is the owner. Making document for kernel patches for which ones need to be retained. AR for Shuai to send the xls to the mailing list for review. GCC compiler upgraded from 4.8 to 8.2. kernel drivers: not analyzed yet. https://storyboard.openstack.org/#!/story/2006729: RPM and sRPM upgrade, how many RPM & sRPM upgrade needed? AR: Shuai to provide a list for RPM and sRPM to be upgrade for CentOS 8.0 - CVE LP fixing - call for contribution (Cindy): we have 12 CVE to be fixed. anybody who is interested, send Cindy email, I will add you onto CVE watching list. The expectation is RC1 (11/20th) for both stx.3.0 and stx.2.0 This is good learning experience to start working as StarlingX developer. - Opens (all) Cindy Xie IAGS -----Original Message----- From: Xie, Cindy Sent: Tuesday, October 22, 2019 9:05 PM To: Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; 'Rowsell, Brent' Subject: Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Agenda for 10/23 meeting: - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade planning (Shuai Zhao) - CVE LP fixing - call for contribution (Cindy) - Opens (all) Cindy Xie -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W; Sun, Austin Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, October 23, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . 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 From sgw at linux.intel.com Wed Oct 23 14:57:33 2019 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 23 Oct 2019 07:57:33 -0700 Subject: [Starlingx-discuss] Starlingx code organization In-Reply-To: <9700A18779F35F49AF027300A49E7C76608D8D42@SHSMSX105.ccr.corp.intel.com> References: <64f36ae3.9627.16df78f5452.Coremail.18245043314@163.com> <9700A18779F35F49AF027300A49E7C76608D8D42@SHSMSX105.ccr.corp.intel.com> Message-ID: On 10/23/19 3:59 AM, Lin, Shuicheng wrote: > Hi, > > For 1^st question, what do you mean “available on ubuntu”? StarlingX is > CentOS based, doesn’t support Ubuntu yet. > > For 2^nd question, stx-tools is to create the build environment, if you > want to build StarlingX from code, you will need it. > If you have not already reviewed the StarlingX Build Guide [0], I would suggest you take a look at that to understand how to setup and build StarlingX for Centos. Currently, as Shuicheng mentioned, StarlingX is based on a customized CentOS 7.6 core and the tooling in cgcs-root which builds the rpm packages and ISO for installation is designed for CentOS. There is a Multi-OS sub-project that is working on an openSUSE based implementation of the StarlingX services. There was some initial limited work on a few services to build debian packages (see the fault repo [1][2]), but that work is not active any longer. If your interested in contributing a Debian and/or Ubuntu implementation, please consider joining the Multi-OS meeting [3]. [0] https://docs.starlingx.io/contributor/build_guide.html [1] https://opendev.org/starlingx/fault [2] https://opendev.org/starlingx/fault/src/branch/master/fm-common/debian [3] https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_MultiOS_Sub-project_call Sau! > Best Regards > > Shuicheng > > *From:*周擎阳<18245043314 at 163.com> > *Sent:* Wednesday, October 23, 2019 3:40 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Starlingx code organization > > Hi > > I am new to the starlingx subject, and i am little confused about > starlingx code organization from https://opendev.org/starlingx/manifest. > I have some questions. > > 1. If I modify the cgcs-root in proper way, can I make it available on > ubuntu? > > 2. What is the purpose of stx-tools folder, is it still in use? > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Bill.Zvonar at windriver.com Wed Oct 23 15:10:48 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 23 Oct 2019 15:10:48 +0000 Subject: [Starlingx-discuss] Community Call (Oct 23, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B07849@ALA-MBD.corp.ad.wrs.com> Notes from today's call... - standing topics - any Gerrit reviews that need attention? - Multi-OS reviews needing attention: https://review.opendev.org/#/q/topic:multios+status:open - looking good now, Saul working through why 1 item hasn't merged - building on this, Saul floated the idea of having Multi-OS representation in other sub-projects - Saul working on the AR to socialize this w/ the relevant cores - sanity - any reds since last call? - Oct 22: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006628.html - related somehow to https://bugs.launchpad.net/starlingx/+bug/1848721, but not sure yet - Bob is looking into it further, will work with Christopher on a joint-debugging session if he can't reproduce - any unanswered calls for assistance on the mailing list - nothing this week - CalSoft Image - Bill to add AR to find a long term home for this - PTG - Agenda discussion items reminder - More disscusion in TSC - PSA from Saul - if folks want to contribute to this, they can attend the TSC meeting tomorrow - Brent: stx.4.0 content will be part of this discussion - Ghada has a draft set of dates for stx.4.0 as well - https://drive.google.com/drive/folders/19iPEuVGCCfKLy9t0_otPAUuizqWmnB8t - Tentative Proposed Dates: - Milestone-1 1/24/2020 - Milestone-2 3/27/2020 - Milestone-3 5/15/2020 - Feature Test 5/29/2020 - Regression Test TBD - RC1 6/12/2020 - Final Regression TBD - Release 7/3/2020 - Features Deferred from stx.3.0 are captured in the "Release Candidates" worksheet - Saul: another topic is better community involvement in project confirmation - Election - reminder to the electorate for the flock-services election to vote by the end of the voting period (Sun, Oct 27 @20:45 UTC) - you should have received the email by now! - Oct 9, 2019 -- Dean -- present an overview of cool things you can do in Gerrit to watch/monitor your reviews (sneak preview: https://opendev.org/x/gerrit-dash-creator ) Quick overview in https://etherpad.openstack.org/p/stx-gerrit-dashboards - Oct 23: done, see etherpad! - Oct 9, 2019 -- Frank -- see if the CENGN access can be opened up to other folks besides Scott & Don so we've got more options to get stuff like this done - Oct 23: in progress - they'll add Saul + - June 5, 2019 --- -- provide requirements/input on Community Activity Dashboard (see notes from June 5 meeting) - Oct 23: Thierry sent survey, see http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006580.html - May 8, 2019 -- Frank -- follow up with CENGN on storage for really large files for reference in Launchpads - Oct 23: demo went well, will start rolling out over next couple of weeks -----Original Message----- From: Zvonar, Bill Sent: Tuesday, October 22, 2019 12:50 PM To: starlingx-discuss at lists.starlingx.io Subject: Community Call (Oct 23, 2019) Hi all, reminder of the Community call tomorrow. Please feel free to add new topics to the agenda at [0]. 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=20191023T1400 From Ghada.Khalil at windriver.com Wed Oct 23 15:14:55 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 23 Oct 2019 15:14:55 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Message-ID: <151EE31B9FCCA54397A757BC674650F0C15D07C7@ALA-MBD.corp.ad.wrs.com> Hi Cindy, Please see comment/questions inline. Ghada -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, October 23, 2019 9:49 AM To: Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; Rowsell, Brent Subject: Re: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Agenda & notes for 10/23 meeting: - Ceph containerization update (Tingjie) part#1: create helm-chart for rook and ceph-cluster: https://review.opendev.org/#/c/681457, feedback to seperate it into two patches. are you working w/ rook upstream community for the customization? Rook community is 1.1 version, backport the yaml files to StarlingX. Tingjie is not making any changes in the upstream rook component. AR: Tingjie/Martin: to update the patches into two patches. part#2: https://review.opendev.org/#/c/687340/ for configuration. Not completed yet, WIP test case is under development. part#3: rook plugin implementation w/ more features: still WIP, patch to be uploaded. Risk for stx.3.0 => goal is to have part#1 & part#2 finished. will review progress later. [[GK]] The ceph containerization feature has been deferred to stx.4.0 as per previous discussions (and request from Bruce). As the release prime, I prefer to limit risk to the upcoming MS-3 and regression plans and defer code submissions for this feature until the stx.3.0 release branch is created at RC1 (~ Nov 20). Is there a reason we need this code to go before then? You are already highlighting a risk above. Is this code completely benign? - CentOS 8.0 upgrade planning (Shuai) Shuai received xls sheet from Saul for kernel patch analysis against 4.19. RT kernel is not available for CentOS 8.0 yet - the RT kernel will release later on. Do not worry about RT kernel later. https://storyboard.openstack.org/#!/story/2006728 for kernel upgrade. Zhiguo is the owner. Making document for kernel patches for which ones need to be retained. AR for Shuai to send the xls to the mailing list for review. GCC compiler upgraded from 4.8 to 8.2. kernel drivers: not analyzed yet. https://storyboard.openstack.org/#!/story/2006729: RPM and sRPM upgrade, how many RPM & sRPM upgrade needed? AR: Shuai to provide a list for RPM and sRPM to be upgrade for CentOS 8.0 - CVE LP fixing - call for contribution (Cindy): we have 12 CVE to be fixed. anybody who is interested, send Cindy email, I will add you onto CVE watching list. The expectation is RC1 (11/20th) for both stx.3.0 and stx.2.0 This is good learning experience to start working as StarlingX developer. - Opens (all) Cindy Xie IAGS -----Original Message----- From: Xie, Cindy Sent: Tuesday, October 22, 2019 9:05 PM To: Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; 'Rowsell, Brent' Subject: Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Agenda for 10/23 meeting: - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade planning (Shuai Zhao) - CVE LP fixing - call for contribution (Cindy) - Opens (all) Cindy Xie -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W; Sun, Austin Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, October 23, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . 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 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From sgw at linux.intel.com Wed Oct 23 16:10:19 2019 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 23 Oct 2019 09:10:19 -0700 Subject: [Starlingx-discuss] Packaging and Multi-OS changes in StarlingX repos Message-ID: <5a65665e-98ba-5e9c-d40f-05c370e6f738@linux.intel.com> Folks, There was a brief discussion in the Community meeting today about getting packaging related changes reviewed. Some of the packaging changes are Multi-OS related and specific to openSUSE. I am not sure if all the cores are comfortable reviewing packaging changes. If that's the case then they should request reviews from folks that know about RPM packaging and/or rely on +1 input from those people who know about those changes. Another option would be to add cores that can focus on the packaging aspects of these repos for the centos and opensuse specfile changes. I apperciate all your input. Thanks Sau! From dtroyer at gmail.com Wed Oct 23 16:47:51 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 23 Oct 2019 11:47:51 -0500 Subject: [Starlingx-discuss] Gerrit Dashboard followup Message-ID: I showed a quick overview of Gerrit Dashboards in the StarlingX Community meeting this morning, I added a bit more information and some documentation links to the etherpad[0]. OpenDev is still using Gerrit v2.13 so the current Gerrit docs will have new features not available in OpenDev yet. The version of docs useful here are at [1] and [2]. gerrit-dash-creator[3] is a tool initially developed by Sean Dague that takes Gerrit queries written in an INI-format style and translates them into the rather long user URLs that Gerrit actually uses. Most people bookmark those or embed them in a page somewhere to share them. I have heard of teams using URL shortener services too. There are dashboards for a number of OpenStack projects in that repo, including one for an overview of StarlingX repos. (I mentioned a pending review during the meeting, that has merged and the starlingx dashboard is functional.) I have included a simpler example in the etherpad showing the open reviews for the repos that the TSC usually reviews, starlingx/governance and starlingx/specs. I should note that when attempting to add these URLs to the wiki[4] I was having trouble getting the links to work directly, I have updated them and they are working for me now. dt [0] https://etherpad.openstack.org/p/stx-gerrit-dashboards [1] https://review.opendev.org/Documentation/user-dashboards.html [2] https://review.opendev.org/Documentation/user-search.html [3] https://opendev.org/x/gerrit-dash-creator [4] https://wiki.openstack.org/wiki/StarlingX (second column in the last row, at the bottom) -- Dean Troyer dtroyer at gmail.com From bruce.e.jones at intel.com Wed Oct 23 16:55:42 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 23 Oct 2019 16:55:42 +0000 Subject: [Starlingx-discuss] Gerrit Dashboard followup In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BDFBFC4A2@fmsmsx123.amr.corp.intel.com> Very cool, thanks Dean! Maybe the teams could each add a link to their review dashboards on their wiki page? brucej -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Wednesday, October 23, 2019 9:48 AM To: starlingx Subject: [Starlingx-discuss] Gerrit Dashboard followup I showed a quick overview of Gerrit Dashboards in the StarlingX Community meeting this morning, I added a bit more information and some documentation links to the etherpad[0]. OpenDev is still using Gerrit v2.13 so the current Gerrit docs will have new features not available in OpenDev yet. The version of docs useful here are at [1] and [2]. gerrit-dash-creator[3] is a tool initially developed by Sean Dague that takes Gerrit queries written in an INI-format style and translates them into the rather long user URLs that Gerrit actually uses. Most people bookmark those or embed them in a page somewhere to share them. I have heard of teams using URL shortener services too. There are dashboards for a number of OpenStack projects in that repo, including one for an overview of StarlingX repos. (I mentioned a pending review during the meeting, that has merged and the starlingx dashboard is functional.) I have included a simpler example in the etherpad showing the open reviews for the repos that the TSC usually reviews, starlingx/governance and starlingx/specs. I should note that when attempting to add these URLs to the wiki[4] I was having trouble getting the links to work directly, I have updated them and they are working for me now. dt [0] https://etherpad.openstack.org/p/stx-gerrit-dashboards [1] https://review.opendev.org/Documentation/user-dashboards.html [2] https://review.opendev.org/Documentation/user-search.html [3] https://opendev.org/x/gerrit-dash-creator [4] https://wiki.openstack.org/wiki/StarlingX (second column in the last row, at the bottom) -- 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 ada.cabrales at intel.com Wed Oct 23 17:41:48 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Wed, 23 Oct 2019 17:41:48 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes for 10/22 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CEFE017@FMSMSX114.amr.corp.intel.com> Agenda for 10/22 Attendees: Elio, Al, Cristopher, Fernando, JC, Jose, JP, Maria P, Ada, Richo, Yang 1. Sanity status Intel Build system broken since Friday. It was restored yesterday, but https://review.opendev.org/#/c/689438/ - broke standard and external storage. WindRiver Same as Intel. https://bugs.launchpad.net/starlingx/+bug/1848721 - Another issue with platform-integ-app failing. Unified sanity On track for 10/28? Cristopher to work on the setup for splitting the run in bare metal environment. Yang to send an email for final sync - Ada to involve the required people to the thread. 2. stx.3.0 testing updates Feature testing Tracker - https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit?usp=sharing Distributed cloud - Yang 52% of progress - checking on the failure, not knowing if it's a procedure or a real issue. Backup and restore - Yang 63% progress, 2 failures with launchpads associated. Fault Containerization - Fer https://bugs.launchpad.net/starlingx/+bug/1848094 - asking Ghada what else is missing in the launchpad. Add a test for checking the FM container end point has switch to https. - Pending Upversion to train - JC EB delivered last week. It works ok in virt environment, but fails in Bare metal (related to nova) a new EB is being generated. 12 tests done: network and glance. GPU for K8 - Richo Basic tests done. One test for using the feature will be done as second priority if time allows it. Tested on standard. QAT for K8 - Richo Basic test done. Using exercising the feature will be done if we have time available. Executed in a EB. Redfish - Cristopher New tests cases to be created for provisioning (bulk installs). - status? Let's work on setup an IPv6 lab for running test on this infra. - JC to send a reminder for getting the info/steps requested. 82% of progress. Due date will be EOW. Infra & Cluster monitoring - Yang Tests defined are done. Will review for making sure on the coverage. Regression testing: Tracker - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit?usp=sharing Please make sure to use the tag stx.regression for all the launchpads created coming out from these tests. Automated robot - ~95% done, please update the report. For gnocchi - yes, it's disabled by default. Will double check failures to make sure they are real. Automated pytest - will collect the data. Some has been run. Manual - 46% of progress. A launchpad created - SSH / SCP to VM failed using NAMESPACE while IP is assigned by Horizon https://bugs.launchpad.net/starlingx/+bug/1835807 https://bugs.launchpad.net/starlingx/+bug/1836252 3. Opens Elio - We are in the 3rd week of regression, 4 weeks left. -- Ada From vm.rod25 at gmail.com Wed Oct 23 19:49:36 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Wed, 23 Oct 2019 14:49:36 -0500 Subject: [Starlingx-discuss] Performance test framework approved and next steps Message-ID: Hi StarlingX team I am pleased to announce that the specification for the performance test suite framework has been accepted: https://review.opendev.org/#/c/677287/ The proposed change is to create a set of scripts and documentation under the StarlingX testing repository (https://opendev.org/starlingx/test) that anyone can use to measure the metric they need under their hardware and software environment/configuration. The next step after the approval of the specification is to send the Gerrit reviews for the test cases. We have a list of test cases for R3.0 preparation, they are partially automated (thanks to all the developers that help on this process): https://drive.google.com/open?id=1Nr12zDRXf34kpjiA0LsFLU8GIpMY8Y-H2zmiC96CD4A These partially automated tests will be uploaded for now into a scripts/ directory at the same directory layer as automated-pytest-suite, this until we have them fully automated and be moved inside automated-pytest-suite directory. This mail is to call for volunteers willing to help to code. If anyone is interested to develop or migrate an existing performance test, please let us know and we will be more than happy to help you with the development/migration. Any help is more than appreciated. Thanks Victor Rodriguez From bruce.e.jones at intel.com Wed Oct 23 20:55:34 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 23 Oct 2019 20:55:34 +0000 Subject: [Starlingx-discuss] PSA: Docs Howto Message-ID: <9A85D2917C58154C960D95352B22818BDFBFC7EF@fmsmsx123.amr.corp.intel.com> This is a Public Service Announcement. If you are interested in contributing to the StarlingX documentation, here are the details for what you need to do. The Docs team publishes a Contributor's Guide [1] that describes the process. The documents are in a format called reStructutedText [2] which is a simple markup language. You should install the "tox" tool on your system, which you can run in your docs repo ("# tox") to check your changes for correctness and to see how they look - tox generates HTML files from your repo that can be found in your browser by opening file:///docs/build/html, which should look just like docs.starlingX.io. You can navigate through the links to find your changes and check them out. Please let me or the Docs team know if you have any questions, and feel free to join our weekly call on Wednesdays at 12:30 Pacific (3:30 Eastern). Thank you! Brucej [1] https://docs.starlingx.io/contributor/doc_contribute_guide.html [2] http://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Thu Oct 24 00:12:45 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Thu, 24 Oct 2019 00:12:45 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 In-Reply-To: <151EE31B9FCCA54397A757BC674650F0C15D07C7@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0C15D07C7@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F36090E98@SHSMSX104.ccr.corp.intel.com> Ghada, In my last week's non-openstack-distr meeting, we reviewed the option to allow partial of features in without impact of stx.3.0 release schedule. So we are execute against that goal. The feature for ceph-containerization won't be functional - and that's why you have it "out" in your release tracking sheet. However, our master branch shall be open to accept the ready patches before MS3. Cindy Xie IAGS -----Original Message----- From: Khalil, Ghada Sent: Wednesday, October 23, 2019 11:15 PM To: Xie, Cindy ; Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; Rowsell, Brent Subject: RE: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Hi Cindy, Please see comment/questions inline. Ghada -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, October 23, 2019 9:49 AM To: Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; Rowsell, Brent Subject: Re: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Agenda & notes for 10/23 meeting: - Ceph containerization update (Tingjie) part#1: create helm-chart for rook and ceph-cluster: https://review.opendev.org/#/c/681457, feedback to seperate it into two patches. are you working w/ rook upstream community for the customization? Rook community is 1.1 version, backport the yaml files to StarlingX. Tingjie is not making any changes in the upstream rook component. AR: Tingjie/Martin: to update the patches into two patches. part#2: https://review.opendev.org/#/c/687340/ for configuration. Not completed yet, WIP test case is under development. part#3: rook plugin implementation w/ more features: still WIP, patch to be uploaded. Risk for stx.3.0 => goal is to have part#1 & part#2 finished. will review progress later. [[GK]] The ceph containerization feature has been deferred to stx.4.0 as per previous discussions (and request from Bruce). As the release prime, I prefer to limit risk to the upcoming MS-3 and regression plans and defer code submissions for this feature until the stx.3.0 release branch is created at RC1 (~ Nov 20). Is there a reason we need this code to go before then? You are already highlighting a risk above. Is this code completely benign? - CentOS 8.0 upgrade planning (Shuai) Shuai received xls sheet from Saul for kernel patch analysis against 4.19. RT kernel is not available for CentOS 8.0 yet - the RT kernel will release later on. Do not worry about RT kernel later. https://storyboard.openstack.org/#!/story/2006728 for kernel upgrade. Zhiguo is the owner. Making document for kernel patches for which ones need to be retained. AR for Shuai to send the xls to the mailing list for review. GCC compiler upgraded from 4.8 to 8.2. kernel drivers: not analyzed yet. https://storyboard.openstack.org/#!/story/2006729: RPM and sRPM upgrade, how many RPM & sRPM upgrade needed? AR: Shuai to provide a list for RPM and sRPM to be upgrade for CentOS 8.0 - CVE LP fixing - call for contribution (Cindy): we have 12 CVE to be fixed. anybody who is interested, send Cindy email, I will add you onto CVE watching list. The expectation is RC1 (11/20th) for both stx.3.0 and stx.2.0 This is good learning experience to start working as StarlingX developer. - Opens (all) Cindy Xie IAGS -----Original Message----- From: Xie, Cindy Sent: Tuesday, October 22, 2019 9:05 PM To: Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; 'Rowsell, Brent' Subject: Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Agenda for 10/23 meeting: - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade planning (Shuai Zhao) - CVE LP fixing - call for contribution (Cindy) - Opens (all) Cindy Xie -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W; Sun, Austin Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, October 23, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . 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 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Brent.Rowsell at windriver.com Thu Oct 24 01:39:58 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Thu, 24 Oct 2019 01:39:58 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F36090E98@SHSMSX104.ccr.corp.intel.com> References: <151EE31B9FCCA54397A757BC674650F0C15D07C7@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F36090E98@SHSMSX104.ccr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EC26FDE49@ALA-MBD.corp.ad.wrs.com> Cindy, Please see my comments on part 1 in the gerrit review. I don't understand why we need to clone upstream helm charts into StarlingX vs consuming them from the upstream project. Thanks, Brent -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, October 23, 2019 8:13 PM To: Khalil, Ghada ; Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; Rowsell, Brent Subject: RE: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Ghada, In my last week's non-openstack-distr meeting, we reviewed the option to allow partial of features in without impact of stx.3.0 release schedule. So we are execute against that goal. The feature for ceph-containerization won't be functional - and that's why you have it "out" in your release tracking sheet. However, our master branch shall be open to accept the ready patches before MS3. Cindy Xie IAGS -----Original Message----- From: Khalil, Ghada Sent: Wednesday, October 23, 2019 11:15 PM To: Xie, Cindy ; Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; Rowsell, Brent Subject: RE: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Hi Cindy, Please see comment/questions inline. Ghada -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, October 23, 2019 9:49 AM To: Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; Rowsell, Brent Subject: Re: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Agenda & notes for 10/23 meeting: - Ceph containerization update (Tingjie) part#1: create helm-chart for rook and ceph-cluster: https://review.opendev.org/#/c/681457, feedback to seperate it into two patches. are you working w/ rook upstream community for the customization? Rook community is 1.1 version, backport the yaml files to StarlingX. Tingjie is not making any changes in the upstream rook component. AR: Tingjie/Martin: to update the patches into two patches. part#2: https://review.opendev.org/#/c/687340/ for configuration. Not completed yet, WIP test case is under development. part#3: rook plugin implementation w/ more features: still WIP, patch to be uploaded. Risk for stx.3.0 => goal is to have part#1 & part#2 finished. will review progress later. [[GK]] The ceph containerization feature has been deferred to stx.4.0 as per previous discussions (and request from Bruce). As the release prime, I prefer to limit risk to the upcoming MS-3 and regression plans and defer code submissions for this feature until the stx.3.0 release branch is created at RC1 (~ Nov 20). Is there a reason we need this code to go before then? You are already highlighting a risk above. Is this code completely benign? - CentOS 8.0 upgrade planning (Shuai) Shuai received xls sheet from Saul for kernel patch analysis against 4.19. RT kernel is not available for CentOS 8.0 yet - the RT kernel will release later on. Do not worry about RT kernel later. https://storyboard.openstack.org/#!/story/2006728 for kernel upgrade. Zhiguo is the owner. Making document for kernel patches for which ones need to be retained. AR for Shuai to send the xls to the mailing list for review. GCC compiler upgraded from 4.8 to 8.2. kernel drivers: not analyzed yet. https://storyboard.openstack.org/#!/story/2006729: RPM and sRPM upgrade, how many RPM & sRPM upgrade needed? AR: Shuai to provide a list for RPM and sRPM to be upgrade for CentOS 8.0 - CVE LP fixing - call for contribution (Cindy): we have 12 CVE to be fixed. anybody who is interested, send Cindy email, I will add you onto CVE watching list. The expectation is RC1 (11/20th) for both stx.3.0 and stx.2.0 This is good learning experience to start working as StarlingX developer. - Opens (all) Cindy Xie IAGS -----Original Message----- From: Xie, Cindy Sent: Tuesday, October 22, 2019 9:05 PM To: Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; 'Rowsell, Brent' Subject: Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Agenda for 10/23 meeting: - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade planning (Shuai Zhao) - CVE LP fixing - call for contribution (Cindy) - Opens (all) Cindy Xie -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W; Sun, Austin Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, October 23, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . 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 _______________________________________________ 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 Oct 24 02:06:15 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 24 Oct 2019 02:06:15 +0000 Subject: [Starlingx-discuss] About openstack train upgrade status Message-ID: <93814834B4855241994F290E959305C7530E50B0@SHSMSX104.ccr.corp.intel.com> Hi all, So far, we have finished openstack release train upgrade and openstack-helm/helm-infra upgrade. Story: https://storyboard.openstack.org/#!/story/2006544 Full Sanity test is good for the engineering build, thanks JC!! Thanks Bob, AI, Saul and other guys to give some good comments!! Next step: Let's push below 6 patches merged together! Current status summarized as below. 1) Openstack upgrade Finished 13 services upgrade, including nova, neutron, keystone, cinder, glance, placement, aodh, ironic, panko, barbican, ceilometer, heat, horizon. 2) Openstack-helm/helm-infra upgrade Upgrade openstack-helm to below version. 13 patches removed commit 82c72367c85ca94270f702661c7b984899c1ae38 //Date: Sat Sep 14 06:40:03 2019 +0000 Upgrade openstack-helm-infra to below version. 1 patch removed commit c9d6676bf9a5aceb311dc31dadd07cba6a3d6392 //Date: Mon Sep 16 17:15:12 2019 +0000 6 patches submitted for review, your comments are appreciated, thanks! https://review.opendev.org/#/c/683886/ openstack-helm upgrade https://review.opendev.org/#/c/683910/ openstack-helm-infra upgrade https://review.opendev.org/#/c/684166/ manifest.yaml update https://review.opendev.org/#/c/687441/ update docker image directives file https://review.opendev.org/#/c/687197/ update download list https://review.opendev.org/#/c/688105/ build wheels tarball for train upgrade Thanks! zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From yan.chen at intel.com Thu Oct 24 02:21:18 2019 From: yan.chen at intel.com (Chen, Yan) Date: Thu, 24 Oct 2019 02:21:18 +0000 Subject: [Starlingx-discuss] About openstack train upgrade status In-Reply-To: <93814834B4855241994F290E959305C7530E50B0@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C7530E50B0@SHSMSX104.ccr.corp.intel.com> Message-ID: <72AD03D27224C74982BE13246D75B39739A65E9B@SHSMSX103.ccr.corp.intel.com> Add 3 StarlingX Dashboard patches, please also help to review. https://review.opendev.org/687200 (project: stx-manifest) upgrade StarlingX dashboard with stable/train. https://review.opendev.org/687203 (project: stx-gui) update stx local_settings for horizon train upgrade. https://review.opendev.org/687204 (project: stx-upstream) update upstream project for horizon train upgrade. Thanks! Yan From: Liu, ZhipengS Sent: Thursday, October 24, 2019 10:06 To: starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada ; Jones, Bruce E ; Alonso, Juan Carlos Subject: [Starlingx-discuss] About openstack train upgrade status Hi all, So far, we have finished openstack release train upgrade and openstack-helm/helm-infra upgrade. Story: https://storyboard.openstack.org/#!/story/2006544 Full Sanity test is good for the engineering build, thanks JC!! Thanks Bob, AI, Saul and other guys to give some good comments!! Next step: Let's push below 6 patches merged together! Current status summarized as below. 1) Openstack upgrade Finished 13 services upgrade, including nova, neutron, keystone, cinder, glance, placement, aodh, ironic, panko, barbican, ceilometer, heat, horizon. 2) Openstack-helm/helm-infra upgrade Upgrade openstack-helm to below version. 13 patches removed commit 82c72367c85ca94270f702661c7b984899c1ae38 //Date: Sat Sep 14 06:40:03 2019 +0000 Upgrade openstack-helm-infra to below version. 1 patch removed commit c9d6676bf9a5aceb311dc31dadd07cba6a3d6392 //Date: Mon Sep 16 17:15:12 2019 +0000 6 patches submitted for review, your comments are appreciated, thanks! https://review.opendev.org/#/c/683886/ openstack-helm upgrade https://review.opendev.org/#/c/683910/ openstack-helm-infra upgrade https://review.opendev.org/#/c/684166/ manifest.yaml update https://review.opendev.org/#/c/687441/ update docker image directives file https://review.opendev.org/#/c/687197/ update download list https://review.opendev.org/#/c/688105/ build wheels tarball for train upgrade Thanks! zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Thu Oct 24 03:22:52 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Thu, 24 Oct 2019 03:22:52 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EC26FDE49@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0C15D07C7@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F36090E98@SHSMSX104.ccr.corp.intel.com> <2588653EBDFFA34B982FAF00F1B4844EC26FDE49@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F3609116F@SHSMSX104.ccr.corp.intel.com> Hi, Brent, I fully understand these two patches need to more work, and this was discussed in yesterday's meeting. Tingjie & Martin will work together to address the comments. If the patches are not ready for merge before MS3 (expecting this week given Train upgrade status), then they will have to wait until RC1 branch out. I made it clear to the developers. Cindy Xie IAGS -----Original Message----- From: Rowsell, Brent Sent: Thursday, October 24, 2019 9:40 AM To: Xie, Cindy ; Khalil, Ghada ; Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Cindy, Please see my comments on part 1 in the gerrit review. I don't understand why we need to clone upstream helm charts into StarlingX vs consuming them from the upstream project. Thanks, Brent -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, October 23, 2019 8:13 PM To: Khalil, Ghada ; Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; Rowsell, Brent Subject: RE: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Ghada, In my last week's non-openstack-distr meeting, we reviewed the option to allow partial of features in without impact of stx.3.0 release schedule. So we are execute against that goal. The feature for ceph-containerization won't be functional - and that's why you have it "out" in your release tracking sheet. However, our master branch shall be open to accept the ready patches before MS3. Cindy Xie IAGS -----Original Message----- From: Khalil, Ghada Sent: Wednesday, October 23, 2019 11:15 PM To: Xie, Cindy ; Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; Rowsell, Brent Subject: RE: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Hi Cindy, Please see comment/questions inline. Ghada -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, October 23, 2019 9:49 AM To: Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; Rowsell, Brent Subject: Re: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Agenda & notes for 10/23 meeting: - Ceph containerization update (Tingjie) part#1: create helm-chart for rook and ceph-cluster: https://review.opendev.org/#/c/681457, feedback to seperate it into two patches. are you working w/ rook upstream community for the customization? Rook community is 1.1 version, backport the yaml files to StarlingX. Tingjie is not making any changes in the upstream rook component. AR: Tingjie/Martin: to update the patches into two patches. part#2: https://review.opendev.org/#/c/687340/ for configuration. Not completed yet, WIP test case is under development. part#3: rook plugin implementation w/ more features: still WIP, patch to be uploaded. Risk for stx.3.0 => goal is to have part#1 & part#2 finished. will review progress later. [[GK]] The ceph containerization feature has been deferred to stx.4.0 as per previous discussions (and request from Bruce). As the release prime, I prefer to limit risk to the upcoming MS-3 and regression plans and defer code submissions for this feature until the stx.3.0 release branch is created at RC1 (~ Nov 20). Is there a reason we need this code to go before then? You are already highlighting a risk above. Is this code completely benign? - CentOS 8.0 upgrade planning (Shuai) Shuai received xls sheet from Saul for kernel patch analysis against 4.19. RT kernel is not available for CentOS 8.0 yet - the RT kernel will release later on. Do not worry about RT kernel later. https://storyboard.openstack.org/#!/story/2006728 for kernel upgrade. Zhiguo is the owner. Making document for kernel patches for which ones need to be retained. AR for Shuai to send the xls to the mailing list for review. GCC compiler upgraded from 4.8 to 8.2. kernel drivers: not analyzed yet. https://storyboard.openstack.org/#!/story/2006729: RPM and sRPM upgrade, how many RPM & sRPM upgrade needed? AR: Shuai to provide a list for RPM and sRPM to be upgrade for CentOS 8.0 - CVE LP fixing - call for contribution (Cindy): we have 12 CVE to be fixed. anybody who is interested, send Cindy email, I will add you onto CVE watching list. The expectation is RC1 (11/20th) for both stx.3.0 and stx.2.0 This is good learning experience to start working as StarlingX developer. - Opens (all) Cindy Xie IAGS -----Original Message----- From: Xie, Cindy Sent: Tuesday, October 22, 2019 9:05 PM To: Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; 'Rowsell, Brent' Subject: Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Agenda for 10/23 meeting: - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade planning (Shuai Zhao) - CVE LP fixing - call for contribution (Cindy) - Opens (all) Cindy Xie -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W; Sun, Austin Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, October 23, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . 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 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cristopher.j.lemus.contreras at intel.com Thu Oct 24 07:58:25 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Thu, 24 Oct 2019 02:58:25 -0500 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$6pqs0g@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191024T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From Brent.Rowsell at windriver.com Thu Oct 24 13:52:55 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Thu, 24 Oct 2019 13:52:55 +0000 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting In-Reply-To: <000001d58a71$c90938e0$5b1baaa0$@neusoft.com> References: <2FD5DDB5A04D264C80D42CA35194914F35F28711@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F36086E35@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F36088FA4@SHSMSX104.ccr.corp.intel.com> <95b0f80b-ed39-32b7-e2f8-aae644b081de@linux.intel.com> <000001d58a71$c90938e0$5b1baaa0$@neusoft.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EC26FFC1F@ALA-MBD.corp.ad.wrs.com> Thanks. Can you elaborate on " we encountered a lot of problems during the porting of the kernel" Thanks, Brent -----Original Message----- From: zhao.shuai [mailto:zhaos at neusoft.com] Sent: Thursday, October 24, 2019 9:49 AM To: 'Saul Wold' ; 'Lin, Shuicheng' ; starlingx-discuss at lists.starlingx.io Cc: Rowsell, Brent ; 'Xie, Cindy' Subject: 回复: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting Regarding the task of upgrading the StarlingX kernel version to CentOS 4.18. Our team currently have a preliminary comparison of the RPM/ and SRPM packages and the kernel patches analysis. Please refer to the attachment for the results of the initial analysis. As the same time, CentOS 4.18 Kernel Source is being compiled and ported . yes we encountered a lot of problems during the porting of the kernel. We are keeping in touch with Saul and Shuicheng in real time. If there is any progress, we will report to you in the Mail list in time. Thank you! Best Regards Wish you happy everyday! -------------------------------- Shuai - Neusoft -----邮件原件----- 发件人: Saul Wold 发送时间: 2019年10月18日 5:36 收件人: starlingx-discuss at lists.starlingx.io 抄送: Rowsell, Brent 主题: Re: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting Please find attached the spreadsheet analyzing the Kernel patches to the existing CentOS 3.10 kernel. As mentioned, most of the patches can be dropped, except for the Notification of Death patch. My understanding is that changes have been made to StarlingX to support the Workqueue CPU affinity model with isolcpus instead of the kthread model that is in the 3.10 kernel. If this is actually the case then we can drop the cpu affinity related patches also. (this would be a good thing). Don't hesitate to reach out and ask for help with the kernel and/or CentOS 8 User space updates. Sau! On 10/16/19 6:53 AM, Xie, Cindy wrote: > Agenda & notes for 10/16 meeting: > > . Ceph containerization update (Tingjie) > https://review.opendev.org/#/c/681457/ this is for Helm chart definition, can be review now. > https://review.opendev.org/#/c/687340/ for Helm overrides framework, need to extend later. > verified in AIO and multi-node provision. > configuration needs to be override according to STX parameters. > Martin working on this for parameters to align w/ the native deployment. > for stx.3.0: only to merge the implantation for Helm chart and override framework. and rook-plugin which support sysinv, this can co-exist w/ current native ceph deployment. > test case development is in progress, Tingjie will sync with Fernando. > for sysinv, still need to working on patches, not ready for upload/review. > AR: Tingjie to send email to the mailing list for the current status & planning for include partial implementation without impacting the native Ceph functionality. > > . Debranding update (Saul) > Starting from the tools repo, the tools in the build area to debrand the mirroring process. Part of this is for ease of use for build steps. Very early stage. Not fit in stx.3.0 scope. > https://storyboard.openstack.org/#!/story/2006387, call volunteer from the community. > > . CentOS 8 upgrade planning (Cindy) CentOS 8.0 2 stories created: > https://storyboard.openstack.org/#!/story/2006728, the kernel inside CentOS 8 is 4.18, there is no RT kernel. > https://storyboard.openstack.org/#!/story/2006729 > Shuai is working on new kernel onto build system. Need to understand each patches. there was an earlier analysis for kernel patches available. > AR: Saul please share this analysis to Shuai. against 4.19 kernel some long time ago. > See > https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAu > gOWXMjB7VIrfc/edit#gid=311578025 Tab Kernel Patches Details > https://github.com/xe1gyq/linux/commits/v4.19 > https://github.com/xe1gyq/linux/commits/v4.18 > AR: Shuai to provide an Excel sheet to compare RPM/sRPM in StarlingX > and in CentOS 8.0 > > . Opens - none > _____________________________________________ > From: Xie, Cindy > Sent: Tuesday, October 15, 2019 9:39 PM > To: Wold, Saul ; > 'starlingx-discuss at lists.starlingx.io' > ; 'Rowsell, Brent' > > Subject: RE: Weekly StarlingX non-OpenStack distro meeting > > > Agenda: > - Ceph containerization update (Tingjie) > - Debranding update (Saul) > - CentOS 8 upgrade planning (Cindy) > - Opens > > Cindy Xie > IAGS > > http://starlingx.io/ > > > -----Original Appointment----- > From: Xie, Cindy > Sent: Thursday, April 25, 2019 5:42 PM > To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' > Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; > 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, > Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, > Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W > Subject: Weekly StarlingX non-OpenStack distro meeting > When: Wednesday, October 16, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. > Where: https://zoom.us/j/342730236 > > > . 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 > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > --------------------------------------------------------------------------------------------------- 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. --------------------------------------------------------------------------------------------------- From Ghada.Khalil at windriver.com Thu Oct 24 13:55:39 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 24 Oct 2019 13:55:39 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F36090E98@SHSMSX104.ccr.corp.intel.com> References: <151EE31B9FCCA54397A757BC674650F0C15D07C7@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F36090E98@SHSMSX104.ccr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0C15D12B8@ALA-MBD.corp.ad.wrs.com> Hi Cindy, MS3 is planned for this week. Based on the status in the minutes below, I didn't think the code will be ready in time; you already highlighted a risk below. I also asked for your assessment on the risk of this code and whether it is benign or not. To re-iterate my questions, will this code be ready to merge this week? Is it benign? Ghada -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, October 23, 2019 8:13 PM To: Khalil, Ghada; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; Rowsell, Brent Subject: RE: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Ghada, In my last week's non-openstack-distr meeting, we reviewed the option to allow partial of features in without impact of stx.3.0 release schedule. So we are execute against that goal. The feature for ceph-containerization won't be functional - and that's why you have it "out" in your release tracking sheet. However, our master branch shall be open to accept the ready patches before MS3. Cindy Xie IAGS -----Original Message----- From: Khalil, Ghada Sent: Wednesday, October 23, 2019 11:15 PM To: Xie, Cindy ; Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; Rowsell, Brent Subject: RE: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Hi Cindy, Please see comment/questions inline. Ghada -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, October 23, 2019 9:49 AM To: Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; Rowsell, Brent Subject: Re: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Agenda & notes for 10/23 meeting: - Ceph containerization update (Tingjie) part#1: create helm-chart for rook and ceph-cluster: https://review.opendev.org/#/c/681457, feedback to seperate it into two patches. are you working w/ rook upstream community for the customization? Rook community is 1.1 version, backport the yaml files to StarlingX. Tingjie is not making any changes in the upstream rook component. AR: Tingjie/Martin: to update the patches into two patches. part#2: https://review.opendev.org/#/c/687340/ for configuration. Not completed yet, WIP test case is under development. part#3: rook plugin implementation w/ more features: still WIP, patch to be uploaded. Risk for stx.3.0 => goal is to have part#1 & part#2 finished. will review progress later. [[GK]] The ceph containerization feature has been deferred to stx.4.0 as per previous discussions (and request from Bruce). As the release prime, I prefer to limit risk to the upcoming MS-3 and regression plans and defer code submissions for this feature until the stx.3.0 release branch is created at RC1 (~ Nov 20). Is there a reason we need this code to go before then? You are already highlighting a risk above. Is this code completely benign? - CentOS 8.0 upgrade planning (Shuai) Shuai received xls sheet from Saul for kernel patch analysis against 4.19. RT kernel is not available for CentOS 8.0 yet - the RT kernel will release later on. Do not worry about RT kernel later. https://storyboard.openstack.org/#!/story/2006728 for kernel upgrade. Zhiguo is the owner. Making document for kernel patches for which ones need to be retained. AR for Shuai to send the xls to the mailing list for review. GCC compiler upgraded from 4.8 to 8.2. kernel drivers: not analyzed yet. https://storyboard.openstack.org/#!/story/2006729: RPM and sRPM upgrade, how many RPM & sRPM upgrade needed? AR: Shuai to provide a list for RPM and sRPM to be upgrade for CentOS 8.0 - CVE LP fixing - call for contribution (Cindy): we have 12 CVE to be fixed. anybody who is interested, send Cindy email, I will add you onto CVE watching list. The expectation is RC1 (11/20th) for both stx.3.0 and stx.2.0 This is good learning experience to start working as StarlingX developer. - Opens (all) Cindy Xie IAGS -----Original Message----- From: Xie, Cindy Sent: Tuesday, October 22, 2019 9:05 PM To: Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; 'Rowsell, Brent' Subject: Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Agenda for 10/23 meeting: - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade planning (Shuai Zhao) - CVE LP fixing - call for contribution (Cindy) - Opens (all) Cindy Xie -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W; Sun, Austin Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, October 23, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . 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 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Thu Oct 24 14:13:55 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Thu, 24 Oct 2019 14:13:55 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 In-Reply-To: <151EE31B9FCCA54397A757BC674650F0C15D12B8@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0C15D07C7@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F36090E98@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0C15D12B8@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F36091B22@SHSMSX104.ccr.corp.intel.com> Those patches will not hold MS3 declare as we agreed earlier. Once you declare it, then they will miss the deadline. But I do not want to hold their attempt to do their best to catch up the deadline. Cindy Xie -----Original Message----- From: Khalil, Ghada Sent: Thursday, October 24, 2019 9:56 PM To: Xie, Cindy ; Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; Rowsell, Brent Subject: RE: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Hi Cindy, MS3 is planned for this week. Based on the status in the minutes below, I didn't think the code will be ready in time; you already highlighted a risk below. I also asked for your assessment on the risk of this code and whether it is benign or not. To re-iterate my questions, will this code be ready to merge this week? Is it benign? Ghada -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, October 23, 2019 8:13 PM To: Khalil, Ghada; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; Rowsell, Brent Subject: RE: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Ghada, In my last week's non-openstack-distr meeting, we reviewed the option to allow partial of features in without impact of stx.3.0 release schedule. So we are execute against that goal. The feature for ceph-containerization won't be functional - and that's why you have it "out" in your release tracking sheet. However, our master branch shall be open to accept the ready patches before MS3. Cindy Xie IAGS -----Original Message----- From: Khalil, Ghada Sent: Wednesday, October 23, 2019 11:15 PM To: Xie, Cindy ; Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; Rowsell, Brent Subject: RE: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Hi Cindy, Please see comment/questions inline. Ghada -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, October 23, 2019 9:49 AM To: Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; Rowsell, Brent Subject: Re: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Agenda & notes for 10/23 meeting: - Ceph containerization update (Tingjie) part#1: create helm-chart for rook and ceph-cluster: https://review.opendev.org/#/c/681457, feedback to seperate it into two patches. are you working w/ rook upstream community for the customization? Rook community is 1.1 version, backport the yaml files to StarlingX. Tingjie is not making any changes in the upstream rook component. AR: Tingjie/Martin: to update the patches into two patches. part#2: https://review.opendev.org/#/c/687340/ for configuration. Not completed yet, WIP test case is under development. part#3: rook plugin implementation w/ more features: still WIP, patch to be uploaded. Risk for stx.3.0 => goal is to have part#1 & part#2 finished. will review progress later. [[GK]] The ceph containerization feature has been deferred to stx.4.0 as per previous discussions (and request from Bruce). As the release prime, I prefer to limit risk to the upcoming MS-3 and regression plans and defer code submissions for this feature until the stx.3.0 release branch is created at RC1 (~ Nov 20). Is there a reason we need this code to go before then? You are already highlighting a risk above. Is this code completely benign? - CentOS 8.0 upgrade planning (Shuai) Shuai received xls sheet from Saul for kernel patch analysis against 4.19. RT kernel is not available for CentOS 8.0 yet - the RT kernel will release later on. Do not worry about RT kernel later. https://storyboard.openstack.org/#!/story/2006728 for kernel upgrade. Zhiguo is the owner. Making document for kernel patches for which ones need to be retained. AR for Shuai to send the xls to the mailing list for review. GCC compiler upgraded from 4.8 to 8.2. kernel drivers: not analyzed yet. https://storyboard.openstack.org/#!/story/2006729: RPM and sRPM upgrade, how many RPM & sRPM upgrade needed? AR: Shuai to provide a list for RPM and sRPM to be upgrade for CentOS 8.0 - CVE LP fixing - call for contribution (Cindy): we have 12 CVE to be fixed. anybody who is interested, send Cindy email, I will add you onto CVE watching list. The expectation is RC1 (11/20th) for both stx.3.0 and stx.2.0 This is good learning experience to start working as StarlingX developer. - Opens (all) Cindy Xie IAGS -----Original Message----- From: Xie, Cindy Sent: Tuesday, October 22, 2019 9:05 PM To: Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; 'Rowsell, Brent' Subject: Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/23 Agenda for 10/23 meeting: - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade planning (Shuai Zhao) - CVE LP fixing - call for contribution (Cindy) - Opens (all) Cindy Xie -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W; Sun, Austin Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, October 23, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . 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 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From sgw at linux.intel.com Thu Oct 24 15:46:15 2019 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 24 Oct 2019 08:46:15 -0700 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSNOiAgV2Vla2x5IFN0YXJsaW5n?= =?utf-8?q?X_non-OpenStack_distro_meeting?= In-Reply-To: <000001d58a71$c90938e0$5b1baaa0$@neusoft.com> References: <2FD5DDB5A04D264C80D42CA35194914F35F28711@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F36086E35@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F36088FA4@SHSMSX104.ccr.corp.intel.com> <95b0f80b-ed39-32b7-e2f8-aae644b081de@linux.intel.com> <000001d58a71$c90938e0$5b1baaa0$@neusoft.com> Message-ID: <728ff81a-523e-daf4-b27a-ed9a3db4587a@linux.intel.com> On 10/24/19 6:48 AM, zhao.shuai wrote: > Regarding the task of upgrading the StarlingX kernel version to CentOS 4.18. > Our team currently have a preliminary comparison of the RPM/ and SRPM packages and the kernel patches analysis. > Please refer to the attachment for the results of the initial analysis. > > As the same time, CentOS 4.18 Kernel Source is being compiled and ported . yes we encountered a lot of problems during the porting of the kernel. We are keeping in touch with Saul and Shuicheng in real time. > If there is any progress, we will report to you in the Mail list in time. > Can you please update us with regards to which patches you are still trying to carry/port? As Brent already asked, can you also please clarify what problems you encountered? As already mentioned, most of the patches can be dropped for 4.18 as they are backports to the 3.10 kernel. Where are you searching for packages to match the el7 vs el8 list? There will be packages that come out later from other teams as they are ported to CentOS 8. Are you searching the EPEL repos [0]? Thanks Sau! [0] http://mirror.pit.teraswitch.com/fedora/epel//8/Everything > Thank you! > > Best Regards > Wish you happy everyday! > -------------------------------- > Shuai - Neusoft > > > -----邮件原件----- > 发件人: Saul Wold > 发送时间: 2019年10月18日 5:36 > 收件人: starlingx-discuss at lists.starlingx.io > 抄送: Rowsell, Brent > 主题: Re: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting > > > Please find attached the spreadsheet analyzing the Kernel patches to the existing CentOS 3.10 kernel. > > As mentioned, most of the patches can be dropped, except for the Notification of Death patch. > > My understanding is that changes have been made to StarlingX to support the Workqueue CPU affinity model with isolcpus instead of the kthread model that is in the 3.10 kernel. If this is actually the case then we can drop the cpu affinity related patches also. (this would be a good thing). > > Don't hesitate to reach out and ask for help with the kernel and/or CentOS 8 User space updates. > > Sau! > > > > > On 10/16/19 6:53 AM, Xie, Cindy wrote: >> Agenda & notes for 10/16 meeting: >> >> . Ceph containerization update (Tingjie) >> https://review.opendev.org/#/c/681457/ this is for Helm chart definition, can be review now. >> https://review.opendev.org/#/c/687340/ for Helm overrides framework, need to extend later. >> verified in AIO and multi-node provision. >> configuration needs to be override according to STX parameters. >> Martin working on this for parameters to align w/ the native deployment. >> for stx.3.0: only to merge the implantation for Helm chart and override framework. and rook-plugin which support sysinv, this can co-exist w/ current native ceph deployment. >> test case development is in progress, Tingjie will sync with Fernando. >> for sysinv, still need to working on patches, not ready for upload/review. >> AR: Tingjie to send email to the mailing list for the current status & planning for include partial implementation without impacting the native Ceph functionality. >> >> . Debranding update (Saul) >> Starting from the tools repo, the tools in the build area to debrand the mirroring process. Part of this is for ease of use for build steps. Very early stage. Not fit in stx.3.0 scope. >> https://storyboard.openstack.org/#!/story/2006387, call volunteer from the community. >> >> . CentOS 8 upgrade planning (Cindy) CentOS 8.0 2 stories created: >> https://storyboard.openstack.org/#!/story/2006728, the kernel inside CentOS 8 is 4.18, there is no RT kernel. >> https://storyboard.openstack.org/#!/story/2006729 >> Shuai is working on new kernel onto build system. Need to understand each patches. there was an earlier analysis for kernel patches available. >> AR: Saul please share this analysis to Shuai. against 4.19 kernel some long time ago. >> See >> https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAu >> gOWXMjB7VIrfc/edit#gid=311578025 Tab Kernel Patches Details >> https://github.com/xe1gyq/linux/commits/v4.19 >> https://github.com/xe1gyq/linux/commits/v4.18 >> AR: Shuai to provide an Excel sheet to compare RPM/sRPM in StarlingX >> and in CentOS 8.0 >> >> . Opens - none >> _____________________________________________ >> From: Xie, Cindy >> Sent: Tuesday, October 15, 2019 9:39 PM >> To: Wold, Saul ; >> 'starlingx-discuss at lists.starlingx.io' >> ; 'Rowsell, Brent' >> >> Subject: RE: Weekly StarlingX non-OpenStack distro meeting >> >> >> Agenda: >> - Ceph containerization update (Tingjie) >> - Debranding update (Saul) >> - CentOS 8 upgrade planning (Cindy) >> - Opens >> >> Cindy Xie >> IAGS >> >> http://starlingx.io/ >> >> >> -----Original Appointment----- >> From: Xie, Cindy >> Sent: Thursday, April 25, 2019 5:42 PM >> To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' >> Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; >> 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, >> Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, >> Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W >> Subject: Weekly StarlingX non-OpenStack distro meeting >> When: Wednesday, October 16, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. >> Where: https://zoom.us/j/342730236 >> >> >> . 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 >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > > --------------------------------------------------------------------------------------------------- > 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. > --------------------------------------------------------------------------------------------------- > From Tao.Liu at windriver.com Thu Oct 24 18:27:12 2019 From: Tao.Liu at windriver.com (Liu, Tao) Date: Thu, 24 Oct 2019 18:27:12 +0000 Subject: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 In-Reply-To: References: Message-ID: <7242A3DC72E453498E3D783BBB134C3EA4EB1D03@ALA-MBD.corp.ad.wrs.com> Thanks Arce! A decision has been made to use OAM Interface and IP to bootstrap the subcloud. I have updated the document accordingly. The main change is to run the config_management script and enable OAM interface. Tao -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Monday, October 21, 2019 1:25 PM To: Liu, Tao; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 > Please add Distributed Cloud Configuration Guide to StarlingX R3.0 > Installation. Hi Tao, Distributed Cloud team, Here you have an early review of Distributed Cloud: https://review.opendev.org/#/c/689847/ We will take it as our base documentation and do the installation in our labs starting today, some changes likely coming. For now, please let us know if we need to add more people as Co-Authored-By. -------------- next part -------------- A non-text attachment was scrubbed... Name: Distributed Cloud Configuration Guide_V2.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 25456 bytes Desc: Distributed Cloud Configuration Guide_V2.docx URL: From David.Sullivan at windriver.com Thu Oct 24 21:52:03 2019 From: David.Sullivan at windriver.com (Sullivan, David) Date: Thu, 24 Oct 2019 21:52:03 +0000 Subject: [Starlingx-discuss] Change to default management_start_address Message-ID: Hello, As part of the fix for https://bugs.launchpad.net/starlingx/+bug/1848376 the calculation for the default management_start_address has been updated. Previously, with a default management subnet, the management_start_address (and floating controller address) would be 192.168.204.2. After this update 192.168.204.1 will be used for the management_start_address. This may impact you if you are used to working with 192.168.204.2 for the floating controller address. Thanks, David -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Thu Oct 24 22:27:27 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 24 Oct 2019 22:27:27 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191024 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-24 (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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006651.html Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Oct 24 22:33:13 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 24 Oct 2019 22:33:13 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Oct 24/2019 Message-ID: <151EE31B9FCCA54397A757BC674650F0C15D1864@ALA-MBD.corp.ad.wrs.com> Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - October 24 2019 stx.3.0 - Good progress on MS3. Expect to declare milestone early next week. - Feature Details: - https://docs.google.com/spreadsheets/d/1ZFR-9-riwhIwiBYBmWmi1qOVyHtgJ8Xk_FaF2jp5rY0/edit#gid=1010323020 - Upversion to train - Focus on updating the containerized openstack services only; leave baremetal as it is - 9 reviews are up - This is all the code needed as far as we know - stx-staging nova is no longer used since the "NUMA Aware Live Migration" merged in train - Sanity w/ train passing on AIO-DX & AIO-SX baremetal - Was not able to run sanity on standard & storage due to the regular sanity issue #1848721 - Plan to have the engineering build rebased by Zhipeng and re-run the sanity - Allow submission after the sanity is successful - Automated Regression: - Then start Intel Automated Regression right away -- 2wk duration - Ada will also ask Yang to schedule a WR openstack regression in parallel - The goal is to run as many TCs as possible to flush out issues early. - Feature Testing - Continue with testing; transition to testing on master once code is submitted. - Forecast to merge - Oct 31 - Kata Containers - Developer has done some testing, but more is needed - Test team has no bandwidth to formally test this feature - Agreed to continue working on this feature, but not allow submission until after RC1 - i.e. this will continue to be an stx.4.0 feature - All other features are coming in next week as well - Regression Test - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 - Completion Rate: 39% (up from 24%) - Feature Test - https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit#gid=968103774 - Completion Rate: 58% (up from 39%) From maria.g.perez.ibarra at intel.com Thu Oct 24 23:14:05 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 24 Oct 2019 23:14:05 +0000 Subject: [Starlingx-discuss] [ Regression testing - stx3.0 ] Report for 10/24/2019 Message-ID: StarlingX 3.0 Release Status: ISO: BUILD_ID=" 20191018T013000Z" from (link) ---------------------------------------------------------------------- MANUAL EXECUTION ---------------------------------------------------------------------- Overall Results: Total = 274 Pass = 158 Fail = 6 Blocked = 9 Not Run = 99 Obsolete = 2 Deferred = 0 Total executed = 164 Pass Rate = 96% Formula used : Pass Rate = (pass * 100) / (pass + fail) --------------------------------------------------------------------------- AUTOMATED ROBOT - INTEL --------------------------------------------------------------------------- Overall Results: Total = 202 Pass = 144 Fail = 19 Blocked = 38 Obsolete = 0 Deferred = 0 Not Valid = 1 Total executed = 163 Pass Rate = 88% Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- AUTOMATED PYTEST - WR --------------------------------------------------------------------------- Overall Results: Total = 467 Pass = 0 Fail = 0 Blocked = 0 Not Run = 467 Obsolete = 0 Deferred = 0 Total executed = 0 Pass Rate = Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- BUGS SSH / SCP to VM failed using NAMESPACE while IP is assigned by Horizon https://bugs.launchpad.net/starlingx/+bug/1849221 --------------------------------------------------------------------------- For more detail of the tests: https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 Regards! Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Fri Oct 25 01:39:13 2019 From: austin.sun at intel.com (Sun, Austin) Date: Fri, 25 Oct 2019 01:39:13 +0000 Subject: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 In-Reply-To: <7242A3DC72E453498E3D783BBB134C3EA4EB1D03@ALA-MBD.corp.ad.wrs.com> References: <7242A3DC72E453498E3D783BBB134C3EA4EB1D03@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Tao: Thanks your update . which gerrit or patch enhances using OAM interface and IP to bootstrap the subcloud ? has this patch already been merged ? Another question , will OAM ip in subcloud L3 connection to OAM ip in central cloud ? does it request mgmt ip in subcloud L2 connect to OAM ip in central cloud for V2? Thanks. BR Austin Sun. -----Original Message----- From: Liu, Tao Sent: Friday, October 25, 2019 2:27 AM To: Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Thanks Arce! A decision has been made to use OAM Interface and IP to bootstrap the subcloud. I have updated the document accordingly. The main change is to run the config_management script and enable OAM interface. Tao -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Monday, October 21, 2019 1:25 PM To: Liu, Tao; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 > Please add Distributed Cloud Configuration Guide to StarlingX R3.0 > Installation. Hi Tao, Distributed Cloud team, Here you have an early review of Distributed Cloud: https://review.opendev.org/#/c/689847/ We will take it as our base documentation and do the installation in our labs starting today, some changes likely coming. For now, please let us know if we need to add more people as Co-Authored-By. From thierry at openstack.org Fri Oct 25 09:17:03 2019 From: thierry at openstack.org (Thierry Carrez) Date: Fri, 25 Oct 2019 11:17:03 +0200 Subject: [Starlingx-discuss] [survey] StarlingX community dashboard In-Reply-To: <983fa25d-4e9c-1f29-fb03-6d85211d3058@openstack.org> References: <983fa25d-4e9c-1f29-fb03-6d85211d3058@openstack.org> Message-ID: <4fe6fab2-4ca0-0404-09a9-996e966f7f36@openstack.org> Thierry Carrez wrote: > The community dashboard at starlingx.biterg.io helps provide insights on > community activity and diversity for the StarlingX project. > > We created a short survey to help us assess how useful those dashboards > are to the community, as well as define key areas for future > improvements. It should take less than 2 minutes to complete. > > Please fill the survey at: > https://www.surveymonkey.com/r/5KW9X8J Last call for this! You have until the end of the week to fill this survey, and let us know if you find the StarlingX community dashboards useful or not. Only 5 people filled it so far... -- Thierry Carrez (ttx) From fuyong at neusoft.com Fri Oct 25 09:56:33 2019 From: fuyong at neusoft.com (=?utf-8?B?5LuY5YuH?=) Date: Fri, 25 Oct 2019 17:56:33 +0800 Subject: [Starlingx-discuss] =?utf-8?b?44CQU3RhcmxpbmdY44CRUmVnYXJkaW5n?= =?utf-8?q?_external_networking_issue?= Message-ID: <005401d58b1a$7be6c6f0$73b454d0$@neusoft.com> Hi StarlingX team we have deploy virtual All-in-one simplex machine and have a question to ask for help. 1. problem: we met a problem with how to connect the external networking in cirros or centos instance. 2. current status controller-0 IP: 10.10.10.3 cirros-vm1 IP: 172.16.100.188, from 172.16.100.188(cirros-vm1) ping external subnet ext_net:10.10.10.190 OK, from 172.16.100.188(cirros-vm1) ping 10.10.10.3 (controller-0) is not OK. from 172.16.100.188(cirros-vm1) ping 8.8.8.8 is not OK. from 10.10.10.3 (controller-0) ping 8.8.8.8 is OK. 3. configuration (1) ml2_conf.ini in container: neutron-ovs-agent-controller-0-937646f6-dtqcn: /etc/neutron/plugins/ml2/ml2_conf.ini -----------[file:ml2_conf.ini]--[begin]---------- [agent] extensions = [ml2] extension_drivers = port_security mechanism_drivers = openvswitch,sriovnicswitch,l2population path_mtu = 0 physical_network_mtus = physnet0:1500,physnet1:1500 tenant_network_types = vlan,vxlan type_drivers = flat,vlan,vxlan [ml2_type_flat] flat_networks = [ml2_type_vxlan] vni_ranges = vxlan_group = [ovs_driver] vhost_user_enabled = true [securitygroup] firewall_driver = openvswitch -----------[file:ml2_conf.ini]--[end]---------- (2) the networking topology refer below pic or the attached file. 4.infer: we need to create a bridge to connect with the external subnet with the external networking. 5.requirement: We want to ask how to configure to connect external networking in cirros-vm1 or centos instance? we expect result as below: from 172.16.100.188(cirros-vm1) ping 8.8.8.8 is OK. Best Regards Wish you happy everyday! -------------------------------- Yong.Fu- Neusoft --------------------------------------------------------------------------------------------------- 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 17924 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: networking_topology_1025.png Type: image/png Size: 51547 bytes Desc: not available URL: From Tao.Liu at windriver.com Fri Oct 25 13:01:50 2019 From: Tao.Liu at windriver.com (Liu, Tao) Date: Fri, 25 Oct 2019 13:01:50 +0000 Subject: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Message-ID: <7242A3DC72E453498E3D783BBB134C3EA4EB1E0F@ALA-MBD.corp.ad.wrs.com> Hi Austin, The subcloud bootstrapping interface can be any interface that has connectivity to the system controller. The script we provided will configure the IP and route on the selected interface. We recommended using the mgmt. interface previously because it would not require configuring OAM prior to bootstrapping, however, the mgmt. subnet would have to be a different subnet than the one that will be configured on the mgmt. interface after bootstrapping. This means an 'additional temporary' IP address/subnet on mgmt. interface is required for bootstrapping. The decision to use the OAM interface and IP removes the requirement to allocate an 'additional temporary' IP address/subnet, and it is consistent with a NON-DC scenario. See inline comments for your questions. Tao -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Thursday, October 24, 2019 9:39 PM To: Liu, Tao; Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi Tao: Thanks your update . which gerrit or patch enhances using OAM interface and IP to bootstrap the subcloud ? has this patch already been merged ? TL> My document update changes network requirements and no code change is required. Another question , will OAM ip in subcloud L3 connection to OAM ip in central cloud ? does it request mgmt ip in subcloud L2 connect to OAM ip in central cloud for V2? TL> Yes, OAM IP Subnets need to be routable between Central Cloud and Subclouds. No, mgmt. ip in subcloud should not be connected to OAM ip in central cloud. Thanks. BR Austin Sun. -----Original Message----- From: Liu, Tao Sent: Friday, October 25, 2019 2:27 AM To: Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Thanks Arce! A decision has been made to use OAM Interface and IP to bootstrap the subcloud. I have updated the document accordingly. The main change is to run the config_management script and enable OAM interface. Tao -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Monday, October 21, 2019 1:25 PM To: Liu, Tao; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 > Please add Distributed Cloud Configuration Guide to StarlingX R3.0 > Installation. Hi Tao, Distributed Cloud team, Here you have an early review of Distributed Cloud: https://review.opendev.org/#/c/689847/ We will take it as our base documentation and do the installation in our labs starting today, some changes likely coming. For now, please let us know if we need to add more people as Co-Authored-By. From bruce.e.jones at intel.com Fri Oct 25 17:20:58 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 25 Oct 2019 17:20:58 +0000 Subject: [Starlingx-discuss] Release notes for R2.0.1 now available Message-ID: <9A85D2917C58154C960D95352B22818BDFBFDC65@fmsmsx123.amr.corp.intel.com> The release notes for R2.0.1 (a bugfix release for R2.0) are now available. https://docs.starlingx.io/releasenotes/r2_0_1_release.html brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Fri Oct 25 22:09:23 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Fri, 25 Oct 2019 17:09:23 -0500 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$6qe16p@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191025T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From austin.sun at intel.com Sat Oct 26 01:20:40 2019 From: austin.sun at intel.com (Sun, Austin) Date: Sat, 26 Oct 2019 01:20:40 +0000 Subject: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 In-Reply-To: <7242A3DC72E453498E3D783BBB134C3EA4EB1E0F@ALA-MBD.corp.ad.wrs.com> References: <7242A3DC72E453498E3D783BBB134C3EA4EB1E0F@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi, Tao: Thanks a lot. So , there are two phase : In Phase 1( bootstrap subcloud) , sub-cloud OAM is need to routed to central OAM. In Phase 2(provision/manger subcloud) mgmt. subcloud is need to routed to central cloud mgmt. network. Thanks. BR Austin Sun. -----Original Message----- From: Liu, Tao Sent: Friday, October 25, 2019 9:02 PM To: Sun, Austin ; Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi Austin, The subcloud bootstrapping interface can be any interface that has connectivity to the system controller. The script we provided will configure the IP and route on the selected interface. We recommended using the mgmt. interface previously because it would not require configuring OAM prior to bootstrapping, however, the mgmt. subnet would have to be a different subnet than the one that will be configured on the mgmt. interface after bootstrapping. This means an 'additional temporary' IP address/subnet on mgmt. interface is required for bootstrapping. The decision to use the OAM interface and IP removes the requirement to allocate an 'additional temporary' IP address/subnet, and it is consistent with a NON-DC scenario. See inline comments for your questions. Tao -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Thursday, October 24, 2019 9:39 PM To: Liu, Tao; Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi Tao: Thanks your update . which gerrit or patch enhances using OAM interface and IP to bootstrap the subcloud ? has this patch already been merged ? TL> My document update changes network requirements and no code change is required. Another question , will OAM ip in subcloud L3 connection to OAM ip in central cloud ? does it request mgmt ip in subcloud L2 connect to OAM ip in central cloud for V2? TL> Yes, OAM IP Subnets need to be routable between Central Cloud and Subclouds. No, mgmt. ip in subcloud should not be connected to OAM ip in central cloud. Thanks. BR Austin Sun. -----Original Message----- From: Liu, Tao Sent: Friday, October 25, 2019 2:27 AM To: Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Thanks Arce! A decision has been made to use OAM Interface and IP to bootstrap the subcloud. I have updated the document accordingly. The main change is to run the config_management script and enable OAM interface. Tao -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Monday, October 21, 2019 1:25 PM To: Liu, Tao; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 > Please add Distributed Cloud Configuration Guide to StarlingX R3.0 > Installation. Hi Tao, Distributed Cloud team, Here you have an early review of Distributed Cloud: https://review.opendev.org/#/c/689847/ We will take it as our base documentation and do the installation in our labs starting today, some changes likely coming. For now, please let us know if we need to add more people as Co-Authored-By. From maria.g.perez.ibarra at intel.com Sat Oct 26 03:09:20 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Sat, 26 Oct 2019 03:09:20 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191025 Message-ID: Due to the changes in the management network, we do not have the baremetal results. Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-25 (link) Status: GREEN =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Sat Oct 26 08:01:38 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Sat, 26 Oct 2019 08:01:38 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C76608D970F@SHSMSX105.ccr.corp.intel.com> Hi Frank & Brent, " - Have we tested with external registry and where username/pwd is required? Answer: Not yet. Action: Request is for Shuicheng to test (maybe work with Yong) " For external registry with authentication, the status is below: 1. Pull image by crictl is supported. Cmd like: crictl pull --creds USERNAME:PASSWORD image_url 2. Pull image by Kubernetes is supported. It is following standard Kubernetes operation. A Secret need be created to store the username/password, and pod yaml file will use it. https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/ Since localhost.yml file for ansible playbook doesn't support authentication info, it means StarlingX cannot be deployed by registry with authentication. Registry with authentication should be used for 3rd application only. Is it right? Please share me your test cases for registry with authentication if you still have concern on it. Thanks. Best Regards Shuicheng From: Miller, Frank Sent: Wednesday, October 23, 2019 8:11 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting Thanks to all who participated in today's meeting. Good progress across the stx.3.0 features. Minutes for Oct 22: 1. Updates on stx.3.0 container features for MS3 milestone: 2004008: [Feature] Create HELM chart for Fault project [Ran An] - one horizon related commit needs a new approach which cannot be done in stx.3.0 timeframe Decision for stx.3.0 is to keep FM container code but disable it so that FM runs natively for stx.3.0 - then address horizon issue in stx.4.0 and re-enable FM containers. Ran has proposed doing this by bringing back the "fault_management_pod_disabled" flag that was introduced in stx.2.0 and removed in stx.3.0 Ran's forecast for completing this and posting gerrit review is end of week, ie Oct 25 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] - Ran confirmed this feature is now merged Below 2 patches are for k8s device plugin enabling mechanism in ansible and sysinv, add intel gpu device plugin as well --- merged - https://review.opendev.org/#/c/666511/ - https://review.opendev.org/#/c/666510/ This patch is for align all device plugins in one method. Will be revisit when default device plugins require to be align. --- abandoned - https://review.opendev.org/#/c/685592/ 2005514: QAT K8S device plugin support in StarlingX Mingyuan: status of 3 patches which depended on Ran's 666510/666511 - https://review.opendev.org/684890 --> merged - https://review.opendev.org/688344 --> Cores have +2'd -- just need WFL +1 - https://review.opendev.org/688363 --> Cores have +2'd -- just need WFL +1 2005860: Upversion container components [Al Bailey] --> merged 2004761: Integrate Backup & Restore with Containers (for platform) [Ovidiu Poncea] --> merged 2. Complete review of KATA containers feature with container Cores. - Shuicheng's update: Here is the latest test status for kata integration in StarlingX. (1) Pass Sanity test for AIO-SX/AIO-DX/Multi/Multi+Storage. (2) Tested private registry (insecure registry) enabled/disabled. (3) Tested docker proxy enabled/disabled. (4) Tested swact/lock & unlock/remove & apply application. (5) Tested local registry (registry.local:9001) with image pull/push, and access both from kubernetes and crictl (CLI). For regression test, I checked container related test cases in below doc, and executed most of them. No issue is found yet. https://docs.google.com/spreadsheets/d/1dwcBwY4Yq1Lo9Der4RylzQ6KYp0BsMHohhEmhwpauDo/edit?usp=sharing Currently, I meet a deploy issue with IPv6 environment, and the issue could be reproduced with master daily build also. I am checking whether it is caused by my environment or a real issue of master now. Here is the patch list waiting review: https://review.opendev.org/#/q/topic:kata+(status:open) Some questions/comments from TL/Brent: - Have we tested with external registry and where username/pwd is required? Answer: Not yet. Action: Request is for Shuicheng to test (maybe work with Yong) - What is the plan to remove dockerd? - Plan is to remove in a separate commit after the main code merges. Shuicheng plan is to wait till stx.4.0 to remove - is this acceptable? - Shuicheng plan is to have the dockerd removal commit ready by end of November. Plan then to merge this into stx.4.0 once it is open. - We agreed this would be acceptable. - Looks like there is one upstream patch we are carrying (in containerd and runc?). What is the plan to upstream these patches? - Action: Ensure there is a task to upversion docker distribution registry to remove the need to carry this patch. - This too will be done early in stx.4.0. Shuicheng to update us in 1 week on when this task can be completed. Decision to allow into stx.3.0? Three requirements: - Shuicheng to complete testing for IPv6 and external registry with username/pwd authentication - Cores to complete their reviews - Frank to confirm with Ada that testing of this feature can be done in time for stx.3.0 - Backup plan: If instability is seen in stx.3.0 or significant testing by Ada results in failures then the feature would need to be backed up and fixed/delivered in stx.4.0 Frank Miller, Manager, Engineering, Wind River direct 613.963.1389 zoom frank.miller at windriver.com 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Sat Oct 26 08:03:34 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Sat, 26 Oct 2019 03:03:34 -0500 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: List of docker images required for "platform-integ-apps": BUILD_ID="20191026T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From austin.sun at intel.com Sat Oct 26 12:32:38 2019 From: austin.sun at intel.com (Sun, Austin) Date: Sat, 26 Oct 2019 12:32:38 +0000 Subject: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 In-Reply-To: References: <7242A3DC72E453498E3D783BBB134C3EA4EB1E0F@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Tao: With the V2 guide you shared , I deployed dist-cloud on virtual environment successfully. There is one different between the guide and setup I deployed In guide, "After run "dcmanager subcloud add --bootstrap-ip --bootstrap-values " , Confirm that the subcloud was deployed successfully" But The result of 'dcmanager subcloud list' on my setup is offline , not online, it became online only after adding route from subcloud to controller mgmt. network. Is it normal behavior ? Another question is what the capability about system controller beside monitoring subcloud alarm . The image is using 20191017T013000Z Thanks. BR Austin Sun. -----Original Message----- From: Sun, Austin Sent: Saturday, October 26, 2019 9:21 AM To: Liu, Tao ; Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi, Tao: Thanks a lot. So , there are two phase : In Phase 1( bootstrap subcloud) , sub-cloud OAM is need to routed to central OAM. In Phase 2(provision/manger subcloud) mgmt. subcloud is need to routed to central cloud mgmt. network. Thanks. BR Austin Sun. -----Original Message----- From: Liu, Tao Sent: Friday, October 25, 2019 9:02 PM To: Sun, Austin ; Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi Austin, The subcloud bootstrapping interface can be any interface that has connectivity to the system controller. The script we provided will configure the IP and route on the selected interface. We recommended using the mgmt. interface previously because it would not require configuring OAM prior to bootstrapping, however, the mgmt. subnet would have to be a different subnet than the one that will be configured on the mgmt. interface after bootstrapping. This means an 'additional temporary' IP address/subnet on mgmt. interface is required for bootstrapping. The decision to use the OAM interface and IP removes the requirement to allocate an 'additional temporary' IP address/subnet, and it is consistent with a NON-DC scenario. See inline comments for your questions. Tao -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Thursday, October 24, 2019 9:39 PM To: Liu, Tao; Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi Tao: Thanks your update . which gerrit or patch enhances using OAM interface and IP to bootstrap the subcloud ? has this patch already been merged ? TL> My document update changes network requirements and no code change is required. Another question , will OAM ip in subcloud L3 connection to OAM ip in central cloud ? does it request mgmt ip in subcloud L2 connect to OAM ip in central cloud for V2? TL> Yes, OAM IP Subnets need to be routable between Central Cloud and Subclouds. No, mgmt. ip in subcloud should not be connected to OAM ip in central cloud. Thanks. BR Austin Sun. -----Original Message----- From: Liu, Tao Sent: Friday, October 25, 2019 2:27 AM To: Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Thanks Arce! A decision has been made to use OAM Interface and IP to bootstrap the subcloud. I have updated the document accordingly. The main change is to run the config_management script and enable OAM interface. Tao -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Monday, October 21, 2019 1:25 PM To: Liu, Tao; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 > Please add Distributed Cloud Configuration Guide to StarlingX R3.0 > Installation. Hi Tao, Distributed Cloud team, Here you have an early review of Distributed Cloud: https://review.opendev.org/#/c/689847/ We will take it as our base documentation and do the installation in our labs starting today, some changes likely coming. For now, please let us know if we need to add more people as Co-Authored-By. From ildiko at openstack.org Sat Oct 26 22:43:58 2019 From: ildiko at openstack.org (Ildiko Vancsa) Date: Sat, 26 Oct 2019 15:43:58 -0700 Subject: [Starlingx-discuss] "Meet the project leaders" opportunities in Shanghai at the Open Infrastructure Summit Message-ID: <3FCF95ED-C2DE-4E7C-8F93-2A911817F423@openstack.org> Hi everyone, The summit is going to mainland China for the first time. It's a great opportunity to meet the Chinese community, make ourselves available for direct discussion, and on-board new team members. In order to facilitate that, the OpenStack TC has been suggesting that the Foundation organizes two opportunities to "meet the project leaders” during the Summit in Shanghai: one around the Monday evening marketplace mixer, and one around the Wednesday lunch: https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24417/ https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24426/meet-the-project-leaders We will have members from all OSF-supported projects around and I encourage StarlingX community leaders and members who attend the Summit to mark these slots in your calendars to use the opportunity to meet the local community as well as mingle with the leaders of other projects. See you there! Thanks, Ildikó From ildiko.vancsa at gmail.com Sun Oct 27 21:22:31 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Sun, 27 Oct 2019 14:22:31 -0700 Subject: [Starlingx-discuss] Election updates and Flock Services PL election results Message-ID: <706FF344-AA97-4372-A017-021981E0BEB9@gmail.com> Hi, The 2019 H2 StarlingX elections are now over. We were running a poll to elect the new Flock Services PL for the next one year term. We had 68 eligible voters and received 46 votes. Congratulations to the new Flock Services PL Dariush Eslimi. You can find all the candidates for the 2019 H2 StarlingX elections here: https://opendev.org/starlingx/election/src/branch/master/candidates/2019_H2 The following patches are updating the projects.yaml and TSC member files with the results where we have changes: https://review.opendev.org/#/c/691531/ https://review.opendev.org/#/c/691532/ We have 5 new PLs and also 5 new TLs and are still looking for to fill 1 PL and 2 TL roles that the TSC can do by appointing new leaders in the absence of eligible candidates. Thank you for all the candidates for running in the elections. If you have any questions please reply to this thread or reach out to the election officials[1]. Thanks and Best Regards, [1] https://docs.starlingx.io/election/#election-officials From ezpeerchen at gmail.com Mon Oct 28 07:10:10 2019 From: ezpeerchen at gmail.com (Ezpeer Chen) Date: Mon, 28 Oct 2019 15:10:10 +0800 Subject: [Starlingx-discuss] Will StarlingX integrated with Openness? Message-ID: Dear all, Will StarlingX integrated with Openness? Any plan about this ? Thanks a lot. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Mon Oct 28 07:20:36 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 28 Oct 2019 07:20:36 +0000 Subject: [Starlingx-discuss] Will StarlingX integrated with Openness? In-Reply-To: References: Message-ID: <2FD5DDB5A04D264C80D42CA35194914F360A60C1@SHSMSX104.ccr.corp.intel.com> Ezpeer, We are currently evaluating OpenNESS and see if it makes sense to integrate w/ StarlingX, and your request just comes in timely. 😊 I am very interested to know the potential requirements: what is the benefit can bring to you or your customers if we have it integrated? Love to get real biz requirements so that we can have better understanding of the use cases. Thx. - cindy From: Ezpeer Chen Sent: Monday, October 28, 2019 3:10 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Will StarlingX integrated with Openness? Dear all, Will StarlingX integrated with Openness? Any plan about this ? Thanks a lot. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ezpeerchen at gmail.com Mon Oct 28 08:03:56 2019 From: ezpeerchen at gmail.com (Ezpeer Chen) Date: Mon, 28 Oct 2019 16:03:56 +0800 Subject: [Starlingx-discuss] Will StarlingX integrated with Openness? In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F360A60C1@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F360A60C1@SHSMSX104.ccr.corp.intel.com> Message-ID: Dear Cindy, Just for Studying, now. I am studying StarlingX for NFVI platform technique also interest in edge computing technique( I hear about Openness for edge computing solution) . >From ETSI MEC , the MEC host will use virtualization infrastructure, therefore I am thinking if it is possible to use StarlingX + Openness to build up a complete MEC system. Thanks a lot. Xie, Cindy 於 2019年10月28日 週一 下午3:20寫道: > Ezpeer, > > We are currently evaluating OpenNESS and see if it makes sense to > integrate w/ StarlingX, and your request just comes in timely. 😊 > > > > I am very interested to know the potential requirements: what is the > benefit can bring to you or your customers if we have it integrated? Love > to get real biz requirements so that we can have better understanding of > the use cases. > > > > Thx. - cindy > > > > > > *From:* Ezpeer Chen > *Sent:* Monday, October 28, 2019 3:10 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Will StarlingX integrated with Openness? > > > > Dear all, > > > > Will StarlingX integrated with Openness? > > > > Any plan about this ? > > > > Thanks a lot. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Mon Oct 28 08:51:18 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Mon, 28 Oct 2019 02:51:18 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$6qvfec@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191027T230000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From cindy.xie at intel.com Mon Oct 28 09:13:20 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 28 Oct 2019 09:13:20 +0000 Subject: [Starlingx-discuss] Will StarlingX integrated with Openness? In-Reply-To: References: <2FD5DDB5A04D264C80D42CA35194914F360A60C1@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F360A6684@SHSMSX104.ccr.corp.intel.com> Ezpeer, We will sharing our learnings to the community about OpenNESS and how it can be integrated w/ StarlingX – personally I am not expert of NFVI thus good to know that if StarlingX + OpenNESS could be used to build up a complete MEC system. It will be nice that you and maybe other community members who are interested to this use case can contribute to the activities… Thanks. - cindy From: Ezpeer Chen Sent: Monday, October 28, 2019 4:04 PM To: Xie, Cindy Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Will StarlingX integrated with Openness? Dear Cindy, Just for Studying, now. I am studying StarlingX for NFVI platform technique also interest in edge computing technique( I hear about Openness for edge computing solution) . From ETSI MEC , the MEC host will use virtualization infrastructure, therefore I am thinking if it is possible to use StarlingX + Openness to build up a complete MEC system. Thanks a lot. Xie, Cindy > 於 2019年10月28日 週一 下午3:20寫道: Ezpeer, We are currently evaluating OpenNESS and see if it makes sense to integrate w/ StarlingX, and your request just comes in timely. 😊 I am very interested to know the potential requirements: what is the benefit can bring to you or your customers if we have it integrated? Love to get real biz requirements so that we can have better understanding of the use cases. Thx. - cindy From: Ezpeer Chen > Sent: Monday, October 28, 2019 3:10 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Will StarlingX integrated with Openness? Dear all, Will StarlingX integrated with Openness? Any plan about this ? Thanks a lot. -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenjie.xu at intel.com Mon Oct 28 10:57:56 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Mon, 28 Oct 2019 10:57:56 +0000 Subject: [Starlingx-discuss] Requesting review for https://review.opendev.org/#/c/687025/ Message-ID: Hi team, Could you please help review the below patch: https://review.opendev.org/#/c/687025/ The patch haven't get a new review for one week. Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: From qianjiang at baicells.com Mon Oct 28 11:13:32 2019 From: qianjiang at baicells.com (=?UTF-8?B?6ZKx5rGf?=) Date: Mon, 28 Oct 2019 19:13:32 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIOOAkFN0YXJsaW5nWA==?= =?utf-8?q?=E3=80=91Regarding_external_networking_issue?= In-Reply-To: <005401d58b1a$7be6c6f0$73b454d0$@neusoft.com> References: <005401d58b1a$7be6c6f0$73b454d0$@neusoft.com> Message-ID: <3950a7e0-ed9a-498d-848a-08a8f2991bcc.qianjiang@baicells.com> Hi, Fuyong I wish you would allow me to write you even I am not from the StarlingX team :-) From your description of your environment, I guess, . cirros-vm1 (IP: 172.16.100.188) is build over management network (10.10.10.0/24) The cirros-vm1 should have its own router (the gateway should be 172.16.100.1), and this Gateway (172.16.100.1) should be routed through an external network. Then where is your external network? You should check your openstack routers, you may find it from "ip netns list", the router should be implemented using a network namespace, just check them. Hope it help Best Regard ------------------------------------------------------------------ 发件人:付勇 发送时间:2019年10月25日(星期五) 17:58 收件人:starlingx-discuss 抄 送:zhaos ; lilong-neu ; cindy.xie ; shuicheng.lin ; austin.sun ; 张志国 主 题:[Starlingx-discuss] 【StarlingX】Regarding external networking issue Hi StarlingX team we have deploy virtual All-in-one simplex machine and have a question to ask for help. 1. problem: we met a problem with how to connect the external networking in cirros or centos instance. 2. current status controller-0 IP: 10.10.10.3 cirros-vm1 IP: 172.16.100.188, from 172.16.100.188(cirros-vm1) ping external subnet ext_net:10.10.10.190 OK, from 172.16.100.188(cirros-vm1) ping 10.10.10.3 (controller-0) is not OK. from 172.16.100.188(cirros-vm1) ping 8.8.8.8 is not OK. from 10.10.10.3 (controller-0) ping 8.8.8.8 is OK. 3. configuration (1) ml2_conf.ini in container: neutron-ovs-agent-controller-0-937646f6-dtqcn: /etc/neutron/plugins/ml2/ml2_conf.ini -----------[file:ml2_conf.ini]--[begin]---------- [agent] extensions = [ml2] extension_drivers = port_security mechanism_drivers = openvswitch,sriovnicswitch,l2population path_mtu = 0 physical_network_mtus = physnet0:1500,physnet1:1500 tenant_network_types = vlan,vxlan type_drivers = flat,vlan,vxlan [ml2_type_flat] flat_networks = [ml2_type_vxlan] vni_ranges = vxlan_group = [ovs_driver] vhost_user_enabled = true [securitygroup] firewall_driver = openvswitch -----------[file:ml2_conf.ini]--[end]---------- (2) the networking topology refer below pic or the attached file. 4.infer: we need to create a bridge to connect with the external subnet with the external networking. 5.requirement: We want to ask how to configure to connect external networking in cirros-vm1 or centos instance? we expect result as below: from 172.16.100.188(cirros-vm1) ping 8.8.8.8 is OK. Best Regards Wish you happy everyday! -------------------------------- Yong.Fu- Neusoft --------------------------------------------------------------------------------------------------- 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: application/octet-stream Size: 17924 bytes Desc: not available URL: From Barton.Wensley at windriver.com Mon Oct 28 13:18:21 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Mon, 28 Oct 2019 13:18:21 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting In-Reply-To: <9700A18779F35F49AF027300A49E7C76608D970F@SHSMSX105.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C76608D970F@SHSMSX105.ccr.corp.intel.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1B98479@ALA-MBD.corp.ad.wrs.com> Shuicheng, The localhost.yml file does support authentication info - please take a look at: ansible-playbooks/playbookconfig/src/playbooks/host_vars/bootstrap/default.yml You need to test installation of the system for the case where the system images are coming from an external authenticated registry. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: October 26, 2019 4:02 AM To: Miller, Frank; starlingx-discuss at lists.starlingx.io; Rowsell, Brent Subject: Re: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting Hi Frank & Brent, " - Have we tested with external registry and where username/pwd is required? Answer: Not yet. Action: Request is for Shuicheng to test (maybe work with Yong) " For external registry with authentication, the status is below: 1. Pull image by crictl is supported. Cmd like: crictl pull --creds USERNAME:PASSWORD image_url 2. Pull image by Kubernetes is supported. It is following standard Kubernetes operation. A Secret need be created to store the username/password, and pod yaml file will use it. https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/ Since localhost.yml file for ansible playbook doesn't support authentication info, it means StarlingX cannot be deployed by registry with authentication. Registry with authentication should be used for 3rd application only. Is it right? Please share me your test cases for registry with authentication if you still have concern on it. Thanks. Best Regards Shuicheng From: Miller, Frank Sent: Wednesday, October 23, 2019 8:11 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting Thanks to all who participated in today's meeting. Good progress across the stx.3.0 features. Minutes for Oct 22: 1. Updates on stx.3.0 container features for MS3 milestone: 2004008: [Feature] Create HELM chart for Fault project [Ran An] - one horizon related commit needs a new approach which cannot be done in stx.3.0 timeframe Decision for stx.3.0 is to keep FM container code but disable it so that FM runs natively for stx.3.0 - then address horizon issue in stx.4.0 and re-enable FM containers. Ran has proposed doing this by bringing back the "fault_management_pod_disabled" flag that was introduced in stx.2.0 and removed in stx.3.0 Ran's forecast for completing this and posting gerrit review is end of week, ie Oct 25 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] - Ran confirmed this feature is now merged Below 2 patches are for k8s device plugin enabling mechanism in ansible and sysinv, add intel gpu device plugin as well --- merged - https://review.opendev.org/#/c/666511/ - https://review.opendev.org/#/c/666510/ This patch is for align all device plugins in one method. Will be revisit when default device plugins require to be align. --- abandoned - https://review.opendev.org/#/c/685592/ 2005514: QAT K8S device plugin support in StarlingX Mingyuan: status of 3 patches which depended on Ran's 666510/666511 - https://review.opendev.org/684890 --> merged - https://review.opendev.org/688344 --> Cores have +2'd -- just need WFL +1 - https://review.opendev.org/688363 --> Cores have +2'd -- just need WFL +1 2005860: Upversion container components [Al Bailey] --> merged 2004761: Integrate Backup & Restore with Containers (for platform) [Ovidiu Poncea] --> merged 2. Complete review of KATA containers feature with container Cores. - Shuicheng's update: Here is the latest test status for kata integration in StarlingX. (1) Pass Sanity test for AIO-SX/AIO-DX/Multi/Multi+Storage. (2) Tested private registry (insecure registry) enabled/disabled. (3) Tested docker proxy enabled/disabled. (4) Tested swact/lock & unlock/remove & apply application. (5) Tested local registry (registry.local:9001) with image pull/push, and access both from kubernetes and crictl (CLI). For regression test, I checked container related test cases in below doc, and executed most of them. No issue is found yet. https://docs.google.com/spreadsheets/d/1dwcBwY4Yq1Lo9Der4RylzQ6KYp0BsMHohhEmhwpauDo/edit?usp=sharing Currently, I meet a deploy issue with IPv6 environment, and the issue could be reproduced with master daily build also. I am checking whether it is caused by my environment or a real issue of master now. Here is the patch list waiting review: https://review.opendev.org/#/q/topic:kata+(status:open) Some questions/comments from TL/Brent: - Have we tested with external registry and where username/pwd is required? Answer: Not yet. Action: Request is for Shuicheng to test (maybe work with Yong) - What is the plan to remove dockerd? - Plan is to remove in a separate commit after the main code merges. Shuicheng plan is to wait till stx.4.0 to remove - is this acceptable? - Shuicheng plan is to have the dockerd removal commit ready by end of November. Plan then to merge this into stx.4.0 once it is open. - We agreed this would be acceptable. - Looks like there is one upstream patch we are carrying (in containerd and runc?). What is the plan to upstream these patches? - Action: Ensure there is a task to upversion docker distribution registry to remove the need to carry this patch. - This too will be done early in stx.4.0. Shuicheng to update us in 1 week on when this task can be completed. Decision to allow into stx.3.0? Three requirements: - Shuicheng to complete testing for IPv6 and external registry with username/pwd authentication - Cores to complete their reviews - Frank to confirm with Ada that testing of this feature can be done in time for stx.3.0 - Backup plan: If instability is seen in stx.3.0 or significant testing by Ada results in failures then the feature would need to be backed up and fixed/delivered in stx.4.0 Frank Miller, Manager, Engineering, Wind River direct 613.963.1389 zoom frank.miller at windriver.com 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Mon Oct 28 13:22:39 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Mon, 28 Oct 2019 13:22:39 +0000 Subject: [Starlingx-discuss] RFC: Kubernetes Upgrades specification Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1B9848A@ALA-MBD.corp.ad.wrs.com> Hey everyone - I have uploaded the following stx.4.0 specification for review: https://review.opendev.org/#/c/691664/ This story will provide a mechanism to upgrade the kubernetes components on a running StarlingX system. This is required to allow bug fixes to be delivered for kubernetes components and to allow upgrades between kubernetes minor versions. Looking forward to receiving your feedback, Bart -------------- next part -------------- An HTML attachment was scrubbed... URL: From vm.rod25 at gmail.com Mon Oct 28 14:12:31 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Mon, 28 Oct 2019 08:12:31 -0600 Subject: [Starlingx-discuss] RFC: Kubernetes Upgrades specification In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1B9848A@ALA-MBD.corp.ad.wrs.com> References: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1B9848A@ALA-MBD.corp.ad.wrs.com> Message-ID: On Mon, Oct 28, 2019 at 7:23 AM Wensley, Barton wrote: > > Hey everyone - I have uploaded the following stx.4.0 specification for review: > > https://review.opendev.org/#/c/691664/ > > > > This story will provide a mechanism to upgrade the kubernetes components on a running StarlingX system. This is required to allow bug fixes to be delivered for kubernetes components and to allow upgrades between kubernetes minor versions. > Thanks a lot for this, it will enable the fast security fixes between kubernetes minor versions. Really appreciate it > > > Looking forward to receiving your feedback, > > > > Bart > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Angie.Wang at windriver.com Mon Oct 28 14:30:53 2019 From: Angie.Wang at windriver.com (Wang, Jing (Angie)) Date: Mon, 28 Oct 2019 14:30:53 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting In-Reply-To: <9700A18779F35F49AF027300A49E7C76608D970F@SHSMSX105.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C76608D970F@SHSMSX105.ccr.corp.intel.com> Message-ID: Hi Shuicheng, Ansible bootstrap supports to deploy with authenticated registry. To deploy with authenticated registry, you will need to specify username and password in localhost.yml, Ie... docker_registries: defaults: url: registry.com username: registryUser password: registryPass You can also take a look playbooks/host_vars/bootstrap/default.yml for details. To test authenticated registry: - Bootstrap system with authenticated registry, verify system images are pulled from private authenticated registry and pushed to local registry. - After bootstrap is done, verify "auth-secret" is stored for each public registry in service-paramater. - Verify platform-integ-apps applied and images are pulled from private authenticated registry and pushed to local registry. - Deploy stx-monitor/stx-openstack app, verify images are pulled from private authenticated registry and pushed to local registry. Thanks, Angie From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: October-26-19 4:02 AM To: Miller, Frank; starlingx-discuss at lists.starlingx.io; Rowsell, Brent Subject: Re: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting Hi Frank & Brent, " - Have we tested with external registry and where username/pwd is required? Answer: Not yet. Action: Request is for Shuicheng to test (maybe work with Yong) " For external registry with authentication, the status is below: 1. Pull image by crictl is supported. Cmd like: crictl pull --creds USERNAME:PASSWORD image_url 2. Pull image by Kubernetes is supported. It is following standard Kubernetes operation. A Secret need be created to store the username/password, and pod yaml file will use it. https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/ Since localhost.yml file for ansible playbook doesn't support authentication info, it means StarlingX cannot be deployed by registry with authentication. Registry with authentication should be used for 3rd application only. Is it right? Please share me your test cases for registry with authentication if you still have concern on it. Thanks. Best Regards Shuicheng From: Miller, Frank Sent: Wednesday, October 23, 2019 8:11 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting Thanks to all who participated in today's meeting. Good progress across the stx.3.0 features. Minutes for Oct 22: 1. Updates on stx.3.0 container features for MS3 milestone: 2004008: [Feature] Create HELM chart for Fault project [Ran An] - one horizon related commit needs a new approach which cannot be done in stx.3.0 timeframe Decision for stx.3.0 is to keep FM container code but disable it so that FM runs natively for stx.3.0 - then address horizon issue in stx.4.0 and re-enable FM containers. Ran has proposed doing this by bringing back the "fault_management_pod_disabled" flag that was introduced in stx.2.0 and removed in stx.3.0 Ran's forecast for completing this and posting gerrit review is end of week, ie Oct 25 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] - Ran confirmed this feature is now merged Below 2 patches are for k8s device plugin enabling mechanism in ansible and sysinv, add intel gpu device plugin as well --- merged - https://review.opendev.org/#/c/666511/ - https://review.opendev.org/#/c/666510/ This patch is for align all device plugins in one method. Will be revisit when default device plugins require to be align. --- abandoned - https://review.opendev.org/#/c/685592/ 2005514: QAT K8S device plugin support in StarlingX Mingyuan: status of 3 patches which depended on Ran's 666510/666511 - https://review.opendev.org/684890 --> merged - https://review.opendev.org/688344 --> Cores have +2'd -- just need WFL +1 - https://review.opendev.org/688363 --> Cores have +2'd -- just need WFL +1 2005860: Upversion container components [Al Bailey] --> merged 2004761: Integrate Backup & Restore with Containers (for platform) [Ovidiu Poncea] --> merged 2. Complete review of KATA containers feature with container Cores. - Shuicheng's update: Here is the latest test status for kata integration in StarlingX. (1) Pass Sanity test for AIO-SX/AIO-DX/Multi/Multi+Storage. (2) Tested private registry (insecure registry) enabled/disabled. (3) Tested docker proxy enabled/disabled. (4) Tested swact/lock & unlock/remove & apply application. (5) Tested local registry (registry.local:9001) with image pull/push, and access both from kubernetes and crictl (CLI). For regression test, I checked container related test cases in below doc, and executed most of them. No issue is found yet. https://docs.google.com/spreadsheets/d/1dwcBwY4Yq1Lo9Der4RylzQ6KYp0BsMHohhEmhwpauDo/edit?usp=sharing Currently, I meet a deploy issue with IPv6 environment, and the issue could be reproduced with master daily build also. I am checking whether it is caused by my environment or a real issue of master now. Here is the patch list waiting review: https://review.opendev.org/#/q/topic:kata+(status:open) Some questions/comments from TL/Brent: - Have we tested with external registry and where username/pwd is required? Answer: Not yet. Action: Request is for Shuicheng to test (maybe work with Yong) - What is the plan to remove dockerd? - Plan is to remove in a separate commit after the main code merges. Shuicheng plan is to wait till stx.4.0 to remove - is this acceptable? - Shuicheng plan is to have the dockerd removal commit ready by end of November. Plan then to merge this into stx.4.0 once it is open. - We agreed this would be acceptable. - Looks like there is one upstream patch we are carrying (in containerd and runc?). What is the plan to upstream these patches? - Action: Ensure there is a task to upversion docker distribution registry to remove the need to carry this patch. - This too will be done early in stx.4.0. Shuicheng to update us in 1 week on when this task can be completed. Decision to allow into stx.3.0? Three requirements: - Shuicheng to complete testing for IPv6 and external registry with username/pwd authentication - Cores to complete their reviews - Frank to confirm with Ada that testing of this feature can be done in time for stx.3.0 - Backup plan: If instability is seen in stx.3.0 or significant testing by Ada results in failures then the feature would need to be backed up and fixed/delivered in stx.4.0 Frank Miller, Manager, Engineering, Wind River direct 613.963.1389 zoom frank.miller at windriver.com 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 -------------- next part -------------- An HTML attachment was scrubbed... URL: From thierry at openstack.org Mon Oct 28 15:08:58 2019 From: thierry at openstack.org (Thierry Carrez) Date: Mon, 28 Oct 2019 16:08:58 +0100 Subject: [Starlingx-discuss] [ptg] ptgbot HOWTO Message-ID: <8c97aa34-17bc-4dc3-942c-2fbc73595717@openstack.org> Hi everyone, In a few days, some contributor teams will meet in Shanghai for our 6th Project Teams Gathering. The event is organized around separate 'tracks' (generally tied to a specific team/group). Topics of discussion are loosely scheduled in those tracks, based on the needs of the attendance. This allows to maximize attendee productivity, but the downside is that it can make the event a bit confusing to navigate. To mitigate that issue, we are using an IRC bot to expose what's happening currently at the event at the following page: http://ptg.openstack.org/ptg.html It is therefore useful to have a volunteer in each room who makes use of the PTG bot to communicate what's happening. This is done by joining the #openstack-ptg IRC channel on Freenode and voicing commands to the bot. Usage of the bot is of course optional, but in past editions it was really useful to help attendees successfully navigate this dynamic event. How to keep attendees informed of what's being discussed in your room --------------------------------------------------------------------- To indicate what's currently being discussed, you will use the track name hashtag (found in the "Scheduled tracks" section on the above page), with the 'now' command: #TRACK now Example: #swift now brainstorming improvements to the ring You can also mention other track names to make sure to get people attention when the topic is transverse: #ops-meetup now discussing #cinder pain points There can only be one 'now' entry for a given track at a time. To indicate what will be discussed next, you can enter one or more 'next' commands: #TRACK next Example: #api-sig next at 2pm we'll be discussing pagination woes Note that in order to keep content current, entering a new 'now' command for a track will automatically erase any 'next' entry for that track. Finally, if you want to clear all 'now' and 'next' entries for your track, you can issue the 'clean' command: #TRACK clean Example: #ironic clean How to make your track etherpad easily found -------------------------------------------- We traditionally use an etherpad for each track, to plan and document the topics being discussed. In the past we used a wiki to list those etherpads, but now we publish a list of them at: http://ptg.openstack.org/etherpads.html PTGbot generates a default URL for your etherpad. If you already have one, you can update the URL by issuing the following command: #TRACK etherpad How to book reservable rooms ---------------------------- In Shanghai we will have some additional reservable space for extra un-scheduled discussions. The PTG bot page shows which track is allocated to which room, as well as available reservable space, with a slot code (room name - time slot) that you can use to issue a 'book' command to the PTG bot: #TRACK book Example: #release-management book Ocata-WedA1 Any track can book additional space and time using this system. If your topic of discussion does not fall into an existing track, it is easy to add a track on the fly. Just ask PTG bot admins (ttx, diablo_rojo...) on the channel to create a track for you (which they can do by getting op rights and issuing a ~add command). For more information on the bot commands, please see: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst Let me know if you have any additional questions. -- Thierry Carrez (ttx) From bruce.e.jones at intel.com Mon Oct 28 18:03:32 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 28 Oct 2019 18:03:32 +0000 Subject: [Starlingx-discuss] Agenda for the Oct 29th Openstack-Distro meeting Message-ID: <9A85D2917C58154C960D95352B22818BDFBFF143@fmsmsx123.amr.corp.intel.com> 10/29/2019 meeting * Welcome to our new PL! * Train upgrade * EB testing in progress (JC) ? Sanity on Standard with External Storage failed - logs available at http://10.219.115.222/ISOS/ALL_NODES_20191025.153624.tar * More patches to be reviewed: ? https://review.opendev.org/687200 (project: stx-manifest) upgrade StarlingX dashboard with stable/train. Not needed! ? https://review.opendev.org/687203 (project: stx-gui) update stx local_settings for horizon train upgrade. MERGED ? https://review.opendev.org/687204 (project: stx-upstream) update upstream project for horizon train upgrade. Not needed! * Governance update in progress, thank you Ya! * https://review.opendev.org/690615 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Mon Oct 28 19:40:03 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 28 Oct 2019 19:40:03 +0000 Subject: [Starlingx-discuss] Looking for collaborators / reviewers - Dev process document Message-ID: <9A85D2917C58154C960D95352B22818BDFBFF1C8@fmsmsx123.amr.corp.intel.com> I am starting work on a development process document and am looking for anyone who would like to contribute to the effort and/or review the draft document. I've posted a very early draft for review [1] and will be working on it this week, keeping the latest version out in the review. Help graciously welcomed! Brucej [1] https://review.opendev.org/#/c/691740/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Mon Oct 28 22:35:43 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Mon, 28 Oct 2019 22:35:43 +0000 Subject: [Starlingx-discuss] [ Test ] meeting agenda for 10/29 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CEFFBBC@FMSMSX114.amr.corp.intel.com> Agenda for 10/29 1. Sanity status Unified sanity 2. stx.3.0 testing updates Feature testing Distributed cloud - Yang % of progress - checking on the failure, not knowing if it's a procedure or a real issue. - status? Backup and restore - Yang % progress Fault Containerization - Fer https://bugs.launchpad.net/starlingx/+bug/1848094 - Fix released Add a test for checking the FM container end point has switch to https. - done Should be re-tested once the ISO with train is released Upversion to train - JC Redfish - Cristopher New tests cases to be created for provisioning (bulk installs). - status? Let's work on setup an IPv6 lab for running test on this infra. - JC to send a reminder for getting the info/steps requested. - status? Infra & Cluster monitoring - Yang Tests defined are done. Will review for making sure on the coverage. - status? Regression testing: Tracker - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit?usp=sharing Please make sure to use the tag stx.regression for all the launchpads created coming out from these tests. Automated robot - Automated pytest - Manual - % of progress. https://bugs.launchpad.net/starlingx/+bug/1849221 - SSH / SCP to VM failed using NAMESPACE while IP is assigned by Horizon 3. Opens Ada on vacations starting Nov 15 -- Regards Ada From maria.g.perez.ibarra at intel.com Mon Oct 28 23:12:09 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Mon, 28 Oct 2019 23:12:09 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191028 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-28 (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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006677.html Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Tue Oct 29 07:17:58 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 29 Oct 2019 07:17:58 +0000 Subject: [Starlingx-discuss] decouple sysinv-conductor with armada application, request to decouple the way to generate image file with armada chart Message-ID: <56829C2A36C2E542B0CCB9854828E4D85627B0C2@CDSMSX102.ccr.corp.intel.com> Hi Angie & Tee Currently decoupling sysinv-conductor with armada application, you introduce new class ArmadaManifestOperator. But I find currently this class only decouple application override. For image list, it still depends on declaration in values.yaml in application's charts. We work to ceph containerization, plan to introduce new charts to launch ceph service. https://review.opendev.org/#/c/681457/ The image declaration in values.yaml is not same as currently application This chart will pull images rook/ceph:v1.1.1, with such way to declare image. https://review.opendev.org/#/c/681457/5/stx-platform-helm/stx-platform-helm/helm-charts/rook-ceph/values.yaml image: prefix: rook repository: rook/ceph tag: v1.1.1 pullPolicy: IfNotPresent So prefer in sysinv-conductor, also use ArmadaManifestOperator to update image list file. Thanks! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ypd01018 at naver.com Tue Oct 29 13:06:22 2019 From: ypd01018 at naver.com (=?utf-8?B?6rCV64+Z7ZuI?=) Date: Tue, 29 Oct 2019 22:06:22 +0900 Subject: [Starlingx-discuss] =?utf-8?q?I_have_a_question_to_ask_you_about_?= =?utf-8?q?instance_console_access_in_Horizon=2E?= Message-ID: <7a369632de3dd30e129627adb6d7ea3@cweb005.nm.nfra.io> Hi StarlingX Team Instances are being created from the Starlingx dashboard rather than from the open-stack dashboard in the Starlingx learn video. Can I do this on AIO-SX? Please let me know what to do if you can. And i can't access the instance from OpenStack Horizons. Can you tell me how to do it? -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Oct 29 13:16:04 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 29 Oct 2019 13:16:04 +0000 Subject: [Starlingx-discuss] openstack-distro meeting 10 29th 2019 minutes Message-ID: <9A85D2917C58154C960D95352B22818BDFBFFA7D@fmsmsx123.amr.corp.intel.com> 10/29/2019 meeting * Welcome to our new PL! * Next week's meeting time is 5AM in the US west coast, Bruce unlikely to attend. Move it back one hour? Issue to be discussed at the community call this week. * Yong suggests moving this to bi-weekly, no disagreement. * Train upgrade * EB testing in progress (JC) ? Sanity on Standard with External Storage failed - logs available at http://10.219.115.222/ISOS/ALL_NODES_20191025.153624.tar ? Patch needed? https://review.opendev.org/#/c/661512/ Yes, we believe that this patch should be un-reverted and applied again. ? It seems to be the root cause of the current failure. New EB (308) already generated and testing to begin asap. * More patches to be reviewed: ? https://review.opendev.org/687200 (project: stx-manifest) upgrade StarlingX dashboard with stable/train. Not needed! ? https://review.opendev.org/687203 (project: stx-gui) update stx local_settings for horizon train upgrade. MERGED ? https://review.opendev.org/687204 (project: stx-upstream) update upstream project for horizon train upgrade. Not needed! * Governance update in progress, thank you Ya! * https://review.opendev.org/690615 - please don't merge topics when merging reviews. Back up to the previous patchset please. * Testing is in progress, 16 pass and 23 remain. Testing on all in one duplex bare metal config. Testing to complete EO next week. * Yong to review the openstack related launchpads to help drive release 3.0 bug fixing. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Tue Oct 29 13:22:20 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 29 Oct 2019 13:22:20 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/30 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F360A8185@SHSMSX104.ccr.corp.intel.com> Agenda for 10/30 meeting: - Welcome new PL Austin Sun - Switch the meeting time starting from 11/6 - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade update (Shuai) - CVE LP fixing (Shuicheng) - Opens (all) -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W; Sun, Austin Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, October 30, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . 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 From cindy.xie at intel.com Tue Oct 29 13:26:43 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 29 Oct 2019 13:26:43 +0000 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIOOAkFN0YXJsaW5nWA==?= =?utf-8?q?=E3=80=91Regarding_external_networking_issue?= In-Reply-To: <3950a7e0-ed9a-498d-848a-08a8f2991bcc.qianjiang@baicells.com> References: <005401d58b1a$7be6c6f0$73b454d0$@neusoft.com> <3950a7e0-ed9a-498d-848a-08a8f2991bcc.qianjiang@baicells.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F360A837C@SHSMSX104.ccr.corp.intel.com> Thanks Qian Jiang, @付勇, not sure if this addressed your question or not, please let us know if any additional help needed. Thx. - cindy From: 钱江 Sent: Monday, October 28, 2019 7:14 PM To: 付勇 ; starlingx-discuss Cc: zhaos ; lilong-neu ; Xie, Cindy ; Lin, Shuicheng ; Sun, Austin ; 张志国 Subject: 回复:[Starlingx-discuss] 【StarlingX】Regarding external networking issue Hi, Fuyong I wish you would allow me to write you even I am not from the StarlingX team :-) From your description of your environment, I guess, . cirros-vm1 (IP: 172.16.100.188) is build over management network (10.10.10.0/24) The cirros-vm1 should have its own router (the gateway should be 172.16.100.1), and this Gateway (172.16.100.1) should be routed through an external network. Then where is your external network? You should check your openstack routers, you may find it from "ip netns list", the router should be implemented using a network namespace, just check them. Hope it help Best Regard ------------------------------------------------------------------ 发件人:付勇 > 发送时间:2019年10月25日(星期五) 17:58 收件人:starlingx-discuss > 抄 送:zhaos >; lilong-neu >; cindy.xie >; shuicheng.lin >; austin.sun >; 张志国 > 主 题:[Starlingx-discuss] 【StarlingX】Regarding external networking issue Hi StarlingX team we have deploy virtual All-in-one simplex machine and have a question to ask for help. 1. problem: we met a problem with how to connect the external networking in cirros or centos instance. 2. current status controller-0 IP: 10.10.10.3 cirros-vm1 IP: 172.16.100.188, from 172.16.100.188(cirros-vm1) ping external subnet ext_net:10.10.10.190 OK, from 172.16.100.188(cirros-vm1) ping 10.10.10.3 (controller-0) is not OK. from 172.16.100.188(cirros-vm1) ping 8.8.8.8 is not OK. from 10.10.10.3 (controller-0) ping 8.8.8.8 is OK. 3. configuration (1) ml2_conf.ini in container: neutron-ovs-agent-controller-0-937646f6-dtqcn: /etc/neutron/plugins/ml2/ml2_conf.ini -----------[file:ml2_conf.ini]--[begin]---------- [agent] extensions = [ml2] extension_drivers = port_security mechanism_drivers = openvswitch,sriovnicswitch,l2population path_mtu = 0 physical_network_mtus = physnet0:1500,physnet1:1500 tenant_network_types = vlan,vxlan type_drivers = flat,vlan,vxlan [ml2_type_flat] flat_networks = [ml2_type_vxlan] vni_ranges = vxlan_group = [ovs_driver] vhost_user_enabled = true [securitygroup] firewall_driver = openvswitch -----------[file:ml2_conf.ini]--[end]---------- (2) the networking topology refer below pic or the attached file. [cid:image003.jpg at 01D58E9F.6D3287B0] 4.infer: we need to create a bridge to connect with the external subnet with the external networking. 5.requirement: We want to ask how to configure to connect external networking in cirros-vm1 or centos instance? we expect result as below: from 172.16.100.188(cirros-vm1) ping 8.8.8.8 is OK. Best Regards Wish you happy everyday! -------------------------------- Yong.Fu- Neusoft --------------------------------------------------------------------------------------------------- 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 17924 bytes Desc: image003.jpg URL: From abraham.arce.moreno at intel.com Tue Oct 29 17:24:06 2019 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 29 Oct 2019 17:24:06 +0000 Subject: [Starlingx-discuss] openSUSE: High Availability Update In-Reply-To: References: Message-ID: Dear High Availability and DevStack community: Last week, my main activity was Distributed Cloud, specifically documentation, some internal things and 1.5 days off so please find the minimum progress reached in ~ 2 days and several questions. I have not moved away from the previous approach proposed [0], now added the step 3.2, to install service manager package using the DevStack way: - One issue found - One patch submitted - Several questions [ Summary ] [ Procedure ] 1. Virtual Box machine based on OpenSUSE Leap [1] 2. DevStack, installed through provided installation instructions [2] 3. High Availability 3.1 Installed through OBS personal repository [3] Launchpad https://bugs.launchpad.net/starlingx/+bug/1850450 3.2 Initially built through DevStack 3.2.1 Runtime dependencies Review https://review.opendev.org/#/c/691905 3.2.2 Includes libraries Your help needed, several questions, see section "details" [Details] [ 3.2 Initially built through DevStack ] [[ Runtime dependencies ]] For runtime dependencies, the following errors were presented: sm_types.c:10:10: fatal error: glib.h: No such file or directory sm_uuid.c:9:10: fatal error: uuid/uuid.h: No such file or directory /usr/lib64/gcc/x86_64-suse-linux/.../bin/ld: cannot find -lsqlite3 /usr/lib64/gcc/x86_64-suse-linux/.../bin/ld: cannot find -ljson-c Patch is out for review: openSUSE: System Packages Devstack based [4] based in DevStack plugin guidelines [5]. [[ Includes libraries ]] To get to a successful local build of ha/devstack, 2 issues were Presented and manually fixed: 1. Fatal error No such file or directory: fatal error: mtceHbsCluster.h: No such file or directory fatal error: fmAPI.h: No such file or directory To temporarily fix, the following libraries were manually added: -I$PATH_TO/metal/mtce/src/heartbeat/ -I$PATH_TO/fault/fm-common/sources/ Questions? Is build_sm function under "devstack/lib/ha" the correct place to add the metal and fault includes location? What is the temporal place directory DevStack assign to these dependencies? Is DevStack plugin guidelines [5] the right documentation to solve this issue so we can get deeply into it? To bring those runtime dependencies, is ha/devstack/settings [6] file the only required place to tell DeStack to bring them? 2. Error fmcommon /usr/lib64/gcc/x86_64-suse-linux/.../bin/ld: cannot find -lfmcommon To temporarily fix, the fmcommon library was manually copied: sudo cp /opt/stack/devstack/ha/devstack/fault/fm-common/sources/libfmcommon.so /usr/lib64/fmcommon.so Questions? I assume this is a prerequisite to be correctly handled by DevStack fault installation? After these 2 issues were manually fixed, we had a successful build after calling local devstack script: stack at linux-qwyc:~/devstack/ha/devstack> bash build.sh [ Next Steps ] Full installation of DevStack adding the following StarlingX ha components under local.conf: enable_plugin ha https://opendev.org/starlingx/ha and then run DevStack: stack at linux-qwyc:~/devstack> bash stack.sh Again, please let me know your feedback, comments, new paths to follow, anything. All details (constantly updated) at personal github [7] [8] [0] http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006623.html [1] https://software.opensuse.org/distributions/leap [2] https://docs.openstack.org/devstack/latest/ [3] https://download.opensuse.org/repositories/home:/xe1gyq/Cloud_StarlingX_2.0_openSUSE_Leap_15.1/home:xe1gyq.repo [4] https://review.opendev.org/#/c/691905 [5] https://docs.openstack.org/devstack/latest/plugins.html [6] https://opendev.org/starlingx/ha/src/branch/master/devstack/settings [7] https://github.com/xe1gyq/starlingx/blob/master/multios/opensuse_ha_install_devstack.md [8] https://github.com/xe1gyq/starlingx/blob/master/multios/opensuse_ha_install_devstack_build.md From maria.g.perez.ibarra at intel.com Tue Oct 29 17:26:51 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 29 Oct 2019 17:26:51 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191029 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-29 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] FAIL: [1 TCs] BLOCKED: [56 TCs] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 60 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 61 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 56 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 60 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 61 TCs ] --------------------------------------------------------------------------- Failure unlocking nodes during setup https://bugs.launchpad.net/starlingx/+bug/1850462 Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Tue Oct 29 17:57:23 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 29 Oct 2019 17:57:23 +0000 Subject: [Starlingx-discuss] FW: Sanity Test - ISO 20191029 - RED Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CF00158@FMSMSX114.amr.corp.intel.com> Hey, just to make sure you are aware we have a red sanity today, due to this bug: https://bugs.launchpad.net/starlingx/+bug/1850462 A. From: Perez Ibarra, Maria G Sent: Tuesday, October 29, 2019 11:27 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191029 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-29 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] FAIL: [1 TCs] BLOCKED: [56 TCs] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 60 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 61 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 56 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 60 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 61 TCs ] --------------------------------------------------------------------------- Failure unlocking nodes during setup https://bugs.launchpad.net/starlingx/+bug/1850462 Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From Ghada.Khalil at windriver.com Tue Oct 29 21:19:07 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 29 Oct 2019 21:19:07 +0000 Subject: [Starlingx-discuss] FW: Sanity Test - ISO 20191029 - RED In-Reply-To: <4F6AACE4B0F173488D033B02A8BB5B7E7CF00158@FMSMSX114.amr.corp.intel.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E7CF00158@FMSMSX114.amr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0C15E41D6@ALA-MBD.corp.ad.wrs.com> Hello all, The issue is now understood. It's due to a code change which merged yesterday. Alex is working on a fix. Sorry for the inconvenience. Regards, Ghada From: Cabrales, Ada [mailto:ada.cabrales at intel.com] Sent: Tuesday, October 29, 2019 1:57 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] FW: Sanity Test - ISO 20191029 - RED Hey, just to make sure you are aware we have a red sanity today, due to this bug: https://bugs.launchpad.net/starlingx/+bug/1850462 A. From: Perez Ibarra, Maria G > Sent: Tuesday, October 29, 2019 11:27 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191029 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-29 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] FAIL: [1 TCs] BLOCKED: [56 TCs] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 60 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 61 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 56 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 60 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 61 TCs ] --------------------------------------------------------------------------- Failure unlocking nodes during setup https://bugs.launchpad.net/starlingx/+bug/1850462 Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Tue Oct 29 21:21:50 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 29 Oct 2019 14:21:50 -0700 Subject: [Starlingx-discuss] StarlingX project update on the next OSF board meeting Message-ID: Hi StarlingX Community, Reaching out to you with a heads up that the project has a session to give an update on progress and plans to the OpenStack Foundation Board of Directors at the next face to face meeting this Sunday in Shanghai. With the StarlingX TSC group we are working on the slides for this session. If you’re interested in contributing as well you can check out the slides and add questions or comments to it here: https://docs.google.com/presentation/d/143vckStI_56RHjBG_1huvY_zr3BUlEBL_6415OAM51Y/edit?usp=sharing Please let me know if you have any questions. Thanks, Ildikó From ada.cabrales at intel.com Tue Oct 29 21:38:34 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 29 Oct 2019 21:38:34 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes for 10/29 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CF0033A@FMSMSX114.amr.corp.intel.com> Agenda for 10/29 Attendees: Elio, JC, Jose, JP, Fernando, Cristopher, Maria P, Richo 1. Sanity status Intel - https://bugs.launchpad.net/starlingx/+bug/1850462 - Failure unlocking nodes during setup Simplex and standard and external storage configs, nodes are failing to unlock Maria P to send the report earlier to let everyone know its broken. Wind River Unified sanity - We had some problems and we will push out the start date. Wind River has to modify its infrastructure. In intel side, we have to implement the ping to VMs from an external source. Cristopher will work on the setting the config. Our proposal is to push out the date to November 12. Let's align offline with Yang. - Yang agreed to set this new date. 2. stx.3.0 testing updates Feature testing Tracker - https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit?usp=sharing Distributed cloud - Yang 65% of progress - checking on the failure, not knowing if it's a procedure or a real issue. - status? Backup and restore - Yang 100% progress - Done Fault Containerization - Fer https://bugs.launchpad.net/starlingx/+bug/1848094 - Fix released Add a test for checking the FM container end point has switch to https. - done Should be re-tested once the ISO with train is released. Upversion to train - JC 33% done. The EB provided last week failed the sanity on external storage. We got a new EB and is being tested under sanity. Redfish - Cristopher New tests cases to be created for provisioning (bulk installs). - status? pending, to be worked this week Basic functionality is covered, no issues found. Let's work on setup an IPv6 lab for running test on this infra. - JC to send a reminder for getting the info/steps requested. - Not yet, will be sent this week. Infra & Cluster monitoring - Yang Tests defined are done. Will review for making sure on the coverage. - status? Regression testing: Tracker - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit?usp=sharing Automated robot - A new run will be done with OpenStack Train. Automated pytest - A new run will be done with OpenStack Train. - Ask Yang again if they can do it, too. - Yes, got confirmation from her. Manual - % of progress. Waiting for an ISO with OpenStack train. A set of manual tests cases (around 60) were selected to be re-run once the OpenStack Train is on the ISO. https://bugs.launchpad.net/starlingx/+bug/1849221 - SSH / SCP to VM failed using NAMESPACE while IP is assigned by Horizon The issue is triaged, and we have a workaround. We are at the 4th week of regression testing. Hopefully we can start testing with train on Monday next week. 3. Opens Ada on vacations starting Nov 15 - Elio to run the meetings in the meantime. Conflicting meeting on 11/5. Can we cancel this one? We agreed on provide status offline and cancel next week's meeting. -- Ada From ada.cabrales at intel.com Tue Oct 29 21:41:06 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 29 Oct 2019 21:41:06 +0000 Subject: [Starlingx-discuss] FW: Sanity Test - ISO 20191029 - RED In-Reply-To: <151EE31B9FCCA54397A757BC674650F0C15E41D6@ALA-MBD.corp.ad.wrs.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E7CF00158@FMSMSX114.amr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0C15E41D6@ALA-MBD.corp.ad.wrs.com> Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CF00354@FMSMSX114.amr.corp.intel.com> Thanks for the update, Ghada! A. From: Khalil, Ghada Sent: Tuesday, October 29, 2019 3:19 PM To: Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] FW: Sanity Test - ISO 20191029 - RED Hello all, The issue is now understood. It's due to a code change which merged yesterday. Alex is working on a fix. Sorry for the inconvenience. Regards, Ghada From: Cabrales, Ada [mailto:ada.cabrales at intel.com] Sent: Tuesday, October 29, 2019 1:57 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] FW: Sanity Test - ISO 20191029 - RED Hey, just to make sure you are aware we have a red sanity today, due to this bug: https://bugs.launchpad.net/starlingx/+bug/1850462 A. From: Perez Ibarra, Maria G > Sent: Tuesday, October 29, 2019 11:27 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191029 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-29 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] FAIL: [1 TCs] BLOCKED: [56 TCs] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 60 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 61 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 56 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 60 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 61 TCs ] --------------------------------------------------------------------------- Failure unlocking nodes during setup https://bugs.launchpad.net/starlingx/+bug/1850462 Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From vm.rod25 at gmail.com Tue Oct 29 23:46:27 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Tue, 29 Oct 2019 17:46:27 -0600 Subject: [Starlingx-discuss] [feedback] Ways to measure the memory footprint by STX Message-ID: Hi team One of the areas we care about in the performance subteam is the footprint. Footprint could be very broad, from CPU/Memory//HD and more. The one topic we are focused on right now is the memory footprint. The basic definition of memory footprint is the amount of memory (RAM + SWAP) software uses when running. However, it is not only referred to the amount of process the text (code) section takes on the virtual memory but also the memory for dynamic data. The program may also reserve memory for additional functions that are called in when needed. I would like to start the thread about recommended ways the community might be interested in reading the footprint. Few ideas could be: On master: Centos 7.6 + k8 + OpenStack running (as containers) + SW needed to make it run Agains STX w/ OpenStack up and running + STX flocks On Client: Centos 7.6 + K8 client side Agains STX + STX flocks Get the delta of memory used with $ free -h ( or any other most used command) Another metric might be to measure the memory of the STX flock services running. At this point, there is a nice point to consider. Linux is equipped with virtual memory management and has ways to provide metrics that show how much memory is being used by a process. The Linux tools most commonly used are the VSZ (Virtual Memory Size) and RSS (Resident Set Size). The VSZ describes the entire virtual memory size of the process regardless of whether or not pages are being loaded in physical memory. This metric is not a realistic indicator to measure memory consumption since it includes pages that are not actually consumed. RSS is an indicator that shows the memory consumption when the process is running by itself without sharing anything with other processes. Since all current programs have shared libraries, RSS overestimates the amount of memory consumed by the process. Proportional set size (PSS), provides a better perspective of the memory in use. The proportional set size of a process indicates the pages a process has in memory, but each page is divided by the number of processes sharing it. Imagine a process with 1000 pages all to itself and 1000 pages shared with one other process. The PSS of the process is 1500. PSS gives a more realistic indicator of memory consumption compared to RSS and VSZ. It works especially well when considering the memory consumption of an entire system and not each process individually. The proportional set size is given by the kernel on the /proc//smaps files as: Pss: kB Another point to track might be how much memory do we need due to OpenStack. After the open stack runs, the amount of memory might increase, Does anybody has an idea how much? There is a great PR under development by Erich to use Prometheus https://github.com/starlingx-staging/tools-contrib/pull/9 Prometheus is a great tool for daily track the memory consumed (and other metrics). It will be nice to have it up and running, it will help us a lot, however in my opinion we will need for the base target in order to get the difference we add in terms in memory Any feedback more than welcome Thanks Victor Rodriguez From yong.hu at intel.com Wed Oct 30 00:18:55 2019 From: yong.hu at intel.com (Yong Hu) Date: Wed, 30 Oct 2019 08:18:55 +0800 Subject: [Starlingx-discuss] I have a question to ask you about instance console access in Horizon. In-Reply-To: <7a369632de3dd30e129627adb6d7ea3@cweb005.nm.nfra.io> References: <7a369632de3dd30e129627adb6d7ea3@cweb005.nm.nfra.io> Message-ID: <4b903dcb-8c30-09e4-1d8f-4cbc791560dd@intel.com> Pls see my feedback online. On 2019/10/29 9:06 PM, 강동훈 wrote: > Hi StarlingX Team > > Instances are being created from the Starlingx dashboard rather than > from the open-stack dashboard in the Starlingx learn video. > We have 2 dashboards at this moment: openstack horizon (http://:31000) and stx-gui (http://:8080) > Can I do this on AIO-SX? Please let me know what to do if you can. > Sure you can access OpenStack Horizon as long as you have already applied "stx-openstack" (which is a set of containerized openstack services) > And i can't access the instance from OpenStack Horizons. Can you tell me > how to do it? Once OpenStack services are running up on StarlingX, AND you've created your VMs, you can access the vnc console of VM instance on OpenStack Horizon page. > > > _______________________________________________ > 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 Wed Oct 30 08:40:51 2019 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 30 Oct 2019 08:40:51 +0000 Subject: [Starlingx-discuss] exploration for adding smaller memory node on stx system Message-ID: Hi StarlingX Community: I have spent some time to explore how to add smaller memory node on stx system. The approach I'm trying is containerizing flocking services for worker node. And the status/achievement are * 2G memory nodes (ubuntu 18.04 and centos 7.6) were successfully added to multi-node stx system . this node is unlocked , available and joined stx k8s system. * Sysinv-agent , hbsClient and mtcClient are containerized and deploy this node . * Configuration was manually set and some device audit was bypass. There should be still a long way to fully functional worker node on such smaller memory node, such as auto-config , devices audit and other containerization services etc., The status and plan for net step is shared in [1] I created story [2] to track the change if task is ready [1] https://drive.google.com/file/d/1nt-Mx2Ebrqr4IBruSoOVmB5cjdOQ9HJR/view?usp=sharing [2] https://storyboard.openstack.org/#!/story/2006787 Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Wed Oct 30 09:00:31 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Wed, 30 Oct 2019 03:00:31 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$6rmh8m@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191030T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From vm.rod25 at gmail.com Wed Oct 30 12:00:35 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Wed, 30 Oct 2019 06:00:35 -0600 Subject: [Starlingx-discuss] exploration for adding smaller memory node on stx system In-Reply-To: References: Message-ID: On Wed, Oct 30, 2019 at 2:42 AM Sun, Austin wrote: > > Hi StarlingX Community: > > I have spent some time to explore how to add smaller memory node on stx system. > > The approach I’m trying is containerizing flocking services for worker node. > Thanks, Austin, having the capability to add small footprint nodes will open the possibilities for users of StarlingX The approach is to containerizing flocking services for worker node seems the most straight forward solution. I was wondering if the scope will be just to make the node visible for k8 or also for open stack. I could think that for now just k8. One more question (based on the previous mail I sent about memory ) is there any host OS package is going to be needed? if so we can work in collaboration with the multi os team to handle it. I was wondering if the kernel or systemd might be needed on the worker + the flock services. One more thing, how do you measure the MB of virtual memory used by the services? > And the status/achievement are > > 2G memory nodes (ubuntu 18.04 and centos 7.6) were successfully added to multi-node stx system . > Great !! > this node is unlocked , available and joined stx k8s system. > > Sysinv-agent , hbsClient and mtcClient are containerized and deploy this node . > Configuration was manually set and some device audit was bypass. > > > > There should be still a long way to fully functional worker node on such smaller memory node, such as auto-config , devices audit and other containerization services etc., > I had the impression as well that it was going to be a long path, but is definitely important, especially for hybrid edge cloud systems Thanks > The status and plan for net step is shared in [1] > > I created story [2] to track the change if task is ready > > > > [1] https://drive.google.com/file/d/1nt-Mx2Ebrqr4IBruSoOVmB5cjdOQ9HJR/view?usp=sharing > > [2] https://storyboard.openstack.org/#!/story/2006787 > > > > Thanks. > > BR > Austin Sun. > > > > > > > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Bill.Zvonar at windriver.com Wed Oct 30 12:01:29 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 30 Oct 2019 12:01:29 +0000 Subject: [Starlingx-discuss] Community Call (Oct 30, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B185A5@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of the Community call later today. Bruce will host today as I'm unable to attend. 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=20191030T1400 -------------- next part -------------- An HTML attachment was scrubbed... URL: From tingjie.chen at intel.com Wed Oct 30 13:28:05 2019 From: tingjie.chen at intel.com (Chen, Tingjie) Date: Wed, 30 Oct 2019 13:28:05 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/30 In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F360A8185@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F360A8185@SHSMSX104.ccr.corp.intel.com> Message-ID: Updates for Ceph containerization: 1/ For the helm-charts of rook-ceph (rook operator) and ceph-cluster (ceph services) Maratin and me are ramp up and work on the rebase and overrides patches, the idea is to export the certain version(1.1.1) and download the rook-ceph helm-chart as tgz and describe it in manifest, also maintain the .patch files for customized changes in starlingx (such as CSI plugin docker image version (the rook community has not assign Ceph CSI plugin version), and local registry, and rook operator docker image version). When need upgrade, upgrade the version tag and the related .patch files. Also Martin has discussion for Armada Operator which impact the helm-chart overrides to decoupling with sysinv-conductor, as attachment mail. Currently 2 patches in working as following and also got feedbacks from community. https://review.opendev.org/#/c/681457 https://review.opendev.org/#/c/687340 2/ The new plugin: python-rookclient Currently I have fork a private github to develop the plugin, which is aiming to provide interface for sysinv, the implementation is to override the rook yaml files/configmap, this github will continue to dev, so is it convenient to maintain the plugin in stx git project? 3/ About the develop plan We have reschedule the dev plan and need to make full discussion about the solution, and plan to integrate the patches in next release, the StoryBoard: https://storyboard.openstack.org/#!/story/2005527 will update to breakdown more details soon. Thanks, Tingjie -----Original Message----- From: Xie, Cindy Sent: Tuesday, October 29, 2019 9:22 PM To: Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; 'Rowsell, Brent' Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/30 Agenda for 10/30 meeting: - Welcome new PL Austin Sun - Switch the meeting time starting from 11/6 - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade update (Shuai) - CVE LP fixing (Shuicheng) - Opens (all) -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W; Sun, Austin Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, October 30, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . 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 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An embedded message was scrubbed... From: "Chen, Haochuan Z" Subject: decouple sysinv-conductor with armada application, request to decouple the way to generate image file with armada chart Date: Tue, 29 Oct 2019 07:17:58 +0000 Size: 7295 URL: From cindy.xie at intel.com Wed Oct 30 13:41:48 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 30 Oct 2019 13:41:48 +0000 Subject: [Starlingx-discuss] Notes: Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/30 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F360AB61E@SHSMSX104.ccr.corp.intel.com> Agenda for 10/30 meeting: - Welcome new PL Austin Sun Austin will be the new PL starting from next week. - Switch the meeting time starting from 11/6 May push to 1 hour, but we will discuss the meeting slot in community call. Cindy will send out the cancellation to mailing list. new meeting invitation will be sent out by Austin once the time slot got agreed. - Ceph containerization update (Tingjie) https://review.opendev.org/#/c/681457, ported the rook-helm-chart from community, The new design is to download the rook-ceph helm-chart as tgz and describe it in manifest, also maintain the patch file for customized changes in StarlingX. Need design discussion btw Brent and Tingjie for a better design. The new plug-in python-rookclient. private Github. Saul: there is an existing repo called "StarlingX/client". Another option is under utility because we have Ceph client under utility. Dev plan: schedule pushed out to stx.4.0 due to the design complexity. Tingjie will update the storyboard and break down into more details tasks. - CentOS 8.0 upgrade update (Shuai) Toolchain upgraded and kernel compilation passed. rpm in 7.6 packages build under new kernel. please ensure each patch analysis can be explained. - CVE LP fixing (Shuicheng) 3 CVEs needs to be upgraded: 2 are related to kernel CVE. CentOS7.6 kernel is no longer maintained. So there is no RPM can be ported over to 7.6. Proposal from Shuicheng is to upgrade the kernel to the version from 7.7. No other srpm/rpm upgrade shall be needed. Will use the same kernel in master and stx.2.0 till the master upgrade to 8.0. - Opens (all) Cindy Xie -----Original Message----- From: Xie, Cindy Sent: Tuesday, October 29, 2019 9:22 PM To: Wold, Saul ; 'starlingx-discuss at lists.starlingx.io' ; 'Rowsell, Brent' Subject: Agenda: Weekly StarlingX non-OpenStack distro meeting, 10/30 Agenda for 10/30 meeting: - Welcome new PL Austin Sun - Switch the meeting time starting from 11/6 - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade update (Shuai) - CVE LP fixing (Shuicheng) - Opens (all) -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W; Sun, Austin Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, October 30, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 . 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 From Bill.Zvonar at windriver.com Wed Oct 30 13:59:50 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 30 Oct 2019 13:59:50 +0000 Subject: [Starlingx-discuss] Unit Test Coverage Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B1865F@ALA-MBD.corp.ad.wrs.com> Hi all, As discussed in recent community calls and release team meetings, we agree that maintaining & increasing unit test coverage is an important step in maintaining & increasing the quality of our code base. I'd like to highlight some recent work by the config sub-project to help 'lower the bar' for contributors to be able to add new unit tests to this sub-project. Going forward, they will require new commits to include appropriate unit tests. This is an excellent model for other sub-projects to follow on their path to having a reasonably low bar of entry for their contributors to add unit tests. I'll be reaching out to those sub-project teams on this - if anyone is interested in helping, please let me know. As well, as discussed in the community call recently, Ada is working on building a heat map [5] of where bugs are coming from - this will help us focus our unit test attention in the areas that have the biggest impact to our project. Thoughts/comments welcome! Bill... >From the config sub-project... We've enhanced and aligned the base unit tests to provide consistency across the different components - specifically for sysinv-api, sysinv-puppet and sysinv-helm. The base unit tests leverage a common system description and configuration, thus adding an expanded coverage of target system deployment configurations to reduce the likelihood of breaking changes that are specific to deployment scenarios (e.g. ipv4 vs ipv6, aio-sx/dx vs standard configurations, etc). Existing and new unit tests will benefit from any additional deployment scenarios that are contributed to the base classes. There are example unit tests available to use as a guide [1-3], and a general guide for how to write unit tests in this area is available at [4]. Going forward, the starlingx/config sub-project will require that new commits to this area be accompanied by appropriate unit tests. [1] https://opendev.org/starlingx/config/src/branch/master/sysinv/sysinv/sysinv/sysinv/tests/puppet/test_puppet.py [2] https://opendev.org/starlingx/config/src/branch/master/sysinv/sysinv/sysinv/sysinv/tests/helm/test_helm.py [3] https://opendev.org/starlingx/config/src/branch/master/sysinv/sysinv/sysinv/sysinv/tests/api/test_host.py [4] https://opendev.org/starlingx/config/src/branch/master/sysinv/sysinv/sysinv/HACKING.rst [5] https://docs.google.com/spreadsheets/d/1pZ3kTpkurKuOzTckbkxX9NHkjg2fMH71Ydl_KEVK4eY/edit?usp=sharing -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Wed Oct 30 14:03:59 2019 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 30 Oct 2019 14:03:59 +0000 Subject: [Starlingx-discuss] exploration for adding smaller memory node on stx system In-Reply-To: References: Message-ID: Hi Victor: the containerizing is just current approach , as mentioned in ppt shared in google driver, there are other potential approaches. If memory is large enough , then not only K8S , but also openstack could be support since openstack are already containerized. About external OS package question , I would say currently NO, only need node support docker and Kubernetes. Yes, there might be overlaps this task , containerization and multi-os , some items can be shared among those projects. But the target/goal is not same . Those services are already containerized, so I just use "docker stats xxxxx" to check the memory and cpu usage of those container. Thanks. BR Austin Sun. -----Original Message----- From: Victor Rodriguez Sent: Wednesday, October 30, 2019 8:01 PM To: Sun, Austin Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] exploration for adding smaller memory node on stx system On Wed, Oct 30, 2019 at 2:42 AM Sun, Austin wrote: > > Hi StarlingX Community: > > I have spent some time to explore how to add smaller memory node on stx system. > > The approach I’m trying is containerizing flocking services for worker node. > Thanks, Austin, having the capability to add small footprint nodes will open the possibilities for users of StarlingX The approach is to containerizing flocking services for worker node seems the most straight forward solution. I was wondering if the scope will be just to make the node visible for k8 or also for open stack. I could think that for now just k8. One more question (based on the previous mail I sent about memory ) is there any host OS package is going to be needed? if so we can work in collaboration with the multi os team to handle it. I was wondering if the kernel or systemd might be needed on the worker + the flock services. One more thing, how do you measure the MB of virtual memory used by the services? > And the status/achievement are > > 2G memory nodes (ubuntu 18.04 and centos 7.6) were successfully added to multi-node stx system . > Great !! > this node is unlocked , available and joined stx k8s system. > > Sysinv-agent , hbsClient and mtcClient are containerized and deploy this node . > Configuration was manually set and some device audit was bypass. > > > > There should be still a long way to fully functional worker > node on such smaller memory node, such as auto-config , devices audit > and other containerization services etc., > I had the impression as well that it was going to be a long path, but is definitely important, especially for hybrid edge cloud systems Thanks > The status and plan for net step is shared in [1] > > I created story [2] to track the change if task is ready > > > > [1] > https://drive.google.com/file/d/1nt-Mx2Ebrqr4IBruSoOVmB5cjdOQ9HJR/view > ?usp=sharing > > [2] https://storyboard.openstack.org/#!/story/2006787 > > > > Thanks. > > BR > Austin Sun. > > > > > > > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Wed Oct 30 14:19:14 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 30 Oct 2019 14:19:14 +0000 Subject: [Starlingx-discuss] Calsoft's Contribution- StarlingX All-in-one EdgeX Deployment In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F36085072@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F36085072@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F360AB704@SHSMSX104.ccr.corp.intel.com> All, For those developers who are interested to the great work Saichandu has done, but cannot access Google service (those from China), I’ve uploaded the image and the doc up to Baidu Cloud. And below are the link: https://pan.baidu.com/s/1OJT2QvrWbY5eLgjn4qB6dA Extract code:645f Due to the fact that the image file is too big, we divided it into 5 files. You need to download all those 5 files, and then use 7zip to decompress the 1st file. Please let us know if there is any questions. Thanks Hejun of uploading it. And again thanks Sai of contributing the EdgeX integration w/ StarlingX! Thx. - cindy From: Xie, Cindy Sent: Monday, October 14, 2019 9:02 PM To: Saichandu Behara ; Bill.Zvonar at windriver.com; starlingx-discuss at lists.starlingx.io; Pavan Gupta ; Jones, Bruce E Subject: Re: [Starlingx-discuss] Calsoft's Contribution- StarlingX All-in-one EdgeX Deployment Thanks Behara! Really appreciate to have EdgeX deployment steps documented. It will be nice if the changes can be updated on docs.starlingx.io. Please see the contribution guide here: https://docs.starlingx.io/contributor/doc_contribute_guide.html again, thanks very much for the effort! Cindy Xie IAGS [StarlingX] From: Saichandu Behara > Sent: Monday, October 14, 2019 7:15 PM To: Bill.Zvonar at windriver.com; starlingx-discuss at lists.starlingx.io; Pavan Gupta > Subject: [Starlingx-discuss] Calsoft's Contribution- StarlingX All-in-one EdgeX Deployment Hello All, The deployment of EdgeX in StarlingX all-in-one Simplex is done successfully. But we faced some challenges during whole process. Thus, to ease the process for a newbie, we have created ready-to-use qcow2 images. One can simply use this image to deploy the VM (containing StarlingX with K8S and EdgeX). Below are the links for StarlingX_all-in-one_Edgex setup Document and Image link. Setup Document: https://drive.google.com/open?id=1j0IBwKiwwD1Vju9_QltFo1oItMIa41x3 Image Link: https://drive.google.com/open?id=1ntQSILp4rg-L_CMQPLCPsvtYdAmQFHFp This is our very first step as contribution to this community and we would like to add more in future. Please let us know where can we upload these images and documents. -- Thanks & Regards Sai Chandu Behara -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 12578 bytes Desc: image002.png URL: From yong.hu at intel.com Wed Oct 30 14:20:10 2019 From: yong.hu at intel.com (Yong Hu) Date: Wed, 30 Oct 2019 22:20:10 +0800 Subject: [Starlingx-discuss] Calsoft's Contribution- StarlingX All-in-one EdgeX Deployment In-Reply-To: References: Message-ID: <51e0246e-c865-30e1-7679-1cd9f83abdfc@intel.com> Hi Sai, What version of EdgeX did you deployed in StarlingX/K8S? I am thinking to make an Armada/helm "application" like "stx-edgex", which hopefully will make life easier. regards, Yong On 2019/10/14 7:15 PM, Saichandu Behara wrote: > Hello All, > > The deployment of EdgeX in StarlingX all-in-one Simplex is done > successfully. But we faced some challenges during whole process. Thus, > to ease the process for a newbie, we have created ready-to-use qcow2 > images. One can simply use this image to deploy the VM /(containing > StarlingX with //K8//S and EdgeX//)/.  Below are the links for > StarlingX_all-in-one_Edgex setup Document and Image link. > > Setup Document: > https://drive.google.com/open?id=1j0IBwKiwwD1Vju9_QltFo1oItMIa41x3 > > Image Link: > https://drive.google.com/open?id=1ntQSILp4rg-L_CMQPLCPsvtYdAmQFHFp > > This is our very first step as contribution to this community and we > would like to add more in future. > > Please let us know where can we upload these images and documents. > > -- > Thanks & Regards > Sai Chandu Behara > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From cindy.xie at intel.com Wed Oct 30 14:23:20 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 30 Oct 2019 14:23:20 +0000 Subject: [Starlingx-discuss] mirror in China behind the firewall Message-ID: <2FD5DDB5A04D264C80D42CA35194914F360AB72D@SHSMSX104.ccr.corp.intel.com> All, We got some feedback mostly from China users that it's extremely slow to pull the images from mirror/registry when deploy StarlingX. Here we created a mirror behind China firewall so it makes easier for the developers in China. Please see attached doc and scripts for how to use it. We didn't translate it into English as I guess most of people find it useful can understand it. Thx. - cindy -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Readme.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 37579 bytes Desc: Readme.docx URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: 1_Warning.txt URL: From cindy.xie at intel.com Wed Oct 30 14:44:08 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 30 Oct 2019 14:44:08 +0000 Subject: [Starlingx-discuss] mirror in China behind the firewall In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F360AB72D@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F360AB72D@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F360AB7C9@SHSMSX104.ccr.corp.intel.com> In case that you find the sh file got blocked, here is the txt version. You just can use it but replace the extension. From: Xie, Cindy Sent: Wednesday, October 30, 2019 10:23 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] mirror in China behind the firewall All, We got some feedback mostly from China users that it's extremely slow to pull the images from mirror/registry when deploy StarlingX. Here we created a mirror behind China firewall so it makes easier for the developers in China. Please see attached doc and scripts for how to use it. We didn't translate it into English as I guess most of people find it useful can understand it. Thx. - cindy -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ci_stx-registry-mirror.txt URL: From scott.little at windriver.com Wed Oct 30 14:54:46 2019 From: scott.little at windriver.com (Scott Little) Date: Wed, 30 Oct 2019 10:54:46 -0400 Subject: [Starlingx-discuss] Heat map question from the community call Message-ID: <22a0bfb8-a399-7fe2-270d-9efee88a6363@windriver.com> To identify frequently changing files within a git e.g. Changes per file within stx-tools since Jan 1 2019, high runners at top of the list... cd stx-tools for sha in $(git log --since "Jan 1 2019" --pretty=format:"%H"); do     git diff-tree --no-commit-id --name-only -r $sha done | sort | uniq -c | sort -nr 42 centos-mirror-tools/rpms_centos.lst 22 centos-mirror-tools/tarball-dl.lst 14 centos-mirror-tools/rpms_centos3rdparties.lst 9 Dockerfile ... From Tao.Liu at windriver.com Wed Oct 30 15:03:24 2019 From: Tao.Liu at windriver.com (Liu, Tao) Date: Wed, 30 Oct 2019 15:03:24 +0000 Subject: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 In-Reply-To: References: <7242A3DC72E453498E3D783BBB134C3EA4EB1E0F@ALA-MBD.corp.ad.wrs.com> Message-ID: <7242A3DC72E453498E3D783BBB134C3EA4EC3DA6@ALA-MBD.corp.ad.wrs.com> Hi Austin, The deployment status is shown under ' deploy status' field. The availability state depends on whether the DC manager can communicate with the Subcloud via the mgmt. interface. If the Subcloud mgmt. IP is not routable between the Central cloud and Subcloud, the availability state shows 'offline'. That's why the availability state changed to online after adding route. You can use the SystemController to add subclouds, synchronize select configuration data (such as the certificate, DNS and NTP), across all subclouds and monitor subcloud operations and alarms. You can also access the individual subclouds through Horizon dashboard at the Central Cloud to perform subcloud-specific operations such as configuring and managing the subclouds' host nodes. System software updates for the subclouds are also centrally managed and applied from the SystemController. Regards, Tao -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Saturday, October 26, 2019 8:33 AM To: Liu, Tao; Arce Moreno, Abraham; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi Tao: With the V2 guide you shared , I deployed dist-cloud on virtual environment successfully. There is one different between the guide and setup I deployed In guide, "After run "dcmanager subcloud add --bootstrap-ip --bootstrap-values " , Confirm that the subcloud was deployed successfully" But The result of 'dcmanager subcloud list' on my setup is offline , not online, it became online only after adding route from subcloud to controller mgmt. network. Is it normal behavior ? Another question is what the capability about system controller beside monitoring subcloud alarm . The image is using 20191017T013000Z Thanks. BR Austin Sun. -----Original Message----- From: Sun, Austin Sent: Saturday, October 26, 2019 9:21 AM To: Liu, Tao ; Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi, Tao: Thanks a lot. So , there are two phase : In Phase 1( bootstrap subcloud) , sub-cloud OAM is need to routed to central OAM. In Phase 2(provision/manger subcloud) mgmt. subcloud is need to routed to central cloud mgmt. network. Thanks. BR Austin Sun. -----Original Message----- From: Liu, Tao Sent: Friday, October 25, 2019 9:02 PM To: Sun, Austin ; Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi Austin, The subcloud bootstrapping interface can be any interface that has connectivity to the system controller. The script we provided will configure the IP and route on the selected interface. We recommended using the mgmt. interface previously because it would not require configuring OAM prior to bootstrapping, however, the mgmt. subnet would have to be a different subnet than the one that will be configured on the mgmt. interface after bootstrapping. This means an 'additional temporary' IP address/subnet on mgmt. interface is required for bootstrapping. The decision to use the OAM interface and IP removes the requirement to allocate an 'additional temporary' IP address/subnet, and it is consistent with a NON-DC scenario. See inline comments for your questions. Tao -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Thursday, October 24, 2019 9:39 PM To: Liu, Tao; Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi Tao: Thanks your update . which gerrit or patch enhances using OAM interface and IP to bootstrap the subcloud ? has this patch already been merged ? TL> My document update changes network requirements and no code change is required. Another question , will OAM ip in subcloud L3 connection to OAM ip in central cloud ? does it request mgmt ip in subcloud L2 connect to OAM ip in central cloud for V2? TL> Yes, OAM IP Subnets need to be routable between Central Cloud and Subclouds. No, mgmt. ip in subcloud should not be connected to OAM ip in central cloud. Thanks. BR Austin Sun. -----Original Message----- From: Liu, Tao Sent: Friday, October 25, 2019 2:27 AM To: Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Thanks Arce! A decision has been made to use OAM Interface and IP to bootstrap the subcloud. I have updated the document accordingly. The main change is to run the config_management script and enable OAM interface. Tao -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Monday, October 21, 2019 1:25 PM To: Liu, Tao; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 > Please add Distributed Cloud Configuration Guide to StarlingX R3.0 > Installation. Hi Tao, Distributed Cloud team, Here you have an early review of Distributed Cloud: https://review.opendev.org/#/c/689847/ We will take it as our base documentation and do the installation in our labs starting today, some changes likely coming. For now, please let us know if we need to add more people as Co-Authored-By. From bruce.e.jones at intel.com Wed Oct 30 18:31:59 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 30 Oct 2019 18:31:59 +0000 Subject: [Starlingx-discuss] Community meeting notes Oct 30 2019 Message-ID: <9A85D2917C58154C960D95352B22818BDFC008FC@fmsmsx123.amr.corp.intel.com> Oct 30 2019 * date/time: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191030T1400 * standing topics * any Gerrit reviews that need attention? * OVS collectd interface/port state monitoring ? review https://review.opendev.org/#/c/687025/, Chenjie's email http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006679.html * OpenStack Train reviews - Waiting on 2+2+2 config not passing Sanity. The team un-reverted a patch (#) but that doesn't fully solve the problem. * sanity - any reds since last call? * Yes, we have had several failing runs. One commit was reverted yesterday which should address the current problem. * any unanswered calls for assistance on the mailing list * Sai - asking for an update on the "create an image" documentation. To be discussed in the Docs team meeting later today. * There is an active WeChat channel for StarlingX. There are 119 members. The Intel China team is not sure if the users would want to swtich to some other platform. There is a lot of activity that we aren't capturing in our metrics. There is customer feedback that the broader community isn't hearing. How to proceed? (brucej) * Ildiko - there is a WeChat channel for OpenStack too. It seems unlikely that we could merge that with a different method. We could appoint a liason or two to monitor the channel and report back to the broader community. Cindy's team can monitor the group and provide a weekly summary to the email list. * The US and Canada are Falling Back this weekend. What do we do? 5AM meetings are not fun. Ildiko - the last time we talked about this we agreed to keep meetings at the same US time. Unanimous support from the community call to keep meetings in US time. (brucej) * Development process doc is in progress. Feedback and collaboration are welcome and TY Bart & Saul for yours! I am looking for opportunities to make the document more aligned with what we actually do and the process more open. Thus the TODO about moving bug triage out into the open - can we leverage a time / existing meeting to start doing that together as a community.? (brucej) * Review: https://review.opendev.org/#/c/691740 * Frank - Ghada and a small team do bug triage several times a week. It will be hard to find a slot for a new meeting. We could have a process where a small team assigns bugs to PLs but the actual triage happens in the team meetings. Saul - we could also do some of this in the Release team meeting. We could have a rotating responsibility to have someone take on a frequent review of issues (as per the Yocto project). Ghada isn't here so let's tee this up for next week. * PSA: Feature candidates for stx.4.0 will be discussed at the PTG next week. An etherpad has been started, https://etherpad.openstack.org/p/stx.4.0-feature-candidates. Please add any new items for consideration in the upcoming release and/or commentson items already captured. * PSA: update on unit test coverage ? will be reaching out to other sub-projects to follow config team's model for making it clear/easy how to add unit tests: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006710.html ? Ada started working on an issue 'heat map' https://docs.google.com/spreadsheets/d/1pZ3kTpkurKuOzTckbkxX9NHkjg2fMH71Ydl_KEVK4eY/edit?usp=sharing - will highlight where more unit tests are most needed * PSA - Project Update at Summit moved to Tuesday Morning slot @ 9:00am - 9:40am - sgw * Shuquan and Saul to present, we should advertise this here and on the list shortly * Are we holding our standing meetings next week? Each team and PL can decide if they want to hold a meeting. There will be no Test team meeting next week due to a conflict. We can hold the community meeting as scheduled. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Oct 30 20:25:27 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 30 Oct 2019 20:25:27 +0000 Subject: [Starlingx-discuss] Calsoft's Contribution- StarlingX All-in-one EdgeX Deployment In-Reply-To: <51e0246e-c865-30e1-7679-1cd9f83abdfc@intel.com> References: <51e0246e-c865-30e1-7679-1cd9f83abdfc@intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BDFC009B8@fmsmsx123.amr.corp.intel.com> Hi Sai. In the Docs team meeting today we talked about this. Kris (the Docs PL) has a review up to start the process of getting your document converted to our format. See https://review.opendev.org/#/c/692202/ for the first draft. Please feel free to join in the review. But we'd like to ask you for a follow on document. Can you please provide some material for the "how to create this image" part of the process? Going forward we'll want to re-create this image for new StarlingX releases and if you've figured out a good way to do that, we'd love to know about it. Thank you! brucej -----Original Message----- From: Yong Hu [mailto:yong.hu at intel.com] Sent: Wednesday, October 30, 2019 7:20 AM To: Saichandu Behara ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Calsoft's Contribution- StarlingX All-in-one EdgeX Deployment Hi Sai, What version of EdgeX did you deployed in StarlingX/K8S? I am thinking to make an Armada/helm "application" like "stx-edgex", which hopefully will make life easier. regards, Yong On 2019/10/14 7:15 PM, Saichandu Behara wrote: > Hello All, > > The deployment of EdgeX in StarlingX all-in-one Simplex is done > successfully. But we faced some challenges during whole process. Thus, > to ease the process for a newbie, we have created ready-to-use qcow2 > images. One can simply use this image to deploy the VM /(containing > StarlingX with //K8//S and EdgeX//)/.  Below are the links for > StarlingX_all-in-one_Edgex setup Document and Image link. > > Setup Document: > https://drive.google.com/open?id=1j0IBwKiwwD1Vju9_QltFo1oItMIa41x3 > > Image Link: > https://drive.google.com/open?id=1ntQSILp4rg-L_CMQPLCPsvtYdAmQFHFp > > This is our very first step as contribution to this community and we > would like to add more in future. > > Please let us know where can we upload these images and documents. > > -- > Thanks & Regards > Sai Chandu Behara > > > _______________________________________________ > 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 bruce.e.jones at intel.com Wed Oct 30 20:39:06 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 30 Oct 2019 20:39:06 +0000 Subject: [Starlingx-discuss] Unit Test Coverage In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC007B1865F@ALA-MBD.corp.ad.wrs.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B1865F@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BDFC00A3A@fmsmsx123.amr.corp.intel.com> This is very cool. Are these tests running within Zuul jobs at code check-in time? brucej From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Wednesday, October 30, 2019 7:00 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Unit Test Coverage Hi all, As discussed in recent community calls and release team meetings, we agree that maintaining & increasing unit test coverage is an important step in maintaining & increasing the quality of our code base. I'd like to highlight some recent work by the config sub-project to help 'lower the bar' for contributors to be able to add new unit tests to this sub-project. Going forward, they will require new commits to include appropriate unit tests. This is an excellent model for other sub-projects to follow on their path to having a reasonably low bar of entry for their contributors to add unit tests. I'll be reaching out to those sub-project teams on this - if anyone is interested in helping, please let me know. As well, as discussed in the community call recently, Ada is working on building a heat map [5] of where bugs are coming from - this will help us focus our unit test attention in the areas that have the biggest impact to our project. Thoughts/comments welcome! Bill... >From the config sub-project... We've enhanced and aligned the base unit tests to provide consistency across the different components - specifically for sysinv-api, sysinv-puppet and sysinv-helm. The base unit tests leverage a common system description and configuration, thus adding an expanded coverage of target system deployment configurations to reduce the likelihood of breaking changes that are specific to deployment scenarios (e.g. ipv4 vs ipv6, aio-sx/dx vs standard configurations, etc). Existing and new unit tests will benefit from any additional deployment scenarios that are contributed to the base classes. There are example unit tests available to use as a guide [1-3], and a general guide for how to write unit tests in this area is available at [4]. Going forward, the starlingx/config sub-project will require that new commits to this area be accompanied by appropriate unit tests. [1] https://opendev.org/starlingx/config/src/branch/master/sysinv/sysinv/sysinv/sysinv/tests/puppet/test_puppet.py [2] https://opendev.org/starlingx/config/src/branch/master/sysinv/sysinv/sysinv/sysinv/tests/helm/test_helm.py [3] https://opendev.org/starlingx/config/src/branch/master/sysinv/sysinv/sysinv/sysinv/tests/api/test_host.py [4] https://opendev.org/starlingx/config/src/branch/master/sysinv/sysinv/sysinv/HACKING.rst [5] https://docs.google.com/spreadsheets/d/1pZ3kTpkurKuOzTckbkxX9NHkjg2fMH71Ydl_KEVK4eY/edit?usp=sharing -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Wed Oct 30 21:18:55 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Wed, 30 Oct 2019 21:18:55 +0000 Subject: [Starlingx-discuss] Unit Test Coverage In-Reply-To: <9A85D2917C58154C960D95352B22818BDFC00A3A@fmsmsx123.amr.corp.intel.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B1865F@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BDFC00A3A@fmsmsx123.amr.corp.intel.com> Message-ID: Those are run by zuul as part of the py27 and py35 jobs for sysinv. https://opendev.org/starlingx/config/src/branch/master/.zuul.yaml#L11-L12 They are invoked when any code change is submitted againt the sysinv code tree. Also at merge time (the gate) as well. Al From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, October 30, 2019 4:39 PM To: Zvonar, Bill Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Unit Test Coverage This is very cool. Are these tests running within Zuul jobs at code check-in time? brucej From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Wednesday, October 30, 2019 7:00 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Unit Test Coverage Hi all, As discussed in recent community calls and release team meetings, we agree that maintaining & increasing unit test coverage is an important step in maintaining & increasing the quality of our code base. I'd like to highlight some recent work by the config sub-project to help 'lower the bar' for contributors to be able to add new unit tests to this sub-project. Going forward, they will require new commits to include appropriate unit tests. This is an excellent model for other sub-projects to follow on their path to having a reasonably low bar of entry for their contributors to add unit tests. I'll be reaching out to those sub-project teams on this - if anyone is interested in helping, please let me know. As well, as discussed in the community call recently, Ada is working on building a heat map [5] of where bugs are coming from - this will help us focus our unit test attention in the areas that have the biggest impact to our project. Thoughts/comments welcome! Bill... >From the config sub-project... We've enhanced and aligned the base unit tests to provide consistency across the different components - specifically for sysinv-api, sysinv-puppet and sysinv-helm. The base unit tests leverage a common system description and configuration, thus adding an expanded coverage of target system deployment configurations to reduce the likelihood of breaking changes that are specific to deployment scenarios (e.g. ipv4 vs ipv6, aio-sx/dx vs standard configurations, etc). Existing and new unit tests will benefit from any additional deployment scenarios that are contributed to the base classes. There are example unit tests available to use as a guide [1-3], and a general guide for how to write unit tests in this area is available at [4]. Going forward, the starlingx/config sub-project will require that new commits to this area be accompanied by appropriate unit tests. [1] https://opendev.org/starlingx/config/src/branch/master/sysinv/sysinv/sysinv/sysinv/tests/puppet/test_puppet.py [2] https://opendev.org/starlingx/config/src/branch/master/sysinv/sysinv/sysinv/sysinv/tests/helm/test_helm.py [3] https://opendev.org/starlingx/config/src/branch/master/sysinv/sysinv/sysinv/sysinv/tests/api/test_host.py [4] https://opendev.org/starlingx/config/src/branch/master/sysinv/sysinv/sysinv/HACKING.rst [5] https://docs.google.com/spreadsheets/d/1pZ3kTpkurKuOzTckbkxX9NHkjg2fMH71Ydl_KEVK4eY/edit?usp=sharing -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Wed Oct 30 21:39:14 2019 From: kristal.dale at intel.com (Dale, Kristal) Date: Wed, 30 Oct 2019 21:39:14 +0000 Subject: [Starlingx-discuss] [docs][meetings] docs team meeting minutes 2019-10-30 Message-ID: <43F963BD1517044B90CF82FB2F3CA7162207F0FF@ORSMSX121.amr.corp.intel.com> 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 Cheers, Kris Current agenda and notes 2019-10-30 o All -- reviews in progress and recent merges -- * See summary at https://review.opendev.org/#/q/project:starlingx/docs. * Recent merges: * https://review.opendev.org/#/c/691957/ -- Kris -- Add governance paragraph and link -- MERGED * https://review.opendev.org/#/c/691119/ -- Bruce -- Add the release notes for the R2.0.1 release -- MERGED * We have 3 open: * https://review.opendev.org/#/c/691740/ -- Bruce -- Add an initial development process document to the docs tree * https://review.opendev.org/#/c/691804/ -- Yi Wang -- Add a document about StarlingX Patching * https://review.opendev.org/#/c/689847/ -- Abraham -- StarlingX Distributed Cloud o Abraham and all -- bug status -- https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs * https://bugs.launchpad.net/starlingx/+bug/1849336 -- Medium -- Incorrect path for referencing bootstrap.yaml while running "ansible-playbook" - (Kris) * https://bugs.launchpad.net/starlingx/+bug/1849341 -- Low -- Remove the repeated "helm" string in the command "helm repo update" command - (Kris) * https://bugs.launchpad.net/starlingx/+bug/1835207 -- Low -- Error links for starling project docs -- Abraham asked for help to repository owners in mailing list http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006621.html o Kris -- structure and plans for new config guide -- * Let's walk through these proposals: * https://drive.google.com/file/d/1Galekjlo7vk9JFht5_XhGAECSIAWRNE0 * https://drive.google.com/file/d/1FhdmISmr_N5vLt4ZXCmUbP4vKHxbGsk3 * Check against Mega-spec: https://docs.starlingx.io/specs/specs/2019.03/approved/documentation-mega-spec.html * TSN contribution is in progress: * https://drive.google.com/file/d/1IQZVTEHRra72wNOHiIXD5Y-DKiFkl7yZ * This is subtask 36405 in https://storyboard.openstack.org/#!/story/2006289 * Result of discussion: Greg's task list essentially replaces the Operational Guide docs from mega spec * Kris will merge Operational Guides w/ Greg's list into the new set of docs. * Greg will contribute additional tasks. * Kris will update the story (configs will be rolled up under ops guides) o Bruce -- StarlingX-in-a-box -- We have two vectors on this -- * Erich's contribution -- https://drive.google.com/file/d/19127DWvfrSvpd9QNjHlbNX2-OEbruxKx * Calsoft's contribution -- http://lists.starlingx.io/pipermail/starlingx-discuss/2019-September/006316.html -- (Kris to provide update after review posted/Wed mtg) * We believe this will go into our StarlingX-in-a-box topic as captured in https://storyboard.openstack.org/#!/story/2006622. Bruce has volunteered to help Sai with the contribution. Cindy recently confirmed that this does apply to StarlingX-in-a-box -- https://drive.google.com/file/d/1vzrx7G-G8yCYi3HgOh0FNJvenoisP2qd. * Setup document: https://drive.google.com/open?id=1j0IBwKiwwD1Vju9_QltFo1oItMIa41x3 * Image link: https://drive.google.com/open?id=1ntQSILp4rg-L_CMQPLCPsvtYdAmQFHFp o This is 4.9 GB. How can we host this in the docs site/repo w/out requiring contributors to pull it locally as part of the repo? (Entirety of stx-docs on disk is currently 157 MB - adding this will drastically increase this.) o Do we have other hosting options? The mirror? - Contact Scott Little (Windriver) scott.little at windriver.com - (Kris) * Kris Dale is taking the assignment (working with Bruce) to create a review draft of the doc. We also talked about hosting the images as blobs in the doc repo, which will be linked from the new document on https://docs.starlingx.io/. Latest status is here: https://drive.google.com/file/d/1rZXBGVUlwNbbMIZKDQiimkf246bbo58 * WIP review: https://review.opendev.org/#/c/692202/1 (does not include link to docs hosted qcow2 images) * We are interested in learning how they built the image. Can the folk at Calsoft provide these instructions? - Bruce will initiate convo * Long term plan: including this type of image for each release. Additional repo in tools that it could build from? - Bruce will initiate covo * Kris will continue to support the review (feedback, etc). * Mike -- R3 stories -- * R3 release is currently planned for early December. * Current R3 doc stories are here -- https://storyboard.openstack.org/#!/story/list?tags=stx.docs&tags=stx.3.0 -- * The community team is tracking top stories. I submitted these two for the doc team -- https://drive.google.com/file/d/1dXFLc6f4d5MA2l7rRBMnfyk4X6wZ07wX * R3.0 updates (new features, changes, etc.) - discuss with Greg on his return (WW46) - outline R3 features and changes that may impact docs. (Kris to prep) * Kris -- new PTL * Kris -- Addition of install-time configs (content from Greg). TBD where this fits best. Action required (AR) summary Completed ARs are archived here: https://etherpad.openstack.org/p/stx-documentation-files-003 * -- -- * 2019-05-15 -- Abraham -- Review these code and terminology changes impacting user docs -- https://drive.google.com/file/d/1sCB-lrWhDIJLNAGWBt7wJ1_JxY21m71p -- and report back on specific actions required. * 2019-10-02 -- Kris and Mary -- Update the contributor guide at https://docs.starlingx.io/contributor/doc_contribute_guide.html to reflect our current doc schema and incorporate elements of the "cheat sheet." * 2019-10-30 -- Kris -- Contact Scott Little regarding hosting Calsoft qcow2 images. * 2019-10-30 -- Kris -- Merge Config Guide/Greg's tasks/Operational Guide topics into one for review. -------------- next part -------------- An HTML attachment was scrubbed... URL: From David.Sullivan at windriver.com Wed Oct 30 23:18:41 2019 From: David.Sullivan at windriver.com (Sullivan, David) Date: Wed, 30 Oct 2019 23:18:41 +0000 Subject: [Starlingx-discuss] Renaming CPU functions Message-ID: Hello, As part of some code cleanup the CPU function "Applications" has been renamed "Application" The application function is derived not assigned so there shouldn't be any functional impact, only the display has changed. If you have any scripts that parse the CPU functions they may need to be updated. Thanks, David Changes: https://review.opendev.org/#/c/691927/ https://review.opendev.org/#/c/691929/ Launchpad: https://bugs.launchpad.net/starlingx/+bug/1848973 -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Thu Oct 31 00:47:26 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 31 Oct 2019 00:47:26 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191030 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-30 (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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] 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 PASS ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006705.html Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Thu Oct 31 01:19:14 2019 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 31 Oct 2019 01:19:14 +0000 Subject: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 In-Reply-To: <7242A3DC72E453498E3D783BBB134C3EA4EC3DA6@ALA-MBD.corp.ad.wrs.com> References: <7242A3DC72E453498E3D783BBB134C3EA4EB1E0F@ALA-MBD.corp.ad.wrs.com> <7242A3DC72E453498E3D783BBB134C3EA4EC3DA6@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Tao: Thanks you . Is this synchronization between System Controller and Subclouds automatic , and can not be individual config ? How access individual subclouds though Horizon dashboard at the Central Cloud ? The system deployed is 10/17, there is only subcloud info (the sublcoud is in-sync status) Thanks. BR Austin Sun. -----Original Message----- From: Liu, Tao Sent: Wednesday, October 30, 2019 11:03 PM To: Sun, Austin ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi Austin, The deployment status is shown under ' deploy status' field. The availability state depends on whether the DC manager can communicate with the Subcloud via the mgmt. interface. If the Subcloud mgmt. IP is not routable between the Central cloud and Subcloud, the availability state shows 'offline'. That's why the availability state changed to online after adding route. You can use the SystemController to add subclouds, synchronize select configuration data (such as the certificate, DNS and NTP), across all subclouds and monitor subcloud operations and alarms. You can also access the individual subclouds through Horizon dashboard at the Central Cloud to perform subcloud-specific operations such as configuring and managing the subclouds' host nodes. System software updates for the subclouds are also centrally managed and applied from the SystemController. Regards, Tao -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Saturday, October 26, 2019 8:33 AM To: Liu, Tao; Arce Moreno, Abraham; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi Tao: With the V2 guide you shared , I deployed dist-cloud on virtual environment successfully. There is one different between the guide and setup I deployed In guide, "After run "dcmanager subcloud add --bootstrap-ip --bootstrap-values " , Confirm that the subcloud was deployed successfully" But The result of 'dcmanager subcloud list' on my setup is offline , not online, it became online only after adding route from subcloud to controller mgmt. network. Is it normal behavior ? Another question is what the capability about system controller beside monitoring subcloud alarm . The image is using 20191017T013000Z Thanks. BR Austin Sun. -----Original Message----- From: Sun, Austin Sent: Saturday, October 26, 2019 9:21 AM To: Liu, Tao ; Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi, Tao: Thanks a lot. So , there are two phase : In Phase 1( bootstrap subcloud) , sub-cloud OAM is need to routed to central OAM. In Phase 2(provision/manger subcloud) mgmt. subcloud is need to routed to central cloud mgmt. network. Thanks. BR Austin Sun. -----Original Message----- From: Liu, Tao Sent: Friday, October 25, 2019 9:02 PM To: Sun, Austin ; Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi Austin, The subcloud bootstrapping interface can be any interface that has connectivity to the system controller. The script we provided will configure the IP and route on the selected interface. We recommended using the mgmt. interface previously because it would not require configuring OAM prior to bootstrapping, however, the mgmt. subnet would have to be a different subnet than the one that will be configured on the mgmt. interface after bootstrapping. This means an 'additional temporary' IP address/subnet on mgmt. interface is required for bootstrapping. The decision to use the OAM interface and IP removes the requirement to allocate an 'additional temporary' IP address/subnet, and it is consistent with a NON-DC scenario. See inline comments for your questions. Tao -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Thursday, October 24, 2019 9:39 PM To: Liu, Tao; Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi Tao: Thanks your update . which gerrit or patch enhances using OAM interface and IP to bootstrap the subcloud ? has this patch already been merged ? TL> My document update changes network requirements and no code change is required. Another question , will OAM ip in subcloud L3 connection to OAM ip in central cloud ? does it request mgmt ip in subcloud L2 connect to OAM ip in central cloud for V2? TL> Yes, OAM IP Subnets need to be routable between Central Cloud and Subclouds. No, mgmt. ip in subcloud should not be connected to OAM ip in central cloud. Thanks. BR Austin Sun. -----Original Message----- From: Liu, Tao Sent: Friday, October 25, 2019 2:27 AM To: Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Thanks Arce! A decision has been made to use OAM Interface and IP to bootstrap the subcloud. I have updated the document accordingly. The main change is to run the config_management script and enable OAM interface. Tao -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Monday, October 21, 2019 1:25 PM To: Liu, Tao; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 > Please add Distributed Cloud Configuration Guide to StarlingX R3.0 > Installation. Hi Tao, Distributed Cloud team, Here you have an early review of Distributed Cloud: https://review.opendev.org/#/c/689847/ We will take it as our base documentation and do the installation in our labs starting today, some changes likely coming. For now, please let us know if we need to add more people as Co-Authored-By. From zhipengs.liu at intel.com Thu Oct 31 01:34:45 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 31 Oct 2019 01:34:45 +0000 Subject: [Starlingx-discuss] About EB verification for openstack train upgrade In-Reply-To: <93814834B4855241994F290E959305C7530F1C97@SHSMSX104.ccr.corp.intel.com> References: <3B594C2B-E02A-4844-A3AA-0649C2885989@intel.com> <93814834B4855241994F290E959305C7530F1A5F@SHSMSX104.ccr.corp.intel.com> <45705CE3-2F92-43BB-9ADF-A5B17861DC71@intel.com> <2FD5DDB5A04D264C80D42CA35194914F360AB833@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F1C97@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C7530F2D55@SHSMSX104.ccr.corp.intel.com> From: Liu, ZhipengS Sent: 2019年10月30日 23:24 To: Xie, Cindy ; Lemus Contreras, Cristopher J ; 朱博祥 ; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang, It should be an issue in nova train. Error log is below: build of instance 363dddce-7af6-4701-8cea-52630b91ebcf aborted: Image 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, but format is now qcow2' You tried to fix this issue before in nova LP: https://bugs.launchpad.net/nova/+bug/1816686 In your patch: https://review.opendev.org/#/c/640271 (This patch is already in train release now) You added below commit message in the patch. “When we import image into rbd, check the format of cache images. If the format is not raw, remove it first and fetch it again. It will be raw format now.” However, it seems not work! Below code will throw error when image format is not raw and block the VM creation. In nova/virt/images.py def fetch_to_raw() ==> if data.file_format != "raw": raise exception.ImageUnacceptable(image_id=image_href, reason=_("Converted to raw, but format is now %s") Not sure if your patch fixed this issue or is there any regression introduced in nova code later. Any comment from you? I will check nova code further tomorrow and sync with you. We may need a patch for nova☹ Thanks! Zhipeng From: Xie, Cindy > Sent: 2019年10月30日 22:49 To: Lemus Contreras, Cristopher J >; Liu, ZhipengS >; 朱博祥 >; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade + mailing list in case anybody can help on debug the issue. From: Lemus Contreras, Cristopher J > Sent: Wednesday, October 30, 2019 7:45 PM To: Liu, ZhipengS >; 朱博祥 > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Xie, Cindy >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, The results are OK for Simplex, Duplex and Standard Local Storage, all Test Cases PASSED. For Standard External Storage (2+2+2) there is a high quantity of Test Cases failing because we cannot launch instances. Here’s a sample output: http://paste.openstack.org/show/785641/ with the error that matches what is described on the launchpad. Sanity summary for this specific configuration: http://paste.openstack.org/show/785655/ Please, let us know if you need additional details. Thanks & Regards, Cristopher Lemus -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhu.boxiang at 99cloud.net Thu Oct 31 02:41:19 2019 From: zhu.boxiang at 99cloud.net (=?UTF-8?B?5pyx5Y2a56Wl?=) Date: Thu, 31 Oct 2019 10:41:19 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?About_EB_verification_for_openstack?= =?utf-8?q?_train_upgrade?= In-Reply-To: <93814834B4855241994F290E959305C7530F2D84@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Zhipeng, I have succeeded to create the vm in openstack upstream(master, code is two weeks ago) now. I deployed the environment with kolla-ansible(ceph as the backend storage). In my nova.conf file, the section of libvirt is as followed: [libvirt] connection_uri = qemu+tcp://172.16.140.14/system images_type = rbd images_rbd_pool = vms images_rbd_ceph_conf = /etc/ceph/ceph.conf rbd_user = nova disk_cachemodes = network=writeback hw_disk_discard = unmap rbd_secret_uuid = 5c79d567-e142-4ab4-87f6-0fdf53060ab9 virt_type = kvm The default value of 'force_raw_images' in nova is True, so I did not set it as True again in my nova.conf file. I use the min image cirros with qcow2 format and created the vm without volume which is created by cinder. It's my image's info: (nova-compute)[root at zbx-allinone /]# qemu-img info cirros-0.4.0-x86_64-disk.img image: cirros-0.4.0-x86_64-disk.img file format: qcow2 virtual size: 44M (46137344 bytes) disk size: 12M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false So as you said, command qemu-img failed to convert the image from qcow2 to raw. BTW, is it a phenomenon that must recur now in STX? Are there other error logs in nova-compute or other nova-* services? -- Thanks, Boxiang 发件人:"Liu, ZhipengS" 发送日期:2019-10-31 10:14:44 收件人:"Liu, ZhipengS" ,"Xie, Cindy" ,"Lemus Contreras, Cristopher J" ,"'朱博祥'" ,"'starlingx-discuss at lists.starlingx.io'" 抄送人:"Alonso, Juan Carlos" ,"Hu, Yong" ,"Cabrales, Ada" ,"Jones, Bruce E" ,"Martinez Monroy, Elio" 主题:RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang and all, In fetch_to_raw(), After force convert image from qcow2 to raw, the format is still not raw, then throw below error. It seems qemu-image convert image failed. Zhipeng From: Liu, ZhipengS Sent: 2019年10月31日 9:35 To: Xie, Cindy ; Lemus Contreras, Cristopher J ; '朱博祥' ; 'starlingx-discuss at lists.starlingx.io' Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade From: Liu, ZhipengS Sent: 2019年10月30日 23:24 To: Xie, Cindy ; Lemus Contreras, Cristopher J ; 朱博祥 ; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang, It should be an issue in nova train. Error log is below: build of instance 363dddce-7af6-4701-8cea-52630b91ebcf aborted: Image 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, but format is now qcow2' You tried to fix this issue before in nova LP: https://bugs.launchpad.net/nova/+bug/1816686 In your patch: https://review.opendev.org/#/c/640271 (This patch is already in train release now) You added below commit message in the patch. “When we import image into rbd, check the format of cache images. If the format is not raw, remove it first and fetch it again. It will be raw format now.” However, it seems not work! Below code will throw error when image format is not raw and block the VM creation. In nova/virt/images.py def fetch_to_raw() è if data.file_format != "raw": raise exception.ImageUnacceptable(image_id=image_href, reason=_("Converted to raw, but format is now %s") Not sure if your patch fixed this issue or is there any regression introduced in nova code later. Any comment from you? I will check nova code further tomorrow and sync with you. We may need a patch for nova☹ Thanks! Zhipeng From: Xie, Cindy Sent: 2019年10月30日 22:49 To: Lemus Contreras, Cristopher J ; Liu, ZhipengS ; 朱博祥 ; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade + mailing list in case anybody can help on debug the issue. From: Lemus Contreras, Cristopher J Sent: Wednesday, October 30, 2019 7:45 PM To: Liu, ZhipengS ; 朱博祥 Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Xie, Cindy ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, The results are OK for Simplex, Duplex and Standard Local Storage, all Test Cases PASSED. For Standard External Storage (2+2+2) there is a high quantity of Test Cases failing because we cannot launch instances. Here’s a sample output: http://paste.openstack.org/show/785641/ with the error that matches what is described on the launchpad. Sanity summary for this specific configuration: http://paste.openstack.org/show/785655/ Please, let us know if you need additional details. Thanks & Regards, Cristopher Lemus -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Thu Oct 31 03:11:37 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 31 Oct 2019 03:11:37 +0000 Subject: [Starlingx-discuss] About EB verification for openstack train upgrade In-Reply-To: References: <93814834B4855241994F290E959305C7530F2D84@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C7530F2DB9@SHSMSX104.ccr.corp.intel.com> Hi Boxiang, Yes, my below patch can be abandoned, just need to remove “force_raw_images: false” in stx/openstack-armada-app/stx-openstack-helm/stx-openstack-helm/manifests/manifest.yamll file since the default value is true currently. https://review.opendev.org/#/c/691802/ I will modify my patch. However, it is not related to current issue since this flag is set to true in the test. The issue is just as error log mentioned below. “ Image 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, but format is now qcow2 ” We need check this point further. Thanks! Zhipeng From: 朱博祥 Sent: 2019年10月31日 10:41 To: Liu, ZhipengS ; Xie, Cindy ; Lemus Contreras, Cristopher J ; 'starlingx-discuss at lists.starlingx.io' Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re:RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, I have succeeded to create the vm in openstack upstream(master, code is two weeks ago) now. I deployed the environment with kolla-ansible(ceph as the backend storage). In my nova.conf file, the section of libvirt is as followed: [libvirt] connection_uri = qemu+tcp://172.16.140.14/system images_type = rbd images_rbd_pool = vms images_rbd_ceph_conf = /etc/ceph/ceph.conf rbd_user = nova disk_cachemodes = network=writeback hw_disk_discard = unmap rbd_secret_uuid = 5c79d567-e142-4ab4-87f6-0fdf53060ab9 virt_type = kvm The default value of 'force_raw_images' in nova is True, so I did not set it as True again in my nova.conf file. I use the min image cirros with qcow2 format and created the vm without volume which is created by cinder. It's my image's info: (nova-compute)[root at zbx-allinone /]# qemu-img info cirros-0.4.0-x86_64-disk.img image: cirros-0.4.0-x86_64-disk.img file format: qcow2 virtual size: 44M (46137344 bytes) disk size: 12M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false So as you said, command qemu-img failed to convert the image from qcow2 to raw. BTW, is it a phenomenon that must recur now in STX? Are there other error logs in nova-compute or other nova-* services? -- Thanks, Boxiang 发件人:"Liu, ZhipengS" > 发送日期:2019-10-31 10:14:44 收件人:"Liu, ZhipengS" >,"Xie, Cindy" >,"Lemus Contreras, Cristopher J" >,"'朱博祥'" >,"'starlingx-discuss at lists.starlingx.io'" > 抄送人:"Alonso, Juan Carlos" >,"Hu, Yong" >,"Cabrales, Ada" >,"Jones, Bruce E" >,"Martinez Monroy, Elio" > 主题:RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang and all, In fetch_to_raw(), After force convert image from qcow2 to raw, the format is still not raw, then throw below error. It seems qemu-image convert image failed. Zhipeng From: Liu, ZhipengS > Sent: 2019年10月31日 9:35 To: Xie, Cindy >; Lemus Contreras, Cristopher J >; '朱博祥' >; 'starlingx-discuss at lists.starlingx.io' > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade From: Liu, ZhipengS Sent: 2019年10月30日 23:24 To: Xie, Cindy >; Lemus Contreras, Cristopher J >; 朱博祥 >; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang, It should be an issue in nova train. Error log is below: build of instance 363dddce-7af6-4701-8cea-52630b91ebcf aborted: Image 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, but format is now qcow2' You tried to fix this issue before in nova LP: https://bugs.launchpad.net/nova/+bug/1816686 In your patch: https://review.opendev.org/#/c/640271 (This patch is already in train release now) You added below commit message in the patch. “When we import image into rbd, check the format of cache images. If the format is not raw, remove it first and fetch it again. It will be raw format now.” However, it seems not work! Below code will throw error when image format is not raw and block the VM creation. In nova/virt/images.py def fetch_to_raw() ==> if data.file_format != "raw": raise exception.ImageUnacceptable(image_id=image_href, reason=_("Converted to raw, but format is now %s") Not sure if your patch fixed this issue or is there any regression introduced in nova code later. Any comment from you? I will check nova code further tomorrow and sync with you. We may need a patch for nova☹ Thanks! Zhipeng From: Xie, Cindy > Sent: 2019年10月30日 22:49 To: Lemus Contreras, Cristopher J >; Liu, ZhipengS >; 朱博祥 >; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade + mailing list in case anybody can help on debug the issue. From: Lemus Contreras, Cristopher J > Sent: Wednesday, October 30, 2019 7:45 PM To: Liu, ZhipengS >; 朱博祥 > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Xie, Cindy >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, The results are OK for Simplex, Duplex and Standard Local Storage, all Test Cases PASSED. For Standard External Storage (2+2+2) there is a high quantity of Test Cases failing because we cannot launch instances. Here’s a sample output: http://paste.openstack.org/show/785641/ with the error that matches what is described on the launchpad. Sanity summary for this specific configuration: http://paste.openstack.org/show/785655/ Please, let us know if you need additional details. Thanks & Regards, Cristopher Lemus -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhu.boxiang at 99cloud.net Thu Oct 31 03:37:33 2019 From: zhu.boxiang at 99cloud.net (=?UTF-8?B?5pyx5Y2a56Wl?=) Date: Thu, 31 Oct 2019 11:37:33 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?About_EB_verification_for_openstack?= =?utf-8?q?_train_upgrade?= In-Reply-To: <93814834B4855241994F290E959305C7530F2DB9@SHSMSX104.ccr.corp.intel.com> Message-ID: From the nova code, in nova/virt/images.py def fetch_to_raw(): -> convert_image(path_tmp, staged, fmt, 'raw') -> cmd = ('qemu-img', 'convert', '-t', cache_mode, '-O', out_format) So if the format of image is not raw, it will call qemu-img command to convert it to raw. But now we got -- Thanks, Boxiang 发件人:"Liu, ZhipengS" 发送日期:2019-10-31 11:11:37 收件人:"朱博祥" ,"Xie, Cindy" ,"Lemus Contreras, Cristopher J" ,"'starlingx-discuss at lists.starlingx.io'" 抄送人:"Alonso, Juan Carlos" ,"Hu, Yong" ,"Cabrales, Ada" ,"Jones, Bruce E" ,"Martinez Monroy, Elio" 主题:RE: Re:RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang, Yes, my below patch can be abandoned, just need to remove “force_raw_images: false” in stx/openstack-armada-app/stx-openstack-helm/stx-openstack-helm/manifests/manifest.yamll file since the default value is true currently. https://review.opendev.org/#/c/691802/ I will modify my patch. However, it is not related to current issue since this flag is set to true in the test. The issue is just as error log mentioned below. “ Image 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, but format is now qcow2 ” We need check this point further. Thanks! Zhipeng From: 朱博祥 Sent: 2019年10月31日 10:41 To: Liu, ZhipengS ; Xie, Cindy ; Lemus Contreras, Cristopher J ; 'starlingx-discuss at lists.starlingx.io' Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re:RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, I have succeeded to create the vm in openstack upstream(master, code is two weeks ago) now. I deployed the environment with kolla-ansible(ceph as the backend storage). In my nova.conf file, the section of libvirt is as followed: [libvirt] connection_uri = qemu+tcp://172.16.140.14/system images_type = rbd images_rbd_pool = vms images_rbd_ceph_conf = /etc/ceph/ceph.conf rbd_user = nova disk_cachemodes = network=writeback hw_disk_discard = unmap rbd_secret_uuid = 5c79d567-e142-4ab4-87f6-0fdf53060ab9 virt_type = kvm The default value of 'force_raw_images' in nova is True, so I did not set it as True again in my nova.conf file. I use the min image cirros with qcow2 format and created the vm without volume which is created by cinder. It's my image's info: (nova-compute)[root at zbx-allinone /]# qemu-img info cirros-0.4.0-x86_64-disk.img image: cirros-0.4.0-x86_64-disk.img file format: qcow2 virtual size: 44M (46137344 bytes) disk size: 12M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false So as you said, command qemu-img failed to convert the image from qcow2 to raw. BTW, is it a phenomenon that must recur now in STX? Are there other error logs in nova-compute or other nova-* services? -- Thanks, Boxiang 发件人:"Liu, ZhipengS" 发送日期:2019-10-31 10:14:44 收件人:"Liu, ZhipengS" ,"Xie, Cindy" ,"Lemus Contreras, Cristopher J" ,"'朱博祥'" ,"'starlingx-discuss at lists.starlingx.io'" 抄送人:"Alonso, Juan Carlos" ,"Hu, Yong" ,"Cabrales, Ada" ,"Jones, Bruce E" ,"Martinez Monroy, Elio" 主题:RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang and all, In fetch_to_raw(), After force convert image from qcow2 to raw, the format is still not raw, then throw below error. It seems qemu-image convert image failed. Zhipeng From: Liu, ZhipengS Sent: 2019年10月31日 9:35 To: Xie, Cindy ; Lemus Contreras, Cristopher J ; '朱博祥' ; 'starlingx-discuss at lists.starlingx.io' Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade From: Liu, ZhipengS Sent: 2019年10月30日 23:24 To: Xie, Cindy ; Lemus Contreras, Cristopher J ; 朱博祥 ; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang, It should be an issue in nova train. Error log is below: build of instance 363dddce-7af6-4701-8cea-52630b91ebcf aborted: Image 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, but format is now qcow2' You tried to fix this issue before in nova LP: https://bugs.launchpad.net/nova/+bug/1816686 In your patch: https://review.opendev.org/#/c/640271 (This patch is already in train release now) You added below commit message in the patch. “When we import image into rbd, check the format of cache images. If the format is not raw, remove it first and fetch it again. It will be raw format now.” However, it seems not work! Below code will throw error when image format is not raw and block the VM creation. In nova/virt/images.py def fetch_to_raw() è if data.file_format != "raw": raise exception.ImageUnacceptable(image_id=image_href, reason=_("Converted to raw, but format is now %s") Not sure if your patch fixed this issue or is there any regression introduced in nova code later. Any comment from you? I will check nova code further tomorrow and sync with you. We may need a patch for nova☹ Thanks! Zhipeng From: Xie, Cindy Sent: 2019年10月30日 22:49 To: Lemus Contreras, Cristopher J ; Liu, ZhipengS ; 朱博祥 ; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade + mailing list in case anybody can help on debug the issue. From: Lemus Contreras, Cristopher J Sent: Wednesday, October 30, 2019 7:45 PM To: Liu, ZhipengS ; 朱博祥 Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Xie, Cindy ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, The results are OK for Simplex, Duplex and Standard Local Storage, all Test Cases PASSED. For Standard External Storage (2+2+2) there is a high quantity of Test Cases failing because we cannot launch instances. Here’s a sample output: http://paste.openstack.org/show/785641/ with the error that matches what is described on the launchpad. Sanity summary for this specific configuration: http://paste.openstack.org/show/785655/ Please, let us know if you need additional details. Thanks & Regards, Cristopher Lemus -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhu.boxiang at 99cloud.net Thu Oct 31 04:06:06 2019 From: zhu.boxiang at 99cloud.net (=?UTF-8?B?5pyx5Y2a56Wl?=) Date: Thu, 31 Oct 2019 12:06:06 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?About_EB_verification_for_openstack?= =?utf-8?q?_train_upgrade?= In-Reply-To: <93814834B4855241994F290E959305C7530F2DE1@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Zhipeng and All, First of all, I found in your nova.conf, images_type = default So I think you just use qcow2 imagebackend and the root disk is on your nova-compute node not in vms pool of ceph storage. You can check that with command 'rbd ls -p vms'. So that the creating vm process will not trigger my code in this patch https://review.opendev.org/#/c/640271 From the nova code, in nova/virt/images.py def fetch_to_raw(): -> convert_image(path_tmp, staged, fmt, 'raw') -> cmd = ('qemu-img', 'convert', '-t', cache_mode, '-O', out_format) So if the format of image is not raw, it will call qemu-img command to convert it to raw. But after converting and check the format of image again, it is still not raw, so it raise exception. So we can check the nova-compute logs whether other error msgs exist or not. BTW, can you check the base image's format under '/var/lib/nova/instances/_base'? You can find the image in nova-compute container. -- Thanks, Boxiang From: "Liu, ZhipengS" Date: 2019-10-31 11:38:36 To: "Liu, ZhipengS" ,"朱博祥" ,"Xie, Cindy" ,"Lemus Contreras, Cristopher J" ,"starlingx-discuss at lists.starlingx.io" Cc: "Alonso, Juan Carlos" ,"Hu, Yong" ,"Cabrales, Ada" ,"Jones, Bruce E" ,"Martinez Monroy, Elio" Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Below is current test config. [libvirt] connection_uri = qemu+tcp://127.0.0.1/system cpu_mode = host-model disk_cachemodes = network=writeback hw_disk_discard = unmap images_rbd_ceph_conf = /etc/ceph/ceph.conf images_rbd_pool = vms images_type = default live_migration_completion_timeout = 180 live_migration_inbound_addr = 192.168.206.150 live_migration_permit_auto_converge = true mem_stats_period_seconds = 0 rbd_secret_uuid = 457eb676-33da-42ec-9a8c-9293d545c337 rbd_user = cinder remove_unused_resized_minimum_age_seconds = 86400 virt_type = qemu I also did below convert command manually, it seems OK. controller-0:~$ qemu-img convert -t none -O raw -f qcow2 cirros-0.4.0-x86_64-disk.img test1.img controller-0:~$ qemu-img convert -t writeback -O raw -f qcow2 cirros-0.4.0-x86_64-disk.img test2.img controller-0:~$ qemu-img info test1.img image: test1.img file format: raw virtual size: 44M (46137344 bytes) disk size: 13M controller-0:~$ qemu-img info test2.img image: test2.img file format: raw virtual size: 44M (46137344 bytes) disk size: 13M Need further check why in the code after convert, the image format is still qcow2. Zhipeng From: Liu, ZhipengS Sent: 2019年10月31日 11:12 To: 朱博祥 ; Xie, Cindy ; Lemus Contreras, Cristopher J ; 'starlingx-discuss at lists.starlingx.io' Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang, Yes, my below patch can be abandoned, just need to remove “force_raw_images: false” in stx/openstack-armada-app/stx-openstack-helm/stx-openstack-helm/manifests/manifest.yamll file since the default value is true currently. https://review.opendev.org/#/c/691802/ I will modify my patch. However, it is not related to current issue since this flag is set to true in the test. The issue is just as error log mentioned below. “ Image 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, but format is now qcow2 ” We need check this point further. Thanks! Zhipeng From: 朱博祥 Sent: 2019年10月31日 10:41 To: Liu, ZhipengS ; Xie, Cindy ; Lemus Contreras, Cristopher J ; 'starlingx-discuss at lists.starlingx.io' Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re:RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, I have succeeded to create the vm in openstack upstream(master, code is two weeks ago) now. I deployed the environment with kolla-ansible(ceph as the backend storage). In my nova.conf file, the section of libvirt is as followed: [libvirt] connection_uri = qemu+tcp://172.16.140.14/system images_type = rbd images_rbd_pool = vms images_rbd_ceph_conf = /etc/ceph/ceph.conf rbd_user = nova disk_cachemodes = network=writeback hw_disk_discard = unmap rbd_secret_uuid = 5c79d567-e142-4ab4-87f6-0fdf53060ab9 virt_type = kvm The default value of 'force_raw_images' in nova is True, so I did not set it as True again in my nova.conf file. I use the min image cirros with qcow2 format and created the vm without volume which is created by cinder. It's my image's info: (nova-compute)[root at zbx-allinone /]# qemu-img info cirros-0.4.0-x86_64-disk.img image: cirros-0.4.0-x86_64-disk.img file format: qcow2 virtual size: 44M (46137344 bytes) disk size: 12M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false So as you said, command qemu-img failed to convert the image from qcow2 to raw. BTW, is it a phenomenon that must recur now in STX? Are there other error logs in nova-compute or other nova-* services? -- Thanks, Boxiang 发件人:"Liu, ZhipengS" 发送日期:2019-10-31 10:14:44 收件人:"Liu, ZhipengS" ,"Xie, Cindy" ,"Lemus Contreras, Cristopher J" ,"'朱博祥'" ,"'starlingx-discuss at lists.starlingx.io'" 抄送人:"Alonso, Juan Carlos" ,"Hu, Yong" ,"Cabrales, Ada" ,"Jones, Bruce E" ,"Martinez Monroy, Elio" 主题:RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang and all, In fetch_to_raw(), After force convert image from qcow2 to raw, the format is still not raw, then throw below error. It seems qemu-image convert image failed. Zhipeng From: Liu, ZhipengS Sent: 2019年10月31日 9:35 To: Xie, Cindy ; Lemus Contreras, Cristopher J ; '朱博祥' ; 'starlingx-discuss at lists.starlingx.io' Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade From: Liu, ZhipengS Sent: 2019年10月30日 23:24 To: Xie, Cindy ; Lemus Contreras, Cristopher J ; 朱博祥 ; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang, It should be an issue in nova train. Error log is below: build of instance 363dddce-7af6-4701-8cea-52630b91ebcf aborted: Image 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, but format is now qcow2' You tried to fix this issue before in nova LP: https://bugs.launchpad.net/nova/+bug/1816686 In your patch: https://review.opendev.org/#/c/640271 (This patch is already in train release now) You added below commit message in the patch. “When we import image into rbd, check the format of cache images. If the format is not raw, remove it first and fetch it again. It will be raw format now.” However, it seems not work! Below code will throw error when image format is not raw and block the VM creation. In nova/virt/images.py def fetch_to_raw() è if data.file_format != "raw": raise exception.ImageUnacceptable(image_id=image_href, reason=_("Converted to raw, but format is now %s") Not sure if your patch fixed this issue or is there any regression introduced in nova code later. Any comment from you? I will check nova code further tomorrow and sync with you. We may need a patch for nova☹ Thanks! Zhipeng From: Xie, Cindy Sent: 2019年10月30日 22:49 To: Lemus Contreras, Cristopher J ; Liu, ZhipengS ; 朱博祥 ; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade + mailing list in case anybody can help on debug the issue. From: Lemus Contreras, Cristopher J Sent: Wednesday, October 30, 2019 7:45 PM To: Liu, ZhipengS ; 朱博祥 Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Xie, Cindy ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, The results are OK for Simplex, Duplex and Standard Local Storage, all Test Cases PASSED. For Standard External Storage (2+2+2) there is a high quantity of Test Cases failing because we cannot launch instances. Here’s a sample output: http://paste.openstack.org/show/785641/ with the error that matches what is described on the launchpad. Sanity summary for this specific configuration: http://paste.openstack.org/show/785655/ Please, let us know if you need additional details. Thanks & Regards, Cristopher Lemus -------------- next part -------------- An HTML attachment was scrubbed... URL: From qianjiang at baicells.com Thu Oct 31 06:41:41 2019 From: qianjiang at baicells.com (=?UTF-8?B?6ZKx5rGf?=) Date: Thu, 31 Oct 2019 14:41:41 +0800 Subject: [Starlingx-discuss] =?utf-8?q?openstack_network_creation_failure?= =?utf-8?q?=3A_Flat_provider_networks_are_disabled?= Message-ID: Hi, the community After installation of "Virtual All-in-one Simplex Installation R2.0", everything goes well except, controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. Could anyone help to point out what's the issue, and how to fix it? Best Regard -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Thu Oct 31 07:19:48 2019 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 31 Oct 2019 07:19:48 +0000 Subject: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled In-Reply-To: References: Message-ID: Hi QianJiang: The default datanetwork in guide is vlan, you should change it to flat before openstack network create. system datanetwork-add ${PHYSNET0} flat Thanks. BR Austin Sun. From: 钱江 Sent: Thursday, October 31, 2019 2:42 PM To: starlingx-discuss Subject: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, the community After installation of "Virtual All-in-one Simplex Installation R2.0", everything goes well except, controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. Could anyone help to point out what's the issue, and how to fix it? Best Regard -------------- next part -------------- An HTML attachment was scrubbed... URL: From saichandu.behara at calsoftinc.com Thu Oct 31 07:41:58 2019 From: saichandu.behara at calsoftinc.com (Saichandu Behara) Date: Thu, 31 Oct 2019 13:11:58 +0530 Subject: [Starlingx-discuss] Calsoft's Contribution- StarlingX All-in-one EdgeX Deployment In-Reply-To: <51e0246e-c865-30e1-7679-1cd9f83abdfc@intel.com> References: <51e0246e-c865-30e1-7679-1cd9f83abdfc@intel.com> Message-ID: Hi Yong, We deployed StarlingX all-in-one simplex EdgeX R2.0 Thanks & Regards Sai Chandu Behara On 30-10-2019 19:50, Yong Hu wrote: > Hi Sai, > What version of EdgeX did you deployed in StarlingX/K8S? > > I am thinking to make an Armada/helm "application" like "stx-edgex", > which hopefully will make life easier. > > regards, > Yong > > On 2019/10/14 7:15 PM, Saichandu Behara wrote: >> Hello All, >> >> The deployment of EdgeX in StarlingX all-in-one Simplex is done >> successfully. But we faced some challenges during whole process. >> Thus, to ease the process for a newbie, we have created ready-to-use >> qcow2 images. One can simply use this image to deploy the VM >> /(containing StarlingX with //K8//S and EdgeX//)/. Below are the >> links for StarlingX_all-in-one_Edgex setup Document and Image link. >> >> Setup Document: >> https://drive.google.com/open?id=1j0IBwKiwwD1Vju9_QltFo1oItMIa41x3 >> >> Image Link: >> https://drive.google.com/open?id=1ntQSILp4rg-L_CMQPLCPsvtYdAmQFHFp >> >> This is our very first step as contribution to this community and we >> would like to add more in future. >> >> Please let us know where can we upload these images and documents. >> >> -- >> Thanks & Regards >> Sai Chandu Behara >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > -- Thanks & Regards Sai Chandu Behara From qianjiang at baicells.com Thu Oct 31 08:11:32 2019 From: qianjiang at baicells.com (=?UTF-8?B?6ZKx5rGf?=) Date: Thu, 31 Oct 2019 16:11:32 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIG9wZW5zdGFjayBuZXR3?= =?utf-8?q?ork_creation_failure=3A_Flat_provider_networks_are_disabled?= In-Reply-To: References: , Message-ID: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> Hi, Austin Thanks for your warmhearted. Follow your suggestion, but I still get the same issue. [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 flat +--------------+--------------------------------------+ | Property | Value | +--------------+--------------------------------------+ | id | 3 | | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | | name | enp2s1 | | network_type | flat | | mtu | 1500 | | description | None | +--------------+--------------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list +--------------------------------------+----------+--------------+------+ | uuid | name | network_type | mtu | +--------------------------------------+----------+--------------+------+ | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | +--------------------------------------+----------+--------------+------+ controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. When I tried type vlan as following, it directed different issue. controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 15:23 收件人:钱江 ; starlingx-discuss 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi QianJiang: The default datanetwork in guide is vlan, you should change it to flat before openstack network create. system datanetwork-add ${PHYSNET0} flat Thanks. BR Austin Sun. From: 钱江 Sent: Thursday, October 31, 2019 2:42 PM To: starlingx-discuss Subject: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, the community After installation of "Virtual All-in-one Simplex Installation R2.0", everything goes well except, controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. Could anyone help to point out what's the issue, and how to fix it? Best Regard -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Thu Oct 31 08:41:57 2019 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 31 Oct 2019 08:41:57 +0000 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIG9wZW5zdGFjayBuZXR3?= =?utf-8?q?ork_creation_failure=3A_Flat_provider_networks_are_disabled?= In-Reply-To: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> References: , <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> Message-ID: Could you double check ? grep -r type_drivers /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml ? it comes out like ‘type_drivers: flat,vlan,vxlan’, if not , you have to use helm command to override to include flat network. Thanks. BR Austin Sun. From: 钱江 Sent: Thursday, October 31, 2019 4:12 PM To: Sun, Austin ; starlingx-discuss Subject: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, Austin Thanks for your warmhearted. Follow your suggestion, but I still get the same issue. [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 flat +--------------+--------------------------------------+ | Property | Value | +--------------+--------------------------------------+ | id | 3 | | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | | name | enp2s1 | | network_type | flat | | mtu | 1500 | | description | None | +--------------+--------------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list +--------------------------------------+----------+--------------+------+ | uuid | name | network_type | mtu | +--------------------------------------+----------+--------------+------+ | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | +--------------------------------------+----------+--------------+------+ controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. When I tried type vlan as following, it directed different issue. controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. ------------------------------------------------------------------ 发件人:Sun, Austin > 发送时间:2019年10月31日(星期四) 15:23 收件人:钱江 >; starlingx-discuss > 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi QianJiang: The default datanetwork in guide is vlan, you should change it to flat before openstack network create. system datanetwork-add ${PHYSNET0} flat Thanks. BR Austin Sun. From: 钱江 > Sent: Thursday, October 31, 2019 2:42 PM To: starlingx-discuss > Subject: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, the community After installation of "Virtual All-in-one Simplex Installation R2.0", everything goes well except, controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. Could anyone help to point out what's the issue, and how to fix it? Best Regard -------------- next part -------------- An HTML attachment was scrubbed... URL: From qianjiang at baicells.com Thu Oct 31 09:25:26 2019 From: qianjiang at baicells.com (=?UTF-8?B?6ZKx5rGf?=) Date: Thu, 31 Oct 2019 17:25:26 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77ya5Zue5aSN77yaIG9wZW5z?= =?utf-8?q?tack_network_creation_failure=3A_Flat_provider_networks_are_dis?= =?utf-8?q?abled?= In-Reply-To: References: , <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com>, Message-ID: <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> Hi, Austin I checked, the type_drivers field has no problem. Do you have more ideas? controller-0:~$ grep type_drivers -r /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml type_drivers: flat,vlan,vxlan Best Regard ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 16:42 收件人:钱江 ; starlingx-discuss 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Could you double check ? grep -r type_drivers /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml ? it comes out like ‘type_drivers: flat,vlan,vxlan’, if not , you have to use helm command to override to include flat network. Thanks. BR Austin Sun. From: 钱江 Sent: Thursday, October 31, 2019 4:12 PM To: Sun, Austin ; starlingx-discuss Subject: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, Austin Thanks for your warmhearted. Follow your suggestion, but I still get the same issue. [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 flat +--------------+--------------------------------------+ | Property | Value | +--------------+--------------------------------------+ | id | 3 | | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | | name | enp2s1 | | network_type | flat | | mtu | 1500 | | description | None | +--------------+--------------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list +--------------------------------------+----------+--------------+------+ | uuid | name | network_type | mtu | +--------------------------------------+----------+--------------+------+ | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | +--------------------------------------+----------+--------------+------+ controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. When I tried type vlan as following, it directed different issue. controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 15:23 收件人:钱江 ; starlingx-discuss 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi QianJiang: The default datanetwork in guide is vlan, you should change it to flat before openstack network create. system datanetwork-add ${PHYSNET0} flat Thanks. BR Austin Sun. From:钱江 Sent: Thursday, October 31, 2019 2:42 PM To: starlingx-discuss Subject: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, the community After installation of "Virtual All-in-one Simplex Installation R2.0", everything goes well except, controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. Could anyone help to point out what's the issue, and how to fix it? Best Regard -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Thu Oct 31 09:30:35 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 31 Oct 2019 09:30:35 +0000 Subject: [Starlingx-discuss] About EB verification for openstack train upgrade In-Reply-To: <93814834B4855241994F290E959305C7530F2D84@SHSMSX104.ccr.corp.intel.com> References: <3B594C2B-E02A-4844-A3AA-0649C2885989@intel.com> <93814834B4855241994F290E959305C7530F1A5F@SHSMSX104.ccr.corp.intel.com> <45705CE3-2F92-43BB-9ADF-A5B17861DC71@intel.com> <2FD5DDB5A04D264C80D42CA35194914F360AB833@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F1C97@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2D55@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2D84@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C7530F2F73@SHSMSX104.ccr.corp.intel.com> Hi Boxiang and all, For remote storage configuration, we have overridden below configurations in helm/nova.py. if remote_storage: default_config.update({'force_raw_images': True}) libvirt_config.update({'images_type': 'rbd', 'images_rbd_pool': rbd_pool, 'images_rbd_ceph_conf': rbd_ceph_conf}) else: libvirt_config.update({'images_type': 'default'}) Next step: The only issue we need to figure out is why image format is still qcow2 after image format convert by qemu-img in nova code. I tried to reproduce it in my virtualized multi-node environment, but no issue found, VM created normally. (I copied yellow code block to else branch) In /var/lib/nova/instances/_base/ folder, I can see one qcow2 image and one raw image which should be converted by nova. [root at compute-1 _base]# ls 3cb926303b665709318d2c099722b914025023b4 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee [root at compute-1 _base]# qemu-img info 3cb926303b665709318d2c099722b914025023b4 image: 3cb926303b665709318d2c099722b914025023b4 file format: qcow2 virtual size: 44M (46137344 bytes) disk size: 12M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false [root at compute-1 _base]# qemu-img info 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee image: 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee file format: raw virtual size: 44M (46137344 bytes) disk size: 13M Any comment? Thanks! zhipeng From: Liu, ZhipengS Sent: 2019年10月31日 10:15 To: Liu, ZhipengS ; Xie, Cindy ; Lemus Contreras, Cristopher J ; '朱博祥' ; 'starlingx-discuss at lists.starlingx.io' Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang and all, In fetch_to_raw(), After force convert image from qcow2 to raw, the format is still not raw, then throw below error. It seems qemu-image convert image failed. Zhipeng From: Liu, ZhipengS > Sent: 2019年10月31日 9:35 To: Xie, Cindy >; Lemus Contreras, Cristopher J >; '朱博祥' >; 'starlingx-discuss at lists.starlingx.io' > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade From: Liu, ZhipengS Sent: 2019年10月30日 23:24 To: Xie, Cindy >; Lemus Contreras, Cristopher J >; 朱博祥 >; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang, It should be an issue in nova train. Error log is below: build of instance 363dddce-7af6-4701-8cea-52630b91ebcf aborted: Image 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, but format is now qcow2' You tried to fix this issue before in nova LP: https://bugs.launchpad.net/nova/+bug/1816686 In your patch: https://review.opendev.org/#/c/640271 (This patch is already in train release now) You added below commit message in the patch. “When we import image into rbd, check the format of cache images. If the format is not raw, remove it first and fetch it again. It will be raw format now.” However, it seems not work! Below code will throw error when image format is not raw and block the VM creation. In nova/virt/images.py def fetch_to_raw() ==> if data.file_format != "raw": raise exception.ImageUnacceptable(image_id=image_href, reason=_("Converted to raw, but format is now %s") Not sure if your patch fixed this issue or is there any regression introduced in nova code later. Any comment from you? I will check nova code further tomorrow and sync with you. We may need a patch for nova☹ Thanks! Zhipeng From: Xie, Cindy > Sent: 2019年10月30日 22:49 To: Lemus Contreras, Cristopher J >; Liu, ZhipengS >; 朱博祥 >; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade + mailing list in case anybody can help on debug the issue. From: Lemus Contreras, Cristopher J > Sent: Wednesday, October 30, 2019 7:45 PM To: Liu, ZhipengS >; 朱博祥 > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Xie, Cindy >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, The results are OK for Simplex, Duplex and Standard Local Storage, all Test Cases PASSED. For Standard External Storage (2+2+2) there is a high quantity of Test Cases failing because we cannot launch instances. Here’s a sample output: http://paste.openstack.org/show/785641/ with the error that matches what is described on the launchpad. Sanity summary for this specific configuration: http://paste.openstack.org/show/785655/ Please, let us know if you need additional details. Thanks & Regards, Cristopher Lemus -------------- next part -------------- An HTML attachment was scrubbed... URL: From ezpeerchen at gmail.com Thu Oct 31 10:09:45 2019 From: ezpeerchen at gmail.com (Ezpeer Chen) Date: Thu, 31 Oct 2019 18:09:45 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77ya5Zue5aSN77yaIG9wZW5z?= =?utf-8?q?tack_network_creation_failure=3A_Flat_provider_networks_?= =?utf-8?q?are_disabled?= In-Reply-To: <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> Message-ID: Dear , Do you do the interface-datanetwork-assign ? #system interface-datanetwork-assign controller-0 Reference Doc: https://wiki.openstack.org/wiki/StarlingX/Networking Thanks. BR 钱江 於 2019年10月31日 週四 下午5:28寫道: > Hi, Austin > > I checked, the type_drivers field has no problem. Do you have more > ideas? > > controller-0:~$ grep type_drivers -r > /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml > > type_drivers: flat,vlan,vxlan > > Best Regard > > ------------------------------------------------------------------ > 发件人:Sun, Austin > 发送时间:2019年10月31日(星期四) 16:42 > 收件人:钱江 ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > Could you double check ? > > grep -r type_drivers > /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml > ? > > > > it comes out like ‘type_drivers: flat,vlan,vxlan’, > > if not , you have to use helm command to override to include flat network. > > > > Thanks. > > BR > Austin Sun. > > > > *From:* 钱江 > *Sent:* Thursday, October 31, 2019 4:12 PM > *To:* Sun, Austin ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > *Subject:* 回复:[Starlingx-discuss] openstack network creation failure: > Flat provider networks are disabled > > > > Hi, Austin > > > > Thanks for your warmhearted. > > Follow your suggestion, but I still get the same issue. > > > > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 > flat > +--------------+--------------------------------------+ > | Property | Value | > +--------------+--------------------------------------+ > | id | 3 | > | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | > | name | enp2s1 | > | network_type | flat | > | mtu | 1500 | > | description | None | > +--------------+--------------------------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list > +--------------------------------------+----------+--------------+------+ > | uuid | name | network_type | mtu | > +--------------------------------------+----------+--------------+------+ > | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | > | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | > | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | > +--------------------------------------+----------+--------------+------+ > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type flat provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: Flat provider networks are disabled. > > > > When I tried type vlan as following, it directed different issue. > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type vlan provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: physical_network 'provider' unknown for VLAN provider network. > > > > ------------------------------------------------------------------ > > 发件人:Sun, Austin > > 发送时间:2019年10月31日(星期四) 15:23 > > 收件人:钱江 ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > > 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > Hi QianJiang: > > The default datanetwork in guide is vlan, you should change it to flat > before openstack network create. > > > > system datanetwork-add ${PHYSNET0} flat > > > > Thanks. > > BR > Austin Sun. > > From:钱江 > *Sent:* Thursday, October 31, 2019 2:42 PM > *To:* starlingx-discuss > *Subject:* [Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > > > Hi, the community > > > > After installation of "Virtual All-in-one Simplex Installation R2.0 > ", > everything goes well except, > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type flat provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: Flat provider networks are disabled. > > > > Could anyone help to point out what's the issue, and how to fix it? > > > > Best Regard > > > > > > > _______________________________________________ > 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 qianjiang at baicells.com Thu Oct 31 11:23:32 2019 From: qianjiang at baicells.com (=?UTF-8?B?6ZKx5rGf?=) Date: Thu, 31 Oct 2019 19:23:32 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIOWbnuWkje+8muWbng==?= =?utf-8?q?=E5=A4=8D=EF=BC=9A_openstack_network_creation_failure=3A_Flat_p?= =?utf-8?q?rovider_networks_are_disabled?= In-Reply-To: References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com>, Message-ID: Hi, Ezpeer I checked and yes, [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list controller-0 +--------------+--------------------------------------+--------+--------------+ | hostname | uuid | ifname | network_name | +--------------+--------------------------------------+--------+--------------+ | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | oam | | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | mgmt | | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | cluster-host | +--------------+--------------------------------------+--------+--------------+ Best Regard ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年10月31日(星期四) 18:12 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear , Do you do the interface-datanetwork-assign ? #system interface-datanetwork-assign controller-0 Reference Doc: https://wiki.openstack.org/wiki/StarlingX/Networking Thanks. BR 钱江 於 2019年10月31日 週四 下午5:28寫道: Hi, Austin I checked, the type_drivers field has no problem. Do you have more ideas? controller-0:~$ grep type_drivers -r /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml type_drivers: flat,vlan,vxlan Best Regard ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 16:42 收件人:钱江 ; starlingx-discuss 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Could you double check ? grep -r type_drivers /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml ? it comes out like ‘type_drivers: flat,vlan,vxlan’, if not , you have to use helm command to override to include flat network. Thanks. BR Austin Sun. From: 钱江 Sent: Thursday, October 31, 2019 4:12 PM To: Sun, Austin ; starlingx-discuss Subject: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, Austin Thanks for your warmhearted. Follow your suggestion, but I still get the same issue. [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 flat +--------------+--------------------------------------+ | Property | Value | +--------------+--------------------------------------+ | id | 3 | | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | | name | enp2s1 | | network_type | flat | | mtu | 1500 | | description | None | +--------------+--------------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list +--------------------------------------+----------+--------------+------+ | uuid | name | network_type | mtu | +--------------------------------------+----------+--------------+------+ | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | +--------------------------------------+----------+--------------+------+ controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. When I tried type vlan as following, it directed different issue. controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 15:23 收件人:钱江 ; starlingx-discuss 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi QianJiang: The default datanetwork in guide is vlan, you should change it to flat before openstack network create. system datanetwork-add ${PHYSNET0} flat Thanks. BR Austin Sun. From:钱江 Sent: Thursday, October 31, 2019 2:42 PM To: starlingx-discuss Subject: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, the community After installation of "Virtual All-in-one Simplex Installation R2.0", everything goes well except, controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. Could anyone help to point out what's the issue, and how to fix it? Best Regard _______________________________________________ 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 saichandu.behara at calsoftinc.com Thu Oct 31 12:33:23 2019 From: saichandu.behara at calsoftinc.com (Saichandu Behara) Date: Thu, 31 Oct 2019 18:03:23 +0530 Subject: [Starlingx-discuss] Calsoft's Contribution- StarlingX All-in-one EdgeX Deployment In-Reply-To: <9A85D2917C58154C960D95352B22818BDFC009B8@fmsmsx123.amr.corp.intel.com> References: <51e0246e-c865-30e1-7679-1cd9f83abdfc@intel.com> <9A85D2917C58154C960D95352B22818BDFC009B8@fmsmsx123.amr.corp.intel.com> Message-ID: <1b4265f4-ca9a-a67c-3c9b-c8c3ae54cc42@calsoftinc.com> Hi Brucej, I have prepared the Document for "How to create Images". Please check the below G-Drive link. G-Drive Link: https://drive.google.com/open?id=1c2WzC3E_FnoJMfFwADFj1FWOn4Fx8jvW Thanks & Regards Sai Chandu Behara On 31-10-2019 01:55, Jones, Bruce E wrote: > Hi Sai. In the Docs team meeting today we talked about this. Kris (the Docs PL) has a review up to start the process of getting your document converted to our format. See https://review.opendev.org/#/c/692202/ for the first draft. Please feel free to join in the review. > > But we'd like to ask you for a follow on document. Can you please provide some material for the "how to create this image" part of the process? Going forward we'll want to re-create this image for new StarlingX releases and if you've figured out a good way to do that, we'd love to know about it. > > Thank you! > > brucej > > -----Original Message----- > From: Yong Hu [mailto:yong.hu at intel.com] > Sent: Wednesday, October 30, 2019 7:20 AM > To: Saichandu Behara ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Calsoft's Contribution- StarlingX All-in-one EdgeX Deployment > > Hi Sai, > What version of EdgeX did you deployed in StarlingX/K8S? > > I am thinking to make an Armada/helm "application" like "stx-edgex", which hopefully will make life easier. > > regards, > Yong > > On 2019/10/14 7:15 PM, Saichandu Behara wrote: >> Hello All, >> >> The deployment of EdgeX in StarlingX all-in-one Simplex is done >> successfully. But we faced some challenges during whole process. Thus, >> to ease the process for a newbie, we have created ready-to-use qcow2 >> images. One can simply use this image to deploy the VM /(containing >> StarlingX with //K8//S and EdgeX//)/. Below are the links for >> StarlingX_all-in-one_Edgex setup Document and Image link. >> >> Setup Document: >> https://drive.google.com/open?id=1j0IBwKiwwD1Vju9_QltFo1oItMIa41x3 >> >> Image Link: >> https://drive.google.com/open?id=1ntQSILp4rg-L_CMQPLCPsvtYdAmQFHFp >> >> This is our very first step as contribution to this community and we >> would like to add more in future. >> >> Please let us know where can we upload these images and documents. >> >> -- >> Thanks & Regards >> Sai Chandu Behara >> >> >> _______________________________________________ >> 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 -- Thanks & Regards Sai Chandu Behara From Ghada.Khalil at windriver.com Thu Oct 31 15:10:03 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 31 Oct 2019 15:10:03 +0000 Subject: [Starlingx-discuss] Weekly StarlingX Release meeting Message-ID: <151EE31B9FCCA54397A757BC674650F0C15E4AD3@ALA-MBD.corp.ad.wrs.com> ** For today's meeting, I can only be there for 30mins. Weekly meeting on Thursday 11AM PT / 1900 UTC Zoom Link: https://zoom.us/j/342730236 Meeting agenda/minutes: https://etherpad.openstack.org/p/stx-releases -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1809 bytes Desc: not available URL: From Barton.Wensley at windriver.com Thu Oct 31 17:55:23 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Thu, 31 Oct 2019 17:55:23 +0000 Subject: [Starlingx-discuss] openstack-distro meeting 10 29th 2019 minutes In-Reply-To: <9A85D2917C58154C960D95352B22818BDFBFFA7D@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BDFBFFA7D@fmsmsx123.amr.corp.intel.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1B9B49D@ALA-MBD.corp.ad.wrs.com> One thing to be aware of is that OpenStack upgrades often impact the VIM, which uses the Nova and Neutron REST APIs. Once the basic testing is passing for Train, someone needs to run the VIM's automated testing, which is described here: https://wiki.openstack.org/wiki/StarlingX/NFV/VIM_Automated_Testing That will help uncover any issues caused by changes to the OpenStack REST APIs that the VIM relies on. You should also be monitory /var/log/nfv-vim.log during your Train testing to look for errors related to communication with the OpenStack REST APIs. Bart From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: October 29, 2019 9:16 AM To: starlingx Subject: [Starlingx-discuss] openstack-distro meeting 10 29th 2019 minutes 10/29/2019 meeting * Welcome to our new PL! * Next week's meeting time is 5AM in the US west coast, Bruce unlikely to attend. Move it back one hour? Issue to be discussed at the community call this week. * Yong suggests moving this to bi-weekly, no disagreement. * Train upgrade * EB testing in progress (JC) * Sanity on Standard with External Storage failed - logs available at http://10.219.115.222/ISOS/ALL_NODES_20191025.153624.tar * Patch needed? https://review.opendev.org/#/c/661512/ Yes, we believe that this patch should be un-reverted and applied again. * It seems to be the root cause of the current failure. New EB (308) already generated and testing to begin asap. * More patches to be reviewed: * https://review.opendev.org/687200 (project: stx-manifest) upgrade StarlingX dashboard with stable/train. Not needed! * https://review.opendev.org/687203 (project: stx-gui) update stx local_settings for horizon train upgrade. MERGED * https://review.opendev.org/687204 (project: stx-upstream) update upstream project for horizon train upgrade. Not needed! * Governance update in progress, thank you Ya! * https://review.opendev.org/690615 - please don't merge topics when merging reviews. Back up to the previous patchset please. * Testing is in progress, 16 pass and 23 remain. Testing on all in one duplex bare metal config. Testing to complete EO next week. * Yong to review the openstack related launchpads to help drive release 3.0 bug fixing. -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Thu Oct 31 18:33:36 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 31 Oct 2019 18:33:36 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191031 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-October-31 (link) Status: RED =========================================== 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 64 TCs ] FAIL: [1 TCs] BLOCKED: [59 TCs] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 60 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 61 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 59 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 60 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] FAIL: [ 1 TCs ] BLOCKED: [ 61 TCs ] --------------------------------------------------------------------------- During setup controllers remain in Degraded status - postgres standalone https://bugs.launchpad.net/starlingx/+bug/1850836 Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Thu Oct 31 18:37:06 2019 From: cristopher.j.lemus.contreras at intel.com (Lemus Contreras, Cristopher J) Date: Thu, 31 Oct 2019 18:37:06 +0000 Subject: [Starlingx-discuss] Bug for Red Sanity - Build 20191030T013000Z Message-ID: <618BBED7-7220-45D3-B6C9-A9FB542255A5@intel.com> Hello, Just to let you know that the sanity execution for today failed during the setup stage on Duplex, Standard and Standard with external storage, on both, virtual and baremetal environments. This bug was created to track down the failure: https://bugs.launchpad.net/starlingx/+bug/1850836 Sanity report will be sent on a sepparate email. Thanks & Regards, Cristopher Lemus -------------- next part -------------- An HTML attachment was scrubbed... URL: From Angie.Wang at windriver.com Thu Oct 31 20:37:05 2019 From: Angie.Wang at windriver.com (Wang, Jing (Angie)) Date: Thu, 31 Oct 2019 20:37:05 +0000 Subject: [Starlingx-discuss] [docs]Refactor Ansible paramaeter "is_secure_registry" Message-ID: Hi All, I have a commit up to review https://review.opendev.org/#/c/692435/1 that renames the Ansible parameter "is_secure_registry" to "secure" and also moves it under "docker_registries:" section. This affects anyone with a setup that specifies alternative insecure docker registries that using "is_secure_registry" key as they will need to change their localhost.yml files From docker_registries: defaults: url: xxx is_secure_registry: False To docker_registires: defaults: url: xxx secure: False Thanks, -Angie -------------- next part -------------- An HTML attachment was scrubbed... URL: From lilong-neu at neusoft.com Wed Oct 30 02:50:19 2019 From: lilong-neu at neusoft.com (lilong-neu) Date: Wed, 30 Oct 2019 10:50:19 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIOOAkFN0YXJsaW5nWA==?= =?utf-8?q?=E3=80=91Regarding_external_networking_issue?= In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F360A837C@SHSMSX104.ccr.corp.intel.com> References: <005401d58b1a$7be6c6f0$73b454d0$@neusoft.com> <3950a7e0-ed9a-498d-848a-08a8f2991bcc.qianjiang@baicells.com> <2FD5DDB5A04D264C80D42CA35194914F360A837C@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Qianjiang We have create the external subnet and Router. the external subnet is ext_net. the Router is configured as below the networking topology is as below the CMD "ip netns list" is as below the external networking is 192.168.3.0/24, gateway is 192.168.3.3. it is our real networking for access internet. from 172.16.100.188(cirros-vm1) ping external subnet ext_net:192.168.3.137 OK, from 172.16.100.188(cirros-vm1) ping 172.16.101.201 ((cirros-vm3)) is OK. from 172.16.100.188(cirros-vm1) ping 10.10.10.3 (controller-0) is not OK. from 172.16.100.188(cirros-vm1) ping 192.168.3.106 is not OK. from 172.16.100.188(cirros-vm1) ping 8.8.8.8 is not OK. from 10.10.10.3 (controller-0) ping 8.8.8.8 is OK. from 10.10.10.3 (controller-0) ping 192.168.3.106 is OK. But we can't connect external networking yet from cirros instance, we will refer to />>>>> / /There are some check point :/ //// /Which NIC ext-net is connected ? / // /Which bridge this NIC is connected to on host ? / // /Does this bridge config ip address (should be 192.168.3.1)?/ // /And have you config any security group to enable icmp ? / // Thanks. BR Austin Sun. />>>>/ we will share our progress if any result. Thanks&Best Regards Long On 2019/10/29 下午9:26, Xie, Cindy wrote: > > Thanks Qian Jiang, > > @付勇 , not sure if this addressed your > question or not, please let us know if any additional help needed. > > Thx. - cindy > > *From:*钱江 > *Sent:* Monday, October 28, 2019 7:14 PM > *To:* 付勇; starlingx-discuss > > *Cc:* zhaos ; lilong-neu ; > Xie, Cindy ; Lin, Shuicheng > ; Sun, Austin ; > 张志国 > *Subject:* 回复:[Starlingx-discuss] 【StarlingX】Regarding external > networking issue > >      Hi, Fuyong > >          I wish you would allow me to write you even I am not from the > StarlingX team :-) > >          From your description of your environment, I guess, > >          . cirros-vm1 (IP: 172.16.100.188) is build over management > network (10.10.10.0/24) > > The cirros-vm1 should have its own router (the gateway should be > 172.16.100.1), and this Gateway (172.16.100.1) should be routed > through an external network. > > Then where is your external network? > > You should check your openstack routers, you may find it from "ip > netns list", the router should be implemented using a network > namespace, just check them. > >      Hope it help > >      Best Regard > > ------------------------------------------------------------------ > > 发件人:付勇> > > 发送时间:2019年10月25日(星期五) 17:58 > > 收件人:starlingx-discuss > > > 抄 送:zhaos >; > lilong-neu >; cindy.xie >; shuicheng.lin > >; > austin.sun >; > 张志国> > > 主 题:[Starlingx-discuss] 【StarlingX】Regarding external networking > issue > > *Hi StarlingX team* > > we have deploy virtual All-in-one simplex machine and have a > question to ask for help. > > *1. problem:* > > we met a problem with how to connect the external networking in > cirros or centos instance. > > *2. current status* > > controller-0 IP: 10.10.10.3 > > cirros-vm1 IP: 172.16.100.188, > > from 172.16.100.188(cirros-vm1) ping external subnet > > ext_net:10.10.10.190 OK, > > from 172.16.100.188(cirros-vm1) ping 10.10.10.3 (controller-0) is > not OK. > > from 172.16.100.188(cirros-vm1) ping 8.8.8.8 is not OK. > > from 10.10.10.3 (controller-0) ping 8.8.8.8 is OK. > > *3. configuration* > > (1) ml2_conf.ini > > in container: neutron-ovs-agent-controller-0-937646f6-dtqcn: > > /etc/neutron/plugins/ml2/ml2_conf.ini > > -----------[file:ml2_conf.ini]--[begin]---------- > > /[agent]/ > > /extensions =/ > > /[ml2]/ > > /extension_drivers = port_security/ > > /mechanism_drivers = openvswitch,sriovnicswitch,l2population/ > > /path_mtu = 0/ > > /physical_network_mtus = physnet0:1500,physnet1:1500 > tenant_network_types = vlan,vxlan type_drivers = flat,vlan,vxlan > [ml2_type_flat] flat_networks = [ml2_type_vxlan] vni_ranges = > vxlan_group = [ovs_driver] vhost_user_enabled = true > [securitygroup] firewall_driver = openvswitch/ > > -----------[file:ml2_conf.ini]--[end]---------- > > (2) the networking topology refer below pic or the attached file. > > *4.infer:* > > we need to create a bridge to connect with the external subnet > with the external networking. > > *5.requirement:* > > We want to ask how to configure to connect external networking in > cirros-vm1 or centos instance? > > we expect result as below: > > from 172.16.100.188(cirros-vm1) ping 8.8.8.8 is OK. > > Best Regards > > Wish you happy everyday! > > -------------------------------- > > Yong.Fu- Neusoft > > --------------------------------------------------------------------------------------------------- > 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. > --------------------------------------------------------------------------------------------------- > --------------------------------------------------------------------------------------------------- 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: pdehonffplebldnk.png Type: image/png Size: 38191 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fpibdcgeplkklgpa.png Type: image/png Size: 53616 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: aaoepokfidmeoolm.png Type: image/png Size: 57120 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bkfaekjhcpjlgijb.png Type: image/png Size: 12496 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 17924 bytes Desc: not available URL: From qianjiang at baicells.com Wed Oct 30 10:41:07 2019 From: qianjiang at baicells.com (=?UTF-8?B?6ZKx5rGf?=) Date: Wed, 30 Oct 2019 18:41:07 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77ya5Zue5aSN77yaIOOAkFN0?= =?utf-8?q?arlingX=E3=80=91Regarding_external_networking_issue?= In-Reply-To: References: <005401d58b1a$7be6c6f0$73b454d0$@neusoft.com> <3950a7e0-ed9a-498d-848a-08a8f2991bcc.qianjiang@baicells.com> <2FD5DDB5A04D264C80D42CA35194914F360A837C@SHSMSX104.ccr.corp.intel.com>, Message-ID: Hi, Lilong You should have two solutions, 1. Add a routine path to 172.16.100.0/24 in your external router (192.168.3.0/24), it's very clear the outgoing icmp can not find the way back. 2. Add NAT rule for 172.16.100.0/24 in host, controller-0? Best Regard ------------------------------------------------------------------ 发件人:lilong-neu 发送时间:2019年10月30日(星期三) 10:50 收件人:钱江 ; starlingx-discuss 抄 送:"Xie, Cindy" ; 付勇 ; zhaos ; "Lin, Shuicheng" ; "Sun, Austin" ; 张志国 主 题:Re: 回复:[Starlingx-discuss] 【StarlingX】Regarding external networking issue Hi Qianjiang We have create the external subnet and Router. the external subnet is ext_net. the Router is configured as below the networking topology is as below the CMD "ip netns list" is as below the external networking is 192.168.3.0/24, gateway is 192.168.3.3. it is our real networking for access internet. from 172.16.100.188(cirros-vm1) ping external subnet ext_net:192.168.3.137 OK, from 172.16.100.188(cirros-vm1) ping 172.16.101.201 ((cirros-vm3)) is OK. from 172.16.100.188(cirros-vm1) ping 10.10.10.3 (controller-0) is not OK. from 172.16.100.188(cirros-vm1) ping 192.168.3.106 is not OK. from 172.16.100.188(cirros-vm1) ping 8.8.8.8 is not OK. from 10.10.10.3 (controller-0) ping 8.8.8.8 is OK. from 10.10.10.3 (controller-0) ping 192.168.3.106 is OK. But we can't connect external networking yet from cirros instance, we will refer to >>>>> There are some check point : Which NIC ext-net is connected ? Which bridge this NIC is connected to on host ? Does this bridge config ip address (should be 192.168.3.1)? And have you config any security group to enable icmp ? Thanks. BR Austin Sun. >>>> we will share our progress if any result. Thanks&Best Regards Long On 2019/10/29 下午9:26, Xie, Cindy wrote: Thanks Qian Jiang, @付勇, not sure if this addressed your question or not, please let us know if any additional help needed. Thx. - cindy From: 钱江 Sent: Monday, October 28, 2019 7:14 PM To: 付勇 ; starlingx-discuss Cc: zhaos ; lilong-neu ; Xie, Cindy ; Lin, Shuicheng ; Sun, Austin ; 张志国 Subject: 回复:[Starlingx-discuss] 【StarlingX】Regarding external networking issue Hi, Fuyong I wish you would allow me to write you even I am not from the StarlingX team :-) From your description of your environment, I guess, . cirros-vm1 (IP: 172.16.100.188) is build over management network (10.10.10.0/24) The cirros-vm1 should have its own router (the gateway should be 172.16.100.1), and this Gateway (172.16.100.1) should be routed through an external network. Then where is your external network? You should check your openstack routers, you may find it from "ip netns list", the router should be implemented using a network namespace, just check them. Hope it help Best Regard ------------------------------------------------------------------ 发件人:付勇 发送时间:2019年10月25日(星期五) 17:58 收件人:starlingx-discuss 抄 送:zhaos ; lilong-neu ; cindy.xie ; shuicheng.lin ; austin.sun ; 张志国 主 题:[Starlingx-discuss] 【StarlingX】Regarding external networking issue Hi StarlingX team we have deploy virtual All-in-one simplex machine and have a question to ask for help. 1. problem: we met a problem with how to connect the external networking in cirros or centos instance. 2. current status controller-0 IP: 10.10.10.3 cirros-vm1 IP: 172.16.100.188, from 172.16.100.188(cirros-vm1) ping external subnet ext_net:10.10.10.190 OK, from 172.16.100.188(cirros-vm1) ping 10.10.10.3 (controller-0) is not OK. from 172.16.100.188(cirros-vm1) ping 8.8.8.8 is not OK. from 10.10.10.3 (controller-0) ping 8.8.8.8 is OK. 3. configuration (1) ml2_conf.ini in container: neutron-ovs-agent-controller-0-937646f6-dtqcn: /etc/neutron/plugins/ml2/ml2_conf.ini -----------[file:ml2_conf.ini]--[begin]---------- [agent] extensions = [ml2] extension_drivers = port_security mechanism_drivers = openvswitch,sriovnicswitch,l2population path_mtu = 0 physical_network_mtus = physnet0:1500,physnet1:1500 tenant_network_types = vlan,vxlan type_drivers = flat,vlan,vxlan [ml2_type_flat] flat_networks = [ml2_type_vxlan] vni_ranges = vxlan_group = [ovs_driver] vhost_user_enabled = true [securitygroup] firewall_driver = openvswitch -----------[file:ml2_conf.ini]--[end]---------- (2) the networking topology refer below pic or the attached file. 4.infer: we need to create a bridge to connect with the external subnet with the external networking. 5.requirement: We want to ask how to configure to connect external networking in cirros-vm1 or centos instance? we expect result as below: from 172.16.100.188(cirros-vm1) ping 8.8.8.8 is OK. Best Regards Wish you happy everyday! -------------------------------- Yong.Fu- Neusoft --------------------------------------------------------------------------------------------------- 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. --------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------- 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: pdehonffplebldnk.png Type: application/octet-stream Size: 38191 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fpibdcgeplkklgpa.png Type: application/octet-stream Size: 53616 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: aaoepokfidmeoolm.png Type: application/octet-stream Size: 57120 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bkfaekjhcpjlgijb.png Type: application/octet-stream Size: 12496 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: application/octet-stream Size: 17924 bytes Desc: not available URL: From cindy.xie at intel.com Wed Oct 30 14:48:52 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 30 Oct 2019 14:48:52 +0000 Subject: [Starlingx-discuss] About EB verification for openstack train upgrade In-Reply-To: <45705CE3-2F92-43BB-9ADF-A5B17861DC71@intel.com> References: <3B594C2B-E02A-4844-A3AA-0649C2885989@intel.com> <93814834B4855241994F290E959305C7530F1A5F@SHSMSX104.ccr.corp.intel.com> <45705CE3-2F92-43BB-9ADF-A5B17861DC71@intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F360AB833@SHSMSX104.ccr.corp.intel.com> + mailing list in case anybody can help on debug the issue. From: Lemus Contreras, Cristopher J Sent: Wednesday, October 30, 2019 7:45 PM To: Liu, ZhipengS ; 朱博祥 Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Xie, Cindy ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, The results are OK for Simplex, Duplex and Standard Local Storage, all Test Cases PASSED. For Standard External Storage (2+2+2) there is a high quantity of Test Cases failing because we cannot launch instances. Here’s a sample output: http://paste.openstack.org/show/785641/ with the error that matches what is described on the launchpad. Sanity summary for this specific configuration: http://paste.openstack.org/show/785655/ Please, let us know if you need additional details. Thanks & Regards, Cristopher Lemus From: "Liu, ZhipengS" > Date: Tuesday, October 29, 2019 at 7:23 PM To: "Lemus Contreras, Cristopher J" >, 朱博祥 > Cc: "Alonso, Juan Carlos" >, "Hu, Yong" >, "Cabrales, Ada" >, "Xie, Cindy" >, "Jones, Bruce E" >, "Martinez Monroy, Elio" > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Cristopher Lemus, Yes, exactly! Do we have a test result with my latest EB now? Thank Boxiang for clarification! I have included related change in latest EB 308. Thanks! Zhipeng From: Lemus Contreras, Cristopher J > Sent: 2019年10月30日 4:16 To: 朱博祥 >; Liu, ZhipengS > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Xie, Cindy >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi All, I think that we are facing the exact same issue that Boxiang mentions, it’s a failure for Standard external storage (2+2+2). We are not able to launch instances on Standard with External Storage, here’s a sample output: http://paste.openstack.org/show/785641/, the error matches the bug: https://bugs.launchpad.net/starlingx/+bug/1837241, which was reverted on the review that Boxiang listed. The rest of the configurations are not affected, this is specific to external storage. Thanks , Cristopher Lemus From: 朱博祥 > Date: Tuesday, October 29, 2019 at 6:15 AM To: "Liu, ZhipengS" > Cc: "Alonso, Juan Carlos" >, "Hu, Yong" >, "Cabrales, Ada" >, "Xie, Cindy" >, "Jones, Bruce E" >, "Lemus Contreras, Cristopher J" >, "Martinez Monroy, Elio" > Subject: Re:RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, Yeah, now when we use the openstack train, we should set force_raw_images to True when we use rbd as images_types in nova.conf. Otherwise the nova-compute service will fail to start. The patch[0] was meant to do that before but it caused the sanity test failure and we didn't find the root cause. [0] https://review.opendev.org/#/c/661512/ Thanks, Boxiang From: "Liu, ZhipengS" > Date: 2019-10-29 10:54:13 To: "Alonso, Juan Carlos" >,"Hu, Yong" >,"Cabrales, Ada" >,"朱博祥" > Cc: "Xie, Cindy" >,"Jones, Bruce E" >,"Lemus Contreras, Cristopher J" >,"Martinez Monroy, Elio" > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade >+baoxiang > >Hi JC, > >Thanks for your quick update! >I have found the root cause from your logs. > >{"log":"2019-10-25 15:36:06.371 235059 ERROR oslo_service.service [-] Error starting thread.: InvalidConfiguration: '[DEFAULT]/force_raw_images = False' is not allowed with '[libvirt]/images_type = rbd'. Please check the two configs and if you really do want to use rbd as images_type, set force_raw_images to True.\n","stream":"stdout","time":"2019-10-25T15:36:06.372419534Z"} > >This is related to an old LP >https://bugs.launchpad.net/starlingx/+bug/1837241 >Last time, I revert the patch provided by Boxiang due to we were using staging nova version with some of Starlingx patches. >https://review.opendev.org/#/c/661512/ >Now, we used upstream Nova, we need set force_raw_images = True again. >https://review.opendev.org/#/c/672287/ > >@Boxiang, any comment or additional change needed? >@JC, I will provide EB to you later for this issue. > >Thanks! >Zhipeng >-----Original Message----- >From: Alonso, Juan Carlos > >Sent: 2019年10月29日 5:33 >To: Liu, ZhipengS >; Hu, Yong >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E >; Lemus Contreras, Cristopher J >; Martinez Monroy, Elio > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Standard External Storage failed again, same issue. >Logs available here: http://10.219.115.222/ISOS/ALL_NODES_20191028.125727.tar >See the log attached too. > >Regards. >Juan Carlos Alonso > > >-----Original Message----- >From: Alonso, Juan Carlos >Sent: Monday, October 28, 2019 9:45 AM >To: Liu, ZhipengS >; Hu, Yong >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E >; Lemus Contreras, Cristopher J >; Martinez Monroy, Elio > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Hello, > >Deployment and sanity execution was launched last Friday. >AIO-SX, AIO-DX and Standard Local Storage deployed successfully and sanity passed. >Cristopher found that for Standard External Storage there was a failure with nova-compute pods, this is causing system application-apply stuck at 54%. >Cristopher also put the logs from collect here: http://10.219.115.222/ISOS/ALL_NODES_20191025.153624.tar > >Today only Standard External Storage was launched in BareMetal and virtual environments to assure this is a real issue. Will let you know. > >Regards. >Juan Carlos Alonso > >-----Original Message----- >From: Liu, ZhipengS > >Sent: Friday, October 25, 2019 12:22 AM >To: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E >; Lemus Contreras, Cristopher J > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Hi JC, > >Please use below EB, which based on 1024 daily build > >Thanks! >Zhipeng > >-----Original Message----- >From: Alonso, Juan Carlos > >Sent: 2019年10月25日 3:24 >To: Liu, ZhipengS >; Hu, Yong >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E >; Lemus Contreras, Cristopher J > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Hello ZhipengS, > >Based on last StarlingX release meeting, we need a new EB with the fix merged since we have to execute sanity in both standard configurations. >Please can you generate a new EB to star testing? > >Regards. >Juan Carlos Alonso > >-----Original Message----- >From: Liu, ZhipengS > >Sent: Wednesday, October 23, 2019 8:47 PM >To: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E >; Lemus Contreras, Cristopher J > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Hi JC, > >Thanks for your update! >According to your test result, it seems just some known issues caused by other changes seen in your test. >Standards setup failure should be introduced in recent code merge. >Since you passed this case when you used my first EB that based on earlier daily build. >BTW, I also passed simplex test in bare metal environment yesterday with EB03 > >@all, >Based on current status, I think we can claim sanity test is good enough and can push related patches to be merged now. > >For images, as this is just for internal verification, they are private images pushed by me. So, you could not get them in your private registry and only get them from dock.io. That's not the problem! > >Thanks! >Zhipeng > >-----Original Message----- >From: Alonso, Juan Carlos > >Sent: 2019年10月24日 3:41 >To: Liu, ZhipengS >; Hu, Yong >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E >; Lemus Contreras, Cristopher J > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Last update, on Virtual environment we have the same issue: AIO-SX and AIO-DX success. Both standards failed. > >Regards. >Juan Carlos Alonso > >-----Original Message----- >From: Alonso, Juan Carlos >Sent: Wednesday, October 23, 2019 10:44 AM >To: Liu, ZhipengS >; Hu, Yong >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E >; Lemus Contreras, Cristopher J > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Hello ZhipengS, > >On Baremetal, deployment and Sanity on Simplex and Duplex success, but failed in both standards. >Your EB is based on master branch, right? Has been an issue last days and the fix has been submitted and merged: https://review.opendev.org/#/c/689438/ >So, deployment on standards should work and if you generate a new EB should work too. > >On virtual environment, all deployments for all configs success. > >During the apply of stx-openstack, it failed due to the lack of some images, we are using a private registry and images could not found there. >Images were downloaded manually and stx-openstack re applied. >Do you have the updated list of the images you download? I CC to Cristopher who helped me with deployment and figure out this issue. > >Regards. >Juan Carlos Alonso > >-----Original Message----- >From: Liu, ZhipengS > >Sent: Wednesday, October 23, 2019 3:33 AM >To: Hu, Yong >; Alonso, Juan Carlos >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >I have tested EB 303 in our simplex bare metal environment Deployment and basic VM test pass! > >Zhipeng > >-----Original Message----- >From: Liu, ZhipengS >Sent: 2019年10月23日 10:27 >To: Hu, Yong >; Alonso, Juan Carlos >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Hi JC, > >I saw the fixed provided by Bob already in my EB 303. >Have you tested this one, any update? > >Thanks! >Zhipeng > >-----Original Message----- >From: Liu, ZhipengS >Sent: 2019年10月23日 9:30 >To: Hu, Yong >; Alonso, Juan Carlos >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Hi JC, > >I saw that sanity test of daily build also has the same issue as you have. >I will trigger a new EB with the fixed provide by Bob. >https://review.opendev.org/#/c/689643/ Ensure minimal replicas for platform-integ-apps managed apply > >Thanks! >Zhipeng > >-----Original Message----- >From: Liu, ZhipengS >Sent: 2019年10月22日 22:27 >To: Hu, Yong >; Alonso, Juan Carlos >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Yes > >But the failure place JC met is not the same as I saw. >I met one failure on applying openstack, but JC saw the failure on applying platform app, which should not be related to train upgrade. >For my failure case, it should disable nova schedule node probe as we did before, I add this fix in my new EB based on latest Daily build 1021. > >@JC, I triggered EB-303, it may be available in 2 hours, you can check the status below http://dcp-dev.intel.com/jenkins/blue/organizations/jenkins/StarlingX%2Fstx-eng-build/activity >When it is ready, you can fetch EB from here and retest in BM setup. >http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/303/outputs/ > >Thanks! >Zhipeng > >-----Original Message----- >From: Hu, Yong > >Sent: 2019年10月22日 22:07 >To: Liu, ZhipengS >; Alonso, Juan Carlos >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E > >Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade > >Thanks Zhipeng, I suppose RC means Root Cause. :-) > >On 2019/10/22 9:37 PM, Liu, ZhipengS wrote: >> Hi JC, >> >> I should find the RC, will send you a new EB in 1 hour. >> >> Thanks! >> >> Zhipeng >> >> *From:*Liu, ZhipengS > >> *Sent:* 2019年10月22日9:27 >> *To:* Alonso, Juan Carlos >; Cabrales, >> Ada > >> *Cc:* Xie, Cindy >; Hu, Yong >; >> Jones, Bruce E > >> *Subject:* RE: [Starlingx-discuss] About EB verification for openstack >> train upgrade >> >> Hi JC, >> >> Thanks for your quick update! >> >> Could you help share your logs? >> >> Anyway, I will also try it in BM environment. >> >> Thanks! >> >> Zhipeng >> >> ---------------------------------------------------------------------- >> -- >> >> *From:*Alonso, Juan Carlos >> *Sent:* Tuesday, October 22, 2019 1:13 AM >> *To:* Liu, ZhipengS; Cabrales, Ada >> *Cc:* Xie, Cindy; Hu, Yong; Jones, Bruce E >> *Subject:* RE: [Starlingx-discuss] About EB verification for openstack >> train upgrade >> >> Hello ZhipengS, >> >> A Sanity execution was launched last Friday on Virtual and BareMetal >> environment. >> >> In virtual environment there was not issues during installation, >> provisioning nor sanity. >> >> In BareMetal environment it could be installed but failed during >> provisioning in 4 configurations: >> >> ====================================================================== >> ======== >> >> Provision :: Tests for provisioning and unlocking controllers, >> computes and >> >> ====================================================================== >> ======== >> >> Provisioning Standard Storage System :: Validates provisioning of ... >> | FAIL | >> >> Maximum limit of started keywords exceeded. >> >> The issue was during system application-apply: >> >> [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 | remove-failed | operation aborted, check logs for >> detail | >> >> +---------------------+---------+-------------------------------+---------------+---------------+------------------------------------------+ >> >> Regards. >> >> Juan Carlos Alonso >> >> *From:*Liu, ZhipengS > > >> *Sent:* Sunday, October 20, 2019 8:35 PM >> *To:* Cabrales, Ada > > >> *Cc:* Xie, Cindy >>; >> Hu, Yong >>; Jones, Bruce >> E >>; Alonso, >> Juan Carlos > > >> *Subject:* RE: [Starlingx-discuss] About EB verification for openstack >> train upgrade >> >> Hi Ada, >> >> Do we have test result now? >> >> Thanks! >> >> Zhipeng >> >> *From:*Cabrales, Ada > > >> *Sent:* 2019年10月14日22:20 >> *To:* Liu, ZhipengS > > >> *Cc:* Xie, Cindy >>; >> Hu, Yong >>; Jones, Bruce >> E >>; Alonso, >> Juan Carlos > > >> *Subject:* RE: [Starlingx-discuss] About EB verification for openstack >> train upgrade >> >> Sure, let us try with this one. >> >> Thanks! >> >> Ada >> >> *From:*Liu, ZhipengS > > >> *Sent:* Sunday, October 13, 2019 6:44 AM >> *To:* Cabrales, Ada > > >> *Cc:* Xie, Cindy >>; >> Hu, Yong >>; Jones, Bruce >> E >> >> *Subject:* RE: [Starlingx-discuss] About EB verification for openstack >> train upgrade >> >> Hi Ada, >> >> Could you please use below new EB? >> >> One horizon issue was fixed, found during my duplex test. >> >> http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/294/outputs/ >> >> Thanks! >> >> Zhipeng >> >> *From:*Liu, ZhipengS > > >> *Sent:* 2019年10月11日20:43 >> *To:* Cabrales, Ada > >; Jones, Bruce E >> >> >> *Cc:* starlingx-discuss at lists.starlingx.io >> >> *Subject:* [Starlingx-discuss] About EB verification for openstack >> train upgrade >> >> Hi Ada and Bruce, >> >> So far, I have finished openstack train upgrade and >> openstack-helm/helm-infra upgrade. >> >> Story: https://storyboard.openstack.org/#!/story/2006544 >> >> Basic deployment and VM creation/remove test pass in AIO setup! >> >> @Ada , Could you help to arrange sanity >> test with below EB, thanks! >> >> http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/290/outputs/ >> >> Current status summarized as below. >> >> 1)Openstack upgrade >> >> Finished 13 services upgrade, including nova, neutron, keystone, >> cinder, glance, placement, aodh, ironic, panko, barbican, ceilometer, heat, horizon. >> >> 2)Openstack-helm/helm-infra upgrade >> >> Upgrade openstack-helm to below version. 13 patches removed >> >> commit 82c72367c85ca94270f702661c7b984899c1ae38 >> //Date: >> Sat Sep 14 06:40:03 2019 +0000 >> >> Upgrade openstack-helm-infra to below version. 1 patch removed >> >> commit c9d6676bf9a5aceb311dc31dadd07cba6a3d6392 >> //Date: >> Mon Sep 16 17:15:12 2019 +0000 >> >> 6 patches submitted for review, your comments are appreciated, thanks! >> >> https://review.opendev.org/#/c/683886/ >> >> https://review.opendev.org/#/c/683910/ >> >> https://review.opendev.org/#/c/684166/ >> >> https://review.opendev.org/#/c/687441/ >> >> https://review.opendev.org/#/c/687197/ >> >> https://review.opendev.org/#/c/688105/ >> >> Thanks! >> >> zhipeng >> > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Wed Oct 30 15:23:32 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 30 Oct 2019 15:23:32 +0000 Subject: [Starlingx-discuss] About EB verification for openstack train upgrade In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F360AB833@SHSMSX104.ccr.corp.intel.com> References: <3B594C2B-E02A-4844-A3AA-0649C2885989@intel.com> <93814834B4855241994F290E959305C7530F1A5F@SHSMSX104.ccr.corp.intel.com> <45705CE3-2F92-43BB-9ADF-A5B17861DC71@intel.com> <2FD5DDB5A04D264C80D42CA35194914F360AB833@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C7530F1C97@SHSMSX104.ccr.corp.intel.com> Hi Boxiang, It should be an issue in nova train. Error log is below: build of instance 363dddce-7af6-4701-8cea-52630b91ebcf aborted: Image 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, but format is now qcow2' You tried to fix this issue before in nova LP: https://bugs.launchpad.net/nova/+bug/1816686 In your patch: https://review.opendev.org/#/c/640271 (This patch is already in train release now) You added below commit message in the patch. “When we import image into rbd, check the format of cache images. If the format is not raw, remove it first and fetch it again. It will be raw format now.” However, it seems not work! Below code will throw error when image format is not raw and block the VM creation. In nova/virt/images.py def fetch_to_raw() ==> if data.file_format != "raw": raise exception.ImageUnacceptable(image_id=image_href, reason=_("Converted to raw, but format is now %s") Not sure if your patch fixed this issue or is there any regression introduced in nova code later. Any comment from you? I will check nova code further tomorrow and sync with you. We may need a patch for nova☹ Thanks! Zhipeng From: Xie, Cindy Sent: 2019年10月30日 22:49 To: Lemus Contreras, Cristopher J ; Liu, ZhipengS ; 朱博祥 ; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade + mailing list in case anybody can help on debug the issue. From: Lemus Contreras, Cristopher J > Sent: Wednesday, October 30, 2019 7:45 PM To: Liu, ZhipengS >; 朱博祥 > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Xie, Cindy >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, The results are OK for Simplex, Duplex and Standard Local Storage, all Test Cases PASSED. For Standard External Storage (2+2+2) there is a high quantity of Test Cases failing because we cannot launch instances. Here’s a sample output: http://paste.openstack.org/show/785641/ with the error that matches what is described on the launchpad. Sanity summary for this specific configuration: http://paste.openstack.org/show/785655/ Please, let us know if you need additional details. Thanks & Regards, Cristopher Lemus From: "Liu, ZhipengS" > Date: Tuesday, October 29, 2019 at 7:23 PM To: "Lemus Contreras, Cristopher J" >, 朱博祥 > Cc: "Alonso, Juan Carlos" >, "Hu, Yong" >, "Cabrales, Ada" >, "Xie, Cindy" >, "Jones, Bruce E" >, "Martinez Monroy, Elio" > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Cristopher Lemus, Yes, exactly! Do we have a test result with my latest EB now? Thank Boxiang for clarification! I have included related change in latest EB 308. Thanks! Zhipeng From: Lemus Contreras, Cristopher J > Sent: 2019年10月30日 4:16 To: 朱博祥 >; Liu, ZhipengS > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Xie, Cindy >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi All, I think that we are facing the exact same issue that Boxiang mentions, it’s a failure for Standard external storage (2+2+2). We are not able to launch instances on Standard with External Storage, here’s a sample output: http://paste.openstack.org/show/785641/, the error matches the bug: https://bugs.launchpad.net/starlingx/+bug/1837241, which was reverted on the review that Boxiang listed. The rest of the configurations are not affected, this is specific to external storage. Thanks , Cristopher Lemus From: 朱博祥 > Date: Tuesday, October 29, 2019 at 6:15 AM To: "Liu, ZhipengS" > Cc: "Alonso, Juan Carlos" >, "Hu, Yong" >, "Cabrales, Ada" >, "Xie, Cindy" >, "Jones, Bruce E" >, "Lemus Contreras, Cristopher J" >, "Martinez Monroy, Elio" > Subject: Re:RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, Yeah, now when we use the openstack train, we should set force_raw_images to True when we use rbd as images_types in nova.conf. Otherwise the nova-compute service will fail to start. The patch[0] was meant to do that before but it caused the sanity test failure and we didn't find the root cause. [0] https://review.opendev.org/#/c/661512/ Thanks, Boxiang From: "Liu, ZhipengS" > Date: 2019-10-29 10:54:13 To: "Alonso, Juan Carlos" >,"Hu, Yong" >,"Cabrales, Ada" >,"朱博祥" > Cc: "Xie, Cindy" >,"Jones, Bruce E" >,"Lemus Contreras, Cristopher J" >,"Martinez Monroy, Elio" > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade >+baoxiang > >Hi JC, > >Thanks for your quick update! >I have found the root cause from your logs. > >{"log":"2019-10-25 15:36:06.371 235059 ERROR oslo_service.service [-] Error starting thread.: InvalidConfiguration: '[DEFAULT]/force_raw_images = False' is not allowed with '[libvirt]/images_type = rbd'. Please check the two configs and if you really do want to use rbd as images_type, set force_raw_images to True.\n","stream":"stdout","time":"2019-10-25T15:36:06.372419534Z"} > >This is related to an old LP >https://bugs.launchpad.net/starlingx/+bug/1837241 >Last time, I revert the patch provided by Boxiang due to we were using staging nova version with some of Starlingx patches. >https://review.opendev.org/#/c/661512/ >Now, we used upstream Nova, we need set force_raw_images = True again. >https://review.opendev.org/#/c/672287/ > >@Boxiang, any comment or additional change needed? >@JC, I will provide EB to you later for this issue. > >Thanks! >Zhipeng >-----Original Message----- >From: Alonso, Juan Carlos > >Sent: 2019年10月29日 5:33 >To: Liu, ZhipengS >; Hu, Yong >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E >; Lemus Contreras, Cristopher J >; Martinez Monroy, Elio > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Standard External Storage failed again, same issue. >Logs available here: http://10.219.115.222/ISOS/ALL_NODES_20191028.125727.tar >See the log attached too. > >Regards. >Juan Carlos Alonso > > >-----Original Message----- >From: Alonso, Juan Carlos >Sent: Monday, October 28, 2019 9:45 AM >To: Liu, ZhipengS >; Hu, Yong >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E >; Lemus Contreras, Cristopher J >; Martinez Monroy, Elio > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Hello, > >Deployment and sanity execution was launched last Friday. >AIO-SX, AIO-DX and Standard Local Storage deployed successfully and sanity passed. >Cristopher found that for Standard External Storage there was a failure with nova-compute pods, this is causing system application-apply stuck at 54%. >Cristopher also put the logs from collect here: http://10.219.115.222/ISOS/ALL_NODES_20191025.153624.tar > >Today only Standard External Storage was launched in BareMetal and virtual environments to assure this is a real issue. Will let you know. > >Regards. >Juan Carlos Alonso > >-----Original Message----- >From: Liu, ZhipengS > >Sent: Friday, October 25, 2019 12:22 AM >To: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E >; Lemus Contreras, Cristopher J > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Hi JC, > >Please use below EB, which based on 1024 daily build > >Thanks! >Zhipeng > >-----Original Message----- >From: Alonso, Juan Carlos > >Sent: 2019年10月25日 3:24 >To: Liu, ZhipengS >; Hu, Yong >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E >; Lemus Contreras, Cristopher J > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Hello ZhipengS, > >Based on last StarlingX release meeting, we need a new EB with the fix merged since we have to execute sanity in both standard configurations. >Please can you generate a new EB to star testing? > >Regards. >Juan Carlos Alonso > >-----Original Message----- >From: Liu, ZhipengS > >Sent: Wednesday, October 23, 2019 8:47 PM >To: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E >; Lemus Contreras, Cristopher J > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Hi JC, > >Thanks for your update! >According to your test result, it seems just some known issues caused by other changes seen in your test. >Standards setup failure should be introduced in recent code merge. >Since you passed this case when you used my first EB that based on earlier daily build. >BTW, I also passed simplex test in bare metal environment yesterday with EB03 > >@all, >Based on current status, I think we can claim sanity test is good enough and can push related patches to be merged now. > >For images, as this is just for internal verification, they are private images pushed by me. So, you could not get them in your private registry and only get them from dock.io. That's not the problem! > >Thanks! >Zhipeng > >-----Original Message----- >From: Alonso, Juan Carlos > >Sent: 2019年10月24日 3:41 >To: Liu, ZhipengS >; Hu, Yong >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E >; Lemus Contreras, Cristopher J > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Last update, on Virtual environment we have the same issue: AIO-SX and AIO-DX success. Both standards failed. > >Regards. >Juan Carlos Alonso > >-----Original Message----- >From: Alonso, Juan Carlos >Sent: Wednesday, October 23, 2019 10:44 AM >To: Liu, ZhipengS >; Hu, Yong >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E >; Lemus Contreras, Cristopher J > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Hello ZhipengS, > >On Baremetal, deployment and Sanity on Simplex and Duplex success, but failed in both standards. >Your EB is based on master branch, right? Has been an issue last days and the fix has been submitted and merged: https://review.opendev.org/#/c/689438/ >So, deployment on standards should work and if you generate a new EB should work too. > >On virtual environment, all deployments for all configs success. > >During the apply of stx-openstack, it failed due to the lack of some images, we are using a private registry and images could not found there. >Images were downloaded manually and stx-openstack re applied. >Do you have the updated list of the images you download? I CC to Cristopher who helped me with deployment and figure out this issue. > >Regards. >Juan Carlos Alonso > >-----Original Message----- >From: Liu, ZhipengS > >Sent: Wednesday, October 23, 2019 3:33 AM >To: Hu, Yong >; Alonso, Juan Carlos >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >I have tested EB 303 in our simplex bare metal environment Deployment and basic VM test pass! > >Zhipeng > >-----Original Message----- >From: Liu, ZhipengS >Sent: 2019年10月23日 10:27 >To: Hu, Yong >; Alonso, Juan Carlos >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Hi JC, > >I saw the fixed provided by Bob already in my EB 303. >Have you tested this one, any update? > >Thanks! >Zhipeng > >-----Original Message----- >From: Liu, ZhipengS >Sent: 2019年10月23日 9:30 >To: Hu, Yong >; Alonso, Juan Carlos >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Hi JC, > >I saw that sanity test of daily build also has the same issue as you have. >I will trigger a new EB with the fixed provide by Bob. >https://review.opendev.org/#/c/689643/ Ensure minimal replicas for platform-integ-apps managed apply > >Thanks! >Zhipeng > >-----Original Message----- >From: Liu, ZhipengS >Sent: 2019年10月22日 22:27 >To: Hu, Yong >; Alonso, Juan Carlos >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E > >Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade > >Yes > >But the failure place JC met is not the same as I saw. >I met one failure on applying openstack, but JC saw the failure on applying platform app, which should not be related to train upgrade. >For my failure case, it should disable nova schedule node probe as we did before, I add this fix in my new EB based on latest Daily build 1021. > >@JC, I triggered EB-303, it may be available in 2 hours, you can check the status below http://dcp-dev.intel.com/jenkins/blue/organizations/jenkins/StarlingX%2Fstx-eng-build/activity >When it is ready, you can fetch EB from here and retest in BM setup. >http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/303/outputs/ > >Thanks! >Zhipeng > >-----Original Message----- >From: Hu, Yong > >Sent: 2019年10月22日 22:07 >To: Liu, ZhipengS >; Alonso, Juan Carlos >; Cabrales, Ada > >Cc: Xie, Cindy >; Jones, Bruce E > >Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade > >Thanks Zhipeng, I suppose RC means Root Cause. :-) > >On 2019/10/22 9:37 PM, Liu, ZhipengS wrote: >> Hi JC, >> >> I should find the RC, will send you a new EB in 1 hour. >> >> Thanks! >> >> Zhipeng >> >> *From:*Liu, ZhipengS > >> *Sent:* 2019年10月22日9:27 >> *To:* Alonso, Juan Carlos >; Cabrales, >> Ada > >> *Cc:* Xie, Cindy >; Hu, Yong >; >> Jones, Bruce E > >> *Subject:* RE: [Starlingx-discuss] About EB verification for openstack >> train upgrade >> >> Hi JC, >> >> Thanks for your quick update! >> >> Could you help share your logs? >> >> Anyway, I will also try it in BM environment. >> >> Thanks! >> >> Zhipeng >> >> ---------------------------------------------------------------------- >> -- >> >> *From:*Alonso, Juan Carlos >> *Sent:* Tuesday, October 22, 2019 1:13 AM >> *To:* Liu, ZhipengS; Cabrales, Ada >> *Cc:* Xie, Cindy; Hu, Yong; Jones, Bruce E >> *Subject:* RE: [Starlingx-discuss] About EB verification for openstack >> train upgrade >> >> Hello ZhipengS, >> >> A Sanity execution was launched last Friday on Virtual and BareMetal >> environment. >> >> In virtual environment there was not issues during installation, >> provisioning nor sanity. >> >> In BareMetal environment it could be installed but failed during >> provisioning in 4 configurations: >> >> ====================================================================== >> ======== >> >> Provision :: Tests for provisioning and unlocking controllers, >> computes and >> >> ====================================================================== >> ======== >> >> Provisioning Standard Storage System :: Validates provisioning of ... >> | FAIL | >> >> Maximum limit of started keywords exceeded. >> >> The issue was during system application-apply: >> >> [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 | remove-failed | operation aborted, check logs for >> detail | >> >> +---------------------+---------+-------------------------------+---------------+---------------+------------------------------------------+ >> >> Regards. >> >> Juan Carlos Alonso >> >> *From:*Liu, ZhipengS > > >> *Sent:* Sunday, October 20, 2019 8:35 PM >> *To:* Cabrales, Ada > > >> *Cc:* Xie, Cindy >>; >> Hu, Yong >>; Jones, Bruce >> E >>; Alonso, >> Juan Carlos > > >> *Subject:* RE: [Starlingx-discuss] About EB verification for openstack >> train upgrade >> >> Hi Ada, >> >> Do we have test result now? >> >> Thanks! >> >> Zhipeng >> >> *From:*Cabrales, Ada > > >> *Sent:* 2019年10月14日22:20 >> *To:* Liu, ZhipengS > > >> *Cc:* Xie, Cindy >>; >> Hu, Yong >>; Jones, Bruce >> E >>; Alonso, >> Juan Carlos > > >> *Subject:* RE: [Starlingx-discuss] About EB verification for openstack >> train upgrade >> >> Sure, let us try with this one. >> >> Thanks! >> >> Ada >> >> *From:*Liu, ZhipengS > > >> *Sent:* Sunday, October 13, 2019 6:44 AM >> *To:* Cabrales, Ada > > >> *Cc:* Xie, Cindy >>; >> Hu, Yong >>; Jones, Bruce >> E >> >> *Subject:* RE: [Starlingx-discuss] About EB verification for openstack >> train upgrade >> >> Hi Ada, >> >> Could you please use below new EB? >> >> One horizon issue was fixed, found during my duplex test. >> >> http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/294/outputs/ >> >> Thanks! >> >> Zhipeng >> >> *From:*Liu, ZhipengS > > >> *Sent:* 2019年10月11日20:43 >> *To:* Cabrales, Ada > >; Jones, Bruce E >> >> >> *Cc:* starlingx-discuss at lists.starlingx.io >> >> *Subject:* [Starlingx-discuss] About EB verification for openstack >> train upgrade >> >> Hi Ada and Bruce, >> >> So far, I have finished openstack train upgrade and >> openstack-helm/helm-infra upgrade. >> >> Story: https://storyboard.openstack.org/#!/story/2006544 >> >> Basic deployment and VM creation/remove test pass in AIO setup! >> >> @Ada , Could you help to arrange sanity >> test with below EB, thanks! >> >> http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/290/outputs/ >> >> Current status summarized as below. >> >> 1)Openstack upgrade >> >> Finished 13 services upgrade, including nova, neutron, keystone, >> cinder, glance, placement, aodh, ironic, panko, barbican, ceilometer, heat, horizon. >> >> 2)Openstack-helm/helm-infra upgrade >> >> Upgrade openstack-helm to below version. 13 patches removed >> >> commit 82c72367c85ca94270f702661c7b984899c1ae38 >> //Date: >> Sat Sep 14 06:40:03 2019 +0000 >> >> Upgrade openstack-helm-infra to below version. 1 patch removed >> >> commit c9d6676bf9a5aceb311dc31dadd07cba6a3d6392 >> //Date: >> Mon Sep 16 17:15:12 2019 +0000 >> >> 6 patches submitted for review, your comments are appreciated, thanks! >> >> https://review.opendev.org/#/c/683886/ >> >> https://review.opendev.org/#/c/683910/ >> >> https://review.opendev.org/#/c/684166/ >> >> https://review.opendev.org/#/c/687441/ >> >> https://review.opendev.org/#/c/687197/ >> >> https://review.opendev.org/#/c/688105/ >> >> Thanks! >> >> zhipeng >> > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Thu Oct 31 02:14:44 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 31 Oct 2019 02:14:44 +0000 Subject: [Starlingx-discuss] About EB verification for openstack train upgrade In-Reply-To: <93814834B4855241994F290E959305C7530F2D55@SHSMSX104.ccr.corp.intel.com> References: <3B594C2B-E02A-4844-A3AA-0649C2885989@intel.com> <93814834B4855241994F290E959305C7530F1A5F@SHSMSX104.ccr.corp.intel.com> <45705CE3-2F92-43BB-9ADF-A5B17861DC71@intel.com> <2FD5DDB5A04D264C80D42CA35194914F360AB833@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F1C97@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2D55@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C7530F2D84@SHSMSX104.ccr.corp.intel.com> Hi Boxiang and all, In fetch_to_raw(), After force convert image from qcow2 to raw, the format is still not raw, then throw below error. It seems qemu-image convert image failed. Zhipeng From: Liu, ZhipengS Sent: 2019年10月31日 9:35 To: Xie, Cindy ; Lemus Contreras, Cristopher J ; '朱博祥' ; 'starlingx-discuss at lists.starlingx.io' Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade From: Liu, ZhipengS Sent: 2019年10月30日 23:24 To: Xie, Cindy >; Lemus Contreras, Cristopher J >; 朱博祥 >; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang, It should be an issue in nova train. Error log is below: build of instance 363dddce-7af6-4701-8cea-52630b91ebcf aborted: Image 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, but format is now qcow2' You tried to fix this issue before in nova LP: https://bugs.launchpad.net/nova/+bug/1816686 In your patch: https://review.opendev.org/#/c/640271 (This patch is already in train release now) You added below commit message in the patch. “When we import image into rbd, check the format of cache images. If the format is not raw, remove it first and fetch it again. It will be raw format now.” However, it seems not work! Below code will throw error when image format is not raw and block the VM creation. In nova/virt/images.py def fetch_to_raw() ==> if data.file_format != "raw": raise exception.ImageUnacceptable(image_id=image_href, reason=_("Converted to raw, but format is now %s") Not sure if your patch fixed this issue or is there any regression introduced in nova code later. Any comment from you? I will check nova code further tomorrow and sync with you. We may need a patch for nova☹ Thanks! Zhipeng From: Xie, Cindy > Sent: 2019年10月30日 22:49 To: Lemus Contreras, Cristopher J >; Liu, ZhipengS >; 朱博祥 >; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade + mailing list in case anybody can help on debug the issue. From: Lemus Contreras, Cristopher J > Sent: Wednesday, October 30, 2019 7:45 PM To: Liu, ZhipengS >; 朱博祥 > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Xie, Cindy >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, The results are OK for Simplex, Duplex and Standard Local Storage, all Test Cases PASSED. For Standard External Storage (2+2+2) there is a high quantity of Test Cases failing because we cannot launch instances. Here’s a sample output: http://paste.openstack.org/show/785641/ with the error that matches what is described on the launchpad. Sanity summary for this specific configuration: http://paste.openstack.org/show/785655/ Please, let us know if you need additional details. Thanks & Regards, Cristopher Lemus -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Thu Oct 31 03:38:36 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 31 Oct 2019 03:38:36 +0000 Subject: [Starlingx-discuss] About EB verification for openstack train upgrade In-Reply-To: <93814834B4855241994F290E959305C7530F2DB9@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C7530F2D84@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2DB9@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C7530F2DE1@SHSMSX104.ccr.corp.intel.com> Below is current test config. [libvirt] connection_uri = qemu+tcp://127.0.0.1/system cpu_mode = host-model disk_cachemodes = network=writeback hw_disk_discard = unmap images_rbd_ceph_conf = /etc/ceph/ceph.conf images_rbd_pool = vms images_type = default live_migration_completion_timeout = 180 live_migration_inbound_addr = 192.168.206.150 live_migration_permit_auto_converge = true mem_stats_period_seconds = 0 rbd_secret_uuid = 457eb676-33da-42ec-9a8c-9293d545c337 rbd_user = cinder remove_unused_resized_minimum_age_seconds = 86400 virt_type = qemu I also did below convert command manually, it seems OK. controller-0:~$ qemu-img convert -t none -O raw -f qcow2 cirros-0.4.0-x86_64-disk.img test1.img controller-0:~$ qemu-img convert -t writeback -O raw -f qcow2 cirros-0.4.0-x86_64-disk.img test2.img controller-0:~$ qemu-img info test1.img image: test1.img file format: raw virtual size: 44M (46137344 bytes) disk size: 13M controller-0:~$ qemu-img info test2.img image: test2.img file format: raw virtual size: 44M (46137344 bytes) disk size: 13M Need further check why in the code after convert, the image format is still qcow2. Zhipeng From: Liu, ZhipengS Sent: 2019年10月31日 11:12 To: 朱博祥 ; Xie, Cindy ; Lemus Contreras, Cristopher J ; 'starlingx-discuss at lists.starlingx.io' Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang, Yes, my below patch can be abandoned, just need to remove “force_raw_images: false” in stx/openstack-armada-app/stx-openstack-helm/stx-openstack-helm/manifests/manifest.yamll file since the default value is true currently. https://review.opendev.org/#/c/691802/ I will modify my patch. However, it is not related to current issue since this flag is set to true in the test. The issue is just as error log mentioned below. “ Image 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, but format is now qcow2 ” We need check this point further. Thanks! Zhipeng From: 朱博祥 > Sent: 2019年10月31日 10:41 To: Liu, ZhipengS >; Xie, Cindy >; Lemus Contreras, Cristopher J >; 'starlingx-discuss at lists.starlingx.io' > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re:RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, I have succeeded to create the vm in openstack upstream(master, code is two weeks ago) now. I deployed the environment with kolla-ansible(ceph as the backend storage). In my nova.conf file, the section of libvirt is as followed: [libvirt] connection_uri = qemu+tcp://172.16.140.14/system images_type = rbd images_rbd_pool = vms images_rbd_ceph_conf = /etc/ceph/ceph.conf rbd_user = nova disk_cachemodes = network=writeback hw_disk_discard = unmap rbd_secret_uuid = 5c79d567-e142-4ab4-87f6-0fdf53060ab9 virt_type = kvm The default value of 'force_raw_images' in nova is True, so I did not set it as True again in my nova.conf file. I use the min image cirros with qcow2 format and created the vm without volume which is created by cinder. It's my image's info: (nova-compute)[root at zbx-allinone /]# qemu-img info cirros-0.4.0-x86_64-disk.img image: cirros-0.4.0-x86_64-disk.img file format: qcow2 virtual size: 44M (46137344 bytes) disk size: 12M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false So as you said, command qemu-img failed to convert the image from qcow2 to raw. BTW, is it a phenomenon that must recur now in STX? Are there other error logs in nova-compute or other nova-* services? -- Thanks, Boxiang 发件人:"Liu, ZhipengS" > 发送日期:2019-10-31 10:14:44 收件人:"Liu, ZhipengS" >,"Xie, Cindy" >,"Lemus Contreras, Cristopher J" >,"'朱博祥'" >,"'starlingx-discuss at lists.starlingx.io'" > 抄送人:"Alonso, Juan Carlos" >,"Hu, Yong" >,"Cabrales, Ada" >,"Jones, Bruce E" >,"Martinez Monroy, Elio" > 主题:RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang and all, In fetch_to_raw(), After force convert image from qcow2 to raw, the format is still not raw, then throw below error. It seems qemu-image convert image failed. Zhipeng From: Liu, ZhipengS > Sent: 2019年10月31日 9:35 To: Xie, Cindy >; Lemus Contreras, Cristopher J >; '朱博祥' >; 'starlingx-discuss at lists.starlingx.io' > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade From: Liu, ZhipengS Sent: 2019年10月30日 23:24 To: Xie, Cindy >; Lemus Contreras, Cristopher J >; 朱博祥 >; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang, It should be an issue in nova train. Error log is below: build of instance 363dddce-7af6-4701-8cea-52630b91ebcf aborted: Image 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, but format is now qcow2' You tried to fix this issue before in nova LP: https://bugs.launchpad.net/nova/+bug/1816686 In your patch: https://review.opendev.org/#/c/640271 (This patch is already in train release now) You added below commit message in the patch. “When we import image into rbd, check the format of cache images. If the format is not raw, remove it first and fetch it again. It will be raw format now.” However, it seems not work! Below code will throw error when image format is not raw and block the VM creation. In nova/virt/images.py def fetch_to_raw() ==> if data.file_format != "raw": raise exception.ImageUnacceptable(image_id=image_href, reason=_("Converted to raw, but format is now %s") Not sure if your patch fixed this issue or is there any regression introduced in nova code later. Any comment from you? I will check nova code further tomorrow and sync with you. We may need a patch for nova☹ Thanks! Zhipeng From: Xie, Cindy > Sent: 2019年10月30日 22:49 To: Lemus Contreras, Cristopher J >; Liu, ZhipengS >; 朱博祥 >; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade + mailing list in case anybody can help on debug the issue. From: Lemus Contreras, Cristopher J > Sent: Wednesday, October 30, 2019 7:45 PM To: Liu, ZhipengS >; 朱博祥 > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Xie, Cindy >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, The results are OK for Simplex, Duplex and Standard Local Storage, all Test Cases PASSED. For Standard External Storage (2+2+2) there is a high quantity of Test Cases failing because we cannot launch instances. Here’s a sample output: http://paste.openstack.org/show/785641/ with the error that matches what is described on the launchpad. Sanity summary for this specific configuration: http://paste.openstack.org/show/785655/ Please, let us know if you need additional details. Thanks & Regards, Cristopher Lemus -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Thu Oct 31 04:41:20 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 31 Oct 2019 04:41:20 +0000 Subject: [Starlingx-discuss] About EB verification for openstack train upgrade In-Reply-To: References: <93814834B4855241994F290E959305C7530F2DE1@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C7530F2E2C@SHSMSX104.ccr.corp.intel.com> Boxiang, Yes, I just want to check with you about images_type. Do we really need to change “images_type” to rbd from default, is it related to format convert? You patch code should already be hit, as we failed with EB307 with below error msg you added in your patch. if CONF.libvirt.images_type in ('rbd',): if not CONF.force_raw_images: msg = _("'[DEFAULT]/force_raw_images = False' is not " "allowed with '[libvirt]/images_type = rbd'. " "Please check the two configs and if you really " "do want to use rbd as images_type, set " "force_raw_images to True.") raise exception.InvalidConfiguration(msg) Below command is sent in my virtual multi-node environment, not in EB test environment. [root at compute-0 instances]# rbd ls -p vms rbd: error opening pool 'vms': (2) No such file or directory rbd: list: (2) No such file or directory [root at compute-0 instances]# ls compute_nodes locks lost+found Unfortunately, we have no whole test log. @Lemus Contreras, Cristopher J Need your help to provide complete logs tested by EB308 Thanks! Zhipeng From: 朱博祥 Sent: 2019年10月31日 12:06 To: Liu, ZhipengS ; Xie, Cindy ; Lemus Contreras, Cristopher J ; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re:RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng and All, First of all, I found in your nova.conf, images_type = default So I think you just use qcow2 imagebackend and the root disk is on your nova-compute node not in vms pool of ceph storage. You can check that with command 'rbd ls -p vms'. So that the creating vm process will not trigger my code in this patch https://review.opendev.org/#/c/640271 From the nova code, in nova/virt/images.py def fetch_to_raw(): -> convert_image(path_tmp, staged, fmt, 'raw') -> cmd = ('qemu-img', 'convert', '-t', cache_mode, '-O', out_format) So if the format of image is not raw, it will call qemu-img command to convert it to raw. But after converting and check the format of image again, it is still not raw, so it raise exception. So we can check the nova-compute logs whether other error msgs exist or not. BTW, can you check the base image's format under '/var/lib/nova/instances/_base'? You can find the image in nova-compute container. -- Thanks, Boxiang From: "Liu, ZhipengS" > Date: 2019-10-31 11:38:36 To: "Liu, ZhipengS" >,"朱博祥" >,"Xie, Cindy" >,"Lemus Contreras, Cristopher J" >,"starlingx-discuss at lists.starlingx.io" > Cc: "Alonso, Juan Carlos" >,"Hu, Yong" >,"Cabrales, Ada" >,"Jones, Bruce E" >,"Martinez Monroy, Elio" > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Below is current test config. [libvirt] connection_uri = qemu+tcp://127.0.0.1/system cpu_mode = host-model disk_cachemodes = network=writeback hw_disk_discard = unmap images_rbd_ceph_conf = /etc/ceph/ceph.conf images_rbd_pool = vms images_type = default live_migration_completion_timeout = 180 live_migration_inbound_addr = 192.168.206.150 live_migration_permit_auto_converge = true mem_stats_period_seconds = 0 rbd_secret_uuid = 457eb676-33da-42ec-9a8c-9293d545c337 rbd_user = cinder remove_unused_resized_minimum_age_seconds = 86400 virt_type = qemu I also did below convert command manually, it seems OK. controller-0:~$ qemu-img convert -t none -O raw -f qcow2 cirros-0.4.0-x86_64-disk.img test1.img controller-0:~$ qemu-img convert -t writeback -O raw -f qcow2 cirros-0.4.0-x86_64-disk.img test2.img controller-0:~$ qemu-img info test1.img image: test1.img file format: raw virtual size: 44M (46137344 bytes) disk size: 13M controller-0:~$ qemu-img info test2.img image: test2.img file format: raw virtual size: 44M (46137344 bytes) disk size: 13M Need further check why in the code after convert, the image format is still qcow2. Zhipeng From: Liu, ZhipengS > Sent: 2019年10月31日 11:12 To: 朱博祥 >; Xie, Cindy >; Lemus Contreras, Cristopher J >; 'starlingx-discuss at lists.starlingx.io' > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang, Yes, my below patch can be abandoned, just need to remove “force_raw_images: false” in stx/openstack-armada-app/stx-openstack-helm/stx-openstack-helm/manifests/manifest.yamll file since the default value is true currently. https://review.opendev.org/#/c/691802/ I will modify my patch. However, it is not related to current issue since this flag is set to true in the test. The issue is just as error log mentioned below. “ Image 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, but format is now qcow2 ” We need check this point further. Thanks! Zhipeng From: 朱博祥 > Sent: 2019年10月31日 10:41 To: Liu, ZhipengS >; Xie, Cindy >; Lemus Contreras, Cristopher J >; 'starlingx-discuss at lists.starlingx.io' > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re:RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, I have succeeded to create the vm in openstack upstream(master, code is two weeks ago) now. I deployed the environment with kolla-ansible(ceph as the backend storage). In my nova.conf file, the section of libvirt is as followed: [libvirt] connection_uri = qemu+tcp://172.16.140.14/system images_type = rbd images_rbd_pool = vms images_rbd_ceph_conf = /etc/ceph/ceph.conf rbd_user = nova disk_cachemodes = network=writeback hw_disk_discard = unmap rbd_secret_uuid = 5c79d567-e142-4ab4-87f6-0fdf53060ab9 virt_type = kvm The default value of 'force_raw_images' in nova is True, so I did not set it as True again in my nova.conf file. I use the min image cirros with qcow2 format and created the vm without volume which is created by cinder. It's my image's info: (nova-compute)[root at zbx-allinone /]# qemu-img info cirros-0.4.0-x86_64-disk.img image: cirros-0.4.0-x86_64-disk.img file format: qcow2 virtual size: 44M (46137344 bytes) disk size: 12M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false So as you said, command qemu-img failed to convert the image from qcow2 to raw. BTW, is it a phenomenon that must recur now in STX? Are there other error logs in nova-compute or other nova-* services? -- Thanks, Boxiang 发件人:"Liu, ZhipengS" > 发送日期:2019-10-31 10:14:44 收件人:"Liu, ZhipengS" >,"Xie, Cindy" >,"Lemus Contreras, Cristopher J" >,"'朱博祥'" >,"'starlingx-discuss at lists.starlingx.io'" > 抄送人:"Alonso, Juan Carlos" >,"Hu, Yong" >,"Cabrales, Ada" >,"Jones, Bruce E" >,"Martinez Monroy, Elio" > 主题:RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang and all, In fetch_to_raw(), After force convert image from qcow2 to raw, the format is still not raw, then throw below error. It seems qemu-image convert image failed. Zhipeng From: Liu, ZhipengS > Sent: 2019年10月31日 9:35 To: Xie, Cindy >; Lemus Contreras, Cristopher J >; '朱博祥' >; 'starlingx-discuss at lists.starlingx.io' > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade From: Liu, ZhipengS Sent: 2019年10月30日 23:24 To: Xie, Cindy >; Lemus Contreras, Cristopher J >; 朱博祥 >; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang, It should be an issue in nova train. Error log is below: build of instance 363dddce-7af6-4701-8cea-52630b91ebcf aborted: Image 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, but format is now qcow2' You tried to fix this issue before in nova LP: https://bugs.launchpad.net/nova/+bug/1816686 In your patch: https://review.opendev.org/#/c/640271 (This patch is already in train release now) You added below commit message in the patch. “When we import image into rbd, check the format of cache images. If the format is not raw, remove it first and fetch it again. It will be raw format now.” However, it seems not work! Below code will throw error when image format is not raw and block the VM creation. In nova/virt/images.py def fetch_to_raw() ==> if data.file_format != "raw": raise exception.ImageUnacceptable(image_id=image_href, reason=_("Converted to raw, but format is now %s") Not sure if your patch fixed this issue or is there any regression introduced in nova code later. Any comment from you? I will check nova code further tomorrow and sync with you. We may need a patch for nova☹ Thanks! Zhipeng From: Xie, Cindy > Sent: 2019年10月30日 22:49 To: Lemus Contreras, Cristopher J >; Liu, ZhipengS >; 朱博祥 >; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade + mailing list in case anybody can help on debug the issue. From: Lemus Contreras, Cristopher J > Sent: Wednesday, October 30, 2019 7:45 PM To: Liu, ZhipengS >; 朱博祥 > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Xie, Cindy >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, The results are OK for Simplex, Duplex and Standard Local Storage, all Test Cases PASSED. For Standard External Storage (2+2+2) there is a high quantity of Test Cases failing because we cannot launch instances. Here’s a sample output: http://paste.openstack.org/show/785641/ with the error that matches what is described on the launchpad. Sanity summary for this specific configuration: http://paste.openstack.org/show/785655/ Please, let us know if you need additional details. Thanks & Regards, Cristopher Lemus -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Thu Oct 31 23:05:45 2019 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 31 Oct 2019 16:05:45 -0700 Subject: [Starlingx-discuss] Layer Build Testing Issue Message-ID: <9685602e-c53f-8a99-1cbf-1d9d2b61c716@linux.intel.com> Hi Martin: I am continuing to test the layer'ed build, I was able to build compile standalone, and then attempted to build distro in the same build area, but I seem to get a failure in kubernetes package build. See the attached root.log. Thanks Sau! -------------- next part -------------- A non-text attachment was scrubbed... Name: root.log Type: text/x-log Size: 218642 bytes Desc: not available URL: From zhaos at neusoft.com Thu Oct 24 13:48:58 2019 From: zhaos at neusoft.com (zhao.shuai) Date: Thu, 24 Oct 2019 21:48:58 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSNOiAgV2Vla2x5IFN0YXJsaW5n?= =?utf-8?q?X_non-OpenStack_distro=09meeting?= In-Reply-To: <95b0f80b-ed39-32b7-e2f8-aae644b081de@linux.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F35F28711@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F36086E35@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F36088FA4@SHSMSX104.ccr.corp.intel.com> <95b0f80b-ed39-32b7-e2f8-aae644b081de@linux.intel.com> Message-ID: <000001d58a71$c90938e0$5b1baaa0$@neusoft.com> Regarding the task of upgrading the StarlingX kernel version to CentOS 4.18. Our team currently have a preliminary comparison of the RPM/ and SRPM packages and the kernel patches analysis. Please refer to the attachment for the results of the initial analysis. As the same time, CentOS 4.18 Kernel Source is being compiled and ported . yes we encountered a lot of problems during the porting of the kernel. We are keeping in touch with Saul and Shuicheng in real time. If there is any progress, we will report to you in the Mail list in time. Thank you! Best Regards Wish you happy everyday! -------------------------------- Shuai - Neusoft -----邮件原件----- 发件人: Saul Wold 发送时间: 2019年10月18日 5:36 收件人: starlingx-discuss at lists.starlingx.io 抄送: Rowsell, Brent 主题: Re: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting Please find attached the spreadsheet analyzing the Kernel patches to the existing CentOS 3.10 kernel. As mentioned, most of the patches can be dropped, except for the Notification of Death patch. My understanding is that changes have been made to StarlingX to support the Workqueue CPU affinity model with isolcpus instead of the kthread model that is in the 3.10 kernel. If this is actually the case then we can drop the cpu affinity related patches also. (this would be a good thing). Don't hesitate to reach out and ask for help with the kernel and/or CentOS 8 User space updates. Sau! On 10/16/19 6:53 AM, Xie, Cindy wrote: > Agenda & notes for 10/16 meeting: > > . Ceph containerization update (Tingjie) > https://review.opendev.org/#/c/681457/ this is for Helm chart definition, can be review now. > https://review.opendev.org/#/c/687340/ for Helm overrides framework, need to extend later. > verified in AIO and multi-node provision. > configuration needs to be override according to STX parameters. > Martin working on this for parameters to align w/ the native deployment. > for stx.3.0: only to merge the implantation for Helm chart and override framework. and rook-plugin which support sysinv, this can co-exist w/ current native ceph deployment. > test case development is in progress, Tingjie will sync with Fernando. > for sysinv, still need to working on patches, not ready for upload/review. > AR: Tingjie to send email to the mailing list for the current status & planning for include partial implementation without impacting the native Ceph functionality. > > . Debranding update (Saul) > Starting from the tools repo, the tools in the build area to debrand the mirroring process. Part of this is for ease of use for build steps. Very early stage. Not fit in stx.3.0 scope. > https://storyboard.openstack.org/#!/story/2006387, call volunteer from the community. > > . CentOS 8 upgrade planning (Cindy) CentOS 8.0 2 stories created: > https://storyboard.openstack.org/#!/story/2006728, the kernel inside CentOS 8 is 4.18, there is no RT kernel. > https://storyboard.openstack.org/#!/story/2006729 > Shuai is working on new kernel onto build system. Need to understand each patches. there was an earlier analysis for kernel patches available. > AR: Saul please share this analysis to Shuai. against 4.19 kernel some long time ago. > See > https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAu > gOWXMjB7VIrfc/edit#gid=311578025 Tab Kernel Patches Details > https://github.com/xe1gyq/linux/commits/v4.19 > https://github.com/xe1gyq/linux/commits/v4.18 > AR: Shuai to provide an Excel sheet to compare RPM/sRPM in StarlingX > and in CentOS 8.0 > > . Opens - none > _____________________________________________ > From: Xie, Cindy > Sent: Tuesday, October 15, 2019 9:39 PM > To: Wold, Saul ; > 'starlingx-discuss at lists.starlingx.io' > ; 'Rowsell, Brent' > > Subject: RE: Weekly StarlingX non-OpenStack distro meeting > > > Agenda: > - Ceph containerization update (Tingjie) > - Debranding update (Saul) > - CentOS 8 upgrade planning (Cindy) > - Opens > > Cindy Xie > IAGS > > http://starlingx.io/ > > > -----Original Appointment----- > From: Xie, Cindy > Sent: Thursday, April 25, 2019 5:42 PM > To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' > Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; > 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, > Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, > Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W > Subject: Weekly StarlingX non-OpenStack distro meeting > When: Wednesday, October 16, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. > Where: https://zoom.us/j/342730236 > > > . 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 > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > --------------------------------------------------------------------------------------------------- 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 -------------- A non-text attachment was scrubbed... Name: Kernel_Upgrade_to_4.18-CentOS8_Analysis_2019-10-24.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 209938 bytes Desc: not available URL: From zhaos at neusoft.com Wed Oct 30 11:17:19 2019 From: zhaos at neusoft.com (zhao.shuai) Date: Wed, 30 Oct 2019 19:17:19 +0800 Subject: [Starlingx-discuss] Upgrading the StarlingX kernel version to CentOS 4.18 Message-ID: <001701d58f13$989ffcb0$c9dff610$@neusoft.com> Hi StarlingX Community: Regarding the task of upgrading the StarlingX kernel version to CentOS 4.18. Completed Task: 1. GCC compiler version upgrade --> GCC version 8.2.1 2. Kernel 4.18 with starlingX patch compilation has been completed.(Patch40004,Patch40007,Patch40008) Doing Task: 1. src rpm package el8 upgrade(if there is el8 version) 2. If there is no el8 version of SRPM compilation failed, we need to build a patch fix it. 3. Configure kernel 4.18 config file with reference to STX kernel 3.10 config file (kernel-3.10.0-x86_64.config.tis_extra) 4. For the el8 version SRPM package that fails to be compiled, the RPM package of the el8 version is preferentially searched for replacement. Please see the attachment for the results of the advancement Thank you! Best Regards Wish you happy everyday! -------------------------------- Shuai - Neusoft -----邮件原件----- 发件人: Saul Wold 发送时间: 2019年10月18日 5:36 收件人: starlingx-discuss at lists.starlingx.io 抄送: Rowsell, Brent 主题: Re: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting Please find attached the spreadsheet analyzing the Kernel patches to the existing CentOS 3.10 kernel. As mentioned, most of the patches can be dropped, except for the Notification of Death patch. My understanding is that changes have been made to StarlingX to support the Workqueue CPU affinity model with isolcpus instead of the kthread model that is in the 3.10 kernel. If this is actually the case then we can drop the cpu affinity related patches also. (this would be a good thing). Don't hesitate to reach out and ask for help with the kernel and/or CentOS 8 User space updates. Sau! On 10/16/19 6:53 AM, Xie, Cindy wrote: > Agenda & notes for 10/16 meeting: > > . Ceph containerization update (Tingjie) > https://review.opendev.org/#/c/681457/ this is for Helm chart definition, can be review now. > https://review.opendev.org/#/c/687340/ for Helm overrides framework, need to extend later. > verified in AIO and multi-node provision. > configuration needs to be override according to STX parameters. > Martin working on this for parameters to align w/ the native deployment. > for stx.3.0: only to merge the implantation for Helm chart and override framework. and rook-plugin which support sysinv, this can co-exist w/ current native ceph deployment. > test case development is in progress, Tingjie will sync with Fernando. > for sysinv, still need to working on patches, not ready for upload/review. > AR: Tingjie to send email to the mailing list for the current status & planning for include partial implementation without impacting the native Ceph functionality. > > . Debranding update (Saul) > Starting from the tools repo, the tools in the build area to debrand the mirroring process. Part of this is for ease of use for build steps. Very early stage. Not fit in stx.3.0 scope. > https://storyboard.openstack.org/#!/story/2006387, call volunteer from the community. > > . CentOS 8 upgrade planning (Cindy) CentOS 8.0 2 stories created: > https://storyboard.openstack.org/#!/story/2006728, the kernel inside CentOS 8 is 4.18, there is no RT kernel. > https://storyboard.openstack.org/#!/story/2006729 > Shuai is working on new kernel onto build system. Need to understand each patches. there was an earlier analysis for kernel patches available. > AR: Saul please share this analysis to Shuai. against 4.19 kernel some long time ago. > See > https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAu > gOWXMjB7VIrfc/edit#gid=311578025 Tab Kernel Patches Details > https://github.com/xe1gyq/linux/commits/v4.19 > https://github.com/xe1gyq/linux/commits/v4.18 > AR: Shuai to provide an Excel sheet to compare RPM/sRPM in StarlingX > and in CentOS 8.0 > > . Opens - none > _____________________________________________ > From: Xie, Cindy > Sent: Tuesday, October 15, 2019 9:39 PM > To: Wold, Saul ; > 'starlingx-discuss at lists.starlingx.io' > ; 'Rowsell, Brent' > > Subject: RE: Weekly StarlingX non-OpenStack distro meeting > > > Agenda: > - Ceph containerization update (Tingjie) > - Debranding update (Saul) > - CentOS 8 upgrade planning (Cindy) > - Opens > > Cindy Xie > IAGS > > http://starlingx.io/ > > > -----Original Appointment----- > From: Xie, Cindy > Sent: Thursday, April 25, 2019 5:42 PM > To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' > Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; > 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, > Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, > Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W > Subject: Weekly StarlingX non-OpenStack distro meeting > When: Wednesday, October 16, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. > Where: https://zoom.us/j/342730236 > > > . 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 > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > --------------------------------------------------------------------------------------------------- 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 -------------- A non-text attachment was scrubbed... Name: Kernel_Upgrade_to_4.18-CentOS8_Analysis_2019-10-30.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 263937 bytes Desc: not available URL: