Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2018-03-01 | Run all components in one namespace | BorislavG | 1 | -2/+5 | |
Change-Id: I5fcd4d577c1fda4de27842807c7cf7a5d372756e Issue-ID: OOM-722 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com> | |||||
2018-02-25 | sdnc persistence folder parametrization | kerenj | 1 | -1/+1 | |
Issue-ID: OOM-145 Change-Id: I40ace4ebb463ca83e1a11badc2e37913c40e8102 Signed-off-by: kerenj <keren.joseph@amdocs.com> | |||||
2018-02-14 | Replica Scaling of SDNC Container | vaibhav_16dec | 1 | -1/+1 | |
Issue-ID: OOM-685 Change-Id: I5fe35221adfd95327d05586536f936e539ac6b17 Signed-off-by: vaibhav_16dec <vaibhav.chopra@amdocs.com> | |||||
2017-12-20 | Single K8S Node Of Deploying SDNC Cluster POC | Hao Kuang | 1 | -0/+55 | |
It's a reference of how to deploy sdnc cluster under single node k8s environment. Currently the config of nfs for mysql db only supports one k8s node. For mutiple nodes, because of dockernfs mount, nfs provisioner has conflict with it, which fails mount operation of SDNC pod. Also, if SDNC needs to fully utilize mysql cluster under k8s, in core project, DbLibService.java should be enhanced to support that writing to master only and reading from them. Issue-ID: SDNC-163 Change-Id: I85ad327f2fe04fe8e9a135289d7c25a917234438 Signed-off-by: Hao Kuang <Hao.Kuang@amdocs.com> |