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-01-24	Deploy loadbalancer service opening UEB port	Alexis de Talhouët	1	-3/+1
	With the support of DCAE added lately, some change was done to accomadate the resolution of some ONAP service for DCAE. Among other things, UEB configuration in SDC is now using external resolution, no longer the internal K8S one. Hence for deployement not deploying DCAEGEN2, we still have to deploy the loadblancer service. Change-Id: I93d0c01920755beed3eeb05d158530c05c255383 Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com> Issue-ID: OOM-608
2018-01-16	Add support for DCAE in Amsterdam	Alexis de Talhouët	1	-0/+53
	- add nginx container to reverse proxy hostname coming from DCAE world to OOM world. - create DNS zone in Designate for simpledemo.onap.org. to point to the K8S hosts where dcaegen2 service is running. - add heat stack to deploy DCAE - update SDC configuration file to dynamically inject the UEB servers as those are in reality the k8s nodes ip addresses, as the dmaap service port is exposed by the dcaegen2 service. This is done because the service-change-handler container deployed by DCAE is getting the UEB servers IP list from SDC itself, hence to enable resolution in the DCAE VM, the IP has to be reachable. (Hence this config assume DCAE VMs can route to K8S hosts). Previous config was using dmaap.onap-message-router for UEB servers host, but this is not resolvable by any DNS. - add knob to deploy DCAE or not - add DCAE related parameters in onap-parameters.yaml (initial config) - fix DCAE healthcheck - add support to keystone v2.0 and v3 - fix vm_properties robot file Change-Id: I64ec6faf7b45b293bf7110e9e23e31798bf9b841 Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com> Issue-ID: OOM-508