oom/offline-installer - 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.

Age	Commit message (Collapse)	Author	Files	Lines
2019-02-28	Dont crash patching on missing chart file	Michal Ptacek	1	-11/+25
	In some deployments not all chart files might be present. We should not fail if some components are not deployed. Issue-ID: OOM-1691 Change-Id: I6a0ae05e753a2de6301ee0188022a958868776ad Signed-off-by: Michal Ptacek <m.ptacek@partner.samsung.com>
2019-02-06	Extract certificate to cloudify-manager	Michal Ptacek	1	-0/+10
	DCAE bootstraping require that bootstrap/cloudify-manager pods has to trust our certificate. We are mounting path to this certificate to respective pod. Change-Id: Ie2ea796851e6def52d4ec556c9d5b19633e8a743 Issue-ID: OOM-1618 Signed-off-by: Michal Ptacek <m.ptacek@partner.samsung.com>
2019-02-06	Setting-up NPM registry for dgbuilder	Michal Ptacek	1	-0/+24
	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>