From austin.sun at intel.com Sat Feb 1 01:19:59 2020 From: austin.sun at intel.com (Sun, Austin) Date: Sat, 1 Feb 2020 01:19:59 +0000 Subject: [Starlingx-discuss] rebase f/centos8 branch In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC1631D0C@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C7660916D83@SHSMSX105.ccr.corp.intel.com> <77bd7f99-b769-68a4-9206-2fd8138cc13e@linux.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC1631D0C@ALA-MBD.corp.ad.wrs.com> Message-ID: Thanks Penny , Al and Saul. BR Austin Sun. -----Original Message----- From: Penney, Don Sent: Friday, January 31, 2020 10:51 PM To: Sun, Austin ; Saul Wold ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] rebase f/centos8 branch The cherry-pick of Al's fix has merged in f/centos8: https://review.opendev.org/704862 -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Friday, January 31, 2020 3:49 AM To: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] rebase f/centos8 branch Thanks Saul. From my opinion , we can cherry-pick pylint change to f/centos8 . Which master base are you using ? shall we wait layer builder change be merged on mainline if layer builder changes will be merged soon ? , or it is already in baseline ? Thank. BR Austin Sun. -----Original Message----- From: Saul Wold Sent: Friday, January 31, 2020 7:44 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] rebase f/centos8 branch A quick update. Due to stx-tools downloads lst files merging before the upgrades merged, I have more work to download the older versions first in order to do some testing of the kernel changes. Another option would be to cherry-pick the pylint change to f/centos8, I think that might be a better option at this point to unblock us. Sau! On 1/29/20 8:26 PM, Saul Wold wrote: > > > On 1/29/20 8:18 PM, Lin, Shuicheng wrote: >> Hi Saul, >> >> CentOS 8 feature branch also needs below patch, otherwise all patches >> in integ repo cannot be merged. >> >> https://review.opendev.org/704566 >> >> Please help rebase master patches to CentOS 8 feature branch. >> > Yes, I am ware of this, I started the rebase this afternoon this one > is more complex and I need to do some build testing before I can merge. > > Sau! > >> Thanks. >> >> Best Regards >> >> Shuicheng >> >> *From:* Sun, Austin >> *Sent:* Thursday, January 30, 2020 10:53 AM >> *To:* starlingx-discuss at lists.starlingx.io >> *Subject:* [Starlingx-discuss] rebase f/centos8 branch >> >> Hi Saul : >> >>       Because mainline has merged some kernel fix , kata feature and >> some other fixes . would you like to rebase f/centos8 branch from >> master now ? >> >> Thanks. >> >> BR >> Austin Sun. >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ 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 ji at sibyl.li Sun Feb 2 18:47:47 2020 From: ji at sibyl.li (Austin Gillmann) Date: Sun, 2 Feb 2020 12:47:47 -0600 Subject: [Starlingx-discuss] stx-openstack neutron failing to applyu In-Reply-To: References: Message-ID: Hi again, I managed to get the chart applied after a reinstall, but it seems whenever it deploys neutron once; it will not be able to deploy again (I just tried to set an endpoint domain and failed with the same error) Thanks! On Thu, Jan 30, 2020 at 10:33 PM Austin Gillmann wrote: > > Hi all, been trying to deploy starlingx on another cluster, but I am > running into a weird error when trying to apply the application. > > It is `ConfigMap "osh-openstack-neutron.v2" is invalid: []: Too long: > must have at most 1048576 characters` I have also attached the log > here: http://paste.debian.net/1128435/ > > I think whatever is at line 484 near the traceback may be of interest. > > Let me know if you need any other information for troubleshooting, thank you! From build.starlingx at gmail.com Mon Feb 3 20:22:23 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 3 Feb 2020 15:22:23 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 27 - Still Failing! In-Reply-To: <1747362619.661.1580420891260.JavaMail.javamailuser@localhost> References: <1747362619.661.1580420891260.JavaMail.javamailuser@localhost> Message-ID: <679694361.671.1580761344239.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 27 Status: Still Failing Timestamp: 20200203T202219Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200203T201134Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20200203T201134Z DOCKER_BUILD_ID: jenkins-master-compiler-20200203T201134Z-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/20200203T201134Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200203T201134Z/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 Mon Feb 3 20:22:46 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 3 Feb 2020 15:22:46 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 305 - Failure! Message-ID: <59125950.675.1580761367494.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 305 Status: Failure Timestamp: 20200203T202224Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200203T201134Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20200203T201134Z DOCKER_BUILD_ID: jenkins-master-compiler-20200203T201134Z-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/20200203T201134Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200203T201134Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From build.starlingx at gmail.com Mon Feb 3 21:41:27 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 3 Feb 2020 16:41:27 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 28 - Still Failing! In-Reply-To: <19537608.669.1580761340809.JavaMail.javamailuser@localhost> References: <19537608.669.1580761340809.JavaMail.javamailuser@localhost> Message-ID: <783715071.678.1580766088868.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 28 Status: Still Failing Timestamp: 20200203T214124Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200203T213134Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20200203T213134Z DOCKER_BUILD_ID: jenkins-master-compiler-20200203T213134Z-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/20200203T213134Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200203T213134Z/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 Mon Feb 3 21:41:51 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 3 Feb 2020 16:41:51 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 306 - Still Failing! In-Reply-To: <1368771159.673.1580761364994.JavaMail.javamailuser@localhost> References: <1368771159.673.1580761364994.JavaMail.javamailuser@localhost> Message-ID: <1758952068.682.1580766112520.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 306 Status: Still Failing Timestamp: 20200203T214129Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200203T213134Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20200203T213134Z DOCKER_BUILD_ID: jenkins-master-compiler-20200203T213134Z-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/20200203T213134Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200203T213134Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From sgw at linux.intel.com Tue Feb 4 00:53:42 2020 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 3 Feb 2020 16:53:42 -0800 Subject: [Starlingx-discuss] PBR Status Check In-Reply-To: <5f55cb03-5360-3e11-fcc9-46f6dc24d6f8@linux.intel.com> References: <5f55cb03-5360-3e11-fcc9-46f6dc24d6f8@linux.intel.com> Message-ID: Hi Wesley, Following up on this, I am not sure what your working status is because of the Virus and various Gov't restrictions. If you are working, can you give us an update on the Performance impact question I listed below. Thanks Sau! On 1/22/20 10:14 AM, Saul Wold wrote: > > Hi All & Welcome Wesley, > > We have a new community member from JitStack starting to look at the PBR > work, here is some background for him. > > The PBR work was proposed via the StarlingX Feature Specification > process, see the Flock Versioning specification [0], this is based on > the OpenStack Python Build Reasonableness [1] and Semantic Versioning > (SemVer) [2] definition. > > One of the issues that we are trying to resolve is the impact of the > proposed change from Bin Yang to the time it takes to build a single > package with PBR before and after the change. Ideally this would be done > multiple times and provide the average along with the deviation. > This in an important part of the project in order for us to move forward. > > Look forward to working with you. > > Sau! > > [0] > https://docs.starlingx.io/specs/specs/stx-3.0/approved/standardize_flock_versioning.html > > [1] https://docs.openstack.org/pbr/latest/ > [2] https://docs.openstack.org/pbr/latest/user/semver.html From austin.sun at intel.com Tue Feb 4 02:41:14 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 4 Feb 2020 02:41:14 +0000 Subject: [Starlingx-discuss] rebase f/centos8 branch In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7660916D83@SHSMSX105.ccr.corp.intel.com> <77bd7f99-b769-68a4-9206-2fd8138cc13e@linux.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC1631D0C@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Saul: When do you think rebase will be ready ? Thanks. BR Austin Sun. -----Original Message----- From: Sun, Austin Sent: Saturday, February 1, 2020 9:20 AM To: 'Penney, Don' ; Saul Wold ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] rebase f/centos8 branch Thanks Penny , Al and Saul. BR Austin Sun. -----Original Message----- From: Penney, Don Sent: Friday, January 31, 2020 10:51 PM To: Sun, Austin ; Saul Wold ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] rebase f/centos8 branch The cherry-pick of Al's fix has merged in f/centos8: https://review.opendev.org/704862 -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Friday, January 31, 2020 3:49 AM To: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] rebase f/centos8 branch Thanks Saul. From my opinion , we can cherry-pick pylint change to f/centos8 . Which master base are you using ? shall we wait layer builder change be merged on mainline if layer builder changes will be merged soon ? , or it is already in baseline ? Thank. BR Austin Sun. -----Original Message----- From: Saul Wold Sent: Friday, January 31, 2020 7:44 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] rebase f/centos8 branch A quick update. Due to stx-tools downloads lst files merging before the upgrades merged, I have more work to download the older versions first in order to do some testing of the kernel changes. Another option would be to cherry-pick the pylint change to f/centos8, I think that might be a better option at this point to unblock us. Sau! On 1/29/20 8:26 PM, Saul Wold wrote: > > > On 1/29/20 8:18 PM, Lin, Shuicheng wrote: >> Hi Saul, >> >> CentOS 8 feature branch also needs below patch, otherwise all patches >> in integ repo cannot be merged. >> >> https://review.opendev.org/704566 >> >> Please help rebase master patches to CentOS 8 feature branch. >> > Yes, I am ware of this, I started the rebase this afternoon this one > is more complex and I need to do some build testing before I can merge. > > Sau! > >> Thanks. >> >> Best Regards >> >> Shuicheng >> >> *From:* Sun, Austin >> *Sent:* Thursday, January 30, 2020 10:53 AM >> *To:* starlingx-discuss at lists.starlingx.io >> *Subject:* [Starlingx-discuss] rebase f/centos8 branch >> >> Hi Saul : >> >>       Because mainline has merged some kernel fix , kata feature and >> some other fixes . would you like to rebase f/centos8 branch from >> master now ? >> >> Thanks. >> >> BR >> Austin Sun. >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ 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 sgw at linux.intel.com Tue Feb 4 05:50:19 2020 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 3 Feb 2020 21:50:19 -0800 Subject: [Starlingx-discuss] rebase f/centos8 branch In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7660916D83@SHSMSX105.ccr.corp.intel.com> <77bd7f99-b769-68a4-9206-2fd8138cc13e@linux.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC1631D0C@ALA-MBD.corp.ad.wrs.com> Message-ID: <9408c4c4-51d0-b5be-8208-7301d75623ff@linux.intel.com> On 2/3/20 6:41 PM, Sun, Austin wrote: > Hi Saul: > When do you think rebase will be ready ? > Austin, Part of the challenge is that I can't download all the RPM/tarballs and build the parts that have potential conflicts, like the kernel with the Mellanox changes that Jim pushed to master recently. I could possibly do a git rebase instead of a git merge, that will change the f/centos8 branch's history and require all the developers working on f/centos8 to re-pull and possibly redo some work, or save their patches and re-apply them to the rebased branch. 2 different workflows, one easier for me (rebase) or easier for developers to track (merge). Sau! > Thanks. > BR > Austin Sun. > > -----Original Message----- > From: Sun, Austin > Sent: Saturday, February 1, 2020 9:20 AM > To: 'Penney, Don' ; Saul Wold ; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] rebase f/centos8 branch > > > Thanks Penny , Al and Saul. > BR > Austin Sun. > > -----Original Message----- > From: Penney, Don > Sent: Friday, January 31, 2020 10:51 PM > To: Sun, Austin ; Saul Wold ; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] rebase f/centos8 branch > > The cherry-pick of Al's fix has merged in f/centos8: > https://review.opendev.org/704862 > > > -----Original Message----- > From: Sun, Austin [mailto:austin.sun at intel.com] > Sent: Friday, January 31, 2020 3:49 AM > To: Saul Wold; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] rebase f/centos8 branch > > Thanks Saul. > From my opinion , we can cherry-pick pylint change to f/centos8 . > Which master base are you using ? shall we wait layer builder change be merged on mainline if layer builder changes will be merged soon ? , or it is already in baseline ? > > Thank. > BR > Austin Sun. > -----Original Message----- > From: Saul Wold > Sent: Friday, January 31, 2020 7:44 AM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] rebase f/centos8 branch > > A quick update. > > Due to stx-tools downloads lst files merging before the upgrades merged, I have more work to download the older versions first in order to do some testing of the kernel changes. > > Another option would be to cherry-pick the pylint change to f/centos8, I think that might be a better option at this point to unblock us. > > Sau! > > On 1/29/20 8:26 PM, Saul Wold wrote: >> >> >> On 1/29/20 8:18 PM, Lin, Shuicheng wrote: >>> Hi Saul, >>> >>> CentOS 8 feature branch also needs below patch, otherwise all patches >>> in integ repo cannot be merged. >>> >>> https://review.opendev.org/704566 >>> >>> Please help rebase master patches to CentOS 8 feature branch. >>> >> Yes, I am ware of this, I started the rebase this afternoon this one >> is more complex and I need to do some build testing before I can merge. >> >> Sau! >> >>> Thanks. >>> >>> Best Regards >>> >>> Shuicheng >>> >>> *From:* Sun, Austin >>> *Sent:* Thursday, January 30, 2020 10:53 AM >>> *To:* starlingx-discuss at lists.starlingx.io >>> *Subject:* [Starlingx-discuss] rebase f/centos8 branch >>> >>> Hi Saul : >>> >>>       Because mainline has merged some kernel fix , kata feature and >>> some other fixes . would you like to rebase f/centos8 branch from >>> master now ? >>> >>> Thanks. >>> >>> BR >>> Austin Sun. >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From build.starlingx at gmail.com Tue Feb 4 07:26:36 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 4 Feb 2020 02:26:36 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 163 - Failure! Message-ID: <956537631.693.1580801197077.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 163 Status: Failure Timestamp: 20200204T040847Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200204T000000Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200204T000000Z 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/20200204T000000Z/logs MASTER_BUILD_NUMBER: 406 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200204T000000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos PUBLISH_TIMESTAMP: 20200204T000000Z DOCKER_BUILD_ID: jenkins-master-20200204T000000Z-builder TIMESTAMP: 20200204T000000Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/20200204T000000Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20200204T000000Z/outputs From build.starlingx at gmail.com Tue Feb 4 07:26:31 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 4 Feb 2020 02:26:31 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 156 - Failure! Message-ID: <608282298.690.1580801192882.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 156 Status: Failure Timestamp: 20200204T051554Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200204T000000Z/logs -------------------------------------------------------------------------------- Parameters HOST_PORT: 80 MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200204T000000Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root BASE_VERSION: master-stable-20200204T000000Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200204T000000Z/logs REGISTRY_USERID: slittlewrs HOST: build.starlingx.cengn.ca LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200204T000000Z/logs PUBLISH_TIMESTAMP: 20200204T000000Z FLOCK_VERSION: master-centos-stable-20200204T000000Z PREFIX: master TIMESTAMP: 20200204T000000Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20200204T000000Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Tue Feb 4 07:26:39 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 4 Feb 2020 02:26:39 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 406 - Failure! Message-ID: <1968418849.696.1580801200837.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 406 Status: Failure Timestamp: 20200204T000000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200204T000000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false From austin.sun at intel.com Tue Feb 4 08:25:27 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 4 Feb 2020 08:25:27 +0000 Subject: [Starlingx-discuss] rebase f/centos8 branch In-Reply-To: <9408c4c4-51d0-b5be-8208-7301d75623ff@linux.intel.com> References: <9700A18779F35F49AF027300A49E7C7660916D83@SHSMSX105.ccr.corp.intel.com> <77bd7f99-b769-68a4-9206-2fd8138cc13e@linux.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC1631D0C@ALA-MBD.corp.ad.wrs.com> <9408c4c4-51d0-b5be-8208-7301d75623ff@linux.intel.com> Message-ID: Hi Saul: Just discussed w/ Shuicheng , we think rebase including manually fix conflict should be fine. You don’t need to build-iso to verify the rebase work. We can fix any issue caused by rebase together. Thanks. BR Austin Sun. -----Original Message----- From: Saul Wold Sent: Tuesday, February 4, 2020 1:50 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] rebase f/centos8 branch On 2/3/20 6:41 PM, Sun, Austin wrote: > Hi Saul: > When do you think rebase will be ready ? > Austin, Part of the challenge is that I can't download all the RPM/tarballs and build the parts that have potential conflicts, like the kernel with the Mellanox changes that Jim pushed to master recently. I could possibly do a git rebase instead of a git merge, that will change the f/centos8 branch's history and require all the developers working on f/centos8 to re-pull and possibly redo some work, or save their patches and re-apply them to the rebased branch. 2 different workflows, one easier for me (rebase) or easier for developers to track (merge). Sau! > Thanks. > BR > Austin Sun. > > -----Original Message----- > From: Sun, Austin > Sent: Saturday, February 1, 2020 9:20 AM > To: 'Penney, Don' ; Saul Wold ; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] rebase f/centos8 branch > > > Thanks Penny , Al and Saul. > BR > Austin Sun. > > -----Original Message----- > From: Penney, Don > Sent: Friday, January 31, 2020 10:51 PM > To: Sun, Austin ; Saul Wold ; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] rebase f/centos8 branch > > The cherry-pick of Al's fix has merged in f/centos8: > https://review.opendev.org/704862 > > > -----Original Message----- > From: Sun, Austin [mailto:austin.sun at intel.com] > Sent: Friday, January 31, 2020 3:49 AM > To: Saul Wold; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] rebase f/centos8 branch > > Thanks Saul. > From my opinion , we can cherry-pick pylint change to f/centos8 . > Which master base are you using ? shall we wait layer builder change be merged on mainline if layer builder changes will be merged soon ? , or it is already in baseline ? > > Thank. > BR > Austin Sun. > -----Original Message----- > From: Saul Wold > Sent: Friday, January 31, 2020 7:44 AM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] rebase f/centos8 branch > > A quick update. > > Due to stx-tools downloads lst files merging before the upgrades merged, I have more work to download the older versions first in order to do some testing of the kernel changes. > > Another option would be to cherry-pick the pylint change to f/centos8, I think that might be a better option at this point to unblock us. > > Sau! > > On 1/29/20 8:26 PM, Saul Wold wrote: >> >> >> On 1/29/20 8:18 PM, Lin, Shuicheng wrote: >>> Hi Saul, >>> >>> CentOS 8 feature branch also needs below patch, otherwise all patches >>> in integ repo cannot be merged. >>> >>> https://review.opendev.org/704566 >>> >>> Please help rebase master patches to CentOS 8 feature branch. >>> >> Yes, I am ware of this, I started the rebase this afternoon this one >> is more complex and I need to do some build testing before I can merge. >> >> Sau! >> >>> Thanks. >>> >>> Best Regards >>> >>> Shuicheng >>> >>> *From:* Sun, Austin >>> *Sent:* Thursday, January 30, 2020 10:53 AM >>> *To:* starlingx-discuss at lists.starlingx.io >>> *Subject:* [Starlingx-discuss] rebase f/centos8 branch >>> >>> Hi Saul : >>> >>>       Because mainline has merged some kernel fix , kata feature and >>> some other fixes . would you like to rebase f/centos8 branch from >>> master now ? >>> >>> Thanks. >>> >>> BR >>> Austin Sun. >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From austin.sun at intel.com Tue Feb 4 08:26:03 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 4 Feb 2020 08:26:03 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 2/05/2020 Message-ID: Hi All: Agenda for 2/5 meeting: - CentOS 8.0 upgrade planning * rebase status update * ansible/qemu/Docker/K8s plan/status * config-files adapt status * RT kernel Open : - https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From yong.hu at intel.com Tue Feb 4 08:47:55 2020 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 4 Feb 2020 08:47:55 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 2/05/2020 In-Reply-To: References: Message-ID: Austin, I would like to add one more item into the agenda: - enable Vista Creek (FPGA card) support in StarlingX for 3.0.x, 4.0 and following. Thanks, Yong -----Original Message----- From: Sun, Austin Sent: Tuesday, February 4, 2020 4:26 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 2/05/2020 Hi All: Agenda for 2/5 meeting: - CentOS 8.0 upgrade planning * rebase status update * ansible/qemu/Docker/K8s plan/status * config-files adapt status * RT kernel Open : - https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Tue Feb 4 11:44:56 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 4 Feb 2020 12:44:56 +0100 Subject: [Starlingx-discuss] Interim PL elections for open positions - DETAILS and TIMELINE reminder In-Reply-To: References: Message-ID: Hi StarlingX Community, It is a friendly reminder that we are having the interim PL elections starting next Monday (February 10) with the one week long nomination period. The project teams looking for new PLs are the following * Docs * MultiOS * Networking * Test For details about the elections please check out the elections web page[1]. Please reply to this thread or let the election officials[2] know if you have any questions. Thanks and Best Regards, [2] https://docs.starlingx.io/election/#election-officials [3] https://docs.starlingx.io/election/ > On Jan 27, 2020, at 11:14, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > As you may have seen on the mailing list we unfortunately have a few people who cannot fulfill their PL responsibilities anymore which leaves us with open positions to fill. > > Following up on my earlier email[1] based on feedback from the community and TSC we will hold interim elections to find people within the affected teams to step up and take these roles. > > The project teams looking for new PLs are the following: > * Docs > * MultiOS > * Networking > * Test > > The elections will consist of a nomination period and a voting period both being one week long. The timeline is the following: > * PL nomination period: February 10, 2100 UTC - February 17, 2100UTC > * PL elections period: February 17, 2100 UTC - February 24, 2100 UTC > > For details about the elections please check out the elections web page[2]. > > Please reply to this thread or let the election officials[3] know if you have any questions. > > Thanks and Best Regards, > > [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007523.html > [2] https://docs.starlingx.io/election/#election-officials > [3] https://docs.starlingx.io/election/ From Ian.Jolliffe at windriver.com Tue Feb 4 14:48:33 2020 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Tue, 4 Feb 2020 14:48:33 +0000 Subject: [Starlingx-discuss] [TSC] Minutes Jan 30th Message-ID: <8F1E1AD7-769C-40AB-A7A6-1360CCED8BA2@windriver.com> NOTE : going forward the TSC meeting will start at 10am Eastern NA time. The community call will follow directly after. CNCF compatibility testing - next steps Foundation to continue with submission to CNCF TSC agreed to move forward with this approach. Worked on an outline for the first cut of project confirmation chart deck. Will be posted to Google drive after this week’s meeting. Here is the outline we discussed: What is StarlingX Mission - User adoption stories People on the ML Summit presentations Commercial offers based on STX Community building activities Hand-ons workshops at summits and in China meet-ups Meet-ups – local, mid-cycle Hack-a-thon (s) Community metrics Contributors – geo, company diversity Commits, velocity, # of contributors Some nice Bitergia graphics Project evolution and timeline Project timeline from Nov pres and add to show latest milestones/accomplishments Project development process Self evaluation Next steps Future direction/vision after confirmations Users and use cases Regards; Ian -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Tue Feb 4 14:59:47 2020 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 4 Feb 2020 14:59:47 +0000 Subject: [Starlingx-discuss] [Containers] Minutes of 02/04 containers meeting Message-ID: Minutes of Feb 4th meeting:       Shuicheng presented kata containers overview, and demonstrated a system running kata. .    armada is still running in docker.  Other pods, etc.. are running in kata (accessible using crictl) .   Greg asked about updating local registry.  .  Shuicheng to provide info to doc team (how to use kata for new development)     Tingjie is changing teams, Austin and Martin are taking over for Ceph containerization     No other topics covered.  Meeting was relatively short. Next containers meeting will be Tuesday Feb 18 Etherpad: https://etherpad.openstack.org/p/stx-containerization Al From sgw at linux.intel.com Tue Feb 4 15:09:02 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 4 Feb 2020 07:09:02 -0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSNOiBQQlIgU3RhdHVzIENoZWNr?= In-Reply-To: <060f01d5db34$f5e38a50$e1aa9ef0$@jitstack.com> References: <5f55cb03-5360-3e11-fcc9-46f6dc24d6f8@linux.intel.com> <060f01d5db34$f5e38a50$e1aa9ef0$@jitstack.com> Message-ID: <42960858-5122-4de5-b4c9-6d5619f4d692@linux.intel.com> Wesley, Yakun: I hope you guys are doing OK with the restrictions and stay healthy! I did a review of the numbers that Yakun provide in a prior email (summary here) Package Compile timeconsumption with pbr without pbr the first time 0.287s 0.301s the second time 0.322s 0.351s the third time 0.554s 0.235s the fourth time( deb package) 0.299s 0.292s Can you please provide more details about what your actual test methodology (and/or scripts) was? I think at some-point it was suggested that 2 packages (python and non-python) should be used. They should then be compiled / cleaned in a loop of about 10-12 times to ensure any caches are cleared. Then an average and deviation be determined. Thanks Sau! On 2/4/20 12:27 AM, wesley.yang at jitstack.com wrote: > Hi Saul > I'm working at home remotely at home for the Government's restriction, my colleagues are also working remotely or still on vacation. > You may see that my colleagues Yakun has just sent the preliminary result to you, and he will do some more test and update later. > > Wesley > > -----邮件原件----- > 发件人: Saul Wold > 发送时间: 2020年2月4日 8:54 > 收件人: wesley.yang at jitstack.com; daniels.cai at jitstack.com; Yang, Bin > 抄送: Hu, Yong ; starlingx-discuss at lists.starlingx.io > 主题: Re: PBR Status Check > > Hi Wesley, > > Following up on this, I am not sure what your working status is because of the Virus and various Gov't restrictions. If you are working, can you give us an update on the Performance impact question I listed below. > > Thanks > Sau! > > > On 1/22/20 10:14 AM, Saul Wold wrote: >> >> Hi All & Welcome Wesley, >> >> We have a new community member from JitStack starting to look at the >> PBR work, here is some background for him. >> >> The PBR work was proposed via the StarlingX Feature Specification >> process, see the Flock Versioning specification [0], this is based on >> the OpenStack Python Build Reasonableness [1] and Semantic Versioning >> (SemVer) [2] definition. >> >> One of the issues that we are trying to resolve is the impact of the >> proposed change from Bin Yang to the time it takes to build a single >> package with PBR before and after the change. Ideally this would be >> done multiple times and provide the average along with the deviation. >> This in an important part of the project in order for us to move forward. >> >> Look forward to working with you. >> >> Sau! >> >> [0] >> https://docs.starlingx.io/specs/specs/stx-3.0/approved/standardize_flo >> ck_versioning.html >> >> [1] https://docs.openstack.org/pbr/latest/ >> [2] https://docs.openstack.org/pbr/latest/user/semver.html > From dejan.muhamedagic at tttech-industrial.com Tue Feb 4 15:10:36 2020 From: dejan.muhamedagic at tttech-industrial.com (Dejan Muhamedagic) Date: Tue, 4 Feb 2020 15:10:36 +0000 Subject: [Starlingx-discuss] docker instance cannot boot (no boot device) Message-ID: Hi, I created in openstack an image of the docker type. When an instance of that image starts, the console shows the SeaBIOS version followed by ipxe and the last message is "No bootable device": it looks like as if openstack is trying to create a VM instead of a container. openstack shows the "container_format" of the image as "docker". The same docker image runs fine on the same controller host when started by hand (docker load, followed by docker run). I couldn't find anything in the logs. What am I missing? Should a docker image be created in some special way? Thanks, Dejan CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail at tttech.com immediately. From scott.little at windriver.com Tue Feb 4 15:47:45 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 4 Feb 2020 10:47:45 -0500 Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 156 - Failure! In-Reply-To: <608282298.690.1580801192882.JavaMail.javamailuser@localhost> References: <608282298.690.1580801192882.JavaMail.javamailuser@localhost> Message-ID: <1941db21-8843-06bd-5055-51186331c42f@windriver.com> CENGN ran out of disk space for docker images last night. I'm doing a manual cleanup. I will re-launch the build, with docker images, when space is available. If there is a common theme, I'll try to implement a longer term fix. Scott On 2020-02-04 2:26 a.m., build.starlingx at gmail.com wrote: > Project: STX_build_docker_flock_images > Build #: 156 > Status: Failure > Timestamp: 20200204T051554Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200204T000000Z/logs > -------------------------------------------------------------------------------- > Parameters > > HOST_PORT: 80 > MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200204T000000Z > OS: centos > MY_REPO: /localdisk/designer/jenkins/master/cgcs-root > BASE_VERSION: master-stable-20200204T000000Z > PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200204T000000Z/logs > REGISTRY_USERID: slittlewrs > HOST: build.starlingx.cengn.ca > LATEST_PREFIX: master > PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200204T000000Z/logs > PUBLISH_TIMESTAMP: 20200204T000000Z > FLOCK_VERSION: master-centos-stable-20200204T000000Z > PREFIX: master > TIMESTAMP: 20200204T000000Z > BUILD_STREAM: stable > REGISTRY_ORG: starlingx > PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20200204T000000Z/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 Dariush.Eslimi at windriver.com Tue Feb 4 18:07:40 2020 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Tue, 4 Feb 2020 18:07:40 +0000 Subject: [Starlingx-discuss] Setting up StarlingX mirroring to GitHub Message-ID: Hi All, As part of effort to apply for CNCF Certified Kubernetes logo, we need to mirror our repositories to GitHub, I have created a story to track our progress, and so far we have completed one repo : ha Here is the link to StarlingX GitHub : https://github.com/starlingx Here is storyboard link : https://storyboard.openstack.org/#!/story/2007252 Bin will go through each repo to setup the mirroring job as part of zuul configuration, cores please review his commits as they get posted. You can get the list of commits using this link: https://review.opendev.org/#/q/projects:starlingx+AND++topic:github-mirror+(status:open+OR+status:merged) Bin will update the developers wiki to add instructions on what has to be done to setup mirroring for your newly created repo. Thanks, Dariush -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Tue Feb 4 20:04:15 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 4 Feb 2020 12:04:15 -0800 Subject: [Starlingx-discuss] Setting up StarlingX mirroring to GitHub In-Reply-To: References: Message-ID: Hi Darish, Bin: I got a look at the one of the reviews for this and I wonder if we can do this via a template in zuul-jobs so that we have have one secret shared for all the github mirror jobs? If needed we can check with the Infra team, and perhaps you already have. Sau! On 2/4/20 10:07 AM, Eslimi, Dariush wrote: > Hi All, > > As part of effort to apply for CNCF Certified Kubernetes logo, we need > to mirror our repositories to GitHub, I have created a story to track > our progress, and so far we have completed one repo : ha > > Here is the link to StarlingX GitHub : https://github.com/starlingx > > Here is storyboard link : https://storyboard.openstack.org/#!/story/2007252 > > Bin will go through each repo to setup the mirroring job as part of zuul > configuration, cores please review his commits as they get posted. > > You can get the list of commits using this link: > https://review.opendev.org/#/q/projects:starlingx+AND++topic:github-mirror+(status:open+OR+status:merged) > > Bin will update the developers wiki to add instructions on what has to > be done to setup mirroring for your newly created repo. > > Thanks, > > Dariush > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Dariush.Eslimi at windriver.com Tue Feb 4 20:23:38 2020 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Tue, 4 Feb 2020 20:23:38 +0000 Subject: [Starlingx-discuss] Setting up StarlingX mirroring to GitHub In-Reply-To: References: Message-ID: Hi Saul, We have followed instruction given to us by Infra team, and if you look at what airship has done, it is same as what we are doing. But having said that if you can help us getting an example of how that is done, and even better if you can do one repo as an example we will follow your lead. Thanks, Dariush -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: February-04-20 3:04 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Setting up StarlingX mirroring to GitHub Hi Darish, Bin: I got a look at the one of the reviews for this and I wonder if we can do this via a template in zuul-jobs so that we have have one secret shared for all the github mirror jobs? If needed we can check with the Infra team, and perhaps you already have. Sau! On 2/4/20 10:07 AM, Eslimi, Dariush wrote: > Hi All, > > As part of effort to apply for CNCF Certified Kubernetes logo, we need > to mirror our repositories to GitHub, I have created a story to track > our progress, and so far we have completed one repo : ha > > Here is the link to StarlingX GitHub : https://github.com/starlingx > > Here is storyboard link : > https://storyboard.openstack.org/#!/story/2007252 > > Bin will go through each repo to setup the mirroring job as part of > zuul configuration, cores please review his commits as they get posted. > > You can get the list of commits using this link: > https://review.opendev.org/#/q/projects:starlingx+AND++topic:github-mi > rror+(status:open+OR+status:merged) > > Bin will update the developers wiki to add instructions on what has to > be done to setup mirroring for your newly created repo. > > Thanks, > > Dariush > > > _______________________________________________ > 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 fungi at yuggoth.org Tue Feb 4 21:13:43 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Tue, 4 Feb 2020 21:13:43 +0000 Subject: [Starlingx-discuss] Setting up StarlingX mirroring to GitHub In-Reply-To: References: Message-ID: <20200204211343.khklxt5n3mhf67rx@yuggoth.org> On 2020-02-04 12:04:15 -0800 (-0800), Saul Wold wrote: > I got a look at the one of the reviews for this and I wonder if we > can do this via a template in zuul-jobs so that we have have one > secret shared for all the github mirror jobs? > > If needed we can check with the Infra team, and perhaps you > already have. [...] The reason is explained in Zuul's documentation on secrets: "If a job with secrets is defined in an untrusted-project, allowed-projects is automatically set to that project only, and can not be overridden (though a config-project may still add the job to any project’s pipeline regardless of this setting; do so with caution as other projects may expose the source project’s secrets)." https://zuul-ci.org/docs/zuul/reference/secret_def.html This is a safety measure, to prevent job definition changes merged to one project from being able to expose secrets belonging to another project. Also secrets are tied to the repository in which they're defined, encrypted with different keys per project, so copying the same secret into a different repository will only yield undecryptable garbage. Further, for related safety reasons, secrets can't be used by child job definitions or job variants, meaning that it would be impossible to override some variables in a secret-using job (for example, the git_mirror_repository variable on which the upload-git-mirror parent job relies) with a job variant in another repository. -- 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 sgw at linux.intel.com Tue Feb 4 21:24:28 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 4 Feb 2020 13:24:28 -0800 Subject: [Starlingx-discuss] Setting up StarlingX mirroring to GitHub In-Reply-To: <20200204211343.khklxt5n3mhf67rx@yuggoth.org> References: <20200204211343.khklxt5n3mhf67rx@yuggoth.org> Message-ID: On 2/4/20 1:13 PM, Jeremy Stanley wrote: > On 2020-02-04 12:04:15 -0800 (-0800), Saul Wold wrote: >> I got a look at the one of the reviews for this and I wonder if we >> can do this via a template in zuul-jobs so that we have have one >> secret shared for all the github mirror jobs? >> >> If needed we can check with the Infra team, and perhaps you >> already have. > [...] > > The reason is explained in Zuul's documentation on secrets: > > "If a job with secrets is defined in an untrusted-project, > allowed-projects is automatically set to that project only, and > can not be overridden (though a config-project may still add the > job to any project’s pipeline regardless of this setting; do so > with caution as other projects may expose the source project’s > secrets)." > > https://zuul-ci.org/docs/zuul/reference/secret_def.html > > This is a safety measure, to prevent job definition changes merged > to one project from being able to expose secrets belonging to > another project. Also secrets are tied to the repository in which > they're defined, encrypted with different keys per project, so > copying the same secret into a different repository will only yield > undecryptable garbage. Further, for related safety reasons, secrets > can't be used by child job definitions or job variants, meaning that > it would be impossible to override some variables in a secret-using > job (for example, the git_mirror_repository variable on which the > upload-git-mirror parent job relies) with a job variant in another > repository. > So based on this, I guess there is no point in trying to create a template and common secret, I will +2 the existing work. I was not fully aware of the above limitation, I was thinking about template-ing a common task. Sau! > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From sgw at linux.intel.com Tue Feb 4 21:32:03 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 4 Feb 2020 13:32:03 -0800 Subject: [Starlingx-discuss] Please review f/centos8 merge requests Message-ID: Folks, I am going through and doing merges of the f/centos8 branch on most of the StarlingX repos. The hard one right now is integ due to the kernel patches being removed and updated, that will be worked on last. If I could get Core Reviewers taking a loot, that would be much appreciated. Thanks Sau! From build.starlingx at gmail.com Wed Feb 5 04:58:16 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 4 Feb 2020 23:58:16 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 605 - Failure! Message-ID: <205388227.704.1580878697985.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 605 Status: Failure Timestamp: 20200205T025621Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200205T023000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200205T023000Z DOCKER_BUILD_ID: jenkins-master-20200205T023000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200205T023000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200205T023000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Wed Feb 5 04:58:20 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 4 Feb 2020 23:58:20 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure! Message-ID: <1384267631.707.1580878701172.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 408 Status: Failure Timestamp: 20200205T023000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200205T023000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false From Bill.Zvonar at windriver.com Wed Feb 5 13:11:59 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 5 Feb 2020 13:11:59 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Feb 5, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B8BB91@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of the Community call coming up later today. As discussed in last week's Community & TSC calls, we agreed that this will be the first combined TSC/Community call. We'll start with TSC business, then we'll move on to the Community call. Not too much on the agenda [0] for the Community call so far besides the usual standing topics, feel free to add other items. 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=20200205T1500 From thierry at openstack.org Wed Feb 5 13:23:33 2020 From: thierry at openstack.org (Thierry Carrez) Date: Wed, 5 Feb 2020 14:23:33 +0100 Subject: [Starlingx-discuss] Training session on Bitergia dashboard, Feb 17 Message-ID: <3c5b0d97-5c82-d981-81a4-ee905829436a@openstack.org> Hi StarlingXers, Since last year, the StarlingX community dashboard is available at starlingx.biterg.io. It shows a series of pre-defined dashboards that let you extract metrics from gerrit, git and ML data. However the real power of the Bitergia toolkit is when you go to the next level and drill down and filter for more relevant data, or when you build your own analysis and visualization. In order to present those features and answer community questions, we've set up a video training session with Bitergia which will happen on Jitsi Meet[1] Monday, February 17 at 1600 UTC[2]. Please sign up on: https://etherpad.openstack.org/p/bitergia-training-Feb2020 All details for connection will be posted there. Also if you have examples of changes in existing dashboards that you'd like to see, or of visualizations you'd like to build, please add to the suggestions in the etherpad. We'll collect suggestions to build the final training contents. See you there! [1] https://meet.jit.si/ [2] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200217T16&p1=1440 -- Thierry Carrez (ttx) From austin.sun at intel.com Wed Feb 5 14:46:25 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 5 Feb 2020 14:46:25 +0000 Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 2/05/2020 Message-ID: Hi All: Thanks for the call. MoM for 2/5 meeting: - CentOS 8.0 upgrade planning Call for input if any missing part in below. * rebase status update keeping git history. * ansible/qemu/Docker/K8s plan/status * config-files adapt status * openstack plan/status - enable Vista Creek (FPGA card) support in StarlingX for 3.0.x, 4.0 and following. feature is already resourced by WR. It is blocked on the required software supporting the Vista Creek being available upstream (the code is posted in the open and part of its respective project) i40e driver (support must be in the mainline driver which also supports the other variants of the Fortville NIC) OPEA Driver and user-space utilities Updates for the sriov device plugin As per Brent, Pull Request is in progress, but not yet merged. As per Yong, the Intel Vista Creek team plans to update the OPEA driver to version 1.5 by next week. ** Need confirmation from the Intel Vista Creek team on the exact versions of the above pieces. Yong took the action to get this information. --- PBR , will update performance in next weeekly call. Open : https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Wed Feb 5 15:25:07 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 5 Feb 2020 10:25:07 -0500 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure! In-Reply-To: <1384267631.707.1580878701172.JavaMail.javamailuser@localhost> References: <1384267631.707.1580878701172.JavaMail.javamailuser@localhost> Message-ID: <5db0be7e-5fe9-0875-b242-c0f3d3f1b85e@windriver.com> Failed to build containerd-1.3.0-1.tis.src.rpm + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/src extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/runc extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl *** ERROR: No build ID note found in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl Previous build success looked like this ... note the extra arguments ... + /usr/lib/rpm/find-debuginfo.sh-j24 --strict-build-id -m--build-id-seed 1.3.0-1.tis --unique-debug-suffix -1.3.0-1.tis.x86_64 --unique-debug-src-base containerd-1.3.0-1.tis.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/src extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/runc *** ERROR: No build ID note found in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl readelf: /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/lib/debug/usr/bin/runc-1.3.0-1.tis.x86_64.debug: Error: the dynamic segment offset + size exceeds the size of the file /usr/lib/rpm/sepdebugcrcfix: Updated 0 CRC32s, 1 CRC32s did match. + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-compress + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1 + /usr/lib/rpm/redhat/brp-python-hardlink + /usr/lib/rpm/redhat/brp-java-repack-jars Processing files: containerd-1.3.0-1.tis.x86_64 warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim-runc-v1 warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim-runc-v2 warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl Provides: containerd containerd = 1.3.0-1.tis containerd(x86-64) = 1.3.0-1.tis containerd.io runc Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: libc.so.6()(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.4)(64bit) libc.so.6(GLIBC_2.7)(64bit) libdl.so.2()(64bit) libdl.so.2(GLIBC_2.2.5)(64bit) libpthread.so.0()(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit) libpthread.so.0(GLIBC_2.3.2)(64bit) libseccomp.so.2()(64bit) rtld(GNU_HASH) Processing files: containerd-debuginfo-1.3.0-1.tis.x86_64 Provides: containerd-debuginfo = 1.3.0-1.tis containerd-debuginfo(x86-64) = 1.3.0-1.tis Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64 Wrote: /builddir/build/RPMS/containerd-1.3.0-1.tis.x86_64.rpm Wrote: /builddir/build/RPMS/containerd-debuginfo-1.3.0-1.tis.x86_64.rpm There is nothing obvious in the change log.  Looking for something environmental... Scott On 2020-02-04 11:58 p.m., build.starlingx at gmail.com wrote: > Project: STX_build_master_master > Build #: 408 > Status: Failure > Timestamp: 20200205T023000Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200205T023000Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: 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 Don.Penney at windriver.com Wed Feb 5 15:42:11 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 5 Feb 2020 15:42:11 +0000 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure! In-Reply-To: <5db0be7e-5fe9-0875-b242-c0f3d3f1b85e@windriver.com> References: <1384267631.707.1580878701172.JavaMail.javamailuser@localhost> <5db0be7e-5fe9-0875-b242-c0f3d3f1b85e@windriver.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC16337EB@ALA-MBD.corp.ad.wrs.com> I don't see any recent updates that would point to this, but I'm trying a build of my own to see if I can reproduce this failure. From: Scott Little [mailto:scott.little at windriver.com] Sent: Wednesday, February 05, 2020 10:25 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure! Failed to build containerd-1.3.0-1.tis.src.rpm + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/src extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/runc extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl *** ERROR: No build ID note found in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl Previous build success looked like this ... note the extra arguments ... + /usr/lib/rpm/find-debuginfo.sh -j24 --strict-build-id -m --build-id-seed 1.3.0-1.tis --unique-debug-suffix -1.3.0-1.tis.x86_64 --unique-debug-src-base containerd-1.3.0-1.tis.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/src extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/runc *** ERROR: No build ID note found in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl readelf: /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/lib/debug/usr/bin/runc-1.3.0-1.tis.x86_64.debug: Error: the dynamic segment offset + size exceeds the size of the file /usr/lib/rpm/sepdebugcrcfix: Updated 0 CRC32s, 1 CRC32s did match. + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-compress + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1 + /usr/lib/rpm/redhat/brp-python-hardlink + /usr/lib/rpm/redhat/brp-java-repack-jars Processing files: containerd-1.3.0-1.tis.x86_64 warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim-runc-v1 warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim-runc-v2 warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl Provides: containerd containerd = 1.3.0-1.tis containerd(x86-64) = 1.3.0-1.tis containerd.io runc Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: libc.so.6()(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.4)(64bit) libc.so.6(GLIBC_2.7)(64bit) libdl.so.2()(64bit) libdl.so.2(GLIBC_2.2.5)(64bit) libpthread.so.0()(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit) libpthread.so.0(GLIBC_2.3.2)(64bit) libseccomp.so.2()(64bit) rtld(GNU_HASH) Processing files: containerd-debuginfo-1.3.0-1.tis.x86_64 Provides: containerd-debuginfo = 1.3.0-1.tis containerd-debuginfo(x86-64) = 1.3.0-1.tis Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64 Wrote: /builddir/build/RPMS/containerd-1.3.0-1.tis.x86_64.rpm Wrote: /builddir/build/RPMS/containerd-debuginfo-1.3.0-1.tis.x86_64.rpm There is nothing obvious in the change log. Looking for something environmental... Scott On 2020-02-04 11:58 p.m., build.starlingx at gmail.com wrote: Project: STX_build_master_master Build #: 408 Status: Failure Timestamp: 20200205T023000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200205T023000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: 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 scott.little at windriver.com Wed Feb 5 15:50:06 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 5 Feb 2020 10:50:06 -0500 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure! In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC16337EB@ALA-MBD.corp.ad.wrs.com> References: <1384267631.707.1580878701172.JavaMail.javamailuser@localhost> <5db0be7e-5fe9-0875-b242-c0f3d3f1b85e@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC16337EB@ALA-MBD.corp.ad.wrs.com> Message-ID: <287284fa-f1e8-96de-3162-1c3771ae6e3d@windriver.com> Comparing installed_pkgs.log between success and failure cases, I note that the failed build was using the stock CentOS rpm, while the success case used rpm-4.14.0-1.tis.1. I think we should try adding...     BuildRequires:    rpm-devel >= 4.14.0     BuildRequires:    rpm-libs >= 4.14.0 ... to the containerd spec. This should induce an upgrade to the newer rpm. On 2020-02-05 10:42 a.m., Penney, Don wrote: > > I don’t see any recent updates that would point to this, but I’m > trying a build of my own to see if I can reproduce this failure. > > *From:*Scott Little [mailto:scott.little at windriver.com] > *Sent:* Wednesday, February 05, 2020 10:25 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] [build-report] > STX_build_master_master - Build # 408 - Failure! > > Failed to build containerd-1.3.0-1.tis.src.rpm > > + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/src > extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/runc > extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl > *** ERROR: No build ID note found in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl > > Previous build success looked like this ... note the extra arguments ... > > + /usr/lib/rpm/find-debuginfo.sh-j24 --strict-build-id -m--build-id-seed 1.3.0-1.tis --unique-debug-suffix -1.3.0-1.tis.x86_64 > --unique-debug-src-base containerd-1.3.0-1.tis.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/src > extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl > extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/runc > *** ERROR: No build ID note found in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl > readelf: /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/lib/debug/usr/bin/runc-1.3.0-1.tis.x86_64.debug: Error: the dynamic segment offset + size exceeds the size of the file > /usr/lib/rpm/sepdebugcrcfix: Updated 0 CRC32s, 1 CRC32s did match. > + /usr/lib/rpm/check-buildroot > + /usr/lib/rpm/redhat/brp-compress > + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip > + /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1 > + /usr/lib/rpm/redhat/brp-python-hardlink > + /usr/lib/rpm/redhat/brp-java-repack-jars > Processing files: containerd-1.3.0-1.tis.x86_64 > warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim > warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim-runc-v1 > warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim-runc-v2 > warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl > Provides: containerd containerd = 1.3.0-1.tis containerd(x86-64) = 1.3.0-1.tis containerd.io runc > Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 > Requires: libc.so.6()(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.4)(64bit) libc.so.6(GLIBC_2.7)(64bit) libdl.so.2()(64bit) libdl.so.2(GLIBC_2.2.5)(64bit) libpthread.so.0()(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit) libpthread.so.0(GLIBC_2.3.2)(64bit) libseccomp.so.2()(64bit) rtld(GNU_HASH) > Processing files: containerd-debuginfo-1.3.0-1.tis.x86_64 > Provides: containerd-debuginfo = 1.3.0-1.tis containerd-debuginfo(x86-64) = 1.3.0-1.tis > Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 > Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64 > Wrote: /builddir/build/RPMS/containerd-1.3.0-1.tis.x86_64.rpm > Wrote: /builddir/build/RPMS/containerd-debuginfo-1.3.0-1.tis.x86_64.rpm > > There is nothing obvious in the change log.  Looking for something > environmental... > > Scott > > On 2020-02-04 11:58 p.m., build.starlingx at gmail.com > wrote: > > Project: STX_build_master_master > > Build #: 408 > > Status: Failure > > Timestamp: 20200205T023000Z > > Check logs at: > > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200205T023000Z/logs > > -------------------------------------------------------------------------------- > > Parameters > > BUILD_CONTAINERS_DEV: false > > BUILD_CONTAINERS_STABLE: 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 Feb 5 15:57:40 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 5 Feb 2020 15:57:40 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Feb 5, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B8BECB@ALA-MBD.corp.ad.wrs.com> Notes from the Community call just now... - Standing Topics - Sanity - only greens since last week, but no reports since last week - Bruce will check in w/ the GDC team & look to transition this to Galati as soon as possible - Reviews - StarlingX Mirror to GitHub (Dariush) http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007679.html - Layered Build (Saul/Scott) - not a review per se, but asking people to try it out http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007641.html - CentOS 8 - see Austin's update from the Distro Non-OpenStack meeting http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007689.html - Community asked to comment on any items that should be added to the CentOS 8 plan - they will be prioritized & resourced/scheduled accordingly - f/centos8 merge requests (Saul): http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007684.html - Topics for This Week - Election reminder/PSA http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007673.html - Training session on Bitergia dashboard, Feb 17 http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007688.html - AR Review - Sep 25, 2019 -- Bill / Doc -- find a place for Sai Chandu's images/documentation - Feb 5: there's an action w/ the build team to re-instate a tool that Sai Chandu may be able to use (he'll have to check it out after it's reinstated) - Jan 29: Kris asked to confirm if this is happening on tomorrow's call - Kris will ping Sai Chandu to confirm the meeting is on - Open Requests for Help - Docker Instance Cannot Boot: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007677.html - Yong will respond on behalf of the Distro OpenStack sub-project - Question from Galati: How Many Cables? - how many cables are required between servers, as they set up their lab for sanity - 3 per node - Management & Data should be at least 10G, BMC & OAM don't need to be 10G -----Original Message----- From: Zvonar, Bill Sent: Wednesday, February 5, 2020 8:12 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: Community (& TSC) Call (Feb 5, 2020) Hi all, reminder of the Community call coming up later today. As discussed in last week's Community & TSC calls, we agreed that this will be the first combined TSC/Community call. We'll start with TSC business, then we'll move on to the Community call. Not too much on the agenda [0] for the Community call so far besides the usual standing topics, feel free to add other items. 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=20200205T1500 From Don.Penney at windriver.com Wed Feb 5 16:12:40 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 5 Feb 2020 16:12:40 +0000 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure! In-Reply-To: <287284fa-f1e8-96de-3162-1c3771ae6e3d@windriver.com> References: <1384267631.707.1580878701172.JavaMail.javamailuser@localhost> <5db0be7e-5fe9-0875-b242-c0f3d3f1b85e@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC16337EB@ALA-MBD.corp.ad.wrs.com> <287284fa-f1e8-96de-3162-1c3771ae6e3d@windriver.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC1633830@ALA-MBD.corp.ad.wrs.com> I’ve been able to reproduce the failure, so I’ll try this fix From: Little, Scott Sent: Wednesday, February 05, 2020 10:50 AM To: Penney, Don; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure! Comparing installed_pkgs.log between success and failure cases, I note that the failed build was using the stock CentOS rpm, while the success case used rpm-4.14.0-1.tis.1. I think we should try adding... BuildRequires: rpm-devel >= 4.14.0 BuildRequires: rpm-libs >= 4.14.0 ... to the containerd spec. This should induce an upgrade to the newer rpm. On 2020-02-05 10:42 a.m., Penney, Don wrote: I don’t see any recent updates that would point to this, but I’m trying a build of my own to see if I can reproduce this failure. From: Scott Little [mailto:scott.little at windriver.com] Sent: Wednesday, February 05, 2020 10:25 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure! Failed to build containerd-1.3.0-1.tis.src.rpm + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/src extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/runc extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl *** ERROR: No build ID note found in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl Previous build success looked like this ... note the extra arguments ... + /usr/lib/rpm/find-debuginfo.sh -j24 --strict-build-id -m --build-id-seed 1.3.0-1.tis --unique-debug-suffix -1.3.0-1.tis.x86_64 --unique-debug-src-base containerd-1.3.0-1.tis.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/src extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/runc *** ERROR: No build ID note found in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl readelf: /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/lib/debug/usr/bin/runc-1.3.0-1.tis.x86_64.debug: Error: the dynamic segment offset + size exceeds the size of the file /usr/lib/rpm/sepdebugcrcfix: Updated 0 CRC32s, 1 CRC32s did match. + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-compress + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1 + /usr/lib/rpm/redhat/brp-python-hardlink + /usr/lib/rpm/redhat/brp-java-repack-jars Processing files: containerd-1.3.0-1.tis.x86_64 warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim-runc-v1 warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim-runc-v2 warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl Provides: containerd containerd = 1.3.0-1.tis containerd(x86-64) = 1.3.0-1.tis containerd.io runc Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: libc.so.6()(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.4)(64bit) libc.so.6(GLIBC_2.7)(64bit) libdl.so.2()(64bit) libdl.so.2(GLIBC_2.2.5)(64bit) libpthread.so.0()(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit) libpthread.so.0(GLIBC_2.3.2)(64bit) libseccomp.so.2()(64bit) rtld(GNU_HASH) Processing files: containerd-debuginfo-1.3.0-1.tis.x86_64 Provides: containerd-debuginfo = 1.3.0-1.tis containerd-debuginfo(x86-64) = 1.3.0-1.tis Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64 Wrote: /builddir/build/RPMS/containerd-1.3.0-1.tis.x86_64.rpm Wrote: /builddir/build/RPMS/containerd-debuginfo-1.3.0-1.tis.x86_64.rpm There is nothing obvious in the change log. Looking for something environmental... Scott On 2020-02-04 11:58 p.m., build.starlingx at gmail.com wrote: Project: STX_build_master_master Build #: 408 Status: Failure Timestamp: 20200205T023000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200205T023000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: 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 Don.Penney at windriver.com Wed Feb 5 16:27:52 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 5 Feb 2020 16:27:52 +0000 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure! In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC1633830@ALA-MBD.corp.ad.wrs.com> References: <1384267631.707.1580878701172.JavaMail.javamailuser@localhost> <5db0be7e-5fe9-0875-b242-c0f3d3f1b85e@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC16337EB@ALA-MBD.corp.ad.wrs.com> <287284fa-f1e8-96de-3162-1c3771ae6e3d@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC1633830@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC1633859@ALA-MBD.corp.ad.wrs.com> I’ve verified this fix and will post a review shortly. · cleaned containerd and rpm from workspace · attempt to build just containerd fails, reproducing CENGN failure · update spec with new BuildRequires · attempt to build just containerd fails, due to failure to meet BuildRequires · attempt to build both rpm and containerd succeeds From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 05, 2020 11:13 AM To: Little, Scott; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure! I’ve been able to reproduce the failure, so I’ll try this fix From: Little, Scott Sent: Wednesday, February 05, 2020 10:50 AM To: Penney, Don; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure! Comparing installed_pkgs.log between success and failure cases, I note that the failed build was using the stock CentOS rpm, while the success case used rpm-4.14.0-1.tis.1. I think we should try adding... BuildRequires: rpm-devel >= 4.14.0 BuildRequires: rpm-libs >= 4.14.0 ... to the containerd spec. This should induce an upgrade to the newer rpm. On 2020-02-05 10:42 a.m., Penney, Don wrote: I don’t see any recent updates that would point to this, but I’m trying a build of my own to see if I can reproduce this failure. From: Scott Little [mailto:scott.little at windriver.com] Sent: Wednesday, February 05, 2020 10:25 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure! Failed to build containerd-1.3.0-1.tis.src.rpm + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/src extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/runc extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl *** ERROR: No build ID note found in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl Previous build success looked like this ... note the extra arguments ... + /usr/lib/rpm/find-debuginfo.sh -j24 --strict-build-id -m --build-id-seed 1.3.0-1.tis --unique-debug-suffix -1.3.0-1.tis.x86_64 --unique-debug-src-base containerd-1.3.0-1.tis.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/src extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/runc *** ERROR: No build ID note found in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl readelf: /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/lib/debug/usr/bin/runc-1.3.0-1.tis.x86_64.debug: Error: the dynamic segment offset + size exceeds the size of the file /usr/lib/rpm/sepdebugcrcfix: Updated 0 CRC32s, 1 CRC32s did match. + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-compress + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1 + /usr/lib/rpm/redhat/brp-python-hardlink + /usr/lib/rpm/redhat/brp-java-repack-jars Processing files: containerd-1.3.0-1.tis.x86_64 warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim-runc-v1 warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim-runc-v2 warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl Provides: containerd containerd = 1.3.0-1.tis containerd(x86-64) = 1.3.0-1.tis containerd.io runc Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: libc.so.6()(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.4)(64bit) libc.so.6(GLIBC_2.7)(64bit) libdl.so.2()(64bit) libdl.so.2(GLIBC_2.2.5)(64bit) libpthread.so.0()(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit) libpthread.so.0(GLIBC_2.3.2)(64bit) libseccomp.so.2()(64bit) rtld(GNU_HASH) Processing files: containerd-debuginfo-1.3.0-1.tis.x86_64 Provides: containerd-debuginfo = 1.3.0-1.tis containerd-debuginfo(x86-64) = 1.3.0-1.tis Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64 Wrote: /builddir/build/RPMS/containerd-1.3.0-1.tis.x86_64.rpm Wrote: /builddir/build/RPMS/containerd-debuginfo-1.3.0-1.tis.x86_64.rpm There is nothing obvious in the change log. Looking for something environmental... Scott On 2020-02-04 11:58 p.m., build.starlingx at gmail.com wrote: Project: STX_build_master_master Build #: 408 Status: Failure Timestamp: 20200205T023000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200205T023000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: 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 Don.Penney at windriver.com Wed Feb 5 17:39:58 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 5 Feb 2020 17:39:58 +0000 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure! In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC1633859@ALA-MBD.corp.ad.wrs.com> References: <1384267631.707.1580878701172.JavaMail.javamailuser@localhost> <5db0be7e-5fe9-0875-b242-c0f3d3f1b85e@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC16337EB@ALA-MBD.corp.ad.wrs.com> <287284fa-f1e8-96de-3162-1c3771ae6e3d@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC1633830@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC1633859@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC16338F6@ALA-MBD.corp.ad.wrs.com> A review is posted in starlingx/integ to resolve this build issue: https://review.opendev.org/706009 From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 05, 2020 11:28 AM To: Little, Scott; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure! I’ve verified this fix and will post a review shortly. · cleaned containerd and rpm from workspace · attempt to build just containerd fails, reproducing CENGN failure · update spec with new BuildRequires · attempt to build just containerd fails, due to failure to meet BuildRequires · attempt to build both rpm and containerd succeeds From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 05, 2020 11:13 AM To: Little, Scott; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure! I’ve been able to reproduce the failure, so I’ll try this fix From: Little, Scott Sent: Wednesday, February 05, 2020 10:50 AM To: Penney, Don; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure! Comparing installed_pkgs.log between success and failure cases, I note that the failed build was using the stock CentOS rpm, while the success case used rpm-4.14.0-1.tis.1. I think we should try adding... BuildRequires: rpm-devel >= 4.14.0 BuildRequires: rpm-libs >= 4.14.0 ... to the containerd spec. This should induce an upgrade to the newer rpm. On 2020-02-05 10:42 a.m., Penney, Don wrote: I don’t see any recent updates that would point to this, but I’m trying a build of my own to see if I can reproduce this failure. From: Scott Little [mailto:scott.little at windriver.com] Sent: Wednesday, February 05, 2020 10:25 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 408 - Failure! Failed to build containerd-1.3.0-1.tis.src.rpm + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/src extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/runc extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl *** ERROR: No build ID note found in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl Previous build success looked like this ... note the extra arguments ... + /usr/lib/rpm/find-debuginfo.sh -j24 --strict-build-id -m --build-id-seed 1.3.0-1.tis --unique-debug-suffix -1.3.0-1.tis.x86_64 --unique-debug-src-base containerd-1.3.0-1.tis.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/src extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl extracting debug info from /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/runc *** ERROR: No build ID note found in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl readelf: /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/lib/debug/usr/bin/runc-1.3.0-1.tis.x86_64.debug: Error: the dynamic segment offset + size exceeds the size of the file /usr/lib/rpm/sepdebugcrcfix: Updated 0 CRC32s, 1 CRC32s did match. + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-compress + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1 + /usr/lib/rpm/redhat/brp-python-hardlink + /usr/lib/rpm/redhat/brp-java-repack-jars Processing files: containerd-1.3.0-1.tis.x86_64 warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim-runc-v1 warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/containerd-shim-runc-v2 warning: Missing build-id in /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64/usr/bin/crictl Provides: containerd containerd = 1.3.0-1.tis containerd(x86-64) = 1.3.0-1.tis containerd.io runc Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: libc.so.6()(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.4)(64bit) libc.so.6(GLIBC_2.7)(64bit) libdl.so.2()(64bit) libdl.so.2(GLIBC_2.2.5)(64bit) libpthread.so.0()(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit) libpthread.so.0(GLIBC_2.3.2)(64bit) libseccomp.so.2()(64bit) rtld(GNU_HASH) Processing files: containerd-debuginfo-1.3.0-1.tis.x86_64 Provides: containerd-debuginfo = 1.3.0-1.tis containerd-debuginfo(x86-64) = 1.3.0-1.tis Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/containerd-1.3.0-1.tis.x86_64 Wrote: /builddir/build/RPMS/containerd-1.3.0-1.tis.x86_64.rpm Wrote: /builddir/build/RPMS/containerd-debuginfo-1.3.0-1.tis.x86_64.rpm There is nothing obvious in the change log. Looking for something environmental... Scott On 2020-02-04 11:58 p.m., build.starlingx at gmail.com wrote: Project: STX_build_master_master Build #: 408 Status: Failure Timestamp: 20200205T023000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200205T023000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: 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 maria.g.perez.ibarra at intel.com Wed Feb 5 18:15:35 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Wed, 5 Feb 2020 18:15:35 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200204 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-February-4 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bin.Qian at windriver.com Wed Feb 5 21:09:42 2020 From: Bin.Qian at windriver.com (Qian, Bin) Date: Wed, 5 Feb 2020 21:09:42 +0000 Subject: [Starlingx-discuss] [distcloud-client][security] security vulnerability detected by GitHub Message-ID: Hello, As part of the activity to upload Startlingx repos to GitHub mirror, the distcloud-client is now uploaded to GitHub [1]. Please be aware that there are total 3 vulnerabilities detected by GitHub during the upload. 1. Known moderate severity security vulnerability detected in SQLAlchemy < 1.3.0 defined in requirements.txt. 2. Known moderate severity security vulnerability detected in requests <= 2.19.1 defined in requirements.txt. 3. Known moderate severity security vulnerability detected in SQLAlchemy < 1.3.0 defined in requirements.txt. Do we have planned actions to take care of the vulnerabilities? Best regards, Bin [1] https://github.com/starlingx/distcloud-client -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Thu Feb 6 01:46:13 2020 From: yong.hu at intel.com (Yong Hu) Date: Thu, 6 Feb 2020 09:46:13 +0800 Subject: [Starlingx-discuss] docker instance cannot boot (no boot device) In-Reply-To: References: Message-ID: <72d1d454-9e3a-8664-d6fe-745e6396bcc7@intel.com> Hi Dejan, Were you trying to run docker application inside a VM instance which is managed by OpenStack? I don't quite understand what your use case was, could you articulate a bit more? regards, Yong On 2020/2/4 11:10 PM, Dejan Muhamedagic wrote: > Hi, > > I created in openstack an image of the docker type. When an instance of > that image starts, the console shows the SeaBIOS version followed by > ipxe and the last message is "No bootable device": it looks like as if > openstack is trying to create a VM instead of a container. openstack > shows the "container_format" of the image as "docker". > > The same docker image runs fine on the same controller host when > started by hand (docker load, followed by docker run). > > I couldn't find anything in the logs. > > What am I missing? Should a docker image be created in some special > way? > > Thanks, > > Dejan > CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail at tttech.com immediately. > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From ildiko.vancsa at gmail.com Thu Feb 6 09:19:38 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 6 Feb 2020 10:19:38 +0100 Subject: [Starlingx-discuss] [docs] Onboarding slide deck Message-ID: <02D23DB2-CEE6-4A05-A51A-6240B0A3C191@gmail.com> Hi Kris and Docs team, As discussed on the team meeting yesterday, I uploaded a powerpoint version of the onboarding slide deck to the docs repo, the review is here: https://review.opendev.org/#/c/706199/ Please let me know if it doesn’t open correctly on Windows, I don’t have the capacity to check. I also modified the file name on the website to be more generic so we can link it from the intro part of the docs without the continuous burden of updating the link: https://www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf Where do you think it would fit to link it from the docs page? Thanks, Ildikó From dejan.muhamedagic at tttech-industrial.com Thu Feb 6 14:44:30 2020 From: dejan.muhamedagic at tttech-industrial.com (Dejan Muhamedagic) Date: Thu, 6 Feb 2020 14:44:30 +0000 Subject: [Starlingx-discuss] docker instance cannot boot (no boot device) In-Reply-To: <72d1d454-9e3a-8664-d6fe-745e6396bcc7@intel.com> References: <72d1d454-9e3a-8664-d6fe-745e6396bcc7@intel.com> Message-ID: Hi Yong, On Thu, 2020-02-06 at 09:46 +0800, Yong Hu wrote: > Hi Dejan, > Were you trying to run docker application inside a VM instance which > is > managed by OpenStack? No. I just tried to launch a docker instance. Are docker instances supposed to run within a VM instance? > I don't quite understand what your use case was, could you articulate > a > bit more? I just wanted to create an instance from the image of type docker. There is nothing really special that I tried to do. I looked around for some documentation on how Openstack deploys docker, but couldn't find any information that could help. Thanks, Dejan > > regards, > Yong > > On 2020/2/4 11:10 PM, Dejan Muhamedagic wrote: > > Hi, > > > > I created in openstack an image of the docker type. When an > > instance of > > that image starts, the console shows the SeaBIOS version followed > > by > > ipxe and the last message is "No bootable device": it looks like as > > if > > openstack is trying to create a VM instead of a container. > > openstack > > shows the "container_format" of the image as "docker". > > > > The same docker image runs fine on the same controller host when > > started by hand (docker load, followed by docker run). > > > > I couldn't find anything in the logs. > > > > What am I missing? Should a docker image be created in some special > > way? > > > > Thanks, > > > > Dejan > > CONFIDENTIALITY: The contents of this e-mail are confidential and > > intended only for the above addressee(s). If you are not the > > intended recipient, or the person responsible for delivering it to > > the intended recipient, copying or delivering it to anyone else or > > using it in any unauthorized manner is prohibited and may be > > unlawful. If you receive this e-mail by mistake, please notify the > > sender and the systems administrator at straymail at tttech.com > > immediately. > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail at tttech.com immediately. From Al.Bailey at windriver.com Thu Feb 6 14:57:42 2020 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Thu, 6 Feb 2020 14:57:42 +0000 Subject: [Starlingx-discuss] [distcloud-client][security] security vulnerability detected by GitHub In-Reply-To: References: Message-ID: The requirements.txt file is out of date, and is only used during tox and not as part of the final product. The spec files for the rpm discard the requirements.txt as part of building the rpms https://opendev.org/starlingx/distcloud/src/branch/master/distributedcloud/centos/distributedcloud.spec#L99 The product (ISO) builds and packages with python2-requests-2.21 and python2-sqlalchemy-1.1.11 so there are no vulnerabilities. We should get into the habit of updating those files, since it means that the version of those python modules that we are running tox against, is not the same as we are shipping with. You are welcome to raise a Launchpad (cosmetic, or minor) about cleaning those up. Al From: Qian, Bin [mailto:Bin.Qian at windriver.com] Sent: Wednesday, February 05, 2020 4:10 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [distcloud-client][security] security vulnerability detected by GitHub Hello, As part of the activity to upload Startlingx repos to GitHub mirror, the distcloud-client is now uploaded to GitHub [1]. Please be aware that there are total 3 vulnerabilities detected by GitHub during the upload. 1. Known moderate severity security vulnerability detected in SQLAlchemy < 1.3.0 defined in requirements.txt. 2. Known moderate severity security vulnerability detected in requests <= 2.19.1 defined in requirements.txt. 3. Known moderate severity security vulnerability detected in SQLAlchemy < 1.3.0 defined in requirements.txt. Do we have planned actions to take care of the vulnerabilities? Best regards, Bin [1] https://github.com/starlingx/distcloud-client -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Thu Feb 6 17:35:21 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Thu, 6 Feb 2020 17:35:21 +0000 Subject: [Starlingx-discuss] [docs][meeting] docs team meeting minutes 2020-02-05 Message-ID: Hello All, Here are this week's docs team meeting minutes. Join us if you have interest in StarlingX docs! We meet Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Cheers, Kris 2020-02-05 * All -- reviews merged since last week: 2, 1 abandoned * All -- bug status -- no new, no change on existing * Kris -- Releases * R4.0 - target release date is July 3, 2020. * Opens * Wiki status ? Someone using an out-of-date set of install instructions? See http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007651.html (KRIS AR) ? What steps are needed to stop chasing the split of content between wiki and docs? * Add link to new slidedeck pdf from Ildiko (when ready) - needs follow up. * All -- Ongoing tasks: * Kris -- misc doc clean up -- reviews made, pending approvals. ? Config update/project names: https://storyboard.openstack.org/#!/story/2007193 -- most merged, minor update needed ? Terminology clean up: Review to update docs to use 'worker' instead of 'compute' for worker nodes - updates needed, will apply this week. * Kris -- STX in a box: (https://storyboard.openstack.org/#!/story/2006622) ? Draft in review https://review.opendev.org/#/c/692202/ ? Send Greg summary of STX-in-a-box thread/info (KRIS AR) * Kris -- Transition plan: https://etherpad.openstack.org/p/docs-transition-plan -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Feb 6 17:58:18 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 6 Feb 2020 17:58:18 +0000 Subject: [Starlingx-discuss] Weekly StarlingX Release meeting Message-ID: <151EE31B9FCCA54397A757BC674650F0C1655550@ALA-MBD.corp.ad.wrs.com> My apologies for the short notice, but I have a conflict today, so I'm reducing the meeting to 30mins only. Weekly meeting on Thursday 11AM PT / 1900 UTC Zoom Link: https://zoom.us/j/342730236 Meeting agenda/minutes: https://etherpad.openstack.org/p/stx-releases -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1867 bytes Desc: not available URL: From maria.g.perez.ibarra at intel.com Thu Feb 6 20:40:07 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 6 Feb 2020 20:40:07 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200206 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-FEBRUARY-06 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Fri Feb 7 04:01:48 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 7 Feb 2020 04:01:48 +0000 Subject: [Starlingx-discuss] ceph containerization patch review Message-ID: <56829C2A36C2E542B0CCB9854828E4D8562A76F5@CDSMSX102.ccr.corp.intel.com> Hi folks I enabled containerized ceph cluster with simplex. You can begin to review my patch. I propose to build an image and deploy a simplex system with these patch to check. https://review.opendev.org/#/c/681457/ https://review.opendev.org/#/c/687340/ https://review.opendev.org/#/c/706256/ https://review.opendev.org/#/c/699557/ https://review.opendev.org/#/c/699556/ And I know there is other story, like remove ceph as default backend storage, maybe some conflict, we can discuss together. Tash Done: 1, disable native ceph cluster in ceph.pp 2, disable ceph daemon monitoring in service manager 3, add rook-ceph helm chart to launch ceph cluster 4, add override in stx-config to generate override with starlingx system config 5, sysinv add label in provision stage, to make containerized ceph mon and ceph mgr on designed host 6, add rook-ceph-provisioner helm chart to generate storage class, secret, config and pool for stx-application 7, enabled stx-openstack with containerized ceph 8, update ceph wrapper in stx-config to set or get containerized ceph cluster All these tasks done is enabled with simplex only. Task to do: 1, enable add osd runtime, after system provisioned 2, fix know issue, if system reboot, ceph cluster launch fail 3, enable bluestore and filestore, currently there is only bluestore 4, enable multi-node and duplex 5, enable swift with containerized ceph 6, enable fm alarm for containerized ceph 7, check backup and restore for containerized ceph 8, check system upgrade or how to transit from native ceph cluster to containerized ceph cluster 9, code cleanup 10, update unit test in stx-config BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Fri Feb 7 11:09:33 2020 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Fri, 7 Feb 2020 11:09:33 +0000 Subject: [Starlingx-discuss] the way to enable swift in starlingx In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D85628A95E@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D85628A95E@CDSMSX102.ccr.corp.intel.com> Message-ID: Hi, my setup: STX 3 (2x controller, 2x worker, 3x storage). STX-OpenStack (1.0-19-centos-stable-latest) is currently successfully installed/running... So i try to enable the swift/radosgw, but it fails: controller-0:~$ source /etc/platform/openrc [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify radosgw config service_enabled=true +-------------+--------------------------------------+ | Property | Value | +-------------+--------------------------------------+ | uuid | 11edb3d5-ac8f-4510-950e-cccbf6da4aad | | service | radosgw | | section | config | | name | service_enabled | | value | true | | personality | None | | resource | None | +-------------+--------------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-apply radosgw Applying radosgw service parameters [sysadmin at controller-0 ~(keystone_admin)]$ system helm-chart-attribute-modify stx-openstack ceph-rgw openstack --enabled=true +------------+--------------------+ | Property | Value | +------------+--------------------+ | attributes | {u'enabled': True} | | name | ceph-rgw | | namespace | openstack | +------------+--------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system application-apply stx-openstack +---------------+----------------------------------+ | Property | Value | +---------------+----------------------------------+ | active | True | | app_version | 1.0-19-centos-stable-latest | | created_at | 2020-01-23T12:21:23.423993+00:00 | | manifest_file | stx-openstack.yaml | | manifest_name | armada-manifest | | name | stx-openstack | | progress | None | | status | applying | | updated_at | 2020-01-23T12:52:39.080423+00:00 | +---------------+----------------------------------+ Please use 'system application-list' or 'system application-show stx-openstack' to view the current progress. [sysadmin at controller-0 ~(keystone_admin)]$ system application-list +---------------------+---------------------------+-------------------------------+--------------------+--------------+-------------------------------------+ | application | version | manifest name | manifest file | status | progress | +---------------------+---------------------------+-------------------------------+--------------------+--------------+-------------------------------------+ | platform-integ-apps | 1.0-8 | platform-integration-manifest | manifest.yaml | applied | completed | | stx-openstack | 1.0-19-centos-stable-latest | armada-manifest | stx-openstack.yaml | apply-failed | (0) Reason: SSLError [Errno 2] No such file or directory | +---------------------+---------------------------+-------------------------------+--------------------+--------------+-------------------------------------+ Is there are any other steps to get this running on STX3 and stx-openstack 1.0-19-centos-stable-latest ? Greez & thx, volker... -----Ursprüngliche Nachricht----- Von: Chen, Haochuan Z Gesendet: Montag, 2. Dezember 2019 05:53 An: von Hoesslin, Volker ; 'ji at sibyl.li' Cc: 'starlingx-discuss at lists.starlingx.io' ; Hu, Yong Betreff: the way to enable swift in starlingx Hi system application-upload system service-parameter-modify radosgw config service_enabled=true system service-parameter-apply radosgw system helm-chart-attribute-modify stx-openstack ceph-rgw openstack --enabled=true system application-apply stx-openstack openstack endpoint list | grep object BR! -----Original Message----- From: Chen, Haochuan Z Sent: Thursday, November 28, 2019 10:12 AM To: starlingx-discuss at lists.starlingx.io Cc: Volker.Hoesslin at swsn.de; ji at sibyl.li Subject: swift enabling Hi I find there is voice to enable swift, why it was removed? Thanks! Message: 2 Date: Mon, 25 Nov 2019 07:53:31 -0600 From: joji vlogs To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Enabling Object Storage Message-ID: Content-Type: text/plain; charset="utf-8" Hi all, I recently did a test deployment based on a 2+2+2 setup with one minor difference being I only have one storage server on hand. My question is how would I go about enabling object storage? I saw a reference to it in the helm charts and attempted to set an override but the APIs would not be listening for requests and a "unable to get swift service info" error. Thank you and have a great day! Message: 3 Date: Fri, 22 Nov 2019 14:14:15 +0000 From: "von Hoesslin, Volker" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] STX 2.0: swift? Message-ID: Content-Type: text/plain; charset="iso-8859-1" hi, how can i add the object storage (swift) feature to my current STX2.0 openstack? BR! Martin, Chen SSP, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Tuesday, November 26, 2019 12:05 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 18, Issue 150 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: controller filesystem (Waines, Greg) 2. Enabling Object Storage (joji vlogs) 3. Re: StarlingX 2.0 Account Locked for User (Andy Ning) ---------------------------------------------------------------------- Message: 1 Date: Mon, 25 Nov 2019 13:26:31 +0000 From: "Waines, Greg" To: Saul Wold , "von Hoesslin, Volker" , "Sun, Austin" , "starlingx-discuss at lists.starlingx.io" , "Dale, Kristal" Subject: Re: [Starlingx-discuss] controller filesystem Message-ID: Content-Type: text/plain; charset="utf-8" Actually a section on managing filesystems on the controllers is planned for STX 3.0 ... based on the proposed TOC for the new Operations Guide. Greg From: Saul Wold Date: Thursday, November 21, 2019 at 12:13 PM To: "von Hoesslin, Volker" , "Sun, Austin" , "starlingx-discuss at lists.starlingx.io" , "Dale, Kristal" Subject: Re: [Starlingx-discuss] controller filesystem Kristal: We probably need a Story/Task added to the documentation to get the documentation of host-fs added in the right place. This helps with filesystem re-sizing. Maybe it's already there. Sau! On 11/21/19 7:12 AM, von Hoesslin, Volker wrote: incredible !!! thats the point i have search! big thx! ------------------------------------------------------------------------ *Von:* Sun, Austin [austin.sun at intel.com] *Gesendet:* Donnerstag, 21. November 2019 15:20 *An:* von Hoesslin, Volker; starlingx-discuss at lists.starlingx.io *Betreff:* Re: [Starlingx-discuss] controller filesystem Hi Volker: From the email chain, http://lists.starlingx.io/pipermail/starlingx-discuss/2019-August/005656.html You can probably the command line to change the size of docker lv Thanks. BR Austin Sun. *From:* von Hoesslin, Volker > *Sent:* Thursday, November 21, 2019 9:20 PM *To:* starlingx-discuss at lists.starlingx.io *Subject:* [Starlingx-discuss] controller filesystem hi, i trying to import some existing qcow2 images into my new installed STX 2.0. openstack image create --file /media/foobar.qcow2 --private --unprotected --disk-format qcow2 "foobar" all works fine, the image are available. now, i'm trying to create an new volume based on this images. if the images are <=6GB all works fine, but some images are very huge (10-200GB) and then it ends in an error. after some research i can see on controller the mount point /dev/mapper/cgts--vg-docker--lv 30G 11G 20G 35% /var/lib/docker increase the used storage. after fail "volume create" it goes back to given value 35%. in my oppinion, this mount point should resize to some value about 300-400GB, but how? in STX horizon backend (http://10.10.10.2:8080/admin/system_config/?tab=system_config_tab__storage_table) there is an "docker-distribution", but no docker-mount-point itself? btw, if i try to change the "docker-distribution" value to some other value (eg. 500GB via horizon backend), i got this error: *Error: *backup size of 60 is insufficient for host controller-1. Minimum backup size of 100 is required based upon glance size 20 and database size 20. Rejecting modification request. - see attachment - how can i increase the backup size to handle this error?! greez & thx, volker... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Mon, 25 Nov 2019 07:53:31 -0600 From: joji vlogs To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Enabling Object Storage Message-ID: Content-Type: text/plain; charset="utf-8" Hi all, I recently did a test deployment based on a 2+2+2 setup with one minor difference being I only have one storage server on hand. My question is how would I go about enabling object storage? I saw a reference to it in the helm charts and attempted to set an override but the APIs would not be listening for requests and a "unable to get swift service info" error. Thank you and have a great day! Austin Gillmann -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Mon, 25 Nov 2019 11:05:19 -0500 From: Andy Ning To: Subject: Re: [Starlingx-discuss] StarlingX 2.0 Account Locked for User Message-ID: <8f8e6cad-0ad7-4be4-6693-a25e6cec93ad at windriver.com> Content-Type: text/plain; charset="utf-8"; format=flowed On 2019-11-25 12:00 AM, Yong Hu wrote: > Hi Anirudh, > > This issue is similar to this LP#1853017 [0], which was triggered the > account locking if the password of Openstack user "admin" was changed. > In this LP, for unknown reason, "registry-token-server" daemon kept > accessing "keystone" on host (not the instance in containers) with > obsolete token and led to "admin" account locked after 5 attempts. > If registry token server keeps on accessing keystone with obsolete token, this could be a bug in the token server. Normally if a keystone client get a failed authentication, it should try to retrieve a new token by using username/password. Andy > Right now, I am debugging this issue. > Good thing is Cengn build 11/16 seemed not to have such a problem > (LP#1853017). > > You might have a try with this version? > BTW: which cengn build were you using? > > > [0] https://bugs.launchpad.net/starlingx/+bug/1853017 > > regards, > Yong > > On 2019/11/19 6:06 PM, Anirudh Gupta wrote: >> Hi Team, >> >> I have installed StarlingX 2.0 Duplex Bare Metal. >> >> I am trying to create 2 VM’s and repeating this cycle a number of times. >> >> After using the setup for around half and hour, I am not longer able >> to access the GUI. >> >> Ever though I type correct Username/Password, it gives an error of >> Invalid Credentials. >> >> Then, I thought to use the CLI commands by following LOAD CLI section >> given in link >> >> https://docs.starlingx.io/deploy_install_guides/r2_release/openstack/ >> access.html#local-cli >> >> >> But with this also, I am facing the same error >> >> controller-0:~$ export OS_CLOUD=openstack_helm >> >> controller-0:~$ openstack endpoint list >> >> The account is locked for user: 230578cde382430a8adac399afab1230. >> (HTTP 401) (Request-ID: req-6da6d59a-2edd-4f2b-a8bf-f13f2e423a77) >> >> Earlier this automatically started working after 5-7 mins. >> >> But this time, I am completely Blocked. >> >> I have also raised a bug regarding the same >> >> https://bugs.launchpad.net/starlingx/+bug/1853093 >> >> Please suggest some pointers, so that I can unblock and resume my >> activities. >> >> Regards >> >> Anirudh Gupta >> >> DISCLAIMER: This electronic message and all of its contents, contains >> information which is privileged, confidential or otherwise protected >> from disclosure. The information contained in this electronic mail >> transmission is intended for use only by the individual or entity to >> which it is addressed. If you are not the intended recipient or may >> have received this electronic mail transmission in error, please >> notify the sender immediately and delete / destroy all copies of this >> electronic mail transmission without disclosing, copying, >> distributing, forwarding, printing or retaining any part of it. >> Hughes Systique accepts no responsibility for loss or damage arising >> from the use of the information transmitted by this email including >> damage from virus. >> >> _______________________________________________ >> 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 -- Andy Ning Cube: 3071 Tel: 613-9631408 (int: 4408) Skype: andy.ning.wr ------------------------------ 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 18, Issue 150 ************************************************** From haochuan.z.chen at intel.com Fri Feb 7 11:37:59 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 7 Feb 2020 11:37:59 +0000 Subject: [Starlingx-discuss] the way to enable swift in starlingx In-Reply-To: References: <56829C2A36C2E542B0CCB9854828E4D85628A95E@CDSMSX102.ccr.corp.intel.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D8562A78C9@CDSMSX102.ccr.corp.intel.com> You can save all the log, with command collect, and submit a launchpad issue with log attached. $ collect https://bugs.launchpad.net/starlingx/+filebug Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: von Hoesslin, Volker Sent: Friday, February 7, 2020 7:10 PM To: Chen, Haochuan Z ; 'ji at sibyl.li' Cc: 'starlingx-discuss at lists.starlingx.io' ; Hu, Yong Subject: AW: the way to enable swift in starlingx Hi, my setup: STX 3 (2x controller, 2x worker, 3x storage). STX-OpenStack (1.0-19-centos-stable-latest) is currently successfully installed/running... So i try to enable the swift/radosgw, but it fails: controller-0:~$ source /etc/platform/openrc [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify radosgw config service_enabled=true +-------------+--------------------------------------+ | Property | Value | +-------------+--------------------------------------+ | uuid | 11edb3d5-ac8f-4510-950e-cccbf6da4aad | | service | radosgw | | section | config | | name | service_enabled | | value | true | | personality | None | | resource | None | +-------------+--------------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-apply radosgw Applying radosgw service parameters [sysadmin at controller-0 ~(keystone_admin)]$ system helm-chart-attribute-modify stx-openstack ceph-rgw openstack --enabled=true +------------+--------------------+ | Property | Value | +------------+--------------------+ | attributes | {u'enabled': True} | | name | ceph-rgw | | namespace | openstack | +------------+--------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system application-apply stx-openstack +---------------+----------------------------------+ | Property | Value | +---------------+----------------------------------+ | active | True | | app_version | 1.0-19-centos-stable-latest | | created_at | 2020-01-23T12:21:23.423993+00:00 | | manifest_file | stx-openstack.yaml | | manifest_name | armada-manifest | | name | stx-openstack | | progress | None | | status | applying | | updated_at | 2020-01-23T12:52:39.080423+00:00 | +---------------+----------------------------------+ Please use 'system application-list' or 'system application-show stx-openstack' to view the current progress. [sysadmin at controller-0 ~(keystone_admin)]$ system application-list +---------------------+---------------------------+-------------------------------+--------------------+--------------+-------------------------------------+ | application | version | manifest name | manifest file | status | progress | +---------------------+---------------------------+-------------------------------+--------------------+--------------+-------------------------------------+ | platform-integ-apps | 1.0-8 | platform-integration-manifest | manifest.yaml | applied | completed | | stx-openstack | 1.0-19-centos-stable-latest | armada-manifest | stx-openstack.yaml | apply-failed | (0) Reason: SSLError [Errno 2] No such file or directory | +---------------------+---------------------------+-------------------------------+--------------------+--------------+-------------------------------------+ Is there are any other steps to get this running on STX3 and stx-openstack 1.0-19-centos-stable-latest ? Greez & thx, volker... -----Ursprüngliche Nachricht----- Von: Chen, Haochuan Z Gesendet: Montag, 2. Dezember 2019 05:53 An: von Hoesslin, Volker ; 'ji at sibyl.li' Cc: 'starlingx-discuss at lists.starlingx.io' ; Hu, Yong Betreff: the way to enable swift in starlingx Hi system application-upload system service-parameter-modify radosgw config service_enabled=true system service-parameter-apply radosgw system helm-chart-attribute-modify stx-openstack ceph-rgw openstack --enabled=true system application-apply stx-openstack openstack endpoint list | grep object BR! -----Original Message----- From: Chen, Haochuan Z Sent: Thursday, November 28, 2019 10:12 AM To: starlingx-discuss at lists.starlingx.io Cc: Volker.Hoesslin at swsn.de; ji at sibyl.li Subject: swift enabling Hi I find there is voice to enable swift, why it was removed? Thanks! Message: 2 Date: Mon, 25 Nov 2019 07:53:31 -0600 From: joji vlogs To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Enabling Object Storage Message-ID: Content-Type: text/plain; charset="utf-8" Hi all, I recently did a test deployment based on a 2+2+2 setup with one minor difference being I only have one storage server on hand. My question is how would I go about enabling object storage? I saw a reference to it in the helm charts and attempted to set an override but the APIs would not be listening for requests and a "unable to get swift service info" error. Thank you and have a great day! Message: 3 Date: Fri, 22 Nov 2019 14:14:15 +0000 From: "von Hoesslin, Volker" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] STX 2.0: swift? Message-ID: Content-Type: text/plain; charset="iso-8859-1" hi, how can i add the object storage (swift) feature to my current STX2.0 openstack? BR! Martin, Chen SSP, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Tuesday, November 26, 2019 12:05 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 18, Issue 150 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: controller filesystem (Waines, Greg) 2. Enabling Object Storage (joji vlogs) 3. Re: StarlingX 2.0 Account Locked for User (Andy Ning) ---------------------------------------------------------------------- Message: 1 Date: Mon, 25 Nov 2019 13:26:31 +0000 From: "Waines, Greg" To: Saul Wold , "von Hoesslin, Volker" , "Sun, Austin" , "starlingx-discuss at lists.starlingx.io" , "Dale, Kristal" Subject: Re: [Starlingx-discuss] controller filesystem Message-ID: Content-Type: text/plain; charset="utf-8" Actually a section on managing filesystems on the controllers is planned for STX 3.0 ... based on the proposed TOC for the new Operations Guide. Greg From: Saul Wold Date: Thursday, November 21, 2019 at 12:13 PM To: "von Hoesslin, Volker" , "Sun, Austin" , "starlingx-discuss at lists.starlingx.io" , "Dale, Kristal" Subject: Re: [Starlingx-discuss] controller filesystem Kristal: We probably need a Story/Task added to the documentation to get the documentation of host-fs added in the right place. This helps with filesystem re-sizing. Maybe it's already there. Sau! On 11/21/19 7:12 AM, von Hoesslin, Volker wrote: incredible !!! thats the point i have search! big thx! ------------------------------------------------------------------------ *Von:* Sun, Austin [austin.sun at intel.com] *Gesendet:* Donnerstag, 21. November 2019 15:20 *An:* von Hoesslin, Volker; starlingx-discuss at lists.starlingx.io *Betreff:* Re: [Starlingx-discuss] controller filesystem Hi Volker: From the email chain, http://lists.starlingx.io/pipermail/starlingx-discuss/2019-August/005656.html You can probably the command line to change the size of docker lv Thanks. BR Austin Sun. *From:* von Hoesslin, Volker > *Sent:* Thursday, November 21, 2019 9:20 PM *To:* starlingx-discuss at lists.starlingx.io *Subject:* [Starlingx-discuss] controller filesystem hi, i trying to import some existing qcow2 images into my new installed STX 2.0. openstack image create --file /media/foobar.qcow2 --private --unprotected --disk-format qcow2 "foobar" all works fine, the image are available. now, i'm trying to create an new volume based on this images. if the images are <=6GB all works fine, but some images are very huge (10-200GB) and then it ends in an error. after some research i can see on controller the mount point /dev/mapper/cgts--vg-docker--lv 30G 11G 20G 35% /var/lib/docker increase the used storage. after fail "volume create" it goes back to given value 35%. in my oppinion, this mount point should resize to some value about 300-400GB, but how? in STX horizon backend (http://10.10.10.2:8080/admin/system_config/?tab=system_config_tab__storage_table) there is an "docker-distribution", but no docker-mount-point itself? btw, if i try to change the "docker-distribution" value to some other value (eg. 500GB via horizon backend), i got this error: *Error: *backup size of 60 is insufficient for host controller-1. Minimum backup size of 100 is required based upon glance size 20 and database size 20. Rejecting modification request. - see attachment - how can i increase the backup size to handle this error?! greez & thx, volker... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Mon, 25 Nov 2019 07:53:31 -0600 From: joji vlogs To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Enabling Object Storage Message-ID: Content-Type: text/plain; charset="utf-8" Hi all, I recently did a test deployment based on a 2+2+2 setup with one minor difference being I only have one storage server on hand. My question is how would I go about enabling object storage? I saw a reference to it in the helm charts and attempted to set an override but the APIs would not be listening for requests and a "unable to get swift service info" error. Thank you and have a great day! Austin Gillmann -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Mon, 25 Nov 2019 11:05:19 -0500 From: Andy Ning To: Subject: Re: [Starlingx-discuss] StarlingX 2.0 Account Locked for User Message-ID: <8f8e6cad-0ad7-4be4-6693-a25e6cec93ad at windriver.com> Content-Type: text/plain; charset="utf-8"; format=flowed On 2019-11-25 12:00 AM, Yong Hu wrote: > Hi Anirudh, > > This issue is similar to this LP#1853017 [0], which was triggered the > account locking if the password of Openstack user "admin" was changed. > In this LP, for unknown reason, "registry-token-server" daemon kept > accessing "keystone" on host (not the instance in containers) with > obsolete token and led to "admin" account locked after 5 attempts. > If registry token server keeps on accessing keystone with obsolete token, this could be a bug in the token server. Normally if a keystone client get a failed authentication, it should try to retrieve a new token by using username/password. Andy > Right now, I am debugging this issue. > Good thing is Cengn build 11/16 seemed not to have such a problem > (LP#1853017). > > You might have a try with this version? > BTW: which cengn build were you using? > > > [0] https://bugs.launchpad.net/starlingx/+bug/1853017 > > regards, > Yong > > On 2019/11/19 6:06 PM, Anirudh Gupta wrote: >> Hi Team, >> >> I have installed StarlingX 2.0 Duplex Bare Metal. >> >> I am trying to create 2 VM’s and repeating this cycle a number of times. >> >> After using the setup for around half and hour, I am not longer able >> to access the GUI. >> >> Ever though I type correct Username/Password, it gives an error of >> Invalid Credentials. >> >> Then, I thought to use the CLI commands by following LOAD CLI section >> given in link >> >> https://docs.starlingx.io/deploy_install_guides/r2_release/openstack/ >> access.html#local-cli >> >> >> But with this also, I am facing the same error >> >> controller-0:~$ export OS_CLOUD=openstack_helm >> >> controller-0:~$ openstack endpoint list >> >> The account is locked for user: 230578cde382430a8adac399afab1230. >> (HTTP 401) (Request-ID: req-6da6d59a-2edd-4f2b-a8bf-f13f2e423a77) >> >> Earlier this automatically started working after 5-7 mins. >> >> But this time, I am completely Blocked. >> >> I have also raised a bug regarding the same >> >> https://bugs.launchpad.net/starlingx/+bug/1853093 >> >> Please suggest some pointers, so that I can unblock and resume my >> activities. >> >> Regards >> >> Anirudh Gupta >> >> DISCLAIMER: This electronic message and all of its contents, contains >> information which is privileged, confidential or otherwise protected >> from disclosure. The information contained in this electronic mail >> transmission is intended for use only by the individual or entity to >> which it is addressed. If you are not the intended recipient or may >> have received this electronic mail transmission in error, please >> notify the sender immediately and delete / destroy all copies of this >> electronic mail transmission without disclosing, copying, >> distributing, forwarding, printing or retaining any part of it. >> Hughes Systique accepts no responsibility for loss or damage arising >> from the use of the information transmitted by this email including >> damage from virus. >> >> _______________________________________________ >> 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 -- Andy Ning Cube: 3071 Tel: 613-9631408 (int: 4408) Skype: andy.ning.wr ------------------------------ 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 18, Issue 150 ************************************************** From Volker.Hoesslin at swsn.de Fri Feb 7 12:46:03 2020 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Fri, 7 Feb 2020 12:46:03 +0000 Subject: [Starlingx-discuss] the way to enable swift in starlingx In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D8562A78C9@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D85628A95E@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A78C9@CDSMSX102.ccr.corp.intel.com> Message-ID: After some research i have checked the stx-openstack.yaml and checkout the chart-url: http://172.17.0.1/helm_charts/starlingx/ceph-rgw-0.1.0.tgz so i curl this endpoint and got an 404 ... so i tried an controller swact... re-apply stx-openstack on controller-1 and it seems running now... $ system application-list +---------------------+---------------------------+-------------------------------+----------------+----------+----------------------------------------------+ | application | version | manifest name | manifest file | status | progress | +---------------------+---------------------------+-------------------------------+----------------+----------+----------------------------------------------+ | platform-integ-apps | 1.0-8 | platform-integration-manifest | manifest.yaml | applied | completed | | stx-openstack | 1.0-19-centos-stable-latest | armada-manifest | stx-openstack.yaml | applying | processing chart: osh-openstack-cinder, overall completion: 36.0% | +---------------------+---------------------------+-------------------------------+----------------+----------+----------------------------------------------+ --- after some minutes... After time its stopped with a failure... i have checked the logs and got the info that the script is waiting for an evicted cinder-volume pod, i think evicted pods should be skipped on script? So i delete this old pod and re-apply the stx-openstack... for now ist running... --- after some minutes Applying is still stopped at 71% on waitung on evicted horizon-pods... after delete all evicted pods, the script is finished successed... So, i tried to use the OS-horizon gui to checkout the new options: Object Storage -> containers ... if i click on this section i got some access-denied toasts and my current user (admin) is logged off... how can i handle this and define the nessesary roles/groups to access this section? Greez & thx, volker... -----Ursprüngliche Nachricht----- Von: Chen, Haochuan Z Gesendet: Freitag, 7. Februar 2020 12:38 An: von Hoesslin, Volker ; 'ji at sibyl.li' Cc: 'starlingx-discuss at lists.starlingx.io' ; Hu, Yong Betreff: [URL wurde verändert] Re: [Starlingx-discuss] the way to enable swift in starlingx Externe E-Mail! Öffnen Sie nur Links oder Anhänge von vertrauenswürdigen Absendern! You can save all the log, with command collect, and submit a launchpad issue with log attached. $ collect http://Achtung/https://bugs.launchpad.net/starlingx/+filebug Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: von Hoesslin, Volker Sent: Friday, February 7, 2020 7:10 PM To: Chen, Haochuan Z ; 'ji at sibyl.li' Cc: 'starlingx-discuss at lists.starlingx.io' ; Hu, Yong Subject: AW: the way to enable swift in starlingx Hi, my setup: STX 3 (2x controller, 2x worker, 3x storage). STX-OpenStack (1.0-19-centos-stable-latest) is currently successfully installed/running... So i try to enable the swift/radosgw, but it fails: controller-0:~$ source /etc/platform/openrc [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify radosgw config service_enabled=true +-------------+--------------------------------------+ | Property | Value | +-------------+--------------------------------------+ | uuid | 11edb3d5-ac8f-4510-950e-cccbf6da4aad | | service | radosgw | | section | config | | name | service_enabled | | value | true | | personality | None | | resource | None | +-------------+--------------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-apply radosgw Applying radosgw service parameters [sysadmin at controller-0 ~(keystone_admin)]$ system helm-chart-attribute-modify stx-openstack ceph-rgw openstack --enabled=true +------------+--------------------+ | Property | Value | +------------+--------------------+ | attributes | {u'enabled': True} | | name | ceph-rgw | | namespace | openstack | +------------+--------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system application-apply stx-openstack +---------------+----------------------------------+ | Property | Value | +---------------+----------------------------------+ | active | True | | app_version | 1.0-19-centos-stable-latest | | created_at | 2020-01-23T12:21:23.423993+00:00 | | manifest_file | stx-openstack.yaml | | manifest_name | armada-manifest | | name | stx-openstack | | progress | None | | status | applying | | updated_at | 2020-01-23T12:52:39.080423+00:00 | +---------------+----------------------------------+ Please use 'system application-list' or 'system application-show stx-openstack' to view the current progress. [sysadmin at controller-0 ~(keystone_admin)]$ system application-list +---------------------+---------------------------+-------------------------------+--------------------+--------------+-------------------------------------+ | application | version | manifest name | manifest file | status | progress | +---------------------+---------------------------+-------------------------------+--------------------+--------------+-------------------------------------+ | platform-integ-apps | 1.0-8 | platform-integration-manifest | manifest.yaml | applied | completed | | stx-openstack | 1.0-19-centos-stable-latest | armada-manifest | stx-openstack.yaml | apply-failed | (0) Reason: SSLError [Errno 2] No such file or directory | +---------------------+---------------------------+-------------------------------+--------------------+--------------+-------------------------------------+ Is there are any other steps to get this running on STX3 and stx-openstack 1.0-19-centos-stable-latest ? Greez & thx, volker... -----Ursprüngliche Nachricht----- Von: Chen, Haochuan Z Gesendet: Montag, 2. Dezember 2019 05:53 An: von Hoesslin, Volker ; 'ji at sibyl.li' Cc: 'starlingx-discuss at lists.starlingx.io' ; Hu, Yong Betreff: the way to enable swift in starlingx Hi system application-upload system service-parameter-modify radosgw config service_enabled=true system service-parameter-apply radosgw system helm-chart-attribute-modify stx-openstack ceph-rgw openstack --enabled=true system application-apply stx-openstack openstack endpoint list | grep object BR! -----Original Message----- From: Chen, Haochuan Z Sent: Thursday, November 28, 2019 10:12 AM To: starlingx-discuss at lists.starlingx.io Cc: Volker.Hoesslin at swsn.de; ji at sibyl.li Subject: swift enabling Hi I find there is voice to enable swift, why it was removed? Thanks! Message: 2 Date: Mon, 25 Nov 2019 07:53:31 -0600 From: joji vlogs To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Enabling Object Storage Message-ID: Content-Type: text/plain; charset="utf-8" Hi all, I recently did a test deployment based on a 2+2+2 setup with one minor difference being I only have one storage server on hand. My question is how would I go about enabling object storage? I saw a reference to it in the helm charts and attempted to set an override but the APIs would not be listening for requests and a "unable to get swift service info" error. Thank you and have a great day! Message: 3 Date: Fri, 22 Nov 2019 14:14:15 +0000 From: "von Hoesslin, Volker" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] STX 2.0: swift? Message-ID: Content-Type: text/plain; charset="iso-8859-1" hi, how can i add the object storage (swift) feature to my current STX2.0 openstack? BR! Martin, Chen SSP, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Tuesday, November 26, 2019 12:05 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 18, Issue 150 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://Achtung/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: controller filesystem (Waines, Greg) 2. Enabling Object Storage (joji vlogs) 3. Re: StarlingX 2.0 Account Locked for User (Andy Ning) ---------------------------------------------------------------------- Message: 1 Date: Mon, 25 Nov 2019 13:26:31 +0000 From: "Waines, Greg" To: Saul Wold , "von Hoesslin, Volker" , "Sun, Austin" , "starlingx-discuss at lists.starlingx.io" , "Dale, Kristal" Subject: Re: [Starlingx-discuss] controller filesystem Message-ID: Content-Type: text/plain; charset="utf-8" Actually a section on managing filesystems on the controllers is planned for STX 3.0 ... based on the proposed TOC for the new Operations Guide. Greg From: Saul Wold Date: Thursday, November 21, 2019 at 12:13 PM To: "von Hoesslin, Volker" , "Sun, Austin" , "starlingx-discuss at lists.starlingx.io" , "Dale, Kristal" Subject: Re: [Starlingx-discuss] controller filesystem Kristal: We probably need a Story/Task added to the documentation to get the documentation of host-fs added in the right place. This helps with filesystem re-sizing. Maybe it's already there. Sau! On 11/21/19 7:12 AM, von Hoesslin, Volker wrote: incredible !!! thats the point i have search! big thx! ------------------------------------------------------------------------ *Von:* Sun, Austin [austin.sun at intel.com] *Gesendet:* Donnerstag, 21. November 2019 15:20 *An:* von Hoesslin, Volker; starlingx-discuss at lists.starlingx.io *Betreff:* Re: [Starlingx-discuss] controller filesystem Hi Volker: From the email chain, http://Achtung/http://lists.starlingx.io/pipermail/starlingx-discuss/2019-August/005656.html You can probably the command line to change the size of docker lv Thanks. BR Austin Sun. *From:* von Hoesslin, Volker > *Sent:* Thursday, November 21, 2019 9:20 PM *To:* starlingx-discuss at lists.starlingx.io *Subject:* [Starlingx-discuss] controller filesystem hi, i trying to import some existing qcow2 images into my new installed STX 2.0. openstack image create --file /media/foobar.qcow2 --private --unprotected --disk-format qcow2 "foobar" all works fine, the image are available. now, i'm trying to create an new volume based on this images. if the images are <=6GB all works fine, but some images are very huge (10-200GB) and then it ends in an error. after some research i can see on controller the mount point /dev/mapper/cgts--vg-docker--lv 30G 11G 20G 35% /var/lib/docker increase the used storage. after fail "volume create" it goes back to given value 35%. in my oppinion, this mount point should resize to some value about 300-400GB, but how? in STX horizon backend (http://Achtung/http://10.10.10.2:8080/admin/system_config/?tab=system_config_tab__storage_table) there is an "docker-distribution", but no docker-mount-point itself? btw, if i try to change the "docker-distribution" value to some other value (eg. 500GB via horizon backend), i got this error: *Error: *backup size of 60 is insufficient for host controller-1. Minimum backup size of 100 is required based upon glance size 20 and database size 20. Rejecting modification request. - see attachment - how can i increase the backup size to handle this error?! greez & thx, volker... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://Achtung/http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://Achtung/http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Mon, 25 Nov 2019 07:53:31 -0600 From: joji vlogs To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Enabling Object Storage Message-ID: Content-Type: text/plain; charset="utf-8" Hi all, I recently did a test deployment based on a 2+2+2 setup with one minor difference being I only have one storage server on hand. My question is how would I go about enabling object storage? I saw a reference to it in the helm charts and attempted to set an override but the APIs would not be listening for requests and a "unable to get swift service info" error. Thank you and have a great day! Austin Gillmann -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Mon, 25 Nov 2019 11:05:19 -0500 From: Andy Ning To: Subject: Re: [Starlingx-discuss] StarlingX 2.0 Account Locked for User Message-ID: <8f8e6cad-0ad7-4be4-6693-a25e6cec93ad at windriver.com> Content-Type: text/plain; charset="utf-8"; format=flowed On 2019-11-25 12:00 AM, Yong Hu wrote: > Hi Anirudh, > > This issue is similar to this LP#1853017 [0], which was triggered the > account locking if the password of Openstack user "admin" was changed. > In this LP, for unknown reason, "registry-token-server" daemon kept > accessing "keystone" on host (not the instance in containers) with > obsolete token and led to "admin" account locked after 5 attempts. > If registry token server keeps on accessing keystone with obsolete token, this could be a bug in the token server. Normally if a keystone client get a failed authentication, it should try to retrieve a new token by using username/password. Andy > Right now, I am debugging this issue. > Good thing is Cengn build 11/16 seemed not to have such a problem > (LP#1853017). > > You might have a try with this version? > BTW: which cengn build were you using? > > > [0] http://Achtung/https://bugs.launchpad.net/starlingx/+bug/1853017 > > regards, > Yong > > On 2019/11/19 6:06 PM, Anirudh Gupta wrote: >> Hi Team, >> >> I have installed StarlingX 2.0 Duplex Bare Metal. >> >> I am trying to create 2 VM’s and repeating this cycle a number of times. >> >> After using the setup for around half and hour, I am not longer able >> to access the GUI. >> >> Ever though I type correct Username/Password, it gives an error of >> Invalid Credentials. >> >> Then, I thought to use the CLI commands by following LOAD CLI section >> given in link >> >> http://Achtung/https://docs.starlingx.io/deploy_install_guides/r2_rel >> ease/openstack/ >> access.html#local-cli >> >> >> But with this also, I am facing the same error >> >> controller-0:~$ export OS_CLOUD=openstack_helm >> >> controller-0:~$ openstack endpoint list >> >> The account is locked for user: 230578cde382430a8adac399afab1230. >> (HTTP 401) (Request-ID: req-6da6d59a-2edd-4f2b-a8bf-f13f2e423a77) >> >> Earlier this automatically started working after 5-7 mins. >> >> But this time, I am completely Blocked. >> >> I have also raised a bug regarding the same >> >> http://Achtung/https://bugs.launchpad.net/starlingx/+bug/1853093 >> >> Please suggest some pointers, so that I can unblock and resume my >> activities. >> >> Regards >> >> Anirudh Gupta >> >> DISCLAIMER: This electronic message and all of its contents, contains >> information which is privileged, confidential or otherwise protected >> from disclosure. The information contained in this electronic mail >> transmission is intended for use only by the individual or entity to >> which it is addressed. If you are not the intended recipient or may >> have received this electronic mail transmission in error, please >> notify the sender immediately and delete / destroy all copies of this >> electronic mail transmission without disclosing, copying, >> distributing, forwarding, printing or retaining any part of it. >> Hughes Systique accepts no responsibility for loss or damage arising >> from the use of the information transmitted by this email including >> damage from virus. >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://Achtung/http://lists.starlingx.io/cgi-bin/mailman/listinfo/sta >> rlingx-discuss >> > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://Achtung/http://lists.starlingx.io/cgi-bin/mailman/listinfo/star > lingx-discuss -- Andy Ning Cube: 3071 Tel: 613-9631408 (int: 4408) Skype: andy.ning.wr ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://Achtung/http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 18, Issue 150 ************************************************** _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://Achtung/http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Jerry.Sun at windriver.com Fri Feb 7 14:31:39 2020 From: Jerry.Sun at windriver.com (Sun, Yicheng (Jerry)) Date: Fri, 7 Feb 2020 14:31:39 +0000 Subject: [Starlingx-discuss] stx docs input:2006711 Message-ID: Hi All, Attached is the documentation changes required for the "Windows Active Directory Auth Support for K8S API" story (https://storyboard.openstack.org/#!/story/2006711) Thanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: StarlingX Windows Active Directory documentation.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 32494 bytes Desc: StarlingX Windows Active Directory documentation.docx URL: From dharmakemo at gmail.com Tue Feb 4 06:16:57 2020 From: dharmakemo at gmail.com (dharma yusuf setiawan) Date: Tue, 4 Feb 2020 13:16:57 +0700 Subject: [Starlingx-discuss] Failed to update the initial system config. Message-ID: i want to ask question, sorry bad english. i have installed dedicated storage with 1 controller ( controller-0) on virtual environment. but when i deploying subcloud(edgecloud) with ansible, i have some error "Failed to update the initial system config." could someone help me please -------------- next part -------------- An HTML attachment was scrubbed... URL: From wesley.yang at jitstack.com Tue Feb 4 08:27:37 2020 From: wesley.yang at jitstack.com (wesley.yang at jitstack.com) Date: Tue, 4 Feb 2020 16:27:37 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSNOiBQQlIgU3RhdHVzIENoZWNr?= In-Reply-To: References: <5f55cb03-5360-3e11-fcc9-46f6dc24d6f8@linux.intel.com> Message-ID: <060f01d5db34$f5e38a50$e1aa9ef0$@jitstack.com>+CCE794F622210891 Hi Saul I'm working at home remotely at home for the Government's restriction, my colleagues are also working remotely or still on vacation. You may see that my colleagues Yakun has just sent the preliminary result to you, and he will do some more test and update later. Wesley -----邮件原件----- 发件人: Saul Wold 发送时间: 2020年2月4日 8:54 收件人: wesley.yang at jitstack.com; daniels.cai at jitstack.com; Yang, Bin 抄送: Hu, Yong ; starlingx-discuss at lists.starlingx.io 主题: Re: PBR Status Check Hi Wesley, Following up on this, I am not sure what your working status is because of the Virus and various Gov't restrictions. If you are working, can you give us an update on the Performance impact question I listed below. Thanks Sau! On 1/22/20 10:14 AM, Saul Wold wrote: > > Hi All & Welcome Wesley, > > We have a new community member from JitStack starting to look at the > PBR work, here is some background for him. > > The PBR work was proposed via the StarlingX Feature Specification > process, see the Flock Versioning specification [0], this is based on > the OpenStack Python Build Reasonableness [1] and Semantic Versioning > (SemVer) [2] definition. > > One of the issues that we are trying to resolve is the impact of the > proposed change from Bin Yang to the time it takes to build a single > package with PBR before and after the change. Ideally this would be > done multiple times and provide the average along with the deviation. > This in an important part of the project in order for us to move forward. > > Look forward to working with you. > > Sau! > > [0] > https://docs.starlingx.io/specs/specs/stx-3.0/approved/standardize_flo > ck_versioning.html > > [1] https://docs.openstack.org/pbr/latest/ > [2] https://docs.openstack.org/pbr/latest/user/semver.html -------------- next part -------------- An embedded message was scrubbed... From: Subject: Re: Testing performance impact of PBR Date: Tue, 4 Feb 2020 16:15:53 +0800 Size: 21362 URL: From huifeng.le at intel.com Thu Feb 6 14:56:10 2020 From: huifeng.le at intel.com (Le, Huifeng) Date: Thu, 6 Feb 2020 14:56:10 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 02/06 Message-ID: <76647BD697F40748B1FA4F56DA02AA0B4D687A02@SHSMSX104.ccr.corp.intel.com> Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Team Meeting Agenda/Notes - Feb 06/2020 * stx3.0 bugs: * https://bugs.launchpad.net/starlingx/+bug/1821026: Containers: Resolving hostname fails within nova containers leading to config_drive VM migration failures * Penging on ipv6 test, Zhipeng help to check * stx2.0 bugs: * https://bugs.launchpad.net/starlingx/+bug/1849655 StarlingX R2 duplex: VM not getting IP assigned to the vlan network when re-spawned on controller-0 after shutting down controller-1 * Wang, Yi help to check * stx 4.0 features: * TSN support in Kata: Shuicheng will take this over as the prime * Containerize OVS-DPDK: (from release meeting notes: consider this out of stx.4.0, Mingyuan will be the owner) ? The OVS-DPDK removal for stx.4.0 was reviewed in the release meeting and agreed to. * stx.4.0 Bugs >> Need to be re-assigned * https://bugs.launchpad.net/starlingx/+bug/1833463 >> Yong to re-assign. Work is related to openstack-helm _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Fri Feb 7 16:42:37 2020 From: scott.little at windriver.com (Scott Little) Date: Fri, 7 Feb 2020 11:42:37 -0500 Subject: [Starlingx-discuss] [important] Build layering In-Reply-To: <830ce6d4-06ec-e409-8536-1540ba46ff3f@linux.intel.com> References: <830ce6d4-06ec-e409-8536-1540ba46ff3f@linux.intel.com> Message-ID: Mirror issues should now be resolved. Scott On 2020-01-31 4:28 p.m., Saul Wold wrote: > > There seems to be an issue with the download mirror, I attempted to do > a "distro" layer build, I started with the download mirror step and it > failed to completely download all the RPMs. These did not download > correctly: > > bash-4.2.46-31.el7.tis.4.x86_64.rpm > golang-1.12.10-3.tis.1.x86_64.rpm > golang-shared-1.12.10-3.tis.1.x86_64.rpm > python-2.7.5-76.el7.tis.4.x86_64.rpm > python-debug-2.7.5-76.el7.tis.4.x86_64.rpm > python-debuginfo-2.7.5-76.el7.tis.4.x86_64.rpm > python-devel-2.7.5-76.el7.tis.4.x86_64.rpm > > These seem to all be part of the compile layer.  When I check on the > cengn mirror, these RPMs are present in the > /mirror/starlingx/master/centos/compiler/latest_build/outputs/RPMS/std/ > directory. > > There is a note in the log about the package not matching: > http://mirror.starlingx.cengn.ca:80/mirror/centos/mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/latest_build/outputs/RPMS/std/golang-shared-1.12.10-3.tis.1.x86_64.rpm: > [Errno -1] Package does not match intended download. Suggestion: run > yum --enablerepo=CENGN_Starlingx-cengn_compiler_std_layer clean metadata > > I tried to run the --enablerpo, but that did not seem to help. > > I will work on testing another configuration. > > Thanks >   Sau! > > > > On 1/30/20 12:39 PM, Scott Little wrote: >> The build layering feature is coming soon. >> >> >> *Code reviews* have been posted ... >> >> https://review.opendev.org/#/c/700819/2 >> >> https://review.opendev.org/#/c/700821/9 >> >> https://review.opendev.org/#/c/681821/28 >> >> https://review.opendev.org/#/c/705092/ >> >> >> *D**ocumentation* can be found in the fourth review, here .... >> >> https://review.opendev.org/gitweb?p=starlingx/docs.git;a=blob;f=doc/source/developer_resources/Layered_Build.rst;h=6f945d8d33f70bd91594033fcfa6abaf6271056d;hb=2a6abc988c9a52321982015831b12819586546df >> >> >> >> *Want to try it out before it merges? * >> >> I've set up a modified manifest that pulls in the required updates .... >> >> One of ... >> >>     repo init -u https://opendev.org/starlingx/manifest.git -b >> refs/changes/04/705104/2 -m compile.xml >> >>     repo init -u https://opendev.org/starlingx/manifest.git -b >> refs/changes/04/705104/2 -m distro.xml >> >>     repo init -u https://opendev.org/starlingx/manifest.git -b >> refs/changes/04/705104/2 -m flock.xml >> >> >> followed by: >> >>     repo sync >> >> >> Scott >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Dariush.Eslimi at windriver.com Fri Feb 7 17:50:33 2020 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Fri, 7 Feb 2020 17:50:33 +0000 Subject: [Starlingx-discuss] Setting up StarlingX mirroring to GitHub In-Reply-To: References: Message-ID: 28 Repos are mirrored to GitHub, thanks to Bin for creating and cores for reviewing the commits. Dariush From: Eslimi, Dariush [mailto:Dariush.Eslimi at windriver.com] Sent: February-04-20 1:08 PM To: starlingx Subject: [Starlingx-discuss] Setting up StarlingX mirroring to GitHub Hi All, As part of effort to apply for CNCF Certified Kubernetes logo, we need to mirror our repositories to GitHub, I have created a story to track our progress, and so far we have completed one repo : ha Here is the link to StarlingX GitHub : https://github.com/starlingx Here is storyboard link : https://storyboard.openstack.org/#!/story/2007252 Bin will go through each repo to setup the mirroring job as part of zuul configuration, cores please review his commits as they get posted. You can get the list of commits using this link: https://review.opendev.org/#/q/projects:starlingx+AND++topic:github-mirror+(status:open+OR+status:merged) Bin will update the developers wiki to add instructions on what has to be done to setup mirroring for your newly created repo. Thanks, Dariush -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bin.Qian at windriver.com Fri Feb 7 19:01:44 2020 From: Bin.Qian at windriver.com (Qian, Bin) Date: Fri, 7 Feb 2020 19:01:44 +0000 Subject: [Starlingx-discuss] [docs] Update developer wiki for adding new repo Message-ID: Hello Kristal, As part of effort to apply for CNCF Certified Kubernetes logo, we need to mirror our repositories to GitHub. I've completed adding zuul job to sync all existing repos that are required to upload to GitHub. For future development, I'd like to add some notes to the StarlingX development wiki for how to create a zuul job to sync repo from opendev to GitHub. Can you provide guidance on how to make the doc changes? Thanks, Bin From Dariush.Eslimi at windriver.com Fri Feb 7 19:34:34 2020 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Fri, 7 Feb 2020 19:34:34 +0000 Subject: [Starlingx-discuss] [docs] Update developer wiki for adding new repo In-Reply-To: References: Message-ID: Just to be clear, I suggested to Bin to add a page here : https://docs.starlingx.io/developer_resources/index.html on how to do the mirroring so rest of community knows how to do it from now on. Dariush -----Original Message----- From: Qian, Bin [mailto:Bin.Qian at windriver.com] Sent: February-07-20 2:02 PM To: Dale, Kristal ; starlingx Subject: [Starlingx-discuss] [docs] Update developer wiki for adding new repo Hello Kristal, As part of effort to apply for CNCF Certified Kubernetes logo, we need to mirror our repositories to GitHub. I've completed adding zuul job to sync all existing repos that are required to upload to GitHub. For future development, I'd like to add some notes to the StarlingX development wiki for how to create a zuul job to sync repo from opendev to GitHub. Can you provide guidance on how to make the doc changes? Thanks, Bin _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Frank.Miller at windriver.com Fri Feb 7 20:16:25 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Fri, 7 Feb 2020 20:16:25 +0000 Subject: [Starlingx-discuss] ceph containerization patch review In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D8562A76F5@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D8562A76F5@CDSMSX102.ccr.corp.intel.com> Message-ID: Martin: Thanks for posting your reviews and the update on the current status for this feature. I was unable to attend the containerization meeting this week so wasn't able to have Tingjie or you give an update on the open actions for the feature. From the Jan 14 minutes [1] one of the actions is to determine "how can you have Rook do all the configuration and not have sysinv involved" For now I suggest you add an additional item to your Tasks to do list to identify a design that does not require sysinv for the configuration and instead has Rook manage the configuration. I would like to ask that we discuss further at the next containerization meeting and if possible review a proposal from yourself and Austin for this item. Frank [1] https://etherpad.openstack.org/p/stx-containerization From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Thursday, February 06, 2020 11:02 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] ceph containerization patch review Hi folks I enabled containerized ceph cluster with simplex. You can begin to review my patch. I propose to build an image and deploy a simplex system with these patch to check. https://review.opendev.org/#/c/681457/ https://review.opendev.org/#/c/687340/ https://review.opendev.org/#/c/706256/ https://review.opendev.org/#/c/699557/ https://review.opendev.org/#/c/699556/ And I know there is other story, like remove ceph as default backend storage, maybe some conflict, we can discuss together. Tash Done: 1, disable native ceph cluster in ceph.pp 2, disable ceph daemon monitoring in service manager 3, add rook-ceph helm chart to launch ceph cluster 4, add override in stx-config to generate override with starlingx system config 5, sysinv add label in provision stage, to make containerized ceph mon and ceph mgr on designed host 6, add rook-ceph-provisioner helm chart to generate storage class, secret, config and pool for stx-application 7, enabled stx-openstack with containerized ceph 8, update ceph wrapper in stx-config to set or get containerized ceph cluster All these tasks done is enabled with simplex only. Task to do: 1, enable add osd runtime, after system provisioned 2, fix know issue, if system reboot, ceph cluster launch fail 3, enable bluestore and filestore, currently there is only bluestore 4, enable multi-node and duplex 5, enable swift with containerized ceph 6, enable fm alarm for containerized ceph 7, check backup and restore for containerized ceph 8, check system upgrade or how to transit from native ceph cluster to containerized ceph cluster 9, code cleanup 10, update unit test in stx-config BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Fri Feb 7 21:38:47 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Fri, 7 Feb 2020 21:38:47 +0000 Subject: [Starlingx-discuss] stx docs input:2006711 In-Reply-To: References: Message-ID: Great - thanks Jerry! I will get the content converted to rst and we can do any needed edits via the Review. Thanks again! Kris From: Sun, Yicheng (Jerry) Sent: Friday, February 7, 2020 6:32 AM To: starlingx-discuss at lists.starlingx.io Cc: Dale, Kristal Subject: stx docs input:2006711 Hi All, Attached is the documentation changes required for the "Windows Active Directory Auth Support for K8S API" story (https://storyboard.openstack.org/#!/story/2006711) Thanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Fri Feb 7 21:49:52 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Fri, 7 Feb 2020 21:49:52 +0000 Subject: [Starlingx-discuss] [docs] Onboarding slide deck In-Reply-To: <02D23DB2-CEE6-4A05-A51A-6240B0A3C191@gmail.com> References: <02D23DB2-CEE6-4A05-A51A-6240B0A3C191@gmail.com> Message-ID: Hi Ildiko, I pulled down your review and clicked through the slide deck on my Window laptop - all looked good, I didn't see anything obviously wrong. Regarding where to add a link to the pdf from the docs page: My thought is to add it to the StarlingX Introduction page. I will create a review with my starting suggestion and add you as a reviewer. Thanks, Kris -----Original Message----- From: Ildiko Vancsa Sent: Thursday, February 6, 2020 1:20 AM To: Dale, Kristal Cc: starlingx Subject: [docs] Onboarding slide deck Hi Kris and Docs team, As discussed on the team meeting yesterday, I uploaded a powerpoint version of the onboarding slide deck to the docs repo, the review is here: https://review.opendev.org/#/c/706199/ Please let me know if it doesn’t open correctly on Windows, I don’t have the capacity to check. I also modified the file name on the website to be more generic so we can link it from the intro part of the docs without the continuous burden of updating the link: https://www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf Where do you think it would fit to link it from the docs page? Thanks, Ildikó From kristal.dale at intel.com Fri Feb 7 22:28:11 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Fri, 7 Feb 2020 22:28:11 +0000 Subject: [Starlingx-discuss] [docs] Update developer wiki for adding new repo In-Reply-To: References: Message-ID: Hi Bin, Dariush, With my understanding of the content, I agree adding it to the Developers Resources section makes sense. Bin - I was already working in the docs repo, so I just now set up an empty page in the Developer Resources section for your new content. Please feel free to add the content by contributing directly to this review: https://review.opendev.org/#/c/706629/ The documentation contributors guide is here: https://docs.starlingx.io/contributor/doc_contribute_guide.html Alternately, send the content to directly to me and I'll add it to the new page. If you have any questions, don't hesitate to contact me directly! Cheers, Kris -----Original Message----- From: Eslimi, Dariush Sent: Friday, February 7, 2020 11:35 AM To: Qian, Bin ; Dale, Kristal ; starlingx Subject: RE: [Starlingx-discuss] [docs] Update developer wiki for adding new repo Just to be clear, I suggested to Bin to add a page here : https://docs.starlingx.io/developer_resources/index.html on how to do the mirroring so rest of community knows how to do it from now on. Dariush -----Original Message----- From: Qian, Bin [mailto:Bin.Qian at windriver.com] Sent: February-07-20 2:02 PM To: Dale, Kristal ; starlingx Subject: [Starlingx-discuss] [docs] Update developer wiki for adding new repo Hello Kristal, As part of effort to apply for CNCF Certified Kubernetes logo, we need to mirror our repositories to GitHub. I've completed adding zuul job to sync all existing repos that are required to upload to GitHub. For future development, I'd like to add some notes to the StarlingX development wiki for how to create a zuul job to sync repo from opendev to GitHub. Can you provide guidance on how to make the doc changes? Thanks, Bin _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From kristal.dale at intel.com Fri Feb 7 22:38:38 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Fri, 7 Feb 2020 22:38:38 +0000 Subject: [Starlingx-discuss] Invalid password for ldapadmin user during simplex installation In-Reply-To: References: Message-ID: Hi Martin, Where did you find the link to these instructions? (https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Simplex) I wasn’t able to find a direct link from the wiki… Did you find this via search? The latest instructions (R3) for a virtual Simplex installation are on the documentation site: https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/aio_simplex.html If there is an older set of instructions floating around, we’d like to find them and correctly deprecate them to avoid confusion in the future! Thanks, Kris (STX docs team) From: Ward, Martin Sent: Friday, January 31, 2020 2:21 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Invalid password for ldapadmin user during simplex installation Good day all, I’m trying to install a Simplex server following the instructions provided in https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Simplex - The base system is CentOS 7.7. I’ve got the basic Simplex VM created, up and running, it’s when I run the Ansible scripts that it fails and logs the error: 2020-01-30T16:19:48.122 Error: 2020-01-30 16:19:48 +0000 ldapadd -D cn=ldapadmin,dc=cgcs,dc=local -w f62083c68b43Ti0* -f /etc/openldap/initial_config.ldif returned 49 instead of one of [0] 2020-01-30T16:19:48.258 Error: 2020-01-30 16:19:48 +0000 /Stage[main]/Platform::Ldap::Bootstrap/Exec[populate initial ldap configuration]/returns: change from notrun to 0 failed: ldapadd -D cn=ldapadmin,dc=cgcs,dc=local -w f62083c68b43Ti0* -f /etc/openldap/initial_config.ldif returned 49 instead of one of [0] 2020-01-30T16:21:54.301 Error: 2020-01-30 16:21:54 +0000 /Stage[main]/Platform::Drbd::Etcd::Bootstrap/Platform::Drbd::Filesystem[drbd-etcd]/Drbd::Resource[drbd-etcd]/Drbd::Resource::Enable[drbd-etcd]/Drbd::Resource::Up[drbd-etcd]/Mount[/opt/etcd]: Could not evaluate: Execution of '/usr/bin/mount /opt/etcd' returned 32: mount: /dev/drbd7 is write-protected, mounting read-only When I run the ldapadd command myself it fails with: ldap_bind: Invalid credentials (49) I’ve not configured any ldap password anywhere so I guess that the ldapadmin password is auto-generated, but the fact that it’s not working is cause for concern. I’ve looked through the log file for any clues but everything prior to the above command has worked fine no errors or warnings. I am at a loss, any pointers would be appreciated. |\\/|artin -- Martin Ward Technical Support Engineer.Senior Group: Carrier Support Ext: 29745 -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Fri Feb 7 23:40:32 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Fri, 7 Feb 2020 23:40:32 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200207 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-FEBRUARY-07 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhaolongqian456 at 163.com Sat Feb 8 01:31:20 2020 From: zhaolongqian456 at 163.com (Longqian Zhao) Date: Sat, 8 Feb 2020 09:31:20 +0800 (CST) Subject: [Starlingx-discuss] The data interface eth1000 cannot be modified when I configure compute-0 Message-ID: <19f153b3.1c3d.170226c3204.Coremail.zhaolongqian456@163.com> Hi , I According to https://docs.starlingx.io/deploy_install_guides/r1_release/controller_storage.html#id8 , the data interface eth1000 cannot be modified. Following is the detail informations about my issue. Could you please help me? Thanks. Brief Description ----------------- My Environment: I install StarlingX in Virtual Environment. StarlingX version: 2018/10 stx-tools version: 2018/10 Steps: 1. Install controller-0 succesfully. 2. Install compute-0. 3. source /etc/nova/openrc. 4. system host-port-list compute-0 +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ | 2b735378-dd09-43b3-929f-5ca110a35001 | eth0 | ethernet | 0000:02:01.0 | 0 | -1 | True | Virtio network device | | 45c95b31-23ec-4eb4-aefb-eb22133a60a9 | eth1 | ethernet | 0000:02:02.0 | 0 | -1 | True | Virtio network device | | 51f58dac-3f6e-486d-bd67-300b15942b80 | eth2 | ethernet | 0000:02:03.0 | 0 | -1 | True | Virtio network device | | 62b4a45b-b167-456b-8b31-41b21d45b0da | eth3 | ethernet | 0000:02:04.0 | 0 | -1 | True | Virtio network device | +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ 5. system host-if-modify -p providernet-a -c data compute-0 eth1000 (The following is the returned information:) Interface not found: host compute-0 if eth1000 Issues: ----------------- 1. I did not find the data interface after executing the command: system host-if-list compute-0 +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | provider networks | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ | b2642ea1-cf58-4bc7-92ab-bbfb374a04c3 | mgmt0 | platform | ethernet | None | [u'eth1'] | [] | [] | MTU=1500 | None | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ 2. I do not know how to use command "system host-if-add" to add data interface. Best regards with you, Longqian -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Sat Feb 8 01:34:23 2020 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 7 Feb 2020 17:34:23 -0800 Subject: [Starlingx-discuss] The data interface eth1000 cannot be modified when I configure compute-0 In-Reply-To: <19f153b3.1c3d.170226c3204.Coremail.zhaolongqian456@163.com> References: <19f153b3.1c3d.170226c3204.Coremail.zhaolongqian456@163.com> Message-ID: <1d300f12-74c7-bb17-772a-747d0bed6676@linux.intel.com> I strongly urge you to look at the StarlingX 3.0 release. The 2018/10 or 1.0 release is old and there have been many improvements. Sau! On 2/7/20 5:31 PM, Longqian Zhao wrote: > Hi , > > I According to > https://docs.starlingx.io/deploy_install_guides/r1_release/controller_storage.html#id8 > , the data interface eth1000 cannot be modified. Following is the detail > informations about my issue. Could you please help me? Thanks. > > Brief Description > > ----------------- > > My Environment: > > I install StarlingX in Virtual Environment. > > StarlingX version: 2018/10 > > stx-tools version: 2018/10 > > Steps: > > 1. Install controller-0 succesfully. > > 2. Install compute-0. > > 3. source /etc/nova/openrc. > > 4. system host-port-list compute-0 > > +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ > > | uuid                                 | name | type     | pci address > | device | processor | accelerated | device type           | > > +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ > > | 2b735378-dd09-43b3-929f-5ca110a35001 | eth0 | ethernet | 0000:02:01.0 > | 0      | -1        | True        | Virtio network device | > > | 45c95b31-23ec-4eb4-aefb-eb22133a60a9 | eth1 | ethernet | 0000:02:02.0 > | 0      | -1        | True        | Virtio network device | > > | 51f58dac-3f6e-486d-bd67-300b15942b80 | eth2 | ethernet | 0000:02:03.0 > | 0      | -1        | True        | Virtio network device | > > | 62b4a45b-b167-456b-8b31-41b21d45b0da | eth3 | ethernet | 0000:02:04.0 > | 0      | -1        | True        | Virtio network device | > > +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ > > 5. system host-if-modify -p providernet-a -c data compute-0 eth1000 > > (The following is the returned information:) > > Interface not found: host compute-0 if eth1000 > > Issues: > > ----------------- > > 1. I did not find the data interface after executing the command: system > host-if-list compute-0 > > +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ > > | uuid                                 | name  | class    | type     | > vlan id | ports     | uses i/f | used by i/f | attributes | provider > networks | > > +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ > > | b2642ea1-cf58-4bc7-92ab-bbfb374a04c3 | mgmt0 | platform | ethernet | > None    | [u'eth1'] | []       | []          | MTU=1500   | None >       | > > +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ > > 2. I do not know how to use command "system host-if-add" to add data > interface. > > /Best regards with you,/ > > /Longqian/ > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From shuicheng.lin at intel.com Sat Feb 8 03:16:37 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Sat, 8 Feb 2020 03:16:37 +0000 Subject: [Starlingx-discuss] The data interface eth1000 cannot be modified when I configure compute-0 In-Reply-To: <19f153b3.1c3d.170226c3204.Coremail.zhaolongqian456@163.com> References: <19f153b3.1c3d.170226c3204.Coremail.zhaolongqian456@163.com> Message-ID: <9700A18779F35F49AF027300A49E7C7660929447@SHSMSX105.ccr.corp.intel.com> Hi, As Saul said, it is highly recommended you have a try with 3.0 Release, instead of 1.0 Release, which is too old and not maintained now. For your environment, with "host-port-list", there are eth0 ~ eth3, no eth1000. So you should use eth2/eth3, instead of eth1000 as data interface. Best Regards Shuicheng From: Longqian Zhao Sent: Saturday, February 8, 2020 9:31 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] The data interface eth1000 cannot be modified when I configure compute-0 Hi , I According to https://docs.starlingx.io/deploy_install_guides/r1_release/controller_storage.html#id8 , the data interface eth1000 cannot be modified. Following is the detail informations about my issue. Could you please help me? Thanks. Brief Description ----------------- My Environment: I install StarlingX in Virtual Environment. StarlingX version: 2018/10 stx-tools version: 2018/10 Steps: 1. Install controller-0 succesfully. 2. Install compute-0. 3. source /etc/nova/openrc. 4. system host-port-list compute-0 +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ | 2b735378-dd09-43b3-929f-5ca110a35001 | eth0 | ethernet | 0000:02:01.0 | 0 | -1 | True | Virtio network device | | 45c95b31-23ec-4eb4-aefb-eb22133a60a9 | eth1 | ethernet | 0000:02:02.0 | 0 | -1 | True | Virtio network device | | 51f58dac-3f6e-486d-bd67-300b15942b80 | eth2 | ethernet | 0000:02:03.0 | 0 | -1 | True | Virtio network device | | 62b4a45b-b167-456b-8b31-41b21d45b0da | eth3 | ethernet | 0000:02:04.0 | 0 | -1 | True | Virtio network device | +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ 5. system host-if-modify -p providernet-a -c data compute-0 eth1000 (The following is the returned information:) Interface not found: host compute-0 if eth1000 Issues: ----------------- 1. I did not find the data interface after executing the command: system host-if-list compute-0 +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | provider networks | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ | b2642ea1-cf58-4bc7-92ab-bbfb374a04c3 | mgmt0 | platform | ethernet | None | [u'eth1'] | [] | [] | MTU=1500 | None | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ 2. I do not know how to use command "system host-if-add" to add data interface. Best regards with you, Longqian -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhaolongqian456 at 163.com Sat Feb 8 04:19:37 2020 From: zhaolongqian456 at 163.com (Longqian Zhao) Date: Sat, 8 Feb 2020 12:19:37 +0800 (CST) Subject: [Starlingx-discuss] The data interface eth1000 cannot be modified when I configure compute-0 In-Reply-To: <9700A18779F35F49AF027300A49E7C7660929447@SHSMSX105.ccr.corp.intel.com> References: <19f153b3.1c3d.170226c3204.Coremail.zhaolongqian456@163.com> <9700A18779F35F49AF027300A49E7C7660929447@SHSMSX105.ccr.corp.intel.com> Message-ID: Hi ShuiCheng, I so glad to receive your email again. I solve my trouble by using eth2 instead of eth1000 and having a try with 3.0 Release,instead of 1.0 Relelase. Lantern wish you happiness,good health! LongQian At 2020-02-08 11:16:37, "Lin, Shuicheng" wrote: Hi, As Saul said, it is highly recommended you have a try with 3.0 Release, instead of 1.0 Release, which is too old and not maintained now. For your environment, with “host-port-list”, there are eth0 ~ eth3, no eth1000. So you should use eth2/eth3, instead of eth1000 as data interface. Best Regards Shuicheng From: Longqian Zhao Sent: Saturday, February 8, 2020 9:31 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] The data interface eth1000 cannot be modified when I configure compute-0 Hi , I According to https://docs.starlingx.io/deploy_install_guides/r1_release/controller_storage.html#id8 , the data interface eth1000 cannot be modified. Following is the detail informations about my issue. Could you please help me? Thanks. Brief Description ----------------- My Environment: I install StarlingX in Virtual Environment. StarlingX version: 2018/10 stx-tools version: 2018/10 Steps: 1. Install controller-0 succesfully. 2. Install compute-0. 3. source /etc/nova/openrc. 4. system host-port-list compute-0 +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ | 2b735378-dd09-43b3-929f-5ca110a35001 | eth0 | ethernet | 0000:02:01.0 | 0 | -1 | True | Virtio network device | | 45c95b31-23ec-4eb4-aefb-eb22133a60a9 | eth1 | ethernet | 0000:02:02.0 | 0 | -1 | True | Virtio network device | | 51f58dac-3f6e-486d-bd67-300b15942b80 | eth2 | ethernet | 0000:02:03.0 | 0 | -1 | True | Virtio network device | | 62b4a45b-b167-456b-8b31-41b21d45b0da | eth3 | ethernet | 0000:02:04.0 | 0 | -1 | True | Virtio network device | +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ 5. system host-if-modify -p providernet-a -c data compute-0 eth1000 (The following is the returned information:) Interface not found: host compute-0 if eth1000 Issues: ----------------- 1. I did not find the data interface after executing the command: system host-if-list compute-0 +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | provider networks | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ | b2642ea1-cf58-4bc7-92ab-bbfb374a04c3 | mgmt0 | platform | ethernet | None | [u'eth1'] | [] | [] | MTU=1500 | None | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ 2. I do not know how to use command "system host-if-add" to add data interface. Best regards with you, Longqian -------------- next part -------------- An HTML attachment was scrubbed... URL: From ji at sibyl.li Sat Feb 8 18:00:17 2020 From: ji at sibyl.li (Austin Gillmann) Date: Sat, 8 Feb 2020 12:00:17 -0600 Subject: [Starlingx-discuss] Openstack reapply failing Message-ID: Hi all, My earlier email was never replied to so I will try to re-word it: I recently deployed StarlingX 3.0 under a dedicated storage standard cluster (the storage servers running on dell r740xd's with HDD's and compute/controllers running on HP bl460c G8 blades with 2 SSD's) the stx-openstack application applies successfully on the first try, but will abort upon reapply for a config change or such. The errors armada puts out is details = "release osh-openstack-neutron failed: poddisruptionbudgets.policy "neutron-server" already exists" and "getting deployed release "osh-openstack-neutron": release: "osh-openstack-neutron" not found" Everything else in logs look normal to me, but let me know if you need any files attached! If anyone has any idea how to get past this please let me know! Best wishes, Austin Gillmann From hu.tianhao at 99cloud.net Mon Feb 10 08:29:30 2020 From: hu.tianhao at 99cloud.net (=?UTF-8?B?6IOh5aSp5piK?=) Date: Mon, 10 Feb 2020 16:29:30 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?_Drdb_fails_for_AIO_Simplex_after_u?= =?utf-8?q?nlock_controller-0?= Message-ID: Hi all, When I install AIO Simplex following this guide(https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/aio_simplex_install_kubernetes.html), drdb fails after unlock controller-0. And following is part of the log(/var/log/puppet/latest/puppet.log): 2020-01-16T09:35:07.689 Debug: 2020-01-16 09:35:07 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-prepare-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/unless: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5707: UserWarning: 2020-01-16T09:35:07.732 Debug: 2020-01-16 09:35:07 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-prepare-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/unless: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5739: UserWarning: 2020-01-16T09:36:15.967 Notice: 2020-01-16 09:36:15 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-prepare-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/returns: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5707: UserWarning: 2020-01-16T09:36:16.507 Notice: 2020-01-16 09:36:16 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-prepare-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/returns: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5739: UserWarning: 2020-01-16T09:36:20.485 Notice: 2020-01-16 09:36:20 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-activate-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/returns: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5707: UserWarning: 2020-01-16T09:36:20.568 Notice: 2020-01-16 09:36:20 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-activate-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/returns: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5739: UserWarning: 2020-01-16T09:36:34.615 Error: 2020-01-16 09:36:34 +0000 yes yes | drbdadm create-md drbd-pgsql -W--peer-max-bio-size=128k returned 40 instead of one of [0] 2020-01-16T09:36:34.843 Error: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Drbd::Pgsql/Platform::Drbd::Filesystem[drbd-pgsql]/Drbd::Resource[drbd-pgsql]/Drbd::Resource::Enable[drbd-pgsql]/Drbd::Resource::Up[drbd-pgsql]/Exec[initialize DRBD metadata for drbd-pgsql]/returns: change from notrun to 0 failed: yes yes | drbdadm create-md drbd-pgsql -W--peer-max-bio-size=128k returned 40 instead of one of [0] 2020-01-16T09:36:34.852 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Drbd::Pgsql/Platform::Drbd::Filesystem[drbd-pgsql]/Drbd::Resource[drbd-pgsql]/Drbd::Resource::Enable[drbd-pgsql]/Drbd::Resource::Up[drbd-pgsql]/Exec[enable DRBD resource drbd-pgsql]: Skipping because of failed dependencies 2020-01-16T09:36:35.052 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Drbd::Service/Service[drbd]: Skipping because of failed dependencies 2020-01-16T09:36:35.094 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Anchors/Anchor[platform::services]: Skipping because of failed dependencies 2020-01-16T09:36:35.122 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Helm/File[/opt/platform/helm_charts]: Skipping because of failed dependencies 2020-01-16T09:36:35.135 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Helm/Exec[restart lighttpd for helm]: Skipping because of failed dependencies 2020-01-16T09:36:35.164 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Helm::Repositories/Platform::Helm::Repository[starlingx]/File[/www/pages/helm_charts/starlingx]: Skipping because of failed dependencies It seems like that drdb config fails. And I run "drbdadm create-md drbd-pgsql -W--peer-max-bio-size=128k", I get the following result: Move internal meta data from last-known position? [need to type 'yes' to confirm] yes md_offset 21474832384 al_offset 0 bm_offset 0 Found ext3 filesystem 20971520 kB data area apparently used 0 kB left usable by current configuration Device size would be truncated, which would corrupt data and result in 'access beyond end of device' errors. You need to either * use external meta data (recommended) * shrink that filesystem first * zero out the device (destroy the filesystem) Operation refused. Command 'drbdmeta 0 v08 /dev/cgts-vg/pgsql-lv internal create-md --peer-max-bio-size=128k' terminated with exit code 40 I'd like to know that how to reconfig drdb or did I set some config wrong? Thanks, Tianhao -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Feb 10 15:46:56 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 10 Feb 2020 15:46:56 +0000 Subject: [Starlingx-discuss] ceph containerization patch review In-Reply-To: References: <56829C2A36C2E542B0CCB9854828E4D8562A76F5@CDSMSX102.ccr.corp.intel.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D8562A7E32@CDSMSX102.ccr.corp.intel.com> Hi Frank: As synced with Tingjie, this is my understanding for Rook manage the configuration instead of sysinv. 1, Remove ceph config and status query from sysinv 2, create another tool, like rook-client to launch and provision ceph cluster 3, one helm plugin like rbd-provision, which depends on newly created tool BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank Sent: Saturday, February 8, 2020 4:16 AM To: Chen, Haochuan Z ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: ceph containerization patch review Martin: Thanks for posting your reviews and the update on the current status for this feature. I was unable to attend the containerization meeting this week so wasn't able to have Tingjie or you give an update on the open actions for the feature. From the Jan 14 minutes [1] one of the actions is to determine "how can you have Rook do all the configuration and not have sysinv involved" For now I suggest you add an additional item to your Tasks to do list to identify a design that does not require sysinv for the configuration and instead has Rook manage the configuration. I would like to ask that we discuss further at the next containerization meeting and if possible review a proposal from yourself and Austin for this item. Frank [1] https://etherpad.openstack.org/p/stx-containerization From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Thursday, February 06, 2020 11:02 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] ceph containerization patch review Hi folks I enabled containerized ceph cluster with simplex. You can begin to review my patch. I propose to build an image and deploy a simplex system with these patch to check. https://review.opendev.org/#/c/681457/ https://review.opendev.org/#/c/687340/ https://review.opendev.org/#/c/706256/ https://review.opendev.org/#/c/699557/ https://review.opendev.org/#/c/699556/ And I know there is other story, like remove ceph as default backend storage, maybe some conflict, we can discuss together. Tash Done: 1, disable native ceph cluster in ceph.pp 2, disable ceph daemon monitoring in service manager 3, add rook-ceph helm chart to launch ceph cluster 4, add override in stx-config to generate override with starlingx system config 5, sysinv add label in provision stage, to make containerized ceph mon and ceph mgr on designed host 6, add rook-ceph-provisioner helm chart to generate storage class, secret, config and pool for stx-application 7, enabled stx-openstack with containerized ceph 8, update ceph wrapper in stx-config to set or get containerized ceph cluster All these tasks done is enabled with simplex only. Task to do: 1, enable add osd runtime, after system provisioned 2, fix know issue, if system reboot, ceph cluster launch fail 3, enable bluestore and filestore, currently there is only bluestore 4, enable multi-node and duplex 5, enable swift with containerized ceph 6, enable fm alarm for containerized ceph 7, check backup and restore for containerized ceph 8, check system upgrade or how to transit from native ceph cluster to containerized ceph cluster 9, code cleanup 10, update unit test in stx-config BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Mon Feb 10 15:59:53 2020 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Mon, 10 Feb 2020 15:59:53 +0000 Subject: [Starlingx-discuss] ceph containerization patch review In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D8562A7E32@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D8562A76F5@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A7E32@CDSMSX102.ccr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EC28D2CAA@ALA-MBD.corp.ad.wrs.com> Thanks. See inline Brent From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Monday, February 10, 2020 10:47 AM To: Miller, Frank ; 'starlingx-discuss at lists.starlingx.io' Cc: Chen, Tingjie ; Sun, Austin ; Qi, Mingyuan Subject: Re: [Starlingx-discuss] ceph containerization patch review Hi Frank: As synced with Tingjie, this is my understanding for Rook manage the configuration instead of sysinv. 1, Remove ceph config and status query from sysinv [BR] So this would be done in new reviews, current code posted is still coupled with sysinv ? 2, create another tool, like rook-client to launch and provision ceph cluster [BR] Wouldn't this just be chart overrides ? Why is a tool required ? 3, one helm plugin like rbd-provision, which depends on newly created tool BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Saturday, February 8, 2020 4:16 AM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: ceph containerization patch review Martin: Thanks for posting your reviews and the update on the current status for this feature. I was unable to attend the containerization meeting this week so wasn't able to have Tingjie or you give an update on the open actions for the feature. From the Jan 14 minutes [1] one of the actions is to determine "how can you have Rook do all the configuration and not have sysinv involved" For now I suggest you add an additional item to your Tasks to do list to identify a design that does not require sysinv for the configuration and instead has Rook manage the configuration. I would like to ask that we discuss further at the next containerization meeting and if possible review a proposal from yourself and Austin for this item. Frank [1] https://etherpad.openstack.org/p/stx-containerization From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Thursday, February 06, 2020 11:02 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] ceph containerization patch review Hi folks I enabled containerized ceph cluster with simplex. You can begin to review my patch. I propose to build an image and deploy a simplex system with these patch to check. https://review.opendev.org/#/c/681457/ https://review.opendev.org/#/c/687340/ https://review.opendev.org/#/c/706256/ https://review.opendev.org/#/c/699557/ https://review.opendev.org/#/c/699556/ And I know there is other story, like remove ceph as default backend storage, maybe some conflict, we can discuss together. Tash Done: 1, disable native ceph cluster in ceph.pp 2, disable ceph daemon monitoring in service manager 3, add rook-ceph helm chart to launch ceph cluster 4, add override in stx-config to generate override with starlingx system config 5, sysinv add label in provision stage, to make containerized ceph mon and ceph mgr on designed host 6, add rook-ceph-provisioner helm chart to generate storage class, secret, config and pool for stx-application 7, enabled stx-openstack with containerized ceph 8, update ceph wrapper in stx-config to set or get containerized ceph cluster All these tasks done is enabled with simplex only. Task to do: 1, enable add osd runtime, after system provisioned 2, fix know issue, if system reboot, ceph cluster launch fail 3, enable bluestore and filestore, currently there is only bluestore 4, enable multi-node and duplex 5, enable swift with containerized ceph 6, enable fm alarm for containerized ceph 7, check backup and restore for containerized ceph 8, check system upgrade or how to transit from native ceph cluster to containerized ceph cluster 9, code cleanup 10, update unit test in stx-config BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Mon Feb 10 17:08:24 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 10 Feb 2020 17:08:24 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Feb 7/2020 Message-ID: <151EE31B9FCCA54397A757BC674650F0C1670B69@ALA-MBD.corp.ad.wrs.com> Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - February 7 2020 stx.4.0 - CentOS 8 - Discussions are in progress to limit the scope of the stx.4.0 feature to de-risk the delivery and prioritize the key items - Brent sent a proposal to the distro.other sub-project which will be reviewed in the next sub-project meeting - If resources are freed up from CentOS8, there is a possibility they can contribute to other key initiatives - From Saul: - Starting to create the CentOS8 mirror on CENGN as some of the older packages are being updated already - Also need to keep in mind the request to move to an even newer kernel (4.19) to support TSN in containers and be mindful of needing to support newer kernels - Need to have CentOS 8 as a base first before getting to this - Layered Build - Still finding issues when attempting to build using layered build on CENGN infrastructure. - Scott is working on a solution and expects to have a review shortly. - Close to getting the code merged by early next week. - Side Note: This will have an impact on the CentOS8 feature branch - Next Milestone: Milestone-2 is planned for March 23 - Criteria: https://wiki.openstack.org/wiki/StarlingX/Release_Plan#Release_Milestones - Spec freeze; no new specs accepted for the release. The focus is on closing current specs - Feature plans defined and feature development well underway - Release test plan defined - including test automation deliverables - stx mid-cycle meeting is on March 3-4 - Need to share a release status during the meeting - Would like to review release pain points From Ghada.Khalil at windriver.com Mon Feb 10 17:10:30 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 10 Feb 2020 17:10:30 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 02/06 In-Reply-To: <76647BD697F40748B1FA4F56DA02AA0B4D687A02@SHSMSX104.ccr.corp.intel.com> References: <76647BD697F40748B1FA4F56DA02AA0B4D687A02@SHSMSX104.ccr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0C1670B77@ALA-MBD.corp.ad.wrs.com> For all interested in the StarlingX networking meeting, I will be chairing this meeting until a new PL is elected. Invite will be sent to the mailing list shortly. I would also like to take this opportunity to thank Huifeng, Forrest and their team for their contributions to StarlingX networking. Regards, Ghada From: Le, Huifeng [mailto:huifeng.le at intel.com] Sent: Thursday, February 06, 2020 9:56 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 02/06 Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Team Meeting Agenda/Notes - Feb 06/2020 * stx3.0 bugs: * https://bugs.launchpad.net/starlingx/+bug/1821026: Containers: Resolving hostname fails within nova containers leading to config_drive VM migration failures * Penging on ipv6 test, Zhipeng help to check * stx2.0 bugs: * https://bugs.launchpad.net/starlingx/+bug/1849655 StarlingX R2 duplex: VM not getting IP assigned to the vlan network when re-spawned on controller-0 after shutting down controller-1 * Wang, Yi help to check * stx 4.0 features: * TSN support in Kata: Shuicheng will take this over as the prime * Containerize OVS-DPDK: (from release meeting notes: consider this out of stx.4.0, Mingyuan will be the owner) ? The OVS-DPDK removal for stx.4.0 was reviewed in the release meeting and agreed to. * stx.4.0 Bugs >> Need to be re-assigned * https://bugs.launchpad.net/starlingx/+bug/1833463 >> Yong to re-assign. Work is related to openstack-helm _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Mon Feb 10 17:20:31 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 10 Feb 2020 17:20:31 +0000 Subject: [Starlingx-discuss] StarlingX Networking Sub-Project Meeting (bi-weekly) Message-ID: <151EE31B9FCCA54397A757BC674650F0C1670BA6@ALA-MBD.corp.ad.wrs.com> Bi-weekly on Thursday 0615 PT / 0915 ET Zoom Link: https://zoom.us/j/342730236 Meeting agenda/minutes: https://etherpad.openstack.org/p/stx-networking Networking team wiki: https://wiki.openstack.org/wiki/StarlingX/Networking -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1835 bytes Desc: not available URL: From Dariush.Eslimi at windriver.com Mon Feb 10 17:59:52 2020 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Mon, 10 Feb 2020 17:59:52 +0000 Subject: [Starlingx-discuss] StarlingX Config/DC/Flock 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 * 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: 2413 bytes Desc: not available URL: From maria.g.perez.ibarra at intel.com Tue Feb 11 00:11:44 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 11 Feb 2020 00:11:44 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200210 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-FEBRUARY-10 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Tue Feb 11 00:55:23 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 10 Feb 2020 18:55:23 -0600 Subject: [Starlingx-discuss] Interim PL elections - nomination period is now open Message-ID: <581F3235-92B6-4E23-AF78-F3E30A7BE1CB@gmail.com> Hi StarlingX Community, Nominations for the interim PL positions are now open and will remain open until __February 17, 2020 2100 UTC__. The project teams looking for new PLs are the following: * Docs * MultiOS * Networking * Test All nominations must be submitted as a text file to the starlingx/election repository as explained on the election website[1]. Please note that the name of the file should match the email address in your Gerrit configuration. Candidates for the Project Lead Positions: Any contributing community member who is an individual member of the Foundation can propose their candidacy for the project PL seat. The election will be held from February 10, 2020 2100 UTC through to February 24, 2020 2100 UTC. The electorate of the PL election are the community members that are contributors for the given official team[2] over the 12-month timeframe February 9, 2019 to February 9, 2020, as well as the contributors who are acknowledged by the TSC. Please see the website[3] for additional details about this election. Please find below the timeline: PL nomination starts @ February 10, 2020 2100 UTC PL nomination ends @ February 17, 2020 2100 UTC PL election starts @ February 17, 2020 2100 UTC PL election ends @ February 24, 2020 2100 UTC If you have any questions please be sure to either ask them on the mailing list or to the elections officials[4]. Thank you, [1] https://docs.starlingx.io/election/#how-to-submit-a-candidacy [2] https://docs.starlingx.io/governance/reference/tsc/projects/index.html [3] https://docs.starlingx.io/election/ [4] https://docs.starlingx.io/election/#election-officials From build.starlingx at gmail.com Tue Feb 11 05:55:43 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 11 Feb 2020 00:55:43 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 158 - Failure! Message-ID: <1388793683.718.1581400544835.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 158 Status: Failure Timestamp: 20200211T035124Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200211T000002Z/logs -------------------------------------------------------------------------------- Parameters HOST_PORT: 80 MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200211T000002Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root BASE_VERSION: master-stable-20200211T000002Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200211T000002Z/logs REGISTRY_USERID: slittlewrs HOST: build.starlingx.cengn.ca LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200211T000002Z/logs PUBLISH_TIMESTAMP: 20200211T000002Z FLOCK_VERSION: master-centos-stable-20200211T000002Z PREFIX: master TIMESTAMP: 20200211T000002Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20200211T000002Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Tue Feb 11 05:55:49 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 11 Feb 2020 00:55:49 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 165 - Failure! Message-ID: <878451779.721.1581400550221.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 165 Status: Failure Timestamp: 20200211T033428Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200211T000002Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200211T000002Z 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/20200211T000002Z/logs MASTER_BUILD_NUMBER: 415 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200211T000002Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos PUBLISH_TIMESTAMP: 20200211T000002Z DOCKER_BUILD_ID: jenkins-master-20200211T000002Z-builder TIMESTAMP: 20200211T000002Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/20200211T000002Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20200211T000002Z/outputs From build.starlingx at gmail.com Tue Feb 11 05:55:52 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 11 Feb 2020 00:55:52 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 415 - Failure! Message-ID: <639352356.724.1581400553576.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 415 Status: Failure Timestamp: 20200211T000002Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200211T000002Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false From austin.sun at intel.com Tue Feb 11 09:02:51 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 11 Feb 2020 09:02:51 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 2/12/2020 Message-ID: Hi All: Agenda for 2/12 meeting: - Ceph containerization status and comments address (Martin) - Pbr update ( JITStack-Wesley) build-time test : http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007676.html - CentOS8 update ( Austin/Shuicheng) Strategy discuss work item update kernel-rt kubeadm (kube-proxy) issue update drbd8 and puppet 4.8 others Opens - Vista Creek (FPGA card) support -Open If have any other topic, feel free to add to https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From yong.hu at intel.com Tue Feb 11 09:15:15 2020 From: yong.hu at intel.com (Yong Hu) Date: Tue, 11 Feb 2020 17:15:15 +0800 Subject: [Starlingx-discuss] Agenda: distro.openstack bi-weekly project meeting on WW07 Message-ID: This is the agenda for the meeting at tonight. 02/11/2020 meeting: 1. Review a PR [0] for Stx.2.0 CVE fix on stx-nava staging. @Shuicheng to update the latest status. 2. Review OpenStack Service Upgrade from "Train" to "Ussuri", for stx.4.0. @Kunpeng and @Chant from 99Cloud 3. Bug status review[1] 4. Open [1] OPEN LPs on distro.openstack: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack regards, Yong From mward at akamai.com Tue Feb 11 12:14:15 2020 From: mward at akamai.com (Ward, Martin) Date: Tue, 11 Feb 2020 12:14:15 +0000 Subject: [Starlingx-discuss] Invalid password for ldapadmin user during simplex installation In-Reply-To: References: Message-ID: Hi Kris, I searched Google using: starlingx simplex installation That link came up as the first hit, in fact the top two hits are in the wiki.openstack.org site. Thanks for the link, I will use that one and see how I get on. |\/|artin From: "Dale, Kristal" Date: Friday, 7 February 2020 at 22:38 To: Martin Ward , "starlingx-discuss at lists.starlingx.io" Subject: RE: [Starlingx-discuss] Invalid password for ldapadmin user during simplex installation Hi Martin, Where did you find the link to these instructions? (https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Simplex) I wasn’t able to find a direct link from the wiki… Did you find this via search? The latest instructions (R3) for a virtual Simplex installation are on the documentation site: https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/aio_simplex.html If there is an older set of instructions floating around, we’d like to find them and correctly deprecate them to avoid confusion in the future! Thanks, Kris (STX docs team) From: Ward, Martin Sent: Friday, January 31, 2020 2:21 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Invalid password for ldapadmin user during simplex installation Good day all, I’m trying to install a Simplex server following the instructions provided in https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Simplex - The base system is CentOS 7.7. I’ve got the basic Simplex VM created, up and running, it’s when I run the Ansible scripts that it fails and logs the error: 2020-01-30T16:19:48.122 Error: 2020-01-30 16:19:48 +0000 ldapadd -D cn=ldapadmin,dc=cgcs,dc=local -w f62083c68b43Ti0* -f /etc/openldap/initial_config.ldif returned 49 instead of one of [0] 2020-01-30T16:19:48.258 Error: 2020-01-30 16:19:48 +0000 /Stage[main]/Platform::Ldap::Bootstrap/Exec[populate initial ldap configuration]/returns: change from notrun to 0 failed: ldapadd -D cn=ldapadmin,dc=cgcs,dc=local -w f62083c68b43Ti0* -f /etc/openldap/initial_config.ldif returned 49 instead of one of [0] 2020-01-30T16:21:54.301 Error: 2020-01-30 16:21:54 +0000 /Stage[main]/Platform::Drbd::Etcd::Bootstrap/Platform::Drbd::Filesystem[drbd-etcd]/Drbd::Resource[drbd-etcd]/Drbd::Resource::Enable[drbd-etcd]/Drbd::Resource::Up[drbd-etcd]/Mount[/opt/etcd]: Could not evaluate: Execution of '/usr/bin/mount /opt/etcd' returned 32: mount: /dev/drbd7 is write-protected, mounting read-only When I run the ldapadd command myself it fails with: ldap_bind: Invalid credentials (49) I’ve not configured any ldap password anywhere so I guess that the ldapadmin password is auto-generated, but the fact that it’s not working is cause for concern. I’ve looked through the log file for any clues but everything prior to the above command has worked fine no errors or warnings. I am at a loss, any pointers would be appreciated. |\\/|artin -- Martin Ward Technical Support Engineer.Senior Group: Carrier Support Ext: 29745 -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Feb 11 16:26:36 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 11 Feb 2020 11:26:36 -0500 Subject: [Starlingx-discuss] repo command stopped working Message-ID: It looks like they pushed repo version 2 into their stable branch last night. You'll likely pick it up with your next 'repo init' or 'repo sync'. It demands git 2.10.2 or better, which isn't available on Centos 7. My initial workaround is ... for folks that are hit by this ... is to revert to repo version 1.  I don't yet see a way to force repo 1 to be used from command line, so we must let the first call fail .... repo init ....    # command fails cd .repo/repo git checkout repo-1 cd - repo init ....    # command passes Hopefully we can work out a better solution... Scott From scott.little at windriver.com Tue Feb 11 16:50:48 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 11 Feb 2020 11:50:48 -0500 Subject: [Starlingx-discuss] repo command stopped working In-Reply-To: References: Message-ID: I've found that there is a poorly documented command line option. repo init --repo-branch=repo-1 ... On 2020-02-11 11:26 a.m., Scott Little wrote: > It looks like they pushed repo version 2 into their stable branch last > night. You'll likely pick it up with your next 'repo init' or 'repo > sync'. It demands git 2.10.2 or better, which isn't available on > Centos 7. > > My initial workaround is ... for folks that are hit by this ... is to > revert to repo version 1.  I don't yet see a way to force repo 1 to be > used from command line, so we must let the first call fail .... > > > repo init ....    # command fails > > cd .repo/repo > > git checkout repo-1 > > cd - > > repo init ....    # command passes > > > Hopefully we can work out a better solution... > > Scott > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From kristal.dale at intel.com Tue Feb 11 17:34:34 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Tue, 11 Feb 2020 17:34:34 +0000 Subject: [Starlingx-discuss] Invalid password for ldapadmin user during simplex installation In-Reply-To: References: Message-ID: Thanks for the info Martin! I will add deprecating the old wiki pages found in search to the maintenance task list. Cheers, Kris From: Ward, Martin Sent: Tuesday, February 11, 2020 4:14 AM To: Dale, Kristal ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Invalid password for ldapadmin user during simplex installation Hi Kris, I searched Google using: starlingx simplex installation That link came up as the first hit, in fact the top two hits are in the wiki.openstack.org site. Thanks for the link, I will use that one and see how I get on. |\/|artin From: "Dale, Kristal" > Date: Friday, 7 February 2020 at 22:38 To: Martin Ward >, "starlingx-discuss at lists.starlingx.io" > Subject: RE: [Starlingx-discuss] Invalid password for ldapadmin user during simplex installation Hi Martin, Where did you find the link to these instructions? (https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Simplex) I wasn’t able to find a direct link from the wiki… Did you find this via search? The latest instructions (R3) for a virtual Simplex installation are on the documentation site: https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/aio_simplex.html If there is an older set of instructions floating around, we’d like to find them and correctly deprecate them to avoid confusion in the future! Thanks, Kris (STX docs team) From: Ward, Martin > Sent: Friday, January 31, 2020 2:21 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Invalid password for ldapadmin user during simplex installation Good day all, I’m trying to install a Simplex server following the instructions provided in https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Simplex - The base system is CentOS 7.7. I’ve got the basic Simplex VM created, up and running, it’s when I run the Ansible scripts that it fails and logs the error: 2020-01-30T16:19:48.122 Error: 2020-01-30 16:19:48 +0000 ldapadd -D cn=ldapadmin,dc=cgcs,dc=local -w f62083c68b43Ti0* -f /etc/openldap/initial_config.ldif returned 49 instead of one of [0] 2020-01-30T16:19:48.258 Error: 2020-01-30 16:19:48 +0000 /Stage[main]/Platform::Ldap::Bootstrap/Exec[populate initial ldap configuration]/returns: change from notrun to 0 failed: ldapadd -D cn=ldapadmin,dc=cgcs,dc=local -w f62083c68b43Ti0* -f /etc/openldap/initial_config.ldif returned 49 instead of one of [0] 2020-01-30T16:21:54.301 Error: 2020-01-30 16:21:54 +0000 /Stage[main]/Platform::Drbd::Etcd::Bootstrap/Platform::Drbd::Filesystem[drbd-etcd]/Drbd::Resource[drbd-etcd]/Drbd::Resource::Enable[drbd-etcd]/Drbd::Resource::Up[drbd-etcd]/Mount[/opt/etcd]: Could not evaluate: Execution of '/usr/bin/mount /opt/etcd' returned 32: mount: /dev/drbd7 is write-protected, mounting read-only When I run the ldapadd command myself it fails with: ldap_bind: Invalid credentials (49) I’ve not configured any ldap password anywhere so I guess that the ldapadmin password is auto-generated, but the fact that it’s not working is cause for concern. I’ve looked through the log file for any clues but everything prior to the above command has worked fine no errors or warnings. I am at a loss, any pointers would be appreciated. |\\/|artin -- Martin Ward Technical Support Engineer.Senior Group: Carrier Support Ext: 29745 -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cordoba.malibran at intel.com Tue Feb 11 17:44:20 2020 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 11 Feb 2020 17:44:20 +0000 Subject: [Starlingx-discuss] repo command stopped working In-Reply-To: References: Message-ID: <734B7412-BF9F-41BF-99AC-9C9923878623@intel.com> This line[0] will need to be changed to: RUN curl https://storage.googleapis.com/git-repo-downloads/repo-1 > /usr/local/bin/repo && \ Pointing to the `repo-1` branch, however this bug[1] needs to be solved first. - Erich [0] https://opendev.org/starlingx/tools/src/branch/master/Dockerfile#L126 [1] https://bugs.chromium.org/p/gerrit/issues/detail?id=12316 On 2/11/20, 10:54 AM, "Scott Little" wrote: I've found that there is a poorly documented command line option. repo init --repo-branch=repo-1 ... On 2020-02-11 11:26 a.m., Scott Little wrote: > It looks like they pushed repo version 2 into their stable branch last > night. You'll likely pick it up with your next 'repo init' or 'repo > sync'. It demands git 2.10.2 or better, which isn't available on > Centos 7. > > My initial workaround is ... for folks that are hit by this ... is to > revert to repo version 1. I don't yet see a way to force repo 1 to be > used from command line, so we must let the first call fail .... > > > repo init .... # command fails > > cd .repo/repo > > git checkout repo-1 > > cd - > > repo init .... # command passes > > > Hopefully we can work out a better solution... > > Scott > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From maria.g.perez.ibarra at intel.com Tue Feb 11 18:12:11 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 11 Feb 2020 18:12:11 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200211 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-FEBRUARY-11 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Tue Feb 11 20:29:04 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 11 Feb 2020 20:29:04 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Feb 12, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B95E1B@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of the TSC/Community call tomorrow. We'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200212T1500 From build.starlingx at gmail.com Tue Feb 11 20:31:39 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 11 Feb 2020 15:31:39 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_repo_sync_layered - Build # 56 - Failure! Message-ID: <1653627227.727.1581453100426.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 56 Status: Failure Timestamp: 20200211T203126Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200211T203111Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MANIFEST: compile.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200211T203111Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200211T203111Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler From build.starlingx at gmail.com Tue Feb 11 20:55:13 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 11 Feb 2020 15:55:13 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_repo_sync_layered - Build # 57 - Still Failing! In-Reply-To: <465208889.725.1581453097948.JavaMail.javamailuser@localhost> References: <465208889.725.1581453097948.JavaMail.javamailuser@localhost> Message-ID: <419334724.731.1581454514454.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 57 Status: Still Failing Timestamp: 20200211T205511Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200211T205501Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MANIFEST: compile.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200211T205501Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200211T205501Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler From scott.little at windriver.com Tue Feb 11 22:10:08 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 11 Feb 2020 17:10:08 -0500 Subject: [Starlingx-discuss] [important] Build layering has merged Message-ID: <083e3f67-fb2f-ffa6-e480-d8aa3ce8f270@windriver.com> The build layering feature has merged. The documentation review is still outstanding, hopefully merged soon:     https://review.opendev.org/#/c/705092/5 CENGN will build in both layered and non-layered mode for a few days. The one are where things are significantly different is the location of lst files, and the fact that each layer carries an independent set of lst files.  Read the doc.  I'll try to incorporate any Q/A into future revisions to the document. Scott From sgw at linux.intel.com Tue Feb 11 22:50:53 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 11 Feb 2020 14:50:53 -0800 Subject: [Starlingx-discuss] [important] Build layering has merged In-Reply-To: <083e3f67-fb2f-ffa6-e480-d8aa3ce8f270@windriver.com> References: <083e3f67-fb2f-ffa6-e480-d8aa3ce8f270@windriver.com> Message-ID: Thanks to Scott and Martin along with a cast of other merged. This should be a major improvement for folks working on building and testing changes in StarlingX. Sau! On 2/11/20 2:10 PM, Scott Little wrote: > The build layering feature has merged. > > The documentation review is still outstanding, hopefully merged soon: > https://review.opendev.org/#/c/705092/5 > > CENGN will build in both layered and non-layered mode for a few days. > > The one are where things are significantly different is the location of > lst files, and the fact that each layer carries an independent set of > lst files.  Read the doc.  I'll try to incorporate any Q/A into future > revisions to the document. > > Scott > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Don.Penney at windriver.com Tue Feb 11 22:53:28 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 11 Feb 2020 22:53:28 +0000 Subject: [Starlingx-discuss] [important] Build layering has merged In-Reply-To: References: <083e3f67-fb2f-ffa6-e480-d8aa3ce8f270@windriver.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC16410C1@ALA-MBD.corp.ad.wrs.com> Agreed. I'm a big fan of this feature, and I think designers will see a big difference from it. -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Tuesday, February 11, 2020 5:51 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [important] Build layering has merged Thanks to Scott and Martin along with a cast of other merged. This should be a major improvement for folks working on building and testing changes in StarlingX. Sau! On 2/11/20 2:10 PM, Scott Little wrote: > The build layering feature has merged. > > The documentation review is still outstanding, hopefully merged soon: > https://review.opendev.org/#/c/705092/5 > > CENGN will build in both layered and non-layered mode for a few days. > > The one are where things are significantly different is the location of > lst files, and the fact that each layer carries an independent set of > lst files.  Read the doc.  I'll try to incorporate any Q/A into future > revisions to the document. > > Scott > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Tue Feb 11 23:47:03 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 11 Feb 2020 23:47:03 +0000 Subject: [Starlingx-discuss] [important] Build layering has merged In-Reply-To: References: <083e3f67-fb2f-ffa6-e480-d8aa3ce8f270@windriver.com> Message-ID: <9A85D2917C58154C960D95352B22818BF166F9C9@fmsmsx123.amr.corp.intel.com> This is very cool. I just merged the Docs changes. brucej -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Tuesday, February 11, 2020 3:51 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [important] Build layering has merged Thanks to Scott and Martin along with a cast of other merged. This should be a major improvement for folks working on building and testing changes in StarlingX. Sau! On 2/11/20 2:10 PM, Scott Little wrote: > The build layering feature has merged. > > The documentation review is still outstanding, hopefully merged soon: > https://review.opendev.org/#/c/705092/5 > > CENGN will build in both layered and non-layered mode for a few days. > > The one are where things are significantly different is the location > of lst files, and the fact that each layer carries an independent set > of lst files.  Read the doc.  I'll try to incorporate any Q/A into > future revisions to the document. > > Scott > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From build.starlingx at gmail.com Wed Feb 12 02:31:34 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 11 Feb 2020 21:31:34 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 416 - Still Failing! In-Reply-To: <1344903451.722.1581400551035.JavaMail.javamailuser@localhost> References: <1344903451.722.1581400551035.JavaMail.javamailuser@localhost> Message-ID: <523336127.739.1581474695105.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 416 Status: Still Failing Timestamp: 20200212T023002Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200212T023002Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From mward at akamai.com Wed Feb 12 09:56:41 2020 From: mward at akamai.com (Ward, Martin) Date: Wed, 12 Feb 2020 09:56:41 +0000 Subject: [Starlingx-discuss] Invalid password for ldapadmin user during simplex installation In-Reply-To: References: Message-ID: <7EB7D256-E88E-41DD-A7D7-FC531C8C6467@akamai.com> No problem. I will have a go at installing using the latest doc at some point this week. Are there any plans to create a non-O/S-specific installation, or one that breaks out any O/S specific stuff out to different sections? I am using CentOS rather than Ubuntu and while I can probably figure out the differences (because I am supposed to be smart) others may need a bit more instruction. |\/| From: "Dale, Kristal" Date: Tuesday, 11 February 2020 at 17:34 To: Martin Ward , "starlingx-discuss at lists.starlingx.io" Subject: RE: [Starlingx-discuss] Invalid password for ldapadmin user during simplex installation Thanks for the info Martin! I will add deprecating the old wiki pages found in search to the maintenance task list. Cheers, Kris -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Wed Feb 12 10:42:28 2020 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Wed, 12 Feb 2020 10:42:28 +0000 Subject: [Starlingx-discuss] the way to enable swift in starlingx In-Reply-To: References: <56829C2A36C2E542B0CCB9854828E4D85628A95E@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A78C9@CDSMSX102.ccr.corp.intel.com> Message-ID: Hey, i do not want to disturb this mailing list but is there realy no one they can help me? My problem is still the same, via CLI or GUI (OS horizon), the response to the container-api (swift) returned a http 401 (access denied). Greez & thx, volker... -----Ursprüngliche Nachricht----- Von: von Hoesslin, Volker Gesendet: Freitag, 7. Februar 2020 13:46 An: Chen, Haochuan Z ; 'ji at sibyl.li' Cc: 'starlingx-discuss at lists.starlingx.io' ; Hu, Yong Betreff: [URL wurde verändert] Re: [Starlingx-discuss] the way to enable swift in starlingx Externe E-Mail! Öffnen Sie nur Links oder Anhänge von vertrauenswürdigen Absendern! After some research i have checked the stx-openstack.yaml and checkout the chart-url: http://Achtung/http://172.17.0.1/helm_charts/starlingx/ceph-rgw-0.1.0.tgz so i curl this endpoint and got an 404 ... so i tried an controller swact... re-apply stx-openstack on controller-1 and it seems running now... $ system application-list +---------------------+---------------------------+-------------------------------+----------------+----------+----------------------------------------------+ | application | version | manifest name | manifest file | status | progress | +---------------------+---------------------------+-------------------------------+----------------+----------+----------------------------------------------+ | platform-integ-apps | 1.0-8 | platform-integration-manifest | manifest.yaml | applied | completed | | stx-openstack | 1.0-19-centos-stable-latest | armada-manifest | stx-openstack.yaml | applying | processing chart: osh-openstack-cinder, overall completion: 36.0% | +---------------------+---------------------------+-------------------------------+----------------+----------+----------------------------------------------+ --- after some minutes... After time its stopped with a failure... i have checked the logs and got the info that the script is waiting for an evicted cinder-volume pod, i think evicted pods should be skipped on script? So i delete this old pod and re-apply the stx-openstack... for now ist running... --- after some minutes Applying is still stopped at 71% on waitung on evicted horizon-pods... after delete all evicted pods, the script is finished successed... So, i tried to use the OS-horizon gui to checkout the new options: Object Storage -> containers ... if i click on this section i got some access-denied toasts and my current user (admin) is logged off... how can i handle this and define the nessesary roles/groups to access this section? Greez & thx, volker... -----Ursprüngliche Nachricht----- Von: Chen, Haochuan Z Gesendet: Freitag, 7. Februar 2020 12:38 An: von Hoesslin, Volker ; 'ji at sibyl.li' Cc: 'starlingx-discuss at lists.starlingx.io' ; Hu, Yong Betreff: [URL wurde verändert] Re: [Starlingx-discuss] the way to enable swift in starlingx Externe E-Mail! Öffnen Sie nur Links oder Anhänge von vertrauenswürdigen Absendern! You can save all the log, with command collect, and submit a launchpad issue with log attached. $ collect http://Achtung/http://Achtung/https://bugs.launchpad.net/starlingx/+filebug Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: von Hoesslin, Volker Sent: Friday, February 7, 2020 7:10 PM To: Chen, Haochuan Z ; 'ji at sibyl.li' Cc: 'starlingx-discuss at lists.starlingx.io' ; Hu, Yong Subject: AW: the way to enable swift in starlingx Hi, my setup: STX 3 (2x controller, 2x worker, 3x storage). STX-OpenStack (1.0-19-centos-stable-latest) is currently successfully installed/running... So i try to enable the swift/radosgw, but it fails: controller-0:~$ source /etc/platform/openrc [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify radosgw config service_enabled=true +-------------+--------------------------------------+ | Property | Value | +-------------+--------------------------------------+ | uuid | 11edb3d5-ac8f-4510-950e-cccbf6da4aad | | service | radosgw | | section | config | | name | service_enabled | | value | true | | personality | None | | resource | None | +-------------+--------------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-apply radosgw Applying radosgw service parameters [sysadmin at controller-0 ~(keystone_admin)]$ system helm-chart-attribute-modify stx-openstack ceph-rgw openstack --enabled=true +------------+--------------------+ | Property | Value | +------------+--------------------+ | attributes | {u'enabled': True} | | name | ceph-rgw | | namespace | openstack | +------------+--------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system application-apply stx-openstack +---------------+----------------------------------+ | Property | Value | +---------------+----------------------------------+ | active | True | | app_version | 1.0-19-centos-stable-latest | | created_at | 2020-01-23T12:21:23.423993+00:00 | | manifest_file | stx-openstack.yaml | | manifest_name | armada-manifest | | name | stx-openstack | | progress | None | | status | applying | | updated_at | 2020-01-23T12:52:39.080423+00:00 | +---------------+----------------------------------+ Please use 'system application-list' or 'system application-show stx-openstack' to view the current progress. [sysadmin at controller-0 ~(keystone_admin)]$ system application-list +---------------------+---------------------------+-------------------------------+--------------------+--------------+-------------------------------------+ | application | version | manifest name | manifest file | status | progress | +---------------------+---------------------------+-------------------------------+--------------------+--------------+-------------------------------------+ | platform-integ-apps | 1.0-8 | platform-integration-manifest | manifest.yaml | applied | completed | | stx-openstack | 1.0-19-centos-stable-latest | armada-manifest | stx-openstack.yaml | apply-failed | (0) Reason: SSLError [Errno 2] No such file or directory | +---------------------+---------------------------+-------------------------------+--------------------+--------------+-------------------------------------+ Is there are any other steps to get this running on STX3 and stx-openstack 1.0-19-centos-stable-latest ? Greez & thx, volker... -----Ursprüngliche Nachricht----- Von: Chen, Haochuan Z Gesendet: Montag, 2. Dezember 2019 05:53 An: von Hoesslin, Volker ; 'ji at sibyl.li' Cc: 'starlingx-discuss at lists.starlingx.io' ; Hu, Yong Betreff: the way to enable swift in starlingx Hi system application-upload system service-parameter-modify radosgw config service_enabled=true system service-parameter-apply radosgw system helm-chart-attribute-modify stx-openstack ceph-rgw openstack --enabled=true system application-apply stx-openstack openstack endpoint list | grep object BR! -----Original Message----- From: Chen, Haochuan Z Sent: Thursday, November 28, 2019 10:12 AM To: starlingx-discuss at lists.starlingx.io Cc: Volker.Hoesslin at swsn.de; ji at sibyl.li Subject: swift enabling Hi I find there is voice to enable swift, why it was removed? Thanks! Message: 2 Date: Mon, 25 Nov 2019 07:53:31 -0600 From: joji vlogs To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Enabling Object Storage Message-ID: Content-Type: text/plain; charset="utf-8" Hi all, I recently did a test deployment based on a 2+2+2 setup with one minor difference being I only have one storage server on hand. My question is how would I go about enabling object storage? I saw a reference to it in the helm charts and attempted to set an override but the APIs would not be listening for requests and a "unable to get swift service info" error. Thank you and have a great day! Message: 3 Date: Fri, 22 Nov 2019 14:14:15 +0000 From: "von Hoesslin, Volker" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] STX 2.0: swift? Message-ID: Content-Type: text/plain; charset="iso-8859-1" hi, how can i add the object storage (swift) feature to my current STX2.0 openstack? BR! Martin, Chen SSP, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Tuesday, November 26, 2019 12:05 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 18, Issue 150 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://Achtung/http://Achtung/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: controller filesystem (Waines, Greg) 2. Enabling Object Storage (joji vlogs) 3. Re: StarlingX 2.0 Account Locked for User (Andy Ning) ---------------------------------------------------------------------- Message: 1 Date: Mon, 25 Nov 2019 13:26:31 +0000 From: "Waines, Greg" To: Saul Wold , "von Hoesslin, Volker" , "Sun, Austin" , "starlingx-discuss at lists.starlingx.io" , "Dale, Kristal" Subject: Re: [Starlingx-discuss] controller filesystem Message-ID: Content-Type: text/plain; charset="utf-8" Actually a section on managing filesystems on the controllers is planned for STX 3.0 ... based on the proposed TOC for the new Operations Guide. Greg From: Saul Wold Date: Thursday, November 21, 2019 at 12:13 PM To: "von Hoesslin, Volker" , "Sun, Austin" , "starlingx-discuss at lists.starlingx.io" , "Dale, Kristal" Subject: Re: [Starlingx-discuss] controller filesystem Kristal: We probably need a Story/Task added to the documentation to get the documentation of host-fs added in the right place. This helps with filesystem re-sizing. Maybe it's already there. Sau! On 11/21/19 7:12 AM, von Hoesslin, Volker wrote: incredible !!! thats the point i have search! big thx! ------------------------------------------------------------------------ *Von:* Sun, Austin [austin.sun at intel.com] *Gesendet:* Donnerstag, 21. November 2019 15:20 *An:* von Hoesslin, Volker; starlingx-discuss at lists.starlingx.io *Betreff:* Re: [Starlingx-discuss] controller filesystem Hi Volker: From the email chain, http://Achtung/http://Achtung/http://lists.starlingx.io/pipermail/starlingx-discuss/2019-August/005656.html You can probably the command line to change the size of docker lv Thanks. BR Austin Sun. *From:* von Hoesslin, Volker > *Sent:* Thursday, November 21, 2019 9:20 PM *To:* starlingx-discuss at lists.starlingx.io *Subject:* [Starlingx-discuss] controller filesystem hi, i trying to import some existing qcow2 images into my new installed STX 2.0. openstack image create --file /media/foobar.qcow2 --private --unprotected --disk-format qcow2 "foobar" all works fine, the image are available. now, i'm trying to create an new volume based on this images. if the images are <=6GB all works fine, but some images are very huge (10-200GB) and then it ends in an error. after some research i can see on controller the mount point /dev/mapper/cgts--vg-docker--lv 30G 11G 20G 35% /var/lib/docker increase the used storage. after fail "volume create" it goes back to given value 35%. in my oppinion, this mount point should resize to some value about 300-400GB, but how? in STX horizon backend (http://Achtung/http://Achtung/http://10.10.10.2:8080/admin/system_config/?tab=system_config_tab__storage_table) there is an "docker-distribution", but no docker-mount-point itself? btw, if i try to change the "docker-distribution" value to some other value (eg. 500GB via horizon backend), i got this error: *Error: *backup size of 60 is insufficient for host controller-1. Minimum backup size of 100 is required based upon glance size 20 and database size 20. Rejecting modification request. - see attachment - how can i increase the backup size to handle this error?! greez & thx, volker... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://Achtung/http://Achtung/http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://Achtung/http://Achtung/http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Mon, 25 Nov 2019 07:53:31 -0600 From: joji vlogs To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Enabling Object Storage Message-ID: Content-Type: text/plain; charset="utf-8" Hi all, I recently did a test deployment based on a 2+2+2 setup with one minor difference being I only have one storage server on hand. My question is how would I go about enabling object storage? I saw a reference to it in the helm charts and attempted to set an override but the APIs would not be listening for requests and a "unable to get swift service info" error. Thank you and have a great day! Austin Gillmann -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Mon, 25 Nov 2019 11:05:19 -0500 From: Andy Ning To: Subject: Re: [Starlingx-discuss] StarlingX 2.0 Account Locked for User Message-ID: <8f8e6cad-0ad7-4be4-6693-a25e6cec93ad at windriver.com> Content-Type: text/plain; charset="utf-8"; format=flowed On 2019-11-25 12:00 AM, Yong Hu wrote: > Hi Anirudh, > > This issue is similar to this LP#1853017 [0], which was triggered the > account locking if the password of Openstack user "admin" was changed. > In this LP, for unknown reason, "registry-token-server" daemon kept > accessing "keystone" on host (not the instance in containers) with > obsolete token and led to "admin" account locked after 5 attempts. > If registry token server keeps on accessing keystone with obsolete token, this could be a bug in the token server. Normally if a keystone client get a failed authentication, it should try to retrieve a new token by using username/password. Andy > Right now, I am debugging this issue. > Good thing is Cengn build 11/16 seemed not to have such a problem > (LP#1853017). > > You might have a try with this version? > BTW: which cengn build were you using? > > > [0] > http://Achtung/http://Achtung/https://bugs.launchpad.net/starlingx/+bu > g/1853017 > > regards, > Yong > > On 2019/11/19 6:06 PM, Anirudh Gupta wrote: >> Hi Team, >> >> I have installed StarlingX 2.0 Duplex Bare Metal. >> >> I am trying to create 2 VM’s and repeating this cycle a number of times. >> >> After using the setup for around half and hour, I am not longer able >> to access the GUI. >> >> Ever though I type correct Username/Password, it gives an error of >> Invalid Credentials. >> >> Then, I thought to use the CLI commands by following LOAD CLI section >> given in link >> >> http://Achtung/http://Achtung/https://docs.starlingx.io/deploy_instal >> l_guides/r2_rel >> ease/openstack/ >> access.html#local-cli >> >> >> But with this also, I am facing the same error >> >> controller-0:~$ export OS_CLOUD=openstack_helm >> >> controller-0:~$ openstack endpoint list >> >> The account is locked for user: 230578cde382430a8adac399afab1230. >> (HTTP 401) (Request-ID: req-6da6d59a-2edd-4f2b-a8bf-f13f2e423a77) >> >> Earlier this automatically started working after 5-7 mins. >> >> But this time, I am completely Blocked. >> >> I have also raised a bug regarding the same >> >> http://Achtung/http://Achtung/https://bugs.launchpad.net/starlingx/+b >> ug/1853093 >> >> Please suggest some pointers, so that I can unblock and resume my >> activities. >> >> Regards >> >> Anirudh Gupta >> >> DISCLAIMER: This electronic message and all of its contents, contains >> information which is privileged, confidential or otherwise protected >> from disclosure. The information contained in this electronic mail >> transmission is intended for use only by the individual or entity to >> which it is addressed. If you are not the intended recipient or may >> have received this electronic mail transmission in error, please >> notify the sender immediately and delete / destroy all copies of this >> electronic mail transmission without disclosing, copying, >> distributing, forwarding, printing or retaining any part of it. >> Hughes Systique accepts no responsibility for loss or damage arising >> from the use of the information transmitted by this email including >> damage from virus. >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://Achtung/http://Achtung/http://lists.starlingx.io/cgi-bin/mailm >> an/listinfo/sta >> rlingx-discuss >> > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://Achtung/http://Achtung/http://lists.starlingx.io/cgi-bin/mailma > n/listinfo/star > lingx-discuss -- Andy Ning Cube: 3071 Tel: 613-9631408 (int: 4408) Skype: andy.ning.wr ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://Achtung/http://Achtung/http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 18, Issue 150 ************************************************** _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://Achtung/http://Achtung/http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://Achtung/http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bin.yang at intel.com Wed Feb 12 14:32:09 2020 From: bin.yang at intel.com (Yang, Bin) Date: Wed, 12 Feb 2020 14:32:09 +0000 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSNOiBQQlIgU3RhdHVzIENoZWNr?= In-Reply-To: <42960858-5122-4de5-b4c9-6d5619f4d692@linux.intel.com> References: <5f55cb03-5360-3e11-fcc9-46f6dc24d6f8@linux.intel.com> <060f01d5db34$f5e38a50$e1aa9ef0$@jitstack.com> <42960858-5122-4de5-b4c9-6d5619f4d692@linux.intel.com> Message-ID: Hi Saul, As you know, the build system patch [1] had introduced the pbr command to generate pkg version. This should be the only effect on the compile time of pbr enabled pkg. Jitstack had tested command execution time. The result of "with pbr" should be the command execution time. Please correct me if my understanding is wrong. But the result of "without pbr" should be "0". Build system will not execute pbr command if it is not enabled. Thanks, Bin [1]: https://review.opendev.org/#/c/691632/ -----Original Message----- From: Saul Wold Sent: Tuesday, February 4, 2020 23:09 To: wesley.yang at jitstack.com; daniels.cai at jitstack.com; Yang, Bin ; shangyakun at jitstack.com Cc: Hu, Yong ; starlingx-discuss at lists.starlingx.io Subject: Re: 回复: PBR Status Check Wesley, Yakun: I hope you guys are doing OK with the restrictions and stay healthy! I did a review of the numbers that Yakun provide in a prior email (summary here) Package Compile timeconsumption with pbr without pbr the first time 0.287s 0.301s the second time 0.322s 0.351s the third time 0.554s 0.235s the fourth time( deb package) 0.299s 0.292s Can you please provide more details about what your actual test methodology (and/or scripts) was? I think at some-point it was suggested that 2 packages (python and non-python) should be used. They should then be compiled / cleaned in a loop of about 10-12 times to ensure any caches are cleared. Then an average and deviation be determined. Thanks Sau! On 2/4/20 12:27 AM, wesley.yang at jitstack.com wrote: > Hi Saul > I'm working at home remotely at home for the Government's restriction, my colleagues are also working remotely or still on vacation. > You may see that my colleagues Yakun has just sent the preliminary result to you, and he will do some more test and update later. > > Wesley > > -----邮件原件----- > 发件人: Saul Wold > 发送时间: 2020年2月4日 8:54 > 收件人: wesley.yang at jitstack.com; daniels.cai at jitstack.com; Yang, Bin > > 抄送: Hu, Yong ; starlingx-discuss at lists.starlingx.io > 主题: Re: PBR Status Check > > Hi Wesley, > > Following up on this, I am not sure what your working status is because of the Virus and various Gov't restrictions. If you are working, can you give us an update on the Performance impact question I listed below. > > Thanks > Sau! > > > On 1/22/20 10:14 AM, Saul Wold wrote: >> >> Hi All & Welcome Wesley, >> >> We have a new community member from JitStack starting to look at the >> PBR work, here is some background for him. >> >> The PBR work was proposed via the StarlingX Feature Specification >> process, see the Flock Versioning specification [0], this is based on >> the OpenStack Python Build Reasonableness [1] and Semantic Versioning >> (SemVer) [2] definition. >> >> One of the issues that we are trying to resolve is the impact of the >> proposed change from Bin Yang to the time it takes to build a single >> package with PBR before and after the change. Ideally this would be >> done multiple times and provide the average along with the deviation. >> This in an important part of the project in order for us to move forward. >> >> Look forward to working with you. >> >> Sau! >> >> [0] >> https://docs.starlingx.io/specs/specs/stx-3.0/approved/standardize_fl >> o >> ck_versioning.html >> >> [1] https://docs.openstack.org/pbr/latest/ >> [2] https://docs.openstack.org/pbr/latest/user/semver.html > From austin.sun at intel.com Wed Feb 12 15:08:02 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 12 Feb 2020 15:08:02 +0000 Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 2/12/2020 Message-ID: Hi All: Thanks join the call. MoM for 2/12 meeting: - Ceph containerization status and comments address (Martin) http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007731.html [1] rook is integrating into application-app currently , if use remove/delete platform-application, ceph-cluster will be destory. this is admin choose if they want to do it. [2] only will consolated app (sysinv or rook) to controller ceph to discuss further in maillist. - Pbr update ( JITStack-Wesley) build-time issue address http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007676.html , Wesley will update result by End of Week to maillist. reply the email and do an exmplaination - CentOS8 update ( Austin/Shuicheng) Strategy discuss 1) kernel 4.18 uprade only , which new gcc 8.2 is using new gcc will cause compile el7 rpms failure. 2) use old gcc(4.x) to compile new kernel + master rpms 3) mixing gcc using (kernel will use new gcc , and other use old gcc) , -- prefer this way , but current mock does not support 2 gcc co-worker. work item update kernel-rt. use kernel 4.18.x.147 , std and rt which is using centos8.1, as much as using current rpm. kubeadm (kube-proxy) issue update. keep legacy mode binary in iptables. drbd8 --- fix compile issues, and worked. puppet 4.8 w/ ruby 2.5 --worked , send result python2/python3 bring python3 to master , and start python2to3 converting for example nfv. Opens - Vista Creek (FPGA card) support still need confirm i40e drivers New OPEA driver will be released by end of this week. SRIOV device plugin https://github.com/intel/sriov-network-device-plugin/pull/196 -Open Thanks. BR Austin Sun. From scott.little at windriver.com Wed Feb 12 15:23:56 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 12 Feb 2020 10:23:56 -0500 Subject: [Starlingx-discuss] [important] Build layering has merged In-Reply-To: <9A85D2917C58154C960D95352B22818BF166F9C9@fmsmsx123.amr.corp.intel.com> References: <083e3f67-fb2f-ffa6-e480-d8aa3ce8f270@windriver.com> <9A85D2917C58154C960D95352B22818BF166F9C9@fmsmsx123.amr.corp.intel.com> Message-ID: All three layers have built successfully on cengn. Compier layer: 52 min: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200211T210351Z/ Distro Layer: 152 min: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200211T215536Z/ Flock Layer: 54 min: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200211T234731Z/     - This build includes iso but not docker containers The layered build iso can be found here: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/outputs/iso/ I hope you will take it out for a test drive. The monolithic build will continue to run for a few weeks, and it can still be found here for now: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_build/outputs/iso/ The old path will likely be removed or symlinked to point to the flock build. How do I recognize the layer content in my build? On cengn http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/outputs/ISO_BUILD_INFO.txt After install     /etc/build.info The expected content is something like: OS="centos" SW_VERSION="20.01" BUILD_TARGET="Host Installer" BUILD_TYPE="Formal" BUILD_ID="20200211T234731Z" JOB="STX_build_layer_flock_master_master" BUILD_BY="starlingx.build at cengn.ca" BUILD_NUMBER="16" BUILD_HOST="starlingx_mirror" BUILD_DATE="2020-02-11 23:47:31 +0000" FLOCK_OS="centos" FLOCK_JOB="STX_build_layer_flock_master_master" FLOCK_BUILD_BY="starlingx.build at cengn.ca" FLOCK_BUILD_NUMBER="16" FLOCK_BUILD_HOST="starlingx_mirror" FLOCK_BUILD_DATE="2020-02-11 23:47:31 +0000" DISTRO_OS="centos" DISTRO_JOB="STX_build_layer_distro_master_master" DISTRO_BUILD_BY="starlingx.build at cengn.ca" DISTRO_BUILD_NUMBER="16" DISTRO_BUILD_HOST="starlingx_mirror" DISTRO_BUILD_DATE="2020-02-11 21:55:36 +0000" COMPILER_OS="centos" COMPILER_JOB="STX_build_layer_compiler_master_master" COMPILER_BUILD_BY="starlingx.build at cengn.ca" COMPILER_BUILD_NUMBER="30" COMPILER_BUILD_HOST="starlingx_mirror" COMPILER_BUILD_DATE="2020-02-11 21:03:51 +0000" However I note cengn didn't generate the content as expected.  I'll be working to fix this today. Next steps: 1) Set up the layered jobs to run nightly 2) Modify the layered build jobs to only run if there is a code change. There is some question as to should an upper layer rebuild occur if a lower layer was rebuilt, even though there is no code delta. I argue yes,  If a compiler layer component changes, I think everything should be rebuilt with the new tools.  Also a flock layer component might change an api, an include file, etc. and publish it via a dev package.  We could try to tease out if the upper layer is using a dev package that has been upversioned by a lower layer, but for a first pass I'd suggest we just rebuild of a lower layer has been updated. The argument against hinges largely on the flock layer containing little if any compiled code.  e.g. Python and Go rather than C or C++.  I'll concede that point. However a change to compile layer, say 'rpm' or 'python' should be picked up right away. All layers should use the same packaging tools.  All python packages should be validated vs the updated interpreter. 3) There has been a suggestion to move iso and container builds out of the flock layer job into an independent job. The argument for moving the iso build into a separate job hinges on the assumption that a lower layer can be rebuilt without triggering a rebuild of the upper layer. The argument to move docker images into an independent layer is a much stronger one.  Most images are pulling a lot, if not all, of there content from external sources.  We might want to pick up new content in a docker image even though the flock layer is unchanged. On 2020-02-11 6:47 p.m., Jones, Bruce E wrote: > This is very cool. I just merged the Docs changes. > > brucej > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Tuesday, February 11, 2020 3:51 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [important] Build layering has merged > > Thanks to Scott and Martin along with a cast of other merged. This should be a major improvement for folks working on building and testing changes in StarlingX. > > Sau! > > On 2/11/20 2:10 PM, Scott Little wrote: >> The build layering feature has merged. >> >> The documentation review is still outstanding, hopefully merged soon: >> https://review.opendev.org/#/c/705092/5 >> >> CENGN will build in both layered and non-layered mode for a few days. >> >> The one are where things are significantly different is the location >> of lst files, and the fact that each layer carries an independent set >> of lst files.  Read the doc.  I'll try to incorporate any Q/A into >> future revisions to the document. >> >> Scott >> >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > 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 Feb 12 15:30:05 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 12 Feb 2020 15:30:05 +0000 Subject: [Starlingx-discuss] puppet 4.8 on CentOS8 Message-ID: Hi All: As you may know, we try to keep puppet4.8 in starlingx, there is no puppet4.8 in centos8 repo. I have explored 2 approaches to enable puppet4.8 in centos8 . Option1: puppet4.8 + ruby 2.5.3(centos8 default ruby version) Option2: puppet4.8 + ruby 2.0.0 rpm (stx currently use) For Option1, after adding depends requests, and pull one patch from upstream[1], puppet4.8 can be run on centos8 now. For Option2, there is deps confliction, libgdbm.so.4()(64bit) and libreadline.so.6()(64bit) which have upgrade in centos8. Is there any concern for option1 ? And for option2 issue, is there any suggestion if option1 is not the best options ? [1] https://github.com/puppetlabs/puppet/commit/578687a00195191185f44d8cb38f4b7716d99c31 Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Wed Feb 12 15:39:05 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 12 Feb 2020 07:39:05 -0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSNOiBQQlIgU3RhdHVzIENoZWNr?= In-Reply-To: References: <5f55cb03-5360-3e11-fcc9-46f6dc24d6f8@linux.intel.com> <060f01d5db34$f5e38a50$e1aa9ef0$@jitstack.com> <42960858-5122-4de5-b4c9-6d5619f4d692@linux.intel.com> Message-ID: On 2/12/20 6:32 AM, Yang, Bin wrote: > Hi Saul, > As you know, the build system patch [1] had introduced the pbr command to generate pkg version. This should be the only effect on the compile time of pbr enabled pkg. > > Jitstack had tested command execution time. > The result of "with pbr" should be the command execution time. Please correct me if my understanding is wrong. > But the result of "without pbr" should be "0". Build system will not execute pbr command if it is not enabled. If your just instrumenting the "pbr execution time", then I guess then without pbr should be 0. based on your comments during the Distro call, the build time with pbr enabled becomes noise in the minutes that it takes to do a build. It's just not clear from below what was being tested, I think this sort of clarifies things. Let's get some feedback from the rest of the Build team (Scott, Don)? Thanks Sau! > > > Thanks, > Bin > > [1]: https://review.opendev.org/#/c/691632/ > > -----Original Message----- > From: Saul Wold > Sent: Tuesday, February 4, 2020 23:09 > To: wesley.yang at jitstack.com; daniels.cai at jitstack.com; Yang, Bin ; shangyakun at jitstack.com > Cc: Hu, Yong ; starlingx-discuss at lists.starlingx.io > Subject: Re: 回复: PBR Status Check > > > Wesley, Yakun: > > I hope you guys are doing OK with the restrictions and stay healthy! > > I did a review of the numbers that Yakun provide in a prior email (summary here) > > Package Compile > timeconsumption with pbr without pbr > the first time 0.287s 0.301s > the second time 0.322s 0.351s > the third time 0.554s 0.235s > the fourth time( deb package) 0.299s 0.292s > > > Can you please provide more details about what your actual test methodology (and/or scripts) was? > > I think at some-point it was suggested that 2 packages (python and > non-python) should be used. They should then be compiled / cleaned in a loop of about 10-12 times to ensure any caches are cleared. Then an average and deviation be determined. > > Thanks > Sau! > > > > On 2/4/20 12:27 AM, wesley.yang at jitstack.com wrote: >> Hi Saul >> I'm working at home remotely at home for the Government's restriction, my colleagues are also working remotely or still on vacation. >> You may see that my colleagues Yakun has just sent the preliminary result to you, and he will do some more test and update later. >> >> Wesley >> >> -----邮件原件----- >> 发件人: Saul Wold >> 发送时间: 2020年2月4日 8:54 >> 收件人: wesley.yang at jitstack.com; daniels.cai at jitstack.com; Yang, Bin >> >> 抄送: Hu, Yong ; starlingx-discuss at lists.starlingx.io >> 主题: Re: PBR Status Check >> >> Hi Wesley, >> >> Following up on this, I am not sure what your working status is because of the Virus and various Gov't restrictions. If you are working, can you give us an update on the Performance impact question I listed below. >> >> Thanks >> Sau! >> >> >> On 1/22/20 10:14 AM, Saul Wold wrote: >>> >>> Hi All & Welcome Wesley, >>> >>> We have a new community member from JitStack starting to look at the >>> PBR work, here is some background for him. >>> >>> The PBR work was proposed via the StarlingX Feature Specification >>> process, see the Flock Versioning specification [0], this is based on >>> the OpenStack Python Build Reasonableness [1] and Semantic Versioning >>> (SemVer) [2] definition. >>> >>> One of the issues that we are trying to resolve is the impact of the >>> proposed change from Bin Yang to the time it takes to build a single >>> package with PBR before and after the change. Ideally this would be >>> done multiple times and provide the average along with the deviation. >>> This in an important part of the project in order for us to move forward. >>> >>> Look forward to working with you. >>> >>> Sau! >>> >>> [0] >>> https://docs.starlingx.io/specs/specs/stx-3.0/approved/standardize_fl >>> o >>> ck_versioning.html >>> >>> [1] https://docs.openstack.org/pbr/latest/ >>> [2] https://docs.openstack.org/pbr/latest/user/semver.html >> From Bill.Zvonar at windriver.com Wed Feb 12 15:49:54 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 12 Feb 2020 15:49:54 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Feb 12, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B96249@ALA-MBD.corp.ad.wrs.com> Notes from the Community Call just now... - Standing Topics - Sanity: back up & running, all green since last week - need to begin sanitizing the Layered Build [in addition to?] the Monoloithic Build - Saul looking into options... - Reviews: anyone? - Kris: a few minor reviews need workflow so she can close them off before she's gone (stx-metal, stx-integration, stx-tools) - https://review.opendev.org/#/c/703221/ - integ - https://review.opendev.org/#/c/702762/ - metal (need to trigger build, then ready for reviews) - https://review.opendev.org/#/c/703879/ - tools - workflow added! thank you! - CentOS 8: good progress discussed in distro non-openstack call - Austin: working on an incremental approach, starting with the kernel upgrade; multiple risk items have been retired - Saul: still lots of reviews to review - https://review.opendev.org/#/q/topic:centos8+(status:open)+AND+projects:starlingx/ - Topics for this week - StarlingX space and time request for the PTG in Vancouver (ildikov) - time for us to give them our requirements - need to get this to them by this time next week - event is from June 8th: https://www.openstack.org/events/opendev-ptg-2020/ - we agreed to go with 1 day, we'll likely have 15-20 people - Layered Build! http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007752.html - see notes about Sanity above - the docs re: build workflow are in review - Saul reports that he has done layered builds successfully, as has the team in India - Mid-Cycle Meetup (Bruce) - team from China will be unable to travel - do we want to hold the meeting w/out them or consider rescheduling? - delaying it would mean it starts bumping up into the PTG (early June) - agreed that we'll carry on with the mid-cycle meeting, and will time-shift to allow folks from China to participate via Zoom - Stale references to Ironic on IRC - Ian has asked some folks to look into it - Kris said the Docs team will re-visit the wiki content to check for what's outdated/deprecatable - Open Requests for Help - stx-openstack fails reapply: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007728.html - Yong will look into it, though it's likely not purely an OpenStack thing (i.e. could be a Container thing) - the way to enable swift in starlingx: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007758.html - normally this would be for the Storage team to look into, but they've been re-orged - Frank will ask someone on his team if they can help -----Original Message----- From: Zvonar, Bill Sent: Tuesday, February 11, 2020 3:29 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: Community (& TSC) Call (Feb 12, 2020) Hi all, reminder of the TSC/Community call tomorrow. We'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200212T1500 From Don.Penney at windriver.com Wed Feb 12 23:06:38 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 12 Feb 2020 23:06:38 +0000 Subject: [Starlingx-discuss] ansible playbook update to replace stable-latest image tag references Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC1644F13@ALA-MBD.corp.ad.wrs.com> Hi folks, I've posted https://review.opendev.org/707462 to update the ansible playbooks with static image tags, rather than using the stable-latest moving tags in the packaged charts. If you're using a mirror or proxy, you may need to update it to pull these images from the docker hub. These are previously built images that have been manually retagged with a static version: docker.io/starlingx/intel-fpga-plugin:stx.3.0-v0.11.0-103-g4f28657 docker.io/starlingx/intel-gpu-plugin:stx.3.0-v0.11.0-103-g4f28657 docker.io/starlingx/intel-qat-plugin:stx.3.0-v0.11.0-109-gc48c502 docker.io/starlingx/k8s-cni-sriov:stx.3.0-v2.2 docker.io/starlingx/k8s-plugins-sriov-network-device:stx.3.0-v3.1 I will send a further email once the update merges, but it won't hurt to pull these image tags into your mirror/proxy ahead of time. Cheers, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Wed Feb 12 23:18:18 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Wed, 12 Feb 2020 23:18:18 +0000 Subject: [Starlingx-discuss] [docs][meeting] docs team meeting minutes 2020-02-12 Message-ID: Hello All, Here are this week's docs team meeting minutes. Join us if you have interest in StarlingX docs! We meet Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Cheers, Kris 2020-02-12 * All -- reviews merged since last week: 8 * All -- bug status -- no change * Opens * Kris -- Assignment of R4 doc tasks - Ping Ghada (KRIS - DONE) * Kris -- Training review:https://review.opendev.org/#/c/706629/ ? This is actually a repeat of pretty much everything on OpenStack. ? Worth instead expanding current doc contribution doc w/ section that refers users to the correct info (setup, config, etc) on openstack, plus outlines the bits for STX? (eg. docs pull content from all projects, explain doc structure) - My cheatsheet is more or less covered by OpenStack content (except testing repos theme locally) * All -- Docs content versioning. Currently manual on just the Install guides. Need to look into long term approach (assuming all Install, Ops, and Config guides will be release specific). ? Q1. How many versions do we want to keep available at a given time? (Is there a way that we can essentially 'freeze' a older version, and not actively build it any more? E.g. just reference the last built html.) ? Q2. Can we transition to making releases of docs to match releases of STX? Does this make sense? (does it allow contributions to the upcoming release?) ? Q3. What do OpenStack projects do? https://docs.openstack.org/horizon/train/ (version switcher), https://docs.openstack.org/ironic/latest/index.html (switch in URL, w/ explanation), https://docs.openstack.org/keystone/latest/install/index.html (switch in URL) * All -- Wiki status ? Revisit planned migration of wiki content: lets close this out (see yellow). https://docs.google.com/spreadsheets/d/1UJjUttsWQRyauATrip0wKGIxSO7DvyetDKmPwvEIDaA/edit?usp=sharing ? Someone using an out-of-date set of install instructions? See http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007651.html * How did they find this? Findable via search. https://wiki.openstack.org/w/index.php?search=simplex&fulltext=Search&searchToken=9i4iqzaqsb3qpuja8mni4d6c7 * We need to clean out old content. Check search results * Found on wiki o https://wiki.openstack.org/wiki/Installation_libvirt_qemu o https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Simplex o https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Duplex o https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Controller_Storage o https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Dedicated_Storage o https://wiki.openstack.org/wiki/StarlingX/Docs_and_Infra/InstallationGuides/virtual-AIO-Simplex/Access-StarlingX-OpenStack o https://wiki.openstack.org/wiki/StarlingX/Docs_and_Infra/InstallationGuides/virtual-AIO-Simplex/Access-StarlingX-Kubernetes o https://wiki.openstack.org/wiki/StarlingX/Docs_and_Infra/InstallationGuides/configurationOptions ? What steps are needed to stop chasing the split of content between wiki and docs? * Windows Active Dir content (Kris) - pending R4 baseline refresh * * All -- Ongoing tasks: * Kris -- misc doc clean up -- all approved thanks to the community! * Kris -- R4 install guides - terms refresh. Review ready, pending merging of R4 updates so I can rebase before creating a review. * STX in a box: (https://storyboard.openstack.org/#!/story/2006622) ? Draft in review https://review.opendev.org/#/c/692202/ ? Next steps (GREG) * Kris -- Transition plan: https://etherpad.openstack.org/p/docs-transition-plan -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Feb 13 02:31:21 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 12 Feb 2020 21:31:21 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 417 - Still Failing! In-Reply-To: <890993274.737.1581474692607.JavaMail.javamailuser@localhost> References: <890993274.737.1581474692607.JavaMail.javamailuser@localhost> Message-ID: <470729110.744.1581561082385.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 417 Status: Still Failing Timestamp: 20200213T023001Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200213T023001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From thierry at openstack.org Thu Feb 13 11:17:27 2020 From: thierry at openstack.org (Thierry Carrez) Date: Thu, 13 Feb 2020 12:17:27 +0100 Subject: [Starlingx-discuss] Training session on Bitergia dashboard, Feb 17 In-Reply-To: <3c5b0d97-5c82-d981-81a4-ee905829436a@openstack.org> References: <3c5b0d97-5c82-d981-81a4-ee905829436a@openstack.org> Message-ID: Reminder: Please signup on the etherpad if you're interested in the training, and suggest dashboard improvements that we could use as practical exercise on Monday. Thierry Carrez wrote: > Hi StarlingXers, > > Since last year, the StarlingX community dashboard is available at > starlingx.biterg.io. It shows a series of pre-defined dashboards that > let you extract metrics from gerrit, git and ML data. > > However the real power of the Bitergia toolkit is when you go to the > next level and drill down and filter for more relevant data, or when you > build your own analysis and visualization. > > In order to present those features and answer community questions, we've > set up a video training session with Bitergia which will happen on Jitsi > Meet[1] Monday, February 17 at 1600 UTC[2]. > > Please sign up on: > https://etherpad.openstack.org/p/bitergia-training-Feb2020 > > All details for connection will be posted there. Also if you have > examples of changes in existing dashboards that you'd like to see, or of > visualizations you'd like to build, please add to the suggestions in the > etherpad. We'll collect suggestions to build the final training contents. > > See you there! > > [1] https://meet.jit.si/ > [2] > https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200217T16&p1=1440 From shuicheng.lin at intel.com Thu Feb 13 12:04:48 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 13 Feb 2020 12:04:48 +0000 Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 2/12/2020 In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C766395FE19@SHSMSX104.ccr.corp.intel.com> Hi BUILD team and all, In yesterday's meeting, we prefer to build CentOS 8 kernel with gcc-8.2.1, while keep other packages with gcc-4.8.5. But current build system doesn't support gcc switch during package build. First, gcc is a base package defined in mock config, and gcc with latest version(8.2.1) will be auto installed to mock environment when mock init, before any package building. This will lead to all packages build with gcc-8.2.1. Another problem is, mock environment is reused for all packages build. There is no mock environment clean between packages build. To support different packages with different gcc, we need have two mock environment with different gcc version, and accept build for corresponding packages build only. It will be a big change for current build system. Do you know how could we handle the case better? Base on upper problem, I prefer to go with option 2, gcc-4.8.5 for CentOS 8 kernel and other CentOS 7 packages. GCC upgrade will be done later along with CentOS 8 base OS packages upgrade. Please share me your suggestion. Thanks. Best Regards Shuicheng -----Original Message----- From: Sun, Austin Sent: Wednesday, February 12, 2020 11:08 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 2/12/2020 Hi All: Thanks join the call. MoM for 2/12 meeting: - Ceph containerization status and comments address (Martin) http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007731.html [1] rook is integrating into application-app currently , if use remove/delete platform-application, ceph-cluster will be destory. this is admin choose if they want to do it. [2] only will consolated app (sysinv or rook) to controller ceph to discuss further in maillist. - Pbr update ( JITStack-Wesley) build-time issue address http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007676.html , Wesley will update result by End of Week to maillist. reply the email and do an exmplaination - CentOS8 update ( Austin/Shuicheng) Strategy discuss 1) kernel 4.18 uprade only , which new gcc 8.2 is using new gcc will cause compile el7 rpms failure. 2) use old gcc(4.x) to compile new kernel + master rpms 3) mixing gcc using (kernel will use new gcc , and other use old gcc) , -- prefer this way , but current mock does not support 2 gcc co-worker. work item update kernel-rt. use kernel 4.18.x.147 , std and rt which is using centos8.1, as much as using current rpm. kubeadm (kube-proxy) issue update. keep legacy mode binary in iptables. drbd8 --- fix compile issues, and worked. puppet 4.8 w/ ruby 2.5 --worked , send result python2/python3 bring python3 to master , and start python2to3 converting for example nfv. Opens - Vista Creek (FPGA card) support still need confirm i40e drivers New OPEA driver will be released by end of this week. SRIOV device plugin https://github.com/intel/sriov-network-device-plugin/pull/196 -Open Thanks. BR Austin Sun. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From mingyuan.qi at intel.com Thu Feb 13 12:41:59 2020 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Thu, 13 Feb 2020 12:41:59 +0000 Subject: [Starlingx-discuss] Openstack reapply failing In-Reply-To: References: Message-ID: Hi Austin, Could you check the pdb resources in openstack namespace when reapplying the opentack app? `$ Kubectl -n openstack get pdb` I suspect that neutron-server pdb is out of helm chart's control for some reason. And you could try to delete it only and re-apply the app again. Mingyuan -----Original Message----- From: Austin Gillmann Sent: Sunday, February 9, 2020 2:00 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Openstack reapply failing Hi all, My earlier email was never replied to so I will try to re-word it: I recently deployed StarlingX 3.0 under a dedicated storage standard cluster (the storage servers running on dell r740xd's with HDD's and compute/controllers running on HP bl460c G8 blades with 2 SSD's) the stx-openstack application applies successfully on the first try, but will abort upon reapply for a config change or such. The errors armada puts out is details = "release osh-openstack-neutron failed: poddisruptionbudgets.policy "neutron-server" already exists" and "getting deployed release "osh-openstack-neutron": release: "osh-openstack-neutron" not found" Everything else in logs look normal to me, but let me know if you need any files attached! If anyone has any idea how to get past this please let me know! Best wishes, Austin Gillmann _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ji at sibyl.li Thu Feb 13 14:28:01 2020 From: ji at sibyl.li (Austin Gillmann) Date: Thu, 13 Feb 2020 08:28:01 -0600 Subject: [Starlingx-discuss] Openstack reapply failing In-Reply-To: References: Message-ID: Hi Mingyuan, I checked the PDB list and neutron-server was indeed listed so I deleted it, however it seems kubernetes is playing whack-a-mole with me; so far I had to delete secrets, serviceaccounts, and RBAC roles as it seems like helm does not have control on *any* neutron related items Best regards, Austin On Thu, Feb 13, 2020 at 6:42 AM Qi, Mingyuan wrote: > > Hi Austin, > > Could you check the pdb resources in openstack namespace when reapplying the opentack app? `$ Kubectl -n openstack get pdb` > I suspect that neutron-server pdb is out of helm chart's control for some reason. And you could try to delete it only and re-apply the app again. > > Mingyuan > > -----Original Message----- > From: Austin Gillmann > Sent: Sunday, February 9, 2020 2:00 > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Openstack reapply failing > > Hi all, > > My earlier email was never replied to so I will try to re-word it: > > I recently deployed StarlingX 3.0 under a dedicated storage standard cluster (the storage servers running on dell r740xd's with HDD's and compute/controllers running on HP bl460c G8 blades with 2 SSD's) the stx-openstack application applies successfully on the first try, but will abort upon reapply for a config change or such. > > The errors armada puts out is details = "release osh-openstack-neutron > failed: poddisruptionbudgets.policy "neutron-server" already exists" > and "getting deployed release "osh-openstack-neutron": release: > "osh-openstack-neutron" not found" > > Everything else in logs look normal to me, but let me know if you need any files attached! If anyone has any idea how to get past this please let me know! > > Best wishes, > Austin Gillmann > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Don.Penney at windriver.com Thu Feb 13 16:15:58 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 13 Feb 2020 16:15:58 +0000 Subject: [Starlingx-discuss] ansible playbook update to replace stable-latest image tag references Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC164522B@ALA-MBD.corp.ad.wrs.com> This update has merged and will be in the next CENGN build. From: Penney, Don Sent: Wednesday, February 12, 2020 6:07 PM To: 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: ansible playbook update to replace stable-latest image tag references Hi folks, I've posted https://review.opendev.org/707462 to update the ansible playbooks with static image tags, rather than using the stable-latest moving tags in the packaged charts. If you're using a mirror or proxy, you may need to update it to pull these images from the docker hub. These are previously built images that have been manually retagged with a static version: docker.io/starlingx/intel-fpga-plugin:stx.3.0-v0.11.0-103-g4f28657 docker.io/starlingx/intel-gpu-plugin:stx.3.0-v0.11.0-103-g4f28657 docker.io/starlingx/intel-qat-plugin:stx.3.0-v0.11.0-109-gc48c502 docker.io/starlingx/k8s-cni-sriov:stx.3.0-v2.2 docker.io/starlingx/k8s-plugins-sriov-network-device:stx.3.0-v3.1 I will send a further email once the update merges, but it won't hurt to pull these image tags into your mirror/proxy ahead of time. Cheers, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Thu Feb 13 17:56:48 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 13 Feb 2020 17:56:48 +0000 Subject: [Starlingx-discuss] Drdb fails for AIO Simplex after unlock controller-0 In-Reply-To: References: Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC16459E9@ALA-MBD.corp.ad.wrs.com> You’re not rebooting the node after the initial ansible playbooks before you do the config and unlock, are you? How big are your disks? From: 胡天昊 [mailto:hu.tianhao at 99cloud.net] Sent: Monday, February 10, 2020 3:30 AM To: starlingx-discuss Subject: [Starlingx-discuss] Drdb fails for AIO Simplex after unlock controller-0 Hi all, When I install AIO Simplex following this guide(https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/aio_simplex_install_kubernetes.html), drdb fails after unlock controller-0. And following is part of the log(/var/log/puppet/latest/puppet.log): 2020-01-16T09:35:07.689 Debug: 2020-01-16 09:35:07 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-prepare-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/unless: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5707: UserWarning: 2020-01-16T09:35:07.732 Debug: 2020-01-16 09:35:07 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-prepare-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/unless: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5739: UserWarning: 2020-01-16T09:36:15.967 Notice: 2020-01-16 09:36:15 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-prepare-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/returns: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5707: UserWarning: 2020-01-16T09:36:16.507 Notice: 2020-01-16 09:36:16 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-prepare-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/returns: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5739: UserWarning: 2020-01-16T09:36:20.485 Notice: 2020-01-16 09:36:20 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-activate-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/returns: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5707: UserWarning: 2020-01-16T09:36:20.568 Notice: 2020-01-16 09:36:20 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-activate-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/returns: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5739: UserWarning: 2020-01-16T09:36:34.615 Error: 2020-01-16 09:36:34 +0000 yes yes | drbdadm create-md drbd-pgsql -W--peer-max-bio-size=128k returned 40 instead of one of [0] 2020-01-16T09:36:34.843 Error: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Drbd::Pgsql/Platform::Drbd::Filesystem[drbd-pgsql]/Drbd::Resource[drbd-pgsql]/Drbd::Resource::Enable[drbd-pgsql]/Drbd::Resource::Up[drbd-pgsql]/Exec[initialize DRBD metadata for drbd-pgsql]/returns: change from notrun to 0 failed: yes yes | drbdadm create-md drbd-pgsql -W--peer-max-bio-size=128k returned 40 instead of one of [0] 2020-01-16T09:36:34.852 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Drbd::Pgsql/Platform::Drbd::Filesystem[drbd-pgsql]/Drbd::Resource[drbd-pgsql]/Drbd::Resource::Enable[drbd-pgsql]/Drbd::Resource::Up[drbd-pgsql]/Exec[enable DRBD resource drbd-pgsql]: Skipping because of failed dependencies 2020-01-16T09:36:35.052 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Drbd::Service/Service[drbd]: Skipping because of failed dependencies 2020-01-16T09:36:35.094 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Anchors/Anchor[platform::services]: Skipping because of failed dependencies 2020-01-16T09:36:35.122 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Helm/File[/opt/platform/helm_charts]: Skipping because of failed dependencies 2020-01-16T09:36:35.135 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Helm/Exec[restart lighttpd for helm]: Skipping because of failed dependencies 2020-01-16T09:36:35.164 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Helm::Repositories/Platform::Helm::Repository[starlingx]/File[/www/pages/helm_charts/starlingx]: Skipping because of failed dependencies It seems like that drdb config fails. And I run "drbdadm create-md drbd-pgsql -W--peer-max-bio-size=128k", I get the following result: Move internal meta data from last-known position? [need to type 'yes' to confirm] yes md_offset 21474832384 al_offset 0 bm_offset 0 Found ext3 filesystem 20971520 kB data area apparently used 0 kB left usable by current configuration Device size would be truncated, which would corrupt data and result in 'access beyond end of device' errors. You need to either * use external meta data (recommended) * shrink that filesystem first * zero out the device (destroy the filesystem) Operation refused. Command 'drbdmeta 0 v08 /dev/cgts-vg/pgsql-lv internal create-md --peer-max-bio-size=128k' terminated with exit code 40 I'd like to know that how to reconfig drdb or did I set some config wrong? Thanks, Tianhao [http://mailhz.qiye.163.com/qiyeimage/logo/60511048/1576638602260.jpg] -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu Feb 13 19:24:26 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 13 Feb 2020 13:24:26 -0600 Subject: [Starlingx-discuss] Interim PL elections - nomination period is now open In-Reply-To: <581F3235-92B6-4E23-AF78-F3E30A7BE1CB@gmail.com> References: <581F3235-92B6-4E23-AF78-F3E30A7BE1CB@gmail.com> Message-ID: Hi, It is a friendly reminder that the nomination period of the interim PL elections is open. The open PL positions are the following: * Docs * MultiOS * Networking * Test The nomination period is open until __February 17, 2020 2100 UTC__. All nominations must be submitted as a text file to the starlingx/election repository as explained on the election website[1]. Please see the website[2] for additional details about this election. If you have any questions please be sure to either ask them on the mailing list or to the elections officials[4]. Thank you, [1] https://docs.starlingx.io/election/#how-to-submit-a-candidacy [2] https://docs.starlingx.io/election/ [3] https://docs.starlingx.io/election/#election-officials > On Feb 10, 2020, at 18:55, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > Nominations for the interim PL positions are now open and will remain open until __February 17, 2020 2100 UTC__. > > The project teams looking for new PLs are the following: > * Docs > * MultiOS > * Networking > * Test > > All nominations must be submitted as a text file to the starlingx/election repository as explained on the election website[1]. > > Please note that the name of the file should match the email address in your Gerrit configuration. > > Candidates for the Project Lead Positions: Any contributing community member who is an individual member of the Foundation can propose their candidacy for the project PL seat. > > The election will be held from February 10, 2020 2100 UTC through to February 24, 2020 2100 UTC. > > The electorate of the PL election are the community members that are contributors for the given official team[2] over the 12-month timeframe February 9, 2019 to February 9, 2020, as well as the contributors who are acknowledged by the TSC. > > Please see the website[3] for additional details about this election. > Please find below the timeline: > > PL nomination starts @ February 10, 2020 2100 UTC > PL nomination ends @ February 17, 2020 2100 UTC > > PL election starts @ February 17, 2020 2100 UTC > PL election ends @ February 24, 2020 2100 UTC > > If you have any questions please be sure to either ask them on the mailing list or to the elections officials[4]. > > Thank you, > > [1] https://docs.starlingx.io/election/#how-to-submit-a-candidacy > [2] https://docs.starlingx.io/governance/reference/tsc/projects/index.html > [3] https://docs.starlingx.io/election/ > [4] https://docs.starlingx.io/election/#election-officials > > > From ildiko.vancsa at gmail.com Thu Feb 13 19:46:54 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 13 Feb 2020 13:46:54 -0600 Subject: [Starlingx-discuss] Meeting wiki page update - ACTION NEEDED Message-ID: Hi StarlingX Community, I’m reaching out to you about the Meetings wiki page[1] which is getting very out of date especially now that we have a few changes that just took place. I would like to ask all of you who have meetings that you are running to check and update the wiki if needed with the latest information about the meeting time and cadence. Also please list every meeting in its own row in the table to ensure every meeting has a good visibility and easy to find for everyone. Please let me know if you need any help editing the wiki. Thanks and Best Regards, Ildikó [1] https://wiki.openstack.org/wiki/Starlingx/Meetings From ji at sibyl.li Fri Feb 14 00:36:04 2020 From: ji at sibyl.li (Austin Gillmann) Date: Thu, 13 Feb 2020 18:36:04 -0600 Subject: [Starlingx-discuss] Openstack reapply failing In-Reply-To: References: Message-ID: Hi again! Seems I found a workaround to my issue, by removing the application that seems to clean up everything well enough to apply successfully again! Albeit destructive it seems to have worked well. Best regards, Austin On Thu, Feb 13, 2020 at 8:28 AM Austin Gillmann wrote: > Hi Mingyuan, > > I checked the PDB list and neutron-server was indeed listed so I > deleted it, however it seems kubernetes is playing whack-a-mole with > me; so far I had to delete secrets, serviceaccounts, and RBAC roles as > it seems like helm does not have control on *any* neutron related > items > > Best regards, > Austin > > On Thu, Feb 13, 2020 at 6:42 AM Qi, Mingyuan > wrote: > > > > Hi Austin, > > > > Could you check the pdb resources in openstack namespace when reapplying > the opentack app? `$ Kubectl -n openstack get pdb` > > I suspect that neutron-server pdb is out of helm chart's control for > some reason. And you could try to delete it only and re-apply the app again. > > > > Mingyuan > > > > -----Original Message----- > > From: Austin Gillmann > > Sent: Sunday, February 9, 2020 2:00 > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] Openstack reapply failing > > > > Hi all, > > > > My earlier email was never replied to so I will try to re-word it: > > > > I recently deployed StarlingX 3.0 under a dedicated storage standard > cluster (the storage servers running on dell r740xd's with HDD's and > compute/controllers running on HP bl460c G8 blades with 2 SSD's) the > stx-openstack application applies successfully on the first try, but will > abort upon reapply for a config change or such. > > > > The errors armada puts out is details = "release osh-openstack-neutron > > failed: poddisruptionbudgets.policy "neutron-server" already exists" > > and "getting deployed release "osh-openstack-neutron": release: > > "osh-openstack-neutron" not found" > > > > Everything else in logs look normal to me, but let me know if you need > any files attached! If anyone has any idea how to get past this please let > me know! > > > > Best wishes, > > Austin Gillmann > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Fri Feb 14 02:31:38 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 13 Feb 2020 21:31:38 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 418 - Still Failing! In-Reply-To: <730419011.742.1581561079787.JavaMail.javamailuser@localhost> References: <730419011.742.1581561079787.JavaMail.javamailuser@localhost> Message-ID: <218817233.748.1581647499528.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 418 Status: Still Failing Timestamp: 20200214T023003Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200214T023003Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From mingyuan.qi at intel.com Fri Feb 14 03:51:27 2020 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Fri, 14 Feb 2020 03:51:27 +0000 Subject: [Starlingx-discuss] Openstack reapply failing In-Reply-To: References: Message-ID: Yes, you can always remove the stx-openstack application if you do not need to keep the data within mariadb database. Mingyuan From: Austin Gillmann Sent: Friday, February 14, 2020 8:36 To: Qi, Mingyuan ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Openstack reapply failing Hi again! Seems I found a workaround to my issue, by removing the application that seems to clean up everything well enough to apply successfully again! Albeit destructive it seems to have worked well. Best regards, Austin On Thu, Feb 13, 2020 at 8:28 AM Austin Gillmann > wrote: Hi Mingyuan, I checked the PDB list and neutron-server was indeed listed so I deleted it, however it seems kubernetes is playing whack-a-mole with me; so far I had to delete secrets, serviceaccounts, and RBAC roles as it seems like helm does not have control on *any* neutron related items Best regards, Austin On Thu, Feb 13, 2020 at 6:42 AM Qi, Mingyuan > wrote: > > Hi Austin, > > Could you check the pdb resources in openstack namespace when reapplying the opentack app? `$ Kubectl -n openstack get pdb` > I suspect that neutron-server pdb is out of helm chart's control for some reason. And you could try to delete it only and re-apply the app again. > > Mingyuan > > -----Original Message----- > From: Austin Gillmann > > Sent: Sunday, February 9, 2020 2:00 > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Openstack reapply failing > > Hi all, > > My earlier email was never replied to so I will try to re-word it: > > I recently deployed StarlingX 3.0 under a dedicated storage standard cluster (the storage servers running on dell r740xd's with HDD's and compute/controllers running on HP bl460c G8 blades with 2 SSD's) the stx-openstack application applies successfully on the first try, but will abort upon reapply for a config change or such. > > The errors armada puts out is details = "release osh-openstack-neutron > failed: poddisruptionbudgets.policy "neutron-server" already exists" > and "getting deployed release "osh-openstack-neutron": release: > "osh-openstack-neutron" not found" > > Everything else in logs look normal to me, but let me know if you need any files attached! If anyone has any idea how to get past this please let me know! > > Best wishes, > Austin Gillmann > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Fri Feb 14 14:52:19 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 14 Feb 2020 09:52:19 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 419 - Still Failing! In-Reply-To: <565012649.746.1581647496685.JavaMail.javamailuser@localhost> References: <565012649.746.1581647496685.JavaMail.javamailuser@localhost> Message-ID: <1638421466.752.1581691940418.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 419 Status: Still Failing Timestamp: 20200214T145145Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200214T145145Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From cristopher.j.lemus.contreras at intel.com Fri Feb 14 16:34:13 2020 From: cristopher.j.lemus.contreras at intel.com (Lemus Contreras, Cristopher J) Date: Fri, 14 Feb 2020 16:34:13 +0000 Subject: [Starlingx-discuss] Sanity test - Layered Build Message-ID: <755A5C4C-AD3F-490E-9F42-B8AADF333471@intel.com> Hello, We have found an issue during the install of the main controller using the image taken from the layered build: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200213T223559Z/ I have filled this bug with additional details: https://bugs.launchpad.net/starlingx/+bug/1863340 In summary, main controller install fails, and it doesn’t boot. Please, let me know if you need any additional details. Regards, Cristopher -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Fri Feb 14 16:58:59 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 14 Feb 2020 11:58:59 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 420 - Still Failing! In-Reply-To: <1003509089.750.1581691938067.JavaMail.javamailuser@localhost> References: <1003509089.750.1581691938067.JavaMail.javamailuser@localhost> Message-ID: <1777179850.756.1581699540352.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 420 Status: Still Failing Timestamp: 20200214T165830Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200214T165830Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From build.starlingx at gmail.com Fri Feb 14 17:47:03 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 14 Feb 2020 12:47:03 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 421 - Still Failing! In-Reply-To: <2046627546.754.1581699537987.JavaMail.javamailuser@localhost> References: <2046627546.754.1581699537987.JavaMail.javamailuser@localhost> Message-ID: <1218744734.760.1581702424858.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 421 Status: Still Failing Timestamp: 20200214T174335Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200214T174335Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From Frank.Miller at windriver.com Fri Feb 14 18:23:12 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Fri, 14 Feb 2020 18:23:12 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Meeting Message-ID: The next containerization meeting is scheduled for Tuesday Feb 18th. Agenda for Feb 18th meeting: 1. Kata containers - list of remaining work items [Shuicheng Lin] 2. Continued discussion for 2005527: CEPH Containerization in StarlingX [Martin Chen] - Update/discussion on how Rook will configure ceph (and not have sysinv involved) - Update/discussion on approach for an existing user with ceph mimic to migrate to a rook ceph cluster 3. Other topics -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2014 bytes Desc: not available URL: From build.starlingx at gmail.com Sat Feb 15 02:32:53 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 14 Feb 2020 21:32:53 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 422 - Still Failing! In-Reply-To: <160861673.758.1581702421269.JavaMail.javamailuser@localhost> References: <160861673.758.1581702421269.JavaMail.javamailuser@localhost> Message-ID: <897194707.764.1581733974580.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 422 Status: Still Failing Timestamp: 20200215T023001Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200215T023001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From build.starlingx at gmail.com Sun Feb 16 02:37:13 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 15 Feb 2020 21:37:13 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 423 - Still Failing! In-Reply-To: <1040614969.762.1581733972085.JavaMail.javamailuser@localhost> References: <1040614969.762.1581733972085.JavaMail.javamailuser@localhost> Message-ID: <1933582907.768.1581820634052.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 423 Status: Still Failing Timestamp: 20200216T023004Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200216T023004Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From hu.tianhao at 99cloud.net Sun Feb 16 15:19:10 2020 From: hu.tianhao at 99cloud.net (=?UTF-8?B?6IOh5aSp5piK?=) Date: Sun, 16 Feb 2020 23:19:10 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?Drdb_fails_for_AIO_Simplex_after_un?= =?utf-8?q?lock_controller-0?= In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC16459E9@ALA-MBD.corp.ad.wrs.com> Message-ID: I didn't reboot the node until the node unlock. And this is my disk information: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 600G 0 disk ├─sda1 8:1 0 1M 0 part ├─sda2 8:2 0 500M 0 part /boot ├─sda3 8:3 0 19.5G 0 part / ├─sda4 8:4 0 229G 0 part │ ├─cgts--vg-scratch--lv 253:0 0 8G 0 lvm /scratch │ ├─cgts--vg-log--lv 253:1 0 7.8G 0 lvm /var/log │ ├─cgts--vg-extension--lv 253:2 0 1G 0 lvm │ │ └─drbd5 147:5 0 1024M 1 disk │ ├─cgts--vg-pgsql--lv 253:3 0 20G 0 lvm │ ├─cgts--vg-docker--lv 253:4 0 30G 0 lvm /var/lib/docker │ ├─cgts--vg-kubelet--lv 253:5 0 10G 0 lvm /var/lib/kubelet │ ├─cgts--vg-etcd--lv 253:6 0 5G 0 lvm │ │ └─drbd7 147:7 0 5G 1 disk │ ├─cgts--vg-backup--lv 253:7 0 25G 0 lvm /opt/backups │ ├─cgts--vg-dockerdistribution--lv 253:8 0 16G 0 lvm │ │ └─drbd8 147:8 0 16G 1 disk │ ├─cgts--vg-rabbit--lv 253:9 0 2G 0 lvm │ │ └─drbd1 147:1 0 2G 1 disk │ ├─cgts--vg-platform--lv 253:10 0 10G 0 lvm │ │ └─drbd2 147:2 0 10G 1 disk │ └─cgts--vg-ceph--mon--lv 253:11 0 20G 0 lvm /var/lib/ceph/mon └─sda5 8:5 0 34G 0 part sdb 8:16 0 200G 0 disk ├─sdb1 8:17 0 199G 0 part /var/lib/ceph/osd/ceph-0 └─sdb2 8:18 0 1G 0 part sdc 8:32 0 200G 0 disk sr0 11:0 1 1.9G 0 rom 发件人:"Penney, Don" 发送日期:2020-02-14 01:56:48 收件人:"胡天昊" ,starlingx-discuss 主题:RE: [Starlingx-discuss] Drdb fails for AIO Simplex after unlock controller-0 You’re not rebooting the node after the initial ansible playbooks before you do the config and unlock, are you? How big are your disks? From: 胡天昊 [mailto:hu.tianhao at 99cloud.net] Sent: Monday, February 10, 2020 3:30 AM To: starlingx-discuss Subject: [Starlingx-discuss] Drdb fails for AIO Simplex after unlock controller-0 Hi all, When I install AIO Simplex following this guide(https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/aio_simplex_install_kubernetes.html), drdb fails after unlock controller-0. And following is part of the log(/var/log/puppet/latest/puppet.log): 2020-01-16T09:35:07.689 Debug: 2020-01-16 09:35:07 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-prepare-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/unless: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5707: UserWarning: 2020-01-16T09:35:07.732 Debug: 2020-01-16 09:35:07 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-prepare-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/unless: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5739: UserWarning: 2020-01-16T09:36:15.967 Notice: 2020-01-16 09:36:15 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-prepare-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/returns: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5707: UserWarning: 2020-01-16T09:36:16.507 Notice: 2020-01-16 09:36:16 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-prepare-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/returns: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5739: UserWarning: 2020-01-16T09:36:20.485 Notice: 2020-01-16 09:36:20 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-activate-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/returns: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5707: UserWarning: 2020-01-16T09:36:20.568 Notice: 2020-01-16 09:36:20 +0000 /Stage[main]/Platform::Ceph::Osds/Platform_ceph_osd[stor-1]/Ceph::Osd[/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/Exec[ceph-osd-activate-/dev/disk/by-path/pci-0000:00:1f.2-ata-2.0]/returns: /usr/lib/python2.7/site-packages/ceph_disk/main.py:5739: UserWarning: 2020-01-16T09:36:34.615 Error: 2020-01-16 09:36:34 +0000 yes yes | drbdadm create-md drbd-pgsql -W--peer-max-bio-size=128k returned 40 instead of one of [0] 2020-01-16T09:36:34.843 Error: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Drbd::Pgsql/Platform::Drbd::Filesystem[drbd-pgsql]/Drbd::Resource[drbd-pgsql]/Drbd::Resource::Enable[drbd-pgsql]/Drbd::Resource::Up[drbd-pgsql]/Exec[initialize DRBD metadata for drbd-pgsql]/returns: change from notrun to 0 failed: yes yes | drbdadm create-md drbd-pgsql -W--peer-max-bio-size=128k returned 40 instead of one of [0] 2020-01-16T09:36:34.852 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Drbd::Pgsql/Platform::Drbd::Filesystem[drbd-pgsql]/Drbd::Resource[drbd-pgsql]/Drbd::Resource::Enable[drbd-pgsql]/Drbd::Resource::Up[drbd-pgsql]/Exec[enable DRBD resource drbd-pgsql]: Skipping because of failed dependencies 2020-01-16T09:36:35.052 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Drbd::Service/Service[drbd]: Skipping because of failed dependencies 2020-01-16T09:36:35.094 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Anchors/Anchor[platform::services]: Skipping because of failed dependencies 2020-01-16T09:36:35.122 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Helm/File[/opt/platform/helm_charts]: Skipping because of failed dependencies 2020-01-16T09:36:35.135 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Helm/Exec[restart lighttpd for helm]: Skipping because of failed dependencies 2020-01-16T09:36:35.164 Warning: 2020-01-16 09:36:34 +0000 /Stage[main]/Platform::Helm::Repositories/Platform::Helm::Repository[starlingx]/File[/www/pages/helm_charts/starlingx]: Skipping because of failed dependencies It seems like that drdb config fails. And I run "drbdadm create-md drbd-pgsql -W--peer-max-bio-size=128k", I get the following result: Move internal meta data from last-known position? [need to type 'yes' to confirm] yes md_offset 21474832384 al_offset 0 bm_offset 0 Found ext3 filesystem 20971520 kB data area apparently used 0 kB left usable by current configuration Device size would be truncated, which would corrupt data and result in 'access beyond end of device' errors. You need to either * use external meta data (recommended) * shrink that filesystem first * zero out the device (destroy the filesystem) Operation refused. Command 'drbdmeta 0 v08 /dev/cgts-vg/pgsql-lv internal create-md --peer-max-bio-size=128k' terminated with exit code 40 I'd like to know that how to reconfig drdb or did I set some config wrong? Thanks, Tianhao -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon Feb 17 00:06:56 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 16 Feb 2020 19:06:56 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 424 - Still Failing! In-Reply-To: <461219701.766.1581820631734.JavaMail.javamailuser@localhost> References: <461219701.766.1581820631734.JavaMail.javamailuser@localhost> Message-ID: <811615347.772.1581898017445.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 424 Status: Still Failing Timestamp: 20200217T000001Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200217T000001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From sgw at linux.intel.com Mon Feb 17 06:18:35 2020 From: sgw at linux.intel.com (Saul Wold) Date: Sun, 16 Feb 2020 22:18:35 -0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSNOiBQQlIgU3RhdHVzIENoZWNr?= In-Reply-To: References: <5f55cb03-5360-3e11-fcc9-46f6dc24d6f8@linux.intel.com> <060f01d5db34$f5e38a50$e1aa9ef0$@jitstack.com> <42960858-5122-4de5-b4c9-6d5619f4d692@linux.intel.com> Message-ID: <54c3f57e-912c-58c0-2520-a529335e2ed5@linux.intel.com> Scott, Don: Does the below information clarify these results and allow for the next steps with the PBR Versioning being enabled for versioning the Flock repos? On 2/12/20 7:39 AM, Saul Wold wrote: > > > On 2/12/20 6:32 AM, Yang, Bin wrote: >> Hi Saul, >>     As you know, the build system patch [1] had introduced the pbr >> command to generate pkg version. This should be the only effect on the >> compile time of pbr enabled pkg. >> >>     Jitstack had tested command execution time. >>     The result of "with pbr" should be the command execution time. >> Please correct me if my understanding is wrong. >>     But the result of "without pbr" should be "0". Build system will >> not execute pbr command if it is not enabled. > If your just instrumenting the "pbr execution time", then I guess then > without pbr should be 0.  based on your comments during the Distro call, > the build time with pbr enabled becomes noise in the minutes that it > takes to do a build. > > It's just not clear from below what was being tested, I think this sort > of clarifies things.  Let's get some feedback from the rest of the Build > team (Scott, Don)? > > Thanks >    Sau! > >> >> >> Thanks, >> Bin >> >> [1]: https://review.opendev.org/#/c/691632/ >> >> -----Original Message----- >> From: Saul Wold >> Sent: Tuesday, February 4, 2020 23:09 >> To: wesley.yang at jitstack.com; daniels.cai at jitstack.com; Yang, Bin >> ; shangyakun at jitstack.com >> Cc: Hu, Yong ; starlingx-discuss at lists.starlingx.io >> Subject: Re: 回复: PBR Status Check >> >> >> Wesley, Yakun: >> >> I hope you guys are doing OK with the restrictions and stay healthy! >> >> I did a review of the numbers that Yakun provide in a prior email >> (summary here) >> >> Package Compile >> timeconsumption                with pbr    without pbr >> the first time                0.287s        0.301s >> the second time                0.322s        0.351s >> the third time                0.554s        0.235s >> the fourth time( deb package)        0.299s        0.292s >> >> >> Can you please provide more details about what your actual test >> methodology (and/or scripts) was? >> >> I think at some-point it was suggested that 2 packages (python and >> non-python) should be used. They should then be compiled / cleaned in >> a loop of about 10-12 times to ensure any caches are cleared. Then an >> average and deviation be determined. >> >> Thanks >>      Sau! >> >> >> >> On 2/4/20 12:27 AM, wesley.yang at jitstack.com wrote: >>> Hi Saul >>> I'm working at home remotely at home for the Government's >>> restriction, my colleagues are also working remotely or still on >>> vacation. >>> You may see that my colleagues Yakun has just sent the preliminary >>> result to you, and he will do some more test and update later. >>> >>> Wesley >>> >>> -----邮件原件----- >>> 发件人: Saul Wold >>> 发送时间: 2020年2月4日 8:54 >>> 收件人: wesley.yang at jitstack.com; daniels.cai at jitstack.com; Yang, Bin >>> >>> 抄送: Hu, Yong ; starlingx-discuss at lists.starlingx.io >>> 主题: Re: PBR Status Check >>> >>> Hi Wesley, >>> >>> Following up on this, I am not sure what your working status is >>> because of the Virus and various Gov't restrictions.  If you are >>> working, can you give us an update on the Performance impact question >>> I listed below. >>> >>> Thanks >>>      Sau! >>> >>> >>> On 1/22/20 10:14 AM, Saul Wold wrote: >>>> >>>> Hi All & Welcome Wesley, >>>> >>>> We have a new community member from JitStack starting to look at the >>>> PBR work, here is some background for him. >>>> >>>> The PBR work was proposed via the StarlingX Feature Specification >>>> process, see the Flock Versioning specification [0], this is based on >>>> the OpenStack Python Build Reasonableness [1] and Semantic Versioning >>>> (SemVer) [2] definition. >>>> >>>> One of the issues that we are trying to resolve is the impact of the >>>> proposed change from Bin Yang to the time it takes to build a single >>>> package with PBR before and after the change. Ideally this would be >>>> done multiple times and provide the average along with the deviation. >>>> This in an important part of the project in order for us to move >>>> forward. >>>> >>>> Look forward to working with you. >>>> >>>> Sau! >>>> >>>> [0] >>>> https://docs.starlingx.io/specs/specs/stx-3.0/approved/standardize_fl >>>> o >>>> ck_versioning.html >>>> >>>> [1] https://docs.openstack.org/pbr/latest/ >>>> [2] https://docs.openstack.org/pbr/latest/user/semver.html >>> > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From haochuan.z.chen at intel.com Mon Feb 17 13:45:48 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 17 Feb 2020 13:45:48 +0000 Subject: [Starlingx-discuss] ceph containerization patch review In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D8562A7E32@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D8562A76F5@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A7E32@CDSMSX102.ccr.corp.intel.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D8562A9371@CDSMSX102.ccr.corp.intel.com> Hi Frank & Brent For rook manage configuration, after introduce rook-ceph, current ceph cluster deployed by puppet will keep or be removed? If removed, containerized ceph cluster deployed by rook-ceph will take the role of provisioner for stx-openstack. If keeps, helm chart rbd-provisioner in platform-integ-app also keeps and takes the role of provisioner for stx-openstack. Containerized ceph cluster deployed by rook-ceph only serve as csi provider for k8s. BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, February 10, 2020 11:47 PM To: Miller, Frank ; 'starlingx-discuss at lists.starlingx.io' Cc: Chen, Tingjie ; Sun, Austin ; Qi, Mingyuan Subject: RE: ceph containerization patch review Hi Frank: As synced with Tingjie, this is my understanding for Rook manage the configuration instead of sysinv. 1, Remove ceph config and status query from sysinv 2, create another tool, like rook-client to launch and provision ceph cluster 3, one helm plugin like rbd-provision, which depends on newly created tool BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Saturday, February 8, 2020 4:16 AM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: ceph containerization patch review Martin: Thanks for posting your reviews and the update on the current status for this feature. I was unable to attend the containerization meeting this week so wasn't able to have Tingjie or you give an update on the open actions for the feature. From the Jan 14 minutes [1] one of the actions is to determine "how can you have Rook do all the configuration and not have sysinv involved" For now I suggest you add an additional item to your Tasks to do list to identify a design that does not require sysinv for the configuration and instead has Rook manage the configuration. I would like to ask that we discuss further at the next containerization meeting and if possible review a proposal from yourself and Austin for this item. Frank [1] https://etherpad.openstack.org/p/stx-containerization From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Thursday, February 06, 2020 11:02 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] ceph containerization patch review Hi folks I enabled containerized ceph cluster with simplex. You can begin to review my patch. I propose to build an image and deploy a simplex system with these patch to check. https://review.opendev.org/#/c/681457/ https://review.opendev.org/#/c/687340/ https://review.opendev.org/#/c/706256/ https://review.opendev.org/#/c/699557/ https://review.opendev.org/#/c/699556/ And I know there is other story, like remove ceph as default backend storage, maybe some conflict, we can discuss together. Tash Done: 1, disable native ceph cluster in ceph.pp 2, disable ceph daemon monitoring in service manager 3, add rook-ceph helm chart to launch ceph cluster 4, add override in stx-config to generate override with starlingx system config 5, sysinv add label in provision stage, to make containerized ceph mon and ceph mgr on designed host 6, add rook-ceph-provisioner helm chart to generate storage class, secret, config and pool for stx-application 7, enabled stx-openstack with containerized ceph 8, update ceph wrapper in stx-config to set or get containerized ceph cluster All these tasks done is enabled with simplex only. Task to do: 1, enable add osd runtime, after system provisioned 2, fix know issue, if system reboot, ceph cluster launch fail 3, enable bluestore and filestore, currently there is only bluestore 4, enable multi-node and duplex 5, enable swift with containerized ceph 6, enable fm alarm for containerized ceph 7, check backup and restore for containerized ceph 8, check system upgrade or how to transit from native ceph cluster to containerized ceph cluster 9, code cleanup 10, update unit test in stx-config BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Mon Feb 17 21:15:58 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 17 Feb 2020 13:15:58 -0800 Subject: [Starlingx-discuss] Interim PL elections - nomination period is now closed In-Reply-To: References: <581F3235-92B6-4E23-AF78-F3E30A7BE1CB@gmail.com> Message-ID: Hi StarlingX Community, The nomination period for the interim PL positions is now closed. Valid nominations: * Test Team PL role: Yang Liu As there is only one valid candidate for the above team we will no hold the voting part of the elections. Teams we are still looking for PLs for: * Docs * MultiOS * Networking The election officials [1] will work with the project teams and the TSC to find people who can take the above open positions and appoint them or look into further actions in case we would not succeed with that attempt. Please stay tuned for updates and final election results. If you have any questions please be sure to either ask them on the mailing list or to the elections officials[1]. Thank you, [1] https://docs.starlingx.io/election/#election-officials > On Feb 13, 2020, at 11:24, Ildiko Vancsa wrote: > > Hi, > > It is a friendly reminder that the nomination period of the interim PL elections is open. > > The open PL positions are the following: > * Docs > * MultiOS > * Networking > * Test > > The nomination period is open until __February 17, 2020 2100 UTC__. > > All nominations must be submitted as a text file to the starlingx/election repository as explained on the election website[1]. > > Please see the website[2] for additional details about this election. > > If you have any questions please be sure to either ask them on the mailing list or to the elections officials[4]. > > Thank you, > > [1] https://docs.starlingx.io/election/#how-to-submit-a-candidacy > [2] https://docs.starlingx.io/election/ > [3] https://docs.starlingx.io/election/#election-officials > > >> On Feb 10, 2020, at 18:55, Ildiko Vancsa wrote: >> >> Hi StarlingX Community, >> >> Nominations for the interim PL positions are now open and will remain open until __February 17, 2020 2100 UTC__. >> >> The project teams looking for new PLs are the following: >> * Docs >> * MultiOS >> * Networking >> * Test >> >> All nominations must be submitted as a text file to the starlingx/election repository as explained on the election website[1]. >> >> Please note that the name of the file should match the email address in your Gerrit configuration. >> >> Candidates for the Project Lead Positions: Any contributing community member who is an individual member of the Foundation can propose their candidacy for the project PL seat. >> >> The election will be held from February 10, 2020 2100 UTC through to February 24, 2020 2100 UTC. >> >> The electorate of the PL election are the community members that are contributors for the given official team[2] over the 12-month timeframe February 9, 2019 to February 9, 2020, as well as the contributors who are acknowledged by the TSC. >> >> Please see the website[3] for additional details about this election. >> Please find below the timeline: >> >> PL nomination starts @ February 10, 2020 2100 UTC >> PL nomination ends @ February 17, 2020 2100 UTC >> >> PL election starts @ February 17, 2020 2100 UTC >> PL election ends @ February 24, 2020 2100 UTC >> >> If you have any questions please be sure to either ask them on the mailing list or to the elections officials[4]. >> >> Thank you, >> >> [1] https://docs.starlingx.io/election/#how-to-submit-a-candidacy >> [2] https://docs.starlingx.io/governance/reference/tsc/projects/index.html >> [3] https://docs.starlingx.io/election/ >> [4] https://docs.starlingx.io/election/#election-officials >> >> >> > From build.starlingx at gmail.com Tue Feb 18 00:07:22 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 17 Feb 2020 19:07:22 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 425 - Still Failing! In-Reply-To: <751055375.770.1581898014227.JavaMail.javamailuser@localhost> References: <751055375.770.1581898014227.JavaMail.javamailuser@localhost> Message-ID: <1961578352.776.1581984443629.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 425 Status: Still Failing Timestamp: 20200218T000003Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T000003Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From haochuan.z.chen at intel.com Tue Feb 18 05:22:20 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 18 Feb 2020 05:22:20 +0000 Subject: [Starlingx-discuss] question about ceph or storage In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D85629C5E4@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D85628DE96@CDSMSX102.ccr.corp.intel.com> <4C60D9C5C8176C47874FFF36647AA19EA4747683@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D85628F3EA@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D85628F402@CDSMSX102.ccr.corp.intel.com> <4C60D9C5C8176C47874FFF36647AA19EA4747C99@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D85629833F@CDSMSX102.ccr.corp.intel.com> <4C60D9C5C8176C47874FFF36647AA19EA4747D45@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D85629BBB7@CDSMSX102.ccr.corp.intel.com> <2239DBED-5ECC-4A11-9426-6B905CBD8348@windriver.com> <56829C2A36C2E542B0CCB9854828E4D85629C5E4@CDSMSX102.ccr.corp.intel.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D8562A945E@CDSMSX102.ccr.corp.intel.com> Hi Bod & Ovidiu What’s usage of deployment rbd-provisioner in helm chart rbd provisioner? BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, January 21, 2020 9:42 PM To: Church, Robert ; Poncea, Ovidiu Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: question about ceph or storage Hi Bob Why sysinv send “admin_keyring” to glance helm chart, but for nova and cinder, send “user_secret_name” in ceph_client config. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Church, Robert > Sent: Thursday, January 16, 2020 11:44 PM To: Chen, Haochuan Z >; Poncea, Ovidiu > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: Re: question about ceph or storage Hi Martin, The rbd provisioner chart creates the secret along with the pool when it’s first installed in the cluster via platform-integ-apps. Regards, Bob From: "Chen, Haochuan Z" > Date: Thursday, January 16, 2020 at 9:22 AM To: Ovidiu Poncea >, Robert Church > Cc: "'starlingx-discuss at lists.starlingx.io'" > Subject: RE: question about ceph or storage Hi Ovidiu & Bob Another question. I found starlingx save ceph cluster’s client.admin key in kube secret “ceph-pool-kube-rbd”. I wonder when starlingx create this secret, read ceph cluster keyring and save to secret. In bootstrap? Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Poncea, Ovidiu > Sent: Monday, December 30, 2019 11:40 PM To: Chen, Haochuan Z >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage I don't know if it's out of date :) it may just need to be retested if it wasn't for current release. ________________________________ From: Chen, Haochuan Z [haochuan.z.chen at intel.com] Sent: Monday, December 30, 2019 3:51 PM To: Poncea, Ovidiu; Church, Robert Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: question about ceph or storage Thanks Ovidiu! If “-c” is out of date, what about remove it later. Martin, Chen SSP, Software Engineer 021-61164330 From: Poncea, Ovidiu > Sent: Monday, December 30, 2019 4:43 PM To: Chen, Haochuan Z >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage Hi Chen, It was used in the previous release for connecting a deployment (especially an openstack one) to an external Ceph cluster. I don't know what is the feature testing status for current release. Ovidiu ________________________________ From: Chen, Haochuan Z [haochuan.z.chen at intel.com] Sent: Monday, December 23, 2019 9:18 AM To: Poncea, Ovidiu; Church, Robert Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: question about ceph or storage Sorry to disturb! Merry Christmas to all StarlingX member! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 23, 2019 3:17 PM To: Poncea, Ovidiu >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage Hi Ovidiu For “system storage-backend-add -c ”, user could deploy another ceph cluster, and add as storage backend, correctly. And this is this command’s intention, correct? Martin, Chen SSP, Software Engineer 021-61164330 From: Poncea, Ovidiu > Sent: Wednesday, December 18, 2019 7:47 PM To: Chen, Haochuan Z >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage Hi Chen, see inline. ________________________________ From: Chen, Haochuan Z [haochuan.z.chen at intel.com] Sent: Tuesday, December 17, 2019 10:46 AM To: Church, Robert; Poncea, Ovidiu Cc: 'starlingx-discuss at lists.starlingx.io' Subject: question about ceph or storage Hi Bob & Ovidiu Some question about ceph or storage. 1, What’s storage tier and storage profile? What’s the [Ovi] Storage tiering is equivalent with this: https://ceph.io/planet/deploying-ceph-with-storage-tiering/ . [Ovi] Profiles are managed by system storprofile-* and system host-apply-profile and are used to copy configuration from one node to another, identical node on initial provisioning. These profiles are only in system inventory, there is no Ceph equivalent. 2, why for duplex it request such puppet class dependency in ceph.pp? Is this request make all drbd config before class ceph? [Ovi] ceph-mon in AIO-DX is DRBD managed and it has a single, floating, monitor. On DX, when you swact, the monitor is stopped on the active controller and started on the standby controller. Drbd::Resource <| |> -> Class['::ceph'] And flag file “.node_ceph_configured”, to inform drbd make init setup before ceph config? 3, To launch ceph-mon, create a logical volume “ceph-mon-lv” and mount to /var/lib/ceph/mon, not directly mkdir “/var/lib/ceph/mon” for ceph-mon [Ovi] Ceph monitors have their own logical volume. They are managed through "system ceph-mon*" commands. Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Wednesday, December 11, 2019 4:46 PM To: Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' >; Poncea, Ovidiu >; Qi, Mingyuan > Subject: RE: ceph ops enabling in sysinv-conductor Hi Bob Some question, what’s storage tier and storage profile? As you said, we no longer manage pool and pg num, is this also unnecessary and we should remove it? BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Church, Robert > Sent: Wednesday, December 4, 2019 12:09 AM To: Chen, Haochuan Z > Cc: 'starlingx-discuss at lists.starlingx.io' >; Poncea, Ovidiu > Subject: Re: ceph ops enabling in sysinv-conductor See inline… From: "Chen, Haochuan Z" > Date: Tuesday, December 3, 2019 at 2:18 AM To: Robert Church > Cc: "'starlingx-discuss at lists.starlingx.io'" >, Ovidiu Poncea > Subject: RE: ceph ops enabling in sysinv-conductor Hi Bob 1, we could update default pg num in sysinv/helm/rbd_provisioner.py. But when platform-integ-apps applied, maybe user has not add osded, so the default pg num is still for user reference. And for user override, I think it should add in ceph-pool-audit, stx-platform-helm/helm-charts/ceph-pools-audit/templates/job-ceph-pools-audit.yaml. but pg num update will make rebalance which cause management network jam. [RTC] For a more robust solution, consider the following: • We can update _met_app_apply_prerequisites () in sysinv/conductor.py for platform-integ-apps to require OSDs to be provisioned prior to applying the application. This will ensure an accurate OSD view when the application is initially applied. • The provisioner system overrides (in sysinv/helm/rbd_provisioner.py) should have the ability to calculate and set an optimal PG number to avoid generating a warning. • The rbd provisioner chart should also support setting a new chunk size (if greater than the existing size) to update the PG num. This will support user PG updates from the helm-overrides API. • I think it’s potentially a good idea for ceph-pool-audit to support adjusting the PG numbers as well but this is tricky as I don’t think we can reduce PG_num in Mimic without creating a new pool and copying the contents (pg_autoscaling is added in Nautilis). This audit code would have to be very specific in adjusting the PG num as installing applications that add additional pools will change the PG_num distribution. 2, the above case is only for system application. Any more alarm for PG number, request user should manage. BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Church, Robert > Sent: Tuesday, December 3, 2019 10:34 AM To: Chen, Haochuan Z > Cc: 'starlingx-discuss at lists.starlingx.io' >; Poncea, Ovidiu > Subject: Re: ceph ops enabling in sysinv-conductor Hi Martin, In STX 1.0, we ran bare-metal openstack services for which we created and managed specific ceph storage pools for glance, cinder, nova, and swift. In this environment, we managed their creation and parameters (PGs and quotas) as the cluster scaled up. With the move to containerizing the openstack services in STX 2.0, pool creation is now driven mostly by helm charts packaged into an application (radosgw pools are the exception). Since we don’t know what additional application(s) will be deployed and what pools may be created, we are currently longer managing pools as in STX 1.0. These related functions in sysinv/conductor/ceph.py are remaining from STX 1.0 and need to be removed and/or repurposed to meet any new requirements. I took a look at the LP logs and it looks like we only have a single application applied: platform-integ-apps. This currently results in a single pool for 6 OSDs cluster: id: 6231df84-33be-4aa4-82ea-7408e0f2421c health: HEALTH_WARN too few PGs per OSD (21 < min 30) services: mon: 3 daemons, quorum controller-0,controller-1,storage-0 mgr: controller-0(active), standbys: controller-1 osd: 6 osds: 6 up, 6 in data: pools: 1 pools, 64 pgs objects: 0 objects, 0 B usage: 645 MiB used, 5.4 TiB / 5.4 TiB avail pgs: 64 active+clean Since every installation will install platform-integ-apps, I think we should do the following: 1. Update the chunk_size calculation in sysinv/helm/rbd_provisioner.py to be dynamically calculated based on the number OSDs provisioned in the cluster. As this may be the only pool created, it should meet the minimum size characteristics to avoid a ceph warning. 2. Update the rbd-provisioner helm chart to support explicitly setting the pg_num based on the chunk size. Do this to allow setting a user override for the chunk size so that we can re-apply platform-integ-apps and explicitly set new values. Regards, Bob From: "Chen, Haochuan Z" > Date: Monday, December 2, 2019 at 1:15 AM To: Robert Church > Cc: "'starlingx-discuss at lists.starlingx.io'" >, Ovidiu Poncea > Subject: ceph ops enabling in sysinv-conductor Hi Bob I find some many function in sysinv-conductor/ceph.py, which could manage ceph cluster, such as create/delete/configure pool, audit pg etc. But why these function is not enabled? Or plan to request user to manage ceph cluster, such as create pool and configure pg num? Now I checked this issue, pg too few, as user maybe deploy few osd, which make alarm. So for such issue, request user to decide correct pg num or user could ignore? https://bugs.launchpad.net/starlingx/+bug/1844164 BR! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Feb 18 10:05:30 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 18 Feb 2020 10:05:30 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 2/19/2020 Message-ID: Hi All : Please check Agenda: Agenda for 2/19 meeting: - Prb update (JITStack-Wesley) --- build time --- new patches - CentOS8 upgrade (Austin/Shuicheng) incremental upgrade on master : * std kernel build status update (kernel 4.18.0-80.11.2 on master env (gcc 4.8 +python2) * rt kernel build status (kernel 4.18.0-147.3.1.rt24.96) , 3.10 patch rebase * python3 enable on master ? which is the prefered repo to upgrade to python3 besides NFV * Ussuri host openstack (oslo , keystone , barbican , horizon and openstack client) upgrade ? plan * the target , plan and goal on stx 4.0 feature ? target : end of March to finish kernel(std and rt) upgrade how about centos8 branch ? shall we conitnue if we fully switch to incremental upgrade - Vista Creek (FPGA card) support OPAE iavf and i40e driver SRIOV device plugin https://github.com/intel/sriov-network-device-plugin/pull/196 - Open If have any other topic, feel free to add to https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. ____________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Frank.Miller at windriver.com Tue Feb 18 14:06:25 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 18 Feb 2020 14:06:25 +0000 Subject: [Starlingx-discuss] ceph containerization patch review In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D8562A9371@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D8562A76F5@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A7E32@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A9371@CDSMSX102.ccr.corp.intel.com> Message-ID: +Bob who is the containers TL From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Monday, February 17, 2020 8:46 AM To: Miller, Frank ; 'starlingx-discuss at lists.starlingx.io' ; Rowsell, Brent Cc: Chen, Tingjie ; Sun, Austin ; Qi, Mingyuan Subject: RE: ceph containerization patch review Hi Frank & Brent For rook manage configuration, after introduce rook-ceph, current ceph cluster deployed by puppet will keep or be removed? If removed, containerized ceph cluster deployed by rook-ceph will take the role of provisioner for stx-openstack. If keeps, helm chart rbd-provisioner in platform-integ-app also keeps and takes the role of provisioner for stx-openstack. Containerized ceph cluster deployed by rook-ceph only serve as csi provider for k8s. BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, February 10, 2020 11:47 PM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan > Subject: RE: ceph containerization patch review Hi Frank: As synced with Tingjie, this is my understanding for Rook manage the configuration instead of sysinv. 1, Remove ceph config and status query from sysinv 2, create another tool, like rook-client to launch and provision ceph cluster 3, one helm plugin like rbd-provision, which depends on newly created tool BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Saturday, February 8, 2020 4:16 AM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: ceph containerization patch review Martin: Thanks for posting your reviews and the update on the current status for this feature. I was unable to attend the containerization meeting this week so wasn't able to have Tingjie or you give an update on the open actions for the feature. From the Jan 14 minutes [1] one of the actions is to determine "how can you have Rook do all the configuration and not have sysinv involved" For now I suggest you add an additional item to your Tasks to do list to identify a design that does not require sysinv for the configuration and instead has Rook manage the configuration. I would like to ask that we discuss further at the next containerization meeting and if possible review a proposal from yourself and Austin for this item. Frank [1] https://etherpad.openstack.org/p/stx-containerization From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Thursday, February 06, 2020 11:02 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] ceph containerization patch review Hi folks I enabled containerized ceph cluster with simplex. You can begin to review my patch. I propose to build an image and deploy a simplex system with these patch to check. https://review.opendev.org/#/c/681457/ https://review.opendev.org/#/c/687340/ https://review.opendev.org/#/c/706256/ https://review.opendev.org/#/c/699557/ https://review.opendev.org/#/c/699556/ And I know there is other story, like remove ceph as default backend storage, maybe some conflict, we can discuss together. Tash Done: 1, disable native ceph cluster in ceph.pp 2, disable ceph daemon monitoring in service manager 3, add rook-ceph helm chart to launch ceph cluster 4, add override in stx-config to generate override with starlingx system config 5, sysinv add label in provision stage, to make containerized ceph mon and ceph mgr on designed host 6, add rook-ceph-provisioner helm chart to generate storage class, secret, config and pool for stx-application 7, enabled stx-openstack with containerized ceph 8, update ceph wrapper in stx-config to set or get containerized ceph cluster All these tasks done is enabled with simplex only. Task to do: 1, enable add osd runtime, after system provisioned 2, fix know issue, if system reboot, ceph cluster launch fail 3, enable bluestore and filestore, currently there is only bluestore 4, enable multi-node and duplex 5, enable swift with containerized ceph 6, enable fm alarm for containerized ceph 7, check backup and restore for containerized ceph 8, check system upgrade or how to transit from native ceph cluster to containerized ceph cluster 9, code cleanup 10, update unit test in stx-config BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Feb 18 16:36:28 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 11:36:28 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_repo_sync - Build # 697 - Failure! Message-ID: <1809193221.779.1582043789015.JavaMail.javamailuser@localhost> Project: STX_repo_sync Build #: 697 Status: Failure Timestamp: 20200218T163616Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T163601Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T163601Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200218T163601Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Tue Feb 18 16:36:31 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 11:36:31 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 426 - Still Failing! In-Reply-To: <1583583699.774.1581984441112.JavaMail.javamailuser@localhost> References: <1583583699.774.1581984441112.JavaMail.javamailuser@localhost> Message-ID: <592365927.782.1582043792176.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 426 Status: Still Failing Timestamp: 20200218T163601Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T163601Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From build.starlingx at gmail.com Tue Feb 18 16:48:07 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 11:48:07 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 427 - Still Failing! In-Reply-To: <215864256.780.1582043789856.JavaMail.javamailuser@localhost> References: <215864256.780.1582043789856.JavaMail.javamailuser@localhost> Message-ID: <1327296913.787.1582044488619.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 427 Status: Still Failing Timestamp: 20200218T163656Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T163656Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From build.starlingx at gmail.com Tue Feb 18 17:04:20 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 12:04:20 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 428 - Still Failing! In-Reply-To: <703655336.785.1582044486345.JavaMail.javamailuser@localhost> References: <703655336.785.1582044486345.JavaMail.javamailuser@localhost> Message-ID: <1869835823.791.1582045461126.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 428 Status: Still Failing Timestamp: 20200218T165551Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T165551Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From Ghada.Khalil at windriver.com Tue Feb 18 17:10:22 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 18 Feb 2020 17:10:22 +0000 Subject: [Starlingx-discuss] Status update: distro.openstack features In-Reply-To: <384edcfa-ea20-af6d-ce3c-b33bcde0d2a0@intel.com> References: <151EE31B9FCCA54397A757BC674650F0C1671BE2@ALA-MBD.corp.ad.wrs.com> <384edcfa-ea20-af6d-ce3c-b33bcde0d2a0@intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0C16730CC@ALA-MBD.corp.ad.wrs.com> Hi Yong, Thanks for the update. I've added the stx-discuss mailing list to give visibility to the community on the progress. In the StarlingX release meeting on Feb 13, Brent and Saul suggested that the distro-openstack team looks at containerizing the openstack clients in order to eliminate the direct dependency on CentOS 8. Regards, Ghada -----Original Message----- From: Yong Hu [mailto:yong.hu at intel.com] Sent: Thursday, February 13, 2020 6:14 AM To: Khalil, Ghada; 张鲲鹏 Cc: Jones, Bruce E; Zvonar, Bill; Shuquan Huang; yong.hu at intel.com Subject: Re: Status update: distro.openstack features +Kunpeng and Shuquan. Hi Ghada, For OpenStack containerized services upgrade, folks @99Cloud have signed up on this task. By far, they are doing some experiments and tests to practice the HOW-TO, and have made some progress. Right now "U" in under development in OpenStack master, and we should be able to start with master branch. So, I am going to settle down the execution plan in following 1~2 weeks with Kunpeng. So, please stay tuned and we will lay out the plan with a bit more details in next community meeting @WW09. About OpenStack clients and 3 services on host, the situation is different from those containerized services. 1. By far, CentOS 8 repo has not released the base packages (RPMs and SRPMs) yet. 2. It said CentOS 8 will only take "U" (but not support legacy versions, like Stein or Train). As well looking at the release plan of "U" itself (May 11 - May 15) at [0], very likely CentOS 8 base packages for "U" won't be available until June or even later. 3. if CentOS 8 packages for OpenStack "U" clients and 3 services cannot meet stx 4.0 release, we have to keep the current packages (Stein versions) from CentOS 7 repo for stx.4.0, and then if necessary switch to "U" (directly jumping from Stein to Ussuri, skipping Train) in 4.0 maintenance release time window. Team has done the analysis about how-to, and roughly 2 weeks should be enough to work out patches for review, after CentOS 8 repo release the packages. [0] Ussuri plan: https://releases.openstack.org/ussuri/schedule.html regards, Yong On 2020/2/13 7:07 AM, Khalil, Ghada wrote: > Hi Yong, > > Can you provide a status update by email on the following > distro.openstack features for the release planning meeting? > > -Upversion Openstack to Ussuris release > > -Upversion Openstack services used by flock components on host > > I checked the etherpad, but there isn’t info regarding the status of > the features, dependencies or the next steps. > > Thanks, > > Ghada > From build.starlingx at gmail.com Tue Feb 18 17:18:19 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 12:18:19 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 429 - Still Failing! In-Reply-To: <1849313752.789.1582045458855.JavaMail.javamailuser@localhost> References: <1849313752.789.1582045458855.JavaMail.javamailuser@localhost> Message-ID: <576271763.795.1582046300025.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 429 Status: Still Failing Timestamp: 20200218T170942Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T170942Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Tue Feb 18 17:21:01 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 12:21:01 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 430 - Still Failing! In-Reply-To: <645318958.793.1582046297749.JavaMail.javamailuser@localhost> References: <645318958.793.1582046297749.JavaMail.javamailuser@localhost> Message-ID: <730065174.799.1582046462618.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 430 Status: Still Failing Timestamp: 20200218T172032Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T172032Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Tue Feb 18 17:31:01 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 12:31:01 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 431 - Still Failing! In-Reply-To: <320371743.797.1582046460262.JavaMail.javamailuser@localhost> References: <320371743.797.1582046460262.JavaMail.javamailuser@localhost> Message-ID: <1874081194.803.1582047062744.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 431 Status: Still Failing Timestamp: 20200218T173032Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T173032Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Tue Feb 18 17:57:52 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 12:57:52 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 432 - Still Failing! In-Reply-To: <1475371815.801.1582047060505.JavaMail.javamailuser@localhost> References: <1475371815.801.1582047060505.JavaMail.javamailuser@localhost> Message-ID: <921194253.807.1582048673205.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 432 Status: Still Failing Timestamp: 20200218T175722Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T175722Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Tue Feb 18 18:00:52 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 13:00:52 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 433 - Still Failing! In-Reply-To: <949046348.805.1582048670590.JavaMail.javamailuser@localhost> References: <949046348.805.1582048670590.JavaMail.javamailuser@localhost> Message-ID: <1332097847.811.1582048852879.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 433 Status: Still Failing Timestamp: 20200218T180022Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T180022Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Tue Feb 18 18:18:17 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 13:18:17 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 434 - Still Failing! In-Reply-To: <1029130620.809.1582048850489.JavaMail.javamailuser@localhost> References: <1029130620.809.1582048850489.JavaMail.javamailuser@localhost> Message-ID: <244778083.815.1582049898632.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 434 Status: Still Failing Timestamp: 20200218T181748Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T181748Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Tue Feb 18 18:32:43 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 13:32:43 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 435 - Still Failing! In-Reply-To: <1843780225.813.1582049896109.JavaMail.javamailuser@localhost> References: <1843780225.813.1582049896109.JavaMail.javamailuser@localhost> Message-ID: <763108749.819.1582050764840.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 435 Status: Still Failing Timestamp: 20200218T182548Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T182548Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Tue Feb 18 18:46:45 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 13:46:45 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 436 - Still Failing! In-Reply-To: <1947661604.817.1582050762188.JavaMail.javamailuser@localhost> References: <1947661604.817.1582050762188.JavaMail.javamailuser@localhost> Message-ID: <1003868233.823.1582051606199.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 436 Status: Still Failing Timestamp: 20200218T183823Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T183823Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From build.starlingx at gmail.com Tue Feb 18 19:06:28 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 14:06:28 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 437 - Still Failing! In-Reply-To: <1376942318.821.1582051603815.JavaMail.javamailuser@localhost> References: <1376942318.821.1582051603815.JavaMail.javamailuser@localhost> Message-ID: <856876858.827.1582052789787.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 437 Status: Still Failing Timestamp: 20200218T185658Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T185658Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From Frank.Miller at windriver.com Tue Feb 18 21:25:49 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 18 Feb 2020 21:25:49 +0000 Subject: [Starlingx-discuss] StarlingX Weekly Build Meeting Changed to Thurs 7am Pacific/3pm GMT Message-ID: StarlingX Community: In order to allow more participation at the weekly build meeting I have moved this meeting one hour earlier to 7am Pacific/10am Easter/3pm GMT/11pm China. I could not find an earlier available timeslot but hopeful this helps. The main weekly call schedule [1] has been updated. Frank [1] https://wiki.openstack.org/wiki/Starlingx/Meetings -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Feb 18 22:06:10 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 17:06:10 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_publish - Build # 588 - Failure! Message-ID: <214968911.831.1582063571895.JavaMail.javamailuser@localhost> Project: STX_publish Build #: 588 Status: Failure Timestamp: 20200218T220504Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T190918Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200218T190918Z OS: centos PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T190918Z/logs TIMESTAMP: 20200218T190918Z PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/20200218T190918Z/inputs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200218T190918Z/logs MASTER_JOB_NAME: STX_build_master_master LAYER: PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20200218T190918Z/outputs MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos From build.starlingx at gmail.com Tue Feb 18 22:06:14 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 17:06:14 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 438 - Still Failing! In-Reply-To: <1303604525.825.1582052787346.JavaMail.javamailuser@localhost> References: <1303604525.825.1582052787346.JavaMail.javamailuser@localhost> Message-ID: <823223828.834.1582063575108.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 438 Status: Still Failing Timestamp: 20200218T190918Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T190918Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From Ian.Jolliffe at windriver.com Tue Feb 18 22:16:47 2020 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Tue, 18 Feb 2020 22:16:47 +0000 Subject: [Starlingx-discuss] [TSC] Minutes 2/12 Message-ID: <12F58B9B-DB15-48EF-8749-DA2D2366C1F8@windriver.com> Hi All; Please see below. Reminder the TSC meeting is now on Wednesday’s. STX CNCF compliance - next steps * Ildiko to look after the form. * Results are for 1.16 Number of repos * currently 28 repos * allows independent build * are there areas to collapse? * Nothing planned here for now Hand-on workshop plans in 2020 - Vancouver? * more about collaborative sessions * likely to be smaller than a regular summit * might not be the right place for a hands on workshop and might not have space * more experienced developers expected. Vancouver - PTG and OpenDev - space needs - 1 day – confirmed for StarlingX Berlin - end of October is the regular summit * this could be the right location for a hands on workshop Other locations? Open Infra Days in other global locations Nordic, London, China, Canada Regards; Ian -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Feb 19 00:01:34 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 19 Feb 2020 00:01:34 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Feb 13/2020 Message-ID: <151EE31B9FCCA54397A757BC674650F0C1673446@ALA-MBD.corp.ad.wrs.com> Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Test Team Update - Bruce was unable to join the meeting; will get an update next week. stx.4.0 - Feature Plans: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 - Layered Build - Team is not able to accomodate all the sanity requests for layered build in addition to the regular master sanity - Right now, starting with an AIO-SX virtual sanity for layered build. - Once that is successful, we'll request that all sanities move to layered build. - Once all layered buid sanities are successful, layered build with become - Openstack Train Rebase - Update from Yong by email on Feb 13 - 99Cloud is taking on the openstack containerized services upgrade. They are currently ramping up & following the how-to. Expect to share plan in 1-2wks (End of Feb). - For host services (openstack clients & 3 services on host), no CentOS8 packages are available yet and will likely not be available for the Ussuris release until June or later. - Saul and Brent suggested looking at containerizing the openstack clients to break dependency on CentOS8 - Kata Containers - What are the next steps for this item? - Frank to follow up in the next containerization meeting - CentOS 8 - Team is currently focused on the kernel and drivers/external modules with the new gcc as the first priority. stx.2.0.2 - Branch: https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.2.0 - Open Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2.0 - Still waiting for nova PR: https://github.com/starlingx-staging/stx-nova/pull/27 - Yong recommended that the code be merged; waiting on Dean to give the go-ahead - Merge of fix for https://bugs.launchpad.net/starlingx/+bug/1853017 is also in progress as recommended by Yong Hu - Date TBD depending on test team ramp / plans stx.3.0.1 - Branch: https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.3.0 - Open Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.3.0 - Developers have been active in cherry-picking required fixes once they are merged in stx master. - Date TBD depending on test team ramp / plans Meeting Cadence - Agreed to reduce the meeting duration to 30mins, but keep weekly for now. - Request that PLs who cannot attend provide weekly updates by email or directly in the feature google sheet From Ghada.Khalil at windriver.com Wed Feb 19 00:49:49 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 19 Feb 2020 00:49:49 +0000 Subject: [Starlingx-discuss] Weekly StarlingX Release meeting Message-ID: <151EE31B9FCCA54397A757BC674650F0C16734B8@ALA-MBD.corp.ad.wrs.com> Weekly meeting on Thursday 11AM PT / 1900 UTC Zoom Link: https://zoom.us/j/342730236 Meeting agenda/minutes: https://etherpad.openstack.org/p/stx-releases -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1735 bytes Desc: not available URL: From build.starlingx at gmail.com Wed Feb 19 01:30:33 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 20:30:33 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_base_image - Build # 172 - Failure! Message-ID: <1764059340.838.1582075834550.JavaMail.javamailuser@localhost> Project: STX_build_docker_base_image Build #: 172 Status: Failure Timestamp: 20200219T012949Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T221309Z/logs -------------------------------------------------------------------------------- Parameters HOST_PORT: 80 MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200218T221309Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root BASE_VERSION: master-stable-20200218T221309Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T221309Z/logs REGISTRY_USERID: slittlewrs HOST: build.starlingx.cengn.ca PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200218T221309Z/logs OS_VERSION: 7.5.1804 BUILD_STREAM: stable REGISTRY_ORG: starlingx BASE_LATEST_TAG: master-stable-latest PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/20200218T221309Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20200218T221309Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Wed Feb 19 01:30:36 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 20:30:36 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 166 - Still Failing! In-Reply-To: <575667311.719.1581400548023.JavaMail.javamailuser@localhost> References: <575667311.719.1581400548023.JavaMail.javamailuser@localhost> Message-ID: <957109220.841.1582075837807.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 166 Status: Still Failing Timestamp: 20200219T012944Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T221309Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200218T221309Z 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/20200218T221309Z/logs MASTER_BUILD_NUMBER: 439 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200218T221309Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos PUBLISH_TIMESTAMP: 20200218T221309Z DOCKER_BUILD_ID: jenkins-master-20200218T221309Z-builder TIMESTAMP: 20200218T221309Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/20200218T221309Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20200218T221309Z/outputs From build.starlingx at gmail.com Wed Feb 19 01:30:40 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 18 Feb 2020 20:30:40 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 439 - Still Failing! In-Reply-To: <1320657491.832.1582063572768.JavaMail.javamailuser@localhost> References: <1320657491.832.1582063572768.JavaMail.javamailuser@localhost> Message-ID: <1086098734.844.1582075841068.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 439 Status: Still Failing Timestamp: 20200218T221309Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200218T221309Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From haochuan.z.chen at intel.com Wed Feb 19 04:53:08 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Wed, 19 Feb 2020 04:53:08 +0000 Subject: [Starlingx-discuss] ceph containerization patch review In-Reply-To: References: <56829C2A36C2E542B0CCB9854828E4D8562A76F5@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A7E32@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A9371@CDSMSX102.ccr.corp.intel.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D8562A97A4@CDSMSX102.ccr.corp.intel.com> Hi folks Answer the question, with only k8s, how to deploy rook. $ helm-upload stx-platform rook-ceph-0.1.0.tga $ helm install stx-platform/rook-ceph -n rook-ceph-cluster -n kube-system -f value.yaml BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank Sent: Tuesday, February 18, 2020 10:06 PM To: Chen, Haochuan Z ; 'starlingx-discuss at lists.starlingx.io' ; Rowsell, Brent Cc: Chen, Tingjie ; Sun, Austin ; Qi, Mingyuan ; Church, Robert Subject: RE: ceph containerization patch review +Bob who is the containers TL From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Monday, February 17, 2020 8:46 AM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan > Subject: RE: ceph containerization patch review Hi Frank & Brent For rook manage configuration, after introduce rook-ceph, current ceph cluster deployed by puppet will keep or be removed? If removed, containerized ceph cluster deployed by rook-ceph will take the role of provisioner for stx-openstack. If keeps, helm chart rbd-provisioner in platform-integ-app also keeps and takes the role of provisioner for stx-openstack. Containerized ceph cluster deployed by rook-ceph only serve as csi provider for k8s. BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, February 10, 2020 11:47 PM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan > Subject: RE: ceph containerization patch review Hi Frank: As synced with Tingjie, this is my understanding for Rook manage the configuration instead of sysinv. 1, Remove ceph config and status query from sysinv 2, create another tool, like rook-client to launch and provision ceph cluster 3, one helm plugin like rbd-provision, which depends on newly created tool BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Saturday, February 8, 2020 4:16 AM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: ceph containerization patch review Martin: Thanks for posting your reviews and the update on the current status for this feature. I was unable to attend the containerization meeting this week so wasn't able to have Tingjie or you give an update on the open actions for the feature. From the Jan 14 minutes [1] one of the actions is to determine "how can you have Rook do all the configuration and not have sysinv involved" For now I suggest you add an additional item to your Tasks to do list to identify a design that does not require sysinv for the configuration and instead has Rook manage the configuration. I would like to ask that we discuss further at the next containerization meeting and if possible review a proposal from yourself and Austin for this item. Frank [1] https://etherpad.openstack.org/p/stx-containerization From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Thursday, February 06, 2020 11:02 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] ceph containerization patch review Hi folks I enabled containerized ceph cluster with simplex. You can begin to review my patch. I propose to build an image and deploy a simplex system with these patch to check. https://review.opendev.org/#/c/681457/ https://review.opendev.org/#/c/687340/ https://review.opendev.org/#/c/706256/ https://review.opendev.org/#/c/699557/ https://review.opendev.org/#/c/699556/ And I know there is other story, like remove ceph as default backend storage, maybe some conflict, we can discuss together. Tash Done: 1, disable native ceph cluster in ceph.pp 2, disable ceph daemon monitoring in service manager 3, add rook-ceph helm chart to launch ceph cluster 4, add override in stx-config to generate override with starlingx system config 5, sysinv add label in provision stage, to make containerized ceph mon and ceph mgr on designed host 6, add rook-ceph-provisioner helm chart to generate storage class, secret, config and pool for stx-application 7, enabled stx-openstack with containerized ceph 8, update ceph wrapper in stx-config to set or get containerized ceph cluster All these tasks done is enabled with simplex only. Task to do: 1, enable add osd runtime, after system provisioned 2, fix know issue, if system reboot, ceph cluster launch fail 3, enable bluestore and filestore, currently there is only bluestore 4, enable multi-node and duplex 5, enable swift with containerized ceph 6, enable fm alarm for containerized ceph 7, check backup and restore for containerized ceph 8, check system upgrade or how to transit from native ceph cluster to containerized ceph cluster 9, code cleanup 10, update unit test in stx-config BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: values.yaml Type: application/octet-stream Size: 360 bytes Desc: values.yaml URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: rook-ceph-0.1.0.tgz Type: application/x-compressed Size: 10971 bytes Desc: rook-ceph-0.1.0.tgz URL: From haochuan.z.chen at intel.com Wed Feb 19 04:57:18 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Wed, 19 Feb 2020 04:57:18 +0000 Subject: [Starlingx-discuss] ceph containerization patch review In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D8562A97A4@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D8562A76F5@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A7E32@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A9371@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A97A4@CDSMSX102.ccr.corp.intel.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D8562A97D3@CDSMSX102.ccr.corp.intel.com> After helm install, you can assign label to nodes, "ceph-mon-placement=enabled", "ceph-mgr-placement=enabled" Then pod with ceph-mon and ceph-mgr will deploy on the label assigned node. Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Wednesday, February 19, 2020 12:53 PM To: 'Miller, Frank' ; 'starlingx-discuss at lists.starlingx.io' ; Rowsell, Brent ; 'Greg.Waines at windriver.com' Cc: Chen, Tingjie ; Sun, Austin ; Qi, Mingyuan ; Church, Robert Subject: RE: ceph containerization patch review Hi folks Answer the question, with only k8s, how to deploy rook. $ helm-upload stx-platform rook-ceph-0.1.0.tga $ helm install stx-platform/rook-ceph -n rook-ceph-cluster -n kube-system -f value.yaml BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Tuesday, February 18, 2020 10:06 PM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan >; Church, Robert > Subject: RE: ceph containerization patch review +Bob who is the containers TL From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Monday, February 17, 2020 8:46 AM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan > Subject: RE: ceph containerization patch review Hi Frank & Brent For rook manage configuration, after introduce rook-ceph, current ceph cluster deployed by puppet will keep or be removed? If removed, containerized ceph cluster deployed by rook-ceph will take the role of provisioner for stx-openstack. If keeps, helm chart rbd-provisioner in platform-integ-app also keeps and takes the role of provisioner for stx-openstack. Containerized ceph cluster deployed by rook-ceph only serve as csi provider for k8s. BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, February 10, 2020 11:47 PM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan > Subject: RE: ceph containerization patch review Hi Frank: As synced with Tingjie, this is my understanding for Rook manage the configuration instead of sysinv. 1, Remove ceph config and status query from sysinv 2, create another tool, like rook-client to launch and provision ceph cluster 3, one helm plugin like rbd-provision, which depends on newly created tool BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Saturday, February 8, 2020 4:16 AM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: ceph containerization patch review Martin: Thanks for posting your reviews and the update on the current status for this feature. I was unable to attend the containerization meeting this week so wasn't able to have Tingjie or you give an update on the open actions for the feature. From the Jan 14 minutes [1] one of the actions is to determine "how can you have Rook do all the configuration and not have sysinv involved" For now I suggest you add an additional item to your Tasks to do list to identify a design that does not require sysinv for the configuration and instead has Rook manage the configuration. I would like to ask that we discuss further at the next containerization meeting and if possible review a proposal from yourself and Austin for this item. Frank [1] https://etherpad.openstack.org/p/stx-containerization From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Thursday, February 06, 2020 11:02 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] ceph containerization patch review Hi folks I enabled containerized ceph cluster with simplex. You can begin to review my patch. I propose to build an image and deploy a simplex system with these patch to check. https://review.opendev.org/#/c/681457/ https://review.opendev.org/#/c/687340/ https://review.opendev.org/#/c/706256/ https://review.opendev.org/#/c/699557/ https://review.opendev.org/#/c/699556/ And I know there is other story, like remove ceph as default backend storage, maybe some conflict, we can discuss together. Tash Done: 1, disable native ceph cluster in ceph.pp 2, disable ceph daemon monitoring in service manager 3, add rook-ceph helm chart to launch ceph cluster 4, add override in stx-config to generate override with starlingx system config 5, sysinv add label in provision stage, to make containerized ceph mon and ceph mgr on designed host 6, add rook-ceph-provisioner helm chart to generate storage class, secret, config and pool for stx-application 7, enabled stx-openstack with containerized ceph 8, update ceph wrapper in stx-config to set or get containerized ceph cluster All these tasks done is enabled with simplex only. Task to do: 1, enable add osd runtime, after system provisioned 2, fix know issue, if system reboot, ceph cluster launch fail 3, enable bluestore and filestore, currently there is only bluestore 4, enable multi-node and duplex 5, enable swift with containerized ceph 6, enable fm alarm for containerized ceph 7, check backup and restore for containerized ceph 8, check system upgrade or how to transit from native ceph cluster to containerized ceph cluster 9, code cleanup 10, update unit test in stx-config BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mingyuan.qi at intel.com Wed Feb 19 08:40:52 2020 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Wed, 19 Feb 2020 08:40:52 +0000 Subject: [Starlingx-discuss] ceph containerization patch review In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D8562A97D3@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D8562A76F5@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A7E32@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A9371@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A97A4@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A97D3@CDSMSX102.ccr.corp.intel.com> Message-ID: Brent & Bob & Frank, >From last night's meeting, we discussed lots of ceph containerization issues. We had some progress, but because of the time limitation, I believe we are not fully on the same page of some issues. To have a clear picture of the issues, I'd like to describe these in detail. Basically there're 2 issues to be addressed, 1. How to decouple sysinv from rook/ceph? 2. How to design a storage migration strategy when a user currently running stx 3.0 wants to upgrade to 4.0. 1. How to decouple sysinv from rook/ceph? In stx 3.0, sysinv is tightly coupled with ceph by communicating with python-cephclient. The original idea from Tingjie's BP[0] is to replace python-cephclient by python-rookclient, without changing the current logic of ceph configuration. The decoupling of sysinv and rook/ceph was mentioned in containerize meeting[1] on Jan 14th and Martin(Haochuan) is not in that meeting. To let folks have a clear view, I have some questions about decoupling: a. When talking about decoupling, does it mean all the ceph configuration would only be set through overrides generated by sysinv helm plugin? b. Does sysinv storage command like host-stor-*/storage-tier-* deprecated along with its sysinv conductor code after rook enabled? c. Can a sysadmin operate rook without sysinv overrides? If so, how to guarantee the previous restrictions of storage policy/rules, like 3 monitors, like osds not locates on worker node. d. Back to sysinv overrides, what's the mechanism of generating runtime overrides to add an osd or a node or change crushmap rules to the ceph cluster? Through customer override? e. Is a command line tool other than cgcs-client needed for sysadmin(if sysinv conductor is not involved)? I believe the command line is more friendly than writing a yaml type override to update ceph cluster. f. What role starlingx plays in storage management? To perform easier integration of rook and let rook manages storage, or to be the manipulator of rook? 2. How to design a storage migration strategy when a user currently running stx 3.0 wants to upgrade to 4.0. We do face this question about how to migration current ceph to rook. However we don't think it blocks the previous issue that the users install stx4.0 from scratch doesn't encounter migration issue. I prefer addressing these 2 issues independently. I think the migration strategy is not an easy implementation because it's about the safety of customer's data. We'd like to follow a standard procedure from upstream to lower the risk of migration failure. Unfortunately, we haven't seen a best practice from rook community yet. To continue this work, I would like to align with you about some points: - All the services using ceph should be down during the migration. - The daemons of ceph running on host will be removed after migration. - What's the interface of migration? A tool or a script or instructions documented? - The implementation of migration should not go along with rook-ceph application. I described the 2 major issues in detail in current ceph containerization task for Martin's reference. Hopefully my questions could be addressed by WR folks to make our communication more effective and efficient. Tingjie, please correct me if I have some misunderstandings since you are the first prim of ceph containerization who knows the full context well. [0] https://opendev.org/starlingx/specs/src/branch/master/doc/source/specs/stx-3.0/approved/containerization-2005527-containerized-ceph-deployment-and-provision.rst [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007485.html Mingyuan From: Chen, Haochuan Z Sent: Wednesday, February 19, 2020 12:57 To: Miller, Frank ; 'starlingx-discuss at lists.starlingx.io' ; Rowsell, Brent ; Greg.Waines at windriver.com Cc: Chen, Tingjie ; Sun, Austin ; Qi, Mingyuan ; Church, Robert Subject: RE: ceph containerization patch review After helm install, you can assign label to nodes, "ceph-mon-placement=enabled", "ceph-mgr-placement=enabled" Then pod with ceph-mon and ceph-mgr will deploy on the label assigned node. Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Wednesday, February 19, 2020 12:53 PM To: 'Miller, Frank' >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent >; 'Greg.Waines at windriver.com' > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan >; Church, Robert > Subject: RE: ceph containerization patch review Hi folks Answer the question, with only k8s, how to deploy rook. $ helm-upload stx-platform rook-ceph-0.1.0.tga $ helm install stx-platform/rook-ceph -n rook-ceph-cluster -n kube-system -f value.yaml BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Tuesday, February 18, 2020 10:06 PM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan >; Church, Robert > Subject: RE: ceph containerization patch review +Bob who is the containers TL From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Monday, February 17, 2020 8:46 AM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan > Subject: RE: ceph containerization patch review Hi Frank & Brent For rook manage configuration, after introduce rook-ceph, current ceph cluster deployed by puppet will keep or be removed? If removed, containerized ceph cluster deployed by rook-ceph will take the role of provisioner for stx-openstack. If keeps, helm chart rbd-provisioner in platform-integ-app also keeps and takes the role of provisioner for stx-openstack. Containerized ceph cluster deployed by rook-ceph only serve as csi provider for k8s. BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, February 10, 2020 11:47 PM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan > Subject: RE: ceph containerization patch review Hi Frank: As synced with Tingjie, this is my understanding for Rook manage the configuration instead of sysinv. 1, Remove ceph config and status query from sysinv 2, create another tool, like rook-client to launch and provision ceph cluster 3, one helm plugin like rbd-provision, which depends on newly created tool BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Saturday, February 8, 2020 4:16 AM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: ceph containerization patch review Martin: Thanks for posting your reviews and the update on the current status for this feature. I was unable to attend the containerization meeting this week so wasn't able to have Tingjie or you give an update on the open actions for the feature. From the Jan 14 minutes [1] one of the actions is to determine "how can you have Rook do all the configuration and not have sysinv involved" For now I suggest you add an additional item to your Tasks to do list to identify a design that does not require sysinv for the configuration and instead has Rook manage the configuration. I would like to ask that we discuss further at the next containerization meeting and if possible review a proposal from yourself and Austin for this item. Frank [1] https://etherpad.openstack.org/p/stx-containerization From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Thursday, February 06, 2020 11:02 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] ceph containerization patch review Hi folks I enabled containerized ceph cluster with simplex. You can begin to review my patch. I propose to build an image and deploy a simplex system with these patch to check. https://review.opendev.org/#/c/681457/ https://review.opendev.org/#/c/687340/ https://review.opendev.org/#/c/706256/ https://review.opendev.org/#/c/699557/ https://review.opendev.org/#/c/699556/ And I know there is other story, like remove ceph as default backend storage, maybe some conflict, we can discuss together. Tash Done: 1, disable native ceph cluster in ceph.pp 2, disable ceph daemon monitoring in service manager 3, add rook-ceph helm chart to launch ceph cluster 4, add override in stx-config to generate override with starlingx system config 5, sysinv add label in provision stage, to make containerized ceph mon and ceph mgr on designed host 6, add rook-ceph-provisioner helm chart to generate storage class, secret, config and pool for stx-application 7, enabled stx-openstack with containerized ceph 8, update ceph wrapper in stx-config to set or get containerized ceph cluster All these tasks done is enabled with simplex only. Task to do: 1, enable add osd runtime, after system provisioned 2, fix know issue, if system reboot, ceph cluster launch fail 3, enable bluestore and filestore, currently there is only bluestore 4, enable multi-node and duplex 5, enable swift with containerized ceph 6, enable fm alarm for containerized ceph 7, check backup and restore for containerized ceph 8, check system upgrade or how to transit from native ceph cluster to containerized ceph cluster 9, code cleanup 10, update unit test in stx-config BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Feb 19 14:06:29 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 19 Feb 2020 14:06:29 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Feb 19, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B99AEE@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of the TSC/Community call coming up shortly [2]. We'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200219T1500 -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Wed Feb 19 15:15:45 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 19 Feb 2020 15:15:45 +0000 Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 2/19/2020 Message-ID: Hi All: Thanks join the call. MoM for 2/19 meeting: - Prb update (JITStack-Wesley) --- build time any feedback from Build Team http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007788.html , currently no feedback from build team. - CentOS8 upgrade (Austin/Shuicheng) - incremental upgrade on master : * mock support (old gcc and new gcc ) , no solution yet. http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007769.html * new gcc will cause el7 rpm conflict or build failure. * std kernel build status update (kernel 4.18.0-80.11.2 on master env (gcc 4.8 +python2) do some minor changes , this kernel 4.18.0-80.11.2 built by gcc 4.8 , kernel can be built successfully AR: summary the changes and send to mail list. * rt kernel build status (kernel 4.18.0-147.3.1.rt24.96) , * 3.10 patch rebase , config update are remaining * python3 enable on master ? which is the preferred repo to upgrade to python3 besides NFV start this task now. * Ussuri host openstack (oslo , keystone , barbican , horizon and openstack client ) upgrade ? plan openstack client containerization no resource assign , some early study have been done by Stephan, timeline for Ussuri official release on CentOS8 should be risk . *the target , plan and goal on stx 4.0 feature ? target : end of March to finish kernel(std and rt) upgrade depends on centos8 rpms readiness (openstack), the minimum target is kernel upgrade . - any new stx.4.0 feature depends on kernel 4.18 ? - when will involve test team - how about centos8 branch ? shall we continue if we fully switch to incremental upgrade. keep centos8 branch, and do test on some user space rpms upgrade. - Vista Creek (FPGA card) support tarball/srpm issue need to be fixed by intel us team OPAE iavf and i40e driver . new driver integrated into stx. ---done . SRIOV device plugin --- no feedback yet . https://github.com/intel/sriov-network-device-plugin/pull/196 - Open Thanks. BR Austin Sun. From scott.little at windriver.com Wed Feb 19 15:39:32 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 19 Feb 2020 10:39:32 -0500 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSNOiBQQlIgU3RhdHVzIENoZWNr?= In-Reply-To: <54c3f57e-912c-58c0-2520-a529335e2ed5@linux.intel.com> References: <5f55cb03-5360-3e11-fcc9-46f6dc24d6f8@linux.intel.com> <060f01d5db34$f5e38a50$e1aa9ef0$@jitstack.com> <42960858-5122-4de5-b4c9-6d5619f4d692@linux.intel.com> <54c3f57e-912c-58c0-2520-a529335e2ed5@linux.intel.com> Message-ID: <38c229c6-c7dc-d7dd-f4ca-43d17cb830bb@windriver.com> If I read this correctly, it's a fraction of a second per package.  I'm ok with that. Scott On 2020-02-17 1:18 a.m., Saul Wold wrote: > Scott, Don: > > Does the below information clarify these results and allow for the > next steps with the PBR Versioning being enabled for versioning the > Flock repos? > > On 2/12/20 7:39 AM, Saul Wold wrote: >> >> >> On 2/12/20 6:32 AM, Yang, Bin wrote: >>> Hi Saul, >>>     As you know, the build system patch [1] had introduced the pbr >>> command to generate pkg version. This should be the only effect on >>> the compile time of pbr enabled pkg. >>> >>>     Jitstack had tested command execution time. >>>     The result of "with pbr" should be the command execution time. >>> Please correct me if my understanding is wrong. >>>     But the result of "without pbr" should be "0". Build system will >>> not execute pbr command if it is not enabled. >> If your just instrumenting the "pbr execution time", then I guess >> then without pbr should be 0.  based on your comments during the >> Distro call, the build time with pbr enabled becomes noise in the >> minutes that it takes to do a build. >> >> It's just not clear from below what was being tested, I think this >> sort of clarifies things.  Let's get some feedback from the rest of >> the Build team (Scott, Don)? >> >> Thanks >>     Sau! >> >>> >>> >>> Thanks, >>> Bin >>> >>> [1]: https://review.opendev.org/#/c/691632/ >>> >>> -----Original Message----- >>> From: Saul Wold >>> Sent: Tuesday, February 4, 2020 23:09 >>> To: wesley.yang at jitstack.com; daniels.cai at jitstack.com; Yang, Bin >>> ; shangyakun at jitstack.com >>> Cc: Hu, Yong ; starlingx-discuss at lists.starlingx.io >>> Subject: Re: 回复: PBR Status Check >>> >>> >>> Wesley, Yakun: >>> >>> I hope you guys are doing OK with the restrictions and stay healthy! >>> >>> I did a review of the numbers that Yakun provide in a prior email >>> (summary here) >>> >>> Package Compile >>> timeconsumption                with pbr    without pbr >>> the first time                0.287s        0.301s >>> the second time                0.322s        0.351s >>> the third time                0.554s        0.235s >>> the fourth time( deb package)        0.299s        0.292s >>> >>> >>> Can you please provide more details about what your actual test >>> methodology (and/or scripts) was? >>> >>> I think at some-point it was suggested that 2 packages (python and >>> non-python) should be used. They should then be compiled / cleaned >>> in a loop of about 10-12 times to ensure any caches are cleared. >>> Then an average and deviation be determined. >>> >>> Thanks >>>      Sau! >>> >>> >>> >>> On 2/4/20 12:27 AM, wesley.yang at jitstack.com wrote: >>>> Hi Saul >>>> I'm working at home remotely at home for the Government's >>>> restriction, my colleagues are also working remotely or still on >>>> vacation. >>>> You may see that my colleagues Yakun has just sent the preliminary >>>> result to you, and he will do some more test and update later. >>>> >>>> Wesley >>>> >>>> -----邮件原件----- >>>> 发件人: Saul Wold >>>> 发送时间: 2020年2月4日 8:54 >>>> 收件人: wesley.yang at jitstack.com; daniels.cai at jitstack.com; Yang, Bin >>>> >>>> 抄送: Hu, Yong ; >>>> starlingx-discuss at lists.starlingx.io >>>> 主题: Re: PBR Status Check >>>> >>>> Hi Wesley, >>>> >>>> Following up on this, I am not sure what your working status is >>>> because of the Virus and various Gov't restrictions.  If you are >>>> working, can you give us an update on the Performance impact >>>> question I listed below. >>>> >>>> Thanks >>>>      Sau! >>>> >>>> >>>> On 1/22/20 10:14 AM, Saul Wold wrote: >>>>> >>>>> Hi All & Welcome Wesley, >>>>> >>>>> We have a new community member from JitStack starting to look at the >>>>> PBR work, here is some background for him. >>>>> >>>>> The PBR work was proposed via the StarlingX Feature Specification >>>>> process, see the Flock Versioning specification [0], this is based on >>>>> the OpenStack Python Build Reasonableness [1] and Semantic Versioning >>>>> (SemVer) [2] definition. >>>>> >>>>> One of the issues that we are trying to resolve is the impact of the >>>>> proposed change from Bin Yang to the time it takes to build a single >>>>> package with PBR before and after the change. Ideally this would be >>>>> done multiple times and provide the average along with the deviation. >>>>> This in an important part of the project in order for us to move >>>>> forward. >>>>> >>>>> Look forward to working with you. >>>>> >>>>> Sau! >>>>> >>>>> [0] >>>>> https://docs.starlingx.io/specs/specs/stx-3.0/approved/standardize_fl >>>>> o >>>>> ck_versioning.html >>>>> >>>>> [1] https://docs.openstack.org/pbr/latest/ >>>>> [2] https://docs.openstack.org/pbr/latest/user/semver.html >>>> >> >> _______________________________________________ >> 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 Feb 19 15:49:57 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 19 Feb 2020 15:49:57 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Feb 19, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B99CB5@ALA-MBD.corp.ad.wrs.com> - Standing Topics - Sanity - working through some issues w/ the Monolithic build, expect to have them sorted by end of today - Scott will post an update - Nico will talk to Christopher re: the plan for running sanities on the 2 builds - Reviews - nothing this week - CentOS 8 - reviews to be reviewed, as usual - https://review.opendev.org/#/q/topic:centos8+(status:open)+AND+projects:starlingx/ - Austin: team is working towards completing the kernel upgrade some time in March --- details to follow - Saul: will open a discussion in the Build team re: setting up a CentOS 8 mirror & on demand feature branch builds - Topics for This Week - Election Closed: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007790.html - Meeting wiki page update - ACTION NEEDED: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007775.html - good updates, some minor updates still pending - Open Requests for Help - Kris: unassigned documentation tasks for r4 features - Bill will add these to the agenda for the release team meeting... - Starlingx/integ - https://storyboard.openstack.org/#!/story/2006711 - https://storyboard.openstack.org/#!/story/2006740 - https://storyboard.openstack.org/#!/story/2005496 - https://storyboard.openstack.org/#!/story/2006588 - Starlingx/config - https://storyboard.openstack.org/#!/story/2006781 - https://storyboard.openstack.org/#!/story/2006770 - https://storyboard.openstack.org/#!/story/2006145 - https://storyboard.openstack.org/#!/story/2006746 From: Zvonar, Bill Sent: Wednesday, February 19, 2020 9:06 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: Community (& TSC) Call (Feb 19, 2020) Hi all, reminder of the TSC/Community call coming up shortly [2]. We'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200219T1500 From maria.g.perez.ibarra at intel.com Wed Feb 19 17:17:31 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Wed, 19 Feb 2020 17:17:31 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200219 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-FEBRUARY-19 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhaolongqian456 at 163.com Sun Feb 9 04:32:33 2020 From: zhaolongqian456 at 163.com (Longqian Zhao) Date: Sun, 9 Feb 2020 12:32:33 +0800 (CST) Subject: [Starlingx-discuss] The data interface eth1000 cannot be modified when I configure compute-0 In-Reply-To: <9700A18779F35F49AF027300A49E7C7660929447@SHSMSX105.ccr.corp.intel.com> References: <19f153b3.1c3d.170226c3204.Coremail.zhaolongqian456@163.com> <9700A18779F35F49AF027300A49E7C7660929447@SHSMSX105.ccr.corp.intel.com> Message-ID: <7f11fe43.576b.1702838730a.Coremail.zhaolongqian456@163.com> Hi Shuichen, Based on your suggestions yesterday, I successfully set up StaringX. But when I access 10.10.10.3:80 using Firefox browser, the web page returned an "Invalid credentials." error information.Could you please help me? Thanks. My Environment: I install StarlingX in Virtual Environment. Reference documentation: https://docs.starlingx.io/deploy_install_guides/r1_release/controller_storage.html StarlingX version: 2018/10 stx-tools version: 2018/10 My Steps: 1. Install controller-0 succesfully. 2. Install compute-0 succesfully. 3. source /etc/nova/openrc in controller-0 4. keyring get CGCS admin 700626Zyt@ 5. Please see the following picture Best regards with you, Longqian 020-02-08 11:16:37, "Lin, Shuicheng" wrote: Hi, As Saul said, it is highly recommended you have a try with 3.0 Release, instead of 1.0 Release, which is too old and not maintained now. For your environment, with “host-port-list”, there are eth0 ~ eth3, no eth1000. So you should use eth2/eth3, instead of eth1000 as data interface. Best Regards Shuicheng From: Longqian Zhao Sent: Saturday, February 8, 2020 9:31 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] The data interface eth1000 cannot be modified when I configure compute-0 Hi , I According to https://docs.starlingx.io/deploy_install_guides/r1_release/controller_storage.html#id8 , the data interface eth1000 cannot be modified. Following is the detail informations about my issue. Could you please help me? Thanks. Brief Description ----------------- My Environment: I install StarlingX in Virtual Environment. StarlingX version: 2018/10 stx-tools version: 2018/10 Steps: 1. Install controller-0 succesfully. 2. Install compute-0. 3. source /etc/nova/openrc. 4. system host-port-list compute-0 +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ | 2b735378-dd09-43b3-929f-5ca110a35001 | eth0 | ethernet | 0000:02:01.0 | 0 | -1 | True | Virtio network device | | 45c95b31-23ec-4eb4-aefb-eb22133a60a9 | eth1 | ethernet | 0000:02:02.0 | 0 | -1 | True | Virtio network device | | 51f58dac-3f6e-486d-bd67-300b15942b80 | eth2 | ethernet | 0000:02:03.0 | 0 | -1 | True | Virtio network device | | 62b4a45b-b167-456b-8b31-41b21d45b0da | eth3 | ethernet | 0000:02:04.0 | 0 | -1 | True | Virtio network device | +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ 5. system host-if-modify -p providernet-a -c data compute-0 eth1000 (The following is the returned information:) Interface not found: host compute-0 if eth1000 Issues: ----------------- 1. I did not find the data interface after executing the command: system host-if-list compute-0 +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | provider networks | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ | b2642ea1-cf58-4bc7-92ab-bbfb374a04c3 | mgmt0 | platform | ethernet | None | [u'eth1'] | [] | [] | MTU=1500 | None | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ 2. I do not know how to use command "system host-if-add" to add data interface. Best regards with you, Longqian -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 109566 bytes Desc: not available URL: From shuicheng.lin at intel.com Sun Feb 9 05:01:13 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Sun, 9 Feb 2020 05:01:13 +0000 Subject: [Starlingx-discuss] The data interface eth1000 cannot be modified when I configure compute-0 In-Reply-To: <7f11fe43.576b.1702838730a.Coremail.zhaolongqian456@163.com> References: <19f153b3.1c3d.170226c3204.Coremail.zhaolongqian456@163.com> <9700A18779F35F49AF027300A49E7C7660929447@SHSMSX105.ccr.corp.intel.com> <7f11fe43.576b.1702838730a.Coremail.zhaolongqian456@163.com> Message-ID: <9700A18779F35F49AF027300A49E7C766092964C@SHSMSX105.ccr.corp.intel.com> Hi Longqian, Username should be "admin", not "wrsroot". Best Regards Shuicheng From: Longqian Zhao Sent: Sunday, February 9, 2020 12:33 PM To: Lin, Shuicheng Cc: starlingx-discuss at lists.starlingx.io Subject: Re:RE: [Starlingx-discuss] The data interface eth1000 cannot be modified when I configure compute-0 Hi Shuichen, Based on your suggestions yesterday, I successfully set up StaringX. But when I access 10.10.10.3:80 using Firefox browser, the web page returned an "Invalid credentials." error information.Could you please help me? Thanks. My Environment: I install StarlingX in Virtual Environment. Reference documentation: https://docs.starlingx.io/deploy_install_guides/r1_release/controller_storage.html StarlingX version: 2018/10 stx-tools version: 2018/10 My Steps: 1. Install controller-0 succesfully. 2. Install compute-0 succesfully. 3. source /etc/nova/openrc in controller-0 4. keyring get CGCS admin 700626Zyt@ 5. Please see the following picture [cid:image001.png at 01D5DF49.0018A740] Best regards with you, Longqian 020-02-08 11:16:37, "Lin, Shuicheng" > wrote: Hi, As Saul said, it is highly recommended you have a try with 3.0 Release, instead of 1.0 Release, which is too old and not maintained now. For your environment, with "host-port-list", there are eth0 ~ eth3, no eth1000. So you should use eth2/eth3, instead of eth1000 as data interface. Best Regards Shuicheng From: Longqian Zhao > Sent: Saturday, February 8, 2020 9:31 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] The data interface eth1000 cannot be modified when I configure compute-0 Hi , I According to https://docs.starlingx.io/deploy_install_guides/r1_release/controller_storage.html#id8 , the data interface eth1000 cannot be modified. Following is the detail informations about my issue. Could you please help me? Thanks. Brief Description ----------------- My Environment: I install StarlingX in Virtual Environment. StarlingX version: 2018/10 stx-tools version: 2018/10 Steps: 1. Install controller-0 succesfully. 2. Install compute-0. 3. source /etc/nova/openrc. 4. system host-port-list compute-0 +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ | uuid | name | type | pci address | device | processor | accelerated | device type | +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ | 2b735378-dd09-43b3-929f-5ca110a35001 | eth0 | ethernet | 0000:02:01.0 | 0 | -1 | True | Virtio network device | | 45c95b31-23ec-4eb4-aefb-eb22133a60a9 | eth1 | ethernet | 0000:02:02.0 | 0 | -1 | True | Virtio network device | | 51f58dac-3f6e-486d-bd67-300b15942b80 | eth2 | ethernet | 0000:02:03.0 | 0 | -1 | True | Virtio network device | | 62b4a45b-b167-456b-8b31-41b21d45b0da | eth3 | ethernet | 0000:02:04.0 | 0 | -1 | True | Virtio network device | +--------------------------------------+------+----------+--------------+--------+-----------+-------------+-----------------------+ 5. system host-if-modify -p providernet-a -c data compute-0 eth1000 (The following is the returned information:) Interface not found: host compute-0 if eth1000 Issues: ----------------- 1. I did not find the data interface after executing the command: system host-if-list compute-0 +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | provider networks | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ | b2642ea1-cf58-4bc7-92ab-bbfb374a04c3 | mgmt0 | platform | ethernet | None | [u'eth1'] | [] | [] | MTU=1500 | None | +--------------------------------------+-------+----------+----------+---------+-----------+----------+-------------+------------+-------------------+ 2. I do not know how to use command "system host-if-add" to add data interface. Best regards with you, Longqian -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 109566 bytes Desc: image001.png URL: From dharmakemo at gmail.com Mon Feb 17 02:20:56 2020 From: dharmakemo at gmail.com (dharma yusuf setiawan) Date: Mon, 17 Feb 2020 09:20:56 +0700 Subject: [Starlingx-discuss] Ask-Question Message-ID: i want to ask question, sorry bad english. i have installed dedicated storage but when i update host with worker personality, but when i check with command "system host-disk list" list does not appear could someone help me please -------------- next part -------------- An HTML attachment was scrubbed... URL: From kehao.zhu at jitstack.com Tue Feb 18 02:14:26 2020 From: kehao.zhu at jitstack.com (kehao.zhu at jitstack.com) Date: Tue, 18 Feb 2020 10:14:26 +0800 Subject: [Starlingx-discuss] PBR build performance test result Message-ID: <202002181014253248416@jitstack.com>+3BF77979FD6F7F07 Hi Saul: I made the PBR building performance test as bellow, please check and review the result in the attached file. 10 python + 10 non-python loop test commands and steps list: $ time python setup.py -q rpm_version #time + ... can show the command execution time $ rm -rf .egg/ #clean the cache $ time python setup.py -q deb_version $ rm -rf .egg/ #clean the cache Please let me know if any issue! Thanks! Kehao. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PBR build performance test result.xlsx Type: application/octet-stream Size: 9753 bytes Desc: not available URL: From build.starlingx at gmail.com Wed Feb 19 21:35:35 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 19 Feb 2020 16:35:35 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 159 - Still Failing! In-Reply-To: <127694898.716.1581400541082.JavaMail.javamailuser@localhost> References: <127694898.716.1581400541082.JavaMail.javamailuser@localhost> Message-ID: <310684211.852.1582148136468.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 159 Status: Still Failing Timestamp: 20200219T181618Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200219T150016Z/logs -------------------------------------------------------------------------------- Parameters HOST_PORT: 80 MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200219T150016Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root BASE_VERSION: master-stable-20200219T150016Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200219T150016Z/logs REGISTRY_USERID: slittlewrs HOST: build.starlingx.cengn.ca LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200219T150016Z/logs PUBLISH_TIMESTAMP: 20200219T150016Z FLOCK_VERSION: master-centos-stable-20200219T150016Z PREFIX: master TIMESTAMP: 20200219T150016Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20200219T150016Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Wed Feb 19 21:35:38 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 19 Feb 2020 16:35:38 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 167 - Still Failing! In-Reply-To: <508679572.839.1582075835447.JavaMail.javamailuser@localhost> References: <508679572.839.1582075835447.JavaMail.javamailuser@localhost> Message-ID: <465691640.855.1582148139690.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 167 Status: Still Failing Timestamp: 20200219T175902Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200219T150016Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200219T150016Z 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/20200219T150016Z/logs MASTER_BUILD_NUMBER: 443 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200219T150016Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos PUBLISH_TIMESTAMP: 20200219T150016Z DOCKER_BUILD_ID: jenkins-master-20200219T150016Z-builder TIMESTAMP: 20200219T150016Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/20200219T150016Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20200219T150016Z/outputs From build.starlingx at gmail.com Wed Feb 19 21:35:42 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 19 Feb 2020 16:35:42 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 443 - Failure! Message-ID: <147474688.858.1582148142814.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 443 Status: Failure Timestamp: 20200219T150016Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200219T150016Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true From scott.little at windriver.com Wed Feb 19 21:49:09 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 19 Feb 2020 16:49:09 -0500 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 443 - Failure! In-Reply-To: <147474688.858.1582148142814.JavaMail.javamailuser@localhost> References: <147474688.858.1582148142814.JavaMail.javamailuser@localhost> Message-ID: Sorry for the long list of build failures folks. the CENGN master branch build can now build iso's again, and will do so automatically tonight. However we still have issues generating docker images.  The failing images are stx-neutron and stx-nova. I'm investigating the failure now. Prior to this, most of the failures of the monolithic build have related to two features added for layered builds. - A new format for the BUILD_INFO file that is friendlier to layered builds - A mechanism to avoid needless builds of lower layers within the layered build. Some of these changes impacted code shared with the monolithic build.  It took several iterations to track down and resolve all the new interactions. Scott On 2020-02-19 4:35 p.m., build.starlingx at gmail.com wrote: > Project: STX_build_master_master > Build #: 443 > Status: Failure > Timestamp: 20200219T150016Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200219T150016Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: true > 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 Don.Penney at windriver.com Wed Feb 19 21:59:43 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 19 Feb 2020 21:59:43 +0000 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 443 - Failure! In-Reply-To: References: <147474688.858.1582148142814.JavaMail.javamailuser@localhost> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC164727E@ALA-MBD.corp.ad.wrs.com> The image build failures are due to openstack constraint updates pointing to a newer python3-only version of the module. Since our images are currently python2, this fails to install. We can push a temporary update to use a previous constraint file to enable the builds, and then work on migrating the images to python3. From: Scott Little [mailto:scott.little at windriver.com] Sent: Wednesday, February 19, 2020 4:49 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 443 - Failure! Sorry for the long list of build failures folks. the CENGN master branch build can now build iso's again, and will do so automatically tonight. However we still have issues generating docker images. The failing images are stx-neutron and stx-nova. I'm investigating the failure now. Prior to this, most of the failures of the monolithic build have related to two features added for layered builds. - A new format for the BUILD_INFO file that is friendlier to layered builds - A mechanism to avoid needless builds of lower layers within the layered build. Some of these changes impacted code shared with the monolithic build. It took several iterations to track down and resolve all the new interactions. Scott On 2020-02-19 4:35 p.m., build.starlingx at gmail.com wrote: Project: STX_build_master_master Build #: 443 Status: Failure Timestamp: 20200219T150016Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200219T150016Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true 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 scott.little at windriver.com Wed Feb 19 22:08:13 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 19 Feb 2020 17:08:13 -0500 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 443 - Failure! In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC164727E@ALA-MBD.corp.ad.wrs.com> References: <147474688.858.1582148142814.JavaMail.javamailuser@localhost> <6703202FD9FDFF4A8DA9ACF104AE129FC164727E@ALA-MBD.corp.ad.wrs.com> Message-ID: <51886ad2-f1af-b298-aacf-b3b50dfd2cde@windriver.com> Raised a launchpad https://bugs.launchpad.net/starlingx/+bug/1863957 Scott On 2020-02-19 4:59 p.m., Penney, Don wrote: > > The image build failures are due to openstack constraint updates > pointing to a newer python3-only version of the module. Since our > images are currently python2, this fails to install. We can push a > temporary update to use a previous constraint file to enable the > builds, and then work on migrating the images to python3. > > *From:*Scott Little [mailto:scott.little at windriver.com] > *Sent:* Wednesday, February 19, 2020 4:49 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] [build-report] > STX_build_master_master - Build # 443 - Failure! > > Sorry for the long list of build failures folks. > > the CENGN master branch build can now build iso's again, and will do > so automatically tonight. > > However we still have issues generating docker images.  The failing > images are stx-neutron and stx-nova.  I'm investigating the failure now. > > Prior to this, most of the failures of the monolithic build have > related to two features added for layered builds. > > - A new format for the BUILD_INFO file that is friendlier to layered > builds > > - A mechanism to avoid needless builds of lower layers within the > layered build. > > Some of these changes impacted code shared with the monolithic build.  > It took several iterations to track down and resolve all the new > interactions. > > Scott > > On 2020-02-19 4:35 p.m., build.starlingx at gmail.com > wrote: > > Project: STX_build_master_master > > Build #: 443 > > Status: Failure > > Timestamp: 20200219T150016Z > > Check logs at: > > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200219T150016Z/logs > > -------------------------------------------------------------------------------- > > Parameters > > BUILD_CONTAINERS_DEV: false > > BUILD_CONTAINERS_STABLE: true > > 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 kristal.dale at intel.com Thu Feb 20 01:14:01 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Thu, 20 Feb 2020 01:14:01 +0000 Subject: [Starlingx-discuss] [docs][meeting] docs team meeting minutes 2020-02-19 Message-ID: Hello All, Here are this week's docs team meeting minutes. Join us if you have interest in StarlingX docs! We meet Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Cheers, Kris 2020-02-19 * All -- reviews merged since last week: 2 * Lets get this merged - made minor edits to trigger rebuild: https://review.opendev.org/#/c/707385/ * Lets get this merged - minor addition of link to wiki: https://review.opendev.org/#/c/708725/ * All -- bug status -- no change * Opens * Kris -- Assignment of R4 doc tasks -- will be discussed in build meeting tomorrow and hopefully assigned * Kris -- Training review:https://review.opendev.org/#/c/706629/ -- recommend dropping when training done, and updating current contrib guide with a few more details. * All -- Wiki status ? Revisit planned migration of wiki content: lets close this out (see yellow). https://docs.google.com/spreadsheets/d/1UJjUttsWQRyauATrip0wKGIxSO7DvyetDKmPwvEIDaA/edit?usp=sharing ? Old content on wiki can be found via search results. Outdated content found on wiki (last week) now flagged out of date/deprecated with link to documentation site. ? What steps are needed to stop chasing the split of content between wiki and docs? * Kris -- Windows Active Dir content -- pending R4 baseline refresh * All -- Ongoing tasks: * Kris -- R4 install guides - terms refresh. Review ready, pending merging of R4 updates so I can rebase before creating a review. * STX in a box: (https://storyboard.openstack.org/#!/story/2006622) ? Draft in review https://review.opendev.org/#/c/692202/ ? Next steps (GREG) - Greg will spend a little time investigating possible scripted try-before-buy option using exisitng deployment stuff. * Kris -- Transition plan: https://etherpad.openstack.org/p/docs-transition-plan -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Feb 20 01:54:48 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 20 Feb 2020 01:54:48 +0000 Subject: [Starlingx-discuss] FW: stx.4.0 Release Planning -- Action Required: Feature Primes to update plans Message-ID: <151EE31B9FCCA54397A757BC674650F0C1673D71@ALA-MBD.corp.ad.wrs.com> Re-sending as the original message was moderated with "Too many recipients to the message". -----Original Message----- From: Khalil, Ghada Sent: Wednesday, February 19, 2020 8:45 PM To: Sun, Austin; Miller, Frank; Khalil, Ghada; 'Hu, Yong'; 张鲲鹏; Eslimi, Dariush; 'Saul Wold' Cc: 'Jones, Bruce E'; Zvonar, Bill; starlingx-discuss at lists.starlingx.io Subject: stx.4.0 Release Planning -- Action Required: Feature Primes to update plans Hello stx.4.0 feature primes, In preparation of the mid-cycle StarlingX meeting in early March and the upcoming stx.4.0 Milestone-2 (planned for March 23), I'd like to ask each feature prime to update their Feature Dates by Feb 26 in: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=110720984 Please update the following columns with your plan dates: - Column I: Plan Available. This is especially important if you don't have planned dates for the subsequent milestones. - Column L: Spec Approved or mark as N/A if no spec is planned - Column O: Code merged in master Please also update Column G (Green, Yellow, Red) w/ Risk. Please use Column V for comments. For more details on each field, see the "Field Definitions" tab in the spreadsheet. If you need any help, please feel free to reach out to me, Bruce or Bill. For reference: Milestone-2 Criteria: https://wiki.openstack.org/wiki/StarlingX/Release_Plan#Release_Milestones - Spec freeze; no new specs accepted for the release. The focus is on closing current specs - Feature plans defined and feature development well underway - Release test plan defined - including test automation deliverables Thanks, Ghada From Ghada.Khalil at windriver.com Thu Feb 20 02:37:23 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 20 Feb 2020 02:37:23 +0000 Subject: [Starlingx-discuss] Canceled: Weekly StarlingX Release meeting Message-ID: <151EE31B9FCCA54397A757BC674650F0C1673DD4@ALA-MBD.corp.ad.wrs.com> My apologies for the short notice, but I need to cancel the release meeting tomorrow as I have a conflict and neither Bruce nor Bill are available to chair the meeting in my place. Weekly meeting on Thursday 11AM PT / 1900 UTC Zoom Link: https://zoom.us/j/342730236 Meeting agenda/minutes: https://etherpad.openstack.org/p/stx-releases -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1967 bytes Desc: not available URL: From sgw at linux.intel.com Thu Feb 20 15:00:37 2020 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 20 Feb 2020 07:00:37 -0800 Subject: [Starlingx-discuss] MariaDB and TokuDB module License Issue Message-ID: <07e065ff-2343-0979-460e-d0753ffb111b@linux.intel.com> Don, I am looking at a CentOS-8 update and saw the only real change is to disable the TokuDB module. I looked up TokuDB and while it's older, it's GPLv2.0, not AGPL as suggested by the spec file. If we drop that patch and use the upstream MariaDB RPM, will that resolve license concern? I think the only patch to mariadb is to disable Toku. Sau! From Stefan.Dinescu at windriver.com Thu Feb 20 15:41:45 2020 From: Stefan.Dinescu at windriver.com (Dinescu, Stefan) Date: Thu, 20 Feb 2020 15:41:45 +0000 Subject: [Starlingx-discuss] Changes to Ceph storage backend provisioning Message-ID: Hello guys. I have been working on a feature to make provisioning of Ceph storage backend optional and the changes will soon merge. Reviews: [1], [2], [3] and [4]. The main purpose of this feature is to allow STX to be installed on systems with a limited number of resources (CPU and RAM mainly, but also hard-drives). If people want to deploy applications that don't require any persistent storage, ceph shouldn't consume RAM and CPU time. IMPORTANT: The stx-openstack application requires persistent storage, and thus requires a ceph storage backend. This change adds a new command that needs to run after the ansible bootstrap, in order to provision the ceph storage backend. The command is: system storage-backend-add ceph --confirmed These changes are also documented in review [4]. There is also the option for users to install a full system without provisioning the Ceph storage backend and then provision it later using the same command. Make sure you update your workflow to take into account this new command. If you encounter any bugs or issues once these changes are merged, feel free to send me an email. Thanks, Stefan [1]: https://review.opendev.org/705234 [2]: https://review.opendev.org/705235 [3]: https://review.opendev.org/705236 [4]: https://review.opendev.org/707385 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Thu Feb 20 16:02:35 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 20 Feb 2020 16:02:35 +0000 Subject: [Starlingx-discuss] MariaDB and TokuDB module License Issue In-Reply-To: <07e065ff-2343-0979-460e-d0753ffb111b@linux.intel.com> References: <07e065ff-2343-0979-460e-d0753ffb111b@linux.intel.com> Message-ID: Looking at the unmodified source tarball, the storage/tokudb/PerconaFT/README.md file has the following: License ------- PerconaFT is available under the GPL version 2, and AGPL version 3. See [COPYING.AGPLv3][agpllicense], [COPYING.GPLv2][gpllicense], and [PATENTS][patents]. [agpllicense]: http://github.com/Percona/PerconaFT/blob/master/COPYING.AGPLv3 [gpllicense]: http://github.com/Percona/PerconaFT/blob/master/COPYING.GPLv2 [patents]: http://github.com/Percona/PerconaFT/blob/master/PATENTS along with the storage/tokudb/PerconaFT/COPYING.AGPLv3 file. I expect this is why we had to drop tokudb from the source tarball. -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Thursday, February 20, 2020 10:01 AM To: Penney, Don; starlingx-discuss at lists.starlingx.io Subject: MariaDB and TokuDB module License Issue Don, I am looking at a CentOS-8 update and saw the only real change is to disable the TokuDB module. I looked up TokuDB and while it's older, it's GPLv2.0, not AGPL as suggested by the spec file. If we drop that patch and use the upstream MariaDB RPM, will that resolve license concern? I think the only patch to mariadb is to disable Toku. Sau! From maria.g.perez.ibarra at intel.com Thu Feb 20 22:13:03 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 20 Feb 2020 22:13:03 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200220 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-FEBRUARY-20 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Fri Feb 21 01:15:23 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 21 Feb 2020 01:15:23 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 02/20 Message-ID: <151EE31B9FCCA54397A757BC674650F0C167452A@ALA-MBD.corp.ad.wrs.com> Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Team Introductions (for Romania team) - Nikoli Jascanu: Leader of StarlingX Intel validation team in Europe - Team size is 10 people - 7 in Romania + 3 in Germany - Mihail-Laurentiu Trica: Ramping up in general on StarlingX; not particularly focused on networking at this time - Chris Winnicki: WR StarlingX Test team - Matt Peters: StarlingX Networking Technical Lead - Steve Webster: StarlingX WR Networking team - Joseph Richard: StarlingX WR Networking team - Sabeel Ansari: StarlingX WR Networking team - new to the team - Yi Wang: StarlingX Intel team stx.4.0 Features - TSN support in Kata - Prime: Shuicheng - Status: Not Started - Question from Matt: Is there a hard dependency on the 4.19 / CentOS 8 kernel? Is there a possibility to break this dependency? - Are there specific features of the newer kernel that is required? - Ghada to follow up with Shuicheng & Yong - IPv6 PXE boot network support - Prime: Kunpeng Zhang - 99cloud - Status: Not Started - Ghada to reach out to him - OVS-DPDK Containerization - Question from Matt: Was there any StarlingX work done on this feature before it was put on hold? - What are the plans for the current reviews posted in other projects? Are they being abandoned or transitioned to a new owner? - Current reviews: - starlingx/openstack-armada-app: https://review.opendev.org/#/c/696437/ - starlingx/config: https://review.opendev.org/#/c/694188 - openstack/openstack-armada-app: https://review.opendev.org/#/c/701676/ - Ghada to follow up with Huifeng stx.4.0 Bugs - Total: 4 - https://bugs.launchpad.net/starlingx/+bug/1833463 -- armada-manifest upload failed when configuring bond with OVS container (vswitch-type=none) - Needs to be re-assigned. Action with Yong. Work is related to openstack-helm - https://bugs.launchpad.net/starlingx/+bug/1850438 -- The sriov device plugin pod may start before it's config manifest is written - Steve. On hold. This is a larger scope item. Should re-gate? - https://bugs.launchpad.net/starlingx/+bug/1855191 - Unable to modify interface to use static IP - Thomas. Review in progress - https://bugs.launchpad.net/starlingx/+bug/1856587 - Traceback in unlock host when configuring pci-passthrough interfaces and sriovdp label enabled - Thomas. Review in progress stx.3.0 Bugs - Total: 1 - https://bugs.launchpad.net/starlingx/+bug/1821026 -- Containers: Resolving hostname fails within nova containers leading to config_drive VM migration failures - This is a valid issue and we want to continue working on it. There is a review in progress, but there are issues with testing. - Is Zhipeng taking this over? Recent emails sent from Weifei stx.2.0 Bugs - Total: 2 - https://bugs.launchpad.net/starlingx/+bug/1849655 -- StarlingX R2 duplex: VM not getting IP assigned to the vlan network when re-spawned on controller-0 after shutting down controller-1 - Lowering the priority as this appears to be a setup issue, not a software issue - https://bugs.launchpad.net/starlingx/+bug/1839181 -- Platform CPU threshold exceeded in compute after lock/unlock a different compute host (Storage System) - Recently re-opened. Not enough data (reference to duplicate LP which also has no data). Following up with the reporter. Low Priority Bugs - Total: 8 From shuicheng.lin at intel.com Fri Feb 21 01:22:29 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 21 Feb 2020 01:22:29 +0000 Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 2/19/2020 In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C76639624AA@SHSMSX104.ccr.corp.intel.com> Hi all, Here is my AR for a quick update for the 4.18 std kernel with gcc-4.8.5. Meta patch for spec: Customize-4.18-kernel-with-centos-7-build-environmen.patch Source code patch: Fix-compile-error-with-gcc-4.8.5.patch Also CONFIG_KASAN=n is added to tis_extra config file, due to gcc-4.8.5 doesn't support -fsanitize=kernel-address. "BUILDSTDERR: scripts/Makefile.kasan:17: Cannot use CONFIG_KASAN: -fsanitize=kernel-address is not supported by compiler" Please notice it is tested with 4.18.0-80 kernel. And patch is expected to be updated with more test and 4.18.0-147 kernel. Best Regards Shuicheng -----Original Message----- From: Sun, Austin Sent: Wednesday, February 19, 2020 11:16 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 2/19/2020 Hi All: Thanks join the call. MoM for 2/19 meeting: - Prb update (JITStack-Wesley) --- build time any feedback from Build Team http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007788.html , currently no feedback from build team. - CentOS8 upgrade (Austin/Shuicheng) - incremental upgrade on master : * mock support (old gcc and new gcc ) , no solution yet. http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007769.html * new gcc will cause el7 rpm conflict or build failure. * std kernel build status update (kernel 4.18.0-80.11.2 on master env (gcc 4.8 +python2) do some minor changes , this kernel 4.18.0-80.11.2 built by gcc 4.8 , kernel can be built successfully AR: summary the changes and send to mail list. * rt kernel build status (kernel 4.18.0-147.3.1.rt24.96) , * 3.10 patch rebase , config update are remaining * python3 enable on master ? which is the preferred repo to upgrade to python3 besides NFV start this task now. * Ussuri host openstack (oslo , keystone , barbican , horizon and openstack client ) upgrade ? plan openstack client containerization no resource assign , some early study have been done by Stephan, timeline for Ussuri official release on CentOS8 should be risk . *the target , plan and goal on stx 4.0 feature ? target : end of March to finish kernel(std and rt) upgrade depends on centos8 rpms readiness (openstack), the minimum target is kernel upgrade . - any new stx.4.0 feature depends on kernel 4.18 ? - when will involve test team - how about centos8 branch ? shall we continue if we fully switch to incremental upgrade. keep centos8 branch, and do test on some user space rpms upgrade. - Vista Creek (FPGA card) support tarball/srpm issue need to be fixed by intel us team OPAE iavf and i40e driver . new driver integrated into stx. ---done . SRIOV device plugin --- no feedback yet . https://github.com/intel/sriov-network-device-plugin/pull/196 - Open Thanks. BR Austin Sun. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- A non-text attachment was scrubbed... Name: Customize-4.18-kernel-with-centos-7-build-environmen.patch Type: application/octet-stream Size: 6592 bytes Desc: Customize-4.18-kernel-with-centos-7-build-environmen.patch URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Fix-compile-error-with-gcc-4.8.5.patch Type: application/octet-stream Size: 1424 bytes Desc: Fix-compile-error-with-gcc-4.8.5.patch URL: From Stefan.Dinescu at windriver.com Fri Feb 21 08:34:24 2020 From: Stefan.Dinescu at windriver.com (Dinescu, Stefan) Date: Fri, 21 Feb 2020 08:34:24 +0000 Subject: [Starlingx-discuss] Changes to Ceph storage backend provisioning In-Reply-To: References: Message-ID: Hello, Changes have been merged, so the new command is not officially required to provision the Ceph storage-backend. Let me know if you encounter any issues. Thanks, Stefan ________________________________ From: Dinescu, Stefan Sent: Thursday, February 20, 2020 5:41 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Changes to Ceph storage backend provisioning Hello guys. I have been working on a feature to make provisioning of Ceph storage backend optional and the changes will soon merge. Reviews: [1], [2], [3] and [4]. The main purpose of this feature is to allow STX to be installed on systems with a limited number of resources (CPU and RAM mainly, but also hard-drives). If people want to deploy applications that don't require any persistent storage, ceph shouldn't consume RAM and CPU time. IMPORTANT: The stx-openstack application requires persistent storage, and thus requires a ceph storage backend. This change adds a new command that needs to run after the ansible bootstrap, in order to provision the ceph storage backend. The command is: system storage-backend-add ceph --confirmed These changes are also documented in review [4]. There is also the option for users to install a full system without provisioning the Ceph storage backend and then provision it later using the same command. Make sure you update your workflow to take into account this new command. If you encounter any bugs or issues once these changes are merged, feel free to send me an email. Thanks, Stefan [1]: https://review.opendev.org/705234 [2]: https://review.opendev.org/705235 [3]: https://review.opendev.org/705236 [4]: https://review.opendev.org/707385 -------------- next part -------------- An HTML attachment was scrubbed... URL: From alfredo.deluca at gmail.com Fri Feb 21 11:42:02 2020 From: alfredo.deluca at gmail.com (Alfredo De Luca) Date: Fri, 21 Feb 2020 12:42:02 +0100 Subject: [Starlingx-discuss] Changes to Ceph storage backend provisioning In-Reply-To: References: Message-ID: Hi Stefan. does it mean that it will be possible to have a different storage backend? Cheers On Fri, Feb 21, 2020 at 9:36 AM Dinescu, Stefan < Stefan.Dinescu at windriver.com> wrote: > Hello, > > Changes have been merged, so the new command is not officially required to > provision the Ceph storage-backend. > > Let me know if you encounter any issues. > > Thanks, > Stefan > ------------------------------ > *From:* Dinescu, Stefan > *Sent:* Thursday, February 20, 2020 5:41 PM > *To:* starlingx-discuss at lists.starlingx.io < > starlingx-discuss at lists.starlingx.io> > *Subject:* [Starlingx-discuss] Changes to Ceph storage backend > provisioning > > Hello guys. > > I have been working on a feature to make provisioning of Ceph storage > backend optional and the changes will soon merge. Reviews: [1], [2], [3] > and [4]. > > The main purpose of this feature is to allow STX to be installed on > systems with a limited number of resources (CPU and RAM mainly, but also > hard-drives). If people want to deploy applications that don't require any > persistent storage, ceph shouldn't consume RAM and CPU time. > > *IMPORTANT: *The stx-openstack application requires persistent storage, > and thus requires a ceph storage backend. > > This change adds a new command that needs to run after the ansible > bootstrap, in order to provision the ceph storage backend. The command is: > > *system storage-backend-add ceph --confirmed* > > > These changes are also documented in review [4]. > > There is also the option for users to install a full system *without* > provisioning the Ceph storage backend and then provision it later using the > same command. > > Make sure you update your workflow to take into account this new command. > If you encounter any bugs or issues once these changes are merged, feel > free to send me an email. > > Thanks, > Stefan > > [1]: https://review.opendev.org/705234 > [2]: https://review.opendev.org/705235 > [3]: https://review.opendev.org/705236 > [4]: https://review.opendev.org/707385 > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- *Alfredo* -------------- next part -------------- An HTML attachment was scrubbed... URL: From Stefan.Dinescu at windriver.com Fri Feb 21 12:42:30 2020 From: Stefan.Dinescu at windriver.com (Dinescu, Stefan) Date: Fri, 21 Feb 2020 12:42:30 +0000 Subject: [Starlingx-discuss] Changes to Ceph storage backend provisioning In-Reply-To: References: , Message-ID: Hello, At this moment in time only the Ceph storage backend in supported. As I said, this feature was designed for less powerful systems where Ceph was not needed. Also, small correction. I said "the new command is not officially required". What I meant to say was "the new command is now officially required". ________________________________ From: Alfredo De Luca Sent: Friday, February 21, 2020 1:42 PM To: Dinescu, Stefan Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Changes to Ceph storage backend provisioning Hi Stefan. does it mean that it will be possible to have a different storage backend? Cheers On Fri, Feb 21, 2020 at 9:36 AM Dinescu, Stefan > wrote: Hello, Changes have been merged, so the new command is not officially required to provision the Ceph storage-backend. Let me know if you encounter any issues. Thanks, Stefan ________________________________ From: Dinescu, Stefan > Sent: Thursday, February 20, 2020 5:41 PM To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Changes to Ceph storage backend provisioning Hello guys. I have been working on a feature to make provisioning of Ceph storage backend optional and the changes will soon merge. Reviews: [1], [2], [3] and [4]. The main purpose of this feature is to allow STX to be installed on systems with a limited number of resources (CPU and RAM mainly, but also hard-drives). If people want to deploy applications that don't require any persistent storage, ceph shouldn't consume RAM and CPU time. IMPORTANT: The stx-openstack application requires persistent storage, and thus requires a ceph storage backend. This change adds a new command that needs to run after the ansible bootstrap, in order to provision the ceph storage backend. The command is: system storage-backend-add ceph --confirmed These changes are also documented in review [4]. There is also the option for users to install a full system without provisioning the Ceph storage backend and then provision it later using the same command. Make sure you update your workflow to take into account this new command. If you encounter any bugs or issues once these changes are merged, feel free to send me an email. Thanks, Stefan [1]: https://review.opendev.org/705234 [2]: https://review.opendev.org/705235 [3]: https://review.opendev.org/705236 [4]: https://review.opendev.org/707385 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Alfredo -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Fri Feb 21 15:13:54 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 21 Feb 2020 15:13:54 +0000 Subject: [Starlingx-discuss] ceph containerization patch review In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D8562A97A4@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D8562A76F5@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A7E32@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A9371@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D8562A97A4@CDSMSX102.ccr.corp.intel.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D8562ACFCA@CDSMSX102.ccr.corp.intel.com> Hi Frank & Bob & Greg & Brent To deploy, it is same as any other helm chart. Wait for you opinion for current solution. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Wednesday, February 19, 2020 12:53 PM To: 'Miller, Frank' ; 'starlingx-discuss at lists.starlingx.io' ; Rowsell, Brent ; 'Greg.Waines at windriver.com' Cc: Chen, Tingjie ; Sun, Austin ; Qi, Mingyuan ; Church, Robert Subject: RE: ceph containerization patch review Hi folks Answer the question, with only k8s, how to deploy rook. $ helm-upload stx-platform rook-ceph-0.1.0.tga $ helm install stx-platform/rook-ceph -n rook-ceph-cluster -n kube-system -f value.yaml BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Tuesday, February 18, 2020 10:06 PM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan >; Church, Robert > Subject: RE: ceph containerization patch review +Bob who is the containers TL From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Monday, February 17, 2020 8:46 AM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' >; Rowsell, Brent > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan > Subject: RE: ceph containerization patch review Hi Frank & Brent For rook manage configuration, after introduce rook-ceph, current ceph cluster deployed by puppet will keep or be removed? If removed, containerized ceph cluster deployed by rook-ceph will take the role of provisioner for stx-openstack. If keeps, helm chart rbd-provisioner in platform-integ-app also keeps and takes the role of provisioner for stx-openstack. Containerized ceph cluster deployed by rook-ceph only serve as csi provider for k8s. BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, February 10, 2020 11:47 PM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' > Cc: Chen, Tingjie >; Sun, Austin >; Qi, Mingyuan > Subject: RE: ceph containerization patch review Hi Frank: As synced with Tingjie, this is my understanding for Rook manage the configuration instead of sysinv. 1, Remove ceph config and status query from sysinv 2, create another tool, like rook-client to launch and provision ceph cluster 3, one helm plugin like rbd-provision, which depends on newly created tool BR! Martin, Chen IOTG, Software Engineer 021-61164330 From: Miller, Frank > Sent: Saturday, February 8, 2020 4:16 AM To: Chen, Haochuan Z >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: ceph containerization patch review Martin: Thanks for posting your reviews and the update on the current status for this feature. I was unable to attend the containerization meeting this week so wasn't able to have Tingjie or you give an update on the open actions for the feature. From the Jan 14 minutes [1] one of the actions is to determine "how can you have Rook do all the configuration and not have sysinv involved" For now I suggest you add an additional item to your Tasks to do list to identify a design that does not require sysinv for the configuration and instead has Rook manage the configuration. I would like to ask that we discuss further at the next containerization meeting and if possible review a proposal from yourself and Austin for this item. Frank [1] https://etherpad.openstack.org/p/stx-containerization From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Thursday, February 06, 2020 11:02 PM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] ceph containerization patch review Hi folks I enabled containerized ceph cluster with simplex. You can begin to review my patch. I propose to build an image and deploy a simplex system with these patch to check. https://review.opendev.org/#/c/681457/ https://review.opendev.org/#/c/687340/ https://review.opendev.org/#/c/706256/ https://review.opendev.org/#/c/699557/ https://review.opendev.org/#/c/699556/ And I know there is other story, like remove ceph as default backend storage, maybe some conflict, we can discuss together. Tash Done: 1, disable native ceph cluster in ceph.pp 2, disable ceph daemon monitoring in service manager 3, add rook-ceph helm chart to launch ceph cluster 4, add override in stx-config to generate override with starlingx system config 5, sysinv add label in provision stage, to make containerized ceph mon and ceph mgr on designed host 6, add rook-ceph-provisioner helm chart to generate storage class, secret, config and pool for stx-application 7, enabled stx-openstack with containerized ceph 8, update ceph wrapper in stx-config to set or get containerized ceph cluster All these tasks done is enabled with simplex only. Task to do: 1, enable add osd runtime, after system provisioned 2, fix know issue, if system reboot, ceph cluster launch fail 3, enable bluestore and filestore, currently there is only bluestore 4, enable multi-node and duplex 5, enable swift with containerized ceph 6, enable fm alarm for containerized ceph 7, check backup and restore for containerized ceph 8, check system upgrade or how to transit from native ceph cluster to containerized ceph cluster 9, code cleanup 10, update unit test in stx-config BR! Martin, Chen IOTG, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From alfredo.deluca at gmail.com Fri Feb 21 15:21:09 2020 From: alfredo.deluca at gmail.com (Alfredo De Luca) Date: Fri, 21 Feb 2020 16:21:09 +0100 Subject: [Starlingx-discuss] Changes to Ceph storage backend provisioning In-Reply-To: References: Message-ID: great! Thanks for clarifying Cheers On Fri, Feb 21, 2020 at 1:42 PM Dinescu, Stefan < Stefan.Dinescu at windriver.com> wrote: > Hello, > > At this moment in time only the Ceph storage backend in supported. As I > said, this feature was designed for less powerful systems where Ceph was > not needed. > > Also, small correction. I said *"the new command is not officially > required". *What I meant to say was "*the new command is now officially > required*". > ------------------------------ > *From:* Alfredo De Luca > *Sent:* Friday, February 21, 2020 1:42 PM > *To:* Dinescu, Stefan > *Cc:* starlingx-discuss at lists.starlingx.io < > starlingx-discuss at lists.starlingx.io> > *Subject:* Re: [Starlingx-discuss] Changes to Ceph storage backend > provisioning > > Hi Stefan. does it mean that it will be possible to have a different > storage backend? > > Cheers > > On Fri, Feb 21, 2020 at 9:36 AM Dinescu, Stefan < > Stefan.Dinescu at windriver.com> wrote: > > Hello, > > Changes have been merged, so the new command is not officially required to > provision the Ceph storage-backend. > > Let me know if you encounter any issues. > > Thanks, > Stefan > ------------------------------ > *From:* Dinescu, Stefan > *Sent:* Thursday, February 20, 2020 5:41 PM > *To:* starlingx-discuss at lists.starlingx.io < > starlingx-discuss at lists.starlingx.io> > *Subject:* [Starlingx-discuss] Changes to Ceph storage backend > provisioning > > Hello guys. > > I have been working on a feature to make provisioning of Ceph storage > backend optional and the changes will soon merge. Reviews: [1], [2], [3] > and [4]. > > The main purpose of this feature is to allow STX to be installed on > systems with a limited number of resources (CPU and RAM mainly, but also > hard-drives). If people want to deploy applications that don't require any > persistent storage, ceph shouldn't consume RAM and CPU time. > > *IMPORTANT: *The stx-openstack application requires persistent storage, > and thus requires a ceph storage backend. > > This change adds a new command that needs to run after the ansible > bootstrap, in order to provision the ceph storage backend. The command is: > > *system storage-backend-add ceph --confirmed* > > > These changes are also documented in review [4]. > > There is also the option for users to install a full system *without* > provisioning the Ceph storage backend and then provision it later using the > same command. > > Make sure you update your workflow to take into account this new command. > If you encounter any bugs or issues once these changes are merged, feel > free to send me an email. > > Thanks, > Stefan > > [1]: https://review.opendev.org/705234 > [2]: https://review.opendev.org/705235 > [3]: https://review.opendev.org/705236 > [4]: https://review.opendev.org/707385 > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > -- > *Alfredo* > > -- *Alfredo* -------------- next part -------------- An HTML attachment was scrubbed... URL: From yi.c.wang at intel.com Mon Feb 24 08:06:02 2020 From: yi.c.wang at intel.com (Wang, Yi C) Date: Mon, 24 Feb 2020 08:06:02 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 02/20 In-Reply-To: <151EE31B9FCCA54397A757BC674650F0C167452A@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0C167452A@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Ghada/Matt, NIC driver should be okay given IGB (Intel I210) is already there. To support TSN, we still need some kernel features, for example, * Qdisc TAPRIO: implemented TSN protocol 802.1Qbv and was introduced in Linux 4.20 * Qdisc CBS: implemented 802.1Qav and was introduced in Linux 4.15 * probably other features like AF_XDP socket family which was introduced in Linux 4.18. For the feature of " TSN support in Kata", since Kata container has its own kernel, there is not hard dependency with CentOS 8 upgrade task. Thanks. Yi -----Original Message----- From: Khalil, Ghada Sent: Friday, February 21, 2020 9:15 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 02/20 Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Team Introductions (for Romania team) - Nikoli Jascanu: Leader of StarlingX Intel validation team in Europe - Team size is 10 people - 7 in Romania + 3 in Germany - Mihail-Laurentiu Trica: Ramping up in general on StarlingX; not particularly focused on networking at this time - Chris Winnicki: WR StarlingX Test team - Matt Peters: StarlingX Networking Technical Lead - Steve Webster: StarlingX WR Networking team - Joseph Richard: StarlingX WR Networking team - Sabeel Ansari: StarlingX WR Networking team - new to the team - Yi Wang: StarlingX Intel team stx.4.0 Features - TSN support in Kata - Prime: Shuicheng - Status: Not Started - Question from Matt: Is there a hard dependency on the 4.19 / CentOS 8 kernel? Is there a possibility to break this dependency? - Are there specific features of the newer kernel that is required? - Ghada to follow up with Shuicheng & Yong - IPv6 PXE boot network support - Prime: Kunpeng Zhang - 99cloud - Status: Not Started - Ghada to reach out to him - OVS-DPDK Containerization - Question from Matt: Was there any StarlingX work done on this feature before it was put on hold? - What are the plans for the current reviews posted in other projects? Are they being abandoned or transitioned to a new owner? - Current reviews: - starlingx/openstack-armada-app: https://review.opendev.org/#/c/696437/ - starlingx/config: https://review.opendev.org/#/c/694188 - openstack/openstack-armada-app: https://review.opendev.org/#/c/701676/ - Ghada to follow up with Huifeng stx.4.0 Bugs - Total: 4 - https://bugs.launchpad.net/starlingx/+bug/1833463 -- armada-manifest upload failed when configuring bond with OVS container (vswitch-type=none) - Needs to be re-assigned. Action with Yong. Work is related to openstack-helm - https://bugs.launchpad.net/starlingx/+bug/1850438 -- The sriov device plugin pod may start before it's config manifest is written - Steve. On hold. This is a larger scope item. Should re-gate? - https://bugs.launchpad.net/starlingx/+bug/1855191 - Unable to modify interface to use static IP - Thomas. Review in progress - https://bugs.launchpad.net/starlingx/+bug/1856587 - Traceback in unlock host when configuring pci-passthrough interfaces and sriovdp label enabled - Thomas. Review in progress stx.3.0 Bugs - Total: 1 - https://bugs.launchpad.net/starlingx/+bug/1821026 -- Containers: Resolving hostname fails within nova containers leading to config_drive VM migration failures - This is a valid issue and we want to continue working on it. There is a review in progress, but there are issues with testing. - Is Zhipeng taking this over? Recent emails sent from Weifei stx.2.0 Bugs - Total: 2 - https://bugs.launchpad.net/starlingx/+bug/1849655 -- StarlingX R2 duplex: VM not getting IP assigned to the vlan network when re-spawned on controller-0 after shutting down controller-1 - Lowering the priority as this appears to be a setup issue, not a software issue - https://bugs.launchpad.net/starlingx/+bug/1839181 -- Platform CPU threshold exceeded in compute after lock/unlock a different compute host (Storage System) - Recently re-opened. Not enough data (reference to duplicate LP which also has no data). Following up with the reporter. Low Priority Bugs - Total: 8 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From mward at akamai.com Mon Feb 24 13:08:32 2020 From: mward at akamai.com (Ward, Martin) Date: Mon, 24 Feb 2020 13:08:32 +0000 Subject: [Starlingx-discuss] Is LDAP required? Message-ID: Hi all, Trying to install a simplex server and I’m running in to LDAP issues. Specifically the fact that it seems to be timing out trying to connect to the server itself. This can be seen when I run “sudo bash”, which eventually reports “Can’t contact LDAP server” and authenticates me against the passwd file. slapd is definitely not running on start up. I can run “systemctl start slapd” and then see it running, but I still get this timeout error. I could remove ldap from the nsswitch.conf file but I don’t know how that will break the StarlingX insallation. Any thought or suggestions? Martin -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dariush.Eslimi at windriver.com Mon Feb 24 13:19:03 2020 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Mon, 24 Feb 2020 13:19:03 +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 * 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: 2492 bytes Desc: not available URL: From andy.ning at windriver.com Mon Feb 24 14:39:02 2020 From: andy.ning at windriver.com (Andy Ning) Date: Mon, 24 Feb 2020 09:39:02 -0500 Subject: [Starlingx-discuss] Is LDAP required? In-Reply-To: References: Message-ID: <978ce9f3-1a66-607d-02aa-0fd0c8887a62@windriver.com> On 2020-02-24 08:08 AM, Ward, Martin wrote: > > Hi all, > > Trying to install a simplex server and I’m running in to LDAP issues. > > Specifically the fact that it seems to be timing out trying to connect > to the server itself. This can be seen when I run “sudo bash”, which > eventually reports “Can’t contact LDAP server” and authenticates me > against the passwd file. > > slapd is definitely not running on start up. I can run “systemctl > start slapd” and then see it running, but I still get this timeout error. > > I could remove ldap from the nsswitch.conf file but I don’t know how > that will break the StarlingX insallation. > In a successful deployment, a ldap "admin" user is created. (not in OS users files). But I don't think this user is used by any services. So I would think it won't break anything if it's removed. Andy > Any thought or suggestions? > > Martin > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Andy Ning Cube: 3071 Tel: 613-9631408 (int: 4408) Skype: andy.ning.wr -------------- next part -------------- An HTML attachment was scrubbed... URL: From dejan.muhamedagic at tttech-industrial.com Mon Feb 24 14:48:36 2020 From: dejan.muhamedagic at tttech-industrial.com (Dejan Muhamedagic) Date: Mon, 24 Feb 2020 14:48:36 +0000 Subject: [Starlingx-discuss] oam address Message-ID: <737e35859c115f6a9511a95677a1f9161cbfb68a.camel@tttech-industrial.com> Hi, Is it possible to change the OAM IP address after the installation? There is a "system oam-modify", but the installation guide warns: "Some Ansible bootstrap parameters cannot be changed or are very difficult to change after installation is complete." The reason I'm asking is that this installation may have to run in different environments and possibly in different networks. Thanks, Dejan CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail at tttech.com immediately. From Chris.Winnicki at windriver.com Mon Feb 24 15:05:24 2020 From: Chris.Winnicki at windriver.com (Winnicki, Chris) Date: Mon, 24 Feb 2020 15:05:24 +0000 Subject: [Starlingx-discuss] oam address In-Reply-To: <737e35859c115f6a9511a95677a1f9161cbfb68a.camel@tttech-industrial.com> References: <737e35859c115f6a9511a95677a1f9161cbfb68a.camel@tttech-industrial.com> Message-ID: <7E4792BA14B1DE4BAB354DF77FE0233AC4376097@ALA-MBD.corp.ad.wrs.com> Hi Dejan It's absolutely possible to change the OAM IP address after the installation is completed. * One thing to watch out for is make sure that: 1) oam_gateway_ip is updated if you're changing networks 2) That your machine (which you're using to access the StarlinX system) can route to the new network (in case the networks were changed) Regards, Chris Winnicki chris.winnicki at windriver.com 613-963-1329 ________________________________________ From: Dejan Muhamedagic [dejan.muhamedagic at tttech-industrial.com] Sent: Monday, February 24, 2020 9:48 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] oam address Hi, Is it possible to change the OAM IP address after the installation? There is a "system oam-modify", but the installation guide warns: "Some Ansible bootstrap parameters cannot be changed or are very difficult to change after installation is complete." The reason I'm asking is that this installation may have to run in different environments and possibly in different networks. Thanks, Dejan CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail at tttech.com immediately. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dejan.muhamedagic at tttech-industrial.com Mon Feb 24 15:08:47 2020 From: dejan.muhamedagic at tttech-industrial.com (Dejan Muhamedagic) Date: Mon, 24 Feb 2020 15:08:47 +0000 Subject: [Starlingx-discuss] oam address In-Reply-To: <7E4792BA14B1DE4BAB354DF77FE0233AC4376097@ALA-MBD.corp.ad.wrs.com> References: <737e35859c115f6a9511a95677a1f9161cbfb68a.camel@tttech-industrial.com> <7E4792BA14B1DE4BAB354DF77FE0233AC4376097@ALA-MBD.corp.ad.wrs.com> Message-ID: <4eef23e79699af717dc621354d0571cd4a0bb300.camel@tttech-industrial.com> Hi Chris, On Mon, 2020-02-24 at 15:05 +0000, Winnicki, Chris wrote: > Hi Dejan > > It's absolutely possible to change the OAM IP address after the > installation is completed. Great! Another question regarding the OAM IP: Do you plan to support dhcp for OAM? Thanks, Dejan > * One thing to watch out for is make sure that: > 1) oam_gateway_ip is updated if you're changing networks > 2) That your machine (which you're using to access the StarlinX > system) can route to the new network (in case the networks were > changed) > > > Regards, > > Chris Winnicki > chris.winnicki at windriver.com > 613-963-1329 > ________________________________________ > From: Dejan Muhamedagic [dejan.muhamedagic at tttech-industrial.com] > Sent: Monday, February 24, 2020 9:48 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] oam address > > Hi, > > Is it possible to change the OAM IP address after the installation? > There is a "system oam-modify", but the installation guide warns: > > "Some Ansible bootstrap parameters cannot be changed or are very > difficult to change after installation is complete." > > The reason I'm asking is that this installation may have to run in > different environments and possibly in different networks. > > Thanks, > > Dejan > > CONFIDENTIALITY: The contents of this e-mail are confidential and > intended only for the above addressee(s). If you are not the intended > recipient, or the person responsible for delivering it to the > intended recipient, copying or delivering it to anyone else or using > it in any unauthorized manner is prohibited and may be unlawful. If > you receive this e-mail by mistake, please notify the sender and the > systems administrator at straymail at tttech.com immediately. > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail at tttech.com immediately. From mward at akamai.com Mon Feb 24 16:07:01 2020 From: mward at akamai.com (Ward, Martin) Date: Mon, 24 Feb 2020 16:07:01 +0000 Subject: [Starlingx-discuss] Is LDAP required? In-Reply-To: <978ce9f3-1a66-607d-02aa-0fd0c8887a62@windriver.com> References: <978ce9f3-1a66-607d-02aa-0fd0c8887a62@windriver.com> Message-ID: > In a successful deployment, a ldap "admin" user is created. (not in OS users files). But I don't think this user is used by any services. So I would think it won't break anything if it's removed. Thanks Andy, perhaps the devs might want to think about removing the LDAP software, at least from the simplex controller. The less complication the better, I think. I did work out why it was failing, dodgy network settings were the issue. If anyone else comes across this issue then my solution was to start all over again and ensure that network interfaces all came up correctly and with the correct IP addresses once the VM had started up but before I configured the localhost.yml file. I basically replaced step 3 with manual commands to configure the interfaces, assign their IPs and make sure that they all worked. -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon Feb 24 16:38:22 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 24 Feb 2020 11:38:22 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 50 - Failure! Message-ID: <1687380426.867.1582562303851.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 50 Status: Failure Timestamp: 20200224T163400Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200224T162509Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20200224T162509Z DOCKER_BUILD_ID: jenkins-master-compiler-20200224T162509Z-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/20200224T162509Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200224T162509Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From Chris.Winnicki at windriver.com Mon Feb 24 16:49:43 2020 From: Chris.Winnicki at windriver.com (Winnicki, Chris) Date: Mon, 24 Feb 2020 16:49:43 +0000 Subject: [Starlingx-discuss] oam address In-Reply-To: <4eef23e79699af717dc621354d0571cd4a0bb300.camel@tttech-industrial.com> References: <737e35859c115f6a9511a95677a1f9161cbfb68a.camel@tttech-industrial.com> <7E4792BA14B1DE4BAB354DF77FE0233AC4376097@ALA-MBD.corp.ad.wrs.com>, <4eef23e79699af717dc621354d0571cd4a0bb300.camel@tttech-industrial.com> Message-ID: <7E4792BA14B1DE4BAB354DF77FE0233AC43760F2@ALA-MBD.corp.ad.wrs.com> Hi Dejan I think DHCP support is possible in the future - but at this time I don't think it's on the roadmap. Regards, Chris Winnicki chris.winnicki at windriver.com 613-963-1329 ________________________________________ From: Dejan Muhamedagic [dejan.muhamedagic at tttech-industrial.com] Sent: Monday, February 24, 2020 10:08 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] oam address Hi Chris, On Mon, 2020-02-24 at 15:05 +0000, Winnicki, Chris wrote: > Hi Dejan > > It's absolutely possible to change the OAM IP address after the > installation is completed. Great! Another question regarding the OAM IP: Do you plan to support dhcp for OAM? Thanks, Dejan > * One thing to watch out for is make sure that: > 1) oam_gateway_ip is updated if you're changing networks > 2) That your machine (which you're using to access the StarlinX > system) can route to the new network (in case the networks were > changed) > > > Regards, > > Chris Winnicki > chris.winnicki at windriver.com > 613-963-1329 > ________________________________________ > From: Dejan Muhamedagic [dejan.muhamedagic at tttech-industrial.com] > Sent: Monday, February 24, 2020 9:48 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] oam address > > Hi, > > Is it possible to change the OAM IP address after the installation? > There is a "system oam-modify", but the installation guide warns: > > "Some Ansible bootstrap parameters cannot be changed or are very > difficult to change after installation is complete." > > The reason I'm asking is that this installation may have to run in > different environments and possibly in different networks. > > Thanks, > > Dejan > > CONFIDENTIALITY: The contents of this e-mail are confidential and > intended only for the above addressee(s). If you are not the intended > recipient, or the person responsible for delivering it to the > intended recipient, copying or delivering it to anyone else or using > it in any unauthorized manner is prohibited and may be unlawful. If > you receive this e-mail by mistake, please notify the sender and the > systems administrator at straymail at tttech.com immediately. > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail at tttech.com immediately. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From build.starlingx at gmail.com Mon Feb 24 19:35:32 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 24 Feb 2020 14:35:32 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 53 - Failure! Message-ID: <1920916225.872.1582572935463.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 53 Status: Failure Timestamp: 20200224T192300Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200224T185245Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200224T185245Z DOCKER_BUILD_ID: jenkins-master-flock-20200224T185245Z-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/20200224T185245Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200224T185245Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From bruce.e.jones at intel.com Mon Feb 24 23:38:25 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 24 Feb 2020 23:38:25 +0000 Subject: [Starlingx-discuss] Changes to Ceph storage backend provisioning In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BF1675172@fmsmsx123.amr.corp.intel.com> Has someone updated docs.starlingX.io for this change? brucej From: Alfredo De Luca [mailto:alfredo.deluca at gmail.com] Sent: Friday, February 21, 2020 7:21 AM To: Dinescu, Stefan Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Changes to Ceph storage backend provisioning great! Thanks for clarifying Cheers On Fri, Feb 21, 2020 at 1:42 PM Dinescu, Stefan > wrote: Hello, At this moment in time only the Ceph storage backend in supported. As I said, this feature was designed for less powerful systems where Ceph was not needed. Also, small correction. I said "the new command is not officially required". What I meant to say was "the new command is now officially required". ________________________________ From: Alfredo De Luca > Sent: Friday, February 21, 2020 1:42 PM To: Dinescu, Stefan > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Changes to Ceph storage backend provisioning Hi Stefan. does it mean that it will be possible to have a different storage backend? Cheers On Fri, Feb 21, 2020 at 9:36 AM Dinescu, Stefan > wrote: Hello, Changes have been merged, so the new command is not officially required to provision the Ceph storage-backend. Let me know if you encounter any issues. Thanks, Stefan ________________________________ From: Dinescu, Stefan > Sent: Thursday, February 20, 2020 5:41 PM To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Changes to Ceph storage backend provisioning Hello guys. I have been working on a feature to make provisioning of Ceph storage backend optional and the changes will soon merge. Reviews: [1], [2], [3] and [4]. The main purpose of this feature is to allow STX to be installed on systems with a limited number of resources (CPU and RAM mainly, but also hard-drives). If people want to deploy applications that don't require any persistent storage, ceph shouldn't consume RAM and CPU time. IMPORTANT: The stx-openstack application requires persistent storage, and thus requires a ceph storage backend. This change adds a new command that needs to run after the ansible bootstrap, in order to provision the ceph storage backend. The command is: system storage-backend-add ceph --confirmed These changes are also documented in review [4]. There is also the option for users to install a full system without provisioning the Ceph storage backend and then provision it later using the same command. Make sure you update your workflow to take into account this new command. If you encounter any bugs or issues once these changes are merged, feel free to send me an email. Thanks, Stefan [1]: https://review.opendev.org/705234 [2]: https://review.opendev.org/705235 [3]: https://review.opendev.org/705236 [4]: https://review.opendev.org/707385 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Alfredo -- Alfredo -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Feb 25 00:00:47 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 24 Feb 2020 19:00:47 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_repo_sync - Build # 721 - Failure! Message-ID: <1151579331.877.1582588848887.JavaMail.javamailuser@localhost> Project: STX_repo_sync Build #: 721 Status: Failure Timestamp: 20200225T000011Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200225T000001Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200225T000001Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200225T000001Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Tue Feb 25 00:00:51 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 24 Feb 2020 19:00:51 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 450 - Failure! Message-ID: <1609869040.880.1582588852522.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 450 Status: Failure Timestamp: 20200225T000001Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200225T000001Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From yong.hu at intel.com Tue Feb 25 06:29:22 2020 From: yong.hu at intel.com (Yong Hu) Date: Tue, 25 Feb 2020 14:29:22 +0800 Subject: [Starlingx-discuss] Agenda: distro.openstack bi-weekly project meeting on WW09 Message-ID: Here is the agenda for today: 02/25/2020 meeting 1. upgrade Plan [0] review for OpenStack "U" services - Kunpeng,Chant @99Cloud, Zhipeng at Intel 2. LaunchPad [1] review - ALL 3. Open [0]:upgrade plan in details: attached [1] OPEN LPs on distro.openstack: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenStack-U-Upgrade-Plan.pdf Type: application/pdf Size: 30070 bytes Desc: not available URL: From austin.sun at intel.com Tue Feb 25 08:46:59 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 25 Feb 2020 08:46:59 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 2/26/2020 Message-ID: Hi All : Please check Agenda: Agenda for 2/26 meeting: - PRB update ( Wesley and Saul) any feedback from Build Team http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007788.html , currently no feedback from build team. - Ceph containerization ( Martin) - CentOS 8 upgrade (Austin/shuicheng) ---- kernel on master --- std kernel status --- rt kernel status - Python3 on master ( Austin) - Vista Creek (FPGA card) support - Open If have any other topic, feel free to add to https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. From bin.yang at intel.com Tue Feb 25 09:01:40 2020 From: bin.yang at intel.com (Yang, Bin) Date: Tue, 25 Feb 2020 09:01:40 +0000 Subject: [Starlingx-discuss] Cannot find git commit of stx-tools from CONTEXT.sh Message-ID: Hi BUILD team, In http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200224T000004Z/outputs/CONTEXT.sh, the stx-tools git commit is 0555c2a3c746a3a39356feb14f92124ee6f41da5. But I cannot checkout it from git repo. Could you please help to look at it? Thanks, Bin -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Feb 25 15:25:01 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 25 Feb 2020 10:25:01 -0500 Subject: [Starlingx-discuss] Cannot find git commit of stx-tools from CONTEXT.sh In-Reply-To: References: Message-ID: <49668949-e417-4720-7598-4cd9c342483b@windriver.com> Sorry, I had CENGN's stx-tool on a side branch as a work around to enable builds while I was waiting for one of my commits to merge.  Forgot that the sha would be published. The update did merge, but that of course had a conflict with the identical change of the side branch.  I have now discarded the side branch, and done a test repo sync.  I'll launch a CENGN build shortly, and we'll then have a valid build and context. The valid sha is: cefeaad93ad3b0de4cd9eb9fad4b6aa9a06615a1 Scott On 2020-02-25 4:01 a.m., Yang, Bin wrote: > > Hi BUILD team, > >                In > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200224T000004Z/outputs/CONTEXT.sh, > the stx-tools git commit is 0555c2a3c746a3a39356feb14f92124ee6f41da5. > But I cannot checkout it from git repo. > > Could you please help to look at it? > > Thanks, > > Bin > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Feb 25 15:59:54 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 25 Feb 2020 10:59:54 -0500 Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 450 - Failure! In-Reply-To: <1609869040.880.1582588852522.JavaMail.javamailuser@localhost> References: <1609869040.880.1582588852522.JavaMail.javamailuser@localhost> Message-ID: <46c35844-7681-5626-19e7-f13623324c27@windriver.com> We failed on a repo merge conflict. I had CENGN's stx-tool on a side branch as a work around to enable builds while I was waiting for one of my commits to merge. The update did merge, but that of course had a conflict with the identical change of the side branch.  I have now discarded the side branch, and done a test repo sync.  I'll launch a CENGN build shortly, and we'll then have a valid build and context. Scott On 2020-02-24 7:00 p.m., build.starlingx at gmail.com wrote: > Project: STX_build_master_master > Build #: 450 > Status: Failure > Timestamp: 20200225T000001Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200225T000001Z/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 build.starlingx at gmail.com Tue Feb 25 16:17:40 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 25 Feb 2020 11:17:40 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 59 - Failure! Message-ID: <1620042542.886.1582647461721.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 59 Status: Failure Timestamp: 20200225T160508Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200225T153313Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200225T153313Z DOCKER_BUILD_ID: jenkins-master-flock-20200225T153313Z-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/20200225T153313Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200225T153313Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From build.starlingx at gmail.com Tue Feb 25 16:17:44 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 25 Feb 2020 11:17:44 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 22 - Failure! Message-ID: <642909573.889.1582647465087.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 22 Status: Failure Timestamp: 20200225T153313Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200225T153313Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: false From scott.little at windriver.com Tue Feb 25 16:49:21 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 25 Feb 2020 11:49:21 -0500 Subject: [Starlingx-discuss] [Important] STX_build_pre_installer_layered - Build # 53 - Failure! In-Reply-To: <1920916225.872.1582572935463.JavaMail.javamailuser@localhost> References: <1920916225.872.1582572935463.JavaMail.javamailuser@localhost> Message-ID: <792e33c4-3734-dea2-63c5-78d7f3d84cd9@windriver.com> *This was an interesting failure* An update to distributed cloud changed the minimum version of python-oslo-concurrency /cgcs-root/stx/distributedcloud/distributedcloud/centos/distributedcloud.spec:BuildRequires: python-oslo-concurrency>= 3.29.1 A corresponding change was attempted in ... stx-tools/centos-mirror-tools/config/centos/distro/rpms_centos.lst       -python2-oslo-concurrency-3.27.0-1.el7.noarch.rpm       +python2-oslo-concurrency-3.29.1-1.el7.noarch.rpm but it was not made in ... stx-tools/centos-mirror-tools/config/centos/flock/rpms_centos.lst python2-oslo-concurrency-3.27.0-1.el7.noarch.rpm *The monolithic build was ok, but not the flock layer build failed.   Why? * Distributed cloud builds under the flock layer.  The flock layer build only uses flock layer lst file.   So it needs 3.29.1, but only 3.27.0 is available.  Build fails. The monolithic build merges the lst files of all layers.  We ended up with two copies of python2-oslo-concurrency,  3.27.0 and 3.29.1, and the highest version was used in the build.  So all would seem ok if the designer tested with a monolithic build rather than a flock layer build. The monolithic build is going away. *Designers need to do layer builds to test their changes!* Other thoughts ... *Does **python2-oslo-concurrency need to be listed in two places?* Yes. There are distro layer components that BuildRequire python2-oslo-concurrency as well.  A distro layer build would look at stx-tools/centos-mirror-tools/config/centos/distro/rpms_centos.lst *What if I only upversion the flock layer and not the distro layer?* * * While it would have passed build on all layers, I don't think it's a good idea.  The iso is built from the flock layer, and will use the newer version.  The distro layer packages would have run there tox tests versus an older version of the library than would be used at runtime.  An error that might have been caught by a unit test will now only be caught at runtime. All lst files should agree on the version to use. ** *What if the need to upversion was being driven by a distro layer package?  Would I still need to upversion the flock layer lst file in addition to the distro layer lst?* Yes. A package with a 'BuildRequire' on a newer version will also usually have a 'Require' on the newer version as well.   Updating the distro layer lst will allow the distro layer build-pkgs to succeed.  However, build-iso runs under the flock layer, only uses the flock layer lst.  Omitting the flock layer lst update will fail on the 'Require' when build-iso is run. On 2020-02-24 2:35 p.m., build.starlingx at gmail.com wrote: > Project: STX_build_pre_installer_layered > Build #: 53 > Status: Failure > Timestamp: 20200224T192300Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200224T185245Z/logs > -------------------------------------------------------------------------------- > Parameters > > MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200224T185245Z > DOCKER_BUILD_ID: jenkins-master-flock-20200224T185245Z-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/20200224T185245Z/logs > PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200224T185245Z/logs > MASTER_JOB_NAME: STX_build_layer_flock_master_master > LAYER: flock > MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock > BUILD_ISO: 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 build.starlingx at gmail.com Tue Feb 25 19:32:41 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 25 Feb 2020 14:32:41 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_master - Build # 39 - Failure! Message-ID: <61729955.893.1582659162716.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 39 Status: Failure Timestamp: 20200225T193224Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200225T193224Z/logs -------------------------------------------------------------------------------- Parameters FORCE_BUILD: false From maria.g.perez.ibarra at intel.com Tue Feb 25 22:16:54 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 25 Feb 2020 22:16:54 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 02242020 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from FEBRUARY-24-2020 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] We do not have the Virtual results, we are still testing the ceph update during the initial configuration Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Wed Feb 26 00:39:38 2020 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 26 Feb 2020 00:39:38 +0000 Subject: [Starlingx-discuss] [Important] STX_build_pre_installer_layered - Build # 53 - Failure! In-Reply-To: <792e33c4-3734-dea2-63c5-78d7f3d84cd9@windriver.com> References: <1920916225.872.1582572935463.JavaMail.javamailuser@localhost>, <792e33c4-3734-dea2-63c5-78d7f3d84cd9@windriver.com> Message-ID: Hi Scott, It's a fantastic sharing and thanks for comprehensive explanation! Inspired by the case here (with 2 versions of python-oslo-concurrency for different layers), I would like to hear your ideas on a similar case (a tech challenge) which we met during CentOS 8 upgrade. Simply we wanted to use new version gcc-8.2.1 for kernel 4.18, and then old version gcc-4.8.5 for user space packages. Is there a way to support this case above under the context of layered build design? We know currently kernel (and out of tree kernel modules) and a set user space packages belong to "disto" layer. But what if we create a new layer for kernel and kernel related modules? Will this make 2 different versions of GCC work for 2 layers? regards, Yong ________________________________ From: Scott Little [scott.little at windriver.com] Sent: Wednesday, February 26, 2020 12:49 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Important] STX_build_pre_installer_layered - Build # 53 - Failure! This was an interesting failure An update to distributed cloud changed the minimum version of python-oslo-concurrency /cgcs-root/stx/distributedcloud/distributedcloud/centos/distributedcloud.spec:BuildRequires: python-oslo-concurrency >= 3.29.1 A corresponding change was attempted in ... stx-tools/centos-mirror-tools/config/centos/distro/rpms_centos.lst -python2-oslo-concurrency-3.27.0-1.el7.noarch.rpm +python2-oslo-concurrency-3.29.1-1.el7.noarch.rpm but it was not made in ... stx-tools/centos-mirror-tools/config/centos/flock/rpms_centos.lst python2-oslo-concurrency-3.27.0-1.el7.noarch.rpm The monolithic build was ok, but not the flock layer build failed. Why? Distributed cloud builds under the flock layer. The flock layer build only uses flock layer lst file. So it needs 3.29.1, but only 3.27.0 is available. Build fails. The monolithic build merges the lst files of all layers. We ended up with two copies of python2-oslo-concurrency, 3.27.0 and 3.29.1, and the highest version was used in the build. So all would seem ok if the designer tested with a monolithic build rather than a flock layer build. The monolithic build is going away. Designers need to do layer builds to test their changes! Other thoughts ... Does python2-oslo-concurrency need to be listed in two places? Yes. There are distro layer components that BuildRequire python2-oslo-concurrency as well. A distro layer build would look at stx-tools/centos-mirror-tools/config/centos/distro/rpms_centos.lst What if I only upversion the flock layer and not the distro layer? While it would have passed build on all layers, I don't think it's a good idea. The iso is built from the flock layer, and will use the newer version. The distro layer packages would have run there tox tests versus an older version of the library than would be used at runtime. An error that might have been caught by a unit test will now only be caught at runtime. All lst files should agree on the version to use. What if the need to upversion was being driven by a distro layer package? Would I still need to upversion the flock layer lst file in addition to the distro layer lst? Yes. A package with a 'BuildRequire' on a newer version will also usually have a 'Require' on the newer version as well. Updating the distro layer lst will allow the distro layer build-pkgs to succeed. However, build-iso runs under the flock layer, only uses the flock layer lst. Omitting the flock layer lst update will fail on the 'Require' when build-iso is run. On 2020-02-24 2:35 p.m., build.starlingx at gmail.com wrote: Project: STX_build_pre_installer_layered Build #: 53 Status: Failure Timestamp: 20200224T192300Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200224T185245Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200224T185245Z DOCKER_BUILD_ID: jenkins-master-flock-20200224T185245Z-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/20200224T185245Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200224T185245Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: 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 bin.yang at intel.com Wed Feb 26 02:51:46 2020 From: bin.yang at intel.com (Yang, Bin) Date: Wed, 26 Feb 2020 02:51:46 +0000 Subject: [Starlingx-discuss] Cannot find git commit of stx-tools from CONTEXT.sh In-Reply-To: <49668949-e417-4720-7598-4cd9c342483b@windriver.com> References: <49668949-e417-4720-7598-4cd9c342483b@windriver.com> Message-ID: Thank you very much for your quick response Thanks, Bin From: Scott Little Sent: Tuesday, February 25, 2020 23:25 To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Cannot find git commit of stx-tools from CONTEXT.sh Sorry, I had CENGN's stx-tool on a side branch as a work around to enable builds while I was waiting for one of my commits to merge. Forgot that the sha would be published. The update did merge, but that of course had a conflict with the identical change of the side branch. I have now discarded the side branch, and done a test repo sync. I'll launch a CENGN build shortly, and we'll then have a valid build and context. The valid sha is: cefeaad93ad3b0de4cd9eb9fad4b6aa9a06615a1 Scott On 2020-02-25 4:01 a.m., Yang, Bin wrote: Hi BUILD team, In http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200224T000004Z/outputs/CONTEXT.sh, the stx-tools git commit is 0555c2a3c746a3a39356feb14f92124ee6f41da5. But I cannot checkout it from git repo. Could you please help to look at it? Thanks, Bin _______________________________________________ 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 yu.chengde at 99cloud.net Wed Feb 26 10:42:18 2020 From: yu.chengde at 99cloud.net (YuChengDe) Date: Wed, 26 Feb 2020 18:42:18 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?Failed_when_build_StarlingX_docker_?= =?utf-8?q?images?= Message-ID: Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Feb 26 13:29:50 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 26 Feb 2020 13:29:50 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Feb 26, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B9CB02@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of today's TSC/Community call [2]. We'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200226T1500 From ji at sibyl.li Wed Feb 26 14:02:32 2020 From: ji at sibyl.li (Austin Gillmann) Date: Wed, 26 Feb 2020 08:02:32 -0600 Subject: [Starlingx-discuss] Openstack Nginx Refusing some Connections Message-ID: Hi all, I have a panel setup that makes requests to keystone, but after an amount of time the panel will error out saying the connection to keystone was refused, but I can still access it fine from my end. Is there some sort of rate limiting that could be occurring, if so how would I go about whitelisting an IP for it? Thanks! Austin Gillmann -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Wed Feb 26 14:44:42 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 26 Feb 2020 14:44:42 +0000 Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 2/26/2020 Message-ID: Hi All: Thanks join the call . MoM for 2/26 meeting: - PRB update ( Wesley and Saul) any feedback from Build Team http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007788.html , currently no feedback from build team. ---- Build ISO and do test , Saul has commented in gerrit review. - Ceph containerization ( Martin) focusing on migrate from native ceph cluster to containerizated ceph cluster. helm plugin for rook is ok and create a new application . static paremeters should be in aramada values. any feedback from http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007848.html http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007820.html - CentOS 8 upgrade (Austin/shuicheng) ---- kernel on master --- std kernel status http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007844.html , any feedback or it's ok ? 147.3.1 kernel could do sanity test on simplex. --- out of tree kernel driver rebase status most kernel module rebase successfully except tpm/integrity tpm/integrity kernel changes are risk , --- rt kernel status - to support new kernel-rt , one new rt-setup rpms (get from https://git.centos.org/rpms/rt-setup/blob/c8/f/SPECS/rt-setup.spec) - kernel-rt-tools enabled (by default is disabled) - tis_extra are merged w/ default config - rt kernel patches rebased (dropped some patches) --- test plan most out of tree kernel driver are rebased , who have hardware and can perform test ? conitinue to check any possiable to start test . - Python3 on master ( Austin) https://review.opendev.org/#/c/709960/ https://review.opendev.org/#/c/709958/ nova-api-proxy https://review.opendev.org/#/c/709980/ nfv https://review.opendev.org/#/c/709983/ - Vista Creek (FPGA card) support SRIOV function , NPG would not be able to merge PR soon. - Open Thanks. BR Austin Sun. From Don.Penney at windriver.com Wed Feb 26 15:37:38 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 26 Feb 2020 15:37:38 +0000 Subject: [Starlingx-discuss] Failed when build StarlingX docker images In-Reply-To: References: Message-ID: I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 [Image removed by sender.] -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD000.jpg Type: image/jpeg Size: 823 bytes Desc: ~WRD000.jpg URL: From Bill.Zvonar at windriver.com Wed Feb 26 15:49:28 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 26 Feb 2020 15:49:28 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Feb 26, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B9CDE2@ALA-MBD.corp.ad.wrs.com> >From today's call... - Standing Topics - Sanity - both Monolithic & Layered builds are happening now - per Nicolae, both look green now - currently, to know which one it is, check the part that says "Status of the Sanity Test" - if the link references ../outputs/iso, then it's a monolithic build - if the link references ../flock/../outputs, then it's a layered build - should start seeing sanity reports for both, they will run alternately - Reviews - nothing new this week - CentOS 8 - progressing towards sanitizing with the new kernel (std & rt) - Topics for This Week - Validation team - Robot vs Pytest Q&A - some questions to bring to Test Meeting and/or Yang (Test PL) - R4 Doc Tasks - will be covered in *this* week's release team meeting (we didn't have the meeting last week) - Open Requests for Help - nothing new this week (well, a couple of very recent ones, but we'll let the Community review) -----Original Message----- From: Zvonar, Bill Sent: Wednesday, February 26, 2020 8:30 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: Community (& TSC) Call (Feb 26, 2020) Hi all, reminder of today's TSC/Community call [2]. We'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200226T1500 From Don.Penney at windriver.com Wed Feb 26 16:24:30 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 26 Feb 2020 16:24:30 +0000 Subject: [Starlingx-discuss] Failed when build StarlingX docker images In-Reply-To: References: Message-ID: I was able to successfully build stx-nova image in master with no changes. Do you have any customizations in your environment? From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 26, 2020 10:38 AM To: YuChengDe; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 [Image removed by sender.] -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From scott.little at windriver.com Wed Feb 26 20:59:15 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 26 Feb 2020 15:59:15 -0500 Subject: [Starlingx-discuss] [Important] STX_build_pre_installer_layered - Build # 53 - Failure! In-Reply-To: References: <1920916225.872.1582572935463.JavaMail.javamailuser@localhost> <792e33c4-3734-dea2-63c5-78d7f3d84cd9@windriver.com> Message-ID: <977e28ba-ac67-5f90-3545-09fabb336174@windriver.com> The only way to make this work is to place the kernel and out-of-tree kernel modules into a layer of their own. Scott On 2020-02-25 7:39 p.m., Hu, Yong wrote: > Hi Scott, > It's a fantastic sharing and thanks for comprehensive explanation! > > Inspired by the case here (with 2 versions of python-oslo-concurrency > for different layers), I would like to hear your ideas on a similar > case (a tech challenge) which we met during CentOS 8 upgrade. Simply > we wanted to use new version gcc-8.2.1 for kernel 4.18, and then old > version gcc-4.8.5 for user space packages. > Is there a way to support this case above under the context of layered > build design? > We know currently kernel (and out of tree kernel modules) and a set > user space packages belong to "disto" layer. > But what if we create a new layer for kernel and kernel related > modules?  Will this make 2 different versions of GCC work for 2 layers? > > regards, > Yong > ------------------------------------------------------------------------ > *From:* Scott Little [scott.little at windriver.com] > *Sent:* Wednesday, February 26, 2020 12:49 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] [Important] > STX_build_pre_installer_layered - Build # 53 - Failure! > > *This was an interesting failure* > > An update to distributed cloud changed the minimum version of > python-oslo-concurrency > > /cgcs-root/stx/distributedcloud/distributedcloud/centos/distributedcloud.spec:BuildRequires: > python-oslo-concurrency>= 3.29.1 > > A corresponding change was attempted in ... > > stx-tools/centos-mirror-tools/config/centos/distro/rpms_centos.lst >       -python2-oslo-concurrency-3.27.0-1.el7.noarch.rpm >       +python2-oslo-concurrency-3.29.1-1.el7.noarch.rpm > > but it was not made in ... > > stx-tools/centos-mirror-tools/config/centos/flock/rpms_centos.lst >       python2-oslo-concurrency-3.27.0-1.el7.noarch.rpm > > *The monolithic build was ok, but not the flock layer build failed.   > Why? * > > Distributed cloud builds under the flock layer.  The flock layer build > only uses flock layer lst file.   So it needs 3.29.1, but only 3.27.0 > is available.  Build fails. > > The monolithic build merges the lst files of all layers.  We ended up > with two copies of python2-oslo-concurrency,  3.27.0 and 3.29.1, and > the highest version was used in the build.  So all would seem ok if > the designer tested with a monolithic build rather than a flock layer > build. > > The monolithic build is going away. > > *Designers need to do layer builds to test their changes!* > > > Other thoughts ... > > *Does **python2-oslo-concurrency need to be listed in two places?* > > Yes. > > There are distro layer components that BuildRequire > python2-oslo-concurrency as well.  A distro layer build would look at > stx-tools/centos-mirror-tools/config/centos/distro/rpms_centos.lst > > *What if I only upversion the flock layer and not the distro layer?* > * > * > While it would have passed build on all layers, I don't think it's a > good idea. The iso is built from the flock layer, and will use the > newer version.  The distro layer packages would have run there tox > tests versus an older version of the library than would be used at > runtime.  An error that might have been caught by a unit test will now > only be caught at runtime. > > All lst files should agree on the version to use. > > *What if the need to upversion was being driven by a distro layer > package? Would I still need to upversion the flock layer lst file in > addition to the distro layer lst?* > > Yes. > > A package with a 'BuildRequire' on a newer version will also usually > have a 'Require' on the newer version as well.   Updating the distro > layer lst will allow the distro layer build-pkgs to succeed.  However, > build-iso runs under the flock layer, only uses the flock layer lst.  > Omitting the flock layer lst update will fail on the 'Require' when > build-iso is run. > > > > > > > > > On 2020-02-24 2:35 p.m., build.starlingx at gmail.com wrote: >> Project: STX_build_pre_installer_layered >> Build #: 53 >> Status: Failure >> Timestamp: 20200224T192300Z >> >> Check logs at: >> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200224T185245Z/logs >> -------------------------------------------------------------------------------- >> Parameters >> >> MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200224T185245Z >> DOCKER_BUILD_ID: jenkins-master-flock-20200224T185245Z-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/20200224T185245Z/logs >> PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200224T185245Z/logs >> MASTER_JOB_NAME: STX_build_layer_flock_master_master >> LAYER: flock >> MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock >> BUILD_ISO: 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 Frank.Miller at windriver.com Wed Feb 26 22:22:44 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Wed, 26 Feb 2020 22:22:44 +0000 Subject: [Starlingx-discuss] Weekly build meeting cancelled for Feb 27 Message-ID: Our next build meeting will occur on March 5th. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Wed Feb 26 23:16:30 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Wed, 26 Feb 2020 23:16:30 +0000 Subject: [Starlingx-discuss] [docs][meeting] docs team meeting minutes 2020-02-26 Message-ID: Hello All, Here are this week's docs team meeting minutes. Join us if you have interest in StarlingX docs! We meet Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Cheers, Kris 2020-02-26 * All -- reviews merged since last week: 5 (plus 1 abandonded) * All -- bug status -- no change * R4 target content: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.4.0&project_id=1046 * Changes needed? http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007847.html * Windows Active Dir content -- ready to add -- http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007710.html ? Where should this go? - Add to config section under K8s (follow up with reference from R4 install guides, likely Remote CLIs for Access K8s) * Assignment of R4 doc tasks -- will be discussed in this weeks build meeting. * Opens * Kris -- Transition plan: https://etherpad.openstack.org/p/docs-transition-plan ? 2 opens, would like to resolve this week. Need some decisions. * Training review: https://review.opendev.org/#/c/704721/ -- recommend dropping when training done, and updating current contrib guide with a few more details. Decision? -- review abandonded. o Follow up minor edits per transition plan here: https://review.opendev.org/#/c/710152/ * How does the team page need to be updated? * All -- Wiki status ? Revisit planned migration of wiki content: lets close this out (see yellow). https://docs.google.com/spreadsheets/d/1UJjUttsWQRyauATrip0wKGIxSO7DvyetDKmPwvEIDaA/edit?usp=sharing * All -- Ongoing tasks: * STX in a box: (https://storyboard.openstack.org/#!/story/2006622) ? Draft in review https://review.opendev.org/#/c/692202/ ? Next steps (GREG) - Greg will spend a little time investigating possible scripted try-before-buy option using exisitng deployment stuff. -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Wed Feb 26 23:23:44 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Wed, 26 Feb 2020 23:23:44 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200226 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-February-26 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From poornima.y.n at intel.com Thu Feb 27 08:10:30 2020 From: poornima.y.n at intel.com (N, Poornima Y) Date: Thu, 27 Feb 2020 08:10:30 +0000 Subject: [Starlingx-discuss] Query on StarlingX R3.0 virtual All-in-one Simplex Message-ID: <337CF5EE66FD714294A89A3DB1597BA28CA35A9C@BGSMSX101.gar.corp.intel.com> Hi all, I have tried deploying Starlinx 3.0 virtual All-in-one Simplex. I'm following https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/aio_simplex_environ.html . While doing Host Set-up, 4th step which is 4. Get the StarlingX ISO from the CENGN StarlingX mirror. Alternately, you can use an ISO from a private StarlingX build. I get as below . [cid:image003.jpg at 01D5ED73.7966F470] Can anyone make me understand, what each of the folder stands for?. Also, as a first timer which folder I need to go and download the ISO.? I have tried 3.0.0 under release, but ended up with issues. Should there be a direct link to output folder when I select Get the StarlingX ISO from the CENGN StarlingX mirror? Thanks, Poornima -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 35993 bytes Desc: image003.jpg URL: From yong.hu at intel.com Thu Feb 27 08:18:29 2020 From: yong.hu at intel.com (Yong Hu) Date: Thu, 27 Feb 2020 16:18:29 +0800 Subject: [Starlingx-discuss] Query on StarlingX R3.0 virtual All-in-one Simplex In-Reply-To: <337CF5EE66FD714294A89A3DB1597BA28CA35A9C@BGSMSX101.gar.corp.intel.com> References: <337CF5EE66FD714294A89A3DB1597BA28CA35A9C@BGSMSX101.gar.corp.intel.com> Message-ID: <00c71c17-477a-e8e6-1b8e-e0c1e6a77301@intel.com> ISO for 3.0 release is under this folder: http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/ If you see issues, you can describe the issues here. On 2020/2/27 4:10 PM, N, Poornima Y wrote: > Hi all, > > I have tried deploying Starlinx 3.0 virtual All-in-one Simplex. > > I’m following > https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/aio_simplex_environ.html > . > > While doing *Host Set-up,  4^th step which is* > > *4. *Get the StarlingX ISO from the CENGN StarlingX mirror > . Alternately, you > can use an ISO from a private StarlingX build. > > I get as below . > > Can anyone make me understand, what each of the folder stands for?. > Also, as a first timer which folder I need to go and download the ISO.? > > I have tried 3.0.0 under release, but ended up with issues. Should there > be a direct link to output folder when I select Get the StarlingX ISO > from the CENGN StarlingX mirror > ? > > Thanks, > > Poornima > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From poornima.y.n at intel.com Thu Feb 27 08:52:16 2020 From: poornima.y.n at intel.com (N, Poornima Y) Date: Thu, 27 Feb 2020 08:52:16 +0000 Subject: [Starlingx-discuss] Query on StarlingX R3.0 virtual All-in-one Simplex In-Reply-To: <00c71c17-477a-e8e6-1b8e-e0c1e6a77301@intel.com> References: <337CF5EE66FD714294A89A3DB1597BA28CA35A9C@BGSMSX101.gar.corp.intel.com> <00c71c17-477a-e8e6-1b8e-e0c1e6a77301@intel.com> Message-ID: <337CF5EE66FD714294A89A3DB1597BA28CA35B19@BGSMSX101.gar.corp.intel.com> When I faced issues while I was installing 3.0.0 ISO, I checked /etc/buildinfo, It said, it is a 2.0 release build!. I'm not sure whether anyone has faced this issue. Finally, I tried with ISO under http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/outputs/iso/ which worked as expected. Hence , I wanted to understand what each folder means in the link http://mirror.starlingx.cengn.ca/mirror/starlingx for my future reference. Thanks, Poornima -----Original Message----- From: Hu, Yong Sent: Thursday, February 27, 2020 1:48 PM To: N, Poornima Y ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Query on StarlingX R3.0 virtual All-in-one Simplex ISO for 3.0 release is under this folder: http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/ If you see issues, you can describe the issues here. On 2020/2/27 4:10 PM, N, Poornima Y wrote: > Hi all, > > I have tried deploying Starlinx 3.0 virtual All-in-one Simplex. > > I'm following > https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/aio > _simplex_environ.html > . > > While doing *Host Set-up,  4^th step which is* > > *4. *Get the StarlingX ISO from the CENGN StarlingX mirror > . Alternately, you > can use an ISO from a private StarlingX build. > > I get as below . > > Can anyone make me understand, what each of the folder stands for?. > Also, as a first timer which folder I need to go and download the ISO.? > > I have tried 3.0.0 under release, but ended up with issues. Should > there be a direct link to output folder when I select Get the > StarlingX ISO from the CENGN StarlingX mirror > ? > > Thanks, > > Poornima > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From nicolae.jascanu at intel.com Thu Feb 27 10:21:42 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Thu, 27 Feb 2020 10:21:42 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200225 - LAYERED BUILD Message-ID: Status of the Sanity Test for last LAYERED BUILD - CENGN ISO: bootimage.iso from 2020-February-25 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200225T194204Z/outputs/iso/) Status: RED =========================================== Sanity Test Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] The following bug is created for the issue with Simplex and Duplex: https://bugs.launchpad.net/starlingx/+bug/1864221 Regards, STX Validation Team Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From mward at akamai.com Thu Feb 27 12:13:42 2020 From: mward at akamai.com (Ward, Martin) Date: Thu, 27 Feb 2020 12:13:42 +0000 Subject: [Starlingx-discuss] =?utf-8?q?A_couple_of_notes_on_the_current_R3?= =?utf-8?q?_Simplex_installation_docs=2C=C2=A0plus_where=27s_LDAP_gone=3F?= Message-ID: Hi, Having gone through the install docs a couple of times now I have few items that I think are worthy of note. Could you please provide some explanation of the networking before the actual installation steps? It took me three installs to get my head around what was intended here. I would suggest a section in the doc that describes the interfaces being created on the physical and virtual servers and what their intended uses are (I still don’t know what the stxbr and vnet interfaces are for). In the VM itself I have an interface called enp4s1, in the doc it is referred to as enp7s1. Perhaps the name changes depending on something external to the Ansible script, I don’t know, but it would be useful to either align the doc with reality or make mention that the interface name could be different. Finally, having gone through the latest install, everything was fine until I tried to run “system host-label-assign controller-0” commands for the “OpenStack-specific host configuration” section. It kept returning “File not found”, while trying to access 192.168.204.1 I think. I tried Microsoft Resolution #1 and rebooted the VM, now I cannot sudo to root because the VM cannot access LDAP, which means I cannot work out the problem from the logs. I’ve checked and slapd is definitely in the process list. Any recommendations for what to look for here? I’m going to reinstall again and this time I will reset the root password before I do anything else, but I still need to work out what’s wrong with LDAP. |\\/|artin -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Thu Feb 27 13:00:38 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 27 Feb 2020 13:00:38 +0000 Subject: [Starlingx-discuss] IPv6 issue when apply OpenStack on IPv6 simplex. Message-ID: <93814834B4855241994F290E959305C753144F59@SHSMSX104.ccr.corp.intel.com> Hi all, For below LP IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status" https://bugs.launchpad.net/starlingx/+bug/1859641 I provided a patch which can fix the known issue in LP. However, it still failed later when starting rabbitmq pod. controller-0:~$ kubectl -n openstack get po NAME READY STATUS RESTARTS AGE ingress-c74489c96-jsb7n 1/1 Running 0 17h ingress-error-pages-5889bfcf6c-h8kl6 1/1 Running 0 17h mariadb-ingress-b5cd65f4b-sq46c 1/1 Running 0 17h mariadb-ingress-error-pages-6d8b79b74f-9zmpc 1/1 Running 0 17h mariadb-server-0 1/1 Running 0 17h osh-openstack-memcached-memcached-545668bdbd-9jkv2 1/1 Running 0 17h osh-openstack-rabbitmq-cluster-wait-wbnwp 0/1 Init:0/2 0 17h osh-openstack-rabbitmq-rabbitmq-0 0/1 CrashLoopBackOff 207 17h There are below error logs 2020-02-26T07:43:36.451103975Z stderr F ++ echo osh-openstack-rabbitmq-rabbitmq-0 2020-02-26T07:43:36.45142814Z stderr F ++ awk -F - '{print $NF}' 2020-02-26T07:43:36.454160452Z stderr F + POD_INCREMENT=0 2020-02-26T07:43:36.454757022Z stderr F + '[' 0 -eq 0 ']' 2020-02-26T07:43:36.454795721Z stderr F + exec rabbitmq-server 2020-02-26T07:43:36.849021551Z stdout F ERROR: epmd error for host osh-openstack-rabbitmq-rabbitmq-0.rabbitmq.openstack.svc.cluster.local: nxdomain (non-existing domain) In /etc/hosts file below, I just found localhost4, no localhost6. Is it expected? I added below line manually after the line of 127.0.0.1. However, it didn’t work☹ ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 # HEADER: This file was autogenerated at 2020-02-26 09:00:35 +0000 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 fd01::1 controller 169.254.202.1 pxecontroller fd00::3 oamcontroller fd01::4 controller-platform-nfs fd01::3 controller-1 fd01::2 controller-0 fd02::3 controller-1-cluster-host fd02::2 controller-0-cluster-host fd01::e8b6:66fe storage-0 I saw that in ./stx-puppet/puppet-manifests/src/modules/platform/manifests/config.pp:215 class platform::config::hosts inherits ::platform::config::params { # The localhost should resolve to the IPv4 loopback address only, therefore # ensure the IPv6 address is removed from configured hosts resources { 'host': purge => true } $localhost = { 'localhost' => { ip => '127.0.0.1', host_aliases => ['localhost.localdomain', 'localhost4', 'localhost4.localdomain4'] }, } $merged_hosts = merge($localhost, $hosts) create_resources('host', $merged_hosts, {}) } Any one can give some help? Thanks! Zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Angie.Wang at windriver.com Thu Feb 27 15:17:23 2020 From: Angie.Wang at windriver.com (Wang, Jing (Angie)) Date: Thu, 27 Feb 2020 15:17:23 +0000 Subject: [Starlingx-discuss] [docs]Provide doc input for 2006781 Message-ID: Hi All, The attached file is the documentation changes required for the story "Kubernetes upgrade support in StarlingX" (https://storyboard.openstack.org/#!/story/2006781). Thanks, Angie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2006781_Kubernetes Upgrade Documentation.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 29533 bytes Desc: 2006781_Kubernetes Upgrade Documentation.docx URL: From scott.little at windriver.com Thu Feb 27 16:08:37 2020 From: scott.little at windriver.com (Scott Little) Date: Thu, 27 Feb 2020 11:08:37 -0500 Subject: [Starlingx-discuss] CENGN has begun the process of mirroring CentOS 8 Message-ID: <2372d317-b2a3-41c5-d9c8-d4273c0ef62e@windriver.com> CENGN has begun the process of mirroring CentOS 8. EPEL 8 will follow. I'm not going to hazard a guess as to the ETA for completing the first pass just yet. Scott From sgw at linux.intel.com Thu Feb 27 16:12:07 2020 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 27 Feb 2020 08:12:07 -0800 Subject: [Starlingx-discuss] Query on StarlingX R3.0 virtual All-in-one Simplex In-Reply-To: <337CF5EE66FD714294A89A3DB1597BA28CA35B19@BGSMSX101.gar.corp.intel.com> References: <337CF5EE66FD714294A89A3DB1597BA28CA35A9C@BGSMSX101.gar.corp.intel.com> <00c71c17-477a-e8e6-1b8e-e0c1e6a77301@intel.com> <337CF5EE66FD714294A89A3DB1597BA28CA35B19@BGSMSX101.gar.corp.intel.com> Message-ID: On 2/27/20 12:52 AM, N, Poornima Y wrote: > When I faced issues while I was installing 3.0.0 ISO, I checked /etc/buildinfo, It said, it is a 2.0 release build!. I'm not sure whether anyone has faced this issue. > Finally, I tried with ISO under http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/outputs/iso/ which worked as expected. > Hence , I wanted to understand what each folder means in the link > http://mirror.starlingx.cengn.ca/mirror/starlingx for my future reference. > One thing you can verify is the md5sum and/or sha256sum of the iso file. I know we have a .sig file, but having the chksum would be an easier way to validate the file is correct. You can check with other folks who may have downloaded the 3.0.0 image and verify that you have the correct one. Sau! > Thanks, > Poornima > > -----Original Message----- > From: Hu, Yong > Sent: Thursday, February 27, 2020 1:48 PM > To: N, Poornima Y ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Query on StarlingX R3.0 virtual All-in-one Simplex > > ISO for 3.0 release is under this folder: > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/ > > If you see issues, you can describe the issues here. > > > On 2020/2/27 4:10 PM, N, Poornima Y wrote: >> Hi all, >> >> I have tried deploying Starlinx 3.0 virtual All-in-one Simplex. >> >> I'm following >> https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/aio >> _simplex_environ.html >> . >> >> While doing *Host Set-up,  4^th step which is* >> >> *4. *Get the StarlingX ISO from the CENGN StarlingX mirror >> . Alternately, you >> can use an ISO from a private StarlingX build. >> >> I get as below . >> >> Can anyone make me understand, what each of the folder stands for?. >> Also, as a first timer which folder I need to go and download the ISO.? >> >> I have tried 3.0.0 under release, but ended up with issues. Should >> there be a direct link to output folder when I select Get the >> StarlingX ISO from the CENGN StarlingX mirror >> ? >> >> Thanks, >> >> Poornima >> >> >> _______________________________________________ >> 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 sgw at linux.intel.com Thu Feb 27 16:13:16 2020 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 27 Feb 2020 08:13:16 -0800 Subject: [Starlingx-discuss] CENGN has begun the process of mirroring CentOS 8 In-Reply-To: <2372d317-b2a3-41c5-d9c8-d4273c0ef62e@windriver.com> References: <2372d317-b2a3-41c5-d9c8-d4273c0ef62e@windriver.com> Message-ID: On 2/27/20 8:08 AM, Scott Little wrote: > CENGN has begun the process of mirroring CentOS 8. EPEL 8 will follow. > Thanks Scott! This will help smooth out some of the changes we are seeing with the f/centos8 branch. > I'm not going to hazard a guess as to the ETA for completing the first > pass just yet. > Please keep us posted, we can test the usage of it next week. Sau! > Scott > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From mihail-laurentiu.trica at intel.com Thu Feb 27 16:27:43 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Thu, 27 Feb 2020 16:27:43 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200226 - LAYERED BUILD Message-ID: Status of the Sanity Test for last LAYERED BUILD - CENGN ISO: bootimage.iso from 2020-February-26 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200226T090221Z/outputs/iso/) Status: RED =========================================== Sanity Test Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] The bug that was created for the issue with Simplex and Duplex is still reproducible with the latest build: https://bugs.launchpad.net/starlingx/+bug/1864221 Regards, STX Validation Team Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Fri Feb 28 03:07:53 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Fri, 28 Feb 2020 03:07:53 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200227 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-February-27 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] App platform-integ-apps failed to apply (error get configmaps) https://bugs.launchpad.net/starlingx/+bug/1856078 Regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From mingyuan.qi at intel.com Fri Feb 28 10:00:44 2020 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Fri, 28 Feb 2020 10:00:44 +0000 Subject: [Starlingx-discuss] [docs]Provide doc input for 2006781 In-Reply-To: References: Message-ID: Hi Angie, The feature looks great that we can now upgrade the k8s cluster at runtime. Regarding the details, I and other folks have several questions that we didn't find clues in the doc. Could you please give us the info from designer's view? * Why the upgrade complete cmd line needed? Any essential checks? * If the first master node upgrade completed on the active controller, that means the active control plane is upgraded to the new version. Then how to ensure the compatibility between upgraded controller plane and un-upgraded kubelet before step 12? * What will happen if some nodes restart unexpectedly between step 11 and 12? * How to deal with the certificates and keys of Kubernetes during upgrading? * Is upgrade rollback supported regardless the upgrade completion? * Is kubelet/kubectl patch marked as in-service patch or reboot-required patch? * Why lock/unlock is needed to upgrade kubelet? Is there a way to avoid that? Since this will impact the running pods on all nodes. Thanks, Mingyuan From: Wang, Jing (Angie) Sent: Thursday, February 27, 2020 23:17 To: starlingx-discuss at lists.starlingx.io Cc: Dale, Kristal Subject: [Starlingx-discuss] [docs]Provide doc input for 2006781 Hi All, The attached file is the documentation changes required for the story "Kubernetes upgrade support in StarlingX" (https://storyboard.openstack.org/#!/story/2006781). Thanks, Angie -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Fri Feb 28 14:14:11 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Fri, 28 Feb 2020 14:14:11 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200227 - LAYERED BUILD Message-ID: Status of the Sanity Test for last LAYERED BUILD - CENGN ISO: bootimage.iso from 2020-February-26 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200227T122131Z/outputs/iso/) Status: RED =========================================== Sanity Test Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] The bug that was created for the issue with Simplex and Duplex is still reproducible with the latest build: https://bugs.launchpad.net/starlingx/+bug/1864221 Regards, STX Validation Team Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From Barton.Wensley at windriver.com Fri Feb 28 14:24:44 2020 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Fri, 28 Feb 2020 14:24:44 +0000 Subject: [Starlingx-discuss] [docs]Provide doc input for 2006781 In-Reply-To: References: Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1C15B4C@ALA-MBD.corp.ad.wrs.com> Good questions Mingyuan. Since I did the original design for k8s upgrades I'll reply to your questions (see below). Bart From: Qi, Mingyuan [mailto:mingyuan.qi at intel.com] Sent: February 28, 2020 5:01 AM To: Wang, Jing (Angie); starlingx-discuss at lists.starlingx.io Cc: Dale, Kristal Subject: Re: [Starlingx-discuss] [docs]Provide doc input for 2006781 Hi Angie, The feature looks great that we can now upgrade the k8s cluster at runtime. Regarding the details, I and other folks have several questions that we didn't find clues in the doc. Could you please give us the info from designer's view? * Why the upgrade complete cmd line needed? Any essential checks? [Bart] This command does a final check to verify that all the k8s components are now running the new release and then updates the state to upgrade-complete. * If the first master node upgrade completed on the active controller, that means the active control plane is upgraded to the new version. Then how to ensure the compatibility between upgraded controller plane and un-upgraded kubelet before step 12? [Bart] The k8s version skew policy (https://kubernetes.io/docs/setup/release/version-skew-policy) specifies that the kubelet may be up to two minor versions older than the kube-apiserver. Any k8s upgrades done to StarlingX deployments must respect those rules. * What will happen if some nodes restart unexpectedly between step 11 and 12? [Bart] The kubelet on the node that restarts would come up running the new version, but would be reading the old format of the kubelet config file. This should be supported (new values in the config file will be defaulted). The user can still run the kube-host-upgrade command after this to upgrade the kubelet config file. * How to deal with the certificates and keys of Kubernetes during upgrading? [Bart] As mentioned in the spec (https://docs.starlingx.io/specs/specs/stx-4.0/approved/containerization-2006781-kubernetes-upgrades.html), we are using the kubeadm command to perform the upgrade. It will take care of anything certificate and key related. * Is upgrade rollback supported regardless the upgrade completion? [Bart] There is no support for rollback. I'm not sure if we will add this in the future - the general consensus in the k8s community is that k8s downgrades are not supported. * Is kubelet/kubectl patch marked as in-service patch or reboot-required patch? [Bart] It is an in-service patch. * Why lock/unlock is needed to upgrade kubelet? Is there a way to avoid that? Since this will impact the running pods on all nodes. [Bart] It is not safe to upgrade the kubelet while there are pods running on the node. The lock will move the pods off the node. In the future, when we add orchestration of k8s upgrades (with the VIM), we will likely add support to move the pods off the node without locking it, which would avoid the reboot of the node when the kubelet was upgraded. Thanks, Mingyuan From: Wang, Jing (Angie) Sent: Thursday, February 27, 2020 23:17 To: starlingx-discuss at lists.starlingx.io Cc: Dale, Kristal Subject: [Starlingx-discuss] [docs]Provide doc input for 2006781 Hi All, The attached file is the documentation changes required for the story "Kubernetes upgrade support in StarlingX" (https://storyboard.openstack.org/#!/story/2006781). Thanks, Angie -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Fri Feb 28 16:07:33 2020 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 28 Feb 2020 08:07:33 -0800 Subject: [Starlingx-discuss] Query on StarlingX R3.0 virtual All-in-one Simplex In-Reply-To: <337CF5EE66FD714294A89A3DB1597BA28CA35A9C@BGSMSX101.gar.corp.intel.com> References: <337CF5EE66FD714294A89A3DB1597BA28CA35A9C@BGSMSX101.gar.corp.intel.com> Message-ID: Sorry, I don't think I correctly answered the question Poornima had, and I think that it might be beneficial to add a README to the top level, describing the directory structure. It might also be worth making a couple of tweaks. Under /mirror/starlingx we have the following: centos - contains what a copy of the 2018.10 release export - Empty (can we remove it??) f - Contains older builds from cento76 and stein upgrade work feature - same as f, could be both be removed or archived? master - contains master daily builds for both older monolithic build and new layered build /centos/lastest_build - points to the artifacts for the latest daily build /centos/flock/latest_build - points to the latest daily layered build artifacts. milestone - older builds from Jan 25, 2019 (looks like testing of somekind)? rc - contains build artifacts from the Release Candidates for 2.0 and 3.0 release - contains the artifacts for all the releases, not sure if we should have an archive directory or EOLed directory here, alternatively a README say how long support for each release could continue for. Maybe creating an /mirror/starlingx/archive to move 2018.10 and older feature branch builds and milestone builds Thoughts from the community? Sau! On 2/27/20 12:10 AM, N, Poornima Y wrote: > Hi all, > > I have tried deploying Starlinx 3.0 virtual All-in-one Simplex. > > I’m following > https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/aio_simplex_environ.html > . > > While doing *Host Set-up,  4^th step which is* > > *4. *Get the StarlingX ISO from the CENGN StarlingX mirror > . Alternately, you > can use an ISO from a private StarlingX build. > > I get as below . > > Can anyone make me understand, what each of the folder stands for?. > Also, as a first timer which folder I need to go and download the ISO.? > > I have tried 3.0.0 under release, but ended up with issues. Should there > be a direct link to output folder when I select Get the StarlingX ISO > from the CENGN StarlingX mirror > ? > > Thanks, > > Poornima > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From bruce.e.jones at intel.com Fri Feb 28 20:48:36 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 28 Feb 2020 20:48:36 +0000 Subject: [Starlingx-discuss] reminder: community meetup next week Message-ID: <9A85D2917C58154C960D95352B22818BF167801E@fmsmsx123.amr.corp.intel.com> We are planning a mid-cycle meetup for StarlingX. The date is March 3rd - 4th at Intel's Chandler Arizona (Phoenix) location. Intel CH7 room CH7-410 5000 W Chandler Blvd Chandler AZ Google maps link: https://www.google.com/maps/place/Intel+CH7/@33.3186517,-111.9424612,13.75z/data=!4m5!3m4!1s0x872b06b9c465d6dd:0x9668f5636d3ede3d!8m2!3d33.3109104!4d-111.9324318 Here's the Zoom link for Tuesday-Wednesday: https://zoom.us/j/8341652381 The agenda can be found here: https://etherpad.openstack.org/p/starlingX-winter-2020-meetup brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Fri Feb 28 21:04:49 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Fri, 28 Feb 2020 21:04:49 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200227 In-Reply-To: References: Message-ID: Maria: The issue reported in this sanity is an upstream tiller issue and the plan to address this is to upversion helm to v3 which will result in tiller being removed and avoiding the tiller issue. Until then if LP 1856078 is seen the workaround is to restart tiller. See the comments in https://bugs.launchpad.net/starlingx/+bug/1856078 Frank From: Perez Ibarra, Maria G [mailto:maria.g.perez.ibarra at intel.com] Sent: Thursday, February 27, 2020 10:08 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200227 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-February-27 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] App platform-integ-apps failed to apply (error get configmaps) https://bugs.launchpad.net/starlingx/+bug/1856078 Regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Fri Feb 28 23:59:06 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Fri, 28 Feb 2020 23:59:06 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200228 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-February-28 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Sat Feb 29 02:31:22 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 28 Feb 2020 21:31:22 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup - Build # 716 - Failure! Message-ID: <538960983.902.1582943484075.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup Build #: 716 Status: Failure Timestamp: 20200229T023038Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200229T023003Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200229T023003Z DOCKER_BUILD_ID: jenkins-master-20200229T023003Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200229T023003Z/logs DOCKER_BUILD_TAG: master-20200229T023003Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200229T023003Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Sat Feb 29 02:31:26 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 28 Feb 2020 21:31:26 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 454 - Failure! Message-ID: <136557628.905.1582943487197.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 454 Status: Failure Timestamp: 20200229T023003Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200229T023003Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From Ghada.Khalil at windriver.com Thu Feb 20 01:45:21 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 20 Feb 2020 01:45:21 -0000 Subject: [Starlingx-discuss] stx.4.0 Release Planning -- Action Required: Feature Primes to update plans Message-ID: <151EE31B9FCCA54397A757BC674650F0C1673D22@ALA-MBD.corp.ad.wrs.com> Hello stx.4.0 feature primes, In preparation of the mid-cycle StarlingX meeting in early March and the upcoming stx.4.0 Milestone-2 (planned for March 23), I'd like to ask each feature prime to update their Feature Dates by Feb 26 in: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=110720984 Please update the following columns with your plan dates: - Column I: Plan Available. This is especially important if you don't have planned dates for the subsequent milestones. - Column L: Spec Approved or mark as N/A if no spec is planned - Column O: Code merged in master Please also update Column G (Green, Yellow, Red) w/ Risk. Please use Column V for comments. For more details on each field, see the "Field Definitions" tab in the spreadsheet. If you need any help, please feel free to reach out to me, Bruce or Bill. For reference: Milestone-2 Criteria: https://wiki.openstack.org/wiki/StarlingX/Release_Plan#Release_Milestones - Spec freeze; no new specs accepted for the release. The focus is on closing current specs - Feature plans defined and feature development well underway - Release test plan defined - including test automation deliverables Thanks, Ghada