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
2021-11-19	[DCAEGEN2] Updates for R10	Jack Lucas	1	-25/+49
	By default, disable all dcaegen2 components except config-binding-service, healthcheck, and ves-openapi-manager. Fix DNS name for the ONAP consul instance. Move mongodb dependency from dcae-bootstrap to dcae-tcagen2. Fix the generation of the JSON list of expected components for the healthcheck services. (Previously could have a spurious leading ",") Update healthcheck-container version to 2.3.0 for logging enhancements and updated base image. Issue-ID: DCAEGEN2-2968 Issue-ID: DCAEGEN2-2958 Issue-ID: DCAEGEN2-2983 Signed-off-by: Jack Lucas <jflos@sonoris.net> Change-Id: I4bcce1d3e43e2e5c7cc2c3179870de72b55d5d2e
2021-03-21	[DCAEGEN2] Deploy DCAE microservices via Helm	Jack Lucas	1	-0/+28
	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>