- rm -f /tmp/resources/offline_data/docker_images_for_nexus/*
- rm -rf /tmp/resources/offline_data/npm_tar
- rm -rf /tmp/resources/offline_data/pypi
-
-Part 4. Application helm charts preparation and patching
---------------------------------------------------------
-
-This is about to clone oom repository and patch it to be able to use it
-offline. Use the following command:
-
-::
-
- ./build/fetch_and_patch_charts.sh <helm charts repo> <commit/tag/branch> <patchfile> <target\_dir>
-
-For example:
-
-::
-
- ./build/fetch_and_patch_charts.sh https://gerrit.onap.org/r/oom 0b904977dde761d189874d6dc6c527cd45928 /tmp/onap-offline/patches/onap.patch /tmp/oom-clone
-
-Part 5. Creating offline installation package
----------------------------------------------
-
-For the packagin itself it's necessary to prepare configuration. You can
-use ./build/package.conf as template or
-directly modify it.
-
-There are some parameters needs to be set in configuration file.
-Example values below are setup according to steps done in this guide to package ONAP.
-
-+---------------------------------------+------------------------------------------------------------------------------+
-| Parameter | Description |
-+=======================================+==============================================================================+
-| HELM_CHARTS_DIR | directory with Helm charts for the application |
-| | |
-| | Example: /tmp/oom-clone/kubernetes |
-+---------------------------------------+------------------------------------------------------------------------------+
-| APP_CONFIGURATION | application install configuration (application_configuration.yml) for |
-| | ansible installer and custom ansible role code directories if any. |
-| | |
-| | Example:: |
-| | |
-| | APP_CONFIGURATION=( |
-| | /tmp/onap-offline/config/application_configuration.yml |
-| | /tmp/onap-offline/patches/onap-patch-role |
-| | ) |
-| | |
-+---------------------------------------+------------------------------------------------------------------------------+
-| APP_BINARY_RESOURCES_DIR | directory with all (binary) resources for offline infra and application |
-| | |
-| | Example: /tmp/resources |
-+---------------------------------------+------------------------------------------------------------------------------+
-| APP_AUX_BINARIES | additional binaries such as docker images loaded during runtime [optional] |
-+---------------------------------------+------------------------------------------------------------------------------+
-
-Offline installer packages are created with prepopulated data via
-following command run from onap-offline directory
-
-::
-
- ./build/package.sh <project> <version> <packaging target directory>
-
-E.g.
-
-::
-
- ./build/package.sh onap 4.0.0 /tmp/package
-
-
-So in the target directory you should find tar files with
-
-::
-
- offline-<PROJECT_NAME>-<PROJECT_VERSION>-sw.tar
- offline-<PROJECT_NAME>-<PROJECT_VERSION>-resources.tar
- offline-<PROJECT_NAME>-<PROJECT_VERSION>-aux-resources.tar
-