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-09-04	[GENERAL] Use readiness container v3.0.1	Sylvain Desbureaux	1	-2/+1
	Readiness container v3.x and up are now present in ONAP main repository. They're also not using root user anymore and then script path has changed. Finally, "job_complete" script has been integrated in main "ready" script. As those changes are significant, we must upgrade all the components at once. Depends-On: I5afa83892043f4844afe12e61724a8d368a9f2e0 Issue-ID: OOM-2545 Signed-off-by: Grzegorz Lis <grzegorz.lis@nokia.com> Change-Id: I0b4eb5dd86390273532d67d0a9696e1cfcadf110
2020-06-25	[DCAE][DCAEMOD] Deploy R7 container images	Jack Lucas	1	-0/+69
	Deploy new versions of cm-container, k8s-bootstrap-container and healthcheck-container for DCAE. Deploy a healthcheck-container for DCAEMOD. Add readiness checks for aaf-cm for dcae-cloudify-manager, dcae-inventory-api, and dcae-config-binding-service, to avoid crash loops in the init phase. Issue-ID: DCAEGEN2-2099 Issue-ID: DCAEGEN2-1789 Issue-ID: DCAEGEN2-2236 Issue-ID: DCAEGEN2-1864 Signed-off-by: Jack Lucas <jflucas@research.att.com> Change-Id: I473a0cd0e3e00d39e6c33d87781581ec527fbc89