Age | Commit message (Collapse) | Author | Files | Lines |
|
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: I5ca369f43e8863f9ae3ec3f5d648740808a5e099
|
|
Fix config of admin portal to expose https instead of http
Change-Id: Ie5d94921fd0fdbe0ea4866385f07fa8859ba59a6
Issue-ID: OJSI-98
Signed-off-by: Timoney, Dan (dt5972) <dtimoney@att.com>
|
|
Change-Id: I41330836901ccf1fcbdd0f9d6e720ce13ea3a9ea
Issue-ID: OOM-1651
Signed-off-by: Mahendra Raghuwanshi <mahendra.raghuwanshi@amdocs.com>
|
|
Change-Id: Ic5eda9c33abca03e2f0bc788261a3a769c5ad7ab
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: OOM-970
|
|
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
|
|
Change-Id: If925a7855b83beba86e769c1350fd65dc4165531
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: OOM-1049
|
|
With these changes, the SDNC Portal pod is now coming up cleanly and there
are no errors in the logs. I was able to successfully create a user and log
in to the portal.
Change-Id: Iab3374c585a0b88844e83860d14e572e151958a6
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: OOM-881
|
|
Change-Id: I9f4d43c2a3f0766b9c8477a180f5a0bd45fde243
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: OOM-748
|