oom - Introduces the ONAP Platform OOM (ONAP Operations Manager) to efficiently Deploy, Manage, Operate the ONAP platform and its components (e.g. MSO, DCAE, SDC, etc.) and infrastructure (VMs, Containers).

Age	Commit message (Collapse)	Author	Files	Lines
2020-02-01	[ONAP-wide] Replace .Release.Name with common.release	Krzysztof Opasiak	1	-2/+2
	ONAP is too big to be deployed using helm install so we need to use a custom helm plugin helm deploy. This script deloys onap component by component instead of deploying evrything at once. Unfortunately this script also modifies the helm release by appending component name to it. As a result of this behavior our objects are called for example: onap-mariadb-galera-mariadb-galera-0 instead of just being called onap-mariadb-galera-0. This patch simplifies this naming convention by replacing all direct usages of .Release.Name with common.release macro which strips the component specific part from the release name. Issue-ID: OOM-2275 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: Ia8cead50d305adb00eef666d0a1ace74479b5183
2018-10-09	Adding SO-Monitoring Helm Charts into SO Subcharts	rope252	1	-0/+45
	This subtask's aim is to create the Helm Charts for SO-Monitoring and then adding these charts to the SO's subcharts. Change-Id: Icb58c9ce4432c6571e656a0ca00079b1f7694ad2 Issue-ID: SO-1054 Signed-off-by: rope252 <gareth.roper@ericsson.com>