Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I41330836901ccf1fcbdd0f9d6e720ce13ea3a9ea
Issue-ID: OOM-1651
Signed-off-by: Mahendra Raghuwanshi <mahendra.raghuwanshi@amdocs.com>
|
|
Change-Id: I7a9f462d1e494e2f9b5ab5df78c2b406aa1bde4d
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: SDNC-454
|
|
Change-Id: I94a0aa4af1516a208b91f2509a713d59fcc81573
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: SDNC-234
|
|
Addressing issues like:
- missing property files
- hard-coded ports
- hard-coded ODL passwords
- improper configMap mounts
- incorrect service names
Change-Id: I74726ffedbfc20e164a814ca8777a699b92b3d65
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: SDNC-310
|
|
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
|
|
Change-Id: I9f4d43c2a3f0766b9c8477a180f5a0bd45fde243
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: OOM-748
|