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
2022-01-06	[DCAEGEN2] Use common.log template	Maciej Wereski	1	-86/+0
	Until now DCAEGEN2 used its own templates instead of common ones. This change switches filebeat sidecar generation to common.log templates. Other ONAP components already use it. Filebeat is depreceated and with use of common templates it is possible to disable it globally. This patch also changes ConfigMap usage from per component ConfigMap to one ConfigMap for all of DCAEGEN2 components. This is done to simplify generated file as there are no differences between per component ConfigMaps. Issue-ID: OOM-1 Signed-off-by: Maciej Wereski <m.wereski@partner.samsung.com> Change-Id: I87ffe4890b9a4d79edfe0669750dbf21b4a7b340
2021-03-21	[DCAEGEN2] Deploy DCAE microservices via Helm	Jack Lucas	1	-0/+86
	Deploy DCAE microservices using Helm instead of having the DCAE bootstrap container deploy them using Cloudify. Charts for the microservices are found under oom/kubernetes/dcaegen2-services. Issue-ID: DCAEGEN2-2615 Issue-ID: DCAEGEN2-2617 Signed-off-by: Jack Lucas <jflos@sonoris.net> Change-Id: I22d88987ae8e21b3c08f31f13ffda98967d13297 [Use common secret template for secrets] Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>