From yong.hu at intel.com Mon Jul 2 02:14:32 2018 From: yong.hu at intel.com (Hu, Yong) Date: Mon, 2 Jul 2018 02:14:32 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> Message-ID: <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> > > 13:37:39 ERROR: Could not find useradd in chroot, maybe the install failed? It looked the local repo failed to be created. please check and assure "~/cgcs-root/cgcs-centos-repo/Binary/comps.xml" is there, and the sub-dirs in ""~/cgcs-root/cgcs-centos-repo/Binary/" do exist with correct symbol links to the mirror. On 30/06/2018, 1:09 PM, "Arce Moreno, Abraham" wrote: > I'm not observing this. Perhaps a change in the @buildsys-build package group > on your system. > > More inline below ... Thanks for your guidance! I am now able to continue with the compilation process, I will debug some time later what are the changes in my setup. > > 13:37:39 ERROR: Could not find useradd in chroot, maybe the install failed? > > > > And this is reflected also as our exit error when we try to enter the mock shell: > > > > $ mock -r $MY_BUILD_CFG --shell > [SL] If you are using parallel build, please use the b0 config under the configs > directory ... e.g. Confirmed b0 config being used... > If you find that shadow-utils is still missing, I'd add it to ... > > $MY_REPO/build-tools/modify-build-cfg > > ... > grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 > yumshadow-utils'" $FILE || \ > echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 > yumshadow-utils'" >> $FILE ... I added it as suggested but it continued failing then I search for any other place buildsys-build [0] was used and I find that adding shadow-utils under b0 config made useradd to be installed and let me continue with the compilation process: $ .../ user-starlingx-tis-r5-pike-std.b0.cfg config_opts['rpmbuild_timeout'] = 0 config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum shadow-utils' config_opts['module_install'] = [] [0] https://fedoraproject.org/wiki/Archive:Legacy/Mock?rd=Legacy/Mock _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Mon Jul 2 14:48:32 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Mon, 2 Jul 2018 14:48:32 +0000 Subject: [Starlingx-discuss] Several build failures due to recent code integrations Message-ID: <824C370FAA1437418C1DC20641E2FC2C43DD15FA@fmsmsx104.amr.corp.intel.com> Hi all, The recent code integration in several components of StarlingX causes different build failures. I create the following stories to track the solution of these issues, in case anyone wants to take a look. https://storyboard.openstack.org/#!/story/2002779 : Kubernetes failure https://storyboard.openstack.org/#!/story/2002790 - docker-ce failure https://storyboard.openstack.org/#!/story/2002791 - etc failure https://storyboard.openstack.org/#!/story/2002792 - ntfs failure https://storyboard.openstack.org/#!/story/2002793 - puppet-collectd The root cause in all failures is the same, not adding the new needed packages into the mirror. Same thing about python src rpm reported last week. -Erich From dtroyer at gmail.com Mon Jul 2 15:33:57 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Mon, 2 Jul 2018 10:33:57 -0500 Subject: [Starlingx-discuss] Several build failures due to recent code integrations In-Reply-To: <824C370FAA1437418C1DC20641E2FC2C43DD15FA@fmsmsx104.amr.corp.intel.com> References: <824C370FAA1437418C1DC20641E2FC2C43DD15FA@fmsmsx104.amr.corp.intel.com> Message-ID: On Mon, Jul 2, 2018 at 9:48 AM, Cordoba Malibran, Erich wrote: > The root cause in all failures is the same, not adding the new needed packages into the mirror. Same thing about python src rpm reported last week. Since this is likely to be a frequent problem can we come up with a test to verify the mirror lists? I mean just make sure that our mirror source lists contain what we think they need to contain, not actually verify that the referenced packages are still available without downloading them. These would both be good to have to run locally and possibly by Zuul if we can minimize reliance on reaching external sites. dt -- Dean Troyer dtroyer at gmail.com From david.a.cobbley at intel.com Mon Jul 2 18:25:08 2018 From: david.a.cobbley at intel.com (Cobbley, David A) Date: Mon, 2 Jul 2018 18:25:08 +0000 Subject: [Starlingx-discuss] Several build failures due to recent code integrations In-Reply-To: References: <824C370FAA1437418C1DC20641E2FC2C43DD15FA@fmsmsx104.amr.corp.intel.com> Message-ID: Great idea to verify mirror source lists. The more involved package availability tests should also be considered as part of a full release cycle validation, though. --David C -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Monday, July 2, 2018 8:34 AM To: Cordoba Malibran, Erich Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Several build failures due to recent code integrations On Mon, Jul 2, 2018 at 9:48 AM, Cordoba Malibran, Erich wrote: > The root cause in all failures is the same, not adding the new needed packages into the mirror. Same thing about python src rpm reported last week. Since this is likely to be a frequent problem can we come up with a test to verify the mirror lists? I mean just make sure that our mirror source lists contain what we think they need to contain, not actually verify that the referenced packages are still available without downloading them. These would both be good to have to run locally and possibly by Zuul if we can minimize reliance on reaching external sites. dt -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Mon Jul 2 18:27:16 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Mon, 2 Jul 2018 18:27:16 +0000 Subject: [Starlingx-discuss] Several build failures due to recent code integrations In-Reply-To: References: <824C370FAA1437418C1DC20641E2FC2C43DD15FA@fmsmsx104.amr.corp.intel.com> Message-ID: > The root cause in all failures is the same, not adding the new needed packages into the mirror. Same thing about python src rpm reported last week. > Since this is likely to be a frequent problem can we come up with a > test to verify the mirror lists? I mean just make sure that our > mirror source lists contain what we think they need to contain, not > actually verify that the referenced packages are still available > without downloading them. This could catch some to the problems, in particular the ones that are explicitly set in the srpm_path files. However, we still have the problem with the build requirements for every package. For example, recently Python was added to be built[0], now the src.rpm is needed. The solution here would be just to add python-2.7.5-58.el7.src.rpm into the package list. It turns out that (as detailed in another mail thread) three more packages (build dependencies) are needed to have a clean build of the python package. This is something that we can see until build time. [0] - https://review.openstack.org/#/c/578996/ From dtroyer at gmail.com Mon Jul 2 18:42:52 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Mon, 2 Jul 2018 13:42:52 -0500 Subject: [Starlingx-discuss] Several build failures due to recent code integrations In-Reply-To: References: <824C370FAA1437418C1DC20641E2FC2C43DD15FA@fmsmsx104.amr.corp.intel.com> Message-ID: On Mon, Jul 2, 2018 at 1:27 PM, Cordoba Malibran, Erich wrote: > This could catch some to the problems, in particular the ones that are > explicitly set in the srpm_path files. We should do that then > However, we still have the problem with the build requirements for every > package. For example, recently Python was added to be built[0], now the > src.rpm is needed. The solution here would be just to add python-2.7.5-58.el7.src.rpm > into the package list. It turns out that (as detailed in another mail thread) > three more packages (build dependencies) are needed to have a clean > build of the python package. This is something that we can see until > build time. Actually you can get an SRPM's build dependencies and check to see that they are already accounted for. As long as we have multiple lists of packages we need to do sanity checking to ensure they are consistent with each other. This isn't going to catch everything of course, but it can catch some things early when the cycle time is short and not hours to do a build. dt -- Dean Troyer dtroyer at gmail.com From abraham.arce.moreno at intel.com Tue Jul 3 12:44:45 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 3 Jul 2018 12:44:45 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> Message-ID: Thanks Yong! > > > 13:37:39 ERROR: Could not find useradd in chroot, maybe the install > > > failed? > > It looked the local repo failed to be created. please check and assure "~/cgcs- > root/cgcs-centos-repo/Binary/comps.xml" is there, and the sub-dirs in > ""~/cgcs-root/cgcs-centos-repo/Binary/" do exist with correct symbol links to > the mirror. I have checked comps.xml and it is there, the symbolic links were also updated using our script update_links_from_mirror.sh. Team here in Mexico have started the building only from external sources yesterday. It will be great if someone else could take our Developer Guide https://wiki.openstack.org/wiki/StarlingX/Developer_Guide and build the ISO from scratch. 2 changes for stx-tools not yet merged to integrate to complete a full external build: - cgcs-centos-repo: https://review.openstack.org/#/c/579709/ - cgcs-dl: https://review.openstack.org/#/c/577953/ Do not hesitate to provide any feedback or modify our wiki as required. Abraham From yong.hu at intel.com Tue Jul 3 12:58:11 2018 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 3 Jul 2018 12:58:11 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> Message-ID: <71FBB182-3630-40E2-8A60-88137137823E@intel.com> > > > It will be great if someone else could take our Developer Guide > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > and build the ISO from scratch. Yeah, we will have someone to do the exercise based on this guide. Pls stay tuned. On 03/07/2018, 8:44 PM, "Arce Moreno, Abraham" wrote: Thanks Yong! > > > 13:37:39 ERROR: Could not find useradd in chroot, maybe the install > > > failed? > > It looked the local repo failed to be created. please check and assure "~/cgcs- > root/cgcs-centos-repo/Binary/comps.xml" is there, and the sub-dirs in > ""~/cgcs-root/cgcs-centos-repo/Binary/" do exist with correct symbol links to > the mirror. I have checked comps.xml and it is there, the symbolic links were also updated using our script update_links_from_mirror.sh. Team here in Mexico have started the building only from external sources yesterday. It will be great if someone else could take our Developer Guide https://wiki.openstack.org/wiki/StarlingX/Developer_Guide and build the ISO from scratch. 2 changes for stx-tools not yet merged to integrate to complete a full external build: - cgcs-centos-repo: https://review.openstack.org/#/c/579709/ - cgcs-dl: https://review.openstack.org/#/c/577953/ Do not hesitate to provide any feedback or modify our wiki as required. Abraham From scott.little at windriver.com Tue Jul 3 14:17:49 2018 From: scott.little at windriver.com (Scott Little) Date: Tue, 3 Jul 2018 10:17:49 -0400 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> Message-ID: <866f9e78-fce5-530f-2a91-15a3724c7020@windriver.com> Did I actually post 'yumshadow-utils' ?     That should read 'shadow-utils'. Scott On 18-06-30 01:08 AM, Arce Moreno, Abraham wrote: >> I'm not observing this. Perhaps a change in the @buildsys-build package group >> on your system. >> >> More inline below ... > Thanks for your guidance! I am now able to continue with the compilation process, > I will debug some time later what are the changes in my setup. > >>> 13:37:39 ERROR: Could not find useradd in chroot, maybe the install failed? >>> >>> And this is reflected also as our exit error when we try to enter the mock shell: >>> >>> $ mock -r $MY_BUILD_CFG --shell >> [SL] If you are using parallel build, please use the b0 config under the configs >> directory ... e.g. > Confirmed b0 config being used... > >> If you find that shadow-utils is still missing, I'd add it to ... >> >> $MY_REPO/build-tools/modify-build-cfg >> >> ... >> grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 >> yumshadow-utils'" $FILE || \ >> echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 >> yumshadow-utils'" >> $FILE ... > I added it as suggested but it continued failing then I search for any other place > buildsys-build [0] was used and I find that adding shadow-utils under b0 config made > useradd to be installed and let me continue with the compilation process: > > $ .../ user-starlingx-tis-r5-pike-std.b0.cfg > config_opts['rpmbuild_timeout'] = 0 > config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum shadow-utils' > config_opts['module_install'] = [] > > [0] https://fedoraproject.org/wiki/Archive:Legacy/Mock?rd=Legacy/Mock From abraham.arce.moreno at intel.com Tue Jul 3 23:02:23 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 3 Jul 2018 23:02:23 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <71FBB182-3630-40E2-8A60-88137137823E@intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> Message-ID: > > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned. Cool! Thank you! From abraham.arce.moreno at intel.com Tue Jul 3 23:20:26 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 3 Jul 2018 23:20:26 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <866f9e78-fce5-530f-2a91-15a3724c7020@windriver.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <866f9e78-fce5-530f-2a91-15a3724c7020@windriver.com> Message-ID: > Did I actually post 'yumshadow-utils' ?     That should read 'shadow-utils'. No issues. So far this " ERROR: Could not find useradd in chroot, maybe the install failed? " is seen in 2 different setups started from scratch, looking more into the source code this ['chroot_setup_cmd'] is found in 2 files: - build-tools/build_minimal_iso/build.cfg - build-tools/modify-build-cfg How possible is it we can add the "required" packages into "modify-build-cfg"? Iso building differ but have them including 'shadow-utils'. Adding them under "modify-build-cfg" allowed me to continue running the build-pkgs and get rid of the problem. Any other cleaner way? Complete repo grep output: [user at 8848c894bb36 cgcs-root]$ repo grep buildsys-build cgcs-root/build-tools/build_minimal_iso/build.cfg:config_opts['chroot_setup_cmd'] = \ 'install @buildsys-build' cgcs-root/build-tools/build_minimal_iso/build.cfg:config_opts['chroot_setup_cmd'] = \ 'install @buildsys-build pigz lbzip2 yum shadow-utils rpm-build lbzip2 gcc glibc-headers make gcc-c++ java-devel' cgcs-root/build-tools/modify-build-cfg:grep -q "config_opts\['chroot_setup_cmd'\] = \ 'install @buildsys-build pigz lbzip2 yum'" $FILE || \ cgcs-root/build-tools/modify-build-cfg: echo "config_opts['chroot_setup_cmd'] = \ 'install @buildsys-build pigz lbzip2 yum'" >> $FILE From fernando.hernandez.gonzalez at intel.com Tue Jul 3 22:50:28 2018 From: fernando.hernandez.gonzalez at intel.com (Hernandez Gonzalez, Fernando) Date: Tue, 3 Jul 2018 22:50:28 +0000 Subject: [Starlingx-discuss] RFC: StarlingX release cadence proposal In-Reply-To: <4F6AACE4B0F173488D033B02A8BB5B7E7169FD30@fmsmsx104.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB54E25A@fmsmsx117.amr.corp.intel.com> <4F6AACE4B0F173488D033B02A8BB5B7E7169FD30@fmsmsx104.amr.corp.intel.com> Message-ID: <03D458D5BAFF6041973594B00B4E58CE590D43D1@FMSMSX102.amr.corp.intel.com> Hi Bruce, As you know I am assigned to "Design and document the release" Starlingx task, as part of that task and since I am more a visual guy (Please feel free to use the excel I attached) I created a Schedule that I might be incorporated in our documentation in the future. I reviewed the proposal, looks good to me, but I still have some doubts/comments/pending? · In the "Starlingx Planning etherpad" you talked about Beta1/2 and RC1,2,3... Are they aligned with August Quarterly Cadence or this is just because of the ramp up of the project? · Just curious for quarterly release, why are you saying "This gives us 4-6 weeks of time to run test" and not more or less weeks? Comments · Regarding "version number change from what the underlying TC product uses today" in my previous BIOS project there was a file created when the SPI Firmware was compiled, the script was fed for the version of main components. This help us a lot when some bug appears and we had to do troubleshooting. Maybe it is a way/option to populate a script with underlying TC and CentOS product versions. Pending · How long N and N-1 long live branches are going to keep alive? And same question for short-live. · LTS is still a topic unclear. Do you have more about it? [cid:image002.jpg at 01D412F6.520B6400] Fernando Hernandez Gonzalez Software Engineer Avenida del Bosque #1001 Col, El Bajío Zapopan, Jalisco MX, 45019 ____________________________________ Office: +52.33.16.45.01.34 inet 86450134 From: Cabrales, Ada [mailto:ada.cabrales at intel.com] Sent: Thursday, June 28, 2018 8:02 PM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] RFC: StarlingX release cadence proposal I like this proposal. I think it would give us periodic, stable versions to work on/with. Also, it gives us the opportunity to plan what would we have on each monthly | quarterly release, considering feature's priority. So, if we decide to follow this schema, let's define what we want to have ready for the Summit in November (the September release, as pointed by Bruce previously) and plan around that. Ada -- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, June 27, 2018 6:48 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] RFC: StarlingX release cadence proposal At our weekly call today we discussed release plans and release cadence. It was a long discussion and a good one. In the end we agreed that we'd like to follow the "bus stop" model of time based releases, and the Ubuntu model of an annual major (LTS) release with quarterly updates. Note that we did not suggest or agree that our currently planned "Release 2" should be a LTS. We all agreed that would be premature. We will declare an LTS at some point in the future. After separate discussions with David, Dean and Ada, rather than just proposing that "our current November release is the first quarterly release", I have a modified proposal to make for how we should handle releases. This is an RFC looking for feedback, questions and comments. Monthly milestone builds -------------------------------- Each month in the 2nd week of the month we will pull a branch. Dean and I suggest using year/month as the branch names, for simplicity. For example, we propose that the branch name for a July 2018 milestone build would be "stx.2018.07". The version number of that build would be "stx.2018.07.0x", where "0x" is a patch number. Yes, that's a change to how version numbers are handled. See below. The purpose of the monthly build is to 1) provide a stable build for long running test cycles 2) provide a "latest known to be good" build for users and partners, and 3) feed into the quarterly release. Fixes for show stopping bugs found in monthly build testing should be done on master and cherry-picked to the branch, increasing the patch number with each one. Quarterly release -------------------- Each quarter's quarterly release will be the monthly milestone build from the 2nd month in the quarter. This gives us 4-6 weeks of time to run test cycles and fix bugs for the release. For each quarterly release, the code freeze for that release is the 2nd week in the 2nd month in the quarter. Branch handling -------------- Branches from the 1st and 3rd month in a quarter can be short-lived. Branches for the 2nd month's (quarterly) build will live longer and I would suggest at any given time we keep the N and N-1 quarterly release branches open for bug fixes. If/when we declare a LTS release, that branch would of course live much longer. Why? ----- Why do we release a build from the 2nd week of the 2nd month? In part because that schedule misses the major holiday weeks. No one likes to do releases over the summer or winter holidays. Impact ------- The planning for release content for what we are currently calling "Release 2" will need to change. If this proposal is accepted, we won't have a "release 2" anymore, just a "release stx.2018.08.x" released in September and "release stx 2018.11.x" released in December. This changes the content we'd have in the release for the November summit (which would be the September release) but anyone there looking for the bleeding edge could pick up the RC for the December build, which would be in testing at that time. Branching also means that key bug fixes would need to be cherry picked to the older branches. New feature code should always go to master only. Version numbers ---------------- This proposal also includes a version number change from what the underlying TC product uses today. I think it's inevitable that the StarlingX project has separate / different version numbers from TC, but I don't know what it means to the system to actually get there, or what headaches it might cause. We should key that up as a separate discussion. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 114313 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Schedule todiscussionlist.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 20159 bytes Desc: Schedule todiscussionlist.xlsx URL: From yong.hu at intel.com Wed Jul 4 07:15:04 2018 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 4 Jul 2018 07:15:04 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> Message-ID: <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> Hi Abraham, Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" wrote: > > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned. Cool! Thank you! From abraham.arce.moreno at intel.com Wed Jul 4 08:04:29 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Wed, 4 Jul 2018 08:04:29 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> Message-ID: > Hi Abraham, Hi Yong! > Did you run "build-pkgs" or "build-pkgs --serial"? > If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if > using "-- serial" the build went smoothly and further, except for failures on > following 3 packages, which is known issue. > 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm > kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm Only build-pkgs, let me execute with build-pkgs --serial and I will get back to you with my findings and documentation updates. > In the meantime, @Zhipeng is following steps in > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide Thanks Zhipeng for your help! Feel free to modify the content as required, please refresh since I wrote some final comments a few minutes ago. For now no more updates from my side. At this point I am able to finally complete all steps except build-iso using the guide. Important Sections/Steps from the guide to double check: - Section 3 Build the CentOS Mirror Repository - Part Setup Repository Docker Container Step 2: "A successful build could depend on the patches to be merged into stx-tools\ make sure you cherry picked them..." - Part Verify Packages "In case there are missing or failed ones due to network instability (or timeout), \ you should download them manually..." - Section 4 Create StarlingX Packages - Part Build Packages "ERROR: Could not find useradd in chroot, maybe the install failed?..." During the build-pkgs process I faced compilation errors due to missing/corrupted packages: 06:18:23 Failed to build packages: tpm-kmod-4.12-0.tis.5.src.rpm spectre-meltdown-checker-0.37+-0.tis.src.rpm \ qemu-kvm-ev-2.10.0-0.tis.0.src.rpm ldapscripts-2.0.8-0.tis.2.src.rpm integrity-kmod-4.12-0.tis.5.src.rpm \ cgcs-users-1.0-0.tis.2.src.rpm cgts-mtce-common-1.0-134.tis.src.rpm libvirt-3.5.0-1.tis.2.src.rpm The packages were manually copied to the container to fix some of the above problems were: - tpm-kmod-668a8270.tar.gz - integrity-kmod-668a8270.tar.gz - ibsh-0.3e.tar.gz - ldapscripts-2.0.8.tgz - cppcheck-1.80-1.el7.x86_64.rpm I will filed a bug to track the issues under downloads directory, problem might be a wrong packaging structure. For spectre-meltdown-checker-0.37+-0.tis.src.rpm, please cherry pick the following: - https://review.openstack.org/#/c/580019/ - https://review.openstack.org/#/c/580015/ I will continue with build-iso after zZzZz... From scott.little at windriver.com Wed Jul 4 13:45:29 2018 From: scott.little at windriver.com (Scott Little) Date: Wed, 4 Jul 2018 09:45:29 -0400 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> Message-ID: <57c9ce60-2092-ef82-198b-6bfb87a425f9@windriver.com> build-pkgs will by default run in parallel mode.  This means two things, a different build order than the serial build, and the possibility that earlier packages built in a different mock environment.  It likely works in a serial build because an earlier package has a "Require: X" where X is shadow-utils or something that depends on shadow-utils.  Since we reuse the mock environment rather than clearing it after each package (faster builds), the shadow-utils package is available for later packages and might allow then to get away with a missing dependency. The real solution is to add 'Requires: shadow-utils' to the spec file of the package that breaks. Adding it via modify-build-cfg was based on the theory (unconfirmed) that @buildsys-build macro has been redefined on newer CentOS systems and shadow-utils has been dropped from the set of packages that @buildsys-build maps to.  It seems like a quicker way to enable folks, rather than adding 'Requires: shadow-utils' to potemtially a lot of packages. Scott On 18-07-04 03:15 AM, Hu, Yong wrote: > Hi Abraham, > Did you run "build-pkgs" or "build-pkgs --serial"? > If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, > but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. > 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm > > In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" wrote: > > > > > > It will be great if someone else could take our Developer Guide > > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > > and build the ISO from scratch. > > > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > > tuned. > > Cool! Thank you! > > From mario.alfredo.c.arevalo at intel.com Wed Jul 4 15:33:02 2018 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Wed, 4 Jul 2018 15:33:02 +0000 Subject: [Starlingx-discuss] building proposal Message-ID: <6594B51DBE477C48AAE23675314E6C465990549D@fmsmsx107.amr.corp.intel.com> Hi folks, Taking a look inside stx-tools mirror, I come up with an idea related to the building ISO flow, I think the most of the instructions can be automated in a centralized tool. This tool can be developed in golang or python language in order to take advantage of the provided modules by these languages. Furthermore we can improve the error handling, and hide the flow complexity due to the current stuff could be a little prone to error. The idea is to have some basic commands as first version. $ stx mirror donwload/create an RPM mirror $ stx build-iso build an ISO image using a possible mirror as input (e.g. --mirror/home/user/mirror), or if it does not exist, crate one. I would like some comments related to this. Best regards. Mario. From guillermo.a.ponce.castaneda at intel.com Wed Jul 4 16:02:48 2018 From: guillermo.a.ponce.castaneda at intel.com (Ponce Castaneda, Guillermo A) Date: Wed, 4 Jul 2018 16:02:48 +0000 Subject: [Starlingx-discuss] building proposal In-Reply-To: <6594B51DBE477C48AAE23675314E6C465990549D@fmsmsx107.amr.corp.intel.com> References: <6594B51DBE477C48AAE23675314E6C465990549D@fmsmsx107.amr.corp.intel.com> Message-ID: <2A2E5954-67E3-4EB9-9FC4-E1BE0F532CA0@intel.com> Hi Mario, I have been working at StarlingX for over a month now and I would really like to have a tool like this one, it can get very complicated to even create a working mirror by only using the documentation, there are steps/hacks that are not documented or are very hard to follow and this tool would solve everything and take load off the final user. I also understand there are a lot of people that like or have the need to do everything step by step but I am also sure that some other people will find this tool very handy, so I would like to work on this project. Thanks and Regards. - Guillermo (Memo) Ponce On 7/4/18, 10:33 AM, "Arevalo, Mario Alfredo C" wrote: Hi folks, Taking a look inside stx-tools mirror, I come up with an idea related to the building ISO flow, I think the most of the instructions can be automated in a centralized tool. This tool can be developed in golang or python language in order to take advantage of the provided modules by these languages. Furthermore we can improve the error handling, and hide the flow complexity due to the current stuff could be a little prone to error. The idea is to have some basic commands as first version. $ stx mirror donwload/create an RPM mirror $ stx build-iso build an ISO image using a possible mirror as input (e.g. --mirror/home/user/mirror), or if it does not exist, crate one. I would like some comments related to this. Best regards. Mario. From cesar.lara at intel.com Wed Jul 4 16:14:15 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Wed, 4 Jul 2018 16:14:15 +0000 Subject: [Starlingx-discuss] building proposal In-Reply-To: <2A2E5954-67E3-4EB9-9FC4-E1BE0F532CA0@intel.com> References: <6594B51DBE477C48AAE23675314E6C465990549D@fmsmsx107.amr.corp.intel.com> <2A2E5954-67E3-4EB9-9FC4-E1BE0F532CA0@intel.com> Message-ID: <0B566C62EC792145B40E29EFEBF1AB47104A065E@fmsmsx104.amr.corp.intel.com> I'm up for taking the complexity out of the picture and have a better error control, so I need people from the community to really take a look at his as this might be what we are going to focus on . Regards Cesar Lara -----Original Message----- From: Ponce Castaneda, Guillermo A [mailto:guillermo.a.ponce.castaneda at intel.com] Sent: Wednesday, July 4, 2018 11:03 AM To: Arevalo, Mario Alfredo C ; starlingx-discuss at lists.starlingx.io Cc: Wold, Saul Subject: Re: [Starlingx-discuss] building proposal Hi Mario, I have been working at StarlingX for over a month now and I would really like to have a tool like this one, it can get very complicated to even create a working mirror by only using the documentation, there are steps/hacks that are not documented or are very hard to follow and this tool would solve everything and take load off the final user. I also understand there are a lot of people that like or have the need to do everything step by step but I am also sure that some other people will find this tool very handy, so I would like to work on this project. Thanks and Regards. - Guillermo (Memo) Ponce On 7/4/18, 10:33 AM, "Arevalo, Mario Alfredo C" wrote: Hi folks, Taking a look inside stx-tools mirror, I come up with an idea related to the building ISO flow, I think the most of the instructions can be automated in a centralized tool. This tool can be developed in golang or python language in order to take advantage of the provided modules by these languages. Furthermore we can improve the error handling, and hide the flow complexity due to the current stuff could be a little prone to error. The idea is to have some basic commands as first version. $ stx mirror donwload/create an RPM mirror $ stx build-iso build an ISO image using a possible mirror as input (e.g. --mirror/home/user/mirror), or if it does not exist, crate one. I would like some comments related to this. Best regards. Mario. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From jose.perez.carranza at intel.com Wed Jul 4 17:03:44 2018 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Wed, 4 Jul 2018 17:03:44 +0000 Subject: [Starlingx-discuss] cannot establish ssh connection compute-vm Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A8A7784@fmsmsx104.amr.corp.intel.com> Hi Folks I followed steps on [1] and [2] and have a successfully cirros VM up and running, but I'm not able to stablish an SSH connection form "compute to VM" using below steps ==================== $USER="cirros" $VM_NAME="server.nano" $IP=`openstack server list --name $VM_NAME -f value -c Networks | awk '{ split($1, v, "="); print v[2]}'` $NAMESPACE=$(ip netns | grep $(neutron net-list --name net -f value -c id)) $sudo ip netns exec $NAMESPACE ssh -o StrictHostKeyChecking=no $USER@$IP =================== Is giving me "Connection timed out", VM has "default" security group that enables all the connections and all the ports. Did someone has faced this issue ? 1- https://wiki.openstack.org/wiki/StarlingX/Installation_Guide/Controller_Storage 2- https://wiki.openstack.org/wiki/StarlingX/Validation_Guide Regards, José From Brent.Rowsell at windriver.com Wed Jul 4 19:43:23 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Wed, 4 Jul 2018 19:43:23 +0000 Subject: [Starlingx-discuss] Plan for stx-gui Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0C68C4@ALA-MBD.corp.ad.wrs.com> What is the current plan for stx-gui ? It is currently not being pulled into the load and the StarlingX specific panels are still in stx-horizon. Brent -------------- next part -------------- An HTML attachment was scrubbed... URL: From yi.c.wang at intel.com Thu Jul 5 02:53:30 2018 From: yi.c.wang at intel.com (Wang, Yi C) Date: Thu, 5 Jul 2018 02:53:30 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> Message-ID: Hi Abraham, I just found, In https://wiki.openstack.org/wiki/StarlingX/Developer_Guide The step 5 of "Download Source Code Repositories" has to be modified due to a patch of stx-manifest.git merged yesterday. https://review.openstack.org/#/c/580170/ Thanks. Yi -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Wednesday, July 4, 2018 4:04 PM To: Hu, Yong ; Scott Little ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > Hi Abraham, Hi Yong! > Did you run "build-pkgs" or "build-pkgs --serial"? > If I run "run-pkgs" (parallel mode) I saw the similar errors as you > did, but if using "-- serial" the build went smoothly and further, > except for failures on following 3 packages, which is known issue. > 13:42:03 Failed to build packages: > memcached-1.4.39-1.el7.tis.1.src.rpm > kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm Only build-pkgs, let me execute with build-pkgs --serial and I will get back to you with my findings and documentation updates. > In the meantime, @Zhipeng is following steps in > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide Thanks Zhipeng for your help! Feel free to modify the content as required, please refresh since I wrote some final comments a few minutes ago. For now no more updates from my side. At this point I am able to finally complete all steps except build-iso using the guide. Important Sections/Steps from the guide to double check: - Section 3 Build the CentOS Mirror Repository - Part Setup Repository Docker Container Step 2: "A successful build could depend on the patches to be merged into stx-tools\ make sure you cherry picked them..." - Part Verify Packages "In case there are missing or failed ones due to network instability (or timeout), \ you should download them manually..." - Section 4 Create StarlingX Packages - Part Build Packages "ERROR: Could not find useradd in chroot, maybe the install failed?..." During the build-pkgs process I faced compilation errors due to missing/corrupted packages: 06:18:23 Failed to build packages: tpm-kmod-4.12-0.tis.5.src.rpm spectre-meltdown-checker-0.37+-0.tis.src.rpm \ qemu-kvm-ev-2.10.0-0.tis.0.src.rpm ldapscripts-2.0.8-0.tis.2.src.rpm integrity-kmod-4.12-0.tis.5.src.rpm \ cgcs-users-1.0-0.tis.2.src.rpm cgts-mtce-common-1.0-134.tis.src.rpm libvirt-3.5.0-1.tis.2.src.rpm The packages were manually copied to the container to fix some of the above problems were: - tpm-kmod-668a8270.tar.gz - integrity-kmod-668a8270.tar.gz - ibsh-0.3e.tar.gz - ldapscripts-2.0.8.tgz - cppcheck-1.80-1.el7.x86_64.rpm I will filed a bug to track the issues under downloads directory, problem might be a wrong packaging structure. For spectre-meltdown-checker-0.37+-0.tis.src.rpm, please cherry pick the following: - https://review.openstack.org/#/c/580019/ - https://review.openstack.org/#/c/580015/ I will continue with build-iso after zZzZz... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From zhipengs.liu at intel.com Thu Jul 5 03:14:22 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 5 Jul 2018 03:14:22 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> Message-ID: <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> Hi Abraham, When I run below step $ docker build -t user:centos-mirror-repository -f Dockerfile . It mentioned Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection It can work after following below steps. =========================================================== Here is a link to the official docker doc for proxy http:https://docs.docker.com/engine/admin/systemd/#http-proxy A quick outline: First, create a systemd drop-in directory for the docker service: mkdir /etc/systemd/system/docker.service.d Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: [Service] Environment="HTTP_PROXY=http://proxy.example.com:80/" If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: Environment="HTTP_PROXY=http://proxy.example.com:80/" Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" Flush changes: $ sudo systemctl daemon-reload Verify that the configuration has been loaded: $ sudo systemctl show --property Environment docker Environment=HTTP_PROXY=http://proxy.example.com:80/ Restart Docker: $ sudo systemctl restart docker -----Original Message----- From: Hu, Yong [mailto:yong.hu at intel.com] Sent: 2018年7月4日 15:15 To: Arce Moreno, Abraham ; Scott Little ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Hi Abraham, Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" wrote: > > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned. Cool! Thank you! _______________________________________________ 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 Thu Jul 5 07:23:46 2018 From: yong.hu at intel.com (Hu, Yong) Date: Thu, 5 Jul 2018 07:23:46 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> Message-ID: Abraham, One more comment to this guide: https://wiki.openstack.org/wiki/StarlingX/Developer_Guide We might have to add a session to update initial images, *if kernel or device modules are modified*. Here are steps: 1). Run command: $ update-pxe-network-installer After this is done, there should be 3 new files (vmlinuz, initrd.img and squashfs.img) generated in: $BUILD_FOLDER/pxe-network-installer/output 2). copy these 3 files into mirror “/import/mirrors/CentOS/tis-installer/” and put appropriate postfix. Note, the new info (images with the postfix) need to updated accordingly in in “build_srpm.data” and “pxe-network-installer.spec” under “cgcs-root/addons/wr-cgcs/layers/cgcs/mwa-beas/installer/pxe-network-installer/centos/” 3). re-build pkgs and iso: (no need to make a clean build) On 05/07/2018, 11:14 AM, "Liu, ZhipengS" wrote: Hi Abraham, When I run below step $ docker build -t user:centos-mirror-repository -f Dockerfile . It mentioned Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection It can work after following below steps. =========================================================== Here is a link to the official docker doc for proxy http:https://docs.docker.com/engine/admin/systemd/#http-proxy A quick outline: First, create a systemd drop-in directory for the docker service: mkdir /etc/systemd/system/docker.service.d Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: [Service] Environment="HTTP_PROXY=http://proxy.example.com:80/" If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: Environment="HTTP_PROXY=http://proxy.example.com:80/" Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" Flush changes: $ sudo systemctl daemon-reload Verify that the configuration has been loaded: $ sudo systemctl show --property Environment docker Environment=HTTP_PROXY=http://proxy.example.com:80/ Restart Docker: $ sudo systemctl restart docker -----Original Message----- From: Hu, Yong [mailto:yong.hu at intel.com] Sent: 2018年7月4日 15:15 To: Arce Moreno, Abraham ; Scott Little ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Hi Abraham, Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" wrote: > > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned. Cool! Thank you! _______________________________________________ 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 Thu Jul 5 08:22:55 2018 From: yong.hu at intel.com (Hu, Yong) Date: Thu, 5 Jul 2018 08:22:55 +0000 Subject: [Starlingx-discuss] the downloading script for tarballs in "wr-cgcs/layers/cgcs/downloads/"? Message-ID: <74DDA7CD-7E28-411A-A8D7-521CE2175FE1@intel.com> Guys, Where I could find the downloading scripts for those tarballs which are placed in “wr-cgcs/layers/cgcs/downloads/”? Per request, now we are upgrading kernel to 3.10.682, accordingly a few tarballs need be upgraded as well. Regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: From yi.c.wang at intel.com Thu Jul 5 08:29:35 2018 From: yi.c.wang at intel.com (Wang, Yi C) Date: Thu, 5 Jul 2018 08:29:35 +0000 Subject: [Starlingx-discuss] the downloading script for tarballs in "wr-cgcs/layers/cgcs/downloads/"? In-Reply-To: <74DDA7CD-7E28-411A-A8D7-521CE2175FE1@intel.com> References: <74DDA7CD-7E28-411A-A8D7-521CE2175FE1@intel.com> Message-ID: Hi Yong, I suppose no download script for those tarballs. WR just put a txt file in the folder for each tarball. The txt file provides the information for downloading the tarball. Thanks. Yi From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Thursday, July 5, 2018 4:23 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] the downloading script for tarballs in "wr-cgcs/layers/cgcs/downloads/"? Guys, Where I could find the downloading scripts for those tarballs which are placed in “wr-cgcs/layers/cgcs/downloads/”? Per request, now we are upgrading kernel to 3.10.682, accordingly a few tarballs need be upgraded as well. Regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Thu Jul 5 10:11:26 2018 From: yong.hu at intel.com (Hu, Yong) Date: Thu, 5 Jul 2018 10:11:26 +0000 Subject: [Starlingx-discuss] the downloading script for tarballs in "wr-cgcs/layers/cgcs/downloads/"? In-Reply-To: References: <74DDA7CD-7E28-411A-A8D7-521CE2175FE1@intel.com> Message-ID: <5462A5B7-5144-4AA5-A61C-4A7F88951DB3@intel.com> @Yi, in the latest code of “stx-tools”, the scripts exist. @Abraham, here is one question for you. In “tarball-dl.lst”, these 2 lines are actually commented out. So where is to download this MLNX_OFED tarball? !MLNX_OFED_LINUX-4.2-1.2.0.0-rhel7.4-x86_64.tgz#MLNX_OFED_LINUX-4.2-1.2.0.0-rhel7.4-x86_64#http://www.mellanox.com/downloads/ofed/MLNX_OFED-4.2-1.2.0.0/MLNX_OFED_LINUX-4.2-1.2.0.0-rhel7.4-x86_64.tgz !MLNX_OFED_LINUX-4.3-1.0.1.0-rhel7.4-x86_64.tgz#MLNX_OFED_LINUX-4.3-1.0.1.0-rhel7.4-x86_64#http://www.mellanox.com/downloads/ofed/MLNX_OFED-4.3-1.0.1.0/MLNX_OFED_LINUX-4.3-1.0.1.0-rhel7.4-x86_64.tgz Regards, Yong From: "Wang, Yi C" Date: Thursday, 5 July 2018 at 4:29 PM To: "Hu, Yong" , "starlingx-discuss at lists.starlingx.io" Subject: RE: the downloading script for tarballs in "wr-cgcs/layers/cgcs/downloads/"? Hi Yong, I suppose no download script for those tarballs. WR just put a txt file in the folder for each tarball. The txt file provides the information for downloading the tarball. Thanks. Yi From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Thursday, July 5, 2018 4:23 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] the downloading script for tarballs in "wr-cgcs/layers/cgcs/downloads/"? Guys, Where I could find the downloading scripts for those tarballs which are placed in “wr-cgcs/layers/cgcs/downloads/”? Per request, now we are upgrading kernel to 3.10.682, accordingly a few tarballs need be upgraded as well. Regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Thu Jul 5 10:15:48 2018 From: yong.hu at intel.com (Hu, Yong) Date: Thu, 5 Jul 2018 10:15:48 +0000 Subject: [Starlingx-discuss] the downloading script for tarballs in "wr-cgcs/layers/cgcs/downloads/"? Message-ID: <21FDAF41-CE5E-4FAF-B92E-83F11ECFF0D5@intel.com> @Abraham, never mind, I got it. “!” doesn’t mean “comment out”, but for “special handling” ☺ From: "Hu, Yong" Date: Thursday, 5 July 2018 at 6:12 PM To: "Wang, Yi C" , "starlingx-discuss at lists.starlingx.io" , "Arce Moreno, Abraham" Subject: Re: [Starlingx-discuss] the downloading script for tarballs in "wr-cgcs/layers/cgcs/downloads/"? @Yi, in the latest code of “stx-tools”, the scripts exist. @Abraham, here is one question for you. In “tarball-dl.lst”, these 2 lines are actually commented out. So where is to download this MLNX_OFED tarball? !MLNX_OFED_LINUX-4.2-1.2.0.0-rhel7.4-x86_64.tgz#MLNX_OFED_LINUX-4.2-1.2.0.0-rhel7.4-x86_64#http://www.mellanox.com/downloads/ofed/MLNX_OFED-4.2-1.2.0.0/MLNX_OFED_LINUX-4.2-1.2.0.0-rhel7.4-x86_64.tgz !MLNX_OFED_LINUX-4.3-1.0.1.0-rhel7.4-x86_64.tgz#MLNX_OFED_LINUX-4.3-1.0.1.0-rhel7.4-x86_64#http://www.mellanox.com/downloads/ofed/MLNX_OFED-4.3-1.0.1.0/MLNX_OFED_LINUX-4.3-1.0.1.0-rhel7.4-x86_64.tgz Regards, Yong From: "Wang, Yi C" Date: Thursday, 5 July 2018 at 4:29 PM To: "Hu, Yong" , "starlingx-discuss at lists.starlingx.io" Subject: RE: the downloading script for tarballs in "wr-cgcs/layers/cgcs/downloads/"? Hi Yong, I suppose no download script for those tarballs. WR just put a txt file in the folder for each tarball. The txt file provides the information for downloading the tarball. Thanks. Yi From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Thursday, July 5, 2018 4:23 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] the downloading script for tarballs in "wr-cgcs/layers/cgcs/downloads/"? Guys, Where I could find the downloading scripts for those tarballs which are placed in “wr-cgcs/layers/cgcs/downloads/”? Per request, now we are upgrading kernel to 3.10.682, accordingly a few tarballs need be upgraded as well. Regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: From yi.c.wang at intel.com Thu Jul 5 10:29:05 2018 From: yi.c.wang at intel.com (Wang, Yi C) Date: Thu, 5 Jul 2018 10:29:05 +0000 Subject: [Starlingx-discuss] the downloading script for tarballs in "wr-cgcs/layers/cgcs/downloads/"? In-Reply-To: <5462A5B7-5144-4AA5-A61C-4A7F88951DB3@intel.com> References: <74DDA7CD-7E28-411A-A8D7-521CE2175FE1@intel.com> , <5462A5B7-5144-4AA5-A61C-4A7F88951DB3@intel.com> Message-ID: <96ACBCDE-4C46-4FA4-B7F4-0939479A922B@intel.com> Got it :) Sent from my iPhone On Jul 5, 2018, at 6:11 PM, Hu, Yong > wrote: @Yi, in the latest code of “stx-tools”, the scripts exist. @Abraham, here is one question for you. In “tarball-dl.lst”, these 2 lines are actually commented out. So where is to download this MLNX_OFED tarball? !MLNX_OFED_LINUX-4.2-1.2.0.0-rhel7.4-x86_64.tgz#MLNX_OFED_LINUX-4.2-1.2.0.0-rhel7.4-x86_64#http://www.mellanox.com/downloads/ofed/MLNX_OFED-4.2-1.2.0.0/MLNX_OFED_LINUX-4.2-1.2.0.0-rhel7.4-x86_64.tgz !MLNX_OFED_LINUX-4.3-1.0.1.0-rhel7.4-x86_64.tgz#MLNX_OFED_LINUX-4.3-1.0.1.0-rhel7.4-x86_64#http://www.mellanox.com/downloads/ofed/MLNX_OFED-4.3-1.0.1.0/MLNX_OFED_LINUX-4.3-1.0.1.0-rhel7.4-x86_64.tgz Regards, Yong From: "Wang, Yi C" > Date: Thursday, 5 July 2018 at 4:29 PM To: "Hu, Yong" >, "starlingx-discuss at lists.starlingx.io" > Subject: RE: the downloading script for tarballs in "wr-cgcs/layers/cgcs/downloads/"? Hi Yong, I suppose no download script for those tarballs. WR just put a txt file in the folder for each tarball. The txt file provides the information for downloading the tarball. Thanks. Yi From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Thursday, July 5, 2018 4:23 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] the downloading script for tarballs in "wr-cgcs/layers/cgcs/downloads/"? Guys, Where I could find the downloading scripts for those tarballs which are placed in “wr-cgcs/layers/cgcs/downloads/”? Per request, now we are upgrading kernel to 3.10.682, accordingly a few tarballs need be upgraded as well. Regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ken.Young at windriver.com Thu Jul 5 16:21:12 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Thu, 5 Jul 2018 16:21:12 +0000 Subject: [Starlingx-discuss] [stx-tools] New Kernel Version Message-ID: I discovered 2 new reviews this morning which are security related this morning: https://review.openstack.org/#/c/580287/ https://review.openstack.org/#/c/580308/ These reviews propose to merge the latest CentOS kernel 862.6.3 to address the latest Spectre / Meltdown CVEs. Before this is completed, we have a kernel update to 862.3.2 we would like to merge which includes module updates to enable containers which we would like to get in first. Otherwise, this will generate a significant amount of rework for these submissions. The easiest path is to follow the kernels in order. We will work to get our updated kernel in ASAP. Thank you in advance. Regards, Ken Y -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesus.ornelas.aguayo at intel.com Thu Jul 5 20:11:43 2018 From: jesus.ornelas.aguayo at intel.com (Ornelas Aguayo, Jesus) Date: Thu, 5 Jul 2018 20:11:43 +0000 Subject: [Starlingx-discuss] building proposal Message-ID: <4DFC2830-4957-4E25-922E-429DFD8E4041@intel.com> I Agree with the optimized tool, the less required steps to build an ISO the better, as an additional comment I think the tool needs to have the next requirements: * Standardize required mirror packages on a single manifest, open to discussion (YAML, CSV,...) * Standardize error's output (Avoid checking multiple error files), based on this output we can add a fallback verification. * Based on the manifest mentioned above we can optimize download time by only downloading the required architecture (E.g. avoid downloading i686 packages) * Use the manifest to avoid missing dependencies by verifying package tree dependencies for each package change on the manifest. Regards Jesus Ornelas Aguayo (chuy) On 7/4/18, 11:14 AM, "Lara, Cesar" wrote: I'm up for taking the complexity out of the picture and have a better error control, so I need people from the community to really take a look at his as this might be what we are going to focus on . Regards Cesar Lara -----Original Message----- From: Ponce Castaneda, Guillermo A [mailto:guillermo.a.ponce.castaneda at intel.com] Sent: Wednesday, July 4, 2018 11:03 AM To: Arevalo, Mario Alfredo C ; starlingx-discuss at lists.starlingx.io Cc: Wold, Saul Subject: Re: [Starlingx-discuss] building proposal Hi Mario, I have been working at StarlingX for over a month now and I would really like to have a tool like this one, it can get very complicated to even create a working mirror by only using the documentation, there are steps/hacks that are not documented or are very hard to follow and this tool would solve everything and take load off the final user. I also understand there are a lot of people that like or have the need to do everything step by step but I am also sure that some other people will find this tool very handy, so I would like to work on this project. Thanks and Regards. - Guillermo (Memo) Ponce On 7/4/18, 10:33 AM, "Arevalo, Mario Alfredo C" wrote: Hi folks, Taking a look inside stx-tools mirror, I come up with an idea related to the building ISO flow, I think the most of the instructions can be automated in a centralized tool. This tool can be developed in golang or python language in order to take advantage of the provided modules by these languages. Furthermore we can improve the error handling, and hide the flow complexity due to the current stuff could be a little prone to error. The idea is to have some basic commands as first version. $ stx mirror donwload/create an RPM mirror $ stx build-iso build an ISO image using a possible mirror as input (e.g. --mirror/home/user/mirror), or if it does not exist, crate one. I would like some comments related to this. Best regards. Mario. _______________________________________________ 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 yong.hu at intel.com Fri Jul 6 00:55:33 2018 From: yong.hu at intel.com (Hu, Yong) Date: Fri, 6 Jul 2018 00:55:33 +0000 Subject: [Starlingx-discuss] [stx-tools] New Kernel Version Message-ID: <839B019D-3E5A-48ED-A2E5-3B49ABDF40B4@intel.com> Hi Ken, We might need a sync-up on this kernel upgrade topic. Actually, moving forward, I would suggest, if there are any big changes to come, we both sides need to inform each other in advance, to avoid duplications or conflicts. Regards, Yong From: "Young, Ken" Date: Friday, 6 July 2018 at 12:21 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [stx-tools] New Kernel Version I discovered 2 new reviews this morning which are security related this morning: https://review.openstack.org/#/c/580287/ https://review.openstack.org/#/c/580308/ These reviews propose to merge the latest CentOS kernel 862.6.3 to address the latest Spectre / Meltdown CVEs. Before this is completed, we have a kernel update to 862.3.2 we would like to merge which includes module updates to enable containers which we would like to get in first. Otherwise, this will generate a significant amount of rework for these submissions. The easiest path is to follow the kernels in order. We will work to get our updated kernel in ASAP. Thank you in advance. Regards, Ken Y -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Fri Jul 6 00:58:17 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Fri, 6 Jul 2018 00:58:17 +0000 Subject: [Starlingx-discuss] [stx-tools] New Kernel Version In-Reply-To: <839B019D-3E5A-48ED-A2E5-3B49ABDF40B4@intel.com> References: <839B019D-3E5A-48ED-A2E5-3B49ABDF40B4@intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0C939C@ALA-MBD.corp.ad.wrs.com> Going forward, I would recommend pending upgrades be posted to the mailing list before the reviews are actually submitted. Brent From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Thursday, July 5, 2018 8:56 PM To: Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Hi Ken, We might need a sync-up on this kernel upgrade topic. Actually, moving forward, I would suggest, if there are any big changes to come, we both sides need to inform each other in advance, to avoid duplications or conflicts. Regards, Yong From: "Young, Ken" > Date: Friday, 6 July 2018 at 12:21 AM To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] [stx-tools] New Kernel Version I discovered 2 new reviews this morning which are security related this morning: https://review.openstack.org/#/c/580287/ https://review.openstack.org/#/c/580308/ These reviews propose to merge the latest CentOS kernel 862.6.3 to address the latest Spectre / Meltdown CVEs. Before this is completed, we have a kernel update to 862.3.2 we would like to merge which includes module updates to enable containers which we would like to get in first. Otherwise, this will generate a significant amount of rework for these submissions. The easiest path is to follow the kernels in order. We will work to get our updated kernel in ASAP. Thank you in advance. Regards, Ken Y -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Fri Jul 6 01:13:20 2018 From: yong.hu at intel.com (Hu, Yong) Date: Fri, 6 Jul 2018 01:13:20 +0000 Subject: [Starlingx-discuss] [stx-tools] New Kernel Version In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB0C939C@ALA-MBD.corp.ad.wrs.com> References: <839B019D-3E5A-48ED-A2E5-3B49ABDF40B4@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0C939C@ALA-MBD.corp.ad.wrs.com> Message-ID: <4BF83FBF-6E76-41A4-8E61-360D252C7FCF@intel.com> Makes sense! Do we intend/agree to apply this rule on all new features or big changes (though practically how we gate the granularity of changes?)? Regards, Yong From: "Rowsell, Brent" Date: Friday, 6 July 2018 at 8:58 AM To: "Hu, Yong" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: RE: [Starlingx-discuss] [stx-tools] New Kernel Version Going forward, I would recommend pending upgrades be posted to the mailing list before the reviews are actually submitted. Brent From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Thursday, July 5, 2018 8:56 PM To: Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Hi Ken, We might need a sync-up on this kernel upgrade topic. Actually, moving forward, I would suggest, if there are any big changes to come, we both sides need to inform each other in advance, to avoid duplications or conflicts. Regards, Yong From: "Young, Ken" > Date: Friday, 6 July 2018 at 12:21 AM To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] [stx-tools] New Kernel Version I discovered 2 new reviews this morning which are security related this morning: https://review.openstack.org/#/c/580287/ https://review.openstack.org/#/c/580308/ These reviews propose to merge the latest CentOS kernel 862.6.3 to address the latest Spectre / Meltdown CVEs. Before this is completed, we have a kernel update to 862.3.2 we would like to merge which includes module updates to enable containers which we would like to get in first. Otherwise, this will generate a significant amount of rework for these submissions. The easiest path is to follow the kernels in order. We will work to get our updated kernel in ASAP. Thank you in advance. Regards, Ken Y -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Fri Jul 6 02:18:22 2018 From: yong.hu at intel.com (Hu, Yong) Date: Fri, 6 Jul 2018 02:18:22 +0000 Subject: [Starlingx-discuss] [stx-tools] New Kernel Version In-Reply-To: <4BF83FBF-6E76-41A4-8E61-360D252C7FCF@intel.com> References: <839B019D-3E5A-48ED-A2E5-3B49ABDF40B4@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0C939C@ALA-MBD.corp.ad.wrs.com> <4BF83FBF-6E76-41A4-8E61-360D252C7FCF@intel.com> Message-ID: <98D9C69F-A421-4149-BC69-EFE07FB67EE0@intel.com> Hi Ken, >>> we have a kernel update to 862.3.2 >>> We will work to get our updated kernel in ASAP Did you mean WRS has already been working on upgrade to 862.3.2? Could you please post the activities and progress here in this mailing list, so that we all are aware of it? Regards, Yong From: "Hu, Yong" Date: Friday, 6 July 2018 at 9:14 AM To: "Rowsell, Brent" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Makes sense! Do we intend/agree to apply this rule on all new features or big changes (though practically how we gate the granularity of changes?)? Regards, Yong From: "Rowsell, Brent" Date: Friday, 6 July 2018 at 8:58 AM To: "Hu, Yong" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: RE: [Starlingx-discuss] [stx-tools] New Kernel Version Going forward, I would recommend pending upgrades be posted to the mailing list before the reviews are actually submitted. Brent From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Thursday, July 5, 2018 8:56 PM To: Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Hi Ken, We might need a sync-up on this kernel upgrade topic. Actually, moving forward, I would suggest, if there are any big changes to come, we both sides need to inform each other in advance, to avoid duplications or conflicts. Regards, Yong From: "Young, Ken" > Date: Friday, 6 July 2018 at 12:21 AM To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] [stx-tools] New Kernel Version I discovered 2 new reviews this morning which are security related this morning: https://review.openstack.org/#/c/580287/ https://review.openstack.org/#/c/580308/ These reviews propose to merge the latest CentOS kernel 862.6.3 to address the latest Spectre / Meltdown CVEs. Before this is completed, we have a kernel update to 862.3.2 we would like to merge which includes module updates to enable containers which we would like to get in first. Otherwise, this will generate a significant amount of rework for these submissions. The easiest path is to follow the kernels in order. We will work to get our updated kernel in ASAP. Thank you in advance. Regards, Ken Y -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ken.Young at windriver.com Fri Jul 6 13:42:43 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Fri, 6 Jul 2018 13:42:43 +0000 Subject: [Starlingx-discuss] [stx-tools] New Kernel Version In-Reply-To: <98D9C69F-A421-4149-BC69-EFE07FB67EE0@intel.com> References: <839B019D-3E5A-48ED-A2E5-3B49ABDF40B4@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0C939C@ALA-MBD.corp.ad.wrs.com> <4BF83FBF-6E76-41A4-8E61-360D252C7FCF@intel.com> <98D9C69F-A421-4149-BC69-EFE07FB67EE0@intel.com> Message-ID: <25398361-E529-4DF7-BD02-1F994B9E6511@windriver.com> See inline. From: YONG HU Date: Thursday, July 5, 2018 at 10:18 PM To: "Rowsell, Brent" , Ken Young , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Hi Ken, >>> we have a kernel update to 862.3.2 >>> We will work to get our updated kernel in ASAP Did you mean WRS has already been working on upgrade to 862.3.2? Yes. We had already migrated to this kernel to enable our kubernetes efforts. The kernel contained capabilities we needed. Could you please post the activities and progress here in this mailing list, so that we all are aware of it? We are planning to put the 862.3.2 into the openstack repos today. Regards, Yong From: "Hu, Yong" Date: Friday, 6 July 2018 at 9:14 AM To: "Rowsell, Brent" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Makes sense! Do we intend/agree to apply this rule on all new features or big changes (though practically how we gate the granularity of changes?)? Regards, Yong From: "Rowsell, Brent" Date: Friday, 6 July 2018 at 8:58 AM To: "Hu, Yong" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: RE: [Starlingx-discuss] [stx-tools] New Kernel Version Going forward, I would recommend pending upgrades be posted to the mailing list before the reviews are actually submitted. Brent From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Thursday, July 5, 2018 8:56 PM To: Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Hi Ken, We might need a sync-up on this kernel upgrade topic. Actually, moving forward, I would suggest, if there are any big changes to come, we both sides need to inform each other in advance, to avoid duplications or conflicts. Regards, Yong From: "Young, Ken" > Date: Friday, 6 July 2018 at 12:21 AM To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] [stx-tools] New Kernel Version I discovered 2 new reviews this morning which are security related this morning: https://review.openstack.org/#/c/580287/ https://review.openstack.org/#/c/580308/ These reviews propose to merge the latest CentOS kernel 862.6.3 to address the latest Spectre / Meltdown CVEs. Before this is completed, we have a kernel update to 862.3.2 we would like to merge which includes module updates to enable containers which we would like to get in first. Otherwise, this will generate a significant amount of rework for these submissions. The easiest path is to follow the kernels in order. We will work to get our updated kernel in ASAP. Thank you in advance. Regards, Ken Y -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ken.Young at windriver.com Fri Jul 6 15:58:35 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Fri, 6 Jul 2018 15:58:35 +0000 Subject: [Starlingx-discuss] [stx-tools] New Kernel Version In-Reply-To: <25398361-E529-4DF7-BD02-1F994B9E6511@windriver.com> References: <839B019D-3E5A-48ED-A2E5-3B49ABDF40B4@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0C939C@ALA-MBD.corp.ad.wrs.com> <4BF83FBF-6E76-41A4-8E61-360D252C7FCF@intel.com> <98D9C69F-A421-4149-BC69-EFE07FB67EE0@intel.com> <25398361-E529-4DF7-BD02-1F994B9E6511@windriver.com> Message-ID: The reviews for the updated kernel are here: https://review.openstack.org/#/c/580688/ https://review.openstack.org/580689 https://review.openstack.org/580690 https://review.openstack.org/580692 /KenY From: Ken Young Date: Friday, July 6, 2018 at 9:42 AM To: YONG HU , "Rowsell, Brent" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version See inline. From: YONG HU Date: Thursday, July 5, 2018 at 10:18 PM To: "Rowsell, Brent" , Ken Young , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Hi Ken, >>> we have a kernel update to 862.3.2 >>> We will work to get our updated kernel in ASAP Did you mean WRS has already been working on upgrade to 862.3.2? Yes. We had already migrated to this kernel to enable our kubernetes efforts. The kernel contained capabilities we needed. Could you please post the activities and progress here in this mailing list, so that we all are aware of it? We are planning to put the 862.3.2 into the openstack repos today. Regards, Yong From: "Hu, Yong" Date: Friday, 6 July 2018 at 9:14 AM To: "Rowsell, Brent" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Makes sense! Do we intend/agree to apply this rule on all new features or big changes (though practically how we gate the granularity of changes?)? Regards, Yong From: "Rowsell, Brent" Date: Friday, 6 July 2018 at 8:58 AM To: "Hu, Yong" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: RE: [Starlingx-discuss] [stx-tools] New Kernel Version Going forward, I would recommend pending upgrades be posted to the mailing list before the reviews are actually submitted. Brent From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Thursday, July 5, 2018 8:56 PM To: Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Hi Ken, We might need a sync-up on this kernel upgrade topic. Actually, moving forward, I would suggest, if there are any big changes to come, we both sides need to inform each other in advance, to avoid duplications or conflicts. Regards, Yong From: "Young, Ken" > Date: Friday, 6 July 2018 at 12:21 AM To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] [stx-tools] New Kernel Version I discovered 2 new reviews this morning which are security related this morning: https://review.openstack.org/#/c/580287/ https://review.openstack.org/#/c/580308/ These reviews propose to merge the latest CentOS kernel 862.6.3 to address the latest Spectre / Meltdown CVEs. Before this is completed, we have a kernel update to 862.3.2 we would like to merge which includes module updates to enable containers which we would like to get in first. Otherwise, this will generate a significant amount of rework for these submissions. The easiest path is to follow the kernels in order. We will work to get our updated kernel in ASAP. Thank you in advance. Regards, Ken Y -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Fri Jul 6 18:28:52 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 6 Jul 2018 18:28:52 +0000 Subject: [Starlingx-discuss] Upcoming commits Message-ID: <151EE31B9FCCA54397A757BC674650F0BA314972@ALA-MBD.corp.ad.wrs.com> Hi, It was suggested on the mailing list earlier today that an email to be sent out with any big changes that are in progress. In line with this suggestion, I'm attaching a list of stories/items that the Wind River team is actively working on and will be sending out for reviews in the next week or so. Regards, Ghada Ghada Khalil, Manager, Titanium Cloud, Wind River direct 613.270.2273 skype ghada.khalil.ottawa 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: stx-in-progress-stories.txt URL: From Brent.Rowsell at windriver.com Fri Jul 6 20:05:19 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Fri, 6 Jul 2018 20:05:19 +0000 Subject: [Starlingx-discuss] Repo consolidation References: <2588653EBDFFA34B982FAF00F1B4844EBB0AD5F0@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB5470FF@fmsmsx117.amr.corp.intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0AD885@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB0ADF6F@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB549971@fmsmsx117.amr.corp.intel.com> <91BAF06A-4AA6-434B-B569-554957924315@windriver.com> <2c45cfbd-0fcb-ae1a-e46e-d1958cd6b377@windriver.com> <9A85D2917C58154C960D95352B22818BAB54A367@fmsmsx117.amr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0CA0CB@ALA-MBD.corp.ad.wrs.com> Folks, I’ve created https://storyboard.openstack.org/#!/story/2002801 to track this. Please provide any feedback you might have. We are targeting submission for July 16th. Thanks, Brent From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Tuesday, June 19, 2018 2:23 PM To: Little, Scott >; Jolliffe, Ian >; Rowsell, Brent >; CORDOBA MALIBRAN, ERICH >; starlingx-discuss at lists.starlingx.io Cc: AMBARDEKAR, PRANJAL > Subject: RE: [Starlingx-discuss] Repo consolidation Cool. Can we see the document? Best way would be to create a Story and enter the contents into the Story so we can all see it. brucej From: Scott Little [mailto:scott.little at windriver.com] Sent: Tuesday, June 19, 2018 7:40 AM To: Jolliffe, Ian (Wind River) >; Jones, Bruce E >; Rowsell, Brent (Wind River) >; Cordoba Malibran, Erich >; starlingx-discuss at lists.starlingx.io Cc: Ambardekar, Pranjal > Subject: Re: [Starlingx-discuss] Repo consolidation Ok, I'll proceed with the reorg per Brent's 'Starlingx_setup_v3.xlxs' document. I'll do the work piecewise, and leave relocating stx-gplv2/3 content till last. So there is still some time for discussion. Scott On 18-06-19 10:04 AM, Jolliffe, Ian wrote: Hi Bruce; Thanks for your flexibility – we will proceed with consolidation. The fewer repos the better, it will be one place to monitor and retire these changes. Maybe there are some ways to make the tool work for us – instead of the other way around. Let’s discuss on IRC. Regards; Ian From: "Jones, Bruce E" Date: Monday, June 18, 2018 at 5:40 PM To: Brent Rowsell , "CORDOBA MALIBRAN, ERICH" , "starlingx-discuss at lists.starlingx.io" Cc: "AMBARDEKAR, PRANJAL" Subject: Re: [Starlingx-discuss] Repo consolidation I met with Pranjal and Abraham today to discuss this. The problem is that we separated that code out for a reason. We have an internal requirement to run a license scanning tool, and the tool assumes that all of the code within a single git repo is covered by the same license. If you have files covered under multiple licenses, it reports errors. It’s rather silly that we’re letting a tool dictate something like this. We are setting up a process to run that tool on a regular basis, so when it comes time to do a release, we don’t run into issues that we didn’t already know about. It would not be the end of the world if someone submitted and approved a PR to merge those repos. It would make mine, Abraham’s and Pranjal’s lives easier if we did not. If you think that this would make things better for everyone else, I would withdraw my objection. Meanwhile, our goal is to get rid of those repos, long term. Brucej From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Wednesday, June 13, 2018 12:00 PM To: Cordoba Malibran, Erich ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Cc: Ambardekar, Pranjal Subject: RE: [Starlingx-discuss] Repo consolidation The objective over time is to eliminate the changes to these open source packages by upstreaming the changes. Given that, I don’t think we want the overhead of creating/managing 250 repos. This project already has 50 repos. Currently we have these packages spread over 4 repos with no real functional division. I am proposing it would make more sense to consolidate into one. One repo to manage, making it easier to track the retirement of customizations over time. Brent -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Sat Jul 7 15:50:09 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Sat, 7 Jul 2018 10:50:09 -0500 Subject: [Starlingx-discuss] Upcoming commits In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA314972@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA314972@ALA-MBD.corp.ad.wrs.com> Message-ID: On Fri, Jul 6, 2018 at 1:28 PM, Khalil, Ghada wrote: > In line with this suggestion, I’m attaching a list of stories/items that the > Wind River team is actively working on and will be sending out for reviews > in the next week or so. Thank you Ghada! I am copying the list in-line as attachments do not always archive well... 2002882: [Enhancement] Miscellaneous system maintenance improvements 2002884: [Enhancement] Code cleanup related to ceph cache tiering 2002888: [Enhancement] sysinv tox improvements 2002895: [Enhancement] Miscellaneous engineering tools improvements 2002820: [Feature] Support for external ceph backend 2002822: [Feature] Support remote client for windows and mac 2002823: [Feature] Collectd Integration for platform resource monitoring 2002824: [Feature] Deprecate proprietary cinder volume backup and restore 2002834: [Feature] Add distributed cloud repos to StarlingX 2002839: [Feature] Docker Runtime Integration 2002840: [Feature] Local Docker Registry 2002841: [Feature] ETCD Integration 2002842: [Feature] Distributed Cloud Keystone Scalability 2002843: [Feature] Initial Kubernetes Integration 2002876: [Feature] Containerized Openstack Prep 2002836: [Bug] Branding typo in config file utility 2002837: [Bug] configutilities README is missing yum commands for CentOS 2002838: [Bug] Unrecoverable sm-api process failure causing controller degrade on IPv6 system 2002851: [Bug] LLDP information on compute nodes not available on initial node install 2002852: [Bug] Unexpected return code on firewall-rules-install failed command 2002853: [Bug] Remote CLI commands fail with Python 3 2002854: [Bug] Remote CLI: Failed to execute: 'openstack --os-identity-api-version 3 event list --filte... 2002855: [Bug] No alarm event generated after killing nova-novnc or vim-webserver process 2+ times 2002856: [Bug] Install using PXE hangs when pxeboot server uses non-standard port number 2002857: [Bug] Distributed Cloud: Horizon issues seen on subclouds when navigating to another subcloud 2002858: [Bug] Service parameter hierarchy allows multiple values for same key 2002859: [Bug] Multiple patch application can fail 2002860: [Bug] VM evacuation intermittent failure on compute force lock 2002861: [Bug] sysinv agent error "Too many open files" 2002862: [Bug] User does not get logged out after the Horizon's SESSION_TIMEOUT value has passed 2002863: [Bug] Distributed Cloud: Patch orchestration fails if AIO-SX host is locked 2002864: [Bug] controller filesystem resize failed (drbd) 2002865: [Bug] AIO-DX: controller-1 fails to PXE boot when duplex-direct is configured with LAG 2002866: [Bug] Volume download time excessively slow; conversion that needs sync is slow 2002869: [Bug] Distributed Cloud: subcloud add should accept 5 IP addresses for MGMT to support /29 sub... 2002870: [Bug] Distributed Cloud: Disallow usage of the entire management IP range 2002871: [Bug] Distributed Cloud: Disallow infrastructure network provisioning on system controllers 2002872: [Bug] VM fails to launch with single core "VMs" function 2002873: [Bug] nova-local instance lv size still shown in MiB rather than GiB 2002889: [Bug] CVE: CVE-2014-9402, CVE-2017-15670, CVE-2017-15804: glibc 2002893: [Bug] Error in cinder volume creation due to cinder process restart 2002894: [Bug] Toggling between http and https w/ TPM causes horizon failure dt -- Dean Troyer dtroyer at gmail.com From yong.hu at intel.com Sun Jul 8 01:17:26 2018 From: yong.hu at intel.com (Hu, Yong) Date: Sun, 8 Jul 2018 01:17:26 +0000 Subject: [Starlingx-discuss] [stx-tools] New Kernel Version In-Reply-To: References: <839B019D-3E5A-48ED-A2E5-3B49ABDF40B4@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0C939C@ALA-MBD.corp.ad.wrs.com> <4BF83FBF-6E76-41A4-8E61-360D252C7FCF@intel.com> <98D9C69F-A421-4149-BC69-EFE07FB67EE0@intel.com> <25398361-E529-4DF7-BD02-1F994B9E6511@windriver.com> Message-ID: <56CE6087-AF0A-48B7-BF11-DEC1156197C6@intel.com> On top of these patches, does anyone has concerns to upgrade kernel to the latest 862.6.3?? BTW, from security perspective, CVE-2018-8897 was updated on 862.3.2 and CVE-2018-3665 was on 862.3.3. ====================================================== POP SS (CVE-2018-8897) – Done on May 8 [Software Only Fix] CentOS6.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022827.html 2.       Speculative Store Bypass Disable (SSBD) (CVE-2018-3639) – Done on May 21 [Software+Microcode Fix] CentOS6.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022835.html CentOS7.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022843.html kernel-3.10.0-862.3.2.el7 3.            Lazy FP State Restore (CVE-2018-3665) – Done on June 13 [Software only Fix] - CentOS7.X: https://lists.centos.org/pipermail/centos-announce/2018-June/022923.html kernel-3.10.0-862.3.3.el7 ======================================================= From: "Young, Ken" Date: Friday, 6 July 2018 at 11:58 PM To: "Hu, Yong" , "Rowsell, Brent" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version The reviews for the updated kernel are here:   https://review.openstack.org/#/c/580688/ https://review.openstack.org/580689 https://review.openstack.org/580690 https://review.openstack.org/580692   /KenY   From: Ken Young Date: Friday, July 6, 2018 at 9:42 AM To: YONG HU , "Rowsell, Brent" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version   See inline.   From: YONG HU Date: Thursday, July 5, 2018 at 10:18 PM To: "Rowsell, Brent" , Ken Young , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version   Hi Ken, >>> we have a kernel update to 862.3.2 >>> We will work to get our updated kernel in ASAP Did you mean WRS has already been working on upgrade to 862.3.2?   Yes.  We had already migrated to this kernel to enable our kubernetes efforts.  The kernel contained capabilities we needed.   Could you please post the activities and progress here in this mailing list, so that we all are aware of it?   We are planning to put the 862.3.2 into the openstack repos today.   Regards, Yong   From: "Hu, Yong" Date: Friday, 6 July 2018 at 9:14 AM To: "Rowsell, Brent" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version   Makes sense! Do we intend/agree to apply this rule on all new features or big changes (though practically how we gate the granularity of changes?)? Regards, Yong From: "Rowsell, Brent" Date: Friday, 6 July 2018 at 8:58 AM To: "Hu, Yong" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: RE: [Starlingx-discuss] [stx-tools] New Kernel Version   Going forward, I would recommend pending upgrades be posted to the mailing list before the reviews are actually submitted.   Brent   From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Thursday, July 5, 2018 8:56 PM To: Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version   Hi Ken, We might need a sync-up on this kernel upgrade topic. Actually, moving forward, I would suggest, if there are any big changes to come, we both sides need to inform each other in advance, to avoid duplications or conflicts.   Regards, Yong From: "Young, Ken" Date: Friday, 6 July 2018 at 12:21 AM To: "mailto:starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [stx-tools] New Kernel Version   I discovered 2 new reviews this morning which are security related this morning: https://review.openstack.org/#/c/580287/ https://review.openstack.org/#/c/580308/   These reviews propose to merge the latest CentOS kernel 862.6.3 to address the latest Spectre / Meltdown CVEs.   Before this is completed, we have a kernel update to 862.3.2 we would like to merge which includes module updates to enable containers which we would like to get in first.  Otherwise, this will generate a significant amount of rework for these submissions.  The easiest path is to follow the kernels in order.   We will work to get our updated kernel in ASAP.   Thank you in advance.   Regards, Ken Y From Brent.Rowsell at windriver.com Mon Jul 9 11:05:31 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Mon, 9 Jul 2018 11:05:31 +0000 Subject: [Starlingx-discuss] [stx-tools] New Kernel Version In-Reply-To: <56CE6087-AF0A-48B7-BF11-DEC1156197C6@intel.com> References: <839B019D-3E5A-48ED-A2E5-3B49ABDF40B4@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0C939C@ALA-MBD.corp.ad.wrs.com> <4BF83FBF-6E76-41A4-8E61-360D252C7FCF@intel.com> <98D9C69F-A421-4149-BC69-EFE07FB67EE0@intel.com> <25398361-E529-4DF7-BD02-1F994B9E6511@windriver.com> <56CE6087-AF0A-48B7-BF11-DEC1156197C6@intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0CB692@ALA-MBD.corp.ad.wrs.com> What testing has been done with 862.6.3 ? Brent -----Original Message----- From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Saturday, July 7, 2018 9:17 PM To: Young, Ken ; Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version On top of these patches, does anyone has concerns to upgrade kernel to the latest 862.6.3?? BTW, from security perspective, CVE-2018-8897 was updated on 862.3.2 and CVE-2018-3665 was on 862.3.3. ====================================================== POP SS (CVE-2018-8897) – Done on May 8 [Software Only Fix] CentOS6.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022827.html 2.       Speculative Store Bypass Disable (SSBD) (CVE-2018-3639) – Done on May 21 [Software+Microcode Fix] CentOS6.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022835.html CentOS7.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022843.html kernel-3.10.0-862.3.2.el7 3.            Lazy FP State Restore (CVE-2018-3665) – Done on June 13 [Software only Fix] - CentOS7.X: https://lists.centos.org/pipermail/centos-announce/2018-June/022923.html kernel-3.10.0-862.3.3.el7 ======================================================= From: "Young, Ken" Date: Friday, 6 July 2018 at 11:58 PM To: "Hu, Yong" , "Rowsell, Brent" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version The reviews for the updated kernel are here:   https://review.openstack.org/#/c/580688/ https://review.openstack.org/580689 https://review.openstack.org/580690 https://review.openstack.org/580692   /KenY   From: Ken Young Date: Friday, July 6, 2018 at 9:42 AM To: YONG HU , "Rowsell, Brent" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version   See inline.   From: YONG HU Date: Thursday, July 5, 2018 at 10:18 PM To: "Rowsell, Brent" , Ken Young , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version   Hi Ken, >>> we have a kernel update to 862.3.2 >>> We will work to get our updated kernel in ASAP Did you mean WRS has already been working on upgrade to 862.3.2?   Yes.  We had already migrated to this kernel to enable our kubernetes efforts.  The kernel contained capabilities we needed.   Could you please post the activities and progress here in this mailing list, so that we all are aware of it?   We are planning to put the 862.3.2 into the openstack repos today.   Regards, Yong   From: "Hu, Yong" Date: Friday, 6 July 2018 at 9:14 AM To: "Rowsell, Brent" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version   Makes sense! Do we intend/agree to apply this rule on all new features or big changes (though practically how we gate the granularity of changes?)? Regards, Yong From: "Rowsell, Brent" Date: Friday, 6 July 2018 at 8:58 AM To: "Hu, Yong" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: RE: [Starlingx-discuss] [stx-tools] New Kernel Version   Going forward, I would recommend pending upgrades be posted to the mailing list before the reviews are actually submitted.   Brent   From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Thursday, July 5, 2018 8:56 PM To: Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version   Hi Ken, We might need a sync-up on this kernel upgrade topic. Actually, moving forward, I would suggest, if there are any big changes to come, we both sides need to inform each other in advance, to avoid duplications or conflicts.   Regards, Yong From: "Young, Ken" Date: Friday, 6 July 2018 at 12:21 AM To: "mailto:starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [stx-tools] New Kernel Version   I discovered 2 new reviews this morning which are security related this morning: https://review.openstack.org/#/c/580287/ https://review.openstack.org/#/c/580308/   These reviews propose to merge the latest CentOS kernel 862.6.3 to address the latest Spectre / Meltdown CVEs.   Before this is completed, we have a kernel update to 862.3.2 we would like to merge which includes module updates to enable containers which we would like to get in first.  Otherwise, this will generate a significant amount of rework for these submissions.  The easiest path is to follow the kernels in order.   We will work to get our updated kernel in ASAP.   Thank you in advance.   Regards, Ken Y From ildiko.vancsa at gmail.com Mon Jul 9 22:45:13 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 9 Jul 2018 17:45:13 -0500 Subject: [Starlingx-discuss] Weekly meetings starting this Wednesday Message-ID: Hi, As it was mentioned on the mailing list earlier we will be having weekly calls for StarlingX. The first call will take place this Wednesday (July 11) 7am PST / 1400 UTC on Zoom. You can find the meeting details and the agenda on the wiki:https://wiki.openstack.org/wiki/StarlingX#Meetings Feel free to add agenda items on the wiki if you have a topic you would like to discuss. Please add your name to the item so we know who to give the floor on the call. Please let me know if you have any questions. Thanks and Best Regards, Ildikó Váncsa Ecosystem Technical Lead, OpenStack Foundation (IRC: ildikov) From bruce.e.jones at intel.com Mon Jul 9 22:46:12 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 9 Jul 2018 22:46:12 +0000 Subject: [Starlingx-discuss] RFC: StarlingX release cadence proposal In-Reply-To: <03D458D5BAFF6041973594B00B4E58CE590D43D1@FMSMSX102.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB54E25A@fmsmsx117.amr.corp.intel.com> <4F6AACE4B0F173488D033B02A8BB5B7E7169FD30@fmsmsx104.amr.corp.intel.com> <03D458D5BAFF6041973594B00B4E58CE590D43D1@FMSMSX102.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB55EE98@fmsmsx117.amr.corp.intel.com> Fernando, you are my new hero. This visual of the schedule is awesome and super helpful. Thank you! Meanwhile, having heard no objections to the proposal, I'm going to assume that we all agree and that this is our new release plan. I will update my documents accordingly. To address your points below: · This plan completely replaces the Beta1/2 RC... plan. I will update the etherpad today. · Re: the "4-6 weeks of time to run tests", I was just guessing. Looking at your awesome table, it looks like we'll have 6 weeks most of the time except in February, where we only get 5 weeks. Comments · I don't know how TC does version numbers. Someone should find out and make a Story for how we want to change that. Pending · Regarding the N and N-1 branches, I would think that they would expire at the point they become an N-2 branch. For instance, the stx.08.2018 branch becomes N-2 once stx.02.2019 is created. · Long Term Support is likely going to remain unclear, or at least undecided, for now. We'll need to get a couple of releases under our belt and lots of test cycles passing before we want to declare anything LTS. brucej From: Hernandez Gonzalez, Fernando Sent: Tuesday, July 3, 2018 3:50 PM To: Cabrales, Ada ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: RFC: StarlingX release cadence proposal Hi Bruce, As you know I am assigned to "Design and document the release" Starlingx task, as part of that task and since I am more a visual guy (Please feel free to use the excel I attached) I created a Schedule that I might be incorporated in our documentation in the future. I reviewed the proposal, looks good to me, but I still have some doubts/comments/pending? · In the "Starlingx Planning etherpad" you talked about Beta1/2 and RC1,2,3... Are they aligned with August Quarterly Cadence or this is just because of the ramp up of the project? · Just curious for quarterly release, why are you saying "This gives us 4-6 weeks of time to run test" and not more or less weeks? Comments · Regarding "version number change from what the underlying TC product uses today" in my previous BIOS project there was a file created when the SPI Firmware was compiled, the script was fed for the version of main components. This help us a lot when some bug appears and we had to do troubleshooting. Maybe it is a way/option to populate a script with underlying TC and CentOS product versions. Pending · How long N and N-1 long live branches are going to keep alive? And same question for short-live. · LTS is still a topic unclear. Do you have more about it? [cid:image002.jpg at 01D4178C.55BFF210] Fernando Hernandez Gonzalez Software Engineer Avenida del Bosque #1001 Col, El Bajío Zapopan, Jalisco MX, 45019 ____________________________________ Office: +52.33.16.45.01.34 inet 86450134 From: Cabrales, Ada [mailto:ada.cabrales at intel.com] Sent: Thursday, June 28, 2018 8:02 PM To: Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] RFC: StarlingX release cadence proposal I like this proposal. I think it would give us periodic, stable versions to work on/with. Also, it gives us the opportunity to plan what would we have on each monthly | quarterly release, considering feature's priority. So, if we decide to follow this schema, let's define what we want to have ready for the Summit in November (the September release, as pointed by Bruce previously) and plan around that. Ada -- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, June 27, 2018 6:48 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] RFC: StarlingX release cadence proposal At our weekly call today we discussed release plans and release cadence. It was a long discussion and a good one. In the end we agreed that we'd like to follow the "bus stop" model of time based releases, and the Ubuntu model of an annual major (LTS) release with quarterly updates. Note that we did not suggest or agree that our currently planned "Release 2" should be a LTS. We all agreed that would be premature. We will declare an LTS at some point in the future. After separate discussions with David, Dean and Ada, rather than just proposing that "our current November release is the first quarterly release", I have a modified proposal to make for how we should handle releases. This is an RFC looking for feedback, questions and comments. Monthly milestone builds -------------------------------- Each month in the 2nd week of the month we will pull a branch. Dean and I suggest using year/month as the branch names, for simplicity. For example, we propose that the branch name for a July 2018 milestone build would be "stx.2018.07". The version number of that build would be "stx.2018.07.0x", where "0x" is a patch number. Yes, that's a change to how version numbers are handled. See below. The purpose of the monthly build is to 1) provide a stable build for long running test cycles 2) provide a "latest known to be good" build for users and partners, and 3) feed into the quarterly release. Fixes for show stopping bugs found in monthly build testing should be done on master and cherry-picked to the branch, increasing the patch number with each one. Quarterly release -------------------- Each quarter's quarterly release will be the monthly milestone build from the 2nd month in the quarter. This gives us 4-6 weeks of time to run test cycles and fix bugs for the release. For each quarterly release, the code freeze for that release is the 2nd week in the 2nd month in the quarter. Branch handling -------------- Branches from the 1st and 3rd month in a quarter can be short-lived. Branches for the 2nd month's (quarterly) build will live longer and I would suggest at any given time we keep the N and N-1 quarterly release branches open for bug fixes. If/when we declare a LTS release, that branch would of course live much longer. Why? ----- Why do we release a build from the 2nd week of the 2nd month? In part because that schedule misses the major holiday weeks. No one likes to do releases over the summer or winter holidays. Impact ------- The planning for release content for what we are currently calling "Release 2" will need to change. If this proposal is accepted, we won't have a "release 2" anymore, just a "release stx.2018.08.x" released in September and "release stx 2018.11.x" released in December. This changes the content we'd have in the release for the November summit (which would be the September release) but anyone there looking for the bleeding edge could pick up the RC for the December build, which would be in testing at that time. Branching also means that key bug fixes would need to be cherry picked to the older branches. New feature code should always go to master only. Version numbers ---------------- This proposal also includes a version number change from what the underlying TC product uses today. I think it's inevitable that the StarlingX project has separate / different version numbers from TC, but I don't know what it means to the system to actually get there, or what headaches it might cause. We should key that up as a separate discussion. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 81368 bytes Desc: image002.jpg URL: From shuicheng.lin at intel.com Tue Jul 10 02:19:33 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 10 Jul 2018 02:19:33 +0000 Subject: [Starlingx-discuss] [stx-tools] New Kernel Version In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB0CB692@ALA-MBD.corp.ad.wrs.com> References: <839B019D-3E5A-48ED-A2E5-3B49ABDF40B4@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0C939C@ALA-MBD.corp.ad.wrs.com> <4BF83FBF-6E76-41A4-8E61-360D252C7FCF@intel.com> <98D9C69F-A421-4149-BC69-EFE07FB67EE0@intel.com> <25398361-E529-4DF7-BD02-1F994B9E6511@windriver.com> <56CE6087-AF0A-48B7-BF11-DEC1156197C6@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0CB692@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C76553375DF@SHSMSX101.ccr.corp.intel.com> Hi Brent, We have gone through basic deploy test in both bare metal and virtual machine case, and doing sanity test now. We also try to verify the updated driver package with the corresponding HW. Best Regards Shuicheng -----Original Message----- From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Monday, July 9, 2018 7:06 PM To: Hu, Yong ; Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version What testing has been done with 862.6.3 ? Brent -----Original Message----- From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Saturday, July 7, 2018 9:17 PM To: Young, Ken ; Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version On top of these patches, does anyone has concerns to upgrade kernel to the latest 862.6.3?? BTW, from security perspective, CVE-2018-8897 was updated on 862.3.2 and CVE-2018-3665 was on 862.3.3. ====================================================== POP SS (CVE-2018-8897) – Done on May 8 [Software Only Fix] CentOS6.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022827.html 2.       Speculative Store Bypass Disable (SSBD) (CVE-2018-3639) – Done on May 21 [Software+Microcode Fix] CentOS6.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022835.html CentOS7.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022843.html kernel-3.10.0-862.3.2.el7 3.            Lazy FP State Restore (CVE-2018-3665) – Done on June 13 [Software only Fix] - CentOS7.X: https://lists.centos.org/pipermail/centos-announce/2018-June/022923.html kernel-3.10.0-862.3.3.el7 ======================================================= From: "Young, Ken" Date: Friday, 6 July 2018 at 11:58 PM To: "Hu, Yong" , "Rowsell, Brent" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version The reviews for the updated kernel are here:   https://review.openstack.org/#/c/580688/ https://review.openstack.org/580689 https://review.openstack.org/580690 https://review.openstack.org/580692   /KenY   From: Ken Young Date: Friday, July 6, 2018 at 9:42 AM To: YONG HU , "Rowsell, Brent" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version   See inline.   From: YONG HU Date: Thursday, July 5, 2018 at 10:18 PM To: "Rowsell, Brent" , Ken Young , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version   Hi Ken, >>> we have a kernel update to 862.3.2 >>> We will work to get our updated kernel in ASAP Did you mean WRS has already been working on upgrade to 862.3.2?   Yes.  We had already migrated to this kernel to enable our kubernetes efforts.  The kernel contained capabilities we needed.   Could you please post the activities and progress here in this mailing list, so that we all are aware of it?   We are planning to put the 862.3.2 into the openstack repos today.   Regards, Yong   From: "Hu, Yong" Date: Friday, 6 July 2018 at 9:14 AM To: "Rowsell, Brent" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version   Makes sense! Do we intend/agree to apply this rule on all new features or big changes (though practically how we gate the granularity of changes?)? Regards, Yong From: "Rowsell, Brent" Date: Friday, 6 July 2018 at 8:58 AM To: "Hu, Yong" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: RE: [Starlingx-discuss] [stx-tools] New Kernel Version   Going forward, I would recommend pending upgrades be posted to the mailing list before the reviews are actually submitted.   Brent   From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Thursday, July 5, 2018 8:56 PM To: Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version   Hi Ken, We might need a sync-up on this kernel upgrade topic. Actually, moving forward, I would suggest, if there are any big changes to come, we both sides need to inform each other in advance, to avoid duplications or conflicts.   Regards, Yong From: "Young, Ken" Date: Friday, 6 July 2018 at 12:21 AM To: "mailto:starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [stx-tools] New Kernel Version   I discovered 2 new reviews this morning which are security related this morning: https://review.openstack.org/#/c/580287/ https://review.openstack.org/#/c/580308/   These reviews propose to merge the latest CentOS kernel 862.6.3 to address the latest Spectre / Meltdown CVEs.   Before this is completed, we have a kernel update to 862.3.2 we would like to merge which includes module updates to enable containers which we would like to get in first.  Otherwise, this will generate a significant amount of rework for these submissions.  The easiest path is to follow the kernels in order.   We will work to get our updated kernel in ASAP.   Thank you in advance.   Regards, Ken Y _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From shuicheng.lin at intel.com Tue Jul 10 02:41:01 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 10 Jul 2018 02:41:01 +0000 Subject: [Starlingx-discuss] [stx-tools] New Kernel Version In-Reply-To: <9700A18779F35F49AF027300A49E7C76553375DF@SHSMSX101.ccr.corp.intel.com> References: <839B019D-3E5A-48ED-A2E5-3B49ABDF40B4@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0C939C@ALA-MBD.corp.ad.wrs.com> <4BF83FBF-6E76-41A4-8E61-360D252C7FCF@intel.com> <98D9C69F-A421-4149-BC69-EFE07FB67EE0@intel.com> <25398361-E529-4DF7-BD02-1F994B9E6511@windriver.com> <56CE6087-AF0A-48B7-BF11-DEC1156197C6@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0CB692@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C76553375DF@SHSMSX101.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C765533765F@SHSMSX101.ccr.corp.intel.com> Hi all, Here is the review link for kernel update to 862.6.3. https://review.openstack.org/#/c/580308/ https://review.openstack.org/#/c/580897/ Best Regards Shuicheng -----Original Message----- From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, July 10, 2018 10:20 AM To: Rowsell, Brent ; Hu, Yong ; Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Hi Brent, We have gone through basic deploy test in both bare metal and virtual machine case, and doing sanity test now. We also try to verify the updated driver package with the corresponding HW. Best Regards Shuicheng -----Original Message----- From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Monday, July 9, 2018 7:06 PM To: Hu, Yong ; Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version What testing has been done with 862.6.3 ? Brent -----Original Message----- From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Saturday, July 7, 2018 9:17 PM To: Young, Ken ; Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version On top of these patches, does anyone has concerns to upgrade kernel to the latest 862.6.3?? BTW, from security perspective, CVE-2018-8897 was updated on 862.3.2 and CVE-2018-3665 was on 862.3.3. ====================================================== POP SS (CVE-2018-8897) – Done on May 8 [Software Only Fix] CentOS6.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022827.html 2.       Speculative Store Bypass Disable (SSBD) (CVE-2018-3639) – Done on May 21 [Software+Microcode Fix] CentOS6.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022835.html CentOS7.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022843.html kernel-3.10.0-862.3.2.el7 3.            Lazy FP State Restore (CVE-2018-3665) – Done on June 13 [Software only Fix] - CentOS7.X: https://lists.centos.org/pipermail/centos-announce/2018-June/022923.html kernel-3.10.0-862.3.3.el7 ======================================================= From: "Young, Ken" Date: Friday, 6 July 2018 at 11:58 PM To: "Hu, Yong" , "Rowsell, Brent" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version The reviews for the updated kernel are here:   https://review.openstack.org/#/c/580688/ https://review.openstack.org/580689 https://review.openstack.org/580690 https://review.openstack.org/580692   /KenY   From: Ken Young Date: Friday, July 6, 2018 at 9:42 AM To: YONG HU , "Rowsell, Brent" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version   See inline.   From: YONG HU Date: Thursday, July 5, 2018 at 10:18 PM To: "Rowsell, Brent" , Ken Young , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version   Hi Ken, >>> we have a kernel update to 862.3.2 >>> We will work to get our updated kernel in ASAP Did you mean WRS has already been working on upgrade to 862.3.2?   Yes.  We had already migrated to this kernel to enable our kubernetes efforts.  The kernel contained capabilities we needed.   Could you please post the activities and progress here in this mailing list, so that we all are aware of it?   We are planning to put the 862.3.2 into the openstack repos today.   Regards, Yong   From: "Hu, Yong" Date: Friday, 6 July 2018 at 9:14 AM To: "Rowsell, Brent" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version   Makes sense! Do we intend/agree to apply this rule on all new features or big changes (though practically how we gate the granularity of changes?)? Regards, Yong From: "Rowsell, Brent" Date: Friday, 6 July 2018 at 8:58 AM To: "Hu, Yong" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: RE: [Starlingx-discuss] [stx-tools] New Kernel Version   Going forward, I would recommend pending upgrades be posted to the mailing list before the reviews are actually submitted.   Brent   From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Thursday, July 5, 2018 8:56 PM To: Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version   Hi Ken, We might need a sync-up on this kernel upgrade topic. Actually, moving forward, I would suggest, if there are any big changes to come, we both sides need to inform each other in advance, to avoid duplications or conflicts.   Regards, Yong From: "Young, Ken" Date: Friday, 6 July 2018 at 12:21 AM To: "mailto:starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [stx-tools] New Kernel Version   I discovered 2 new reviews this morning which are security related this morning: https://review.openstack.org/#/c/580287/ https://review.openstack.org/#/c/580308/   These reviews propose to merge the latest CentOS kernel 862.6.3 to address the latest Spectre / Meltdown CVEs.   Before this is completed, we have a kernel update to 862.3.2 we would like to merge which includes module updates to enable containers which we would like to get in first.  Otherwise, this will generate a significant amount of rework for these submissions.  The easiest path is to follow the kernels in order.   We will work to get our updated kernel in ASAP.   Thank you in advance.   Regards, Ken Y _______________________________________________ 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 erich.cordoba.malibran at intel.com Tue Jul 10 04:51:56 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 10 Jul 2018 04:51:56 +0000 Subject: [Starlingx-discuss] tpm-kmod patches cannot be applied with upstream code Message-ID: Hi all, I'm having problems to apply the patches for tpm-kmod with the code from upstream. The following patch to the tpm_crb.c file is failing: 0001-disable-arm64-acpi-command.patch @@ -572,11 +572,12 @@ static int crb_acpi_add(struct acpi_devi ACPI_TPM2_COMMAND_BUFFER_WITH_SMC); return -EINVAL; } - crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, + struct tpm2_crb_smc *crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, ACPI_TPM2_START_METHOD_PARAMETER_OFFSET); priv->smc_func_id = crb_smc->smc_func_id; priv->flags |= CRB_FL_CRB_SMC_START; } +#endif This patch expects to find crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, ACPI_TPM2_START_METHOD_PARAMETER_OFFSET); However, in the upstream code this line is : crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, sizeof(*buf)); I had reviewed all kernel versions and in none of them ACPI_TPM2_START_METHOD_PARAMETER_OFFSET is used. In the old tmp-kmod tarball (the one in cgcs-dl repository) the name of the tarball references to the SHA fd5c78694f3, however that one doesn't have the specified line[0]. Does anyone can help us to find where this upstream code is? Thanks. [0] http://git.infradead.org/users/jjs/linux-tpmdd.git/blob/fd5c78694f3:/drivers/char/tpm/tpm_crb.c#l575 From bruce.e.jones at intel.com Tue Jul 10 05:03:19 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 10 Jul 2018 05:03:19 +0000 Subject: [Starlingx-discuss] FIrst release branch Message-ID: <9A85D2917C58154C960D95352B22818BAB55F0A2@fmsmsx117.amr.corp.intel.com> As previously discussed on this list, we have agreed to move to a quarterly release model with monthly branches. I proposed pulling monthly branches the 2nd week of each month. And now it's the 2nd week of the month. It's time to pull our first monthly branch. It should be called "stx.2018.07" and it should not be created until the latest kernel updates are complete. Unless those updates aren't in by Thursday, because we're going to pull the branch this week regardless. Erick, can you write a script that creates a branch, and (once the kernel changes are in or Friday happens), run it and pull the branch and kick off a build? The story and tasks are in https://storyboard.openstack.org/#!/story/2002923. Which I can't assign to you. Do you have an OpenStack ID? Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Tue Jul 10 08:35:41 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 10 Jul 2018 08:35:41 +0000 Subject: [Starlingx-discuss] tpm-kmod patches cannot be applied with upstream code In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C7655337736@SHSMSX101.ccr.corp.intel.com> Hi Erich, Please check below link, the definition of "ACPI_TPM2_START_METHOD_PARAMETER_OFFSET" is removed. I think you could update the patch to use the upstream code. https://sourceforge.net/p/tpmdd/mailman/message/35770085/ https://patchwork.kernel.org/patch/9663779/ Best Regards Shuicheng -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Tuesday, July 10, 2018 12:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] tpm-kmod patches cannot be applied with upstream code Hi all, I'm having problems to apply the patches for tpm-kmod with the code from upstream. The following patch to the tpm_crb.c file is failing: 0001-disable-arm64-acpi-command.patch @@ -572,11 +572,12 @@ static int crb_acpi_add(struct acpi_devi ACPI_TPM2_COMMAND_BUFFER_WITH_SMC); return -EINVAL; } - crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, + struct tpm2_crb_smc *crb_smc = ACPI_ADD_PTR(struct + tpm2_crb_smc, buf, ACPI_TPM2_START_METHOD_PARAMETER_OFFSET); priv->smc_func_id = crb_smc->smc_func_id; priv->flags |= CRB_FL_CRB_SMC_START; } +#endif This patch expects to find crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, ACPI_TPM2_START_METHOD_PARAMETER_OFFSET); However, in the upstream code this line is : crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, sizeof(*buf)); I had reviewed all kernel versions and in none of them ACPI_TPM2_START_METHOD_PARAMETER_OFFSET is used. In the old tmp-kmod tarball (the one in cgcs-dl repository) the name of the tarball references to the SHA fd5c78694f3, however that one doesn't have the specified line[0]. Does anyone can help us to find where this upstream code is? Thanks. [0] http://git.infradead.org/users/jjs/linux-tpmdd.git/blob/fd5c78694f3:/drivers/char/tpm/tpm_crb.c#l575 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Brent.Rowsell at windriver.com Tue Jul 10 11:20:49 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Tue, 10 Jul 2018 11:20:49 +0000 Subject: [Starlingx-discuss] tpm-kmod patches cannot be applied with upstream code In-Reply-To: References: Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0CDF3F@ALA-MBD.corp.ad.wrs.com> Erich, Why are we upversioning this now ? Brent -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Tuesday, July 10, 2018 12:52 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] tpm-kmod patches cannot be applied with upstream code Hi all, I'm having problems to apply the patches for tpm-kmod with the code from upstream. The following patch to the tpm_crb.c file is failing: 0001-disable-arm64-acpi-command.patch @@ -572,11 +572,12 @@ static int crb_acpi_add(struct acpi_devi ACPI_TPM2_COMMAND_BUFFER_WITH_SMC); return -EINVAL; } - crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, + struct tpm2_crb_smc *crb_smc = ACPI_ADD_PTR(struct + tpm2_crb_smc, buf, ACPI_TPM2_START_METHOD_PARAMETER_OFFSET); priv->smc_func_id = crb_smc->smc_func_id; priv->flags |= CRB_FL_CRB_SMC_START; } +#endif This patch expects to find crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, ACPI_TPM2_START_METHOD_PARAMETER_OFFSET); However, in the upstream code this line is : crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, sizeof(*buf)); I had reviewed all kernel versions and in none of them ACPI_TPM2_START_METHOD_PARAMETER_OFFSET is used. In the old tmp-kmod tarball (the one in cgcs-dl repository) the name of the tarball references to the SHA fd5c78694f3, however that one doesn't have the specified line[0]. Does anyone can help us to find where this upstream code is? Thanks. [0] http://git.infradead.org/users/jjs/linux-tpmdd.git/blob/fd5c78694f3:/drivers/char/tpm/tpm_crb.c#l575 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Tue Jul 10 04:31:25 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 10 Jul 2018 04:31:25 +0000 Subject: [Starlingx-discuss] RFC: StarlingX release cadence proposal Message-ID: <68F20408-BB2B-4AA6-9CB7-9E6BF5C2FD5F@intel.com> Hi, Not sure if this is out of the scope of this proposal but now that we have defined a release cadence, which would be the best dates within the quarterly release to define the items/feature to be released (a release planning)? Also we would need to define a bug scrub or some related meeting to decide which bugs will be fixed in the release. -Erich From: "Jones, Bruce E" Date: Monday, July 9, 2018 at 6:29 PM To: "Hernandez Gonzalez, Fernando" , "Cabrales, Ada" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] RFC: StarlingX release cadence proposal Fernando, you are my new hero. This visual of the schedule is awesome and super helpful. Thank you! Meanwhile, having heard no objections to the proposal, I’m going to assume that we all agree and that this is our new release plan. I will update my documents accordingly. To address your points below: · This plan completely replaces the Beta1/2 RC… plan. I will update the etherpad today. · Re: the “4-6 weeks of time to run tests”, I was just guessing. Looking at your awesome table, it looks like we’ll have 6 weeks most of the time except in February, where we only get 5 weeks. Comments · I don’t know how TC does version numbers. Someone should find out and make a Story for how we want to change that. Pending · Regarding the N and N-1 branches, I would think that they would expire at the point they become an N-2 branch. For instance, the stx.08.2018 branch becomes N-2 once stx.02.2019 is created. · Long Term Support is likely going to remain unclear, or at least undecided, for now. We’ll need to get a couple of releases under our belt and lots of test cycles passing before we want to declare anything LTS. brucej From: Hernandez Gonzalez, Fernando Sent: Tuesday, July 3, 2018 3:50 PM To: Cabrales, Ada ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: RFC: StarlingX release cadence proposal Hi Bruce, As you know I am assigned to “Design and document the release” Starlingx task, as part of that task and since I am more a visual guy (Please feel free to use the excel I attached) I created a Schedule that I might be incorporated in our documentation in the future. I reviewed the proposal, looks good to me, but I still have some doubts/comments/pending? · In the “Starlingx Planning etherpad” you talked about Beta1/2 and RC1,2,3… Are they aligned with August Quarterly Cadence or this is just because of the ramp up of the project? · Just curious for quarterly release, why are you saying “This gives us 4-6 weeks of time to run test” and not more or less weeks? Comments · Regarding “version number change from what the underlying TC product uses today” in my previous BIOS project there was a file created when the SPI Firmware was compiled, the script was fed for the version of main components. This help us a lot when some bug appears and we had to do troubleshooting. Maybe it is a way/option to populate a script with underlying TC and CentOS product versions. Pending · How long N and N-1 long live branches are going to keep alive? And same question for short-live. · LTS is still a topic unclear. Do you have more about it? [cid:image002.jpg at 01D4178C.55BFF210] Fernando Hernandez Gonzalez Software Engineer Avenida del Bosque #1001 Col, El Bajío Zapopan, Jalisco MX, 45019 ____________________________________ Office: +52.33.16.45.01.34 inet 86450134 From: Cabrales, Ada [mailto:ada.cabrales at intel.com] Sent: Thursday, June 28, 2018 8:02 PM To: Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] RFC: StarlingX release cadence proposal I like this proposal. I think it would give us periodic, stable versions to work on/with. Also, it gives us the opportunity to plan what would we have on each monthly | quarterly release, considering feature’s priority. So, if we decide to follow this schema, let’s define what we want to have ready for the Summit in November (the September release, as pointed by Bruce previously) and plan around that. Ada -- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, June 27, 2018 6:48 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] RFC: StarlingX release cadence proposal At our weekly call today we discussed release plans and release cadence. It was a long discussion and a good one. In the end we agreed that we’d like to follow the “bus stop” model of time based releases, and the Ubuntu model of an annual major (LTS) release with quarterly updates. Note that we did not suggest or agree that our currently planned “Release 2” should be a LTS. We all agreed that would be premature. We will declare an LTS at some point in the future. After separate discussions with David, Dean and Ada, rather than just proposing that “our current November release is the first quarterly release”, I have a modified proposal to make for how we should handle releases. This is an RFC looking for feedback, questions and comments. Monthly milestone builds -------------------------------- Each month in the 2nd week of the month we will pull a branch. Dean and I suggest using year/month as the branch names, for simplicity. For example, we propose that the branch name for a July 2018 milestone build would be “stx.2018.07”. The version number of that build would be “stx.2018.07.0x”, where “0x” is a patch number. Yes, that’s a change to how version numbers are handled. See below. The purpose of the monthly build is to 1) provide a stable build for long running test cycles 2) provide a “latest known to be good” build for users and partners, and 3) feed into the quarterly release. Fixes for show stopping bugs found in monthly build testing should be done on master and cherry-picked to the branch, increasing the patch number with each one. Quarterly release -------------------- Each quarter’s quarterly release will be the monthly milestone build from the 2nd month in the quarter. This gives us 4-6 weeks of time to run test cycles and fix bugs for the release. For each quarterly release, the code freeze for that release is the 2nd week in the 2nd month in the quarter. Branch handling -------------- Branches from the 1st and 3rd month in a quarter can be short-lived. Branches for the 2nd month’s (quarterly) build will live longer and I would suggest at any given time we keep the N and N-1 quarterly release branches open for bug fixes. If/when we declare a LTS release, that branch would of course live much longer. Why? ----- Why do we release a build from the 2nd week of the 2nd month? In part because that schedule misses the major holiday weeks. No one likes to do releases over the summer or winter holidays. Impact ------- The planning for release content for what we are currently calling “Release 2” will need to change. If this proposal is accepted, we won’t have a “release 2” anymore, just a “release stx.2018.08.x” released in September and “release stx 2018.11.x” released in December. This changes the content we’d have in the release for the November summit (which would be the September release) but anyone there looking for the bleeding edge could pick up the RC for the December build, which would be in testing at that time. Branching also means that key bug fixes would need to be cherry picked to the older branches. New feature code should always go to master only. Version numbers ---------------- This proposal also includes a version number change from what the underlying TC product uses today. I think it’s inevitable that the StarlingX project has separate / different version numbers from TC, but I don’t know what it means to the system to actually get there, or what headaches it might cause. We should key that up as a separate discussion. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 81369 bytes Desc: image001.jpg URL: From bruce.e.jones at intel.com Tue Jul 10 05:08:46 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 10 Jul 2018 05:08:46 +0000 Subject: [Starlingx-discuss] RFC: StarlingX release cadence proposal In-Reply-To: <68F20408-BB2B-4AA6-9CB7-9E6BF5C2FD5F@intel.com> References: <68F20408-BB2B-4AA6-9CB7-9E6BF5C2FD5F@intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB55F0D1@fmsmsx117.amr.corp.intel.com> Erich, I completely agree. Fernando, let’s work together on it. brucej From: Cordoba Malibran, Erich Sent: Monday, July 9, 2018 9:31 PM To: Jones, Bruce E ; Hernandez Gonzalez, Fernando ; Cabrales, Ada ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] RFC: StarlingX release cadence proposal Hi, Not sure if this is out of the scope of this proposal but now that we have defined a release cadence, which would be the best dates within the quarterly release to define the items/feature to be released (a release planning)? Also we would need to define a bug scrub or some related meeting to decide which bugs will be fixed in the release. -Erich From: "Jones, Bruce E" > Date: Monday, July 9, 2018 at 6:29 PM To: "Hernandez Gonzalez, Fernando" >, "Cabrales, Ada" >, "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] RFC: StarlingX release cadence proposal Fernando, you are my new hero. This visual of the schedule is awesome and super helpful. Thank you! Meanwhile, having heard no objections to the proposal, I’m going to assume that we all agree and that this is our new release plan. I will update my documents accordingly. To address your points below: · This plan completely replaces the Beta1/2 RC… plan. I will update the etherpad today. · Re: the “4-6 weeks of time to run tests”, I was just guessing. Looking at your awesome table, it looks like we’ll have 6 weeks most of the time except in February, where we only get 5 weeks. Comments · I don’t know how TC does version numbers. Someone should find out and make a Story for how we want to change that. Pending · Regarding the N and N-1 branches, I would think that they would expire at the point they become an N-2 branch. For instance, the stx.08.2018 branch becomes N-2 once stx.02.2019 is created. · Long Term Support is likely going to remain unclear, or at least undecided, for now. We’ll need to get a couple of releases under our belt and lots of test cycles passing before we want to declare anything LTS. brucej From: Hernandez Gonzalez, Fernando Sent: Tuesday, July 3, 2018 3:50 PM To: Cabrales, Ada >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: RE: RFC: StarlingX release cadence proposal Hi Bruce, As you know I am assigned to “Design and document the release” Starlingx task, as part of that task and since I am more a visual guy (Please feel free to use the excel I attached) I created a Schedule that I might be incorporated in our documentation in the future. I reviewed the proposal, looks good to me, but I still have some doubts/comments/pending? · In the “Starlingx Planning etherpad” you talked about Beta1/2 and RC1,2,3… Are they aligned with August Quarterly Cadence or this is just because of the ramp up of the project? · Just curious for quarterly release, why are you saying “This gives us 4-6 weeks of time to run test” and not more or less weeks? Comments · Regarding “version number change from what the underlying TC product uses today” in my previous BIOS project there was a file created when the SPI Firmware was compiled, the script was fed for the version of main components. This help us a lot when some bug appears and we had to do troubleshooting. Maybe it is a way/option to populate a script with underlying TC and CentOS product versions. Pending · How long N and N-1 long live branches are going to keep alive? And same question for short-live. · LTS is still a topic unclear. Do you have more about it? [cid:image002.jpg at 01D4178C.55BFF210] Fernando Hernandez Gonzalez Software Engineer Avenida del Bosque #1001 Col, El Bajío Zapopan, Jalisco MX, 45019 ____________________________________ Office: +52.33.16.45.01.34 inet 86450134 From: Cabrales, Ada [mailto:ada.cabrales at intel.com] Sent: Thursday, June 28, 2018 8:02 PM To: Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] RFC: StarlingX release cadence proposal I like this proposal. I think it would give us periodic, stable versions to work on/with. Also, it gives us the opportunity to plan what would we have on each monthly | quarterly release, considering feature’s priority. So, if we decide to follow this schema, let’s define what we want to have ready for the Summit in November (the September release, as pointed by Bruce previously) and plan around that. Ada -- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Wednesday, June 27, 2018 6:48 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] RFC: StarlingX release cadence proposal At our weekly call today we discussed release plans and release cadence. It was a long discussion and a good one. In the end we agreed that we’d like to follow the “bus stop” model of time based releases, and the Ubuntu model of an annual major (LTS) release with quarterly updates. Note that we did not suggest or agree that our currently planned “Release 2” should be a LTS. We all agreed that would be premature. We will declare an LTS at some point in the future. After separate discussions with David, Dean and Ada, rather than just proposing that “our current November release is the first quarterly release”, I have a modified proposal to make for how we should handle releases. This is an RFC looking for feedback, questions and comments. Monthly milestone builds -------------------------------- Each month in the 2nd week of the month we will pull a branch. Dean and I suggest using year/month as the branch names, for simplicity. For example, we propose that the branch name for a July 2018 milestone build would be “stx.2018.07”. The version number of that build would be “stx.2018.07.0x”, where “0x” is a patch number. Yes, that’s a change to how version numbers are handled. See below. The purpose of the monthly build is to 1) provide a stable build for long running test cycles 2) provide a “latest known to be good” build for users and partners, and 3) feed into the quarterly release. Fixes for show stopping bugs found in monthly build testing should be done on master and cherry-picked to the branch, increasing the patch number with each one. Quarterly release -------------------- Each quarter’s quarterly release will be the monthly milestone build from the 2nd month in the quarter. This gives us 4-6 weeks of time to run test cycles and fix bugs for the release. For each quarterly release, the code freeze for that release is the 2nd week in the 2nd month in the quarter. Branch handling -------------- Branches from the 1st and 3rd month in a quarter can be short-lived. Branches for the 2nd month’s (quarterly) build will live longer and I would suggest at any given time we keep the N and N-1 quarterly release branches open for bug fixes. If/when we declare a LTS release, that branch would of course live much longer. Why? ----- Why do we release a build from the 2nd week of the 2nd month? In part because that schedule misses the major holiday weeks. No one likes to do releases over the summer or winter holidays. Impact ------- The planning for release content for what we are currently calling “Release 2” will need to change. If this proposal is accepted, we won’t have a “release 2” anymore, just a “release stx.2018.08.x” released in September and “release stx 2018.11.x” released in December. This changes the content we’d have in the release for the November summit (which would be the September release) but anyone there looking for the bleeding edge could pick up the RC for the December build, which would be in testing at that time. Branching also means that key bug fixes would need to be cherry picked to the older branches. New feature code should always go to master only. Version numbers ---------------- This proposal also includes a version number change from what the underlying TC product uses today. I think it’s inevitable that the StarlingX project has separate / different version numbers from TC, but I don’t know what it means to the system to actually get there, or what headaches it might cause. We should key that up as a separate discussion. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 81369 bytes Desc: image001.jpg URL: From Brent.Rowsell at windriver.com Tue Jul 10 12:58:22 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Tue, 10 Jul 2018 12:58:22 +0000 Subject: [Starlingx-discuss] FIrst release branch In-Reply-To: <9A85D2917C58154C960D95352B22818BAB55F0A2@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB55F0A2@fmsmsx117.amr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0CDFD6@ALA-MBD.corp.ad.wrs.com> Apologies for the late response. I somehow missed this thread when I returned from vacation. With all the restructuring/churn that is currently going on branching at this time does not seem like the right thing to do. We should finish some of those activities first before branching. Even for a quarterly release why do we need to have a monthly branch. Shouldn't we just work on master and branch at some point before the release. Brent From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Tuesday, July 10, 2018 1:03 AM To: Cardona Ruiz, Erick Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] FIrst release branch As previously discussed on this list, we have agreed to move to a quarterly release model with monthly branches. I proposed pulling monthly branches the 2nd week of each month. And now it's the 2nd week of the month. It's time to pull our first monthly branch. It should be called "stx.2018.07" and it should not be created until the latest kernel updates are complete. Unless those updates aren't in by Thursday, because we're going to pull the branch this week regardless. Erick, can you write a script that creates a branch, and (once the kernel changes are in or Friday happens), run it and pull the branch and kick off a build? The story and tasks are in https://storyboard.openstack.org/#!/story/2002923. Which I can't assign to you. Do you have an OpenStack ID? Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From claire at openstack.org Tue Jul 10 13:45:35 2018 From: claire at openstack.org (claire at openstack.org) Date: Tue, 10 Jul 2018 13:45:35 +0000 Subject: [Starlingx-discuss] Invitation: Weekly StarlingX mtg 7:00am PDT (1400 UTC) @ Weekly from 9am to 10am on Wednesday from Wed Jul 11 to Wed Nov 7 (CDT) (starlingx-discuss@lists.starlingx.io) Message-ID: <0000000000003940bc0570a55827@google.com> You have been invited to the following event. Title: Weekly StarlingX mtg 7:00am PDT (1400 UTC) Agenda & Notes: https://wiki.openstack.org/wiki/StarlingX#Meetings When: Weekly from 9am to 10am on Wednesday from Wed Jul 11 to Wed Nov 7 Central Time Where: https://zoom.us/j/342730236 Calendar: starlingx-discuss at lists.starlingx.io Who: * claire at openstack.org - organizer * Ildiko Vancsa * starlingx-discuss at lists.starlingx.io Event details: https://www.google.com/calendar/event?action=VIEW&eid=XzZvb2syYzloNjkxMzBiOWg4Z3A0Y2I5azg4bzM0YjlwNmgxNDJiYTI2b3MzMmc5ZzZoMWs2ZHBuNmsgc3Rhcmxpbmd4LWRpc2N1c3NAbGlzdHMuc3Rhcmxpbmd4Lmlv&tok=MjAjY2xhaXJlQG9wZW5zdGFjay5vcmcyNzEzYTdmZDQ3NjI0OWViZWEyNjA2ZTUzMjA3ZjZhODliOGZkMzAy&ctz=America%2FChicago&hl=en&es=0 Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account starlingx-discuss at lists.starlingx.io because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2131 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 2187 bytes Desc: not available URL: From dtroyer at gmail.com Tue Jul 10 14:41:10 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 10 Jul 2018 09:41:10 -0500 Subject: [Starlingx-discuss] FIrst release branch In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB0CDFD6@ALA-MBD.corp.ad.wrs.com> References: <9A85D2917C58154C960D95352B22818BAB55F0A2@fmsmsx117.amr.corp.intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0CDFD6@ALA-MBD.corp.ad.wrs.com> Message-ID: On Tue, Jul 10, 2018 at 7:58 AM, Rowsell, Brent wrote: > With all the restructuring/churn that is currently going on branching at > this time does not seem like the right thing to do. The primary reason for branching now is to use that to work on the release process and flesh out some of our policy, such as release branch backports, etc. It also provides a common point-in-time to reference the code for longer-term testing. There is a good bit of process for us to work out here[0] and I think we're going to learn a lot by the time we want to cut a release to show the world in Berlin. > We should finish some of those activities first before branching. I agree that branching now may limit the ability to backport (cleanly) commits from master into the branch but I don't think this is a concern for the purposes of getting some experience with a brand-new release process. > Even for a quarterly release why do we need to have a monthly branch. > Shouldn’t we just work on master and branch at some point before the > release. I don't expect the intermediate monthly branches to be around for a long time and if they turn out to not be useful we can always re-evaluate and stop doing it later. dt [0] In addition we actually need to write down our definition of a 'release'. We know it is source-only, I suspect it may not have any generated artifacts besides branches in git repos, at some point though it will include published documentation. I am making an assumption here that all of the "flock" repos are considered a single unit. Some of the sub-projects do appear to have versions and at some point we may want to start to treat those as distinct projects using a release model similar to OpenStack's cycle-with-intermediary [1] model (our default is closer to the cycle-with-milestone [2] model). [1] https://releases.openstack.org/reference/release_models.html#cycle-with-intermediary [2] https://releases.openstack.org/reference/release_models.html#cycle-with-milestones -- Dean Troyer dtroyer at gmail.com From erich.cordoba.malibran at intel.com Tue Jul 10 15:21:57 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 10 Jul 2018 15:21:57 +0000 Subject: [Starlingx-discuss] tpm-kmod patches cannot be applied with upstream code In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB0CDF3F@ALA-MBD.corp.ad.wrs.com> References: <2588653EBDFFA34B982FAF00F1B4844EBB0CDF3F@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Brent, This is not upversioning, we are trying to use the same version, according to the tpm-kmod-668a8270.txt file in cgcs-dl repository the SHA used is fd5c78694 from http://git.infradead.org/users/jjs/linux-tpmdd.git/ but the code there is not the same as the content of tpm-kmod-668a8270.tar.gz in cgcs-dl. That's why the question about where to find the correct code for tpm-kmod. -Erich On 7/10/18, 6:20 AM, "Rowsell, Brent" wrote: Erich, Why are we upversioning this now ? Brent -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Tuesday, July 10, 2018 12:52 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] tpm-kmod patches cannot be applied with upstream code Hi all, I'm having problems to apply the patches for tpm-kmod with the code from upstream. The following patch to the tpm_crb.c file is failing: 0001-disable-arm64-acpi-command.patch @@ -572,11 +572,12 @@ static int crb_acpi_add(struct acpi_devi ACPI_TPM2_COMMAND_BUFFER_WITH_SMC); return -EINVAL; } - crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, + struct tpm2_crb_smc *crb_smc = ACPI_ADD_PTR(struct + tpm2_crb_smc, buf, ACPI_TPM2_START_METHOD_PARAMETER_OFFSET); priv->smc_func_id = crb_smc->smc_func_id; priv->flags |= CRB_FL_CRB_SMC_START; } +#endif This patch expects to find crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, ACPI_TPM2_START_METHOD_PARAMETER_OFFSET); However, in the upstream code this line is : crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, sizeof(*buf)); I had reviewed all kernel versions and in none of them ACPI_TPM2_START_METHOD_PARAMETER_OFFSET is used. In the old tmp-kmod tarball (the one in cgcs-dl repository) the name of the tarball references to the SHA fd5c78694f3, however that one doesn't have the specified line[0]. Does anyone can help us to find where this upstream code is? Thanks. [0] http://git.infradead.org/users/jjs/linux-tpmdd.git/blob/fd5c78694f3:/drivers/char/tpm/tpm_crb.c#l575 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Tue Jul 10 16:59:20 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 10 Jul 2018 16:59:20 +0000 Subject: [Starlingx-discuss] [stx-tools] New Kernel Version In-Reply-To: <9700A18779F35F49AF027300A49E7C765533765F@SHSMSX101.ccr.corp.intel.com> References: <839B019D-3E5A-48ED-A2E5-3B49ABDF40B4@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0C939C@ALA-MBD.corp.ad.wrs.com> <4BF83FBF-6E76-41A4-8E61-360D252C7FCF@intel.com> <98D9C69F-A421-4149-BC69-EFE07FB67EE0@intel.com> <25398361-E529-4DF7-BD02-1F994B9E6511@windriver.com> <56CE6087-AF0A-48B7-BF11-DEC1156197C6@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0CB692@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C76553375DF@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765533765F@SHSMSX101.ccr.corp.intel.com> Message-ID: <836ECC37-2443-427F-92D1-61CC96EA14EE@intel.com> As upgrading kernel will be a frequent task, I would like to follow on this question > What testing has been done with 862.6.3 ? I your experience, what would be the best test scenario for a kernel upgrade? Thanks -Erich On 7/9/18, 9:41 PM, "Lin, Shuicheng" wrote: Hi all, Here is the review link for kernel update to 862.6.3. https://review.openstack.org/#/c/580308/ https://review.openstack.org/#/c/580897/ Best Regards Shuicheng -----Original Message----- From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, July 10, 2018 10:20 AM To: Rowsell, Brent ; Hu, Yong ; Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Hi Brent, We have gone through basic deploy test in both bare metal and virtual machine case, and doing sanity test now. We also try to verify the updated driver package with the corresponding HW. Best Regards Shuicheng -----Original Message----- From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Monday, July 9, 2018 7:06 PM To: Hu, Yong ; Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version What testing has been done with 862.6.3 ? Brent -----Original Message----- From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Saturday, July 7, 2018 9:17 PM To: Young, Ken ; Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version On top of these patches, does anyone has concerns to upgrade kernel to the latest 862.6.3?? BTW, from security perspective, CVE-2018-8897 was updated on 862.3.2 and CVE-2018-3665 was on 862.3.3. ====================================================== POP SS (CVE-2018-8897) – Done on May 8 [Software Only Fix] CentOS6.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022827.html 2. Speculative Store Bypass Disable (SSBD) (CVE-2018-3639) – Done on May 21 [Software+Microcode Fix] CentOS6.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022835.html CentOS7.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022843.html kernel-3.10.0-862.3.2.el7 3. Lazy FP State Restore (CVE-2018-3665) – Done on June 13 [Software only Fix] - CentOS7.X: https://lists.centos.org/pipermail/centos-announce/2018-June/022923.html kernel-3.10.0-862.3.3.el7 ======================================================= From: "Young, Ken" Date: Friday, 6 July 2018 at 11:58 PM To: "Hu, Yong" , "Rowsell, Brent" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version The reviews for the updated kernel are here: https://review.openstack.org/#/c/580688/ https://review.openstack.org/580689 https://review.openstack.org/580690 https://review.openstack.org/580692 /KenY From: Ken Young Date: Friday, July 6, 2018 at 9:42 AM To: YONG HU , "Rowsell, Brent" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version See inline. From: YONG HU Date: Thursday, July 5, 2018 at 10:18 PM To: "Rowsell, Brent" , Ken Young , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Hi Ken, >>> we have a kernel update to 862.3.2 >>> We will work to get our updated kernel in ASAP Did you mean WRS has already been working on upgrade to 862.3.2? Yes. We had already migrated to this kernel to enable our kubernetes efforts. The kernel contained capabilities we needed. Could you please post the activities and progress here in this mailing list, so that we all are aware of it? We are planning to put the 862.3.2 into the openstack repos today. Regards, Yong From: "Hu, Yong" Date: Friday, 6 July 2018 at 9:14 AM To: "Rowsell, Brent" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Makes sense! Do we intend/agree to apply this rule on all new features or big changes (though practically how we gate the granularity of changes?)? Regards, Yong From: "Rowsell, Brent" Date: Friday, 6 July 2018 at 8:58 AM To: "Hu, Yong" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: RE: [Starlingx-discuss] [stx-tools] New Kernel Version Going forward, I would recommend pending upgrades be posted to the mailing list before the reviews are actually submitted. Brent From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Thursday, July 5, 2018 8:56 PM To: Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Hi Ken, We might need a sync-up on this kernel upgrade topic. Actually, moving forward, I would suggest, if there are any big changes to come, we both sides need to inform each other in advance, to avoid duplications or conflicts. Regards, Yong From: "Young, Ken" Date: Friday, 6 July 2018 at 12:21 AM To: "mailto:starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [stx-tools] New Kernel Version I discovered 2 new reviews this morning which are security related this morning: https://review.openstack.org/#/c/580287/ https://review.openstack.org/#/c/580308/ These reviews propose to merge the latest CentOS kernel 862.6.3 to address the latest Spectre / Meltdown CVEs. Before this is completed, we have a kernel update to 862.3.2 we would like to merge which includes module updates to enable containers which we would like to get in first. Otherwise, this will generate a significant amount of rework for these submissions. The easiest path is to follow the kernels in order. We will work to get our updated kernel in ASAP. Thank you in advance. Regards, Ken Y _______________________________________________ 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 Jason.McKenna at windriver.com Tue Jul 10 19:21:41 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Tue, 10 Jul 2018 19:21:41 +0000 Subject: [Starlingx-discuss] tpm-kmod patches cannot be applied with upstream code In-Reply-To: References: <2588653EBDFFA34B982FAF00F1B4844EBB0CDF3F@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Eric, I dug into the origin of the our version of tpm-kmod-668a8270.tar.gz, and it looks like our tarball was generated from an incomplete view of the git tree, and therefore the patches were generated against the incomplete code. Specifically, commit 3b395d67 appears to be missing in our tarball (this is the commit immediately before the fd5c78694 commit the .txt file claims the tarball represents). Our tarball is does also include the e6aef069b commit (the immediately after fd5c78694). $ git log ... future e6aef069b <--- rev the tarball actually is (less 3b39d67 commit) fd5c78694 <--- rev the .txt claims to be 3b395d67 <--- our tarball missing this commit past ... So to recreate the tarball, you'd checkout e6aef069b, revert 3b395d67, and tar up the drivers/char/tpm directory. It might be worthwhile creating a story to regenerate the patches against a proper snapshot of the git. -Jason -----Original Message----- From: Cordoba Malibran, Erich Sent: July 10, 2018 11:22 AM To: Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] tpm-kmod patches cannot be applied with upstream code Hi Brent, This is not upversioning, we are trying to use the same version, according to the tpm-kmod-668a8270.txt file in cgcs-dl repository the SHA used is fd5c78694 from http://git.infradead.org/users/jjs/linux-tpmdd.git/ but the code there is not the same as the content of tpm-kmod-668a8270.tar.gz in cgcs-dl. That's why the question about where to find the correct code for tpm-kmod. -Erich On 7/10/18, 6:20 AM, "Rowsell, Brent" wrote: Erich, Why are we upversioning this now ? Brent -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Tuesday, July 10, 2018 12:52 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] tpm-kmod patches cannot be applied with upstream code Hi all, I'm having problems to apply the patches for tpm-kmod with the code from upstream. The following patch to the tpm_crb.c file is failing: 0001-disable-arm64-acpi-command.patch @@ -572,11 +572,12 @@ static int crb_acpi_add(struct acpi_devi ACPI_TPM2_COMMAND_BUFFER_WITH_SMC); return -EINVAL; } - crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, + struct tpm2_crb_smc *crb_smc = ACPI_ADD_PTR(struct + tpm2_crb_smc, buf, ACPI_TPM2_START_METHOD_PARAMETER_OFFSET); priv->smc_func_id = crb_smc->smc_func_id; priv->flags |= CRB_FL_CRB_SMC_START; } +#endif This patch expects to find crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, ACPI_TPM2_START_METHOD_PARAMETER_OFFSET); However, in the upstream code this line is : crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, sizeof(*buf)); I had reviewed all kernel versions and in none of them ACPI_TPM2_START_METHOD_PARAMETER_OFFSET is used. In the old tmp-kmod tarball (the one in cgcs-dl repository) the name of the tarball references to the SHA fd5c78694f3, however that one doesn't have the specified line[0]. Does anyone can help us to find where this upstream code is? Thanks. [0] http://git.infradead.org/users/jjs/linux-tpmdd.git/blob/fd5c78694f3:/drivers/char/tpm/tpm_crb.c#l575 _______________________________________________ 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 erich.cordoba.malibran at intel.com Tue Jul 10 20:21:26 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 10 Jul 2018 20:21:26 +0000 Subject: [Starlingx-discuss] tpm-kmod patches cannot be applied with upstream code In-Reply-To: References: <2588653EBDFFA34B982FAF00F1B4844EBB0CDF3F@ALA-MBD.corp.ad.wrs.com> Message-ID: Thanks Jason for the explanation, now makes sense. I can create the story, what do you think would be the proper snapshot to recreate the patches? fd5c78694 or e6aef069b? -Erich On 7/10/18, 2:21 PM, "McKenna, Jason" wrote: Hi Eric, I dug into the origin of the our version of tpm-kmod-668a8270.tar.gz, and it looks like our tarball was generated from an incomplete view of the git tree, and therefore the patches were generated against the incomplete code. Specifically, commit 3b395d67 appears to be missing in our tarball (this is the commit immediately before the fd5c78694 commit the .txt file claims the tarball represents). Our tarball is does also include the e6aef069b commit (the immediately after fd5c78694). $ git log ... future e6aef069b <--- rev the tarball actually is (less 3b39d67 commit) fd5c78694 <--- rev the .txt claims to be 3b395d67 <--- our tarball missing this commit past ... So to recreate the tarball, you'd checkout e6aef069b, revert 3b395d67, and tar up the drivers/char/tpm directory. It might be worthwhile creating a story to regenerate the patches against a proper snapshot of the git. -Jason -----Original Message----- From: Cordoba Malibran, Erich Sent: July 10, 2018 11:22 AM To: Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] tpm-kmod patches cannot be applied with upstream code Hi Brent, This is not upversioning, we are trying to use the same version, according to the tpm-kmod-668a8270.txt file in cgcs-dl repository the SHA used is fd5c78694 from http://git.infradead.org/users/jjs/linux-tpmdd.git/ but the code there is not the same as the content of tpm-kmod-668a8270.tar.gz in cgcs-dl. That's why the question about where to find the correct code for tpm-kmod. -Erich On 7/10/18, 6:20 AM, "Rowsell, Brent" wrote: Erich, Why are we upversioning this now ? Brent -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Tuesday, July 10, 2018 12:52 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] tpm-kmod patches cannot be applied with upstream code Hi all, I'm having problems to apply the patches for tpm-kmod with the code from upstream. The following patch to the tpm_crb.c file is failing: 0001-disable-arm64-acpi-command.patch @@ -572,11 +572,12 @@ static int crb_acpi_add(struct acpi_devi ACPI_TPM2_COMMAND_BUFFER_WITH_SMC); return -EINVAL; } - crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, + struct tpm2_crb_smc *crb_smc = ACPI_ADD_PTR(struct + tpm2_crb_smc, buf, ACPI_TPM2_START_METHOD_PARAMETER_OFFSET); priv->smc_func_id = crb_smc->smc_func_id; priv->flags |= CRB_FL_CRB_SMC_START; } +#endif This patch expects to find crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, ACPI_TPM2_START_METHOD_PARAMETER_OFFSET); However, in the upstream code this line is : crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, sizeof(*buf)); I had reviewed all kernel versions and in none of them ACPI_TPM2_START_METHOD_PARAMETER_OFFSET is used. In the old tmp-kmod tarball (the one in cgcs-dl repository) the name of the tarball references to the SHA fd5c78694f3, however that one doesn't have the specified line[0]. Does anyone can help us to find where this upstream code is? Thanks. [0] http://git.infradead.org/users/jjs/linux-tpmdd.git/blob/fd5c78694f3:/drivers/char/tpm/tpm_crb.c#l575 _______________________________________________ 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 Ghada.Khalil at windriver.com Tue Jul 10 22:21:38 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 10 Jul 2018 22:21:38 +0000 Subject: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches Message-ID: <151EE31B9FCCA54397A757BC674650F0BA3160B7@ALA-MBD.corp.ad.wrs.com> Hello, With the increased number of active stories in StartlingX, I'd like to propose that we consistently use a set of prefixes to make it easier to search and find work items. Suggested Prefixes: [Bug] A problem which impairs or prevents the functionality of StarlingX [Enhancement] An improvement or enhancement to the functionality of StartingX Typically smaller scope items [Feature] A new feature/functionality to be added to StarlingX Ideally, the scope should fit within a release time-frame (ex: 3-6 months) [Build] Build tools, environment, repo organization, etc [Process] Process and project related work items [Doc] Documentation related work items [Upstreaming] Work items that need to be pushed in the core openstack projects ** Others can be added as long as we agree on a manageable set. Sample Queries: - Active Features https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Feature - Active Bugs https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Bug I would also like to explore using worklists for larger project initiatives which would potentially span multiple features/releases. Example: [Initiative] Containerized Openstack Example: [Initiative] StarlingX Project Re-structuring Does anyone know how to scope worklists and boards to the StarlingX project group only? Any feedback is welcome. Regards, Ghada Ghada Khalil, Manager, Titanium Cloud, Wind River direct 613.270.2273  skype ghada.khalil.ottawa 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 From Ghada.Khalil at windriver.com Tue Jul 10 22:25:23 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 10 Jul 2018 22:25:23 +0000 Subject: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches Message-ID: <151EE31B9FCCA54397A757BC674650F0BA3160CF@ALA-MBD.corp.ad.wrs.com> Re-sending due to message formatting issues. My apologies! -----Original Message----- From: Khalil, Ghada Sent: Tuesday, July 10, 2018 6:22 PM To: starlingx-discuss at lists.starlingx.io Subject: Proposal to use prefixes in Story Board to ease searches Hello, With the increased number of active stories in StartlingX, I'd like to propose that we consistently use a set of prefixes to make it easier to search and find work items. Suggested Prefixes: [Bug] A problem which impairs or prevents the functionality of StarlingX [Enhancement] An improvement or enhancement to the functionality of StartingX Typically smaller scope items [Feature] A new feature/functionality to be added to StarlingX Ideally, the scope should fit within a release time-frame (ex: 3-6 months) [Build] Build tools, environment, repo organization, etc [Process] Process and project related work items [Doc] Documentation related work items [Upstreaming] Work items that need to be pushed in the core openstack projects ** Others can be added as long as we agree on a manageable set. Sample Queries: - Active Features https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Feature - Active Bugs https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Bug I would also like to explore using worklists for larger project initiatives which would potentially span multiple features/releases. Example: [Initiative] Containerized Openstack Example: [Initiative] StarlingX Project Re-structuring Does anyone know how to scope worklists and boards to the StarlingX project group only? Any feedback is welcome. Regards, Ghada Ghada Khalil, Manager, Titanium Cloud, Wind River direct 613.270.2273  skype ghada.khalil.ottawa 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 From erich.cordoba.malibran at intel.com Tue Jul 10 23:03:12 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 10 Jul 2018 23:03:12 +0000 Subject: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA3160CF@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA3160CF@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi, Storyboard also supports tags, that could be another way to track the stories/issues. Also I would add [help] to the list, this is considering that someone can just create a story to ask a question (similar to the model in Github, where anyone can create issues). -Erich On 7/10/18, 5:25 PM, "Khalil, Ghada" wrote: Re-sending due to message formatting issues. My apologies! -----Original Message----- From: Khalil, Ghada Sent: Tuesday, July 10, 2018 6:22 PM To: starlingx-discuss at lists.starlingx.io Subject: Proposal to use prefixes in Story Board to ease searches Hello, With the increased number of active stories in StartlingX, I'd like to propose that we consistently use a set of prefixes to make it easier to search and find work items. Suggested Prefixes: [Bug] A problem which impairs or prevents the functionality of StarlingX [Enhancement] An improvement or enhancement to the functionality of StartingX Typically smaller scope items [Feature] A new feature/functionality to be added to StarlingX Ideally, the scope should fit within a release time-frame (ex: 3-6 months) [Build] Build tools, environment, repo organization, etc [Process] Process and project related work items [Doc] Documentation related work items [Upstreaming] Work items that need to be pushed in the core openstack projects ** Others can be added as long as we agree on a manageable set. Sample Queries: - Active Features https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Feature - Active Bugs https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Bug I would also like to explore using worklists for larger project initiatives which would potentially span multiple features/releases. Example: [Initiative] Containerized Openstack Example: [Initiative] StarlingX Project Re-structuring Does anyone know how to scope worklists and boards to the StarlingX project group only? Any feedback is welcome. Regards, Ghada Ghada Khalil, Manager, Titanium Cloud, Wind River direct 613.270.2273 skype ghada.khalil.ottawa 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Wed Jul 11 00:06:04 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 11 Jul 2018 00:06:04 +0000 Subject: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0BA3160CF@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB55FA42@fmsmsx117.amr.corp.intel.com> This is a good discussion. If someone can document the Storyboard query interface or point me at the documents, that would be super helpful. Re: worklists, I've tried using them and found that you have to explicitly authorize users to make changes to them. That's not something I want to do a lot of. I'm hoping there's a better way. The nice folks from the Foundation have offered to give us some Storyboard training, so perhaps we should hold off on making any decisions until then. brucej -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Tuesday, July 10, 2018 4:03 PM To: Khalil, Ghada ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches Hi, Storyboard also supports tags, that could be another way to track the stories/issues. Also I would add [help] to the list, this is considering that someone can just create a story to ask a question (similar to the model in Github, where anyone can create issues). -Erich On 7/10/18, 5:25 PM, "Khalil, Ghada" wrote: Re-sending due to message formatting issues. My apologies! -----Original Message----- From: Khalil, Ghada Sent: Tuesday, July 10, 2018 6:22 PM To: starlingx-discuss at lists.starlingx.io Subject: Proposal to use prefixes in Story Board to ease searches Hello, With the increased number of active stories in StartlingX, I'd like to propose that we consistently use a set of prefixes to make it easier to search and find work items. Suggested Prefixes: [Bug] A problem which impairs or prevents the functionality of StarlingX [Enhancement] An improvement or enhancement to the functionality of StartingX Typically smaller scope items [Feature] A new feature/functionality to be added to StarlingX Ideally, the scope should fit within a release time-frame (ex: 3-6 months) [Build] Build tools, environment, repo organization, etc [Process] Process and project related work items [Doc] Documentation related work items [Upstreaming] Work items that need to be pushed in the core openstack projects ** Others can be added as long as we agree on a manageable set. Sample Queries: - Active Features https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Feature - Active Bugs https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Bug I would also like to explore using worklists for larger project initiatives which would potentially span multiple features/releases. Example: [Initiative] Containerized Openstack Example: [Initiative] StarlingX Project Re-structuring Does anyone know how to scope worklists and boards to the StarlingX project group only? Any feedback is welcome. Regards, Ghada Ghada Khalil, Manager, Titanium Cloud, Wind River direct 613.270.2273 skype ghada.khalil.ottawa 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 _______________________________________________ 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 Brent.Rowsell at windriver.com Wed Jul 11 00:11:07 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Wed, 11 Jul 2018 00:11:07 +0000 Subject: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches In-Reply-To: <9A85D2917C58154C960D95352B22818BAB55FA42@fmsmsx117.amr.corp.intel.com> References: <151EE31B9FCCA54397A757BC674650F0BA3160CF@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB55FA42@fmsmsx117.amr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0CF03C@ALA-MBD.corp.ad.wrs.com> I put this on the agenda for tomorrow's project meeting, we can follow-up there on the proposal. Brent -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Tuesday, July 10, 2018 8:06 PM To: Cordoba Malibran, Erich ; Khalil, Ghada ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches This is a good discussion. If someone can document the Storyboard query interface or point me at the documents, that would be super helpful. Re: worklists, I've tried using them and found that you have to explicitly authorize users to make changes to them. That's not something I want to do a lot of. I'm hoping there's a better way. The nice folks from the Foundation have offered to give us some Storyboard training, so perhaps we should hold off on making any decisions until then. brucej -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Tuesday, July 10, 2018 4:03 PM To: Khalil, Ghada ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches Hi, Storyboard also supports tags, that could be another way to track the stories/issues. Also I would add [help] to the list, this is considering that someone can just create a story to ask a question (similar to the model in Github, where anyone can create issues). -Erich On 7/10/18, 5:25 PM, "Khalil, Ghada" wrote: Re-sending due to message formatting issues. My apologies! -----Original Message----- From: Khalil, Ghada Sent: Tuesday, July 10, 2018 6:22 PM To: starlingx-discuss at lists.starlingx.io Subject: Proposal to use prefixes in Story Board to ease searches Hello, With the increased number of active stories in StartlingX, I'd like to propose that we consistently use a set of prefixes to make it easier to search and find work items. Suggested Prefixes: [Bug] A problem which impairs or prevents the functionality of StarlingX [Enhancement] An improvement or enhancement to the functionality of StartingX Typically smaller scope items [Feature] A new feature/functionality to be added to StarlingX Ideally, the scope should fit within a release time-frame (ex: 3-6 months) [Build] Build tools, environment, repo organization, etc [Process] Process and project related work items [Doc] Documentation related work items [Upstreaming] Work items that need to be pushed in the core openstack projects ** Others can be added as long as we agree on a manageable set. Sample Queries: - Active Features https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Feature - Active Bugs https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Bug I would also like to explore using worklists for larger project initiatives which would potentially span multiple features/releases. Example: [Initiative] Containerized Openstack Example: [Initiative] StarlingX Project Re-structuring Does anyone know how to scope worklists and boards to the StarlingX project group only? Any feedback is welcome. Regards, Ghada Ghada Khalil, Manager, Titanium Cloud, Wind River direct 613.270.2273 skype ghada.khalil.ottawa 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 _______________________________________________ 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 zhipengs.liu at intel.com Wed Jul 11 08:14:49 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 11 Jul 2018 08:14:49 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> Hi Abraham, When I followed your guide, there are 3 issues I found. 1) We need change mock.cfg.proto file as below [TisCentos7Distro] name=Tis-Centos-7-Distro enabled=1 baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found. 2) In Download Source Code Repositories step of the guide. cgcs-dl $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads // change to $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/ 3) lighttpd not started by default in build container, and also could not started manually. =============================================================== Raised below 2 stories. 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto 2002938 lighttpd not started by default in build container BRs zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2018年7月5日 11:14 To: Hu, Yong ; Arce Moreno, Abraham ; Scott Little ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Hi Abraham, When I run below step $ docker build -t user:centos-mirror-repository -f Dockerfile . It mentioned Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection It can work after following below steps. =========================================================== Here is a link to the official docker doc for proxy http:https://docs.docker.com/engine/admin/systemd/#http-proxy A quick outline: First, create a systemd drop-in directory for the docker service: mkdir /etc/systemd/system/docker.service.d Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: [Service] Environment="HTTP_PROXY=http://proxy.example.com:80/" If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: Environment="HTTP_PROXY=http://proxy.example.com:80/" Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" Flush changes: $ sudo systemctl daemon-reload Verify that the configuration has been loaded: $ sudo systemctl show --property Environment docker Environment=HTTP_PROXY=http://proxy.example.com:80/ Restart Docker: $ sudo systemctl restart docker -----Original Message----- From: Hu, Yong [mailto:yong.hu at intel.com] Sent: 2018年7月4日 15:15 To: Arce Moreno, Abraham ; Scott Little ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Hi Abraham, Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" wrote: > > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned. Cool! Thank you! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Jason.McKenna at windriver.com Wed Jul 11 13:33:31 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Wed, 11 Jul 2018 13:33:31 +0000 Subject: [Starlingx-discuss] tpm-kmod patches cannot be applied with upstream code In-Reply-To: References: <2588653EBDFFA34B982FAF00F1B4844EBB0CDF3F@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Erich, e6aef069b is closer to what has been tested, so I'd recommend going with that. -Jason -----Original Message----- From: Cordoba Malibran, Erich Sent: July 10, 2018 4:21 PM To: McKenna, Jason ; Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] tpm-kmod patches cannot be applied with upstream code Thanks Jason for the explanation, now makes sense. I can create the story, what do you think would be the proper snapshot to recreate the patches? fd5c78694 or e6aef069b? -Erich On 7/10/18, 2:21 PM, "McKenna, Jason" wrote: Hi Eric, I dug into the origin of the our version of tpm-kmod-668a8270.tar.gz, and it looks like our tarball was generated from an incomplete view of the git tree, and therefore the patches were generated against the incomplete code. Specifically, commit 3b395d67 appears to be missing in our tarball (this is the commit immediately before the fd5c78694 commit the .txt file claims the tarball represents). Our tarball is does also include the e6aef069b commit (the immediately after fd5c78694). $ git log ... future e6aef069b <--- rev the tarball actually is (less 3b39d67 commit) fd5c78694 <--- rev the .txt claims to be 3b395d67 <--- our tarball missing this commit past ... So to recreate the tarball, you'd checkout e6aef069b, revert 3b395d67, and tar up the drivers/char/tpm directory. It might be worthwhile creating a story to regenerate the patches against a proper snapshot of the git. -Jason -----Original Message----- From: Cordoba Malibran, Erich Sent: July 10, 2018 11:22 AM To: Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] tpm-kmod patches cannot be applied with upstream code Hi Brent, This is not upversioning, we are trying to use the same version, according to the tpm-kmod-668a8270.txt file in cgcs-dl repository the SHA used is fd5c78694 from http://git.infradead.org/users/jjs/linux-tpmdd.git/ but the code there is not the same as the content of tpm-kmod-668a8270.tar.gz in cgcs-dl. That's why the question about where to find the correct code for tpm-kmod. -Erich On 7/10/18, 6:20 AM, "Rowsell, Brent" wrote: Erich, Why are we upversioning this now ? Brent -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Tuesday, July 10, 2018 12:52 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] tpm-kmod patches cannot be applied with upstream code Hi all, I'm having problems to apply the patches for tpm-kmod with the code from upstream. The following patch to the tpm_crb.c file is failing: 0001-disable-arm64-acpi-command.patch @@ -572,11 +572,12 @@ static int crb_acpi_add(struct acpi_devi ACPI_TPM2_COMMAND_BUFFER_WITH_SMC); return -EINVAL; } - crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, + struct tpm2_crb_smc *crb_smc = ACPI_ADD_PTR(struct + tpm2_crb_smc, buf, ACPI_TPM2_START_METHOD_PARAMETER_OFFSET); priv->smc_func_id = crb_smc->smc_func_id; priv->flags |= CRB_FL_CRB_SMC_START; } +#endif This patch expects to find crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, ACPI_TPM2_START_METHOD_PARAMETER_OFFSET); However, in the upstream code this line is : crb_smc = ACPI_ADD_PTR(struct tpm2_crb_smc, buf, sizeof(*buf)); I had reviewed all kernel versions and in none of them ACPI_TPM2_START_METHOD_PARAMETER_OFFSET is used. In the old tmp-kmod tarball (the one in cgcs-dl repository) the name of the tarball references to the SHA fd5c78694f3, however that one doesn't have the specified line[0]. Does anyone can help us to find where this upstream code is? Thanks. [0] http://git.infradead.org/users/jjs/linux-tpmdd.git/blob/fd5c78694f3:/drivers/char/tpm/tpm_crb.c#l575 _______________________________________________ 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 Wed Jul 11 13:57:12 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 11 Jul 2018 08:57:12 -0500 Subject: [Starlingx-discuss] Meeting reminder Message-ID: <7B04176B-CACE-4BF0-B593-FAE68125F07A@gmail.com> Hi, It is a friendly reminder that we are having the first weekly call for StarlingX in a few minutes at 1400 UTC. Details are here: https://wiki.openstack.org/wiki/StarlingX#Meetings See you on the call soon! Thanks and Best Regards, Ildikó From scott.little at windriver.com Wed Jul 11 14:09:16 2018 From: scott.little at windriver.com (Scott Little) Date: Wed, 11 Jul 2018 10:09:16 -0400 Subject: [Starlingx-discuss] Download packages issues Message-ID: The 'bash download_mirror.sh' step seems to be very fragile. e.g. this morning I tried to start fresh and it failed at several points.    ------ using kernel-3.10.0-862.3.2.el7 to search kernel-3.10.0-862.3.2.el7.src.rpm ------    --> run: sudo -E yumdownloader -q -C --source kernel-3.10.0-862.3.2.el7    Looking for kernel-3.10.0-862.3.2.el7.src.rpm    No source RPM found for kernel-3.10.0-862.3.2.el7.x86_64    Nothing to download     ------ using epel-rpm-macros-7-18 to search epel-rpm-macros-7-18.noarch.rpm ------    --> run: sudo -E yumdownloader -q -C epel-rpm-macros-7-18 --archlist=noarch,x86_64    Looking for epel-rpm-macros-7-18.noarch.rpm...    No Match for argument epel-rpm-macros-7-18    Nothing to download and the tarball downloads failed on.    --2018-07-11 13:13:28-- http://git.infradead.org/users/jjs/linux-tpmdd.git/snapshot/fd5c78694f3f1c875e293de7a641ba8a3d60d00d.tar.g    Resolving git.infradead.org (git.infradead.org)... 198.137.202.133, 2607:7c80:54:e::133    Connecting to git.infradead.org (git.infradead.org)|198.137.202.133|:80... connected.    HTTP request sent, awaiting response... 200 OK    Length: unspecified [application/x-gzip]    Saving to: 'fd5c78694f3f1c875e293de7a641ba8a3d60d00d.tar.gz'    2018-07-11 13:14:34 (0.00 B/s) - 'fd5c78694f3f1c875e293de7a641ba8a3d60d00d.tar.gz' saved [0]    tar: This does not look like a tar archive    gzip: stdin: unexpected end of file    tar: Child returned status 1    tar: Error is not recoverable: exiting now    mv: cannot stat 'linux-tpmdd-fd5c786/drivers/char/tpm': No such file or directory    tar: tpm: Cannot stat: No such file or directory    tar: Exiting with failure status due to previous errors    /localdisk    tss2-930.tar.gz    /localdisk/output/stx-r1/CentOS/pike/downloads /localdisk    ./tarball-dl.sh: line 156: git: command not found    ./tarball-dl.sh: line 157: pushd: ibmtpm20tss-tss: No such file or directory    ./tarball-dl.sh: line 158: git: command not found    /localdisk    mv: cannot stat 'ibmtpm20tss-tss': No such file or directory    tar: tss2-930: Cannot stat: No such file or directory    tar: Exiting with failure status due to previous errors    ./tarball-dl.sh: line 165: popd: directory stack empty Is this really going to be our default operating mode?   Never knowing, day by day, when the next package will be dropped from an upstream source.  Is it possible for strarlingX to host it's own mirrors... of at least the needed subset of packages? Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Wed Jul 11 15:28:32 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 11 Jul 2018 10:28:32 -0500 Subject: [Starlingx-discuss] Call to discuss blocking issues Message-ID: Hi All, On the weekly call today we agreed to continue discussions on blocking issues to have faster progress with those items and agreements on how to proceed. The call will take place tomorrow (Thursday, July 12) at 7am PDT / 1400 UTC on Zoom. You can find the call details here: https://wiki.openstack.org/wiki/StarlingX#Discussion_on_Blocking_Issues Please feel free to add agenda items and let me know if you have any questions. Thanks and Best Regards, Ildikó From scott.little at windriver.com Wed Jul 11 15:49:28 2018 From: scott.little at windriver.com (Scott Little) Date: Wed, 11 Jul 2018 11:49:28 -0400 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> Message-ID: <9d889c66-a603-2d12-dd70-c8fb3b3911d0@windriver.com> You shouldn't have to do that. The mock.cfg.proto file is processed by the modify-build-cfg script.  You should see it using sed to substitute "MY_REPO_DIR" with $MY_REPO. There might be weaknesses elsewhere in the build process where it attempts to determine if modify-build-cfg should be re-run.  e.g. I don't think we test for changes to environment variables between runs. Scott On 18-07-11 04:14 AM, Liu, ZhipengS wrote: > Hi Abraham, > > When I followed your guide, there are 3 issues I found. > > 1) We need change mock.cfg.proto file as below > [TisCentos7Distro] > name=Tis-Centos-7-Distro > enabled=1 > baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary > // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found. > > 2) In Download Source Code Repositories step of the guide. > cgcs-dl > $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads > // change to > $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/ > > 3) lighttpd not started by default in build container, and also could not started manually. > > =============================================================== > Raised below 2 stories. > 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto > 2002938 lighttpd not started by default in build container > > > BRs > zhipeng > -----Original Message----- > From: Liu, ZhipengS > Sent: 2018年7月5日 11:14 > To: Hu, Yong ; Arce Moreno, Abraham ; Scott Little ; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Hi Abraham, > > When I run below step > $ docker build -t user:centos-mirror-repository -f Dockerfile . > It mentioned > Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection > > It can work after following below steps. > =========================================================== > Here is a link to the official docker doc for proxy http:https://docs.docker.com/engine/admin/systemd/#http-proxy > A quick outline: > First, create a systemd drop-in directory for the docker service: > mkdir /etc/systemd/system/docker.service.d > Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: > [Service] > Environment="HTTP_PROXY=http://proxy.example.com:80/" > If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: > Environment="HTTP_PROXY=http://proxy.example.com:80/" > Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" > Flush changes: > $ sudo systemctl daemon-reload > Verify that the configuration has been loaded: > $ sudo systemctl show --property Environment docker Environment=HTTP_PROXY=http://proxy.example.com:80/ > Restart Docker: > $ sudo systemctl restart docker > > -----Original Message----- > From: Hu, Yong [mailto:yong.hu at intel.com] > Sent: 2018年7月4日 15:15 > To: Arce Moreno, Abraham ; Scott Little ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Hi Abraham, > Did you run "build-pkgs" or "build-pkgs --serial"? > If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. > 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm > > In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" wrote: > > > > > > It will be great if someone else could take our Developer Guide > > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > > and build the ISO from scratch. > > > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > > tuned. > > Cool! Thank you! > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Wed Jul 11 19:17:52 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Wed, 11 Jul 2018 19:17:52 +0000 Subject: [Starlingx-discuss] Download packages issues In-Reply-To: References: Message-ID: Hi Scott. Indeed, the mirror downloading is very fragile, actually some of the packages can't be downloaded with yumdownloader and direct wget is used. Every time that a package has a new patch a new release version is generated and our mirror is broken. Not sure about hosting our own mirror, although it will ease our process in a short term, the path to be able to run with latest CentOS (or another distro) will be harder to reach. So, this could be a first step going there. Probably, in the future we can remove from the build system the dependency on specific srpm versions (1.2.3-10 <- moving from 10 to 11 shouldn't be an issue) and just update patches when is necessary. Anyway, in this particular problem, kernel-3.10.0-862.3.2.el7.src.rpm was added here[0] but the proper repository wasn't added. The fix for this was already merged[1] The issue about not finding git was fixed last week, so maybe a git pull may help. -Erich [0] https://review.openstack.org/#/c/580689/ [1] https://review.openstack.org/#/c/581471/ From: Scott Little Date: Wednesday, July 11, 2018 at 9:09 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Download packages issues The 'bash download_mirror.sh' step seems to be very fragile.  e.g. this morning I tried to start fresh and it failed at several points.    ------ using kernel-3.10.0-862.3.2.el7 to search kernel-3.10.0-862.3.2.el7.src.rpm ------    --> run: sudo -E yumdownloader -q -C --source kernel-3.10.0-862.3.2.el7    Looking for kernel-3.10.0-862.3.2.el7.src.rpm    No source RPM found for kernel-3.10.0-862.3.2.el7.x86_64    Nothing to download     ------ using epel-rpm-macros-7-18 to search epel-rpm-macros-7-18.noarch.rpm ------    --> run: sudo -E yumdownloader -q -C epel-rpm-macros-7-18 --archlist=noarch,x86_64    Looking for epel-rpm-macros-7-18.noarch.rpm...    No Match for argument epel-rpm-macros-7-18    Nothing to download and the tarball downloads failed on.    --2018-07-11 13:13:28--  http://git.infradead.org/users/jjs/linux-tpmdd.git/snapshot/fd5c78694f3f1c875e293de7a641ba8a3d60d00d.tar.g    Resolving git.infradead.org (git.infradead.org)... 198.137.202.133, 2607:7c80:54:e::133    Connecting to git.infradead.org (git.infradead.org)|198.137.202.133|:80... connected.    HTTP request sent, awaiting response... 200 OK    Length: unspecified [application/x-gzip]    Saving to: 'fd5c78694f3f1c875e293de7a641ba8a3d60d00d.tar.gz'    2018-07-11 13:14:34 (0.00 B/s) - 'fd5c78694f3f1c875e293de7a641ba8a3d60d00d.tar.gz' saved [0]    tar: This does not look like a tar archive    gzip: stdin: unexpected end of file    tar: Child returned status 1    tar: Error is not recoverable: exiting now    mv: cannot stat 'linux-tpmdd-fd5c786/drivers/char/tpm': No such file or directory    tar: tpm: Cannot stat: No such file or directory    tar: Exiting with failure status due to previous errors    /localdisk    tss2-930.tar.gz    /localdisk/output/stx-r1/CentOS/pike/downloads /localdisk    ./tarball-dl.sh: line 156: git: command not found    ./tarball-dl.sh: line 157: pushd: ibmtpm20tss-tss: No such file or directory    ./tarball-dl.sh: line 158: git: command not found    /localdisk    mv: cannot stat 'ibmtpm20tss-tss': No such file or directory    tar: tss2-930: Cannot stat: No such file or directory    tar: Exiting with failure status due to previous errors    ./tarball-dl.sh: line 165: popd: directory stack empty Is this really going to be our default operating mode?   Never knowing, day by day, when the next package will be dropped from an upstream source.  Is it possible for strarlingX to host it's own mirrors... of at least the needed subset of packages? Scott From ildiko.vancsa at gmail.com Wed Jul 11 19:20:45 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 11 Jul 2018 14:20:45 -0500 Subject: [Starlingx-discuss] Berlin Summit CFP Closes in a Week Message-ID: Hi everyone, The CFP deadline for the OpenStack Summit Berlin is less than one week away, so make sure to submit your talks before July 18th at 6:59am UTC (July 17 at 11:59pm PST). Tracks: • CI/CD • Container Infrastructure • Edge Computing • Hands on Workshops • HPC / GPU / AI • Open Source Community • Private & Hybrid Cloud • Public Cloud • Telecom & NFV SUBMIT HERE Community voting, the first step in building the Summit schedule, will open in mid July. Once community voting concludes, a Programming Committee for each Track will build the schedule. Programming Committees are made up of individuals from many different open source communities working in open infrastructure, in addition to people who have participated in the past. Read the full selection process here . Register for the Summit - Early Bird pricing ends August 21 Become a Sponsor Thanks and Best Regards, Ildikó Váncsa Ecosystem Technical Lead, OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Wed Jul 11 19:46:48 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Wed, 11 Jul 2018 19:46:48 +0000 Subject: [Starlingx-discuss] Download packages issues In-Reply-To: References: Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0D088A@ALA-MBD.corp.ad.wrs.com> Comments inline -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Wednesday, July 11, 2018 3:18 PM To: Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Download packages issues Hi Scott. Indeed, the mirror downloading is very fragile, actually some of the packages can't be downloaded with yumdownloader and direct wget is used. Every time that a package has a new patch a new release version is generated and our mirror is broken. Not sure about hosting our own mirror, although it will ease our process in a short term, the path to be able to run with latest CentOS (or another distro) will be harder to reach. So, this could be a first step going there. Probably, in the future we can remove from the build system the dependency on specific srpm versions (1.2.3-10 <- moving from 10 to 11 shouldn't be an issue) and just update patches when is necessary. [BR] We are not going to be able to remove dependencies on specific rpm versions for packages with patches against them which is currently a significant number. We need predictable builds and finding out at build time that patches don’t apply is not really acceptable. Once this has been eliminated/significantly reduced then perhaps that becomes an option. Anyway, in this particular problem, kernel-3.10.0-862.3.2.el7.src.rpm was added here[0] but the proper repository wasn't added. The fix for this was already merged[1] The issue about not finding git was fixed last week, so maybe a git pull may help. -Erich [0] https://review.openstack.org/#/c/580689/ [1] https://review.openstack.org/#/c/581471/ From: Scott Little Date: Wednesday, July 11, 2018 at 9:09 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Download packages issues The 'bash download_mirror.sh' step seems to be very fragile.  e.g. this morning I tried to start fresh and it failed at several points.    ------ using kernel-3.10.0-862.3.2.el7 to search kernel-3.10.0-862.3.2.el7.src.rpm ------    --> run: sudo -E yumdownloader -q -C --source kernel-3.10.0-862.3.2.el7    Looking for kernel-3.10.0-862.3.2.el7.src.rpm    No source RPM found for kernel-3.10.0-862.3.2.el7.x86_64    Nothing to download     ------ using epel-rpm-macros-7-18 to search epel-rpm-macros-7-18.noarch.rpm ------    --> run: sudo -E yumdownloader -q -C epel-rpm-macros-7-18 --archlist=noarch,x86_64    Looking for epel-rpm-macros-7-18.noarch.rpm...    No Match for argument epel-rpm-macros-7-18    Nothing to download and the tarball downloads failed on.    --2018-07-11 13:13:28--  http://git.infradead.org/users/jjs/linux-tpmdd.git/snapshot/fd5c78694f3f1c875e293de7a641ba8a3d60d00d.tar.g    Resolving git.infradead.org (git.infradead.org)... 198.137.202.133, 2607:7c80:54:e::133    Connecting to git.infradead.org (git.infradead.org)|198.137.202.133|:80... connected.    HTTP request sent, awaiting response... 200 OK    Length: unspecified [application/x-gzip]    Saving to: 'fd5c78694f3f1c875e293de7a641ba8a3d60d00d.tar.gz'    2018-07-11 13:14:34 (0.00 B/s) - 'fd5c78694f3f1c875e293de7a641ba8a3d60d00d.tar.gz' saved [0]    tar: This does not look like a tar archive    gzip: stdin: unexpected end of file    tar: Child returned status 1    tar: Error is not recoverable: exiting now    mv: cannot stat 'linux-tpmdd-fd5c786/drivers/char/tpm': No such file or directory    tar: tpm: Cannot stat: No such file or directory    tar: Exiting with failure status due to previous errors    /localdisk    tss2-930.tar.gz    /localdisk/output/stx-r1/CentOS/pike/downloads /localdisk    ./tarball-dl.sh: line 156: git: command not found    ./tarball-dl.sh: line 157: pushd: ibmtpm20tss-tss: No such file or directory    ./tarball-dl.sh: line 158: git: command not found    /localdisk    mv: cannot stat 'ibmtpm20tss-tss': No such file or directory    tar: tss2-930: Cannot stat: No such file or directory    tar: Exiting with failure status due to previous errors    ./tarball-dl.sh: line 165: popd: directory stack empty Is this really going to be our default operating mode?   Never knowing, day by day, when the next package will be dropped from an upstream source.  Is it possible for strarlingX to host it's own mirrors... of at least the needed subset of packages? Scott _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From chris.friesen at windriver.com Wed Jul 11 20:15:43 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Wed, 11 Jul 2018 14:15:43 -0600 Subject: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA3160B7@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA3160B7@ALA-MBD.corp.ad.wrs.com> Message-ID: <5B46656F.2000604@windriver.com> On 07/10/2018 04:21 PM, Khalil, Ghada wrote: > Hello, > With the increased number of active stories in StartlingX, I'd like to propose that we consistently use a set of prefixes to make it easier to search and find work items. Isn't this sort of thing what "tags" are intended to be used for? You can search using tags as well, and can have multiple tags on a given story. Chris From Brent.Rowsell at windriver.com Wed Jul 11 20:17:12 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Wed, 11 Jul 2018 20:17:12 +0000 Subject: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches In-Reply-To: <5B46656F.2000604@windriver.com> References: <151EE31B9FCCA54397A757BC674650F0BA3160B7@ALA-MBD.corp.ad.wrs.com> <5B46656F.2000604@windriver.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0D09B5@ALA-MBD.corp.ad.wrs.com> With tags there is no guarantee there won't be overlap with other projects. Brent -----Original Message----- From: Chris Friesen [mailto:chris.friesen at windriver.com] Sent: Wednesday, July 11, 2018 4:16 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches On 07/10/2018 04:21 PM, Khalil, Ghada wrote: > Hello, > With the increased number of active stories in StartlingX, I'd like to propose that we consistently use a set of prefixes to make it easier to search and find work items. Isn't this sort of thing what "tags" are intended to be used for? You can search using tags as well, and can have multiple tags on a given story. Chris _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From chris.friesen at windriver.com Wed Jul 11 20:22:12 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Wed, 11 Jul 2018 14:22:12 -0600 Subject: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB0D09B5@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA3160B7@ALA-MBD.corp.ad.wrs.com> <5B46656F.2000604@windriver.com> <2588653EBDFFA34B982FAF00F1B4844EBB0D09B5@ALA-MBD.corp.ad.wrs.com> Message-ID: <5B4666F4.5010707@windriver.com> On 07/11/2018 02:17 PM, Rowsell, Brent wrote: > With tags there is no guarantee there won't be overlap with other projects. Not a problem. You can search for tags within our project: https://storyboard.openstack.org/#!/story/list?status=active&tags=cinder&tags=enhancement&project_group_id=86 Chris From ildiko.vancsa at gmail.com Wed Jul 11 20:40:04 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 11 Jul 2018 15:40:04 -0500 Subject: [Starlingx-discuss] Keystone federation testing Message-ID: <158F3F30-C6A2-4782-A31D-BF2B20170857@gmail.com> Hi, Within the Edge Computing Group we have a few people interested in Keystone federation testing starting with general federation and moving to edge specific test cases onwards. In case you are interested in this activity, we are organizing a call for next Thursday to talk about basic testing in OpenStack including identifying tasks and volunteers to complete them. We would like to use the time to clarify questions about Keystone federation capabilities if there’s any. We are also collaborating with the OPNFV Edge Cloud project for advanced test scenarios which we will also discuss on the call. The call details are here: https://wiki.openstack.org/wiki/Edge_Computing_Group#Federation_Testing_Call Please check out the materials on this etherpad prior to the call if you plan to join: https://etherpad.openstack.org/p/ECG_Keystone_Testing Please let me know if you have any questions. Thanks and Best Regards, Ildikó From Tee.Ngo at windriver.com Wed Jul 11 20:45:48 2018 From: Tee.Ngo at windriver.com (Ngo, Tee) Date: Wed, 11 Jul 2018 20:45:48 +0000 Subject: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches In-Reply-To: <5B4666F4.5010707@windriver.com> References: <151EE31B9FCCA54397A757BC674650F0BA3160B7@ALA-MBD.corp.ad.wrs.com> <5B46656F.2000604@windriver.com> <2588653EBDFFA34B982FAF00F1B4844EBB0D09B5@ALA-MBD.corp.ad.wrs.com> <5B4666F4.5010707@windriver.com> Message-ID: <80ED4CE81E3D8F4099306648E95DAFE44C8893DA@ALA-MBD.corp.ad.wrs.com> Proposed prefixes also have merit. Each story is self described category wise. It's helpful when viewing a list of stories by owner/project. Tee -----Original Message----- From: Chris Friesen [mailto:chris.friesen at windriver.com] Sent: July-11-18 4:22 PM To: Rowsell, Brent; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches On 07/11/2018 02:17 PM, Rowsell, Brent wrote: > With tags there is no guarantee there won't be overlap with other projects. Not a problem. You can search for tags within our project: https://storyboard.openstack.org/#!/story/list?status=active&tags=cinder&tags=enhancement&project_group_id=86 Chris _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Wed Jul 11 20:49:23 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 11 Jul 2018 20:49:23 +0000 Subject: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches In-Reply-To: <5B4666F4.5010707@windriver.com> References: <151EE31B9FCCA54397A757BC674650F0BA3160B7@ALA-MBD.corp.ad.wrs.com> <5B46656F.2000604@windriver.com> <2588653EBDFFA34B982FAF00F1B4844EBB0D09B5@ALA-MBD.corp.ad.wrs.com> <5B4666F4.5010707@windriver.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA3166D9@ALA-MBD.corp.ad.wrs.com> I was going for a more visual approach where one can easily see the category by looking at the story list. In any case, the use of prefixes doesn't preclude the use of tags for further search refinement. But, if tags are more efficient to use and are the preferred option for the community, we can use them exclusively. We will need to agree on the minimal set. Ghada -----Original Message----- From: Chris Friesen [mailto:chris.friesen at windriver.com] Sent: Wednesday, July 11, 2018 4:22 PM To: Rowsell, Brent; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches On 07/11/2018 02:17 PM, Rowsell, Brent wrote: > With tags there is no guarantee there won't be overlap with other projects. Not a problem. You can search for tags within our project: https://storyboard.openstack.org/#!/story/list?status=active&tags=cinder&tags=enhancement&project_group_id=86 Chris _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From chris.friesen at windriver.com Wed Jul 11 21:09:25 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Wed, 11 Jul 2018 15:09:25 -0600 Subject: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA3166D9@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA3160B7@ALA-MBD.corp.ad.wrs.com> <5B46656F.2000604@windriver.com> <2588653EBDFFA34B982FAF00F1B4844EBB0D09B5@ALA-MBD.corp.ad.wrs.com> <5B4666F4.5010707@windriver.com> <151EE31B9FCCA54397A757BC674650F0BA3166D9@ALA-MBD.corp.ad.wrs.com> Message-ID: <5B467205.5060808@windriver.com> On 07/11/2018 02:49 PM, Khalil, Ghada wrote: > I was going for a more visual approach where one can easily see the category by looking at the story list. In any case, the use of prefixes doesn't preclude the use of tags for further search refinement. > > But, if tags are more efficient to use and are the preferred option for the community, we can use them exclusively. We will need to agree on the minimal set. The main benefit I see to using tags is that it lets you limit the search to specifically the tags rather than pattern-matching against the whole story which I think the "&q=keyword" search query does. Either way would likely work, I just thought I'd mention the possibility of tags. Chris From zhipengs.liu at intel.com Thu Jul 12 01:44:33 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 12 Jul 2018 01:44:33 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <9d889c66-a603-2d12-dd70-c8fb3b3911d0@windriver.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> <9d889c66-a603-2d12-dd70-c8fb3b3911d0@windriver.com> Message-ID: <93814834B4855241994F290E959305C752F48CC6@SHSMSX104.ccr.corp.intel.com> Thanks Little! We also found it should be OK that sed used later yesterday. Before we changed this place, we could not build any RPM. It always gave out errors like below 15:13:50 Error: Package: python-urlgrabber-3.10-8.el7.noarch (TisCentos7Distro) 15:13:50 Requires: /usr/bin/python 15:13:50 Error: Package: nss-3.28.4-1.2.el7_3.x86_64 (TisCentos7Distro) 15:13:50 Requires: libsoftokn3.so()(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libfreebl3.so(NSSRAWHASH_3.12.3)(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1()(64bit) 15:13:50 Error: Package: krb5-libs-1.15.1-19.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libcom_err.so.2()(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1(ELFUTILS_1.0)(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) ........ After changed this place, no this issue found anymore, but another error we saw all the time. 19:30:45 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. 19:30:45 http://127.0.0.1:8088/MY_REPO/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found Zhipeng -----Original Message----- From: Scott Little [mailto:scott.little at windriver.com] Sent: 2018年7月11日 23:49 To: Liu, ZhipengS ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing You shouldn't have to do that. The mock.cfg.proto file is processed by the modify-build-cfg script. You should see it using sed to substitute "MY_REPO_DIR" with $MY_REPO. There might be weaknesses elsewhere in the build process where it attempts to determine if modify-build-cfg should be re-run.  e.g. I don't think we test for changes to environment variables between runs. Scott On 18-07-11 04:14 AM, Liu, ZhipengS wrote: > Hi Abraham, > > When I followed your guide, there are 3 issues I found. > > 1) We need change mock.cfg.proto file as below [TisCentos7Distro] > name=Tis-Centos-7-Distro > enabled=1 > baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary > // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found. > > 2) In Download Source Code Repositories step of the guide. > cgcs-dl > $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ > $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads > // change to > $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ > $MY_REPO/stx/ > > 3) lighttpd not started by default in build container, and also could not started manually. > > =============================================================== > Raised below 2 stories. > 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto > 2002938 lighttpd not started by default in build container > > > BRs > zhipeng > -----Original Message----- > From: Liu, ZhipengS > Sent: 2018年7月5日 11:14 > To: Hu, Yong ; Arce Moreno, Abraham > ; Scott Little > ; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , > mock package missing > > Hi Abraham, > > When I run below step > $ docker build -t user:centos-mirror-repository -f Dockerfile . > It mentioned > Get https://registry-1.docker.io/v2/: net/http: request canceled while > waiting for connection > > It can work after following below steps. > =========================================================== > Here is a link to the official docker doc for proxy > http:https://docs.docker.com/engine/admin/systemd/#http-proxy > A quick outline: > First, create a systemd drop-in directory for the docker service: > mkdir /etc/systemd/system/docker.service.d > Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: > [Service] > Environment="HTTP_PROXY=http://proxy.example.com:80/" > If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: > Environment="HTTP_PROXY=http://proxy.example.com:80/" > Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" > Flush changes: > $ sudo systemctl daemon-reload > Verify that the configuration has been loaded: > $ sudo systemctl show --property Environment docker > Environment=HTTP_PROXY=http://proxy.example.com:80/ > Restart Docker: > $ sudo systemctl restart docker > > -----Original Message----- > From: Hu, Yong [mailto:yong.hu at intel.com] > Sent: 2018年7月4日 15:15 > To: Arce Moreno, Abraham ; Scott Little > ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , > mock package missing > > Hi Abraham, > Did you run "build-pkgs" or "build-pkgs --serial"? > If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. > 13:42:03 Failed to build packages: > memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm > python-2.7.5-58.el7.tis.3.src.rpm > > In the meantime, @Zhipeng is following steps in > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" wrote: > > > > > > It will be great if someone else could take our Developer Guide > > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > > and build the ISO from scratch. > > > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > > tuned. > > Cool! Thank you! > > > _______________________________________________ > 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 Jul 12 06:37:34 2018 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Thu, 12 Jul 2018 06:37:34 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <93814834B4855241994F290E959305C752F48CC6@SHSMSX104.ccr.corp.intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> <9d889c66-a603-2d12-dd70-c8fb3b3911d0@windriver.com> <93814834B4855241994F290E959305C752F48CC6@SHSMSX104.ccr.corp.intel.com> Message-ID: Zhipeng, The failure is due to your mirror package missing, such as python, nss-softokn3... so that mock init failed at the beginning. Could you check whether packages in rpms_from_centos_3rd_parties.lst are totally downloaded? Thanks, Mingyuan -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, July 12, 2018 9:45 To: Scott Little ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Thanks Little! We also found it should be OK that sed used later yesterday. Before we changed this place, we could not build any RPM. It always gave out errors like below 15:13:50 Error: Package: python-urlgrabber-3.10-8.el7.noarch (TisCentos7Distro) 15:13:50 Requires: /usr/bin/python 15:13:50 Error: Package: nss-3.28.4-1.2.el7_3.x86_64 (TisCentos7Distro) 15:13:50 Requires: libsoftokn3.so()(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libfreebl3.so(NSSRAWHASH_3.12.3)(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1()(64bit) 15:13:50 Error: Package: krb5-libs-1.15.1-19.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libcom_err.so.2()(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1(ELFUTILS_1.0)(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) ........ After changed this place, no this issue found anymore, but another error we saw all the time. 19:30:45 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. 19:30:45 http://127.0.0.1:8088/MY_REPO/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found Zhipeng -----Original Message----- From: Scott Little [mailto:scott.little at windriver.com] Sent: 2018年7月11日 23:49 To: Liu, ZhipengS ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing You shouldn't have to do that. The mock.cfg.proto file is processed by the modify-build-cfg script. You should see it using sed to substitute "MY_REPO_DIR" with $MY_REPO. There might be weaknesses elsewhere in the build process where it attempts to determine if modify-build-cfg should be re-run.  e.g. I don't think we test for changes to environment variables between runs. Scott On 18-07-11 04:14 AM, Liu, ZhipengS wrote: > Hi Abraham, > > When I followed your guide, there are 3 issues I found. > > 1) We need change mock.cfg.proto file as below [TisCentos7Distro] > name=Tis-Centos-7-Distro > enabled=1 > baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary > // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found. > > 2) In Download Source Code Repositories step of the guide. > cgcs-dl > $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ > $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads > // change to > $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ > $MY_REPO/stx/ > > 3) lighttpd not started by default in build container, and also could not started manually. > > =============================================================== > Raised below 2 stories. > 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto > 2002938 lighttpd not started by default in build container > > > BRs > zhipeng > -----Original Message----- > From: Liu, ZhipengS > Sent: 2018年7月5日 11:14 > To: Hu, Yong ; Arce Moreno, Abraham > ; Scott Little > ; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , > mock package missing > > Hi Abraham, > > When I run below step > $ docker build -t user:centos-mirror-repository -f Dockerfile . > It mentioned > Get https://registry-1.docker.io/v2/: net/http: request canceled while > waiting for connection > > It can work after following below steps. > =========================================================== > Here is a link to the official docker doc for proxy > http:https://docs.docker.com/engine/admin/systemd/#http-proxy > A quick outline: > First, create a systemd drop-in directory for the docker service: > mkdir /etc/systemd/system/docker.service.d > Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: > [Service] > Environment="HTTP_PROXY=http://proxy.example.com:80/" > If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: > Environment="HTTP_PROXY=http://proxy.example.com:80/" > Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" > Flush changes: > $ sudo systemctl daemon-reload > Verify that the configuration has been loaded: > $ sudo systemctl show --property Environment docker > Environment=HTTP_PROXY=http://proxy.example.com:80/ > Restart Docker: > $ sudo systemctl restart docker > > -----Original Message----- > From: Hu, Yong [mailto:yong.hu at intel.com] > Sent: 2018年7月4日 15:15 > To: Arce Moreno, Abraham ; Scott Little > ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , > mock package missing > > Hi Abraham, > Did you run "build-pkgs" or "build-pkgs --serial"? > If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. > 13:42:03 Failed to build packages: > memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm > python-2.7.5-58.el7.tis.3.src.rpm > > In the meantime, @Zhipeng is following steps in > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" wrote: > > > > > > It will be great if someone else could take our Developer Guide > > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > > and build the ISO from scratch. > > > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > > tuned. > > Cool! Thank you! > > > _______________________________________________ > 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 zhipengs.liu at intel.com Thu Jul 12 13:32:34 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 12 Jul 2018 13:32:34 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> <9d889c66-a603-2d12-dd70-c8fb3b3911d0@windriver.com> <93814834B4855241994F290E959305C752F48CC6@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C752F48FA8@SHSMSX104.ccr.corp.intel.com> Thanks Mingyuan! Some RPM exactly missing. Hi Abraham, We'd better add 3rd-centos_rpms_missing_L1.txt to below as well ======================================== Verify Packages 1.Verify there are no missing or failed packages: # cat output/3rd_rpms_missing_L1.txt output/3rd_srpms_missing_L1.txt output/centos_rpms_missing_L1.txt output/centos_srpms_missing_L1.txt ======================================== Thanks! Zhipeng -----Original Message----- From: Qi, Mingyuan Sent: 2018年7月12日 14:38 To: Liu, ZhipengS ; Scott Little ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Zhipeng, The failure is due to your mirror package missing, such as python, nss-softokn3... so that mock init failed at the beginning. Could you check whether packages in rpms_from_centos_3rd_parties.lst are totally downloaded? Thanks, Mingyuan -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, July 12, 2018 9:45 To: Scott Little ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Thanks Little! We also found it should be OK that sed used later yesterday. Before we changed this place, we could not build any RPM. It always gave out errors like below 15:13:50 Error: Package: python-urlgrabber-3.10-8.el7.noarch (TisCentos7Distro) 15:13:50 Requires: /usr/bin/python 15:13:50 Error: Package: nss-3.28.4-1.2.el7_3.x86_64 (TisCentos7Distro) 15:13:50 Requires: libsoftokn3.so()(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libfreebl3.so(NSSRAWHASH_3.12.3)(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1()(64bit) 15:13:50 Error: Package: krb5-libs-1.15.1-19.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libcom_err.so.2()(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1(ELFUTILS_1.0)(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) ........ After changed this place, no this issue found anymore, but another error we saw all the time. 19:30:45 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. 19:30:45 http://127.0.0.1:8088/MY_REPO/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found Zhipeng -----Original Message----- From: Scott Little [mailto:scott.little at windriver.com] Sent: 2018年7月11日 23:49 To: Liu, ZhipengS ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing You shouldn't have to do that. The mock.cfg.proto file is processed by the modify-build-cfg script. You should see it using sed to substitute "MY_REPO_DIR" with $MY_REPO. There might be weaknesses elsewhere in the build process where it attempts to determine if modify-build-cfg should be re-run.  e.g. I don't think we test for changes to environment variables between runs. Scott On 18-07-11 04:14 AM, Liu, ZhipengS wrote: > Hi Abraham, > > When I followed your guide, there are 3 issues I found. > > 1) We need change mock.cfg.proto file as below [TisCentos7Distro] > name=Tis-Centos-7-Distro > enabled=1 > baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary > // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found. > > 2) In Download Source Code Repositories step of the guide. > cgcs-dl > $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ > $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads > // change to > $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ > $MY_REPO/stx/ > > 3) lighttpd not started by default in build container, and also could not started manually. > > =============================================================== > Raised below 2 stories. > 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto > 2002938 lighttpd not started by default in build container > > > BRs > zhipeng > -----Original Message----- > From: Liu, ZhipengS > Sent: 2018年7月5日 11:14 > To: Hu, Yong ; Arce Moreno, Abraham > ; Scott Little > ; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , > mock package missing > > Hi Abraham, > > When I run below step > $ docker build -t user:centos-mirror-repository -f Dockerfile . > It mentioned > Get https://registry-1.docker.io/v2/: net/http: request canceled while > waiting for connection > > It can work after following below steps. > =========================================================== > Here is a link to the official docker doc for proxy > http:https://docs.docker.com/engine/admin/systemd/#http-proxy > A quick outline: > First, create a systemd drop-in directory for the docker service: > mkdir /etc/systemd/system/docker.service.d > Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: > [Service] > Environment="HTTP_PROXY=http://proxy.example.com:80/" > If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: > Environment="HTTP_PROXY=http://proxy.example.com:80/" > Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" > Flush changes: > $ sudo systemctl daemon-reload > Verify that the configuration has been loaded: > $ sudo systemctl show --property Environment docker > Environment=HTTP_PROXY=http://proxy.example.com:80/ > Restart Docker: > $ sudo systemctl restart docker > > -----Original Message----- > From: Hu, Yong [mailto:yong.hu at intel.com] > Sent: 2018年7月4日 15:15 > To: Arce Moreno, Abraham ; Scott Little > ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , > mock package missing > > Hi Abraham, > Did you run "build-pkgs" or "build-pkgs --serial"? > If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. > 13:42:03 Failed to build packages: > memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm > python-2.7.5-58.el7.tis.3.src.rpm > > In the meantime, @Zhipeng is following steps in > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" wrote: > > > > > > It will be great if someone else could take our Developer Guide > > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > > and build the ISO from scratch. > > > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > > tuned. > > Cool! Thank you! > > > _______________________________________________ > 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 zhipengs.liu at intel.com Thu Jul 12 15:13:04 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 12 Jul 2018 15:13:04 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <93814834B4855241994F290E959305C752F48FA8@SHSMSX104.ccr.corp.intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> <9d889c66-a603-2d12-dd70-c8fb3b3911d0@windriver.com> <93814834B4855241994F290E959305C752F48CC6@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48FA8@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C752F49046@SHSMSX104.ccr.corp.intel.com> Hi Scott and Abraham, After I add missing RPMS, build still failed as below. However, with the mirror I built, the build in our old build environment is ongoing normally. 23:40:14 Start: chroot init 23:40:14 INFO: calling preinit hooks 23:40:14 INFO: enabled root cache 23:40:14 INFO: enabled yum cache 23:40:14 Start: cleaning yum metadata 23:40:14 Finish: cleaning yum metadata 23:40:14 INFO: enabled HW Info plugin 23:40:14 Mock Version: 1.4.11 23:40:14 INFO: Mock Version: 1.4.11 23:40:14 Start: yum install 23:40:14 Finish: yum install 23:40:14 ERROR: Exception(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis-extensions-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) 0 minutes 2 seconds 23:40:14 INFO: Results and/or logs in: /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx-tis-r5-pike-std/tis-extensions-1.0-2.tis 23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? 23:40:14 End build: /localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis-extensions-1.0-2.tis.src.rpm 23:40:14 Error building tis-extensions-1.0-2.tis.src.rpm. 23:40:14 Will try to build again (if some other package will succeed). 23:40:14 Start build: /localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm 23:40:14 building tpm2-openssl-engine-1.0-2.tis.src.rpm 23:40:18 INFO: mock.py version 1.4.11 starting (python version = 2.7.5)... 23:40:18 Start: init plugins 23:40:18 INFO: selinux disabled 23:40:18 Finish: init plugins 23:40:18 Start: run 23:40:18 INFO: Start(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) BRs zhipeng -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: 2018年7月12日 21:33 To: Qi, Mingyuan ; Scott Little ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Thanks Mingyuan! Some RPM exactly missing. Hi Abraham, We'd better add 3rd-centos_rpms_missing_L1.txt to below as well ======================================== Verify Packages 1.Verify there are no missing or failed packages: # cat output/3rd_rpms_missing_L1.txt output/3rd_srpms_missing_L1.txt output/centos_rpms_missing_L1.txt output/centos_srpms_missing_L1.txt ======================================== Thanks! Zhipeng -----Original Message----- From: Qi, Mingyuan Sent: 2018年7月12日 14:38 To: Liu, ZhipengS ; Scott Little ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Zhipeng, The failure is due to your mirror package missing, such as python, nss-softokn3... so that mock init failed at the beginning. Could you check whether packages in rpms_from_centos_3rd_parties.lst are totally downloaded? Thanks, Mingyuan -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, July 12, 2018 9:45 To: Scott Little ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Thanks Little! We also found it should be OK that sed used later yesterday. Before we changed this place, we could not build any RPM. It always gave out errors like below 15:13:50 Error: Package: python-urlgrabber-3.10-8.el7.noarch (TisCentos7Distro) 15:13:50 Requires: /usr/bin/python 15:13:50 Error: Package: nss-3.28.4-1.2.el7_3.x86_64 (TisCentos7Distro) 15:13:50 Requires: libsoftokn3.so()(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libfreebl3.so(NSSRAWHASH_3.12.3)(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1()(64bit) 15:13:50 Error: Package: krb5-libs-1.15.1-19.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libcom_err.so.2()(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1(ELFUTILS_1.0)(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) ........ After changed this place, no this issue found anymore, but another error we saw all the time. 19:30:45 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. 19:30:45 http://127.0.0.1:8088/MY_REPO/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found Zhipeng -----Original Message----- From: Scott Little [mailto:scott.little at windriver.com] Sent: 2018年7月11日 23:49 To: Liu, ZhipengS ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing You shouldn't have to do that. The mock.cfg.proto file is processed by the modify-build-cfg script. You should see it using sed to substitute "MY_REPO_DIR" with $MY_REPO. There might be weaknesses elsewhere in the build process where it attempts to determine if modify-build-cfg should be re-run.  e.g. I don't think we test for changes to environment variables between runs. Scott On 18-07-11 04:14 AM, Liu, ZhipengS wrote: > Hi Abraham, > > When I followed your guide, there are 3 issues I found. > > 1) We need change mock.cfg.proto file as below [TisCentos7Distro] > name=Tis-Centos-7-Distro > enabled=1 > baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary > // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found. > > 2) In Download Source Code Repositories step of the guide. > cgcs-dl > $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ > $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads > // change to > $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ > $MY_REPO/stx/ > > 3) lighttpd not started by default in build container, and also could not started manually. > > =============================================================== > Raised below 2 stories. > 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto > 2002938 lighttpd not started by default in build container > > > BRs > zhipeng > -----Original Message----- > From: Liu, ZhipengS > Sent: 2018年7月5日 11:14 > To: Hu, Yong ; Arce Moreno, Abraham > ; Scott Little > ; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , > mock package missing > > Hi Abraham, > > When I run below step > $ docker build -t user:centos-mirror-repository -f Dockerfile . > It mentioned > Get https://registry-1.docker.io/v2/: net/http: request canceled while > waiting for connection > > It can work after following below steps. > =========================================================== > Here is a link to the official docker doc for proxy > http:https://docs.docker.com/engine/admin/systemd/#http-proxy > A quick outline: > First, create a systemd drop-in directory for the docker service: > mkdir /etc/systemd/system/docker.service.d > Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: > [Service] > Environment="HTTP_PROXY=http://proxy.example.com:80/" > If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: > Environment="HTTP_PROXY=http://proxy.example.com:80/" > Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" > Flush changes: > $ sudo systemctl daemon-reload > Verify that the configuration has been loaded: > $ sudo systemctl show --property Environment docker > Environment=HTTP_PROXY=http://proxy.example.com:80/ > Restart Docker: > $ sudo systemctl restart docker > > -----Original Message----- > From: Hu, Yong [mailto:yong.hu at intel.com] > Sent: 2018年7月4日 15:15 > To: Arce Moreno, Abraham ; Scott Little > ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , > mock package missing > > Hi Abraham, > Did you run "build-pkgs" or "build-pkgs --serial"? > If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. > 13:42:03 Failed to build packages: > memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm > python-2.7.5-58.el7.tis.3.src.rpm > > In the meantime, @Zhipeng is following steps in > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" wrote: > > > > > > It will be great if someone else could take our Developer Guide > > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > > and build the ISO from scratch. > > > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > > tuned. > > Cool! Thank you! > > > _______________________________________________ > 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 scott.little at windriver.com Thu Jul 12 15:35:30 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 12 Jul 2018 11:35:30 -0400 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <93814834B4855241994F290E959305C752F49046@SHSMSX104.ccr.corp.intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> <9d889c66-a603-2d12-dd70-c8fb3b3911d0@windriver.com> <93814834B4855241994F290E959305C752F48CC6@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48FA8@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F49046@SHSMSX104.ccr.corp.intel.com> Message-ID: <93bfa378-9f26-d4c8-8f37-ad23a543e756@windriver.com> For more details, examine the log files in this directory ... /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx-tis-r5-pike-std/tis-extensions-1.0-2.tis/ On 18-07-12 11:13 AM, Liu, ZhipengS wrote: > Hi Scott and Abraham, > > After I add missing RPMS, build still failed as below. However, with the mirror I built, > the build in our old build environment is ongoing normally. > > 23:40:14 Start: chroot init > 23:40:14 INFO: calling preinit hooks > 23:40:14 INFO: enabled root cache > 23:40:14 INFO: enabled yum cache > 23:40:14 Start: cleaning yum metadata > 23:40:14 Finish: cleaning yum metadata > 23:40:14 INFO: enabled HW Info plugin > 23:40:14 Mock Version: 1.4.11 > 23:40:14 INFO: Mock Version: 1.4.11 > 23:40:14 Start: yum install > 23:40:14 Finish: yum install > 23:40:14 ERROR: Exception(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis-extensions-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) 0 minutes 2 seconds > 23:40:14 INFO: Results and/or logs in: /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx-tis-r5-pike-std/tis-extensions-1.0-2.tis > 23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? > 23:40:14 End build: /localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis-extensions-1.0-2.tis.src.rpm > 23:40:14 Error building tis-extensions-1.0-2.tis.src.rpm. > 23:40:14 Will try to build again (if some other package will succeed). > 23:40:14 Start build: /localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm > 23:40:14 building tpm2-openssl-engine-1.0-2.tis.src.rpm > 23:40:18 INFO: mock.py version 1.4.11 starting (python version = 2.7.5)... > 23:40:18 Start: init plugins > 23:40:18 INFO: selinux disabled > 23:40:18 Finish: init plugins > 23:40:18 Start: run > 23:40:18 INFO: Start(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) > > BRs > zhipeng > > > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: 2018年7月12日 21:33 > To: Qi, Mingyuan ; Scott Little ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Thanks Mingyuan! > Some RPM exactly missing. > > Hi Abraham, > > We'd better add > 3rd-centos_rpms_missing_L1.txt to below as well > ======================================== > Verify Packages > 1.Verify there are no missing or failed packages: > # cat output/3rd_rpms_missing_L1.txt output/3rd_srpms_missing_L1.txt output/centos_rpms_missing_L1.txt output/centos_srpms_missing_L1.txt > ======================================== > > Thanks! > Zhipeng > > -----Original Message----- > From: Qi, Mingyuan > Sent: 2018年7月12日 14:38 > To: Liu, ZhipengS ; Scott Little ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Zhipeng, > > The failure is due to your mirror package missing, such as python, nss-softokn3... so that mock init failed at the beginning. > Could you check whether packages in rpms_from_centos_3rd_parties.lst are totally downloaded? > > Thanks, > Mingyuan > > > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: Thursday, July 12, 2018 9:45 > To: Scott Little ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Thanks Little! > We also found it should be OK that sed used later yesterday. > > Before we changed this place, we could not build any RPM. > It always gave out errors like below > 15:13:50 Error: Package: python-urlgrabber-3.10-8.el7.noarch (TisCentos7Distro) > 15:13:50 Requires: /usr/bin/python > 15:13:50 Error: Package: nss-3.28.4-1.2.el7_3.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libsoftokn3.so()(64bit) > 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libfreebl3.so(NSSRAWHASH_3.12.3)(64bit) > 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libelf.so.1()(64bit) > 15:13:50 Error: Package: krb5-libs-1.15.1-19.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libcom_err.so.2()(64bit) > 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libelf.so.1(ELFUTILS_1.0)(64bit) > 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) ........ > > After changed this place, no this issue found anymore, but another error we saw all the time. > 19:30:45 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. > 19:30:45 http://127.0.0.1:8088/MY_REPO/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found > > Zhipeng > > -----Original Message----- > From: Scott Little [mailto:scott.little at windriver.com] > Sent: 2018年7月11日 23:49 > To: Liu, ZhipengS ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > You shouldn't have to do that. > > The mock.cfg.proto file is processed by the modify-build-cfg script. You should see it using sed to substitute "MY_REPO_DIR" with $MY_REPO. > > There might be weaknesses elsewhere in the build process where it attempts to determine if modify-build-cfg should be re-run.  e.g. I don't think we test for changes to environment variables between runs. > > Scott > > > On 18-07-11 04:14 AM, Liu, ZhipengS wrote: >> Hi Abraham, >> >> When I followed your guide, there are 3 issues I found. >> >> 1) We need change mock.cfg.proto file as below [TisCentos7Distro] >> name=Tis-Centos-7-Distro >> enabled=1 >> baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary >> // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found. >> >> 2) In Download Source Code Repositories step of the guide. >> cgcs-dl >> $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ >> $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads >> // change to >> $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ >> $MY_REPO/stx/ >> >> 3) lighttpd not started by default in build container, and also could not started manually. >> >> =============================================================== >> Raised below 2 stories. >> 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto >> 2002938 lighttpd not started by default in build container >> >> >> BRs >> zhipeng >> -----Original Message----- >> From: Liu, ZhipengS >> Sent: 2018年7月5日 11:14 >> To: Hu, Yong ; Arce Moreno, Abraham >> ; Scott Little >> ; starlingx-discuss at lists.starlingx.io >> Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , >> mock package missing >> >> Hi Abraham, >> >> When I run below step >> $ docker build -t user:centos-mirror-repository -f Dockerfile . >> It mentioned >> Get https://registry-1.docker.io/v2/: net/http: request canceled while >> waiting for connection >> >> It can work after following below steps. >> =========================================================== >> Here is a link to the official docker doc for proxy >> http:https://docs.docker.com/engine/admin/systemd/#http-proxy >> A quick outline: >> First, create a systemd drop-in directory for the docker service: >> mkdir /etc/systemd/system/docker.service.d >> Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: >> [Service] >> Environment="HTTP_PROXY=http://proxy.example.com:80/" >> If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: >> Environment="HTTP_PROXY=http://proxy.example.com:80/" >> Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" >> Flush changes: >> $ sudo systemctl daemon-reload >> Verify that the configuration has been loaded: >> $ sudo systemctl show --property Environment docker >> Environment=HTTP_PROXY=http://proxy.example.com:80/ >> Restart Docker: >> $ sudo systemctl restart docker >> >> -----Original Message----- >> From: Hu, Yong [mailto:yong.hu at intel.com] >> Sent: 2018年7月4日 15:15 >> To: Arce Moreno, Abraham ; Scott Little >> ; starlingx-discuss at lists.starlingx.io >> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , >> mock package missing >> >> Hi Abraham, >> Did you run "build-pkgs" or "build-pkgs --serial"? >> If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. >> 13:42:03 Failed to build packages: >> memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm >> python-2.7.5-58.el7.tis.3.src.rpm >> >> In the meantime, @Zhipeng is following steps in >> https://wiki.openstack.org/wiki/StarlingX/Developer_Guide >> >> On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" wrote: >> >> > > > > It will be great if someone else could take our Developer Guide >> > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide >> > > > > and build the ISO from scratch. >> > >> > Yeah, we will have someone to do the exercise based on this guide. Pls stay >> > tuned. >> >> Cool! Thank you! >> >> >> _______________________________________________ >> 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 yong.hu at intel.com Thu Jul 12 15:46:49 2018 From: yong.hu at intel.com (Hu, Yong) Date: Thu, 12 Jul 2018 15:46:49 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <93bfa378-9f26-d4c8-8f37-ad23a543e756@windriver.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> <9d889c66-a603-2d12-dd70-c8fb3b3911d0@windriver.com> <93814834B4855241994F290E959305C752F48CC6@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48FA8@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F49046@SHSMSX104.ccr.corp.intel.com> <93bfa378-9f26-d4c8-8f37-ad23a543e756@windriver.com> Message-ID: <738B5DAD-15A1-404C-A65C-952A699A1D98@intel.com> Zhipeng, It looks the local repo in your build environment is not correct. You can check if "~/cgcs-root/cgcs-centos-repo/Binary/comps.xml" exists. If no, you need to recreate "cgcs-centos-repo" with the latest version of "stx-tools/toCOPY/generate-cgcs-centos-repo.sh" to assure: 1. the folder structure in "~/cgcs-root/cgcs-centos-repo/Binary/" is correct 2. "~/cgcs-root/cgcs-centos-repo/Binary/comps.xml" does exist Regards, Yong On 12/07/2018, 8:36 AM, "Scott Little" wrote: For more details, examine the log files in this directory ... /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx-tis-r5-pike-std/tis-extensions-1.0-2.tis/ On 18-07-12 11:13 AM, Liu, ZhipengS wrote: > Hi Scott and Abraham, > > After I add missing RPMS, build still failed as below. However, with the mirror I built, > the build in our old build environment is ongoing normally. > > 23:40:14 Start: chroot init > 23:40:14 INFO: calling preinit hooks > 23:40:14 INFO: enabled root cache > 23:40:14 INFO: enabled yum cache > 23:40:14 Start: cleaning yum metadata > 23:40:14 Finish: cleaning yum metadata > 23:40:14 INFO: enabled HW Info plugin > 23:40:14 Mock Version: 1.4.11 > 23:40:14 INFO: Mock Version: 1.4.11 > 23:40:14 Start: yum install > 23:40:14 Finish: yum install > 23:40:14 ERROR: Exception(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis-extensions-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) 0 minutes 2 seconds > 23:40:14 INFO: Results and/or logs in: /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx-tis-r5-pike-std/tis-extensions-1.0-2.tis > 23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? > 23:40:14 End build: /localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis-extensions-1.0-2.tis.src.rpm > 23:40:14 Error building tis-extensions-1.0-2.tis.src.rpm. > 23:40:14 Will try to build again (if some other package will succeed). > 23:40:14 Start build: /localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm > 23:40:14 building tpm2-openssl-engine-1.0-2.tis.src.rpm > 23:40:18 INFO: mock.py version 1.4.11 starting (python version = 2.7.5)... > 23:40:18 Start: init plugins > 23:40:18 INFO: selinux disabled > 23:40:18 Finish: init plugins > 23:40:18 Start: run > 23:40:18 INFO: Start(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) > > BRs > zhipeng > > > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: 2018年7月12日 21:33 > To: Qi, Mingyuan ; Scott Little ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Thanks Mingyuan! > Some RPM exactly missing. > > Hi Abraham, > > We'd better add > 3rd-centos_rpms_missing_L1.txt to below as well > ======================================== > Verify Packages > 1.Verify there are no missing or failed packages: > # cat output/3rd_rpms_missing_L1.txt output/3rd_srpms_missing_L1.txt output/centos_rpms_missing_L1.txt output/centos_srpms_missing_L1.txt > ======================================== > > Thanks! > Zhipeng > > -----Original Message----- > From: Qi, Mingyuan > Sent: 2018年7月12日 14:38 > To: Liu, ZhipengS ; Scott Little ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Zhipeng, > > The failure is due to your mirror package missing, such as python, nss-softokn3... so that mock init failed at the beginning. > Could you check whether packages in rpms_from_centos_3rd_parties.lst are totally downloaded? > > Thanks, > Mingyuan > > > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: Thursday, July 12, 2018 9:45 > To: Scott Little ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Thanks Little! > We also found it should be OK that sed used later yesterday. > > Before we changed this place, we could not build any RPM. > It always gave out errors like below > 15:13:50 Error: Package: python-urlgrabber-3.10-8.el7.noarch (TisCentos7Distro) > 15:13:50 Requires: /usr/bin/python > 15:13:50 Error: Package: nss-3.28.4-1.2.el7_3.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libsoftokn3.so()(64bit) > 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libfreebl3.so(NSSRAWHASH_3.12.3)(64bit) > 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libelf.so.1()(64bit) > 15:13:50 Error: Package: krb5-libs-1.15.1-19.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libcom_err.so.2()(64bit) > 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libelf.so.1(ELFUTILS_1.0)(64bit) > 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) ........ > > After changed this place, no this issue found anymore, but another error we saw all the time. > 19:30:45 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. > 19:30:45 http://127.0.0.1:8088/MY_REPO/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found > > Zhipeng > > -----Original Message----- > From: Scott Little [mailto:scott.little at windriver.com] > Sent: 2018年7月11日 23:49 > To: Liu, ZhipengS ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > You shouldn't have to do that. > > The mock.cfg.proto file is processed by the modify-build-cfg script. You should see it using sed to substitute "MY_REPO_DIR" with $MY_REPO. > > There might be weaknesses elsewhere in the build process where it attempts to determine if modify-build-cfg should be re-run. e.g. I don't think we test for changes to environment variables between runs. > > Scott > > > On 18-07-11 04:14 AM, Liu, ZhipengS wrote: >> Hi Abraham, >> >> When I followed your guide, there are 3 issues I found. >> >> 1) We need change mock.cfg.proto file as below [TisCentos7Distro] >> name=Tis-Centos-7-Distro >> enabled=1 >> baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary >> // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found. >> >> 2) In Download Source Code Repositories step of the guide. >> cgcs-dl >> $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ >> $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads >> // change to >> $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ >> $MY_REPO/stx/ >> >> 3) lighttpd not started by default in build container, and also could not started manually. >> >> =============================================================== >> Raised below 2 stories. >> 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto >> 2002938 lighttpd not started by default in build container >> >> >> BRs >> zhipeng >> -----Original Message----- >> From: Liu, ZhipengS >> Sent: 2018年7月5日 11:14 >> To: Hu, Yong ; Arce Moreno, Abraham >> ; Scott Little >> ; starlingx-discuss at lists.starlingx.io >> Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , >> mock package missing >> >> Hi Abraham, >> >> When I run below step >> $ docker build -t user:centos-mirror-repository -f Dockerfile . >> It mentioned >> Get https://registry-1.docker.io/v2/: net/http: request canceled while >> waiting for connection >> >> It can work after following below steps. >> =========================================================== >> Here is a link to the official docker doc for proxy >> http:https://docs.docker.com/engine/admin/systemd/#http-proxy >> A quick outline: >> First, create a systemd drop-in directory for the docker service: >> mkdir /etc/systemd/system/docker.service.d >> Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: >> [Service] >> Environment="HTTP_PROXY=http://proxy.example.com:80/" >> If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: >> Environment="HTTP_PROXY=http://proxy.example.com:80/" >> Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" >> Flush changes: >> $ sudo systemctl daemon-reload >> Verify that the configuration has been loaded: >> $ sudo systemctl show --property Environment docker >> Environment=HTTP_PROXY=http://proxy.example.com:80/ >> Restart Docker: >> $ sudo systemctl restart docker >> >> -----Original Message----- >> From: Hu, Yong [mailto:yong.hu at intel.com] >> Sent: 2018年7月4日 15:15 >> To: Arce Moreno, Abraham ; Scott Little >> ; starlingx-discuss at lists.starlingx.io >> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , >> mock package missing >> >> Hi Abraham, >> Did you run "build-pkgs" or "build-pkgs --serial"? >> If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. >> 13:42:03 Failed to build packages: >> memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm >> python-2.7.5-58.el7.tis.3.src.rpm >> >> In the meantime, @Zhipeng is following steps in >> https://wiki.openstack.org/wiki/StarlingX/Developer_Guide >> >> On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" wrote: >> >> > > > > It will be great if someone else could take our Developer Guide >> > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide >> > > > > and build the ISO from scratch. >> > >> > Yeah, we will have someone to do the exercise based on this guide. Pls stay >> > tuned. >> >> Cool! Thank you! >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Thu Jul 12 16:20:22 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 12 Jul 2018 16:20:22 +0000 Subject: [Starlingx-discuss] Notes / summary of today's build system call Message-ID: <9A85D2917C58154C960D95352B22818BAB56064C@fmsmsx117.amr.corp.intel.com> We had a call today to discuss build system issues. The Notes are here: https://etherpad.openstack.org/p/stx-status. The problem statement is that the current build is not stable, as the import mirror has been hard to set up for just about everyone and needs to be changed on a daily basis as packages are changed upstream. In the short term Bruce & Brent will look into hosting options for an external (shared) import mirror. In the long term, Saul will lead an effort to see if we can leverage https://openbuildservice.org/. Mario and Erich will join in, with Scott and Jason. This is the most important work going on right now, so please keep us all updated and to ask for any help needed early and often. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Jul 12 18:18:17 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 12 Jul 2018 18:18:17 +0000 Subject: [Starlingx-discuss] RFC: Project Priorities Message-ID: <9A85D2917C58154C960D95352B22818BAB5606C8@fmsmsx117.amr.corp.intel.com> We had an internal meeting yesterday to discuss project priorities. I'd like to share our list with the community, get feedback, and submit this as input to the Architect call next Thursday. This list is also available on https://etherpad.openstack.org/p/stx-planning, which I propose we use as the master for this discussion. brucej Project Priorities ============= 1. Build stability & mirror cache / improvements 2. Basic processes & infrastructure e.g. CI/CD, Test/Validation, Releases, Dev, Bug handling, Security, Devstack, Zuul tests, unit tests, etc.... 3. Documentation e.g. project map, how to contribute, how to build/install, how to run, how to debug, .... 4. Distro management - build, updates, automation, etc... We believe these four items are needed for StarlingX to be a viable project and to recruit & retain contributors, users and operators. 5. KPI establishment, test automation and on-going improvements The value of StarlingX is in the high level of performance and robustness it provides. Setting KPIs and improving them over time is critical. 6. Reduce patch backlog - openstack and non-openstack The patch backlog is something no one likes. The Intel team has the lead on this but on-going assistance from Wind River will be needed (e.g. to help write upstream Specs). There are many opportunities to re-architect the system to more closely align it with upstream communities. 7. Containerized OpenStack services and support for containerized workloads We believe this is a key feature for the product. Wind River has the lead on this work. 8. Networking features (containerized VNFs, ONAP integration, TSN, ...) High performance and fully featured networking is another key value of StarlingX. Adding containerized VNFs, supporting ONAP and Time Senstive Networking enable important use cases for the project. 9. Intel-specific features: SGX, EPID, integrations with Intel platforms and software Intel will have the lead on this work. We expect that other vendor requirements will emerge as the community grows. 10. Python 3 readiness 11. Operating System independence These are both long term goals that we can start working towards gradually. Python 2 support will be gone in a few years. We have already had multiple requests for supporting other Host operating systems and we expect that to continue. Moving in toward OS independence means de-coupling the services from the OS which makes the services themselves easier to work on and more interesting for other projects and communities to use. This will get easier the more OS patches we get upstream. From bruce.e.jones at intel.com Thu Jul 12 20:37:24 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 12 Jul 2018 20:37:24 +0000 Subject: [Starlingx-discuss] FIrst release branch In-Reply-To: <9A85D2917C58154C960D95352B22818BAB55F0A2@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB55F0A2@fmsmsx117.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB5607BE@fmsmsx117.amr.corp.intel.com> Erick, the kernel changes are in. Can you please pull this branch and see if you can get a build to complete? brucej From: Jones, Bruce E Sent: Monday, July 9, 2018 10:03 PM To: Cardona Ruiz, Erick Cc: starlingx-discuss at lists.starlingx.io Subject: FIrst release branch As previously discussed on this list, we have agreed to move to a quarterly release model with monthly branches. I proposed pulling monthly branches the 2nd week of each month. And now it's the 2nd week of the month. It's time to pull our first monthly branch. It should be called "stx.2018.07" and it should not be created until the latest kernel updates are complete. Unless those updates aren't in by Thursday, because we're going to pull the branch this week regardless. Erick, can you write a script that creates a branch, and (once the kernel changes are in or Friday happens), run it and pull the branch and kick off a build? The story and tasks are in https://storyboard.openstack.org/#!/story/2002923. Which I can't assign to you. Do you have an OpenStack ID? Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Thu Jul 12 21:22:31 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Thu, 12 Jul 2018 21:22:31 +0000 Subject: [Starlingx-discuss] RFC: Project Priorities In-Reply-To: <9A85D2917C58154C960D95352B22818BAB5606C8@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB5606C8@fmsmsx117.amr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0D2133@ALA-MBD.corp.ad.wrs.com> Bruce, I have added some initial comments and new items to the etherpad. More to come Brent -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, July 12, 2018 2:18 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] RFC: Project Priorities We had an internal meeting yesterday to discuss project priorities. I'd like to share our list with the community, get feedback, and submit this as input to the Architect call next Thursday. This list is also available on https://etherpad.openstack.org/p/stx-planning, which I propose we use as the master for this discussion. brucej Project Priorities ============= 1. Build stability & mirror cache / improvements 2. Basic processes & infrastructure e.g. CI/CD, Test/Validation, Releases, Dev, Bug handling, Security, Devstack, Zuul tests, unit tests, etc.... 3. Documentation e.g. project map, how to contribute, how to build/install, how to run, how to debug, .... 4. Distro management - build, updates, automation, etc... We believe these four items are needed for StarlingX to be a viable project and to recruit & retain contributors, users and operators. 5. KPI establishment, test automation and on-going improvements The value of StarlingX is in the high level of performance and robustness it provides. Setting KPIs and improving them over time is critical. 6. Reduce patch backlog - openstack and non-openstack The patch backlog is something no one likes. The Intel team has the lead on this but on-going assistance from Wind River will be needed (e.g. to help write upstream Specs). There are many opportunities to re-architect the system to more closely align it with upstream communities. 7. Containerized OpenStack services and support for containerized workloads We believe this is a key feature for the product. Wind River has the lead on this work. 8. Networking features (containerized VNFs, ONAP integration, TSN, ...) High performance and fully featured networking is another key value of StarlingX. Adding containerized VNFs, supporting ONAP and Time Senstive Networking enable important use cases for the project. 9. Intel-specific features: SGX, EPID, integrations with Intel platforms and software Intel will have the lead on this work. We expect that other vendor requirements will emerge as the community grows. 10. Python 3 readiness 11. Operating System independence These are both long term goals that we can start working towards gradually. Python 2 support will be gone in a few years. We have already had multiple requests for supporting other Host operating systems and we expect that to continue. Moving in toward OS independence means de-coupling the services from the OS which makes the services themselves easier to work on and more interesting for other projects and communities to use. This will get easier the more OS patches we get upstream. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Brent.Rowsell at windriver.com Thu Jul 12 21:29:43 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Thu, 12 Jul 2018 21:29:43 +0000 Subject: [Starlingx-discuss] Plan for stx-gui Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0D2142@ALA-MBD.corp.ad.wrs.com> Reposting. Does anyone have this on their to do list ? Brent From: Rowsell, Brent Sent: Wednesday, July 4, 2018 3:43 PM To: starlingx-discuss at lists.starlingx.io Subject: Plan for stx-gui What is the current plan for stx-gui ? It is currently not being pulled into the load and the StarlingX specific panels are still in stx-horizon. Brent -------------- next part -------------- An HTML attachment was scrubbed... URL: From eddie.ramirez at intel.com Thu Jul 12 21:56:06 2018 From: eddie.ramirez at intel.com (Ramirez, Eddie) Date: Thu, 12 Jul 2018 21:56:06 +0000 Subject: [Starlingx-discuss] Plan for stx-gui Message-ID: Hi Brent, sorry I missed this email last week. Short answer: No, it’s not currently being pulled into the building pipeline just yet. I’m trying workarounds to get it working with the last version of Pike. Most of problems I run into are related to changes done to non-panels files like core classes, functions and settings that make STX specific functionality possible. I’m few steps away from trying these changes in the build process as I’m working on a dev environment and following the standard installation process of installing a Horizon plugin, that is, using the upstream horizon release and importing the package stx-gui into the namespace. From: "Rowsell, Brent" Date: Thursday, July 12, 2018 at 2:29 PM To: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Plan for stx-gui Reposting. Does anyone have this on their to do list ? Brent From: Rowsell, Brent Sent: Wednesday, July 4, 2018 3:43 PM To: starlingx-discuss at lists.starlingx.io Subject: Plan for stx-gui What is the current plan for stx-gui ? It is currently not being pulled into the load and the StarlingX specific panels are still in stx-horizon. Brent -------------- next part -------------- An HTML attachment was scrubbed... URL: From abraham.arce.moreno at intel.com Fri Jul 13 00:28:36 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Fri, 13 Jul 2018 00:28:36 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <57c9ce60-2092-ef82-198b-6bfb87a425f9@windriver.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <57c9ce60-2092-ef82-198b-6bfb87a425f9@windriver.com> Message-ID: > build-pkgs will by default run in parallel mode.  This means two things, a > different build order than the serial build, and the possibility that earlier > packages built in a different mock environment.  It likely works in a serial > build because an earlier package has a "Require: X" where X is shadow-utils or > something that depends on shadow-utils.  Since we reuse the mock > environment rather than clearing it after each package (faster builds), the > shadow-utils package is available for later packages and might allow then to > get away with a missing dependency. > > The real solution is to add 'Requires: shadow-utils' to the spec file of the > package that breaks. In one round of compilation I saw more than 20 packages failing due to this missing shadow-utils dependency so several changes might be required. Let me add some other packages are failing due to another missing dependency: rpm-build. Only 2 for now so far seen in my setup. > Adding it via modify-build-cfg was based on the theory (unconfirmed) that > @buildsys-build macro has been redefined on newer CentOS systems and > shadow-utils has been dropped from the set of packages that @buildsys-build > maps to.  It seems like a quicker way to enable folks, rather than adding > 'Requires: shadow-utils' to potemtially a lot of packages. Agree! Since we are reusing this mock environment, I am in favor to add via modify-build-cfg. From abraham.arce.moreno at intel.com Fri Jul 13 00:31:00 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Fri, 13 Jul 2018 00:31:00 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> Message-ID: > I just found, In https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > The step 5 of "Download Source Code Repositories" has to be modified due > to a patch of stx-manifest.git merged yesterday. > https://review.openstack.org/#/c/580170/ Thanks Yi! Changes has been made to https://wiki.openstack.org/wiki/StarlingX/Developer_Guide ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/ From abraham.arce.moreno at intel.com Fri Jul 13 00:39:18 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Fri, 13 Jul 2018 00:39:18 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> Message-ID: Thanks ZhipengS! > When I run below step > $ docker build -t user:centos-mirror-repository -f Dockerfile . > It mentioned > Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting > for connection > > It can work after following below steps. > =========================================================== > Here is a link to the official docker doc for proxy > http:https://docs.docker.com/engine/admin/systemd/#http-proxy > A quick outline: > First, create a systemd drop-in directory for the docker service: > mkdir /etc/systemd/system/docker.service.d > Now create a file called /etc/systemd/system/docker.service.d/http- > proxy.conf that adds the HTTP_PROXY environment variable: > [Service] > Environment="HTTP_PROXY=http://proxy.example.com:80/" > If you have internal Docker registries that you need to contact without > proxying you can specify them via the NO_PROXY environment variable: > Environment="HTTP_PROXY=http://proxy.example.com:80/" > Environment="NO_PROXY=localhost,127.0.0.0/8,docker- > registry.somecorporation.com" > Flush changes: > $ sudo systemctl daemon-reload > Verify that the configuration has been loaded: > $ sudo systemctl show --property Environment docker > Environment=HTTP_PROXY=http://proxy.example.com:80/ > Restart Docker: > $ sudo systemctl restart docker I have add the url for this, your post, as a reference under https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Software_Requirements We will leave the hard work to change references using best tech writing guidelines to our experts. From abraham.arce.moreno at intel.com Fri Jul 13 01:15:39 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Fri, 13 Jul 2018 01:15:39 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> Message-ID: Thanks Yong! > One more comment to this guide: > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > We might have to add a session to update initial images, *if kernel or device > modules are modified*. In you experience, how would we identify this "update initial images" is required? Are we having a specific error saying the image is not found and take it as a trigger? Can we make this a default process to follow? We have the following steps under the same guide, are they still meaningful? Should they be replaced by the steps you have shared? Mirror Binaries $ mkdir -p $HOME/starlingx/mirror/CentOS/tis-installer $ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/images/pxeboot/initrd.img $HOME/starlingx/mirror/CentOS/tis-installer/initrd.img-stx-0.2 $ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/images/pxeboot/vmlinuz $HOME/starlingx/mirror/CentOS/tis-installer/vmlinuz-stx-0.2 $ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/LiveOS/squashfs.img $HOME/starlingx/mirror/CentOS/tis-installer/squashfs.img-stx-0.2 > Here are steps: > 1). Run command: $ update-pxe-network-installer After this is done, there > should be 3 new files (vmlinuz, initrd.img and squashfs.img) generated in: > $BUILD_FOLDER/pxe-network-installer/output > 2). copy these 3 files into mirror “/import/mirrors/CentOS/tis-installer/” and > put appropriate postfix. Note, the new info (images with the postfix) need to > updated accordingly in in “build_srpm.data” and “pxe-network- > installer.spec” under “cgcs-root/addons/wr-cgcs/layers/cgcs/mwa- > beas/installer/pxe-network-installer/centos/” > 3). re-build pkgs and iso: (no need to make a clean build) These are our building steps: $ cd $MY_WORKSPACE $ build-pkgs --serial $ generate-cgcs-tis-repo $ build-srpms --installer $ build-rpms --installer $ build-iso Where do you suggest we add the "update initial images" process? From abraham.arce.moreno at intel.com Fri Jul 13 01:21:53 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Fri, 13 Jul 2018 01:21:53 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> Message-ID: Thanks ZhipengS! > When I followed your guide, there are 3 issues I found. > > 1) We need change mock.cfg.proto file as below [TisCentos7Distro] name=Tis- > Centos-7-Distro > enabled=1 > baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary > // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found. Scott's reply annotated. On hold, waiting for more comments. https://storyboard.openstack.org/#!/story/2002939 > 2) In Download Source Code Repositories step of the guide. > cgcs-dl > $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ > $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads > // change to > $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ > $MY_REPO/stx/ Done! https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Download_Source_Code_Repositories > 3) lighttpd not started by default in build container, and also could not > started manually. > > =============================================================== > Raised below 2 stories. > 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto > 2002938 lighttpd not started by default in build container https://storyboard.openstack.org/#!/story/2002938 From abraham.arce.moreno at intel.com Fri Jul 13 01:23:49 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Fri, 13 Jul 2018 01:23:49 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <93814834B4855241994F290E959305C752F48FA8@SHSMSX104.ccr.corp.intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> <9d889c66-a603-2d12-dd70-c8fb3b3911d0@windriver.com> <93814834B4855241994F290E959305C752F48CC6@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48FA8@SHSMSX104.ccr.corp.intel.com> Message-ID: Thanks again ZhipengS! > We'd better add > 3rd-centos_rpms_missing_L1.txt to below as well > ======================================== > Verify Packages > 1.Verify there are no missing or failed packages: > # cat output/3rd_rpms_missing_L1.txt output/3rd_srpms_missing_L1.txt > output/centos_rpms_missing_L1.txt output/centos_srpms_missing_L1.txt > ======================================== Added! https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Verify_Packages From abraham.arce.moreno at intel.com Fri Jul 13 01:39:44 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Fri, 13 Jul 2018 01:39:44 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <93814834B4855241994F290E959305C752F49046@SHSMSX104.ccr.corp.intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> <9d889c66-a603-2d12-dd70-c8fb3b3911d0@windriver.com> <93814834B4855241994F290E959305C752F48CC6@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48FA8@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F49046@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi ZhipengS, > After I add missing RPMS, build still failed as below. However, with the mirror > I built, the build in our old build environment is ongoing normally. Important to get your feedback on the activities asked to be executed by Scott and Yong. > 23:40:14 Start: chroot init > 23:40:14 INFO: calling preinit hooks > 23:40:14 INFO: enabled root cache > 23:40:14 INFO: enabled yum cache > 23:40:14 Start: cleaning yum metadata > 23:40:14 Finish: cleaning yum metadata > 23:40:14 INFO: enabled HW Info plugin > 23:40:14 Mock Version: 1.4.11 > 23:40:14 INFO: Mock Version: 1.4.11 > 23:40:14 Start: yum install > 23:40:14 Finish: yum install > 23:40:14 ERROR: > Exception(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis- > extensions-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) 0 > minutes 2 seconds > 23:40:14 INFO: Results and/or logs in: > /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx-tis-r5- > pike-std/tis-extensions-1.0-2.tis > 23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? > 23:40:14 End build: You are hitting " ERROR: Could not find useradd in chroot, maybe the install failed?" Information is spread among the different messages under thread: "[Starlingx-discuss] build-pkgs: package built failed , mock package missing" http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000125.html http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000129.html http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000206.html In summary, to pass this and other dependency issue during build-pkgs is by adding - shadow-utils - rpm-build to modify-build-cfg under build-tools diff --git a/build-tools/modify-build-cfg b/build-tools/modify-build-cfg ... -grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 yum'" $FILE || \ - echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum'" >> $FILE +grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 yum shadow-utils rpm-build'" $FILE || \ + echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum shadow-utils rpm-build'" >> $FILE From Ken.Young at windriver.com Fri Jul 13 01:52:46 2018 From: Ken.Young at windriver.com (Young, Ken) Date: Fri, 13 Jul 2018 01:52:46 +0000 Subject: [Starlingx-discuss] [stx-tools] New Kernel Version In-Reply-To: <836ECC37-2443-427F-92D1-61CC96EA14EE@intel.com> References: <839B019D-3E5A-48ED-A2E5-3B49ABDF40B4@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0C939C@ALA-MBD.corp.ad.wrs.com> <4BF83FBF-6E76-41A4-8E61-360D252C7FCF@intel.com> <98D9C69F-A421-4149-BC69-EFE07FB67EE0@intel.com> <25398361-E529-4DF7-BD02-1F994B9E6511@windriver.com> <56CE6087-AF0A-48B7-BF11-DEC1156197C6@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0CB692@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C76553375DF@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765533765F@SHSMSX101.ccr.corp.intel.com> <836ECC37-2443-427F-92D1-61CC96EA14EE@intel.com> Message-ID: <4223339C-19CB-41AB-91FA-608C08F95215@windriver.com> Erich, The new 862.6.3 kernel has been merged. I am interested in an answer to the question below: What testing has been done with 862.6.3 ? Are there artifacts for the testing of the new kernel? Was there a system regression test performed? Was system level KPIs measured? /KenY On 2018-07-10, 12:59 PM, "Cordoba Malibran, Erich" wrote: As upgrading kernel will be a frequent task, I would like to follow on this question > What testing has been done with 862.6.3 ? I your experience, what would be the best test scenario for a kernel upgrade? Thanks -Erich On 7/9/18, 9:41 PM, "Lin, Shuicheng" wrote: Hi all, Here is the review link for kernel update to 862.6.3. https://review.openstack.org/#/c/580308/ https://review.openstack.org/#/c/580897/ Best Regards Shuicheng -----Original Message----- From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, July 10, 2018 10:20 AM To: Rowsell, Brent ; Hu, Yong ; Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Hi Brent, We have gone through basic deploy test in both bare metal and virtual machine case, and doing sanity test now. We also try to verify the updated driver package with the corresponding HW. Best Regards Shuicheng -----Original Message----- From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Monday, July 9, 2018 7:06 PM To: Hu, Yong ; Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version What testing has been done with 862.6.3 ? Brent -----Original Message----- From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Saturday, July 7, 2018 9:17 PM To: Young, Ken ; Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version On top of these patches, does anyone has concerns to upgrade kernel to the latest 862.6.3?? BTW, from security perspective, CVE-2018-8897 was updated on 862.3.2 and CVE-2018-3665 was on 862.3.3. ====================================================== POP SS (CVE-2018-8897) – Done on May 8 [Software Only Fix] CentOS6.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022827.html 2. Speculative Store Bypass Disable (SSBD) (CVE-2018-3639) – Done on May 21 [Software+Microcode Fix] CentOS6.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022835.html CentOS7.X: https://lists.centos.org/pipermail/centos-announce/2018-May/022843.html kernel-3.10.0-862.3.2.el7 3. Lazy FP State Restore (CVE-2018-3665) – Done on June 13 [Software only Fix] - CentOS7.X: https://lists.centos.org/pipermail/centos-announce/2018-June/022923.html kernel-3.10.0-862.3.3.el7 ======================================================= From: "Young, Ken" Date: Friday, 6 July 2018 at 11:58 PM To: "Hu, Yong" , "Rowsell, Brent" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version The reviews for the updated kernel are here: https://review.openstack.org/#/c/580688/ https://review.openstack.org/580689 https://review.openstack.org/580690 https://review.openstack.org/580692 /KenY From: Ken Young Date: Friday, July 6, 2018 at 9:42 AM To: YONG HU , "Rowsell, Brent" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version See inline. From: YONG HU Date: Thursday, July 5, 2018 at 10:18 PM To: "Rowsell, Brent" , Ken Young , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Hi Ken, >>> we have a kernel update to 862.3.2 >>> We will work to get our updated kernel in ASAP Did you mean WRS has already been working on upgrade to 862.3.2? Yes. We had already migrated to this kernel to enable our kubernetes efforts. The kernel contained capabilities we needed. Could you please post the activities and progress here in this mailing list, so that we all are aware of it? We are planning to put the 862.3.2 into the openstack repos today. Regards, Yong From: "Hu, Yong" Date: Friday, 6 July 2018 at 9:14 AM To: "Rowsell, Brent" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Makes sense! Do we intend/agree to apply this rule on all new features or big changes (though practically how we gate the granularity of changes?)? Regards, Yong From: "Rowsell, Brent" Date: Friday, 6 July 2018 at 8:58 AM To: "Hu, Yong" , "Young, Ken" , "starlingx-discuss at lists.starlingx.io" Subject: RE: [Starlingx-discuss] [stx-tools] New Kernel Version Going forward, I would recommend pending upgrades be posted to the mailing list before the reviews are actually submitted. Brent From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Thursday, July 5, 2018 8:56 PM To: Young, Ken ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version Hi Ken, We might need a sync-up on this kernel upgrade topic. Actually, moving forward, I would suggest, if there are any big changes to come, we both sides need to inform each other in advance, to avoid duplications or conflicts. Regards, Yong From: "Young, Ken" Date: Friday, 6 July 2018 at 12:21 AM To: "mailto:starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [stx-tools] New Kernel Version I discovered 2 new reviews this morning which are security related this morning: https://review.openstack.org/#/c/580287/ https://review.openstack.org/#/c/580308/ These reviews propose to merge the latest CentOS kernel 862.6.3 to address the latest Spectre / Meltdown CVEs. Before this is completed, we have a kernel update to 862.3.2 we would like to merge which includes module updates to enable containers which we would like to get in first. Otherwise, this will generate a significant amount of rework for these submissions. The easiest path is to follow the kernels in order. We will work to get our updated kernel in ASAP. Thank you in advance. Regards, Ken Y _______________________________________________ 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 abraham.arce.moreno at intel.com Fri Jul 13 02:01:49 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Fri, 13 Jul 2018 02:01:49 +0000 Subject: [Starlingx-discuss] the downloading script for tarballs in "wr-cgcs/layers/cgcs/downloads/"? In-Reply-To: <21FDAF41-CE5E-4FAF-B92E-83F11ECFF0D5@intel.com> References: <21FDAF41-CE5E-4FAF-B92E-83F11ECFF0D5@intel.com> Message-ID: Thanks Yi, Yong, > @Abraham, never mind, I got it. “!” doesn’t mean “comment out”, but for > “special handling” ☺ Correct! More information about our downloads directory: https://review.openstack.org/#/c/577953/5//COMMIT_MSG Some rework is needed as highlighted by Dean, see History from Gerrit Review. https://review.openstack.org/#/c/577953/ From zhipengs.liu at intel.com Fri Jul 13 02:09:28 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Fri, 13 Jul 2018 02:09:28 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <738B5DAD-15A1-404C-A65C-952A699A1D98@intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> <9d889c66-a603-2d12-dd70-c8fb3b3911d0@windriver.com> <93814834B4855241994F290E959305C752F48CC6@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48FA8@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F49046@SHSMSX104.ccr.corp.intel.com> <93bfa378-9f26-d4c8-8f37-ad23a543e756@windriver.com> <738B5DAD-15A1-404C-A65C-952A699A1D98@intel.com> Message-ID: <93814834B4855241994F290E959305C752F496DD@SHSMSX104.ccr.corp.intel.com> Hi Yong and Abraham Mingyuan asked me checked comps.xml yesterday, it didn't exist. I also could not create it through executing generate-cgcs-centos-repo.sh. Zhipeng -----Original Message----- From: Hu, Yong Sent: 2018年7月12日 23:47 To: Scott Little ; Liu, ZhipengS ; Qi, Mingyuan ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Zhipeng, It looks the local repo in your build environment is not correct. You can check if "~/cgcs-root/cgcs-centos-repo/Binary/comps.xml" exists. If no, you need to recreate "cgcs-centos-repo" with the latest version of "stx-tools/toCOPY/generate-cgcs-centos-repo.sh" to assure: 1. the folder structure in "~/cgcs-root/cgcs-centos-repo/Binary/" is correct 2. "~/cgcs-root/cgcs-centos-repo/Binary/comps.xml" does exist Regards, Yong On 12/07/2018, 8:36 AM, "Scott Little" wrote: For more details, examine the log files in this directory ... /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx-tis-r5-pike-std/tis-extensions-1.0-2.tis/ On 18-07-12 11:13 AM, Liu, ZhipengS wrote: > Hi Scott and Abraham, > > After I add missing RPMS, build still failed as below. However, with the mirror I built, > the build in our old build environment is ongoing normally. > > 23:40:14 Start: chroot init > 23:40:14 INFO: calling preinit hooks > 23:40:14 INFO: enabled root cache > 23:40:14 INFO: enabled yum cache > 23:40:14 Start: cleaning yum metadata > 23:40:14 Finish: cleaning yum metadata > 23:40:14 INFO: enabled HW Info plugin > 23:40:14 Mock Version: 1.4.11 > 23:40:14 INFO: Mock Version: 1.4.11 > 23:40:14 Start: yum install > 23:40:14 Finish: yum install > 23:40:14 ERROR: Exception(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis-extensions-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) 0 minutes 2 seconds > 23:40:14 INFO: Results and/or logs in: /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx-tis-r5-pike-std/tis-extensions-1.0-2.tis > 23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? > 23:40:14 End build: /localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis-extensions-1.0-2.tis.src.rpm > 23:40:14 Error building tis-extensions-1.0-2.tis.src.rpm. > 23:40:14 Will try to build again (if some other package will succeed). > 23:40:14 Start build: /localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm > 23:40:14 building tpm2-openssl-engine-1.0-2.tis.src.rpm > 23:40:18 INFO: mock.py version 1.4.11 starting (python version = 2.7.5)... > 23:40:18 Start: init plugins > 23:40:18 INFO: selinux disabled > 23:40:18 Finish: init plugins > 23:40:18 Start: run > 23:40:18 INFO: Start(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) > > BRs > zhipeng > > > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: 2018年7月12日 21:33 > To: Qi, Mingyuan ; Scott Little ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Thanks Mingyuan! > Some RPM exactly missing. > > Hi Abraham, > > We'd better add > 3rd-centos_rpms_missing_L1.txt to below as well > ======================================== > Verify Packages > 1.Verify there are no missing or failed packages: > # cat output/3rd_rpms_missing_L1.txt output/3rd_srpms_missing_L1.txt output/centos_rpms_missing_L1.txt output/centos_srpms_missing_L1.txt > ======================================== > > Thanks! > Zhipeng > > -----Original Message----- > From: Qi, Mingyuan > Sent: 2018年7月12日 14:38 > To: Liu, ZhipengS ; Scott Little ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Zhipeng, > > The failure is due to your mirror package missing, such as python, nss-softokn3... so that mock init failed at the beginning. > Could you check whether packages in rpms_from_centos_3rd_parties.lst are totally downloaded? > > Thanks, > Mingyuan > > > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: Thursday, July 12, 2018 9:45 > To: Scott Little ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Thanks Little! > We also found it should be OK that sed used later yesterday. > > Before we changed this place, we could not build any RPM. > It always gave out errors like below > 15:13:50 Error: Package: python-urlgrabber-3.10-8.el7.noarch (TisCentos7Distro) > 15:13:50 Requires: /usr/bin/python > 15:13:50 Error: Package: nss-3.28.4-1.2.el7_3.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libsoftokn3.so()(64bit) > 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libfreebl3.so(NSSRAWHASH_3.12.3)(64bit) > 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libelf.so.1()(64bit) > 15:13:50 Error: Package: krb5-libs-1.15.1-19.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libcom_err.so.2()(64bit) > 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libelf.so.1(ELFUTILS_1.0)(64bit) > 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) ........ > > After changed this place, no this issue found anymore, but another error we saw all the time. > 19:30:45 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. > 19:30:45 http://127.0.0.1:8088/MY_REPO/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found > > Zhipeng > > -----Original Message----- > From: Scott Little [mailto:scott.little at windriver.com] > Sent: 2018年7月11日 23:49 > To: Liu, ZhipengS ; Hu, Yong ; Arce Moreno, Abraham ; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > You shouldn't have to do that. > > The mock.cfg.proto file is processed by the modify-build-cfg script. You should see it using sed to substitute "MY_REPO_DIR" with $MY_REPO. > > There might be weaknesses elsewhere in the build process where it attempts to determine if modify-build-cfg should be re-run. e.g. I don't think we test for changes to environment variables between runs. > > Scott > > > On 18-07-11 04:14 AM, Liu, ZhipengS wrote: >> Hi Abraham, >> >> When I followed your guide, there are 3 issues I found. >> >> 1) We need change mock.cfg.proto file as below [TisCentos7Distro] >> name=Tis-Centos-7-Distro >> enabled=1 >> baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary >> // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found. >> >> 2) In Download Source Code Repositories step of the guide. >> cgcs-dl >> $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ >> $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads >> // change to >> $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ >> $MY_REPO/stx/ >> >> 3) lighttpd not started by default in build container, and also could not started manually. >> >> =============================================================== >> Raised below 2 stories. >> 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto >> 2002938 lighttpd not started by default in build container >> >> >> BRs >> zhipeng >> -----Original Message----- >> From: Liu, ZhipengS >> Sent: 2018年7月5日 11:14 >> To: Hu, Yong ; Arce Moreno, Abraham >> ; Scott Little >> ; starlingx-discuss at lists.starlingx.io >> Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , >> mock package missing >> >> Hi Abraham, >> >> When I run below step >> $ docker build -t user:centos-mirror-repository -f Dockerfile . >> It mentioned >> Get https://registry-1.docker.io/v2/: net/http: request canceled while >> waiting for connection >> >> It can work after following below steps. >> =========================================================== >> Here is a link to the official docker doc for proxy >> http:https://docs.docker.com/engine/admin/systemd/#http-proxy >> A quick outline: >> First, create a systemd drop-in directory for the docker service: >> mkdir /etc/systemd/system/docker.service.d >> Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: >> [Service] >> Environment="HTTP_PROXY=http://proxy.example.com:80/" >> If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: >> Environment="HTTP_PROXY=http://proxy.example.com:80/" >> Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" >> Flush changes: >> $ sudo systemctl daemon-reload >> Verify that the configuration has been loaded: >> $ sudo systemctl show --property Environment docker >> Environment=HTTP_PROXY=http://proxy.example.com:80/ >> Restart Docker: >> $ sudo systemctl restart docker >> >> -----Original Message----- >> From: Hu, Yong [mailto:yong.hu at intel.com] >> Sent: 2018年7月4日 15:15 >> To: Arce Moreno, Abraham ; Scott Little >> ; starlingx-discuss at lists.starlingx.io >> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , >> mock package missing >> >> Hi Abraham, >> Did you run "build-pkgs" or "build-pkgs --serial"? >> If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. >> 13:42:03 Failed to build packages: >> memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm >> python-2.7.5-58.el7.tis.3.src.rpm >> >> In the meantime, @Zhipeng is following steps in >> https://wiki.openstack.org/wiki/StarlingX/Developer_Guide >> >> On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" wrote: >> >> > > > > It will be great if someone else could take our Developer Guide >> > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide >> > > > > and build the ISO from scratch. >> > >> > Yeah, we will have someone to do the exercise based on this guide. Pls stay >> > tuned. >> >> Cool! Thank you! >> >> >> _______________________________________________ >> 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 zhipengs.liu at intel.com Fri Jul 13 02:35:04 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Fri, 13 Jul 2018 02:35:04 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> <9d889c66-a603-2d12-dd70-c8fb3b3911d0@windriver.com> <93814834B4855241994F290E959305C752F48CC6@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48FA8@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F49046@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C752F49726@SHSMSX104.ccr.corp.intel.com> Hi Araham, I changed modify-build-cfg according to your below solution, below issue fixed > 23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? Now, RPM build is ongoing normally, and I can see some "Success building". Thank you so much! BRs zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月13日 9:40 To: Liu, ZhipengS ; Qi, Mingyuan ; Scott Little ; Hu, Yong ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Hi ZhipengS, > After I add missing RPMS, build still failed as below. However, with > the mirror I built, the build in our old build environment is ongoing normally. Important to get your feedback on the activities asked to be executed by Scott and Yong. > 23:40:14 Start: chroot init > 23:40:14 INFO: calling preinit hooks > 23:40:14 INFO: enabled root cache > 23:40:14 INFO: enabled yum cache > 23:40:14 Start: cleaning yum metadata > 23:40:14 Finish: cleaning yum metadata > 23:40:14 INFO: enabled HW Info plugin > 23:40:14 Mock Version: 1.4.11 > 23:40:14 INFO: Mock Version: 1.4.11 > 23:40:14 Start: yum install > 23:40:14 Finish: yum install > 23:40:14 ERROR: > Exception(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/t > is- > extensions-1.0-2.tis.src.rpm) > Config(zhipengl-starlingx-tis-r5-pike-std/mock) 0 minutes 2 seconds > 23:40:14 INFO: Results and/or logs in: > /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx > -tis-r5- > pike-std/tis-extensions-1.0-2.tis > 23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? > 23:40:14 End build: You are hitting " ERROR: Could not find useradd in chroot, maybe the install failed?" Information is spread among the different messages under thread: "[Starlingx-discuss] build-pkgs: package built failed , mock package missing" http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000125.html http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000129.html http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000206.html In summary, to pass this and other dependency issue during build-pkgs is by adding - shadow-utils - rpm-build to modify-build-cfg under build-tools diff --git a/build-tools/modify-build-cfg b/build-tools/modify-build-cfg ... -grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 yum'" $FILE || \ - echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum'" >> $FILE +grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 yum shadow-utils rpm-build'" $FILE || \ + echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum shadow-utils rpm-build'" >> $FILE From cindy.xie at intel.com Fri Jul 13 02:53:42 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Fri, 13 Jul 2018 02:53:42 +0000 Subject: [Starlingx-discuss] Notes / summary of today's build system call In-Reply-To: <9A85D2917C58154C960D95352B22818BAB56064C@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB56064C@fmsmsx117.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B2D8EFC@SHSMSX104.ccr.corp.intel.com> Bruce, Brent, Hosting an external (shared) mirror is good to align the build environment btw Intel and WR. However, as we still have the build server hosted behind company's firewall, we still need to synchronize external mirror with our internal build environment. The part I am not sure is: any concern of re-distributing RH signed RPM in a public mirror? Or shall we re-sign it using our key if we patch it? Thx. - cindy From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Friday, July 13, 2018 12:20 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Notes / summary of today's build system call We had a call today to discuss build system issues. The Notes are here: https://etherpad.openstack.org/p/stx-status. The problem statement is that the current build is not stable, as the import mirror has been hard to set up for just about everyone and needs to be changed on a daily basis as packages are changed upstream. In the short term Bruce & Brent will look into hosting options for an external (shared) import mirror. In the long term, Saul will lead an effort to see if we can leverage https://openbuildservice.org/. Mario and Erich will join in, with Scott and Jason. This is the most important work going on right now, so please keep us all updated and to ask for any help needed early and often. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From abraham.arce.moreno at intel.com Fri Jul 13 03:53:38 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Fri, 13 Jul 2018 03:53:38 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <93814834B4855241994F290E959305C752F496DD@SHSMSX104.ccr.corp.intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> <9d889c66-a603-2d12-dd70-c8fb3b3911d0@windriver.com> <93814834B4855241994F290E959305C752F48CC6@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48FA8@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F49046@SHSMSX104.ccr.corp.intel.com> <93bfa378-9f26-d4c8-8f37-ad23a543e756@windriver.com> <738B5DAD-15A1-404C-A65C-952A699A1D98@intel.com> <93814834B4855241994F290E959305C752F496DD@SHSMSX104.ccr.corp.intel.com> Message-ID: > Mingyuan asked me checked comps.xml yesterday, it didn't exist. > I also could not create it through executing generate-cgcs-centos-repo.sh. Thanks Zhipeng, Mingyuan, Understood about the problem. Yong and Erich were talking a few days ago internally about the way to handle comps.xml and they suggested a minimal xml so time to bring this conversation out. How about this first version [0]? If it is possible for you to test and see if we can start taking this as our base file. [0] https://pastebin.com/KMB8QLNX From bruce.e.jones at intel.com Fri Jul 13 04:37:51 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 13 Jul 2018 04:37:51 +0000 Subject: [Starlingx-discuss] Notes / summary of today's build system call In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B2D8EFC@SHSMSX104.ccr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB56064C@fmsmsx117.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2D8EFC@SHSMSX104.ccr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB560ABF@fmsmsx117.amr.corp.intel.com> I met with Arjan tonight. The Clear Linux team has an external yum repo they use for builds. I'm meeting with them in the morning US time to see if we can use the same approach. brucej From: Xie, Cindy Sent: Thursday, July 12, 2018 7:54 PM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: Notes / summary of today's build system call Bruce, Brent, Hosting an external (shared) mirror is good to align the build environment btw Intel and WR. However, as we still have the build server hosted behind company's firewall, we still need to synchronize external mirror with our internal build environment. The part I am not sure is: any concern of re-distributing RH signed RPM in a public mirror? Or shall we re-sign it using our key if we patch it? Thx. - cindy From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Friday, July 13, 2018 12:20 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Notes / summary of today's build system call We had a call today to discuss build system issues. The Notes are here: https://etherpad.openstack.org/p/stx-status. The problem statement is that the current build is not stable, as the import mirror has been hard to set up for just about everyone and needs to be changed on a daily basis as packages are changed upstream. In the short term Bruce & Brent will look into hosting options for an external (shared) import mirror. In the long term, Saul will lead an effort to see if we can leverage https://openbuildservice.org/. Mario and Erich will join in, with Scott and Jason. This is the most important work going on right now, so please keep us all updated and to ask for any help needed early and often. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Jul 13 05:03:22 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 13 Jul 2018 05:03:22 +0000 Subject: [Starlingx-discuss] RFC: Project Priorities In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB0D2133@ALA-MBD.corp.ad.wrs.com> References: <9A85D2917C58154C960D95352B22818BAB5606C8@fmsmsx117.amr.corp.intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0D2133@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB560C14@fmsmsx117.amr.corp.intel.com> Thank you Brent, your changes look good. brucej -----Original Message----- From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Thursday, July 12, 2018 2:23 PM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: RFC: Project Priorities Bruce, I have added some initial comments and new items to the etherpad. More to come Brent -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, July 12, 2018 2:18 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] RFC: Project Priorities We had an internal meeting yesterday to discuss project priorities. I'd like to share our list with the community, get feedback, and submit this as input to the Architect call next Thursday. This list is also available on https://etherpad.openstack.org/p/stx-planning, which I propose we use as the master for this discussion. brucej Project Priorities ============= 1. Build stability & mirror cache / improvements 2. Basic processes & infrastructure e.g. CI/CD, Test/Validation, Releases, Dev, Bug handling, Security, Devstack, Zuul tests, unit tests, etc.... 3. Documentation e.g. project map, how to contribute, how to build/install, how to run, how to debug, .... 4. Distro management - build, updates, automation, etc... We believe these four items are needed for StarlingX to be a viable project and to recruit & retain contributors, users and operators. 5. KPI establishment, test automation and on-going improvements The value of StarlingX is in the high level of performance and robustness it provides. Setting KPIs and improving them over time is critical. 6. Reduce patch backlog - openstack and non-openstack The patch backlog is something no one likes. The Intel team has the lead on this but on-going assistance from Wind River will be needed (e.g. to help write upstream Specs). There are many opportunities to re-architect the system to more closely align it with upstream communities. 7. Containerized OpenStack services and support for containerized workloads We believe this is a key feature for the product. Wind River has the lead on this work. 8. Networking features (containerized VNFs, ONAP integration, TSN, ...) High performance and fully featured networking is another key value of StarlingX. Adding containerized VNFs, supporting ONAP and Time Senstive Networking enable important use cases for the project. 9. Intel-specific features: SGX, EPID, integrations with Intel platforms and software Intel will have the lead on this work. We expect that other vendor requirements will emerge as the community grows. 10. Python 3 readiness 11. Operating System independence These are both long term goals that we can start working towards gradually. Python 2 support will be gone in a few years. We have already had multiple requests for supporting other Host operating systems and we expect that to continue. Moving in toward OS independence means de-coupling the services from the OS which makes the services themselves easier to work on and more interesting for other projects and communities to use. This will get easier the more OS patches we get upstream. _______________________________________________ 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 Jul 13 22:06:19 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 13 Jul 2018 22:06:19 +0000 Subject: [Starlingx-discuss] Build and import mirror strategy Message-ID: <9A85D2917C58154C960D95352B22818BAB5613EF@fmsmsx117.amr.corp.intel.com> I've made a bit of progress today on how we might improve our handling of the import mirror and improve our builds. If you look at the Clear Linux project (https://clearlinux.org/), they have solved the same problem we are trying to solve. So what I would propose Is that the Intel team take the lead of putting together a proposal to create a StarlingX build environment that leverages tools, practices and processes from Clear Linux. We have people on our team who are already familiar with those tools and with Clear Linux. This is a medium-to-long term solution. Even if we re-use all the methods, docs and tools, getting it all working for us will take a while. No progress yet on a short term solution. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Jul 13 22:29:39 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 13 Jul 2018 22:29:39 +0000 Subject: [Starlingx-discuss] FIrst release branch In-Reply-To: <9A85D2917C58154C960D95352B22818BAB5607BE@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB55F0A2@fmsmsx117.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB5607BE@fmsmsx117.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB561465@fmsmsx117.amr.corp.intel.com> Did this branch get created today? From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, July 12, 2018 1:37 PM To: Cardona Ruiz, Erick Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] FIrst release branch Erick, the kernel changes are in. Can you please pull this branch and see if you can get a build to complete? brucej From: Jones, Bruce E Sent: Monday, July 9, 2018 10:03 PM To: Cardona Ruiz, Erick > Cc: starlingx-discuss at lists.starlingx.io Subject: FIrst release branch As previously discussed on this list, we have agreed to move to a quarterly release model with monthly branches. I proposed pulling monthly branches the 2nd week of each month. And now it's the 2nd week of the month. It's time to pull our first monthly branch. It should be called "stx.2018.07" and it should not be created until the latest kernel updates are complete. Unless those updates aren't in by Thursday, because we're going to pull the branch this week regardless. Erick, can you write a script that creates a branch, and (once the kernel changes are in or Friday happens), run it and pull the branch and kick off a build? The story and tasks are in https://storyboard.openstack.org/#!/story/2002923. Which I can't assign to you. Do you have an OpenStack ID? Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From erick.cardona.ruiz at intel.com Fri Jul 13 22:46:47 2018 From: erick.cardona.ruiz at intel.com (Cardona Ruiz, Erick) Date: Fri, 13 Jul 2018 22:46:47 +0000 Subject: [Starlingx-discuss] FIrst release branch In-Reply-To: <9A85D2917C58154C960D95352B22818BAB561465@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB55F0A2@fmsmsx117.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB5607BE@fmsmsx117.amr.corp.intel.com>, <9A85D2917C58154C960D95352B22818BAB561465@fmsmsx117.amr.corp.intel.com> Message-ID: <4706113BCD6C07449D1494B0F0932FEA52797039@FMSMSX103.amr.corp.intel.com> Hi Bruce, Sure, I just need permissions in order to create the branches. I'll follow Dean's proposed process (based on some strategies of the openstack release process, specified here: https://docs.openstack.org/infra/manual/drivers.html). -Erick ________________________________ From: Jones, Bruce E Sent: Friday, July 13, 2018 5:29 PM To: Cardona Ruiz, Erick Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: FIrst release branch Did this branch get created today? From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, July 12, 2018 1:37 PM To: Cardona Ruiz, Erick Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] FIrst release branch Erick, the kernel changes are in. Can you please pull this branch and see if you can get a build to complete? brucej From: Jones, Bruce E Sent: Monday, July 9, 2018 10:03 PM To: Cardona Ruiz, Erick > Cc: starlingx-discuss at lists.starlingx.io Subject: FIrst release branch As previously discussed on this list, we have agreed to move to a quarterly release model with monthly branches. I proposed pulling monthly branches the 2nd week of each month. And now it’s the 2nd week of the month. It’s time to pull our first monthly branch. It should be called “stx.2018.07” and it should not be created until the latest kernel updates are complete. Unless those updates aren’t in by Thursday, because we’re going to pull the branch this week regardless. Erick, can you write a script that creates a branch, and (once the kernel changes are in or Friday happens), run it and pull the branch and kick off a build? The story and tasks are in https://storyboard.openstack.org/#!/story/2002923. Which I can’t assign to you. Do you have an OpenStack ID? Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Jul 13 22:51:09 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 13 Jul 2018 22:51:09 +0000 Subject: [Starlingx-discuss] FIrst release branch In-Reply-To: <4706113BCD6C07449D1494B0F0932FEA52797039@FMSMSX103.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB55F0A2@fmsmsx117.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB5607BE@fmsmsx117.amr.corp.intel.com>, <9A85D2917C58154C960D95352B22818BAB561465@fmsmsx117.amr.corp.intel.com> <4706113BCD6C07449D1494B0F0932FEA52797039@FMSMSX103.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB56148E@fmsmsx117.amr.corp.intel.com> @Dean how do we get Erick the right permissions? From: Cardona Ruiz, Erick Sent: Friday, July 13, 2018 3:47 PM To: Jones, Bruce E Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: FIrst release branch Hi Bruce, Sure, I just need permissions in order to create the branches. I'll follow Dean's proposed process (based on some strategies of the openstack release process, specified here: https://docs.openstack.org/infra/manual/drivers.html). -Erick ________________________________ From: Jones, Bruce E Sent: Friday, July 13, 2018 5:29 PM To: Cardona Ruiz, Erick Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: FIrst release branch Did this branch get created today? From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, July 12, 2018 1:37 PM To: Cardona Ruiz, Erick > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] FIrst release branch Erick, the kernel changes are in. Can you please pull this branch and see if you can get a build to complete? brucej From: Jones, Bruce E Sent: Monday, July 9, 2018 10:03 PM To: Cardona Ruiz, Erick > Cc: starlingx-discuss at lists.starlingx.io Subject: FIrst release branch As previously discussed on this list, we have agreed to move to a quarterly release model with monthly branches. I proposed pulling monthly branches the 2nd week of each month. And now it's the 2nd week of the month. It's time to pull our first monthly branch. It should be called "stx.2018.07" and it should not be created until the latest kernel updates are complete. Unless those updates aren't in by Thursday, because we're going to pull the branch this week regardless. Erick, can you write a script that creates a branch, and (once the kernel changes are in or Friday happens), run it and pull the branch and kick off a build? The story and tasks are in https://storyboard.openstack.org/#!/story/2002923. Which I can't assign to you. Do you have an OpenStack ID? Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Sat Jul 14 01:04:14 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Sat, 14 Jul 2018 01:04:14 +0000 Subject: [Starlingx-discuss] Plan for stx-gui In-Reply-To: References: Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0D3955@ALA-MBD.corp.ad.wrs.com> Thanks Eddie. Do you have a forecast when your changes will be done ? Reason I am asking is we have some changes that will need to go into stx-gui. Thanks, Brent From: Ramirez, Eddie [mailto:eddie.ramirez at intel.com] Sent: Thursday, July 12, 2018 5:56 PM To: Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Plan for stx-gui Hi Brent, sorry I missed this email last week. Short answer: No, it’s not currently being pulled into the building pipeline just yet. I’m trying workarounds to get it working with the last version of Pike. Most of problems I run into are related to changes done to non-panels files like core classes, functions and settings that make STX specific functionality possible. I’m few steps away from trying these changes in the build process as I’m working on a dev environment and following the standard installation process of installing a Horizon plugin, that is, using the upstream horizon release and importing the package stx-gui into the namespace. From: "Rowsell, Brent" > Date: Thursday, July 12, 2018 at 2:29 PM To: "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] Plan for stx-gui Reposting. Does anyone have this on their to do list ? Brent From: Rowsell, Brent Sent: Wednesday, July 4, 2018 3:43 PM To: starlingx-discuss at lists.starlingx.io Subject: Plan for stx-gui What is the current plan for stx-gui ? It is currently not being pulled into the load and the StarlingX specific panels are still in stx-horizon. Brent -------------- next part -------------- An HTML attachment was scrubbed... URL: From yi.c.wang at intel.com Mon Jul 16 07:47:29 2018 From: yi.c.wang at intel.com (Wang, Yi C) Date: Mon, 16 Jul 2018 07:47:29 +0000 Subject: [Starlingx-discuss] patch merge approach for starlingx-staging projects ? Message-ID: Hi all, Considering in some case, like security bug fixing , we still need to make some patches for starlingx-staging projects. Do we have a proposed patch merge approach for them? Thanks. BR Yi -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Mon Jul 16 15:04:34 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Mon, 16 Jul 2018 10:04:34 -0500 Subject: [Starlingx-discuss] patch merge approach for starlingx-staging projects ? In-Reply-To: References: Message-ID: On Mon, Jul 16, 2018 at 2:47 AM, Wang, Yi C wrote: > Considering in some case, like security bug fixing , we still need to make > some patches for starlingx-staging projects. Do we have a proposed patch > merge approach for them? Thanks. It is basically the same process, submit a PR, get at least 2 core +2s and merge it. However, merging things into those repos has a higher bar, at least for anything that should be upstreamed (making our tests run for example are not in this category). Backports of existing upstream work are easier to justify as is anything new that is also accompanied by an upstream review. dt -- Dean Troyer dtroyer at gmail.com From bruce.e.jones at intel.com Mon Jul 16 17:52:09 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 16 Jul 2018 17:52:09 +0000 Subject: [Starlingx-discuss] Agenda open for Wednesday's weekly call Message-ID: <9A85D2917C58154C960D95352B22818BAB56241F@fmsmsx117.amr.corp.intel.com> The agenda for this week's StarlingX call is open. If you have topics you'd like to raise please add them. Please update https://etherpad.openstack.org/p/stx-status to add your topics. Thanks! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Mon Jul 16 17:52:12 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 16 Jul 2018 17:52:12 +0000 Subject: [Starlingx-discuss] Agenda for this week's Core team call Message-ID: <9A85D2917C58154C960D95352B22818BAB56242F@fmsmsx117.amr.corp.intel.com> The agenda for this week's StarlingX Core team call is open. If you have topics you'd like to raise please add them. Please update https://etherpad.openstack.org/p/stx-cores to add your topics. Thanks! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Mon Jul 16 18:21:52 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 16 Jul 2018 18:21:52 +0000 Subject: [Starlingx-discuss] Adding packages to build .lst files Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F3A9@ALA-MBD.corp.ad.wrs.com> Hi folks, We've got some packages to add to the build, and I'm wondering if there's some description of the various .lst files in stxtools/centos-mirror-tools. For example, how do you decide whether a package is listed in rpms_from_centos_repo.lst vs rpms_from_centos_3rd_parties.lst? I started writing a script to pull together a list of the dependencies based on Requires and BuildRequires. As I understand it, we need to add all such dependencies, recursively, to these .lst files. Using the StarlingX.repo config file as an arg to repoquery, I get some packages overlapping with rpms_from_centos_3rd_parties.lst, however, so I'm hoping there's some clear direction with these files. My script is finding hundreds of rpms to add to rpms_from_centos_repo.lst with its calls to repoquery to resolve the dependencies, so either I've got lots of overlap and many of these need to go to the 3rdparty file, my repoquery approach for automating this is completely wrong, or these new packages are using a completely different set of dependencies for the builds than anything else we've got. I've attached the first draft of my script for anyone that's curious. Thanks, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: starlingx_add_pkgs.sh Type: application/octet-stream Size: 2268 bytes Desc: starlingx_add_pkgs.sh URL: From yi.c.wang at intel.com Tue Jul 17 00:44:11 2018 From: yi.c.wang at intel.com (Wang, Yi C) Date: Tue, 17 Jul 2018 00:44:11 +0000 Subject: [Starlingx-discuss] patch merge approach for starlingx-staging projects ? In-Reply-To: References: Message-ID: Thanks Dean. One more question. Who are in the list of core of starlingx-staging projects? Thanks. Yi -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Monday, July 16, 2018 11:05 PM To: Wang, Yi C Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] patch merge approach for starlingx-staging projects ? On Mon, Jul 16, 2018 at 2:47 AM, Wang, Yi C wrote: > Considering in some case, like security bug fixing , we still need to > make some patches for starlingx-staging projects. Do we have a > proposed patch merge approach for them? Thanks. It is basically the same process, submit a PR, get at least 2 core +2s and merge it. However, merging things into those repos has a higher bar, at least for anything that should be upstreamed (making our tests run for example are not in this category). Backports of existing upstream work are easier to justify as is anything new that is also accompanied by an upstream review. dt -- Dean Troyer dtroyer at gmail.com From fernando.hernandez.gonzalez at intel.com Mon Jul 16 22:54:22 2018 From: fernando.hernandez.gonzalez at intel.com (Hernandez Gonzalez, Fernando) Date: Mon, 16 Jul 2018 22:54:22 +0000 Subject: [Starlingx-discuss] Design and Documentation for our Starlingx/Release Plan Web Page. Message-ID: <03D458D5BAFF6041973594B00B4E58CE590EABB4@fmsmsx101.amr.corp.intel.com> Hi Team, Last Friday 13th we discussed our first draft about how are we going to release our builds in our Starlingx/Release Plan official page. Please take a look into this first proposal, our first approach is releasing something clean and neat, comments and suggestions are well welcome, more things can be added/removed if necessary. AR All, I have an Action Request for every Stx pioneer who would like to be in the Release Team (basically would be Point of Contact regarding Release plan matters, currently we have Thanks Mario for help me out with this first draft) Please look at the text below for web page explanation. For those who are more visual people see attached image. StarlingX/Release Plan List of releases Describing Current Table Version Link should be something like https://git.stx.com/stx.2018.08.0x.tar.gz: containing: · .tar, .img, .iso, or wathever is decided. · Rpms, srpm. · Debug keys - if apply. · Packages. Remark: at the end something similar like Clearlinux.org deploys Clearlinux Link Docs or Release Notes Link should re direct you to the Release notes Web Page containing at least: · Version link. · Freeze code Date. · Major features list. · List of Code Changes - higher level. · Validation done against the build. e.g. "This build has been validated with Sanity test " Remark: where git repo link redirect to test cases folder stored in git. · Known issues. Same comments apply for Future Table. Management of releases Release cadence and Schedule Releases are published in a time based fashion: · Every Long Term period with quarterly updates. · Every Quarterly with monthly updates. Monthly release · Each month in the 2nd week of the month a branch will be pulled. · Branch name format stx.YY.MM.patch# e.g. stx.2018.08.0x (where "0x" is a patch number) Quarterly release · 2nd month in the quarter. · For each quarterly release, the code freeze for that release is the 2nd week in the 2nd month in the quarter. Long Team release · TBD Support length · Quarterly releases are supported for 6 months. · Long Term releases are out of plan so far. Release team · Visit the release team page Release Plan Page Out of Scope list. **Remark: our current plan marked below items out of scope and based on the project needs it could be added. We want to start with something simple. · Web Page containing Stx Details of Release Schedule. o Detail Schedule with feature freeze, figure it out bug handling, known issues for the release, point to backlog in the future, what will be fixed, etc. [cid:image002.png at 01D41D26.755B7DC0] · Branch support length should be in Dev doc. · IRC, [Starlingx-discuss] channel is in the Starlingx main page. · Release/build announcements will be in the Starlingx main page. · Starlingx Technical Committee should be in Starlingx main page or Dev doc. Thanks. Fernando Hernandez Gonzalez Software Engineer Avenida del Bosque #1001 Col, El Bajío Zapopan, Jalisco MX, 45019 ____________________________________ Office: +52.33.16.45.01.34 inet 86450134 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.emz Type: application/octet-stream Size: 29046 bytes Desc: image001.emz URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 37050 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: oledata.mso Type: application/octet-stream Size: 37769 bytes Desc: oledata.mso URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: StxRelPlanDraft_V1.0.png Type: image/png Size: 233820 bytes Desc: StxRelPlanDraft_V1.0.png URL: From shuicheng.lin at intel.com Tue Jul 17 02:04:55 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 17 Jul 2018 02:04:55 +0000 Subject: [Starlingx-discuss] Design and Documentation for our Starlingx/Release Plan Web Page. In-Reply-To: <03D458D5BAFF6041973594B00B4E58CE590EABB4@fmsmsx101.amr.corp.intel.com> References: <03D458D5BAFF6041973594B00B4E58CE590EABB4@fmsmsx101.amr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C765533A8D0@SHSMSX101.ccr.corp.intel.com> Hi Fernando, I guess "Long Team release" should be "Long Term release". :) Best Regards Shuicheng From: Hernandez Gonzalez, Fernando [mailto:fernando.hernandez.gonzalez at intel.com] Sent: Tuesday, July 17, 2018 6:54 AM To: 'starlingx-discuss at lists.starlingx.io' Cc: Troyer, Dean Subject: [Starlingx-discuss] Design and Documentation for our Starlingx/Release Plan Web Page. Hi Team, Last Friday 13th we discussed our first draft about how are we going to release our builds in our Starlingx/Release Plan official page. Please take a look into this first proposal, our first approach is releasing something clean and neat, comments and suggestions are well welcome, more things can be added/removed if necessary. AR All, I have an Action Request for every Stx pioneer who would like to be in the Release Team (basically would be Point of Contact regarding Release plan matters, currently we have Thanks Mario for help me out with this first draft) Please look at the text below for web page explanation. For those who are more visual people see attached image. StarlingX/Release Plan List of releases Describing Current Table Version Link should be something like https://git.stx.com/stx.2018.08.0x.tar.gz: containing: · .tar, .img, .iso, or wathever is decided. · Rpms, srpm. · Debug keys - if apply. · Packages. Remark: at the end something similar like Clearlinux.org deploys Clearlinux Link Docs or Release Notes Link should re direct you to the Release notes Web Page containing at least: · Version link. · Freeze code Date. · Major features list. · List of Code Changes - higher level. · Validation done against the build. e.g. "This build has been validated with Sanity test " Remark: where git repo link redirect to test cases folder stored in git. · Known issues. Same comments apply for Future Table. Management of releases Release cadence and Schedule Releases are published in a time based fashion: · Every Long Term period with quarterly updates. · Every Quarterly with monthly updates. Monthly release · Each month in the 2nd week of the month a branch will be pulled. · Branch name format stx.YY.MM.patch# e.g. stx.2018.08.0x (where "0x" is a patch number) Quarterly release · 2nd month in the quarter. · For each quarterly release, the code freeze for that release is the 2nd week in the 2nd month in the quarter. Long Team release · TBD Support length · Quarterly releases are supported for 6 months. · Long Term releases are out of plan so far. Release team · Visit the release team page Release Plan Page Out of Scope list. **Remark: our current plan marked below items out of scope and based on the project needs it could be added. We want to start with something simple. · Web Page containing Stx Details of Release Schedule. o Detail Schedule with feature freeze, figure it out bug handling, known issues for the release, point to backlog in the future, what will be fixed, etc. [cid:image003.png at 01D41DB5.9BE96F80] · Branch support length should be in Dev doc. · IRC, [Starlingx-discuss] channel is in the Starlingx main page. · Release/build announcements will be in the Starlingx main page. · Starlingx Technical Committee should be in Starlingx main page or Dev doc. Thanks. Fernando Hernandez Gonzalez Software Engineer Avenida del Bosque #1001 Col, El Bajío Zapopan, Jalisco MX, 45019 ____________________________________ Office: +52.33.16.45.01.34 inet 86450134 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 37050 bytes Desc: image003.png URL: From hazzim.i.anaya.casas at intel.com Tue Jul 17 14:06:17 2018 From: hazzim.i.anaya.casas at intel.com (Anaya casas, Hazzim I) Date: Tue, 17 Jul 2018 14:06:17 +0000 Subject: [Starlingx-discuss] Design and Documentation for our Starlingx/Release Plan Web Page. In-Reply-To: <03D458D5BAFF6041973594B00B4E58CE590EABB4@fmsmsx101.amr.corp.intel.com> References: <03D458D5BAFF6041973594B00B4E58CE590EABB4@fmsmsx101.amr.corp.intel.com> Message-ID: <614A117A-E61F-4812-AFDE-4028C9F6DC42@intel.com> Hi Fernando, count me in to be in release team. Regards. On Jul 16, 2018, at 17:54, Hernandez Gonzalez, Fernando > wrote: Hi Team, Last Friday 13th we discussed our first draft about how are we going to release our builds in our Starlingx/Release Plan official page. Please take a look into this first proposal, our first approach is releasing something clean and neat, comments and suggestions are well welcome, more things can be added/removed if necessary. AR All, I have an Action Request for every Stx pioneer who would like to be in the Release Team (basically would be Point of Contact regarding Release plan matters, currently we have Thanks Mario for help me out with this first draft) Please look at the text below for web page explanation. For those who are more visual people see attached image. Thanks. Fernando Hernandez Gonzalez Software Engineer Avenida del Bosque #1001 Col, El Bajío Zapopan, Jalisco MX, 45019 ____________________________________ Office: +52.33.16.45.01.34 inet 86450134 _______________________________________________ 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 Tue Jul 17 14:19:21 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 17 Jul 2018 14:19:21 +0000 Subject: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches Message-ID: <151EE31B9FCCA54397A757BC674650F0BA31892F@ALA-MBD.corp.ad.wrs.com> As discussed in last Wednesday's meeting, I have updated the StarlingX wiki with the tracking proposal below: https://wiki.openstack.org/wiki/StarlingX#Meetings I've also added a [Test] prefix for test-related work items. I have updated all stories with prefixes. If I mislabeled something, please feel free to fix as you see fit. Regards, Ghada -----Original Message----- From: Khalil, Ghada Sent: Tuesday, July 10, 2018 6:22 PM To: starlingx-discuss at lists.starlingx.io Subject: Proposal to use prefixes in Story Board to ease searches Hello, With the increased number of active stories in StartlingX, I'd like to propose that we consistently use a set of prefixes to make it easier to search and find work items. Suggested Prefixes: [Bug] A problem which impairs or prevents the functionality of StarlingX [Enhancement] An improvement or enhancement to the functionality of StartingX Typically smaller scope items [Feature] A new feature/functionality to be added to StarlingX Ideally, the scope should fit within a release time-frame (ex: 3-6 months) [Build] Build tools, environment, repo organization, etc [Process] Process and project related work items [Doc] Documentation related work items [Upstreaming] Work items that need to be pushed in the core openstack projects [Help] Request for assistance / help ** Others can be added as long as we agree on a manageable set. Sample Queries: - Active Features https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Feature - Active Bugs https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Bug I would also like to explore using worklists for larger project initiatives which would potentially span multiple features/releases. Example: [Initiative] Containerized Openstack Example: [Initiative] StarlingX Project Re-structuring Does anyone know how to scope worklists and boards to the StarlingX project group only? Any feedback is welcome. Regards, Ghada Ghada Khalil, Manager, Titanium Cloud, Wind River direct 613.270.2273  skype ghada.khalil.ottawa 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 From ildiko.vancsa at gmail.com Tue Jul 17 14:54:13 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 17 Jul 2018 07:54:13 -0700 Subject: [Starlingx-discuss] Berlin Summit CFP closes in less than 24 hours!! Message-ID: Hi, It is a friendly reminder that the Berlin CFP closes at 11:59pm Pacific Time / 0659 UTC. You can submit your talk/panel/workshop proposal here: https://www.openstack.org/summit/berlin-2018/call-for-presentations/ Please let me know if you have any questions or if you need any help. Thanks and Best Regards, Ildikó From scott.little at windriver.com Tue Jul 17 15:07:19 2018 From: scott.little at windriver.com (Scott Little) Date: Tue, 17 Jul 2018 11:07:19 -0400 Subject: [Starlingx-discuss] Restructuring round 2 Message-ID: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> Story: https://storyboard.openstack.org/#!/story/2002801 *Goals:* 1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils 2) Restructure the directories under which packages are to be found. Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense.  stx-utils is just i mess of stuff that never found a home when StarlingX was first set up. Directories should descriptive of the class of packages to be found within. Intent is to preserve update history as best is is possible. *Timeline: * Probably around July 23 unless there are strong objections.  We should probably have a freeze on submissions to the affected repos until it is all completed. *Code Reviews: * Most of this is just moving code around.  A few path corrections, but no new code.  The number and size of the reviews will be huge, and the code should all have been inspected once before.  Is there a way to fast track this?  Would there be strong objections to me just doing a +2/+1 without waiting for independent review? *Details of directories/groups ...* Create new directories under stx-integ (logical groupings for files):    ceph    config    config-files    database    filesystem    filesystem/drbd    grub    kernel    kernel/kernel-modules    ldap    logging    strorage-drivers    tools    utilities    virt Retained directories under stx-integ (additional logical groupings for files):    base    mellanox    monitoring    networking    python    restapi-doc    security Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire):    connectivity    core    devtools    extended    support *Details of packages ...* Relocated packages (internal to stx-integ):    base/       dhcp       initscripts       libevent       lighttpd       memcached       net-snmp       novnc       ntp       openssh       pam       procps       sanlock       shadow       sudo       systemd       util-linux       vim       watchdog    ceph/       python-cephclient    config/       e2fsprogs       facter       nfs-utils       nfscheck       puppet-4.8.2       puppet-modules    kernel/       kernel-std       kernel-rt    kernel/kernel-modules/       mlnx-ofa_kernel    ldap/       nss-pam-ldapd       openldap    logging/       syslog-ng       logrotate    networking/       lldpd       iproute       mellanox       python-ryu       mlx4-config    python/       python-2.7.5       python-django       python-gunicorn       python-setuptools       python-smartpm    security/       shim-signed       shim-unsigned       tboot    strorage-drivers/       python-3parclient       python-lefthandclient    virt/       cloud-init       libvirt       libvirt-python       qemu    tools/       storage-topology       vm-topology    utilities/       tis-extensions       namespace-utils       nova-utils       update-motd Relocated packages (stx-utils to stx-update):     enable-dev-patch Relocated packages (stx-utils to stx-integ):     config-files/         io-scheduler     filesystem/         filesystem-scripts     grub/         grubby     logging/         logmgmt     tools/         collector         monitor-tools     tools/engtools/         hostdata-collectors         parsers     utilities/         build-info         branding   (formerly wrs-branding)         platform-util Relocated packages (stx-gpl2 to stx-integ):     base/         bash         cgcs-users         cluster-resource-agents         dpkg         haproxy         libfdt         netpbm         rpm     database/         mariadb     filesystem/         iscsi-initiator-utils     filesystem/drbd/         drbd-tools     kernel/kernel-modules/         drbd         integrity         intel-e1000e         intel-i40e         intel-i40evf         intel-ixgbe         intel-ixgbevf         qat17         tpmdd     ldap/         ldapscripts     networking/         iptables         net-tools Relocated packages (stx-gpl3 to stx-integ):     base/         anaconda         crontabs         dnsmasq         rsync     database/         python-psycopg2     filesystem/         parted     grub/         grub2     security/         python-keyring Delete two packages from stx-integ:    tgt    irqbalance Delete two packages from stx-gplv3:    seabios    sysvinit Delete one package from stx-utils:    io-monitor -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cordoba.malibran at intel.com Tue Jul 17 15:54:17 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 17 Jul 2018 15:54:17 +0000 Subject: [Starlingx-discuss] Restructuring round 2 In-Reply-To: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> References: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> Message-ID: <795D2371-83B9-4562-9854-8C331BB1978C@intel.com> Hi Scott, Thanks for the info. There's something I would like to bring into the discussion of the consolidation. It has started a discussion on what infrastructure we need to have a CI of StarlingX and an evaluation on OBS (openbuildservice) and Koji has started. Taking that in mind I'm wondering how this consolidation can help/affect to adapt the StarlingX building Into one of these infrastructures, as far as I recall, both solutions requires to have a repository per rpm. What are your thoughts on this? Thanks -Erich From: Scott Little Date: Tuesday, July 17, 2018 at 10:08 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Restructuring round 2 Story: https://storyboard.openstack.org/#!/story/2002801 Goals: 1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils 2) Restructure the directories under which packages are to be found.  Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense.  stx-utils is just i mess of stuff that never found a home when StarlingX was first set up. Directories should descriptive of the class of packages to be found within. Intent is to preserve update history as best is is possible. Timeline:  Probably around July 23 unless there are strong objections.  We should probably have a freeze on submissions to the affected repos until it is all completed. Code Reviews:  Most of this is just moving code around.  A few path corrections, but no new code.  The number and size of the reviews will be huge, and the code should all have been inspected once before.  Is there a way to fast track this?  Would there be strong objections to me just doing a +2/+1 without waiting for independent review? Details of directories/groups ... Create new directories under stx-integ (logical groupings for files):    ceph    config    config-files    database    filesystem    filesystem/drbd    grub    kernel    kernel/kernel-modules    ldap    logging    strorage-drivers    tools    utilities    virt Retained directories under stx-integ (additional logical groupings for files):    base    mellanox    monitoring    networking    python    restapi-doc    security Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire):    connectivity    core    devtools    extended    support Details of packages ... Relocated packages (internal to stx-integ):    base/       dhcp       initscripts       libevent       lighttpd       memcached       net-snmp       novnc       ntp       openssh       pam       procps       sanlock       shadow       sudo       systemd       util-linux       vim       watchdog    ceph/       python-cephclient    config/       e2fsprogs       facter       nfs-utils       nfscheck       puppet-4.8.2       puppet-modules    kernel/       kernel-std       kernel-rt    kernel/kernel-modules/       mlnx-ofa_kernel    ldap/       nss-pam-ldapd       openldap    logging/       syslog-ng       logrotate    networking/       lldpd       iproute       mellanox       python-ryu       mlx4-config    python/       python-2.7.5       python-django       python-gunicorn       python-setuptools       python-smartpm    security/       shim-signed       shim-unsigned       tboot    strorage-drivers/       python-3parclient       python-lefthandclient    virt/       cloud-init       libvirt       libvirt-python       qemu    tools/       storage-topology       vm-topology    utilities/       tis-extensions       namespace-utils       nova-utils       update-motd Relocated packages (stx-utils to stx-update):     enable-dev-patch Relocated packages (stx-utils to stx-integ):     config-files/         io-scheduler     filesystem/         filesystem-scripts     grub/         grubby     logging/         logmgmt     tools/         collector         monitor-tools     tools/engtools/         hostdata-collectors         parsers         utilities/         build-info         branding   (formerly wrs-branding)         platform-util Relocated packages (stx-gpl2 to stx-integ):     base/         bash         cgcs-users         cluster-resource-agents         dpkg         haproxy         libfdt         netpbm         rpm     database/         mariadb     filesystem/         iscsi-initiator-utils     filesystem/drbd/         drbd-tools     kernel/kernel-modules/         drbd         integrity         intel-e1000e         intel-i40e         intel-i40evf         intel-ixgbe         intel-ixgbevf         qat17         tpmdd     ldap/         ldapscripts     networking/         iptables         net-tools Relocated packages (stx-gpl3 to stx-integ):     base/         anaconda         crontabs         dnsmasq         rsync     database/         python-psycopg2     filesystem/         parted     grub/         grub2     security/         python-keyring Delete two packages from stx-integ:    tgt    irqbalance Delete two packages from stx-gplv3:    seabios    sysvinit Delete one package from stx-utils:    io-monitor From Brent.Rowsell at windriver.com Tue Jul 17 16:05:20 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Tue, 17 Jul 2018 16:05:20 +0000 Subject: [Starlingx-discuss] Restructuring round 2 In-Reply-To: <795D2371-83B9-4562-9854-8C331BB1978C@intel.com> References: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> <795D2371-83B9-4562-9854-8C331BB1978C@intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0D8339@ALA-MBD.corp.ad.wrs.com> I think the build system alternatives question is independent of this initiative and probably does not impact +/-. Brent -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Tuesday, July 17, 2018 11:54 AM To: Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Restructuring round 2 Hi Scott, Thanks for the info. There's something I would like to bring into the discussion of the consolidation. It has started a discussion on what infrastructure we need to have a CI of StarlingX and an evaluation on OBS (openbuildservice) and Koji has started. Taking that in mind I'm wondering how this consolidation can help/affect to adapt the StarlingX building Into one of these infrastructures, as far as I recall, both solutions requires to have a repository per rpm. What are your thoughts on this? Thanks -Erich From: Scott Little Date: Tuesday, July 17, 2018 at 10:08 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Restructuring round 2 Story: https://storyboard.openstack.org/#!/story/2002801 Goals: 1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils 2) Restructure the directories under which packages are to be found. Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense.  stx-utils is just i mess of stuff that never found a home when StarlingX was first set up. Directories should descriptive of the class of packages to be found within. Intent is to preserve update history as best is is possible. Timeline: Probably around July 23 unless there are strong objections.  We should probably have a freeze on submissions to the affected repos until it is all completed. Code Reviews: Most of this is just moving code around.  A few path corrections, but no new code.  The number and size of the reviews will be huge, and the code should all have been inspected once before.  Is there a way to fast track this?  Would there be strong objections to me just doing a +2/+1 without waiting for independent review? Details of directories/groups ... Create new directories under stx-integ (logical groupings for files):    ceph    config    config-files    database    filesystem    filesystem/drbd    grub    kernel    kernel/kernel-modules    ldap    logging    strorage-drivers    tools    utilities    virt Retained directories under stx-integ (additional logical groupings for files):    base    mellanox    monitoring    networking    python    restapi-doc    security Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire):    connectivity    core    devtools    extended    support Details of packages ... Relocated packages (internal to stx-integ):    base/       dhcp       initscripts       libevent       lighttpd       memcached       net-snmp       novnc       ntp       openssh       pam       procps       sanlock       shadow       sudo       systemd       util-linux       vim       watchdog    ceph/       python-cephclient    config/       e2fsprogs       facter       nfs-utils       nfscheck       puppet-4.8.2       puppet-modules    kernel/       kernel-std       kernel-rt    kernel/kernel-modules/       mlnx-ofa_kernel    ldap/       nss-pam-ldapd       openldap    logging/       syslog-ng       logrotate    networking/       lldpd       iproute       mellanox       python-ryu       mlx4-config    python/       python-2.7.5       python-django       python-gunicorn       python-setuptools       python-smartpm    security/       shim-signed       shim-unsigned       tboot    strorage-drivers/       python-3parclient       python-lefthandclient    virt/       cloud-init       libvirt       libvirt-python       qemu    tools/       storage-topology       vm-topology    utilities/       tis-extensions       namespace-utils       nova-utils       update-motd Relocated packages (stx-utils to stx-update):     enable-dev-patch Relocated packages (stx-utils to stx-integ):     config-files/         io-scheduler     filesystem/         filesystem-scripts     grub/         grubby     logging/         logmgmt     tools/         collector         monitor-tools     tools/engtools/         hostdata-collectors         parsers         utilities/         build-info         branding   (formerly wrs-branding)         platform-util Relocated packages (stx-gpl2 to stx-integ):     base/         bash         cgcs-users         cluster-resource-agents         dpkg         haproxy         libfdt         netpbm         rpm     database/         mariadb     filesystem/         iscsi-initiator-utils     filesystem/drbd/         drbd-tools     kernel/kernel-modules/         drbd         integrity         intel-e1000e         intel-i40e         intel-i40evf         intel-ixgbe         intel-ixgbevf         qat17         tpmdd     ldap/         ldapscripts     networking/         iptables         net-tools Relocated packages (stx-gpl3 to stx-integ):     base/         anaconda         crontabs         dnsmasq         rsync     database/         python-psycopg2     filesystem/         parted     grub/         grub2     security/         python-keyring Delete two packages from stx-integ:    tgt    irqbalance Delete two packages from stx-gplv3:    seabios    sysvinit Delete one package from stx-utils:    io-monitor _______________________________________________ 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 Tue Jul 17 16:15:16 2018 From: scott.little at windriver.com (Scott Little) Date: Tue, 17 Jul 2018 12:15:16 -0400 Subject: [Starlingx-discuss] Restructuring round 2 In-Reply-To: <795D2371-83B9-4562-9854-8C331BB1978C@intel.com> References: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> <795D2371-83B9-4562-9854-8C331BB1978C@intel.com> Message-ID: Important subjects that I want to participate in, but I think that's a subject for a different thread.  Long term solutions, versus a short term need to get WindRiver converged onto StarlingX. For now, we'd like to get a rational directory structure.  Subdivision of current gits into per-package gits can happen later if that's the path we choose. Scott On 18-07-17 11:54 AM, Cordoba Malibran, Erich wrote: > Hi Scott, > > Thanks for the info. There's something I would like to bring into the discussion of the consolidation. > It has started a discussion on what infrastructure we need to have a CI of StarlingX and an evaluation on > OBS (openbuildservice) and Koji has started. > > Taking that in mind I'm wondering how this consolidation can help/affect to adapt the StarlingX building > Into one of these infrastructures, as far as I recall, both solutions requires to have a repository per rpm. > > What are your thoughts on this? > > Thanks > > -Erich From bruce.e.jones at intel.com Tue Jul 17 16:32:46 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 17 Jul 2018 16:32:46 +0000 Subject: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA31892F@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0BA31892F@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB562AE2@fmsmsx117.amr.corp.intel.com> Hi Ghada! I really like what you're doing here, and want to combine it with the sub-project approach I had already started. There is a bit of over-lap between the two but I think we can work it out. For instance I'm thinking that a bug in Documentation might be marked as "[Bug] [Doc]", and so on. Basically each story gets marked with a kind for what kind of thing it is, and what sub-project it's part of. I have built both worklists and boards for testing and experimentation, and there are some usability issues with them. Both are access controlled and can only be modified by the owner granting explicit permission. This might be fine for things we want to control closely but not so much otherwise. Manually populating worklists is painful given the number of stories we already have. Populating them with automated queries works well but automated worklists can't be sorted the way manual lists can be. I started out using Etherpads and Ethercalc tables since those can be sorted, but we are hitting basic data integrity issues with Ethercalc that are really starting to scare us. I've put this on the agenda for our call tomorrow but we might want to hold a separate call with a smaller audience. brucej -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Tuesday, July 17, 2018 7:19 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Proposal to use prefixes in Story Board to ease searches As discussed in last Wednesday's meeting, I have updated the StarlingX wiki with the tracking proposal below: https://wiki.openstack.org/wiki/StarlingX#Meetings I've also added a [Test] prefix for test-related work items. I have updated all stories with prefixes. If I mislabeled something, please feel free to fix as you see fit. Regards, Ghada -----Original Message----- From: Khalil, Ghada Sent: Tuesday, July 10, 2018 6:22 PM To: starlingx-discuss at lists.starlingx.io Subject: Proposal to use prefixes in Story Board to ease searches Hello, With the increased number of active stories in StartlingX, I'd like to propose that we consistently use a set of prefixes to make it easier to search and find work items. Suggested Prefixes: [Bug] A problem which impairs or prevents the functionality of StarlingX [Enhancement] An improvement or enhancement to the functionality of StartingX Typically smaller scope items [Feature] A new feature/functionality to be added to StarlingX Ideally, the scope should fit within a release time-frame (ex: 3-6 months) [Build] Build tools, environment, repo organization, etc [Process] Process and project related work items [Doc] Documentation related work items [Upstreaming] Work items that need to be pushed in the core openstack projects [Help] Request for assistance / help ** Others can be added as long as we agree on a manageable set. Sample Queries: - Active Features https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Feature - Active Bugs https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&q=Bug I would also like to explore using worklists for larger project initiatives which would potentially span multiple features/releases. Example: [Initiative] Containerized Openstack Example: [Initiative] StarlingX Project Re-structuring Does anyone know how to scope worklists and boards to the StarlingX project group only? Any feedback is welcome. Regards, Ghada Ghada Khalil, Manager, Titanium Cloud, Wind River direct 613.270.2273  skype ghada.khalil.ottawa 350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Tue Jul 17 16:32:14 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 17 Jul 2018 16:32:14 +0000 Subject: [Starlingx-discuss] Restructuring round 2 In-Reply-To: References: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> <795D2371-83B9-4562-9854-8C331BB1978C@intel.com> Message-ID: Agree, we can move that into a later discussion. Taking back into the topic I think that the proposal needs a section describing why this is needed or what is the problem that we are trying to solve with these changes. -Erich On 7/17/18, 11:16 AM, "Scott Little" wrote: Important subjects that I want to participate in, but I think that's a subject for a different thread. Long term solutions, versus a short term need to get WindRiver converged onto StarlingX. For now, we'd like to get a rational directory structure. Subdivision of current gits into per-package gits can happen later if that's the path we choose. Scott On 18-07-17 11:54 AM, Cordoba Malibran, Erich wrote: > Hi Scott, > > Thanks for the info. There's something I would like to bring into the discussion of the consolidation. > It has started a discussion on what infrastructure we need to have a CI of StarlingX and an evaluation on > OBS (openbuildservice) and Koji has started. > > Taking that in mind I'm wondering how this consolidation can help/affect to adapt the StarlingX building > Into one of these infrastructures, as far as I recall, both solutions requires to have a repository per rpm. > > What are your thoughts on this? > > Thanks > > -Erich From sgw at linux.intel.com Tue Jul 17 16:38:08 2018 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 17 Jul 2018 09:38:08 -0700 Subject: [Starlingx-discuss] Restructuring round 2 In-Reply-To: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> References: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> Message-ID: <7f3c17c2-1997-4d8e-5414-13d41cdb846b@linux.intel.com> Scott, Thanks for getting started on this. As you may know I worked on the Yocto Project and worked on the initial split that you mention came from WRLinux. I think you have done a good job with the reorganization. As I am just coming up to speed I might have a couple of dumb questions to as ask I don't know of all the content changes yet (Patches, config changes, ...). A simple high level question, would it make sense to segregate out everything that is CentOS into base? That way as we move to more of an OS independent setup, the core directory could possibly go away? Can you add some definition as the what belongs in some of the other directories (config vs config-files, tools vs utilities)? See more direct questions inline in the lists below. Do you have a full "after" list, that might help then just seeing what's being relocated. Thanks Sau! On 07/17/2018 08:07 AM, Scott Little wrote: > Story: https://storyboard.openstack.org/#!/story/2002801 > > *Goals:* > > 1) Consolidate the following repo’s under stx-integ. > • stx-gplv2 > • stx-gplv3 > • stx-utils > > 2) Restructure the directories under which packages are to be found. > > Currently stx-gplv2/3 are largely without structure. Parts of the > stx-integ structure were inherited from WRLinux and make little sense. > stx-utils is just i mess of stuff that never found a home when StarlingX > was first set up. > > Directories should descriptive of the class of packages to be found within. > > Intent is to preserve update history as best is is possible. > > > *Timeline: * > > Probably around July 23 unless there are strong objections.  We should > probably have a freeze on submissions to the affected repos until it is > all completed. > > > *Code Reviews: * > > Most of this is just moving code around.  A few path corrections, but no > new code.  The number and size of the reviews will be huge, and the code > should all have been inspected once before.  Is there a way to fast > track this?  Would there be strong objections to me just doing a +2/+1 > without waiting for independent review? > > > *Details of directories/groups ...* > > > Create new directories under stx-integ (logical groupings for files): >    ceph >    config >    config-files >    database >    filesystem >    filesystem/drbd >    grub >    kernel >    kernel/kernel-modules >    ldap >    logging >    strorage-drivers >    tools >    utilities >    virt > > Retained directories under stx-integ (additional logical groupings for > files): >    base >    mellanox >    monitoring >    networking >    python >    restapi-doc >    security > > Retire directories under stx-integ (non-descriptive or ambiguous > grouping we will retire): >    connectivity >    core >    devtools >    extended >    support > > > *Details of packages ...* > > Relocated packages (internal to stx-integ): >    base/ >       dhcp >       initscripts >       libevent >       lighttpd >       memcached >       net-snmp >       novnc >       ntp >       openssh >       pam >       procps >       sanlock >       shadow >       sudo >       systemd >       util-linux >       vim >       watchdog > >    ceph/ >       python-cephclient > >    config/ >       e2fsprogs Why e2fsprogs in config vs base? >       facter >       nfs-utils Same here base? >       nfscheck >       puppet-4.8.2 >       puppet-modules > >    kernel/ >       kernel-std >       kernel-rt > >    kernel/kernel-modules/ >       mlnx-ofa_kernel > >    ldap/ >       nss-pam-ldapd >       openldap > >    logging/ >       syslog-ng >       logrotate With just 2 items maybe base as they are part of CentOS? > >    networking/ >       lldpd >       iproute I could see this one both ways it's one item that could be part of base. >       mellanox >       python-ryu >       mlx4-config > >    python/ >       python-2.7.5 >       python-django >       python-gunicorn >       python-setuptools >       python-smartpm > >    security/ >       shim-signed >       shim-unsigned >       tboot > >    strorage-drivers/ >       python-3parclient >       python-lefthandclient > >    virt/ >       cloud-init >       libvirt >       libvirt-python >       qemu > >    tools/ >       storage-topology >       vm-topology > >    utilities/ >       tis-extensions >       namespace-utils >       nova-utils >       update-motd > > > > Relocated packages (stx-utils to stx-update): >     enable-dev-patch > > > > Relocated packages (stx-utils to stx-integ): > >     config-files/ >         io-scheduler > >     filesystem/ >         filesystem-scripts > >     grub/ >         grubby > >     logging/ >         logmgmt > >     tools/ >         collector >         monitor-tools > >     tools/engtools/ >         hostdata-collectors >         parsers > >     utilities/ >         build-info >         branding   (formerly wrs-branding) >         platform-util > > > > Relocated packages (stx-gpl2 to stx-integ): >     base/ >         bash >         cgcs-users >         cluster-resource-agents >         dpkg >         haproxy >         libfdt >         netpbm >         rpm > >     database/ >         mariadb > >     filesystem/ >         iscsi-initiator-utils > >     filesystem/drbd/ >         drbd-tools > >     kernel/kernel-modules/ >         drbd >         integrity >         intel-e1000e >         intel-i40e >         intel-i40evf >         intel-ixgbe >         intel-ixgbevf >         qat17 >         tpmdd > >     ldap/ >         ldapscripts > >     networking/ >         iptables >         net-tools > > > > Relocated packages (stx-gpl3 to stx-integ): >     base/ >         anaconda >         crontabs >         dnsmasq >         rsync > >     database/ >         python-psycopg2 > >     filesystem/ >         parted > >     grub/ >         grub2 > >     security/ >         python-keyring > > > > Delete two packages from stx-integ: >    tgt >    irqbalance > > Delete two packages from stx-gplv3: >    seabios >    sysvinit > > Delete one package from stx-utils: >    io-monitor > > > > _______________________________________________ > 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 Jul 17 16:46:37 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 17 Jul 2018 16:46:37 +0000 Subject: [Starlingx-discuss] Restructuring round 2 In-Reply-To: <7f3c17c2-1997-4d8e-5414-13d41cdb846b@linux.intel.com> References: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> <7f3c17c2-1997-4d8e-5414-13d41cdb846b@linux.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB562E92@fmsmsx117.amr.corp.intel.com> I think this proposal makes sense. As we get patches merged to their upstreams, we can replace much of this with upstream binaries and over time remove much of this content. brucej -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Tuesday, July 17, 2018 9:38 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Restructuring round 2 Scott, Thanks for getting started on this. As you may know I worked on the Yocto Project and worked on the initial split that you mention came from WRLinux. I think you have done a good job with the reorganization. As I am just coming up to speed I might have a couple of dumb questions to as ask I don't know of all the content changes yet (Patches, config changes, ...). A simple high level question, would it make sense to segregate out everything that is CentOS into base? That way as we move to more of an OS independent setup, the core directory could possibly go away? Can you add some definition as the what belongs in some of the other directories (config vs config-files, tools vs utilities)? See more direct questions inline in the lists below. Do you have a full "after" list, that might help then just seeing what's being relocated. Thanks Sau! On 07/17/2018 08:07 AM, Scott Little wrote: > Story: https://storyboard.openstack.org/#!/story/2002801 > > *Goals:* > > 1) Consolidate the following repo’s under stx-integ. > • stx-gplv2 > • stx-gplv3 > • stx-utils > > 2) Restructure the directories under which packages are to be found. > > Currently stx-gplv2/3 are largely without structure. Parts of the > stx-integ structure were inherited from WRLinux and make little sense. > stx-utils is just i mess of stuff that never found a home when > StarlingX was first set up. > > Directories should descriptive of the class of packages to be found within. > > Intent is to preserve update history as best is is possible. > > > *Timeline: * > > Probably around July 23 unless there are strong objections.  We should > probably have a freeze on submissions to the affected repos until it > is all completed. > > > *Code Reviews: * > > Most of this is just moving code around.  A few path corrections, but > no new code.  The number and size of the reviews will be huge, and the > code should all have been inspected once before.  Is there a way to > fast track this?  Would there be strong objections to me just doing a > +2/+1 without waiting for independent review? > > > *Details of directories/groups ...* > > > Create new directories under stx-integ (logical groupings for files): >    ceph >    config >    config-files >    database >    filesystem >    filesystem/drbd >    grub >    kernel >    kernel/kernel-modules >    ldap >    logging >    strorage-drivers >    tools >    utilities >    virt > > Retained directories under stx-integ (additional logical groupings for > files): >    base >    mellanox >    monitoring >    networking >    python >    restapi-doc >    security > > Retire directories under stx-integ (non-descriptive or ambiguous > grouping we will retire): >    connectivity >    core >    devtools >    extended >    support > > > *Details of packages ...* > > Relocated packages (internal to stx-integ): >    base/ >       dhcp >       initscripts >       libevent >       lighttpd >       memcached >       net-snmp >       novnc >       ntp >       openssh >       pam >       procps >       sanlock >       shadow >       sudo >       systemd >       util-linux >       vim >       watchdog > >    ceph/ >       python-cephclient > >    config/ >       e2fsprogs Why e2fsprogs in config vs base? >       facter >       nfs-utils Same here base? >       nfscheck >       puppet-4.8.2 >       puppet-modules > >    kernel/ >       kernel-std >       kernel-rt > >    kernel/kernel-modules/ >       mlnx-ofa_kernel > >    ldap/ >       nss-pam-ldapd >       openldap > >    logging/ >       syslog-ng >       logrotate With just 2 items maybe base as they are part of CentOS? > >    networking/ >       lldpd >       iproute I could see this one both ways it's one item that could be part of base. >       mellanox >       python-ryu >       mlx4-config > >    python/ >       python-2.7.5 >       python-django >       python-gunicorn >       python-setuptools >       python-smartpm > >    security/ >       shim-signed >       shim-unsigned >       tboot > >    strorage-drivers/ >       python-3parclient >       python-lefthandclient > >    virt/ >       cloud-init >       libvirt >       libvirt-python >       qemu > >    tools/ >       storage-topology >       vm-topology > >    utilities/ >       tis-extensions >       namespace-utils >       nova-utils >       update-motd > > > > Relocated packages (stx-utils to stx-update): >     enable-dev-patch > > > > Relocated packages (stx-utils to stx-integ): > >     config-files/ >         io-scheduler > >     filesystem/ >         filesystem-scripts > >     grub/ >         grubby > >     logging/ >         logmgmt > >     tools/ >         collector >         monitor-tools > >     tools/engtools/ >         hostdata-collectors >         parsers > >     utilities/ >         build-info >         branding   (formerly wrs-branding) >         platform-util > > > > Relocated packages (stx-gpl2 to stx-integ): >     base/ >         bash >         cgcs-users >         cluster-resource-agents >         dpkg >         haproxy >         libfdt >         netpbm >         rpm > >     database/ >         mariadb > >     filesystem/ >         iscsi-initiator-utils > >     filesystem/drbd/ >         drbd-tools > >     kernel/kernel-modules/ >         drbd >         integrity >         intel-e1000e >         intel-i40e >         intel-i40evf >         intel-ixgbe >         intel-ixgbevf >         qat17 >         tpmdd > >     ldap/ >         ldapscripts > >     networking/ >         iptables >         net-tools > > > > Relocated packages (stx-gpl3 to stx-integ): >     base/ >         anaconda >         crontabs >         dnsmasq >         rsync > >     database/ >         python-psycopg2 > >     filesystem/ >         parted > >     grub/ >         grub2 > >     security/ >         python-keyring > > > > Delete two packages from stx-integ: >    tgt >    irqbalance > > Delete two packages from stx-gplv3: >    seabios >    sysvinit > > Delete one package from stx-utils: >    io-monitor > > > > _______________________________________________ > 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 Jul 17 16:50:28 2018 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 17 Jul 2018 09:50:28 -0700 Subject: [Starlingx-discuss] Adding packages to build .lst files In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB0D8186@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F3A9@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB0D8186@ALA-MBD.corp.ad.wrs.com> Message-ID: <9e4a416b-6e09-7aaa-8cd0-c1073f8dcaba@linux.intel.com> Hi Don, Not sure what happened, maybe because of the attached script, this got scrubbed on my end. Can you resend possibly with the script in a zip file? Thanks Sau! On 07/17/2018 08:15 AM, Rowsell, Brent wrote: > Saul, > > Can someone provide some input on this ? > > Thanks, > > Brent > > *From:* Penney, Don [mailto:Don.Penney at windriver.com] > *Sent:* Monday, July 16, 2018 2:22 PM > *To:* 'starlingx-discuss at lists.starlingx.io' > > > *Subject:* [Starlingx-discuss] Adding packages to build .lst files > > Hi folks, > > We’ve got some packages to add to the build, and I’m wondering if > there’s some description of the various .lst files in > stxtools/centos-mirror-tools. For example, how do you decide whether a > package is listed in rpms_from_centos_repo.lst vs > rpms_from_centos_3rd_parties.lst? > > I started writing a script to pull together a list of the dependencies > based on Requires and BuildRequires. As I understand it, we need to add > all such dependencies, recursively, to these .lst files. Using the > StarlingX.repo config file as an arg to repoquery, I get some packages > overlapping with rpms_from_centos_3rd_parties.lst, however, so I’m > hoping there’s some clear direction with these files. My script is > finding hundreds of rpms to add to rpms_from_centos_repo.lst with its > calls to repoquery to resolve the dependencies, so either I’ve got lots > of overlap and many of these need to go to the 3rdparty file, my > repoquery approach for automating this is completely wrong, or these new > packages are using a completely different set of dependencies for the > builds than anything else we’ve got. > > I’ve attached the first draft of my script for anyone that’s curious. > > Thanks, > > Don. > > *Don Penney*, Developer, *Wind River* > From Brent.Rowsell at windriver.com Tue Jul 17 16:51:26 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Tue, 17 Jul 2018 16:51:26 +0000 Subject: [Starlingx-discuss] Restructuring round 2 In-Reply-To: References: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> <795D2371-83B9-4562-9854-8C331BB1978C@intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0D83FF@ALA-MBD.corp.ad.wrs.com> This was posted to the mailing list over a week ago. Brent -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Tuesday, July 17, 2018 12:32 PM To: Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Restructuring round 2 Agree, we can move that into a later discussion. Taking back into the topic I think that the proposal needs a section describing why this is needed or what is the problem that we are trying to solve with these changes. -Erich On 7/17/18, 11:16 AM, "Scott Little" wrote: Important subjects that I want to participate in, but I think that's a subject for a different thread. Long term solutions, versus a short term need to get WindRiver converged onto StarlingX. For now, we'd like to get a rational directory structure. Subdivision of current gits into per-package gits can happen later if that's the path we choose. Scott On 18-07-17 11:54 AM, Cordoba Malibran, Erich wrote: > Hi Scott, > > Thanks for the info. There's something I would like to bring into the discussion of the consolidation. > It has started a discussion on what infrastructure we need to have a CI of StarlingX and an evaluation on > OBS (openbuildservice) and Koji has started. > > Taking that in mind I'm wondering how this consolidation can help/affect to adapt the StarlingX building > Into one of these infrastructures, as far as I recall, both solutions requires to have a repository per rpm. > > What are your thoughts on this? > > Thanks > > -Erich _______________________________________________ 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 Tue Jul 17 19:10:49 2018 From: scott.little at windriver.com (Scott Little) Date: Tue, 17 Jul 2018 15:10:49 -0400 Subject: [Starlingx-discuss] Restructuring round 2 In-Reply-To: <7f3c17c2-1997-4d8e-5414-13d41cdb846b@linux.intel.com> References: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> <7f3c17c2-1997-4d8e-5414-13d41cdb846b@linux.intel.com> Message-ID: On 18-07-17 12:38 PM, Saul Wold wrote: > > Scott, > > Thanks for getting started on this.  As you may know I worked on the > Yocto Project and worked on the initial split that you mention came > from WRLinux. > > I think you have done a good job with the reorganization.  As I am > just coming up to speed I might have a couple of dumb questions to as > ask I don't know of all the content changes yet (Patches, config > changes, ...). > > A simple high level question, would it make sense to segregate out > everything that is CentOS into base?  That way as we move to more of > an OS independent setup, the core directory could possibly go away? [SL]  We were envisioning function rather than upstream source as the reason for the categories.  'Base' are those packages that are pretty much universal to a Linux server. > > Can you add some definition as the what belongs in some of the other > directories (config vs config-files, tools vs utilities)? [SL] Tools vs utilities.  Not clear I'll admit.  Utilities are small, special purpose, shortcuts that could otherwise be accomplished by the right set of CLI commands. Tools are bigger, more complex, e.g. investigating and analyze the state of the system. > > See more direct questions inline in the lists below. > > Do you have a full "after" list, that might help then just seeing > what's being relocated. [SL]  will send seperately > > Thanks > Sau! > > > On 07/17/2018 08:07 AM, Scott Little wrote: >> Story: https://storyboard.openstack.org/#!/story/2002801 >> >> *Goals:* >> >> 1) Consolidate the following repo’s under stx-integ. >> • stx-gplv2 >> • stx-gplv3 >> • stx-utils >> >> 2) Restructure the directories under which packages are to be found. >> >> Currently stx-gplv2/3 are largely without structure. Parts of the >> stx-integ structure were inherited from WRLinux and make little >> sense.  stx-utils is just i mess of stuff that never found a home >> when StarlingX was first set up. >> >> Directories should descriptive of the class of packages to be found >> within. >> >> Intent is to preserve update history as best is is possible. >> >> >> *Timeline: * >> >> Probably around July 23 unless there are strong objections.  We >> should probably have a freeze on submissions to the affected repos >> until it is all completed. >> >> >> *Code Reviews: * >> >> Most of this is just moving code around.  A few path corrections, but >> no new code.  The number and size of the reviews will be huge, and >> the code should all have been inspected once before.  Is there a way >> to fast track this? Would there be strong objections to me just doing >> a +2/+1 without waiting for independent review? >> >> >> *Details of directories/groups ...* >> >> >> Create new directories under stx-integ (logical groupings for files): >>     ceph >>     config >>     config-files >>     database >>     filesystem >>     filesystem/drbd >>     grub >>     kernel >>     kernel/kernel-modules >>     ldap >>     logging >>     strorage-drivers >>     tools >>     utilities >>     virt >> >> Retained directories under stx-integ (additional logical groupings >> for files): >>     base >>     mellanox >>     monitoring >>     networking >>     python >>     restapi-doc >>     security >> >> Retire directories under stx-integ (non-descriptive or ambiguous >> grouping we will retire): >>     connectivity >>     core >>     devtools >>     extended >>     support >> >> >> *Details of packages ...* >> >> Relocated packages (internal to stx-integ): >>     base/ >>        dhcp >>        initscripts >>        libevent >>        lighttpd >>        memcached >>        net-snmp >>        novnc >>        ntp >>        openssh >>        pam >>        procps >>        sanlock >>        shadow >>        sudo >>        systemd >>        util-linux >>        vim >>        watchdog >> >>     ceph/ >>        python-cephclient >> >>     config/ >>        e2fsprogs > Why e2fsprogs in config vs base? [SL] error on my part.  Some sort of cut-n-paste error.    config/       facter       puppet-4.8.2       puppet-modules    filesystem/       e2fsprogs       nfs-utils       nfscheck > >>        facter >>        nfs-utils > Same here base? >>        nfscheck >>        puppet-4.8.2 >>        puppet-modules >> >>     kernel/ >>        kernel-std >>        kernel-rt >> >>     kernel/kernel-modules/ >>        mlnx-ofa_kernel >> >>     ldap/ >>        nss-pam-ldapd >>        openldap >> >>     logging/ >>        syslog-ng >>        logrotate > With just 2 items maybe base as they are part of CentOS? [SL] additional packages might land here that filter/manipulate/look for trends in logs > >> >>     networking/ >>        lldpd >>        iproute > I could see this one both ways it's one item that could be part of base. > >>        mellanox >>        python-ryu >>        mlx4-config >> >>     python/ >>        python-2.7.5 >>        python-django >>        python-gunicorn >>        python-setuptools >>        python-smartpm >> >>     security/ >>        shim-signed >>        shim-unsigned >>        tboot >> >>     strorage-drivers/ >>        python-3parclient >>        python-lefthandclient >> >>     virt/ >>        cloud-init >>        libvirt >>        libvirt-python >>        qemu >> >>     tools/ >>        storage-topology >>        vm-topology >> >>     utilities/ >>        tis-extensions >>        namespace-utils >>        nova-utils >>        update-motd >> >> >> >> Relocated packages (stx-utils to stx-update): >>      enable-dev-patch >> >> >> >> Relocated packages (stx-utils to stx-integ): >> >>      config-files/ >>          io-scheduler >> >>      filesystem/ >>          filesystem-scripts >> >>      grub/ >>          grubby >> >>      logging/ >>          logmgmt >> >>      tools/ >>          collector >>          monitor-tools >> >>      tools/engtools/ >>          hostdata-collectors >>          parsers >> >>      utilities/ >>          build-info >>          branding   (formerly wrs-branding) >>          platform-util >> >> >> >> Relocated packages (stx-gpl2 to stx-integ): >>      base/ >>          bash >>          cgcs-users >>          cluster-resource-agents >>          dpkg >>          haproxy >>          libfdt >>          netpbm >>          rpm >> >>      database/ >>          mariadb >> >>      filesystem/ >>          iscsi-initiator-utils >> >>      filesystem/drbd/ >>          drbd-tools >> >>      kernel/kernel-modules/ >>          drbd >>          integrity >>          intel-e1000e >>          intel-i40e >>          intel-i40evf >>          intel-ixgbe >>          intel-ixgbevf >>          qat17 >>          tpmdd >> >>      ldap/ >>          ldapscripts >> >>      networking/ >>          iptables >>          net-tools >> >> >> >> Relocated packages (stx-gpl3 to stx-integ): >>      base/ >>          anaconda >>          crontabs >>          dnsmasq >>          rsync >> >>      database/ >>          python-psycopg2 >> >>      filesystem/ >>          parted >> >>      grub/ >>          grub2 >> >>      security/ >>          python-keyring >> >> >> >> Delete two packages from stx-integ: >>     tgt >>     irqbalance >> >> Delete two packages from stx-gplv3: >>     seabios >>     sysvinit >> >> Delete one package from stx-utils: >>     io-monitor >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Tue Jul 17 19:25:11 2018 From: scott.little at windriver.com (Scott Little) Date: Tue, 17 Jul 2018 15:25:11 -0400 Subject: [Starlingx-discuss] Restructuring round 2 In-Reply-To: References: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> <7f3c17c2-1997-4d8e-5414-13d41cdb846b@linux.intel.com> Message-ID: <78f0da9b-9498-7b06-0901-2e411e2fd6a8@windriver.com> The full list of packages in stx-integ after proposed changes On 18-07-17 03:10 PM, Scott Little wrote: > On 18-07-17 12:38 PM, Saul Wold wrote: >> >> Do you have a full "after" list, that might help then just seeing >> what's being relocated. > [SL]  will send seperately base/anaconda base/bash base/centos-release base/cgcs-users base/cluster-resource-agents base/crontabs base/dhcp base/dnsmasq base/dpkg base/haproxy base/initscripts base/libevent base/libfdt base/lighttpd base/lshell base/memcached base/netpbm base/net-snmp base/novnc base/ntp base/openssh base/pam base/rpm base/rsync base/sanlock base/setup base/shadow-utils base/sudo base/systemd base/util-linux base/vim base/watchdog ceph/python-cephclient config/facter config/puppet-4.8.2 config/puppet-modules/openstack/puppet-ceilometer-11.3.0 config/puppet-modules/openstack/puppet-ceph-2.2.0 config/puppet-modules/openstack/puppet-cinder-11.3.0 config/puppet-modules/openstack/puppet-glance-11.3.0 config/puppet-modules/openstack/puppet-heat-11.3.0 config/puppet-modules/openstack/puppet-horizon-9.5.0 config/puppet-modules/openstack/puppet-ironic-11.3.0 config/puppet-modules/openstack/puppet-keystone-11.3.0 config/puppet-modules/openstack/puppet-magnum-11.3.0 config/puppet-modules/openstack/puppet-memcached-3.0.2 config/puppet-modules/openstack/puppet-murano-11.3.0 config/puppet-modules/openstack/puppet-neutron-11.3.0 config/puppet-modules/openstack/puppet-nova-11.4.0 config/puppet-modules/openstack/puppet-openstacklib-11.3.0 config/puppet-modules/openstack/puppet-oslo-11.3.0 config/puppet-modules/openstack/puppet-panko-11.3.0 config/puppet-modules/openstack/puppet-swift-11.3.0 config/puppet-modules/puppet-boolean-1.0.2 config/puppet-modules/puppet-create_resources config/puppet-modules/puppet-dnsmasq config/puppet-modules/puppet-drbd-0.3.1 config/puppet-modules/puppet-filemapper config/puppet-modules/puppet-haproxy-1.5.0 config/puppet-modules/puppet-ldap config/puppet-modules/puppet-lvm config/puppet-modules/puppet-network config/puppet-modules/puppet-nslcd config/puppet-modules/puppet-postgresql-4.8.0 config/puppet-modules/puppet-puppi config/puppet-modules/puppet-rabbitmq-5.5.0 config/puppet-modules/puppet-staging config/puppet-modules/puppet-stdlib-4.12.0 config-files/io-scheduler database/mariadb database/python-psycopg2 filesystem/drbd/drbd-tools filesystem/e2fsprogs filesystem/filesystem-scripts filesystem/iscsi-initiator-utils filesystem/nfscheck filesystem/nfs-utils filesystem/parted grub/grub2 grub/grubby kernel/kernel-rt kernel/kernel-std kernel/kernel-modules/drbd kernel/kernel-modules/integrity kernel/kernel-modules/intel-e1000e kernel/kernel-modules/intel-i40e kernel/kernel-modules/intel-i40evf kernel/kernel-modules/intel-ixgbe kernel/kernel-modules/intel-ixgbevf kernel/kernel-modules/mlnx-ofa_kernel kernel/kernel-modules/qat17 kernel/kernel-modules/tpmdd kubernetes/docker-ce kubernetes/kubernetes ldap/ldapscripts ldap/nss-pam-ldapd ldap/openldap logging/logmgmt logging/logrotate logging/syslog-ng monitoring/collectd-extensions monitoring/influxdb-extensions networking/iproute networking/iptables networking/lldpd networking/mellanox/libibverbs networking/mellanox/libmlx4 networking/mellanox/libmlx5 networking/mellanox/mlx4-config networking/mellanox/rdma-core networking/net-tools networking/openvswitch networking/python-ryu networking/scapy python/python-2.7.5 python/python-django python/python-eventlet python/python-gunicorn python/python-requests python/python-setuptools python/python-smartpm restapi-doc security/audit security/libtpms security/python-keyring security/shim-signed security/shim-unsigned security/spectre-meltdown-checker security/swtpm security/tboot security/tpm2-openssl-engine security/tpm2-tools security/tss2 security/wrs-ssl strorage-drivers/python-3parclient strorage-drivers/python-lefthandclient tools/collector tools/engtools/hostdata-collectors tools/monitor-tools tools/vm-topology utilities/branding utilities/build-info utilities/namespace-utils utilities/nova-utils utilities/platform-util utilities/tis-extensions utilities/update-motd virt/cloud-init virt/libvirt virt/libvirt-python virt/qemu From Don.Penney at windriver.com Tue Jul 17 19:43:12 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 17 Jul 2018 19:43:12 +0000 Subject: [Starlingx-discuss] Adding packages to build .lst files In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F3A9@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F3A9@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F8C4@ALA-MBD.corp.ad.wrs.com> Providing the script in a zip file for anyone who couldn't see the original shell script file attachment. As a side note: I started following the README in stx-tools to try out the download utility, to hopefully glean a little more info about the LST files on my own. I setup a fresh repo yesterday afternoon, then setup and launched the docker image this morning. The download fails: done!! finish 1st round of RPM downloading successfully! ERROR: -------RPMs missing 4 in yumdownloader with L1 match --------------- The failed RPMs are recorded: $ cat centos_rpms_missing_L1.txt epel-rpm-macros-7-18.noarch.rpm python2-rpm-macros-3-18.el7.noarch.rpm python-rpm-macros-3-18.el7.noarch.rpm python-srpm-macros-3-18.el7.noarch.rpm Seems odd to fail on these... so a repoquery to check: $ repoquery -c StarlingX.repo --quiet epel-rpm-macros python2-rpm-macros python-rpm-macros python-srpm-macros epel-rpm-macros-0:7-19.noarch python-rpm-macros-0:3-21.el7.noarch python-srpm-macros-0:3-21.el7.noarch python2-rpm-macros-0:3-21.el7.noarch Yep... versions don't match. So these pkgs have been upversioned in the repos, and the older versions are not maintained in the repos. So the LST files would seem to be quickly out of date. From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Monday, July 16, 2018 2:22 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] Adding packages to build .lst files Hi folks, We've got some packages to add to the build, and I'm wondering if there's some description of the various .lst files in stxtools/centos-mirror-tools. For example, how do you decide whether a package is listed in rpms_from_centos_repo.lst vs rpms_from_centos_3rd_parties.lst? I started writing a script to pull together a list of the dependencies based on Requires and BuildRequires. As I understand it, we need to add all such dependencies, recursively, to these .lst files. Using the StarlingX.repo config file as an arg to repoquery, I get some packages overlapping with rpms_from_centos_3rd_parties.lst, however, so I'm hoping there's some clear direction with these files. My script is finding hundreds of rpms to add to rpms_from_centos_repo.lst with its calls to repoquery to resolve the dependencies, so either I've got lots of overlap and many of these need to go to the 3rdparty file, my repoquery approach for automating this is completely wrong, or these new packages are using a completely different set of dependencies for the builds than anything else we've got. I've attached the first draft of my script for anyone that's curious. Thanks, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: starlingx_add_pkgs.zip Type: application/x-zip-compressed Size: 1075 bytes Desc: starlingx_add_pkgs.zip URL: From erich.cordoba.malibran at intel.com Tue Jul 17 19:43:44 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 17 Jul 2018 19:43:44 +0000 Subject: [Starlingx-discuss] Adding packages to build .lst files In-Reply-To: <9e4a416b-6e09-7aaa-8cd0-c1073f8dcaba@linux.intel.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F3A9@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB0D8186@ALA-MBD.corp.ad.wrs.com> <9e4a416b-6e09-7aaa-8cd0-c1073f8dcaba@linux.intel.com> Message-ID: About the names of the files, we don't have a description of the content but Initially the 3rd_parties.lst content was for the rpms that couldn't be get through yumdownloader, presumably these are the oldest packages as they are not in vault.centos.org or they are hard to find. The best scenario is to not have the 3rd_parties.lst file. On 7/17/18, 11:50 AM, "Saul Wold" wrote: Hi Don, Not sure what happened, maybe because of the attached script, this got scrubbed on my end. Can you resend possibly with the script in a zip file? Thanks Sau! On 07/17/2018 08:15 AM, Rowsell, Brent wrote: > Saul, > > Can someone provide some input on this ? > > Thanks, > > Brent > > *From:* Penney, Don [mailto:Don.Penney at windriver.com] > *Sent:* Monday, July 16, 2018 2:22 PM > *To:* 'starlingx-discuss at lists.starlingx.io' > > > *Subject:* [Starlingx-discuss] Adding packages to build .lst files > > Hi folks, > > We’ve got some packages to add to the build, and I’m wondering if > there’s some description of the various .lst files in > stxtools/centos-mirror-tools. For example, how do you decide whether a > package is listed in rpms_from_centos_repo.lst vs > rpms_from_centos_3rd_parties.lst? > > I started writing a script to pull together a list of the dependencies > based on Requires and BuildRequires. As I understand it, we need to add > all such dependencies, recursively, to these .lst files. Using the > StarlingX.repo config file as an arg to repoquery, I get some packages > overlapping with rpms_from_centos_3rd_parties.lst, however, so I’m > hoping there’s some clear direction with these files. My script is > finding hundreds of rpms to add to rpms_from_centos_repo.lst with its > calls to repoquery to resolve the dependencies, so either I’ve got lots > of overlap and many of these need to go to the 3rdparty file, my > repoquery approach for automating this is completely wrong, or these new > packages are using a completely different set of dependencies for the > builds than anything else we’ve got. > > I’ve attached the first draft of my script for anyone that’s curious. > > Thanks, > > Don. > > *Don Penney*, Developer, *Wind River* > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Tue Jul 17 19:55:35 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 17 Jul 2018 14:55:35 -0500 Subject: [Starlingx-discuss] Restructuring round 2 In-Reply-To: References: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> <7f3c17c2-1997-4d8e-5414-13d41cdb846b@linux.intel.com> Message-ID: On Tue, Jul 17, 2018 at 2:10 PM, Scott Little wrote: > On 18-07-17 12:38 PM, Saul Wold wrote: >> A simple high level question, would it make sense to segregate out >> everything that is CentOS into base? That way as we move to more of an OS >> independent setup, the core directory could possibly go away? > > [SL] We were envisioning function rather than upstream source as the reason > for the categories. 'Base' are those packages that are pretty much > universal to a Linux server. I haven't compared RHEL directly to Ubuntu in a number of years in this regard but there used to be the kinds of differences that just made things frustrating. WRS has been through the Yocto -> CentOS mapping already, maybe that was smoother than I am imagining? I lean toward abstracting the distro layer as much as possible with a small list of exceptions (kernel, libvirt,, qemu, etc) that need special attention. this can always be done later though, I don't see anything here that makes it harder down the road, if we can make it easier that might be a win. > [SL] Tools vs utilities. Not clear I'll admit. Utilities are small, > special purpose, shortcuts that could otherwise be accomplished by the right > set of CLI commands. > Tools are bigger, more complex, e.g. investigating and analyze the state of > the system. FWIW, I names stx-tools with the distinction of 'things used to _build_ the system' as opposed to 'things used to operate/diagnose the system'. >>> Most of this is just moving code around. A few path corrections, but no >>> new code. The number and size of the reviews will be huge, and the code >>> should all have been inspected once before. Is there a way to fast track >>> this? Would there be strong objections to me just doing a +2/+1 without >>> waiting for independent review? We need to stick to the review process as much as possible, we're already getting into some bad habits that will be hard to break. I think it would be useful to post the reviews as soon as possible and mark them WIP (workflow -1) so they don't merge. That's where the specific discussions about tweaks can/should happen. Also, if the reviews for each repo are stacked we can build a manifest file to pull the reviews directly from Gerrit and actually test a build before merging it. dt -- Dean Troyer dtroyer at gmail.com From dtroyer at gmail.com Tue Jul 17 19:55:52 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 17 Jul 2018 14:55:52 -0500 Subject: [Starlingx-discuss] Adding packages to build .lst files In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F3A9@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F3A9@ALA-MBD.corp.ad.wrs.com> Message-ID: On Mon, Jul 16, 2018 at 1:21 PM, Penney, Don wrote: > I started writing a script to pull together a list of the dependencies based > on Requires and BuildRequires. As I understand it, we need to add all such > dependencies, recursively, to these .lst files. Using the StarlingX.repo > config file as an arg to repoquery, I get some packages overlapping with > rpms_from_centos_3rd_parties.lst, however, so I’m hoping there’s some clear > direction with these files. My script is finding hundreds of rpms to add to > rpms_from_centos_repo.lst with its calls to repoquery to resolve the > dependencies, so either I’ve got lots of overlap and many of these need to > go to the 3rdparty file, my repoquery approach for automating this is > completely wrong, or these new packages are using a completely different set > of dependencies for the builds than anything else we’ve got. Thank you! I haven't had time to look at that yet but have been hoping that we could generate even more of this stuff from the other parts of the repo. As for the volume of dependencies, it's been a while since I did something like that with RHEL, but it has always had copious amounts of dependencies even for "small" installations. (Does DBus still require X on a server? I don't think so, but it once did...) > I’ve attached the first draft of my script for anyone that’s curious. The attachment was bounced by Intel's MTA because of the .sh attachment so @intel.com addresses missed this. I'd go ahead and propose a WIP review[0] to stx-tools and iterate on it there. dt [0] In case not everyone knows the common practices in Gerrit, WIP reviews usually begin the commit message with 'WIP' or the author/committer can set a Workflow -1 in the Reply dialog. Or both. Often this means it is not ready for detailed review or it could be a way to solicit feedback during development, it is convenient to mention the reason for WIP in the commit message. -- Dean Troyer dtroyer at gmail.com From sgw at linux.intel.com Tue Jul 17 19:56:18 2018 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 17 Jul 2018 12:56:18 -0700 Subject: [Starlingx-discuss] Restructuring round 2 In-Reply-To: <78f0da9b-9498-7b06-0901-2e411e2fd6a8@windriver.com> References: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> <7f3c17c2-1997-4d8e-5414-13d41cdb846b@linux.intel.com> <78f0da9b-9498-7b06-0901-2e411e2fd6a8@windriver.com> Message-ID: <9d0618b7-cea6-6050-92f4-c77f92161443@linux.intel.com> On 07/17/2018 12:25 PM, Scott Little wrote: > The full list of packages in stx-integ after proposed changes > Thanks, this help me understand some of the context and content in the re-arranged packages. I understand your thought of functionality over upstream source, but it would make it clearer, especially for the OS upstream bits to all be contained in "base". That way we work so reduce that one directory to zero. I am not going to block, just saying. I am currently pursuing the existing stx tree trying to understand some of the changes. I will send email on those later. Sau! > > On 18-07-17 03:10 PM, Scott Little wrote: >> On 18-07-17 12:38 PM, Saul Wold wrote: >>> >>> Do you have a full "after" list, that might help then just seeing >>> what's being relocated. >> [SL]  will send seperately > > base/anaconda > base/bash > base/centos-release > base/cgcs-users > base/cluster-resource-agents > base/crontabs > base/dhcp > base/dnsmasq > base/dpkg > base/haproxy > base/initscripts > base/libevent > base/libfdt > base/lighttpd > base/lshell > base/memcached > base/netpbm > base/net-snmp > base/novnc > base/ntp > base/openssh > base/pam > base/rpm > base/rsync > base/sanlock > base/setup > base/shadow-utils > base/sudo > base/systemd > base/util-linux > base/vim > base/watchdog > > ceph/python-cephclient > > config/facter > config/puppet-4.8.2 > config/puppet-modules/openstack/puppet-ceilometer-11.3.0 > config/puppet-modules/openstack/puppet-ceph-2.2.0 > config/puppet-modules/openstack/puppet-cinder-11.3.0 > config/puppet-modules/openstack/puppet-glance-11.3.0 > config/puppet-modules/openstack/puppet-heat-11.3.0 > config/puppet-modules/openstack/puppet-horizon-9.5.0 > config/puppet-modules/openstack/puppet-ironic-11.3.0 > config/puppet-modules/openstack/puppet-keystone-11.3.0 > config/puppet-modules/openstack/puppet-magnum-11.3.0 > config/puppet-modules/openstack/puppet-memcached-3.0.2 > config/puppet-modules/openstack/puppet-murano-11.3.0 > config/puppet-modules/openstack/puppet-neutron-11.3.0 > config/puppet-modules/openstack/puppet-nova-11.4.0 > config/puppet-modules/openstack/puppet-openstacklib-11.3.0 > config/puppet-modules/openstack/puppet-oslo-11.3.0 > config/puppet-modules/openstack/puppet-panko-11.3.0 > config/puppet-modules/openstack/puppet-swift-11.3.0 > config/puppet-modules/puppet-boolean-1.0.2 > config/puppet-modules/puppet-create_resources > config/puppet-modules/puppet-dnsmasq > config/puppet-modules/puppet-drbd-0.3.1 > config/puppet-modules/puppet-filemapper > config/puppet-modules/puppet-haproxy-1.5.0 > config/puppet-modules/puppet-ldap > config/puppet-modules/puppet-lvm > config/puppet-modules/puppet-network > config/puppet-modules/puppet-nslcd > config/puppet-modules/puppet-postgresql-4.8.0 > config/puppet-modules/puppet-puppi > config/puppet-modules/puppet-rabbitmq-5.5.0 > config/puppet-modules/puppet-staging > config/puppet-modules/puppet-stdlib-4.12.0 > > config-files/io-scheduler > > database/mariadb > database/python-psycopg2 > > filesystem/drbd/drbd-tools > filesystem/e2fsprogs > filesystem/filesystem-scripts > filesystem/iscsi-initiator-utils > filesystem/nfscheck > filesystem/nfs-utils > filesystem/parted > > grub/grub2 > grub/grubby > > kernel/kernel-rt > kernel/kernel-std > > kernel/kernel-modules/drbd > kernel/kernel-modules/integrity > kernel/kernel-modules/intel-e1000e > kernel/kernel-modules/intel-i40e > kernel/kernel-modules/intel-i40evf > kernel/kernel-modules/intel-ixgbe > kernel/kernel-modules/intel-ixgbevf > kernel/kernel-modules/mlnx-ofa_kernel > kernel/kernel-modules/qat17 > kernel/kernel-modules/tpmdd > > kubernetes/docker-ce > kubernetes/kubernetes > > ldap/ldapscripts > ldap/nss-pam-ldapd > ldap/openldap > > logging/logmgmt > logging/logrotate > logging/syslog-ng > > monitoring/collectd-extensions > monitoring/influxdb-extensions > > networking/iproute > networking/iptables > networking/lldpd > networking/mellanox/libibverbs > networking/mellanox/libmlx4 > networking/mellanox/libmlx5 > networking/mellanox/mlx4-config > networking/mellanox/rdma-core > networking/net-tools > networking/openvswitch > networking/python-ryu > networking/scapy > > python/python-2.7.5 > python/python-django > python/python-eventlet > python/python-gunicorn > python/python-requests > python/python-setuptools > python/python-smartpm > > restapi-doc > > security/audit > security/libtpms > security/python-keyring > security/shim-signed > security/shim-unsigned > security/spectre-meltdown-checker > security/swtpm > security/tboot > security/tpm2-openssl-engine > security/tpm2-tools > security/tss2 > security/wrs-ssl > > strorage-drivers/python-3parclient > strorage-drivers/python-lefthandclient > > tools/collector > tools/engtools/hostdata-collectors > tools/monitor-tools > tools/vm-topology > > utilities/branding > utilities/build-info > utilities/namespace-utils > utilities/nova-utils > utilities/platform-util > utilities/tis-extensions > utilities/update-motd > > virt/cloud-init > virt/libvirt > virt/libvirt-python > virt/qemu > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Brent.Rowsell at windriver.com Tue Jul 17 20:21:47 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Tue, 17 Jul 2018 20:21:47 +0000 Subject: [Starlingx-discuss] Restructuring round 2 In-Reply-To: <9d0618b7-cea6-6050-92f4-c77f92161443@linux.intel.com> References: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> <7f3c17c2-1997-4d8e-5414-13d41cdb846b@linux.intel.com> <78f0da9b-9498-7b06-0901-2e411e2fd6a8@windriver.com> <9d0618b7-cea6-6050-92f4-c77f92161443@linux.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0D8745@ALA-MBD.corp.ad.wrs.com> You also need to consider the designer workflow including the number of repos they have to change to develop features. For instance having klms and the kernel spread across multiple repos makes no sense. Brent -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Tuesday, July 17, 2018 3:56 PM To: Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Restructuring round 2 On 07/17/2018 12:25 PM, Scott Little wrote: > The full list of packages in stx-integ after proposed changes > Thanks, this help me understand some of the context and content in the re-arranged packages. I understand your thought of functionality over upstream source, but it would make it clearer, especially for the OS upstream bits to all be contained in "base". That way we work so reduce that one directory to zero. I am not going to block, just saying. I am currently pursuing the existing stx tree trying to understand some of the changes. I will send email on those later. Sau! > > On 18-07-17 03:10 PM, Scott Little wrote: >> On 18-07-17 12:38 PM, Saul Wold wrote: >>> >>> Do you have a full "after" list, that might help then just seeing >>> what's being relocated. >> [SL]  will send seperately > > base/anaconda > base/bash > base/centos-release > base/cgcs-users > base/cluster-resource-agents > base/crontabs > base/dhcp > base/dnsmasq > base/dpkg > base/haproxy > base/initscripts > base/libevent > base/libfdt > base/lighttpd > base/lshell > base/memcached > base/netpbm > base/net-snmp > base/novnc > base/ntp > base/openssh > base/pam > base/rpm > base/rsync > base/sanlock > base/setup > base/shadow-utils > base/sudo > base/systemd > base/util-linux > base/vim > base/watchdog > > ceph/python-cephclient > > config/facter > config/puppet-4.8.2 > config/puppet-modules/openstack/puppet-ceilometer-11.3.0 > config/puppet-modules/openstack/puppet-ceph-2.2.0 > config/puppet-modules/openstack/puppet-cinder-11.3.0 > config/puppet-modules/openstack/puppet-glance-11.3.0 > config/puppet-modules/openstack/puppet-heat-11.3.0 > config/puppet-modules/openstack/puppet-horizon-9.5.0 > config/puppet-modules/openstack/puppet-ironic-11.3.0 > config/puppet-modules/openstack/puppet-keystone-11.3.0 > config/puppet-modules/openstack/puppet-magnum-11.3.0 > config/puppet-modules/openstack/puppet-memcached-3.0.2 > config/puppet-modules/openstack/puppet-murano-11.3.0 > config/puppet-modules/openstack/puppet-neutron-11.3.0 > config/puppet-modules/openstack/puppet-nova-11.4.0 > config/puppet-modules/openstack/puppet-openstacklib-11.3.0 > config/puppet-modules/openstack/puppet-oslo-11.3.0 > config/puppet-modules/openstack/puppet-panko-11.3.0 > config/puppet-modules/openstack/puppet-swift-11.3.0 > config/puppet-modules/puppet-boolean-1.0.2 > config/puppet-modules/puppet-create_resources > config/puppet-modules/puppet-dnsmasq > config/puppet-modules/puppet-drbd-0.3.1 > config/puppet-modules/puppet-filemapper > config/puppet-modules/puppet-haproxy-1.5.0 > config/puppet-modules/puppet-ldap > config/puppet-modules/puppet-lvm > config/puppet-modules/puppet-network > config/puppet-modules/puppet-nslcd > config/puppet-modules/puppet-postgresql-4.8.0 > config/puppet-modules/puppet-puppi > config/puppet-modules/puppet-rabbitmq-5.5.0 > config/puppet-modules/puppet-staging > config/puppet-modules/puppet-stdlib-4.12.0 > > config-files/io-scheduler > > database/mariadb > database/python-psycopg2 > > filesystem/drbd/drbd-tools > filesystem/e2fsprogs > filesystem/filesystem-scripts > filesystem/iscsi-initiator-utils > filesystem/nfscheck > filesystem/nfs-utils > filesystem/parted > > grub/grub2 > grub/grubby > > kernel/kernel-rt > kernel/kernel-std > > kernel/kernel-modules/drbd > kernel/kernel-modules/integrity > kernel/kernel-modules/intel-e1000e > kernel/kernel-modules/intel-i40e > kernel/kernel-modules/intel-i40evf > kernel/kernel-modules/intel-ixgbe > kernel/kernel-modules/intel-ixgbevf > kernel/kernel-modules/mlnx-ofa_kernel > kernel/kernel-modules/qat17 > kernel/kernel-modules/tpmdd > > kubernetes/docker-ce > kubernetes/kubernetes > > ldap/ldapscripts > ldap/nss-pam-ldapd > ldap/openldap > > logging/logmgmt > logging/logrotate > logging/syslog-ng > > monitoring/collectd-extensions > monitoring/influxdb-extensions > > networking/iproute > networking/iptables > networking/lldpd > networking/mellanox/libibverbs > networking/mellanox/libmlx4 > networking/mellanox/libmlx5 > networking/mellanox/mlx4-config > networking/mellanox/rdma-core > networking/net-tools > networking/openvswitch > networking/python-ryu > networking/scapy > > python/python-2.7.5 > python/python-django > python/python-eventlet > python/python-gunicorn > python/python-requests > python/python-setuptools > python/python-smartpm > > restapi-doc > > security/audit > security/libtpms > security/python-keyring > security/shim-signed > security/shim-unsigned > security/spectre-meltdown-checker > security/swtpm > security/tboot > security/tpm2-openssl-engine > security/tpm2-tools > security/tss2 > security/wrs-ssl > > strorage-drivers/python-3parclient > strorage-drivers/python-lefthandclient > > tools/collector > tools/engtools/hostdata-collectors > tools/monitor-tools > tools/vm-topology > > utilities/branding > utilities/build-info > utilities/namespace-utils > utilities/nova-utils > utilities/platform-util > utilities/tis-extensions > utilities/update-motd > > virt/cloud-init > virt/libvirt > virt/libvirt-python > virt/qemu > > _______________________________________________ > 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 abraham.arce.moreno at intel.com Tue Jul 17 20:28:39 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 17 Jul 2018 20:28:39 +0000 Subject: [Starlingx-discuss] Adding packages to build .lst files In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F3A9@ALA-MBD.corp.ad.wrs.com> Message-ID: > As a side note: I started following the README in stx-tools to try out the > download utility, to hopefully glean a little more info about the LST files on > my own. I setup a fresh repo yesterday afternoon, then setup and launched > the docker image this morning. The download fails: > > done!! > finish 1st round of RPM downloading successfully! > ERROR: -------RPMs missing 4 in yumdownloader with L1 match --------------- > > The failed RPMs are recorded: > $ cat centos_rpms_missing_L1.txt > epel-rpm-macros-7-18.noarch.rpm > python2-rpm-macros-3-18.el7.noarch.rpm > python-rpm-macros-3-18.el7.noarch.rpm > python-srpm-macros-3-18.el7.noarch.rpm Memo has created a node script to download those dependencies and it perfectly worked For me today to gather the specific versions. I am wondering if we can take out to help with our missing Packages for now, here are the steps using that tool: # cat output/3rd-centos_rpms_missing_L1.txt output/3rd_rpms_missing_L1.txt \ output/3rd_srpms_missing_L1.txt output/centos_rpms_missing_L1.txt output/centos_srpms_missing_L1.txt epel-rpm-macros-7-18.noarch.rpm python2-rpm-macros-3-18.el7.noarch.rpm python-rpm-macros-3-18.el7.noarch.rpm python-srpm-macros-3-18.el7.noarch.rpm $ node index.js -p epel-rpm-macros-7-18.noarch.rpm $ node index.js -p python2-rpm-macros-3-18.el7.noarch.rpm $ node index.js -p python-rpm-macros-3-18.el7.noarch.rpm $ node index.js -p python-srpm-macros-3-18.el7.noarch.rpm All Key ID for these packages ok $ rpm -vK /import/mirrors/CentOS/stx-r1/CentOS/pike/Binary/noarch/epel-rpm-macros-7-18.noarch.rpm $ rpm -vK /import/mirrors/CentOS/stx-r1/CentOS/pike/Binary/noarch/python2-rpm-macros-3-18.el7.noarch.rpm $ rpm -vK /import/mirrors/CentOS/stx-r1/CentOS/pike/Binary/noarch/python-rpm-macros-3-18.el7.noarch.rpm $ rpm -vK /import/mirrors/CentOS/stx-r1/CentOS/pike/Binary/noarch/python-srpm-macros-3-18.el7.noarch.rpm From scott.little at windriver.com Tue Jul 17 20:48:02 2018 From: scott.little at windriver.com (Scott Little) Date: Tue, 17 Jul 2018 16:48:02 -0400 Subject: [Starlingx-discuss] Restructuring round 2 In-Reply-To: References: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> <7f3c17c2-1997-4d8e-5414-13d41cdb846b@linux.intel.com> Message-ID: On 18-07-17 03:55 PM, Dean Troyer wrote: > We need to stick to the review process as much as possible, we're > already getting into some bad habits that will be hard to break. > > I think it would be useful to post the reviews as soon as possible and > mark them WIP (workflow -1) so they don't merge. That's where the > specific discussions about tweaks can/should happen. > > Also, if the reviews for each repo are stacked we can build a manifest > file to pull the reviews directly from Gerrit and actually test a > build before merging it. My challenge is trying to not disrupt the next set of updates being back ported to StarlingX from Titanium.  If I go and re-arrange everything, their patch sets won't apply.  Conversely their updates will break many of the relocation patches if they were created based on todays content. The model I've adopted is to create scripts to perform all the relocations.  I can generate the relocation patches in a hurry. I'll run the script as soon as the last titanium back port is accepted or abandoned.  The result will be a blizzard of reviews of content that's already been reviewed.  The internal stx-integ relocations with 'git mv' are trivial enough.  However, package moves between repos will look like large blocks of all new code, when it's nothing of the sort.  The only competent reviewer is likely another script that runs diff a lot. My fears are: 1) Standard reviews will just invite lots of comments on the code content, rather than it's location and a few path changes.  Those battles should already have been fought when the code was delivered to it's original location. 2) A long review process might prevent Titanium from converging, forcing a third back port cycle. Hoping someone has suggestions .... Scott From scott.little at windriver.com Tue Jul 17 21:01:49 2018 From: scott.little at windriver.com (Scott Little) Date: Tue, 17 Jul 2018 17:01:49 -0400 Subject: [Starlingx-discuss] Restructuring round 2 In-Reply-To: <9d0618b7-cea6-6050-92f4-c77f92161443@linux.intel.com> References: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> <7f3c17c2-1997-4d8e-5414-13d41cdb846b@linux.intel.com> <78f0da9b-9498-7b06-0901-2e411e2fd6a8@windriver.com> <9d0618b7-cea6-6050-92f4-c77f92161443@linux.intel.com> Message-ID: <5c986a48-61cc-da72-f65e-08a11d81a644@windriver.com> If we are talking centos + epel, the packages that need upstreaming can be quickly identified by looking for 'mirror:' in centos/srpm_path grep 'mirror:' $(find .  -path '*/centos/srpm_path') ./base/centos-release/centos/srpm_path:mirror:Source/centos-release-7-4.1708.el7.centos.src.rpm ./base/lshell/centos/srpm_path:mirror:Source/lshell-0.9.16-5.el7.src.rpm ./base/setup/centos/srpm_path:mirror:Source/setup-2.8.71-7.el7.src.rpm ./base/libevent/centos/srpm_path:mirror:Source/libevent-2.0.21-4.el7.src.rpm ./base/dhcp/centos/srpm_path:mirror:Source/dhcp-4.2.5-58.el7.centos.src.rpm ./base/openssh/centos/srpm_path:mirror:Source/openssh-7.4p1-12.el7_4.src.rpm ./base/initscripts/centos/srpm_path:mirror:Source/initscripts-9.49.39-1.el7.src.rpm ./base/util-linux/centos/srpm_path:mirror:Source/util-linux-2.23.2-43.el7.src.rpm ./base/vim/centos/srpm_path:mirror:Source/vim-7.4.160-2.el7.src.rpm ./base/lighttpd/centos/srpm_path:mirror:Source/lighttpd-1.4.45-1.el7.src.rpm ./base/novnc/centos/srpm_path:mirror:Source/novnc-0.6.2-1.el7.src.rpm ./base/ntp/centos/srpm_path:mirror:Source/ntp-4.2.6p5-25.el7.centos.2.src.rpm ./base/pam/centos/srpm_path:mirror:Source/pam-1.1.8-18.el7.src.rpm ./base/sanlock/centos/srpm_path:mirror:Source/sanlock-3.5.0-1.el7.src.rpm ./base/shadow-utils/centos/srpm_path:mirror:Source/shadow-utils-4.1.5.1-24.el7.src.rpm ./base/sudo/centos/srpm_path:mirror:Source/sudo-1.8.19p2-11.el7_4.src.rpm ./base/systemd/centos/srpm_path:mirror:Source/systemd-219-42.el7_4.1.src.rpm ./base/watchdog/centos/srpm_path:mirror:Source/watchdog-5.13-11.el7.src.rpm ./base/net-snmp/centos/srpm_path:mirror:Source/net-snmp-5.7.2-28.el7.src.rpm ./base/memcached/centos/srpm_path:mirror:Source/memcached-1.4.39-1.el7.src.rpm ./base/cluster-resource-agents/centos/srpm_path:mirror:Source/resource-agents-3.9.5-105.el7.src.rpm ./base/bash/centos/srpm_path:mirror:Source/bash-4.2.46-29.el7_4.src.rpm ./base/haproxy/centos/srpm_path:mirror:Source/haproxy-1.5.18-6.el7.src.rpm ./base/netpbm/centos/srpm_path:mirror:Source/netpbm-10.61.02-9.el7.src.rpm ./base/anaconda/centos/srpm_path:mirror:Source/anaconda-21.48.22.121-1.el7.centos.src.rpm ./base/crontabs/centos/srpm_path:mirror:Source/crontabs-1.11-6.20121102git.el7.src.rpm ./base/dnsmasq/centos/srpm_path:mirror:Source/dnsmasq-2.76-2.el7_4.2.src.rpm ./base/rsync/centos/srpm_path:mirror:Source/rsync-3.0.9-18.el7.src.rpm ./kubernetes/docker-ce/centos/srpm_path:mirror:Source/docker-ce-18.03.1.ce-1.el7.centos.src.rpm ./kubernetes/kubernetes/centos/srpm_path:mirror:Source/kubernetes-1.10.0-1.el7.src.rpm ./networking/openvswitch/centos/srpm_path:mirror:/Source/openvswitch-2.9.0-3.el7.src.rpm ./networking/scapy/centos/srpm_path:mirror:Source/scapy-2.3.3-1.el7.src.rpm ./networking/iproute/centos/srpm_path:mirror:Source/iproute-3.10.0-87.el7.src.rpm ./networking/net-tools/centos/srpm_path:mirror:Source/net-tools-2.0-0.22.20131004git.el7.src.rpm ./networking/iptables/centos/srpm_path:mirror:Source/iptables-1.4.21-18.0.1.el7.centos.src.rpm ./python/python-eventlet/centos/srpm_path:mirror:Source/python-eventlet-0.18.4-2.el7.src.rpm ./python/python-requests/centos/srpm_path:mirror:Source/python-requests-2.14.2-1.el7.src.rpm ./python/python-django/centos/srpm_path:mirror:Source/python-django-1.8.14-1.el7.src.rpm ./python/python-gunicorn/centos/srpm_path:mirror:Source/python-gunicorn-19.7.1-1.fc27.src.rpm ./python/python-2.7.5/centos/srpm_path:mirror:Source/python-2.7.5-58.el7.src.rpm ./security/audit/centos/srpm_path:mirror:Source/audit-2.7.6-3.el7.src.rpm ./security/tpm2-tools/centos/srpm_path:mirror:Source/tpm2-tools-1.1.0-7.el7.src.rpm ./security/shim-signed/centos/srpm_path:mirror:Source/shim-signed-12-1.el7.centos.src.rpm ./security/shim-unsigned/centos/srpm_path:mirror:Source/shim-12-1.el7.centos.src.rpm ./security/tboot/centos/srpm_path:mirror:Source/tboot-1.9.5-1.el7.src.rpm ./security/python-keyring/centos/srpm_path:mirror:Source/python-keyring-5.7.1-1.el7.src.rpm ./kernel/kernel-std/centos/srpm_path:mirror:Source/kernel-3.10.0-862.3.2.el7.src.rpm ./kernel/kernel-rt/centos/srpm_path:mirror:Source/kernel-rt-3.10.0-862.3.2.rt56.808.el7.src.rpm ./logging/syslog-ng/centos/srpm_path:mirror:Source/syslog-ng-3.5.6-3.el7.src.rpm ./logging/logrotate/centos/srpm_path:mirror:Source/logrotate-3.8.6-14.el7.src.rpm ./ldap/nss-pam-ldapd/centos/srpm_path:mirror:Source/nss-pam-ldapd-0.8.13-8.el7.src.rpm ./ldap/openldap/centos/srpm_path:mirror:Source/openldap-2.4.44-5.el7.src.rpm ./filesystem/nfs-utils/centos/srpm_path:mirror:Source/nfs-utils-1.3.0-0.48.el7.src.rpm ./filesystem/e2fsprogs/centos/srpm_path:mirror:Source/e2fsprogs-1.42.9-10.el7.src.rpm ./filesystem/iscsi-initiator-utils/centos/srpm_path:mirror:Source/iscsi-initiator-utils-6.2.0.874-4.el7.src.rpm ./filesystem/parted/centos/srpm_path:mirror:Source/parted-3.1-28.el7.src.rpm ./config/puppet-4.8.2/centos/srpm_path:mirror:Source/puppet-4.8.2-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-ceilometer-11.3.0/centos/srpm_path:mirror:Source/puppet-ceilometer-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-ceph-2.2.0/centos/srpm_path:mirror:Source/puppet-ceph-2.2.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-cinder-11.3.0/centos/srpm_path:mirror:Source/puppet-cinder-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-glance-11.3.0/centos/srpm_path:mirror:Source/puppet-glance-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-heat-11.3.0/centos/srpm_path:mirror:Source/puppet-heat-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-horizon-9.5.0/centos/srpm_path:mirror:Source/puppet-horizon-9.5.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-ironic-11.3.0/centos/srpm_path:mirror:Source/puppet-ironic-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-keystone-11.3.0/centos/srpm_path:mirror:Source/puppet-keystone-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-magnum-11.3.0/centos/srpm_path:mirror:Source/puppet-magnum-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-memcached-3.0.2/centos/srpm_path:mirror:Source/puppet-memcached-3.0.2-1.adf8b63git.el7.src.rpm ./config/puppet-modules/openstack/puppet-murano-11.3.0/centos/srpm_path:mirror:Source/puppet-murano-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-neutron-11.3.0/centos/srpm_path:mirror:Source/puppet-neutron-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-nova-11.4.0/centos/srpm_path:mirror:Source/puppet-nova-11.4.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-openstacklib-11.3.0/centos/srpm_path:mirror:Source/puppet-openstacklib-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-oslo-11.3.0/centos/srpm_path:mirror:Source/puppet-oslo-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-panko-11.3.0/centos/srpm_path:mirror:Source/puppet-panko-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-swift-11.3.0/centos/srpm_path:mirror:Source/puppet-swift-11.3.0-1.el7.src.rpm ./config/puppet-modules/puppet-haproxy-1.5.0/centos/srpm_path:mirror:Source/puppet-haproxy-1.5.0-2.6ee8180git.el7.src.rpm ./config/puppet-modules/puppet-rabbitmq-5.5.0/centos/srpm_path:mirror:Source/puppet-rabbitmq-5.6.0-4.5ac45degit.el7.src.rpm ./config/puppet-modules/puppet-staging/centos/srpm_path:mirror:Source/puppet-staging-1.0.4-1.b466d93git.el7.src.rpm ./config/puppet-modules/puppet-stdlib-4.12.0/centos/srpm_path:mirror:Source/puppet-stdlib-4.13.1-2.dcef77agit.el7.src.rpm ./config/facter/centos/srpm_path:mirror:Source/facter-2.4.4-4.el7.src.rpm ./virt/libvirt-python/centos/srpm_path:mirror:Source/libvirt-python-3.5.0-1.fc24.src.rpm ./virt/cloud-init/centos/srpm_path:mirror:Source/cloud-init-0.7.9-9.el7.centos.2.src.rpm ./grub/grubby/centos/srpm_path:mirror:Source/grubby-8.28-23.el7.src.rpm ./grub/grub2/centos/srpm_path:mirror:Source/grub2-2.02-0.64.el7.centos.src.rpm ./database/python-psycopg2/centos/srpm_path:mirror:Source/python-psycopg2-2.5.1-3.el7.src.rpm On 18-07-17 03:56 PM, Saul Wold wrote: > > > On 07/17/2018 12:25 PM, Scott Little wrote: >> The full list of packages in stx-integ after proposed changes >> > Thanks, this help me understand some of the context and content in the > re-arranged packages. > > I understand your thought of functionality over upstream source, but > it would make it clearer, especially for the OS upstream bits to all > be contained in "base".  That way we work so reduce that one directory > to zero. > > I am not going to block, just saying.  I am currently pursuing the > existing stx tree trying to understand some of the changes.  I will > send email on those later. > > Sau! > > >> >> On 18-07-17 03:10 PM, Scott Little wrote: >>> On 18-07-17 12:38 PM, Saul Wold wrote: >>>> >>>> Do you have a full "after" list, that might help then just seeing >>>> what's being relocated. >>> [SL]  will send seperately >> >> base/anaconda >> base/bash >> base/centos-release >> base/cgcs-users >> base/cluster-resource-agents >> base/crontabs >> base/dhcp >> base/dnsmasq >> base/dpkg >> base/haproxy >> base/initscripts >> base/libevent >> base/libfdt >> base/lighttpd >> base/lshell >> base/memcached >> base/netpbm >> base/net-snmp >> base/novnc >> base/ntp >> base/openssh >> base/pam >> base/rpm >> base/rsync >> base/sanlock >> base/setup >> base/shadow-utils >> base/sudo >> base/systemd >> base/util-linux >> base/vim >> base/watchdog >> >> ceph/python-cephclient >> >> config/facter >> config/puppet-4.8.2 >> config/puppet-modules/openstack/puppet-ceilometer-11.3.0 >> config/puppet-modules/openstack/puppet-ceph-2.2.0 >> config/puppet-modules/openstack/puppet-cinder-11.3.0 >> config/puppet-modules/openstack/puppet-glance-11.3.0 >> config/puppet-modules/openstack/puppet-heat-11.3.0 >> config/puppet-modules/openstack/puppet-horizon-9.5.0 >> config/puppet-modules/openstack/puppet-ironic-11.3.0 >> config/puppet-modules/openstack/puppet-keystone-11.3.0 >> config/puppet-modules/openstack/puppet-magnum-11.3.0 >> config/puppet-modules/openstack/puppet-memcached-3.0.2 >> config/puppet-modules/openstack/puppet-murano-11.3.0 >> config/puppet-modules/openstack/puppet-neutron-11.3.0 >> config/puppet-modules/openstack/puppet-nova-11.4.0 >> config/puppet-modules/openstack/puppet-openstacklib-11.3.0 >> config/puppet-modules/openstack/puppet-oslo-11.3.0 >> config/puppet-modules/openstack/puppet-panko-11.3.0 >> config/puppet-modules/openstack/puppet-swift-11.3.0 >> config/puppet-modules/puppet-boolean-1.0.2 >> config/puppet-modules/puppet-create_resources >> config/puppet-modules/puppet-dnsmasq >> config/puppet-modules/puppet-drbd-0.3.1 >> config/puppet-modules/puppet-filemapper >> config/puppet-modules/puppet-haproxy-1.5.0 >> config/puppet-modules/puppet-ldap >> config/puppet-modules/puppet-lvm >> config/puppet-modules/puppet-network >> config/puppet-modules/puppet-nslcd >> config/puppet-modules/puppet-postgresql-4.8.0 >> config/puppet-modules/puppet-puppi >> config/puppet-modules/puppet-rabbitmq-5.5.0 >> config/puppet-modules/puppet-staging >> config/puppet-modules/puppet-stdlib-4.12.0 >> >> config-files/io-scheduler >> >> database/mariadb >> database/python-psycopg2 >> >> filesystem/drbd/drbd-tools >> filesystem/e2fsprogs >> filesystem/filesystem-scripts >> filesystem/iscsi-initiator-utils >> filesystem/nfscheck >> filesystem/nfs-utils >> filesystem/parted >> >> grub/grub2 >> grub/grubby >> >> kernel/kernel-rt >> kernel/kernel-std >> >> kernel/kernel-modules/drbd >> kernel/kernel-modules/integrity >> kernel/kernel-modules/intel-e1000e >> kernel/kernel-modules/intel-i40e >> kernel/kernel-modules/intel-i40evf >> kernel/kernel-modules/intel-ixgbe >> kernel/kernel-modules/intel-ixgbevf >> kernel/kernel-modules/mlnx-ofa_kernel >> kernel/kernel-modules/qat17 >> kernel/kernel-modules/tpmdd >> >> kubernetes/docker-ce >> kubernetes/kubernetes >> >> ldap/ldapscripts >> ldap/nss-pam-ldapd >> ldap/openldap >> >> logging/logmgmt >> logging/logrotate >> logging/syslog-ng >> >> monitoring/collectd-extensions >> monitoring/influxdb-extensions >> >> networking/iproute >> networking/iptables >> networking/lldpd >> networking/mellanox/libibverbs >> networking/mellanox/libmlx4 >> networking/mellanox/libmlx5 >> networking/mellanox/mlx4-config >> networking/mellanox/rdma-core >> networking/net-tools >> networking/openvswitch >> networking/python-ryu >> networking/scapy >> >> python/python-2.7.5 >> python/python-django >> python/python-eventlet >> python/python-gunicorn >> python/python-requests >> python/python-setuptools >> python/python-smartpm >> >> restapi-doc >> >> security/audit >> security/libtpms >> security/python-keyring >> security/shim-signed >> security/shim-unsigned >> security/spectre-meltdown-checker >> security/swtpm >> security/tboot >> security/tpm2-openssl-engine >> security/tpm2-tools >> security/tss2 >> security/wrs-ssl >> >> strorage-drivers/python-3parclient >> strorage-drivers/python-lefthandclient >> >> tools/collector >> tools/engtools/hostdata-collectors >> tools/monitor-tools >> tools/vm-topology >> >> utilities/branding >> utilities/build-info >> utilities/namespace-utils >> utilities/nova-utils >> utilities/platform-util >> utilities/tis-extensions >> utilities/update-motd >> >> virt/cloud-init >> virt/libvirt >> virt/libvirt-python >> virt/qemu >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From guillermo.a.ponce.castaneda at intel.com Tue Jul 17 21:25:43 2018 From: guillermo.a.ponce.castaneda at intel.com (Ponce Castaneda, Guillermo A) Date: Tue, 17 Jul 2018 21:25:43 +0000 Subject: [Starlingx-discuss] Adding packages to build .lst files In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F3A9@ALA-MBD.corp.ad.wrs.com> Message-ID: <939BBE33-59F9-4D2C-B813-B32CB0006634@intel.com> Hi all, Yes, this tool I made can come in handy to search for packages faster. The tools utilizes a Google API to search for specific files, it can search for any kind of file, althought we have to use it for rpms and srpms. Google API returns a list of sites that match the search criteria, this script goes to that list and search on the html for the tags looking for the name of the package and tries to download them all. In the end you get a directory tree like this: downloads// with none or many files. Why is it written in node.js and not in any other language? I know how to code on it (more or less) and the Google API was way easier to use than python's, the one that I was able to make work on python was for python 2. This script is still far from being perfect but I could move faster if more people uses it and gives me feedback, what I have identified as improvement opportunities are: - It could receive a list of packages instead of a single one. - It could look for rpm integrity or at least if the package is signed. I will add it to the stx-tools repo shortly and see if it goes through. On 7/17/18, 3:45 PM, "Arce Moreno, Abraham" wrote: > From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] > Sent: Tuesday, July 17, 2018 3:29 PM > To: Dean Troyer ; Penney, Don > > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Adding packages to build .lst files > > > As a side note: I started following the README in stx-tools to try out > > the download utility, to hopefully glean a little more info about the > > LST files on my own. I setup a fresh repo yesterday afternoon, then > > setup and launched the docker image this morning. The download fails: > > > > done!! > > finish 1st round of RPM downloading successfully! > > ERROR: -------RPMs missing 4 in yumdownloader with L1 match > > --------------- > > > > The failed RPMs are recorded: > > $ cat centos_rpms_missing_L1.txt > > epel-rpm-macros-7-18.noarch.rpm > > python2-rpm-macros-3-18.el7.noarch.rpm > > python-rpm-macros-3-18.el7.noarch.rpm > > python-srpm-macros-3-18.el7.noarch.rpm > > Memo has created a node script to download those dependencies and it > perfectly worked For me today to gather the specific versions. I am wondering > if we can take out to help with our missing Packages for now, here are the > steps using that tool: > > # cat output/3rd-centos_rpms_missing_L1.txt > output/3rd_rpms_missing_L1.txt \ > output/3rd_srpms_missing_L1.txt output/centos_rpms_missing_L1.txt > output/centos_srpms_missing_L1.txt > epel-rpm-macros-7-18.noarch.rpm > python2-rpm-macros-3-18.el7.noarch.rpm > python-rpm-macros-3-18.el7.noarch.rpm > python-srpm-macros-3-18.el7.noarch.rpm > > $ node index.js -p epel-rpm-macros-7-18.noarch.rpm > $ node index.js -p python2-rpm-macros-3-18.el7.noarch.rpm > $ node index.js -p python-rpm-macros-3-18.el7.noarch.rpm > $ node index.js -p python-srpm-macros-3-18.el7.noarch.rpm > > All Key ID for these packages ok > > $ rpm -vK /import/mirrors/CentOS/stx-r1/CentOS/pike/Binary/noarch/epel- > rpm-macros-7-18.noarch.rpm > $ rpm -vK /import/mirrors/CentOS/stx- > r1/CentOS/pike/Binary/noarch/python2-rpm-macros-3-18.el7.noarch.rpm > $ rpm -vK /import/mirrors/CentOS/stx- > r1/CentOS/pike/Binary/noarch/python-rpm-macros-3-18.el7.noarch.rpm > $ rpm -vK /import/mirrors/CentOS/stx- > r1/CentOS/pike/Binary/noarch/python-srpm-macros-3-18.el7.noarch.rpm > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Wed Jul 18 00:17:45 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 17 Jul 2018 19:17:45 -0500 Subject: [Starlingx-discuss] Adding packages to build .lst files In-Reply-To: <939BBE33-59F9-4D2C-B813-B32CB0006634@intel.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F3A9@ALA-MBD.corp.ad.wrs.com> <939BBE33-59F9-4D2C-B813-B32CB0006634@intel.com> Message-ID: On Tue, Jul 17, 2018 at 4:25 PM, Ponce Castaneda, Guillermo A wrote: > Why is it written in node.js and not in any other language? > I know how to code on it (more or less) and the Google API was way easier to use > than python's, the one that I was able to make work on python was for python 2. Is there any other node in STX? I am not aware of any and would be reluctant to add yet another platform requirement to this build system. I know I'd be reluctant to install node on my laptop just to run this... it's bad enough the python bits I have to go through to install OpenStackClient and I wrote the dang thing. > This script is still far from being perfect but I could move faster if more > people uses it and gives me feedback, what I have identified as improvement > opportunities are: > - It could receive a list of packages instead of a single one. > - It could look for rpm integrity or at least if the package is signed. Validating signed packages is an absolute requirement. > I will add it to the stx-tools repo shortly and see if it goes through. Posting a review is the right way to share something to get feedback on it. Make it clear in the commit message that is your intention, optionally even set workflow -1 to prevent it from being merged although sometimes people don't even look at those... dt -- Dean Troyer dtroyer at gmail.com From abraham.arce.moreno at intel.com Wed Jul 18 03:23:12 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Wed, 18 Jul 2018 03:23:12 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> <9d889c66-a603-2d12-dd70-c8fb3b3911d0@windriver.com> <93814834B4855241994F290E959305C752F48CC6@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48FA8@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F49046@SHSMSX104.ccr.corp.intel.com> <93bfa378-9f26-d4c8-8f37-ad23a543e756@windriver.com> <738B5DAD-15A1-404C-A65C-952A699A1D98@intel.com> <93814834B4855241994F290E959305C752F496DD@SHSMSX104.ccr.corp.intel.com> Message-ID: > > Mingyuan asked me checked comps.xml yesterday, it didn't exist. > > I also could not create it through executing generate-cgcs-centos-repo.sh. > > Thanks Zhipeng, Mingyuan, > > Understood about the problem. Yong and Erich were talking a few days ago > internally about the way to handle comps.xml and they suggested a minimal > xml so time to bring this conversation out. > > How about this first version [0]? If it is possible for you to test and see if we > can start taking this as our base file. > > [0] https://pastebin.com/KMB8QLNX Review submitted: "Add minimal comps.xml file into cgcs-centos generator" https://review.openstack.org/#/c/583445 From guillermo.a.ponce.castaneda at intel.com Wed Jul 18 13:26:47 2018 From: guillermo.a.ponce.castaneda at intel.com (Ponce Castaneda, Guillermo A) Date: Wed, 18 Jul 2018 13:26:47 +0000 Subject: [Starlingx-discuss] Adding packages to build .lst files In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F3A9@ALA-MBD.corp.ad.wrs.com> <939BBE33-59F9-4D2C-B813-B32CB0006634@intel.com> Message-ID: >On 7/17/18, 7:18 PM, "Dean Troyer" wrote: >On Tue, Jul 17, 2018 at 4:25 PM, Ponce Castaneda, Guillermo A > wrote: >> Why is it written in node.js and not in any other language? >> I know how to code on it (more or less) and the Google API was way easier to use >> than python's, the one that I was able to make work on python was for python 2. >Is there any other node in STX? I am not aware of any and would be >reluctant to add yet another platform requirement to this build >system. I know I'd be reluctant to install node on my laptop just to >run this... it's bad enough the python bits I have to go through to >install OpenStackClient and I wrote the dang thing. That is correct, I do not think there is another node.js code, and that is why I also created a Dockerfile so nobody has to install node on their machines and just run it inside a container. >> This script is still far from being perfect but I could move faster if more >> people uses it and gives me feedback, what I have identified as improvement >> opportunities are: >> - It could receive a list of packages instead of a single one. >> - It could look for rpm integrity or at least if the package is signed. >Validating signed packages is an absolute requirement. Totally agree, I haven't found a way to do it with node instructions, but I guess I can just add an 'rpm -vK' command inside a subprocess like instruction. >> I will add it to the stx-tools repo shortly and see if it goes through. >Posting a review is the right way to share something to get feedback >on it. Make it clear in the commit message that is your intention, >optionally even set workflow -1 to prevent it from being merged >although sometimes people don't even look at those... >dt -- Dean Troyer dtroyer at gmail.com From Don.Penney at windriver.com Wed Jul 18 14:47:02 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 18 Jul 2018 14:47:02 +0000 Subject: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F9E3@ALA-MBD.corp.ad.wrs.com> Hi all, The StarlingX.repo file in stx-tools has all the CentOS 7.4.1708 binary repos disabled and is instead using 7.3.1611. This would likely explain why some of the specified RPMs cannot be downloaded via yum, as they were upversioned in 7.4. Was this done for a particular reason, or is it a configuration error? Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Jul 18 15:16:04 2018 From: scott.little at windriver.com (Scott Little) Date: Wed, 18 Jul 2018 11:16:04 -0400 Subject: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F9E3@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F9E3@ALA-MBD.corp.ad.wrs.com> Message-ID: StarlingX should be based on Centos 7.4 for the vast majority of packages.  I think there are a dozen that have made the move to 7.5.  There are also a few that we blacklisted and are pulling from earlier releases. I'll attach my black_list notes as they exist today.  I'll have to audit them to make sure my notes are up to date. Scott On 18-07-18 10:47 AM, Penney, Don wrote: > > Hi all, > > The StarlingX.repo file in stx-tools has all the CentOS 7.4.1708 > binary repos disabled and is instead using 7.3.1611. This would likely > explain why some of the specified RPMs cannot be downloaded via yum, > as they were upversioned in 7.4. > > Was this done for a particular reason, or is it a configuration error? > > *Don Penney*, Developer, *Wind River* > > > > _______________________________________________ > 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: -------------- next part -------------- # frozen zeromq-4.1.4-5.el.src.rpm zeromq-4.1.4-5.el.x86_64.rpm zeromq-devel-4.1.4-5.el.x86_64.rpm zeromq-debuginfo-4.1.4-5.el.x86_64.rpm cppzmq-devel-4.1.4-5.el.x86_64.rpm zeromq-4.1.4-5.el7.src.rpm zeromq-4.1.4-5.el7.x86_64.rpm zeromq-devel-4.1.4-5.el7.x86_64.rpm zeromq-debuginfo-4.1.4-5.el7.x86_64.rpm cppzmq-devel-4.1.4-5.el7.x86_64.rpm zeromq-4.1.4-9.el7.src.rpm zeromq-4.1.4-9.el7.x86_64.rpm zeromq-devel-4.1.4-9.el7.x86_64.rpm zeromq-debuginfo-4.1.4-9.el7.x86_64.rpm cppzmq-devel-4.1.4-9.el7.x86_64.rpm # python2-oauth2client 4.0.0 breaks openstack-cinder # File "/usr/lib/python2.7/site-packages/googleapiclient/errors.py", line 26, in # from oauth2client import util # ImportError: cannot import name util python-oauth2client-4.0.0-2.el7.src.rpm python2-oauth2client-4.0.0-2.el7.noarch.rpm # Compiled from downloads libibverbs-1.2.1-1.el7.src.rpm libibverbs-1.2.1-1.el7.x86_64.rpm libibverbs-devel-1.2.1-1.el7.x86_64.rpm libibverbs-devel-static-1.2.1-1.el7.x86_64.rpm libibverbs-utils-1.2.1-1.el7.x86_64.rpm # Compiled from downloads libmlx4-1.2.1-1.el7.src.rpm libmlx4-1.2.1-1.el7.x86_64.rpm libmlx4-static-1.2.1-1.el7.x86_64.rpm # Compiled from downloads libmlx5-1.2.1-8.el7.src.rpm libmlx5-1.2.1-8.el7.x86_64.rpm libmlx5-static-1.2.1-8.el7.x86_64.rpm # Compiled from git libvirt-2.0.0-10.el7_3.5.x86_64.rpm libvirt-client-2.0.0-10.el7_3.5.x86_64.rpm libvirt-daemon-2.0.0-10.el7_3.5.x86_64.rpm libvirt-daemon-config-network-2.0.0-10.el7_3.5.x86_64.rpm libvirt-daemon-config-nwfilter-2.0.0-10.el7_3.5.x86_64.rpm libvirt-daemon-driver-interface-2.0.0-10.el7_3.5.x86_64.rpm libvirt-daemon-driver-lxc-2.0.0-10.el7_3.5.x86_64.rpm libvirt-daemon-driver-network-2.0.0-10.el7_3.5.x86_64.rpm libvirt-daemon-driver-nodedev-2.0.0-10.el7_3.5.x86_64.rpm libvirt-daemon-driver-nwfilter-2.0.0-10.el7_3.5.x86_64.rpm libvirt-daemon-driver-qemu-2.0.0-10.el7_3.5.x86_64.rpm libvirt-daemon-driver-secret-2.0.0-10.el7_3.5.x86_64.rpm libvirt-daemon-driver-storage-2.0.0-10.el7_3.5.x86_64.rpm libvirt-daemon-kvm-2.0.0-10.el7_3.5.x86_64.rpm libvirt-daemon-lxc-2.0.0-10.el7_3.5.x86_64.rpm libvirt-devel-2.0.0-10.el7_3.5.x86_64.rpm libvirt-docs-2.0.0-10.el7_3.5.x86_64.rpm libvirt-lock-sanlock-2.0.0-10.el7_3.5.x86_64.rpm libvirt-login-shell-2.0.0-10.el7_3.5.x86_64.rpm libvirt-nss-2.0.0-10.el7_3.5.x86_64.rpm # Compiled from downloads dpkg-1.17.27-1.el7.x86_64.rpm dpkg-debuginfo-1.17.27-1.el7.x86_64.rpm dpkg-devel-1.17.27-1.el7.x86_64.rpm dpkg-dev-1.17.27-1.el7.noarch.rpm dpkg-perl-1.17.27-1.el7.noarch.rpm # Compiled from tarball mariadb-10.1.20-1.el7.x86_64.rpm mariadb-bench-10.1.20-1.el7.x86_64.rpm mariadb-common-10.1.20-1.el7.x86_64.rpm mariadb-config-10.1.20-1.el7.x86_64.rpm mariadb-connect-engine-10.1.20-1.el7.x86_64.rpm mariadb-devel-10.1.20-1.el7.x86_64.rpm mariadb-embedded-10.1.20-1.el7.x86_64.rpm mariadb-embedded-devel-10.1.20-1.el7.x86_64.rpm mariadb-errmsg-10.1.20-1.el7.x86_64.rpm mariadb-errmsg-10.1.20-1.el7.x86_64.rpm mariadb-server-10.1.20-1.el7.x86_64.rpm mariadb-server-galera-10.1.20-1.el7.x86_64.rpm mariadb-test-10.1.20-1.el7.x86_64.rpm # Compiled from git openstack-ceilometer-api-7.0.1-1.el7.noarch.rpm openstack-ceilometer-central-7.0.1-1.el7.noarch.rpm openstack-ceilometer-collector-7.0.1-1.el7.noarch.rpm openstack-ceilometer-common-7.0.1-1.el7.noarch.rpm openstack-ceilometer-compute-7.0.1-1.el7.noarch.rpm openstack-ceilometer-ipmi-7.0.1-1.el7.noarch.rpm openstack-ceilometer-notification-7.0.1-1.el7.noarch.rpm openstack-ceilometer-polling-7.0.1-1.el7.noarch.rpm python-ceilometer-7.0.1-1.el7.noarch.rpm python-ceilometer-tests-7.0.1-1.el7.noarch.rpm # Compiled from git openstack-cinder-9.1.2-1.el7.noarch.rpm openstack-cinder-doc-9.1.2-1.el7.noarch.rpm python-cinder-9.1.2-1.el7.noarch.rpm python-cinder-tests-9.1.2-1.el7.noarch.rpm # Compiled from git openstack-glance-13.0.0-1.el7.noarch.rpm openstack-glance-doc-13.0.0-1.el7.noarch.rpm python-glance-13.0.0-1.el7.noarch.rpm python-glance-tests-13.0.0-1.el7.noarch.rpm # Compiled from git openstack-heat-api-7.0.2-1.el7.noarch.rpm openstack-heat-api-cfn-7.0.2-1.el7.noarch.rpm openstack-heat-api-cloudwatch-7.0.2-1.el7.noarch.rpm openstack-heat-common-7.0.2-1.el7.noarch.rpm openstack-heat-engine-7.0.2-1.el7.noarch.rpm python-heat-tests-7.0.2-1.el7.noarch.rpm # Compiled from git openstack-keystone-10.0.1-1.el7.noarch.rpm openstack-keystone-doc-10.0.1-1.el7.noarch.rpm python-keystone-10.0.1-1.el7.noarch.rpm python-keystone-tests-10.0.1-1.el7.noarch.rpm # Compiled from git openstack-murano-api-3.0.0-1.el7.noarch.rpm openstack-murano-cf-api-3.0.0-1.el7.noarch.rpm openstack-murano-common-3.0.0-1.el7.noarch.rpm openstack-murano-doc-3.0.0-1.el7.noarch.rpm openstack-murano-engine-3.0.0-1.el7.noarch.rpm openstack-murano-ui-3.0.0-1.el7.noarch.rpm openstack-murano-ui-doc-3.0.0-1.el7.noarch.rpm python-murano-tests-3.0.0-1.el7.noarch.rpm # Compiled from git openstack-neutron-9.2.0-1.el7.noarch.rpm openstack-neutron-common-9.2.0-1.el7.noarch.rp openstack-neutron-linuxbridge-9.2.0-1.el7.noarch.rpm openstack-neutron-macvtap-agent-9.2.0-1.el7.noarch.rpm openstack-neutron-metering-agent-9.2.0-1.el7.noarch.rpm openstack-neutron-ml2-9.2.0-1.el7.noarch.rpm openstack-neutron-openvswitch-9.2.0-1.el7.noarch.rpm openstack-neutron-rpc-server-9.2.0-1.el7.noarch.rpm openstack-neutron-sriov-nic-agent-9.2.0-1.el7.noarch.rpm python-neutron-9.2.0-1.el7.noarch.rpm python-neutron-tests-9.2.0-1.el7.noarch.rpm # Compiled from git openstack-nova-14.0.3-1.el7.noarch.rpm openstack-nova-api-14.0.3-1.el7.noarch.rpm openstack-nova-cells-14.0.3-1.el7.noarch.rpm openstack-nova-cert-14.0.3-1.el7.noarch.rpm openstack-nova-common-14.0.3-1.el7.noarch.rpm openstack-nova-compute-14.0.3-1.el7.noarch.rpm openstack-nova-conductor-14.0.3-1.el7.noarch.rpm openstack-nova-console-14.0.3-1.el7.noarch.rpm openstack-nova-doc-14.0.3-1.el7.noarch.rpm openstack-nova-network-14.0.3-1.el7.noarch.rpm openstack-nova-novncproxy-14.0.3-1.el7.noarch.rpm openstack-nova-placement-api-14.0.3-1.el7.noarch.rp openstack-nova-scheduler-14.0.3-1.el7.noarch.rpm openstack-nova-serialproxy-14.0.3-1.el7.noarch.rpm openstack-nova-spicehtml5proxy-14.0.3-1.el7.noarch.rpm python-nova-14.0.3-1.el7.noarch.rpm python-nova-tests-14.0.3-1.el7.noarch.rpm # Compiled from git python-ceilometerclient-doc-2.6.2-1.el7.noarch.rpm python2-ceilometerclient-2.6.2-1.el7.noarch.rpm # Compiled from git python-cinderclient-doc-1.9.0-1.el7.noarch.rpm python2-cinderclient-1.9.0-1.el7.noarch.rpm # Compiled from git python-django-horizon-10.0.2-1.el7.noarch.rpm python-django-horizon-doc-10.0.2-1.el7.noarch.rpm openstack-dashboard-10.0.2-1.el7.noarch.rpm openstack-dashboard-theme-10.0.2-1.el7.noarch.rp # Compiled from git python-glanceclient-doc-2.5.0-1.el7.noarch.rpm python2-glanceclient-2.5.0-1.el7.noarch.rpm # Compiled from git python-muranoclient-doc-0.11.1-1.el7.noarch.rpm # Compiled from git python-networking-odl-3.1.0-1.el7.noarch.rpm # Compiled from git python-neutronclient-doc-6.0.0-2.el7.noarch.rpm python2-neutronclient-6.0.0-2.el7.noarch.rpm # Compiled from git python-novaclient-doc-6.0.0-1.el7.noarch.rpm python2-novaclient-6.0.0-1.el7.noarch.rpm # Compiled from git python2-muranoclient-0.11.1-1.el7.noarch.rpm # Compiled from git python2-openstacksdk-0.9.5-1.el7.noarch.rpm python2-openstacksdk-tests-0.9.5-1.el7.noarch.rpm # R16 reads as newer than 18, we want 18 or better erlang-doc-R16B-03.18.el7.noarch.rpm erlang-appmon-R16B-03.18.el7.x86_64.rpm erlang-asn1-R16B-03.18.el7.x86_64.rpm erlang-common_test-R16B-03.18.el7.x86_64.rpm erlang-compiler-R16B-03.18.el7.x86_64.rpm erlang-cosEvent-R16B-03.18.el7.x86_64.rpm erlang-cosEventDomain-R16B-03.18.el7.x86_64.rpm erlang-cosFileTransfer-R16B-03.18.el7.x86_64.rpm erlang-cosNotification-R16B-03.18.el7.x86_64.rpm erlang-cosProperty-R16B-03.18.el7.x86_64.rpm erlang-cosTime-R16B-03.18.el7.x86_64.rpm erlang-cosTransactions-R16B-03.18.el7.x86_64.rpm erlang-crypto-R16B-03.18.el7.x86_64.rpm erlang-debugger-R16B-03.18.el7.x86_64.rpm erlang-debuginfo-R16B-03.18.el7.x86_64.rpm erlang-dialyzer-R16B-03.18.el7.x86_64.rpm erlang-diameter-R16B-03.18.el7.x86_64.rpm erlang-edoc-R16B-03.18.el7.x86_64.rpm erlang-eldap-R16B-03.18.el7.x86_64.rpm erlang-erl_docgen-R16B-03.18.el7.x86_64.rpm erlang-erl_interface-R16B-03.18.el7.x86_64.rpm erlang-erts-R16B-03.18.el7.x86_64.rpm erlang-et-R16B-03.18.el7.x86_64.rpm erlang-eunit-R16B-03.18.el7.x86_64.rpm erlang-examples-R16B-03.18.el7.x86_64.rpm erlang-gs-R16B-03.18.el7.x86_64.rpm erlang-hipe-R16B-03.18.el7.x86_64.rpm erlang-ic-R16B-03.18.el7.x86_64.rpm erlang-inets-R16B-03.18.el7.x86_64.rpm erlang-jinterface-R16B-03.18.el7.x86_64.rpm erlang-kernel-R16B-03.18.el7.x86_64.rpm erlang-megaco-R16B-03.18.el7.x86_64.rpm erlang-mnesia-R16B-03.18.el7.x86_64.rpm erlang-observer-R16B-03.18.el7.x86_64.rpm erlang-odbc-R16B-03.18.el7.x86_64.rpm erlang-orber-R16B-03.18.el7.x86_64.rpm erlang-os_mon-R16B-03.18.el7.x86_64.rpm erlang-otp_mibs-R16B-03.18.el7.x86_64.rpm erlang-parsetools-R16B-03.18.el7.x86_64.rpm erlang-percept-R16B-03.18.el7.x86_64.rpm erlang-pman-R16B-03.18.el7.x86_64.rpm erlang-public_key-R16B-03.18.el7.x86_64.rpm erlang-R16B-03.18.el7.x86_64.rpm erlang-reltool-R16B-03.18.el7.x86_64.rpm erlang-runtime_tools-R16B-03.18.el7.x86_64.rpm erlang-sasl-R16B-03.18.el7.x86_64.rpm erlang-snmp-R16B-03.18.el7.x86_64.rpm erlang-ssh-R16B-03.18.el7.x86_64.rpm erlang-ssl-R16B-03.18.el7.x86_64.rpm erlang-stdlib-R16B-03.18.el7.x86_64.rpm erlang-syntax_tools-R16B-03.18.el7.x86_64.rpm erlang-test_server-R16B-03.18.el7.x86_64.rpm erlang-toolbar-R16B-03.18.el7.x86_64.rpm erlang-tools-R16B-03.18.el7.x86_64.rpm erlang-tv-R16B-03.18.el7.x86_64.rpm erlang-typer-R16B-03.18.el7.x86_64.rpm erlang-webtool-R16B-03.18.el7.x86_64.rpm erlang-wx-R16B-03.18.el7.x86_64.rpm erlang-xmerl-R16B-03.18.el7.x86_64.rpm erlang-R16B-03.18.el7.src.rpm erlang-18.3.4.4-1.el7.src.rpm erlang-18.3.4.4-2.el7.src.rpm erlang-18.3.4.4-2.el7.x86_64.rpm erlang-asn1-18.3.4.4-2.el7.x86_64.rpm erlang-compiler-18.3.4.4-2.el7.x86_64.rpm erlang-cosEvent-18.3.4.4-2.el7.x86_64.rpm erlang-cosEventDomain-18.3.4.4-2.el7.x86_64.rpm erlang-cosFileTransfer-18.3.4.4-2.el7.x86_64.rpm erlang-cosNotification-18.3.4.4-2.el7.x86_64.rpm erlang-cosProperty-18.3.4.4-2.el7.x86_64.rpm erlang-cosTime-18.3.4.4-2.el7.x86_64.rpm erlang-cosTransactions-18.3.4.4-2.el7.x86_64.rpm erlang-crypto-18.3.4.4-2.el7.x86_64.rpm erlang-diameter-18.3.4.4-2.el7.x86_64.rpm erlang-doc-18.3.4.4-2.el7.noarch.rpm erlang-edoc-18.3.4.4-2.el7.x86_64.rpm erlang-eldap-18.3.4.4-2.el7.x86_64.rpm erlang-erl_docgen-18.3.4.4-2.el7.x86_64.rpm erlang-erl_interface-18.3.4.4-2.el7.x86_64.rpm erlang-erts-18.3.4.4-2.el7.x86_64.rpm erlang-eunit-18.3.4.4-2.el7.x86_64.rpm erlang-gs-18.3.4.4-2.el7.x86_64.rpm erlang-hipe-18.3.4.4-2.el7.x86_64.rpm erlang-ic-18.3.4.4-2.el7.x86_64.rpm erlang-inets-18.3.4.4-2.el7.x86_64.rpm erlang-jinterface-18.3.4.4-2.el7.x86_64.rpm erlang-kernel-18.3.4.4-2.el7.x86_64.rpm erlang-mnesia-18.3.4.4-2.el7.x86_64.rpm erlang-odbc-18.3.4.4-2.el7.x86_64.rpm erlang-orber-18.3.4.4-2.el7.x86_64.rpm erlang-os_mon-18.3.4.4-2.el7.x86_64.rpm erlang-otp_mibs-18.3.4.4-2.el7.x86_64.rpm erlang-parsetools-18.3.4.4-2.el7.x86_64.rpm erlang-percept-18.3.4.4-2.el7.x86_64.rpm erlang-public_key-18.3.4.4-2.el7.x86_64.rpm erlang-runtime_tools-18.3.4.4-2.el7.x86_64.rpm erlang-sasl-18.3.4.4-2.el7.x86_64.rpm erlang-snmp-18.3.4.4-2.el7.x86_64.rpm erlang-ssh-18.3.4.4-2.el7.x86_64.rpm erlang-ssl-18.3.4.4-2.el7.x86_64.rpm erlang-stdlib-18.3.4.4-2.el7.x86_64.rpm erlang-syntax_tools-18.3.4.4-2.el7.x86_64.rpm erlang-tools-18.3.4.4-2.el7.x86_64.rpm erlang-xmerl-18.3.4.4-2.el7.x86_64.rpm openstack-ceilometer-api-8.0.0-2.el7.noarch.rpm openstack-ceilometer-central-8.0.0-2.el7.noarch.rpm openstack-ceilometer-collector-8.0.0-2.el7.noarch.rpm openstack-ceilometer-common-8.0.0-2.el7.noarch.rpm openstack-ceilometer-compute-8.0.0-2.el7.noarch.rpm openstack-ceilometer-ipmi-8.0.0-2.el7.noarch.rpm openstack-ceilometer-notification-8.0.0-2.el7.noarch.rpm openstack-ceilometer-polling-8.0.0-2.el7.noarch.rpm openstack-cinder-10.0.0-1.el7.noarch.rpm openstack-cinder-doc-10.0.0-1.el7.noarch.rpm openstack-dashboard-11.0.0-1.el7.noarch.rpm openstack-glance-14.0.0-1.el7.noarch.rpm openstack-glance-2015.1.4-1.el7.noarch.rpm openstack-glance-doc-14.0.0-1.el7.noarch.rpm openstack-glance-doc-2015.1.4-1.el7.noarch.rpm openstack-heat-api-6.1.0-1.el7.noarch.rpm openstack-heat-api-8.0.0-1.el7.noarch.rpm openstack-heat-api-cfn-6.1.0-1.el7.noarch.rpm openstack-heat-api-cfn-8.0.0-1.el7.noarch.rpm openstack-heat-api-cloudwatch-6.1.0-1.el7.noarch.rpm openstack-heat-api-cloudwatch-8.0.0-1.el7.noarch.rpm openstack-heat-common-6.1.0-1.el7.noarch.rpm openstack-heat-common-8.0.0-1.el7.noarch.rpm openstack-heat-engine-6.1.0-1.el7.noarch.rpm openstack-heat-engine-8.0.0-1.el7.noarch.rpm openstack-keystone-11.0.0-1.el7.noarch.rpm openstack-keystone-doc-11.0.0-1.el7.noarch.rpm openstack-murano-api-3.2.0-1.el7.noarch.rpm openstack-murano-cf-api-3.2.0-1.el7.noarch.rpm openstack-murano-common-3.2.0-1.el7.noarch.rpm openstack-murano-doc-3.2.0-1.el7.noarch.rpm openstack-murano-engine-3.2.0-1.el7.noarch.rpm openstack-murano-ui-3.2.0-1.el7.noarch.rpm openstack-murano-ui-doc-3.2.0-1.el7.noarch.rpm openstack-neutron-10.0.0-1.el7.noarch.rpm openstack-neutron-linuxbridge-10.0.0-1.el7.noarch.rpm openstack-neutron-macvtap-agent-10.0.0-1.el7.noarch.rpm openstack-neutron-metering-agent-10.0.0-1.el7.noarch.rpm openstack-neutron-ml2-10.0.0-1.el7.noarch.rpm openstack-neutron-openvswitch-10.0.0-1.el7.noarch.rpm openstack-neutron-rpc-server-10.0.0-1.el7.noarch.rpm openstack-neutron-sriov-nic-agent-10.0.0-1.el7.noarch.rpm openstack-nova-15.0.0-1.el7.noarch.rpm openstack-nova-api-15.0.0-1.el7.noarch.rpm openstack-nova-cells-15.0.0-1.el7.noarch.rpm openstack-nova-cert-15.0.0-1.el7.noarch.rpm openstack-nova-common-15.0.0-1.el7.noarch.rpm openstack-nova-compute-15.0.0-1.el7.noarch.rpm openstack-nova-conductor-15.0.0-1.el7.noarch.rpm openstack-nova-console-15.0.0-1.el7.noarch.rpm openstack-nova-doc-15.0.0-1.el7.noarch.rpm openstack-nova-network-15.0.0-1.el7.noarch.rpm openstack-nova-novncproxy-15.0.0-1.el7.noarch.rpm openstack-nova-scheduler-15.0.0-1.el7.noarch.rpm openstack-nova-serialproxy-15.0.0-1.el7.noarch.rpm openstack-nova-spicehtml5proxy-15.0.0-1.el7.noarch.rpm python2-ceilometerclient-2.8.0-1.el7.noarch.rpm python2-cinderclient-1.11.0-1.el7.noarch.rpm python2-cinderclient-1.6.0-2.el7.noarch.rpm python2-glanceclient-2.0.1-2.el7.noarch.rpm python2-glanceclient-2.6.0-1.el7.noarch.rpm python2-muranoclient-0.12.0-1.el7.noarch.rpm python2-neutronclient-6.1.0-1.el7.noarch.rpm python2-novaclient-3.3.2-1.el7.noarch.rpm python2-novaclient-7.1.0-1.el7.noarch.rpm python2-openstacksdk-0.9.13-1.el7.noarch.rpm python2-openstacksdk-tests-0.9.13-1.el7.noarch.rpm python-ceilometer-8.0.0-2.el7.noarch.rpm python-ceilometerclient-doc-2.8.0-1.el7.noarch.rpm python-ceilometer-tests-8.0.0-2.el7.noarch.rpm python-cinder-10.0.0-1.el7.noarch.rpm python-cinderclient-doc-1.11.0-1.el7.noarch.rpm python-cinderclient-doc-1.6.0-2.el7.noarch.rpm python-cinder-tests-10.0.0-1.el7.noarch.rpm python-django-horizon-11.0.0-1.el7.noarch.rpm python-django-horizon-doc-11.0.0-1.el7.noarch.rpm python-glance-14.0.0-1.el7.noarch.rpm python-glance-2015.1.4-1.el7.noarch.rpm python-glanceclient-doc-0.17.3-2.el7.noarch.rpm python-glanceclient-doc-2.0.1-2.el7.noarch.rpm python-glanceclient-doc-2.6.0-1.el7.noarch.rpm python-glance-tests-14.0.0-1.el7.noarch.rpm python-heat-tests-6.1.0-1.el7.noarch.rpm python-heat-tests-8.0.0-1.el7.noarch.rpm python-keystone-11.0.0-1.el7.noarch.rpm python-keystone-tests-11.0.0-1.el7.noarch.rpm python-muranoclient-doc-0.12.0-1.el7.noarch.rpm python-murano-tests-3.2.0-1.el7.noarch.rpm python-networking-odl-4.0.0-1.el7.noarch.rpm python-neutron-10.0.0-1.el7.noarch.rpm python-neutronclient-doc-6.1.0-1.el7.noarch.rpm python-neutron-tests-10.0.0-1.el7.noarch.rpm python-nova-15.0.0-1.el7.noarch.rpm python-novaclient-doc-2.23.3-1.el7.noarch.rpm python-novaclient-doc-3.3.2-1.el7.noarch.rpm python-novaclient-doc-7.1.0-1.el7.noarch.rpm python-nova-tests-15.0.0-1.el7.noarch.rpm # python-pyelftools-0.22 is importing a removed class in python-constructs-2.8.10, revert to our prior python-constructs-2.5.1 python-construct-2.8.10-1.el7.src.rpm python-construct-2.8.10-1.el7.noarch.rpm mariadb-5.5.56-2.el7.x86_64.rpm mariadb-bench-5.5.56-2.el7.x86_64.rpm mariadb-devel-5.5.56-2.el7.x86_64.rpm mariadb-embedded-5.5.56-2.el7.x86_64.rpm mariadb-embedded-devel-5.5.56-2.el7.x86_64.rpm mariadb-server-5.5.56-2.el7.x86_64.rpm mariadb-test-5.5.56-2.el7.x86_64.rpm openstack-glance-14.0.0-2.el7.noarch.rpm openstack-glance-15.0.0-1.el7.noarch.rpm openstack-glance-doc-14.0.0-2.el7.noarch.rpm openstack-glance-doc-15.0.0-1.el7.noarch.rpm openstack-murano-api-4.0.0-1.el7.noarch.rpm openstack-murano-cf-api-4.0.0-1.el7.noarch.rpm openstack-murano-common-4.0.0-1.el7.noarch.rpm openstack-murano-doc-4.0.0-1.el7.noarch.rpm openstack-murano-engine-4.0.0-1.el7.noarch.rpm openstack-murano-ui-4.0.0-1.el7.noarch.rpm openstack-murano-ui-doc-4.0.0-1.el7.noarch.rpm python2-ceilometerclient-2.8.1-1.el7.noarch.rpm python2-ceilometerclient-2.9.0-1.el7.noarch.rpm python2-cinderclient-3.1.0-1.el7.noarch.rpm python2-glanceclient-2.8.0-1.el7.noarch.rpm python2-muranoclient-0.14.0-1.el7.noarch.rpm python2-openstacksdk-0.9.17-1.el7.noarch.rpm python2-openstacksdk-tests-0.9.17-1.el7.noarch.rpm python-ceilometerclient-doc-2.8.1-1.el7.noarch.rpm python-ceilometerclient-doc-2.9.0-1.el7.noarch.rpm python-cinderclient-doc-3.1.0-1.el7.noarch.rpm python-glance-14.0.0-2.el7.noarch.rpm python-glance-15.0.0-1.el7.noarch.rpm python-glanceclient-doc-2.8.0-1.el7.noarch.rpm python-glance-tests-14.0.0-2.el7.noarch.rpm python-glance-tests-15.0.0-1.el7.noarch.rpm python-muranoclient-doc-0.14.0-1.el7.noarch.rpm python-murano-tests-4.0.0-1.el7.noarch.rpm python-networking-odl-11.0.0-1.el7.noarch.rpm From dtroyer at gmail.com Wed Jul 18 16:47:21 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 18 Jul 2018 11:47:21 -0500 Subject: [Starlingx-discuss] Adding packages to build .lst files In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F3A9@ALA-MBD.corp.ad.wrs.com> <939BBE33-59F9-4D2C-B813-B32CB0006634@intel.com> Message-ID: On Wed, Jul 18, 2018 at 8:26 AM, Ponce Castaneda, Guillermo A wrote: > That is correct, I do not think there is another node.js code, and that is why I > also created a Dockerfile so nobody has to install node on their machines and > just run it inside a container. I'm sorry but I do not consider requiring Docker and some non-trivial OS image to run a simple script to be an improvement. It isn't just the installation of the runtime it is also the cognitive overhead of requiring another bit of language expertise to maintain the tool. If this were a node project I'd say the same thing about introducing a python script. dt -- Dean Troyer dtroyer at gmail.com From bruce.e.jones at intel.com Wed Jul 18 17:01:39 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 18 Jul 2018 17:01:39 +0000 Subject: [Starlingx-discuss] Use of Storyboard Message-ID: <9A85D2917C58154C960D95352B22818BAB56371A@fmsmsx117.amr.corp.intel.com> At the project call this morning we discussed some of the limitations of Storyboard. We're going to think about what alternatives we might want to use, but just to remind everyone, we don't have any right now. So please continue to use Storyboard. If you are working on a Task, please make sure it's assigned to you in the tool. Please keep the task up to date - change the state as you work on it (ToDo -> Progress -> etc...) and add comments to document how the work is going. Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillermo.a.ponce.castaneda at intel.com Wed Jul 18 17:42:39 2018 From: guillermo.a.ponce.castaneda at intel.com (Ponce Castaneda, Guillermo A) Date: Wed, 18 Jul 2018 17:42:39 +0000 Subject: [Starlingx-discuss] Adding packages to build .lst files In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F3A9@ALA-MBD.corp.ad.wrs.com> <939BBE33-59F9-4D2C-B813-B32CB0006634@intel.com> Message-ID: <2B6889A0-364E-4BC3-9190-D8227727B92F@intel.com> >On 7/18/18, 11:47 AM, "Dean Troyer" wrote: >On Wed, Jul 18, 2018 at 8:26 AM, Ponce Castaneda, Guillermo A > wrote: >> That is correct, I do not think there is another node.js code, and that is why I >> also created a Dockerfile so nobody has to install node on their machines and >> just run it inside a container. >I'm sorry but I do not consider requiring Docker and some non-trivial >OS image to run a simple script to be an improvement. It isn't just >the installation of the runtime it is also the cognitive overhead of >requiring another bit of language expertise to maintain the tool. If >this were a node project I'd say the same thing about introducing a >python script. Thanks for the feedback Dean, I will the improve this tool on the points you are mentioning and will try going at it again. >dt Guillermo Ponce -- Dean Troyer dtroyer at gmail.com From jesus.ornelas.aguayo at intel.com Wed Jul 18 18:23:25 2018 From: jesus.ornelas.aguayo at intel.com (Ornelas Aguayo, Jesus) Date: Wed, 18 Jul 2018 18:23:25 +0000 Subject: [Starlingx-discuss] Use koji to create repository with required RPMS Message-ID: <9FCFFF8D-4089-48F2-B14E-CD8ABC8AF560@intel.com> Hi all, As we know we use the centos-mirror-tools from the stx-tools repo to download the required RPMS to build StarlingX, this tool downloads the packages from the following list files: Filename Packages Description rpms_from_3rd_parties.lst 9 Third party packages without repository (downloaded by wget) rpms_from_centos_3rd_parties.lst. 152 Third party packages with repository rpms_from_centos_repo.lst 1699 Centos packages with repository As time goes by, Some packages disappear and we need to replace the repositories or urls , and in some scenarios the specific package version disappears. This can be fixed by getting the source code of the packages mentioned above and their dependencies ( ~3900 packages) and use koji to build the required versions, this way we can host a repository with the required RPMS and SRPMS to build starlingX . I would like to open a discussion of this proposal, the first approach would be start hosting the rpms_from_3rd_parties.lst(downloaded by wget) and replacing the package repository in the centos-mirror-tools list, so changes will be gradually. Once this is completed we can follow the same process for the the rpms_from_centos_3rd_parties.lst and ending with the rms_from_centos_repo.lst. From dtroyer at gmail.com Wed Jul 18 18:51:19 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 18 Jul 2018 13:51:19 -0500 Subject: [Starlingx-discuss] Design and Documentation for our Starlingx/Release Plan Web Page. In-Reply-To: <03D458D5BAFF6041973594B00B4E58CE590EABB4@fmsmsx101.amr.corp.intel.com> References: <03D458D5BAFF6041973594B00B4E58CE590EABB4@fmsmsx101.amr.corp.intel.com> Message-ID: [Formatting in these messages is likely to be mangled for many readers and completely stripped in the archives. Attachments are also stripped in the archives. Here is how the original message looks: http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000232.html] On Mon, Jul 16, 2018 at 5:54 PM, Hernandez Gonzalez, Fernando < fernando.hernandez.gonzalez at intel.com> wrote: > Please take a look into this first proposal, our first approach is > releasing something clean and neat, comments and suggestions are well > welcome, more things can be added/removed if necessary. > I think we need to include a definition of exactly what a StarlingX Release/milestone is: * A StarlingX milestone/release is a branch in the source code repositories that: * is considered stable * will have no additional features added * will backport bug fixes for critical issues only * will be maintained in the canonical repositories for a specified minimum period * The list of repos included is maintained in stx-manifest/default.xml (or similar) for any given release. (Note: this file included non-StarlingX-managed repos, only repos from the "starlingx" and "stx-staging" remotes are included.) Based on that definition the release process for a milestone might look like: * check out the current repos * create branches at either HEAD or a specific SHA * push branches back to master repos * create new review to update the .gitreview file in each repo (this _should_ be the first merge on the new branch, there may be additional branch-specific updates required here at some point (release notes are common)) * update default.xml in the stx-manifest stable branch to pull the milestone branches rather than master The process for the periodic releases would include the milestone process and additionally: * when the RC period is concluded tag HEAD on the stable branches to denote the actual release We should consider if we want to branch stx-tools or not as its intended to be release-agnostic and should not have any release-specific contents. We may want to branch it anyway. Thoughts? dt -- Dean Troyer dtroyer at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Jul 18 19:50:48 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 18 Jul 2018 19:50:48 +0000 Subject: [Starlingx-discuss] Design and Documentation for our Starlingx/Release Plan Web Page. In-Reply-To: References: <03D458D5BAFF6041973594B00B4E58CE590EABB4@fmsmsx101.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB563CDE@fmsmsx117.amr.corp.intel.com> This LGTM. I would add one more bullet item to the definition: * can re-built at a later date e e.g. to add a fix. So anything that might impact the build should be branched, including (possibly) stx-tools. If/when we ever start hosting binaries, we’ll want to branch everything from the toolchain on up. brucej From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Wednesday, July 18, 2018 11:51 AM To: Hernandez Gonzalez, Fernando Cc: Troyer, Dean ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Design and Documentation for our Starlingx/Release Plan Web Page. [Formatting in these messages is likely to be mangled for many readers and completely stripped in the archives. Attachments are also stripped in the archives. Here is how the original message looks: http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000232.html] On Mon, Jul 16, 2018 at 5:54 PM, Hernandez Gonzalez, Fernando > wrote: Please take a look into this first proposal, our first approach is releasing something clean and neat, comments and suggestions are well welcome, more things can be added/removed if necessary. I think we need to include a definition of exactly what a StarlingX Release/milestone is: * A StarlingX milestone/release is a branch in the source code repositories that: * is considered stable * will have no additional features added * will backport bug fixes for critical issues only * will be maintained in the canonical repositories for a specified minimum period * The list of repos included is maintained in stx-manifest/default.xml (or similar) for any given release. (Note: this file included non-StarlingX-managed repos, only repos from the "starlingx" and "stx-staging" remotes are included.) Based on that definition the release process for a milestone might look like: * check out the current repos * create branches at either HEAD or a specific SHA * push branches back to master repos * create new review to update the .gitreview file in each repo (this _should_ be the first merge on the new branch, there may be additional branch-specific updates required here at some point (release notes are common)) * update default.xml in the stx-manifest stable branch to pull the milestone branches rather than master The process for the periodic releases would include the milestone process and additionally: * when the RC period is concluded tag HEAD on the stable branches to denote the actual release We should consider if we want to branch stx-tools or not as its intended to be release-agnostic and should not have any release-specific contents. We may want to branch it anyway. Thoughts? dt -- Dean Troyer dtroyer at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Wed Jul 18 20:05:24 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Wed, 18 Jul 2018 15:05:24 -0500 Subject: [Starlingx-discuss] Design and Documentation for our Starlingx/Release Plan Web Page. In-Reply-To: <9A85D2917C58154C960D95352B22818BAB563CDE@fmsmsx117.amr.corp.intel.com> References: <03D458D5BAFF6041973594B00B4E58CE590EABB4@fmsmsx101.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB563CDE@fmsmsx117.amr.corp.intel.com> Message-ID: On Wed, Jul 18, 2018 at 2:50 PM, Jones, Bruce E wrote: > This LGTM. I would add one more bullet item to the definition: > * can re-built at a later date > > e e.g. to add a fix. So anything that might impact the build should be > branched, including (possibly) stx-tools. That is part of the intent but I'll add that explicitly... And that's enough reason to go ahead and branch stx-tools. dt -- Dean Troyer dtroyer at gmail.com From yong.hu at intel.com Thu Jul 19 00:47:35 2018 From: yong.hu at intel.com (Hu, Yong) Date: Thu, 19 Jul 2018 00:47:35 +0000 Subject: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F9E3@ALA-MBD.corp.ad.wrs.com> Message-ID: <4F11E6D3-0E43-4B57-A041-EAA93D3C2279@intel.com> What if we move to the latest 7.5 1804? Do you see any drawbacks or hard dependencies still on old packages? Regards, Yong From: Scott Little Date: Wednesday, 18 July 2018 at 11:17 PM To: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? StarlingX should be based on Centos 7.4 for the vast majority of packages. I think there are a dozen that have made the move to 7.5. There are also a few that we blacklisted and are pulling from earlier releases. I'll attach my black_list notes as they exist today. I'll have to audit them to make sure my notes are up to date. Scott On 18-07-18 10:47 AM, Penney, Don wrote: Hi all, The StarlingX.repo file in stx-tools has all the CentOS 7.4.1708 binary repos disabled and is instead using 7.3.1611. This would likely explain why some of the specified RPMs cannot be downloaded via yum, as they were upversioned in 7.4. Was this done for a particular reason, or is it a configuration error? Don Penney, Developer, Wind River _______________________________________________ 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 Brent.Rowsell at windriver.com Thu Jul 19 01:04:12 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Thu, 19 Jul 2018 01:04:12 +0000 Subject: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? In-Reply-To: <4F11E6D3-0E43-4B57-A041-EAA93D3C2279@intel.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F9E3@ALA-MBD.corp.ad.wrs.com> <4F11E6D3-0E43-4B57-A041-EAA93D3C2279@intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0DA3E4@ALA-MBD.corp.ad.wrs.com> Moving to 7.5 should be considered as part of the upcoming release, but retirement of existing patches needs to be part of that plan. Brent From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Wednesday, July 18, 2018 8:48 PM To: Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? What if we move to the latest 7.5 1804? Do you see any drawbacks or hard dependencies still on old packages? Regards, Yong From: Scott Little > Date: Wednesday, 18 July 2018 at 11:17 PM To: "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? StarlingX should be based on Centos 7.4 for the vast majority of packages. I think there are a dozen that have made the move to 7.5. There are also a few that we blacklisted and are pulling from earlier releases. I'll attach my black_list notes as they exist today. I'll have to audit them to make sure my notes are up to date. Scott On 18-07-18 10:47 AM, Penney, Don wrote: Hi all, The StarlingX.repo file in stx-tools has all the CentOS 7.4.1708 binary repos disabled and is instead using 7.3.1611. This would likely explain why some of the specified RPMs cannot be downloaded via yum, as they were upversioned in 7.4. Was this done for a particular reason, or is it a configuration error? Don Penney, Developer, Wind River _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Thu Jul 19 01:26:21 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 19 Jul 2018 01:26:21 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> <9d889c66-a603-2d12-dd70-c8fb3b3911d0@windriver.com> <93814834B4855241994F290E959305C752F48CC6@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48FA8@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F49046@SHSMSX104.ccr.corp.intel.com> <93bfa378-9f26-d4c8-8f37-ad23a543e756@windriver.com> <738B5DAD-15A1-404C-A65C-952A699A1D98@intel.com> <93814834B4855241994F290E959305C752F496DD@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C752F4D61A@SHSMSX104.ccr.corp.intel.com> Hi Abraham, I have tried your comps.xml, it can work! Now I have finished all build except iso building Thanks! zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月18日 11:23 To: Liu, ZhipengS ; Hu, Yong ; 'Scott Little' ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Mingyuan asked me checked comps.xml yesterday, it didn't exist. > > I also could not create it through executing generate-cgcs-centos-repo.sh. > > Thanks Zhipeng, Mingyuan, > > Understood about the problem. Yong and Erich were talking a few days > ago internally about the way to handle comps.xml and they suggested a > minimal xml so time to bring this conversation out. > > How about this first version [0]? If it is possible for you to test > and see if we can start taking this as our base file. > > [0] https://pastebin.com/KMB8QLNX Review submitted: "Add minimal comps.xml file into cgcs-centos generator" https://review.openstack.org/#/c/583445 From cindy.xie at intel.com Thu Jul 19 06:56:57 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Thu, 19 Jul 2018 06:56:57 +0000 Subject: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB0DA3E4@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F9E3@ALA-MBD.corp.ad.wrs.com> <4F11E6D3-0E43-4B57-A041-EAA93D3C2279@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0DA3E4@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B2DFACE@SHSMSX104.ccr.corp.intel.com> Brent, Scott, This is great information! It turns out the way of handling the retired RPM packages are different from WR internal mirror and Intel scripts (to generate mirror): - WR will move the retired RPM and its dependency RPM from 7.4 repo to 7.5 repo, and this is where the blacklist from Scott coming from; - Intel turn to other 3rd party repo (hosted by somebody else other than RHS) and download the exact same version (the missing ones from RHS repo due to retirement). To me, if WR has gone through the RPM dependency map analysis and correctly migrate the retired RPMs from 7.4 to 7.5, then I think it’s a more reliable way. Also this is prefer way from security point of view. @ Scott, I think this worthy a discussion in Bruce’s meeting for how to setup external mirror. And I wish this could be a short-term solution before Cesar’s long-term solution up & running. Then we can ensure external build can work for WR. Thanks. - cindy From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Thursday, July 19, 2018 9:04 AM To: Hu, Yong ; Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? Moving to 7.5 should be considered as part of the upcoming release, but retirement of existing patches needs to be part of that plan. Brent From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Wednesday, July 18, 2018 8:48 PM To: Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? What if we move to the latest 7.5 1804? Do you see any drawbacks or hard dependencies still on old packages? Regards, Yong From: Scott Little > Date: Wednesday, 18 July 2018 at 11:17 PM To: "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? StarlingX should be based on Centos 7.4 for the vast majority of packages. I think there are a dozen that have made the move to 7.5. There are also a few that we blacklisted and are pulling from earlier releases. I'll attach my black_list notes as they exist today. I'll have to audit them to make sure my notes are up to date. Scott On 18-07-18 10:47 AM, Penney, Don wrote: Hi all, The StarlingX.repo file in stx-tools has all the CentOS 7.4.1708 binary repos disabled and is instead using 7.3.1611. This would likely explain why some of the specified RPMs cannot be downloaded via yum, as they were upversioned in 7.4. Was this done for a particular reason, or is it a configuration error? Don Penney, Developer, Wind River _______________________________________________ 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 Jason.McKenna at windriver.com Thu Jul 19 14:36:20 2018 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Thu, 19 Jul 2018 14:36:20 +0000 Subject: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B2DFACE@SHSMSX104.ccr.corp.intel.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F9E3@ALA-MBD.corp.ad.wrs.com> <4F11E6D3-0E43-4B57-A041-EAA93D3C2279@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0DA3E4@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B2DFACE@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Cindy, Just as a heads’ up, we have not done the analysis to move from CentOS 7.4 to 7.5. The blacklist we generated was as we migrated from 7.2, through 7.3, and to 7.4. We’ve uprev’d a few packages since then to the match 7.5, but this has been on an as-required basis. -Jason From: Xie, Cindy Sent: July 19, 2018 2:57 AM To: Rowsell, Brent ; Hu, Yong ; Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? Brent, Scott, This is great information! It turns out the way of handling the retired RPM packages are different from WR internal mirror and Intel scripts (to generate mirror): - WR will move the retired RPM and its dependency RPM from 7.4 repo to 7.5 repo, and this is where the blacklist from Scott coming from; - Intel turn to other 3rd party repo (hosted by somebody else other than RHS) and download the exact same version (the missing ones from RHS repo due to retirement). To me, if WR has gone through the RPM dependency map analysis and correctly migrate the retired RPMs from 7.4 to 7.5, then I think it’s a more reliable way. Also this is prefer way from security point of view. @ Scott, I think this worthy a discussion in Bruce’s meeting for how to setup external mirror. And I wish this could be a short-term solution before Cesar’s long-term solution up & running. Then we can ensure external build can work for WR. Thanks. - cindy From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Thursday, July 19, 2018 9:04 AM To: Hu, Yong >; Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? Moving to 7.5 should be considered as part of the upcoming release, but retirement of existing patches needs to be part of that plan. Brent From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Wednesday, July 18, 2018 8:48 PM To: Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? What if we move to the latest 7.5 1804? Do you see any drawbacks or hard dependencies still on old packages? Regards, Yong From: Scott Little > Date: Wednesday, 18 July 2018 at 11:17 PM To: "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? StarlingX should be based on Centos 7.4 for the vast majority of packages. I think there are a dozen that have made the move to 7.5. There are also a few that we blacklisted and are pulling from earlier releases. I'll attach my black_list notes as they exist today. I'll have to audit them to make sure my notes are up to date. Scott On 18-07-18 10:47 AM, Penney, Don wrote: Hi all, The StarlingX.repo file in stx-tools has all the CentOS 7.4.1708 binary repos disabled and is instead using 7.3.1611. This would likely explain why some of the specified RPMs cannot be downloaded via yum, as they were upversioned in 7.4. Was this done for a particular reason, or is it a configuration error? Don Penney, Developer, Wind River _______________________________________________ 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 cindy.xie at intel.com Thu Jul 19 14:44:33 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Thu, 19 Jul 2018 14:44:33 +0000 Subject: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F9E3@ALA-MBD.corp.ad.wrs.com> <4F11E6D3-0E43-4B57-A041-EAA93D3C2279@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0DA3E4@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B2DFACE@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B2DFF67@SHSMSX104.ccr.corp.intel.com> Jason, Thanks for letting me know that the list was used for evaluating 7.2 to 7.3 as well as to 7.4. If we all think this is a quicker way to address the retired RPM issues, then we can start looking into using those retired packages from 7.5. Thanks. - cindy From: McKenna, Jason [mailto:Jason.McKenna at windriver.com] Sent: Thursday, July 19, 2018 10:36 PM To: Xie, Cindy ; Rowsell, Brent ; Hu, Yong ; Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? Hi Cindy, Just as a heads’ up, we have not done the analysis to move from CentOS 7.4 to 7.5. The blacklist we generated was as we migrated from 7.2, through 7.3, and to 7.4. We’ve uprev’d a few packages since then to the match 7.5, but this has been on an as-required basis. -Jason From: Xie, Cindy > Sent: July 19, 2018 2:57 AM To: Rowsell, Brent >; Hu, Yong >; Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? Brent, Scott, This is great information! It turns out the way of handling the retired RPM packages are different from WR internal mirror and Intel scripts (to generate mirror): - WR will move the retired RPM and its dependency RPM from 7.4 repo to 7.5 repo, and this is where the blacklist from Scott coming from; - Intel turn to other 3rd party repo (hosted by somebody else other than RHS) and download the exact same version (the missing ones from RHS repo due to retirement). To me, if WR has gone through the RPM dependency map analysis and correctly migrate the retired RPMs from 7.4 to 7.5, then I think it’s a more reliable way. Also this is prefer way from security point of view. @ Scott, I think this worthy a discussion in Bruce’s meeting for how to setup external mirror. And I wish this could be a short-term solution before Cesar’s long-term solution up & running. Then we can ensure external build can work for WR. Thanks. - cindy From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Thursday, July 19, 2018 9:04 AM To: Hu, Yong >; Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? Moving to 7.5 should be considered as part of the upcoming release, but retirement of existing patches needs to be part of that plan. Brent From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Wednesday, July 18, 2018 8:48 PM To: Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? What if we move to the latest 7.5 1804? Do you see any drawbacks or hard dependencies still on old packages? Regards, Yong From: Scott Little > Date: Wednesday, 18 July 2018 at 11:17 PM To: "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? StarlingX should be based on Centos 7.4 for the vast majority of packages. I think there are a dozen that have made the move to 7.5. There are also a few that we blacklisted and are pulling from earlier releases. I'll attach my black_list notes as they exist today. I'll have to audit them to make sure my notes are up to date. Scott On 18-07-18 10:47 AM, Penney, Don wrote: Hi all, The StarlingX.repo file in stx-tools has all the CentOS 7.4.1708 binary repos disabled and is instead using 7.3.1611. This would likely explain why some of the specified RPMs cannot be downloaded via yum, as they were upversioned in 7.4. Was this done for a particular reason, or is it a configuration error? Don Penney, Developer, Wind River _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Jul 19 16:36:31 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 19 Jul 2018 16:36:31 +0000 Subject: [Starlingx-discuss] Project weekly call minutes 7/18/18 Message-ID: <9A85D2917C58154C960D95352B22818BAB5640DB@fmsmsx117.amr.corp.intel.com> Notes for the 7/18/18 Meeting These can also be found at: https://etherpad.openstack.org/p/stx-status Recording: https://zoom.us/recording/share/uThwWwqzr_FABVy_8kBRpHVy2SXMKiFWoqqoINZr1e2wIumekTziMw * Branch created? Erick to send script to Dean for review. Build status? Build was completed but some docker/K8s issues needed to be added manually, plus several patches in review needed to be applied. WR has never been able to get a build to work. Erich to post the patches externally along with new bugs he just made. WR has found some gaps in the Getting Started guide. * Use of Storyboard for planning o Etherpad / Ethercalc - benefits & limitations - perhaps replacing these with google drive o Bruce's experiments with Boards o Ghada's [TAGS] and queries o We can invest in Storyboard development, we can invest in building our own apps using the API. We've been coming off of Jira and the comparison is not positive. The Foundation has a strong preference for open source tools. o Bruce and Ghada to meet and 1) brainstorm on how to best use SB and 2) get feedback from the team on how to improve the tool to provide input to the SB team o Can we separate bug tracking and feature tracking, e.g. spin up a bugzilla? o Bruce and Ghada to meet and discuss how to move this forward, jointly with Kendal and Ildiko * Update on build issues and documentation (Brent) * Repo restructuring proposal - feedback, impact on the team - most of the impact lands on WR who will manage this and post the ETA to the mailing list * Review ARs / status from the previous meetings o IRC channel logging code review in progress o Bruce to post starlingx intro slidedeck to wiki o Kernel upgrade is complete. Intel's ability to deeply test starlingx is limited. Can WR help test? * Plan for stx-staging repos (Brent) to be discussed at our (internal) sync meeting later today. * Continuous build and integration testing - Dariush * Long term we want to add Zuul test cases for API and unit testing to the check and gate queues. In progress. o Nightly builds were being run but have paused due to build debugging o Mirror checking scripts are being run daily o Investigating adding unit tests to the C/C++ code o There is no current way to run tests on real hardware in the community, only in our internal labs. What testing services to do we want to provide, what are the hardware configuration requirements. AR Bruce add to the PTG agenda. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Jul 19 17:43:29 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 19 Jul 2018 17:43:29 +0000 Subject: [Starlingx-discuss] Minutes from 7/19/18 Core team call Message-ID: <9A85D2917C58154C960D95352B22818BAB56455B@fmsmsx117.amr.corp.intel.com> This file is: https://etherpad.openstack.org/p/stx-cores Agenda items for the 7/19/18 call: * Recording: https://zoom.us/recording/share/r7hfh1Nw9KFbiQs_pJ_1QN9wL9jKVNJSUsg5zdVOp--wIumekTziMw * Project priorities https://wiki.openstack.org/wiki/StarlingX/Project_Priorities * Build system improvements - Bruce We reviewed and updated the Project Priorities page on the wiki. This included discussions on a number of topics including: * We agreed that the build issues are the most important near term problem to solve. * We discussed how/when to update the "base OS" (CentOS) components of the project. We agreed that we would start planning an upgrade to CentOS 7.5 and update to newer versions of qemu/libvirt as new sub-projects. * Patch upstreaming - can we move to SRPM patches instead of repos? * StarlingX staging repos - can we disposition, what is the long term plan? Near term WR will replace the existing kingbird repo (which isn't really kingbird) with new repos * Project decoupling - code changes to make each of the services more independent. WR is/will drive. * We raised addressing the Python2 issues to a higher priority level given the large scope of the work - we need to start sooner. Meanwhile Bruce has been working to get internal approval for Intel to host StarlingX binaries, and we had a discussion as to the implications of that for the project. The basic plan is to become a distro with a capital D and build/host all RPM packages in open yum repositories. We do not yet agree that this is the right approach - it's a ton of work to set up and maintain. But we have not been able identify a better long term solution so far. Saul has the lead for this. Near term there are reviews in flight to address this week's mirror issues. The team is actively soliciting input for both short and long term solutions to the build issues. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From eddie.ramirez at intel.com Thu Jul 19 18:37:19 2018 From: eddie.ramirez at intel.com (Ramirez, Eddie) Date: Thu, 19 Jul 2018 18:37:19 +0000 Subject: [Starlingx-discuss] Plan for stx-gui In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB0D3955@ALA-MBD.corp.ad.wrs.com> References: <2588653EBDFFA34B982FAF00F1B4844EBB0D3955@ALA-MBD.corp.ad.wrs.com> Message-ID: <979C5D06-2713-4205-9386-5CBF9CC2C244@intel.com> Right now, I don’t have a clear forecast for when these changes (stx-gui) will land into a build since new workarounds are tested and implemented as more “incompatibilities” are being found with upstream (horizon/pike). Good news is that, the most tedious longest task, which is packing all of WRS customizations done to horizon framework, the API layer and other utility functions for quotas, etc. is being exhaustively tested and documented for future reference. We will continue sending incoming changes to two different repos for some time: stx-gui and the stx-horizon. I will review them and make necessary adjustments to make them work on stx-gui as several LoCs and files are being moved around. From: "Rowsell, Brent" Date: Friday, July 13, 2018 at 6:04 PM To: "Ramirez, Eddie" , "starlingx-discuss at lists.starlingx.io" Subject: RE: [Starlingx-discuss] Plan for stx-gui Thanks Eddie. Do you have a forecast when your changes will be done ? Reason I am asking is we have some changes that will need to go into stx-gui. Thanks, Brent From: Ramirez, Eddie [mailto:eddie.ramirez at intel.com] Sent: Thursday, July 12, 2018 5:56 PM To: Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Plan for stx-gui Hi Brent, sorry I missed this email last week. Short answer: No, it’s not currently being pulled into the building pipeline just yet. I’m trying workarounds to get it working with the last version of Pike. Most of problems I run into are related to changes done to non-panels files like core classes, functions and settings that make STX specific functionality possible. I’m few steps away from trying these changes in the build process as I’m working on a dev environment and following the standard installation process of installing a Horizon plugin, that is, using the upstream horizon release and importing the package stx-gui into the namespace. From: "Rowsell, Brent" > Date: Thursday, July 12, 2018 at 2:29 PM To: "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] Plan for stx-gui Reposting. Does anyone have this on their to do list ? Brent From: Rowsell, Brent Sent: Wednesday, July 4, 2018 3:43 PM To: starlingx-discuss at lists.starlingx.io Subject: Plan for stx-gui What is the current plan for stx-gui ? It is currently not being pulled into the load and the StarlingX specific panels are still in stx-horizon. Brent -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Thu Jul 19 19:18:00 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 19 Jul 2018 14:18:00 -0500 Subject: [Starlingx-discuss] Plan for stx-gui In-Reply-To: <979C5D06-2713-4205-9386-5CBF9CC2C244@intel.com> References: <2588653EBDFFA34B982FAF00F1B4844EBB0D3955@ALA-MBD.corp.ad.wrs.com> <979C5D06-2713-4205-9386-5CBF9CC2C244@intel.com> Message-ID: On Thu, Jul 19, 2018 at 1:37 PM, Ramirez, Eddie wrote: > We will continue sending incoming changes to two different repos for some > time: stx-gui and the stx-horizon. I will review them and make necessary > adjustments to make them work on stx-gui as several LoCs and files are being > moved around. I don't see any activity in either repo, where is this being done? I think it will be better to roll it out in reviewable chunks rather than drop the whole thing at once, is this possible? dt -- Dean Troyer dtroyer at gmail.com From yong.hu at intel.com Fri Jul 20 01:00:43 2018 From: yong.hu at intel.com (Hu, Yong) Date: Fri, 20 Jul 2018 01:00:43 +0000 Subject: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F9E3@ALA-MBD.corp.ad.wrs.com> Message-ID: <07D8CE54-5C3A-4158-AEC9-C4EE8C7F67A7@intel.com> Hi Scott, I noticed in the black_list, there are a couple of RPMs (such as erlang*-R16B*.rpm”), which were in tis-r4-CentOS mirror but were NOT used since tis-r5-CentOS. As well, we are certain they are not needed for building R5 or current StarlingX codebase. Could we just drop them? BTW: in tis-r5-CentOS mirror, there are over 30,000 RPMs, while actually among those only ~1900 RPMs are necessary. regards, Yong From: Scott Little Date: Wednesday, 18 July 2018 at 11:17 PM To: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? StarlingX should be based on Centos 7.4 for the vast majority of packages. I think there are a dozen that have made the move to 7.5. There are also a few that we blacklisted and are pulling from earlier releases. I'll attach my black_list notes as they exist today. I'll have to audit them to make sure my notes are up to date. Scott On 18-07-18 10:47 AM, Penney, Don wrote: Hi all, The StarlingX.repo file in stx-tools has all the CentOS 7.4.1708 binary repos disabled and is instead using 7.3.1611. This would likely explain why some of the specified RPMs cannot be downloaded via yum, as they were upversioned in 7.4. Was this done for a particular reason, or is it a configuration error? Don Penney, Developer, Wind River _______________________________________________ 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 eddie.ramirez at intel.com Fri Jul 20 02:22:31 2018 From: eddie.ramirez at intel.com (Ramirez, Eddie) Date: Fri, 20 Jul 2018 02:22:31 +0000 Subject: [Starlingx-discuss] Plan for stx-gui In-Reply-To: References: <2588653EBDFFA34B982FAF00F1B4844EBB0D3955@ALA-MBD.corp.ad.wrs.com> <979C5D06-2713-4205-9386-5CBF9CC2C244@intel.com> Message-ID: <630BBEAE-8A16-46D9-98D7-04261995D0A9@intel.com> I share your concerns of proposing big changes, however there will be an initial “big one” that packs deep changes to the structure of the project. Subsequent patches should be smaller and focused on functionality or theme. Patch on gerrit: https://review.openstack.org/#/584201/ On 7/19/18, 12:18 PM, "Dean Troyer" wrote: On Thu, Jul 19, 2018 at 1:37 PM, Ramirez, Eddie wrote: > We will continue sending incoming changes to two different repos for some > time: stx-gui and the stx-horizon. I will review them and make necessary > adjustments to make them work on stx-gui as several LoCs and files are being > moved around. I don't see any activity in either repo, where is this being done? I think it will be better to roll it out in reviewable chunks rather than drop the whole thing at once, is this possible? dt -- Dean Troyer dtroyer at gmail.com From scott.little at windriver.com Fri Jul 20 13:47:48 2018 From: scott.little at windriver.com (Scott Little) Date: Fri, 20 Jul 2018 09:47:48 -0400 Subject: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? In-Reply-To: <07D8CE54-5C3A-4158-AEC9-C4EE8C7F67A7@intel.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F9E3@ALA-MBD.corp.ad.wrs.com> <07D8CE54-5C3A-4158-AEC9-C4EE8C7F67A7@intel.com> Message-ID: erlang*18.3.4.4*rpm are the ones to use.  The R16B version should have been excluded. Yes, our mirror was of all ~30000 rpms.  In this way, when a designer adds a new package or dependency, it and it's recursive dependencies were already present and ready for use. The method that has been concocted for StarlingX requires adding packages to .lst files every time there is a change.  Further there doesn't seem to be a tool to assist in the search for missing dependencies.  The result is likely to be several iterations of ...    add package, compile, fail due to missing dependency,    add package, compile, fail due to missing dependency ... very time consuming and frustrating. Scott On 18-07-19 09:00 PM, Hu, Yong wrote: > > Hi Scott, > > I noticed in the black_list, there are a couple of RPMs (such as > erlang*-R16B*.rpm”), which were in tis-r4-CentOS mirror but were NOT > used since tis-r5-CentOS. > > As well, we are certain they are not needed for building R5 or current > StarlingX codebase. > > Could we just drop them? > > BTW: in tis-r5-CentOS mirror, there are over 30,000 RPMs, while > actually among those only ~1900 RPMs are necessary. > > regards, > > Yong > > *From: *Scott Little > *Date: *Wednesday, 18 July 2018 at 11:17 PM > *To: *"starlingx-discuss at lists.starlingx.io" > > *Subject: *Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 > binary repos instead of 7.4? > > StarlingX should be based on Centos 7.4 for the vast majority of > packages.  I think there are a dozen that have made the move to 7.5.  > There are also a few that we blacklisted and are pulling from earlier > releases. > > I'll attach my black_list notes as they exist today.  I'll have to > audit them to make sure my notes are up to date. > > Scott > > > > > On 18-07-18 10:47 AM, Penney, Don wrote: > > Hi all, > > The StarlingX.repo file in stx-tools has all the CentOS 7.4.1708 > binary repos disabled and is instead using 7.3.1611. This would > likely explain why some of the specified RPMs cannot be downloaded > via yum, as they were upversioned in 7.4. > > Was this done for a particular reason, or is it a configuration error? > > *Don Penney*, Developer, *Wind River* > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Jul 20 15:59:15 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 20 Jul 2018 15:59:15 +0000 Subject: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F9E3@ALA-MBD.corp.ad.wrs.com> <07D8CE54-5C3A-4158-AEC9-C4EE8C7F67A7@intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB564B89@fmsmsx117.amr.corp.intel.com> Managing the rpm dependency tree in an automated way is one of the key things I’m hoping we can learn from (leverage) from the Clear Linux project. They seem to have solved this problem. Several ex-Clear team members are on our team now and thinking about this… brucej From: Scott Little [mailto:scott.little at windriver.com] Sent: Friday, July 20, 2018 6:48 AM To: Hu, Yong ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? erlang*18.3.4.4*rpm are the ones to use. The R16B version should have been excluded. Yes, our mirror was of all ~30000 rpms. In this way, when a designer adds a new package or dependency, it and it's recursive dependencies were already present and ready for use. The method that has been concocted for StarlingX requires adding packages to .lst files every time there is a change. Further there doesn't seem to be a tool to assist in the search for missing dependencies. The result is likely to be several iterations of ... add package, compile, fail due to missing dependency, add package, compile, fail due to missing dependency ... very time consuming and frustrating. Scott On 18-07-19 09:00 PM, Hu, Yong wrote: Hi Scott, I noticed in the black_list, there are a couple of RPMs (such as erlang*-R16B*.rpm”), which were in tis-r4-CentOS mirror but were NOT used since tis-r5-CentOS. As well, we are certain they are not needed for building R5 or current StarlingX codebase. Could we just drop them? BTW: in tis-r5-CentOS mirror, there are over 30,000 RPMs, while actually among those only ~1900 RPMs are necessary. regards, Yong From: Scott Little Date: Wednesday, 18 July 2018 at 11:17 PM To: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? StarlingX should be based on Centos 7.4 for the vast majority of packages. I think there are a dozen that have made the move to 7.5. There are also a few that we blacklisted and are pulling from earlier releases. I'll attach my black_list notes as they exist today. I'll have to audit them to make sure my notes are up to date. Scott On 18-07-18 10:47 AM, Penney, Don wrote: Hi all, The StarlingX.repo file in stx-tools has all the CentOS 7.4.1708 binary repos disabled and is instead using 7.3.1611. This would likely explain why some of the specified RPMs cannot be downloaded via yum, as they were upversioned in 7.4. Was this done for a particular reason, or is it a configuration error? Don Penney, Developer, Wind River _______________________________________________ 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 dtroyer at gmail.com Fri Jul 20 16:05:47 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Fri, 20 Jul 2018 11:05:47 -0500 Subject: [Starlingx-discuss] Milestone 2018.07.0 is available. Message-ID: In our first steps toward creating a release process I created a branch last night named 'm/2018.07' that forms the basis for our first monthly milestone. See the new wiki page[0] for a WIP overview of the process. As a reminder, the milestones are created in order to provide a stable source for extended testing and a way to fix issues specifically for that build (backported from master). [Between the time I started this email and actually sent it we had our first backport!] I submitted a review[2] that contains an updated default.xml manifest that will pull the branch rather than master, you can try it with: repo init -u https://git.starlingx.io/stx-manifest.git -b refs/changes/48/584348/1 -m default.xml It pulls the right branches, however there are a couple of things I am still investigating: * the remote branchess are all prefixed with 'm/', so the remote branch for the milestone is shown in a git branch -r as 'm/m/2018.07' * the repos from Gerrit are detatched HEAD although it is at the right sha I am certain these are due to my still becoming familiar with the intricacies of the repo tool and configuring the manifest properly. Manual git clones from the upstream repos show the branch names as expected. dt [0] https://wiki.openstack.org/wiki/StarlingX/Release_Process [1] https://review.openstack.org/#/c/584430/ [2] https://review.openstack.org/#/c/584348/ -- Dean Troyer dtroyer at gmail.com From Brent.Rowsell at windriver.com Fri Jul 20 18:34:31 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Fri, 20 Jul 2018 18:34:31 +0000 Subject: [Starlingx-discuss] build-pkgs: package built failed , mock package missing In-Reply-To: <93814834B4855241994F290E959305C752F49726@SHSMSX104.ccr.corp.intel.com> References: <60b836e9-3388-7bbc-f63c-9e6db7ec6e4a@windriver.com> <1F2AA110-5A73-43E2-A2AE-AB254608232A@intel.com> <71FBB182-3630-40E2-8A60-88137137823E@intel.com> <109C9245-D45B-4869-940B-89EC2B78FE62@intel.com> <93814834B4855241994F290E959305C752F41ED4@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48664@SHSMSX104.ccr.corp.intel.com> <9d889c66-a603-2d12-dd70-c8fb3b3911d0@windriver.com> <93814834B4855241994F290E959305C752F48CC6@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F48FA8@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F49046@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F49726@SHSMSX104.ccr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0DD0A6@ALA-MBD.corp.ad.wrs.com> Hi, Has a fix been pushed to the repo for this ? Thanks, Brent -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, July 12, 2018 10:35 PM To: Arce Moreno, Abraham ; Qi, Mingyuan ; Little, Scott ; Hu, Yong ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Hi Araham, I changed modify-build-cfg according to your below solution, below issue fixed > 23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? Now, RPM build is ongoing normally, and I can see some "Success building". Thank you so much! BRs zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月13日 9:40 To: Liu, ZhipengS ; Qi, Mingyuan ; Scott Little ; Hu, Yong ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Hi ZhipengS, > After I add missing RPMS, build still failed as below. However, with > the mirror I built, the build in our old build environment is ongoing normally. Important to get your feedback on the activities asked to be executed by Scott and Yong. > 23:40:14 Start: chroot init > 23:40:14 INFO: calling preinit hooks > 23:40:14 INFO: enabled root cache > 23:40:14 INFO: enabled yum cache > 23:40:14 Start: cleaning yum metadata > 23:40:14 Finish: cleaning yum metadata > 23:40:14 INFO: enabled HW Info plugin > 23:40:14 Mock Version: 1.4.11 > 23:40:14 INFO: Mock Version: 1.4.11 > 23:40:14 Start: yum install > 23:40:14 Finish: yum install > 23:40:14 ERROR: > Exception(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/t > is- > extensions-1.0-2.tis.src.rpm) > Config(zhipengl-starlingx-tis-r5-pike-std/mock) 0 minutes 2 seconds > 23:40:14 INFO: Results and/or logs in: > /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx > -tis-r5- > pike-std/tis-extensions-1.0-2.tis > 23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? > 23:40:14 End build: You are hitting " ERROR: Could not find useradd in chroot, maybe the install failed?" Information is spread among the different messages under thread: "[Starlingx-discuss] build-pkgs: package built failed , mock package missing" http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000125.html http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000129.html http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000206.html In summary, to pass this and other dependency issue during build-pkgs is by adding - shadow-utils - rpm-build to modify-build-cfg under build-tools diff --git a/build-tools/modify-build-cfg b/build-tools/modify-build-cfg ... -grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 yum'" $FILE || \ - echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum'" >> $FILE +grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 yum shadow-utils rpm-build'" $FILE || \ + echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum shadow-utils rpm-build'" >> $FILE _______________________________________________ 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 Jul 20 19:07:06 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 20 Jul 2018 19:07:06 +0000 Subject: [Starlingx-discuss] Important! Storyboard Story Tag & Prefix Policy Message-ID: <9A85D2917C58154C960D95352B22818BAB564DDB@fmsmsx117.amr.corp.intel.com> I have made an executive decision as to how we should use the Storyboard tool. After discussing the matter with Ghada and our OpenStack Foundation team, I have documented our Tag and Prefix policy[0] on the wiki, in the section called "Story and Bug Tracking" [1]. I'm doing this because Reasons [2]. Here is a summary of the policy. All Stories in the Storyboard tool shall have Tags. If you create a new Story, make sure to add the tag "stx.new". We can then query this story and assign it to a sub-project and a release. If you don't tag it that way, we may never find it again. Assigning Stories to releases is a process that I think should be driven by the Cores together with the Release team. That is TBD. If you are filing a bug, please also add the "stx.bug" tag. I have updated all of the currently entered bugs with that tag. If you are filing a Story for a feature, please add the "stx.feature" tag. I'm going to update the existing feature stories to add that tag soon. I'd like to break down planning for the project into a set of Sub-projects. Each will have its own tag so the team working on that Sub-project can manage their work items. I'll be adding those tags soon as well. Should a team decide to add additional tags to Stories, for example so they can build a Board in Storyboard for their work, feel free, but please update the document on the wiki [0]. Note that as far as I can tell, each tag needs to be entered one at a time in the web UI. Brucej [0] https://wiki.openstack.org/wiki/StarlingX/Tags_and_Prefixes [1] https://wiki.openstack.org/wiki/StarlingX#Story_and_Bug_Tracking [2] We need to assign issues to sub-projects and releases, and keep track of bugs and features separately to simplify doing bug scrubs and release planning. Tags are easily searchable and don't clutter up the text fields. Using queries instead of Worklists or Boards gives us both flexibility and reliability. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Jul 20 23:24:11 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 20 Jul 2018 23:24:11 +0000 Subject: [Starlingx-discuss] Milestone 2018.07.0 is available. In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BAB5653D8@fmsmsx117.amr.corp.intel.com> As a second step in our release process, can someone please do a build against the branch? And send the ISO to the Test team? brucej -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Friday, July 20, 2018 9:06 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Milestone 2018.07.0 is available. In our first steps toward creating a release process I created a branch last night named 'm/2018.07' that forms the basis for our first monthly milestone. See the new wiki page[0] for a WIP overview of the process. As a reminder, the milestones are created in order to provide a stable source for extended testing and a way to fix issues specifically for that build (backported from master). [Between the time I started this email and actually sent it we had our first backport!] I submitted a review[2] that contains an updated default.xml manifest that will pull the branch rather than master, you can try it with: repo init -u https://git.starlingx.io/stx-manifest.git -b refs/changes/48/584348/1 -m default.xml It pulls the right branches, however there are a couple of things I am still investigating: * the remote branchess are all prefixed with 'm/', so the remote branch for the milestone is shown in a git branch -r as 'm/m/2018.07' * the repos from Gerrit are detatched HEAD although it is at the right sha I am certain these are due to my still becoming familiar with the intricacies of the repo tool and configuring the manifest properly. Manual git clones from the upstream repos show the branch names as expected. dt [0] https://wiki.openstack.org/wiki/StarlingX/Release_Process [1] https://review.openstack.org/#/c/584430/ [2] https://review.openstack.org/#/c/584348/ -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Mon Jul 23 00:32:46 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 23 Jul 2018 00:32:46 +0000 Subject: [Starlingx-discuss] Important! Storyboard Story Tag & Prefix Policy In-Reply-To: <9A85D2917C58154C960D95352B22818BAB564DDB@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB564DDB@fmsmsx117.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B2E229C@SHSMSX104.ccr.corp.intel.com> Bruce, Do you have a pre-build query and can be shared with the team? For example, stx.bug.not_resolved? Stx.feature.merged? Thx. - cindy From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Saturday, July 21, 2018 3:07 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Important! Storyboard Story Tag & Prefix Policy I have made an executive decision as to how we should use the Storyboard tool. After discussing the matter with Ghada and our OpenStack Foundation team, I have documented our Tag and Prefix policy[0] on the wiki, in the section called "Story and Bug Tracking" [1]. I'm doing this because Reasons [2]. Here is a summary of the policy. All Stories in the Storyboard tool shall have Tags. If you create a new Story, make sure to add the tag "stx.new". We can then query this story and assign it to a sub-project and a release. If you don't tag it that way, we may never find it again. Assigning Stories to releases is a process that I think should be driven by the Cores together with the Release team. That is TBD. If you are filing a bug, please also add the "stx.bug" tag. I have updated all of the currently entered bugs with that tag. If you are filing a Story for a feature, please add the "stx.feature" tag. I'm going to update the existing feature stories to add that tag soon. I'd like to break down planning for the project into a set of Sub-projects. Each will have its own tag so the team working on that Sub-project can manage their work items. I'll be adding those tags soon as well. Should a team decide to add additional tags to Stories, for example so they can build a Board in Storyboard for their work, feel free, but please update the document on the wiki [0]. Note that as far as I can tell, each tag needs to be entered one at a time in the web UI. Brucej [0] https://wiki.openstack.org/wiki/StarlingX/Tags_and_Prefixes [1] https://wiki.openstack.org/wiki/StarlingX#Story_and_Bug_Tracking [2] We need to assign issues to sub-projects and releases, and keep track of bugs and features separately to simplify doing bug scrubs and release planning. Tags are easily searchable and don't clutter up the text fields. Using queries instead of Worklists or Boards gives us both flexibility and reliability. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Mon Jul 23 01:06:43 2018 From: yong.hu at intel.com (Hu, Yong) Date: Mon, 23 Jul 2018 01:06:43 +0000 Subject: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? In-Reply-To: <9A85D2917C58154C960D95352B22818BAB564B89@fmsmsx117.amr.corp.intel.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F9E3@ALA-MBD.corp.ad.wrs.com> <07D8CE54-5C3A-4158-AEC9-C4EE8C7F67A7@intel.com> <9A85D2917C58154C960D95352B22818BAB564B89@fmsmsx117.amr.corp.intel.com> Message-ID: We have 2 types of dependencies to handle: 1). Build dependencies (indicated by “build requires”) and 2) deployment (installation) dependencies (indicated by “requires”). If we are aware of a new package is needed, this package name could be added into *.lst, and accordingly the package itself can be managed to download and added into the mirror. But the *indirect* dependencies brought into by this new package couldn’t be explicitly figured out until the build failures, going along with the building iterations. It would be helpful to have a script to analyze the dependency chain, BEFORE actually trying the build iterations painfully. Would love to see how Clear Linux project efficiently resolve this problem. Regards, Yong From: "Jones, Bruce E" Date: Friday, 20 July 2018 at 11:59 PM To: Scott Little , "Hu, Yong" , "starlingx-discuss at lists.starlingx.io" Subject: RE: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? Managing the rpm dependency tree in an automated way is one of the key things I’m hoping we can learn from (leverage) from the Clear Linux project. They seem to have solved this problem. Several ex-Clear team members are on our team now and thinking about this… brucej From: Scott Little [mailto:scott.little at windriver.com] Sent: Friday, July 20, 2018 6:48 AM To: Hu, Yong ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? erlang*18.3.4.4*rpm are the ones to use. The R16B version should have been excluded. Yes, our mirror was of all ~30000 rpms. In this way, when a designer adds a new package or dependency, it and it's recursive dependencies were already present and ready for use. The method that has been concocted for StarlingX requires adding packages to .lst files every time there is a change. Further there doesn't seem to be a tool to assist in the search for missing dependencies. The result is likely to be several iterations of ... add package, compile, fail due to missing dependency, add package, compile, fail due to missing dependency ... very time consuming and frustrating. Scott On 18-07-19 09:00 PM, Hu, Yong wrote: Hi Scott, I noticed in the black_list, there are a couple of RPMs (such as erlang*-R16B*.rpm”), which were in tis-r4-CentOS mirror but were NOT used since tis-r5-CentOS. As well, we are certain they are not needed for building R5 or current StarlingX codebase. Could we just drop them? BTW: in tis-r5-CentOS mirror, there are over 30,000 RPMs, while actually among those only ~1900 RPMs are necessary. regards, Yong From: Scott Little Date: Wednesday, 18 July 2018 at 11:17 PM To: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? StarlingX should be based on Centos 7.4 for the vast majority of packages. I think there are a dozen that have made the move to 7.5. There are also a few that we blacklisted and are pulling from earlier releases. I'll attach my black_list notes as they exist today. I'll have to audit them to make sure my notes are up to date. Scott On 18-07-18 10:47 AM, Penney, Don wrote: Hi all, The StarlingX.repo file in stx-tools has all the CentOS 7.4.1708 binary repos disabled and is instead using 7.3.1611. This would likely explain why some of the specified RPMs cannot be downloaded via yum, as they were upversioned in 7.4. Was this done for a particular reason, or is it a configuration error? Don Penney, Developer, Wind River _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Mon Jul 23 01:25:11 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 23 Jul 2018 01:25:11 +0000 Subject: [Starlingx-discuss] Important! Storyboard Story Tag & Prefix Policy In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B2E229C@SHSMSX104.ccr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB564DDB@fmsmsx117.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E229C@SHSMSX104.ccr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB565D66@fmsmsx117.amr.corp.intel.com> There are links on the wiki page to pre-built queries under the Story and Bug Tracking section. The links look like this: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.bug. You can change the highlighted text to query for various things. I'm still learning how to do this. Ghada send me a script that shows what you can do if you know scripting: #!/bin/bash curl https://storyboard.openstack.org/api/v1/tasks?project_group_id=86|python -mjson.tool|grep -B11 "\"assignee_id\": null" |egrep "title|\|story_id" > unassigned_tasks.txt sed 's/,//g;/^$/d' unassigned_tasks.txt | paste - - - From: Xie, Cindy Sent: Sunday, July 22, 2018 5:33 PM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Important! Storyboard Story Tag & Prefix Policy Bruce, Do you have a pre-build query and can be shared with the team? For example, stx.bug.not_resolved? Stx.feature.merged? Thx. - cindy From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Saturday, July 21, 2018 3:07 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Important! Storyboard Story Tag & Prefix Policy I have made an executive decision as to how we should use the Storyboard tool. After discussing the matter with Ghada and our OpenStack Foundation team, I have documented our Tag and Prefix policy[0] on the wiki, in the section called "Story and Bug Tracking" [1]. I'm doing this because Reasons [2]. Here is a summary of the policy. All Stories in the Storyboard tool shall have Tags. If you create a new Story, make sure to add the tag "stx.new". We can then query this story and assign it to a sub-project and a release. If you don't tag it that way, we may never find it again. Assigning Stories to releases is a process that I think should be driven by the Cores together with the Release team. That is TBD. If you are filing a bug, please also add the "stx.bug" tag. I have updated all of the currently entered bugs with that tag. If you are filing a Story for a feature, please add the "stx.feature" tag. I'm going to update the existing feature stories to add that tag soon. I'd like to break down planning for the project into a set of Sub-projects. Each will have its own tag so the team working on that Sub-project can manage their work items. I'll be adding those tags soon as well. Should a team decide to add additional tags to Stories, for example so they can build a Board in Storyboard for their work, feel free, but please update the document on the wiki [0]. Note that as far as I can tell, each tag needs to be entered one at a time in the web UI. Brucej [0] https://wiki.openstack.org/wiki/StarlingX/Tags_and_Prefixes [1] https://wiki.openstack.org/wiki/StarlingX#Story_and_Bug_Tracking [2] We need to assign issues to sub-projects and releases, and keep track of bugs and features separately to simplify doing bug scrubs and release planning. Tags are easily searchable and don't clutter up the text fields. Using queries instead of Worklists or Boards gives us both flexibility and reliability. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Mon Jul 23 03:54:47 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 23 Jul 2018 03:54:47 +0000 Subject: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F9E3@ALA-MBD.corp.ad.wrs.com> <07D8CE54-5C3A-4158-AEC9-C4EE8C7F67A7@intel.com> <9A85D2917C58154C960D95352B22818BAB564B89@fmsmsx117.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B2E24B0@SHSMSX104.ccr.corp.intel.com> So I guess Chen Yan’s scripts can solve the dependencies of 2), right? From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Monday, July 23, 2018 9:07 AM To: Jones, Bruce E ; Scott Little ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? We have 2 types of dependencies to handle: 1). Build dependencies (indicated by “build requires”) and 2) deployment (installation) dependencies (indicated by “requires”). If we are aware of a new package is needed, this package name could be added into *.lst, and accordingly the package itself can be managed to download and added into the mirror. But the *indirect* dependencies brought into by this new package couldn’t be explicitly figured out until the build failures, going along with the building iterations. It would be helpful to have a script to analyze the dependency chain, BEFORE actually trying the build iterations painfully. Would love to see how Clear Linux project efficiently resolve this problem. Regards, Yong From: "Jones, Bruce E" > Date: Friday, 20 July 2018 at 11:59 PM To: Scott Little >, "Hu, Yong" >, "starlingx-discuss at lists.starlingx.io" > Subject: RE: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? Managing the rpm dependency tree in an automated way is one of the key things I’m hoping we can learn from (leverage) from the Clear Linux project. They seem to have solved this problem. Several ex-Clear team members are on our team now and thinking about this… brucej From: Scott Little [mailto:scott.little at windriver.com] Sent: Friday, July 20, 2018 6:48 AM To: Hu, Yong >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? erlang*18.3.4.4*rpm are the ones to use. The R16B version should have been excluded. Yes, our mirror was of all ~30000 rpms. In this way, when a designer adds a new package or dependency, it and it's recursive dependencies were already present and ready for use. The method that has been concocted for StarlingX requires adding packages to .lst files every time there is a change. Further there doesn't seem to be a tool to assist in the search for missing dependencies. The result is likely to be several iterations of ... add package, compile, fail due to missing dependency, add package, compile, fail due to missing dependency ... very time consuming and frustrating. Scott On 18-07-19 09:00 PM, Hu, Yong wrote: Hi Scott, I noticed in the black_list, there are a couple of RPMs (such as erlang*-R16B*.rpm”), which were in tis-r4-CentOS mirror but were NOT used since tis-r5-CentOS. As well, we are certain they are not needed for building R5 or current StarlingX codebase. Could we just drop them? BTW: in tis-r5-CentOS mirror, there are over 30,000 RPMs, while actually among those only ~1900 RPMs are necessary. regards, Yong From: Scott Little Date: Wednesday, 18 July 2018 at 11:17 PM To: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? StarlingX should be based on Centos 7.4 for the vast majority of packages. I think there are a dozen that have made the move to 7.5. There are also a few that we blacklisted and are pulling from earlier releases. I'll attach my black_list notes as they exist today. I'll have to audit them to make sure my notes are up to date. Scott On 18-07-18 10:47 AM, Penney, Don wrote: Hi all, The StarlingX.repo file in stx-tools has all the CentOS 7.4.1708 binary repos disabled and is instead using 7.3.1611. This would likely explain why some of the specified RPMs cannot be downloaded via yum, as they were upversioned in 7.4. Was this done for a particular reason, or is it a configuration error? Don Penney, Developer, Wind River _______________________________________________ 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 yan.chen at intel.com Mon Jul 23 05:53:56 2018 From: yan.chen at intel.com (Chen, Yan) Date: Mon, 23 Jul 2018 05:53:56 +0000 Subject: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B2E24B0@SHSMSX104.ccr.corp.intel.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F9E3@ALA-MBD.corp.ad.wrs.com> <07D8CE54-5C3A-4158-AEC9-C4EE8C7F67A7@intel.com> <9A85D2917C58154C960D95352B22818BAB564B89@fmsmsx117.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E24B0@SHSMSX104.ccr.corp.intel.com> Message-ID: <72AD03D27224C74982BE13246D75B39739925E12@SHSMSX103.ccr.corp.intel.com> I guess so, currently we already get some information from the rpms. We will review the data first and I will improve the tool to get more. Yan From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Monday, July 23, 2018 11:55 To: Hu, Yong ; Jones, Bruce E ; Scott Little ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? So I guess Chen Yan’s scripts can solve the dependencies of 2), right? From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Monday, July 23, 2018 9:07 AM To: Jones, Bruce E >; Scott Little >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? We have 2 types of dependencies to handle: 1). Build dependencies (indicated by “build requires”) and 2) deployment (installation) dependencies (indicated by “requires”). If we are aware of a new package is needed, this package name could be added into *.lst, and accordingly the package itself can be managed to download and added into the mirror. But the *indirect* dependencies brought into by this new package couldn’t be explicitly figured out until the build failures, going along with the building iterations. It would be helpful to have a script to analyze the dependency chain, BEFORE actually trying the build iterations painfully. Would love to see how Clear Linux project efficiently resolve this problem. Regards, Yong From: "Jones, Bruce E" > Date: Friday, 20 July 2018 at 11:59 PM To: Scott Little >, "Hu, Yong" >, "starlingx-discuss at lists.starlingx.io" > Subject: RE: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? Managing the rpm dependency tree in an automated way is one of the key things I’m hoping we can learn from (leverage) from the Clear Linux project. They seem to have solved this problem. Several ex-Clear team members are on our team now and thinking about this… brucej From: Scott Little [mailto:scott.little at windriver.com] Sent: Friday, July 20, 2018 6:48 AM To: Hu, Yong >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? erlang*18.3.4.4*rpm are the ones to use. The R16B version should have been excluded. Yes, our mirror was of all ~30000 rpms. In this way, when a designer adds a new package or dependency, it and it's recursive dependencies were already present and ready for use. The method that has been concocted for StarlingX requires adding packages to .lst files every time there is a change. Further there doesn't seem to be a tool to assist in the search for missing dependencies. The result is likely to be several iterations of ... add package, compile, fail due to missing dependency, add package, compile, fail due to missing dependency ... very time consuming and frustrating. Scott On 18-07-19 09:00 PM, Hu, Yong wrote: Hi Scott, I noticed in the black_list, there are a couple of RPMs (such as erlang*-R16B*.rpm”), which were in tis-r4-CentOS mirror but were NOT used since tis-r5-CentOS. As well, we are certain they are not needed for building R5 or current StarlingX codebase. Could we just drop them? BTW: in tis-r5-CentOS mirror, there are over 30,000 RPMs, while actually among those only ~1900 RPMs are necessary. regards, Yong From: Scott Little Date: Wednesday, 18 July 2018 at 11:17 PM To: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? StarlingX should be based on Centos 7.4 for the vast majority of packages. I think there are a dozen that have made the move to 7.5. There are also a few that we blacklisted and are pulling from earlier releases. I'll attach my black_list notes as they exist today. I'll have to audit them to make sure my notes are up to date. Scott On 18-07-18 10:47 AM, Penney, Don wrote: Hi all, The StarlingX.repo file in stx-tools has all the CentOS 7.4.1708 binary repos disabled and is instead using 7.3.1611. This would likely explain why some of the specified RPMs cannot be downloaded via yum, as they were upversioned in 7.4. Was this done for a particular reason, or is it a configuration error? Don Penney, Developer, Wind River _______________________________________________ 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 yong.hu at intel.com Mon Jul 23 07:07:41 2018 From: yong.hu at intel.com (Hu, Yong) Date: Mon, 23 Jul 2018 07:07:41 +0000 Subject: [Starlingx-discuss] upgrade RPM for Linux Firmware Security Update Message-ID: <4B9F6095-5DEE-4303-B059-5C9FE50F12CB@intel.com> In order to catch up this Linux Firmware Security Update: CESA-2018:0014 https://lists.centos.org/pipermail/centos-announce/2018-January/022698.html I'd like to upgrade RPM from the current version in mirror to the available version in CentOS 7.5 distro: linux-firmware-20170606-56.gitc990aae.el7.noarch.rpm ==> linux-firmware-20180220-62.2.git6d51311.el7_5.noarch.rpm Any concerns or feedback? Regards, Yong From zhipengs.liu at intel.com Mon Jul 23 08:38:55 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Mon, 23 Jul 2018 08:38:55 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Message-ID: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> Hi all, After did below 2 modifications, the issue mentioned in https://storyboard.openstack.org/#!/story/2003036 should be fixed tentatively since we have not enabled docker/kubernetes related features ==================================================================== Remove below 3 lines in stx-config/puppet-manifests/src/manifests/controller.pp #include ::platform::docker #include ::platform::kubernetes::master #include ::platform::collectd Remove below 2 lines in stx-config/puppet-manifests/src/manifests/compute.pp #include ::platform::collectd #include ::platform::kubernetes::worker ==================================================================== To avoid this deployment issue, may I submit a patch for above change? Welcome to add your comment if you have any concern or good suggestion. Thanks! Zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月18日 11:23 To: Liu, ZhipengS ; Hu, Yong ; 'Scott Little' ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Mingyuan asked me checked comps.xml yesterday, it didn't exist. > > I also could not create it through executing generate-cgcs-centos-repo.sh. > > Thanks Zhipeng, Mingyuan, > > Understood about the problem. Yong and Erich were talking a few days > ago internally about the way to handle comps.xml and they suggested a > minimal xml so time to bring this conversation out. > > How about this first version [0]? If it is possible for you to test > and see if we can start taking this as our base file. > > [0] https://pastebin.com/KMB8QLNX Review submitted: "Add minimal comps.xml file into cgcs-centos generator" https://review.openstack.org/#/c/583445 From cindy.xie at intel.com Mon Jul 23 12:37:46 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 23 Jul 2018 12:37:46 +0000 Subject: [Starlingx-discuss] upgrade RPM for Linux Firmware Security Update In-Reply-To: <4B9F6095-5DEE-4303-B059-5C9FE50F12CB@intel.com> References: <4B9F6095-5DEE-4303-B059-5C9FE50F12CB@intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B2E2961@SHSMSX104.ccr.corp.intel.com> Yong, can you submit a story for this CVE? Thx. - cindy -----Original Message----- From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Monday, July 23, 2018 3:08 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] upgrade RPM for Linux Firmware Security Update In order to catch up this Linux Firmware Security Update: CESA-2018:0014 https://lists.centos.org/pipermail/centos-announce/2018-January/022698.html I'd like to upgrade RPM from the current version in mirror to the available version in CentOS 7.5 distro: linux-firmware-20170606-56.gitc990aae.el7.noarch.rpm ==> linux-firmware-20180220-62.2.git6d51311.el7_5.noarch.rpm Any concerns or feedback? Regards, Yong _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Frank.Miller at windriver.com Mon Jul 23 13:41:48 2018 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 23 Jul 2018 13:41:48 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> Message-ID: Zhipeng: Please hold off on your proposed modifications. We do not see config_controller failures in our builds and testing and the code below is required for current storyboards that are in progress. We are investigating and will get back to you soon. Frank -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Monday, July 23, 2018 4:39 AM To: Arce Moreno, Abraham; Hu, Yong; Little, Scott; Qi, Mingyuan; 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Hi all, After did below 2 modifications, the issue mentioned in https://storyboard.openstack.org/#!/story/2003036 should be fixed tentatively since we have not enabled docker/kubernetes related features ==================================================================== Remove below 3 lines in stx-config/puppet-manifests/src/manifests/controller.pp #include ::platform::docker #include ::platform::kubernetes::master #include ::platform::collectd Remove below 2 lines in stx-config/puppet-manifests/src/manifests/compute.pp #include ::platform::collectd #include ::platform::kubernetes::worker ==================================================================== To avoid this deployment issue, may I submit a patch for above change? Welcome to add your comment if you have any concern or good suggestion. Thanks! Zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月18日 11:23 To: Liu, ZhipengS ; Hu, Yong ; 'Scott Little' ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Mingyuan asked me checked comps.xml yesterday, it didn't exist. > > I also could not create it through executing generate-cgcs-centos-repo.sh. > > Thanks Zhipeng, Mingyuan, > > Understood about the problem. Yong and Erich were talking a few days > ago internally about the way to handle comps.xml and they suggested a > minimal xml so time to bring this conversation out. > > How about this first version [0]? If it is possible for you to test > and see if we can start taking this as our base file. > > [0] https://pastebin.com/KMB8QLNX Review submitted: "Add minimal comps.xml file into cgcs-centos generator" https://review.openstack.org/#/c/583445 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Mon Jul 23 13:49:56 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 23 Jul 2018 13:49:56 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> Frank, This is due to Zhipeng was following wiki guide here: https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Build_StarlingX_ISO And please notice that the generated ISO missed the below packages: #selinux-policy ... #dockers-ce #kubernetes #kubernetes-client #kubernetes-kubeadm #kubernetes-master #kubernetes-node But Abraham commented out due to the missing dependencies of those RPMs. If WR can provide the dependencies that we shall add into our mirror (yours are superset of ours), then I am thinking it can help to solve the issue correctly. Thanks. - cindy -----Original Message----- From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Monday, July 23, 2018 9:42 PM To: Liu, ZhipengS ; Arce Moreno, Abraham ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Zhipeng: Please hold off on your proposed modifications. We do not see config_controller failures in our builds and testing and the code below is required for current storyboards that are in progress. We are investigating and will get back to you soon. Frank -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Monday, July 23, 2018 4:39 AM To: Arce Moreno, Abraham; Hu, Yong; Little, Scott; Qi, Mingyuan; 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Hi all, After did below 2 modifications, the issue mentioned in https://storyboard.openstack.org/#!/story/2003036 should be fixed tentatively since we have not enabled docker/kubernetes related features ==================================================================== Remove below 3 lines in stx-config/puppet-manifests/src/manifests/controller.pp #include ::platform::docker #include ::platform::kubernetes::master #include ::platform::collectd Remove below 2 lines in stx-config/puppet-manifests/src/manifests/compute.pp #include ::platform::collectd #include ::platform::kubernetes::worker ==================================================================== To avoid this deployment issue, may I submit a patch for above change? Welcome to add your comment if you have any concern or good suggestion. Thanks! Zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月18日 11:23 To: Liu, ZhipengS ; Hu, Yong ; 'Scott Little' ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Mingyuan asked me checked comps.xml yesterday, it didn't exist. > > I also could not create it through executing generate-cgcs-centos-repo.sh. > > Thanks Zhipeng, Mingyuan, > > Understood about the problem. Yong and Erich were talking a few days > ago internally about the way to handle comps.xml and they suggested a > minimal xml so time to bring this conversation out. > > How about this first version [0]? If it is possible for you to test > and see if we can start taking this as our base file. > > [0] https://pastebin.com/KMB8QLNX Review submitted: "Add minimal comps.xml file into cgcs-centos generator" https://review.openstack.org/#/c/583445 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Frank.Miller at windriver.com Mon Jul 23 14:01:26 2018 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 23 Jul 2018 14:01:26 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> Message-ID: Cindy: I think the first issue is the storyboard is using an old ISO from July 3rd (stx-07-03-2018.iso) and the commits to add the influxdb and kubernetes packages were merged after July 3rd: Influxdb: https://review.openstack.org/#/c/580021/ (Jul 4) Docker: https://review.openstack.org/#/c/581076/ (Jul 12) Kubernetes: https://review.openstack.org/#/c/581108/ (July 9) So my suggestion is you try a more recent pull & build and see if the issue is solved. Frank -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Monday, July 23, 2018 9:50 AM To: Miller, Frank; Liu, ZhipengS; Arce Moreno, Abraham; Hu, Yong; Little, Scott; Qi, Mingyuan; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Frank, This is due to Zhipeng was following wiki guide here: https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Build_StarlingX_ISO And please notice that the generated ISO missed the below packages: #selinux-policy ... #dockers-ce #kubernetes #kubernetes-client #kubernetes-kubeadm #kubernetes-master #kubernetes-node But Abraham commented out due to the missing dependencies of those RPMs. If WR can provide the dependencies that we shall add into our mirror (yours are superset of ours), then I am thinking it can help to solve the issue correctly. Thanks. - cindy -----Original Message----- From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Monday, July 23, 2018 9:42 PM To: Liu, ZhipengS ; Arce Moreno, Abraham ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Zhipeng: Please hold off on your proposed modifications. We do not see config_controller failures in our builds and testing and the code below is required for current storyboards that are in progress. We are investigating and will get back to you soon. Frank -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Monday, July 23, 2018 4:39 AM To: Arce Moreno, Abraham; Hu, Yong; Little, Scott; Qi, Mingyuan; 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Hi all, After did below 2 modifications, the issue mentioned in https://storyboard.openstack.org/#!/story/2003036 should be fixed tentatively since we have not enabled docker/kubernetes related features ==================================================================== Remove below 3 lines in stx-config/puppet-manifests/src/manifests/controller.pp #include ::platform::docker #include ::platform::kubernetes::master #include ::platform::collectd Remove below 2 lines in stx-config/puppet-manifests/src/manifests/compute.pp #include ::platform::collectd #include ::platform::kubernetes::worker ==================================================================== To avoid this deployment issue, may I submit a patch for above change? Welcome to add your comment if you have any concern or good suggestion. Thanks! Zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月18日 11:23 To: Liu, ZhipengS ; Hu, Yong ; 'Scott Little' ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Mingyuan asked me checked comps.xml yesterday, it didn't exist. > > I also could not create it through executing generate-cgcs-centos-repo.sh. > > Thanks Zhipeng, Mingyuan, > > Understood about the problem. Yong and Erich were talking a few days > ago internally about the way to handle comps.xml and they suggested a > minimal xml so time to bring this conversation out. > > How about this first version [0]? If it is possible for you to test > and see if we can start taking this as our base file. > > [0] https://pastebin.com/KMB8QLNX Review submitted: "Add minimal comps.xml file into cgcs-centos generator" https://review.openstack.org/#/c/583445 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Don.Penney at windriver.com Mon Jul 23 14:05:23 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 23 Jul 2018 14:05:23 +0000 Subject: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? In-Reply-To: <72AD03D27224C74982BE13246D75B39739925E12@SHSMSX103.ccr.corp.intel.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F9E3@ALA-MBD.corp.ad.wrs.com> <07D8CE54-5C3A-4158-AEC9-C4EE8C7F67A7@intel.com> <9A85D2917C58154C960D95352B22818BAB564B89@fmsmsx117.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E24B0@SHSMSX104.ccr.corp.intel.com> <72AD03D27224C74982BE13246D75B39739925E12@SHSMSX103.ccr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA250012@ALA-MBD.corp.ad.wrs.com> The script I sent in another thread (Adding packages to build .lst files) uses repoquery to recursively determine dependencies of packages, with commands like: repoquery --quiet -c $REPOCFG --resolve --requires --recursive From: Chen, Yan [mailto:yan.chen at intel.com] Sent: Monday, July 23, 2018 1:54 AM To: Xie, Cindy; Hu, Yong; Jones, Bruce E; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? I guess so, currently we already get some information from the rpms. We will review the data first and I will improve the tool to get more. Yan From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Monday, July 23, 2018 11:55 To: Hu, Yong ; Jones, Bruce E ; Scott Little ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? So I guess Chen Yan’s scripts can solve the dependencies of 2), right? From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Monday, July 23, 2018 9:07 AM To: Jones, Bruce E >; Scott Little >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? We have 2 types of dependencies to handle: 1). Build dependencies (indicated by “build requires”) and 2) deployment (installation) dependencies (indicated by “requires”). If we are aware of a new package is needed, this package name could be added into *.lst, and accordingly the package itself can be managed to download and added into the mirror. But the *indirect* dependencies brought into by this new package couldn’t be explicitly figured out until the build failures, going along with the building iterations. It would be helpful to have a script to analyze the dependency chain, BEFORE actually trying the build iterations painfully. Would love to see how Clear Linux project efficiently resolve this problem. Regards, Yong From: "Jones, Bruce E" > Date: Friday, 20 July 2018 at 11:59 PM To: Scott Little >, "Hu, Yong" >, "starlingx-discuss at lists.starlingx.io" > Subject: RE: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? Managing the rpm dependency tree in an automated way is one of the key things I’m hoping we can learn from (leverage) from the Clear Linux project. They seem to have solved this problem. Several ex-Clear team members are on our team now and thinking about this… brucej From: Scott Little [mailto:scott.little at windriver.com] Sent: Friday, July 20, 2018 6:48 AM To: Hu, Yong >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? erlang*18.3.4.4*rpm are the ones to use. The R16B version should have been excluded. Yes, our mirror was of all ~30000 rpms. In this way, when a designer adds a new package or dependency, it and it's recursive dependencies were already present and ready for use. The method that has been concocted for StarlingX requires adding packages to .lst files every time there is a change. Further there doesn't seem to be a tool to assist in the search for missing dependencies. The result is likely to be several iterations of ... add package, compile, fail due to missing dependency, add package, compile, fail due to missing dependency ... very time consuming and frustrating. Scott On 18-07-19 09:00 PM, Hu, Yong wrote: Hi Scott, I noticed in the black_list, there are a couple of RPMs (such as erlang*-R16B*.rpm”), which were in tis-r4-CentOS mirror but were NOT used since tis-r5-CentOS. As well, we are certain they are not needed for building R5 or current StarlingX codebase. Could we just drop them? BTW: in tis-r5-CentOS mirror, there are over 30,000 RPMs, while actually among those only ~1900 RPMs are necessary. regards, Yong From: Scott Little Date: Wednesday, 18 July 2018 at 11:17 PM To: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? StarlingX should be based on Centos 7.4 for the vast majority of packages. I think there are a dozen that have made the move to 7.5. There are also a few that we blacklisted and are pulling from earlier releases. I'll attach my black_list notes as they exist today. I'll have to audit them to make sure my notes are up to date. Scott On 18-07-18 10:47 AM, Penney, Don wrote: Hi all, The StarlingX.repo file in stx-tools has all the CentOS 7.4.1708 binary repos disabled and is instead using 7.3.1611. This would likely explain why some of the specified RPMs cannot be downloaded via yum, as they were upversioned in 7.4. Was this done for a particular reason, or is it a configuration error? Don Penney, Developer, Wind River _______________________________________________ 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 Jul 23 14:17:09 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 23 Jul 2018 14:17:09 +0000 Subject: [Starlingx-discuss] Important! Storyboard Story Tag & Prefix Policy In-Reply-To: <9A85D2917C58154C960D95352B22818BAB565D66@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB564DDB@fmsmsx117.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E229C@SHSMSX104.ccr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB565D66@fmsmsx117.amr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA31B027@ALA-MBD.corp.ad.wrs.com> FYI, the StoryBoard API documentation is available at: https://docs.openstack.org/infra/storyboard/webapi/v1.html# From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Sunday, July 22, 2018 9:25 PM To: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Important! Storyboard Story Tag & Prefix Policy There are links on the wiki page to pre-built queries under the Story and Bug Tracking section. The links look like this: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.bug. You can change the highlighted text to query for various things. I'm still learning how to do this. Ghada send me a script that shows what you can do if you know scripting: #!/bin/bash curl https://storyboard.openstack.org/api/v1/tasks?project_group_id=86|python -mjson.tool|grep -B11 "\"assignee_id\": null" |egrep "title|\|story_id" > unassigned_tasks.txt sed 's/,//g;/^$/d' unassigned_tasks.txt | paste - - - From: Xie, Cindy Sent: Sunday, July 22, 2018 5:33 PM To: Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Important! Storyboard Story Tag & Prefix Policy Bruce, Do you have a pre-build query and can be shared with the team? For example, stx.bug.not_resolved? Stx.feature.merged? Thx. - cindy From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Saturday, July 21, 2018 3:07 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Important! Storyboard Story Tag & Prefix Policy I have made an executive decision as to how we should use the Storyboard tool. After discussing the matter with Ghada and our OpenStack Foundation team, I have documented our Tag and Prefix policy[0] on the wiki, in the section called "Story and Bug Tracking" [1]. I'm doing this because Reasons [2]. Here is a summary of the policy. All Stories in the Storyboard tool shall have Tags. If you create a new Story, make sure to add the tag "stx.new". We can then query this story and assign it to a sub-project and a release. If you don't tag it that way, we may never find it again. Assigning Stories to releases is a process that I think should be driven by the Cores together with the Release team. That is TBD. If you are filing a bug, please also add the "stx.bug" tag. I have updated all of the currently entered bugs with that tag. If you are filing a Story for a feature, please add the "stx.feature" tag. I'm going to update the existing feature stories to add that tag soon. I'd like to break down planning for the project into a set of Sub-projects. Each will have its own tag so the team working on that Sub-project can manage their work items. I'll be adding those tags soon as well. Should a team decide to add additional tags to Stories, for example so they can build a Board in Storyboard for their work, feel free, but please update the document on the wiki [0]. Note that as far as I can tell, each tag needs to be entered one at a time in the web UI. Brucej [0] https://wiki.openstack.org/wiki/StarlingX/Tags_and_Prefixes [1] https://wiki.openstack.org/wiki/StarlingX#Story_and_Bug_Tracking [2] We need to assign issues to sub-projects and releases, and keep track of bugs and features separately to simplify doing bug scrubs and release planning. Tags are easily searchable and don't clutter up the text fields. Using queries instead of Worklists or Boards gives us both flexibility and reliability. -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Mon Jul 23 14:46:39 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Mon, 23 Jul 2018 14:46:39 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C752F50B3A@SHSMSX104.ccr.corp.intel.com> Hi Frank, My iso file was built with the code synced in 7/19. I have double checked that the code has already included all these 3 patches.(influxdb and docker RPM are already there) As I know, Abraham also used latest code after 7/17. Right? @Abraham. When built iso, it had some dependency issues, then commented out below lines in build_iso/image.inc #selinux-policy ... #dockers-ce #kubernetes #kubernetes-client #kubernetes-kubeadm #kubernetes-master #kubernetes-node Thanks! Zhipeng -----Original Message----- From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: 2018年7月23日 22:01 To: Xie, Cindy ; Liu, ZhipengS ; Arce Moreno, Abraham ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Cindy: I think the first issue is the storyboard is using an old ISO from July 3rd (stx-07-03-2018.iso) and the commits to add the influxdb and kubernetes packages were merged after July 3rd: Influxdb: https://review.openstack.org/#/c/580021/ (Jul 4) Docker: https://review.openstack.org/#/c/581076/ (Jul 12) Kubernetes: https://review.openstack.org/#/c/581108/ (July 9) So my suggestion is you try a more recent pull & build and see if the issue is solved. Frank -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Monday, July 23, 2018 9:50 AM To: Miller, Frank; Liu, ZhipengS; Arce Moreno, Abraham; Hu, Yong; Little, Scott; Qi, Mingyuan; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Frank, This is due to Zhipeng was following wiki guide here: https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Build_StarlingX_ISO And please notice that the generated ISO missed the below packages: #selinux-policy ... #dockers-ce #kubernetes #kubernetes-client #kubernetes-kubeadm #kubernetes-master #kubernetes-node But Abraham commented out due to the missing dependencies of those RPMs. If WR can provide the dependencies that we shall add into our mirror (yours are superset of ours), then I am thinking it can help to solve the issue correctly. Thanks. - cindy -----Original Message----- From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Monday, July 23, 2018 9:42 PM To: Liu, ZhipengS ; Arce Moreno, Abraham ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Zhipeng: Please hold off on your proposed modifications. We do not see config_controller failures in our builds and testing and the code below is required for current storyboards that are in progress. We are investigating and will get back to you soon. Frank -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Monday, July 23, 2018 4:39 AM To: Arce Moreno, Abraham; Hu, Yong; Little, Scott; Qi, Mingyuan; 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Hi all, After did below 2 modifications, the issue mentioned in https://storyboard.openstack.org/#!/story/2003036 should be fixed tentatively since we have not enabled docker/kubernetes related features ==================================================================== Remove below 3 lines in stx-config/puppet-manifests/src/manifests/controller.pp #include ::platform::docker #include ::platform::kubernetes::master #include ::platform::collectd Remove below 2 lines in stx-config/puppet-manifests/src/manifests/compute.pp #include ::platform::collectd #include ::platform::kubernetes::worker ==================================================================== To avoid this deployment issue, may I submit a patch for above change? Welcome to add your comment if you have any concern or good suggestion. Thanks! Zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月18日 11:23 To: Liu, ZhipengS ; Hu, Yong ; 'Scott Little' ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Mingyuan asked me checked comps.xml yesterday, it didn't exist. > > I also could not create it through executing generate-cgcs-centos-repo.sh. > > Thanks Zhipeng, Mingyuan, > > Understood about the problem. Yong and Erich were talking a few days > ago internally about the way to handle comps.xml and they suggested a > minimal xml so time to bring this conversation out. > > How about this first version [0]? If it is possible for you to test > and see if we can start taking this as our base file. > > [0] https://pastebin.com/KMB8QLNX Review submitted: "Add minimal comps.xml file into cgcs-centos generator" https://review.openstack.org/#/c/583445 _______________________________________________ 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 chris.friesen at windriver.com Mon Jul 23 14:56:13 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Mon, 23 Jul 2018 08:56:13 -0600 Subject: [Starlingx-discuss] Important! Storyboard Story Tag & Prefix Policy In-Reply-To: <9A85D2917C58154C960D95352B22818BAB564DDB@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB564DDB@fmsmsx117.amr.corp.intel.com> Message-ID: <5B55EC8D.2080409@windriver.com> On 07/20/2018 01:07 PM, Jones, Bruce E wrote: > I have made an executive decision as to how we should use the Storyboard tool. > After discussing the matter with Ghada and our OpenStack Foundation team, I have > documented our Tag and Prefix policy[0] on the wiki, in the section called > “Story and Bug Tracking” [1]. I’m doing this because Reasons [2]. > > Here is a summary of the policy. > > All Stories in the Storyboard tool shall have Tags. *If you create a new Story,* > *make sure to add the tag “stx.new”*. We can then query this story and assign > it to a sub-project and a release. If you don’t tag it that way, we may never > find it again. Assigning Stories to releases is a process that I think should > be driven by the Cores together with the Release team. That is TBD. Given that bugs might be opened by people that don't know our procedures, would it would maybe make more sense to have new bugs start with no such tag, and then we could add a tag indicating that it's been processed? We could create an automatic workist to track "Stories where ProjectGroup is starlingx and Tags is bug and Tags is not new" in order to monitor which new bugs need to get assigned a sub-project and release. > If you are filing a bug, please also add the “stx.bug” tag. I have updated all > of the currently entered bugs with that tag. If you are filing a Story for a > feature, please add the “stx.feature” tag. I’m going to update the existing > feature stories to add that tag soon. Why do we need "stx." prefixes for the tags? If it's to distinguish stories/tasks belonging to StarlingX I think we could skip the prefix and add a "ProjectGroup is starlingx" query clause when querying stories/tasks. Chris From scott.little at windriver.com Mon Jul 23 14:57:14 2018 From: scott.little at windriver.com (Scott Little) Date: Mon, 23 Jul 2018 10:57:14 -0400 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> Message-ID: The story seems to  implicate collectd and influxdb. In addition to the changes Frank has identified, you also need ...    https://review.openstack.org/579307 I've attempted a manual audit of the .lst files.  All requirements for the new packages seem to be present. Can you confirm the new packages have been installed in your build?    1) in your build environmnet, look in $MY_WORKSPACE/export/dist/isolinux/Packages    $ ls *collectd* *influx*    collectd-5.7.1-2.el7.x86_64.rpm influxdb-0.9.5.1-1.x86_64.rpm puppet-collectd-5.1.0-2.4a3843cgit.el7.noarch.rpm    collectd-extensions-1.0-0.tis.1.x86_64.rpm influxdb-extensions-1.0-0.tis.1.x86_64.rpm python2-influxdb-4.0.0-1.el7.1.noarch.rpm    2) the runtime view on your controllor...    $ rpm -qa | grep influxdb    python2-influxdb-4.0.0-1.el7.1.noarch    influxdb-0.9.5.1-1.x86_64    $ rpm -qa | grep collectd    collectd-5.7.1-2.el7.x86_64    collectd-extensions-1.0-0.tis.1.x86_64    puppet-collectd-5.1.0-2.4a3843cgit.el7.noarch On 18-07-23 10:01 AM, Miller, Frank wrote: > Cindy: > > I think the first issue is the storyboard is using an old ISO from July 3rd (stx-07-03-2018.iso) and the commits to add the influxdb and kubernetes packages were merged after July 3rd: > > Influxdb: https://review.openstack.org/#/c/580021/ (Jul 4) > Docker: https://review.openstack.org/#/c/581076/ (Jul 12) > Kubernetes: https://review.openstack.org/#/c/581108/ (July 9) > > So my suggestion is you try a more recent pull & build and see if the issue is solved. > > Frank > > -----Original Message----- > From: Xie, Cindy [mailto:cindy.xie at intel.com] > Sent: Monday, July 23, 2018 9:50 AM > To: Miller, Frank; Liu, ZhipengS; Arce Moreno, Abraham; Hu, Yong; Little, Scott; Qi, Mingyuan; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller > > Frank, > This is due to Zhipeng was following wiki guide here: https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Build_StarlingX_ISO > > And please notice that the generated ISO missed the below packages: > > #selinux-policy > ... > #dockers-ce > #kubernetes > #kubernetes-client > #kubernetes-kubeadm > #kubernetes-master > #kubernetes-node > > But Abraham commented out due to the missing dependencies of those RPMs. If WR can provide the dependencies that we shall add into our mirror (yours are superset of ours), then I am thinking it can help to solve the issue correctly. > > Thanks. - cindy > > > -----Original Message----- > From: Miller, Frank [mailto:Frank.Miller at windriver.com] > Sent: Monday, July 23, 2018 9:42 PM > To: Liu, ZhipengS ; Arce Moreno, Abraham ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller > > Zhipeng: > > Please hold off on your proposed modifications. We do not see config_controller failures in our builds and testing and the code below is required for current storyboards that are in progress. We are investigating and will get back to you soon. > > Frank > > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: Monday, July 23, 2018 4:39 AM > To: Arce Moreno, Abraham; Hu, Yong; Little, Scott; Qi, Mingyuan; 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller > > Hi all, > > After did below 2 modifications, the issue mentioned in https://storyboard.openstack.org/#!/story/2003036 > should be fixed tentatively since we have not enabled docker/kubernetes related features > > ==================================================================== > Remove below 3 lines in stx-config/puppet-manifests/src/manifests/controller.pp > #include ::platform::docker > #include ::platform::kubernetes::master > #include ::platform::collectd > Remove below 2 lines in stx-config/puppet-manifests/src/manifests/compute.pp > #include ::platform::collectd > #include ::platform::kubernetes::worker > ==================================================================== > > To avoid this deployment issue, may I submit a patch for above change? > Welcome to add your comment if you have any concern or good suggestion. > > Thanks! > Zhipeng > > > > > -----Original Message----- > From: Arce Moreno, Abraham > Sent: 2018年7月18日 11:23 > To: Liu, ZhipengS ; Hu, Yong ; 'Scott Little' ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > >>> Mingyuan asked me checked comps.xml yesterday, it didn't exist. >>> I also could not create it through executing generate-cgcs-centos-repo.sh. >> Thanks Zhipeng, Mingyuan, >> >> Understood about the problem. Yong and Erich were talking a few days >> ago internally about the way to handle comps.xml and they suggested a >> minimal xml so time to bring this conversation out. >> >> How about this first version [0]? If it is possible for you to test >> and see if we can start taking this as our base file. >> >> [0] https://pastebin.com/KMB8QLNX > Review submitted: > > "Add minimal comps.xml file into cgcs-centos generator" > https://review.openstack.org/#/c/583445 > _______________________________________________ > 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 abraham.arce.moreno at intel.com Mon Jul 23 15:04:14 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Mon, 23 Jul 2018 15:04:14 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> Message-ID: > Frank, > This is due to Zhipeng was following wiki guide here: > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Build_StarlingX_ > ISO Correct, great to see we are following this guide which shall be the official steps to follow. > And please notice that the generated ISO missed the below packages: > > #selinux-policy > ... > #dockers-ce > #kubernetes > #kubernetes-client > #kubernetes-kubeadm > #kubernetes-master > #kubernetes-node > > But Abraham commented out due to the missing dependencies of those > RPMs. If WR can provide the dependencies that we shall add into our mirror > (yours are superset of ours), then I am thinking it can help to solve the issue > correctly. However due to changes happening everyday it gets outdated so today I will work In having one pointing to our Milestone 2018.07.0 [0] [0] http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000285.html From abraham.arce.moreno at intel.com Mon Jul 23 15:09:22 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Mon, 23 Jul 2018 15:09:22 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> Message-ID: > I think the first issue is the storyboard is using an old ISO from July 3rd (stx-07- > 03-2018.iso) and the commits to add the influxdb and kubernetes packages > were merged after July 3rd: > > Influxdb: https://review.openstack.org/#/c/580021/ (Jul 4) > Docker: https://review.openstack.org/#/c/581076/ (Jul 12) > Kubernetes: https://review.openstack.org/#/c/581108/ (July 9) > > So my suggestion is you try a more recent pull & build and see if the issue is > solved. I will build from master today and report back. Also, if there is some reason we shall not base our Getting Started Developer Guide [0] in Milestone 2018.07.0 [1] please let us know. [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000285.html From abraham.arce.moreno at intel.com Mon Jul 23 15:30:02 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Mon, 23 Jul 2018 15:30:02 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: <93814834B4855241994F290E959305C752F50B3A@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F50B3A@SHSMSX104.ccr.corp.intel.com> Message-ID: > My iso file was built with the code synced in 7/19. > I have double checked that the code has already included all these 3 > patches.(influxdb and docker RPM are already there) > > As I know, Abraham also used latest code after 7/17. Right? @Abraham. Correct! > When built iso, it had some dependency issues, then commented out below > lines in build_iso/image.inc > > #selinux-policy > ... > #dockers-ce > #kubernetes > #kubernetes-client > #kubernetes-kubeadm > #kubernetes-master > #kubernetes-node Let us try today and will get back to this mailing list. From abraham.arce.moreno at intel.com Mon Jul 23 15:39:54 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Mon, 23 Jul 2018 15:39:54 +0000 Subject: [Starlingx-discuss] Milestone 2018.07.0 is available. In-Reply-To: <9A85D2917C58154C960D95352B22818BAB5653D8@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB5653D8@fmsmsx117.amr.corp.intel.com> Message-ID: > As a second step in our release process, can someone please do a build > against the branch? And send the ISO to the Test team? @Hayde is taking care of this step, will provide the update as soon as possible. If someone has already built it please let us know so we can cross reference steps and update the Getting Started Developer Guide [0] now based on our stable branch. Does anyone see any benefit in having another Developer Guide based on master? The challenge will be to keep up to date with all changes happening, is it worth the effort? [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide From dtroyer at gmail.com Mon Jul 23 15:47:32 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Mon, 23 Jul 2018 10:47:32 -0500 Subject: [Starlingx-discuss] Milestone 2018.07.0 is available. In-Reply-To: References: <9A85D2917C58154C960D95352B22818BAB5653D8@fmsmsx117.amr.corp.intel.com> Message-ID: On Mon, Jul 23, 2018 at 10:39 AM, Arce Moreno, Abraham wrote: > Does anyone see any benefit in having another Developer Guide based on master? > The challenge will be to keep up to date with all changes happening, is it worth the effort? > > [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide I expect the divergence between master and the recent monthly milestone is not going to be huge (after the upcoming restructuring) most of the time, it may not be worth it to maintain two versions, making notes as required in the existing guide should be sufficient. dt -- Dean Troyer dtroyer at gmail.com From cesar.lara at intel.com Mon Jul 23 16:14:17 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Mon, 23 Jul 2018 16:14:17 +0000 Subject: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA250012@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F9E3@ALA-MBD.corp.ad.wrs.com> <07D8CE54-5C3A-4158-AEC9-C4EE8C7F67A7@intel.com> <9A85D2917C58154C960D95352B22818BAB564B89@fmsmsx117.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E24B0@SHSMSX104.ccr.corp.intel.com> <72AD03D27224C74982BE13246D75B39739925E12@SHSMSX103.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA250012@ALA-MBD.corp.ad.wrs.com> Message-ID: <0B566C62EC792145B40E29EFEBF1AB47104BCFDD@fmsmsx104.amr.corp.intel.com> Marcela got this script merges that is looking for dependencies on added packages , it is now merged in stx-tools https://git.openstack.org/cgit/openstack/stx-tools/commit/?id=b2a81a46128c069ab4b321f273b95f69c3d80914 Regards Cesar Lara From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Monday, July 23, 2018 9:05 AM To: Chen, Yan ; Xie, Cindy ; Hu, Yong ; Jones, Bruce E ; Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? The script I sent in another thread (Adding packages to build .lst files) uses repoquery to recursively determine dependencies of packages, with commands like: repoquery --quiet -c $REPOCFG --resolve --requires --recursive From: Chen, Yan [mailto:yan.chen at intel.com] Sent: Monday, July 23, 2018 1:54 AM To: Xie, Cindy; Hu, Yong; Jones, Bruce E; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? I guess so, currently we already get some information from the rpms. We will review the data first and I will improve the tool to get more. Yan From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Monday, July 23, 2018 11:55 To: Hu, Yong >; Jones, Bruce E >; Scott Little >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? So I guess Chen Yan’s scripts can solve the dependencies of 2), right? From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Monday, July 23, 2018 9:07 AM To: Jones, Bruce E >; Scott Little >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? We have 2 types of dependencies to handle: 1). Build dependencies (indicated by “build requires”) and 2) deployment (installation) dependencies (indicated by “requires”). If we are aware of a new package is needed, this package name could be added into *.lst, and accordingly the package itself can be managed to download and added into the mirror. But the *indirect* dependencies brought into by this new package couldn’t be explicitly figured out until the build failures, going along with the building iterations. It would be helpful to have a script to analyze the dependency chain, BEFORE actually trying the build iterations painfully. Would love to see how Clear Linux project efficiently resolve this problem. Regards, Yong From: "Jones, Bruce E" > Date: Friday, 20 July 2018 at 11:59 PM To: Scott Little >, "Hu, Yong" >, "starlingx-discuss at lists.starlingx.io" > Subject: RE: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? Managing the rpm dependency tree in an automated way is one of the key things I’m hoping we can learn from (leverage) from the Clear Linux project. They seem to have solved this problem. Several ex-Clear team members are on our team now and thinking about this… brucej From: Scott Little [mailto:scott.little at windriver.com] Sent: Friday, July 20, 2018 6:48 AM To: Hu, Yong >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? erlang*18.3.4.4*rpm are the ones to use. The R16B version should have been excluded. Yes, our mirror was of all ~30000 rpms. In this way, when a designer adds a new package or dependency, it and it's recursive dependencies were already present and ready for use. The method that has been concocted for StarlingX requires adding packages to .lst files every time there is a change. Further there doesn't seem to be a tool to assist in the search for missing dependencies. The result is likely to be several iterations of ... add package, compile, fail due to missing dependency, add package, compile, fail due to missing dependency ... very time consuming and frustrating. Scott On 18-07-19 09:00 PM, Hu, Yong wrote: Hi Scott, I noticed in the black_list, there are a couple of RPMs (such as erlang*-R16B*.rpm”), which were in tis-r4-CentOS mirror but were NOT used since tis-r5-CentOS. As well, we are certain they are not needed for building R5 or current StarlingX codebase. Could we just drop them? BTW: in tis-r5-CentOS mirror, there are over 30,000 RPMs, while actually among those only ~1900 RPMs are necessary. regards, Yong From: Scott Little Date: Wednesday, 18 July 2018 at 11:17 PM To: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? StarlingX should be based on Centos 7.4 for the vast majority of packages. I think there are a dozen that have made the move to 7.5. There are also a few that we blacklisted and are pulling from earlier releases. I'll attach my black_list notes as they exist today. I'll have to audit them to make sure my notes are up to date. Scott On 18-07-18 10:47 AM, Penney, Don wrote: Hi all, The StarlingX.repo file in stx-tools has all the CentOS 7.4.1708 binary repos disabled and is instead using 7.3.1611. This would likely explain why some of the specified RPMs cannot be downloaded via yum, as they were upversioned in 7.4. Was this done for a particular reason, or is it a configuration error? Don Penney, Developer, Wind River _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Mon Jul 23 16:31:27 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 23 Jul 2018 16:31:27 +0000 Subject: [Starlingx-discuss] Milestone 2018.07.0 is available. In-Reply-To: References: <9A85D2917C58154C960D95352B22818BAB5653D8@fmsmsx117.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB565EEF@fmsmsx117.amr.corp.intel.com> At some point we should start putting our docs into the actual stx-docs repo and published using the OpenStack documentation framework. Then they will be versioned and in sync when we branch. brucej -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Monday, July 23, 2018 8:48 AM To: Arce Moreno, Abraham Cc: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Milestone 2018.07.0 is available. On Mon, Jul 23, 2018 at 10:39 AM, Arce Moreno, Abraham wrote: > Does anyone see any benefit in having another Developer Guide based on master? > The challenge will be to keep up to date with all changes happening, is it worth the effort? > > [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide I expect the divergence between master and the recent monthly milestone is not going to be huge (after the upcoming restructuring) most of the time, it may not be worth it to maintain two versions, making notes as required in the existing guide should be sufficient. dt -- Dean Troyer dtroyer at gmail.com From bruce.e.jones at intel.com Mon Jul 23 16:39:24 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 23 Jul 2018 16:39:24 +0000 Subject: [Starlingx-discuss] Important! Storyboard Story Tag & Prefix Policy In-Reply-To: <5B55EC8D.2080409@windriver.com> References: <9A85D2917C58154C960D95352B22818BAB564DDB@fmsmsx117.amr.corp.intel.com> <5B55EC8D.2080409@windriver.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB565F18@fmsmsx117.amr.corp.intel.com> Please see inline below due to my silly top posting email client. Chris, the main answer to your questions is that I don't know much about how Storyboard works, I'm learning new things every day. I'd like to get us on a more operational footing quickly so I'm working with what I know each day. We can easily make changes to any process as we learn more about how things really work. brucej -----Original Message----- From: Chris Friesen [mailto:chris.friesen at windriver.com] Sent: Monday, July 23, 2018 7:56 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Important! Storyboard Story Tag & Prefix Policy On 07/20/2018 01:07 PM, Jones, Bruce E wrote: > I have made an executive decision as to how we should use the Storyboard tool. > After discussing the matter with Ghada and our OpenStack Foundation > team, I have documented our Tag and Prefix policy[0] on the wiki, in > the section called “Story and Bug Tracking” [1]. I’m doing this because Reasons [2]. > > Here is a summary of the policy. > > All Stories in the Storyboard tool shall have Tags. *If you create a > new Story,* *make sure to add the tag “stx.new”*. We can then query > this story and assign it to a sub-project and a release. If you don’t tag it that way, we may never > find it again. Assigning Stories to releases is a process that I think should > be driven by the Cores together with the Release team. That is TBD. Given that bugs might be opened by people that don't know our procedures, would it would maybe make more sense to have new bugs start with no such tag, and then we could add a tag indicating that it's been processed? [brucej] Yes, this would make sense. At the time I didn't know how to find Stories with no tags, or get the tags displayed in the web UI. I still don't know how to do the former, other than to run complex scripts. And have no idea how to change the web UI (other than contributing code to it). We could create an automatic workist to track "Stories where ProjectGroup is starlingx and Tags is bug and Tags is not new" in order to monitor which new bugs need to get assigned a sub-project and release. [brucej] That would also make sense, but I haven't figured out how to build a query that says "tag == NULL". > If you are filing a bug, please also add the “stx.bug” tag. I have > updated all of the currently entered bugs with that tag. If you are > filing a Story for a feature, please add the “stx.feature” tag. I’m > going to update the existing feature stories to add that tag soon. Why do we need "stx." prefixes for the tags? If it's to distinguish stories/tasks belonging to StarlingX I think we could skip the prefix and add a "ProjectGroup is starlingx" query clause when querying stories/tasks. [brucej] I don't know enough about how tags work. If it's just a random text field with no namespace, great, we can do whatever we want. But I didn't want to pollute the namespace of the other projects and didn't get an answer to my IRC query on #storyboard, so I went with a safe approach. Chris _______________________________________________ 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 Mon Jul 23 16:57:42 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 23 Jul 2018 18:57:42 +0200 Subject: [Starlingx-discuss] Denver PTG schedule Message-ID: <590BE545-7103-483F-B67B-B81200BB99FB@gmail.com> Hi, I would like to draw your attention to the recently published schedule[1] for the upcoming Denver PTG[2]. StarlingX is scheduled for Wednesday, the only overlapping is with Glance. We have a planning etherpad[3] to work on topics to discuss and we need to start planning cross-project sessions with projects such as Keystone, Glance, Airship and the Edge Computing Group. Please add your name if you’re planning to attend the PTG and the edge sessions. Please let me know if you have any questions. Thanks and Best Regards, Ildikó [1] https://www.openstack.org/ptg/#tab_schedule [2] https://www.openstack.org/ptg [3] https://etherpad.openstack.org/p/stx-PTG-agenda From chris.friesen at windriver.com Mon Jul 23 17:14:18 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Mon, 23 Jul 2018 11:14:18 -0600 Subject: [Starlingx-discuss] Important! Storyboard Story Tag & Prefix Policy In-Reply-To: <9A85D2917C58154C960D95352B22818BAB565F18@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB564DDB@fmsmsx117.amr.corp.intel.com> <5B55EC8D.2080409@windriver.com> <9A85D2917C58154C960D95352B22818BAB565F18@fmsmsx117.amr.corp.intel.com> Message-ID: <5B560CEA.9010100@windriver.com> On 07/23/2018 10:39 AM, Jones, Bruce E wrote: > -----Original Message----- From: Chris Friesen > [mailto:chris.friesen at windriver.com] >> All Stories in the Storyboard tool shall have Tags. *If you create a new >> Story,* *make sure to add the tag “stx.new”*. We can then query this story >> and assign it to a sub-project and a release. If you don’t tag it that >> way, we may never find it again. Assigning Stories to releases is a >> process that I think should be driven by the Cores together with the >> Release team. That is TBD. > > Given that bugs might be opened by people that don't know our procedures, > would it would maybe make more sense to have new bugs start with no such tag, > and then we could add a tag indicating that it's been processed? > > [brucej] Yes, this would make sense. At the time I didn't know how to find > Stories with no tags, or get the tags displayed in the web UI. I still don't > know how to do the former, other than to run complex scripts. And have no > idea how to change the web UI (other than contributing code to it). Currently the only way I know of to find stories using OR and NOT clauses is to use automatic worklists. I plan on opening a storyboard bug to add more complex queries to the search mechanism. > We could create an automatic workist to track "Stories where ProjectGroup is > starlingx and Tags is bug and Tags is not new" in order to monitor which new > bugs need to get assigned a sub-project and release. > > [brucej] That would also make sense, but I haven't figured out how to build a > query that says "tag == NULL". You can have arbitrary tags, so I don't think it makes sense to search for no tags at all. Specifically for finding stories that don't have a *specific* tag (or don't have one of a list of specific tags) you can create an automatic worklist, which then lets you do more complicated logic. It's a bit limiting in that you can only search for a series of "OR" statements, where each one is a series of AND clauses, where each clause is either matching or not matching. But like in my example you can make an automatic worklist for: "ProjectGroup is starlingx" AND "'bug' tag exists" AND "'triaged' tag doesn't exist" The above worklist is available at: https://storyboard.openstack.org/#!/worklist/420 In this scenario, we could set the "triaged" tag once the bug has been analyzed. >> If you are filing a bug, please also add the “stx.bug” tag. I have updated As an example of tags, h >> all of the currently entered bugs with that tag. If you are filing a Story >> for a feature, please add the “stx.feature” tag. I’m going to update the >> existing feature stories to add that tag soon. > > Why do we need "stx." prefixes for the tags? If it's to distinguish > stories/tasks belonging to StarlingX I think we could skip the prefix and add > a "ProjectGroup is starlingx" query clause when querying stories/tasks. > > [brucej] I don't know enough about how tags work. If it's just a random text > field with no namespace, great, we can do whatever we want. But I didn't > want to pollute the namespace of the other projects and didn't get an answer > to my IRC query on #storyboard, so I went with a safe approach. As far as I can tell each tag just an arbitrary text string. When adding a tag you start typing and the system will give a drop-down list of all previously-specified tags containing the substring that you've typed so far, and you can pick one of them or add your custom string. When searching for stories/tasks you can start typing and it will show all ProjectGroups, Projects, and Tags containing the substring you've entered so far. Then you just pick the one you want. Here's an example of a bug from the vitrage project with multiple tags: https://storyboard.openstack.org/#!/story/2003065 Chris From chris.friesen at windriver.com Mon Jul 23 18:48:01 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Mon, 23 Jul 2018 12:48:01 -0600 Subject: [Starlingx-discuss] Important! Storyboard Story Tag & Prefix Policy In-Reply-To: <5B560CEA.9010100@windriver.com> References: <9A85D2917C58154C960D95352B22818BAB564DDB@fmsmsx117.amr.corp.intel.com> <5B55EC8D.2080409@windriver.com> <9A85D2917C58154C960D95352B22818BAB565F18@fmsmsx117.amr.corp.intel.com> <5B560CEA.9010100@windriver.com> Message-ID: <5B5622E1.1070502@windriver.com> On 07/23/2018 11:14 AM, Chris Friesen wrote: > But like in my > example you can make an automatic worklist for: > > "ProjectGroup is starlingx" AND "'bug' tag exists" AND "'triaged' tag doesn't > exist" > > The above worklist is available at: > https://storyboard.openstack.org/#!/worklist/420 I've been informed that looking at someone else's public worklist doesn't let you see the query, sorry about that. Here are the steps generate the above worklist: 1) In "Create New" pulldown box at top, select "Worklist" 2) Add a title and select "automatic". 3) Under "Criteria", click in the box and type "starlingx" and click on the ProjectGroup. 4) Click the "+and" over on the right, click in the box and enter "bug" and select the tag from the provided list. 5) Click it the "+and" again, change the dropdown menu to "not matching", click in the box and enter "triaged" and select the tag from the provided list. 6) Click on "Save" to save the first line in the query. 7) Click on "Save" to save the worklist. In this example I'm envisioning someone adding the "triaged" tag once the initial vetting is done. This is just an example, similar queries could be used for other tags. Chris From erich.cordoba.malibran at intel.com Mon Jul 23 19:33:33 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Mon, 23 Jul 2018 19:33:33 +0000 Subject: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? In-Reply-To: <0B566C62EC792145B40E29EFEBF1AB47104BCFDD@fmsmsx104.amr.corp.intel.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F9E3@ALA-MBD.corp.ad.wrs.com> <07D8CE54-5C3A-4158-AEC9-C4EE8C7F67A7@intel.com> <9A85D2917C58154C960D95352B22818BAB564B89@fmsmsx117.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E24B0@SHSMSX104.ccr.corp.intel.com> <72AD03D27224C74982BE13246D75B39739925E12@SHSMSX103.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA250012@ALA-MBD.corp.ad.wrs.com>, <0B566C62EC792145B40E29EFEBF1AB47104BCFDD@fmsmsx104.amr.corp.intel.com> Message-ID: <824C370FAA1437418C1DC20641E2FC2C43DE293C@fmsmsx104.amr.corp.intel.com> This could help to start an analysis on the rpms, I created a spreadsheet detailing the package, version and from which repository is being downloaded. There's a lot that comes from centos 7.2 and that could be because that some old package from StarlingX requires these versions. Here is the spreadsheet: https://ethercalc.openstack.org/48zp05mejrly -Erich ________________________________________ From: Lara, Cesar [cesar.lara at intel.com] Sent: Monday, July 23, 2018 11:14 AM To: Penney, Don; Chen, Yan; Xie, Cindy; Hu, Yong; Jones, Bruce E; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? Marcela got this script merges that is looking for dependencies on added packages , it is now merged in stx-tools https://git.openstack.org/cgit/openstack/stx-tools/commit/?id=b2a81a46128c069ab4b321f273b95f69c3d80914 Regards Cesar Lara From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Monday, July 23, 2018 9:05 AM To: Chen, Yan ; Xie, Cindy ; Hu, Yong ; Jones, Bruce E ; Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? The script I sent in another thread (Adding packages to build .lst files) uses repoquery to recursively determine dependencies of packages, with commands like: repoquery --quiet -c $REPOCFG --resolve --requires --recursive From: Chen, Yan [mailto:yan.chen at intel.com] Sent: Monday, July 23, 2018 1:54 AM To: Xie, Cindy; Hu, Yong; Jones, Bruce E; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? I guess so, currently we already get some information from the rpms. We will review the data first and I will improve the tool to get more. Yan From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Monday, July 23, 2018 11:55 To: Hu, Yong >; Jones, Bruce E >; Scott Little >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? So I guess Chen Yan’s scripts can solve the dependencies of 2), right? From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Monday, July 23, 2018 9:07 AM To: Jones, Bruce E >; Scott Little >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? We have 2 types of dependencies to handle: 1). Build dependencies (indicated by “build requires”) and 2) deployment (installation) dependencies (indicated by “requires”). If we are aware of a new package is needed, this package name could be added into *.lst, and accordingly the package itself can be managed to download and added into the mirror. But the *indirect* dependencies brought into by this new package couldn’t be explicitly figured out until the build failures, going along with the building iterations. It would be helpful to have a script to analyze the dependency chain, BEFORE actually trying the build iterations painfully. Would love to see how Clear Linux project efficiently resolve this problem. Regards, Yong From: "Jones, Bruce E" > Date: Friday, 20 July 2018 at 11:59 PM To: Scott Little >, "Hu, Yong" >, "starlingx-discuss at lists.starlingx.io" > Subject: RE: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? Managing the rpm dependency tree in an automated way is one of the key things I’m hoping we can learn from (leverage) from the Clear Linux project. They seem to have solved this problem. Several ex-Clear team members are on our team now and thinking about this… brucej From: Scott Little [mailto:scott.little at windriver.com] Sent: Friday, July 20, 2018 6:48 AM To: Hu, Yong >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? erlang*18.3.4.4*rpm are the ones to use. The R16B version should have been excluded. Yes, our mirror was of all ~30000 rpms. In this way, when a designer adds a new package or dependency, it and it's recursive dependencies were already present and ready for use. The method that has been concocted for StarlingX requires adding packages to .lst files every time there is a change. Further there doesn't seem to be a tool to assist in the search for missing dependencies. The result is likely to be several iterations of ... add package, compile, fail due to missing dependency, add package, compile, fail due to missing dependency ... very time consuming and frustrating. Scott On 18-07-19 09:00 PM, Hu, Yong wrote: Hi Scott, I noticed in the black_list, there are a couple of RPMs (such as erlang*-R16B*.rpm”), which were in tis-r4-CentOS mirror but were NOT used since tis-r5-CentOS. As well, we are certain they are not needed for building R5 or current StarlingX codebase. Could we just drop them? BTW: in tis-r5-CentOS mirror, there are over 30,000 RPMs, while actually among those only ~1900 RPMs are necessary. regards, Yong From: Scott Little Date: Wednesday, 18 July 2018 at 11:17 PM To: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4? StarlingX should be based on Centos 7.4 for the vast majority of packages. I think there are a dozen that have made the move to 7.5. There are also a few that we blacklisted and are pulling from earlier releases. I'll attach my black_list notes as they exist today. I'll have to audit them to make sure my notes are up to date. Scott On 18-07-18 10:47 AM, Penney, Don wrote: Hi all, The StarlingX.repo file in stx-tools has all the CentOS 7.4.1708 binary repos disabled and is instead using 7.3.1611. This would likely explain why some of the specified RPMs cannot be downloaded via yum, as they were upversioned in 7.4. Was this done for a particular reason, or is it a configuration error? Don Penney, Developer, Wind River _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From guillermo.a.ponce.castaneda at intel.com Mon Jul 23 19:58:13 2018 From: guillermo.a.ponce.castaneda at intel.com (Ponce Castaneda, Guillermo A) Date: Mon, 23 Jul 2018 19:58:13 +0000 Subject: [Starlingx-discuss] Adding packages to build .lst files In-Reply-To: <2B6889A0-364E-4BC3-9190-D8227727B92F@intel.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F3A9@ALA-MBD.corp.ad.wrs.com> <939BBE33-59F9-4D2C-B813-B32CB0006634@intel.com> <2B6889A0-364E-4BC3-9190-D8227727B92F@intel.com> Message-ID: <189BD4A4-E0D0-4014-812E-5DD2EDA889ED@intel.com> Hello team, I am giving it another try to introduce and automatic package downloader to the mirror creation process, this time I managed to actually write it on python3. The goal of this tool is still the same, to avoid the hassle of manually go looking and downloading failing packages from Google and just run a single command instead. You can go and review the code here: https://review.openstack.org/#/c/585009/ I really appreciate any feedback, specially opportunities of improvement and any kind comments. Thank You - Guillermo Ponce On 7/18/18, 12:42 PM, "Ponce Castaneda, Guillermo A" wrote: >>On 7/18/18, 11:47 AM, "Dean Troyer" wrote: >>On Wed, Jul 18, 2018 at 8:26 AM, Ponce Castaneda, Guillermo A >> wrote: >>> That is correct, I do not think there is another node.js code, and that is why I >>> also created a Dockerfile so nobody has to install node on their machines and >>> just run it inside a container. >>I'm sorry but I do not consider requiring Docker and some non-trivial >>OS image to run a simple script to be an improvement. It isn't just >>the installation of the runtime it is also the cognitive overhead of >>requiring another bit of language expertise to maintain the tool. If >>this were a node project I'd say the same thing about introducing a >>python script. >Thanks for the feedback Dean, >I will the improve this tool on the points you are mentioning and will try going >at it again. >>dt >Guillermo Ponce >-- >>Dean Troyer >>dtroyer at gmail.com From scott.little at windriver.com Mon Jul 23 20:07:22 2018 From: scott.little at windriver.com (Scott Little) Date: Mon, 23 Jul 2018 16:07:22 -0400 Subject: [Starlingx-discuss] Adding packages to build .lst files In-Reply-To: <189BD4A4-E0D0-4014-812E-5DD2EDA889ED@intel.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F3A9@ALA-MBD.corp.ad.wrs.com> <939BBE33-59F9-4D2C-B813-B32CB0006634@intel.com> <2B6889A0-364E-4BC3-9190-D8227727B92F@intel.com> <189BD4A4-E0D0-4014-812E-5DD2EDA889ED@intel.com> Message-ID: Do we trust every link on google to point to a malware free version of the package ? I think it's ill advised to take the human out of the loop.  At most, list the validated download url's found... along with a warning from all but a few trusted url's. Scott On 18-07-23 03:58 PM, Ponce Castaneda, Guillermo A wrote: > Hello team, > > I am giving it another try to introduce and automatic package downloader > to the mirror creation process, this time I managed to actually write it > on python3. > > The goal of this tool is still the same, to avoid the hassle of manually go > looking and downloading failing packages from Google and just run a > single command instead. > > You can go and review the code here: https://review.openstack.org/#/c/585009/ > I really appreciate any feedback, specially opportunities of improvement and any > kind comments. > > Thank You > - Guillermo Ponce > > > On 7/18/18, 12:42 PM, "Ponce Castaneda, Guillermo A" wrote: > > > > >>On 7/18/18, 11:47 AM, "Dean Troyer" wrote: > > >>On Wed, Jul 18, 2018 at 8:26 AM, Ponce Castaneda, Guillermo A > >> wrote: > >>> That is correct, I do not think there is another node.js code, and that is why I > >>> also created a Dockerfile so nobody has to install node on their machines and > >>> just run it inside a container. > > >>I'm sorry but I do not consider requiring Docker and some non-trivial > >>OS image to run a simple script to be an improvement. It isn't just > >>the installation of the runtime it is also the cognitive overhead of > >>requiring another bit of language expertise to maintain the tool. If > >>this were a node project I'd say the same thing about introducing a > >>python script. > > >Thanks for the feedback Dean, > >I will the improve this tool on the points you are mentioning and will try going > >at it again. > > >>dt > > >Guillermo Ponce > > >-- > > >>Dean Troyer > >>dtroyer at gmail.com > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From guillermo.a.ponce.castaneda at intel.com Mon Jul 23 20:30:25 2018 From: guillermo.a.ponce.castaneda at intel.com (Ponce Castaneda, Guillermo A) Date: Mon, 23 Jul 2018 20:30:25 +0000 Subject: [Starlingx-discuss] Adding packages to build .lst files In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FBA24F3A9@ALA-MBD.corp.ad.wrs.com> <939BBE33-59F9-4D2C-B813-B32CB0006634@intel.com> <2B6889A0-364E-4BC3-9190-D8227727B92F@intel.com> <189BD4A4-E0D0-4014-812E-5DD2EDA889ED@intel.com> Message-ID: >On 7/23/18, 3:08 PM, "Scott Little" wrote: >Do we trust every link on google to point to a malware free version of >the package ? >I think it's ill advised to take the human out of the loop. At most, >list the validated download url's found... along with a warning from all >but a few trusted url's. Totally agree, the script prints the URL where the package comes from on Line 64: 64 print("Downloading file %02d: %s" % (count, p)) Regarding the trusted URLs, I did not know there was a list of them, in fact I thought the problem was that since the package was not found on the repositories, which are trusted, we needed to look for them on the web, if there is a list, I will make use of it and display any warning message just as suggested. The workaround so far is to run a command rpm -Kv on the packages to be sure the packages are signed and throw away the ones that are not. As for the automation of the rpm check process, it is still work in progress, I want to avoid using a subprocess command to do it and I want to do it using only python modules, so far I haven't had luck when looking for a module that does that, another reason not to use a subprocess command is that if you run the program from a system that does not have rpm command the script would fail anyway. >Scott Thank you - Guillermo Ponce >>On 18-07-23 03:58 PM, Ponce Castaneda, Guillermo A wrote: >> Hello team, >> I am giving it another try to introduce and automatic package downloader >> to the mirror creation process, this time I managed to actually write it >> on python3. >> The goal of this tool is still the same, to avoid the hassle of manually go >> looking and downloading failing packages from Google and just run a >> single command instead. >> You can go and review the code here: https://review.openstack.org/#/c/585009/ >> I really appreciate any feedback, specially opportunities of improvement and any >> kind comments. >> Thank You >> - Guillermo Ponce >> On 7/18/18, 12:42 PM, "Ponce Castaneda, Guillermo A" wrote: >> >>>On 7/18/18, 11:47 AM, "Dean Troyer" wrote: >>>On Wed, Jul 18, 2018 at 8:26 AM, Ponce Castaneda, Guillermo A >>> wrote: >>>> That is correct, I do not think there is another node.js code, and that is why I >>>> also created a Dockerfile so nobody has to install node on their machines and >>>> just run it inside a container. >>>I'm sorry but I do not consider requiring Docker and some non-trivial >>>OS image to run a simple script to be an improvement. It isn't just >>>the installation of the runtime it is also the cognitive overhead of >>>requiring another bit of language expertise to maintain the tool. If >>>this were a node project I'd say the same thing about introducing a >>>python script. >>Thanks for the feedback Dean, >>I will the improve this tool on the points you are mentioning and will try going >>at it again. >>>dt >>Guillermo Ponce >>-- >>>Dean Troyer >>>dtroyer at gmail.com >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >_______________________________________________ >Starlingx-discuss mailing list >Starlingx-discuss at lists.starlingx.io >http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From mario.alfredo.c.arevalo at intel.com Mon Jul 23 21:25:52 2018 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Mon, 23 Jul 2018 21:25:52 +0000 Subject: [Starlingx-discuss] Use koji to create repository with required RPMS In-Reply-To: <9FCFFF8D-4089-48F2-B14E-CD8ABC8AF560@intel.com> References: <9FCFFF8D-4089-48F2-B14E-CD8ABC8AF560@intel.com> Message-ID: <6594B51DBE477C48AAE23675314E6C465991E68C@fmsmsx107.amr.corp.intel.com> Hi Jesus, You are touching a very important point related to building process. I think, one of the most painful concerns is which mirror has to deal with the constantly loss of tracking of some packages due to the dependence with multiple third party host sites. I think the first approach sounds good and is an achievable goal. The packages described in the third parties file are an excellent staring point due to they are more prone to disappear and each time will be more complicated to find a secure copy. Best regards. Mario. ________________________________________ From: Ornelas Aguayo, Jesus [jesus.ornelas.aguayo at intel.com] Sent: Wednesday, July 18, 2018 11:23 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Use koji to create repository with required RPMS Hi all, As we know we use the centos-mirror-tools from the stx-tools repo to download the required RPMS to build StarlingX, this tool downloads the packages from the following list files: Filename Packages Description rpms_from_3rd_parties.lst 9 Third party packages without repository (downloaded by wget) rpms_from_centos_3rd_parties.lst. 152 Third party packages with repository rpms_from_centos_repo.lst 1699 Centos packages with repository As time goes by, Some packages disappear and we need to replace the repositories or urls , and in some scenarios the specific package version disappears. This can be fixed by getting the source code of the packages mentioned above and their dependencies ( ~3900 packages) and use koji to build the required versions, this way we can host a repository with the required RPMS and SRPMS to build starlingX . I would like to open a discussion of this proposal, the first approach would be start hosting the rpms_from_3rd_parties.lst(downloaded by wget) and replacing the package repository in the centos-mirror-tools list, so changes will be gradually. Once this is completed we can follow the same process for the the rpms_from_centos_3rd_parties.lst and ending with the rms_from_centos_repo.lst. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From hayde.martinez.landa at intel.com Mon Jul 23 22:35:03 2018 From: hayde.martinez.landa at intel.com (Martinez Landa, Hayde) Date: Mon, 23 Jul 2018 22:35:03 +0000 Subject: [Starlingx-discuss] Milestone 2018.07.0 is available. In-Reply-To: References: <9A85D2917C58154C960D95352B22818BAB5653D8@fmsmsx117.amr.corp.intel.com> Message-ID: <22CBF5E7-BDA5-4223-A413-3BDE86C1EFD5@intel.com> >> As a second step in our release process, can someone please do a build >> against the branch? And send the ISO to the Test team? >@Hayde is taking care of this step, will provide the update as soon as possible. I have successfully built an .iso on branch M/2018.07 and I have submitted a patch that applies for both, master [0] and branch M/2018.07 [1] that solves the package dependency issues. [0] https://review.openstack.org/#/c/585043/ [1] https://review.openstack.org/#/c/585046/ From dtroyer at gmail.com Mon Jul 23 22:53:45 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Mon, 23 Jul 2018 17:53:45 -0500 Subject: [Starlingx-discuss] Milestone 2018.07.0 is available. In-Reply-To: <22CBF5E7-BDA5-4223-A413-3BDE86C1EFD5@intel.com> References: <9A85D2917C58154C960D95352B22818BAB5653D8@fmsmsx117.amr.corp.intel.com> <22CBF5E7-BDA5-4223-A413-3BDE86C1EFD5@intel.com> Message-ID: On Mon, Jul 23, 2018 at 5:35 PM, Martinez Landa, Hayde wrote: > I have successfully built an .iso on branch M/2018.07 and I have submitted a patch that > applies for both, master [0] and branch M/2018.07 [1] that solves the package dependency issues. \o/ The patches look good, we'll merge the one for master first, and make any adjustments needed before merging the backport (I don't expect any in this case). We should get some reviews on https://review.openstack.org/#/c/584348/ to merge the m/2018.07 manifest... dt -- Dean Troyer dtroyer at gmail.com From abraham.arce.moreno at intel.com Mon Jul 23 23:36:03 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Mon, 23 Jul 2018 23:36:03 +0000 Subject: [Starlingx-discuss] StarlingX: Tar Compressed Files Repository Restructuring Message-ID: The build of StarlingX relies, besides RPM Binaries and Sources, in a collection of packages in the form of Tar Compressed files. Initial review already merged can be found under Gerrit Review "StarlingX: Tar Compressed files repository" [0] We have received several feedback about its content and it is time to gather all of it including security related discussion to restructure the way it is handled, if needed. Please take some time to read, review and send back comments. The complete analysis of these required packages is found at [1]. [ Call Sequence ] The call sequence under CentOS Mirror Tools [2] is as follows ending in executing our tarball-dl.sh: 1 download_mirror.sh 1.1 dl_rpms.sh 1.2 dl_other_from_centos_repo.sh 1.3 tarball-dl.sh Open Questions: - Should we keep this script being called from download_mirror.sh? - Should we keep this file being written as shell script? - Any comment based on midterm / long term changes? - Any other comment? [ List of Packages ] The script tarball-dl.sh [3] takes a text file tarball-dl.lst [4] as argument which contains 3 columns: - Column 1, name of package including extension as it is referenced by the build system. - Column 2, name of the directory path after it is decompressed as it is referenced in the build system. - Column 3, the URL for the package download. Open Questions: - We use "#" to separate columns however in our review we have suggestions to use other characters such as "|" including also change to CSV format, what do you think? - Any other comment? [ List of Packages: Column 1 ] Our build system have references to the name of the file, the file name might include: - name of the package - version - commit id Some examples? - python-cephclient-v0.1.0.5.tar.gz - gnulib-ffc927e.tar.gz - puppet-boolean-22b726dd78b0a60a224cc7054aebbf28e9306f62.tar.gz A special character "!" is used at the beginning of 6 package file names denoting they require special handling is required: additional steps besides the common process including but not limited to remove text from some files, use only one directory, etc: - integrity-kmod-668a8270.tar.gz - mariadb-10.1.28.tar.gz - mvn.repo.tgz - qat1.7.upstream.l.1.0.3-42.tar.gz - tpm-kmod-668a8270.tar.gz - tss2-930.tar.gz Open Questions: - Any specific method to handle these 6 packages? - Any other comment? [ List of Packages: Column 2 ] Our build system uses defined paths after the Tarball package filename is decompressed, see Columns H " 'Directory Name Cgcs-Dl" and Column I " 'Directory Name tarball-dl.sh" for a comparison: - It could be the same after it is decompressed from the original file - dpkg_1.18.24.tar.xz#dpkg-1.18.24 - It could use a different name after it is decompressed from the original file - !integrity-kmod-668a8270.tar.gz#integrity - puppet-dnsmasq-cff07e90890662972c97684a2baee964f68ff3ed.tar.gz#packstack/puppet/modules/dnsmasq/ Open Questions: - Do we want to have predefined paths or should we targeted default paths as given by the original file names? - Any other comment? [ List of Packages: Column 3 ] Nothing specific here but hardcoded URLs. Open Questions: - Use wget Vs curl? - Any other method to get the sources of the packages? Is it possible to migrate to source RPMs? [ Security ] Open Discussion! We went through an initial package integrity verification, see column F "GPG Key" but only 6 packages got their PGP key available in their official repository source. Open Questions: - What is the best way to approach? - Specific question. Can we say Tarballs coming from Git sources are naturally verified? - Any other comment? [0] https://review.openstack.org/#/c/577953/ [1] https://ethercalc.openstack.org/615btsy7i8k6 [2] https://git.openstack.org/cgit/openstack/stx-tools/tree/centos-mirror-tools [3] https://git.openstack.org/cgit/openstack/stx-tools/tree/centos-mirror-tools/tarball-dl.sh [4] https://git.openstack.org/cgit/openstack/stx-tools/tree/centos-mirror-tools/tarball-dl.lst From bruce.e.jones at intel.com Mon Jul 23 23:52:59 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 23 Jul 2018 23:52:59 +0000 Subject: [Starlingx-discuss] Milestone 2018.07.0 is available. In-Reply-To: References: <9A85D2917C58154C960D95352B22818BAB5653D8@fmsmsx117.amr.corp.intel.com> <22CBF5E7-BDA5-4223-A413-3BDE86C1EFD5@intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB56673A@fmsmsx117.amr.corp.intel.com> Awesome! Ada please have tests run against this build and report the results, thanks! brucej -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Monday, July 23, 2018 3:54 PM To: Martinez Landa, Hayde Cc: Arce Moreno, Abraham ; Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Milestone 2018.07.0 is available. On Mon, Jul 23, 2018 at 5:35 PM, Martinez Landa, Hayde wrote: > I have successfully built an .iso on branch M/2018.07 and I have > submitted a patch that applies for both, master [0] and branch M/2018.07 [1] that solves the package dependency issues. \o/ The patches look good, we'll merge the one for master first, and make any adjustments needed before merging the backport (I don't expect any in this case). We should get some reviews on https://review.openstack.org/#/c/584348/ to merge the m/2018.07 manifest... dt -- Dean Troyer dtroyer at gmail.com From abraham.arce.moreno at intel.com Tue Jul 24 00:19:42 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 24 Jul 2018 00:19:42 +0000 Subject: [Starlingx-discuss] Milestone 2018.07.0 is available. In-Reply-To: <9A85D2917C58154C960D95352B22818BAB56673A@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB5653D8@fmsmsx117.amr.corp.intel.com> <22CBF5E7-BDA5-4223-A413-3BDE86C1EFD5@intel.com> <9A85D2917C58154C960D95352B22818BAB56673A@fmsmsx117.amr.corp.intel.com> Message-ID: > > I have successfully built an .iso on branch M/2018.07 and I have > > submitted a patch that applies for both, master [0] and branch M/2018.07 > [1] that solves the package dependency issues. > > \o/ > > The patches look good, we'll merge the one for master first, and make any > adjustments needed before merging the backport (I don't expect any in this > case). > > We should get some reviews on https://review.openstack.org/#/c/584348/ > to merge the m/2018.07 manifest... > > dt Developer Guide has been updated including notes for branches Master and M/2018.07 https://wiki.openstack.org/wiki/StarlingX/Developer_Guide From abraham.arce.moreno at intel.com Tue Jul 24 00:31:13 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 24 Jul 2018 00:31:13 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F50B3A@SHSMSX104.ccr.corp.intel.com> Message-ID: > > When built iso, it had some dependency issues, then commented out > > below lines in build_iso/image.inc > > > > #selinux-policy > > ... > > #dockers-ce > > #kubernetes > > #kubernetes-client > > #kubernetes-kubeadm > > #kubernetes-master > > #kubernetes-node > > Let us try today and will get back to this mailing list. Zhipeng, @Hayde has been able to build today from M/2018.07 [0] removing the need to comment above dependencies. Can you please help us confirm the steps are correct starting from scratch? Master compilation is in process using Hayde's fix. Developer Guide has been updated including notes for branches Master and M/2018.07 https://wiki.openstack.org/wiki/StarlingX/Developer_Guide M/2018.07 generated ISO is being deployed today under Controller Storage and Simplex configurations following Installation Guide [1] and Validation Guide [2]: [0] http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000321.html [1] https://wiki.openstack.org/wiki/StarlingX/Installation_Guide [2] https://wiki.openstack.org/wiki/StarlingX/Validation_Guide From zhipengs.liu at intel.com Tue Jul 24 02:11:57 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 24 Jul 2018 02:11:57 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F50B3A@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C752F511D2@SHSMSX104.ccr.corp.intel.com> Hi Abraham, Thanks for your quick feedback! I will also try it according to your updated GUIDE and update to you later today. Since dependency issue has been fixed, no need for my patch. zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月24日 8:31 To: Arce Moreno, Abraham ; Liu, ZhipengS ; Miller, Frank ; Xie, Cindy ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller > > When built iso, it had some dependency issues, then commented out > > below lines in build_iso/image.inc > > > > #selinux-policy > > ... > > #dockers-ce > > #kubernetes > > #kubernetes-client > > #kubernetes-kubeadm > > #kubernetes-master > > #kubernetes-node > > Let us try today and will get back to this mailing list. Zhipeng, @Hayde has been able to build today from M/2018.07 [0] removing the need to comment above dependencies. Can you please help us confirm the steps are correct starting from scratch? Master compilation is in process using Hayde's fix. Developer Guide has been updated including notes for branches Master and M/2018.07 https://wiki.openstack.org/wiki/StarlingX/Developer_Guide M/2018.07 generated ISO is being deployed today under Controller Storage and Simplex configurations following Installation Guide [1] and Validation Guide [2]: [0] http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000321.html [1] https://wiki.openstack.org/wiki/StarlingX/Installation_Guide [2] https://wiki.openstack.org/wiki/StarlingX/Validation_Guide From erich.cordoba.malibran at intel.com Tue Jul 24 03:37:56 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 24 Jul 2018 03:37:56 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: <93814834B4855241994F290E959305C752F511D2@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F50B3A@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F511D2@SHSMSX104.ccr.corp.intel.com> Message-ID: <32D1079A-B94E-429B-B1B8-D917E1414699@intel.com> Hi, I think there are two issues here, 1.- kubernetes-kubeadm requires a containernetworking-cni and that causes a failure in build-iso, this is reported here[0] 2.- With the dependencies resolved and with docker and kubernetes packages within the ISO, the config_controller command fails in step 6 trying to install docker-ce. We have seen this behavior in three different builds, also we have see it as sporadic, same ISO in some system finishes successful and in other fails. Next time we see the problem we'll make a further debug. [0] https://storyboard.openstack.org/#!/story/2003011 On 7/23/18, 9:12 PM, "Liu, ZhipengS" wrote: Hi Abraham, Thanks for your quick feedback! I will also try it according to your updated GUIDE and update to you later today. Since dependency issue has been fixed, no need for my patch. zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月24日 8:31 To: Arce Moreno, Abraham ; Liu, ZhipengS ; Miller, Frank ; Xie, Cindy ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller > > When built iso, it had some dependency issues, then commented out > > below lines in build_iso/image.inc > > > > #selinux-policy > > ... > > #dockers-ce > > #kubernetes > > #kubernetes-client > > #kubernetes-kubeadm > > #kubernetes-master > > #kubernetes-node > > Let us try today and will get back to this mailing list. Zhipeng, @Hayde has been able to build today from M/2018.07 [0] removing the need to comment above dependencies. Can you please help us confirm the steps are correct starting from scratch? Master compilation is in process using Hayde's fix. Developer Guide has been updated including notes for branches Master and M/2018.07 https://wiki.openstack.org/wiki/StarlingX/Developer_Guide M/2018.07 generated ISO is being deployed today under Controller Storage and Simplex configurations following Installation Guide [1] and Validation Guide [2]: [0] http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000321.html [1] https://wiki.openstack.org/wiki/StarlingX/Installation_Guide [2] https://wiki.openstack.org/wiki/StarlingX/Validation_Guide _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From yan.chen at intel.com Tue Jul 24 04:37:43 2018 From: yan.chen at intel.com (Chen, Yan) Date: Tue, 24 Jul 2018 04:37:43 +0000 Subject: [Starlingx-discuss] Python 2to3 code porting Message-ID: <72AD03D27224C74982BE13246D75B397399260EA@SHSMSX103.ccr.corp.intel.com> Hi, there, I just wonder if anyone is already working on this task now? I created a story days ago, and studied most of our Python code and the python rpms in the system. Here's the conclusions: 1. Most of the Tis dependency python packages are already Python 2/3 compatible, but still some exceptions: a. The following packages are Python2 only and same for the latest code tree: i. createrepo-0.9.9 (used by cgcs-patch-controller) ii. net-snmp-5.7.2 (used by snmp-audittrail) iii. pyparted-3.9 (used by sysinv) b. The following packages are Python 2 but the latest version has Python 3 support, need upgrade: i. python-daemon-1.6 (used by logmgmt) * This analysis is still on-going, more packages may be found. 2. The Python modules for Python 2/3 compatibility (python-futures and python-six) are already included. 3. Some of the openstack packages/dependencies are Python 2 only, we may need to find a good version of Openstack to upgrade. We can start to clean our code first, I think we follow the guideline here, one topic each time, how do you think? http://python-future.org/compatible_idioms.html Here's the link for the story: https://storyboard.openstack.org/#!/story/2002909 Yan -------------- next part -------------- An HTML attachment was scrubbed... URL: From xiaoyan.li at intel.com Tue Jul 24 07:18:29 2018 From: xiaoyan.li at intel.com (Li, Xiaoyan) Date: Tue, 24 Jul 2018 07:18:29 +0000 Subject: [Starlingx-discuss] Replace WR backup with Cinder upstream backup Message-ID: Hi all, Currently in StarlingX, it uses WR backup to backup volumes into local folders. On the other side, Cinder provides its own backup service to backup volumes to kinds of backend storages, including local folders, Ceph etc. This is already in Pike release. I am going to replace WR backup with Cinder upstream backup service, and it provides more choice to do backup. To do the change, except work in StarlingX/Cinder, it also needs update in the component std-config. In Cinder upstream, backup service is a standalone service. And in WR backup, it is in volume service. As a result, we need to allow admins to enable/start backup service when installing StarlingX. This needs to be update in std-config. Anyone is working on std-config? Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Tue Jul 24 07:59:19 2018 From: Robert.Church at windriver.com (Church, Robert) Date: Tue, 24 Jul 2018 07:59:19 +0000 Subject: [Starlingx-discuss] Replace WR backup with Cinder upstream backup In-Reply-To: References: Message-ID: <6EDCC53B-A060-490C-9A06-12DAA071D23B@windriver.com> Hi Lisa, We have already completed the effort to enable upstream cinder backup and replace the current functionality provided by the custom backup API. Cinder backup service will be started along with the other Cinder services when Cinder is enabled. I anticipate we’ll deliver this functionality in the coming weeks. Once delivered, we’ll still need to retire the custom API code for volume import and volume/snapshot export to align with upstream. We will then be in a position to look at expanding support for backing up to other storage backends. Regards, Bob From: "Li, Xiaoyan" Date: Tuesday, July 24, 2018 at 2:18 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Replace WR backup with Cinder upstream backup Hi all, Currently in StarlingX, it uses WR backup to backup volumes into local folders. On the other side, Cinder provides its own backup service to backup volumes to kinds of backend storages, including local folders, Ceph etc. This is already in Pike release. I am going to replace WR backup with Cinder upstream backup service, and it provides more choice to do backup. To do the change, except work in StarlingX/Cinder, it also needs update in the component std-config. In Cinder upstream, backup service is a standalone service. And in WR backup, it is in volume service. As a result, we need to allow admins to enable/start backup service when installing StarlingX. This needs to be update in std-config. Anyone is working on std-config? Best wishes Lisa -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Tue Jul 24 09:08:22 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 24 Jul 2018 09:08:22 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: <32D1079A-B94E-429B-B1B8-D917E1414699@intel.com> References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F50B3A@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F511D2@SHSMSX104.ccr.corp.intel.com> <32D1079A-B94E-429B-B1B8-D917E1414699@intel.com> Message-ID: <93814834B4855241994F290E959305C752F514DA@SHSMSX104.ccr.corp.intel.com> Hi Erich and Abraham, According to the latest GUIDE, changes in imag.inc are reverted. I synced the latest code and finished build. When build iso, there is a dependency issue I saw below. 16:25:59 These RPMS had problems (likely version conflicts) 16:25:59 containernetworking-cni 16:25:59 selinux-policy-base 16:25:59 selinux-policy-targeted 16:25:59 Could not install dependencies After I downloaded below 3 rpms, build-iso pass. policycoreutils-2.5-22.el7.x86_64.rpm policycoreutils-newrole-2.5-22.el7.x86_64.rpm policycoreutils-python-2.5-22.el7.x86_64.rpm Do you have the same dependency issue? Need to update it to GUIDE if so. Zhipeng -----Original Message----- From: Cordoba Malibran, Erich Sent: 2018年7月24日 11:38 To: Liu, ZhipengS ; Arce Moreno, Abraham ; Miller, Frank ; Xie, Cindy ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Hi, I think there are two issues here, 1.- kubernetes-kubeadm requires a containernetworking-cni and that causes a failure in build-iso, this is reported here[0] 2.- With the dependencies resolved and with docker and kubernetes packages within the ISO, the config_controller command fails in step 6 trying to install docker-ce. We have seen this behavior in three different builds, also we have see it as sporadic, same ISO in some system finishes successful and in other fails. Next time we see the problem we'll make a further debug. [0] https://storyboard.openstack.org/#!/story/2003011 On 7/23/18, 9:12 PM, "Liu, ZhipengS" wrote: Hi Abraham, Thanks for your quick feedback! I will also try it according to your updated GUIDE and update to you later today. Since dependency issue has been fixed, no need for my patch. zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月24日 8:31 To: Arce Moreno, Abraham ; Liu, ZhipengS ; Miller, Frank ; Xie, Cindy ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller > > When built iso, it had some dependency issues, then commented out > > below lines in build_iso/image.inc > > > > #selinux-policy > > ... > > #dockers-ce > > #kubernetes > > #kubernetes-client > > #kubernetes-kubeadm > > #kubernetes-master > > #kubernetes-node > > Let us try today and will get back to this mailing list. Zhipeng, @Hayde has been able to build today from M/2018.07 [0] removing the need to comment above dependencies. Can you please help us confirm the steps are correct starting from scratch? Master compilation is in process using Hayde's fix. Developer Guide has been updated including notes for branches Master and M/2018.07 https://wiki.openstack.org/wiki/StarlingX/Developer_Guide M/2018.07 generated ISO is being deployed today under Controller Storage and Simplex configurations following Installation Guide [1] and Validation Guide [2]: [0] http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000321.html [1] https://wiki.openstack.org/wiki/StarlingX/Installation_Guide [2] https://wiki.openstack.org/wiki/StarlingX/Validation_Guide _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Tue Jul 24 11:20:05 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 24 Jul 2018 11:20:05 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: <93814834B4855241994F290E959305C752F514DA@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F50B3A@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F511D2@SHSMSX104.ccr.corp.intel.com> <32D1079A-B94E-429B-B1B8-D917E1414699@intel.com> <93814834B4855241994F290E959305C752F514DA@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B2E3330@SHSMSX104.ccr.corp.intel.com> Zhipeng, Please check if you have this patch included in your code base: https://review.openstack.org/#/c/585043/ this one newly merged in the morning. GDC has built the ISO with the patch and Ada is doing the validation. Thx. - cindy -----Original Message----- From: Liu, ZhipengS Sent: Tuesday, July 24, 2018 5:08 PM To: Cordoba Malibran, Erich ; Arce Moreno, Abraham ; Miller, Frank ; Xie, Cindy ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Hi Erich and Abraham, According to the latest GUIDE, changes in imag.inc are reverted. I synced the latest code and finished build. When build iso, there is a dependency issue I saw below. 16:25:59 These RPMS had problems (likely version conflicts) 16:25:59 containernetworking-cni 16:25:59 selinux-policy-base 16:25:59 selinux-policy-targeted 16:25:59 Could not install dependencies After I downloaded below 3 rpms, build-iso pass. policycoreutils-2.5-22.el7.x86_64.rpm policycoreutils-newrole-2.5-22.el7.x86_64.rpm policycoreutils-python-2.5-22.el7.x86_64.rpm Do you have the same dependency issue? Need to update it to GUIDE if so. Zhipeng -----Original Message----- From: Cordoba Malibran, Erich Sent: 2018年7月24日 11:38 To: Liu, ZhipengS ; Arce Moreno, Abraham ; Miller, Frank ; Xie, Cindy ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Hi, I think there are two issues here, 1.- kubernetes-kubeadm requires a containernetworking-cni and that causes a failure in build-iso, this is reported here[0] 2.- With the dependencies resolved and with docker and kubernetes packages within the ISO, the config_controller command fails in step 6 trying to install docker-ce. We have seen this behavior in three different builds, also we have see it as sporadic, same ISO in some system finishes successful and in other fails. Next time we see the problem we'll make a further debug. [0] https://storyboard.openstack.org/#!/story/2003011 On 7/23/18, 9:12 PM, "Liu, ZhipengS" wrote: Hi Abraham, Thanks for your quick feedback! I will also try it according to your updated GUIDE and update to you later today. Since dependency issue has been fixed, no need for my patch. zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月24日 8:31 To: Arce Moreno, Abraham ; Liu, ZhipengS ; Miller, Frank ; Xie, Cindy ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller > > When built iso, it had some dependency issues, then commented out > > below lines in build_iso/image.inc > > > > #selinux-policy > > ... > > #dockers-ce > > #kubernetes > > #kubernetes-client > > #kubernetes-kubeadm > > #kubernetes-master > > #kubernetes-node > > Let us try today and will get back to this mailing list. Zhipeng, @Hayde has been able to build today from M/2018.07 [0] removing the need to comment above dependencies. Can you please help us confirm the steps are correct starting from scratch? Master compilation is in process using Hayde's fix. Developer Guide has been updated including notes for branches Master and M/2018.07 https://wiki.openstack.org/wiki/StarlingX/Developer_Guide M/2018.07 generated ISO is being deployed today under Controller Storage and Simplex configurations following Installation Guide [1] and Validation Guide [2]: [0] http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000321.html [1] https://wiki.openstack.org/wiki/StarlingX/Installation_Guide [2] https://wiki.openstack.org/wiki/StarlingX/Validation_Guide _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Brent.Rowsell at windriver.com Tue Jul 24 11:22:51 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Tue, 24 Jul 2018 11:22:51 +0000 Subject: [Starlingx-discuss] Python 2to3 code porting In-Reply-To: <72AD03D27224C74982BE13246D75B397399260EA@SHSMSX103.ccr.corp.intel.com> References: <72AD03D27224C74982BE13246D75B397399260EA@SHSMSX103.ccr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0E5AA4@ALA-MBD.corp.ad.wrs.com> The priority of this needs to be discussed at the next architecture meeting. With all current churn and lack of a working build, this activity in my opinion needs to wait. Brent From: Chen, Yan [mailto:yan.chen at intel.com] Sent: Tuesday, July 24, 2018 12:38 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Python 2to3 code porting Hi, there, I just wonder if anyone is already working on this task now? I created a story days ago, and studied most of our Python code and the python rpms in the system. Here's the conclusions: 1. Most of the Tis dependency python packages are already Python 2/3 compatible, but still some exceptions: a. The following packages are Python2 only and same for the latest code tree: i. createrepo-0.9.9 (used by cgcs-patch-controller) ii. net-snmp-5.7.2 (used by snmp-audittrail) iii. pyparted-3.9 (used by sysinv) b. The following packages are Python 2 but the latest version has Python 3 support, need upgrade: i. python-daemon-1.6 (used by logmgmt) * This analysis is still on-going, more packages may be found. 2. The Python modules for Python 2/3 compatibility (python-futures and python-six) are already included. 3. Some of the openstack packages/dependencies are Python 2 only, we may need to find a good version of Openstack to upgrade. We can start to clean our code first, I think we follow the guideline here, one topic each time, how do you think? http://python-future.org/compatible_idioms.html Here's the link for the story: https://storyboard.openstack.org/#!/story/2002909 Yan -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Tue Jul 24 13:10:20 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 24 Jul 2018 13:10:20 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B2E3330@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F50B3A@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F511D2@SHSMSX104.ccr.corp.intel.com> <32D1079A-B94E-429B-B1B8-D917E1414699@intel.com> <93814834B4855241994F290E959305C752F514DA@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E3330@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C752F515B7@SHSMSX104.ccr.corp.intel.com> Hi Cindy, This is the key one, already in my code base. BRs zhipeng -----Original Message----- From: Xie, Cindy Sent: 2018年7月24日 19:20 To: Liu, ZhipengS ; Cordoba Malibran, Erich ; Arce Moreno, Abraham ; Miller, Frank ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Zhipeng, Please check if you have this patch included in your code base: https://review.openstack.org/#/c/585043/ this one newly merged in the morning. GDC has built the ISO with the patch and Ada is doing the validation. Thx. - cindy -----Original Message----- From: Liu, ZhipengS Sent: Tuesday, July 24, 2018 5:08 PM To: Cordoba Malibran, Erich ; Arce Moreno, Abraham ; Miller, Frank ; Xie, Cindy ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Hi Erich and Abraham, According to the latest GUIDE, changes in imag.inc are reverted. I synced the latest code and finished build. When build iso, there is a dependency issue I saw below. 16:25:59 These RPMS had problems (likely version conflicts) 16:25:59 containernetworking-cni 16:25:59 selinux-policy-base 16:25:59 selinux-policy-targeted 16:25:59 Could not install dependencies After I downloaded below 3 rpms, build-iso pass. policycoreutils-2.5-22.el7.x86_64.rpm policycoreutils-newrole-2.5-22.el7.x86_64.rpm policycoreutils-python-2.5-22.el7.x86_64.rpm Do you have the same dependency issue? Need to update it to GUIDE if so. Zhipeng -----Original Message----- From: Cordoba Malibran, Erich Sent: 2018年7月24日 11:38 To: Liu, ZhipengS ; Arce Moreno, Abraham ; Miller, Frank ; Xie, Cindy ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Hi, I think there are two issues here, 1.- kubernetes-kubeadm requires a containernetworking-cni and that causes a failure in build-iso, this is reported here[0] 2.- With the dependencies resolved and with docker and kubernetes packages within the ISO, the config_controller command fails in step 6 trying to install docker-ce. We have seen this behavior in three different builds, also we have see it as sporadic, same ISO in some system finishes successful and in other fails. Next time we see the problem we'll make a further debug. [0] https://storyboard.openstack.org/#!/story/2003011 On 7/23/18, 9:12 PM, "Liu, ZhipengS" wrote: Hi Abraham, Thanks for your quick feedback! I will also try it according to your updated GUIDE and update to you later today. Since dependency issue has been fixed, no need for my patch. zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月24日 8:31 To: Arce Moreno, Abraham ; Liu, ZhipengS ; Miller, Frank ; Xie, Cindy ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller > > When built iso, it had some dependency issues, then commented out > > below lines in build_iso/image.inc > > > > #selinux-policy > > ... > > #dockers-ce > > #kubernetes > > #kubernetes-client > > #kubernetes-kubeadm > > #kubernetes-master > > #kubernetes-node > > Let us try today and will get back to this mailing list. Zhipeng, @Hayde has been able to build today from M/2018.07 [0] removing the need to comment above dependencies. Can you please help us confirm the steps are correct starting from scratch? Master compilation is in process using Hayde's fix. Developer Guide has been updated including notes for branches Master and M/2018.07 https://wiki.openstack.org/wiki/StarlingX/Developer_Guide M/2018.07 generated ISO is being deployed today under Controller Storage and Simplex configurations following Installation Guide [1] and Validation Guide [2]: [0] http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000321.html [1] https://wiki.openstack.org/wiki/StarlingX/Installation_Guide [2] https://wiki.openstack.org/wiki/StarlingX/Validation_Guide _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From zhipengs.liu at intel.com Tue Jul 24 13:41:00 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 24 Jul 2018 13:41:00 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: <93814834B4855241994F290E959305C752F515B7@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F50B3A@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F511D2@SHSMSX104.ccr.corp.intel.com> <32D1079A-B94E-429B-B1B8-D917E1414699@intel.com> <93814834B4855241994F290E959305C752F514DA@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E3330@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F515B7@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C752F515EF@SHSMSX104.ccr.corp.intel.com> Cindy, Sorry, I copied the wrong build error info in my first email today, which mislead you. It should be below one ========================================= 17:34:28 Debug: Packages still unresolved: 17:34:28 17:34:29 Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/zhipengl/starlingx/export/deps.txt for details -- exiting 17:34:29 These RPMS had problems (likely version conflicts) 17:34:29 policycoreutils 17:34:29 policycoreutils-newrole 17:34:29 policycoreutils-python 17:34:29 Could not install dependencies ============================================== From error detail log, it indicates selinux-policy depend on policycoreutils with version >= 2.5-18. In current mirror, we only have two related RPM below. policycoreutils-2.5-17.1.el7.x86_64. policycoreutils-devel-2.5-17.1.el7.x86_64.rpm policycoreutils-python-2.5-17.1.el7.x86_64.rpm So, I downloaded below 3 RPM, and build-iso pass (with latest code today) policycoreutils-2.5-22.el7.x86_64.rpm policycoreutils-newrole-2.5-22.el7.x86_64.rpm policycoreutils-python-2.5-22.el7.x86_64.rpm I also deployed with the ISO I built without comment out kubernetes/docker/connectd. Then it failed at step6/8 during Config_controller. With the error info in puppet.log as below. ========================================================= Error: Systemd start for connectd failed! Stage/Platform::Collectd/Service[collectd]/ensure:change from stopped to running failed: Systemd start for collectd failed. ========================================================= @Erich and Abraham, any comment on my build and test result? Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: 2018年7月24日 21:10 To: Xie, Cindy ; Cordoba Malibran, Erich ; Arce Moreno, Abraham ; Miller, Frank ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Hi Cindy, This is the key one, already in my code base. BRs zhipeng -----Original Message----- From: Xie, Cindy Sent: 2018年7月24日 19:20 To: Liu, ZhipengS ; Cordoba Malibran, Erich ; Arce Moreno, Abraham ; Miller, Frank ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Zhipeng, Please check if you have this patch included in your code base: https://review.openstack.org/#/c/585043/ this one newly merged in the morning. GDC has built the ISO with the patch and Ada is doing the validation. Thx. - cindy -----Original Message----- From: Liu, ZhipengS Sent: Tuesday, July 24, 2018 5:08 PM To: Cordoba Malibran, Erich ; Arce Moreno, Abraham ; Miller, Frank ; Xie, Cindy ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Hi Erich and Abraham, According to the latest GUIDE, changes in imag.inc are reverted. I synced the latest code and finished build. When build iso, there is a dependency issue I saw below. 16:25:59 These RPMS had problems (likely version conflicts) 16:25:59 containernetworking-cni 16:25:59 selinux-policy-base 16:25:59 selinux-policy-targeted 16:25:59 Could not install dependencies After I downloaded below 3 rpms, build-iso pass. policycoreutils-2.5-22.el7.x86_64.rpm policycoreutils-newrole-2.5-22.el7.x86_64.rpm policycoreutils-python-2.5-22.el7.x86_64.rpm Do you have the same dependency issue? Need to update it to GUIDE if so. Zhipeng -----Original Message----- From: Cordoba Malibran, Erich Sent: 2018年7月24日 11:38 To: Liu, ZhipengS ; Arce Moreno, Abraham ; Miller, Frank ; Xie, Cindy ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Hi, I think there are two issues here, 1.- kubernetes-kubeadm requires a containernetworking-cni and that causes a failure in build-iso, this is reported here[0] 2.- With the dependencies resolved and with docker and kubernetes packages within the ISO, the config_controller command fails in step 6 trying to install docker-ce. We have seen this behavior in three different builds, also we have see it as sporadic, same ISO in some system finishes successful and in other fails. Next time we see the problem we'll make a further debug. [0] https://storyboard.openstack.org/#!/story/2003011 On 7/23/18, 9:12 PM, "Liu, ZhipengS" wrote: Hi Abraham, Thanks for your quick feedback! I will also try it according to your updated GUIDE and update to you later today. Since dependency issue has been fixed, no need for my patch. zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月24日 8:31 To: Arce Moreno, Abraham ; Liu, ZhipengS ; Miller, Frank ; Xie, Cindy ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller > > When built iso, it had some dependency issues, then commented out > > below lines in build_iso/image.inc > > > > #selinux-policy > > ... > > #dockers-ce > > #kubernetes > > #kubernetes-client > > #kubernetes-kubeadm > > #kubernetes-master > > #kubernetes-node > > Let us try today and will get back to this mailing list. Zhipeng, @Hayde has been able to build today from M/2018.07 [0] removing the need to comment above dependencies. Can you please help us confirm the steps are correct starting from scratch? Master compilation is in process using Hayde's fix. Developer Guide has been updated including notes for branches Master and M/2018.07 https://wiki.openstack.org/wiki/StarlingX/Developer_Guide M/2018.07 generated ISO is being deployed today under Controller Storage and Simplex configurations following Installation Guide [1] and Validation Guide [2]: [0] http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000321.html [1] https://wiki.openstack.org/wiki/StarlingX/Installation_Guide [2] https://wiki.openstack.org/wiki/StarlingX/Validation_Guide _______________________________________________ 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 abraham.arce.moreno at intel.com Tue Jul 24 13:53:10 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 24 Jul 2018 13:53:10 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: <93814834B4855241994F290E959305C752F515B7@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F50B3A@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F511D2@SHSMSX104.ccr.corp.intel.com> <32D1079A-B94E-429B-B1B8-D917E1414699@intel.com> <93814834B4855241994F290E959305C752F514DA@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E3330@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F515B7@SHSMSX104.ccr.corp.intel.com> Message-ID: > This is the key one, already in my code base Yes Zhipeng, you are correct! Those packages are missing to have the full build. Do you have the patch available? If not we can work on it with CC to you. From scott.little at windriver.com Tue Jul 24 14:23:03 2018 From: scott.little at windriver.com (Scott Little) Date: Tue, 24 Jul 2018 10:23:03 -0400 Subject: [Starlingx-discuss] Python 2to3 code porting In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB0E5AA4@ALA-MBD.corp.ad.wrs.com> References: <72AD03D27224C74982BE13246D75B397399260EA@SHSMSX103.ccr.corp.intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0E5AA4@ALA-MBD.corp.ad.wrs.com> Message-ID: <233d9f7d-e660-efbc-5f1a-11e17c916325@windriver.com> Agreed.  We need the code restructuring and a working build before starting this task. Scott On 18-07-24 07:22 AM, Rowsell, Brent wrote: > > The priority of this needs to be discussed at the next architecture > meeting. > > With all  current churn and lack of a working build, this activity in > my opinion needs to wait. > > Brent > > *From:* Chen, Yan [mailto:yan.chen at intel.com] > *Sent:* Tuesday, July 24, 2018 12:38 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Python 2to3 code porting > > Hi, there, > > I just wonder if anyone is already working on this task now? > > I created a story days ago, and studied most of our Python code and > the python rpms in the system. > > Here’s the conclusions: > > 1.Most of the Tis dependency python packages are already Python 2/3 > compatible, but still some exceptions: > > a.The following packages are Python2 only and same for the latest code > tree: > > i.createrepo-0.9.9 (used by cgcs-patch-controller) > > ii.net-snmp-5.7.2 (used by snmp-audittrail) > > iii.pyparted-3.9 (used by sysinv) > > b.The following packages are Python 2 but the latest version has > Python 3 support, need upgrade: > > i.python-daemon-1.6 (used by logmgmt) > >              * This analysis is still on-going, more packages may be > found. > > 2.The Python modules for Python 2/3 compatibility (python-futures and > python-six) are already included. > > 3.Some of the openstack packages/dependencies are Python 2 only, we > may need to find a good version of Openstack to upgrade. > > We can start to clean our code first, I think we follow the guideline > here, one topic each time, how do you think? > > http://python-future.org/compatible_idioms.html > > Here’s the link for the story: > > https://storyboard.openstack.org/#!/story/2002909 > > > Yan > > > > _______________________________________________ > 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 Jul 24 14:30:25 2018 From: scott.little at windriver.com (Scott Little) Date: Tue, 24 Jul 2018 10:30:25 -0400 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: <93814834B4855241994F290E959305C752F514DA@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F50B3A@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F511D2@SHSMSX104.ccr.corp.intel.com> <32D1079A-B94E-429B-B1B8-D917E1414699@intel.com> <93814834B4855241994F290E959305C752F514DA@SHSMSX104.ccr.corp.intel.com> Message-ID: Yes, these are required. Scott On 18-07-24 05:08 AM, Liu, ZhipengS wrote: > After I downloaded below 3 rpms, build-iso pass. > policycoreutils-2.5-22.el7.x86_64.rpm > policycoreutils-newrole-2.5-22.el7.x86_64.rpm > policycoreutils-python-2.5-22.el7.x86_64.rpm From erich.cordoba.malibran at intel.com Tue Jul 24 16:11:30 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 24 Jul 2018 16:11:30 +0000 Subject: [Starlingx-discuss] Understanding package building order Message-ID: <824C370FAA1437418C1DC20641E2FC2C43DE2AFC@fmsmsx104.amr.corp.intel.com> Hi all, I'm trying to understand how the build system decides what to build on specific scenarios. Let's say we have a complete build and then we run: $ build-pkgs bash This will rebuild the bash package, but also the build system decides to delete and rebuild a set of packages that I don't understand why are being rebuild, for example: iptables-1.4.21-18.0.1.el7.tis.3.x86_64.rpm kernel-3.10.0-862.6.3.el7.35.tis.x86_64.rpm qemu-kvm-common-ev-2.10.0-0.tis.0.x86_64.rpm sm-common-libs-1.0.0-19.tis.x86_64.rpm and a big list of packages. So, the main question here is why the build system decides to rebuild a kernel (taking an example) in order to rebuild bash. Thank you, -Erich From ada.cabrales at intel.com Tue Jul 24 16:14:20 2018 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 24 Jul 2018 16:14:20 +0000 Subject: [Starlingx-discuss] Milestone 2018.07.0 is available. In-Reply-To: <9A85D2917C58154C960D95352B22818BAB56673A@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB5653D8@fmsmsx117.amr.corp.intel.com> <22CBF5E7-BDA5-4223-A413-3BDE86C1EFD5@intel.com> <9A85D2917C58154C960D95352B22818BAB56673A@fmsmsx117.amr.corp.intel.com> Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E716BA459@fmsmsx104.amr.corp.intel.com> Working on it > -----Original Message----- > From: Jones, Bruce E > Sent: Monday, July 23, 2018 6:53 PM > To: Dean Troyer ; Martinez Landa, Hayde > ; Cabrales, Ada > Cc: Arce Moreno, Abraham ; starlingx- > discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] Milestone 2018.07.0 is available. > > Awesome! Ada please have tests run against this build and report the results, > thanks! > > brucej > > -----Original Message----- > From: Dean Troyer [mailto:dtroyer at gmail.com] > Sent: Monday, July 23, 2018 3:54 PM > To: Martinez Landa, Hayde > Cc: Arce Moreno, Abraham ; Jones, Bruce E > ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Milestone 2018.07.0 is available. > > On Mon, Jul 23, 2018 at 5:35 PM, Martinez Landa, Hayde > wrote: > > I have successfully built an .iso on branch M/2018.07 and I have > > submitted a patch that applies for both, master [0] and branch M/2018.07 [1] > that solves the package dependency issues. > > \o/ > > The patches look good, we'll merge the one for master first, and make any > adjustments needed before merging the backport (I don't expect any in this > case). > > We should get some reviews on https://review.openstack.org/#/c/584348/ > to merge the m/2018.07 manifest... > > dt > > -- > > Dean Troyer > dtroyer at gmail.com From hayde.martinez.landa at intel.com Tue Jul 24 16:31:33 2018 From: hayde.martinez.landa at intel.com (Martinez Landa, Hayde) Date: Tue, 24 Jul 2018 16:31:33 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F50B3A@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F511D2@SHSMSX104.ccr.corp.intel.com> <32D1079A-B94E-429B-B1B8-D917E1414699@intel.com> <93814834B4855241994F290E959305C752F514DA@SHSMSX104.ccr.corp.intel.com> Message-ID: <436CE402-6467-4B5C-870D-A7654823D32F@intel.com> Thanks Zhipeng for noticing. > Yes, these are required. > Scott >> After I downloaded below 3 rpms, build-iso pass. >> policycoreutils-2.5-22.el7.x86_64.rpm >> policycoreutils-newrole-2.5-22.el7.x86_64.rpm >> policycoreutils-python-2.5-22.el7.x86_64.rpm I have submitted a new patch [0] that already requires these rpms. [0] https://review.openstack.org/#/c/585465/ From eddie.ramirez at intel.com Tue Jul 24 16:51:10 2018 From: eddie.ramirez at intel.com (Ramirez, Eddie) Date: Tue, 24 Jul 2018 16:51:10 +0000 Subject: [Starlingx-discuss] Python 2to3 code porting In-Reply-To: <233d9f7d-e660-efbc-5f1a-11e17c916325@windriver.com> References: <72AD03D27224C74982BE13246D75B397399260EA@SHSMSX103.ccr.corp.intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0E5AA4@ALA-MBD.corp.ad.wrs.com> <233d9f7d-e660-efbc-5f1a-11e17c916325@windriver.com> Message-ID: <75202A5D-E336-47DB-B1BA-72119BEEBB87@intel.com> +1 We would need to add cgtsclient to the list. I will confirm with other TiS packages today as Horizon uses packages like: cgtsclient, cgcs_patch, sysinv, tsconfig and mfclient… From: Scott Little Date: Tuesday, July 24, 2018 at 7:23 AM To: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Python 2to3 code porting Agreed. We need the code restructuring and a working build before starting this task. Scott On 18-07-24 07:22 AM, Rowsell, Brent wrote: The priority of this needs to be discussed at the next architecture meeting. With all current churn and lack of a working build, this activity in my opinion needs to wait. Brent From: Chen, Yan [mailto:yan.chen at intel.com] Sent: Tuesday, July 24, 2018 12:38 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Python 2to3 code porting Hi, there, I just wonder if anyone is already working on this task now? I created a story days ago, and studied most of our Python code and the python rpms in the system. Here’s the conclusions: 1. Most of the Tis dependency python packages are already Python 2/3 compatible, but still some exceptions: * The following packages are Python2 only and same for the latest code tree: i. createrepo-0.9.9 (used by cgcs-patch-controller) ii. net-snmp-5.7.2 (used by snmp-audittrail) iii. pyparted-3.9 (used by sysinv) * The following packages are Python 2 but the latest version has Python 3 support, need upgrade: i. python-daemon-1.6 (used by logmgmt) * This analysis is still on-going, more packages may be found. 1. The Python modules for Python 2/3 compatibility (python-futures and python-six) are already included. 2. Some of the openstack packages/dependencies are Python 2 only, we may need to find a good version of Openstack to upgrade. We can start to clean our code first, I think we follow the guideline here, one topic each time, how do you think? http://python-future.org/compatible_idioms.html Here’s the link for the story: https://storyboard.openstack.org/#!/story/2002909 Yan _______________________________________________ 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 Jul 24 16:57:29 2018 From: scott.little at windriver.com (Scott Little) Date: Tue, 24 Jul 2018 12:57:29 -0400 Subject: [Starlingx-discuss] Understanding package building order In-Reply-To: <824C370FAA1437418C1DC20641E2FC2C43DE2AFC@fmsmsx104.amr.corp.intel.com> References: <824C370FAA1437418C1DC20641E2FC2C43DE2AFC@fmsmsx104.amr.corp.intel.com> Message-ID: <4764129e-f74d-6845-f9f5-d30bcbb26304@windriver.com> The default behaviour when building pkg A, is to also build anything in the BuildRequires of pkg A, and the requires of those packages, transitively until it has a full set.  It then adds packages that have a direct BuildRequires on A. We do this to protect compiles in languages like C/C++ where a include file change in one package can have major impacts on the compile of other packages that uses the .h Paranoia by default e.g.  A BuildRequires B and C, and C requires D, and E and F requires A E F \ /  A / \ B C   |   D so the build set is: D B C A E F.  This would also be the default build order for this simple case A, E and F as cleaned to force a rebuild. D, B and C are only built it not already built. The unfortunate part is that RPM BuildRequires doesn't distinguish a source code requirement from a tool requirement.  So some packages could probably be excluded.  An advisory in build_srpm.data to ignore some dependencies is a future enhancement I've been pondering.  Another possibility is to only follow dependencies with -dev in the name.... not sure if that is 100% correct though. BuildRequires/Requires are also littered with dependency loops. This can play havoc with trying to find an optimal build order. Some times it's a case of try to build something, and if it fails, try something else and circle back with a second or third iteration if at least one package built ok.   There were a dependency cache files in cgts-tis-repo that helped find good build orders, but StarlingX dropped that content last time I looked.  Without it, I expect the iteration counts to get quite large, wasting a lot of time. One of nastiest dependency loops includes bash and the linux kernel. To exclude E and F from our hypothetical build ...    build-pkgs --no-descendants  A To exclude B C D from our hypothetical build ...    build-pkgs  --no-required  A Finally we always add 'build-info' to the build list, and it may have descendants.  To suppress this ...    build-pkgs --no-build-info A Put it all together, for a fast build of A when dependencies are not a concern ... (e.g. resolving build issues internal to pkg A) ...    build-pkgs --no-descendants --no-required --no-build-info A On 18-07-24 12:11 PM, Cordoba Malibran, Erich wrote: > Hi all, > > I'm trying to understand how the build system decides what to build on > specific scenarios. Let's say we have a complete build and then we run: > > $ build-pkgs bash > > This will rebuild the bash package, but also the build system decides to > delete and rebuild a set of packages that I don't understand why are > being rebuild, for example: > > iptables-1.4.21-18.0.1.el7.tis.3.x86_64.rpm > kernel-3.10.0-862.6.3.el7.35.tis.x86_64.rpm > qemu-kvm-common-ev-2.10.0-0.tis.0.x86_64.rpm > sm-common-libs-1.0.0-19.tis.x86_64.rpm > > and a big list of packages. So, the main question here is why the build system > decides to rebuild a kernel (taking an example) in order to rebuild bash. > > Thank you, > > -Erich > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From eddie.ramirez at intel.com Tue Jul 24 17:16:12 2018 From: eddie.ramirez at intel.com (Ramirez, Eddie) Date: Tue, 24 Jul 2018 17:16:12 +0000 Subject: [Starlingx-discuss] Python 2to3 code porting In-Reply-To: <75202A5D-E336-47DB-B1BA-72119BEEBB87@intel.com> References: <72AD03D27224C74982BE13246D75B397399260EA@SHSMSX103.ccr.corp.intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0E5AA4@ALA-MBD.corp.ad.wrs.com> <233d9f7d-e660-efbc-5f1a-11e17c916325@windriver.com> <75202A5D-E336-47DB-B1BA-72119BEEBB87@intel.com> Message-ID: <8B9B7BE5-D938-46E6-B0CB-5B410B762F5A@intel.com> Yan, I created this list https://etherpad.openstack.org/p/stx-python-2-to-3, I hope it can help us to track those packages as we make more discoveries. From: "Ramirez, Eddie" Date: Tuesday, July 24, 2018 at 9:52 AM To: Scott Little , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Python 2to3 code porting +1 We would need to add cgtsclient to the list. I will confirm with other TiS packages today as Horizon uses packages like: cgtsclient, cgcs_patch, sysinv, tsconfig and mfclient… From: Scott Little Date: Tuesday, July 24, 2018 at 7:23 AM To: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Python 2to3 code porting Agreed. We need the code restructuring and a working build before starting this task. Scott On 18-07-24 07:22 AM, Rowsell, Brent wrote: The priority of this needs to be discussed at the next architecture meeting. With all current churn and lack of a working build, this activity in my opinion needs to wait. Brent From: Chen, Yan [mailto:yan.chen at intel.com] Sent: Tuesday, July 24, 2018 12:38 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Python 2to3 code porting Hi, there, I just wonder if anyone is already working on this task now? I created a story days ago, and studied most of our Python code and the python rpms in the system. Here’s the conclusions: 1. Most of the Tis dependency python packages are already Python 2/3 compatible, but still some exceptions: * The following packages are Python2 only and same for the latest code tree: i. createrepo-0.9.9 (used by cgcs-patch-controller) ii. net-snmp-5.7.2 (used by snmp-audittrail) iii. pyparted-3.9 (used by sysinv) * The following packages are Python 2 but the latest version has Python 3 support, need upgrade: i. python-daemon-1.6 (used by logmgmt) * This analysis is still on-going, more packages may be found. 1. The Python modules for Python 2/3 compatibility (python-futures and python-six) are already included. 2. Some of the openstack packages/dependencies are Python 2 only, we may need to find a good version of Openstack to upgrade. We can start to clean our code first, I think we follow the guideline here, one topic each time, how do you think? http://python-future.org/compatible_idioms.html Here’s the link for the story: https://storyboard.openstack.org/#!/story/2002909 Yan _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Jul 24 22:31:57 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 24 Jul 2018 22:31:57 +0000 Subject: [Starlingx-discuss] Python 2to3 code porting In-Reply-To: <8B9B7BE5-D938-46E6-B0CB-5B410B762F5A@intel.com> References: <72AD03D27224C74982BE13246D75B397399260EA@SHSMSX103.ccr.corp.intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB0E5AA4@ALA-MBD.corp.ad.wrs.com> <233d9f7d-e660-efbc-5f1a-11e17c916325@windriver.com> <75202A5D-E336-47DB-B1BA-72119BEEBB87@intel.com> <8B9B7BE5-D938-46E6-B0CB-5B410B762F5A@intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB5670B4@fmsmsx117.amr.corp.intel.com> Thanks for getting started on this. I’m setting up formal sub-projects and giving each its own wiki page. I’ve started one for this sub-project: https://wiki.openstack.org/wiki/StarlingX/Pyton2. It links to the Etherpad below. Eddie and Yan – can you please update that wiki page so it captures the info in this email thread? And meanwhile, while we thank you both for looking at this, this is not the highest priority work right now, and there are some very big work items hiding under the covers of this one. Please focus on tasks higher on the project's priority list. brucej From: Ramirez, Eddie [mailto:eddie.ramirez at intel.com] Sent: Tuesday, July 24, 2018 10:16 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Python 2to3 code porting Yan, I created this list https://etherpad.openstack.org/p/stx-python-2-to-3, I hope it can help us to track those packages as we make more discoveries. From: "Ramirez, Eddie" > Date: Tuesday, July 24, 2018 at 9:52 AM To: Scott Little >, "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] Python 2to3 code porting +1 We would need to add cgtsclient to the list. I will confirm with other TiS packages today as Horizon uses packages like: cgtsclient, cgcs_patch, sysinv, tsconfig and mfclient… From: Scott Little > Date: Tuesday, July 24, 2018 at 7:23 AM To: "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] Python 2to3 code porting Agreed. We need the code restructuring and a working build before starting this task. Scott On 18-07-24 07:22 AM, Rowsell, Brent wrote: The priority of this needs to be discussed at the next architecture meeting. With all current churn and lack of a working build, this activity in my opinion needs to wait. Brent From: Chen, Yan [mailto:yan.chen at intel.com] Sent: Tuesday, July 24, 2018 12:38 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Python 2to3 code porting Hi, there, I just wonder if anyone is already working on this task now? I created a story days ago, and studied most of our Python code and the python rpms in the system. Here’s the conclusions: 1. Most of the Tis dependency python packages are already Python 2/3 compatible, but still some exceptions: * The following packages are Python2 only and same for the latest code tree: i. createrepo-0.9.9 (used by cgcs-patch-controller) ii. net-snmp-5.7.2 (used by snmp-audittrail) iii. pyparted-3.9 (used by sysinv) * The following packages are Python 2 but the latest version has Python 3 support, need upgrade: i. python-daemon-1.6 (used by logmgmt) * This analysis is still on-going, more packages may be found. 1. The Python modules for Python 2/3 compatibility (python-futures and python-six) are already included. 2. Some of the openstack packages/dependencies are Python 2 only, we may need to find a good version of Openstack to upgrade. We can start to clean our code first, I think we follow the guideline here, one topic each time, how do you think? http://python-future.org/compatible_idioms.html Here’s the link for the story: https://storyboard.openstack.org/#!/story/2002909 Yan _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Jul 24 22:55:58 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 24 Jul 2018 22:55:58 +0000 Subject: [Starlingx-discuss] Understanding package building order In-Reply-To: <4764129e-f74d-6845-f9f5-d30bcbb26304@windriver.com> References: <824C370FAA1437418C1DC20641E2FC2C43DE2AFC@fmsmsx104.amr.corp.intel.com> <4764129e-f74d-6845-f9f5-d30bcbb26304@windriver.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB5670F7@fmsmsx117.amr.corp.intel.com> Scott, thank you, this is super helpful. Is this covered in any of the StarlingX documents out on the wiki? If not, can someone add it please? brucej -----Original Message----- From: Scott Little [mailto:scott.little at windriver.com] Sent: Tuesday, July 24, 2018 9:57 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Understanding package building order The default behaviour when building pkg A, is to also build anything in the BuildRequires of pkg A, and the requires of those packages, transitively until it has a full set.  It then adds packages that have a direct BuildRequires on A. We do this to protect compiles in languages like C/C++ where a include file change in one package can have major impacts on the compile of other packages that uses the .h Paranoia by default e.g.  A BuildRequires B and C, and C requires D, and E and F requires A E F \ /  A / \ B C   |   D so the build set is: D B C A E F.  This would also be the default build order for this simple case A, E and F as cleaned to force a rebuild. D, B and C are only built it not already built. The unfortunate part is that RPM BuildRequires doesn't distinguish a source code requirement from a tool requirement.  So some packages could probably be excluded.  An advisory in build_srpm.data to ignore some dependencies is a future enhancement I've been pondering.  Another possibility is to only follow dependencies with -dev in the name.... not sure if that is 100% correct though. BuildRequires/Requires are also littered with dependency loops. This can play havoc with trying to find an optimal build order. Some times it's a case of try to build something, and if it fails, try something else and circle back with a second or third iteration if at least one package built ok.   There were a dependency cache files in cgts-tis-repo that helped find good build orders, but StarlingX dropped that content last time I looked.  Without it, I expect the iteration counts to get quite large, wasting a lot of time. One of nastiest dependency loops includes bash and the linux kernel. To exclude E and F from our hypothetical build ...    build-pkgs --no-descendants  A To exclude B C D from our hypothetical build ...    build-pkgs  --no-required  A Finally we always add 'build-info' to the build list, and it may have descendants.  To suppress this ...    build-pkgs --no-build-info A Put it all together, for a fast build of A when dependencies are not a concern ... (e.g. resolving build issues internal to pkg A) ...    build-pkgs --no-descendants --no-required --no-build-info A On 18-07-24 12:11 PM, Cordoba Malibran, Erich wrote: > Hi all, > > I'm trying to understand how the build system decides what to build on > specific scenarios. Let's say we have a complete build and then we run: > > $ build-pkgs bash > > This will rebuild the bash package, but also the build system decides to > delete and rebuild a set of packages that I don't understand why are > being rebuild, for example: > > iptables-1.4.21-18.0.1.el7.tis.3.x86_64.rpm > kernel-3.10.0-862.6.3.el7.35.tis.x86_64.rpm > qemu-kvm-common-ev-2.10.0-0.tis.0.x86_64.rpm > sm-common-libs-1.0.0-19.tis.x86_64.rpm > > and a big list of packages. So, the main question here is why the build system > decides to rebuild a kernel (taking an example) in order to rebuild bash. > > Thank you, > > -Erich > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From zhipengs.liu at intel.com Wed Jul 25 01:23:05 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 25 Jul 2018 01:23:05 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F50B3A@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F511D2@SHSMSX104.ccr.corp.intel.com> <32D1079A-B94E-429B-B1B8-D917E1414699@intel.com> <93814834B4855241994F290E959305C752F514DA@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E3330@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F515B7@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C752F51AB3@SHSMSX104.ccr.corp.intel.com> Hi Abraham, Scott, Hayde Thanks for your confirm! I have reviewed the patch, let's make it merged today. The remaining issue is that I saw the same error as before when I deployed it on multinode. Error: Systemd start for connectd failed! @Scott, could you help check it as well? Thanks! Zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月24日 21:53 To: Liu, ZhipengS ; Xie, Cindy ; Cordoba Malibran, Erich ; Miller, Frank ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller > This is the key one, already in my code base Yes Zhipeng, you are correct! Those packages are missing to have the full build. Do you have the patch available? If not we can work on it with CC to you. From zhipengs.liu at intel.com Wed Jul 25 01:51:19 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 25 Jul 2018 01:51:19 +0000 Subject: [Starlingx-discuss] StarlingX: Tar Compressed Files Repository Restructuring In-Reply-To: References: Message-ID: <93814834B4855241994F290E959305C752F51B22@SHSMSX104.ccr.corp.intel.com> Hi Abraham, Just 2 proposals. 1) Every time, when I run download_mirror, it will always download mvn which will take around 1~2 hours. Could you add a check in the script that if mvn.repo.tgz exists, do not try to download it again. Same for other packages. 2) When download list changed, the script only downloads added packages and also removes the ones of old versions that we do not used anymore. Zhipeng -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: 2018年7月24日 7:36 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX: Tar Compressed Files Repository Restructuring The build of StarlingX relies, besides RPM Binaries and Sources, in a collection of packages in the form of Tar Compressed files. Initial review already merged can be found under Gerrit Review "StarlingX: Tar Compressed files repository" [0] We have received several feedback about its content and it is time to gather all of it including security related discussion to restructure the way it is handled, if needed. Please take some time to read, review and send back comments. The complete analysis of these required packages is found at [1]. [ Call Sequence ] The call sequence under CentOS Mirror Tools [2] is as follows ending in executing our tarball-dl.sh: 1 download_mirror.sh 1.1 dl_rpms.sh 1.2 dl_other_from_centos_repo.sh 1.3 tarball-dl.sh Open Questions: - Should we keep this script being called from download_mirror.sh? - Should we keep this file being written as shell script? - Any comment based on midterm / long term changes? - Any other comment? [ List of Packages ] The script tarball-dl.sh [3] takes a text file tarball-dl.lst [4] as argument which contains 3 columns: - Column 1, name of package including extension as it is referenced by the build system. - Column 2, name of the directory path after it is decompressed as it is referenced in the build system. - Column 3, the URL for the package download. Open Questions: - We use "#" to separate columns however in our review we have suggestions to use other characters such as "|" including also change to CSV format, what do you think? - Any other comment? [ List of Packages: Column 1 ] Our build system have references to the name of the file, the file name might include: - name of the package - version - commit id Some examples? - python-cephclient-v0.1.0.5.tar.gz - gnulib-ffc927e.tar.gz - puppet-boolean-22b726dd78b0a60a224cc7054aebbf28e9306f62.tar.gz A special character "!" is used at the beginning of 6 package file names denoting they require special handling is required: additional steps besides the common process including but not limited to remove text from some files, use only one directory, etc: - integrity-kmod-668a8270.tar.gz - mariadb-10.1.28.tar.gz - mvn.repo.tgz - qat1.7.upstream.l.1.0.3-42.tar.gz - tpm-kmod-668a8270.tar.gz - tss2-930.tar.gz Open Questions: - Any specific method to handle these 6 packages? - Any other comment? [ List of Packages: Column 2 ] Our build system uses defined paths after the Tarball package filename is decompressed, see Columns H " 'Directory Name Cgcs-Dl" and Column I " 'Directory Name tarball-dl.sh" for a comparison: - It could be the same after it is decompressed from the original file - dpkg_1.18.24.tar.xz#dpkg-1.18.24 - It could use a different name after it is decompressed from the original file - !integrity-kmod-668a8270.tar.gz#integrity - puppet-dnsmasq-cff07e90890662972c97684a2baee964f68ff3ed.tar.gz#packstack/puppet/modules/dnsmasq/ Open Questions: - Do we want to have predefined paths or should we targeted default paths as given by the original file names? - Any other comment? [ List of Packages: Column 3 ] Nothing specific here but hardcoded URLs. Open Questions: - Use wget Vs curl? - Any other method to get the sources of the packages? Is it possible to migrate to source RPMs? [ Security ] Open Discussion! We went through an initial package integrity verification, see column F "GPG Key" but only 6 packages got their PGP key available in their official repository source. Open Questions: - What is the best way to approach? - Specific question. Can we say Tarballs coming from Git sources are naturally verified? - Any other comment? [0] https://review.openstack.org/#/c/577953/ [1] https://ethercalc.openstack.org/615btsy7i8k6 [2] https://git.openstack.org/cgit/openstack/stx-tools/tree/centos-mirror-tools [3] https://git.openstack.org/cgit/openstack/stx-tools/tree/centos-mirror-tools/tarball-dl.sh [4] https://git.openstack.org/cgit/openstack/stx-tools/tree/centos-mirror-tools/tarball-dl.lst _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From abraham.arce.moreno at intel.com Wed Jul 25 01:54:38 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Wed, 25 Jul 2018 01:54:38 +0000 Subject: [Starlingx-discuss] [RFC] Deployment: StarlingX Installation in a Virtualized Environment Message-ID: Initial objective for this review is to get community feedback: https://review.openstack.org/#/c/585588 A StarlingX system can be installed in a variety of platforms with the following deployment options: - Standard Controller - Dedicated Storage - Controller Storage - All-in-one - Duplex - Simplex Deployment options uses a variety of configurations based on 3 node identities: - Controller - Storage - Compute [ Standard Controller :: Dedicated Storage ] The software installation workflow for an initial Ceph-backed block storage on dedicated storage nodes is: - Controller-0 Installation and Provisioning - Controller-1 / Compute Host / Storage Host Installation - Controller-1 Provisioning - Provider Network Configuration - Compute Host Provisioning - Storage Host Provisioning [ Standard Controller :: Controller Storage ] The software installation workflow for an initial LVM-backed block storage on controller nodes is: - Controller-0 Installation - Controller-0 and System Provisioning - Controller-1 / Compute Host Installation - Controller-1 Provisioning - Compute Host Provisioning [ All-in-one :: Duplex ] The software installation workflow for two combined controller / compute nodes is: - Controller-0 Installation and Provisioning - Controller-1 Installation and Provisioning [ All-in-one :: Simplex ] The software installation workflow for a single combined controller / compute node is: - Controller-0 Installation and Provisioning [ Virtualization Environments ] The available virtualization products where StarlingX has been deployed are: - VirtualBox - Libvirt/QEMU [ Directory Structure ] Deployment directory hosts a total of 3 directories and 18 files: $ tree -L 3 deployment/ deployment/ ├── libvirt │   ├── compute.xml │   ├── controller_allinone.xml │   ├── controller.xml │   ├── destroy_all_in_one.sh │   ├── destroy_standard_controller.sh │   ├── install_packages.sh │   ├── README.rst │   ├── setup_all_in_one.sh │   └── setup_standard_controller.sh ├── provision │   ├── simplex_stage_1.sh │   └── simplex_stage_2.sh └── virtualbox ├── all_in_one.conf ├── README.md ├── serial_vm.sh ├── setup_vm.sh ├── standard_controller.conf ├── start_vm.sh └── stop_vm.sh Directory: libvirt Deployment under Libvirt/QEMU uses a set of xml files to define the node identity: - Controller All-in-one - Controller - Compute These nodes are used to create the virtual machines and the network interfaces to setup the StarlingX system: - Setup All-in-one - Setup Standard Controller Directory: virtualbox Deployment under VirtualBox uses a set of configuration files to define the StarlingX system: - All-in-one Configuration - Standard Controller Configuration These configurations files are used to create the virtual machines and the network interfaces from a single script: - Setup VM Directory: provision A set of scripts are provided to automate the provisioning of data interfaces and local storage resources for the compute function for StarlingX Duplex or Simplex. From abraham.arce.moreno at intel.com Wed Jul 25 02:14:03 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Wed, 25 Jul 2018 02:14:03 +0000 Subject: [Starlingx-discuss] Understanding package building order In-Reply-To: <9A85D2917C58154C960D95352B22818BAB5670F7@fmsmsx117.amr.corp.intel.com> References: <824C370FAA1437418C1DC20641E2FC2C43DE2AFC@fmsmsx104.amr.corp.intel.com> <4764129e-f74d-6845-f9f5-d30bcbb26304@windriver.com> <9A85D2917C58154C960D95352B22818BAB5670F7@fmsmsx117.amr.corp.intel.com> Message-ID: > Scott, thank you, this is super helpful. Pure gold! > Is this covered in any of the StarlingX documents out on the wiki? If not, can > someone add it please? I think we already have the right place for this information, some other shared in the past and in the future, all related to our Build System [0]. Please be patient so we can have a first draft by the end of next week. [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide/Build_System From cindy.xie at intel.com Wed Jul 25 14:51:09 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 25 Jul 2018 14:51:09 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: <93814834B4855241994F290E959305C752F51AB3@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F50B3A@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F511D2@SHSMSX104.ccr.corp.intel.com> <32D1079A-B94E-429B-B1B8-D917E1414699@intel.com> <93814834B4855241994F290E959305C752F514DA@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E3330@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F515B7@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F51AB3@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B2E4221@SHSMSX104.ccr.corp.intel.com> Do we already have a patch regarding: https://storyboard.openstack.org/#!/story/2003070 ? Then please add the patch link there. @ Zhipeng, you can create another task under the same story for the connectd failure you're seeing. Thx. - cindy -----Original Message----- From: Liu, ZhipengS Sent: Wednesday, July 25, 2018 9:23 AM To: Arce Moreno, Abraham ; Xie, Cindy ; Cordoba Malibran, Erich ; Miller, Frank ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Hi Abraham, Scott, Hayde Thanks for your confirm! I have reviewed the patch, let's make it merged today. The remaining issue is that I saw the same error as before when I deployed it on multinode. Error: Systemd start for connectd failed! @Scott, could you help check it as well? Thanks! Zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月24日 21:53 To: Liu, ZhipengS ; Xie, Cindy ; Cordoba Malibran, Erich ; Miller, Frank ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller > This is the key one, already in my code base Yes Zhipeng, you are correct! Those packages are missing to have the full build. Do you have the patch available? If not we can work on it with CC to you. From Ghada.Khalil at windriver.com Wed Jul 25 15:04:47 2018 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 25 Jul 2018 15:04:47 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B2E4221@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F50B3A@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F511D2@SHSMSX104.ccr.corp.intel.com> <32D1079A-B94E-429B-B1B8-D917E1414699@intel.com> <93814834B4855241994F290E959305C752F514DA@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E3330@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F515B7@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F51AB3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E4221@SHSMSX104.ccr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA31BFBD@ALA-MBD.corp.ad.wrs.com> There is Gerrit integration with story board. This was discussed previously on the mailing list, but I am re-sending as a reminder. http://superuser.openstack.org/articles/openstack-gerrit-storyboard-integration/ If the commit message includes the Story and Task IDs, the task will automatically be set to Merged and gerrit will include links to the review in story board. See this story for an example: https://storyboard.openstack.org/#!/story/2003085 I suggest we all use this moving forward for better traceability. Thanks, Ghada -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, July 25, 2018 10:51 AM To: Liu, ZhipengS; Arce Moreno, Abraham; Cordoba Malibran, Erich; Miller, Frank; Hu, Yong; Little, Scott; Qi, Mingyuan; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Do we already have a patch regarding: https://storyboard.openstack.org/#!/story/2003070 ? Then please add the patch link there. @ Zhipeng, you can create another task under the same story for the connectd failure you're seeing. Thx. - cindy -----Original Message----- From: Liu, ZhipengS Sent: Wednesday, July 25, 2018 9:23 AM To: Arce Moreno, Abraham ; Xie, Cindy ; Cordoba Malibran, Erich ; Miller, Frank ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Hi Abraham, Scott, Hayde Thanks for your confirm! I have reviewed the patch, let's make it merged today. The remaining issue is that I saw the same error as before when I deployed it on multinode. Error: Systemd start for connectd failed! @Scott, could you help check it as well? Thanks! Zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月24日 21:53 To: Liu, ZhipengS ; Xie, Cindy ; Cordoba Malibran, Erich ; Miller, Frank ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller > This is the key one, already in my code base Yes Zhipeng, you are correct! Those packages are missing to have the full build. Do you have the patch available? If not we can work on it with CC to you. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Al.Bailey at windriver.com Wed Jul 25 15:25:43 2018 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Wed, 25 Jul 2018 15:25:43 +0000 Subject: [Starlingx-discuss] download_mirrors.sh issues Message-ID: I am following the instructions here: https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Software_Requirements I have been un-successful in running the first setup actions for doing an official build, which is getting my mirror setup. I have all the latest commits in master for stx-tools. The first issue encountered was the macros. This has already been reported here https://storyboard.openstack.org/#!/story/2003072 I only had 4 entries listed as missing, until after I updated these to the following newer versions epel-rpm-macros-7-19.noarch.rpm python2-rpm-macros-3-20.el7.noarch.rpm python-rpm-macros-3-20.el7.noarch.rpm python-srpm-macros-3-20.el7.noarch.rpm I don't know if that is the appropriate solution, since all this allowed me to do was fail to download some other things. Running download_mirror.sh again showed 140+ rpms as missing As an aside, sometimes the "missing" log files are blank, even though not all components were downloaded. I assume this is due to something aborting. Lighttpd for example is never being found. By redirecting the script to log everything to a file, it shows this particular error message which may be a potential culprit "Loaded plugins: fastestmirror, ovl http://epel.blizoo.mk/epel/7Server/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden Trying other mirror. To address this issue please refer to the below knowledge base article https://access.redhat.com/solutions/69319 If above article doesn't help to resolve this issue please create a bug on https://bugs.centos.org/ One of the configured repositories failed (Starlingx-epel.blizoo.mk_epel_7Server_x86_64 - epel.blizoo.mk_epel_7Server_x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail." Does anyone know anything about this blizoo repo? Is it causing anyone else to not be able to download all the rpms, or is it unrelated to the build setup issues? Al -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cordoba.malibran at intel.com Wed Jul 25 16:48:07 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Wed, 25 Jul 2018 16:48:07 +0000 Subject: [Starlingx-discuss] Understanding package building order In-Reply-To: <4764129e-f74d-6845-f9f5-d30bcbb26304@windriver.com> References: <824C370FAA1437418C1DC20641E2FC2C43DE2AFC@fmsmsx104.amr.corp.intel.com> <4764129e-f74d-6845-f9f5-d30bcbb26304@windriver.com> Message-ID: <49692e16390cc646ae1890775303758294409caf.camel@intel.com> Thanks Scott! This was a really good explanation :) > The default behaviour when building pkg A, is to also build anything > in > the BuildRequires of pkg A, and the requires of those packages, > transitively until it has a full set. It then adds packages that > have a > direct BuildRequires on A. > > We do this to protect compiles in languages like C/C++ where a > include > file change in one package can have major impacts on the compile of > other packages that uses the .h > > Paranoia by default > > e.g. > > A BuildRequires B and C, and C requires D, and E and F requires A > > E F > \ / > A > / \ > B C > | > D > > > so the build set is: D B C A E F. This would also be the default > build > order for this simple case > A, E and F as cleaned to force a rebuild. > D, B and C are only built it not already built. > > The unfortunate part is that RPM BuildRequires doesn't distinguish a > source code requirement from a tool requirement. So some packages > could > probably be excluded. An advisory in build_srpm.data to ignore some > dependencies is a future enhancement I've been pondering. Another > possibility is to only follow dependencies with -dev in the name.... > not > sure if that is 100% correct though. > > BuildRequires/Requires are also littered with dependency loops. This > can > play havoc with trying to find an optimal build order. Some times > it's a > case of try to build something, and if it fails, try something else > and > circle back with a second or third iteration if at least one package > built ok. There were a dependency cache files in cgts-tis-repo > that > helped find good build orders, but StarlingX dropped that content > last > time I looked. Without it, I expect the iteration counts to get > quite > large, wasting a lot of time. > > One of nastiest dependency loops includes bash and the linux kernel. > > To exclude E and F from our hypothetical build ... > build-pkgs --no-descendants A > > To exclude B C D from our hypothetical build ... > build-pkgs --no-required A > > Finally we always add 'build-info' to the build list, and it may > have > descendants. To suppress this ... > build-pkgs --no-build-info A > > Put it all together, for a fast build of A when dependencies are not > a > concern ... (e.g. resolving build issues internal to pkg A) ... > build-pkgs --no-descendants --no-required --no-build-info A > > > > On 18-07-24 12:11 PM, Cordoba Malibran, Erich wrote: > > Hi all, > > > > I'm trying to understand how the build system decides what to build > > on > > specific scenarios. Let's say we have a complete build and then we > > run: > > > > $ build-pkgs bash > > > > This will rebuild the bash package, but also the build system > > decides to > > delete and rebuild a set of packages that I don't understand why > > are > > being rebuild, for example: > > > > iptables-1.4.21-18.0.1.el7.tis.3.x86_64.rpm > > kernel-3.10.0-862.6.3.el7.35.tis.x86_64.rpm > > qemu-kvm-common-ev-2.10.0-0.tis.0.x86_64.rpm > > sm-common-libs-1.0.0-19.tis.x86_64.rpm > > > > and a big list of packages. So, the main question here is why the > > build system > > decides to rebuild a kernel (taking an example) in order to rebuild > > bash. > > > > Thank you, > > > > -Erich > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Al.Bailey at windriver.com Wed Jul 25 18:16:07 2018 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Wed, 25 Jul 2018 18:16:07 +0000 Subject: [Starlingx-discuss] download_mirrors.sh issues Message-ID: I don't know if this is the proper solution, but I was able to google around and find the centos repo where some of those missing rpms are located. http://vault.centos.org/centos/7.3.1611/cr/x86_64/ If I add this entry to StarlingX.repo [Starlingx-C7.3.1611-cr] name=Starlingx-CentOS-7.3.1611 - cr baseurl=http://vault.centos.org/centos/7.3.1611/cr/x86_64 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7 enabled=1 and re-copy that to /etc/yum.repos.d/ then the download stage no longer complains about some of the missing entries like python-2.7.5-58 etc.. I will re-run the complete download routine and see if this fixes all the remaining (non src) issues. Al From: Bailey, Henry Albert (Al) Sent: Wednesday, July 25, 2018 11:26 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: download_mirrors.sh issues I am following the instructions here: https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Software_Requirements I have been un-successful in running the first setup actions for doing an official build, which is getting my mirror setup. I have all the latest commits in master for stx-tools. The first issue encountered was the macros. This has already been reported here https://storyboard.openstack.org/#!/story/2003072 I only had 4 entries listed as missing, until after I updated these to the following newer versions epel-rpm-macros-7-19.noarch.rpm python2-rpm-macros-3-20.el7.noarch.rpm python-rpm-macros-3-20.el7.noarch.rpm python-srpm-macros-3-20.el7.noarch.rpm I don't know if that is the appropriate solution, since all this allowed me to do was fail to download some other things. Running download_mirror.sh again showed 140+ rpms as missing As an aside, sometimes the "missing" log files are blank, even though not all components were downloaded. I assume this is due to something aborting. Lighttpd for example is never being found. By redirecting the script to log everything to a file, it shows this particular error message which may be a potential culprit "Loaded plugins: fastestmirror, ovl http://epel.blizoo.mk/epel/7Server/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden Trying other mirror. To address this issue please refer to the below knowledge base article https://access.redhat.com/solutions/69319 If above article doesn't help to resolve this issue please create a bug on https://bugs.centos.org/ One of the configured repositories failed (Starlingx-epel.blizoo.mk_epel_7Server_x86_64 - epel.blizoo.mk_epel_7Server_x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail." Does anyone know anything about this blizoo repo? Is it causing anyone else to not be able to download all the rpms, or is it unrelated to the build setup issues? Al -------------- next part -------------- An HTML attachment was scrubbed... URL: From abraham.arce.moreno at intel.com Wed Jul 25 18:32:50 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Wed, 25 Jul 2018 18:32:50 +0000 Subject: [Starlingx-discuss] download_mirrors.sh issues In-Reply-To: References: Message-ID: > I am following the instructions here: > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Software_Requir > ements Thanks Al! A request for everybody, please continuously refresh the webpage due to the daily changes. The word "Temporal!" is used across this guide to highlight those patches needed to have a successful build. For branch Master, we are identifying those patches not merged as: Temporal! Only Branch Master For branch m/2018.07, we are identifying those patches not merged as: Temporal! Only Branch m/2018.07 > I have been un-successful in running the first setup actions for doing an > official build, which is getting my mirror setup. > > I have all the latest commits in master for stx-tools. Our commit ids for today's build are: stx-tools branch master $ git log --pretty=oneline -2 f31f99ab91435c32c24a86efd2e697177074f4b7 Merge "policycoreutils-newrole was missing" c3000c2936f56ad0257142d5c5bad3afc08c46cc Merge "upgrade linux-firmware RPM version"``` stx-tools branch m/2018.07 $ git log --pretty=oneline -5 88aadc543085e24e3c5df10ec63996b9f5551ff6 Merge "Package updates for new version of selinux-policy" into m/2018.07 9c44470a2d6ff86a40f42c2b608e723c355ae38f Merge "Copy mock.cfg.proto and comps.xml files into cgcs-centos-repo" into m/2018.07``` > The first issue encountered was the macros. This has already been reported > here > https://storyboard.openstack.org/#!/story/2003072 > > I only had 4 entries listed as missing, until after I updated these to the > following newer versions > > epel-rpm-macros-7-19.noarch.rpm > python2-rpm-macros-3-20.el7.noarch.rpm > python-rpm-macros-3-20.el7.noarch.rpm > python-srpm-macros-3-20.el7.noarch.rpm Also in this setup... > I don't know if that is the appropriate solution, since all this allowed me to do > was fail to download some other things. We have 2 options: 1. a manual download of the packages 2. use of a tool, in review status [0] > Running download_mirror.sh again showed 140+ rpms as missing > > As an aside, sometimes the "missing" log files are blank, even though not all > components were downloaded. I assume this is due to something aborting. > Lighttpd for example is never being found. Same here: Delta RPMs disabled because /usr/bin/applydeltarpm not installed. warning: /var/cache/yum/x86_64/7/epel/packages/lighttpd-1.4.49-1.el7.x86_64.rpm: \ Header V3 RSA/SHA256 Signature, key ID 352c64e5: NOKEY Public key for lighttpd-1.4.49-1.el7.x86_64.rpm is not installed > By redirecting the script to log everything to a file, it shows this particular > error message which may be a potential culprit > > "Loaded plugins: fastestmirror, ovl > http://epel.blizoo.mk/epel/7Server/x86_64/repodata/repomd.xml: [Errno 14] > HTTP Error 403 - Forbidden > Trying other mirror. > To address this issue please refer to the below knowledge base article > https://access.redhat.com/solutions/69319 > If above article doesn't help to resolve this issue please create a bug on > https://bugs.centos.org/ > One of the configured repositories failed (Starlingx- > epel.blizoo.mk_epel_7Server_x86_64 - > epel.blizoo.mk_epel_7Server_x86_64), > and yum doesn't have enough cached data to continue. At this point the only > safe thing yum can do is fail." > > Does anyone know anything about this blizoo repo? Is it causing anyone else > to not be able to download all the rpms, or is it unrelated to the build setup > issues? Not seeing the blizoo repo failure in our side... internet connection is slow so will come back to you with more updates some time later. [0] https://review.openstack.org/#/c/585009/ From abraham.arce.moreno at intel.com Wed Jul 25 18:44:44 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Wed, 25 Jul 2018 18:44:44 +0000 Subject: [Starlingx-discuss] download_mirrors.sh issues In-Reply-To: References: Message-ID: > I don't know if this is the proper solution, but I was able to google around > and find the centos repo where some of those missing rpms are located. Thanks Al! I will leave this to our rpm experts... > http://vault.centos.org/centos/7.3.1611/cr/x86_64/ > > If I add this entry to StarlingX.repo > > [Starlingx-C7.3.1611-cr] > name=Starlingx-CentOS-7.3.1611 - cr > baseurl=http://vault.centos.org/centos/7.3.1611/cr/x86_64 > gpgcheck=1 > gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7 > enabled=1 > > and re-copy that to /etc/yum.repos.d/ > > then the download stage no longer complains about some of the missing > entries like python-2.7.5-58 etc.. > > I will re-run the complete download routine and see if this fixes all the > remaining (non src) issues. Is it possible you submit a patch if it works for you? Adopting the over communication approach, I am logging all the steps and output in this url [0]. Not using etherpad to have a faster edit / easy formatting. [0] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md From scott.little at windriver.com Wed Jul 25 19:33:59 2018 From: scott.little at windriver.com (Scott Little) Date: Wed, 25 Jul 2018 15:33:59 -0400 Subject: [Starlingx-discuss] download_mirrors.sh issues In-Reply-To: References: Message-ID: <886c47cc-855b-4ceb-4649-0f8e02b8b571@windriver.com> The http://epel.blizoo.mk/epel/ site is blocked by the security gateway internal to Windriver.  Reason is 'potentially unwanted programs'.  Is there an alternative to this site? What packages are being supplied by this site? Scott On 18-07-25 02:32 PM, Arce Moreno, Abraham wrote: >> I am following the instructions here: >> >> https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Software_Requir >> ements > Thanks Al! > > A request for everybody, please continuously refresh the webpage due to the > daily changes. The word "Temporal!" is used across this guide to highlight those patches > needed to have a successful build. > > For branch Master, we are identifying those patches not merged as: > Temporal! Only Branch Master > > For branch m/2018.07, we are identifying those patches not merged as: > Temporal! Only Branch m/2018.07 > >> I have been un-successful in running the first setup actions for doing an >> official build, which is getting my mirror setup. >> >> I have all the latest commits in master for stx-tools. > Our commit ids for today's build are: > > stx-tools branch master > > $ git log --pretty=oneline -2 > f31f99ab91435c32c24a86efd2e697177074f4b7 Merge "policycoreutils-newrole was missing" > c3000c2936f56ad0257142d5c5bad3afc08c46cc Merge "upgrade linux-firmware RPM version"``` > > stx-tools branch m/2018.07 > > $ git log --pretty=oneline -5 > 88aadc543085e24e3c5df10ec63996b9f5551ff6 Merge "Package updates for new version of selinux-policy" into m/2018.07 > 9c44470a2d6ff86a40f42c2b608e723c355ae38f Merge "Copy mock.cfg.proto and comps.xml files into cgcs-centos-repo" into m/2018.07``` > >> The first issue encountered was the macros. This has already been reported >> here >> https://storyboard.openstack.org/#!/story/2003072 >> >> I only had 4 entries listed as missing, until after I updated these to the >> following newer versions >> >> epel-rpm-macros-7-19.noarch.rpm >> python2-rpm-macros-3-20.el7.noarch.rpm >> python-rpm-macros-3-20.el7.noarch.rpm >> python-srpm-macros-3-20.el7.noarch.rpm > Also in this setup... > >> I don't know if that is the appropriate solution, since all this allowed me to do >> was fail to download some other things. > We have 2 options: > > 1. a manual download of the packages > 2. use of a tool, in review status [0] > >> Running download_mirror.sh again showed 140+ rpms as missing >> >> As an aside, sometimes the "missing" log files are blank, even though not all >> components were downloaded. I assume this is due to something aborting. > >> Lighttpd for example is never being found. > Same here: > > Delta RPMs disabled because /usr/bin/applydeltarpm not installed. > warning: /var/cache/yum/x86_64/7/epel/packages/lighttpd-1.4.49-1.el7.x86_64.rpm: \ > Header V3 RSA/SHA256 Signature, key ID 352c64e5: NOKEY > Public key for lighttpd-1.4.49-1.el7.x86_64.rpm is not installed > >> By redirecting the script to log everything to a file, it shows this particular >> error message which may be a potential culprit >> >> "Loaded plugins: fastestmirror, ovl >> http://epel.blizoo.mk/epel/7Server/x86_64/repodata/repomd.xml: [Errno 14] >> HTTP Error 403 - Forbidden >> Trying other mirror. >> To address this issue please refer to the below knowledge base article >> https://access.redhat.com/solutions/69319 >> If above article doesn't help to resolve this issue please create a bug on >> https://bugs.centos.org/ >> One of the configured repositories failed (Starlingx- >> epel.blizoo.mk_epel_7Server_x86_64 - >> epel.blizoo.mk_epel_7Server_x86_64), >> and yum doesn't have enough cached data to continue. At this point the only >> safe thing yum can do is fail." >> >> Does anyone know anything about this blizoo repo? Is it causing anyone else >> to not be able to download all the rpms, or is it unrelated to the build setup >> issues? > Not seeing the blizoo repo failure in our side... internet connection is slow so will come back to > you with more updates some time later. > > [0] https://review.openstack.org/#/c/585009/ > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Wed Jul 25 19:40:58 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Wed, 25 Jul 2018 19:40:58 +0000 Subject: [Starlingx-discuss] Script to check mirror health Message-ID: Hi all, I create a script to help with the mirror monitoring. Currently we need to download the entire mirror to know if something has failed, in particular if a package has been updated in the CentOS repositories. However, it is possible to know if something has changed using the yum cache, in specific the primary_db files with all the package information. So, this script iterates over all the content of the 'rpms_from_centos_repos.lst' and uses repoquery to retrieve the information of that specific package and version. If results are not found, then it tries to get the information only using the package name. For example, doing : repoquery --qf '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}' epel-rpm-macros-7-18.noarch returns no output, however: repoquery --qf '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}' epel-rpm-macros returns: epel-rpm-macros-7-19.noarch In this case, epel-rpm-macros needs to be upgraded. So, for today's execution, this script shows: ... list of packages... 2018-07-25 19-20-29 ==> INFO: Checking zlib-1.2.7-17.el7.x86_64... OK 2018-07-25 19-20-30 ==> INFO: Checking zlib-devel-1.2.7-7.el7.x86_64... OK 2018-07-25 19-20-30 ==> INFO: Checking zziplib-0.13.62-5.el7.x86_64... OK 2018-07-25 19-20-31 ==> ERROR: Failures found, error log: 2018-07-25 19-20-31 ==> ERROR: ========================== Package epel-rpm-macros-7-18.noarch not found, available epel-rpm-macros-7-19.noarch Package python2-rpm-macros-3-18.el7.noarch not found, available python2-rpm-macros-3-21.el7.noarch Package python-rpm-macros-3-18.el7.noarch not found, available python-rpm-macros-3-21.el7.noarch Package python-srpm-macros-3-18.el7.noarch not found, available python-srpm-macros-3-21.el7.noarch I send a review with this script, please let me know any feedback or comments. Review: https://review.openstack.org/#/c/585858/ Thanks -Erich From bruce.e.jones at intel.com Wed Jul 25 19:53:42 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 25 Jul 2018 19:53:42 +0000 Subject: [Starlingx-discuss] Bug scrub! Message-ID: <9A85D2917C58154C960D95352B22818BAB5675C9@fmsmsx117.amr.corp.intel.com> We need to start reviewing and scrubbing bugs. If you've filed a bug, please make sure the issue(s) still reproduce on current builds [0]. If you are assigned a bug, please keep it updated in comments as you work on resolving it. Bugs should be tagged with stx.bug. Most are also tagged with a release tag. You can find our open bugs: * All bugs: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.bug * stx.2018.08 bugs: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.bug&tags=stx.2018.08 * stx.2018.11 bugs:https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.bug&tags=stx.2018.11 Thank you! brucej [0] yes, I know it's hard to get the build to work. Keep trying! -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.friesen at windriver.com Wed Jul 25 20:39:37 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Wed, 25 Jul 2018 14:39:37 -0600 Subject: [Starlingx-discuss] download_mirrors.sh issues In-Reply-To: <886c47cc-855b-4ceb-4649-0f8e02b8b571@windriver.com> References: <886c47cc-855b-4ceb-4649-0f8e02b8b571@windriver.com> Message-ID: <5B58E009.505@windriver.com> On 07/25/2018 01:33 PM, Scott Little wrote: > The http://epel.blizoo.mk/epel/ site is blocked by the security gateway internal > to Windriver. Reason is 'potentially unwanted programs'. Is there an > alternative to this site? > > What packages are being supplied by this site? It looks like it's just EPEL. I think this is equivalent: http://mirror.csclub.uwaterloo.ca/fedora/epel/ Chris From abraham.arce.moreno at intel.com Wed Jul 25 20:59:54 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Wed, 25 Jul 2018 20:59:54 +0000 Subject: [Starlingx-discuss] download_mirrors.sh issues In-Reply-To: References: Message-ID: > > I will re-run the complete download routine and see if this fixes all > > the remaining (non src) issues. > > Is it possible you submit a patch if it works for you? > > Adopting the over communication approach, I am logging all the steps and > output in this url [0]. Not using etherpad to have a faster edit / easy > formatting. > > [0] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md Afternoon update on StarlingX Compilation Master Branch started today morning. stx-tools branch master $ git log --pretty=oneline -2 f31f99ab91435c32c24a86efd2e697177074f4b7 Merge "policycoreutils-newrole was missing" c3000c2936f56ad0257142d5c5bad3afc08c46cc Merge "upgrade linux-firmware RPM version" Taking StarlingX Developer Guide [0] as an input and a temporal Github page [1] as an output. [1] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [0] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md From yong.hu at intel.com Wed Jul 25 23:13:22 2018 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 25 Jul 2018 23:13:22 +0000 Subject: [Starlingx-discuss] download_mirrors.sh issues In-Reply-To: <5B58E009.505@windriver.com> References: <886c47cc-855b-4ceb-4649-0f8e02b8b571@windriver.com> <5B58E009.505@windriver.com> Message-ID: <988AB878-C0E2-4D8B-BBEA-753ED29F2DEA@intel.com> Hi Chris and Scott, These following 4 packages used to be downloaded from this site: http://epel.blizoo.mk/epel/7/SRPMS/l/lighttpd-1.4.45-1.el7.src.rpm http://epel.blizoo.mk/epel/7Server/x86_64/p/python2-msgpack-0.4.8-1.el7.x86_64.rpm http://epel.blizoo.mk/epel/7Server/x86_64/p/python2-pysocks-1.5.7-1.el7.noarch.rpm http://epel.blizoo.mk/epel/7Server/x86_64/p/python-pyngus-2.2.1-1.el7.noarch.rpm regards, Yong On 26/07/2018, 4:40 AM, "Chris Friesen" wrote: On 07/25/2018 01:33 PM, Scott Little wrote: > The http://epel.blizoo.mk/epel/ site is blocked by the security gateway internal > to Windriver. Reason is 'potentially unwanted programs'. Is there an > alternative to this site? > > What packages are being supplied by this site? It looks like it's just EPEL. I think this is equivalent: http://mirror.csclub.uwaterloo.ca/fedora/epel/ Chris _______________________________________________ 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 Wed Jul 25 23:57:10 2018 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 25 Jul 2018 23:57:10 +0000 Subject: [Starlingx-discuss] download_mirrors.sh issues Message-ID: <47AA738A-2AEF-4510-B921-5B0968304F5B@intel.com> Hi AI and Abraham, I think it is okay to add "http://vault.centos.org/centos/7.3.1611/cr/x86_64/" as one of repos for downloading those 4 missing packages. In addition, it is helpful by putting comments there to explain why this old CentOS repo (7.3.1611) is added. Regards, Yong On 26/07/2018, 2:46 AM, "Arce Moreno, Abraham" wrote: > I don't know if this is the proper solution, but I was able to google around > and find the centos repo where some of those missing rpms are located. Thanks Al! I will leave this to our rpm experts... > http://vault.centos.org/centos/7.3.1611/cr/x86_64/ > > If I add this entry to StarlingX.repo > > [Starlingx-C7.3.1611-cr] > name=Starlingx-CentOS-7.3.1611 - cr > baseurl=http://vault.centos.org/centos/7.3.1611/cr/x86_64 > gpgcheck=1 > gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7 > enabled=1 > > and re-copy that to /etc/yum.repos.d/ > > then the download stage no longer complains about some of the missing > entries like python-2.7.5-58 etc.. > > I will re-run the complete download routine and see if this fixes all the > remaining (non src) issues. Is it possible you submit a patch if it works for you? Adopting the over communication approach, I am logging all the steps and output in this url [0]. Not using etherpad to have a faster edit / easy formatting. [0] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From abraham.arce.moreno at intel.com Thu Jul 26 00:36:55 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Thu, 26 Jul 2018 00:36:55 +0000 Subject: [Starlingx-discuss] download_mirrors.sh issues In-Reply-To: References: Message-ID: > Afternoon update on StarlingX Compilation Master Branch started today > morning. Next update: stx-tools branch master $ git log --pretty=oneline -2 f31f99ab91435c32c24a86efd2e697177074f4b7 Merge "policycoreutils-newrole was missing" c3000c2936f56ad0257142d5c5bad3afc08c46cc Merge "upgrade linux-firmware RPM version" Changes: - During build-pkgs: "No Package found for selinux-policy-devel" - Bug / Task created [2] - Review created [3] Taking StarlingX Developer Guide [0] as an input and a temporal Github page [1] as an output. [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md [2] https://storyboard.openstack.org/#!/story/2003102 [3] https://review.openstack.org/#/c/585915/ From yong.hu at intel.com Thu Jul 26 01:36:09 2018 From: yong.hu at intel.com (Hu, Yong) Date: Thu, 26 Jul 2018 01:36:09 +0000 Subject: [Starlingx-discuss] Script to check mirror health Message-ID: <6DA8A8AE-B009-4B76-8275-FDFE5C46419D@intel.com> Hi Erich, This script is helpful, thank you! 2 cents: 1). A tiny comment in the patch that we probably need to distinguish ".noarch" and ".src" inside function "get_repoquery_info"? 2). Whenever StaringX.repo is updated by a new patch, we might need a way to refresh the yum cache. Isn't it? Regards, Yong On 26/07/2018, 3:41 AM, "Cordoba Malibran, Erich" wrote: Hi all, I create a script to help with the mirror monitoring. Currently we need to download the entire mirror to know if something has failed, in particular if a package has been updated in the CentOS repositories. However, it is possible to know if something has changed using the yum cache, in specific the primary_db files with all the package information. So, this script iterates over all the content of the 'rpms_from_centos_repos.lst' and uses repoquery to retrieve the information of that specific package and version. If results are not found, then it tries to get the information only using the package name. For example, doing : repoquery --qf '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}' epel-rpm-macros-7-18.noarch returns no output, however: repoquery --qf '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}' epel-rpm-macros returns: epel-rpm-macros-7-19.noarch In this case, epel-rpm-macros needs to be upgraded. So, for today's execution, this script shows: ... list of packages... 2018-07-25 19-20-29 ==> INFO: Checking zlib-1.2.7-17.el7.x86_64... OK 2018-07-25 19-20-30 ==> INFO: Checking zlib-devel-1.2.7-7.el7.x86_64... OK 2018-07-25 19-20-30 ==> INFO: Checking zziplib-0.13.62-5.el7.x86_64... OK 2018-07-25 19-20-31 ==> ERROR: Failures found, error log: 2018-07-25 19-20-31 ==> ERROR: ========================== Package epel-rpm-macros-7-18.noarch not found, available epel-rpm-macros-7-19.noarch Package python2-rpm-macros-3-18.el7.noarch not found, available python2-rpm-macros-3-21.el7.noarch Package python-rpm-macros-3-18.el7.noarch not found, available python-rpm-macros-3-21.el7.noarch Package python-srpm-macros-3-18.el7.noarch not found, available python-srpm-macros-3-21.el7.noarch I send a review with this script, please let me know any feedback or comments. Review: https://review.openstack.org/#/c/585858/ Thanks -Erich _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From abraham.arce.moreno at intel.com Thu Jul 26 02:13:04 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Thu, 26 Jul 2018 02:13:04 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide Message-ID: Hi again, Can someone please help test the process to build an ISO based on master using Developer Guide [0]? Please use Github page [1] as a documentation support. Requirements: - Repo status checked 7/25/2018 19:12 PST - stx-tools master branch - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros - Temporal! Changes, already in Developer Guide - RPM: selinux-policy-devel required https://review.openstack.org/#/c/585915 [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md From austin.sun at intel.com Thu Jul 26 02:23:46 2018 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 26 Jul 2018 02:23:46 +0000 Subject: [Starlingx-discuss] [Gerrit] Gerrit notifaction to starlingx IRC channel Message-ID: Hi All: According doc of https://docs.openstack.org/infra/manual/drivers.html#gerrit-irc-notifications I have made gerrit : https://review.openstack.org/#/c/585919/ , please help review it. Thanks. BR Austin Sun. From zhipengs.liu at intel.com Thu Jul 26 02:31:42 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 26 Jul 2018 02:31:42 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: References: Message-ID: <93814834B4855241994F290E959305C752F5280F@SHSMSX104.ccr.corp.intel.com> Hi Abraham, I will try it again and update to you later today zhipeng -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: 2018年7月26日 10:13 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide Hi again, Can someone please help test the process to build an ISO based on master using Developer Guide [0]? Please use Github page [1] as a documentation support. Requirements: - Repo status checked 7/25/2018 19:12 PST - stx-tools master branch - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros - Temporal! Changes, already in Developer Guide - RPM: selinux-policy-devel required https://review.openstack.org/#/c/585915 [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ran1.an at intel.com Thu Jul 26 02:52:57 2018 From: ran1.an at intel.com (An, Ran1) Date: Thu, 26 Jul 2018 02:52:57 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: <93814834B4855241994F290E959305C752F5280F@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F5280F@SHSMSX104.ccr.corp.intel.com> Message-ID: <9BAB5B7CAF57C3459E4636391F1071CECA1D32@shsmsx102.ccr.corp.intel.com> Hi Abraham and Zhipeng Hope to join you. And I'll update to you once I make any progress. BG Ran -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, July 26, 2018 10:32 AM To: Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide Hi Abraham, I will try it again and update to you later today zhipeng -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: 2018年7月26日 10:13 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide Hi again, Can someone please help test the process to build an ISO based on master using Developer Guide [0]? Please use Github page [1] as a documentation support. Requirements: - Repo status checked 7/25/2018 19:12 PST - stx-tools master branch - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros - Temporal! Changes, already in Developer Guide - RPM: selinux-policy-devel required https://review.openstack.org/#/c/585915 [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md _______________________________________________ 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 Jul 26 04:10:50 2018 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 25 Jul 2018 21:10:50 -0700 Subject: [Starlingx-discuss] StarlingX: Tar Compressed Files Repository Restructuring In-Reply-To: <93814834B4855241994F290E959305C752F51B22@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F51B22@SHSMSX104.ccr.corp.intel.com> Message-ID: <52dd7eca-a630-71af-ab70-aae4c0e5ad7d@linux.intel.com> On 07/24/2018 06:51 PM, Liu, ZhipengS wrote: > Hi Abraham, > > Just 2 proposals. > 1) Every time, when I run download_mirror, it will always download mvn which will take around 1~2 hours. > Could you add a check in the script that if mvn.repo.tgz exists, do not try to download it again. Same for other package > 2) When download list changed, the script only downloads added packages and also removes the ones of old versions that we do not used anymore. > I was thinking we could try to incorporate somekind of checksum information, in order to validate the downloads are correct and complete. more below > Zhipeng > > -----Original Message----- > From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] > Sent: 2018年7月24日 7:36 > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] StarlingX: Tar Compressed Files Repository Restructuring > > The build of StarlingX relies, besides RPM Binaries and Sources, in a collection of packages in the form of Tar Compressed files. Initial review already merged can be found under Gerrit Review "StarlingX: Tar Compressed files repository" [0] > > We have received several feedback about its content and it is time to gather all of it including security related discussion to restructure the way it is handled, if needed. > Please take some time to read, review and send back comments. > The complete analysis of these required packages is found at [1]. > > [ Call Sequence ] > > The call sequence under CentOS Mirror Tools [2] is as follows ending in executing our tarball-dl.sh: > > 1 download_mirror.sh > 1.1 dl_rpms.sh > 1.2 dl_other_from_centos_repo.sh > 1.3 tarball-dl.sh > > Open Questions: > - Should we keep this script being called from download_mirror.sh? > - Should we keep this file being written as shell script? > - Any comment based on midterm / long term changes? > - Any other comment? > So the script is doing 3 things, I think there should be more checking as to what exists and what's needed. The RPM fetching can be done independant of the tarball, so that we can use a query of the repos instead of full download. Another thought is to provide the option to point this at somekind of company based mirror, so that each larger company could keep an internal mirror, but smaller organizations will hit the external sources. > [ List of Packages ] > > The script tarball-dl.sh [3] takes a text file tarball-dl.lst [4] as argument which contains 3 columns: > > - Column 1, name of package including extension as it is referenced by the build > system. > - Column 2, name of the directory path after it is decompressed as it is referenced > in the build system. > - Column 3, the URL for the package download. > > Open Questions: > - We use "#" to separate columns however in our review we have suggestions to use other > characters such as "|" including also change to CSV format, what do you think? > - Any other comment? > > [ List of Packages: Column 1 ] > > Our build system have references to the name of the file, the file name might include: > - name of the package > - version > - commit id > > Some examples? > - python-cephclient-v0.1.0.5.tar.gz > - gnulib-ffc927e.tar.gz > - puppet-boolean-22b726dd78b0a60a224cc7054aebbf28e9306f62.tar.gz > > A special character "!" is used at the beginning of 6 package file names denoting they require special handling is required: additional steps besides the common process including but not limited to remove text from some files, use only one directory, etc: > > - integrity-kmod-668a8270.tar.gz > - mariadb-10.1.28.tar.gz > - mvn.repo.tgz > - qat1.7.upstream.l.1.0.3-42.tar.gz > - tpm-kmod-668a8270.tar.gz > - tss2-930.tar.gz > > Open Questions: > - Any specific method to handle these 6 packages? > - Any other comment? > This one is harder, since each of these is a different special case to deal with git or multiple downloads (mvn). Short of creating some sort of "plugin" mechanism that handles each special case. > [ List of Packages: Column 2 ] > > Our build system uses defined paths after the Tarball package filename is decompressed, see Columns H " 'Directory Name Cgcs-Dl" and Column I " 'Directory Name tarball-dl.sh" for a > comparison: > > - It could be the same after it is decompressed from the original file > - dpkg_1.18.24.tar.xz#dpkg-1.18.24 > - It could use a different name after it is decompressed from the original file > - !integrity-kmod-668a8270.tar.gz#integrity > - puppet-dnsmasq-cff07e90890662972c97684a2baee964f68ff3ed.tar.gz#packstack/puppet/modules/dnsmasq/ > > Open Questions: > - Do we want to have predefined paths or should we targeted default paths as given by the original file names? > - Any other comment? > I have not looked deeper, but are the predefined paths required for the way build system is currently looking for files? > [ List of Packages: Column 3 ] > > Nothing specific here but hardcoded URLs. > > Open Questions: > - Use wget Vs curl? I would lean towards curl as it has better protocol support and supports socks for proxy activity. > - Any other method to get the sources of the packages? Is it possible to migrate to source RPMs? > > [ Security ] > > Open Discussion! We went through an initial package integrity verification, see column F "GPG Key" but only 6 packages got their PGP key available in their official repository source. > > Open Questions: > - What is the best way to approach? If there is a GPG key, then I think we should verify it, we could also validate that what we currently have does not need to be updated (see above) > - Specific question. Can we say Tarballs coming from Git sources are naturally verified? I think that makes sense, the problem with those tarballs is that we can't have a checksum on them since they are created on the fly and the time stamps change. > - Any other comment? > > [0] https://review.openstack.org/#/c/577953/ > [1] https://ethercalc.openstack.org/615btsy7i8k6 > [2] https://git.openstack.org/cgit/openstack/stx-tools/tree/centos-mirror-tools > [3] https://git.openstack.org/cgit/openstack/stx-tools/tree/centos-mirror-tools/tarball-dl.sh > [4] https://git.openstack.org/cgit/openstack/stx-tools/tree/centos-mirror-tools/tarball-dl.lst > > _______________________________________________ > 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 zhipengs.liu at intel.com Thu Jul 26 08:53:07 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 26 Jul 2018 08:53:07 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: References: Message-ID: <93814834B4855241994F290E959305C752F52B57@SHSMSX104.ccr.corp.intel.com> Hi Abraham and Hayde I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. Start collectd failed. Could you help deploy ISO I built to see if it can work in your environment, thanks! Zhipeng -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: 2018年7月26日 10:13 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide Hi again, Can someone please help test the process to build an ISO based on master using Developer Guide [0]? Please use Github page [1] as a documentation support. Requirements: - Repo status checked 7/25/2018 19:12 PST - stx-tools master branch - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros - Temporal! Changes, already in Developer Guide - RPM: selinux-policy-devel required https://review.openstack.org/#/c/585915 [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Thu Jul 26 12:42:26 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Thu, 26 Jul 2018 12:42:26 +0000 Subject: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller In-Reply-To: <151EE31B9FCCA54397A757BC674650F0BA31BFBD@ALA-MBD.corp.ad.wrs.com> References: <93814834B4855241994F290E959305C752F508D3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E2A53@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F50B3A@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F511D2@SHSMSX104.ccr.corp.intel.com> <32D1079A-B94E-429B-B1B8-D917E1414699@intel.com> <93814834B4855241994F290E959305C752F514DA@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E3330@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F515B7@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F51AB3@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E4221@SHSMSX104.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA31BFBD@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B2E5044@SHSMSX104.ccr.corp.intel.com> Ghada, Yes, this is great feature - we used to have this inside Intel with Gerrit and Jira but nice to see we now have it with Gerrit and StoryBoard integrated. We shall use it! Thanks. - cindy -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, July 25, 2018 11:05 PM To: Xie, Cindy ; Liu, ZhipengS ; Arce Moreno, Abraham ; Cordoba Malibran, Erich ; Miller, Frank ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller There is Gerrit integration with story board. This was discussed previously on the mailing list, but I am re-sending as a reminder. http://superuser.openstack.org/articles/openstack-gerrit-storyboard-integration/ If the commit message includes the Story and Task IDs, the task will automatically be set to Merged and gerrit will include links to the review in story board. See this story for an example: https://storyboard.openstack.org/#!/story/2003085 I suggest we all use this moving forward for better traceability. Thanks, Ghada -----Original Message----- From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, July 25, 2018 10:51 AM To: Liu, ZhipengS; Arce Moreno, Abraham; Cordoba Malibran, Erich; Miller, Frank; Hu, Yong; Little, Scott; Qi, Mingyuan; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Do we already have a patch regarding: https://storyboard.openstack.org/#!/story/2003070 ? Then please add the patch link there. @ Zhipeng, you can create another task under the same story for the connectd failure you're seeing. Thx. - cindy -----Original Message----- From: Liu, ZhipengS Sent: Wednesday, July 25, 2018 9:23 AM To: Arce Moreno, Abraham ; Xie, Cindy ; Cordoba Malibran, Erich ; Miller, Frank ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller Hi Abraham, Scott, Hayde Thanks for your confirm! I have reviewed the patch, let's make it merged today. The remaining issue is that I saw the same error as before when I deployed it on multinode. Error: Systemd start for connectd failed! @Scott, could you help check it as well? Thanks! Zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月24日 21:53 To: Liu, ZhipengS ; Xie, Cindy ; Cordoba Malibran, Erich ; Miller, Frank ; Hu, Yong ; Little, Scott ; Qi, Mingyuan ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] About deployment issue: 06/08: Failed to execute controller manifest. Sporadic fail when config_controller > This is the key one, already in my code base Yes Zhipeng, you are correct! Those packages are missing to have the full build. Do you have the patch available? If not we can work on it with CC to you. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Thu Jul 26 12:59:36 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 26 Jul 2018 07:59:36 -0500 Subject: [Starlingx-discuss] [Gerrit] Gerrit notifaction to starlingx IRC channel In-Reply-To: References: Message-ID: On Wed, Jul 25, 2018 at 9:23 PM, Sun, Austin wrote: > I have made gerrit : https://review.openstack.org/#/c/585919/ , please help review it. That looks good Austin, thank you. We should also add the release branches to the gerritbot list: - ^r/.* dt -- Dean Troyer dtroyer at gmail.com From Eric.MacDonald at windriver.com Thu Jul 26 13:19:05 2018 From: Eric.MacDonald at windriver.com (MacDonald, Eric) Date: Thu, 26 Jul 2018 13:19:05 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: <93814834B4855241994F290E959305C752F52B57@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F52B57@SHSMSX104.ccr.corp.intel.com> Message-ID: <210898B96CA058408C55992CCAD98676B9E049F3@ALA-MBD.corp.ad.wrs.com> Looks like the manifest that configures and starts the collectd process is failing. Can you please execute the following commands on the host that shows collectd failing and publish the errors you see that might reveal the cause. # Get the config error logs ... sudo -i cd /var/log/puppet ; fgrep -R Error * # get the collectd startup failure logs cat /var/log/daemon.log | grep collectd one startup block is fine ; start to exit should show the error. Eric MacDonald > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: Thursday, July 26, 2018 4:53 AM > To: Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > Hi Abraham and Hayde > > I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. > Start collectd failed. > Could you help deploy ISO I built to see if it can work in your environment, thanks! > > Zhipeng > > > -----Original Message----- > From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] > Sent: 2018年7月26日 10:13 > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > Hi again, > > Can someone please help test the process to build an ISO based on master using Developer Guide [0]? > Please use Github page [1] as a documentation support. > > Requirements: > > - Repo status checked 7/25/2018 19:12 PST > - stx-tools master branch > - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros > - Temporal! Changes, already in Developer Guide > - RPM: selinux-policy-devel required > https://review.openstack.org/#/c/585915 > > [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Thu Jul 26 13:49:32 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 26 Jul 2018 08:49:32 -0500 Subject: [Starlingx-discuss] Firewalls and git URLs Message-ID: I had a question earlier about reaching git: URLs and was reminded that these do not work from China without corporate network proxy assistance, nor from inside some corporate proxies. I've updated the Developer Guide to use https://git.starlingx.io/stx-XXXX form URLs for git clone and repo init commands. I would appreciate someone in China verifying that these are reachable from outside corporate networks. Thanks dt -- Dean Troyer dtroyer at gmail.com From Al.Bailey at windriver.com Thu Jul 26 14:23:47 2018 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Thu, 26 Jul 2018 14:23:47 +0000 Subject: [Starlingx-discuss] download_mirrors.sh issues In-Reply-To: References: Message-ID: Hi Abraham, The patch is available here. https://review.openstack.org/#/c/586230/ This seems to fix almost all the missing rpms. There are less than 20 missing now, some of which may be related to the blizoo repo . I am recreating a fresh mirror now, and I will try to track down the remaining missing rpms. Al -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Wednesday, July 25, 2018 5:00 PM To: Arce Moreno, Abraham; Bailey, Henry Albert (Al); starlingx-discuss at lists.starlingx.io Subject: RE: download_mirrors.sh issues > > I will re-run the complete download routine and see if this fixes all > > the remaining (non src) issues. > > Is it possible you submit a patch if it works for you? > > Adopting the over communication approach, I am logging all the steps and > output in this url [0]. Not using etherpad to have a faster edit / easy > formatting. > > [0] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md Afternoon update on StarlingX Compilation Master Branch started today morning. stx-tools branch master $ git log --pretty=oneline -2 f31f99ab91435c32c24a86efd2e697177074f4b7 Merge "policycoreutils-newrole was missing" c3000c2936f56ad0257142d5c5bad3afc08c46cc Merge "upgrade linux-firmware RPM version" Taking StarlingX Developer Guide [0] as an input and a temporal Github page [1] as an output. [1] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [0] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md From zhipengs.liu at intel.com Thu Jul 26 14:25:00 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 26 Jul 2018 14:25:00 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: <210898B96CA058408C55992CCAD98676B9E049F3@ALA-MBD.corp.ad.wrs.com> References: <93814834B4855241994F290E959305C752F52B57@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E049F3@ALA-MBD.corp.ad.wrs.com> Message-ID: <93814834B4855241994F290E959305C752F52D91@SHSMSX104.ccr.corp.intel.com> Hi Eric, Thanks for your comment!! Could you help further check the error I saw below? ============================================================================= controller-0:/var/log/puppet# grep -R Error* latest/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! latest/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! =============================================================================== ontroller-0:~$ cat /var/log/daemon.log | grep collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "network" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "threshold" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "df" successfully loaded. 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.073 localhost collectd[25253]: info Error: Reading the config file failed! 2018-07-26T16:36:33.073 localhost collectd[25253]: info Read the syslog for details. 2018-07-26T16:36:33.073 localhost collectd[25253]: info = 2018-07-26T16:36:33.100 localhost systemd[1]: notice collectd.service: main process exited, code=exited, status=1/FAILURE 2018-07-26T16:36:33.110 localhost systemd[1]: notice Unit collectd.service entered failed state. 2018-07-26T16:36:33.110 localhost systemd[1]: warning collectd.service failed. ====================================================================== Thanks! Zhipeng -----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: 2018年7月26日 21:19 To: Liu, ZhipengS ; Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide Looks like the manifest that configures and starts the collectd process is failing. Can you please execute the following commands on the host that shows collectd failing and publish the errors you see that might reveal the cause. # Get the config error logs ... sudo -i cd /var/log/puppet ; fgrep -R Error * # get the collectd startup failure logs cat /var/log/daemon.log | grep collectd one startup block is fine ; start to exit should show the error. Eric MacDonald > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: Thursday, July 26, 2018 4:53 AM > To: Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > Hi Abraham and Hayde > > I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. > Start collectd failed. > Could you help deploy ISO I built to see if it can work in your environment, thanks! > > Zhipeng > > > -----Original Message----- > From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] > Sent: 2018年7月26日 10:13 > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > Hi again, > > Can someone please help test the process to build an ISO based on master using Developer Guide [0]? > Please use Github page [1] as a documentation support. > > Requirements: > > - Repo status checked 7/25/2018 19:12 PST > - stx-tools master branch > - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros > - Temporal! Changes, already in Developer Guide > - RPM: selinux-policy-devel required > https://review.openstack.org/#/c/585915 > > [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md > > _______________________________________________ > 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 abraham.arce.moreno at intel.com Thu Jul 26 14:40:15 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Thu, 26 Jul 2018 14:40:15 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: <9BAB5B7CAF57C3459E4636391F1071CECA1D32@shsmsx102.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F5280F@SHSMSX104.ccr.corp.intel.com> <9BAB5B7CAF57C3459E4636391F1071CECA1D32@shsmsx102.ccr.corp.intel.com> Message-ID: > Hi Abraham and Zhipeng > Hope to join you. And I'll update to you once I make any progress. Thanks again Zhipeng, Ran! From Eric.MacDonald at windriver.com Thu Jul 26 14:45:10 2018 From: Eric.MacDonald at windriver.com (MacDonald, Eric) Date: Thu, 26 Jul 2018 14:45:10 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: <93814834B4855241994F290E959305C752F52D91@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F52B57@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E049F3@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C752F52D91@SHSMSX104.ccr.corp.intel.com> Message-ID: <210898B96CA058408C55992CCAD98676B9E04A62@ALA-MBD.corp.ad.wrs.com> That's interesting. It looks like the python plugin manager for collectd is missing yet the 'network' on of the same is ok. Please execute this command to see what related packages exists (or are missing) rpm -qa | grep collect Eric. > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: Thursday, July 26, 2018 10:25 AM > To: MacDonald, Eric; Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io > Subject: RE: [RFC] StarlingX Developer Guide > Importance: High > > Hi Eric, > > Thanks for your comment!! Could you help further check the error I saw below? > ============================================================================= > controller-0:/var/log/puppet# grep -R Error* > latest/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for > collectd failed! > latest/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 > /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: > Systemd start for collectd failed! > 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 > +0000 Systemd start for collectd failed! > 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 > +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: > Systemd start for collectd failed! > =============================================================================== > ontroller-0:~$ cat /var/log/daemon.log | grep collectd > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "network" successfully > loaded. > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in > /usr/lib64/collectd > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in > /usr/lib64/collectd > 2018-07-26T16:36:33.072 localhost collectd[25253]: info Automatically loading plugin "python" failed > with status 1. > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "threshold" successfully > loaded. > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "df" successfully loaded. > 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in > /usr/lib64/collectd > 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in > /usr/lib64/collectd > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Automatically loading plugin "python" failed > with status 1. > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Error: Reading the config file failed! > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Read the syslog for details. > 2018-07-26T16:36:33.073 localhost collectd[25253]: info = > 2018-07-26T16:36:33.100 localhost systemd[1]: notice collectd.service: main process exited, code=exited, > status=1/FAILURE > 2018-07-26T16:36:33.110 localhost systemd[1]: notice Unit collectd.service entered failed state. > 2018-07-26T16:36:33.110 localhost systemd[1]: warning collectd.service failed. > ====================================================================== > > Thanks! > Zhipeng > -----Original Message----- > From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] > Sent: 2018年7月26日 21:19 > To: Liu, ZhipengS ; Arce Moreno, Abraham ; > starlingx-discuss at lists.starlingx.io > Subject: RE: [RFC] StarlingX Developer Guide > > Looks like the manifest that configures and starts the collectd process is failing. > > Can you please execute the following commands on the host that shows collectd failing and publish the > errors you see that might reveal the cause. > > # Get the config error logs ... > sudo -i > cd /var/log/puppet ; fgrep -R Error * > > # get the collectd startup failure logs > cat /var/log/daemon.log | grep collectd > > one startup block is fine ; start to exit should show the error. > > Eric MacDonald > > > -----Original Message----- > > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > > Sent: Thursday, July 26, 2018 4:53 AM > > To: Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > > > Hi Abraham and Hayde > > > > I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. > > Start collectd failed. > > Could you help deploy ISO I built to see if it can work in your environment, thanks! > > > > Zhipeng > > > > > > -----Original Message----- > > From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] > > Sent: 2018年7月26日 10:13 > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > > > Hi again, > > > > Can someone please help test the process to build an ISO based on master using Developer Guide [0]? > > Please use Github page [1] as a documentation support. > > > > Requirements: > > > > - Repo status checked 7/25/2018 19:12 PST > > - stx-tools master branch > > - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros > > - Temporal! Changes, already in Developer Guide > > - RPM: selinux-policy-devel required > > https://review.openstack.org/#/c/585915 > > > > [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md > > > > _______________________________________________ > > 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 zhipengs.liu at intel.com Thu Jul 26 14:45:25 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 26 Jul 2018 14:45:25 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: <93814834B4855241994F290E959305C752F52D91@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F52B57@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E049F3@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C752F52D91@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C752F52DDC@SHSMSX104.ccr.corp.intel.com> Do we need collected-python package in mirror? -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: 2018年7月26日 22:25 To: MacDonald, Eric ; Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide Hi Eric, Thanks for your comment!! Could you help further check the error I saw below? ============================================================================= controller-0:/var/log/puppet# grep -R Error* latest/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! latest/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! =============================================================================== ontroller-0:~$ cat /var/log/daemon.log | grep collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "network" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "threshold" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "df" successfully loaded. 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.073 localhost collectd[25253]: info Error: Reading the config file failed! 2018-07-26T16:36:33.073 localhost collectd[25253]: info Read the syslog for details. 2018-07-26T16:36:33.073 localhost collectd[25253]: info = 2018-07-26T16:36:33.100 localhost systemd[1]: notice collectd.service: main process exited, code=exited, status=1/FAILURE 2018-07-26T16:36:33.110 localhost systemd[1]: notice Unit collectd.service entered failed state. 2018-07-26T16:36:33.110 localhost systemd[1]: warning collectd.service failed. ====================================================================== Thanks! Zhipeng -----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: 2018年7月26日 21:19 To: Liu, ZhipengS ; Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide Looks like the manifest that configures and starts the collectd process is failing. Can you please execute the following commands on the host that shows collectd failing and publish the errors you see that might reveal the cause. # Get the config error logs ... sudo -i cd /var/log/puppet ; fgrep -R Error * # get the collectd startup failure logs cat /var/log/daemon.log | grep collectd one startup block is fine ; start to exit should show the error. Eric MacDonald > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: Thursday, July 26, 2018 4:53 AM > To: Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > Hi Abraham and Hayde > > I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. > Start collectd failed. > Could you help deploy ISO I built to see if it can work in your environment, thanks! > > Zhipeng > > > -----Original Message----- > From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] > Sent: 2018年7月26日 10:13 > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > Hi again, > > Can someone please help test the process to build an ISO based on master using Developer Guide [0]? > Please use Github page [1] as a documentation support. > > Requirements: > > - Repo status checked 7/25/2018 19:12 PST > - stx-tools master branch > - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros > - Temporal! Changes, already in Developer Guide > - RPM: selinux-policy-devel required > https://review.openstack.org/#/c/585915 > > [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md > > _______________________________________________ > 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 Dariush.Eslimi at windriver.com Thu Jul 26 14:47:31 2018 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Thu, 26 Jul 2018 14:47:31 +0000 Subject: [Starlingx-discuss] download_mirrors.sh issues In-Reply-To: <5B58E009.505@windriver.com> References: <886c47cc-855b-4ceb-4649-0f8e02b8b571@windriver.com> <5B58E009.505@windriver.com> Message-ID: Chris, I tried your suggested mirror, and it is failing from Ottawa : http://mirror.csclub.uwaterloo.ca/fedora/epel/7Server/x86_64/repodata/15643babbd68ee80c284c83a6474b9af954efc4c8daaf78cca45ef3fb79a8630-primary.xml.gz: [Errno 12] Timeout on http://mirror.csclub.uwaterloo.ca/fedora/epel/7Server/x86_64/repodata/15643babbd68ee80c284c83a6474b9af954efc4c8daaf78cca45ef3fb79a8630-primary.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Any other one? Thanks, Dariush -----Original Message----- From: Chris Friesen [mailto:chris.friesen at windriver.com] Sent: July-25-18 4:40 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] download_mirrors.sh issues On 07/25/2018 01:33 PM, Scott Little wrote: > The http://epel.blizoo.mk/epel/ site is blocked by the security > gateway internal to Windriver. Reason is 'potentially unwanted > programs'. Is there an alternative to this site? > > What packages are being supplied by this site? It looks like it's just EPEL. I think this is equivalent: http://mirror.csclub.uwaterloo.ca/fedora/epel/ Chris _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From abraham.arce.moreno at intel.com Thu Jul 26 14:47:46 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Thu, 26 Jul 2018 14:47:46 +0000 Subject: [Starlingx-discuss] StarlingX: Tar Compressed Files Repository Restructuring In-Reply-To: <93814834B4855241994F290E959305C752F51B22@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F51B22@SHSMSX104.ccr.corp.intel.com> Message-ID: Thanks Zhipeng! > Just 2 proposals. > 1) Every time, when I run download_mirror, it will always download mvn > which will take around 1~2 hours. > Could you add a check in the script that if mvn.repo.tgz exists, do not try to > download it again. Same for other packages. Annotated, I will complement your idea with Saul's. Today the check is done only by identifying if the file is there, a checksum will give us the next level of verification. > 2) When download list changed, the script only downloads added packages > and also removes the ones of old versions that we do not used anymore. Annotated. From zhipengs.liu at intel.com Thu Jul 26 14:47:12 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 26 Jul 2018 14:47:12 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: <210898B96CA058408C55992CCAD98676B9E04A62@ALA-MBD.corp.ad.wrs.com> References: <93814834B4855241994F290E959305C752F52B57@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E049F3@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C752F52D91@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E04A62@ALA-MBD.corp.ad.wrs.com> Message-ID: <93814834B4855241994F290E959305C752F52DF5@SHSMSX104.ccr.corp.intel.com> controller-0:~# rpm -qa | grep collect libcollection-0.6.2-27.el7.x86_64 openstack-ceilometer-collector-9.0.1-1.tis.3.noarch collectd-extensions-1.0-0.tis.1.x86_64 collector-1.0-24.tis.x86_64 collectd-5.7.1-2.el7.x86_64 puppet-collectd-5.1.0-2.4a3843cgit.el7.noarch python2-debtcollector-1.17.0-1.el7.noarch controller-0:~# -----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: 2018年7月26日 22:45 To: Liu, ZhipengS ; Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide That's interesting. It looks like the python plugin manager for collectd is missing yet the 'network' on of the same is ok. Please execute this command to see what related packages exists (or are missing) rpm -qa | grep collect Eric. > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: Thursday, July 26, 2018 10:25 AM > To: MacDonald, Eric; Arce Moreno, Abraham; > starlingx-discuss at lists.starlingx.io > Subject: RE: [RFC] StarlingX Developer Guide > Importance: High > > Hi Eric, > > Thanks for your comment!! Could you help further check the error I saw below? > ====================================================================== > ======= controller-0:/var/log/puppet# grep -R Error* > latest/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 > +0000 Systemd start for collectd failed! > latest/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 > +0000 > /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: > Systemd start for collectd failed! > 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.125 > Error: 2018-07-26 16:36:33 > +0000 Systemd start for collectd failed! > 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.236 > Error: 2018-07-26 16:36:33 > +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: > Systemd start for collectd failed! > ====================================================================== > ========= ontroller-0:~$ cat /var/log/daemon.log | grep collectd > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > plugin "network" successfully loaded. > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > Could not find plugin "python" in /usr/lib64/collectd > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > Could not find plugin "python" in /usr/lib64/collectd > 2018-07-26T16:36:33.072 localhost collectd[25253]: info Automatically > loading plugin "python" failed with status 1. > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > plugin "threshold" successfully loaded. > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "df" successfully loaded. > 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: > Could not find plugin "python" in /usr/lib64/collectd > 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: > Could not find plugin "python" in /usr/lib64/collectd > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Automatically > loading plugin "python" failed with status 1. > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Error: Reading the config file failed! > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Read the syslog for details. > 2018-07-26T16:36:33.073 localhost collectd[25253]: info = > 2018-07-26T16:36:33.100 localhost systemd[1]: notice collectd.service: > main process exited, code=exited, status=1/FAILURE > 2018-07-26T16:36:33.110 localhost systemd[1]: notice Unit collectd.service entered failed state. > 2018-07-26T16:36:33.110 localhost systemd[1]: warning collectd.service failed. > ====================================================================== > > Thanks! > Zhipeng > -----Original Message----- > From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] > Sent: 2018年7月26日 21:19 > To: Liu, ZhipengS ; Arce Moreno, Abraham > ; starlingx-discuss at lists.starlingx.io > Subject: RE: [RFC] StarlingX Developer Guide > > Looks like the manifest that configures and starts the collectd process is failing. > > Can you please execute the following commands on the host that shows > collectd failing and publish the errors you see that might reveal the cause. > > # Get the config error logs ... > sudo -i > cd /var/log/puppet ; fgrep -R Error * > > # get the collectd startup failure logs cat /var/log/daemon.log | grep > collectd > > one startup block is fine ; start to exit should show the error. > > Eric MacDonald > > > -----Original Message----- > > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > > Sent: Thursday, July 26, 2018 4:53 AM > > To: Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > > > Hi Abraham and Hayde > > > > I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. > > Start collectd failed. > > Could you help deploy ISO I built to see if it can work in your environment, thanks! > > > > Zhipeng > > > > > > -----Original Message----- > > From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] > > Sent: 2018年7月26日 10:13 > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > > > Hi again, > > > > Can someone please help test the process to build an ISO based on master using Developer Guide [0]? > > Please use Github page [1] as a documentation support. > > > > Requirements: > > > > - Repo status checked 7/25/2018 19:12 PST > > - stx-tools master branch > > - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update > > RPM macros > > - Temporal! Changes, already in Developer Guide > > - RPM: selinux-policy-devel required > > https://review.openstack.org/#/c/585915 > > > > [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > [1] > > https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md > > > > _______________________________________________ > > 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 Eric.MacDonald at windriver.com Thu Jul 26 14:50:25 2018 From: Eric.MacDonald at windriver.com (MacDonald, Eric) Date: Thu, 26 Jul 2018 14:50:25 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: <93814834B4855241994F290E959305C752F52DF5@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F52B57@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E049F3@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C752F52D91@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E04A62@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C752F52DF5@SHSMSX104.ccr.corp.intel.com> Message-ID: <210898B96CA058408C55992CCAD98676B9E04A91@ALA-MBD.corp.ad.wrs.com> That looks ok, I'll continue to investigate ... stay tuned > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: Thursday, July 26, 2018 10:47 AM > To: MacDonald, Eric; Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io > Subject: RE: [RFC] StarlingX Developer Guide > Importance: High > > controller-0:~# rpm -qa | grep collect > libcollection-0.6.2-27.el7.x86_64 > openstack-ceilometer-collector-9.0.1-1.tis.3.noarch > collectd-extensions-1.0-0.tis.1.x86_64 > collector-1.0-24.tis.x86_64 > collectd-5.7.1-2.el7.x86_64 > puppet-collectd-5.1.0-2.4a3843cgit.el7.noarch > python2-debtcollector-1.17.0-1.el7.noarch > controller-0:~# > > -----Original Message----- > From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] > Sent: 2018年7月26日 22:45 > To: Liu, ZhipengS ; Arce Moreno, Abraham ; > starlingx-discuss at lists.starlingx.io > Subject: RE: [RFC] StarlingX Developer Guide > > That's interesting. It looks like the python plugin manager for collectd is missing yet the 'network' on of the > same is ok. > > Please execute this command to see what related packages exists (or are missing) > > rpm -qa | grep collect > > Eric. > > > -----Original Message----- > > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > > Sent: Thursday, July 26, 2018 10:25 AM > > To: MacDonald, Eric; Arce Moreno, Abraham; > > starlingx-discuss at lists.starlingx.io > > Subject: RE: [RFC] StarlingX Developer Guide > > Importance: High > > > > Hi Eric, > > > > Thanks for your comment!! Could you help further check the error I saw below? > > ====================================================================== > > ======= controller-0:/var/log/puppet# grep -R Error* > > latest/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 > > +0000 Systemd start for collectd failed! > > latest/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 > > +0000 > > /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: > > Systemd start for collectd failed! > > 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.125 > > Error: 2018-07-26 16:36:33 > > +0000 Systemd start for collectd failed! > > 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.236 > > Error: 2018-07-26 16:36:33 > > +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: > > Systemd start for collectd failed! > > ====================================================================== > > ========= ontroller-0:~$ cat /var/log/daemon.log | grep collectd > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > > plugin "network" successfully loaded. > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > > Could not find plugin "python" in /usr/lib64/collectd > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > > Could not find plugin "python" in /usr/lib64/collectd > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info Automatically > > loading plugin "python" failed with status 1. > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > > plugin "threshold" successfully loaded. > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "df" successfully loaded. > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: > > Could not find plugin "python" in /usr/lib64/collectd > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: > > Could not find plugin "python" in /usr/lib64/collectd > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Automatically > > loading plugin "python" failed with status 1. > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Error: Reading the config file failed! > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Read the syslog for details. > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info = > > 2018-07-26T16:36:33.100 localhost systemd[1]: notice collectd.service: > > main process exited, code=exited, status=1/FAILURE > > 2018-07-26T16:36:33.110 localhost systemd[1]: notice Unit collectd.service entered failed state. > > 2018-07-26T16:36:33.110 localhost systemd[1]: warning collectd.service failed. > > ====================================================================== > > > > Thanks! > > Zhipeng > > -----Original Message----- > > From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] > > Sent: 2018年7月26日 21:19 > > To: Liu, ZhipengS ; Arce Moreno, Abraham > > ; starlingx-discuss at lists.starlingx.io > > Subject: RE: [RFC] StarlingX Developer Guide > > > > Looks like the manifest that configures and starts the collectd process is failing. > > > > Can you please execute the following commands on the host that shows > > collectd failing and publish the errors you see that might reveal the cause. > > > > # Get the config error logs ... > > sudo -i > > cd /var/log/puppet ; fgrep -R Error * > > > > # get the collectd startup failure logs cat /var/log/daemon.log | grep > > collectd > > > > one startup block is fine ; start to exit should show the error. > > > > Eric MacDonald > > > > > -----Original Message----- > > > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > > > Sent: Thursday, July 26, 2018 4:53 AM > > > To: Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io > > > Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > > > > > Hi Abraham and Hayde > > > > > > I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. > > > Start collectd failed. > > > Could you help deploy ISO I built to see if it can work in your environment, thanks! > > > > > > Zhipeng > > > > > > > > > -----Original Message----- > > > From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] > > > Sent: 2018年7月26日 10:13 > > > To: starlingx-discuss at lists.starlingx.io > > > Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > > > > > Hi again, > > > > > > Can someone please help test the process to build an ISO based on master using Developer Guide [0]? > > > Please use Github page [1] as a documentation support. > > > > > > Requirements: > > > > > > - Repo status checked 7/25/2018 19:12 PST > > > - stx-tools master branch > > > - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update > > > RPM macros > > > - Temporal! Changes, already in Developer Guide > > > - RPM: selinux-policy-devel required > > > https://review.openstack.org/#/c/585915 > > > > > > [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > [1] > > > https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md > > > > > > _______________________________________________ > > > 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 yong.hu at intel.com Thu Jul 26 14:52:15 2018 From: yong.hu at intel.com (Hu, Yong) Date: Thu, 26 Jul 2018 14:52:15 +0000 Subject: [Starlingx-discuss] Firewalls and git URLs In-Reply-To: References: Message-ID: <70FA85CF-3089-4426-A262-CB81CB9785EA@intel.com> Hi Dean, At my home, without VPN or corporate network proxy, in my laptop I can access https://git.starlingx.io/ And also, I can do "git clone", for example, git clone https://git.starlingx.io/stx-config BTW: inside office, because our Linux hosts are not in any domains, they have to go through network proxies (http and https), in order to access network. Regards, Yong On 26/07/2018, 9:50 PM, "Dean Troyer" wrote: I had a question earlier about reaching git: URLs and was reminded that these do not work from China without corporate network proxy assistance, nor from inside some corporate proxies. I've updated the Developer Guide to use https://git.starlingx.io/stx-XXXX form URLs for git clone and repo init commands. I would appreciate someone in China verifying that these are reachable from outside corporate networks. Thanks dt -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From zhipengs.liu at intel.com Thu Jul 26 14:52:21 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 26 Jul 2018 14:52:21 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: <210898B96CA058408C55992CCAD98676B9E04A91@ALA-MBD.corp.ad.wrs.com> References: <93814834B4855241994F290E959305C752F52B57@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E049F3@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C752F52D91@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E04A62@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C752F52DF5@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E04A91@ALA-MBD.corp.ad.wrs.com> Message-ID: <93814834B4855241994F290E959305C752F52E1E@SHSMSX104.ccr.corp.intel.com> Thanks a lot! Zhipeng -----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: 2018年7月26日 22:50 To: Liu, ZhipengS ; Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide That looks ok, I'll continue to investigate ... stay tuned > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: Thursday, July 26, 2018 10:47 AM > To: MacDonald, Eric; Arce Moreno, Abraham; > starlingx-discuss at lists.starlingx.io > Subject: RE: [RFC] StarlingX Developer Guide > Importance: High > > controller-0:~# rpm -qa | grep collect > libcollection-0.6.2-27.el7.x86_64 > openstack-ceilometer-collector-9.0.1-1.tis.3.noarch > collectd-extensions-1.0-0.tis.1.x86_64 > collector-1.0-24.tis.x86_64 > collectd-5.7.1-2.el7.x86_64 > puppet-collectd-5.1.0-2.4a3843cgit.el7.noarch > python2-debtcollector-1.17.0-1.el7.noarch > controller-0:~# > > -----Original Message----- > From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] > Sent: 2018年7月26日 22:45 > To: Liu, ZhipengS ; Arce Moreno, Abraham > ; starlingx-discuss at lists.starlingx.io > Subject: RE: [RFC] StarlingX Developer Guide > > That's interesting. It looks like the python plugin manager for > collectd is missing yet the 'network' on of the same is ok. > > Please execute this command to see what related packages exists (or > are missing) > > rpm -qa | grep collect > > Eric. > > > -----Original Message----- > > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > > Sent: Thursday, July 26, 2018 10:25 AM > > To: MacDonald, Eric; Arce Moreno, Abraham; > > starlingx-discuss at lists.starlingx.io > > Subject: RE: [RFC] StarlingX Developer Guide > > Importance: High > > > > Hi Eric, > > > > Thanks for your comment!! Could you help further check the error I saw below? > > ==================================================================== > > == ======= controller-0:/var/log/puppet# grep -R Error* > > latest/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 > > +0000 Systemd start for collectd failed! > > latest/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 > > +0000 > > /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: > > Systemd start for collectd failed! > > 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.125 > > Error: 2018-07-26 16:36:33 > > +0000 Systemd start for collectd failed! > > 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.236 > > Error: 2018-07-26 16:36:33 > > +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: > > Systemd start for collectd failed! > > ==================================================================== > > == ========= ontroller-0:~$ cat /var/log/daemon.log | grep collectd > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > > plugin "network" successfully loaded. > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > > Could not find plugin "python" in /usr/lib64/collectd > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > > Could not find plugin "python" in /usr/lib64/collectd > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info > > Automatically loading plugin "python" failed with status 1. > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > > plugin "threshold" successfully loaded. > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "df" successfully loaded. > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: > > Could not find plugin "python" in /usr/lib64/collectd > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: > > Could not find plugin "python" in /usr/lib64/collectd > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info > > Automatically loading plugin "python" failed with status 1. > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Error: Reading the config file failed! > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Read the syslog for details. > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info = > > 2018-07-26T16:36:33.100 localhost systemd[1]: notice collectd.service: > > main process exited, code=exited, status=1/FAILURE > > 2018-07-26T16:36:33.110 localhost systemd[1]: notice Unit collectd.service entered failed state. > > 2018-07-26T16:36:33.110 localhost systemd[1]: warning collectd.service failed. > > ==================================================================== > > == > > > > Thanks! > > Zhipeng > > -----Original Message----- > > From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] > > Sent: 2018年7月26日 21:19 > > To: Liu, ZhipengS ; Arce Moreno, Abraham > > ; > > starlingx-discuss at lists.starlingx.io > > Subject: RE: [RFC] StarlingX Developer Guide > > > > Looks like the manifest that configures and starts the collectd process is failing. > > > > Can you please execute the following commands on the host that shows > > collectd failing and publish the errors you see that might reveal the cause. > > > > # Get the config error logs ... > > sudo -i > > cd /var/log/puppet ; fgrep -R Error * > > > > # get the collectd startup failure logs cat /var/log/daemon.log | > > grep collectd > > > > one startup block is fine ; start to exit should show the error. > > > > Eric MacDonald > > > > > -----Original Message----- > > > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > > > Sent: Thursday, July 26, 2018 4:53 AM > > > To: Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io > > > Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > > > > > Hi Abraham and Hayde > > > > > > I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. > > > Start collectd failed. > > > Could you help deploy ISO I built to see if it can work in your environment, thanks! > > > > > > Zhipeng > > > > > > > > > -----Original Message----- > > > From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] > > > Sent: 2018年7月26日 10:13 > > > To: starlingx-discuss at lists.starlingx.io > > > Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > > > > > Hi again, > > > > > > Can someone please help test the process to build an ISO based on master using Developer Guide [0]? > > > Please use Github page [1] as a documentation support. > > > > > > Requirements: > > > > > > - Repo status checked 7/25/2018 19:12 PST > > > - stx-tools master branch > > > - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update > > > RPM macros > > > - Temporal! Changes, already in Developer Guide > > > - RPM: selinux-policy-devel required > > > https://review.openstack.org/#/c/585915 > > > > > > [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > [1] > > > https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discu > > > ss _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Thu Jul 26 15:07:11 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 26 Jul 2018 11:07:11 -0400 Subject: [Starlingx-discuss] download_mirrors.sh issues In-Reply-To: <886c47cc-855b-4ceb-4649-0f8e02b8b571@windriver.com> References: <886c47cc-855b-4ceb-4649-0f8e02b8b571@windriver.com> Message-ID: In download_mirror.sh step 1 ... When http://epel.blizoo.mk/cannot be accessed due to firewall restrictions, StarlingX_3rd.repo is deleted from /etc/yum.repos.d/. This means that all other repos named in that file are dropped as well. I proposed we do this... 1) create directory stx-tools/centos-mirror-tools/yum.repos.d 2) move StarlingX_3rd.repo and StarlingX.repo into stx-tools/centos-mirror-tools/yum.repos.d/ 3) break up StarlingX_3rd.repo ... one file per sight 4) break up StarlingX.repo ... one file per centos release 5) modify Dockerfile -  COPY StarlingX.repo /etc/yum.repos.d -  COPY StarlingX_3rd.repo /etc/yum.repos.d +  COPY yum.repos.d/* /etc/yum.repos.d/ On 18-07-25 03:33 PM, Scott Little wrote: > The http://epel.blizoo.mk/epel/ site is blocked by the security > gateway internal to Windriver.  Reason is 'potentially unwanted > programs'.  Is there an alternative to this site? > > What packages are being supplied by this site? > > Scott > > > On 18-07-25 02:32 PM, Arce Moreno, Abraham wrote: >>> I am following the instructions here: >>> >>> https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Software_Requir >>> >>> ements >> Thanks Al! >> >> A request for everybody, please continuously refresh the webpage due >> to the >> daily changes. The word "Temporal!" is used across this guide to >> highlight those patches >> needed to have a successful build. >> >> For branch Master, we are identifying those patches not merged as: >>      Temporal! Only Branch Master >> >> For branch m/2018.07, we are identifying those patches not merged as: >>      Temporal! Only Branch m/2018.07 >> >>> I have been un-successful in running the first setup actions for >>> doing an >>> official build, which is getting my mirror setup. >>> >>> I have all the latest commits in master for stx-tools. >> Our commit ids for today's build are: >> >> stx-tools branch master >> >>      $ git log --pretty=oneline -2 >>      f31f99ab91435c32c24a86efd2e697177074f4b7 Merge >> "policycoreutils-newrole was missing" >>      c3000c2936f56ad0257142d5c5bad3afc08c46cc Merge "upgrade >> linux-firmware RPM version"``` >> >> stx-tools branch m/2018.07 >> >>      $ git log --pretty=oneline -5 >>      88aadc543085e24e3c5df10ec63996b9f5551ff6 Merge "Package updates >> for new version of selinux-policy" into m/2018.07 >>     9c44470a2d6ff86a40f42c2b608e723c355ae38f Merge "Copy >> mock.cfg.proto and comps.xml files into cgcs-centos-repo" into >> m/2018.07``` >> >>> The first issue encountered was the macros.   This has already been >>> reported >>> here >>> https://storyboard.openstack.org/#!/story/2003072 >>> >>> I only had 4 entries listed as missing, until after I updated these >>> to the >>> following newer versions >>> >>> epel-rpm-macros-7-19.noarch.rpm >>> python2-rpm-macros-3-20.el7.noarch.rpm >>> python-rpm-macros-3-20.el7.noarch.rpm >>> python-srpm-macros-3-20.el7.noarch.rpm >> Also in this setup... >> >>> I don't know if that is the appropriate solution, since all this >>> allowed me to do >>> was fail to download some other things. >> We have 2 options: >> >> 1. a manual download of the packages >> 2. use of a tool, in review status [0] >> >>> Running download_mirror.sh again showed 140+ rpms as missing >>> >>> As an aside, sometimes the "missing"  log files are blank, even >>> though not all >>> components were downloaded.   I assume this is due to something >>> aborting. >> >>> Lighttpd  for example  is never being found. >> Same here: >> >>      Delta RPMs disabled because /usr/bin/applydeltarpm not installed. >>      warning: >> /var/cache/yum/x86_64/7/epel/packages/lighttpd-1.4.49-1.el7.x86_64.rpm: >> \ >>          Header V3 RSA/SHA256 Signature, key ID 352c64e5: NOKEY >>      Public key for lighttpd-1.4.49-1.el7.x86_64.rpm is not installed >> >>> By redirecting the script to log everything to a file, it shows this >>> particular >>> error message which may be a potential culprit >>> >>> "Loaded plugins: fastestmirror, ovl >>> http://epel.blizoo.mk/epel/7Server/x86_64/repodata/repomd.xml: >>> [Errno 14] >>> HTTP Error 403 - Forbidden >>> Trying other mirror. >>> To address this issue please refer to the below knowledge base article >>> https://access.redhat.com/solutions/69319 >>> If above article doesn't help to resolve this issue please create a >>> bug on >>> https://bugs.centos.org/ >>> One of the configured repositories failed (Starlingx- >>> epel.blizoo.mk_epel_7Server_x86_64 - >>> epel.blizoo.mk_epel_7Server_x86_64), >>> and yum doesn't have enough cached data to continue. At this point >>> the only >>> safe thing yum can do is fail." >>> >>> Does anyone know anything about this blizoo  repo?  Is it causing >>> anyone else >>> to not be able to download all the rpms,  or  is it unrelated to the >>> build setup >>> issues? >> Not seeing the blizoo repo failure in our side... internet connection >> is slow so will come back to >> you with more updates some time later. >> >> [0] https://review.openstack.org/#/c/585009/ >> >> _______________________________________________ >> 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 abraham.arce.moreno at intel.com Thu Jul 26 15:09:17 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Thu, 26 Jul 2018 15:09:17 +0000 Subject: [Starlingx-discuss] StarlingX: Tar Compressed Files Repository Restructuring In-Reply-To: <52dd7eca-a630-71af-ab70-aae4c0e5ad7d@linux.intel.com> References: <93814834B4855241994F290E959305C752F51B22@SHSMSX104.ccr.corp.intel.com> <52dd7eca-a630-71af-ab70-aae4c0e5ad7d@linux.intel.com> Message-ID: Thanks Saul! > > Just 2 proposals. > > 1) Every time, when I run download_mirror, it will always download mvn > which will take around 1~2 hours. > > Could you add a check in the script that if mvn.repo.tgz exists, do > > not try to download it again. Same for other package > > 2) When download list changed, the script only downloads added packages > and also removes the ones of old versions that we do not used anymore. > > > I was thinking we could try to incorporate somekind of checksum > information, in order to validate the downloads are correct and complete. Is this harcoded checksum checking the same way Yocto does as part of the recipes? Can we have the checksum incorporated in our existing text file as another column? Do we need another file? > > The call sequence under CentOS Mirror Tools [2] is as follows ending in > executing our tarball-dl.sh: > > > > 1 download_mirror.sh > > 1.1 dl_rpms.sh > > 1.2 dl_other_from_centos_repo.sh > > 1.3 tarball-dl.sh > > > > Open Questions: > > - Should we keep this script being called from download_mirror.sh? > > - Should we keep this file being written as shell script? > > - Any comment based on midterm / long term changes? > > - Any other comment? > > > So the script is doing 3 things, I think there should be more checking as to > what exists and what's needed. The RPM fetching can be done independant > of the tarball, so that we can use a query of the repos instead of full > download. How about starting by splitting our download of tarballs from the rpms script? this will allow us to track independently the 2 efforts and avoid having a failure in the download of one because of the other. Taking your idea and Zhipeng's, how about something like the steps below? This will be also reflected in our Developer Guide: 1 "Step Download RPMs" > download_mirror.sh 1.1 dl_rpms.sh 1.2 dl_other_from_centos_repo.sh 2 "Step Download Tarballs" > tarball-dl.sh 2.1 what exists 2.2 verify .. checksum? 2.3 continue / download 2.4 if download? verify .. checksum ? > Another thought is to provide the option to point this at somekind of > company based mirror, so that each larger company could keep an internal > mirror, but smaller organizations will hit the external sources. The "Step Download Tarball" can allow us to build that repo and same script to verify its integrity, complementing with Zhipeng's idea to download new versions or remove old ones. > > A special character "!" is used at the beginning of 6 package file names > denoting they require special handling is required: additional steps besides > the common process including but not limited to remove text from some files, > use only one directory, etc: > > > > - integrity-kmod-668a8270.tar.gz > > - mariadb-10.1.28.tar.gz > > - mvn.repo.tgz > > - qat1.7.upstream.l.1.0.3-42.tar.gz > > - tpm-kmod-668a8270.tar.gz > > - tss2-930.tar.gz > > > > Open Questions: > > - Any specific method to handle these 6 packages? > > - Any other comment? > > > This one is harder, since each of these is a different special case to deal with > git or multiple downloads (mvn). Short of creating some sort of "plugin" > mechanism that handles each special case. > I will ask for feedback to our experts about how this "plugin" can be achieved. This includes suggestion from Zhipeng related to mvn in previous email thread. > > Our build system uses defined paths after the Tarball package filename > > is decompressed, see Columns H " 'Directory Name Cgcs-Dl" and Column I > > " 'Directory Name tarball-dl.sh" for a > > comparison: > > > > - It could be the same after it is decompressed from the original file > > - dpkg_1.18.24.tar.xz#dpkg-1.18.24 > > - It could use a different name after it is decompressed from the original file > > - !integrity-kmod-668a8270.tar.gz#integrity > > - > > puppet-dnsmasq- > cff07e90890662972c97684a2baee964f68ff3ed.tar.gz#packsta > > ck/puppet/modules/dnsmasq/ > > > > Open Questions: > > - Do we want to have predefined paths or should we targeted default paths > as given by the original file names? > > - Any other comment? > > > I have not looked deeper, but are the predefined paths required for the way > build system is currently looking for files? In my limited understanding of the Build System? Yes according to a first search of paths, but I might be wrong. I will leave to Wind River team to give the correct answer. > > [ List of Packages: Column 3 ] > > > > Nothing specific here but hardcoded URLs. > > > > Open Questions: > > - Use wget Vs curl? > > I would lean towards curl as it has better protocol support and supports > socks for proxy activity. Annotated > > > - Any other method to get the sources of the packages? Is it possible to > migrate to source RPMs? > > > > [ Security ] > > > > Open Discussion! We went through an initial package integrity verification, > see column F "GPG Key" but only 6 packages got their PGP key available in > their official repository source. > > > > Open Questions: > > - What is the best way to approach? > If there is a GPG key, then I think we should verify it, we could also > validate that what we currently have does not need to be updated (see > above) > > > - Specific question. Can we say Tarballs coming from Git sources are > naturally verified? > I think that makes sense, the problem with those tarballs is that we > can't have a checksum on them since they are created on the fly and the > time stamps change. Annotated + some tests in progress + some proposals From cesar.lara at intel.com Thu Jul 26 15:16:57 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Thu, 26 Jul 2018 15:16:57 +0000 Subject: [Starlingx-discuss] on our mirror proposal/milestone Message-ID: <0B566C62EC792145B40E29EFEBF1AB47104C15E9@fmsmsx104.amr.corp.intel.com> So i just want to get our story straight on the mirror milestone What we are working for, is to mirror the things that are a moving target, hard to get packages that are outside the centos repos and hosted by third party entities which are initially 9 packages. My assumption is that outside these 9 packages, everything else is reachable and we have reliable-ish sources for rpms Moving forward, the next wave of packages that we will plan to host, will be those packages who are not hosted on centOS repos, and if we need to add things to the intel hosted mirror due a third party or centOS repos retiring those packages, we will take those packages to our internal approval process to mirror those. please share your thoughts Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Thu Jul 26 15:23:50 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 26 Jul 2018 11:23:50 -0400 Subject: [Starlingx-discuss] download_mirrors.sh issues In-Reply-To: <886c47cc-855b-4ceb-4649-0f8e02b8b571@windriver.com> References: <886c47cc-855b-4ceb-4649-0f8e02b8b571@windriver.com> Message-ID: Proposal 2 Can we explore pulling old rpms from kojipkgs.fedoraproject.org. It seems to retain a history of old rpms far longer than the main repos.  This may allow use to remove many repos from StarlingX_3rd.repo --- snip --- cat koji_url.py #!/usr/bin/python import sys from rpmUtils.miscutils import splitFilename for filename in sys.argv[1:]:    (n, v, r, e, a) = splitFilename(filename)    print "https://kojipkgs.fedoraproject.org/packages/%s/%s/%s/%s/%s-%s-%s.%s.rpm" % (n,v,r,a,n,v,r,a) --- end snip --- e.g. ./koji_url.py epel-rpm-macros-7-18.noarch.rpm https://kojipkgs.fedoraproject.org/packages/epel-rpm-macros/7/18/noarch/epel-rpm-macros-7-18.noarch.rpm So a loop like this might catch a lot of missing rpms ... add some logging and error handling ... for missing_rpm in $(cat output/*missing*.txt); do     url=$(./koji_url.py $missing_rpm)     wget $url done Anything downloaded in this manner should be flagged for upgrade. We don't want to rely on it as a matter of routine.  Just a way to avoid people getting blocked on missing downloads. I suspect there is a lot of repos in StarlingX_3rd.repo that we don't need.  Also a lot of rpms currently listed under rpms_from_centos_3rd_parties.lst or rpms_from_3rd_parties.lst that could move back to rpms_from_centos_repo.lst.  i.e. Ideally they come from CentOS/EPEL (they aren't patches or customized), they just aged out. Scott On 18-07-25 03:33 PM, Scott Little wrote: > The http://epel.blizoo.mk/epel/ site is blocked by the security > gateway internal to Windriver.  Reason is 'potentially unwanted > programs'.  Is there an alternative to this site? > > What packages are being supplied by this site? > > Scott > > > On 18-07-25 02:32 PM, Arce Moreno, Abraham wrote: >>> I am following the instructions here: >>> >>> https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Software_Requir >>> >>> ements >> Thanks Al! >> >> A request for everybody, please continuously refresh the webpage due >> to the >> daily changes. The word "Temporal!" is used across this guide to >> highlight those patches >> needed to have a successful build. >> >> For branch Master, we are identifying those patches not merged as: >>      Temporal! Only Branch Master >> >> For branch m/2018.07, we are identifying those patches not merged as: >>      Temporal! Only Branch m/2018.07 >> >>> I have been un-successful in running the first setup actions for >>> doing an >>> official build, which is getting my mirror setup. >>> >>> I have all the latest commits in master for stx-tools. >> Our commit ids for today's build are: >> >> stx-tools branch master >> >>      $ git log --pretty=oneline -2 >>      f31f99ab91435c32c24a86efd2e697177074f4b7 Merge >> "policycoreutils-newrole was missing" >>      c3000c2936f56ad0257142d5c5bad3afc08c46cc Merge "upgrade >> linux-firmware RPM version"``` >> >> stx-tools branch m/2018.07 >> >>      $ git log --pretty=oneline -5 >>      88aadc543085e24e3c5df10ec63996b9f5551ff6 Merge "Package updates >> for new version of selinux-policy" into m/2018.07 >>     9c44470a2d6ff86a40f42c2b608e723c355ae38f Merge "Copy >> mock.cfg.proto and comps.xml files into cgcs-centos-repo" into >> m/2018.07``` >> >>> The first issue encountered was the macros.   This has already been >>> reported >>> here >>> https://storyboard.openstack.org/#!/story/2003072 >>> >>> I only had 4 entries listed as missing, until after I updated these >>> to the >>> following newer versions >>> >>> epel-rpm-macros-7-19.noarch.rpm >>> python2-rpm-macros-3-20.el7.noarch.rpm >>> python-rpm-macros-3-20.el7.noarch.rpm >>> python-srpm-macros-3-20.el7.noarch.rpm >> Also in this setup... >> >>> I don't know if that is the appropriate solution, since all this >>> allowed me to do >>> was fail to download some other things. >> We have 2 options: >> >> 1. a manual download of the packages >> 2. use of a tool, in review status [0] >> >>> Running download_mirror.sh again showed 140+ rpms as missing >>> >>> As an aside, sometimes the "missing"  log files are blank, even >>> though not all >>> components were downloaded.   I assume this is due to something >>> aborting. >> >>> Lighttpd  for example  is never being found. >> Same here: >> >>      Delta RPMs disabled because /usr/bin/applydeltarpm not installed. >>      warning: >> /var/cache/yum/x86_64/7/epel/packages/lighttpd-1.4.49-1.el7.x86_64.rpm: >> \ >>          Header V3 RSA/SHA256 Signature, key ID 352c64e5: NOKEY >>      Public key for lighttpd-1.4.49-1.el7.x86_64.rpm is not installed >> >>> By redirecting the script to log everything to a file, it shows this >>> particular >>> error message which may be a potential culprit >>> >>> "Loaded plugins: fastestmirror, ovl >>> http://epel.blizoo.mk/epel/7Server/x86_64/repodata/repomd.xml: >>> [Errno 14] >>> HTTP Error 403 - Forbidden >>> Trying other mirror. >>> To address this issue please refer to the below knowledge base article >>> https://access.redhat.com/solutions/69319 >>> If above article doesn't help to resolve this issue please create a >>> bug on >>> https://bugs.centos.org/ >>> One of the configured repositories failed (Starlingx- >>> epel.blizoo.mk_epel_7Server_x86_64 - >>> epel.blizoo.mk_epel_7Server_x86_64), >>> and yum doesn't have enough cached data to continue. At this point >>> the only >>> safe thing yum can do is fail." >>> >>> Does anyone know anything about this blizoo  repo?  Is it causing >>> anyone else >>> to not be able to download all the rpms,  or  is it unrelated to the >>> build setup >>> issues? >> Not seeing the blizoo repo failure in our side... internet connection >> is slow so will come back to >> you with more updates some time later. >> >> [0] https://review.openstack.org/#/c/585009/ >> >> _______________________________________________ >> 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 abraham.arce.moreno at intel.com Thu Jul 26 15:26:58 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Thu, 26 Jul 2018 15:26:58 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: <93814834B4855241994F290E959305C752F52DDC@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F52B57@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E049F3@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C752F52D91@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F52DDC@SHSMSX104.ccr.corp.intel.com> Message-ID: > Do we need collected-python package in mirror? In my build container, only 2 packages related to collectd [user at 867cb3cb6824 starlingx]$ sudo find /import -name *collectd* /import/mirrors/CentOS/stx-r1/CentOS/pike/Binary/noarch/puppet-collectd-5.1.0-2.4a3843cgit.el7.noarch.rpm /import/mirrors/CentOS/stx-r1/CentOS/pike/Binary/x86_64/collectd-5.7.1-2.el7.x86_64.rpm [user at 867cb3cb6824 starlingx]$ sudo find /import -name *collected* [user at 867cb3cb6824 starlingx]$ [user at 867cb3cb6824 starlingx]$ cd $MY_REPO [user at 867cb3cb6824 cgcs-root]$ repo grep collected-python [user at 867cb3cb6824 cgcs-root]$ repo grep collectd-python [user at 867cb3cb6824 cgcs-root]$ From hayde.martinez.landa at intel.com Thu Jul 26 15:27:05 2018 From: hayde.martinez.landa at intel.com (Martinez Landa, Hayde) Date: Thu, 26 Jul 2018 15:27:05 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide Message-ID: <2614F1A8-BAA1-48BC-9469-47C9F7316EAD@intel.com> Hi Abraham and Zhipeng, I'm also working on building from Master, I'll update you later with the results. From Eric.MacDonald at windriver.com Thu Jul 26 15:28:26 2018 From: Eric.MacDonald at windriver.com (MacDonald, Eric) Date: Thu, 26 Jul 2018 15:28:26 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: <93814834B4855241994F290E959305C752F52DDC@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F52B57@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E049F3@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C752F52D91@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F52DDC@SHSMSX104.ccr.corp.intel.com> Message-ID: <210898B96CA058408C55992CCAD98676B9E04AF2@ALA-MBD.corp.ad.wrs.com> I've been able to reproduce the log failure signature with a change to the collectd.conf file The issue is definitely related to the python library but it is packed in the collectd rpm. The one you call out is not in my working env. To further this investigation please provide the output of the following commands ls -lrt /usr/lib64/collectd/python.so ldd /usr/lib64/collectd/python.so Eric. > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: Thursday, July 26, 2018 10:45 AM > To: Liu, ZhipengS; MacDonald, Eric; Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io > Subject: RE: [RFC] StarlingX Developer Guide > Importance: High > > Do we need collected-python package in mirror? > > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: 2018年7月26日 22:25 > To: MacDonald, Eric ; Arce Moreno, Abraham > ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > Hi Eric, > > Thanks for your comment!! Could you help further check the error I saw below? > ============================================================================= > controller-0:/var/log/puppet# grep -R Error* > latest/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for > collectd failed! > latest/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 > /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: > Systemd start for collectd failed! > 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 > +0000 Systemd start for collectd failed! > 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 > +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: > Systemd start for collectd failed! > =============================================================================== > ontroller-0:~$ cat /var/log/daemon.log | grep collectd > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "network" successfully > loaded. > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in > /usr/lib64/collectd > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in > /usr/lib64/collectd > 2018-07-26T16:36:33.072 localhost collectd[25253]: info Automatically loading plugin "python" failed > with status 1. > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "threshold" successfully > loaded. > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "df" successfully loaded. > 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in > /usr/lib64/collectd > 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in > /usr/lib64/collectd > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Automatically loading plugin "python" failed > with status 1. > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Error: Reading the config file failed! > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Read the syslog for details. > 2018-07-26T16:36:33.073 localhost collectd[25253]: info = > 2018-07-26T16:36:33.100 localhost systemd[1]: notice collectd.service: main process exited, code=exited, > status=1/FAILURE > 2018-07-26T16:36:33.110 localhost systemd[1]: notice Unit collectd.service entered failed state. > 2018-07-26T16:36:33.110 localhost systemd[1]: warning collectd.service failed. > ====================================================================== > > Thanks! > Zhipeng > -----Original Message----- > From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] > Sent: 2018年7月26日 21:19 > To: Liu, ZhipengS ; Arce Moreno, Abraham ; > starlingx-discuss at lists.starlingx.io > Subject: RE: [RFC] StarlingX Developer Guide > > Looks like the manifest that configures and starts the collectd process is failing. > > Can you please execute the following commands on the host that shows collectd failing and publish the > errors you see that might reveal the cause. > > # Get the config error logs ... > sudo -i > cd /var/log/puppet ; fgrep -R Error * > > # get the collectd startup failure logs > cat /var/log/daemon.log | grep collectd > > one startup block is fine ; start to exit should show the error. > > Eric MacDonald > > > -----Original Message----- > > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > > Sent: Thursday, July 26, 2018 4:53 AM > > To: Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > > > Hi Abraham and Hayde > > > > I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. > > Start collectd failed. > > Could you help deploy ISO I built to see if it can work in your environment, thanks! > > > > Zhipeng > > > > > > -----Original Message----- > > From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] > > Sent: 2018年7月26日 10:13 > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > > > Hi again, > > > > Can someone please help test the process to build an ISO based on master using Developer Guide [0]? > > Please use Github page [1] as a documentation support. > > > > Requirements: > > > > - Repo status checked 7/25/2018 19:12 PST > > - stx-tools master branch > > - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros > > - Temporal! Changes, already in Developer Guide > > - RPM: selinux-policy-devel required > > https://review.openstack.org/#/c/585915 > > > > [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md > > > > _______________________________________________ > > 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 abraham.arce.moreno at intel.com Thu Jul 26 15:34:04 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Thu, 26 Jul 2018 15:34:04 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: <210898B96CA058408C55992CCAD98676B9E04AF2@ALA-MBD.corp.ad.wrs.com> References: <93814834B4855241994F290E959305C752F52B57@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E049F3@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C752F52D91@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F52DDC@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E04AF2@ALA-MBD.corp.ad.wrs.com> Message-ID: Here goes mine, Eric > I've been able to reproduce the log failure signature with a change to the > collectd.conf file > > The issue is definitely related to the python library but it is packed in the > collectd rpm. > The one you call out is not in my working env. > To further this investigation please provide the output of the following > commands > > ls -lrt /usr/lib64/collectd/python.so > ldd /usr/lib64/collectd/python.so A simplex configuration... controller-0:~$ ls -lrt /usr/lib64/collectd/python.so -rwxr-xr-x. 1 root root 76008 Apr 14 2017 /usr/lib64/collectd/python.so controller-0:~$ ldd /usr/lib64/collectd/python.so linux-vdso.so.1 => (0x00007ffee5b9d000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f53e9b8a000) libutil.so.1 => /lib64/libutil.so.1 (0x00007f53e9987000) libm.so.6 => /lib64/libm.so.6 (0x00007f53e9685000) libpython2.7.so.1.0 => /lib64/libpython2.7.so.1.0 (0x00007f53e926b000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f53e9067000) libc.so.6 => /lib64/libc.so.6 (0x00007f53e8c9a000) /lib64/ld-linux-x86-64.so.2 (0x00007f53e9fb8000) controller-0:~$ controller-0:~$ uname -a Linux controller-0 3.10.0-862.6.3.el7.35.tis.x86_64 #1 SMP PREEMPT Fri Jul 20 15:55:20 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux controller-0:~$ From scott.little at windriver.com Thu Jul 26 15:33:42 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 26 Jul 2018 11:33:42 -0400 Subject: [Starlingx-discuss] on our mirror proposal/milestone In-Reply-To: <0B566C62EC792145B40E29EFEBF1AB47104C15E9@fmsmsx104.amr.corp.intel.com> References: <0B566C62EC792145B40E29EFEBF1AB47104C15E9@fmsmsx104.amr.corp.intel.com> Message-ID: <982be81b-544e-1c7f-4fc5-151ede9b1f1a@windriver.com> I'd caution you that the list of 'hard to get' packages is ever changing due to both internal and external factors.  Certainly none of the EPEL content is safe. In particular, for StarlingX releases, you'll probably want to snapshot all packages that went into the release. Scott On 18-07-26 11:16 AM, Lara, Cesar wrote: > > So i just want to get our story straight on the mirror milestone > > What we are working for, is to mirror the things that are a moving > target, hard to get packages that are outside the centos repos and > hosted by third party entities which are initially 9 packages. > > My assumption is that outside these 9 packages, everything else is > reachable and we have reliable-ish sources for rpms > > Moving forward, the next wave of packages that we will plan to host, > will be those packages who are not hosted on centOS repos, > > and > > if we need to add things to the intel hosted mirror due a third party > or centOS repos retiring those packages, we will take those packages > to our internal approval process to mirror those. > > please share your thoughts > > Regards > > *//* > > */Cesar Lara/* > > Software Engineering Manager > > OpenSource Technology Center > > > > _______________________________________________ > 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 chris.friesen at windriver.com Thu Jul 26 15:36:31 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Thu, 26 Jul 2018 09:36:31 -0600 Subject: [Starlingx-discuss] download_mirrors.sh issues In-Reply-To: References: <886c47cc-855b-4ceb-4649-0f8e02b8b571@windriver.com> <5B58E009.505@windriver.com> Message-ID: <5B59EA7F.6050409@windriver.com> On 07/26/2018 08:47 AM, Eslimi, Dariush wrote: > Chris, > > I tried your suggested mirror, and it is failing from Ottawa : > > http://mirror.csclub.uwaterloo.ca/fedora/epel/7Server/x86_64/repodata/15643babbd68ee80c284c83a6474b9af954efc4c8daaf78cca45ef3fb79a8630-primary.xml.gz: [Errno 12] Timeout on http://mirror.csclub.uwaterloo.ca/fedora/epel/7Server/x86_64/repodata/15643babbd68ee80c284c83a6474b9af954efc4c8daaf78cca45ef3fb79a8630-primary.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds') Where did you get that filename from? Under http://mirror.csclub.uwaterloo.ca/fedora/epel/7Server/x86_64/repodata I don't see that file. The current xxx-primary.xml.gz file is b58ae8f180ca61fab3d1d6caf1f2312628ec7eb0bb0cf621df6a8434f1c7368e-primary.xml.gz I confirmed the filename at another mirror. Looking at http://epel.blizoo.mk/epel/7Server/x86_64/repodata/ it seems like they also don't have your filename, but it looks like they're stale--the files are timestamped June 25 2017 while the other mirrors I checked were both synced this morning. Chris From dtroyer at gmail.com Thu Jul 26 15:42:10 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 26 Jul 2018 10:42:10 -0500 Subject: [Starlingx-discuss] Firewalls and git URLs In-Reply-To: <70FA85CF-3089-4426-A262-CB81CB9785EA@intel.com> References: <70FA85CF-3089-4426-A262-CB81CB9785EA@intel.com> Message-ID: On Thu, Jul 26, 2018 at 9:52 AM, Hu, Yong wrote: > At my home, without VPN or corporate network proxy, in my laptop I can access https://git.starlingx.io/ > And also, I can do "git clone", for example, git clone https://git.starlingx.io/stx-config Thank you Yong! dt -- Dean Troyer dtroyer at gmail.com From Dariush.Eslimi at windriver.com Thu Jul 26 15:43:19 2018 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Thu, 26 Jul 2018 15:43:19 +0000 Subject: [Starlingx-discuss] download_mirrors.sh issues In-Reply-To: <5B59EA7F.6050409@windriver.com> References: <886c47cc-855b-4ceb-4649-0f8e02b8b571@windriver.com> <5B58E009.505@windriver.com> <5B59EA7F.6050409@windriver.com> Message-ID: Filenames comes out .lst files. Dariush -----Original Message----- From: Friesen, Chris Sent: July-26-18 11:37 AM To: Eslimi, Dariush; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] download_mirrors.sh issues On 07/26/2018 08:47 AM, Eslimi, Dariush wrote: > Chris, > > I tried your suggested mirror, and it is failing from Ottawa : > > http://mirror.csclub.uwaterloo.ca/fedora/epel/7Server/x86_64/repodata/ > 15643babbd68ee80c284c83a6474b9af954efc4c8daaf78cca45ef3fb79a8630-prima > ry.xml.gz: [Errno 12] Timeout on > http://mirror.csclub.uwaterloo.ca/fedora/epel/7Server/x86_64/repodata/ > 15643babbd68ee80c284c83a6474b9af954efc4c8daaf78cca45ef3fb79a8630-prima > ry.xml.gz: (28, 'Operation too slow. Less than 1000 bytes/sec > transferred the last 30 seconds') Where did you get that filename from? Under http://mirror.csclub.uwaterloo.ca/fedora/epel/7Server/x86_64/repodata I don't see that file. The current xxx-primary.xml.gz file is b58ae8f180ca61fab3d1d6caf1f2312628ec7eb0bb0cf621df6a8434f1c7368e-primary.xml.gz I confirmed the filename at another mirror. Looking at http://epel.blizoo.mk/epel/7Server/x86_64/repodata/ it seems like they also don't have your filename, but it looks like they're stale--the files are timestamped June 25 2017 while the other mirrors I checked were both synced this morning. Chris From dtroyer at gmail.com Thu Jul 26 15:50:37 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 26 Jul 2018 10:50:37 -0500 Subject: [Starlingx-discuss] on our mirror proposal/milestone In-Reply-To: <982be81b-544e-1c7f-4fc5-151ede9b1f1a@windriver.com> References: <0B566C62EC792145B40E29EFEBF1AB47104C15E9@fmsmsx104.amr.corp.intel.com> <982be81b-544e-1c7f-4fc5-151ede9b1f1a@windriver.com> Message-ID: On Thu, Jul 26, 2018 at 10:33 AM, Scott Little wrote: > I'd caution you that the list of 'hard to get' packages is ever changing due > to both internal and external factors. Certainly none of the EPEL content > is safe. > > In particular, for StarlingX releases, you'll probably want to snapshot all > packages that went into the release. Exactly. Scott, is there currently a record somewhere in the build tree or ISO of what was actually used? I suppose in the ISO we can just look at the embedded repo, correct? Related, is there anything currently recorded regarding the branch/commit of the git repos for a particular build? What I think we might want to re-create a specific build might be a re-written repo manifest (default.xml) that includes tags or commit SHAs... dt -- Dean Troyer dtroyer at gmail.com From chris.friesen at windriver.com Thu Jul 26 15:56:04 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Thu, 26 Jul 2018 09:56:04 -0600 Subject: [Starlingx-discuss] download_mirrors.sh issues In-Reply-To: <988AB878-C0E2-4D8B-BBEA-753ED29F2DEA@intel.com> References: <886c47cc-855b-4ceb-4649-0f8e02b8b571@windriver.com> <5B58E009.505@windriver.com> <988AB878-C0E2-4D8B-BBEA-753ED29F2DEA@intel.com> Message-ID: <5B59EF14.1070105@windriver.com> On 07/25/2018 05:13 PM, Hu, Yong wrote: > Hi Chris and Scott, > > These following 4 packages used to be downloaded from this site: > > http://epel.blizoo.mk/epel/7/SRPMS/l/lighttpd-1.4.45-1.el7.src.rpm > http://epel.blizoo.mk/epel/7Server/x86_64/p/python2-msgpack-0.4.8-1.el7.x86_64.rpm > http://epel.blizoo.mk/epel/7Server/x86_64/p/python2-pysocks-1.5.7-1.el7.noarch.rpm > http://epel.blizoo.mk/epel/7Server/x86_64/p/python-pyngus-2.2.1-1.el7.noarch.rpm For what it's worth, all four of these seem to still work for me, including from windriver build machines. Chris From sgw at linux.intel.com Thu Jul 26 15:58:11 2018 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 26 Jul 2018 08:58:11 -0700 Subject: [Starlingx-discuss] StarlingX: Tar Compressed Files Repository Restructuring In-Reply-To: References: <93814834B4855241994F290E959305C752F51B22@SHSMSX104.ccr.corp.intel.com> <52dd7eca-a630-71af-ab70-aae4c0e5ad7d@linux.intel.com> Message-ID: <8256e19b-3cdd-0581-1b3d-02a9aa376dd4@linux.intel.com> On 07/26/2018 08:09 AM, Arce Moreno, Abraham wrote: > Thanks Saul! > >>> Just 2 proposals. >>> 1) Every time, when I run download_mirror, it will always download mvn >> which will take around 1~2 hours. >>> Could you add a check in the script that if mvn.repo.tgz exists, do >>> not try to download it again. Same for other package >>> 2) When download list changed, the script only downloads added packages >> and also removes the ones of old versions that we do not used anymore. >>> >> I was thinking we could try to incorporate somekind of checksum >> information, in order to validate the downloads are correct and complete. > > Is this harcoded checksum checking the same way Yocto does as part of the recipes? > Can we have the checksum incorporated in our existing text file as another column? > Do we need another file? > >>> The call sequence under CentOS Mirror Tools [2] is as follows ending in >> executing our tarball-dl.sh: >>> >>> 1 download_mirror.sh >>> 1.1 dl_rpms.sh >>> 1.2 dl_other_from_centos_repo.sh >>> 1.3 tarball-dl.sh >>> >>> Open Questions: >>> - Should we keep this script being called from download_mirror.sh? >>> - Should we keep this file being written as shell script? >>> - Any comment based on midterm / long term changes? >>> - Any other comment? >>> >> So the script is doing 3 things, I think there should be more checking as to >> what exists and what's needed. The RPM fetching can be done independant >> of the tarball, so that we can use a query of the repos instead of full >> download. > > How about starting by splitting our download of tarballs from the rpms script? > this will allow us to track independently the 2 efforts and avoid having a failure > in the download of one because of the other. > > Taking your idea and Zhipeng's, how about something like the steps below? > This will be also reflected in our Developer Guide: > > 1 "Step Download RPMs" > download_mirror.sh > 1.1 dl_rpms.sh > 1.2 dl_other_from_centos_repo.sh Can you do an existence check here also and use the repoquery or is that already part of dl_rpms? Can these scripts be merged into one that just uses 2 different input information? > 2 "Step Download Tarballs" > tarball-dl.sh > 2.1 what exists > 2.2 verify .. checksum? > 2.3 continue / download > 2.4 if download? verify .. checksum ? > >> Another thought is to provide the option to point this at somekind of >> company based mirror, so that each larger company could keep an internal >> mirror, but smaller organizations will hit the external sources. > > The "Step Download Tarball" can allow us to build that repo and same script to > verify its integrity, complementing with Zhipeng's idea to download new versions > or remove old ones. > Sounds good, can we do the same for the RPM repo, not just tarballs? Sau! >>> A special character "!" is used at the beginning of 6 package file names >> denoting they require special handling is required: additional steps besides >> the common process including but not limited to remove text from some files, >> use only one directory, etc: >>> >>> - integrity-kmod-668a8270.tar.gz >>> - mariadb-10.1.28.tar.gz >>> - mvn.repo.tgz >>> - qat1.7.upstream.l.1.0.3-42.tar.gz >>> - tpm-kmod-668a8270.tar.gz >>> - tss2-930.tar.gz >>> >>> Open Questions: >>> - Any specific method to handle these 6 packages? >>> - Any other comment? >>> >> This one is harder, since each of these is a different special case to deal with >> git or multiple downloads (mvn). Short of creating some sort of "plugin" >> mechanism that handles each special case. >> > > I will ask for feedback to our experts about how this "plugin" can be achieved. > This includes suggestion from Zhipeng related to mvn in previous email thread. > >>> Our build system uses defined paths after the Tarball package filename >>> is decompressed, see Columns H " 'Directory Name Cgcs-Dl" and Column I >>> " 'Directory Name tarball-dl.sh" for a >>> comparison: >>> >>> - It could be the same after it is decompressed from the original file >>> - dpkg_1.18.24.tar.xz#dpkg-1.18.24 >>> - It could use a different name after it is decompressed from the original file >>> - !integrity-kmod-668a8270.tar.gz#integrity >>> - >>> puppet-dnsmasq- >> cff07e90890662972c97684a2baee964f68ff3ed.tar.gz#packsta >>> ck/puppet/modules/dnsmasq/ >>> >>> Open Questions: >>> - Do we want to have predefined paths or should we targeted default paths >> as given by the original file names? >>> - Any other comment? >>> >> I have not looked deeper, but are the predefined paths required for the way >> build system is currently looking for files? > > In my limited understanding of the Build System? Yes according to a first search of paths, > but I might be wrong. I will leave to Wind River team to give the correct answer. > >>> [ List of Packages: Column 3 ] >>> >>> Nothing specific here but hardcoded URLs. >>> >>> Open Questions: >>> - Use wget Vs curl? >> >> I would lean towards curl as it has better protocol support and supports >> socks for proxy activity. > > Annotated > >> >>> - Any other method to get the sources of the packages? Is it possible to >> migrate to source RPMs? >>> >>> [ Security ] >>> >>> Open Discussion! We went through an initial package integrity verification, >> see column F "GPG Key" but only 6 packages got their PGP key available in >> their official repository source. >>> >>> Open Questions: >>> - What is the best way to approach? >> If there is a GPG key, then I think we should verify it, we could also >> validate that what we currently have does not need to be updated (see >> above) >> >>> - Specific question. Can we say Tarballs coming from Git sources are >> naturally verified? >> I think that makes sense, the problem with those tarballs is that we >> can't have a checksum on them since they are created on the fly and the >> time stamps change. > > Annotated + some tests in progress + some proposals > From sgw at linux.intel.com Thu Jul 26 16:16:04 2018 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 26 Jul 2018 09:16:04 -0700 Subject: [Starlingx-discuss] on our mirror proposal/milestone In-Reply-To: References: <0B566C62EC792145B40E29EFEBF1AB47104C15E9@fmsmsx104.amr.corp.intel.com> <982be81b-544e-1c7f-4fc5-151ede9b1f1a@windriver.com> Message-ID: <2b944e06-3948-9ae1-7a63-67b21603bd03@linux.intel.com> On 07/26/2018 08:50 AM, Dean Troyer wrote: > On Thu, Jul 26, 2018 at 10:33 AM, Scott Little > wrote: >> I'd caution you that the list of 'hard to get' packages is ever changing due >> to both internal and external factors. Certainly none of the EPEL content >> is safe. >> >> In particular, for StarlingX releases, you'll probably want to snapshot all >> packages that went into the release. > > Exactly. Scott, is there currently a record somewhere in the build > tree or ISO of what was actually used? I suppose in the ISO we can > just look at the embedded repo, correct? > > Related, is there anything currently recorded regarding the > branch/commit of the git repos for a particular build? What I think > we might want to re-create a specific build might be a re-written repo > manifest (default.xml) that includes tags or commit SHAs... > Yes, getting a good manifest of the tarball related items would be the right thing to do. I know we have mentioned the shifting sands of RPMs, should we also be concerned about any of the tarballs disappearing (due to version change) or git repos deleting branches that we have used? Sau! > dt > From bruce.e.jones at intel.com Thu Jul 26 16:20:36 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 26 Jul 2018 16:20:36 +0000 Subject: [Starlingx-discuss] on our mirror proposal/milestone In-Reply-To: <2b944e06-3948-9ae1-7a63-67b21603bd03@linux.intel.com> References: <0B566C62EC792145B40E29EFEBF1AB47104C15E9@fmsmsx104.amr.corp.intel.com> <982be81b-544e-1c7f-4fc5-151ede9b1f1a@windriver.com> <2b944e06-3948-9ae1-7a63-67b21603bd03@linux.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB567ED2@fmsmsx117.amr.corp.intel.com> We might want to use the technique that the Clear Linux team uses. When they create a new release they create a new yum repo with all the contents hard linked to the previous repo. Anything that is changed in the repo breaks the links. This way they have exactly what they released for any release and space utilization is minimal. brucej -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Thursday, July 26, 2018 9:16 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] on our mirror proposal/milestone On 07/26/2018 08:50 AM, Dean Troyer wrote: > On Thu, Jul 26, 2018 at 10:33 AM, Scott Little > wrote: >> I'd caution you that the list of 'hard to get' packages is ever >> changing due to both internal and external factors. Certainly none >> of the EPEL content is safe. >> >> In particular, for StarlingX releases, you'll probably want to >> snapshot all packages that went into the release. > > Exactly. Scott, is there currently a record somewhere in the build > tree or ISO of what was actually used? I suppose in the ISO we can > just look at the embedded repo, correct? > > Related, is there anything currently recorded regarding the > branch/commit of the git repos for a particular build? What I think > we might want to re-create a specific build might be a re-written repo > manifest (default.xml) that includes tags or commit SHAs... > Yes, getting a good manifest of the tarball related items would be the right thing to do. I know we have mentioned the shifting sands of RPMs, should we also be concerned about any of the tarballs disappearing (due to version change) or git repos deleting branches that we have used? Sau! > dt > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Thu Jul 26 16:28:46 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 26 Jul 2018 16:28:46 +0000 Subject: [Starlingx-discuss] Notes from this week's project meeting Message-ID: <9A85D2917C58154C960D95352B22818BAB567FBE@fmsmsx117.amr.corp.intel.com> StarlingX Status https://etherpad.openstack.org/p/stx-status Agenda & notes for the 7/25 Meeting Recording: https://zoom.us/recording/share/5ZBGWUSeTw5oNOESL-6-GThAgwid3nxJ_snyMeTvVWOwIumekTziMw * Hosting binary files - status update - it appears that we have a path going forward for Intel to do this. More work needed to resolve some process issues. * restructuring status? Done internally, waiting on build stability... * planning update * Bug Scrub! Set a separate meeting (with the Cores, with Test) to review and prioritize bugs? AR Bruce lead discussion on the email list. o All bugs: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.bug o stx.2018.08 bugs: https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.bug&tags=stx.2018.08 o stx.2018.11 bugs:https://storyboard.openstack.org/#!/story/list?status=active&project_group_id=86&tags=stx.bug&tags=stx.2018.11 * Branch build and test status o WR still can't build from the scripts - Intel reports some success. o Changes have been made to update the repo file to Centos 7.5 but we're not pulling any packages from that. o Can WR start doing builds without using the their internal mirror? o Please post build related checkins and updates to the mailing list. Please over-communicate. Use #starlingX!!! * ARs from previous meetings o IRC channel logging code review in progress - This has been merged! o Bruce to post starlingx intro slidedeck to wiki - email thread in progress, needs a ping. AR Bruce to post a PDF to the wiki. * Virtual Box deployment - bug only open internally @ Intel * Release process & reno tool - do we apply this to all stx projects? Start with stx-tools. Will take some work to fit our code into the expected framework. Abe to write some stories for stx.releases. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Jul 26 16:36:37 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 26 Jul 2018 16:36:37 +0000 Subject: [Starlingx-discuss] Core team meeting minutes 8/26/2018 Message-ID: <9A85D2917C58154C960D95352B22818BAB567FEF@fmsmsx117.amr.corp.intel.com> StarlingX Core Team meeting agenda and notes This file is: https://etherpad.openstack.org/p/stx-cores Agenda & notes for the 7/26 call: * Priority of Python2 work - to be discussed next week * Build system follow up - Bruce o Build the OS independently from everything else? Set up a generic CentOS 7.5 build, then add our patches? o Can the WR internal build mirror be posted on S3? How would we keep it secure? o We also need to improve the process of adding new dependencies - new commits require new mirror content * e.g. 35 pending commits need 190 new packages added to the mirror. o Work is in progress to enable per-company mirrors - might be best short term solution * stx-gui plan - Ian o This review in gerrit (584201) was not fully visible in the community. It is now. Eddie has posted reviews and updated them. He may have posted an incorrect link. Dean recommends we merge them. Request for the WR Horizon prime (Tyler) to join the review. Official StarlingX art assets have been requested and will be available to us shortly (EO July). * Release planning (using release tags) - Bruce * Review draft roadmap - Bruce to send out for review * Bug scrub process o WR to scrub internally. Many of the currently open bugs have fixes in progress. * Wind River commit backlog - size, scope, schedule o First wave is through. Integration of gnochi - replaces ceilometer. Docker / K8S support too. Then the restructuring. Then a next wave including initial containerized services and the beginnings of project de-coupling. * SDL update o An internal Intel security review generated more work for the team - additional threats to mitigate. Yong please share the list with the Core teams privately. * Agenda for F2F in Ottawa o Strategic discussions e.g. Arkaino o Working in the open o Intel's requirements & plans o Wind River's requirements & plans o Jointly agreed roadmap ? Big ticket items - rebase OpenStack, Python3, OS Independence o Test strategy / release strategy / release planning o Security team and other subteams - review proposal, refine o Ian to consolidate and send out an updated agenda -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Thu Jul 26 17:07:35 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 26 Jul 2018 13:07:35 -0400 Subject: [Starlingx-discuss] on our mirror proposal/milestone In-Reply-To: References: <0B566C62EC792145B40E29EFEBF1AB47104C15E9@fmsmsx104.amr.corp.intel.com> <982be81b-544e-1c7f-4fc5-151ede9b1f1a@windriver.com> Message-ID: <0d1c436f-6a01-c15f-aff7-ee39e7932782@windriver.com> On 18-07-26 11:50 AM, Dean Troyer wrote: > On Thu, Jul 26, 2018 at 10:33 AM, Scott Little > wrote: >> I'd caution you that the list of 'hard to get' packages is ever changing due >> to both internal and external factors. Certainly none of the EPEL content >> is safe. >> >> In particular, for StarlingX releases, you'll probably want to snapshot all >> packages that went into the release. > Exactly. Scott, is there currently a record somewhere in the build > tree or ISO of what was actually used? I suppose in the ISO we can > just look at the embedded repo, correct? [SL] $MY_WORKSPACE/export/dist/isolinux/Packages/ contains all the packages added to the iso, excluding anything unique to the initrd (just anaconda think). There is no single record of rpms required by to satisfy all the BuildRequires.  I'de try a query like this cd $MY_WORKSPACE grep -i 'Installing :' --no-filename */results/jenkins-CGCS_6.0_Host-2018-07-19_11-30-21-tis-r6-pike-std/*/root.log | awk '{ print $5 }' | sort --unique For both queries, some rpms will by unique to StarlingX, or contain release values suggesting it's stx patched. > > Related, is there anything currently recorded regarding the > branch/commit of the git repos for a particular build? What I think > we might want to re-create a specific build might be a re-written repo > manifest (default.xml) that includes tags or commit SHAs... [SL] I do have code to do that in our jenkins build jobs.  I can move it into the build scripts if we have a story to cover it. > > dt > From Dariush.Eslimi at windriver.com Thu Jul 26 17:33:22 2018 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Thu, 26 Jul 2018 17:33:22 +0000 Subject: [Starlingx-discuss] download_mirrors.sh issues In-Reply-To: <5B59EF14.1070105@windriver.com> References: <886c47cc-855b-4ceb-4649-0f8e02b8b571@windriver.com> <5B58E009.505@windriver.com> <988AB878-C0E2-4D8B-BBEA-753ED29F2DEA@intel.com> <5B59EF14.1070105@windriver.com> Message-ID: Ok, for me "bash download_mirror.sh" script is failing to get the file : failure: repodata/repomd.xml from Starlingx-epel.blizoo.mk_epel_7Server_x86_64: [Errno 256] No more mirrors to try. http://epel.blizoo.mk/epel/7Server/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden fg tail: cannot open 'downloadfg' for reading: No such file or directory tail: no files remaining But the same file can be downloaded from same docker image using wget: [root at 90df3cd4e352 localdisk]# wget http://epel.blizoo.mk/epel/7Server/x86_64/repodata/repomd.xml --2018-07-26 17:29:09-- http://epel.blizoo.mk/epel/7Server/x86_64/repodata/repomd.xml Resolving epel.blizoo.mk (epel.blizoo.mk)... 78.157.16.91 Connecting to epel.blizoo.mk (epel.blizoo.mk)|78.157.16.91|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 4380 (4.3K) [text/xml] Saving to: 'repomd.xml.1' 100%[===================================================================================================================================================================================================>] 4,380 --.-K/s in 0s 2018-07-26 17:29:09 (97.1 MB/s) - 'repomd.xml.1' saved [4380/4380] Dariush -----Original Message----- From: Chris Friesen [mailto:chris.friesen at windriver.com] Sent: July-26-18 11:56 AM To: Hu, Yong; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] download_mirrors.sh issues On 07/25/2018 05:13 PM, Hu, Yong wrote: > Hi Chris and Scott, > > These following 4 packages used to be downloaded from this site: > > http://epel.blizoo.mk/epel/7/SRPMS/l/lighttpd-1.4.45-1.el7.src.rpm > http://epel.blizoo.mk/epel/7Server/x86_64/p/python2-msgpack-0.4.8-1.el > 7.x86_64.rpm > http://epel.blizoo.mk/epel/7Server/x86_64/p/python2-pysocks-1.5.7-1.el > 7.noarch.rpm > http://epel.blizoo.mk/epel/7Server/x86_64/p/python-pyngus-2.2.1-1.el7. > noarch.rpm For what it's worth, all four of these seem to still work for me, including from windriver build machines. Chris _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Al.Bailey at windriver.com Thu Jul 26 18:27:55 2018 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Thu, 26 Jul 2018 18:27:55 +0000 Subject: [Starlingx-discuss] download_mirrors.sh issues References: Message-ID: After wiping the output folder and running the download_mirror.sh command with the updated repo, there were still 24 rpms missing. Some of those (like docker-ce) did not make any sense, so I looked into it. 1) StarlingX_3rd.repo is only copied to /etc/yum.repos.d/ when the docker image is created. It is removed by the download_mirror.sh script. If you run that script a second time to try to update your mirror, all the 3rd party repos are missing and it will not be able to find them. Re-copying StarlingX_3rd.repo to /etc/yum.repos.d/ at the beginning of download_mirror.sh resolves this. I think the StarlingX.repo should also get re-copied, in case that file is altered by a commit, and you wish to re-run the script to re-update the mirror. 2) 3 of the missing entries are macros. My update for https://review.openstack.org/#/c/585861/ did not fix them. yum seems to be able to find version 21, so I will update to that version. Al -----Original Message----- From: Bailey, Henry Albert (Al) Sent: Thursday, July 26, 2018 10:24 AM To: starlingx-discuss at lists.starlingx.io Subject: RE: download_mirrors.sh issues Hi Abraham, The patch is available here. https://review.openstack.org/#/c/586230/ This seems to fix almost all the missing rpms. There are less than 20 missing now, some of which may be related to the blizoo repo . I am recreating a fresh mirror now, and I will try to track down the remaining missing rpms. Al -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Wednesday, July 25, 2018 5:00 PM To: Arce Moreno, Abraham; Bailey, Henry Albert (Al); starlingx-discuss at lists.starlingx.io Subject: RE: download_mirrors.sh issues > > I will re-run the complete download routine and see if this fixes all > > the remaining (non src) issues. > > Is it possible you submit a patch if it works for you? > > Adopting the over communication approach, I am logging all the steps and > output in this url [0]. Not using etherpad to have a faster edit / easy > formatting. > > [0] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md Afternoon update on StarlingX Compilation Master Branch started today morning. stx-tools branch master $ git log --pretty=oneline -2 f31f99ab91435c32c24a86efd2e697177074f4b7 Merge "policycoreutils-newrole was missing" c3000c2936f56ad0257142d5c5bad3afc08c46cc Merge "upgrade linux-firmware RPM version" Taking StarlingX Developer Guide [0] as an input and a temporal Github page [1] as an output. [1] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [0] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md From scott.little at windriver.com Thu Jul 26 18:42:46 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 26 Jul 2018 14:42:46 -0400 Subject: [Starlingx-discuss] download_mirrors.sh issues In-Reply-To: References: Message-ID: setting enabled=0 on the epel.blizoo.mk repos will prevent the deletion of StarlingX_3rd.repo On 18-07-26 02:27 PM, Bailey, Henry Albert (Al) wrote: > After wiping the output folder and running the download_mirror.sh command with the updated repo, there were still 24 rpms missing. > Some of those (like docker-ce) did not make any sense, so I looked into it. > > 1) StarlingX_3rd.repo is only copied to /etc/yum.repos.d/ when the docker image is created. It is removed by the download_mirror.sh script. > If you run that script a second time to try to update your mirror, all the 3rd party repos are missing and it will not be able to find them. > Re-copying StarlingX_3rd.repo to /etc/yum.repos.d/ at the beginning of download_mirror.sh resolves this. > I think the StarlingX.repo should also get re-copied, in case that file is altered by a commit, and you wish to re-run the script to re-update the mirror. > > 2) 3 of the missing entries are macros. My update for https://review.openstack.org/#/c/585861/ did not fix them. yum seems to be able to find version 21, so I will update to that version. > > Al > > -----Original Message----- > From: Bailey, Henry Albert (Al) > Sent: Thursday, July 26, 2018 10:24 AM > To: starlingx-discuss at lists.starlingx.io > Subject: RE: download_mirrors.sh issues > > Hi Abraham, > The patch is available here. https://review.openstack.org/#/c/586230/ > This seems to fix almost all the missing rpms. > There are less than 20 missing now, some of which may be related to the blizoo repo . > > I am recreating a fresh mirror now, and I will try to track down the remaining missing rpms. > > Al > > -----Original Message----- > From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] > Sent: Wednesday, July 25, 2018 5:00 PM > To: Arce Moreno, Abraham; Bailey, Henry Albert (Al); starlingx-discuss at lists.starlingx.io > Subject: RE: download_mirrors.sh issues > >>> I will re-run the complete download routine and see if this fixes all >>> the remaining (non src) issues. >> Is it possible you submit a patch if it works for you? >> >> Adopting the over communication approach, I am logging all the steps and >> output in this url [0]. Not using etherpad to have a faster edit / easy >> formatting. >> >> [0] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md > Afternoon update on StarlingX Compilation Master Branch started today morning. > > stx-tools branch master > > $ git log --pretty=oneline -2 > f31f99ab91435c32c24a86efd2e697177074f4b7 Merge "policycoreutils-newrole was missing" > c3000c2936f56ad0257142d5c5bad3afc08c46cc Merge "upgrade linux-firmware RPM version" > > Taking StarlingX Developer Guide [0] as an input and a temporal Github page [1] as an output. > > [1] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > [0] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Thu Jul 26 19:00:48 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 26 Jul 2018 15:00:48 -0400 Subject: [Starlingx-discuss] download_mirrors.sh issues In-Reply-To: References: Message-ID: <209520f9-37aa-98c9-96ca-d73c6e9d3bb8@windriver.com> Ignore that.  StarlingX_3rd.repo is explicitly deleted in download_mirror.sh.  never got that far do to a syntax error i introduced. On 18-07-26 02:42 PM, Scott Little wrote: > setting enabled=0 on the epel.blizoo.mk repos will prevent the > deletion of StarlingX_3rd.repo > > On 18-07-26 02:27 PM, Bailey, Henry Albert (Al) wrote: >> After wiping the output folder and running the download_mirror.sh >> command with the updated repo, there were still 24 rpms missing. >> Some of those (like docker-ce) did not make any sense, so I looked >> into it. >> >> 1)  StarlingX_3rd.repo  is only copied to   /etc/yum.repos.d/ when >> the docker image is created.    It is removed by the >> download_mirror.sh  script. >> If you run that script a second time  to try to update your mirror,  >> all the 3rd party repos are missing and it will not be able to find >> them. >> Re-copying    StarlingX_3rd.repo to  /etc/yum.repos.d/  at the >> beginning of  download_mirror.sh   resolves this. >> I think the StarlingX.repo should also get re-copied, in case that >> file is altered by a commit, and you wish to re-run the script to >> re-update the mirror. >> >> 2)  3 of the missing entries are macros. My update for >> https://review.openstack.org/#/c/585861/   did not fix them. yum >> seems to be able to find version 21, so I will update to that version. >> >> Al >> >> -----Original Message----- >> From: Bailey, Henry Albert (Al) >> Sent: Thursday, July 26, 2018 10:24 AM >> To: starlingx-discuss at lists.starlingx.io >> Subject: RE: download_mirrors.sh issues >> >> Hi Abraham, >>    The patch is available here. https://review.openstack.org/#/c/586230/ >> This seems to fix almost all the missing rpms. >> There are less than 20 missing now, some of which may be related to >> the blizoo repo . >> >> I am recreating a fresh mirror now, and I will try to track down the >> remaining missing rpms. >> >> Al >> >> -----Original Message----- >> From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] >> Sent: Wednesday, July 25, 2018 5:00 PM >> To: Arce Moreno, Abraham; Bailey, Henry Albert (Al); >> starlingx-discuss at lists.starlingx.io >> Subject: RE: download_mirrors.sh issues >> >>>> I will re-run the complete download routine and see if this fixes all >>>> the remaining (non src) issues. >>> Is it possible you submit a patch if it works for you? >>> >>> Adopting the over communication approach, I am logging all the steps >>> and >>> output in this url [0]. Not using etherpad to have a faster edit / easy >>> formatting. >>> >>> [0] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md >> Afternoon update on StarlingX Compilation Master Branch started today >> morning. >> >> stx-tools branch master >> >>      $ git log --pretty=oneline -2 >>      f31f99ab91435c32c24a86efd2e697177074f4b7 Merge >> "policycoreutils-newrole was missing" >>      c3000c2936f56ad0257142d5c5bad3afc08c46cc Merge "upgrade >> linux-firmware RPM version" >> >> Taking StarlingX Developer Guide [0] as an input and a temporal >> Github page [1] as an output. >> >> [1] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide >> [0] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Don.Penney at windriver.com Thu Jul 26 19:46:15 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 26 Jul 2018 19:46:15 +0000 Subject: [Starlingx-discuss] download_mirror.sh using bash -e causes early exit Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA2508C7@ALA-MBD.corp.ad.wrs.com> Hi folks, I was just running a fresh download_mirror.sh execution and ran into a problem. I run it as follows, to get timing info and record output: time ./download_mirror.sh 2>&1 | tee dpenney.out The script exited here: --> run: sudo -E yumdownloader -q -C --source python-voluptuous-0.8.9-1.el7 Looking for python-voluptuous-0.8.9-1.el7.src.rpm done!! finish 1st round of RPM downloading successfully! ERROR: -------RPMs missing 6 in yumdownloader with L1 match --------------- real 84m3.238s user 62m49.391s sys 9m46.608s It seemed like an odd place to finish "1st round", so I took a look around there, checking various timestamps to try to see where it quit, and found the last command executed was this line: ## verify all RPMs SRPMs we download for the GPG keys find ./output -type f -name "*.rpm" | xargs rpm -K | grep -i "MISSING KEYS" > ./rpm-gpg-key-missing.txt Because I had no missing keys, the last piped command returned a non-zero status. And since this script is launched with "bash -e" on the first line, and I ran the script directly instead of "bash download_mirror.sh", the script exited at this point. The other download scripts use "bash -e" here as well. Since these are called directly from download_mirror.sh, they could be exiting early silently. Cheers, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Thu Jul 26 19:52:44 2018 From: scott.little at windriver.com (Scott Little) Date: Thu, 26 Jul 2018 15:52:44 -0400 Subject: [Starlingx-discuss] download_mirror.sh using bash -e causes early exit In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA2508C7@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA2508C7@ALA-MBD.corp.ad.wrs.com> Message-ID: find ./output -type f -name "*.rpm" | xargs rpm -K | { grep -i "MISSING KEYS" || true } > ./rpm-gpg-key-missing.txt Scott On 18-07-26 03:46 PM, Penney, Don wrote: > > Hi folks, > > I was just running a fresh download_mirror.sh execution and ran into a > problem. I run it as follows, to get timing info and record output: > > time ./download_mirror.sh 2>&1 | tee dpenney.out > > The script exited here: > > --> run: sudo -E yumdownloader -q -C --source > python-voluptuous-0.8.9-1.el7 > > Looking for python-voluptuous-0.8.9-1.el7.src.rpm > > done!! > > finish 1st round of RPM downloading successfully! > > ERROR:  -------RPMs missing 6 in yumdownloader with L1 match > --------------- > > real    84m3.238s > > user    62m49.391s > > sys     9m46.608s > > It seemed like an odd place to finish “1^st round”, so I took a look > around there, checking various timestamps to try to see where it quit, > and found the last command executed was this line: > > ## verify all RPMs SRPMs we download for the GPG keys > > find ./output -type f -name "*.rpm" | xargs rpm -K | grep -i "MISSING > KEYS" > ./rpm-gpg-key-missing.txt > > Because I had no missing keys, the last piped command returned a > non-zero status. And since this script is launched with “bash -e” on > the first line, and I ran the script directly instead of “bash > download_mirror.sh”, the script exited at this point. > > The other download scripts use “bash -e” here as well. Since these are > called directly from download_mirror.sh, they could be exiting early > silently. > > Cheers, > > Don. > > *Don Penney*, Developer, *Wind River* > > > > _______________________________________________ > 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 Thu Jul 26 21:09:46 2018 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 26 Jul 2018 21:09:46 +0000 Subject: [Starlingx-discuss] patch merge approach for starlingx-staging projects ? In-Reply-To: References: Message-ID: Hi Dean: There is a request to backport a change from openstack Heat (Rocky) to the starlingx-staging github repo: https://github.com/starlingx-staging/stx-heat/pull/1 We think we followed the right steps but can you confirm? And who are the core reviewers for the starlingx-staging projects so we can work on getting the required +2? Frank P.S. We know we want to minimize changes in the staging githubs but this is a backport and falls within the guidelines for changes. -----Original Message----- From: Wang, Yi C [mailto:yi.c.wang at intel.com] Sent: Monday, July 16, 2018 8:44 PM To: Dean Troyer Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] patch merge approach for starlingx-staging projects ? Thanks Dean. One more question. Who are in the list of core of starlingx-staging projects? Thanks. Yi -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Monday, July 16, 2018 11:05 PM To: Wang, Yi C Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] patch merge approach for starlingx-staging projects ? On Mon, Jul 16, 2018 at 2:47 AM, Wang, Yi C wrote: > Considering in some case, like security bug fixing , we still need to > make some patches for starlingx-staging projects. Do we have a > proposed patch merge approach for them? Thanks. It is basically the same process, submit a PR, get at least 2 core +2s and merge it. However, merging things into those repos has a higher bar, at least for anything that should be upstreamed (making our tests run for example are not in this category). Backports of existing upstream work are easier to justify as is anything new that is also accompanied by an upstream review. dt -- Dean Troyer dtroyer at gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Thu Jul 26 22:11:42 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 26 Jul 2018 17:11:42 -0500 Subject: [Starlingx-discuss] patch merge approach for starlingx-staging projects ? In-Reply-To: References: Message-ID: On Thu, Jul 26, 2018 at 4:09 PM, Miller, Frank wrote: > There is a request to backport a change from openstack Heat (Rocky) to the starlingx-staging github repo: https://github.com/starlingx-staging/stx-heat/pull/1 > > We think we followed the right steps but can you confirm? And who are the core reviewers for the starlingx-staging projects so we can work on getting the required +2? That looks good Frank. I'm assuming Heat didn't backport that to Pike so pulling from master is fine. Regarding the cores, it is the same group as in Gerrit, however, most do not have commit access. I need to work that bit out, but nothing prevents anyone from doing a review and leaving their ++. Thanks dt -- Dean Troyer dtroyer at gmail.com From austin.sun at intel.com Fri Jul 27 01:24:30 2018 From: austin.sun at intel.com (Sun, Austin) Date: Fri, 27 Jul 2018 01:24:30 +0000 Subject: [Starlingx-discuss] [Gerrit] Gerrit notifaction to starlingx IRC channel In-Reply-To: References: Message-ID: Thanks your review. Uploaded new patch set to includ release branches. -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Thursday, July 26, 2018 9:00 PM To: Sun, Austin Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Gerrit] Gerrit notifaction to starlingx IRC channel On Wed, Jul 25, 2018 at 9:23 PM, Sun, Austin wrote: > I have made gerrit : https://review.openstack.org/#/c/585919/ , please help review it. That looks good Austin, thank you. We should also add the release branches to the gerritbot list: - ^r/.* dt -- Dean Troyer dtroyer at gmail.com From zhipengs.liu at intel.com Fri Jul 27 02:53:52 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Fri, 27 Jul 2018 02:53:52 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: <210898B96CA058408C55992CCAD98676B9E04AF2@ALA-MBD.corp.ad.wrs.com> References: <93814834B4855241994F290E959305C752F52B57@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E049F3@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C752F52D91@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F52DDC@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E04AF2@ALA-MBD.corp.ad.wrs.com> Message-ID: <93814834B4855241994F290E959305C752F53540@SHSMSX104.ccr.corp.intel.com> Thanks Eric!! Use below 2 commands, no python.so found. However, RC found that a wrong collectd-5.7.1-2.el7.x86_64.rpm used. Its size is not the same as the one used by Abraham. After used the right collectd-5.7.1-2.el7.x86_64.rpm, no issue anymore The iso can be deloyed successfully on multimode. Zhipeng -----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: 2018年7月26日 23:28 To: Liu, ZhipengS ; Arce Moreno, Abraham ; starlingx-discuss at lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide I've been able to reproduce the log failure signature with a change to the collectd.conf file The issue is definitely related to the python library but it is packed in the collectd rpm. The one you call out is not in my working env. To further this investigation please provide the output of the following commands ls -lrt /usr/lib64/collectd/python.so ldd /usr/lib64/collectd/python.so Eric. > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: Thursday, July 26, 2018 10:45 AM > To: Liu, ZhipengS; MacDonald, Eric; Arce Moreno, Abraham; > starlingx-discuss at lists.starlingx.io > Subject: RE: [RFC] StarlingX Developer Guide > Importance: High > > Do we need collected-python package in mirror? > > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: 2018年7月26日 22:25 > To: MacDonald, Eric ; Arce Moreno, > Abraham ; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > Hi Eric, > > Thanks for your comment!! Could you help further check the error I saw below? > ====================================================================== > ======= controller-0:/var/log/puppet# grep -R Error* > latest/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 > +0000 Systemd start for collectd failed! > latest/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 > +0000 > /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: > Systemd start for collectd failed! > 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.125 > Error: 2018-07-26 16:36:33 > +0000 Systemd start for collectd failed! > 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.236 > Error: 2018-07-26 16:36:33 > +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: > Systemd start for collectd failed! > ====================================================================== > ========= ontroller-0:~$ cat /var/log/daemon.log | grep collectd > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > plugin "network" successfully loaded. > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > Could not find plugin "python" in /usr/lib64/collectd > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > Could not find plugin "python" in /usr/lib64/collectd > 2018-07-26T16:36:33.072 localhost collectd[25253]: info Automatically > loading plugin "python" failed with status 1. > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > plugin "threshold" successfully loaded. > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "df" successfully loaded. > 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: > Could not find plugin "python" in /usr/lib64/collectd > 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: > Could not find plugin "python" in /usr/lib64/collectd > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Automatically > loading plugin "python" failed with status 1. > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Error: Reading the config file failed! > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Read the syslog for details. > 2018-07-26T16:36:33.073 localhost collectd[25253]: info = > 2018-07-26T16:36:33.100 localhost systemd[1]: notice collectd.service: > main process exited, code=exited, status=1/FAILURE > 2018-07-26T16:36:33.110 localhost systemd[1]: notice Unit collectd.service entered failed state. > 2018-07-26T16:36:33.110 localhost systemd[1]: warning collectd.service failed. > ====================================================================== > > Thanks! > Zhipeng > -----Original Message----- > From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] > Sent: 2018年7月26日 21:19 > To: Liu, ZhipengS ; Arce Moreno, Abraham > ; starlingx-discuss at lists.starlingx.io > Subject: RE: [RFC] StarlingX Developer Guide > > Looks like the manifest that configures and starts the collectd process is failing. > > Can you please execute the following commands on the host that shows > collectd failing and publish the errors you see that might reveal the cause. > > # Get the config error logs ... > sudo -i > cd /var/log/puppet ; fgrep -R Error * > > # get the collectd startup failure logs cat /var/log/daemon.log | grep > collectd > > one startup block is fine ; start to exit should show the error. > > Eric MacDonald > > > -----Original Message----- > > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > > Sent: Thursday, July 26, 2018 4:53 AM > > To: Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > > > Hi Abraham and Hayde > > > > I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. > > Start collectd failed. > > Could you help deploy ISO I built to see if it can work in your environment, thanks! > > > > Zhipeng > > > > > > -----Original Message----- > > From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] > > Sent: 2018年7月26日 10:13 > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > > > Hi again, > > > > Can someone please help test the process to build an ISO based on master using Developer Guide [0]? > > Please use Github page [1] as a documentation support. > > > > Requirements: > > > > - Repo status checked 7/25/2018 19:12 PST > > - stx-tools master branch > > - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update > > RPM macros > > - Temporal! Changes, already in Developer Guide > > - RPM: selinux-policy-devel required > > https://review.openstack.org/#/c/585915 > > > > [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > [1] > > https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md > > > > _______________________________________________ > > 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 abraham.arce.moreno at intel.com Fri Jul 27 05:38:28 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Fri, 27 Jul 2018 05:38:28 +0000 Subject: [Starlingx-discuss] StarlingX Master Branch Successful Compilation Message-ID: We have a successful built of StarlingX ISO based on Master branch using Developer Guide [0] Please use Github page [1] as a documentation support. Environment: - Workstation - Xeon 3.8 GHz 4 Cores - RAM 16 GB - SSD 500 GB - Build time: ~ 6 hours Requirements: - Build process started 7/26/2018 18:00 PST - stx-tools master branch - latest change: Merge "Add repo for finding older python packages" c4b5cd26a2140b999f0540a16d41d53ea4ee7060 - Temporal! Changes, already in Developer Guide - RPM Macros + Sphinxcontrib Versions Changed https://review.openstack.org/#/c/586393/ [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md From cindy.xie at intel.com Fri Jul 27 07:16:56 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Fri, 27 Jul 2018 07:16:56 +0000 Subject: [Starlingx-discuss] StarlingX Master Branch Successful Compilation In-Reply-To: References: Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B2E640C@SHSMSX104.ccr.corp.intel.com> Abraham, This is great! Can we have a manifest with the commitID associated for this particular build? Thx. - cindy -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: Friday, July 27, 2018 1:38 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Master Branch Successful Compilation We have a successful built of StarlingX ISO based on Master branch using Developer Guide [0] Please use Github page [1] as a documentation support. Environment: - Workstation - Xeon 3.8 GHz 4 Cores - RAM 16 GB - SSD 500 GB - Build time: ~ 6 hours Requirements: - Build process started 7/26/2018 18:00 PST - stx-tools master branch - latest change: Merge "Add repo for finding older python packages" c4b5cd26a2140b999f0540a16d41d53ea4ee7060 - Temporal! Changes, already in Developer Guide - RPM Macros + Sphinxcontrib Versions Changed https://review.openstack.org/#/c/586393/ [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md _______________________________________________ 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 Fri Jul 27 12:55:41 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Fri, 27 Jul 2018 12:55:41 +0000 Subject: [Starlingx-discuss] download_mirror.sh using bash -e causes early exit In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FBA2508C7@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA25091F@ALA-MBD.corp.ad.wrs.com> We need to drop the -e from these scripts. Proper error checking would need to be added to commands that need it. The failure to access the blizoo repo we've been experiencing caused the 1st stage download to silently abort when the "yum makecache" failed. failure: repodata/repomd.xml from Starlingx-epel.blizoo.mk_epel_7Server_x86_64: [Errno 256] No more mirrors to try. http://epel.blizoo.mk/epel/7Server/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden step #2: start 1st round of downloading RPMs and SRPMs with L1 match criteria... using ./rpms_from_centos_repo.lst as the download name lists [root at fd7ddd238144 localdisk]# cat logs/log_download_rpms_from_3rd_party.txt using ./rpms_from_3rd_parties.lst as the download name lists 2018-07-26_2009 Loaded plugins: fastestmirror, ovl [root at fd7ddd238144 localdisk]# From: Scott Little [mailto:scott.little at windriver.com] Sent: Thursday, July 26, 2018 3:53 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] download_mirror.sh using bash -e causes early exit find ./output -type f -name "*.rpm" | xargs rpm -K | { grep -i "MISSING KEYS" || true } > ./rpm-gpg-key-missing.txt Scott On 18-07-26 03:46 PM, Penney, Don wrote: Hi folks, I was just running a fresh download_mirror.sh execution and ran into a problem. I run it as follows, to get timing info and record output: time ./download_mirror.sh 2>&1 | tee dpenney.out The script exited here: --> run: sudo -E yumdownloader -q -C --source python-voluptuous-0.8.9-1.el7 Looking for python-voluptuous-0.8.9-1.el7.src.rpm done!! finish 1st round of RPM downloading successfully! ERROR: -------RPMs missing 6 in yumdownloader with L1 match --------------- real 84m3.238s user 62m49.391s sys 9m46.608s It seemed like an odd place to finish "1st round", so I took a look around there, checking various timestamps to try to see where it quit, and found the last command executed was this line: ## verify all RPMs SRPMs we download for the GPG keys find ./output -type f -name "*.rpm" | xargs rpm -K | grep -i "MISSING KEYS" > ./rpm-gpg-key-missing.txt Because I had no missing keys, the last piped command returned a non-zero status. And since this script is launched with "bash -e" on the first line, and I ran the script directly instead of "bash download_mirror.sh", the script exited at this point. The other download scripts use "bash -e" here as well. Since these are called directly from download_mirror.sh, they could be exiting early silently. Cheers, Don. Don Penney, Developer, Wind River _______________________________________________ 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 Eric.MacDonald at windriver.com Fri Jul 27 13:07:54 2018 From: Eric.MacDonald at windriver.com (MacDonald, Eric) Date: Fri, 27 Jul 2018 13:07:54 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: <93814834B4855241994F290E959305C752F53540@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F52B57@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E049F3@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C752F52D91@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C752F52DDC@SHSMSX104.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9E04AF2@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C752F53540@SHSMSX104.ccr.corp.intel.com> Message-ID: <210898B96CA058408C55992CCAD98676B9E04F04@ALA-MBD.corp.ad.wrs.com> Ok, interesting. Glad your unblocked. However, I have to ask. Have you or will you be root causing what caused the build system to choose and include the wrong package ? even one of the same name and version but without the correct fundamental content. Weird. Wonder if that is hitting use elsewhere not or will again in the future ? Eric. > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > Sent: Thursday, July 26, 2018 10:54 PM > To: MacDonald, Eric; Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io > Subject: RE: [RFC] StarlingX Developer Guide > Importance: High > > Thanks Eric!! > Use below 2 commands, no python.so found. > > However, RC found that a wrong collectd-5.7.1-2.el7.x86_64.rpm used. > Its size is not the same as the one used by Abraham. > After used the right collectd-5.7.1-2.el7.x86_64.rpm, no issue anymore > The iso can be deloyed successfully on multimode. > > Zhipeng > > -----Original Message----- > From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] > Sent: 2018年7月26日 23:28 > To: Liu, ZhipengS ; Arce Moreno, Abraham ; > starlingx-discuss at lists.starlingx.io > Subject: RE: [RFC] StarlingX Developer Guide > > I've been able to reproduce the log failure signature with a change to the collectd.conf file > > The issue is definitely related to the python library but it is packed in the collectd rpm. > The one you call out is not in my working env. > To further this investigation please provide the output of the following commands > > ls -lrt /usr/lib64/collectd/python.so > ldd /usr/lib64/collectd/python.so > > Eric. > > > -----Original Message----- > > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > > Sent: Thursday, July 26, 2018 10:45 AM > > To: Liu, ZhipengS; MacDonald, Eric; Arce Moreno, Abraham; > > starlingx-discuss at lists.starlingx.io > > Subject: RE: [RFC] StarlingX Developer Guide > > Importance: High > > > > Do we need collected-python package in mirror? > > > > -----Original Message----- > > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > > Sent: 2018年7月26日 22:25 > > To: MacDonald, Eric ; Arce Moreno, > > Abraham ; > > starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > > > Hi Eric, > > > > Thanks for your comment!! Could you help further check the error I saw below? > > ====================================================================== > > ======= controller-0:/var/log/puppet# grep -R Error* > > latest/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 > > +0000 Systemd start for collectd failed! > > latest/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 > > +0000 > > /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: > > Systemd start for collectd failed! > > 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.125 > > Error: 2018-07-26 16:36:33 > > +0000 Systemd start for collectd failed! > > 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.236 > > Error: 2018-07-26 16:36:33 > > +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: > > Systemd start for collectd failed! > > ====================================================================== > > ========= ontroller-0:~$ cat /var/log/daemon.log | grep collectd > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > > plugin "network" successfully loaded. > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > > Could not find plugin "python" in /usr/lib64/collectd > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > > Could not find plugin "python" in /usr/lib64/collectd > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info Automatically > > loading plugin "python" failed with status 1. > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: > > plugin "threshold" successfully loaded. > > 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "df" successfully loaded. > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: > > Could not find plugin "python" in /usr/lib64/collectd > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: > > Could not find plugin "python" in /usr/lib64/collectd > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Automatically > > loading plugin "python" failed with status 1. > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Error: Reading the config file failed! > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info Read the syslog for details. > > 2018-07-26T16:36:33.073 localhost collectd[25253]: info = > > 2018-07-26T16:36:33.100 localhost systemd[1]: notice collectd.service: > > main process exited, code=exited, status=1/FAILURE > > 2018-07-26T16:36:33.110 localhost systemd[1]: notice Unit collectd.service entered failed state. > > 2018-07-26T16:36:33.110 localhost systemd[1]: warning collectd.service failed. > > ====================================================================== > > > > Thanks! > > Zhipeng > > -----Original Message----- > > From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] > > Sent: 2018年7月26日 21:19 > > To: Liu, ZhipengS ; Arce Moreno, Abraham > > ; starlingx-discuss at lists.starlingx.io > > Subject: RE: [RFC] StarlingX Developer Guide > > > > Looks like the manifest that configures and starts the collectd process is failing. > > > > Can you please execute the following commands on the host that shows > > collectd failing and publish the errors you see that might reveal the cause. > > > > # Get the config error logs ... > > sudo -i > > cd /var/log/puppet ; fgrep -R Error * > > > > # get the collectd startup failure logs cat /var/log/daemon.log | grep > > collectd > > > > one startup block is fine ; start to exit should show the error. > > > > Eric MacDonald > > > > > -----Original Message----- > > > From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] > > > Sent: Thursday, July 26, 2018 4:53 AM > > > To: Arce Moreno, Abraham; starlingx-discuss at lists.starlingx.io > > > Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > > > > > Hi Abraham and Hayde > > > > > > I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. > > > Start collectd failed. > > > Could you help deploy ISO I built to see if it can work in your environment, thanks! > > > > > > Zhipeng > > > > > > > > > -----Original Message----- > > > From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] > > > Sent: 2018年7月26日 10:13 > > > To: starlingx-discuss at lists.starlingx.io > > > Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide > > > > > > Hi again, > > > > > > Can someone please help test the process to build an ISO based on master using Developer Guide [0]? > > > Please use Github page [1] as a documentation support. > > > > > > Requirements: > > > > > > - Repo status checked 7/25/2018 19:12 PST > > > - stx-tools master branch > > > - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update > > > RPM macros > > > - Temporal! Changes, already in Developer Guide > > > - RPM: selinux-policy-devel required > > > https://review.openstack.org/#/c/585915 > > > > > > [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > [1] > > > https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Don.Penney at windriver.com Fri Jul 27 14:23:16 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Fri, 27 Jul 2018 14:23:16 +0000 Subject: [Starlingx-discuss] download_mirror.sh using bash -e causes early exit In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA25091F@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA2508C7@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA25091F@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA25098B@ALA-MBD.corp.ad.wrs.com> There are 3 repos in StarlingX_3rd.repo that are unreachable currently from our site, due to firewall concerns. Disabling these repos allows me to complete the download_mirror.sh $ git diff StarlingX_3rd.repo diff --git a/centos-mirror-tools/StarlingX_3rd.repo b/centos-mirror-tools/StarlingX_3rd.repo index d9c5b37..d669784 100644 --- a/centos-mirror-tools/StarlingX_3rd.repo +++ b/centos-mirror-tools/StarlingX_3rd.repo @@ -11,17 +11,17 @@ enabled=1 [Starlingx-epel.blizoo.mk_epel_7Server_x86_64] name=Starlingx-epel.blizoo.mk_epel_7Server_x86_64 - epel.blizoo.mk_epel_7Server_x86_64 baseurl=http://epel.blizoo.mk/epel/7Server/x86_64 -enabled=1 +enabled=0 [Starlingx-epel.blizoo.mk_epel_7_SRPMS] name=Starlingx-epel.blizoo.mk_epel_7_SRPMS - epel.blizoo.mk_epel_7_SRPMS baseurl=http://epel.blizoo.mk/epel/7/SRPMS -enabled=1 +enabled=0 [Starlingx-ftp.iij.ad.jp_pub_linux_centos_7_rt_x86_64] name=Starlingx-ftp.iij.ad.jp_pub_linux_centos_7_rt_x86_64 - ftp.iij.ad.jp_pub_linux_centos_7_rt_x86_64 baseurl=http://ftp.iij.ad.jp/pub/linux/centos/7/rt/x86_64 -enabled=1 +enabled=0 [Starlingx-ftp.riken.jp_Linux_cern_centos_7_rt_Sources] name=Starlingx-ftp.riken.jp_Linux_cern_centos_7_rt_Sources - ftp.riken.jp_Linux_cern_centos_7_rt_Sources Without these disabled, the "yum makecache" aborts with an error. With them disabled, the only missing RPMs I have now are those covered by this pending update: https://review.openstack.org/#/c/586393/ From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Friday, July 27, 2018 8:56 AM To: Little, Scott; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] download_mirror.sh using bash -e causes early exit We need to drop the -e from these scripts. Proper error checking would need to be added to commands that need it. The failure to access the blizoo repo we've been experiencing caused the 1st stage download to silently abort when the "yum makecache" failed. failure: repodata/repomd.xml from Starlingx-epel.blizoo.mk_epel_7Server_x86_64: [Errno 256] No more mirrors to try. http://epel.blizoo.mk/epel/7Server/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden step #2: start 1st round of downloading RPMs and SRPMs with L1 match criteria... using ./rpms_from_centos_repo.lst as the download name lists [root at fd7ddd238144 localdisk]# cat logs/log_download_rpms_from_3rd_party.txt using ./rpms_from_3rd_parties.lst as the download name lists 2018-07-26_2009 Loaded plugins: fastestmirror, ovl [root at fd7ddd238144 localdisk]# From: Scott Little [mailto:scott.little at windriver.com] Sent: Thursday, July 26, 2018 3:53 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] download_mirror.sh using bash -e causes early exit find ./output -type f -name "*.rpm" | xargs rpm -K | { grep -i "MISSING KEYS" || true } > ./rpm-gpg-key-missing.txt Scott On 18-07-26 03:46 PM, Penney, Don wrote: Hi folks, I was just running a fresh download_mirror.sh execution and ran into a problem. I run it as follows, to get timing info and record output: time ./download_mirror.sh 2>&1 | tee dpenney.out The script exited here: --> run: sudo -E yumdownloader -q -C --source python-voluptuous-0.8.9-1.el7 Looking for python-voluptuous-0.8.9-1.el7.src.rpm done!! finish 1st round of RPM downloading successfully! ERROR: -------RPMs missing 6 in yumdownloader with L1 match --------------- real 84m3.238s user 62m49.391s sys 9m46.608s It seemed like an odd place to finish "1st round", so I took a look around there, checking various timestamps to try to see where it quit, and found the last command executed was this line: ## verify all RPMs SRPMs we download for the GPG keys find ./output -type f -name "*.rpm" | xargs rpm -K | grep -i "MISSING KEYS" > ./rpm-gpg-key-missing.txt Because I had no missing keys, the last piped command returned a non-zero status. And since this script is launched with "bash -e" on the first line, and I ran the script directly instead of "bash download_mirror.sh", the script exited at this point. The other download scripts use "bash -e" here as well. Since these are called directly from download_mirror.sh, they could be exiting early silently. Cheers, Don. Don Penney, Developer, Wind River _______________________________________________ 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 cindy.xie at intel.com Fri Jul 27 14:45:54 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Fri, 27 Jul 2018 14:45:54 +0000 Subject: [Starlingx-discuss] download_mirror.sh using bash -e causes early exit In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA25098B@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA2508C7@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA25091F@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA25098B@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B2E69B4@SHSMSX104.ccr.corp.intel.com> This is great - can somebody merge this patch (https://review.openstack.org/#/c/586393/)? I saw Intel's auto-build log also shows that these are the only files still missing: error: failed packages: python2-rpm-macros-3-20.el7.noarch.rpm python2-sphinxcontrib-httpdomain-1.5.0-3.el7.noarch.rpm python-rpm-macros-3-20.el7.noarch.rpm python-srpm-macros-3-20.el7.noarch.rpm thx. - cindy From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Friday, July 27, 2018 10:23 PM To: Penney, Don ; Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] download_mirror.sh using bash -e causes early exit There are 3 repos in StarlingX_3rd.repo that are unreachable currently from our site, due to firewall concerns. Disabling these repos allows me to complete the download_mirror.sh $ git diff StarlingX_3rd.repo diff --git a/centos-mirror-tools/StarlingX_3rd.repo b/centos-mirror-tools/StarlingX_3rd.repo index d9c5b37..d669784 100644 --- a/centos-mirror-tools/StarlingX_3rd.repo +++ b/centos-mirror-tools/StarlingX_3rd.repo @@ -11,17 +11,17 @@ enabled=1 [Starlingx-epel.blizoo.mk_epel_7Server_x86_64] name=Starlingx-epel.blizoo.mk_epel_7Server_x86_64 - epel.blizoo.mk_epel_7Server_x86_64 baseurl=http://epel.blizoo.mk/epel/7Server/x86_64 -enabled=1 +enabled=0 [Starlingx-epel.blizoo.mk_epel_7_SRPMS] name=Starlingx-epel.blizoo.mk_epel_7_SRPMS - epel.blizoo.mk_epel_7_SRPMS baseurl=http://epel.blizoo.mk/epel/7/SRPMS -enabled=1 +enabled=0 [Starlingx-ftp.iij.ad.jp_pub_linux_centos_7_rt_x86_64] name=Starlingx-ftp.iij.ad.jp_pub_linux_centos_7_rt_x86_64 - ftp.iij.ad.jp_pub_linux_centos_7_rt_x86_64 baseurl=http://ftp.iij.ad.jp/pub/linux/centos/7/rt/x86_64 -enabled=1 +enabled=0 [Starlingx-ftp.riken.jp_Linux_cern_centos_7_rt_Sources] name=Starlingx-ftp.riken.jp_Linux_cern_centos_7_rt_Sources - ftp.riken.jp_Linux_cern_centos_7_rt_Sources Without these disabled, the "yum makecache" aborts with an error. With them disabled, the only missing RPMs I have now are those covered by this pending update: https://review.openstack.org/#/c/586393/ From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Friday, July 27, 2018 8:56 AM To: Little, Scott; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] download_mirror.sh using bash -e causes early exit We need to drop the -e from these scripts. Proper error checking would need to be added to commands that need it. The failure to access the blizoo repo we've been experiencing caused the 1st stage download to silently abort when the "yum makecache" failed. failure: repodata/repomd.xml from Starlingx-epel.blizoo.mk_epel_7Server_x86_64: [Errno 256] No more mirrors to try. http://epel.blizoo.mk/epel/7Server/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden step #2: start 1st round of downloading RPMs and SRPMs with L1 match criteria... using ./rpms_from_centos_repo.lst as the download name lists [root at fd7ddd238144 localdisk]# cat logs/log_download_rpms_from_3rd_party.txt using ./rpms_from_3rd_parties.lst as the download name lists 2018-07-26_2009 Loaded plugins: fastestmirror, ovl [root at fd7ddd238144 localdisk]# From: Scott Little [mailto:scott.little at windriver.com] Sent: Thursday, July 26, 2018 3:53 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] download_mirror.sh using bash -e causes early exit find ./output -type f -name "*.rpm" | xargs rpm -K | { grep -i "MISSING KEYS" || true } > ./rpm-gpg-key-missing.txt Scott On 18-07-26 03:46 PM, Penney, Don wrote: Hi folks, I was just running a fresh download_mirror.sh execution and ran into a problem. I run it as follows, to get timing info and record output: time ./download_mirror.sh 2>&1 | tee dpenney.out The script exited here: --> run: sudo -E yumdownloader -q -C --source python-voluptuous-0.8.9-1.el7 Looking for python-voluptuous-0.8.9-1.el7.src.rpm done!! finish 1st round of RPM downloading successfully! ERROR: -------RPMs missing 6 in yumdownloader with L1 match --------------- real 84m3.238s user 62m49.391s sys 9m46.608s It seemed like an odd place to finish "1st round", so I took a look around there, checking various timestamps to try to see where it quit, and found the last command executed was this line: ## verify all RPMs SRPMs we download for the GPG keys find ./output -type f -name "*.rpm" | xargs rpm -K | grep -i "MISSING KEYS" > ./rpm-gpg-key-missing.txt Because I had no missing keys, the last piped command returned a non-zero status. And since this script is launched with "bash -e" on the first line, and I ran the script directly instead of "bash download_mirror.sh", the script exited at this point. The other download scripts use "bash -e" here as well. Since these are called directly from download_mirror.sh, they could be exiting early silently. Cheers, Don. Don Penney, Developer, Wind River _______________________________________________ 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 dtroyer at gmail.com Fri Jul 27 14:49:35 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Fri, 27 Jul 2018 09:49:35 -0500 Subject: [Starlingx-discuss] download_mirror.sh using bash -e causes early exit In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B2E69B4@SHSMSX104.ccr.corp.intel.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA2508C7@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA25091F@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA25098B@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E69B4@SHSMSX104.ccr.corp.intel.com> Message-ID: On Fri, Jul 27, 2018 at 9:45 AM, Xie, Cindy wrote: > This is great – can somebody merge this patch > (https://review.openstack.org/#/c/586393/)? I saw Intel’s auto-build log > also shows that these are the only files still missing: I just did... dt -- Dean Troyer dtroyer at gmail.com From abraham.arce.moreno at intel.com Fri Jul 27 15:07:27 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Fri, 27 Jul 2018 15:07:27 +0000 Subject: [Starlingx-discuss] StarlingX Master Branch Successful Compilation In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B2E640C@SHSMSX104.ccr.corp.intel.com> References: <2FD5DDB5A04D264C80D42CA35194914F2B2E640C@SHSMSX104.ccr.corp.intel.com> Message-ID: > This is great! Can we have a manifest with the commitID associated for this > particular build? Sure Cindy. Here you have 2 manifests of 2 successful builds, reason? I am somehow confused about the content of our manifest with the information found at our Developer Guide [0] based on how we initialized the manifest: repo init -u https://git.starlingx.io/stx-manifest.git -m default.xml I appreciate community corrections please. I was assuming this was the master but default revision is pointing to m/2018.07. Anyway, I went an build again changing the default revision to master. Next see the details and links, repo was created using the line: repo manifest -r -o my-manifest.xml [Details / Links] Default Revision m/2018.07 [1] The resulting manifest [2] stx-manifest/tree/default.xml content: Default Revision Master [3] The resulting manifest [4] stx-manifest/tree/default.xml?h=m/2018.07 content: As an additional information, I complete a parallel build of StarlingX using a Digital Ocean virtual machine. It took ~ 7 hours, the specs were: 2 vCPUs, RAM 4 GB, Disk 80 GB. [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://git.openstack.org/cgit/openstack/stx-manifest/tree/default.xml [2] https://etherpad.openstack.org/p/stx-manifest-2018.07 [3] https://git.openstack.org/cgit/openstack/stx-manifest/tree/default.xml?h=m/2018.07 [4] https://etherpad.openstack.org/p/stx-manifest-master From Numan.Waheed at windriver.com Fri Jul 27 15:30:23 2018 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Fri, 27 Jul 2018 15:30:23 +0000 Subject: [Starlingx-discuss] Proposed Bug Story Template Message-ID: <3CAA827B7A79BA46B15B280EC82088FE4809FF98@ALA-MBD.corp.ad.wrs.com> Hi, In order to fix the defects reported by community members, it is necessary that required information is provided in the defect. If bugs are reported using a template then it becomes easier to gather required information in the story. Keeping this in mind, I am proposing following template for reporting defects. Please provide your feedback on this template. Once we have general consensus on the template, I can put it on the wiki for general use. Story Board [Bug] Template ========================== Title ----- Appropriate title for the Issue should be given. Use [Bug] prefix to identify it as a defect. Title should clearly state the defect. Example: [Bug] Controller swact fails after Backup & Restore Brief Description ----------------- Provide a brief description of the issue. Usually, it should not be more than 2 to 3 lines. Example: After performing a restore of the system, user is unable to swact the controller. Severity -------- Provide the severity of the defect. Steps to Reproduce ------------------ Write down steps to reproduce the issue Expected Behavior ------------------ Write down what was expected after taking the steps written above Actual Behavior ---------------- State what is the actual behavior Reproducibility --------------- State if the issue is 100% reproducible or intermittent. If it is intermittent, state the frequency of occurrence System Configuration -------------------- Branch/Pull Time/Commit ----------------------- Branch and the time when code was pulled or git commit Timestamp/Logs -------------- Provide a snippet of logs if available and the timestamp when issue was seen. Please indicate the unique identifier in the logs to highlight the problem Provide the path for product log directory for debugging Thanks, [WR logo signiture] Numan Waheed, Manager, Titanium Cloud Testing, Wind River Direct: 613.270.5762 * Mobile: 613.793.5476 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 1416 bytes Desc: image002.jpg URL: From bruce.e.jones at intel.com Fri Jul 27 15:54:33 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 27 Jul 2018 15:54:33 +0000 Subject: [Starlingx-discuss] Proposed Bug Story Template In-Reply-To: <3CAA827B7A79BA46B15B280EC82088FE4809FF98@ALA-MBD.corp.ad.wrs.com> References: <3CAA827B7A79BA46B15B280EC82088FE4809FF98@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB56897A@fmsmsx117.amr.corp.intel.com> Thank you! This LGTM. Please add "tag bugs with stx.bug and stx.new". In a previous project we had a script that we asked bug submitters to run which would gather logs from the product. It didn't gather all the logs, just the ones that were generally useful for triaging new defects. Long term it would be nice to have such a script. In the short term, if there are logs that should be captured, please list them in the template and let's figure out how to post them somewhere - we can't post files to Stories or Tasks :( but we can post links to them. brucej From: Waheed, Numan [mailto:Numan.Waheed at windriver.com] Sent: Friday, July 27, 2018 8:30 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Proposed Bug Story Template Hi, In order to fix the defects reported by community members, it is necessary that required information is provided in the defect. If bugs are reported using a template then it becomes easier to gather required information in the story. Keeping this in mind, I am proposing following template for reporting defects. Please provide your feedback on this template. Once we have general consensus on the template, I can put it on the wiki for general use. Story Board [Bug] Template ========================== Title ----- Appropriate title for the Issue should be given. Use [Bug] prefix to identify it as a defect. Title should clearly state the defect. Example: [Bug] Controller swact fails after Backup & Restore Brief Description ----------------- Provide a brief description of the issue. Usually, it should not be more than 2 to 3 lines. Example: After performing a restore of the system, user is unable to swact the controller. Severity -------- Provide the severity of the defect. Steps to Reproduce ------------------ Write down steps to reproduce the issue Expected Behavior ------------------ Write down what was expected after taking the steps written above Actual Behavior ---------------- State what is the actual behavior Reproducibility --------------- State if the issue is 100% reproducible or intermittent. If it is intermittent, state the frequency of occurrence System Configuration -------------------- Branch/Pull Time/Commit ----------------------- Branch and the time when code was pulled or git commit Timestamp/Logs -------------- Provide a snippet of logs if available and the timestamp when issue was seen. Please indicate the unique identifier in the logs to highlight the problem Provide the path for product log directory for debugging Thanks, [WR logo signiture] Numan Waheed, Manager, Titanium Cloud Testing, Wind River Direct: 613.270.5762 * Mobile: 613.793.5476 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 1416 bytes Desc: image001.jpg URL: From dtroyer at gmail.com Fri Jul 27 16:07:38 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Fri, 27 Jul 2018 11:07:38 -0500 Subject: [Starlingx-discuss] Proposed Bug Story Template In-Reply-To: <9A85D2917C58154C960D95352B22818BAB56897A@fmsmsx117.amr.corp.intel.com> References: <3CAA827B7A79BA46B15B280EC82088FE4809FF98@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB56897A@fmsmsx117.amr.corp.intel.com> Message-ID: On Fri, Jul 27, 2018 at 10:54 AM, Jones, Bruce E wrote: > In the short term, if there are logs that should be captured, please list > them in the template and let’s figure out how to post them somewhere – we > can’t post files to Stories or Tasks L but we can post links to them. > This is usually a pastebin, we have paste.openstack.org available... dt -- Dean Troyer dtroyer at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Fri Jul 27 18:19:07 2018 From: scott.little at windriver.com (Scott Little) Date: Fri, 27 Jul 2018 14:19:07 -0400 Subject: [Starlingx-discuss] stx-tools in manifest Message-ID: Why is it that when I try to 'repo init' per the wiki I get the m/2018.07 version of stx-tools by default?   I did not request that branch via -b.   Shouldn't our default be the bleeding edge of master? This is masking important fixes from Al and others. Scott From Brent.Rowsell at windriver.com Fri Jul 27 18:22:11 2018 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Fri, 27 Jul 2018 18:22:11 +0000 Subject: [Starlingx-discuss] stx-tools in manifest In-Reply-To: References: Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB0ED108@ALA-MBD.corp.ad.wrs.com> I agree, this needs to be pointing to master . Brent -----Original Message----- From: Scott Little [mailto:scott.little at windriver.com] Sent: Friday, July 27, 2018 2:19 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx-tools in manifest Why is it that when I try to 'repo init' per the wiki I get the m/2018.07 version of stx-tools by default?   I did not request that branch via -b.   Shouldn't our default be the bleeding edge of master? This is masking important fixes from Al and others. Scott _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Al.Bailey at windriver.com Fri Jul 27 18:32:49 2018 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Fri, 27 Jul 2018 18:32:49 +0000 Subject: [Starlingx-discuss] stx-tools in manifest In-Reply-To: References: Message-ID: Abraham noted this earlier in his thread: " StarlingX Master Branch Successful Compilation". He mentions a workaround Al -----Original Message----- From: Scott Little [mailto:scott.little at windriver.com] Sent: Friday, July 27, 2018 2:19 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx-tools in manifest Why is it that when I try to 'repo init' per the wiki I get the m/2018.07 version of stx-tools by default?   I did not request that branch via -b.   Shouldn't our default be the bleeding edge of master? This is masking important fixes from Al and others. Scott _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dtroyer at gmail.com Fri Jul 27 18:39:01 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Fri, 27 Jul 2018 13:39:01 -0500 Subject: [Starlingx-discuss] stx-tools in manifest In-Reply-To: References: Message-ID: On Fri, Jul 27, 2018 at 1:19 PM, Scott Little wrote: > Why is it that when I try to 'repo init' per the wiki I get the m/2018.07 > version of stx-tools by default? I did not request that branch via -b. > Shouldn't our default be the bleeding edge of master? My error, https://review.openstack.org/584348 was committed against master not the m/2018.07 branch. I've cherry-picked that to the correct branch [0] and submitted a revert [1]. dt [0] https://review.openstack.org/586637 [1] https://review.openstack.org/586638 -- Dean Troyer dtroyer at gmail.com From dtroyer at gmail.com Fri Jul 27 18:43:37 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Fri, 27 Jul 2018 13:43:37 -0500 Subject: [Starlingx-discuss] StarlingX Master Branch Successful Compilation In-Reply-To: References: <2FD5DDB5A04D264C80D42CA35194914F2B2E640C@SHSMSX104.ccr.corp.intel.com> Message-ID: On Fri, Jul 27, 2018 at 10:07 AM, Arce Moreno, Abraham wrote: > I appreciate community corrections please. I was assuming this was the master > but default revision is pointing to m/2018.07. Anyway, I went an build again changing > the default revision to master. Next see the details and links, > repo was created using the line: So yup, the manifests were backwards. I committed the branch update to master rather than the m/2018.07 branch. Yay for practice runs! I've cherry-picked the change to the right branch and reverted the original in https://review.openstack.org/586637 and https://review.openstack.org/586638. dt -- Dean Troyer dtroyer at gmail.com From erich.cordoba.malibran at intel.com Fri Jul 27 23:02:07 2018 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Fri, 27 Jul 2018 23:02:07 +0000 Subject: [Starlingx-discuss] Trying a "mirrorless" build Message-ID: <37030510e66e4ae681e1601117e7189514e66cc0.camel@intel.com> Hi all, I tried an experiment on building StarlingX without downloading a mirror and use mock/yum to download and resolve depenencies on the fly. I want to share with you this report[0] with the findings. I hope you can find this interesting :) -Erich [0] https://gist.github.com/ericho/049d1908f5d80485541e918515996702 From abraham.arce.moreno at intel.com Sat Jul 28 14:14:31 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Sat, 28 Jul 2018 14:14:31 +0000 Subject: [Starlingx-discuss] RPM Macros Versions Changed Message-ID: We have this bug [0] in review still not merged: RPM Macros + Sphinxcontrib Versions Changed [1] which changes the versions to: python2-rpm-macros-3-21.el7.noarch.rpm python2-sphinxcontrib-httpdomain-1.7.0-1.el7.noarch.rpm python-rpm-macros-3-21.el7.noarch.rpm python-srpm-macros-3-21.el7.noarch.rpm In today's build, the python*macros* rpm's version has changed again [2] requiring us: python-srpm-macros-3-22.el7.noarch.rpm python-rpm-macros-3-22.el7.noarch.rpm python2-rpm-macros-3-22.el7.noarch.rpm What is the appropriate option to proceed? 1. Create another patch with Depends-On: [1] 2. Update [1] to modify the newer version number [0] https://storyboard.openstack.org/#!/story/2003124 [1] https://review.openstack.org/#/c/586393/ [2] https://storyboard.openstack.org/#!/story/2003137 From dtroyer at gmail.com Sat Jul 28 18:30:56 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Sat, 28 Jul 2018 13:30:56 -0500 Subject: [Starlingx-discuss] RPM Macros Versions Changed In-Reply-To: References: Message-ID: On Sat, Jul 28, 2018 at 9:14 AM, Arce Moreno, Abraham wrote: > What is the appropriate option to proceed? > > 1. Create another patch with Depends-On: [1] > 2. Update [1] to modify the newer version number 2. Just update it, there isn't a need to preserve the original review for history or anything (sometimes there might be). Also, within the same repo you can 'stack' reviews and not need Depends-On. git-review will ask if you try to submit more than one new commit in a branch. In a long series, it only creates new patchsets starting with the first commit that is different that what is already in Gerrit. dt -- Dean Troyer dtroyer at gmail.com From abraham.arce.moreno at intel.com Sun Jul 29 00:53:32 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Sun, 29 Jul 2018 00:53:32 +0000 Subject: [Starlingx-discuss] RPM Macros Versions Changed In-Reply-To: References: Message-ID: > > 1. Create another patch with Depends-On: [1] 2. Update [1] to modify > > the newer version number > > 2. Just update it, there isn't a need to preserve the original review for history > or anything (sometimes there might be). Done! https://review.openstack.org/#/c/586393/ Added the 2 stories and tasks created. > Also, within the same repo you can 'stack' reviews and not need Depends-On. > git-review will ask if you try to submit more than one new commit in a > branch. In a long series, it only creates new patchsets starting with the first > commit that is different that what is already in Gerrit. Nice feature, thanks Dean for the explanation :) From abraham.arce.moreno at intel.com Sun Jul 29 01:04:56 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Sun, 29 Jul 2018 01:04:56 +0000 Subject: [Starlingx-discuss] StarlingX Master Branch Successful Compilation Message-ID: We close this week with a successful built of StarlingX ISO based on Master branch using Developer Guide [0]. Please use Github page [1] as a documentation support. Environment: - Workstation - Xeon 3.8 GHz 4 Cores - RAM 16 GB - SSD 500 GB - Build time: ~ 6 hours Requirements: - Build process started 7/27/2018 18:00 PST - stx-tools master branch - latest change: Merge "Add repo for finding older python packages" c4b5cd26a2140b999f0540a16d41d53ea4ee7060 - Temporal! Changes, already in Developer Guide - RPM Macros + Sphinxcontrib Versions Changed https://review.openstack.org/#/c/586393/ - Repo Init Manifest - repo init -u https://git.starlingx.io/stx-manifest.git -m default.xml Feel free to highlight / modify any error found. [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md From austin.sun at intel.com Sun Jul 29 06:54:34 2018 From: austin.sun at intel.com (Sun, Austin) Date: Sun, 29 Jul 2018 06:54:34 +0000 Subject: [Starlingx-discuss] [Gerrit] Gerrit notifaction to starlingx IRC channel In-Reply-To: References: Message-ID: Hi All: This change has merged , every gerrit will post to IRC channel #starlingx now. :) Thanks. BR Austin Sun. -----Original Message----- From: Sun, Austin Sent: Friday, July 27, 2018 9:25 AM To: Dean Troyer Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [Gerrit] Gerrit notifaction to starlingx IRC channel Thanks your review. Uploaded new patch set to includ release branches. -----Original Message----- From: Dean Troyer [mailto:dtroyer at gmail.com] Sent: Thursday, July 26, 2018 9:00 PM To: Sun, Austin Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Gerrit] Gerrit notifaction to starlingx IRC channel On Wed, Jul 25, 2018 at 9:23 PM, Sun, Austin wrote: > I have made gerrit : https://review.openstack.org/#/c/585919/ , please help review it. That looks good Austin, thank you. We should also add the release branches to the gerritbot list: - ^r/.* dt -- Dean Troyer dtroyer at gmail.com From haibin.huang at intel.com Mon Jul 30 06:45:08 2018 From: haibin.huang at intel.com (Huang, Haibin) Date: Mon, 30 Jul 2018 06:45:08 +0000 Subject: [Starlingx-discuss] How to install StarlingX Message-ID: <26F9979367EE7A488DB1ED79369D372039C9D107@SHSMSX104.ccr.corp.intel.com> Hi guys, I am StarlingX user. I have two questions. First, How to install StarlingX? Second, What version should I install? If you have guide for installing StarlingX, please tell me. Thank you very much! ------------------------------------------------------------------------------------------------------------------------------- Huang.haibin 11628530 86+18106533356 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Mon Jul 30 07:51:13 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Mon, 30 Jul 2018 07:51:13 +0000 Subject: [Starlingx-discuss] How to install StarlingX In-Reply-To: <26F9979367EE7A488DB1ED79369D372039C9D107@SHSMSX104.ccr.corp.intel.com> References: <26F9979367EE7A488DB1ED79369D372039C9D107@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B2E8675@SHSMSX104.ccr.corp.intel.com> Haibin, Please check starlingx wiki for installation guide: https://wiki.openstack.org/wiki/StarlingX/Installation_Guide Send questions to this mailing list to get the support. Thx. - cindy From: Huang, Haibin [mailto:haibin.huang at intel.com] Sent: Monday, July 30, 2018 2:45 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] How to install StarlingX Hi guys, I am StarlingX user. I have two questions. First, How to install StarlingX? Second, What version should I install? If you have guide for installing StarlingX, please tell me. Thank you very much! ------------------------------------------------------------------------------------------------------------------------------- Huang.haibin 11628530 86+18106533356 -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Mon Jul 30 14:40:23 2018 From: scott.little at windriver.com (Scott Little) Date: Mon, 30 Jul 2018 10:40:23 -0400 Subject: [Starlingx-discuss] Trying a "mirrorless" build In-Reply-To: <37030510e66e4ae681e1601117e7189514e66cc0.camel@intel.com> References: <37030510e66e4ae681e1601117e7189514e66cc0.camel@intel.com> Message-ID: <7cad83d0-5dae-903d-2441-206a58e9101d@windriver.com> I think there is a fundamental tension between between two views of were StarlingX should go. Vision A, StarlingX's is about a usable iso)    + If software context X (tag, branch what ever) compiles today, it should compile tomorrow.    + Software context X (tag, branch what ever) should always produce the same iso when compiled.    - Requires that the set of packages that we compile against be frozen in some fashion. Vision B, StarlingX is just software)    + Always use the latest and greatest packages.  I don't want to hand manage which external packages are used.    - Builds may break at any time due to external factors, even on release branches. Folks who want to make a functioning product likely prefer A. Folks that want to work with the latest features, or prototyping new features might prefer B. You experiment is solidly in the B camp. I did experiment with yum priorities recently, but it didn't deliver the desired result.  An older StarlingX package with higher priority failed to override a newer upstream package. Instead yum threw an error because newest package was ... 'eclipsed'... I think the word was.  Couldn't find a quick way to suppress that error, so I abandoned the experiment. Scott On 18-07-27 07:02 PM, Cordoba Malibran, Erich wrote: > Hi all, > > I tried an experiment on building StarlingX without downloading a > mirror and use mock/yum to download and resolve depenencies on the fly. > > I want to share with you this report[0] with the findings. > > I hope you can find this interesting :) > > -Erich > > [0] https://gist.github.com/ericho/049d1908f5d80485541e918515996702 > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From chris.friesen at windriver.com Mon Jul 30 15:49:57 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Mon, 30 Jul 2018 09:49:57 -0600 Subject: [Starlingx-discuss] Proposed Bug Story Template In-Reply-To: References: <3CAA827B7A79BA46B15B280EC82088FE4809FF98@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BAB56897A@fmsmsx117.amr.corp.intel.com> Message-ID: <5B5F33A5.70009@windriver.com> On 07/27/2018 10:07 AM, Dean Troyer wrote: > On Fri, Jul 27, 2018 at 10:54 AM, Jones, Bruce E > wrote: > > In the short term, if there are logs that should be captured, please list > them in the template and let’s figure out how to post them somewhere – we > can’t post files to Stories or Tasks Lbut we can post links to them. > > > This is usually a pastebin, we have paste.openstack.org > available... Customers often don't know what logs are important and don't necessarily have the expertise to extract key snippets. Accordingly, our "collect" script basically grabs much of /etc/ and /var/log from each specified node, as well as database dumps on the controller node (and other information as well). This can easily add up to hundreds of MB of compressed tarball. We currently stick these on a shared internal filesystem and mention the location in the internal bug tracker. I wonder if the "collect" tool should have the option to upload logs to a "support" server and return an identifier to the customer to include in their bug report. If you just allow anyone to dump large files on a server somewhere it risks being turned into a filesharing site. The Cinder and Manila folks have also highlighted the lack of support for attachments as a serious problem: https://storyboard.openstack.org/#!/story/2003071 Chris From bruce.e.jones at intel.com Mon Jul 30 17:18:16 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 30 Jul 2018 17:18:16 +0000 Subject: [Starlingx-discuss] Trying a "mirrorless" build In-Reply-To: <7cad83d0-5dae-903d-2441-206a58e9101d@windriver.com> References: <37030510e66e4ae681e1601117e7189514e66cc0.camel@intel.com> <7cad83d0-5dae-903d-2441-206a58e9101d@windriver.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB569B52@fmsmsx117.amr.corp.intel.com> Scott, you raised a very interesting point. I think that the tension between A and B is more about wanting to do both at the same time. We want to provide high levels of performance and stability, pushing us toward A. But the pain of maintaining the patches necessary and managing older package versions pushes us toward B. I think we need to find the balancing point between the two - where performance is high and the pain as low. brucej -----Original Message----- From: Scott Little [mailto:scott.little at windriver.com] Sent: Monday, July 30, 2018 7:40 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Trying a "mirrorless" build I think there is a fundamental tension between between two views of were StarlingX should go. Vision A, StarlingX's is about a usable iso)    + If software context X (tag, branch what ever) compiles today, it should compile tomorrow.    + Software context X (tag, branch what ever) should always produce the same iso when compiled.    - Requires that the set of packages that we compile against be frozen in some fashion. Vision B, StarlingX is just software)    + Always use the latest and greatest packages.  I don't want to hand manage which external packages are used.    - Builds may break at any time due to external factors, even on release branches. Folks who want to make a functioning product likely prefer A. Folks that want to work with the latest features, or prototyping new features might prefer B. You experiment is solidly in the B camp. I did experiment with yum priorities recently, but it didn't deliver the desired result.  An older StarlingX package with higher priority failed to override a newer upstream package. Instead yum threw an error because newest package was ... 'eclipsed'... I think the word was.  Couldn't find a quick way to suppress that error, so I abandoned the experiment. Scott On 18-07-27 07:02 PM, Cordoba Malibran, Erich wrote: > Hi all, > > I tried an experiment on building StarlingX without downloading a > mirror and use mock/yum to download and resolve depenencies on the fly. > > I want to share with you this report[0] with the findings. > > I hope you can find this interesting :) > > -Erich > > [0] https://gist.github.com/ericho/049d1908f5d80485541e918515996702 > _______________________________________________ > 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 chris.friesen at windriver.com Mon Jul 30 17:50:30 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Mon, 30 Jul 2018 11:50:30 -0600 Subject: [Starlingx-discuss] Trying a "mirrorless" build In-Reply-To: <9A85D2917C58154C960D95352B22818BAB569B52@fmsmsx117.amr.corp.intel.com> References: <37030510e66e4ae681e1601117e7189514e66cc0.camel@intel.com> <7cad83d0-5dae-903d-2441-206a58e9101d@windriver.com> <9A85D2917C58154C960D95352B22818BAB569B52@fmsmsx117.amr.corp.intel.com> Message-ID: <5B5F4FE6.6080208@windriver.com> On 07/30/2018 11:18 AM, Jones, Bruce E wrote: > Scott, you raised a very interesting point. > > I think that the tension between A and B is more about wanting to do both at the same time. We want to provide high levels of performance and stability, pushing us toward A. But the pain of maintaining the patches necessary and managing older package versions pushes us toward B. > > I think we need to find the balancing point between the two - where performance is high and the pain as low. I think Scott's point about A is not so much about keeping the same set of packages forever, but rather that if I build a given release today and then build that same release a month (or a year) from now it should result in the same package versions in the ISO. Theoretically I think you could have both behaviours as long as: 1) Each build using the latest upstream package versions gets an auto-generated identifier and all package versions used in that build get dumped into a mirror somewhere. 2) If you build with an explicit identifier you would use the package versions that were originally used for the identified build. This would let you run with the latest and greatest during a development cycle, and then lock down the versions on a release branch. Chris From bruce.e.jones at intel.com Mon Jul 30 19:39:42 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 30 Jul 2018 19:39:42 +0000 Subject: [Starlingx-discuss] Trying a "mirrorless" build In-Reply-To: <5B5F4FE6.6080208@windriver.com> References: <37030510e66e4ae681e1601117e7189514e66cc0.camel@intel.com> <7cad83d0-5dae-903d-2441-206a58e9101d@windriver.com> <9A85D2917C58154C960D95352B22818BAB569B52@fmsmsx117.amr.corp.intel.com> <5B5F4FE6.6080208@windriver.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB569C48@fmsmsx117.amr.corp.intel.com> Chris wrote: > I think Scott's point about A is not so much about keeping the same set of packages forever, but rather that if I build a given release today and then build that same release a month (or a year) from now it should result in the same package versions in the ISO. I agree that repeatable release builds should be the goal. That's why we branch, of course. I don't think we need (or want) to get to completely repeatable releases (e.g. at the toolchain level) but just at the package level. For package dependencies, I know of three ways to handle them - 1) create a big mirror that includes the union of everything 2) version the mirror in parallel with the release branches 3) let koji handle dependencies. I think we're at 1) now, we should start moving to 2) with a long term goal of moving to 3). brucej -----Original Message----- From: Chris Friesen [mailto:chris.friesen at windriver.com] Sent: Monday, July 30, 2018 10:51 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Trying a "mirrorless" build On 07/30/2018 11:18 AM, Jones, Bruce E wrote: > Scott, you raised a very interesting point. > > I think that the tension between A and B is more about wanting to do both at the same time. We want to provide high levels of performance and stability, pushing us toward A. But the pain of maintaining the patches necessary and managing older package versions pushes us toward B. > > I think we need to find the balancing point between the two - where performance is high and the pain as low. I think Scott's point about A is not so much about keeping the same set of packages forever, but rather that if I build a given release today and then build that same release a month (or a year) from now it should result in the same package versions in the ISO. Theoretically I think you could have both behaviours as long as: 1) Each build using the latest upstream package versions gets an auto-generated identifier and all package versions used in that build get dumped into a mirror somewhere. 2) If you build with an explicit identifier you would use the package versions that were originally used for the identified build. This would let you run with the latest and greatest during a development cycle, and then lock down the versions on a release branch. Chris _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From abraham.arce.moreno at intel.com Mon Jul 30 20:30:51 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Mon, 30 Jul 2018 20:30:51 +0000 Subject: [Starlingx-discuss] How to install StarlingX In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B2E8675@SHSMSX104.ccr.corp.intel.com> References: <26F9979367EE7A488DB1ED79369D372039C9D107@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E8675@SHSMSX104.ccr.corp.intel.com> Message-ID: > Please check starlingx wiki for installation guide: > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide Thanks Cindy! > Hi guys, > > I am StarlingX user. I have two questions. > First, How to install StarlingX? > Second, What version should I install? Hi Haibin! I will take advantage of Cindy's answer, your questions and expand what we currently have in StarlingX for people willing to participate. Welcome to the StarlingX Project! We are encouraging everyone to learn about the whole process of: - [0] Building - [1] Installing - [2] Validating [0][Building] This guide takes you through: - Setting up your Development Environment - Building a CentOS based repository consisting in RPM, SRPMS and Tarballs - Creating StarlingX packages by applying patches to the downloaded SRPMS and Tarballs - With all the packages required, building the StarlingX ISO [1][Installing] The guide takes 2 software configurations and creates 4 different deployments: - Standard Controller - StarlingX Cloud with Dedicated Storage - StarlingX Cloud with Controller Storage - All-in-one - StarlingX Cloud Duplex - StarlingX Cloud Simplex We recommend to follow today the "StarlingX Cloud with Controller Storage" since the process has been exercised several times giving us a successful StarlingX ISO installation in the last days. "StarlingX Cloud Simplex" should be completed end of this week and the remaining 2 by next week. One immediate thing you can help with is to feedback the whole installation process taking the User Guide and the scripts the team has written in the form of a Gerrit Review [3]: "Deployment: StarlingX Installation in a Virtualized Environment" [2][Validating] The guide takes us for now through 2 processes: - 2 instances running by getting a Cirros image, creating the appropriate image, flavors, network, subnetwork and finally having those 2 Cirros based servers running. - Check OVS/DPDK health. In summary, everyone's contributions are highly appreciated in any form, from identifying mismatches to suggesting changes. Once you think our guides are healthy enough to follow, we will have a Tech Writer taking care of "having well written Getting Started Guides". Please do not hesitate to contact us through any of our available channels, we are more than happy to help. Welcome to the StarlingX Project [4] [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://wiki.openstack.org/wiki/StarlingX/Installation_Guide [2] https://wiki.openstack.org/wiki/StarlingX/Validation_Guide [3] https://review.openstack.org/#/c/585588 [4] https://wiki.openstack.org/wiki/StarlingX From james at openstack.org Mon Jul 30 20:50:44 2018 From: james at openstack.org (James Cole) Date: Mon, 30 Jul 2018 13:50:44 -0700 Subject: [Starlingx-discuss] StarlingX Logo Concepts Message-ID: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: StarlingX_Logo_Concepts.pdf Type: application/pdf Size: 1154046 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From eddie.ramirez at intel.com Mon Jul 30 21:02:09 2018 From: eddie.ramirez at intel.com (Ramirez, Eddie) Date: Mon, 30 Jul 2018 21:02:09 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: +1 Concept 1. Can’t wait to see it with some color(s) Super! Eddie From: James Cole Date: Monday, July 30, 2018 at 1:51 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] StarlingX Logo Concepts Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From hazzim.i.anaya.casas at intel.com Mon Jul 30 21:03:53 2018 From: hazzim.i.anaya.casas at intel.com (Anaya casas, Hazzim I) Date: Mon, 30 Jul 2018 21:03:53 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: Concept 1, +1. Any idea for colors?? Regards. On Jul 30, 2018, at 15:50, James Cole > wrote: Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From glenn.seiler at windriver.com Mon Jul 30 21:05:15 2018 From: glenn.seiler at windriver.com (Seiler, Glenn) Date: Mon, 30 Jul 2018 21:05:15 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: +1 Concept 1. I like that it is simple and can be self-contained (i.e. without text) and still recognizable. Not sure the other two could do that. From: James Cole [mailto:james at openstack.org] Sent: Monday, July 30, 2018 1:51 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Logo Concepts Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From hayde.martinez.landa at intel.com Mon Jul 30 21:08:17 2018 From: hayde.martinez.landa at intel.com (Martinez Landa, Hayde) Date: Mon, 30 Jul 2018 21:08:17 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: Concept 3, +1 >Hello StarlingX Team, >I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. >There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network >components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling >murmuration. >We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. >I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t >view the attachment. >Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation From felipe_57 at live.com.mx Mon Jul 30 22:10:06 2018 From: felipe_57 at live.com.mx (Felipe de Jesus Ruiz Garcia) Date: Mon, 30 Jul 2018 22:10:06 +0000 Subject: [Starlingx-discuss] Starlingx-discuss Digest, Vol 2, Issue 88 In-Reply-To: References: Message-ID: Hi James, your work is amazing, these logos looks very nice :D I prefer the concept 1, such as already is. Regards Felipe Ruiz > Super! > > Eddie > > From: James Cole > Date: Monday, July 30, 2018 at 1:51 PM > To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] StarlingX Logo Concepts > > Hello StarlingX Team, > > I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. > > There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. > > We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. > > I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. > > Looking forward to hearing what you think! > > James Cole > Graphic Designer > OpenStack Foundation > > End of Starlingx-discuss Digest, Vol 2, Issue 88 > ************************************************ From guillermo.a.ponce.castaneda at intel.com Mon Jul 30 22:27:41 2018 From: guillermo.a.ponce.castaneda at intel.com (Ponce Castaneda, Guillermo A) Date: Mon, 30 Jul 2018 22:27:41 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: I think concept 1 is the best. I think concept 2 reminds me of and old Xerox logo and concept 3 kind of looks like the Zacua logo https://zacua.com/ Best Regards. * Memo From: James Cole Date: Monday, July 30, 2018 at 3:51 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] StarlingX Logo Concepts Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Mon Jul 30 22:29:49 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 30 Jul 2018 22:29:49 +0000 Subject: [Starlingx-discuss] Starlingx-discuss Digest, Vol 2, Issue 88 In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BAB569D2F@fmsmsx117.amr.corp.intel.com> +1 for Concept 1. These are all awesome though! brucej -----Original Message----- From: Felipe de Jesus Ruiz Garcia [mailto:felipe_57 at live.com.mx] Sent: Monday, July 30, 2018 3:10 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Starlingx-discuss Digest, Vol 2, Issue 88 Hi James, your work is amazing, these logos looks very nice :D I prefer the concept 1, such as already is. Regards Felipe Ruiz > Super! > > Eddie > > From: James Cole > Date: Monday, July 30, 2018 at 1:51 PM > To: "starlingx-discuss at lists.starlingx.io" > > Subject: [Starlingx-discuss] StarlingX Logo Concepts > > Hello StarlingX Team, > > I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. > > There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. > > We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. > > I’ve attached a PDF showing all three concepts. It is also available > on Dropbox in case you can’t view the > attachment. oncepts.pdf?dl=0> > > Looking forward to hearing what you think! > > James Cole > Graphic Designer > OpenStack Foundation > > End of Starlingx-discuss Digest, Vol 2, Issue 88 > ************************************************ _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ada.cabrales at intel.com Mon Jul 30 22:32:17 2018 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Mon, 30 Jul 2018 22:32:17 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E716BD562@fmsmsx104.amr.corp.intel.com> Nice and neat! +1 for Opt 3 Ada From: James Cole [mailto:james at openstack.org] Sent: Monday, July 30, 2018 3:51 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Logo Concepts Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.a.cobbley at intel.com Mon Jul 30 22:36:36 2018 From: david.a.cobbley at intel.com (Cobbley, David A) Date: Mon, 30 Jul 2018 22:36:36 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: Concept 1 +1 – captures the essence without confusion the others introduce. From: James Cole [mailto:james at openstack.org] Sent: Monday, July 30, 2018 1:51 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Logo Concepts Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Mon Jul 30 22:37:00 2018 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 30 Jul 2018 22:37:00 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <4F6AACE4B0F173488D033B02A8BB5B7E716BD562@fmsmsx104.amr.corp.intel.com> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> <4F6AACE4B0F173488D033B02A8BB5B7E716BD562@fmsmsx104.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BAB569D56@fmsmsx117.amr.corp.intel.com> Re: colors, the common starling is pretty boring. Would this one work for a color scheme? https://en.wikipedia.org/wiki/Starling#/media/File:Lamprotornis_hildebrandti_-Tanzania-8-2c.jpg brucej From: Cabrales, Ada [mailto:ada.cabrales at intel.com] Sent: Monday, July 30, 2018 3:32 PM To: James Cole ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX Logo Concepts Nice and neat! +1 for Opt 3 Ada From: James Cole [mailto:james at openstack.org] Sent: Monday, July 30, 2018 3:51 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Logo Concepts Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From james at openstack.org Mon Jul 30 22:44:19 2018 From: james at openstack.org (James Cole) Date: Mon, 30 Jul 2018 15:44:19 -0700 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <9A85D2917C58154C960D95352B22818BAB569D56@fmsmsx117.amr.corp.intel.com> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> <4F6AACE4B0F173488D033B02A8BB5B7E716BD562@fmsmsx104.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BAB569D56@fmsmsx117.amr.corp.intel.com> Message-ID: Loving all the feedback, everyone—thank you! Bruce, I like what you’re thinking with colors—I’ve been referencing that image as well. Colors will definitely be the next step after we reach a consensus on concept. James Cole Graphic Designer OpenStack Foundation > On Jul 30, 2018, at 3:37 PM, Jones, Bruce E wrote: > > Re: colors, the common starling is pretty boring. Would this one work for a color scheme? > > https://en.wikipedia.org/wiki/Starling#/media/File:Lamprotornis_hildebrandti_-Tanzania-8-2c.jpg > > brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From felipe_57 at live.com.mx Mon Jul 30 22:47:11 2018 From: felipe_57 at live.com.mx (Felipe de Jesus Ruiz Garcia) Date: Mon, 30 Jul 2018 22:47:11 +0000 Subject: [Starlingx-discuss] Starlingx-discuss Digest, Vol 2, Issue 88 In-Reply-To: <9A85D2917C58154C960D95352B22818BAB569D2F@fmsmsx117.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BAB569D2F@fmsmsx117.amr.corp.intel.com> Message-ID: Maybe this free and open survey polls could help us http://www.easypolls.net/poll.html?p=5b5f9539e4b0f78c70ada6ac Regards Felipe Ruiz On Mon, Jul 30, 2018 at 10:29:49PM +0000, Jones, Bruce E wrote: > +1 for Concept 1. These are all awesome though! > > brucej > > -----Original Message----- > From: Felipe de Jesus Ruiz Garcia [mailto:felipe_57 at live.com.mx] > Sent: Monday, July 30, 2018 3:10 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Starlingx-discuss Digest, Vol 2, Issue 88 > > Hi James, your work is amazing, these logos looks very nice :D I prefer the concept 1, such as already is. > > Regards > Felipe Ruiz > > > Super! > > > > Eddie > > > > From: James Cole > > Date: Monday, July 30, 2018 at 1:51 PM > > To: "starlingx-discuss at lists.starlingx.io" > > > > Subject: [Starlingx-discuss] StarlingX Logo Concepts > > > > Hello StarlingX Team, > > > > I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. > > > > There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. > > > > We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. > > > > I’ve attached a PDF showing all three concepts. It is also available > > on Dropbox in case you can’t view the > > attachment. > oncepts.pdf?dl=0> > > > > Looking forward to hearing what you think! > > > > James Cole > > Graphic Designer > > OpenStack Foundation > > > > End of Starlingx-discuss Digest, Vol 2, Issue 88 > > ************************************************ > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From haibin.huang at intel.com Mon Jul 30 22:47:19 2018 From: haibin.huang at intel.com (Huang, Haibin) Date: Mon, 30 Jul 2018 22:47:19 +0000 Subject: [Starlingx-discuss] How to install StarlingX In-Reply-To: References: <26F9979367EE7A488DB1ED79369D372039C9D107@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E8675@SHSMSX104.ccr.corp.intel.com> Message-ID: <26F9979367EE7A488DB1ED79369D372039C9DA59@SHSMSX104.ccr.corp.intel.com> Thank you! > -----Original Message----- > From: Arce Moreno, Abraham > Sent: Tuesday, July 31, 2018 4:31 AM > To: Xie, Cindy ; Huang, Haibin > ; starlingx-discuss at lists.starlingx.io > Subject: RE: How to install StarlingX > > > Please check starlingx wiki for installation guide: > > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide > > Thanks Cindy! > > > Hi guys, > > > > I am StarlingX user. I have two questions. > > First, How to install StarlingX? > > Second, What version should I install? > > Hi Haibin! > > I will take advantage of Cindy's answer, your questions and expand what we > currently have in StarlingX for people willing to participate. Welcome to the > StarlingX Project! > > We are encouraging everyone to learn about the whole process of: > > - [0] Building > - [1] Installing > - [2] Validating > > [0][Building] > > This guide takes you through: > > - Setting up your Development Environment > - Building a CentOS based repository consisting in RPM, SRPMS and Tarballs > - Creating StarlingX packages by applying patches to the downloaded > SRPMS and Tarballs > - With all the packages required, building the StarlingX ISO > > [1][Installing] > > The guide takes 2 software configurations and creates 4 different > deployments: > > - Standard Controller > - StarlingX Cloud with Dedicated Storage > - StarlingX Cloud with Controller Storage > - All-in-one > - StarlingX Cloud Duplex > - StarlingX Cloud Simplex > > We recommend to follow today the "StarlingX Cloud with Controller > Storage" since the process has been exercised several times giving us a > successful StarlingX ISO installation in the last days. > > "StarlingX Cloud Simplex" should be completed end of this week and the > remaining 2 by next week. > > One immediate thing you can help with is to feedback the whole installation > process taking the User Guide and the scripts the team has written in the > form of a Gerrit Review [3]: > "Deployment: StarlingX Installation in a Virtualized Environment" > > [2][Validating] > > The guide takes us for now through 2 processes: > > - 2 instances running by getting a Cirros image, creating the appropriate > image, flavors, network, subnetwork and finally > having those 2 Cirros based servers running. > - Check OVS/DPDK health. > > In summary, everyone's contributions are highly appreciated in any form, > from identifying mismatches to suggesting changes. Once you think our > guides are healthy enough to follow, we will have a Tech Writer taking care > of "having well written Getting Started Guides". > > Please do not hesitate to contact us through any of our available channels, > we are more than happy to help. > > Welcome to the StarlingX Project [4] > > [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > [1] https://wiki.openstack.org/wiki/StarlingX/Installation_Guide > [2] https://wiki.openstack.org/wiki/StarlingX/Validation_Guide > [3] https://review.openstack.org/#/c/585588 > [4] https://wiki.openstack.org/wiki/StarlingX > > > From cesar.lara at intel.com Mon Jul 30 23:09:57 2018 From: cesar.lara at intel.com (Lara, Cesar) Date: Mon, 30 Jul 2018 23:09:57 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: <0B566C62EC792145B40E29EFEBF1AB47104C363D@fmsmsx104.amr.corp.intel.com> Concept 1 +1 Regards Cesar Lara From: James Cole [mailto:james at openstack.org] Sent: Monday, July 30, 2018 3:51 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Logo Concepts Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From forrest.zhao at intel.com Mon Jul 30 23:32:18 2018 From: forrest.zhao at intel.com (Zhao, Forrest) Date: Mon, 30 Jul 2018 23:32:18 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: <6345119E91D5C843A93D64F498ACFA136999EA2B@SHSMSX101.ccr.corp.intel.com> Concept #1, +1. From: James Cole [mailto:james at openstack.org] Sent: Tuesday, July 31, 2018 4:51 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Logo Concepts Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jolliffe at windriver.com Mon Jul 30 23:32:48 2018 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Mon, 30 Jul 2018 23:32:48 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: <8ABA6D41-90FD-4CED-A5B1-F75ABEE60E41@windriver.com> Thanks James - concept one looks great - grabs your attention. +1 Ian On Jul 30, 2018, at 4:51 PM, James Cole > wrote: Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.friesen at windriver.com Mon Jul 30 23:41:44 2018 From: chris.friesen at windriver.com (Chris Friesen) Date: Mon, 30 Jul 2018 17:41:44 -0600 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: <5B5FA238.7090901@windriver.com> On 07/30/2018 02:50 PM, James Cole wrote: > Hello StarlingX Team, > > I’m James, a graphic designer with the OpenStack Foundation. We’ve been working > on a few logo concepts for StarlingX and wanted to get your thoughts. +1 for concept 1. From austin.sun at intel.com Tue Jul 31 00:19:36 2018 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 31 Jul 2018 00:19:36 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: Hi James. Cool. Thanks a lot. It seems no one vote concept 2 yet , But I like it. “Concept 2” +1. Thanks. BR Austin Sun. From: James Cole [mailto:james at openstack.org] Sent: Tuesday, July 31, 2018 4:51 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Logo Concepts Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From abraham.arce.moreno at intel.com Tue Jul 31 00:27:51 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 31 Jul 2018 00:27:51 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: > I’m James, a graphic designer with the OpenStack Foundation. We’ve been > working on a few logo concepts for StarlingX and wanted to get your > thoughts. Awesome team job! Thanks! > There were quite a few possibilities for this, but we narrowed it down three > concepts, all with the same overarching theme—using multiple component > pieces to create one unifying symbol as a nod to edge network components. > The first features an X icon that is partially created using a bird silhouette. > The second is also an X, but it is formed in part by a number of small dots. The > third uses a bird as the central icon, with a texture created from a photo of a > Starling murmuration. +1 for concept 1... how about playing with the width of the "\" in the logo? taking this into consideration, the way it can be seen might be as follows: 1. As it is, the focus in the logo is shared between the "\" and our dear starling, and I assume the width of the "\" is the same width as our starling's body. 2. How about changing the "\" to the same width of our starling's tail? Would that put more attention into our bird? > We have not explored color yet since we’re hoping to get your thoughts > about form and concept before moving to the smaller details, but feel free to > share any ideas on color you think make sense. Some color between the gray and black zone... From yi.c.wang at intel.com Tue Jul 31 00:36:09 2018 From: yi.c.wang at intel.com (Wang, Yi C) Date: Tue, 31 Jul 2018 00:36:09 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: James, Cool. I like concept 1. Thanks. Yi From: James Cole [mailto:james at openstack.org] Sent: Tuesday, July 31, 2018 4:51 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Logo Concepts Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From mingyuan.qi at intel.com Tue Jul 31 01:16:22 2018 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Tue, 31 Jul 2018 01:16:22 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: +1 for concept 1 Thanks, Mingyuan From: James Cole [mailto:james at openstack.org] Sent: Tuesday, July 31, 2018 4:51 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Logo Concepts Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Tue Jul 31 01:18:40 2018 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 31 Jul 2018 01:18:40 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: <9700A18779F35F49AF027300A49E7C765533CB18@SHSMSX101.ccr.corp.intel.com> +1 for concepte 1. I like the bird. ☺ Best Regards Shuicheng From: James Cole [mailto:james at openstack.org] Sent: Tuesday, July 31, 2018 4:51 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Logo Concepts Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Tue Jul 31 01:23:42 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 31 Jul 2018 01:23:42 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: <93814834B4855241994F290E959305C752F55232@SHSMSX104.ccr.corp.intel.com> +1 for concept 3, thanks! From: James Cole [mailto:james at openstack.org] Sent: 2018年7月31日 4:51 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Logo Concepts Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Tue Jul 31 01:30:46 2018 From: dtroyer at gmail.com (Dean Troyer) Date: Mon, 30 Jul 2018 20:30:46 -0500 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: On Mon, Jul 30, 2018 at 3:50 PM, James Cole wrote: > The first features an X icon that is partially created using a bird > silhouette. I like this one the best, alas it reminds me of one of the older X11 logos [0]. Maybe it is sufficiently different to not be an issue. Mirroring it horizontally might be an option except for the 'facing left' subtext for us left-to-right readers. (forward is often subconsciously to the right for us without additional context). dt [0] https://commons.wikimedia.org/wiki/File:X11.svg -- Dean Troyer dtroyer at gmail.com From kailun.qin at intel.com Tue Jul 31 03:01:00 2018 From: kailun.qin at intel.com (Qin, Kailun) Date: Tue, 31 Jul 2018 03:01:00 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: +1 for concept 1. Bravo! BR, Kailun From: James Cole [mailto:james at openstack.org] Sent: Tuesday, July 31, 2018 4:51 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Logo Concepts Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Tue Jul 31 03:04:08 2018 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 31 Jul 2018 03:04:08 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: References: Message-ID: <93814834B4855241994F290E959305C752F5547F@SHSMSX104.ccr.corp.intel.com> Hi Abraham, Some place need to be changed in GUIDE. 1) Setup Building Docker Container If necessary you might have to set http/https proxy in your Dockerfile.centos73 before building the docker image. ENV http_proxy "http://your.actual_http_proxy.com:your_port" && \ https_proxy "https://your.actual_https_proxy.com:your_port" && \ ftp_proxy "http://your.actual_ftp_proxy.com:your_port" RUN echo "proxy=http://your-proxy.com:port" >> /etc/yum.conf Need change to below. ENV http_proxy " http://your.actual_http_proxy.com:your_port " ENV https_proxy " https://your.actual_https_proxy.com:your_port " ENV ftp_proxy " http://your.actual_ftp_proxy.com:your_port " RUN echo " proxy=http://your-proxy.com:port " >> /etc/yum.conf Story raised: https://storyboard.openstack.org/#!/story/2003169 2) Update the symbolic links Update the symbolic links $ generate-cgcs-centos-repo.sh /import/mirrors/CentOS/stx-r1/CentOS/pike/ Need change to $ generate-cgcs-centos-repo /import/mirrors/CentOS/stx-r1/CentOS/pike/ Thanks! zhipeng -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno at intel.com] Sent: 2018年7月26日 10:13 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide Hi again, Can someone please help test the process to build an ISO based on master using Developer Guide [0]? Please use Github page [1] as a documentation support. Requirements: - Repo status checked 7/25/2018 19:12 PST - stx-tools master branch - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros - Temporal! Changes, already in Developer Guide - RPM: selinux-policy-devel required https://review.openstack.org/#/c/585915 [0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md _______________________________________________ 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 Jul 31 04:44:01 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 31 Jul 2018 04:44:01 +0000 Subject: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA25C16C@ALA-MBD.corp.ad.wrs.com> output/3rd-centos_srpms_missing_L1.txt: scapy-2.3.3-1.el7.src.rpm output/3rd-centos_rpms_missing_L1.txt: cppcheck-1.80-1.el7.x86_64.rpm ima-evm-utils-1.0-1.el7.x86_64.rpm ima-evm-utils-devel-1.0-1.el7.x86_64.rpm For scapy, it seems now only an older version is available: scapy-2.2.0-2.el7.src.rpm Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Jul 31 04:50:48 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 31 Jul 2018 04:50:48 +0000 Subject: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA25C184@ALA-MBD.corp.ad.wrs.com> Sorry... hit "send" accidentally :) output/3rd-centos_srpms_missing_L1.txt: scapy-2.3.3-1.el7.src.rpm output/3rd-centos_rpms_missing_L1.txt: cppcheck-1.80-1.el7.x86_64.rpm ima-evm-utils-1.0-1.el7.x86_64.rpm ima-evm-utils-devel-1.0-1.el7.x86_64.rpm For scapy, it seems now only an older version is available: scapy-2.2.0-2.el7.src.rpm This is coming from the Starlingx-epel.blizoo.mk_epel_7_SRPMS. I don't know if that means it was previously coming from a different repo and has now disappeared. How will a case like this be handled? This would seem to be an older package, so we'd actually be downgrading if we shifted the patches to it. For the missing binaries, it's likely safe enough to just upversion them: [root at 2509dea5bd84 localdisk]# repoquery --archlist=x86_64,none cppcheck ima-evm-utils ima-evm-utils-devel cppcheck-0:1.83-3.el7.x86_64 ima-evm-utils-0:1.1-2.el7.x86_64 ima-evm-utils-devel-0:1.1-2.el7.x86_64 From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, July 31, 2018 12:44 AM To: 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt output/3rd-centos_srpms_missing_L1.txt: scapy-2.3.3-1.el7.src.rpm output/3rd-centos_rpms_missing_L1.txt: cppcheck-1.80-1.el7.x86_64.rpm ima-evm-utils-1.0-1.el7.x86_64.rpm ima-evm-utils-devel-1.0-1.el7.x86_64.rpm For scapy, it seems now only an older version is available: scapy-2.2.0-2.el7.src.rpm Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Tue Jul 31 07:14:48 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 31 Jul 2018 07:14:48 +0000 Subject: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA25C184@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA25C184@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B2E9719@SHSMSX104.ccr.corp.intel.com> Hi, Don, I agree with you. If a higher version of below RPMs are available, let's upgrade to newer version: cppcheck-0:1.83-3.el7.x86_64 ima-evm-utils-0:1.1-2.el7.x86_64 ima-evm-utils-devel-0:1.1-2.el7.x86_64 for scapy-2.3.3-1.el7.src.rpm, do you see a newer version? I think we shall use one newer instead of scapy-2.2.0-2.el7.src.rpm. thx. - cindy From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, July 31, 2018 12:51 PM To: Penney, Don ; 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: Re: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt Sorry... hit "send" accidentally :) output/3rd-centos_srpms_missing_L1.txt: scapy-2.3.3-1.el7.src.rpm output/3rd-centos_rpms_missing_L1.txt: cppcheck-1.80-1.el7.x86_64.rpm ima-evm-utils-1.0-1.el7.x86_64.rpm ima-evm-utils-devel-1.0-1.el7.x86_64.rpm For scapy, it seems now only an older version is available: scapy-2.2.0-2.el7.src.rpm This is coming from the Starlingx-epel.blizoo.mk_epel_7_SRPMS. I don't know if that means it was previously coming from a different repo and has now disappeared. How will a case like this be handled? This would seem to be an older package, so we'd actually be downgrading if we shifted the patches to it. For the missing binaries, it's likely safe enough to just upversion them: [root at 2509dea5bd84 localdisk]# repoquery --archlist=x86_64,none cppcheck ima-evm-utils ima-evm-utils-devel cppcheck-0:1.83-3.el7.x86_64 ima-evm-utils-0:1.1-2.el7.x86_64 ima-evm-utils-devel-0:1.1-2.el7.x86_64 From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, July 31, 2018 12:44 AM To: 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt output/3rd-centos_srpms_missing_L1.txt: scapy-2.3.3-1.el7.src.rpm output/3rd-centos_rpms_missing_L1.txt: cppcheck-1.80-1.el7.x86_64.rpm ima-evm-utils-1.0-1.el7.x86_64.rpm ima-evm-utils-devel-1.0-1.el7.x86_64.rpm For scapy, it seems now only an older version is available: scapy-2.2.0-2.el7.src.rpm Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Tue Jul 31 07:42:45 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 31 Jul 2018 07:42:45 +0000 Subject: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B2E9719@SHSMSX104.ccr.corp.intel.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA25C184@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E9719@SHSMSX104.ccr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B2E97B0@SHSMSX104.ccr.corp.intel.com> Don, I found the file scapy-2.3.3-1.el7.src.rpm is still existing below: http://epel.blizoo.mk/epel/testing/7/SRPMS/s/scapy-2.3.3-1.el7.src.rpm is that because WR proxy blocked this address? Thx. - cindy From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Tuesday, July 31, 2018 3:15 PM To: Penney, Don ; 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: Re: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt Hi, Don, I agree with you. If a higher version of below RPMs are available, let's upgrade to newer version: cppcheck-0:1.83-3.el7.x86_64 ima-evm-utils-0:1.1-2.el7.x86_64 ima-evm-utils-devel-0:1.1-2.el7.x86_64 for scapy-2.3.3-1.el7.src.rpm, do you see a newer version? I think we shall use one newer instead of scapy-2.2.0-2.el7.src.rpm. thx. - cindy From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, July 31, 2018 12:51 PM To: Penney, Don >; 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) > Subject: Re: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt Sorry... hit "send" accidentally :) output/3rd-centos_srpms_missing_L1.txt: scapy-2.3.3-1.el7.src.rpm output/3rd-centos_rpms_missing_L1.txt: cppcheck-1.80-1.el7.x86_64.rpm ima-evm-utils-1.0-1.el7.x86_64.rpm ima-evm-utils-devel-1.0-1.el7.x86_64.rpm For scapy, it seems now only an older version is available: scapy-2.2.0-2.el7.src.rpm This is coming from the Starlingx-epel.blizoo.mk_epel_7_SRPMS. I don't know if that means it was previously coming from a different repo and has now disappeared. How will a case like this be handled? This would seem to be an older package, so we'd actually be downgrading if we shifted the patches to it. For the missing binaries, it's likely safe enough to just upversion them: [root at 2509dea5bd84 localdisk]# repoquery --archlist=x86_64,none cppcheck ima-evm-utils ima-evm-utils-devel cppcheck-0:1.83-3.el7.x86_64 ima-evm-utils-0:1.1-2.el7.x86_64 ima-evm-utils-devel-0:1.1-2.el7.x86_64 From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, July 31, 2018 12:44 AM To: 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt output/3rd-centos_srpms_missing_L1.txt: scapy-2.3.3-1.el7.src.rpm output/3rd-centos_rpms_missing_L1.txt: cppcheck-1.80-1.el7.x86_64.rpm ima-evm-utils-1.0-1.el7.x86_64.rpm ima-evm-utils-devel-1.0-1.el7.x86_64.rpm For scapy, it seems now only an older version is available: scapy-2.2.0-2.el7.src.rpm Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ovidiu.Poncea at windriver.com Tue Jul 31 08:31:45 2018 From: Ovidiu.Poncea at windriver.com (Poncea, Ovidiu) Date: Tue, 31 Jul 2018 08:31:45 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: <4C60D9C5C8176C47874FFF36647AA19E9D47FEC9@ALA-MBD.corp.ad.wrs.com> +1 Concept 1. ________________________________ From: James Cole [james at openstack.org] Sent: Monday, July 30, 2018 11:50 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Logo Concepts Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Jul 31 13:57:09 2018 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 31 Jul 2018 13:57:09 +0000 Subject: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F2B2E97B0@SHSMSX104.ccr.corp.intel.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA25C184@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E9719@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E97B0@SHSMSX104.ccr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA25D27E@ALA-MBD.corp.ad.wrs.com> That exists, but that's not the repo that's configured in StarlingX_3rd.repo, which is: http://epel.blizoo.mk/epel/7Server/x86_64 Maybe someone moved it from the main repo to the testing directory? From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Tuesday, July 31, 2018 3:43 AM To: Penney, Don; 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: RE: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt Don, I found the file scapy-2.3.3-1.el7.src.rpm is still existing below: http://epel.blizoo.mk/epel/testing/7/SRPMS/s/scapy-2.3.3-1.el7.src.rpm is that because WR proxy blocked this address? Thx. - cindy From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Tuesday, July 31, 2018 3:15 PM To: Penney, Don ; 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: Re: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt Hi, Don, I agree with you. If a higher version of below RPMs are available, let's upgrade to newer version: cppcheck-0:1.83-3.el7.x86_64 ima-evm-utils-0:1.1-2.el7.x86_64 ima-evm-utils-devel-0:1.1-2.el7.x86_64 for scapy-2.3.3-1.el7.src.rpm, do you see a newer version? I think we shall use one newer instead of scapy-2.2.0-2.el7.src.rpm. thx. - cindy From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, July 31, 2018 12:51 PM To: Penney, Don >; 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) > Subject: Re: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt Sorry... hit "send" accidentally :) output/3rd-centos_srpms_missing_L1.txt: scapy-2.3.3-1.el7.src.rpm output/3rd-centos_rpms_missing_L1.txt: cppcheck-1.80-1.el7.x86_64.rpm ima-evm-utils-1.0-1.el7.x86_64.rpm ima-evm-utils-devel-1.0-1.el7.x86_64.rpm For scapy, it seems now only an older version is available: scapy-2.2.0-2.el7.src.rpm This is coming from the Starlingx-epel.blizoo.mk_epel_7_SRPMS. I don't know if that means it was previously coming from a different repo and has now disappeared. How will a case like this be handled? This would seem to be an older package, so we'd actually be downgrading if we shifted the patches to it. For the missing binaries, it's likely safe enough to just upversion them: [root at 2509dea5bd84 localdisk]# repoquery --archlist=x86_64,none cppcheck ima-evm-utils ima-evm-utils-devel cppcheck-0:1.83-3.el7.x86_64 ima-evm-utils-0:1.1-2.el7.x86_64 ima-evm-utils-devel-0:1.1-2.el7.x86_64 From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, July 31, 2018 12:44 AM To: 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt output/3rd-centos_srpms_missing_L1.txt: scapy-2.3.3-1.el7.src.rpm output/3rd-centos_rpms_missing_L1.txt: cppcheck-1.80-1.el7.x86_64.rpm ima-evm-utils-1.0-1.el7.x86_64.rpm ima-evm-utils-devel-1.0-1.el7.x86_64.rpm For scapy, it seems now only an older version is available: scapy-2.2.0-2.el7.src.rpm Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Tue Jul 31 14:09:29 2018 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 31 Jul 2018 14:09:29 +0000 Subject: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA25D27E@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA25C184@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E9719@SHSMSX104.ccr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F2B2E97B0@SHSMSX104.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA25D27E@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F2B2E9EF5@SHSMSX104.ccr.corp.intel.com> I submitted two stories for the below two issues: https://storyboard.openstack.org/#!/story/2003173 https://storyboard.openstack.org/#!/story/2003174 They probably need to handle differently. I am assigning engineers to see if upgrading to newer version will cause additional dependency issues. Thx. - cindy From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, July 31, 2018 9:57 PM To: Xie, Cindy ; 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: RE: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt That exists, but that's not the repo that's configured in StarlingX_3rd.repo, which is: http://epel.blizoo.mk/epel/7Server/x86_64 Maybe someone moved it from the main repo to the testing directory? From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Tuesday, July 31, 2018 3:43 AM To: Penney, Don; 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: RE: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt Don, I found the file scapy-2.3.3-1.el7.src.rpm is still existing below: http://epel.blizoo.mk/epel/testing/7/SRPMS/s/scapy-2.3.3-1.el7.src.rpm is that because WR proxy blocked this address? Thx. - cindy From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Tuesday, July 31, 2018 3:15 PM To: Penney, Don >; 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) > Subject: Re: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt Hi, Don, I agree with you. If a higher version of below RPMs are available, let's upgrade to newer version: cppcheck-0:1.83-3.el7.x86_64 ima-evm-utils-0:1.1-2.el7.x86_64 ima-evm-utils-devel-0:1.1-2.el7.x86_64 for scapy-2.3.3-1.el7.src.rpm, do you see a newer version? I think we shall use one newer instead of scapy-2.2.0-2.el7.src.rpm. thx. - cindy From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, July 31, 2018 12:51 PM To: Penney, Don >; 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) > Subject: Re: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt Sorry... hit "send" accidentally :) output/3rd-centos_srpms_missing_L1.txt: scapy-2.3.3-1.el7.src.rpm output/3rd-centos_rpms_missing_L1.txt: cppcheck-1.80-1.el7.x86_64.rpm ima-evm-utils-1.0-1.el7.x86_64.rpm ima-evm-utils-devel-1.0-1.el7.x86_64.rpm For scapy, it seems now only an older version is available: scapy-2.2.0-2.el7.src.rpm This is coming from the Starlingx-epel.blizoo.mk_epel_7_SRPMS. I don't know if that means it was previously coming from a different repo and has now disappeared. How will a case like this be handled? This would seem to be an older package, so we'd actually be downgrading if we shifted the patches to it. For the missing binaries, it's likely safe enough to just upversion them: [root at 2509dea5bd84 localdisk]# repoquery --archlist=x86_64,none cppcheck ima-evm-utils ima-evm-utils-devel cppcheck-0:1.83-3.el7.x86_64 ima-evm-utils-0:1.1-2.el7.x86_64 ima-evm-utils-devel-0:1.1-2.el7.x86_64 From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, July 31, 2018 12:44 AM To: 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: [Starlingx-discuss] missing rpms/srpms from latest download_mirrors.sh attempt output/3rd-centos_srpms_missing_L1.txt: scapy-2.3.3-1.el7.src.rpm output/3rd-centos_rpms_missing_L1.txt: cppcheck-1.80-1.el7.x86_64.rpm ima-evm-utils-1.0-1.el7.x86_64.rpm ima-evm-utils-devel-1.0-1.el7.x86_64.rpm For scapy, it seems now only an older version is available: scapy-2.2.0-2.el7.src.rpm Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Jul 31 15:26:12 2018 From: scott.little at windriver.com (Scott Little) Date: Tue, 31 Jul 2018 11:26:12 -0400 Subject: [Starlingx-discuss] Restructuring round 2 In-Reply-To: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> References: <2ab7ffb1-aa63-daab-d79d-60875d72527a@windriver.com> Message-ID: Revised timeline is August 1 or 2. Scott On 18-07-17 11:07 AM, Scott Little wrote: > > Story: https://storyboard.openstack.org/#!/story/2002801 > > *Goals:* > > 1) Consolidate the following repo’s under stx-integ. > • stx-gplv2 > • stx-gplv3 > • stx-utils > > 2) Restructure the directories under which packages are to be found. > > Currently stx-gplv2/3 are largely without structure. Parts of the > stx-integ structure were inherited from WRLinux and make little > sense.  stx-utils is just i mess of stuff that never found a home when > StarlingX was first set up. > > Directories should descriptive of the class of packages to be found > within. > > Intent is to preserve update history as best is is possible. > > > *Timeline: * > > Probably around July 23 unless there are strong objections.  We should > probably have a freeze on submissions to the affected repos until it > is all completed. > > > *Code Reviews: * > > Most of this is just moving code around.  A few path corrections, but > no new code.  The number and size of the reviews will be huge, and the > code should all have been inspected once before.  Is there a way to > fast track this? Would there be strong objections to me just doing a > +2/+1 without waiting for independent review? > > > *Details of directories/groups ...* > > > Create new directories under stx-integ (logical groupings for files): >    ceph >    config >    config-files >    database >    filesystem >    filesystem/drbd >    grub >    kernel >    kernel/kernel-modules >    ldap >    logging >    strorage-drivers >    tools >    utilities >    virt > > Retained directories under stx-integ (additional logical groupings for > files): >    base >    mellanox >    monitoring >    networking >    python >    restapi-doc >    security > > Retire directories under stx-integ (non-descriptive or ambiguous > grouping we will retire): >    connectivity >    core >    devtools >    extended >    support > > > *Details of packages ...* > > Relocated packages (internal to stx-integ): >    base/ >       dhcp >       initscripts >       libevent >       lighttpd >       memcached >       net-snmp >       novnc >       ntp >       openssh >       pam >       procps >       sanlock >       shadow >       sudo >       systemd >       util-linux >       vim >       watchdog > >    ceph/ >       python-cephclient > >    config/ >       e2fsprogs >       facter >       nfs-utils >       nfscheck >       puppet-4.8.2 >       puppet-modules > >    kernel/ >       kernel-std >       kernel-rt > >    kernel/kernel-modules/ >       mlnx-ofa_kernel > >    ldap/ >       nss-pam-ldapd >       openldap > >    logging/ >       syslog-ng >       logrotate > >    networking/ >       lldpd >       iproute >       mellanox >       python-ryu >       mlx4-config > >    python/ >       python-2.7.5 >       python-django >       python-gunicorn >       python-setuptools >       python-smartpm > >    security/ >       shim-signed >       shim-unsigned >       tboot > >    strorage-drivers/ >       python-3parclient >       python-lefthandclient > >    virt/ >       cloud-init >       libvirt >       libvirt-python >       qemu > >    tools/ >       storage-topology >       vm-topology > >    utilities/ >       tis-extensions >       namespace-utils >       nova-utils >       update-motd > > > > Relocated packages (stx-utils to stx-update): >     enable-dev-patch > > > > Relocated packages (stx-utils to stx-integ): > >     config-files/ >         io-scheduler > >     filesystem/ >         filesystem-scripts > >     grub/ >         grubby > >     logging/ >         logmgmt > >     tools/ >         collector >         monitor-tools > >     tools/engtools/ >         hostdata-collectors >         parsers > >     utilities/ >         build-info >         branding   (formerly wrs-branding) >         platform-util > > > > Relocated packages (stx-gpl2 to stx-integ): >     base/ >         bash >         cgcs-users >         cluster-resource-agents >         dpkg >         haproxy >         libfdt >         netpbm >         rpm > >     database/ >         mariadb > >     filesystem/ >         iscsi-initiator-utils > >     filesystem/drbd/ >         drbd-tools > >     kernel/kernel-modules/ >         drbd >         integrity >         intel-e1000e >         intel-i40e >         intel-i40evf >         intel-ixgbe >         intel-ixgbevf >         qat17 >         tpmdd > >     ldap/ >         ldapscripts > >     networking/ >         iptables >         net-tools > > > > Relocated packages (stx-gpl3 to stx-integ): >     base/ >         anaconda >         crontabs >         dnsmasq >         rsync > >     database/ >         python-psycopg2 > >     filesystem/ >         parted > >     grub/ >         grub2 > >     security/ >         python-keyring > > > > Delete two packages from stx-integ: >    tgt >    irqbalance > > Delete two packages from stx-gplv3: >    seabios >    sysvinit > > Delete one package from stx-utils: >    io-monitor > > > > _______________________________________________ > 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 Jul 31 15:42:46 2018 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Tue, 31 Jul 2018 15:42:46 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: I like the concept one, but can you try a mirrored bird for the other side of the X. So basically 2 birds to create an X. Dariush From: James Cole [mailto:james at openstack.org] Sent: July-30-18 4:51 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Logo Concepts Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.hernandez.gonzalez at intel.com Tue Jul 31 17:08:13 2018 From: fernando.hernandez.gonzalez at intel.com (Hernandez Gonzalez, Fernando) Date: Tue, 31 Jul 2018 17:08:13 +0000 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> Message-ID: <03D458D5BAFF6041973594B00B4E58CE590F0975@fmsmsx101.amr.corp.intel.com> +1 “Concept 3” Fernando Hernandez Gonzalez Software Engineer Avenida del Bosque #1001 Col, El Bajío Zapopan, Jalisco MX, 45019 ____________________________________ Office: +52.33.16.45.01.34 inet 86450134 From: James Cole [mailto:james at openstack.org] Sent: Monday, July 30, 2018 3:51 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Logo Concepts Hello StarlingX Team, I’m James, a graphic designer with the OpenStack Foundation. We’ve been working on a few logo concepts for StarlingX and wanted to get your thoughts. There were quite a few possibilities for this, but we narrowed it down three concepts, all with the same overarching theme—using multiple component pieces to create one unifying symbol as a nod to edge network components. The first features an X icon that is partially created using a bird silhouette. The second is also an X, but it is formed in part by a number of small dots. The third uses a bird as the central icon, with a texture created from a photo of a Starling murmuration. We have not explored color yet since we’re hoping to get your thoughts about form and concept before moving to the smaller details, but feel free to share any ideas on color you think make sense. I’ve attached a PDF showing all three concepts. It is also available on Dropbox in case you can’t view the attachment. Looking forward to hearing what you think! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Jul 31 19:01:18 2018 From: scott.little at windriver.com (Scott Little) Date: Tue, 31 Jul 2018 15:01:18 -0400 Subject: [Starlingx-discuss] build-pkg --parallel Message-ID: I had a successful parallel build (aka build-pkgs --parallel) inside the docker container.   ~1h45m on 24 core, 64G ram The prerequisite was a populated $MY_REPO/cgcs-tis-repo/dependancy-cache. Currently we only generate the cache *after* the build in the 'generate-cgcs-tis-repo' step. *I'd like to see the cache stored in git and updated regularly by 'official' builds.* Note: The cache doesn't have to be perfect, so a cache that is out of date by a day or a week is still very useful. build-pkgs/mockchain just needs a rough guide on build dependencies and potential dependency loops. Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: From james at openstack.org Tue Jul 31 20:08:24 2018 From: james at openstack.org (James Cole) Date: Tue, 31 Jul 2018 13:08:24 -0700 Subject: [Starlingx-discuss] StarlingX Logo Concepts In-Reply-To: <03D458D5BAFF6041973594B00B4E58CE590F0975@fmsmsx101.amr.corp.intel.com> References: <8DCAF24C-F92F-4892-864F-0E3BF8A289AA@openstack.org> <03D458D5BAFF6041973594B00B4E58CE590F0975@fmsmsx101.amr.corp.intel.com> Message-ID: Thanks again for all the feedback, everyone! I appreciate the design suggestions. It looks like Concept 1 is in the lead right now, but we’re going to keep this discussion open until next Monday so anyone else who wants to chime in has a chance to do so. Thank you! James Cole Graphic Designer OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From abraham.arce.moreno at intel.com Tue Jul 31 21:36:25 2018 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Tue, 31 Jul 2018 21:36:25 +0000 Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide In-Reply-To: <93814834B4855241994F290E959305C752F5547F@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C752F5547F@SHSMSX104.ccr.corp.intel.com> Message-ID: Thanks Zhipeng! > Some place need to be changed in GUIDE. > 1) Setup Building Docker Container > > Need change to below. > ENV http_proxy " http://your.actual_http_proxy.com:your_port " > ENV https_proxy " https://your.actual_https_proxy.com:your_port " > ENV ftp_proxy " http://your.actual_ftp_proxy.com:your_port " > RUN echo " proxy=http://your-proxy.com:port " >> /etc/yum.conf > > Story raised: https://storyboard.openstack.org/#!/story/2003169 Done > 2) Update the symbolic links > Update the symbolic links > $ generate-cgcs-centos-repo.sh /import/mirrors/CentOS/stx-r1/CentOS/pike/ > Need change to > $ generate-cgcs-centos-repo /import/mirrors/CentOS/stx-r1/CentOS/pike/ Done