Code Review / oom.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 615f949) | patch
Fix SDNC DMaaP connectivity issues 59/45159/1
authorjmac <james.macnider@amdocs.com>
Fri, 27 Apr 2018 19:45:00 +0000 (19:45 +0000)
committerjmac <james.macnider@amdocs.com>
Fri, 27 Apr 2018 19:48:27 +0000 (19:48 +0000)
commitb717cce649889ecf9d324f0b463586972e61899e
tree11f07d3f4788edf22b5a8b00e34b6a58e2f26933tree | snapshot
parent615f9490a7d99ab1345f72645f1816a70e2753eacommit | diff
Fix SDNC DMaaP connectivity issues

DMaaP listener was not trying to connect to the right service name, so
it was failing.

In addition, the pod doesn't wait for the dmaap pod to be up and running
before starting, so I've added that dependency.

Lastly, I removed the config of the DMaaP port from the top level values.yaml
files, as out of the box it's very unlikely this would be changed.

Change-Id: I5a190b39f4f163b020189ac9dd178040f80125cd
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: SDNC-293
kubernetes/onap/resources/environments/dev.yaml diff | blob | history
kubernetes/onap/values.yaml diff | blob | history
kubernetes/sdnc/charts/dmaap-listener/resources/config/dhcpalert.properties diff | blob | history
kubernetes/sdnc/charts/dmaap-listener/templates/deployment.yaml diff | blob | history
kubernetes/sdnc/charts/dmaap-listener/values.yaml diff | blob | history
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).