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
2019-04-10	default storageclass and nfs provisioner	sushil masal	1	-0/+34
	Issue-ID: OOM-1500 Change-Id: I15dd98ea8042914220f1b6025e93f65224bb9adb Signed-off-by: sushil masal <sushil.masal@amdocs.com>
2018-05-10	Improve docker registry secret management	BorislavG	1	-2/+2
	Change-Id: I2d1ff878c215becc9856af184eb0b11defd75e1d Issue-ID: OOM-1064 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-03-22	Move deployment-specific templates to parent chart	Mike Elliott	2	-0/+59
	This change provides a single centralized location (onap parent chart) to change/install secrets, persistent volumes, service account(s), RBAC and configuration overrides. It also eliminates the need for a 2-step install of setup and application charts. Users would customize the onap parent chart to install both the deployment-specific resources and one or more "enabled" sub charts, using a command like the following: helm install local/onap -f dev.yaml where dev.yaml (or prod.yaml, etc.) provides the customization of application subcharts to deploy. Change-Id: Idbef28ffa404ea35922a4c3994605bdc27f3471e Issue-ID: OOM-817 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>