summaryrefslogtreecommitdiffstats
path: root/kubernetes/sdnc/charts/dmaap-listener/resources
AgeCommit message (Collapse)AuthorFilesLines
2020-06-19Fix SDNC DMAAP consumer properties in HELM chartsSandeep Shah3-7/+7
Minor configuration changes required in 3 SDNC DMAAP listener/consumer properties Issue-ID: OOM-2400 Signed-off-by: Dan Timoney <dtimoney@att.com> Change-Id: I329d0cb6e7f706ff3ad22eabdbcce442a9c56410
2020-04-07Add dmaap-listener prop filesDan Timoney6-3/+108
Add dmaap-listener properties files Issue-ID: SDNC-1138 Signed-off-by: Dan Timoney <dtimoney@att.com> Change-Id: I534871a3d690bf86cb2e655f8fb6910a04a1a559
2020-02-21[SDNC] Use common secret template in dmaap-listenerKrzysztof Opasiak4-12/+11
Whole SDNC strongly depends on the assumption that it is using a common mariadb-galera instance and that root password is secret password. Also user and password to sdnc DB is hardcoded. Let's start working on removing this assumption and component by component add support for local and shared mariadb instance without hardcoding any passwords to the database. In this patch all passwords are still hardcoded in the helm chart to not break other parts of SDNC. Those values will be removed in a final patch. Issue-ID: OOM-2309 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I3280f9d7ff4933d4e50b94ca248676ed9aa6688d
2019-04-12SDNC using shared mariadb-galera clusterMahendra Raghuwanshi1-1/+1
Change-Id: I41330836901ccf1fcbdd0f9d6e720ce13ea3a9ea Issue-ID: OOM-1651 Signed-off-by: Mahendra Raghuwanshi <mahendra.raghuwanshi@amdocs.com>
2018-09-18add missing properties for SDNC DMaaP listenerjmac1-0/+35
Change-Id: I7a9f462d1e494e2f9b5ab5df78c2b406aa1bde4d Signed-off-by: jmac <james.macnider@amdocs.com> Issue-ID: SDNC-454
2018-05-23Fix id parameter DMaaP propertiesjmac1-1/+1
Change-Id: I94a0aa4af1516a208b91f2509a713d59fcc81573 Signed-off-by: jmac <james.macnider@amdocs.com> Issue-ID: SDNC-234
2018-05-11General cleanup of SDNC chartsjmac3-3/+70
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
2018-04-27Fix SDNC DMaaP connectivity issuesjmac1-1/+1
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
2018-04-02Add Standardized Configuration to SDN-C Chartjmac1-0/+35
Change-Id: I9f4d43c2a3f0766b9c8477a180f5a0bd45fde243 Signed-off-by: jmac <james.macnider@amdocs.com> Issue-ID: OOM-748