1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. http://creativecommons.org/licenses/by/4.0
3 .. Copyright 2019 Samsung Electronics Co., Ltd.
5 OOM ONAP Offline Installer Package Build Guide
6 =============================================================
8 This document is describing procedure for building offline installer packages. It is supposed to be triggered on server with internet connectivity and will download all artifacts required for ONAP deployment based on our static lists. The server used for the procedure in this guide is preferred to be separate build server.
10 Procedure was completely tested on RHEL 7.6 as it’s tested target platform, however with small adaptations it should be applicable also for other platforms.
11 Some discrepancies when Centos 7.6 is used are described below as well.
16 We assume that procedure is executed on RHEL 7.6 server with \~300G disc space, 16G+ RAM and internet connectivity
18 Some additional sw packages are required by ONAP Offline platform building tooling. in order to install them
19 following repos has to be configured for RHEL 7.6 platform.
30 subscription-manager register --username <rhel licence name> --password <password> --auto-attach
32 # required by special centos docker recommended by ONAP
33 yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
35 # required by docker dependencies i.e. docker-selinux
36 subscription-manager repos --enable=rhel-7-server-extras-rpms
38 # epel is required by npm within blob build
39 rpm -ivh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
45 ToDo: newer download scripts needs to be verified on Centos with ONAP Dublin
51 # required by special centos docker recommended by ONAP
52 yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
54 # enable epel repo for npm and jq
55 yum install -y epel-release
57 Subsequent steps are the same on both platforms:
61 # install following packages
62 yum install -y docker-ce-18.09.5 python-pip git createrepo expect nodejs npm jq
64 # install Python 3 (download scripts don't support Python 2 anymore)
65 yum install -y python36 python36-pip
67 # twine package is needed by nexus blob build script
70 # docker daemon must be running on host
73 Then it is necessary to clone all installer and build related repositories and prepare the directory structure.
77 # prepare the onap build directory structure
79 git clone https://gerrit.onap.org/r/oom/offline-installer onap-offline
82 # install required pip packages for build and download scripts
83 pip3 install -r ./build/requirements.txt
84 pip3 install -r ./build/download/requirements.txt
86 Part 2. Download artifacts for offline installer
87 ------------------------------------------------
89 .. note:: Skip this step if you have already all necessary resources and continue with Part 3. Populate local nexus
91 It's possible to download all artifacts in single ./download.py execution. Recently we improved reliability of download scripts
92 so one might try following command to download most of the required artifacts in single shot.
96 # following arguments are provided
97 # all data lists are taken in ./build/data_lists/ folder
98 # all resources will be stored in expected folder structure within ../resources folder
99 # for more details refer to Appendix 1.
101 ./build/download/download.py --docker ./build/data_lists/infra_docker_images.list ../resources/offline_data/docker_images_infra \
102 --docker ./build/data_lists/rke_docker_images.list ../resources/offline_data/docker_images_for_nexus \
103 --docker ./build/data_lists/onap_docker_images.list ../resources/offline_data/docker_images_for_nexus \
104 --git ./build/data_lists/onap_git_repos.list ../resources/git-repo \
105 --npm ./build/data_lists/onap_npm.list ../resources/offline_data/npm_tar \
106 --rpm ./build/data_lists/onap_rpm.list ../resources/pkg/rhel \
107 --pypi ./build/data_lists/onap_pip_packages.list ../resources/offline_data/pypi \
108 --http ./build/data_lists/infra_bin_utils.list ../resources/downloads
111 Alternatively, step-by-step procedure is described in Appendix 1.
113 This concludes SW download part required for ONAP offline platform creating.
115 Part 3. Populate local nexus
116 ----------------------------
120 - All data lists and resources which are pushed to local nexus repository are available
121 - Following ports are not occupied buy another service: 80, 8081, 8082, 10001
122 - There's no docker container called "nexus"
124 .. note:: In case you skipped the Part 2 for the artifacts download, please ensure that the copy of resources data are untarred in *./onap-offline/../resources/*
126 Whole nexus blob data will be created by running script build_nexus_blob.sh.
127 It will load the listed docker images, run the Nexus, configure it as npm, pypi
128 and docker repositories. Then it will push all listed npm and pypi packages and
129 docker images to the repositories. After all is done the repository container
132 .. note:: build_nexus_blob.sh script is using docker, npm and pip data lists for building nexus blob. Unfortunatelly we now have 2 different docker data lists (RKE & ONAP). So we need to merge them as visible from following snippet. This problem will be fixed in OOM-1890
134 You can run the script as following example:
138 # merge RKE and ONAP app data lists
139 cat ./build/data_lists/rke_docker_images.list >> ./build/data_lists/onap_docker_images.list
141 ./build/build_nexus_blob.sh
143 .. note:: in current release scope we aim to maintain just single example data lists set, tags used in previous releases are not needed. Datalists are also covering latest versions verified by us despite user is allowed to build data lists on his own.
145 Once the Nexus data blob is created, the docker images and npm and pypi
146 packages can be deleted to reduce the package size as they won't be needed in
147 the installation time:
153 rm -f /tmp/resources/offline_data/docker_images_for_nexus/*
154 rm -rf /tmp/resources/offline_data/npm_tar
155 rm -rf /tmp/resources/offline_data/pypi
157 Part 4. Packages preparation
158 --------------------------------------------------------
160 ONAP offline deliverable consist of 3 packages:
162 +---------------------------------------+------------------------------------------------------------------------------+
163 | Package | Description |
164 +=======================================+==============================================================================+
165 | sw_package.tar | Contains installation software and configuration for infrastructure and ONAP |
166 +---------------------------------------+------------------------------------------------------------------------------+
167 | resources_package.tar | Contains all input files needed to deploy infrastructure and ONAP |
168 +---------------------------------------+------------------------------------------------------------------------------+
169 | aux_package.tar | Contains auxiliary input files that can be added to ONAP |
170 +---------------------------------------+------------------------------------------------------------------------------+
172 All packages can be created using script build/package.py. Beside of archiving files gathered in the previous steps, script also builds installer software and apply patch over application repository to make it usable without internet access.
174 From onap-offline directory run:
178 ./build/package.py <helm charts repo> --application-repository_reference <commit/tag/branch> --application-patch_file <patchfile> --output-dir <target\_dir> --resources-directory <target\_dir>
184 ./build/package.py https://gerrit.onap.org/r/oom --application-repository_reference master --application-patch_file ./patches/onap.patch --output-dir ../packages --resources-directory ../resources
187 In the target directory you should find tar files:
192 resources_package.tar
196 Appendix 1. Step-by-step download procedure
197 -------------------------------------------
199 **Step 1 - docker images**
203 # This step will parse all 3 docker datalists (offline infrastructure images, rke k8s images & onap images)
204 # and start building onap offline platform in /tmp/resources folder
206 ./build/download/download.py --docker ./build/data_lists/infra_docker_images.list ../resources/offline_data/docker_images_infra \
207 --docker ./build/data_lists/rke_docker_images.list ../resources/offline_data/docker_images_for_nexus \
208 --docker ./build/data_lists/onap_docker_images.list ../resources/offline_data/docker_images_for_nexus
211 **Step 2 - git repos**
215 # Following step will download all git repos
216 ./build/download/download.py --git ./build/data_lists/onap_git_repos.list ../resources/git-repo
219 **Step 3 - npm packages**
223 # Following step will download all npm packages
224 ./build/download/download.py --npm ./build/data_lists/onap_npm.list ../resources/offline_data/npm_tar
226 **Step 4 - binaries**
230 # Following step will download rke, kubectl and helm binaries
231 ./build/download/download.py --http ./build/data_lists/infra_bin_utils.sh ../resources/downloads
237 # Following step will download all rpms and create repo
238 ./build/download/download.py --rpm ./build/data_lists/onap_rpm.list ../resources/pkg/rhel
240 createrepo ../resources/pkg/rhel
242 **Step 6 - pip packages**
246 # Following step will download all pip packages
247 ./build/download/download.py --pypi ./build/data_lists/onap_pip_packages.list ../resources/offline_data/pypi