Code Review / oom / offline-installer.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 1f264b4) | patch
Setting-up NPM registry for dgbuilder 44/77444/8
authorMichal Ptacek <m.ptacek@partner.samsung.com>
Mon, 28 Jan 2019 13:03:16 +0000 (13:03 +0000)
committerMichal Ptacek <m.ptacek@partner.samsung.com>
Wed, 6 Feb 2019 08:24:39 +0000 (08:24 +0000)
commit5a269d2e06be837377364111be9c238979260b78
tree024c52b6b215ab9e5e780b9289030e81d0d3339btree | snapshot
parent1f264b4f471e3570b8b541af7be9a2d300f7c930commit | diff
Setting-up NPM registry for dgbuilder

This commit is showing-up how OOM patches must be handled in casablanca
release. In Dublin we would like to avoid this completely OOM-1610
so here we are just reproducing the same logic which was already
implemented in Beijing for bash offline installer.
In general it works in a way that OOM charts are patched during
offline platform build and values are configured in install time using
pre-install application role/hook.

Change-Id: I1a2425ef63edd6bc08dcecf0fcae7fd6e553d0ed
Issue-ID: OOM-1616
Signed-off-by: Michal Ptacek <m.ptacek@partner.samsung.com>
build/fetch_and_patch_charts.sh [new file with mode: 0755] blob
config/application_configuration.yml [new file with mode: 0755] blob
patches/casablanca_3.0.0.patch [new file with mode: 0644] blob
patches/offline-changes.patch [deleted file] blob | history
patches/onap-casablanca-patch-role/tasks/main.yml [new file with mode: 0644] blob
This repo contains SRC code for offline installer solution. It can be primarily used for ONAP offline deployments using OOM charts however it can be used for other offline deployments as well as it's concept is quite generic.