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-24	Make all services independent of helm Release.Name	BorislavG	1	-0/+1
	Issue-ID: OOM-906 Change-Id: Ic65127d3981cb0a696c784392cab59fbf06b1e66 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-04-20	fixing sdc health check	Mandeep Khinda	1	-1/+2
	-Basically compared docker_run.sh from sdc master branch with charts/values in OOM -disabling sdc-kb liveness until we tune the timing of it Issue-ID: OOM-964 Change-Id: I7447eed47c919d5d64786f45e01b5f2a3bc490a0 Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-04-16	Update readiness-check version	BorislavG	1	-1/+1
	Readiness check version is not sinchronized in many pods This causing deployment failures. Issue-ID: OOM-936 Change-Id: Ieef91df17836adcdf24db536440d0a1624a50591 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-03-29	adding license to SDC chart templates	Mandeep Khinda	1	-0/+14
	-missed adding it to the original review before it was merged Issue-ID: OOM-838 Change-Id: I04b515e2f4c58a14b4b4194e59e160b1f8534bc6 Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-03-28	standardizing SDC helm charts	Mandeep Khinda	1	-0/+101
	all pods come up robot health reports HTTP 500 -> mostly due to missing dmaap resolving filebeat merge conflict addressing CI comments do we need a pv/pvc for the logs? Issue-ID: OOM-747 Change-Id: Id6f1e57fdaf3cd6d9f75e8bc1e5bfde39b91235e Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com> Signed-off-by: Areli Fuss <af732p@intl.att.com> (cherry picked from commit fe3e499547c91eadd71bde630594720b918c2af9)