I can't reproduce this, with or without https://review.openstack.org/#/c/615316 Where you in the container when you ran mirror_downloader.sh? In directory /localdisk? Scott On 18-11-06 11:51 AM, Martinez Landa, Hayde wrote:
Hi Ken!
We tried mirror_downloader.sh on our Jenkins automated environment and also on
my local environment and when it finished running we noticed that the following files were moved:
this ones were sent to: “/localdisk/output/stx-r1/CentOS/pike/Binary/x86_64”
-rpms_3rdparties.lst
-rpms_centos.lst
-rpms_centos3rdparties.lst
-tarball-dl.lst
Same with “yum.repos.d” were sent to: “CentOS/pike/Binary/noarch/”
CentOS/pike/Binary/noarch/yum.repos.d/
CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.2.repo
CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_buildlogs_centos_org.repo
CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_download_docker_com.repo
CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_CentOS-OpenStack-queens.repo
CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_epel_blizoo_mk.repo
CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_linuxsoft_cern_ch.repo
CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.3.repo
CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_buildlogs-seed_centos_org.repo
CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_www_rpmfind_net.repo
CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.4.repo
CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-EPEL-7.repo
CentOS/pike/Binary/noarch/yum.repos.d/StarlingX_3rd_ftp_iij_ad_jp.repo
CentOS/pike/Binary/noarch/yum.repos.d/StarlingX-Centos-7.5.repo
And finally rpm-gpg-keys sent to: “CentOS/pike/Binary/x86_64”
CentOS/pike/Binary/x86_64/rpm-gpg-keys/
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27-primary
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-SCLo
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Debug-6
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-6
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-EPEL-6
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Security-6
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-OpsTools
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC29
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-EPEL-7
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-5
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-DOCKER
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-cern
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-SIG-Virtualization
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC27-second
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-FC28
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-CentOS-Testing-6
CentOS/pike/Binary/x86_64/rpm-gpg-keys/RPM-GPG-KEY-Cloud-SIG
Is this the expected behavior?
I’m currently finishing the build with this mirror, will update once it’s done.
Best
-Hayde
*From: *"Young, Ken" <Ken.Young@windriver.com> *Date: *Monday, November 5, 2018 at 2:43 PM *To: *"Lara, Cesar" <cesar.lara@intel.com> *Cc: *"starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> *Subject: *Re: [Starlingx-discuss] [build][meetings] Meeting minutes 11/1/2018
Cesar,
A quick update on the mirror. The tooling to enable the mirror was merged on Friday. The Wind River used the mirror over the week-end for its builds with no issues.
How have your builds gone since Friday?
/KenY
*From: *"Lara, Cesar" <cesar.lara@intel.com> *Date: *Thursday, November 1, 2018 at 6:58 PM *To: *"starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> *Subject: *[Starlingx-discuss] [build][meetings] Meeting minutes 11/1/2018
Build team meeting minutes 11/1/2018
Attendees
Ken, Jason, Scott, Memo, Erich, Marcela, Victor, Chuy, Cesar, Luis
Cengn Status
-Mirror is now completed and operational, the wiki has been updated with the details for Cengn and our partnership, the details and specs are already there.
-The scripts that are related with mirror download are now pointing to Cengn repos and are waiting in the queue to be reviewed tested and merged, the desired date for fully operational mirror is November 5^th
- Now changes to the packages required to build will be caught by Cengn mirror within one day, the scripts will try to download first from Cengn and if is still not available will try to go get the packages from upstream.
Koji follow up
-presentation on a possible scenario hosting Koji and demo on using Koji based built packages with our current build scripts.
-discussion followed up by implementation details led to different points of view about the problem we have to solve if there’s any, the amount of effort to integrate tooling as we know Koji doesn’t solve every use case by itself and where to host a Koji service(we are striving to host a centralized service for the whole community).
-The statement we are using to follow thru with Koji versus our current script is that we will require a lot of effort to support multi OS with the current tools.
We had to defer the topic of mirror script refactored using Python.
We will start a thread on the goals this team has for next release on the mailing list.
Regards
*//*
*/Cesar Lara/*
Software Engineering Manager
OpenSource Technology Center
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss