From haochuan.z.chen at intel.com Tue Sep 1 00:31:02 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 1 Sep 2020 00:31:02 +0000 Subject: [Starlingx-discuss] patch review for rook-ceph In-Reply-To: References: Message-ID: Thanks Mary, I will update doc in this week. Martin, Chen IOTG, Software Engineer 021-61164330 From: Camp, MaryX Sent: Tuesday, September 1, 2020 2:53 AM To: Chen, Haochuan Z ; starlingx-discuss at lists.starlingx.io; Bailey, Henry Albert (Al) Subject: RE: patch review for rook-ceph Hi Martin, There are 5 reviews in progress for STX docs for rook-ceph. Can you please resolve the outstanding comments? Then the docs team will review again. https://review.opendev.org/#/q/status:open+project:starlingx/docs+branch:master+topic:ceph-cluster-editorial Thanks in advance, Mary Camp PTIGlobal Technical Writer | maryx.camp at intel.com From: Chen, Haochuan Z > Sent: Monday, August 31, 2020 11:16 AM To: starlingx-discuss at lists.starlingx.io; Bailey, Henry Albert (Al) > Subject: [Starlingx-discuss] patch review for rook-ceph Thanks AL review my patch for rook-ceph Appreciate more reviewer for my patch. https://review.opendev.org/#/q/topic:%22ceph+containerization%22+(status:open+OR+status:merged) Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Sep 1 03:49:04 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 31 Aug 2020 23:49:04 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_retag_docker_images - Build # 189 - Still Failing! In-Reply-To: <1531649609.2223.1598872444690.JavaMail.javamailuser@localhost> References: <1531649609.2223.1598872444690.JavaMail.javamailuser@localhost> Message-ID: <1526860698.4.1598932146400.JavaMail.javamailuser@localhost> Project: STX_retag_docker_images Build #: 189 Status: Still Failing Timestamp: 20200901T034857Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200901T001315Z/logs -------------------------------------------------------------------------------- Parameters HOST_PORT: 80 OLD_LATEST_PREFIX: master WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20200901T001315Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20200901T001315Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200901T001315Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20200901T001315Z/logs RETAG_IMAGE_LIST: stx-fm-rest-api stx-libvirt stx-mariadb FLOCK_VERSION: master-centos-stable-20200901T001315Z PREFIX: master TIMESTAMP: 20200901T001315Z BUILD_STREAM: dev REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20200901T001315Z/outputs REGISTRY: docker.io OLD_BUILD_STREAM: stable From austin.sun at intel.com Tue Sep 1 07:29:52 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 1 Sep 2020 07:29:52 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 9/2/2020 Message-ID: Hi All: Agenda 9/2 meeting: -Ceph containerization : Patches Review Status : https://review.opendev.org/#/q/status:open+branch:master+topic:%22ceph+containerization%22 feature test status - Open If any more topic , please add into https://etherpad.opendev.org/p/stx-distro-other Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ankush.Rai at commscope.com Tue Sep 1 07:58:56 2020 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Tue, 1 Sep 2020 07:58:56 +0000 Subject: [Starlingx-discuss] DANM support Message-ID: Any guideline or pointer to run DANM over starlingx setup? -------------- next part -------------- An HTML attachment was scrubbed... URL: From gopalkrishna.bhat at intel.com Tue Sep 1 08:42:05 2020 From: gopalkrishna.bhat at intel.com (Bhat, Gopalkrishna) Date: Tue, 1 Sep 2020 08:42:05 +0000 Subject: [Starlingx-discuss] STX containerization meetings stopped In-Reply-To: References: Message-ID: Hello Frank , Considering FM containerization is https://etherpad.openstack.org/p/stx.4.0-feature-candidates part of the 5.0 features planned requiring inputs/discussion & there are few new topics requiring inputs from the community ,Can we keep the meeting & cancel only if no topics for that week ? Regards Gopi From: Miller, Frank Sent: Monday, August 31, 2020 8:30 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] STX containerization meetings stopped The number of topics for STX containerization has significantly reduced with the release of stx.4.0. As such I am cancelling the bi-weekly meetings at this time. If there is a need to revive these meetings during stx.5.0 I will send an email to announce when the next meeting will occur. Frank PL STX Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: From sharath.kumar at intel.com Tue Sep 1 09:11:32 2020 From: sharath.kumar at intel.com (Kumar, Sharath) Date: Tue, 1 Sep 2020 09:11:32 +0000 Subject: [Starlingx-discuss] Starlingx-discuss Digest, Vol 27, Issue 82 In-Reply-To: References: Message-ID: Hi Ankush, To redefine the docker subnet in your machine, you can try below steps. Here as an example taking 10.10.10.0 network. 1. sudo vim /etc/docker/daemon.json { "default-address-pools": [ {"base":"10.10.10.0/16","size":24} ] } 2. Restart the Docker Daemon by using this command: sudo service docker restart Regards, Sharath -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Friday, August 28, 2020 1:05 PM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 27, Issue 82 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. [stable] [build-report] STX_build_docker_images_layered - Build # 45 - Still Failing! (build.starlingx at gmail.com) 2. [build-report] STX_build_layer_containers_master_master - Build # 66 - Still Failing! (build.starlingx at gmail.com) 3. Is this possible to make use of single NIC interface in Starlingx deployment ? (Rai, Ankush) 4. Re: Is this possible to make use of single NIC interface in Starlingx deployment ? (Marc Ferland) 5. How to change docker default subnet? (Rai, Ankush) ---------------------------------------------------------------------- Message: 1 Date: Thu, 27 Aug 2020 13:53:08 -0400 (EDT) From: build.starlingx at gmail.com To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images_layered - Build # 45 - Still Failing! Message-ID: <1080234674.2195.1598550789393.JavaMail.javamailuser at localhost> Content-Type: text/plain; charset="utf-8" Project: STX_build_docker_images_layered Build #: 45 Status: Still Failing Timestamp: 20200827T134602Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200827T132712Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20200827T132712Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200827T132712Z/logs MASTER_BUILD_NUMBER: 66 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20200827T132712Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20200827T132712Z DOCKER_BUILD_ID: jenkins-master-containers-20200827T132712Z-builder TIMESTAMP: 20200827T132712Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20200827T132712Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20200827T132712Z/outputs ------------------------------ Message: 2 Date: Thu, 27 Aug 2020 13:53:10 -0400 (EDT) From: build.starlingx at gmail.com To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_build_layer_containers_master_master - Build # 66 - Still Failing! Message-ID: <1016082276.2198.1598550791504.JavaMail.javamailuser at localhost> Content-Type: text/plain; charset="utf-8" Project: STX_build_layer_containers_master_master Build #: 66 Status: Still Failing Timestamp: 20200827T132712Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200827T132712Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true ------------------------------ Message: 3 Date: Thu, 27 Aug 2020 18:19:20 +0000 From: "Rai, Ankush" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Is this possible to make use of single NIC interface in Starlingx deployment ? Message-ID: Content-Type: text/plain; charset="iso-8859-1" Any pointers for StarlingX deployment with single NIC interface? (Duplex or multi-node cluster) How to configure VLAN tagging for OAM and Management ? Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 4 Date: Thu, 27 Aug 2020 14:21:57 -0400 From: Marc Ferland To: "Rai, Ankush" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Is this possible to make use of single NIC interface in Starlingx deployment ? Message-ID: Content-Type: text/plain; charset="utf-8" This should get you going: https://docs.starlingx.io/configuration/host_interface_network_config.html#network-configuration-and-assignment On Thu, Aug 27, 2020 at 2:20 PM Rai, Ankush wrote: > Any pointers for StarlingX deployment with single NIC interface? > (Duplex or multi-node cluster) How to configure VLAN tagging for OAM > and Management ? > > Thanks, > Ankush > _______________________________________________ > 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: ------------------------------ Message: 5 Date: Thu, 27 Aug 2020 18:46:29 +0000 From: "Rai, Ankush" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] How to change docker default subnet? Message-ID: Content-Type: text/plain; charset="iso-8859-1" Is there any Ansible configuration or CLI to redefine the docker subnet ? This default subnet 172.17. 0.0/16 is clashing with LAB network and I am not able to access the StarlingX cluster from LAB network. Is it feasible to use "bip" option in "/etc/docker/daemon.json" ? Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 27, Issue 82 ************************************************* From oliver.lovaszi at intel.com Tue Sep 1 11:54:50 2020 From: oliver.lovaszi at intel.com (Lovaszi, Oliver) Date: Tue, 1 Sep 2020 11:54:50 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200831T230230Z Message-ID: Sanity Test from 2020-Spetember-1 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200831T230230Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200831T230230Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ebiibe82 at gmail.com Tue Sep 1 13:19:32 2020 From: ebiibe82 at gmail.com (Amit Mahajan) Date: Tue, 1 Sep 2020 18:49:32 +0530 Subject: [Starlingx-discuss] Regarding Distro OpenStack Team meeting Message-ID: Hi All, Is the OpenStack Distro Team meeting cancelled for today? Anybody having any idea when the next meeting is planned? Regards, Amit -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Sep 1 14:21:24 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 1 Sep 2020 10:21:24 -0400 Subject: [Starlingx-discuss] [build]: py2 starlingx images locked to python modules from June build? In-Reply-To: References: Message-ID: <3ff5c16a-2e08-81bb-aeee-bf8d6eba024e@windriver.com> Zhipemg Can you provide a method to generate an updated stx-centos-py2_stable-wheels.tar that I can implement on the CENGN side? In this way, we can have the tarball automatically update when new updates arrive. Scott \ On 2020-08-14 10:47 a.m., Liu, ZhipengS wrote: > > Hi Frank and Don, > > This is exactly a workaround for 4 python2 base images build after I > discussed with Scott and Chant in mailing list. > > Please see my attached email for more detail. > > We cannot revert this patch directly as it will block ussuri openstack > image build. > > Chant and I also tried several solutions before, including > > 1. Try to find all python2 dependent wheels > >        Need add almost all old python2 wheels and fix conflict and > dependency issues. > > 2. Try to find wheels support both python2 and python3 > > Some wheels could not support both. > > 3. Try to build these 4 images with python3 enabled > > But these local packages have several local dependencies, which are > all python2 based. > > stx-nova-api-proxy   (This one can be upgraded to py3) > > stx-fm-rest-api > > stx-keystone-api-proxy > > stx-platformclients > > Thanks! > > Zhipeng > > *From:* Miller, Frank > *Sent:* 2020年8月14日 4:07 > *To:* Khalil, Ghada ; Penney, Don > ; 'starlingx-discuss at lists.starlingx.io' > ; Liu, ZhipengS > > *Subject:* RE: [build]: py2 starlingx images locked to python modules > from June build? > > Zhipeng: > > Please suggest a solution to this issue. One option is to back out the > commit that introduced this issue.  Can you identify a solution that > doesn’t require you to back out your commit? > > Frank > > *From:* Khalil, Ghada > > *Sent:* Wednesday, August 12, 2020 10:06 PM > *To:* Penney, Don >; > 'starlingx-discuss at lists.starlingx.io' > >; Liu, ZhipengS > (zhipengs.liu at intel.com ) > >; Miller, > Frank > > *Subject:* RE: [build]: py2 starlingx images locked to python modules > from June build? > > The launchpad is: https://bugs.launchpad.net/starlingx/+bug/1891416 > > > *From:* Penney, Don > > *Sent:* Wednesday, August 12, 2020 9:21 PM > *To:* 'starlingx-discuss at lists.starlingx.io' > >; Liu, ZhipengS > (zhipengs.liu at intel.com ) > >; Miller, > Frank > > *Subject:* [Starlingx-discuss] [build]: py2 starlingx images locked to > python modules from June build? > > Hi folks, > > It was discovered that the recent stx-platformclients image was not > picking up recent changes made to the distributedcloud-client package > (I believe a Launchpad will be raised shortly). Tracing back through > the CENGN build logs, the problem appears to stem from the changes > introduced by: > > https://review.opendev.org/#/c/737456/11/build-tools/build-docker-images/docker-image-build.cfg > > So for specific images, including stx-platformclients, the image build > is now using a reference to a presumably static tarball: > > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/stx-centos-py2_stable-wheels.tar > > Looking at the dir listing, we can see this tarball is dated June 23^rd : > > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ > > What this means is that these particular images will be using this > locked tarball for installing python modules from the wheels (ie. The > PIP_PACKAGES list)… which means that an image like > stx-platformclients, which is getting various starlingx clients from > wheels, will only ever have content from that June 23^rd build. > > Was this the intended behavior? Instead of this “alternate wheels > tarball”, shouldn’t we be generating a wheels tarball with both py2 > and py3 support, as long as we’re building any py2 images? > > Thanks, > > Don. > > > _______________________________________________ > 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 jimmy at openstack.org Tue Sep 1 15:08:12 2020 From: jimmy at openstack.org (Jimmy McArthur) Date: Tue, 1 Sep 2020 10:08:12 -0500 Subject: [Starlingx-discuss] 2020 Virtual Summit: Forum Submissions Now Accepted Message-ID: <9B9E2444-06D4-483E-B311-C9237AD2BA06@getmailspring.com> Hello Everyone! We are now accepting Forum [1] submissions for the 2020 Virtual Open Infrastructure Summit [2]. Please submit your ideas through the Summit CFP tool [3] through September 14th. Don't forget to put your brainstorming etherpad up on the Shanghai Forum page [4]. This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. More information about the Forum [1]. The timeline for submissions is as follows: Aug 31st | Formal topic submission tool opens: https://cfp.openstack.org. Sep 14th | Deadline for proposing Forum topics. Scheduling committee meeting to make draft agenda. Sep 21st | Draft Forum schedule published. Crowd sourced session conflict detection. Forum promotion begins. Sept 28th | Forum schedule final Oct 19th | Forum begins! If you have questions or concerns, please reach out to speakersupport at openstack.org. Cheers, Jimmy [1] https://wiki.openstack.org/wiki/Forum [2] https://www.openstack.org/summit/2020/ [3] https://cfp.openstack.org [4]https://wiki.openstack.org/wiki/Forum/Virtual2020 -------------- next part -------------- An HTML attachment was scrubbed... URL: From yang.liu at windriver.com Tue Sep 1 15:20:52 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Tue, 1 Sep 2020 15:20:52 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 09/01/2020 Message-ID: Agenda/meeting notes are posted here: https://etherpad.openstack.org/p/stx-test Agenda for 9/1/2020 Attendees: Yang, Greg, Mary · Open topics * Doc testing § Upstreaming docs from WR · Concept type of procedures do not need to be tested · Concern: doc testing is needed for some of the procedures such as install and config (errors cannot easily be caught by gerrit review) · What is procedure to request Doc testing? o Most of Doc changes are tracked via launchpads or task under a story if designer is going to add the doc o Propose we use launchpads for test request * Greg/Mary to create launchpads for explict testing, and provide query to test team. * Test team to review backlog and have them discussed and assigned in test meeting. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Tue Sep 1 16:52:31 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 1 Sep 2020 16:52:31 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Sep 2, 2020) Message-ID: Hi all, reminder of the TSC/Community call tomorrow. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200902T1400 From fungi at yuggoth.org Tue Sep 1 17:39:00 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Tue, 1 Sep 2020 17:39:00 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-08-19 In-Reply-To: <20200831200707.ik2usiqak37mconr@yuggoth.org> References: <20200820160118.ilnaqgukaqh2oraj@yuggoth.org> <20200831200707.ik2usiqak37mconr@yuggoth.org> Message-ID: <20200901173859.yggznqtd4uadq2n7@yuggoth.org> On 2020-08-28 14:57:36 +0000 (+0000), Camp, MaryX wrote: [...] > The STX docs repo already has an R4 branch: > https://opendev.org/starlingx/docs/src/branch/r/stx.4.0 so that > part is done. Our planned URL structures are: > https://docs.starlingx.io/R4.01 (current release) and > https://docs.starlingx.io/latest for the master branch. [...] In drafting https://review.opendev.org/749369 to implement this alternative matching, it has dawned on me that I'm not entirely clear from the above what your expectations are when publishing. In short, are you publishing from a branch or from a tag? If the former, then the r/stx.4.0 branch's documentation would presumably be published under R4.0 not R4.01. Was that a typo, or is there some missing bit of detail to determine the publication directory from the branch? -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From zhipengs.liu at intel.com Wed Sep 2 01:43:41 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 2 Sep 2020 01:43:41 +0000 Subject: [Starlingx-discuss] [build]: py2 starlingx images locked to python modules from June build? In-Reply-To: <3ff5c16a-2e08-81bb-aeee-bf8d6eba024e@windriver.com> References: <3ff5c16a-2e08-81bb-aeee-bf8d6eba024e@windriver.com> Message-ID: Hi Scott, You might utilize below script, get-stx-wheels.sh to get latest local StarlingX wheels produced by the StarlingX build. Then update them to current stx-centos-py2_stable-wheels.tar Thanks! Zhipeng From: Scott Little Sent: 2020年9月1日 22:21 To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build]: py2 starlingx images locked to python modules from June build? Zhipemg Can you provide a method to generate an updated stx-centos-py2_stable-wheels.tar that I can implement on the CENGN side? In this way, we can have the tarball automatically update when new updates arrive. Scott \ On 2020-08-14 10:47 a.m., Liu, ZhipengS wrote: Hi Frank and Don, This is exactly a workaround for 4 python2 base images build after I discussed with Scott and Chant in mailing list. Please see my attached email for more detail. We cannot revert this patch directly as it will block ussuri openstack image build. Chant and I also tried several solutions before, including 1. Try to find all python2 dependent wheels Need add almost all old python2 wheels and fix conflict and dependency issues. 1. Try to find wheels support both python2 and python3 Some wheels could not support both. 1. Try to build these 4 images with python3 enabled But these local packages have several local dependencies, which are all python2 based. stx-nova-api-proxy (This one can be upgraded to py3) stx-fm-rest-api stx-keystone-api-proxy stx-platformclients Thanks! Zhipeng From: Miller, Frank Sent: 2020年8月14日 4:07 To: Khalil, Ghada ; Penney, Don ; 'starlingx-discuss at lists.starlingx.io' ; Liu, ZhipengS Subject: RE: [build]: py2 starlingx images locked to python modules from June build? Zhipeng: Please suggest a solution to this issue. One option is to back out the commit that introduced this issue. Can you identify a solution that doesn’t require you to back out your commit? Frank From: Khalil, Ghada > Sent: Wednesday, August 12, 2020 10:06 PM To: Penney, Don >; 'starlingx-discuss at lists.starlingx.io' >; Liu, ZhipengS (zhipengs.liu at intel.com) >; Miller, Frank > Subject: RE: [build]: py2 starlingx images locked to python modules from June build? The launchpad is: https://bugs.launchpad.net/starlingx/+bug/1891416 From: Penney, Don > Sent: Wednesday, August 12, 2020 9:21 PM To: 'starlingx-discuss at lists.starlingx.io' >; Liu, ZhipengS (zhipengs.liu at intel.com) >; Miller, Frank > Subject: [Starlingx-discuss] [build]: py2 starlingx images locked to python modules from June build? Hi folks, It was discovered that the recent stx-platformclients image was not picking up recent changes made to the distributedcloud-client package (I believe a Launchpad will be raised shortly). Tracing back through the CENGN build logs, the problem appears to stem from the changes introduced by: https://review.opendev.org/#/c/737456/11/build-tools/build-docker-images/docker-image-build.cfg So for specific images, including stx-platformclients, the image build is now using a reference to a presumably static tarball: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/stx-centos-py2_stable-wheels.tar Looking at the dir listing, we can see this tarball is dated June 23rd: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ What this means is that these particular images will be using this locked tarball for installing python modules from the wheels (ie. The PIP_PACKAGES list)… which means that an image like stx-platformclients, which is getting various starlingx clients from wheels, will only ever have content from that June 23rd build. Was this the intended behavior? Instead of this “alternate wheels tarball”, shouldn’t we be generating a wheels tarball with both py2 and py3 support, as long as we’re building any py2 images? Thanks, Don. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Wed Sep 2 02:05:48 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 1 Sep 2020 22:05:48 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 755 - Failure! Message-ID: <2107035419.2.1599012350312.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 755 Status: Failure Timestamp: 20200902T014658Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200902T013240Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200902T013240Z DOCKER_BUILD_ID: jenkins-master-flock-20200902T013240Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200902T013240Z/logs BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200902T013240Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From build.starlingx at gmail.com Wed Sep 2 02:05:52 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 1 Sep 2020 22:05:52 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 234 - Failure! Message-ID: <1107080122.5.1599012352758.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 234 Status: Failure Timestamp: 20200902T013240Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200902T013240Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Wed Sep 2 07:34:36 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 2 Sep 2020 03:34:36 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_publish - Build # 1554 - Failure! Message-ID: <1774866706.10.1599032076913.JavaMail.javamailuser@localhost> Project: STX_publish Build #: 1554 Status: Failure Timestamp: 20200902T073434Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200902T043000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200902T043000Z OS: centos PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200902T043000Z/logs TIMESTAMP: 20200902T043000Z PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200902T043000Z/inputs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200902T043000Z/logs MASTER_JOB_NAME: STX_build_master_master LAYER: PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200902T043000Z/outputs MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/monolithic From build.starlingx at gmail.com Wed Sep 2 07:34:38 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 2 Sep 2020 03:34:38 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 661 - Failure! Message-ID: <581493093.13.1599032079248.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 661 Status: Failure Timestamp: 20200902T043000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200902T043000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From austin.sun at intel.com Wed Sep 2 07:46:08 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 2 Sep 2020 07:46:08 +0000 Subject: [Starlingx-discuss] Regarding Distro OpenStack Team meeting In-Reply-To: References: Message-ID: Hi Amit: According to [1], openstack meeting is running bi-weekly , so next meeting is planned next Tuesday. If you have any topic, would you like to add to [2] [1] https://wiki.openstack.org/wiki/Starlingx/Meetings#6am_Pacific_-_Distro_OpenStack_Team_Call_.28Bi-Weekly.29 [2] https://etherpad.openstack.org/p/stx-distro-openstack-meetings Thanks. BR Austin Sun. From: Amit Mahajan Sent: Tuesday, September 1, 2020 9:20 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Regarding Distro OpenStack Team meeting Hi All, Is the OpenStack Distro Team meeting cancelled for today? Anybody having any idea when the next meeting is planned? Regards, Amit -------------- next part -------------- An HTML attachment was scrubbed... URL: From ebiibe82 at gmail.com Wed Sep 2 14:25:52 2020 From: ebiibe82 at gmail.com (Amit Mahajan) Date: Wed, 2 Sep 2020 19:55:52 +0530 Subject: [Starlingx-discuss] Regarding Distro OpenStack Team meeting In-Reply-To: References: Message-ID: Hi Austin, Thanks for your reply. I want to understand the Distro OpenStack team's take on a couple of bugs in launchpad. I will surely add them in the etherpad. On Wed, Sep 2, 2020 at 3:46 PM Sun, Austin wrote: > Hi Amit: > > According to [1], openstack meeting is running bi-weekly , so next meeting > is planned next Tuesday. > > If you have any topic, would you like to add to [2] > > > > [1] > https://wiki.openstack.org/wiki/Starlingx/Meetings#6am_Pacific_-_Distro_OpenStack_Team_Call_.28Bi-Weekly.29 > > [2] https://etherpad.openstack.org/p/stx-distro-openstack-meetings > > > > Thanks. > > BR > Austin Sun. > > *From:* Amit Mahajan > *Sent:* Tuesday, September 1, 2020 9:20 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Regarding Distro OpenStack Team meeting > > > > Hi All, > > > > Is the OpenStack Distro Team meeting cancelled for today? Anybody having > any idea when the next meeting is planned? > > > > Regards, > > Amit > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Wed Sep 2 14:40:15 2020 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 2 Sep 2020 14:40:15 +0000 Subject: [Starlingx-discuss] Regarding Distro OpenStack Team meeting In-Reply-To: References: Message-ID: Hi Amit, Please have a look through the list of distro.openstack issues: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack Except those LPs under “IN PROGRESS”, which means patches/solutions are presented, you could pick up other LPs to start with. In addition, another challengeable but fancy task is to take OpenStack services upgrade from “U” to “V” for following release(s). Let me know if you have further thoughts. Regards, Yong From: Amit Mahajan Date: Wednesday, September 2, 2020 at 10:27 PM To: "Sun, Austin" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Regarding Distro OpenStack Team meeting Hi Austin, Thanks for your reply. I want to understand the Distro OpenStack team's take on a couple of bugs in launchpad. I will surely add them in the etherpad. On Wed, Sep 2, 2020 at 3:46 PM Sun, Austin > wrote: Hi Amit: According to [1], openstack meeting is running bi-weekly , so next meeting is planned next Tuesday. If you have any topic, would you like to add to [2] [1] https://wiki.openstack.org/wiki/Starlingx/Meetings#6am_Pacific_-_Distro_OpenStack_Team_Call_.28Bi-Weekly.29 [2] https://etherpad.openstack.org/p/stx-distro-openstack-meetings Thanks. BR Austin Sun. From: Amit Mahajan > Sent: Tuesday, September 1, 2020 9:20 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Regarding Distro OpenStack Team meeting Hi All, Is the OpenStack Distro Team meeting cancelled for today? Anybody having any idea when the next meeting is planned? Regards, Amit -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Sep 2 15:04:41 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 2 Sep 2020 11:04:41 -0400 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 661 - Failure! In-Reply-To: <581493093.13.1599032079248.JavaMail.javamailuser@localhost> References: <581493093.13.1599032079248.JavaMail.javamailuser@localhost> Message-ID: <97f22ad5-e9de-9968-954a-83e91c2bff46@windriver.com> The failure with in the publication step, not the build step. This is another transient failure of the network file system that allows us to publish to mirror.starlingx.cengn.ca.  A ticket has been raised with CENGN. Scott On 2020-09-02 3:34 a.m., build.starlingx at gmail.com wrote: > Project: STX_build_master_master > Build #: 661 > Status: Failure > Timestamp: 20200902T043000Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200902T043000Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: false > FORCE_BUILD: true > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Wed Sep 2 15:05:58 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 2 Sep 2020 15:05:58 +0000 Subject: [Starlingx-discuss] How to change docker default subnet? In-Reply-To: References: Message-ID: Hi Ankush: Yes . Stx has ansible variant cluster_pod_subnet to config the subnet of k8s cluster . please check [1] for it. [1] https://opendev.org/starlingx/ansible-playbooks/src/branch/master/playbookconfig/src/playbooks/host_vars/bootstrap/default.yml#L50 Thanks. BR Austin Sun. From: Rai, Ankush Sent: Friday, August 28, 2020 2:46 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] How to change docker default subnet? Is there any Ansible configuration or CLI to redefine the docker subnet ? This default subnet 172.17. 0.0/16 is clashing with LAB network and I am not able to access the StarlingX cluster from LAB network. Is it feasible to use "bip" option in "/etc/docker/daemon.json" ? Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Sep 2 15:08:11 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 2 Sep 2020 11:08:11 -0400 Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 234 - Failure! In-Reply-To: <1107080122.5.1599012352758.JavaMail.javamailuser@localhost> References: <1107080122.5.1599012352758.JavaMail.javamailuser@localhost> Message-ID: <02c09cd7-9fa8-ed59-c3e4-59710f652de3@windriver.com> This build failed in build-iso when a loop device could not be obtained. I re-ran the build this morning and it passed.  This is another strange intermittent failure.  I'm scanning logs, but so far I don't see anything to explain the failure. Scott On 2020-09-01 10:05 p.m., build.starlingx at gmail.com wrote: > Project: STX_build_layer_flock_master_master > Build #: 234 > Status: Failure > Timestamp: 20200902T013240Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200902T013240Z/logs > -------------------------------------------------------------------------------- > Parameters > > FULL_BUILD: false > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Sep 2 15:23:28 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 2 Sep 2020 15:23:28 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Sep 2, 2020) In-Reply-To: References: Message-ID: >From today's meeting: * Standing Topics * Sanity * all green since last week * Gerrit Reviews in Need of Attention * rook ceph: https://review.opendev.org/#/q/status:open+branch:master+topic:%22ceph+containerization%22 * 13 patch request to review, 6 patch already reivew+2, 4 patch review+1, 3 patch is still no review idea * the 3 projects patches needs attention * stx-metal: https://review.opendev.org/#/c/737228/ * stx-puppet: https://review.opendev.org/#/c/721765/ * ansible-playbook: https://review.opendev.org/#/c/734065/ * https://review.opendev.org/#/c/728364/ suggest merge this first, this is only manifest and empty repo * it will help doing eng build once this change is merged. * Topics for this Week * brucej - how to fill the Saul-shaped hole in the Multi-OS project (yocto port)? * Saul is back, so no hole to fill! * stx.3.0.1 * 2 LPs left to cherry-pick, in progress * Mingyuan - EdgeWorker further discussion (previously "small node") * Mingyuan will send an email out to the list with the presentation * Containers Meetings * agreed to move these to be on an as-needed basis * next meeting scheduled for Sep 15 * Gopi will send details before then re: FM containerization * ARs from Previous Meetings * Aug 26 * Ildiko: poll to get a feel for which time blocks are preferred by folks for the PTG - we covered this in the TSC * Nic/Yang: feedback from test perspective on stx.4.0 lessons learned * Yong: (rough) plan for starting the Victoria rebase work - might have a better view next week, but it could be at risk for 5.0 resource-wise * Aug 19 * Scott: Docker stuff (see notes from last week) * we agree we can wait a couple more weeks, at least, to get more info re: email notifications & dashboard showing read age * AR: Nic/Yang provide more info on how many images we pull for a given sanity * AR: Release Team discuss whether or not we should just go ahead & nuke stx.2.0 now, as is our stated policy * Open Requests for Help * How to change docker default subnet?: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-August/009514.html * Austin will respond ---Done * Unable to reconfigure the edge cloud if its addition failed: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-August/009515.html * maybe someone from the Dist Cloud area could chime in on this * DANM support: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-September/009534.html * not much knowledge about what DANM is - apparently a networking thing * Build Matters (if required) * nothing this week -----Original Message----- From: Zvonar, Bill Sent: Tuesday, September 1, 2020 12:53 PM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Sep 2, 2020) Hi all, reminder of the TSC/Community call tomorrow. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200902T1400 From ildiko.vancsa at gmail.com Wed Sep 2 15:38:08 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 2 Sep 2020 17:38:08 +0200 Subject: [Starlingx-discuss] Virtual version of the hands-on workshop Message-ID: <16B2A57A-F144-47CD-B434-BBF656A823F5@gmail.com> Hi, As the virtual Open Infrastructure Summit is approaching quickly I wanted to reach out about the hands-on workshop. While the virtual format may not be the best for onboarding sessions like this it might be doable if we have people interested in experimenting with this approach. If you are interested in discussing this idea and helping out during the Summit please respond to this thread or reach out to me. We can check on the next community call as well on what people think and come to a decision. Please let me know if you have any questions. Thanks, Ildikó From mingyuan.qi at intel.com Thu Sep 3 05:10:30 2020 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Thu, 3 Sep 2020 05:10:30 +0000 Subject: [Starlingx-discuss] EdgeWorker presentation and plan In-Reply-To: References: Message-ID: Hi folks, This is the slide deck[0] that I've presented in yesterday's community call. The last part is the executive plan for stx.5.0 and later, let me know if you have questions. [0] https://drive.google.com/file/d/1DJGKG5hzN_BkvSe0xAunoDMxfPwNy7xN/view?usp=sharing Best Regards, Mingyuan -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Thu Sep 3 05:51:34 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Thu, 3 Sep 2020 05:51:34 +0000 Subject: [Starlingx-discuss] patch review for rook-ceph In-Reply-To: References: Message-ID: Hi Mary I update patch for doc. For these three patch, you could only review the first only, doc for standard multi node system deployment. I will update both three patch. https://review.opendev.org/#/c/724623/ https://review.opendev.org/#/c/742102/ https://review.opendev.org/#/c/742573/ Hi Greg I agree, move these two patch to R5 together with simple and duplex deployment. I will update late. https://review.opendev.org/#/c/742102/ https://review.opendev.org/#/c/742573/ BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, September 1, 2020 8:31 AM To: Camp, MaryX ; starlingx-discuss at lists.starlingx.io; Bailey, Henry Albert (Al) Subject: RE: patch review for rook-ceph Thanks Mary, I will update doc in this week. Martin, Chen IOTG, Software Engineer 021-61164330 From: Camp, MaryX > Sent: Tuesday, September 1, 2020 2:53 AM To: Chen, Haochuan Z >; starlingx-discuss at lists.starlingx.io; Bailey, Henry Albert (Al) > Subject: RE: patch review for rook-ceph Hi Martin, There are 5 reviews in progress for STX docs for rook-ceph. Can you please resolve the outstanding comments? Then the docs team will review again. https://review.opendev.org/#/q/status:open+project:starlingx/docs+branch:master+topic:ceph-cluster-editorial Thanks in advance, Mary Camp PTIGlobal Technical Writer | maryx.camp at intel.com From: Chen, Haochuan Z > Sent: Monday, August 31, 2020 11:16 AM To: starlingx-discuss at lists.starlingx.io; Bailey, Henry Albert (Al) > Subject: [Starlingx-discuss] patch review for rook-ceph Thanks AL review my patch for rook-ceph Appreciate more reviewer for my patch. https://review.opendev.org/#/q/topic:%22ceph+containerization%22+(status:open+OR+status:merged) Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From oliver.lovaszi at intel.com Thu Sep 3 06:49:00 2020 From: oliver.lovaszi at intel.com (Lovaszi, Oliver) Date: Thu, 3 Sep 2020 06:49:00 +0000 Subject: [Starlingx-discuss] Sanity Test Message-ID: Dear Team, Due to issues in our Jenkins test infrastructure, sanity test will be available only later. Regards, StarlinX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mingyuan.qi at intel.com Thu Sep 3 02:05:43 2020 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Thu, 3 Sep 2020 02:05:43 +0000 Subject: [Starlingx-discuss] EdgeWorker presentation and plan Message-ID: Hi folks, This is the slide deck that I've presented in yesterday's community call. The last part is the executive plan for stx.5.0 and later, let me know if you have questions. Best Regards, Mingyuan -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Edgeworker-management.pdf Type: application/pdf Size: 886441 bytes Desc: Edgeworker-management.pdf URL: From ildiko.vancsa at gmail.com Thu Sep 3 14:24:53 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 3 Sep 2020 16:24:53 +0200 Subject: [Starlingx-discuss] Combined PL/TL/TSC Election Season Message-ID: Hi StarlingX Community, The second election season is starting in just a month from now. This email contains important information about the elections, please read carefully. For all the details on the elections please visit: https://docs.starlingx.io/election/ The nomination period officially begins on __October 6, 2020, 20:45 UTC__. Please read the stipulations and timelines for candidates and electorate contained in the above governance documentation. IMPORTANT NOTE: as we started this practice a year ago if you would like to run for any open position you need to register as an OpenStack Foundation Individual Member prior to when the nomination period starts. Also please note that you are required to confirm your preferred email address in Gerrit by __September 20, 2020 00:00 UTC__ as described here: https://docs.starlingx.io/election/#electorate to make sure ballots are sent out to the correct addresses. As decided by the TSC group and the election officials the 2020, H2 PL/TL and TSC elections will run concurrently; deadlines for their nomination and voting activities are synchronized but will still use separate ballots. Please note, if only one candidate is nominated as PL or TL for a project team during the PL/TL nomination period, that candidate will win by acclaim, and there will be no poll. There will only be a poll if there is more than one candidate stepping forward for a project team's PL or TL position. There will be further announcements posted to the mailing list as action is required from the electorate or candidates. This email is for information purposes only. If you have any questions which you feel affect others please reply to this email thread. If you have any questions that you which to discuss in private please email any of the election officials[1] so that we may address your concerns. Thank you, [1] https://docs.starlingx.io/election/#election-officials From maryx.camp at intel.com Thu Sep 3 17:14:33 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Thu, 3 Sep 2020 17:14:33 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-08-19 In-Reply-To: <20200901173859.yggznqtd4uadq2n7@yuggoth.org> References: <20200820160118.ilnaqgukaqh2oraj@yuggoth.org> <20200831200707.ik2usiqak37mconr@yuggoth.org> <20200901173859.yggznqtd4uadq2n7@yuggoth.org> Message-ID: Hi Jeremy, Heads-up that I'm replying to your 2 most recent messages in this 1 email. Hoping that the text makes sense. http://lists.starlingx.io/pipermail/starlingx-discuss/2020-August/009530.html [...] Thanks, examples are very useful since it's often easier to do a bit of reverse engineering to find out how it got implemented. In this case I see the problem straight away. The Sphinx extension which identifies the version names can be found here: [Forgive the long permalink, it's for posterity since this discussion will live in the ML archive long after the file in Git has changed.] As you can see, that script is, at documentation build time, scraping the project repository's branch list to find any which start with the prefix "stable" (an OpenStack convention) so that it can figure out what "interesting_series" to return in the _get_other_versions() function. That entire extension is, quite frankly, full of OpenStackisms. I can imagine two solutions to this: expand the extension's scope or fork it. I suppose there's also a middle ground where we extract the OpenStackisms from ext.py into a separate replaceable module and then we'd only need to fork that module. I'll see if anybody in the OpenStack Technical Writing SIG has an opinion on whether the scope expansion or refactoring solutions would be acceptable to them, since they're co-maintainers of openstackdocstheme (along with the OpenStack Oslo team). Ultimately, though, if you're considering eventually forking all of openstackdocstheme anyway, this might be the change which pushes that decision over the edge. [...] [MaryC ] In the STX docs meeting yesterday, we discussed your suggestion about forking the theme into the STX docs repo. The team agrees that this is the right time to implement it. Your guidance/help with this process is really appreciated. http://lists.starlingx.io/pipermail/starlingx-discuss/2020-September/009543.html [...] In drafting https://review.opendev.org/749369 to implement this alternative matching, it has dawned on me that I'm not entirely clear from the above what your expectations are when publishing. In short, are you publishing from a branch or from a tag? If the former, then the r/stx.4.0 branch's documentation would presumably be published under R4.0 not R4.01. Was that a typo, or is there some missing bit of detail to determine the publication directory from the branch? [...] [MaryC ] We want to publish from a branch (not tags) and use the branch naming convention. "R4.01" was a typo in my original email. Corrected text: Our planned URL structures are: https://docs.starlingx.io/R4.0 (current release) and https://docs.starlingx.io/latest for the master branch. Please let me know about next steps and recommended actions. As an aside, since you mentioned these threads will live on in the ML archives forever, I'm wondering what the etiquette is for modifying the message subject line to be more relevant/useful? Maybe adding a descriptor to the end of the subject, like [theme]? Thanks again, Mary C. From maryx.camp at intel.com Thu Sep 3 17:15:48 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Thu, 3 Sep 2020 17:15:48 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-09-02 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST.   [1]   Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings   [2]   Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2020-09-02 All -- reviews merged since last meeting: 1 All -- bug status -- 6 total - team agrees to defer all low priority LP until the upstreaming effort is completed. Reviews in progress: Several reviews related to Rook are ready to review per discuss list message: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-August/009452.html Pinged Martin Chen to respond to review comments for these reviews: https://review.opendev.org/#/q/status:open+project:starlingx/docs+branch:master+topic:ceph-cluster-editorial All -- Opens Can the test team be looped in to test some of our complicated procedures (ie install/deployment guides)? Greg and Mary attended Test meeting this week. Propose we use launchpads for test request. Greg/Mary to create launchpads for explict testing, and provide query to test team. Test team will review the backlog and have them discussed and assigned in test meeting. Upstreaming WR docs status Multiple WIP reviews now. Substitutions file -- https://review.opendev.org/#/c/748747/ Ron will resubmit patch without the switch -- team agreed to use 1 strings file and agreed to the suggestions in the strings file. General discussion about strings/substitutions: Need to be sure that any non-STX doc builds don't replace the existing copyright/legal statements that refer to STX. As we upstream docs, be aware about replacing WR (or removing naming entirely) in the STX docs. Ron to check with Drake and Keane if their reviews are ready for actual review or still in testing mode. Still fiddling with the generator that will do bulk of the work. Goal is to have tool do more of the grunt work (manual search & replace, etc). Another update next week. Keep submitting reviews in small-ish chunks to be sure we catch any generator issues. Display multiple versions of STX docs More messages with Jeremy Stanley on discuss list, portions copied below for convenience during meeting discussion: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-August/009530.html That entire extension is, quite frankly, full of OpenStackisms. I can imagine two solutions to this: expand the extension's scope or fork it. I suppose there's also a middle ground where we extract the OpenStackisms from ext.py into a separate replaceable module and then we'd only need to fork that module. I'll see if anybody in the OpenStack Technical Writing SIG has an opinion on whether the scope expansion or refactoring solutions would be acceptable to them, since they're co-maintainers of openstackdocstheme (along with the OpenStack Oslo team). Ultimately, though, if you're considering eventually forking all of openstackdocstheme anyway, this might be the change which pushes that decision over the edge. Team discussion: Ildiko pointed out that the OpenStack theme is more "locked" and harder to tweak, it needs to be released for any updates. Our theme could be more flexible if it was completely our own. Bruce agrees. OpenStack folks are more involved with infra/tools because it's more complex. Our needs will be simpler for the most part, even long term. AR Mary to reply to Jeremy that we want to implement the fork option. http://lists.starlingx.io/pipermail/starlingx-discuss/2020-September/009543.html > The STX docs repo already has an R4 branch: > https://opendev.org/starlingx/docs/src/branch/r/stx.4.0 so that part > is done. Our planned URL structures are: > https://docs.starlingx.io/R4.01 (current release) and > https://docs.starlingx.io/latest for the master branch. [...] In drafting https://review.opendev.org/749369 to implement this alternative matching, it has dawned on me that I'm not entirely clear from the above what your expectations are when publishing. In short, are you publishing from a branch or from a tag? If the former, then the r/stx.4.0 branch's documentation would presumably be published under R4.0 not R4.01. Was that a typo, or is there some missing bit of detail to determine the publication directory from the branch? AR Mary to reply to Jeremy: We want to publish from a branch (not tags) and use the branch naming convention. From alexandru.dimofte at intel.com Thu Sep 3 17:37:06 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 3 Sep 2020 17:37:06 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200902T134605Z Message-ID: Sanity Test from 2020-September-02 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200902T134605Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200902T134605Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal 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 06 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From fungi at yuggoth.org Thu Sep 3 17:44:54 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 3 Sep 2020 17:44:54 +0000 Subject: [Starlingx-discuss] [docs][meeting] Docs site theme (was: Docs team notes 2020-08-19) In-Reply-To: References: <20200820160118.ilnaqgukaqh2oraj@yuggoth.org> <20200831200707.ik2usiqak37mconr@yuggoth.org> <20200901173859.yggznqtd4uadq2n7@yuggoth.org> Message-ID: <20200903174454.vec4rolbndzcor7a@yuggoth.org> On 2020-09-03 17:14:33 +0000 (+0000), Camp, MaryX wrote: [...] > In the STX docs meeting yesterday, we discussed your suggestion > about forking the theme into the STX docs repo. The team agrees > that this is the right time to implement it. Your guidance/help > with this process is really appreciated. [...] My pleasure. Probably the place to start is copying the files from the openstackdocstheme subdirectory of the openstack/openstackdocstheme repository into the appropriate locations for the doc/source tree of the starlingx/docs repository. The up side to this move is that it will be tested completely with draft renderings we can check over before it's ever approved and deployed. I'll abandon https://review.opendev.org/749369 but we'll want to make sure to incorporate a similar change into the new extension script in starlingx/docs. > We want to publish from a branch (not tags) and use the branch > naming convention. "R4.01" was a typo in my original email. > Corrected text: Our planned URL structures are: > https://docs.starlingx.io/R4.0 (current release) and > https://docs.starlingx.io/latest for the master branch. Great, thanks confirming! That will make all this a lot simpler than trying to derive version numbers from something other than the branch name. > Please let me know about next steps and recommended actions. I outlined the general idea above, but the specifics will probably take as much effort to write up as it would to just push an initial attempt myself. I can have something up for review in the next day or so with copies of the files in the places I expect they should go, but I'm also no expert when it comes to Sphinx so am just as happy for someone else to give it a shot instead, if there are any volunteers for that (in which case I'll gladly help review and debug the result). > As an aside, since you mentioned these threads will live on in the > ML archives forever, I'm wondering what the etiquette is for > modifying the message subject line to be more relevant/useful? > Maybe adding a descriptor to the end of the subject, like [theme]? The conventional way, which I've done just now in this reply, is to replace the subject but follow it with all or some of the old subject in parentheses with a preceding "was:" to indicate this is a subthread of the original discussion topic. The OpenStack community documents this in their wiki article on Mailing List Etiquette, though it's really just a long-standing entrenched tradition on most of the technical mailing lists to which I've ever subscribed: https://wiki.openstack.org/wiki/MailingListEtiquette#Changing_Subject -- 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 fungi at yuggoth.org Thu Sep 3 18:01:05 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 3 Sep 2020 18:01:05 +0000 Subject: [Starlingx-discuss] [docs][meeting] Docs site theme (was: Docs team notes 2020-08-19) In-Reply-To: <20200903174454.vec4rolbndzcor7a@yuggoth.org> References: <20200820160118.ilnaqgukaqh2oraj@yuggoth.org> <20200831200707.ik2usiqak37mconr@yuggoth.org> <20200901173859.yggznqtd4uadq2n7@yuggoth.org> <20200903174454.vec4rolbndzcor7a@yuggoth.org> Message-ID: <20200903180105.pyx6uf4rqwbqucz6@yuggoth.org> On 2020-09-03 17:14:33 +0000 (+0000), Camp, MaryX wrote: [...] > In the STX docs meeting yesterday, we discussed your suggestion > about forking the theme into the STX docs repo. The team agrees > that this is the right time to implement it. [...] Oh, one other upshot I likely missed mentioning (since it didn't dawn on me until just now), putting the theme in a branched repository and building documentation from each branch will require that the theme implementation gets backported to the existing branches, and any changes you make to theming over time would also need to be backported accordingly to maintain consistency. It's probably not a big deal since those files are unlikely to ever diverge, only become outdated, so as long as you backport each change to the theme and extensions it should be trivial to maintain. Still, it *is* one more thing to remember when proposing, reviewing, and approving changes for those files. -- 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 Ghada.Khalil at windriver.com Thu Sep 3 18:13:40 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 3 Sep 2020 18:13:40 +0000 Subject: [Starlingx-discuss] Looking for contributors to stx.5.0 Message-ID: Hello community members, The StarlingX release team has started the planning for the next major stx release (stx.5.0). We are looking for contributors to a number of key features: - Python3 - CentOS 8 Rebase - Openstack Rebase to Victoria If you are interested in contributing, please reach out to myself, Bill Zvonar or Bruce Jones. For a list of candidate features, see: https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=1107209846 Story Board: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.5.0 Regards, Ghada From Ghada.Khalil at windriver.com Thu Sep 3 18:22:07 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 3 Sep 2020 18:22:07 +0000 Subject: [Starlingx-discuss] stx.3.0.1 maintenance release - build request Message-ID: Hi Davlet, The required code for stx.3.0.1 hass been cherrypicked to the r/stx.3.0 branch. Please start an RC build for the stx.3.0.1 maintenance release. Hi Nick, Once the build is available, please arrange for a sanity and some regression. A list of fixes can be seen in the branch [0]. Thanks, Ghada Reference: [0] https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.3.0 From maryx.camp at intel.com Thu Sep 3 18:36:37 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Thu, 3 Sep 2020 18:36:37 +0000 Subject: [Starlingx-discuss] [docs][meeting] Docs site theme (was: Docs team notes 2020-08-19) Message-ID: > I outlined the general idea above, but the specifics will probably take as much effort to write up as it would to just push an initial attempt myself. I can have something up for review in the next day or so with copies of the files in the places I expect they should go, but I'm also no expert when it comes to Sphinx so am just as happy for someone else to give it a shot instead, if there are any volunteers for that (in which case I'll gladly help review and debug the result). Speaking for the Docs team, we 100% accept your offer to push the first review yourself! I will help with debug and testing as we figure out all the bits & pieces to be modified. Please shout if you need anything from me. -Mary C. From Ghada.Khalil at windriver.com Thu Sep 3 19:11:37 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 3 Sep 2020 19:11:37 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Aug 27/2020 & Sept 3/2020 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Sep 3 2020 - stx.3.0.1 - All required code has been cherry-picked. - Ghada to send an email to Davlet to build a new stx.3.0.1 RC build and cc Nick for sanity/regression. - stx.5.0 - Major features are still un-resourced. - Email sent to solicit community contributions - Bill will add this topic on the next TSC call - Feature Candidate List: https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=1107209846 - Story Board: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.5.0 Release Team Meeting - Aug 27 2020 - stx.3.0.1 - Not much progress on the cherrypicks. Bill will follow up this week and we'll decide by Monday if we go ahead. - Next step is to ask Davlet to build the candidate build - Need to line up the test team for sanity and possibly some targeted regression based on the commits - stx.5.0 - What do we want to change going forward? - Setup of CENGN Replica Environment - Brought up in the stx.4.0 retrospective by Yong and seconded by Scott - Action: Frank/Scott/Build team to make a recommendation on how to make this easier moving forward - stx.5.0 test initiatives?? - Want feedback from Nick and Yang - Release Risks - Feature Candidate List: https://docs.google.com/spreadsheets/d/1JbOQELqXG_GDoP1jo6YoRDytpTkJEs89TVimzvrqc_A/edit#gid=1107209846 - Major features are still not resourced - Python3 - Openstack Rebase to Victoria - CentOS 8 Rebase - Share with the community and solicit community contributions for stx.5.0 - Also raise on the TSC call in two weeks as the unresourced features are table-stakes for the release From build.starlingx at gmail.com Fri Sep 4 01:08:55 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 3 Sep 2020 21:08:55 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_retag_docker_images - Build # 190 - Still Failing! In-Reply-To: <1753453581.0.1598932143011.JavaMail.javamailuser@localhost> References: <1753453581.0.1598932143011.JavaMail.javamailuser@localhost> Message-ID: <1519730272.21.1599181736417.JavaMail.javamailuser@localhost> Project: STX_retag_docker_images Build #: 190 Status: Still Failing Timestamp: 20200904T010853Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200903T190312Z/logs -------------------------------------------------------------------------------- Parameters HOST_PORT: 80 OLD_LATEST_PREFIX: master WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-3.0/20200903T190312Z OS: centos MY_REPO: /localdisk/designer/jenkins/rc-3.0/cgcs-root BASE_VERSION: rc-3.0-stable-20200903T190312Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200903T190312Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: rc-3.0 PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/3.0/centos/20200903T190312Z/logs RETAG_IMAGE_LIST: stx-fm-rest-api stx-libvirt stx-mariadb FLOCK_VERSION: rc-3.0-centos-stable-20200903T190312Z PREFIX: rc-3.0 TIMESTAMP: 20200903T190312Z BUILD_STREAM: dev REGISTRY_ORG: slittlewrs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/rc/3.0/centos/20200903T190312Z/outputs REGISTRY: docker.io OLD_BUILD_STREAM: stable From oliver.lovaszi at intel.com Fri Sep 4 12:57:29 2020 From: oliver.lovaszi at intel.com (Lovaszi, Oliver) Date: Fri, 4 Sep 2020 12:57:29 +0000 Subject: [Starlingx-discuss] =?utf-8?q?_Sanity_Master_Test_LAYERED_build_I?= =?utf-8?q?SO_20200904T013=E2=80=8B234Z?= Message-ID: Sanity Test from 2020-Spetember-4 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200904T013234Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200904T013234Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Fri Sep 4 17:51:48 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Fri, 4 Sep 2020 17:51:48 +0000 Subject: [Starlingx-discuss] [docs][meeting] Docs site theme (was: Docs team notes 2020-08-19) In-Reply-To: References: Message-ID: <20200904175148.pt4nzkbznbgbbohc@yuggoth.org> On 2020-09-03 18:36:37 +0000 (+0000), Camp, MaryX wrote: [...] > Speaking for the Docs team, we 100% accept your offer to push the > first review yourself! I will help with debug and testing as we > figure out all the bits & pieces to be modified. Please shout if > you need anything from me. Doing my best not to dispel your (arguably misplaced) faith in my abilities here, I've pushed up the beginnings of a series of changes to make this happen: https://review.opendev.org/750005 https://review.opendev.org/750006 The resulting preview from the docs build result on 750006 should be using only the in-repo starlingxdocs theme and associated starlingx Sphinx extension (both copied from openstackdocstheme with only the most minimal adjustments made to get the build working). Still to do are incorporating the branch selection change I abandoned for openstackdocstheme earlier, and also there's still tons of openstackdocs references which can be cleaned up and replaced, as well as code handling OpenStack-specific workflows and layouts which can be safely removed to simplify what's there. Also, fair warning, I haven't even looked at the results yet other than to make sure Sphinx can build the project locally on my workstation, so this first iteration may have plenty of cosmetic fixes needed for all I know. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From build.starlingx at gmail.com Fri Sep 4 18:51:12 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 4 Sep 2020 14:51:12 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 274 - Failure! Message-ID: <810396970.24.1599245472791.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 274 Status: Failure Timestamp: 20200904T155519Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200904T151627Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20200904T151627Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20200904T151627Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200904T151627Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20200904T151627Z/logs PUBLISH_TIMESTAMP: 20200904T151627Z FLOCK_VERSION: master-centos-stable-20200904T151627Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20200904T151627Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20200904T151627Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Fri Sep 4 18:51:14 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 4 Sep 2020 14:51:14 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images_layered - Build # 47 - Failure! Message-ID: <1938208517.27.1599245474982.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 47 Status: Failure Timestamp: 20200904T153535Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200904T151627Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20200904T151627Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200904T151627Z/logs MASTER_BUILD_NUMBER: 68 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20200904T151627Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20200904T151627Z DOCKER_BUILD_ID: jenkins-master-containers-20200904T151627Z-builder TIMESTAMP: 20200904T151627Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20200904T151627Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20200904T151627Z/outputs From build.starlingx at gmail.com Fri Sep 4 18:51:16 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 4 Sep 2020 14:51:16 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_containers_master_master - Build # 68 - Failure! Message-ID: <2002320276.30.1599245477330.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 68 Status: Failure Timestamp: 20200904T151627Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200904T151627Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From alexandru.dimofte at intel.com Sat Sep 5 11:06:49 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 5 Sep 2020 11:06:49 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200904T140446Z Message-ID: Sanity Test from 2020-September-04 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200904T140446Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200904T140446Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal 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 06 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From ebiibe82 at gmail.com Mon Sep 7 08:34:14 2020 From: ebiibe82 at gmail.com (Amit Mahajan) Date: Mon, 7 Sep 2020 14:04:14 +0530 Subject: [Starlingx-discuss] Regarding installation of controller-0 from PXE boot server Message-ID: Hi All, Is there any documentation which can guide on setting up a StarlingX PXE boot server so that I can install controller-0 from this PXE server? Regards, Amit -------------- next part -------------- An HTML attachment was scrubbed... URL: From ebiibe82 at gmail.com Mon Sep 7 11:10:38 2020 From: ebiibe82 at gmail.com (Amit Mahajan) Date: Mon, 7 Sep 2020 16:40:38 +0530 Subject: [Starlingx-discuss] Regarding stx-openstack aplication deployment in R4.0 Message-ID: Hi All, We are deploying *StarlingX R4.0 Duplex Bare metal mode*. While downloading stx-openstack applications manifests and helm-charts from the public domain (CENGN StarlingX mirror ), we got to the “4.0.1” release folder. Exploring it further, we found that “ stx-openstack-1.0-49-centos-stable-versioned.tgz” was placed at following two locations. 1. http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/ containers /outputs/helm-charts/stx-openstack-1.0-49-centos-stable-versioned.tgz 2. http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/ flock /outputs/helm-charts/stx-openstack-1.0-49-centos-stable-versioned.tgz Both the “stx-openstack-1.0-49-centos-stable-versioned.tgz” placed at above paths are different (checked md5 checksum). We explored a couple of charts (heat and neutron) inside these tgz files, but only difference was in *requirement.lock *and that too was only in the time of generation. However, *plugins/k8sapp_openstack-1.0-py2.py3-none-any.whl *seems different in both these files. Considering the plugin related differences, please suggest which one should be used for deploying the stx-openstack application. Regards, Amit -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon Sep 7 12:07:19 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 7 Sep 2020 08:07:19 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 275 - Still Failing! In-Reply-To: <2083858346.22.1599245470703.JavaMail.javamailuser@localhost> References: <2083858346.22.1599245470703.JavaMail.javamailuser@localhost> Message-ID: <199343135.33.1599480440062.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 275 Status: Still Failing Timestamp: 20200907T080135Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200907T043000Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200907T043000Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root BASE_VERSION: master-stable-20200907T043000Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200907T043000Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200907T043000Z/logs PUBLISH_TIMESTAMP: 20200907T043000Z FLOCK_VERSION: master-centos-stable-20200907T043000Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20200907T043000Z BUILD_STREAM: stable REGISTRY_ORG: slittlewrs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200907T043000Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Mon Sep 7 12:07:21 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 7 Sep 2020 08:07:21 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 268 - Failure! Message-ID: <1540471330.36.1599480442431.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 268 Status: Failure Timestamp: 20200907T074127Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200907T043000Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200907T043000Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200907T043000Z/logs MASTER_BUILD_NUMBER: 666 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200907T043000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/monolithic PUBLISH_TIMESTAMP: 20200907T043000Z DOCKER_BUILD_ID: jenkins-master-20200907T043000Z-builder TIMESTAMP: 20200907T043000Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200907T043000Z/inputs LAYER: PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200907T043000Z/outputs From build.starlingx at gmail.com Mon Sep 7 12:07:24 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 7 Sep 2020 08:07:24 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 666 - Failure! Message-ID: <1077409017.39.1599480444764.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 666 Status: Failure Timestamp: 20200907T043000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200907T043000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From zhipengs.liu at intel.com Tue Sep 8 02:44:46 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 8 Sep 2020 02:44:46 +0000 Subject: [Starlingx-discuss] Regarding stx-openstack aplication deployment in R4.0 In-Reply-To: References: Message-ID: Hi Mahajan, You should use the second one. 1. http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/helm-charts/stx-openstack-1.0-49-centos-stable-versioned.tgz Thanks! Zhipeng From: Amit Mahajan Sent: 2020年9月7日 19:11 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Regarding stx-openstack aplication deployment in R4.0 Hi All, We are deploying StarlingX R4.0 Duplex Bare metal mode. While downloading stx-openstack applications manifests and helm-charts from the public domain (CENGN StarlingX mirror), we got to the “4.0.1” release folder. Exploring it further, we found that “stx-openstack-1.0-49-centos-stable-versioned.tgz” was placed at following two locations. 1. http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/containers/outputs/helm-charts/stx-openstack-1.0-49-centos-stable-versioned.tgz 2. http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/helm-charts/stx-openstack-1.0-49-centos-stable-versioned.tgz Both the “stx-openstack-1.0-49-centos-stable-versioned.tgz” placed at above paths are different (checked md5 checksum). We explored a couple of charts (heat and neutron) inside these tgz files, but only difference was in requirement.lock and that too was only in the time of generation. However, plugins/k8sapp_openstack-1.0-py2.py3-none-any.whl seems different in both these files. Considering the plugin related differences, please suggest which one should be used for deploying the stx-openstack application. Regards, Amit -------------- next part -------------- An HTML attachment was scrubbed... URL: From ebiibe82 at gmail.com Tue Sep 8 05:06:32 2020 From: ebiibe82 at gmail.com (Amit Mahajan) Date: Tue, 8 Sep 2020 10:36:32 +0530 Subject: [Starlingx-discuss] Regarding stx-openstack aplication deployment in R4.0 In-Reply-To: References: Message-ID: Hi Liu, Thanks for the reply. But what is the use of the application placed in the "containers" folder? On Tue, Sep 8, 2020 at 8:14 AM Liu, ZhipengS wrote: > Hi Mahajan, > > > > You should use the second one. > > 1. > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/ > flock > /outputs/helm-charts/stx-openstack-1.0-49-centos-stable-versioned.tgz > > > Thanks! > > Zhipeng > > > > *From:* Amit Mahajan > *Sent:* 2020年9月7日 19:11 > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Regarding stx-openstack aplication > deployment in R4.0 > > > > Hi All, > > > > We are deploying *StarlingX R4.0 Duplex Bare metal mode*. > > > > While downloading stx-openstack applications manifests and helm-charts > from the public domain (CENGN StarlingX mirror > ), we got to the > “4.0.1” release folder. Exploring it further, we found that “stx-openstack-1.0-49-centos-stable-versioned.tgz” > was placed at following two locations. > > 1. > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/ > containers > /outputs/helm-charts/stx-openstack-1.0-49-centos-stable-versioned.tgz > > 2. > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/ > flock > /outputs/helm-charts/stx-openstack-1.0-49-centos-stable-versioned.tgz > > > Both the “stx-openstack-1.0-49-centos-stable-versioned.tgz” placed at > above paths are different (checked md5 checksum). We explored a couple of > charts (heat and neutron) inside these tgz files, but only difference was > in *requirement.lock *and that too was only in the time of generation. > However, *plugins/k8sapp_openstack-1.0-py2.py3-none-any.whl *seems > different in both these files. Considering the plugin related differences, please > suggest which one should be used for deploying the stx-openstack > application. > > > > Regards, > > Amit > -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Sep 8 05:54:00 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 8 Sep 2020 01:54:00 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 276 - Still Failing! In-Reply-To: <722985961.31.1599480437378.JavaMail.javamailuser@localhost> References: <722985961.31.1599480437378.JavaMail.javamailuser@localhost> Message-ID: <901499732.42.1599544440959.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 276 Status: Still Failing Timestamp: 20200908T014554Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200908T010849Z/logs -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20200908T010849Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20200908T010849Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200908T010849Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20200908T010849Z/logs PUBLISH_TIMESTAMP: 20200908T010849Z FLOCK_VERSION: master-centos-stable-20200908T010849Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20200908T010849Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20200908T010849Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Tue Sep 8 05:54:03 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 8 Sep 2020 01:54:03 -0400 (EDT) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images_layered - Build # 48 - Still Failing! In-Reply-To: <386173047.25.1599245473368.JavaMail.javamailuser@localhost> References: <386173047.25.1599245473368.JavaMail.javamailuser@localhost> Message-ID: <2121039249.45.1599544444507.JavaMail.javamailuser@localhost> Project: STX_build_docker_images_layered Build #: 48 Status: Still Failing Timestamp: 20200908T012742Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200908T010849Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20200908T010849Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200908T010849Z/logs MASTER_BUILD_NUMBER: 69 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20200908T010849Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20200908T010849Z DOCKER_BUILD_ID: jenkins-master-containers-20200908T010849Z-builder TIMESTAMP: 20200908T010849Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20200908T010849Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20200908T010849Z/outputs From build.starlingx at gmail.com Tue Sep 8 05:54:06 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 8 Sep 2020 01:54:06 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_containers_master_master - Build # 69 - Still Failing! In-Reply-To: <373615781.28.1599245475618.JavaMail.javamailuser@localhost> References: <373615781.28.1599245475618.JavaMail.javamailuser@localhost> Message-ID: <1789260043.48.1599544446688.JavaMail.javamailuser@localhost> Project: STX_build_layer_containers_master_master Build #: 69 Status: Still Failing Timestamp: 20200908T010849Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200908T010849Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false From yong.hu at intel.com Tue Sep 8 08:04:45 2020 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 8 Sep 2020 08:04:45 +0000 Subject: [Starlingx-discuss] StarlingX Distro-OpenStack: Bi-weekly Project Meeting Message-ID: Hi guys, We are going to have meeting with 3 major items on the agenda: 1. Community election for PL/TL and TSC. 2. Call for contributors for OpenStack upgrade from “U” to “V”. 3. LP review for 3.x/4.x maintenance releases and 5.0. Anyone who is interested in this, please join us. Regards, Yong From: yong.hu at intel.com When: 9:00 PM - 9:30 PM September 8, 2020 Subject: StarlingX Distro-OpenStack: Bi-weekly Project Meeting Location: https://zoom.us/j/342730236 Hi folks, This is a new series of bi-weekly project meeting on StarlingX Distro-OpenStack. Your participation to this meeting and/or other offline contribution by all means are highly appreciated! Join the meeting: https://zoom.us/j/342730236 Project Team Etherpad: https://etherpad.openstack.org/p/stx-distro-openstack-meetings PS: from now to next summer early, we are going to keep this time slot to accommodate US standard time (6:00 AM in the morning). regards, Yong Hu -------------- next part -------------- An HTML attachment was scrubbed... URL: From sharath.kumar at intel.com Tue Sep 8 13:49:25 2020 From: sharath.kumar at intel.com (Kumar, Sharath) Date: Tue, 8 Sep 2020 13:49:25 +0000 Subject: [Starlingx-discuss] How to use Tox in the flock layer for adding new dashboard plugin for starlingx dashboard In-Reply-To: References: Message-ID: Hi Team, I would like to check with the community regarding use of Tox framework in the flock layer. It is available under distro layer for building changes on openstack_dashboard but missing in the flok layer. Any help how to setup and use tox and its dependencies under flock layer to make changes on starlingx dashboard? Regards, Sharath -------------- next part -------------- An HTML attachment was scrubbed... URL: From Davlet.Panech at windriver.com Tue Sep 8 14:06:52 2020 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Tue, 8 Sep 2020 14:06:52 +0000 Subject: [Starlingx-discuss] stx.3.0.1 maintenance release - build request In-Reply-To: References: Message-ID: A candidate 3.0.x build has completed and can be tested now. ________________________________ From: Khalil, Ghada Sent: September 3, 2020 2:22 PM To: Panech, Davlet ; Jascanu, Nicolae Cc: 'starlingx-discuss at lists.starlingx.io' Subject: stx.3.0.1 maintenance release - build request Hi Davlet, The required code for stx.3.0.1 hass been cherrypicked to the r/stx.3.0 branch. Please start an RC build for the stx.3.0.1 maintenance release. Hi Nick, Once the build is available, please arrange for a sanity and some regression. A list of fixes can be seen in the branch [0]. Thanks, Ghada Reference: [0] https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.3.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Tue Sep 8 14:33:26 2020 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 8 Sep 2020 14:33:26 +0000 Subject: [Starlingx-discuss] How to use Tox in the flock layer for adding new dashboard plugin for starlingx dashboard In-Reply-To: References: , Message-ID: I assume you are looking at starlingx_dashboard. It looks like only pylint is setup for that repo. It has dependencies on many other repos (due to the use of their clients) so if you have setup your dev environment using 'repo' commands on the manifest, it should find those directories and be able to run tox. https://github.com/starlingx/gui/blob/master/.zuul.yaml#L30 I don't think you need to set the STX_DC_CLIENT env variable in a normal 'repo' dev env. Al ________________________________ From: Kumar, Sharath Sent: Tuesday, September 8, 2020 9:49 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] How to use Tox in the flock layer for adding new dashboard plugin for starlingx dashboard Hi Team, I would like to check with the community regarding use of Tox framework in the flock layer. It is available under distro layer for building changes on openstack_dashboard but missing in the flok layer. Any help how to setup and use tox and its dependencies under flock layer to make changes on starlingx dashboard? Regards, Sharath -------------- next part -------------- An HTML attachment was scrubbed... URL: From yang.liu at windriver.com Tue Sep 8 15:25:31 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Tue, 8 Sep 2020 15:25:31 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 09/08/2020 Message-ID: Agenda/meeting notes are posted here: https://etherpad.openstack.org/p/stx-test Agenda for 9/8/2020 Attendees: Yang, Oliver, Nic · Sanity Status: * Sep 4 build was green * No new build since then - build team is investigating · stx3.1 testing: * Nic's team: Internal test jenkins server is down and is being worked on to bring it back · stx4.0 testing: * CNCF Sonobuoy § It's getting docker images from docker.io directly, Nic has not figured out the recipe for installing Sonobuoy § Nic's team will continue to investigate § Yang's team will try sonobuoy test in the meantime due to tight timeline · Open topics: * Doc testing § What is procedure to request Doc testing? · Most of new contents are tracked via launchpads or task under a story if designer is going to add the doc · Greg/Mary to create launchpads for explict testing, and provide query to test team. The backlog will be discussed and assigned in test meeting · Doc test LP will be assigned to Yang or Nic for triage * Automation: § Move daily sanity from robot to pytest § Unified sanity - make use of original pytest sanity test cases · Review the setups for openstack neutron § Convert existing robot tests to pytest if not already exists in pytest * Test In the Open § Build team is working on generating Qcow image § Nic and Yang's team will work together to prototype test in the open with 1 SX vm -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jolliffe at windriver.com Tue Sep 8 15:47:34 2020 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Tue, 8 Sep 2020 15:47:34 +0000 Subject: [Starlingx-discuss] TSC resignation - Ian Message-ID: <397EF83A-71A4-4440-A14D-A92E30D1BE7B@windriver.com> Hi StarlingX Community; As I mentioned at a TSC call a few weeks ago, after much consideration I have decided to pursue a new career opportunity. As a result, I will no longer be able to serve the community on the StarlingX TSC. I am very proud of what the community has accomplished over the past 2 years and look forward to seeing even more adoption and impact from this great project. Thank you for the good times, friendships and all that we have accomplished as a community. Best Regards; Ian -------------- next part -------------- An HTML attachment was scrubbed... URL: From Akshay.346 at hsc.com Fri Sep 4 07:32:28 2020 From: Akshay.346 at hsc.com (Akshay 346) Date: Fri, 4 Sep 2020 07:32:28 +0000 Subject: [Starlingx-discuss] StarlingX 4.0 stx-application manifest and helm-charts issue. Message-ID: Hello Team, I was deploying StarlingX R4.0 Duplex Bare metal mode. While getting "stx-application" manifests and helm-charts from the public domain, I was not able to find "4.0.0" folder under "release", also I tried looking into "4.0.1" release but did not find the mentioned path i.e. "centos/outputs/helm-charts" under it. I found "stx-openstack-1.0-49-centos-stable-versioned.tgz" under two folders in "4.0.1" release. These are : - http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/containers/outputs/helm-charts/stx-openstack-1.0-49-centos-stable-versioned.tgz - http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/helm-charts/stx-openstack-1.0-49-centos-stable-versioned.tgz Both the "stx-openstack-1.0-49-centos-stable-versioned.tgz" placed at above paths are different. (Checked with md5sum) Please suggest me which one to use. Regards Akshay DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Sep 8 21:27:05 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 8 Sep 2020 17:27:05 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_retag_docker_images - Build # 191 - Still Failing! In-Reply-To: <1418171.19.1599181734076.JavaMail.javamailuser@localhost> References: <1418171.19.1599181734076.JavaMail.javamailuser@localhost> Message-ID: <523423154.53.1599600426581.JavaMail.javamailuser@localhost> Project: STX_retag_docker_images Build #: 191 Status: Still Failing Timestamp: 20200908T212703Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200908T174218Z/logs -------------------------------------------------------------------------------- Parameters HOST_PORT: 80 OLD_LATEST_PREFIX: master WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20200908T174218Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20200908T174218Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200908T174218Z/logs REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20200908T174218Z/logs RETAG_IMAGE_LIST: stx-fm-rest-api stx-libvirt stx-mariadb FLOCK_VERSION: master-centos-stable-20200908T174218Z PREFIX: master TIMESTAMP: 20200908T174218Z BUILD_STREAM: dev REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20200908T174218Z/outputs REGISTRY: docker.io OLD_BUILD_STREAM: stable From pvmpublic at gmail.com Wed Sep 9 01:44:23 2020 From: pvmpublic at gmail.com (Pratik M.) Date: Wed, 9 Sep 2020 07:14:23 +0530 Subject: [Starlingx-discuss] StarlingX 4.0 stx-application manifest and helm-charts issue. In-Reply-To: References: Message-ID: Hi, Pl use the flock variant. See: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-September/009583.html Thanks On Tue, 8 Sep, 2020, 23:40 Akshay 346, wrote: > Hello Team, > > > > I was deploying *StarlingX R4.0 Duplex Bare metal mode*. > > While getting “stx-application” manifests and helm-charts from the public > domain, I was not able to find “4.0.0” folder under “release”, also I tried > looking into “4.0.1” release but did not find the mentioned path i.e. “ > *centos/outputs/helm-charts*” under it. > > I found “*stx-openstack-1.0-49-centos-stable-versioned.tgz*” under two folders in “4.0.1” release. These are : > > - http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/*containers*/outputs/helm-charts/stx-openstack-1.0-49-centos-stable-versioned.tgz > > - http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/*flock*/outputs/helm-charts/stx-openstack-1.0-49-centos-stable-versioned.tgz > > > > Both the “stx-openstack-1.0-49-centos-stable-versioned.tgz” placed at > above paths are different. (Checked with md5sum) > > > > Please suggest me which one to use. > > > > Regards > > Akshay > DISCLAIMER: This electronic message and all of its contents, contains > information which is privileged, confidential or otherwise protected from > disclosure. The information contained in this electronic mail transmission > is intended for use only by the individual or entity to which it is > addressed. If you are not the intended recipient or may have received this > electronic mail transmission in error, please notify the sender immediately > and delete / destroy all copies of this electronic mail transmission > without disclosing, copying, distributing, forwarding, printing or > retaining any part of it. Hughes Systique accepts no responsibility for > loss or damage arising from the use of the information transmitted by this > email including damage from virus. > _______________________________________________ > 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 zhipengs.liu at intel.com Wed Sep 9 03:14:09 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 9 Sep 2020 03:14:09 +0000 Subject: [Starlingx-discuss] StarlingX 4.0 stx-application manifest and helm-charts issue. In-Reply-To: References: Message-ID: Hi Akshay, Please use the “flock” one, I have answered the same question sent by Amit yesterday. Zhipeng From: Akshay 346 Sent: 2020年9月4日 15:32 To: starlingx-discuss at lists.starlingx.io; Hu, Yong Subject: [Starlingx-discuss] StarlingX 4.0 stx-application manifest and helm-charts issue. Hello Team, I was deploying StarlingX R4.0 Duplex Bare metal mode. While getting “stx-application” manifests and helm-charts from the public domain, I was not able to find “4.0.0” folder under “release”, also I tried looking into “4.0.1” release but did not find the mentioned path i.e. “centos/outputs/helm-charts” under it. I found “stx-openstack-1.0-49-centos-stable-versioned.tgz” under two folders in “4.0.1” release. These are : - http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/containers/outputs/helm-charts/stx-openstack-1.0-49-centos-stable-versioned.tgz - http://mirror.starlingx.cengn.ca/mirror/starlingx/release/4.0.1/centos/flock/outputs/helm-charts/stx-openstack-1.0-49-centos-stable-versioned.tgz Both the “stx-openstack-1.0-49-centos-stable-versioned.tgz” placed at above paths are different. (Checked with md5sum) Please suggest me which one to use. Regards Akshay DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Wed Sep 9 05:09:00 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 9 Sep 2020 01:09:00 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1077 - Failure! Message-ID: <1301227767.60.1599628141340.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1077 Status: Failure Timestamp: 20200909T050354Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200909T043000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200909T043000Z DOCKER_BUILD_ID: jenkins-master-20200909T043000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200909T043000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200909T043000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/monolithic From build.starlingx at gmail.com Wed Sep 9 05:42:05 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 9 Sep 2020 01:42:05 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_publish - Build # 1591 - Failure! Message-ID: <610884644.65.1599630125925.JavaMail.javamailuser@localhost> Project: STX_publish Build #: 1591 Status: Failure Timestamp: 20200909T054203Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200909T042523Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200909T042523Z OS: centos PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200909T042523Z/logs TIMESTAMP: 20200909T042523Z PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/flock/20200909T042523Z/inputs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200909T042523Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/flock/20200909T042523Z/outputs MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/flock From build.starlingx at gmail.com Wed Sep 9 05:42:07 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 9 Sep 2020 01:42:07 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 243 - Failure! Message-ID: <1794481158.69.1599630128373.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 243 Status: Failure Timestamp: 20200909T042523Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200909T042523Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From ildiko.vancsa at gmail.com Wed Sep 9 09:39:36 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 9 Sep 2020 11:39:36 +0200 Subject: [Starlingx-discuss] TSC resignation - Ian In-Reply-To: <397EF83A-71A4-4440-A14D-A92E30D1BE7B@windriver.com> References: <397EF83A-71A4-4440-A14D-A92E30D1BE7B@windriver.com> Message-ID: <0B796EA7-924F-40B7-BBCE-550F89EEF3E5@gmail.com> Hi Ian, It is very sad to see you leaving the community. Thank you for all the work and effort that you’ve put into building and guiding the community since the project was launched! I wish you all the best with your new adventures and I hope that maybe we will see you again in the community some time in the future. :) Best Regards, Ildikó > On Sep 8, 2020, at 17:47, Jolliffe, Ian wrote: > > Hi StarlingX Community; > > As I mentioned at a TSC call a few weeks ago, after much consideration I have decided to pursue a new career opportunity. As a result, I will no longer be able to serve the community on the StarlingX TSC. I am very proud of what the community has accomplished over the past 2 years and look forward to seeing even more adoption and impact from this great project. Thank you for the good times, friendships and all that we have accomplished as a community. > > Best Regards; > > Ian > _______________________________________________ > 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 Sep 9 11:52:42 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 9 Sep 2020 11:52:42 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Sep 9, 2020) Message-ID: Hi all, reminder of the TSC/Community call coming up later today. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200909T1400 From scott.little at windriver.com Wed Sep 9 14:03:49 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 9 Sep 2020 10:03:49 -0400 Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 275 - Still Failing! In-Reply-To: <199343135.33.1599480440062.JavaMail.javamailuser@localhost> References: <2083858346.22.1599245470703.JavaMail.javamailuser@localhost> <199343135.33.1599480440062.JavaMail.javamailuser@localhost> Message-ID: My fault Was attempting a procedure to update the python2 wheels tarball (stx-centos-py2_stable-wheels.tar) and missed the upper constraints file. It is now fixed. Scott On 2020-09-07 8:07 a.m., build.starlingx at gmail.com wrote: > Project: STX_build_docker_flock_images > Build #: 275 > Status: Still Failing > Timestamp: 20200907T080135Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200907T043000Z/logs > -------------------------------------------------------------------------------- > Parameters > > WEB_HOST: mirror.starlingx.cengn.ca > MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200907T043000Z > OS: centos > MY_REPO: /localdisk/designer/jenkins/master/cgcs-root > BASE_VERSION: master-stable-20200907T043000Z > PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200907T043000Z/logs > REGISTRY_USERID: slittlewrs > LATEST_PREFIX: master > PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200907T043000Z/logs > PUBLISH_TIMESTAMP: 20200907T043000Z > FLOCK_VERSION: master-centos-stable-20200907T043000Z > WEB_HOST_PORT: 80 > PREFIX: master > TIMESTAMP: 20200907T043000Z > BUILD_STREAM: stable > REGISTRY_ORG: slittlewrs > PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200907T043000Z/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 scott.little at windriver.com Wed Sep 9 14:11:59 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 9 Sep 2020 10:11:59 -0400 Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 243 - Failure! In-Reply-To: <1794481158.69.1599630128373.JavaMail.javamailuser@localhost> References: <1794481158.69.1599630128373.JavaMail.javamailuser@localhost> Message-ID: Another successful build marked as a failure when we couldn't publish to the web server. The file system issue seems to have cleared itself this morning. I re-ran the publish step successfully. I have updated our ticket with CENGN. Still no resolution. Scott On 2020-09-09 1:42 a.m., build.starlingx at gmail.com wrote: > Project: STX_build_layer_flock_master_master > Build #: 243 > Status: Failure > Timestamp: 20200909T042523Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200909T042523Z/logs > -------------------------------------------------------------------------------- > Parameters > > FULL_BUILD: false > FORCE_BUILD: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From huang.shuquan at 99cloud.net Wed Sep 9 14:30:07 2020 From: huang.shuquan at 99cloud.net (Shuquan Huang) Date: Wed, 9 Sep 2020 22:30:07 +0800 Subject: [Starlingx-discuss] TSC resignation - Ian In-Reply-To: <0B796EA7-924F-40B7-BBCE-550F89EEF3E5@gmail.com> References: <397EF83A-71A4-4440-A14D-A92E30D1BE7B@windriver.com> <0B796EA7-924F-40B7-BBCE-550F89EEF3E5@gmail.com> Message-ID: Hi Ian, Thank you for your contribution. It’s great to work with you. Wish you all the best. > On Sep 9, 2020, at 5:39 PM, Ildiko Vancsa wrote: > > Hi Ian, > > It is very sad to see you leaving the community. Thank you for all the work and effort that you’ve put into building and guiding the community since the project was launched! > > I wish you all the best with your new adventures and I hope that maybe we will see you again in the community some time in the future. :) > > Best Regards, > Ildikó > > >> On Sep 8, 2020, at 17:47, Jolliffe, Ian wrote: >> >> Hi StarlingX Community; >> >> As I mentioned at a TSC call a few weeks ago, after much consideration I have decided to pursue a new career opportunity. As a result, I will no longer be able to serve the community on the StarlingX TSC. I am very proud of what the community has accomplished over the past 2 years and look forward to seeing even more adoption and impact from this great project. Thank you for the good times, friendships and all that we have accomplished as a community. >> >> Best Regards; >> >> Ian >> _______________________________________________ >> 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 Sep 9 14:33:05 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 9 Sep 2020 14:33:05 +0000 Subject: [Starlingx-discuss] TSC call nodes Sep 9 2020 Message-ID: 9/9/2020 * The governance reviews to remove previous TSC members are ready to merge but need more reviews - TSC members please review! * https://review.opendev.org/#/c/749519/ and https://review.opendev.org/#/c/745909/ * Specs pending are not ready to merge * some key pieces for stx.5.0 are now unresourced (Python 3, CentOS 8, OpenStack Rebase to Victoria) - what is the impact to this release * For Python 2->3 there is work to address issues in unit tests. Pylint runs can help as well. Certain Python components may not have Python3 versions. An additional issue is that P3 behavior is not always the same as P2 behavior. * The CentOS update may be a dependency ofthe P2->P3 work as CentOS 7 did not (does not?) have all of the required P3 components. The two tasks are bound together. Yong recommends moving to CentOS 8 user space first and then dealing with the remaining P2 issues. * We believe P2 removal can be done in parallel with CentOS update to 8, which would help us de-risk it. * The risk of not doing this is that upstream projects will increasingly not support Python2 making it impossible for us to update them. CVEs fixed in newer upstream versions might not apply directly to our older code. * We discussed the release schedule - is this work an anchor feature for the release? If so, we could defer our release until this work completed. The consensus of the community seems to be that this work is an "anchor feature" for StarlingX and we would not release without it. * Do we have a sizing on this work? Can the work be broken down and spread out across teams? Neusoft's previous work showed 40 RPMs needing to be updated (plus the OpenStack and Ceph dependencies). * Please continue this discussion in the Release team call this week. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Sep 9 14:34:27 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 9 Sep 2020 14:34:27 +0000 Subject: [Starlingx-discuss] Interested in Contributing back to community In-Reply-To: References: Message-ID: Hi Akshay, Thank you for reaching out to me. We welcome community contributions. In terms of the next steps, I recommend that you join an upcoming TSC/Community meeting (Wednesdays at 10am Eastern time) to provide an overview of what you are proposing to gauge interest. If there is sufficient interest, then you would follow the contributor/development process for StarlingX: https://docs.starlingx.io/contributor/development_process.html The first step in the development process would be to post a spec for review by TSC members. I think we also need the test teams to review as they have a number of automation tools as well and they may benefit from your contributions. The more specific pointer to the spec process is: https://docs.starlingx.io/contributor/development_process.html#specification-phase Regards, Ghada From: Akshay 346 Sent: Friday, September 04, 2020 4:26 AM To: Khalil, Ghada Subject: Interested in Contributing back to community Hello Ghada, I hope you are doing good and keeping safe. >From around last 1 year I am using StarlingX , deployed many modes of it many-many times, played around it, tested it and reported issues if I had any. >From all this I came to one point to automate these various deployments to save time and efforts. I was thinking to automate all these deployments and contribute it to the community. In addition, I can also give a GUI on top of this automation. Please let me know if it is a acceptable idea or not. Regards Akshay DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Sep 9 15:20:54 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 9 Sep 2020 15:20:54 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Sep 9, 2020) In-Reply-To: References: Message-ID: Notes from today's meeting: * Standing Topics * Sanity * no build since Sep 4, only since there was nothing new to build * there was an issue with Docker builds due to CENGN issues, Scott has sorted it out https://etherpad.opendev.org/p/stx-build * Gerrit Reviews in Need of Attention * rook ceph: https://review.opendev.org/#/q/status:open+branch:master+topic:%22ceph+containerization%22 Thanks everyone reviewed patches, the patches were updated according to review comments. * Topics for this Week * Debranding - File types to be modified. * Story board: https://storyboard.openstack.org/#!/story/2006387 * Merged: Changes to .spec & .service files. * Review: Blocked on workflow label, Needs workflow label ?? * Todo: No reference, confirm project (w.r.t master except starlingx/update) * De-brand Topic: https://review.opendev.org/#/q/status:+open+branch:master+topic:debrand_wip * Removal of stx-r1 & pike changes are also part of this topic. * File extensions include - .xml, .py, Dockerfile, .rst, buildrc, .sh, generate-cgcs-tis-repo, make* * Current Analysis - Flock layer path: /localdisk/designer/stx40/flock/cgcs-root/ * References to 'Titanium' included in below file types - * .py, .h, .cpp, .yaml, .cfg, .txt, .rst * .bash_completion, PKG_INFO, hwmon, hbsAgent, mtcAgent, *password*, *collect*, .ocf * References to cgcs & tis ?? * Request for SPEC review: Initial Spec for SDO integration on STX(https://review.opendev.org/#/c/750636/) * PTG Topics * Ildiko renewed the call for PTG topics: https://etherpad.opendev.org/p/stx-ptg-planning-october-2020 * ARs from Previous Meetings * Aug 26 * Ildiko: poll to get a feel for which time blocks are preferred by folks for the PTG - this is closed * Nic/Yang: feedback from test perspective on stx.4.0 lessons learned * Yong: (rough) plan for starting the Victoria rebase work - still open, un-resourced * Aug 19 * Scott: Docker stuff (see notes from last week) * we agree we can wait a couple more weeks, at least, to get more info re: email notifications & dashboard showing read age * AR: Nic/Yang provide more info on how many images we pull for a given sanity - Nic will check * for last release there are 29 docker.io images. These are listed at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200903T190312Z/outputs/docker-images/images-centos-stable-versioned.lst andhttp://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200903T190312Z/outputs/docker-images/images-distroless-stable-versioned.lst * AR: Release Team discuss whether or not we should just go ahead & nuke stx.2.0 now, as is our stated policy * Open Requests for Help * nothing this week * Build Matters (if required) * nothing this week -----Original Message----- From: Zvonar, Bill Sent: Wednesday, September 9, 2020 7:53 AM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Sep 9, 2020) Hi all, reminder of the TSC/Community call coming up later today. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200909T1400 From ildiko.vancsa at gmail.com Wed Sep 9 17:10:25 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 9 Sep 2020 19:10:25 +0200 Subject: [Starlingx-discuss] Schedule is Live for the 2020 Virtual Open Infrastructure Summit Message-ID: <4151B2BD-54D3-49A0-AE23-76007D9A1504@gmail.com> Hi everyone, We are excited to announce that the schedule[1] for the virtual 2020 Open Infrastructure Summit[2] is now live featuring keynotes and sessions from users like Volvo, Workday, Société Générale and Ant Group. View the schedule for the 2020 virtual Open Infrastructure Summit here: https://www.openstack.org/summit/2020/summit-schedule The virtual event takes place October 19-23 and includes more than 100 sessions and thousands of attendees are expected to participate, representing 30+ open source communities from more than 100 countries. Sessions for the virtual summit are led by users from global enterprises and research institutions building and operating open infrastructure at scale. The Summit includes: • Sessions spanning 30+ open source projects from technical community leaders and organizations including Alibaba Cloud, AT&T, China Mobile, CERN, European Weather Cloud, GE Digital and Volvo Cars and many more. • Collaborative sessions with project leaders and open source communities, including Airship, Ansible, Ceph, Docker, Kata Containers, Kubernetes, ONAP, OpenStack, Open vSwitch, OPNFV, StarlingX, and Zuul. • Get hands on workshops around open source technologies directly from the developers and operators building the software. • Familiarize with the updated Certified OpenStack Administrator (COA)[3] exam and test your OpenStack knowledge at the COA sessions, sponsored by the OpenStack Foundation, in collaboration with Mirantis. Now what? __Register for your free virtual Summit pass[4]__ and meet the users, developers, and vendors who are building and operating open infrastructure on October 19-23! Thank you to our Summit Headline, Premier and Exhibitor sponsors: Huawei, Cisco, InMotion Hosting, Trilio and ZTE. Event sponsors gain visibility with a wide array of open source infrastructure developers, operators and decision makers. Download the Open Infrastructure Summit sponsor prospectus[5] for more information. Questions? Reach out to summit at openstack.org “See you” in October! Thanks, Ildikó [1] https://www.openstack.org/summit/2020/summit-schedule [2] https://www.openstack.org/summit/2020/ [3] https://www.openstack.org/coa [4] https://www.eventbrite.com/e/open-infrastructure-summit-2020-tickets-96967218561 [5] https://www.openstack.org/summit/2020/sponsors/ From kendall at openstack.org Wed Sep 9 18:30:46 2020 From: kendall at openstack.org (Kendall Waters) Date: Wed, 9 Sep 2020 13:30:46 -0500 Subject: [Starlingx-discuss] vPTG October 2020 Team Signup Reminder In-Reply-To: References: Message-ID: <878F9C73-994F-429C-A520-8B0F9DFF924C@openstack.org> Hello Everyone! This is your final reminder! You have until September 11th at 7:00 UTC to sign up your team for the PTG! You must complete BOTH the survey[1] AND reserve time in the ethercalc[2] to sign up your team. And don't forget to register! [3] - TheKendalls (diablo_rojo & wendallkaters) [1] Team Survey: https://openstackfoundation.formstack.com/forms/oct2020_vptg_survey [2] Ethercalc Signup: https://ethercalc.openstack.org/7xp2pcbh1ncb [3] PTG Registration: https://october2020ptg.eventbrite.com > On Aug 31, 2020, at 12:39 PM, Kendall Waters wrote: > > Hello Everyone! > > Wanted to give you all a reminder that the deadline for signing up teams for the PTG is approaching! > > The virtual PTG will be held from Monday October 26th to Friday October 30th, 2020. > > To signup your team, you must complete BOTH the survey[1] AND reserve time in the ethercalc[2] by September 11th at 7:00 UTC. > > We ask that the PTL/SIG Chair/Team lead sign up for time to have their discussions in with 4 rules/guidelines. > > 1. Cross project discussions (like SIGs or support project teams) should be scheduled towards the start of the week so that any discussions that might shape those of other teams happen first. > 2. No team should sign up for more than 4 hours per UTC day to help keep participants actively engaged. > 3. No team should sign up for more than 16 hours across all time slots to avoid burning out our contributors and to enable participation in multiple teams discussions. > > Once your team is signed up, please register[3]! And remind your team to register! Registration is free, but since it will be how we contact you with passwords, event details, etc. it is still important! > > If you have any questions, please let us know. > > -The Kendalls (diablo_rojo & wendallkaters) > > [1] Team Survey: https://openstackfoundation.formstack.com/forms/oct2020_vptg_survey > [2] Ethercalc Signup: https://ethercalc.openstack.org/7xp2pcbh1ncb > [3] PTG Registration: https://october2020ptg.eventbrite.com > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Saul.Wold at windriver.com Wed Sep 9 19:57:38 2020 From: Saul.Wold at windriver.com (Wold, Saul) Date: Wed, 9 Sep 2020 19:57:38 +0000 Subject: [Starlingx-discuss] Multi-OS Meeting Time shift to 7:00am Message-ID: Folks, We are going to have a Multi-OS meeting tomorrow at 7:00am PT (14:00 UTC). I have a new conflict at the original 7:30am timeslot. We can discuss moving this meeting if needed. Agenda: - Meeting Time - Either confirm this earlier time or come up with another time - Status Update from Babak - Where to host the meta-starlingx layer - github.com/starlingx seems right - Next Steps Sau! 0700am Pacific - Multi-OS Team Call Call details Zoom link: https://zoom.us/j/342730236 Dialing in from phone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 Meeting ID: 342 730 236 International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes The agenda and notes for each call are kept in Etherpads: Multi-OS team Agenda and Notes From maryx.camp at intel.com Wed Sep 9 20:37:22 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 9 Sep 2020 20:37:22 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-09-09 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST.   [1]   Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings   [2]   Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2020-09-09  All -- reviews merged since last meeting:  0  All -- bug status -- 6 total - team agrees to defer all low priority LP until the upstreaming effort is completed.  Reviews in progress:    5 reviews related to Rook are ready to review per discuss list message: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-August/009452.html   All -- Opens Upstreaming WR docs status None of the existing reviews are actionable - still in the testing phase. Output generator tool is working pretty smoothly now. They've taken a snapshot of everything, did a pass of cleanup, and shared it with the team doing the upstreaming.  Next steps will be for that team to start submitting reviews. What to do about links between different chapters/books? Will it build locally with tox? Will it build if submitted via gerrit/zuul? Can test this locally - figure out a plan.  DITA task topics have pre-reqs, task/steps, & post-reqs subsections. Exporting to XML makes these subsection heads into real headings, which we don't want. Ron investigated & tested the RST "rubric" directive, which allows these to be ignored from the TOC as headings. Team approved this approach.  Display multiple versions of STX docs  Jeremy has submitted 2 reviews to port over the openstackdocs theme files into the STX docs repo:  https://review.opendev.org/#/c/750005 and https://review.opendev.org/#/c/750006/  He's still figuring out which files are required and which are OpenStack-specific (can be deleted).  Release 3.0.1:  Mary will attend release meeting this week and ask about Release Notes. Likely to be a simple format like R2.01 RN [https://docs.starlingx.io/releasenotes/r2_0_1_release.html] From jimmy at openstack.org Wed Sep 9 22:55:23 2020 From: jimmy at openstack.org (Jimmy McArthur) Date: Wed, 9 Sep 2020 17:55:23 -0500 Subject: [Starlingx-discuss] REMINDER: 2020 Virtual Summit: Forum Submissions Now Accepted In-Reply-To: <9B9E2444-06D4-483E-B311-C9237AD2BA06@getmailspring.com> References: <9B9E2444-06D4-483E-B311-C9237AD2BA06@getmailspring.com> Message-ID: <197DA99C-96AC-4892-96DF-7EDBD0887EB2@getmailspring.com> Hello Everyone! We are now accepting Forum [1] submissions for the 2020 Virtual Open Infrastructure Summit [2]. Please submit your ideas through the Summit CFP tool [3] through September 14th. Don't forget to put your brainstorming etherpad up on the Virtual Forum page [4]. This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. More information about the Forum [1]. The timeline for submissions is as follows: Aug 31st | Formal topic submission tool opens: https://cfp.openstack.org. Sep 14th | Deadline for proposing Forum topics. Scheduling committee meeting to make draft agenda. Sep 21st | Draft Forum schedule published. Crowd sourced session conflict detection. Forum promotion begins. Sept 28th | Forum schedule final Oct 19th | Forum begins! If you have questions or concerns, please reach out to speakersupport at openstack.org (mailto:speakersupport at openstack.org). Cheers, Jimmy [1] https://wiki.openstack.org/wiki/Forum [2] https://www.openstack.org/summit/2020/ [3] https://cfp.openstack.org [4]https://wiki.openstack.org/wiki/Forum/Virtual2020 On Sep 1 2020, at 10:08 am, Jimmy McArthur wrote: > Hello Everyone! > > We are now accepting Forum [1] submissions for the 2020 Virtual Open Infrastructure Summit [2]. Please submit your ideas through the Summit CFP tool [3] through September 14th. Don't forget to put your brainstorming etherpad up on the Shanghai Forum page [4]. > > This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. More information about the Forum [1]. > > The timeline for submissions is as follows: > > Aug 31st | Formal topic submission tool opens: https://cfp.openstack.org. > Sep 14th | Deadline for proposing Forum topics. Scheduling committee meeting to make draft agenda. > Sep 21st | Draft Forum schedule published. Crowd sourced session conflict detection. Forum promotion begins. > Sept 28th | Forum schedule final > Oct 19th | Forum begins! > > If you have questions or concerns, please reach out to speakersupport at openstack.org. > > Cheers, > Jimmy > > [1] https://wiki.openstack.org/wiki/Forum > [2] https://www.openstack.org/summit/2020/ > [3] https://cfp.openstack.org > [4]https://wiki.openstack.org/wiki/Forum/Virtual2020 -------------- next part -------------- An HTML attachment was scrubbed... URL: From chen.dq at neusoft.com Thu Sep 10 06:52:46 2020 From: chen.dq at neusoft.com (chen.dq at neusoft.com) Date: Thu, 10 Sep 2020 06:52:46 +0000 Subject: [Starlingx-discuss] =?gb2312?b?tPC4tDogIFJlZ2FyZGluZyBpbnN0YWxs?= =?gb2312?b?YXRpb24gb2YgY29udHJvbGxlci0wIGZyb20gUFhFCWJvb3Qgc2VydmVy?= In-Reply-To: References: Message-ID: This may help you: - Set the NIC for PXE server on the jumper to a static IP. - Install and config dnsmasq: ``` $ sudo apt-get install dnsmasq $ sudo vi /etc/dnsmasq.conf $ sudo service dnsmasq restart ``` Example of /etc/dnsmasq.conf: ``` interface=nic_name ## NIC for PXE Server bind-interfaces dhcp-range=10.10.10.150,10.10.10.200 ## DHCP Range for PXE install dhcp-boot=grubx64.efi ## StarlingX PXE boot file enable-tftp tftp-root=/var/lib/tftpboot/uefi ## tftp server location ### Fix PXE/OAM NIC for Test Nodes # testnode-1 dhcp-host=12:34:56:78:90:AB,10.10.10.151 # testnode-1 dhcp-host=12:34:56:78:90:AC,10.10.10.152 Below is my configuration /etc/dnsmasq.conf: interface=eno1 # DHCP range-leases dhcp-range= eno1,192.168.3.50,192.168.3.100,255.255.255.0,1h # PXE dhcp-boot=pxelinux.0 # Gateway dhcp-option=3,192.168.3.3 enable-tftp tftp-root=/var/lib/tftpboot dhcp-host=94:c6:91:a9:54:f9,192.168.3.157 sudo apt-get install apache2 systemctl start apache2.service The attachment is a simple script I wrote, for reference only. ________________________________ 发件人: Amit Mahajan 发送时间: 2020年9月7日 16:34:14 收件人: starlingx-discuss at lists.starlingx.io 主题: [Starlingx-discuss] Regarding installation of controller-0 from PXE boot server Hi All, Is there any documentation which can guide on setting up a StarlingX PXE boot server so that I can install controller-0 from this PXE server? Regards, Amit --------------------------------------------------------------------------------------------------- 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: pxeserver_setup.sh Type: application/x-shellscript Size: 1351 bytes Desc: pxeserver_setup.sh URL: From scott.little at windriver.com Thu Sep 10 13:37:00 2020 From: scott.little at windriver.com (Scott Little) Date: Thu, 10 Sep 2020 09:37:00 -0400 Subject: [Starlingx-discuss] [build-report] STX_retag_docker_images - Build # 191 - Still Failing! In-Reply-To: <523423154.53.1599600426581.JavaMail.javamailuser@localhost> References: <1418171.19.1599181734076.JavaMail.javamailuser@localhost> <523423154.53.1599600426581.JavaMail.javamailuser@localhost> Message-ID: <66854780-9718-7768-5cb7-24de31e715c6@windriver.com> A parameter passing error within the jenkins scripts. Fixed and re-run successfully. Scott On 2020-09-08 5:27 p.m., build.starlingx at gmail.com wrote: > Project: STX_retag_docker_images > Build #: 191 > Status: Still Failing > Timestamp: 20200908T212703Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200908T174218Z/logs > -------------------------------------------------------------------------------- > Parameters > > HOST_PORT: 80 > OLD_LATEST_PREFIX: master > WEB_HOST: mirror.starlingx.cengn.ca > MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20200908T174218Z > OS: centos > MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root > BASE_VERSION: master-stable-20200908T174218Z > PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200908T174218Z/logs > REGISTRY_USERID: slittlewrs > LATEST_PREFIX: master > PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20200908T174218Z/logs > RETAG_IMAGE_LIST: stx-fm-rest-api stx-libvirt stx-mariadb > FLOCK_VERSION: master-centos-stable-20200908T174218Z > PREFIX: master > TIMESTAMP: 20200908T174218Z > BUILD_STREAM: dev > REGISTRY_ORG: starlingx > PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20200908T174218Z/outputs > REGISTRY: docker.io > OLD_BUILD_STREAM: stable > > _______________________________________________ > 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 oliver.lovaszi at intel.com Thu Sep 10 14:07:40 2020 From: oliver.lovaszi at intel.com (Lovaszi, Oliver) Date: Thu, 10 Sep 2020 14:07:40 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200910T013244Z Message-ID: Sanity Test from 2020-Spetember-10 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200910T013244Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200910T013244Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Thu Sep 10 14:20:07 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 10 Sep 2020 14:20:07 +0000 Subject: [Starlingx-discuss] =?utf-8?b?562U5aSNOiAgUmVnYXJkaW5nIGluc3Rh?= =?utf-8?q?llation_of_controller-0_from_PXE=09boot_server?= In-Reply-To: References: Message-ID: The ISO also has a pxeboot_setup.sh utility that is designed to help with setting up a pxeboot server. I don’t think this is currently in the StarlingX docs, but maybe the following will help: controller-0:/home/sysadmin# mkdir /mnt/iso controller-0:/home/sysadmin# mount -o loop bootimage.iso /mnt/iso mount: /dev/loop0 is write-protected, mounting read-only controller-0:/home/sysadmin# /mnt/iso/pxeboot_setup.sh -h Usage: /mnt/iso/pxeboot_setup.sh -u [-t ] or [-w ] lab:/home/sysadmin# mkdir -p /export/pxeboot lab:/home/sysadmin# /mnt/iso/pxeboot_setup.sh -u http://someserver:8123/nodeX -t /export/pxeboot/nodeX Create /export/pxeboot/nodeX The setup is complete controller-0:/home/sysadmin# This will extract the load from the ISO under the specific directory, and setup pxeboot kickstarts using the specified base URL. This creates a pxeboot.cfg file in the /export/pxeboot/nodeX with install instructions to point to your server, such as: # Serial Console submenu label 3 menu label Serial Console kernel vmlinuz append initrd=initrd.img bootifonly=1 devfs=nomount inst.repo=http://someserver:8123/nodeX inst.ks=http://someserver:8123/nodeX/pxeboot_smallsystem.cfg boot_device=sda rootfs_device=sda biosdevname=0 inst.text serial console=ttyS0,115200n8 inst.gpt security_profile=standard user_namespace.enable=1 ipappend 2 with the http server setup so that http://someserver:8123/nodeX references /export/pxeboot/nodeX, such as with a symlink. From: chen.dq at neusoft.com Sent: Thursday, September 10, 2020 2:53 AM To: Amit Mahajan ; starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] 答复: Regarding installation of controller-0 from PXE boot server This may help you: - Set the NIC for PXE server on the jumper to a static IP. - Install and config dnsmasq: ``` $ sudo apt-get install dnsmasq $ sudo vi /etc/dnsmasq.conf $ sudo service dnsmasq restart ``` Example of /etc/dnsmasq.conf: ``` interface=nic_name ## NIC for PXE Server bind-interfaces dhcp-range=10.10.10.150,10.10.10.200 ## DHCP Range for PXE install dhcp-boot=grubx64.efi ## StarlingX PXE boot file enable-tftp tftp-root=/var/lib/tftpboot/uefi ## tftp server location ### Fix PXE/OAM NIC for Test Nodes # testnode-1 dhcp-host=12:34:56:78:90:AB,10.10.10.151 # testnode-1 dhcp-host=12:34:56:78:90:AC,10.10.10.152 Below is my configuration /etc/dnsmasq.conf: interface=eno1 # DHCP range-leases dhcp-range= eno1,192.168.3.50,192.168.3.100,255.255.255.0,1h # PXE dhcp-boot=pxelinux.0 # Gateway dhcp-option=3,192.168.3.3 enable-tftp tftp-root=/var/lib/tftpboot dhcp-host=94:c6:91:a9:54:f9,192.168.3.157 sudo apt-get install apache2 systemctl start apache2.service The attachment is a simple script I wrote, for reference only. ________________________________ 发件人: Amit Mahajan > 发送时间: 2020年9月7日 16:34:14 收件人: starlingx-discuss at lists.starlingx.io 主题: [Starlingx-discuss] Regarding installation of controller-0 from PXE boot server Hi All, Is there any documentation which can guide on setting up a StarlingX PXE boot server so that I can install controller-0 from this PXE server? Regards, Amit --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Thu Sep 10 15:18:47 2020 From: scott.little at windriver.com (Scott Little) Date: Thu, 10 Sep 2020 11:18:47 -0400 Subject: [Starlingx-discuss] [Build] Debranding Message-ID: We need a thread for the discussion of Debranding.  Interested parties should reply here. Intent is the removal of references to cgcs, tis, Titanium, stx-r1 and pike from the code base and it's supporting build systems.  Some of work will impact the CENGN build service, and might impact automated test resources as well. We'll need to progress slowly and carefully, and have backward compatibility kept in mind for the near term. Story board: *https://storyboard.openstack.org/#!/story/2006387* Review Topic: *https://review.opendev.org/#/q/status:+open+branch:master+topic:debrand_wip*** -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Sep 10 16:49:21 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 10 Sep 2020 16:49:21 +0000 Subject: [Starlingx-discuss] [Build] Debranding In-Reply-To: References: Message-ID: Scott, thank you for taking up the lead on this. I support the effort, as it has benefits both for cleaning up the code and for removing the need to explain just what a cgcs is. I encourage the community to actively support Scott, reviewing the patches and helping move this forward. brucej From: Scott Little Sent: Thursday, September 10, 2020 8:19 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Build] Debranding We need a thread for the discussion of Debranding. Interested parties should reply here. Intent is the removal of references to cgcs, tis, Titanium, stx-r1 and pike from the code base and it's supporting build systems. Some of work will impact the CENGN build service, and might impact automated test resources as well. We'll need to progress slowly and carefully, and have backward compatibility kept in mind for the near term. Story board: https://storyboard.openstack.org/#!/story/2006387 Review Topic: https://review.opendev.org/#/q/status:+open+branch:master+topic:debrand_wip -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Fri Sep 11 03:41:36 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 11 Sep 2020 03:41:36 +0000 Subject: [Starlingx-discuss] patch review for rook-ceph In-Reply-To: References: Message-ID: Hi Greg As your review comment, I move rook simplex and duplex deployment guide to r5 deployment guide. doc/source/deploy_install_guides/r5_release/virtual/aio_simplex_install_kubernetes.rst doc/source/deploy_install_guides/r5_release/virtual/aio_duplex_install_kubernetes.rst https://review.opendev.org/#/c/751158/ After the above patch merged, these two patch will be abandoned. https://review.opendev.org/#/c/742573/ https://review.opendev.org/#/c/742102/ BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Thursday, September 3, 2020 1:52 PM To: Camp, MaryX ; starlingx-discuss at lists.starlingx.io; Waines, Greg Subject: RE: patch review for rook-ceph Hi Mary I update patch for doc. For these three patch, you could only review the first only, doc for standard multi node system deployment. I will update both three patch. https://review.opendev.org/#/c/724623/ https://review.opendev.org/#/c/742102/ https://review.opendev.org/#/c/742573/ Hi Greg I agree, move these two patch to R5 together with simple and duplex deployment. I will update late. https://review.opendev.org/#/c/742102/ https://review.opendev.org/#/c/742573/ BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, September 1, 2020 8:31 AM To: Camp, MaryX >; starlingx-discuss at lists.starlingx.io; Bailey, Henry Albert (Al) > Subject: RE: patch review for rook-ceph Thanks Mary, I will update doc in this week. Martin, Chen IOTG, Software Engineer 021-61164330 From: Camp, MaryX > Sent: Tuesday, September 1, 2020 2:53 AM To: Chen, Haochuan Z >; starlingx-discuss at lists.starlingx.io; Bailey, Henry Albert (Al) > Subject: RE: patch review for rook-ceph Hi Martin, There are 5 reviews in progress for STX docs for rook-ceph. Can you please resolve the outstanding comments? Then the docs team will review again. https://review.opendev.org/#/q/status:open+project:starlingx/docs+branch:master+topic:ceph-cluster-editorial Thanks in advance, Mary Camp PTIGlobal Technical Writer | maryx.camp at intel.com From: Chen, Haochuan Z > Sent: Monday, August 31, 2020 11:16 AM To: starlingx-discuss at lists.starlingx.io; Bailey, Henry Albert (Al) > Subject: [Starlingx-discuss] patch review for rook-ceph Thanks AL review my patch for rook-ceph Appreciate more reviewer for my patch. https://review.opendev.org/#/q/topic:%22ceph+containerization%22+(status:open+OR+status:merged) Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Fri Sep 11 11:44:39 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Fri, 11 Sep 2020 11:44:39 +0000 Subject: [Starlingx-discuss] stx.3.0.1 maintenance release - build request In-Reply-To: References: Message-ID: Hi All, We executed sanity tests for stx 3.0.1 release. It FAILS at provisioning using: - current bootimage.iso - http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200903T190312Z/outputs/iso/bootimage.iso - current helm chart - http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200903T190312Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz It PASS using: - current bootimage.iso - http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20200903T190312Z/outputs/iso/bootimage.iso - old helm chart - http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20191213T023000Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz Regards, Nicolae Jascanu, Ph.D. Software Engineer IOTG Galati, Romania From: Panech, Davlet Sent: Tuesday, September 8, 2020 17:07 To: Khalil, Ghada ; Jascanu, Nicolae Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: stx.3.0.1 maintenance release - build request A candidate 3.0.x build has completed and can be tested now. ________________________________ From: Khalil, Ghada > Sent: September 3, 2020 2:22 PM To: Panech, Davlet >; Jascanu, Nicolae > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: stx.3.0.1 maintenance release - build request Hi Davlet, The required code for stx.3.0.1 hass been cherrypicked to the r/stx.3.0 branch. Please start an RC build for the stx.3.0.1 maintenance release. Hi Nick, Once the build is available, please arrange for a sanity and some regression. A list of fixes can be seen in the branch [0]. Thanks, Ghada Reference: [0] https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.3.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From oliver.lovaszi at intel.com Fri Sep 11 14:42:43 2020 From: oliver.lovaszi at intel.com (Lovaszi, Oliver) Date: Fri, 11 Sep 2020 14:42:43 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200911T013237Z Message-ID: Sanity Test from 2020-Spetember-11 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200911T013237Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200911T013237Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon Sep 14 04:47:22 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 14 Sep 2020 00:47:22 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1092 - Failure! Message-ID: <801490624.85.1600058843274.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1092 Status: Failure Timestamp: 20200914T044242Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200914T043000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200914T043000Z DOCKER_BUILD_ID: jenkins-master-20200914T043000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200914T043000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200914T043000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/monolithic From susendra.selvaraj at intel.com Mon Sep 14 06:54:09 2020 From: susendra.selvaraj at intel.com (Selvaraj, Susendra) Date: Mon, 14 Sep 2020 06:54:09 +0000 Subject: [Starlingx-discuss] [Build] Debranding In-Reply-To: References: Message-ID: Hello Scott, Bruce, Below is the information gathered on De-branding – Story board: https://storyboard.openstack.org/#!/story/2006387 · Merged: Changes to .spec & .service files. · Review: Blocked on workflow label, Needs workflow label ?? · Todo: starlingx/ha (no reference), stx-tools, starlingx/update Existing De-brand Topic: https://review.opendev.org/#/q/status:+open+branch:master+topic:debrand_wip · Removal of stx-r1 & pike changes are also part of this topic. · File extensions include - .xml, .py, Dockerfile, .rst, buildrc, .sh, generate-cgcs-tis-repo, make* Current Analysis - Flock layer path: /localdisk/designer/stx40/flock/cgcs-root/ · References to 'Titanium' included in below file types - o .py, .h, .cpp, .yaml, .cfg, .txt, .rst o .bash_completion, PKG_INFO, hwmon, hbsAgent, mtcAgent, *password*, *collect*, .ocf · References to Titanium, cgcs & tis Baseline path References (w/o binary files) Count Distinct Files (w/o binary files) Count /localdisk/designer/stx40/flock/ grep -rnsw -I "Titanium" ./* | wc 120 grep -rnsw -I -l "Titanium" ./* | w 77 /localdisk/designer/stx40/flock grep -rnsw -I "cgcs*" ./* | w 483 grep -rnsw -I -l "cgcs*" ./* | wc 151 /localdisk/designer/stx40/flock grep -rnsw -I "tis*" ./* | w 3194 grep -rnsw -I -l "tis*" ./* | wc 91 We can start with merging the existing De-brand topic. Please let me know for comments. Regards, Susendra. From: N, Poornima Y Sent: Monday, September 14, 2020 11:59 AM To: Selvaraj, Susendra Subject: FW: [Starlingx-discuss] [Build] Debranding From: Jones, Bruce E > Sent: Thursday, September 10, 2020 10:19 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Build] Debranding Scott, thank you for taking up the lead on this. I support the effort, as it has benefits both for cleaning up the code and for removing the need to explain just what a cgcs is. I encourage the community to actively support Scott, reviewing the patches and helping move this forward. brucej From: Scott Little > Sent: Thursday, September 10, 2020 8:19 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Build] Debranding We need a thread for the discussion of Debranding. Interested parties should reply here. Intent is the removal of references to cgcs, tis, Titanium, stx-r1 and pike from the code base and it's supporting build systems. Some of work will impact the CENGN build service, and might impact automated test resources as well. We'll need to progress slowly and carefully, and have backward compatibility kept in mind for the near term. Story board: https://storyboard.openstack.org/#!/story/2006387 Review Topic: https://review.opendev.org/#/q/status:+open+branch:master+topic:debrand_wip -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Sep 14 13:33:36 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 14 Sep 2020 13:33:36 +0000 Subject: [Starlingx-discuss] patch review for rook-ceph In-Reply-To: References: Message-ID: Thanks AL and Penney review for my patch. Appreciate more reviewer for my patch. https://review.opendev.org/#/q/topic:%22ceph+containerization%22+(status:open+OR+status:merged) Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, August 31, 2020 11:16 PM To: starlingx-discuss at lists.starlingx.io; Bailey, Henry Albert (Al) Subject: patch review for rook-ceph Thanks AL review my patch for rook-ceph Appreciate more reviewer for my patch. https://review.opendev.org/#/q/topic:%22ceph+containerization%22+(status:open+OR+status:merged) Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From susendra.selvaraj at intel.com Mon Sep 14 16:37:27 2020 From: susendra.selvaraj at intel.com (Selvaraj, Susendra) Date: Mon, 14 Sep 2020 16:37:27 +0000 Subject: [Starlingx-discuss] FW: [Build] Debranding In-Reply-To: References: Message-ID: Hello Scott, Bruce, Below is the information gathered on De-branding – Story board: https://storyboard.openstack.org/#!/story/2006387 · Merged: Changes to .spec & .service files. · Review: Blocked on workflow label, Needs workflow label ?? · Todo: starlingx/ha (no reference), stx-tools, starlingx/update Existing De-brand Topic: https://review.opendev.org/#/q/status:+open+branch:master+topic:debrand_wip · Removal of stx-r1 & pike changes are also part of this topic. · File extensions include - .xml, .py, Dockerfile, .rst, buildrc, .sh, generate-cgcs-tis-repo, make* Current Analysis - Flock layer path: /localdisk/designer/stx40/flock/cgcs-root/ · References to 'Titanium' included in below file types - o .py, .h, .cpp, .yaml, .cfg, .txt, .rst o .bash_completion, PKG_INFO, hwmon, hbsAgent, mtcAgent, *password*, *collect*, .ocf · References to Titanium, cgcs & tis Baseline path References (w/o binary files) Count Distinct Files (w/o binary files) Count /localdisk/designer/stx40/flock/ grep -rnsw -I "Titanium" ./* | wc 120 grep -rnsw -I -l "Titanium" ./* | w 77 /localdisk/designer/stx40/flock grep -rnsw -I "cgcs*" ./* | w 483 grep -rnsw -I -l "cgcs*" ./* | wc 151 /localdisk/designer/stx40/flock grep -rnsw -I "tis*" ./* | w 3194 grep -rnsw -I -l "tis*" ./* | wc 91 We can start with merging the existing De-brand topic. Please let me know for comments. Regards, Susendra. From: N, Poornima Y > Sent: Monday, September 14, 2020 11:59 AM To: Selvaraj, Susendra > Subject: FW: [Starlingx-discuss] [Build] Debranding From: Jones, Bruce E > Sent: Thursday, September 10, 2020 10:19 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Build] Debranding Scott, thank you for taking up the lead on this. I support the effort, as it has benefits both for cleaning up the code and for removing the need to explain just what a cgcs is. I encourage the community to actively support Scott, reviewing the patches and helping move this forward. brucej From: Scott Little > Sent: Thursday, September 10, 2020 8:19 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Build] Debranding We need a thread for the discussion of Debranding. Interested parties should reply here. Intent is the removal of references to cgcs, tis, Titanium, stx-r1 and pike from the code base and it's supporting build systems. Some of work will impact the CENGN build service, and might impact automated test resources as well. We'll need to progress slowly and carefully, and have backward compatibility kept in mind for the near term. Story board: https://storyboard.openstack.org/#!/story/2006387 Review Topic: https://review.opendev.org/#/q/status:+open+branch:master+topic:debrand_wip -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Mon Sep 14 20:12:52 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 14 Sep 2020 20:12:52 +0000 Subject: [Starlingx-discuss] [Build] Debranding In-Reply-To: References: Message-ID: Thank you Susendra. Agree that the current de-branding changes should merge in an orderly way. For the “References to Titanium, cgcs, tis” I suggest that we focus on the changes that are visible to end users first, e.g. messages written to log files. I think changing text in source code comments and other innocuous places is not a priority. Suggest doing the changes in batches so they can be reviewed easily. brucej From: Selvaraj, Susendra Sent: Monday, September 14, 2020 9:37 AM To: scott.little at windriver.com; Jones, Bruce E Cc: starlingx-discuss at lists.starlingx.io Subject: FW: [Starlingx-discuss] [Build] Debranding Hello Scott, Bruce, Below is the information gathered on De-branding – Story board: https://storyboard.openstack.org/#!/story/2006387 · Merged: Changes to .spec & .service files. · Review: Blocked on workflow label, Needs workflow label ?? · Todo: starlingx/ha (no reference), stx-tools, starlingx/update Existing De-brand Topic: https://review.opendev.org/#/q/status:+open+branch:master+topic:debrand_wip · Removal of stx-r1 & pike changes are also part of this topic. · File extensions include - .xml, .py, Dockerfile, .rst, buildrc, .sh, generate-cgcs-tis-repo, make* Current Analysis - Flock layer path: /localdisk/designer/stx40/flock/cgcs-root/ · References to 'Titanium' included in below file types - o .py, .h, .cpp, .yaml, .cfg, .txt, .rst o .bash_completion, PKG_INFO, hwmon, hbsAgent, mtcAgent, *password*, *collect*, .ocf · References to Titanium, cgcs & tis Baseline path References (w/o binary files) Count Distinct Files (w/o binary files) Count /localdisk/designer/stx40/flock/ grep -rnsw -I "Titanium" ./* | wc 120 grep -rnsw -I -l "Titanium" ./* | w 77 /localdisk/designer/stx40/flock grep -rnsw -I "cgcs*" ./* | w 483 grep -rnsw -I -l "cgcs*" ./* | wc 151 /localdisk/designer/stx40/flock grep -rnsw -I "tis*" ./* | w 3194 grep -rnsw -I -l "tis*" ./* | wc 91 We can start with merging the existing De-brand topic. Please let me know for comments. Regards, Susendra. From: N, Poornima Y > Sent: Monday, September 14, 2020 11:59 AM To: Selvaraj, Susendra > Subject: FW: [Starlingx-discuss] [Build] Debranding From: Jones, Bruce E > Sent: Thursday, September 10, 2020 10:19 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Build] Debranding Scott, thank you for taking up the lead on this. I support the effort, as it has benefits both for cleaning up the code and for removing the need to explain just what a cgcs is. I encourage the community to actively support Scott, reviewing the patches and helping move this forward. brucej From: Scott Little > Sent: Thursday, September 10, 2020 8:19 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Build] Debranding We need a thread for the discussion of Debranding. Interested parties should reply here. Intent is the removal of references to cgcs, tis, Titanium, stx-r1 and pike from the code base and it's supporting build systems. Some of work will impact the CENGN build service, and might impact automated test resources as well. We'll need to progress slowly and carefully, and have backward compatibility kept in mind for the near term. Story board: https://storyboard.openstack.org/#!/story/2006387 Review Topic: https://review.opendev.org/#/q/status:+open+branch:master+topic:debrand_wip -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Mon Sep 14 20:30:34 2020 From: scott.little at windriver.com (Scott Little) Date: Mon, 14 Sep 2020 16:30:34 -0400 Subject: [Starlingx-discuss] [Build] Debranding In-Reply-To: References: Message-ID: <7de7499e-fcd4-3e71-b0d7-310610b0861e@windriver.com> Re the list you seem to be compiling ... Not so sure limiting the search to just these file types is productive, although it does identify instances that can likely change independently of the build infrastructure.  My personal concern is limited to those that ARE tied to the build infrastructure.  e.g. TIS_PATCH_VER in build_srpm.data and %{?_tis_dist}.%{tis_patch_ver} in spec files. I'm also a bit skeptical of just publishing a count.  I'd suggest something like a google docs spreadsheet, with fields for package, file path, reference type (comment, method, class, local variable, global variable, file name, ...), reference value (e.g. variable name in full).   The goal would be an ability to filter and/or sort on a field. e.g. Filtering on a variable's name might allow identification of both source code that uses the variable, and yaml files that might initialize the variable.  They would all have to change in a co-ordinated fashion.  Seeds for a task that a designer might tackle independent of the big picture On 2020-09-14 2:54 a.m., Selvaraj, Susendra wrote: > > Hello Scott, Bruce, > > Below is the information gathered on De-branding – > > Story board: *https://storyboard.openstack.org/#!/story/2006387* > > ·Merged: Changes to .spec & .service files. > > ·Review: Blocked on workflow label, Needs workflow label ?? > > ·Todo: starlingx/ha (no reference), stx-tools, starlingx/update > > Existing De-brand Topic: > https://review.opendev.org/#/q/status:+open+branch:master+topic:debrand_wip > > ·Removal of stx-r1 & pike changes are also part of this topic. > > ·File extensions include - .xml, .py, Dockerfile, .rst, buildrc, .sh, > generate-cgcs-tis-repo, make* > > Current Analysis - Flock layer path: > /localdisk/designer/stx40/flock/cgcs-root/ > > ·References to 'Titanium' included in below file types - > > o.py, .h, .cpp, .yaml, .cfg, .txt, .rst > > o.bash_completion, PKG_INFO, hwmon, hbsAgent, mtcAgent, *password*, > *collect*, .ocf > > ·References to Titanium, cgcs & tis > > Baseline path > > > > References (w/o binary files) > > > > Count > > > > Distinct Files (w/o binary files) > > > > Count > > /localdisk/designer/stx40/flock/ > > > > grep -rnsw -I "Titanium" ./* | wc > > > > 120 > > > > grep -rnsw -I -l "Titanium" ./* | w > > > > 77 > > /localdisk/designer/stx40/flock > > > > grep -rnsw -I "cgcs*" ./* | w > > > > 483 > > > > grep -rnsw -I -l "cgcs*" ./* | wc > > > > 151 > > /localdisk/designer/stx40/flock > > > > grep -rnsw -I "tis*" ./* | w > > > > 3194 > > > > grep -rnsw -I -l "tis*" ./* | wc > > > > 91 > > We can start with merging the existing De-brand topic. Please let me > know for comments. > > Regards, > > Susendra. > > *From:*N, Poornima Y > *Sent:* Monday, September 14, 2020 11:59 AM > *To:* Selvaraj, Susendra > *Subject:* FW: [Starlingx-discuss] [Build] Debranding > > *From:*Jones, Bruce E > > *Sent:* Thursday, September 10, 2020 10:19 PM > *To:* starlingx-discuss at lists.starlingx.io > > *Subject:* Re: [Starlingx-discuss] [Build] Debranding > > Scott, thank you for taking up the lead on this.  I support the > effort, as it has benefits both for cleaning up the code and for > removing the need to explain just what a cgcs is. > > I encourage the community to actively support Scott, reviewing the > patches and helping move this forward. > > brucej > > *From:*Scott Little > > *Sent:* Thursday, September 10, 2020 8:19 AM > *To:* starlingx-discuss at lists.starlingx.io > > *Subject:* [Starlingx-discuss] [Build] Debranding > > We need a thread for the discussion of Debranding.  Interested parties > should reply here. > > Intent is the removal of references to cgcs, tis, Titanium, stx-r1 and > pike from the code base and it's supporting build systems.  Some of > work will impact the CENGN build service, and might impact automated > test resources as well.  We'll need to progress slowly and carefully, > and have backward compatibility kept in mind for the near term. > > > Story board: *https://storyboard.openstack.org/#!/story/2006387* > > Review Topic: > *https://review.opendev.org/#/q/status:+open+branch:master+topic:debrand_wip* > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Saul.Wold at windriver.com Mon Sep 14 21:17:36 2020 From: Saul.Wold at windriver.com (Wold, Saul) Date: Mon, 14 Sep 2020 21:17:36 +0000 Subject: [Starlingx-discuss] Multi-OS Meeting (Updated) Tuesday 1430UTC / 0730PT Message-ID: Welcome to the new bi-weekly StarlingX Mulit-OS team meeting. You are invited to join a meeting. Join the meeting: https://meet.jit.si/starlingx-multios To join by phone instead, tap this: +1.512.647.1431,,2792742287# Looking for a different dial-in number? See meeting dial-in numbers: https://meet.jit.si/static/dialInInfo.html?room=starlingx-multios If also dialing-in through a room phone, join without connecting to audio: https://meet.jit.si/starlingx-multios#config.startSilent=true -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2552 bytes Desc: not available URL: From Greg.Waines at windriver.com Tue Sep 15 00:05:06 2020 From: Greg.Waines at windriver.com (Waines, Greg) Date: Tue, 15 Sep 2020 00:05:06 +0000 Subject: [Starlingx-discuss] patch review for rook-ceph In-Reply-To: References: Message-ID: I provided comments on: * doc/source/deploy_install_guides/r5_release/virtual/aio_simplex_install_kubernetes.rst * doc/source/deploy_install_guides/r5_release/virtual/aio_duplex_install_kubernetes.rst Are you providing updates to ??? * VIRTUAL Standard w/controller storage INSTALL GUIDE * VIRTUAL Standard w/dedicated storage INSTALL GUIDE * BARE METAL aio-simplex INSTALL GUIDE * BARE METAL aio-duplex INSTALL GUIDE * BARE METAL Standard w/controller storage INSTALL GUIDE * BARE METAL Standard w/dedicated storage INSTALL GUIDE Greg. From: "Chen, Haochuan Z" Date: Thursday, September 10, 2020 at 11:41 PM To: "Camp, MaryX" , "starlingx-discuss at lists.starlingx.io" , Greg Waines Subject: RE: patch review for rook-ceph Hi Greg As your review comment, I move rook simplex and duplex deployment guide to r5 deployment guide. doc/source/deploy_install_guides/r5_release/virtual/aio_simplex_install_kubernetes.rst doc/source/deploy_install_guides/r5_release/virtual/aio_duplex_install_kubernetes.rst https://review.opendev.org/#/c/751158/ After the above patch merged, these two patch will be abandoned. https://review.opendev.org/#/c/742573/ https://review.opendev.org/#/c/742102/ BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Thursday, September 3, 2020 1:52 PM To: Camp, MaryX ; starlingx-discuss at lists.starlingx.io; Waines, Greg Subject: RE: patch review for rook-ceph Hi Mary I update patch for doc. For these three patch, you could only review the first only, doc for standard multi node system deployment. I will update both three patch. https://review.opendev.org/#/c/724623/ https://review.opendev.org/#/c/742102/ https://review.opendev.org/#/c/742573/ Hi Greg I agree, move these two patch to R5 together with simple and duplex deployment. I will update late. https://review.opendev.org/#/c/742102/ https://review.opendev.org/#/c/742573/ BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, September 1, 2020 8:31 AM To: Camp, MaryX >; starlingx-discuss at lists.starlingx.io; Bailey, Henry Albert (Al) > Subject: RE: patch review for rook-ceph Thanks Mary, I will update doc in this week. Martin, Chen IOTG, Software Engineer 021-61164330 From: Camp, MaryX > Sent: Tuesday, September 1, 2020 2:53 AM To: Chen, Haochuan Z >; starlingx-discuss at lists.starlingx.io; Bailey, Henry Albert (Al) > Subject: RE: patch review for rook-ceph Hi Martin, There are 5 reviews in progress for STX docs for rook-ceph. Can you please resolve the outstanding comments? Then the docs team will review again. https://review.opendev.org/#/q/status:open+project:starlingx/docs+branch:master+topic:ceph-cluster-editorial Thanks in advance, Mary Camp PTIGlobal Technical Writer | maryx.camp at intel.com From: Chen, Haochuan Z > Sent: Monday, August 31, 2020 11:16 AM To: starlingx-discuss at lists.starlingx.io; Bailey, Henry Albert (Al) > Subject: [Starlingx-discuss] patch review for rook-ceph Thanks AL review my patch for rook-ceph Appreciate more reviewer for my patch. https://review.opendev.org/#/q/topic:%22ceph+containerization%22+(status:open+OR+status:merged) Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bnovickovs at weecodelab.com Tue Sep 15 09:16:56 2020 From: bnovickovs at weecodelab.com (bnovickovs at weecodelab.com) Date: Tue, 15 Sep 2020 10:16:56 +0100 Subject: [Starlingx-discuss] Kubevirt integration Message-ID: <6c7b0c3bd987cbdcb76cf83e1e83035c@weecodelab.com> Hello, I am wondering, guys if you thought about Kubevirt integration https://kubevirt.io/ for VM workloads. In case if somebody does not want to deploy openstack on top of kube cluster and save on resources, kubevirt could be a really good alternative to that? Thank you and regards From haochuan.z.chen at intel.com Tue Sep 15 01:46:44 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 15 Sep 2020 01:46:44 +0000 Subject: [Starlingx-discuss] review patch to enable rook-ceph in metal project In-Reply-To: References: Message-ID: Add Ovidiu. Please review my patch for rook-ceph in metal project. https://review.opendev.org/#/c/737228/ Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, August 10, 2020 11:09 AM To: Bart Wensley ; Penney, Don ; MacDonald, Eric ; Kung, John ; Liu, Tao Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: review patch to enable rook-ceph in metal project Hi folks Please review my patch to enable rook-ceph in metal project. https://review.opendev.org/#/c/737228/ BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Sep 15 13:11:36 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 15 Sep 2020 13:11:36 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 9/16/2020 Message-ID: Hi All: Agenda 9/16 meeting: -Ceph containerization : Patches Review Status : https://review.opendev.org/#/q/status:open+branch:master+topic:%22ceph+containerization%22 feature test summary - LPs https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.other https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.storage - Open If any more topic , please add into https://etherpad.opendev.org/p/stx-distro-other Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Tue Sep 15 13:40:35 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 15 Sep 2020 13:40:35 +0000 Subject: [Starlingx-discuss] STX containerization meeting minutes Message-ID: There was not enough quorum for this meeting today so no minutes. At this point there are no topics planned for the next meeting which would normally be Sept 29. If there are topics to discuss and a meeting is warranted please request by sending an email to the community mailing list prefixed with [Containers]. Frank PL StarlingX Containerization -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Sep 15 14:26:52 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 15 Sep 2020 14:26:52 +0000 Subject: [Starlingx-discuss] Kubevirt integration In-Reply-To: <6c7b0c3bd987cbdcb76cf83e1e83035c@weecodelab.com> References: <6c7b0c3bd987cbdcb76cf83e1e83035c@weecodelab.com> Message-ID: We've thought about kubevirt, but I don't believe it's been implemented yet. StarlingX does support Kata Containers. See https://docs.starlingx.io/operations/kata_container.html. brucej -----Original Message----- From: bnovickovs at weecodelab.com Sent: Tuesday, September 15, 2020 2:17 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Kubevirt integration Hello, I am wondering, guys if you thought about Kubevirt integration https://kubevirt.io/ for VM workloads. In case if somebody does not want to deploy openstack on top of kube cluster and save on resources, kubevirt could be a really good alternative to that? Thank you and regards _______________________________________________ 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 Sep 15 15:37:19 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 15 Sep 2020 17:37:19 +0200 Subject: [Starlingx-discuss] StarlingX Introduction session for the Summit - ACTION NEEDED Message-ID: Hi, I’m reaching out about the upcoming virtual Open Infrastructure Summit. To make sure that the project is getting a good exposure at the event as well as giving opportunities to reach out to potential new contributors as well as users we are asking all OSF projects to prepare an introductory 101 session. The goal is to give attendees an introduction to the project, as well as further guidance on how to get involved. Some further guidance for the session: * Title: “StarlingX Overview” * 10 - 15 minute recording with time for live text chat Q&A (max session time of 30 minutes) * Oriented toward beginner audience * High-level overview suggested touch points: * Explain what the project is * Where it fits in the software stack * Open source projects it integrates with * Tools used to contribute/where to find us online * How it follows the 4 Opens We are looking for a volunteer or volunteers to put together and record the session. __If you are interested in volunteering please let me know as soon as possible.__ Please let me know if you have any questions. Thanks, Ildikó From scott.little at windriver.com Tue Sep 15 16:41:17 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 15 Sep 2020 12:41:17 -0400 Subject: [Starlingx-discuss] rook-ceph core reviewers needed Message-ID: <221e43ba-5ce8-a309-a742-2303efc085c6@windriver.com> We need to nominate a few core reviewers for the rook-ceph project. Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Tue Sep 15 17:05:06 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 15 Sep 2020 17:05:06 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200915T010922Z Message-ID: Sanity Test from 2020-September-15 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200915T010922Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200915T010922Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal 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 06 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment We don't have yet the results for Virtual Environment because we experienced some timeouts and we triggered again this jobs. Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20513 bytes Desc: image003.png URL: From Don.Penney at windriver.com Tue Sep 15 18:01:58 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 15 Sep 2020 18:01:58 +0000 Subject: [Starlingx-discuss] rook-ceph core reviewers needed In-Reply-To: <221e43ba-5ce8-a309-a742-2303efc085c6@windriver.com> References: <221e43ba-5ce8-a309-a742-2303efc085c6@windriver.com> Message-ID: I would expect we would need storage folks like Bob and Ovidiu and the folks familiar with the rook work (Martin and Austin?) From: Scott Little Sent: Tuesday, September 15, 2020 12:41 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] rook-ceph core reviewers needed We need to nominate a few core reviewers for the rook-ceph project. Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Wed Sep 16 00:29:29 2020 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 16 Sep 2020 00:29:29 +0000 Subject: [Starlingx-discuss] rook-ceph core reviewers needed In-Reply-To: References: <221e43ba-5ce8-a309-a742-2303efc085c6@windriver.com> Message-ID: Yeah, I’d like to nominate Austin to be one of core on this project. Regards, Yong From: "Penney, Don" Date: Wednesday, September 16, 2020 at 2:03 AM To: "Little, Scott" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] rook-ceph core reviewers needed I would expect we would need storage folks like Bob and Ovidiu and the folks familiar with the rook work (Martin and Austin?) From: Scott Little Sent: Tuesday, September 15, 2020 12:41 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] rook-ceph core reviewers needed We need to nominate a few core reviewers for the rook-ceph project. Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Wed Sep 16 06:53:33 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Wed, 16 Sep 2020 06:53:33 +0000 Subject: [Starlingx-discuss] rook-ceph core reviewers needed Message-ID: Hi scott You can propose a reviewer temporarily, if he review +1, you can review +2 for this patch. https://review.opendev.org/716792 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Wednesday, September 16, 2020 1:05 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 28, Issue 41 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Re: Kubevirt integration (Jones, Bruce E) 2. StarlingX Introduction session for the Summit - ACTION NEEDED (Ildiko Vancsa) 3. rook-ceph core reviewers needed (Scott Little) 4. Sanity Master Test LAYERED build ISO 20200915T010922Z (Dimofte, Alexandru) ---------------------------------------------------------------------- Message: 1 Date: Tue, 15 Sep 2020 14:26:52 +0000 From: "Jones, Bruce E" To: "bnovickovs at weecodelab.com" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Kubevirt integration Message-ID: Content-Type: text/plain; charset="utf-8" We've thought about kubevirt, but I don't believe it's been implemented yet. StarlingX does support Kata Containers. See https://docs.starlingx.io/operations/kata_container.html. brucej -----Original Message----- From: bnovickovs at weecodelab.com Sent: Tuesday, September 15, 2020 2:17 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Kubevirt integration Hello, I am wondering, guys if you thought about Kubevirt integration https://kubevirt.io/ for VM workloads. In case if somebody does not want to deploy openstack on top of kube cluster and save on resources, kubevirt could be a really good alternative to that? Thank you and regards _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ Message: 2 Date: Tue, 15 Sep 2020 17:37:19 +0200 From: Ildiko Vancsa To: StarlingX ML Subject: [Starlingx-discuss] StarlingX Introduction session for the Summit - ACTION NEEDED Message-ID: Content-Type: text/plain; charset=utf-8 Hi, I’m reaching out about the upcoming virtual Open Infrastructure Summit. To make sure that the project is getting a good exposure at the event as well as giving opportunities to reach out to potential new contributors as well as users we are asking all OSF projects to prepare an introductory 101 session. The goal is to give attendees an introduction to the project, as well as further guidance on how to get involved. Some further guidance for the session: * Title: “StarlingX Overview” * 10 - 15 minute recording with time for live text chat Q&A (max session time of 30 minutes) * Oriented toward beginner audience * High-level overview suggested touch points: * Explain what the project is * Where it fits in the software stack * Open source projects it integrates with * Tools used to contribute/where to find us online * How it follows the 4 Opens We are looking for a volunteer or volunteers to put together and record the session. __If you are interested in volunteering please let me know as soon as possible.__ Please let me know if you have any questions. Thanks, Ildikó ------------------------------ Message: 3 Date: Tue, 15 Sep 2020 12:41:17 -0400 From: Scott Little To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] rook-ceph core reviewers needed Message-ID: <221e43ba-5ce8-a309-a742-2303efc085c6 at windriver.com> Content-Type: text/plain; charset="utf-8"; Format="flowed" We need to nominate a few core reviewers for the rook-ceph project. Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 4 Date: Tue, 15 Sep 2020 17:05:06 +0000 From: "Dimofte, Alexandru" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200915T010922Z Message-ID: Content-Type: text/plain; charset="utf-8" Sanity Test from 2020-September-15 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200915T010922Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200915T010922Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal 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 06 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment We don't have yet the results for Virtual Environment because we experienced some timeouts and we triggered again this jobs. Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20513 bytes Desc: image003.png URL: ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 28, Issue 41 ************************************************* From Ankush.Rai at commscope.com Wed Sep 16 08:05:47 2020 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Wed, 16 Sep 2020 08:05:47 +0000 Subject: [Starlingx-discuss] DANM support In-Reply-To: References: Message-ID: Please provide some pointers Thanks, Ankush From: Rai, Ankush Sent: Tuesday, September 1, 2020 1:29 PM To: starlingx-discuss at lists.starlingx.io Subject: DANM support Any guideline or pointer to run DANM over starlingx setup? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Sep 16 11:58:55 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 16 Sep 2020 11:58:55 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Sep 16, 2020) Message-ID: Hi all, reminder of the TSC/Community call coming up later today. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200916T1400 From oliver.lovaszi at intel.com Wed Sep 16 12:59:30 2020 From: oliver.lovaszi at intel.com (Lovaszi, Oliver) Date: Wed, 16 Sep 2020 12:59:30 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200916T013238Z Message-ID: Sanity Test from 2020-Spetember-16 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200916T013238Z/outputs/iso/) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200916T013238Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment Virtual Environment sanity test was not executed. Regards, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Wed Sep 16 13:47:11 2020 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Wed, 16 Sep 2020 13:47:11 +0000 Subject: [Starlingx-discuss] rook-ceph core reviewers needed In-Reply-To: References: <221e43ba-5ce8-a309-a742-2303efc085c6@windriver.com> , Message-ID: +1 ________________________________ From: Hu, Yong Sent: Tuesday, September 15, 2020 8:29 PM To: Penney, Don ; Little, Scott ; starlingx-discuss at lists.starlingx.io Cc: Sun, Austin Subject: Re: [Starlingx-discuss] rook-ceph core reviewers needed Yeah, I’d like to nominate Austin to be one of core on this project. Regards, Yong From: "Penney, Don" Date: Wednesday, September 16, 2020 at 2:03 AM To: "Little, Scott" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] rook-ceph core reviewers needed I would expect we would need storage folks like Bob and Ovidiu and the folks familiar with the rook work (Martin and Austin?) From: Scott Little Sent: Tuesday, September 15, 2020 12:41 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] rook-ceph core reviewers needed We need to nominate a few core reviewers for the rook-ceph project. Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Sep 16 14:24:55 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 16 Sep 2020 10:24:55 -0400 Subject: [Starlingx-discuss] rook-ceph core reviewers needed In-Reply-To: References: <221e43ba-5ce8-a309-a742-2303efc085c6@windriver.com> Message-ID: <2f31b2a3-c35b-0bf9-a782-ba4913facfe1@windriver.com> Added Bob, Ovidiu and Austin Scott On 2020-09-16 9:47 a.m., Bailey, Henry Albert (Al) wrote: > +1 > ------------------------------------------------------------------------ > *From:* Hu, Yong > *Sent:* Tuesday, September 15, 2020 8:29 PM > *To:* Penney, Don ; Little, Scott > ; starlingx-discuss at lists.starlingx.io > > *Cc:* Sun, Austin > *Subject:* Re: [Starlingx-discuss] rook-ceph core reviewers needed > > Yeah, I’d like to nominate Austin to be one of core on this project. > > Regards, > > Yong > > *From: *"Penney, Don" > *Date: *Wednesday, September 16, 2020 at 2:03 AM > *To: *"Little, Scott" , > "starlingx-discuss at lists.starlingx.io" > > *Subject: *Re: [Starlingx-discuss] rook-ceph core reviewers needed > > I would expect we would need storage folks like Bob and Ovidiu and the > folks familiar with the rook work (Martin and Austin?) > > *From:*Scott Little > *Sent:* Tuesday, September 15, 2020 12:41 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] rook-ceph core reviewers needed > > We need to nominate a few core reviewers for the rook-ceph project. > > Scott > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Sep 16 14:48:11 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 16 Sep 2020 14:48:11 +0000 Subject: [Starlingx-discuss] TSC meeting minutes Sep 16 2020 Message-ID: Standing topics: * Pending reviews for stx-governance * https://review.openstack.org/#/q/project:starlingx/governance,n,z * Pending reviews for stx-specshttps://etherpad.opendev.org/p/stx-cores * https://review.openstack.org/#/q/status:open+AND+project:%255Estarlingx/specs 9/16/2020 * Request meta-starlingx repo in opendev vs meta-starlingx in github/starlingx org - sgw * This is for the open embedded work in the multi-os team. The repo is an open embeded layer with patches and recipes to create an OE-based StarlingX. * No objections from the community * Who owns the github.com/starlingx repos? - Saul to ask on the mailing list -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Sep 16 14:49:56 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 16 Sep 2020 14:49:56 +0000 Subject: [Starlingx-discuss] StarlingX community call Sep 16 2020 Message-ID: Sep 16 * Standing Topics * Sanity has been Green. Alex has found that with layered images from the last 3 days that BM is fine, but virutal is showing a problem. * Usually tests run in just a few minutes each, but tests are running 10x slower - changed from 2 minutes per test to 20-30 minutes per test!!! * All configurations show the issue. * This started for the runs on Sept 15th. What changes merged prior to that? Last green run was from Sept 10th. * Reiews that have merged can be found here: https://review.opendev.org/#/q/projects:starlingx+is:merged+branch:master * Nic to open an LP * Gerrit Reviews in Need of Attention * Ceph/Rook reviews - addressing comments from Greg, more work is needed to resolve them. Austin to set a call with cores to discuss. * See https://review.opendev.org/#/q/status:open+branch:master+topic:%22ceph+containerization%22 * Topics for this Week * Project 101 session for the Summit - Volunteer(s) needed!! - ildikov o Title: "StarlingX Overview" o 10 - 15 minute recording with time for live text chat Q&A (max session time of 30 minutes) o Oriented toward beginner audience o High-level overview suggested touch points: * Explain what the project is * Where it fits in the software stack * Open source projects it integrates with * Tools used to contribute/where to find us online * How it follows the 4 Opens ? Yong volunteered to do the recording, thank you! He and/or community members can cover the Q&A o The on-boarding deck on www.starlingx.io is one option for this content, but that deck is out of date a bit. Bruce can update it - Ildiko please see if you have the source. ? https://opendev.org/starlingx/docs/src/branch/master/resources/StarlingX_Onboarding_Deck_February_2020.pptx * Zoom requires a passcode starting September 27 - ildikov * This will require changing the link that we have been using for the last year or so to a new link. * De-branding Approach * Current de-branding changes should merge in an orderly way. Start with below patches - o https://review.opendev.org/#/c/687401/ o https://review.opendev.org/#/c/687403/ ? These can be merged once we get some +2's from the Cores - Scott will then remove the -1. * Focus on the changes that are visible to end users first, e.g. messages written to log files. * Limit to those that ARE tied to the build infrastructure. e.g. TIS_PATCH_VER in build_srpm.data and %{?_tis_dist}.%{tis_patch_ver} in spec files. * Changing text in source code comments and other innocuous places is not a priority * Google docs spreadsheet with fields for package, file path, reference type, reference value - ability to filter and/or sort on a field. change in a co-ordinated fashion. * ARs from Previous Meetings ? Nic/Yang: feedback from test perspective on stx.4.0 lessons learned - not set up yet ? Docker images - Scott - we are OK on the build side, not sure if we are OK from the test side (60-100 image limit from one IP per hour) ? AR: Release Team discuss whether or not we should just go ahead & nuke stx.2.0 now, as is our stated policy -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Wed Sep 16 18:21:00 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 16 Sep 2020 20:21:00 +0200 Subject: [Starlingx-discuss] Zoom meeting link change - IMPORTANT UPDATE Message-ID: Hi, I’m reaching out to you about a recent update in the Zoom policies. Starting September 27th Zoom will require the meetings to have a passcode or waiting room setup for every call. We will use the passcode option which results in a new link to join the calls. We will __switch to the new links starting next Monday (September 21)__ to allow a short test period to make sure everything works by the time the policy will be enforced. __I will update the wiki with the new meeting links that you will be able to use over the weekend.__ Please let me know if you have any questions. Thanks, Ildikó From maryx.camp at intel.com Wed Sep 16 21:35:31 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 16 Sep 2020 21:35:31 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-09-16 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings << Starting 21Sep20, STX Zoom meetings will change to add a passcode. Check here for new link/info. [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2020-09-16 All -- reviews merged since last meeting: 0 All -- bug status -- 6 total - team agrees to defer all low priority LP until the upstreaming effort is completed. Reviews in progress: Several reviews related to Rook are being worked: https://review.opendev.org/#/q/status:open+project:starlingx/docs+branch:master+topic:ceph-cluster-editorial Mary question: about these changes against "R5" install guides... when merged, we don't want to cherry-pick these changes into the R4 branch, right? Rook is NOT officially in r4.0 but code will merge quickly afterwards. Orig review 723291 has link to story https://storyboard.openstack.org/#!/story/2005527 All -- Opens Upstreaming WR docs status + Need to submit batches larger than expected due to links within docs. Tox fails due to missing links, not just a warning. Probably will have to submit 1 entire book at a time. Plan is to comment out the links to other docs. Ron and team will come up with suggested comment string to use for cleanup later. + Need to merge the "substitutions" review so that further testing can happen. Mary gave +2 during meeting. After meeting, Bruce also +2, then +1 workflow. This is now merged. + Question about mini-TOC at the beginning of guides. Relevant in STX docs because they are monolithic guides and some are very long. Different for WR because the DITA topics are generally small by design. We agreed that adding a mini-TOC is a judgement call during the conversion process. Preliminary guideline is: if the RST file has more than one level1 heading (not title) and the 2nd level1 heading is >75 lines down the page, then add mini-TOC . Here is example of the lines to add: .. contents:: :local: :depth: 1 + Acronyms - we discussed the best method to implement, pre-conversion vs post-processing, seems a toss-up. We agreed to not do anything special for the first document and evaluate afterwards. We could use the substitutions file to fix after. + AR Mary to send Ron/Juanita my cheatsheet with info about Sublime text editor and the plugins that I use (line length, blank spaces, etc). Display multiple versions of STX docs - No updates this week. Release 3.0.1: Mary will attend release meeting this week and ask about Release Notes. Likely to be a simple format like R2.01 RN [https://docs.starlingx.io/releasenotes/r2_0_1_release.html] Housekeeping note: Starting next week, Zoom meetings will change to add a passcode. New link/passcode will be available here after the weekend: https://wiki.openstack.org/wiki/Starlingx/Meetings#12:30pm_Pacific_-_Docs_Team_Call -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Wed Sep 16 22:13:35 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 16 Sep 2020 22:13:35 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-09-16 In-Reply-To: References: Message-ID: <20200916221334.tafb7zfsmjchezdo@yuggoth.org> On 2020-09-16 21:35:31 +0000 (+0000), Camp, MaryX wrote: [...] > Display multiple versions of STX docs - No updates this week. [...] Yep, sorry, I think I'm going to need to copy some additional openstackdocstheme files into https://review.opendev.org/750005 (as evidenced by draft builds for its https://review.opendev.org/750006 child change), but I've been distracted by other fires for a couple of weeks. If anybody is interested in helping with that migration effort, please feel free to push up your own revisions, I won't be offended! ;) -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From alexandru.dimofte at intel.com Thu Sep 17 09:46:43 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 17 Sep 2020 09:46:43 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200917T013238Z Message-ID: Sanity Test from 2020-Spetember-17 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200917T013238Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200917T013238Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment Virtual Environment sanity test was not executed. Timeouts exceeded. See: https://bugs.launchpad.net/starlingx/+bug/1895858 Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20513 bytes Desc: image003.png URL: From Saul.Wold at windriver.com Thu Sep 17 15:20:09 2020 From: Saul.Wold at windriver.com (Wold, Saul) Date: Thu, 17 Sep 2020 15:20:09 +0000 Subject: [Starlingx-discuss] Looking for owners/members of the github/starlingx org repos Message-ID: Folks, The project created a github organization called StarlingX to host a mirror of the opendev.org repos, I think as a requirement for the CNCF certification. I am not sure if this was setup by Dean, I tried to reach out to him by IRC, but no response right now. If anyone is a member of the StarlingX Org on Github, please speak up. Thanks Sau! From Greg.Waines at windriver.com Thu Sep 17 15:38:16 2020 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 17 Sep 2020 15:38:16 +0000 Subject: [Starlingx-discuss] Looking for owners/members of the github/starlingx org repos In-Reply-To: References: Message-ID: It’s me and dariush. Greg. From: "Wold, Saul" Date: Thursday, September 17, 2020 at 11:23 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Looking for owners/members of the github/starlingx org repos Folks, The project created a github organization called StarlingX to host a mirror of the opendev.org repos, I think as a requirement for the CNCF certification. I am not sure if this was setup by Dean, I tried to reach out to him by IRC, but no response right now. If anyone is a member of the StarlingX Org on Github, please speak up. Thanks Sau! _______________________________________________ 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 Saul.Wold at windriver.com Thu Sep 17 16:19:09 2020 From: Saul.Wold at windriver.com (Saul Wold) Date: Thu, 17 Sep 2020 09:19:09 -0700 Subject: [Starlingx-discuss] Looking for owners/members of the github/starlingx org repos In-Reply-To: References: Message-ID: On 9/17/20 8:38 AM, Waines, Greg wrote: > It’s me and dariush. > Maybe we could make sure the members are visible to public level and add Scott and/or Davlet to that list? Thanks. Sau! > Greg. > > *From: *"Wold, Saul" > *Date: *Thursday, September 17, 2020 at 11:23 AM > *To: *"starlingx-discuss at lists.starlingx.io" > > *Subject: *[Starlingx-discuss] Looking for owners/members of the > github/starlingx org repos > > Folks, > > The project created a github organization called StarlingX to host a > mirror of the opendev.org repos, I think as a requirement for the CNCF > certification.  I am not sure if this was setup by Dean, I tried to > reach out to him by IRC, but no response right now. > > If anyone is a member of the StarlingX Org on Github, please speak up. > > Thanks > >   Sau! > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Sau! From Greg.Waines at windriver.com Thu Sep 17 16:50:35 2020 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 17 Sep 2020 16:50:35 +0000 Subject: [Starlingx-discuss] Looking for owners/members of the github/starlingx org repos In-Reply-To: References: Message-ID: Done. ( should have mentioned that Ildiko is an owner as well ) From: "Wold, Saul" Date: Thursday, September 17, 2020 at 12:19 PM To: Greg Waines , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Looking for owners/members of the github/starlingx org repos On 9/17/20 8:38 AM, Waines, Greg wrote: It’s me and dariush. Maybe we could make sure the members are visible to public level and add Scott and/or Davlet to that list? Thanks. Sau! Greg. *From: *"Wold, Saul" > *Date: *Thursday, September 17, 2020 at 11:23 AM *To: *"starlingx-discuss at lists.starlingx.io" > *Subject: *[Starlingx-discuss] Looking for owners/members of the github/starlingx org repos Folks, The project created a github organization called StarlingX to host a mirror of the opendev.org repos, I think as a requirement for the CNCF certification. I am not sure if this was setup by Dean, I tried to reach out to him by IRC, but no response right now. If anyone is a member of the StarlingX Org on Github, please speak up. Thanks Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Sau! -------------- next part -------------- An HTML attachment was scrubbed... URL: From amy at demarco.com Thu Sep 17 18:50:18 2020 From: amy at demarco.com (Amy Marrich) Date: Thu, 17 Sep 2020 13:50:18 -0500 Subject: [Starlingx-discuss] [Diversity] Diversity & Inclusion WG Meeting 9/21 - Removing Divisive Language Message-ID: The Diversity and Inclusion WG will be holding a meeting to continue drafting the OSF's stance on the removal of Divisive Language within the OSF projects. The WG invites members of all OSF projects to participate in this effort and to join us at our next meeting Monday, September 21, at 17:00 UTC which will be held at https://meetpad.opendev.org/osf-diversity-and-inclusion. Drafts for the stance can be found at https://etherpad.opendev.org/p/divisivelanguage If you have any questions please let me and the team know here, on #openstack-diversity on IRC, or you can email me directly. Thanks, Amy Marrich (spotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Sep 17 20:18:08 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 17 Sep 2020 20:18:08 +0000 Subject: [Starlingx-discuss] Release proposal Message-ID: Here is a proposal for one way we could move forward on release planning. For those of you who didn't attend the release team call, there are two problems we need to solve: 1. Our policy has been to schedule releases aligned with upstream OpenStack, with a 6-8 week lag. OpenStack Victoria is planned to release Oct 26 and we don't have a closed plan for the StarlingX 5.0 release, because... 2. We have content that has been agreed to be an Anchor Feature for 5.0 that does not yet have anyone available to do the work In a sidebar conversation today with David and Dariush, Dariush suggested that we consider doing a 4.1 release on or near to the "Victoria + 6-8 weeks" schedule, and include the content that can be delivered in that timeframe. The key feature would likely be Ceph/Rook, which is in the process of merging. This allows us to get a release out the door on the current schedule, and defer the CentOS/Py2->3/OpenStack update work to later, giving us more time to figure out how to do the work. We could include those updates in a 5.0 release, tentatively planned for Aug 2021. Shuquan and Wang - do you agree with this direction? There are details to be worked out, but the TSC needs to give the release team direction as to how to proceed, and this proposal makes sense to me. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From bnovickovs at weecodelab.com Fri Sep 18 10:33:46 2020 From: bnovickovs at weecodelab.com (bnovickovs at weecodelab.com) Date: Fri, 18 Sep 2020 11:33:46 +0100 Subject: [Starlingx-discuss] Openstack UI request: Elektra as an alternative to Horizon Message-ID: Hello, I think we are all aware that Horizon can be very slow. Thus, I am wondering if other UI can be added as a feature in next slx releases: https://github.com/sapcc/elektra Thank you From alexandru.dimofte at intel.com Fri Sep 18 16:14:47 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 18 Sep 2020 16:14:47 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200918T013248Z Message-ID: Sanity Test from 2020-Spetember-18 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200918T013248Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200918T013248Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment Virtual Environment sanity test was not executed. Timeouts exceeded. See: https://bugs.launchpad.net/starlingx/+bug/1895858 Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20513 bytes Desc: image002.png URL: From fungi at yuggoth.org Fri Sep 18 17:07:36 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Fri, 18 Sep 2020 17:07:36 +0000 Subject: [Starlingx-discuss] Openstack UI request: Elektra as an alternative to Horizon In-Reply-To: References: Message-ID: <20200918170736.p62nnlhj7n4pmfm3@yuggoth.org> On 2020-09-18 11:33:46 +0100 (+0100), bnovickovs at weecodelab.com wrote: > I think we are all aware that Horizon can be very slow. Thus, I am > wondering if other UI can be added as a feature in next slx > releases: > > https://github.com/sapcc/elektra Looks neat! I didn't know that existed until now. I suppose if you want to add any plugins you need to have some experience with Ruby/Rails (as well as Javascript obviously), but that's probably not a show-stopper. The license seems to be a mix of Apache and MIT/Expat, so no concerns there that I can see. There's been renewed discussion within OpenStack in recent months about a potential Horizon rewrite/successor, so if you're interested in this topic it may also be a good idea to get involved there with requirements gathering and whatever else makes sense: http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015551.html http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016347.html http://lists.openstack.org/pipermail/openstack-discuss/2020-September/017299.html -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From build.starlingx at gmail.com Fri Sep 18 18:52:22 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Sep 2020 14:52:22 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_repo_sync_layered - Build # 923 - Failure! Message-ID: <1192251534.91.1600455142828.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 923 Status: Failure Timestamp: 20200918T185210Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200918T185110Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MANIFEST: compile.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200918T185110Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200918T185110Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler From build.starlingx at gmail.com Fri Sep 18 18:52:24 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Sep 2020 14:52:24 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_master - Build # 280 - Failure! Message-ID: <1677493600.94.1600455145274.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 280 Status: Failure Timestamp: 20200918T185110Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200918T185110Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true From build.starlingx at gmail.com Fri Sep 18 19:59:02 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Sep 2020 15:59:02 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_master - Build # 281 - Still Failing! In-Reply-To: <51512051.92.1600455143472.JavaMail.javamailuser@localhost> References: <51512051.92.1600455143472.JavaMail.javamailuser@localhost> Message-ID: <651571465.98.1600459142739.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 281 Status: Still Failing Timestamp: 20200918T185613Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200918T185613Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true From build.starlingx at gmail.com Fri Sep 18 21:54:50 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Sep 2020 17:54:50 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_master - Build # 282 - Still Failing! In-Reply-To: <538588897.96.1600459140443.JavaMail.javamailuser@localhost> References: <538588897.96.1600459140443.JavaMail.javamailuser@localhost> Message-ID: <1595866078.101.1600466090719.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 282 Status: Still Failing Timestamp: 20200918T204702Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200918T204702Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true From build.starlingx at gmail.com Fri Sep 18 23:12:08 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Sep 2020 19:12:08 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_master - Build # 283 - Still Failing! In-Reply-To: <362783124.99.1600466088593.JavaMail.javamailuser@localhost> References: <362783124.99.1600466088593.JavaMail.javamailuser@localhost> Message-ID: <71255010.106.1600470728728.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 283 Status: Still Failing Timestamp: 20200918T222536Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200918T222536Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true From build.starlingx at gmail.com Sat Sep 19 00:13:46 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Sep 2020 20:13:46 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_populate - Build # 834 - Failure! Message-ID: <257333280.110.1600474427086.JavaMail.javamailuser@localhost> Project: STX_build_populate Build #: 834 Status: Failure Timestamp: 20200919T001344Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200918T234925Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20200918T234925Z DOCKER_BUILD_ID: jenkins-master-compiler-20200918T234925Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200918T234925Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200918T234925Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Sat Sep 19 00:13:48 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Sep 2020 20:13:48 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_master - Build # 284 - Still Failing! In-Reply-To: <1175329834.104.1600470727022.JavaMail.javamailuser@localhost> References: <1175329834.104.1600470727022.JavaMail.javamailuser@localhost> Message-ID: <742282474.113.1600474429373.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 284 Status: Still Failing Timestamp: 20200918T234925Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200918T234925Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true From build.starlingx at gmail.com Sat Sep 19 02:00:09 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Sep 2020 22:00:09 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_populate - Build # 837 - Failure! Message-ID: <1304022818.118.1600480810625.JavaMail.javamailuser@localhost> Project: STX_build_populate Build #: 837 Status: Failure Timestamp: 20200919T020007Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200919T013225Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200919T013225Z DOCKER_BUILD_ID: jenkins-master-flock-20200919T013225Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200919T013225Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200919T013225Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From build.starlingx at gmail.com Sat Sep 19 02:00:12 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 18 Sep 2020 22:00:12 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 254 - Failure! Message-ID: <949484224.121.1600480812985.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 254 Status: Failure Timestamp: 20200919T013225Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200919T013225Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Sat Sep 19 04:50:59 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 19 Sep 2020 00:50:59 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 875 - Failure! Message-ID: <553133827.125.1600491060234.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 875 Status: Failure Timestamp: 20200919T045054Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200919T043000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200919T043000Z DOCKER_BUILD_ID: jenkins-master-20200919T043000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200919T043000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200919T043000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Sat Sep 19 04:51:01 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 19 Sep 2020 00:51:01 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 678 - Failure! Message-ID: <478264369.128.1600491062452.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 678 Status: Failure Timestamp: 20200919T043000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200919T043000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From build.starlingx at gmail.com Sat Sep 19 04:51:23 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 19 Sep 2020 00:51:23 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1109 - Failure! Message-ID: <1670187726.131.1600491083862.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 1109 Status: Failure Timestamp: 20200919T045100Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200919T043000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200919T043000Z DOCKER_BUILD_ID: jenkins-master-20200919T043000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200919T043000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200919T043000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/monolithic From haochuan.z.chen at intel.com Sat Sep 19 14:44:23 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Sat, 19 Sep 2020 14:44:23 +0000 Subject: [Starlingx-discuss] patch review for rook-ceph In-Reply-To: References: Message-ID: Hi Greg and Mary I have updated patch. Wait for your review comment. For multi-node, I add rook-storage type. So there will be controller-storage, dedicated-storage and rook-storage for multi-system. BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Waines, Greg Sent: Tuesday, September 15, 2020 8:05 AM To: Chen, Haochuan Z ; Camp, MaryX ; starlingx-discuss at lists.starlingx.io Subject: Re: patch review for rook-ceph I provided comments on: * doc/source/deploy_install_guides/r5_release/virtual/aio_simplex_install_kubernetes.rst * doc/source/deploy_install_guides/r5_release/virtual/aio_duplex_install_kubernetes.rst Are you providing updates to ??? * VIRTUAL Standard w/controller storage INSTALL GUIDE * VIRTUAL Standard w/dedicated storage INSTALL GUIDE * BARE METAL aio-simplex INSTALL GUIDE * BARE METAL aio-duplex INSTALL GUIDE * BARE METAL Standard w/controller storage INSTALL GUIDE * BARE METAL Standard w/dedicated storage INSTALL GUIDE Greg. From: "Chen, Haochuan Z" > Date: Thursday, September 10, 2020 at 11:41 PM To: "Camp, MaryX" >, "starlingx-discuss at lists.starlingx.io" >, Greg Waines > Subject: RE: patch review for rook-ceph Hi Greg As your review comment, I move rook simplex and duplex deployment guide to r5 deployment guide. doc/source/deploy_install_guides/r5_release/virtual/aio_simplex_install_kubernetes.rst doc/source/deploy_install_guides/r5_release/virtual/aio_duplex_install_kubernetes.rst https://review.opendev.org/#/c/751158/ After the above patch merged, these two patch will be abandoned. https://review.opendev.org/#/c/742573/ https://review.opendev.org/#/c/742102/ BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Thursday, September 3, 2020 1:52 PM To: Camp, MaryX >; starlingx-discuss at lists.starlingx.io; Waines, Greg > Subject: RE: patch review for rook-ceph Hi Mary I update patch for doc. For these three patch, you could only review the first only, doc for standard multi node system deployment. I will update both three patch. https://review.opendev.org/#/c/724623/ https://review.opendev.org/#/c/742102/ https://review.opendev.org/#/c/742573/ Hi Greg I agree, move these two patch to R5 together with simple and duplex deployment. I will update late. https://review.opendev.org/#/c/742102/ https://review.opendev.org/#/c/742573/ BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, September 1, 2020 8:31 AM To: Camp, MaryX >; starlingx-discuss at lists.starlingx.io; Bailey, Henry Albert (Al) > Subject: RE: patch review for rook-ceph Thanks Mary, I will update doc in this week. Martin, Chen IOTG, Software Engineer 021-61164330 From: Camp, MaryX > Sent: Tuesday, September 1, 2020 2:53 AM To: Chen, Haochuan Z >; starlingx-discuss at lists.starlingx.io; Bailey, Henry Albert (Al) > Subject: RE: patch review for rook-ceph Hi Martin, There are 5 reviews in progress for STX docs for rook-ceph. Can you please resolve the outstanding comments? Then the docs team will review again. https://review.opendev.org/#/q/status:open+project:starlingx/docs+branch:master+topic:ceph-cluster-editorial Thanks in advance, Mary Camp PTIGlobal Technical Writer | maryx.camp at intel.com From: Chen, Haochuan Z > Sent: Monday, August 31, 2020 11:16 AM To: starlingx-discuss at lists.starlingx.io; Bailey, Henry Albert (Al) > Subject: [Starlingx-discuss] patch review for rook-ceph Thanks AL review my patch for rook-ceph Appreciate more reviewer for my patch. https://review.opendev.org/#/q/topic:%22ceph+containerization%22+(status:open+OR+status:merged) Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Sat Sep 19 15:23:40 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 19 Sep 2020 15:23:40 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200919T055106Z Message-ID: Sanity Test from 2020-Spetember-19 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200919T055106Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200919T055106Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment Virtual Environment sanity test was not executed. Timeouts exceeded. See: https://bugs.launchpad.net/starlingx/+bug/1895858 Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20513 bytes Desc: image002.png URL: From scott.little at windriver.com Sun Sep 20 05:09:36 2020 From: scott.little at windriver.com (Scott Little) Date: Sun, 20 Sep 2020 01:09:36 -0400 Subject: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_master - Build # 284 - Still Failing! In-Reply-To: <742282474.113.1600474429373.JavaMail.javamailuser@localhost> References: <1175329834.104.1600470727022.JavaMail.javamailuser@localhost> <742282474.113.1600474429373.JavaMail.javamailuser@localhost> Message-ID: Apologies for this series of failures. A slip of the mouse had me accidentally hitting the 'Workflow +1' button on one of the debranding inspections that was still under test. Because of the underlying transformation of the download directory structure, and the lack of a reverse transformation, It seemed like my best option was to forge ahead.  A test compile of the compiler layer found a problem that I had to correct. If you ran a 'repo sync' followed by a 'download_mirror.sh' between Sept 18 6:00 pm UTC and Sept 19 1:30 am UTC, you may have seen failures. Look under your stx-tools/centos-mirror-tools/output/.  If you see both 'stx' and 'stx-r1' directories, you have a problem. Work around if the problem persists is to - Verify that any files under 'stx-r1/CentOS/pike' have been copied over to an identical directory sub-structure under 'stx/CentOS/'. - Delete directory 'stx-r1'. Scott On 2020-09-18 8:13 p.m., build.starlingx at gmail.com wrote: > Project: STX_build_layer_compiler_master_master > Build #: 284 > Status: Still Failing > Timestamp: 20200918T234925Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200918T234925Z/logs > -------------------------------------------------------------------------------- > Parameters > > FULL_BUILD: false > FORCE_BUILD: true > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Sun Sep 20 07:00:05 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Sun, 20 Sep 2020 09:00:05 +0200 Subject: [Starlingx-discuss] Zoom meeting link change - IMPORTANT UPDATE In-Reply-To: References: Message-ID: Hi, As mentioned in my previous email the Zoom dial-in information needs to be updated due to a policy change. I updated all the StarlingX Zoom meetings to require a passcode which resulted in a new meeting link for each call. You can find the __updated Zoom dial-in__ information on the wiki: https://wiki.openstack.org/wiki/Starlingx/Meetings Those of you who maintain a meeting invite please do not forget to update those. Please let me know if you have any questions. Thanks, Ildikó > On Sep 16, 2020, at 20:21, Ildiko Vancsa wrote: > > Hi, > > I’m reaching out to you about a recent update in the Zoom policies. > > Starting September 27th Zoom will require the meetings to have a passcode or waiting room setup for every call. We will use the passcode option which results in a new link to join the calls. > > We will __switch to the new links starting next Monday (September 21)__ to allow a short test period to make sure everything works by the time the policy will be enforced. > > __I will update the wiki with the new meeting links that you will be able to use over the weekend.__ > > Please let me know if you have any questions. > > Thanks, > Ildikó > > From amy at demarco.com Mon Sep 21 18:35:54 2020 From: amy at demarco.com (Amy Marrich) Date: Mon, 21 Sep 2020 13:35:54 -0500 Subject: [Starlingx-discuss] [Diversity] Community feedback on Divisive Language stance Message-ID: The OSF Diversity & Inclusion WG has been working on creating the OSF's stance concerning divisive language. We will be holding one more meeting before sending the stance to the OSF Board for any changes before bringing it back to the Community. Our goal however is to get your input now to reduce any concerns in the future! Please check out Draft 4 on the etherpad[0] and place your comments there and join us on October 5th (meeting information will be sent out closer to the meeting) Thanks, Amy (spotz) 0 - https://etherpad.opendev.org/p/divisivelanguage -------------- next part -------------- An HTML attachment was scrubbed... URL: From bnovickovs at weecodelab.com Mon Sep 21 18:49:24 2020 From: bnovickovs at weecodelab.com (bnovickovs at weecodelab.com) Date: Mon, 21 Sep 2020 19:49:24 +0100 Subject: [Starlingx-discuss] Openstack: Correct configuration with 1 interface available for data network Message-ID: <2f4e3273c1ae2aefb01a26f53bcb75f3@weecodelab.com> Hello, I have 3 bare-metal servers therefore, I went for 2+2 aio-duplex setup. Simple non-manageable switch. (No vlans) controller-0 - 3 NIC, 1 for mngmt/cluster, 1 for OAM, 1 for data network. controller-1 - 3 NIC, 1 for mngmt/cluster, 1 for OAM, 1 for data network. worker-0 - 2 NIC, 1 for mngmt/cluster, 1 for data network. Thus, I am wondering what would be the right process of adding data network to openstack setup? What I ve already tried: 1. Added flat data network on each node: system datanetwork-add physnet0 flat 2. Created external network in openstack: ENABLE_EXT_NET=${ENABLE_EXT_NET:-1} EXT_NET_CIDR=${EXT_NET_CIDR:-'10.0.2.0/24'} EXT_NET_RANGE=${EXT_NET_RANGE:-'start=10.0.2.150,end=10.0.2.199'} EXT_NET_GATEWAY=${EXT_NET_GATEWAY:-'10.0.2.1'} openstack network create --external --provider-physical-network physnet0 \ --provider-network-type flat public1 openstack subnet create --no-dhcp \ --allocation-pool ${EXT_NET_RANGE} --network public1 \ --subnet-range ${EXT_NET_CIDR} --gateway ${EXT_NET_GATEWAY} public1-subnet openstack router set --external-gateway public1 demo-router Using this setup, I cant have any virtual network in openstack using vxlan? If I have dhcp enabled for public1 network, I can create vm assigned with public1 network and ping/ssh machine directly. However, what I can do if I want to have private network and use public1 for my floating ip's? Do I need to have 1 more NIC card and assign data-network(vxlan) to that? Thank you From kennelson11 at gmail.com Mon Sep 21 22:17:38 2020 From: kennelson11 at gmail.com (Kendall Nelson) Date: Mon, 21 Sep 2020 15:17:38 -0700 Subject: [Starlingx-discuss] Fwd: Forum schedule is now LIVE! In-Reply-To: References: Message-ID: Hello Everyone! The forum schedule is now live: https://www.openstack.org/summit/2020/summit-schedule/global-search?t=forum Please let myself or Jimmy McArthur know as soon as possible if you see any conflicts. Speakers will be contacted shortly (if not already) with more details about the event and your sessions. Thanks! -Kendall Nelson (diablo_rojo) -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ankush.Rai at commscope.com Fri Sep 18 05:20:43 2020 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Fri, 18 Sep 2020 05:20:43 +0000 Subject: [Starlingx-discuss] Ubuntu OS support Message-ID: Any pointer to Ubuntu-OS support. Is this already available or line-up for future release? https://wiki.openstack.org/wiki/StarlingX/MultiOS Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Mon Sep 21 08:48:47 2020 From: austin.sun at intel.com (Sun, Austin) Date: Mon, 21 Sep 2020 08:48:47 +0000 Subject: [Starlingx-discuss] [StarlingX] adding Storage Node to k8s cluster discuss meeting Message-ID: Hi Stakeholders: Please join this one time meeting to discuss adding storage node to k8s cluster to prepare rook ceph migration on dedicate storage setup. Zoom Link : https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3926 bytes Desc: not available URL: From yong.hu at intel.com Tue Sep 22 07:12:22 2020 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 22 Sep 2020 07:12:22 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Distro-OpenStack: Bi-weekly Project Meeting Message-ID: <99ec8cbeb54244d9838fb959e534df83@intel.com> We will cancel today’s meeting because there is no particular topic coming out. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3760 bytes Desc: not available URL: From alexandru.dimofte at intel.com Tue Sep 22 10:32:26 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 22 Sep 2020 10:32:26 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200921T230235Z Message-ID: Sanity Test from 2020-Spetember-22 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200921T230235Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200921T230235Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment Virtual Environment sanity test was not executed. Timeouts exceeded. See: https://bugs.launchpad.net/starlingx/+bug/1895858 Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20513 bytes Desc: image002.png URL: From bruce.e.jones at intel.com Tue Sep 22 13:30:44 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 22 Sep 2020 13:30:44 +0000 Subject: [Starlingx-discuss] Ubuntu OS support In-Reply-To: References: Message-ID: There are no plans for Ubuntu as a host OS at this time. It’s a lot of work both up front and over time to enable it. A lot of work… ☹ Can I ask why you are asking? brucej From: Rai, Ankush Sent: Thursday, September 17, 2020 10:21 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Ubuntu OS support Any pointer to Ubuntu-OS support. Is this already available or line-up for future release? https://wiki.openstack.org/wiki/StarlingX/MultiOS Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From mward at akamai.com Tue Sep 22 15:56:16 2020 From: mward at akamai.com (Ward, Martin) Date: Tue, 22 Sep 2020 15:56:16 +0000 Subject: [Starlingx-discuss] Duplex install - How does controller-1 decide which interface to use? Message-ID: I’m trying to set up a duplex install using v4 and I’ve finally managed to get the first box, a virtual machine, up, running and configured. I now boot the second VM, duplex-controller-2 but instead of coming up with four interfaces (OAM, data, mgmt and cluster) the PXE only shows two and neither of them are the management interface, so the second controller doesn’t boot. I’ve struggled with the network settings all through this installation so would really appreciate any suggestions or guidance. I’m installing this using virsh for my virtual machine and network management, the base O/S is CentOS 7.7 |\/|artin -------------- next part -------------- An HTML attachment was scrubbed... URL: From yang.liu at windriver.com Tue Sep 22 15:34:07 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Tue, 22 Sep 2020 15:34:07 +0000 Subject: [Starlingx-discuss] Weekly StarlingX Test meeting Message-ID: 8am Pacific - Test Team Call Call details * https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 * Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o Passcode: 419405 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes * The agenda and notes for each call are here: https://etherpad.openstack.org/p/stx-test * Call recordings: https://wiki.openstack.org/wiki/Starlingx/Meeting_Logs#Test_Team_Call StarlingX Meeting schedules: https://wiki.openstack.org/wiki/Starlingx/Meetings -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 6679 bytes Desc: not available URL: From Dariush.Eslimi at windriver.com Tue Sep 22 16:33:48 2020 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Tue, 22 Sep 2020 16:33:48 +0000 Subject: [Starlingx-discuss] StarlingX Config/DC/Flock/Upgrade Bi-weekly Meeting Message-ID: All, This will not be a status meeting, please bring your questions or bring issues that requires discussions that would help you make decisions. Thanks, Dariush Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC (every 2 weeks) Call details * Zoom link: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 * 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 Meeting notes are at https://etherpad.openstack.org/p/stx-config_DC_flock Subproject wikis: https://wiki.openstack.org/wiki/StarlingX/Config https://wiki.openstack.org/wiki/StarlingX/DistCloud https://wiki.openstack.org/wiki/StarlingX/FlockServices -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2873 bytes Desc: not available URL: From Bill.Zvonar at windriver.com Tue Sep 22 18:54:39 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 22 Sep 2020 18:54:39 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Sep 23, 2020) Message-ID: Hi all, reminder of the TSC/Community call coming up tomorrow. Please feel free to add items to the agenda [0] for the community call & don't forget to use the new Zoom dial in [3], per Ildiko's email [4]. 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=20200923T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 [4] http://lists.starlingx.io/pipermail/starlingx-discuss/2020-September/009677.html From haochuan.z.chen at intel.com Wed Sep 23 00:21:52 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Wed, 23 Sep 2020 00:21:52 +0000 Subject: [Starlingx-discuss] patch review for rook-ceph project Message-ID: + Bob, Ovidiu and Greg Please review my patch for rook-ceph. You can raise any your concern. https://review.opendev.org/716792 Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: Chen, Haochuan Z Sent: Wednesday, September 16, 2020 2:54 PM To: Scott Little ; Sabeel.Ansari at windriver.com Cc: starlingx-discuss at lists.starlingx.io Subject: rook-ceph core reviewers needed Hi scott You can propose a reviewer temporarily, if he review +1, you can review +2 for this patch. https://review.opendev.org/716792 BR! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Wednesday, September 16, 2020 1:05 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 28, Issue 41 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Re: Kubevirt integration (Jones, Bruce E) 2. StarlingX Introduction session for the Summit - ACTION NEEDED (Ildiko Vancsa) 3. rook-ceph core reviewers needed (Scott Little) 4. Sanity Master Test LAYERED build ISO 20200915T010922Z (Dimofte, Alexandru) ---------------------------------------------------------------------- Message: 1 Date: Tue, 15 Sep 2020 14:26:52 +0000 From: "Jones, Bruce E" To: "bnovickovs at weecodelab.com" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Kubevirt integration Message-ID: Content-Type: text/plain; charset="utf-8" We've thought about kubevirt, but I don't believe it's been implemented yet. StarlingX does support Kata Containers. See https://docs.starlingx.io/operations/kata_container.html. brucej -----Original Message----- From: bnovickovs at weecodelab.com Sent: Tuesday, September 15, 2020 2:17 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Kubevirt integration Hello, I am wondering, guys if you thought about Kubevirt integration https://kubevirt.io/ for VM workloads. In case if somebody does not want to deploy openstack on top of kube cluster and save on resources, kubevirt could be a really good alternative to that? Thank you and regards _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ Message: 2 Date: Tue, 15 Sep 2020 17:37:19 +0200 From: Ildiko Vancsa To: StarlingX ML Subject: [Starlingx-discuss] StarlingX Introduction session for the Summit - ACTION NEEDED Message-ID: Content-Type: text/plain; charset=utf-8 Hi, I’m reaching out about the upcoming virtual Open Infrastructure Summit. To make sure that the project is getting a good exposure at the event as well as giving opportunities to reach out to potential new contributors as well as users we are asking all OSF projects to prepare an introductory 101 session. The goal is to give attendees an introduction to the project, as well as further guidance on how to get involved. Some further guidance for the session: * Title: “StarlingX Overview” * 10 - 15 minute recording with time for live text chat Q&A (max session time of 30 minutes) * Oriented toward beginner audience * High-level overview suggested touch points: * Explain what the project is * Where it fits in the software stack * Open source projects it integrates with * Tools used to contribute/where to find us online * How it follows the 4 Opens We are looking for a volunteer or volunteers to put together and record the session. __If you are interested in volunteering please let me know as soon as possible.__ Please let me know if you have any questions. Thanks, Ildikó ------------------------------ Message: 3 Date: Tue, 15 Sep 2020 12:41:17 -0400 From: Scott Little To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] rook-ceph core reviewers needed Message-ID: <221e43ba-5ce8-a309-a742-2303efc085c6 at windriver.com> Content-Type: text/plain; charset="utf-8"; Format="flowed" We need to nominate a few core reviewers for the rook-ceph project. Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 4 Date: Tue, 15 Sep 2020 17:05:06 +0000 From: "Dimofte, Alexandru" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200915T010922Z Message-ID: Content-Type: text/plain; charset="utf-8" Sanity Test from 2020-September-15 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200915T010922Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200915T010922Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal 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 06 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment We don't have yet the results for Virtual Environment because we experienced some timeouts and we triggered again this jobs. Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20513 bytes Desc: image003.png URL: ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 28, Issue 41 ************************************************* From haochuan.z.chen at intel.com Wed Sep 23 00:30:51 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Wed, 23 Sep 2020 00:30:51 +0000 Subject: [Starlingx-discuss] review patch to enable rook-ceph in metal project In-Reply-To: References: Message-ID: Hi folks Please review these three patch, for rook-ceph's backup and restore function. https://review.opendev.org/#/c/734065/ https://review.opendev.org/#/c/735501/ https://review.opendev.org/#/c/737228/ Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, September 15, 2020 9:47 AM To: Bart Wensley ; Penney, Don ; MacDonald, Eric ; Kung, John ; Liu, Tao ; 'Poncea, Ovidiu' Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: review patch to enable rook-ceph in metal project Add Ovidiu. Please review my patch for rook-ceph in metal project. https://review.opendev.org/#/c/737228/ Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, August 10, 2020 11:09 AM To: Bart Wensley >; Penney, Don >; MacDonald, Eric >; Kung, John >; Liu, Tao > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: review patch to enable rook-ceph in metal project Hi folks Please review my patch to enable rook-ceph in metal project. https://review.opendev.org/#/c/737228/ BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Saul.Wold at windriver.com Wed Sep 23 02:06:58 2020 From: Saul.Wold at windriver.com (Saul Wold) Date: Tue, 22 Sep 2020 19:06:58 -0700 Subject: [Starlingx-discuss] Searching for Patch Analysis Spreadsheets Message-ID: <37fcce55-92f0-3487-5118-d036131498d9@windriver.com> StarlingX Folks: I am trying to find the spreadsheets that we shared with the team regarding patch analysis for the early time of StarlingX. I tried looking around the StarlingX google drive and email archives, but my search-foo was not working. I would like to get this for validating the multi-os work. Thanks -- Sau! (Please be sure your replying to my new @windriver email and my @intel email). From chen.dq at neusoft.com Wed Sep 23 06:02:49 2020 From: chen.dq at neusoft.com (chen.dq at neusoft.com) Date: Wed, 23 Sep 2020 06:02:49 +0000 Subject: [Starlingx-discuss] review patch for bug 1894171 Message-ID: Hi Eric Please review my patch for bug 1894171 in metal project. https://review.opendev.org/#/c/752140/ Thanks ! BR! --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Wed Sep 23 12:38:23 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 23 Sep 2020 12:38:23 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200923T035442Z Message-ID: Sanity Test from 2020-Spetember-23 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200923T035442Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200923T035442Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment Virtual Environment sanity test was not executed. Timeouts exceeded. See: https://bugs.launchpad.net/starlingx/+bug/1895858 Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20513 bytes Desc: image002.png URL: From bruce.e.jones at intel.com Wed Sep 23 14:22:14 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 23 Sep 2020 14:22:14 +0000 Subject: [Starlingx-discuss] TSC meeting notes Sep 23 2020 Message-ID: 9/23/2020 * Bruce will be out of the office for the 9/30 meeting. It is a holiday in China as well. Cancel the TSC meeting for next week. * Release proposal: * Summary: Change the release plan to do a 4.1 release in January'21 with the content that can hit that schedule. Defer the Py2->3 and CentOS update work to the 5.0 release in Jul'21. * Hao suggests following this cadence going forward - one big release and one X.1 release per year * How does this affect the maintenance timeframe(currently 12 months)? (ildikov) This is not a change to the release maintenance commitment, just a change to the release number and content. * add SNMPv3 Support https://storyboard.openstack.org/#!/story/2008132 * Confirming meta-starlingx will be added to gerrit * Limited Cores may initially have single +2. * Thanks to the team who met this morning to discuss the Ceph/Rook changes - please share a readout with the community. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ankush.Rai at commscope.com Wed Sep 23 14:18:58 2020 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Wed, 23 Sep 2020 14:18:58 +0000 Subject: [Starlingx-discuss] How to get the list of running docker container ? Message-ID: Running "docker ps" as a sysadmin does not list the running containers. Any reference how to get the list of running container ? sysadmin# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES controller-1:/home/sysadmin# docker info Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: 18.09.6 Storage Driver: overlay2 (keystone_admin)]$ docker ps Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/json: dial unix /var/run/docker.sock: connect: permission denied (keystone_admin)]$ system host-list +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | | 2 | controller-1 | controller | unlocked | enabled | available | +----+--------------+-------------+----------------+-------------+--------------+ (keystone_admin)]$ system application-list +--------------------------+---------+-----------------------------------+----------------------------------------+----------+-----------+ | application | version | manifest name | manifest file | status | progress | +--------------------------+---------+-----------------------------------+----------------------------------------+----------+-----------+ | cert-manager | 1.0-5 | cert-manager-manifest | certmanager-manifest.yaml | applied | completed | | nginx-ingress-controller | 1.0-0 | nginx-ingress-controller-manifest | nginx_ingress_controller_manifest.yaml | applied | completed | | oidc-auth-apps | 1.0-27 | oidc-auth-manifest | manifest.yaml | uploaded | completed | | platform-integ-apps | 1.0-9 | platform-integration-manifest | manifest.yaml | applied | completed | +--------------------------+---------+-----------------------------------+----------------------------------------+----------+-----------+ Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Wed Sep 23 14:32:03 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 23 Sep 2020 14:32:03 +0000 Subject: [Starlingx-discuss] How to get the list of running docker container ? In-Reply-To: References: Message-ID: please try 'crictl ps' command . From: Rai, Ankush Sent: Wednesday, September 23, 2020 10:19 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] How to get the list of running docker container ? Running "docker ps" as a sysadmin does not list the running containers. Any reference how to get the list of running container ? sysadmin# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES controller-1:/home/sysadmin# docker info Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: 18.09.6 Storage Driver: overlay2 (keystone_admin)]$ docker ps Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/json: dial unix /var/run/docker.sock: connect: permission denied (keystone_admin)]$ system host-list +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | | 2 | controller-1 | controller | unlocked | enabled | available | +----+--------------+-------------+----------------+-------------+--------------+ (keystone_admin)]$ system application-list +--------------------------+---------+-----------------------------------+----------------------------------------+----------+-----------+ | application | version | manifest name | manifest file | status | progress | +--------------------------+---------+-----------------------------------+----------------------------------------+----------+-----------+ | cert-manager | 1.0-5 | cert-manager-manifest | certmanager-manifest.yaml | applied | completed | | nginx-ingress-controller | 1.0-0 | nginx-ingress-controller-manifest | nginx_ingress_controller_manifest.yaml | applied | completed | | oidc-auth-apps | 1.0-27 | oidc-auth-manifest | manifest.yaml | uploaded | completed | | platform-integ-apps | 1.0-9 | platform-integration-manifest | manifest.yaml | applied | completed | +--------------------------+---------+-----------------------------------+----------------------------------------+----------+-----------+ Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Wed Sep 23 14:34:23 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 23 Sep 2020 14:34:23 +0000 Subject: [Starlingx-discuss] [StarlingX] MoM adding Storage Node to k8s cluster discuss meeting Message-ID: Hi All: Thanks a lots every one join this meeting. MoM 9/23 meeting: 1) Storage Node is not needed in long term. 2) for dedicated storage migration , suggest approach : reinstall Storage Node ---> worker Node to support migration AR: Austin will take look into this approach. focus on: * not wipe data * any more ceph data needs Test process ,deploy dedicated storage cluster ---> reinstall storage nodes ---> worker nodes ---> migration on worker nodes 3) other rook ceph changes will still ongoing and can get merged if review is ok. 4) will continue discuss approach on next week non-distro openstack meeting 9/30 Thanks BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Sep 23 14:36:57 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 23 Sep 2020 14:36:57 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Sep 23, 2020) In-Reply-To: References: Message-ID: >From today's Community Call: * Standing Topics * Sanity * looking pretty green since last week (on baremetal) * Nic pointed out that they're still having issues on the virtual servers - something new w/ Ubuntu * they're investigating, some tests are failing due to timeouts * Gerrit Reviews in Need of Attention https://review.opendev.org/#/c/716792/ needs another +2 , LP#1894171 rook ceph : https://review.opendev.org/716792 needs another +2 rook ceph B&R https://review.opendev.org/#/c/734065/ need +2 anisble playbook https://review.opendev.org/#/c/735501/ need another +2 puppet https://review.opendev.org/#/c/737228/ waitting Ovidiu to review * Topics for this Week * nothing this week * ARs from Previous Meetings * Nic/Yang: feedback from test perspective on stx.4.0 lessons learned - not set up yet * Docker images - Scott - we are OK on the build side, not sure if we are OK from the test side (60-100 image limit from one IP per hour) * AR: Release Team discuss whether or not we should just go ahead & nuke stx.2.0 now, as is our stated policy - we agreed to just keep it (thought Scott will nuke the build-side artifacts, which are taking up space) * Open Requests for Help * Correct configuration with 1 interface available for data network * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-September/009679.html * can the Networking team weigh in on this question? * Duplex install - How does controller-1 decide which interface to use? * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-September/009686.html * Yong said someone from his team would have a look at this question tomorrow * Build Matters (if required) * Scott mentioned the slip of the mouse issue from the weekend - check his email if you had 'repo sync' type failures in the Sep 18/19 time fram * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-September/009676.html -----Original Message----- From: Zvonar, Bill Sent: Tuesday, September 22, 2020 2:55 PM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Sep 23, 2020) Hi all, reminder of the TSC/Community call coming up tomorrow. Please feel free to add items to the agenda [0] for the community call & don't forget to use the new Zoom dial in [3], per Ildiko's email [4]. 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=20200923T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 [4] http://lists.starlingx.io/pipermail/starlingx-discuss/2020-September/009677.html From haridhar.kalvala at intel.com Wed Sep 23 15:06:14 2020 From: haridhar.kalvala at intel.com (Kalvala, Haridhar) Date: Wed, 23 Sep 2020 15:06:14 +0000 Subject: [Starlingx-discuss] Query on openstack horizon dashboard build Message-ID: Hi Scott, I had observation w.r.t horizon build of openstack_dashboard. Made few changes to add new panel, wanted to test whether its replicate on the horizon dashboard. Tox and python-django-horizon rpm is successful but I do not see any of change reflected on dashboard on deployment. Is their any reference on how to build local changes of openstack_dashboard ? Thank you, Haridhar -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ankush.Rai at commscope.com Wed Sep 23 19:04:30 2020 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Wed, 23 Sep 2020 19:04:30 +0000 Subject: [Starlingx-discuss] how to get rt-kernel support ? Message-ID: Hi, I couldn't find the rpm for rt-kernel. Is starlingx comes up with rt-kernel support or it need to be patched ? Any pointer to get the rt-kernel support ? software_version | 20.06 I am using the latest green image: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_green_build/outputs/iso/bootimage.iso Required rt-kernel patch: kernel-rt-3.10.0-693.2.2.rt56.623.el7.x86_64 Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Wed Sep 23 19:20:36 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 23 Sep 2020 19:20:36 +0000 Subject: [Starlingx-discuss] how to get rt-kernel support ? In-Reply-To: References: Message-ID: The kernel-rt RPM is installed on the "lowlatency" nodes. For AIO, you'd want to install AIO-lowlatency. From: Rai, Ankush Sent: Wednesday, September 23, 2020 3:05 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] how to get rt-kernel support ? Hi, I couldn't find the rpm for rt-kernel. Is starlingx comes up with rt-kernel support or it need to be patched ? Any pointer to get the rt-kernel support ? software_version | 20.06 I am using the latest green image: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_green_build/outputs/iso/bootimage.iso Required rt-kernel patch: kernel-rt-3.10.0-693.2.2.rt56.623.el7.x86_64 Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Wed Sep 23 20:41:20 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 23 Sep 2020 20:41:20 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-09-23 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2020-09-23 All -- reviews merged since last meeting: 1 (Onboarding PPT is archived in docs repo; Onboarding PDF is published on website) All -- bug status -- 7 total - team agrees to defer all low priority LP until the upstreaming effort is completed. new LP submitted by Ildikó (low priority). https://bugs.launchpad.net/starlingx/+bug/1896634 AR Mary to work with Greg on how to resolve (update the note text or the diagram?) Reviews in progress: Update the Release Notes landing page to show R1.0 ands R.2 are EOL https://review.opendev.org/#/c/753140/ Several reviews related to Rook are being worked: https://review.opendev.org/#/q/status:open+project:starlingx/docs+branch:master+topic:ceph-cluster-editorial Upstreaming WR docs status Both Drake's and Keane's reviews are ready for actual review (even though title is DNM): https://review.opendev.org/#/c/753129/ and https://review.opendev.org/#/c/749551/ AR team to dig into these reviews to see if there are other implementation details we need to discuss/resolve. They are going to start working on other guides in the background. Next week: discuss the TOC mapping that Greg shared during planning. AR Mary distribute the docs again before next meeting. Display multiple versions of STX docs Jeremy is busy with other tasks at the moment. Ildikó will try to look at the WIP reviews next week. Mary is going to submit a review with minor editorial cleanup on Governance pages (remove Indices & Tables section, etc). Future work will be to update the theme so it aligns with STX docs. From Ankush.Rai at commscope.com Thu Sep 24 03:42:19 2020 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Thu, 24 Sep 2020 03:42:19 +0000 Subject: [Starlingx-discuss] how to get rt-kernel support ? In-Reply-To: References: Message-ID: Thank you for your response to this query. But I am still not clear on this. Are you saying that, the kernel-rt RPM will get installed only for “lowlatency” nodes? If my understanding is correct then I have few more questions: - How can I set the node as “lowlatency” node? (Is there any documentation reference for this ?) - Can I make the controller node as a low low-latency node or is it possible for only worker nodes ? - What are the pre-requirement for a node to be a low-latency node ? - Post installation, is there a way to make a node as low-latency node ? I have All-in-one-Duplex mode of deployment, both having “controller” personality and “controller,worker” as subfunctions. capabilities | {u'stor_function': u'monitor', u'Personality': u'Controller-Active'} capabilities | {u'stor_function': u'monitor', u'Personality': u'Controller-Standby'} personality | controller subfunctions | controller,worker Regards, Ankush From: Penney, Don Sent: Thursday, September 24, 2020 12:51 AM To: Rai, Ankush ; starlingx-discuss at lists.starlingx.io Subject: RE: how to get rt-kernel support ? The kernel-rt RPM is installed on the “lowlatency” nodes. For AIO, you’d want to install AIO-lowlatency. ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ External (don.penney at windriver.com) Report This Email FAQ Protection by INKY The kernel-rt RPM is installed on the “lowlatency” nodes. For AIO, you’d want to install AIO-lowlatency. From: Rai, Ankush > Sent: Wednesday, September 23, 2020 3:05 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] how to get rt-kernel support ? Hi, I couldn’t find the rpm for rt-kernel. Is starlingx comes up with rt-kernel support or it need to be patched ? Any pointer to get the rt-kernel support ? software_version | 20.06 I am using the latest green image: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_green_build/outputs/iso/bootimage.iso Required rt-kernel patch: kernel-rt-3.10.0-693.2.2.rt56.623.el7.x86_64 Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Thu Sep 24 07:35:32 2020 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 24 Sep 2020 07:35:32 +0000 Subject: [Starlingx-discuss] how to get rt-kernel support ? In-Reply-To: References: Message-ID: Hi Ankush: You can check doc [1] , select 'All-in-one (lowlatency) Controller' for lowlatency , this is same all release r3 , r4 changes, if you want to use Simplex or Duplex system . For multi Nodes setup , only worker nodes support low-latency. There is no pre-requirement for a node to be a low-latency node . I this there is no way to change node to low-latency node after installation except re-install. [1] https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_duplex_install_kubernetes.html Thanks. BR Austin Sun. From: Rai, Ankush Sent: Thursday, September 24, 2020 11:42 AM To: Penney, Don ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] how to get rt-kernel support ? Thank you for your response to this query. But I am still not clear on this. Are you saying that, the kernel-rt RPM will get installed only for "lowlatency" nodes? If my understanding is correct then I have few more questions: * How can I set the node as "lowlatency" node? (Is there any documentation reference for this ?) * Can I make the controller node as a low low-latency node or is it possible for only worker nodes ? * What are the pre-requirement for a node to be a low-latency node ? * Post installation, is there a way to make a node as low-latency node ? I have All-in-one-Duplex mode of deployment, both having "controller" personality and "controller,worker" as subfunctions. capabilities | {u'stor_function': u'monitor', u'Personality': u'Controller-Active'} capabilities | {u'stor_function': u'monitor', u'Personality': u'Controller-Standby'} personality | controller subfunctions | controller,worker Regards, Ankush From: Penney, Don > Sent: Thursday, September 24, 2020 12:51 AM To: Rai, Ankush >; starlingx-discuss at lists.starlingx.io Subject: RE: how to get rt-kernel support ? The kernel-rt RPM is installed on the "lowlatency" nodes. For AIO, you'd want to install AIO-lowlatency. From: Rai, Ankush > Sent: Wednesday, September 23, 2020 3:05 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] how to get rt-kernel support ? Hi, I couldn't find the rpm for rt-kernel. Is starlingx comes up with rt-kernel support or it need to be patched ? Any pointer to get the rt-kernel support ? software_version | 20.06 I am using the latest green image: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_green_build/outputs/iso/bootimage.iso Required rt-kernel patch: kernel-rt-3.10.0-693.2.2.rt56.623.el7.x86_64 Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From sriram.ec at gmail.com Thu Sep 24 09:33:15 2020 From: sriram.ec at gmail.com (Sriram) Date: Thu, 24 Sep 2020 15:03:15 +0530 Subject: [Starlingx-discuss] SRIOV in starlingx Message-ID: Hi, I have installed distributed starlingx 4.0 in "All in one Duplex" mode. There are two nodes in the central cloud and two in the edge cloud. I have enabled SRIOV in bios settings of edge cloud nodes and set total VFs as 16. After that, while installing starlingX I followed the steps to enable SRIOV. system host-label-assign controller-0 sriovdp=enabled > system host-memory-modify controller-0 0 -1G 100 > system host-memory-modify controller-0 1 -1G 100 and ran these steps for controller-1 as well. As I understand the first step would label the node "controller-0 and controller-1" as "sriovdp=enabled" and set the number of 1G huge pages to 200. Once the installation was complete, I saw that k8s sriov-device plugin was not coming up. It complained that the resource list was empty. I had to set "/sys/devices/pci0000:3a/0000:3a:00.0/0000:3b:00.0/sriov_numvfs" to 8 (I needed 8 virtual interfaces) and update the resource list in /etc/pcidp/config.json { > "resourceList": [ > { > "resourceName": "bcm_sriov_netdevice", > "selectors": { > "vendors": ["14e4"], > "devices": ["16dc"], > "drivers": ["bnxt_en"], > "pfNames": ["enp59s0f0#0-7"] > } > } > ] > } to see that sriov-dp comes up properly. Is there any way to pass on the number of VF's( sriov_numvfs )required per node and resourcelist during the time of installation when we label the nodes as sriovdp=enabled Regards, Sriram -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ankush.Rai at commscope.com Thu Sep 24 09:11:40 2020 From: Ankush.Rai at commscope.com (Rai, Ankush) Date: Thu, 24 Sep 2020 09:11:40 +0000 Subject: [Starlingx-discuss] how to get rt-kernel support ? In-Reply-To: References: Message-ID: Ok got it. Thank you. Regards, Ankush From: Sun, Austin Sent: Thursday, September 24, 2020 1:06 PM To: Rai, Ankush ; Penney, Don ; starlingx-discuss at lists.starlingx.io Subject: RE: how to get rt-kernel support ? Hi Ankush: You can check doc [1] , select 'All-in-one (lowlatency) Controller' for lowlatency , this is same all release r3 , r4 changes, if you want to use Simplex or Duplex system . For multi Nodes External (austin.sun at intel.com) Report This Email FAQ Protection by INKY Hi Ankush: You can check doc [1] , select 'All-in-one (lowlatency) Controller' for lowlatency , this is same all release r3 , r4 changes, if you want to use Simplex or Duplex system . For multi Nodes setup , only worker nodes support low-latency. There is no pre-requirement for a node to be a low-latency node . I this there is no way to change node to low-latency node after installation except re-install. [1] https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_duplex_install_kubernetes.html Thanks. BR Austin Sun. From: Rai, Ankush > Sent: Thursday, September 24, 2020 11:42 AM To: Penney, Don >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] how to get rt-kernel support ? Thank you for your response to this query. But I am still not clear on this. Are you saying that, the kernel-rt RPM will get installed only for "lowlatency" nodes? If my understanding is correct then I have few more questions: * How can I set the node as "lowlatency" node? (Is there any documentation reference for this ?) * Can I make the controller node as a low low-latency node or is it possible for only worker nodes ? * What are the pre-requirement for a node to be a low-latency node ? * Post installation, is there a way to make a node as low-latency node ? I have All-in-one-Duplex mode of deployment, both having "controller" personality and "controller,worker" as subfunctions. capabilities | {u'stor_function': u'monitor', u'Personality': u'Controller-Active'} capabilities | {u'stor_function': u'monitor', u'Personality': u'Controller-Standby'} personality | controller subfunctions | controller,worker Regards, Ankush From: Penney, Don > Sent: Thursday, September 24, 2020 12:51 AM To: Rai, Ankush >; starlingx-discuss at lists.starlingx.io Subject: RE: how to get rt-kernel support ? The kernel-rt RPM is installed on the "lowlatency" nodes. For AIO, you'd want to install AIO-lowlatency. From: Rai, Ankush > Sent: Wednesday, September 23, 2020 3:05 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] how to get rt-kernel support ? Hi, I couldn't find the rpm for rt-kernel. Is starlingx comes up with rt-kernel support or it need to be patched ? Any pointer to get the rt-kernel support ? software_version | 20.06 I am using the latest green image: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_green_build/outputs/iso/bootimage.iso Required rt-kernel patch: kernel-rt-3.10.0-693.2.2.rt56.623.el7.x86_64 Thanks, Ankush -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Thu Sep 24 12:12:59 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 24 Sep 2020 12:12:59 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200924T035144Z Message-ID: Sanity Test from 2020-September-24 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200924T035144Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200924T035144Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From bruce.e.jones at intel.com Thu Sep 24 16:59:29 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 24 Sep 2020 16:59:29 +0000 Subject: [Starlingx-discuss] Rook patch reviews needed Message-ID: Thank you to all the reviewers who have provided feedback on the Ceph/Rook changes. There are two that haven’t been getting attention lately, please take a look soon and update your feedback/vote. Thank you! https://review.opendev.org/#/c/720637/ https://review.opendev.org/716792 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Sep 24 18:11:23 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 24 Sep 2020 18:11:23 +0000 Subject: [Starlingx-discuss] Weekly StarlingX Release meeting Message-ID: ** Re-sending with the updated zoom link Weekly meeting on Thursday 11AM PT / 1900 UTC Zoom Link: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 Meeting agenda/minutes: https://etherpad.openstack.org/p/stx-releases -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2071 bytes Desc: not available URL: From scott.little at windriver.com Thu Sep 24 19:22:21 2020 From: scott.little at windriver.com (Scott Little) Date: Thu, 24 Sep 2020 15:22:21 -0400 Subject: [Starlingx-discuss] Debranding reviews please Message-ID: I know the debranding topic still says 'wip' but the code is ready for review. Reviews in intended delivery order ... Preparing the tool chain for the switch ... https://review.opendev.org/#/c/750041 https://review.opendev.org/#/c/750467 https://review.opendev.org/#/c/750042 https://review.opendev.org/#/c/749974 Then as a set  ... rename cgcs-tis-repo to local-repo ... https://review.opendev.org/#/c/687401 https://review.opendev.org/#/c/749997 https://review.opendev.org/#/c/754129 And the next set   ... rename cgcs-centos-repo to centos-repo https://review.opendev.org/#/c/687403 https://review.opendev.org/#/c/749998 https://review.opendev.org/#/c/750043 Finally https://review.opendev.org/#/c/754130 The full set for review is here: https://review.opendev.org/#/q/topic:debrand_wip+(status:open+OR+status:merged) Thanks Scott From bruce.e.jones at intel.com Thu Sep 24 19:50:24 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 24 Sep 2020 19:50:24 +0000 Subject: [Starlingx-discuss] Debranding reviews please In-Reply-To: References: Message-ID: Scott, thank you for driving this! Are there any updates needed to the documentation (starlingx/docs project) as a result of this change? brucej -----Original Message----- From: Scott Little Sent: Thursday, September 24, 2020 12:22 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Debranding reviews please I know the debranding topic still says 'wip' but the code is ready for review. Reviews in intended delivery order ... Preparing the tool chain for the switch ... https://review.opendev.org/#/c/750041 https://review.opendev.org/#/c/750467 https://review.opendev.org/#/c/750042 https://review.opendev.org/#/c/749974 Then as a set  ... rename cgcs-tis-repo to local-repo ... https://review.opendev.org/#/c/687401 https://review.opendev.org/#/c/749997 https://review.opendev.org/#/c/754129 And the next set   ... rename cgcs-centos-repo to centos-repo https://review.opendev.org/#/c/687403 https://review.opendev.org/#/c/749998 https://review.opendev.org/#/c/750043 Finally https://review.opendev.org/#/c/754130 The full set for review is here: https://review.opendev.org/#/q/topic:debrand_wip+(status:open+OR+status:merged) Thanks Scott _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Thu Sep 24 20:34:36 2020 From: scott.little at windriver.com (Scott Little) Date: Thu, 24 Sep 2020 16:34:36 -0400 Subject: [Starlingx-discuss] Debranding reviews please In-Reply-To: References: Message-ID: <6876c3f5-fbb3-8d72-5007-894d1556995c@windriver.com> I should have that for you tomorrow Scott On 2020-09-24 3:50 p.m., Jones, Bruce E wrote: > Scott, thank you for driving this! > > Are there any updates needed to the documentation (starlingx/docs project) as a result of this change? > > brucej > > -----Original Message----- > From: Scott Little > Sent: Thursday, September 24, 2020 12:22 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Debranding reviews please > > I know the debranding topic still says 'wip' but the code is ready for review. > > > Reviews in intended delivery order ... > > > Preparing the tool chain for the switch ... > > https://review.opendev.org/#/c/750041 > > https://review.opendev.org/#/c/750467 > > https://review.opendev.org/#/c/750042 > > https://review.opendev.org/#/c/749974 > > Then as a set  ... rename cgcs-tis-repo to local-repo ... > > https://review.opendev.org/#/c/687401 > > https://review.opendev.org/#/c/749997 > > https://review.opendev.org/#/c/754129 > > And the next set   ... rename cgcs-centos-repo to centos-repo > > https://review.opendev.org/#/c/687403 > > https://review.opendev.org/#/c/749998 > > https://review.opendev.org/#/c/750043 > > Finally > > https://review.opendev.org/#/c/754130 > > > The full set for review is here: > > https://review.opendev.org/#/q/topic:debrand_wip+(status:open+OR+status:merged) > > > Thanks Scott > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From pvmpublic at gmail.com Fri Sep 25 07:32:20 2020 From: pvmpublic at gmail.com (Pratik M.) Date: Fri, 25 Sep 2020 13:02:20 +0530 Subject: [Starlingx-discuss] SRIOV in starlingx In-Reply-To: References: Message-ID: Hi, You would need to do: # system host-label-assign controller-0 sriovdp=enabled # system host-if-modify controller-0 -c pci-sriov -n sriov0 -N # system interface-datanetwork-assign controller-0 # system host-unlock And that should populate the /etc/pcidp/config.json Ref: https://wiki.openstack.org/wiki/StarlingX/Networking Steven Webster's helpful comments in https://bugs.launchpad.net/starlingx/+bug/1891889 Thanks On Thu, Sep 24, 2020 at 3:04 PM Sriram wrote: > Hi, > > I have installed distributed starlingx 4.0 in "All in one Duplex" mode. > There are two nodes in the central cloud and two in the edge cloud. > > I have enabled SRIOV in bios settings of edge cloud nodes and set total > VFs as 16. > > After that, while installing starlingX I followed the steps to enable > SRIOV. > > system host-label-assign controller-0 sriovdp=enabled >> system host-memory-modify controller-0 0 -1G 100 >> system host-memory-modify controller-0 1 -1G 100 > > and ran these steps for controller-1 as well. > > As I understand the first step would label the node "controller-0 and > controller-1" as "sriovdp=enabled" and set the number of 1G huge pages to > 200. > Once the installation was complete, I saw that k8s sriov-device plugin was > not coming up. It complained that the resource list was empty. > > I had to set > "/sys/devices/pci0000:3a/0000:3a:00.0/0000:3b:00.0/sriov_numvfs" to 8 (I > needed 8 virtual interfaces) and update the resource list in > /etc/pcidp/config.json > > { >> "resourceList": [ >> { >> "resourceName": "bcm_sriov_netdevice", >> "selectors": { >> "vendors": ["14e4"], >> "devices": ["16dc"], >> "drivers": ["bnxt_en"], >> "pfNames": ["enp59s0f0#0-7"] >> } >> } >> ] >> } > > > to see that sriov-dp comes up properly. > > Is there any way to pass on the number of VF's( sriov_numvfs )required per > node and resourcelist during the time of installation when we label the > nodes as sriovdp=enabled > > Regards, > Sriram > > > > > > > > _______________________________________________ > 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 sriram.ec at gmail.com Fri Sep 25 07:50:11 2020 From: sriram.ec at gmail.com (Sriram) Date: Fri, 25 Sep 2020 13:20:11 +0530 Subject: [Starlingx-discuss] SRIOV in starlingx In-Reply-To: References: Message-ID: Hi Pratik, Thanks for your reply. a. Can these steps be done after the installation is complete, now that I have already installed. b. How do we ensure the uniqueness of VF mac addresses across all the nodes in the k8s cluster formed on edge nodes. Regards, Sriram On Fri, Sep 25, 2020 at 1:02 PM Pratik M. wrote: > Hi, > You would need to do: > # system host-label-assign controller-0 sriovdp=enabled > # system host-if-modify controller-0 -c pci-sriov -n sriov0 -N > > # system interface-datanetwork-assign controller-0 > > # system host-unlock > > And that should populate the /etc/pcidp/config.json > > Ref: > https://wiki.openstack.org/wiki/StarlingX/Networking > Steven Webster's helpful comments in > https://bugs.launchpad.net/starlingx/+bug/1891889 > > Thanks > > On Thu, Sep 24, 2020 at 3:04 PM Sriram wrote: > >> Hi, >> >> I have installed distributed starlingx 4.0 in "All in one Duplex" mode. >> There are two nodes in the central cloud and two in the edge cloud. >> >> I have enabled SRIOV in bios settings of edge cloud nodes and set total >> VFs as 16. >> >> After that, while installing starlingX I followed the steps to enable >> SRIOV. >> >> system host-label-assign controller-0 sriovdp=enabled >>> system host-memory-modify controller-0 0 -1G 100 >>> system host-memory-modify controller-0 1 -1G 100 >> >> and ran these steps for controller-1 as well. >> >> As I understand the first step would label the node "controller-0 and >> controller-1" as "sriovdp=enabled" and set the number of 1G huge pages to >> 200. >> Once the installation was complete, I saw that k8s sriov-device plugin >> was not coming up. It complained that the resource list was empty. >> >> I had to set >> "/sys/devices/pci0000:3a/0000:3a:00.0/0000:3b:00.0/sriov_numvfs" to 8 (I >> needed 8 virtual interfaces) and update the resource list in >> /etc/pcidp/config.json >> >> { >>> "resourceList": [ >>> { >>> "resourceName": "bcm_sriov_netdevice", >>> "selectors": { >>> "vendors": ["14e4"], >>> "devices": ["16dc"], >>> "drivers": ["bnxt_en"], >>> "pfNames": ["enp59s0f0#0-7"] >>> } >>> } >>> ] >>> } >> >> >> to see that sriov-dp comes up properly. >> >> Is there any way to pass on the number of VF's( sriov_numvfs )required >> per node and resourcelist during the time of installation when we label the >> nodes as sriovdp=enabled >> >> Regards, >> Sriram >> >> >> >> >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Fri Sep 25 13:46:42 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 25 Sep 2020 13:46:42 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200925T013227Z Message-ID: Sanity Test from 2020-September-25 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200925T013227Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200925T013227Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From Ghada.Khalil at windriver.com Fri Sep 25 22:08:59 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 25 Sep 2020 22:08:59 +0000 Subject: [Starlingx-discuss] Canceled: Weekly StarlingX Release meeting Message-ID: The StarlingX release meeting is cancelled for October 1st as both Bruce and myself are on vacation. ** Re-sending with the updated zoom link Weekly meeting on Thursday 11AM PT / 1900 UTC Zoom Link: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 Meeting agenda/minutes: https://etherpad.openstack.org/p/stx-releases -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1872 bytes Desc: not available URL: From alexandru.dimofte at intel.com Sat Sep 26 19:36:04 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sat, 26 Sep 2020 19:36:04 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200926T035542Z Message-ID: Sanity Test from 2020-September-26 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200926T035542Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200926T035542Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From srivahni.chivukula at intel.com Mon Sep 28 18:22:41 2020 From: srivahni.chivukula at intel.com (Chivukula, Srivahni) Date: Mon, 28 Sep 2020 18:22:41 +0000 Subject: [Starlingx-discuss] Remote ssh issues to Starlingx Message-ID: Hi everyone, Not sure if this is a right place to post this question. If not, please direct me to the correct mailing list. I have a set up with starlingx 4.0 installed and I'm trying to remote ssh in to the controller node using VS-Code editor but see "administratively prohibited: open failed" error. Can anyone provide me with a workaround for this? Also, is there any other editor that starlingx developers use to remote connect to the starlingx controller without any issues and debug code? Regards, Vahni -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Mon Sep 28 22:57:22 2020 From: yong.hu at intel.com (Hu, Yong) Date: Mon, 28 Sep 2020 22:57:22 +0000 Subject: [Starlingx-discuss] Remote ssh issues to Starlingx In-Reply-To: References: Message-ID: <520D4AE1-555C-49A0-A56A-E8B119A07025@intel.com> Hi Vahni, You might double-check if you can reach the OAM IP of the controllers, preferably the floating IP or active controller. It should work for SSH, regardless what SSH client is used. Regards, Yong From: "Chivukula, Srivahni" Date: Tuesday, September 29, 2020 at 2:24 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Remote ssh issues to Starlingx Hi everyone, Not sure if this is a right place to post this question. If not, please direct me to the correct mailing list. I have a set up with starlingx 4.0 installed and I’m trying to remote ssh in to the controller node using VS-Code editor but see “administratively prohibited: open failed” error. Can anyone provide me with a workaround for this? Also, is there any other editor that starlingx developers use to remote connect to the starlingx controller without any issues and debug code? Regards, Vahni -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Sep 29 05:44:17 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 29 Sep 2020 05:44:17 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 9/30/2020 Message-ID: Hi All: Agenda 9/30 meeting: 1) rook ceph: a) discuss rook ceph dedicated storage setup migration solution b) rook ceph patches status https://review.opendev.org/#/q/status:open++branch:master+topic:%22ceph+containerization%22 2) open If any more topic , please add into https://etherpad.opendev.org/p/stx-distro-other Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Tue Sep 29 08:12:41 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Tue, 29 Sep 2020 08:12:41 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200928T230235Z Message-ID: Sanity Test from 2020-September-29 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200928T230235Z/outputs/iso/ ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200928T230235Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stable-versioned.tgz =========================================== Sanity Test executed on Bare Metal AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed on Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard External Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards, STX Validation Team [cid:image003.png at 01D10733.2D2570D0] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20512 bytes Desc: image002.png URL: From austin.sun at intel.com Tue Sep 29 05:24:06 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 29 Sep 2020 05:24:06 +0000 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting Message-ID: Hi All: Change to Bi-weekly meeting, Agenda for each will be sent individual email. Next Meeting will be planned on Jun 22th. * Cadence and time slot: o Bi-Weekly Wednesday 9AM EDT (9 PM China time, US PDT time 6AM) * Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ * Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 5628 bytes Desc: not available URL: From ildiko.vancsa at gmail.com Tue Sep 29 09:11:29 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 29 Sep 2020 11:11:29 +0200 Subject: [Starlingx-discuss] Combined PL/TL/TSC Election Season is starting in a week! Message-ID: <43169C8F-7CFE-4D0E-AF30-89B08C2A28AD@gmail.com> Hi StarlingX Community, I’m reaching out to you to remind you to the upcoming election period and some of the preparation steps needed to participate. The nomination period officially begins on __October 6, 2020, 20:45 UTC__. Please review your preferred email address in Gerrit and update in case needed __as soon as possible__. Please also remember to register a Foundation individual membership account in case you haven’t done it yet here: https://www.openstack.org/join/ For further details please visit: https://docs.starlingx.io/election/ If you have any questions which you feel affect others please reply to this email thread. If you have any questions that you wish to discuss in private please email any of the election officials[1] so that we may address your concerns. Thank you, [1] https://docs.starlingx.io/election/#election-officials From sriram.ec at gmail.com Tue Sep 29 17:52:54 2020 From: sriram.ec at gmail.com (Sriram) Date: Tue, 29 Sep 2020 23:22:54 +0530 Subject: [Starlingx-discuss] SRIOV in starlingx In-Reply-To: References: Message-ID: Hi, How do we ensure the uniqueness of VF mac addresses across all the nodes in the k8s cluster formed on edge nodes. Please let me know if this problem is addressed by starlingX or if it is taken care of by some other means. Regards, Sriram On Fri, Sep 25, 2020 at 1:20 PM Sriram wrote: > Hi Pratik, > > Thanks for your reply. > > a. Can these steps be done after the installation is complete, now that I > have already installed. > b. How do we ensure the uniqueness of VF mac addresses across all the > nodes in the k8s cluster formed on edge nodes. > > Regards, > Sriram > > On Fri, Sep 25, 2020 at 1:02 PM Pratik M. wrote: > >> Hi, >> You would need to do: >> # system host-label-assign controller-0 sriovdp=enabled >> # system host-if-modify controller-0 -c pci-sriov -n sriov0 >> -N >> # system interface-datanetwork-assign controller-0 >> >> # system host-unlock >> >> And that should populate the /etc/pcidp/config.json >> >> Ref: >> https://wiki.openstack.org/wiki/StarlingX/Networking >> Steven Webster's helpful comments in >> https://bugs.launchpad.net/starlingx/+bug/1891889 >> >> Thanks >> >> On Thu, Sep 24, 2020 at 3:04 PM Sriram wrote: >> >>> Hi, >>> >>> I have installed distributed starlingx 4.0 in "All in one Duplex" mode. >>> There are two nodes in the central cloud and two in the edge cloud. >>> >>> I have enabled SRIOV in bios settings of edge cloud nodes and set total >>> VFs as 16. >>> >>> After that, while installing starlingX I followed the steps to enable >>> SRIOV. >>> >>> system host-label-assign controller-0 sriovdp=enabled >>>> system host-memory-modify controller-0 0 -1G 100 >>>> system host-memory-modify controller-0 1 -1G 100 >>> >>> and ran these steps for controller-1 as well. >>> >>> As I understand the first step would label the node "controller-0 and >>> controller-1" as "sriovdp=enabled" and set the number of 1G huge pages to >>> 200. >>> Once the installation was complete, I saw that k8s sriov-device plugin >>> was not coming up. It complained that the resource list was empty. >>> >>> I had to set >>> "/sys/devices/pci0000:3a/0000:3a:00.0/0000:3b:00.0/sriov_numvfs" to 8 (I >>> needed 8 virtual interfaces) and update the resource list in >>> /etc/pcidp/config.json >>> >>> { >>>> "resourceList": [ >>>> { >>>> "resourceName": "bcm_sriov_netdevice", >>>> "selectors": { >>>> "vendors": ["14e4"], >>>> "devices": ["16dc"], >>>> "drivers": ["bnxt_en"], >>>> "pfNames": ["enp59s0f0#0-7"] >>>> } >>>> } >>>> ] >>>> } >>> >>> >>> to see that sriov-dp comes up properly. >>> >>> Is there any way to pass on the number of VF's( sriov_numvfs )required >>> per node and resourcelist during the time of installation when we label the >>> nodes as sriovdp=enabled >>> >>> Regards, >>> Sriram >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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 amy at demarco.com Tue Sep 29 22:21:46 2020 From: amy at demarco.com (Amy Marrich) Date: Tue, 29 Sep 2020 17:21:46 -0500 Subject: [Starlingx-discuss] [Airship-discuss] [Diversity] Community feedback on Divisive Language stance In-Reply-To: References: Message-ID: Bob, Thanks for the feedback and the link. At this time we're leaving the new wording to the individual projects vs saying all OSF projects must use Y instead of X. In part it's because projects have found that words have different meanings in the context of where they're located within their code, at least in the case of blacklist/whitelist. Ultimately we're hoping to have a list of suggested replacements but realize what may work for one project may not for another. Thanks again! Amy Marrich (spotz) On Tue, Sep 29, 2020 at 5:09 PM Monkman, Bob wrote: > Amy, et al, > > Thanks for sharing this and I think Draft 5 seems like a > good statement to build from. I am working on a Linux Foundation Networking > (LFN) task force looking at this issue for the projects under that > umbrella. > > As a part of that process, on our wiki page for this task > force, we have compiled some links and a table of example recommended > replacement terms that could be of interest to your OSF work as well. > > Please see this reference at > https://wiki.lfnetworking.org/display/LN/Inclusive+Language+Initiative > > If this is of interest. > > Best regards, > > Bob Monkman > > LFN Contributor, Strategic Planning Committee member, Marketing Chair > CNTT/OPNFV > > > > > > > > *From:* Amy Marrich > *Sent:* Monday, September 21, 2020 11:36 AM > *To:* starlingx-discuss at lists.starlingx.io; > airship-discuss at lists.airshipit.org; kata-dev at lists.katacontainers.io; > zuul-discuss at lists.zuul-ci.org; openstack-discuss < > openstack-discuss at lists.openstack.org>; foundation at lists.openstack.org > *Subject:* [Airship-discuss] [Diversity] Community feedback on Divisive > Language stance > > > > The OSF Diversity & Inclusion WG has been working on creating the OSF's > stance concerning divisive language. We will be holding one more meeting > before sending the stance to the OSF Board for any changes before bringing > it back to the Community. > > > > Our goal however is to get your input now to reduce any concerns in the > future! Please check out Draft 4 on the etherpad[0] and place your comments > there and join us on October 5th (meeting information will be sent out > closer to the meeting) > > > > Thanks, > > > > Amy (spotz) > > 0 - https://etherpad.opendev.org/p/divisivelanguage > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alterriu at gmail.com Wed Sep 30 03:58:05 2020 From: alterriu at gmail.com (Popoi Zen) Date: Wed, 30 Sep 2020 10:58:05 +0700 Subject: [Starlingx-discuss] Failed when add subcloud on Starlingx 4.0 : deploy-prep-failed Message-ID: I have following environment: ___________________________________________________________________________ | VM Name | Hostname | IP MGMT | IP OAM | Type | | ---------- | -----------------| ------------------ | -------------- | -------------------------------------| | cc-duplex-controller-0 | controller-0 | 192.168.20.3 | 10.10.20.3 | AIO Duplex - Central Cloud | | cc-duplex-controller-1 | controller-1 | 192.168.20.4 | 10.10.20.4 | AIO Duplex - Central Cloud | ------------------------------------------------------------------------------------------------------------------------------- | sc-duplex-controller-0 | localhost | - | 10.10.30.3 | AIO Duplex - Sub Cloud | | sc-duplex-controller-1 | - | - | 10.10.20.4 | AIO Duplex - Sub Cloud | | sc-duplex-controller-2 | - | - | 10.10.20.5 | AIO Duplex - Sub Cloud | My subcloud YAML file: system_mode: duplex > name: "Region-Sub1" > description: "Sub1Site" > location: "SUB1" > timezone: Asia/Jakarta > > management_subnet: 192.168.30.0/24 > management_start_address: 192.168.30.2 > management_end_address: 192.168.30.50 > management_gateway_address: 192.168.30.1 > > external_oam_subnet: 10.10.30.0/24 > external_oam_gateway_address: 10.10.30.1 > external_oam_floating_address: 10.10.30.2 > > systemcontroller_gateway_address: 192.168.20.1 > Every time I try to add subcloud using command: `dcmanager subcloud add --bootstrap-address 10.10.30.3 --bootstrap-values subcloud-1.yml` It always end up failed like below: [sysadmin at controller-0 ~(keystone_admin)]$ dcmanager subcloud list +----+------------+------------+--------------+--------------------+---------+ | id | name | management | availability | deploy status | sync | +----+------------+------------+--------------+--------------------+---------+ | 6 | Region-BGR | unmanaged | offline | deploy-prep-failed | unknown | +----+------------+------------+--------------+--------------------+---------+ There is no log subcloud log reproduced or maybe any workaround I could try? -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Wed Sep 30 08:01:34 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 30 Sep 2020 04:01:34 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_publish - Build # 1680 - Failure! Message-ID: <1878471554.162.1601452895753.JavaMail.javamailuser@localhost> Project: STX_publish Build #: 1680 Status: Failure Timestamp: 20200930T080133Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200930T043000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200930T043000Z OS: centos PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200930T043000Z/logs TIMESTAMP: 20200930T043000Z PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200930T043000Z/inputs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200930T043000Z/logs MASTER_JOB_NAME: STX_build_master_master LAYER: PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200930T043000Z/outputs MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/monolithic From build.starlingx at gmail.com Wed Sep 30 08:01:37 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 30 Sep 2020 04:01:37 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 690 - Failure! Message-ID: <1112973871.165.1601452898378.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 690 Status: Failure Timestamp: 20200930T043000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200930T043000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From austin.sun at intel.com Wed Sep 30 13:30:28 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 30 Sep 2020 13:30:28 +0000 Subject: [Starlingx-discuss] review patch to enable rook-ceph in metal project 9/30 update Message-ID: @Poncea, Ovidiu : Would you like review https://review.opendev.org/#/c/737228/? It has no any review feedback from you for 2 weeks. @Ansible-playbook core reviewer : would you like to review https://review.opendev.org/#/c/734065/ ? no review feedback for 1 month. https://review.opendev.org/#/c/735501/ need another stx-puppet core reviewer +2 if review is ok. Thanks. BR Austin Sun. From: Chen, Haochuan Z Sent: Wednesday, September 23, 2020 8:31 AM To: starlingx-discuss at lists.starlingx.io Cc: Sun, Austin ; Hu, Yong ; Jones, Bruce E Subject: RE: review patch to enable rook-ceph in metal project Hi folks Please review these three patch, for rook-ceph's backup and restore function. https://review.opendev.org/#/c/734065/ https://review.opendev.org/#/c/735501/ https://review.opendev.org/#/c/737228/ Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, September 15, 2020 9:47 AM To: Bart Wensley >; Penney, Don >; MacDonald, Eric >; Kung, John >; Liu, Tao >; 'Poncea, Ovidiu' > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: RE: review patch to enable rook-ceph in metal project Add Ovidiu. Please review my patch for rook-ceph in metal project. https://review.opendev.org/#/c/737228/ Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, August 10, 2020 11:09 AM To: Bart Wensley >; Penney, Don >; MacDonald, Eric >; Kung, John >; Liu, Tao > Cc: Sun, Austin >; Hu, Yong >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: review patch to enable rook-ceph in metal project Hi folks Please review my patch to enable rook-ceph in metal project. https://review.opendev.org/#/c/737228/ BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Wed Sep 30 20:52:06 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Wed, 30 Sep 2020 20:52:06 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-09-30 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2020-09-30 All -- reviews merged since last meeting: 1 Dist Cloud outdated note (+1 cherry pick which requires new follow-on review) All -- bug status -- 11 total - team agrees to defer all low priority LP until the upstreaming effort is completed. 4 new LP submitted by https://launchpad.net/~leiyuehui against API documentation, which is generated from source code. They have self-assigned and are submitting reviews. (low priority). Reviews in progress: Several reviews related to Rook are being worked: https://review.opendev.org/#/q/status:open+project:starlingx/docs+branch:master+topic:ceph-cluster-editorial Opens: Upstreaming WR docs status Mary noticed some formatting issues (caption and numbered steps) https://review.opendev.org/#/c/753129/3/doc/source/node_management/starlingx-kubernetes/the_life_cycle_of_a_host/the-life-cycle-of-a-host.rst Dealing with content that is both upstream/downstream - we will discuss next week. TOC mapping discussion (updated doc from Juanita) -- we will discuss next week. Display multiple versions of STX docs - no update this week. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bob.monkman at intel.com Tue Sep 29 22:09:02 2020 From: bob.monkman at intel.com (Monkman, Bob) Date: Tue, 29 Sep 2020 22:09:02 +0000 Subject: [Starlingx-discuss] [Airship-discuss] [Diversity] Community feedback on Divisive Language stance In-Reply-To: References: Message-ID: Amy, et al, Thanks for sharing this and I think Draft 5 seems like a good statement to build from. I am working on a Linux Foundation Networking (LFN) task force looking at this issue for the projects under that umbrella. As a part of that process, on our wiki page for this task force, we have compiled some links and a table of example recommended replacement terms that could be of interest to your OSF work as well. Please see this reference at https://wiki.lfnetworking.org/display/LN/Inclusive+Language+Initiative If this is of interest. Best regards, Bob Monkman LFN Contributor, Strategic Planning Committee member, Marketing Chair CNTT/OPNFV From: Amy Marrich Sent: Monday, September 21, 2020 11:36 AM To: starlingx-discuss at lists.starlingx.io; airship-discuss at lists.airshipit.org; kata-dev at lists.katacontainers.io; zuul-discuss at lists.zuul-ci.org; openstack-discuss ; foundation at lists.openstack.org Subject: [Airship-discuss] [Diversity] Community feedback on Divisive Language stance The OSF Diversity & Inclusion WG has been working on creating the OSF's stance concerning divisive language. We will be holding one more meeting before sending the stance to the OSF Board for any changes before bringing it back to the Community. Our goal however is to get your input now to reduce any concerns in the future! Please check out Draft 4 on the etherpad[0] and place your comments there and join us on October 5th (meeting information will be sent out closer to the meeting) Thanks, Amy (spotz) 0 - https://etherpad.opendev.org/p/divisivelanguage -------------- next part -------------- An HTML attachment was scrubbed... URL: