tools/centos-mirror-tools
2018-11-19 22:47:02 +00:00
..
rpm-gpg-keys Add missing key for CentOS Virtualization. 2018-08-16 15:26:41 -05:00
stx_mirror_scripts StarlingX mirror bug fixes 2018-11-07 11:26:18 -05:00
yum.repos.d Enable starlingx mirror 2018-11-02 13:33:00 -04:00
dl_other_from_centos_repo.sh Enable starlingx mirror 2018-11-02 13:33:00 -04:00
dl_rpms.sh Enable starlingx mirror 2018-11-02 13:33:00 -04:00
dl_tarball.sh Enable starlingx mirror 2018-11-02 13:33:00 -04:00
Dockerfile Split and move repo data files to yum.repo.d subdirectory. 2018-08-07 16:48:16 -04:00
download_mirror.sh StarlingX mirror bug fixes 2018-11-07 11:26:18 -05:00
make_stx_mirror_yum_conf.sh Enable starlingx mirror 2018-11-02 13:33:00 -04:00
mirror-check.sh Check for releasever in yum.conf before grepping 2018-09-06 11:18:28 -04:00
mvn-artifacts.lst StarlingX: Tar Compressed files repository 2018-07-03 06:04:28 -07:00
other_downloads.lst Add build tools 2018-06-08 17:01:43 -05:00
README.rst Modify README in create mirror steps 2018-10-24 03:39:07 +00:00
rpms_3rdparties.lst Upversion kubernetes client from 4.0 to 6.0 2018-11-02 10:27:08 -05:00
rpms_centos3rdparties.lst refactor audit 2018-11-16 02:21:03 +00:00
rpms_centos.lst Merge "Refactor patches for pam package" 2018-11-19 22:47:02 +00:00
show_imported_rpm_gpg_keys.sh Add build tools 2018-06-08 17:01:43 -05:00
starlingx_add_pkgs.sh Merge "Split and move repo data files to yum.repo.d subdirectory." 2018-08-08 16:25:51 +00:00
tarball-dl.lst Rebase openstack-helm and openstack-helm-infra 2018-11-16 10:12:31 -05:00
url_utils.sh Enable starlingx mirror 2018-11-02 13:33:00 -04:00
utils_tests.sh Refactor on dl_rpms.sh 2018-09-10 09:57:39 -05:00
utils.sh StarlingX mirror bug fixes 2018-11-07 11:26:18 -05:00
yum.conf.sample yum.conf.sample: Add example yum.conf 2018-09-13 13:56:39 -07:00

Create mirror for StarlingX

Step 0 - Build the container

Build the docker image on your Linux host (with Docker supported). NOTE: if necessary you might have to set http/https proxy in your Dockerfile before building the docker image below.

$ docker build -t <your_docker_image_name>:<your_image_version> -f Dockerfile .

Step 1 - Run the container

The container shall be run from the same directory where the other scripts are stored.

$ docker run -it -v $(pwd):/localdisk <your_docker_image_name>:<your_image_version>

The container can also be run the following way, so the download_mirror.sh runs automatically without having to enter the container and the step 2can be simplified.

$ docker run -it -v $(pwd):/localdisk <your_docker_image_name>:<your_image_version> download_mirror.sh

As /localdisk is defined as the workdir of the container, the same folder name should be used to define the volume. The container will start to run and populate a logs and output folders in this directory. The container shall be run from the same directory where the other scripts are stored.

step 2 - Run the download_mirror.sh script

Once inside the container run the downloader script

$ ./download_mirror.sh

NOTE: in case there are some downloading failures due to network instability (or timeout), you should download them manually, to assure you get all RPMs listed in "rpms_from_3rd_parties.lst" and "rpms_from_centos_repo.lst".

step 3 - Copy the files to the mirror

After all downloading complete, copy the download files to mirror.

$ mkdir -p <your_mirror_folder>/ $ cp -r output/stx-r1/ <your_mirror_folder>/

In this case <your_mirror_folder> can be whatever folder you want to use as mirror.

step 4 - Tweaks in the StarlingX build system.

NOTE: step below is not needed if you've synced the latest codebase.

Go into StarlingX build system (another container which hosts cgcs build system), and follow up below steps:

Debugging issues

The download_mirror.sh script will create log files in the form of centos_rpms_*.txt. After the download is complete, it's recommended to check the content of these files to see if everything was downloaded correctly.

A quick look into these files could be:

$ cd output/ $ cat missing

In this case, there shoudn't be any package in the "missing" files.