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
2018-04-30	Integration w common/postgres	Dominic Lunanuova	1	-10/+0
	Patchset 1: first cut at integration with common/postgres Patchset 2: Mandeep Khinda - refactored charts to standardize Wired in shared postgres chart Patchset 6: Introduced simple dmaap/Makefile to force helm dep up in the deeper charts directory. Includes slight modification to parent make clean target Patchset 8: merge conflict again Change-Id: If59f08638bac8761ae5452b60f172c99fcf4ec86 Signed-off-by: Dominic Lunanuova <dgl@research.att.com> Issue-ID: DMAAP-117 Signed-off-by: Dominic Lunanuova <dgl@research.att.com>
2018-04-04	Initial chart for dmaap - 2nd attempt	Dominic Lunanuova	1	-0/+10
	This should conform to new OOM standard helm structure. It starts a directory called dmaap which will hold all dmaap components. But for now it only has buscontroller. Once we get this working, we can add message-router. (see DMAAP-386) Patch 2 gets private postgresql working. I'd prefer to integreate with common postgresql from Tony in a future commit to avoid any immediate delivery timing dependency. Patch 3 corrects some port mapping from service to pod. Change-Id: Id9838d7ddb2ccccfc8b0e3f3b9e50f9b5672c484 Signed-off-by: Dominic Lunanuova <dgl@research.att.com> Issue-ID: DMAAP-117 Signed-off-by: Dominic Lunanuova <dgl@research.att.com>