Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Id8626c02f4c8bf3e1da406920169c0ed6bee457f
Issue-ID: SDC-2798
Signed-off-by: MichaelMorris <michael.morris@est.tech>
|
|
Move OOM to use SDC cassandra 3
Issue-ID: SDC-2595
Signed-off-by: shrek2000 <oren.kleks@amdocs.com>
Change-Id: Ie58f3420cad70fbed7931656a98951e69a4b7b4b
Signed-off-by: shrek2000 <oren.kleks@amdocs.com>
|
|
ONAP is too big to be deployed using helm install so we need to
use a custom helm plugin helm deploy. This script deloys onap
component by component instead of deploying evrything at
once. Unfortunately this script also modifies the helm release by
appending component name to it.
As a result of this behavior our objects are called for example:
onap-mariadb-galera-mariadb-galera-0
instead of just being called onap-mariadb-galera-0.
This patch simplifies this naming convention by replacing all direct
usages of .Release.Name with common.release macro which strips the
component specific part from the release name.
Issue-ID: OOM-2275
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: Ia8cead50d305adb00eef666d0a1ace74479b5183
|
|
Issue-ID: OOM-2187
Change-Id: I2ae6b0f2482641b3f482121354596574b684b2d1
Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
|
|
Proper configuration for HTTPS in the sdc:
-configured the livenessProbe/readinessProbe ports
-changed mount path for dcea-be components
-updated dcea component images
-updated VID and Portal to talk with the SDC
Change-Id: Ibdece8f095aaa79e326cb9c4510e8227a7856b15
Issue-ID: SDC-2548
Signed-off-by: Krystian Kedron <k.kedron@partner.samsung.com>
|
|
Signed-off-by: Yang Xu <yang.xu@futurewei.com>
Issue-ID: SDC-2375
Change-Id: I459359828485c31a247a495674eb450af9fdf167
|
|
Signed-off-by: Yang Xu <yang.xu@futurewei.com>
Issue-ID: INT-1106
Change-Id: I09966ff3735a10342a6dd2e4a394eab95d46fb05
|
|
tcpSocket probe does not work for the web application
Kubernetes will never detect that, and will never try to re-create the pod.
liveness probe based on the health-check API can be used.
Issue-ID: SDC-1986
Change-Id: I93720e19feb2ff558fa6c4dc3ababdbfa2eda102
Signed-off-by: amitjai <amitjai@amdocs.com>
|
|
SDC Fix initial values
Change-Id: I0723c936cca909c428abf9c522eb3e115662c8c1
Issue-ID: SDC-1893
Signed-off-by: Areli, Fuss (af732p) <areli.fuss@intl.att.com>
|
|
Issue-ID: OOM-1145
Change-Id: I1510339a820802554b6e8b9a201619ef66be17a0
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
Issue-ID: OOM-1161
Change-Id: Ie8dbf32d2b77ed839be65f812cf2762f76f574c5
Signed-off-by: Mukul <mukul.joshi@amdocs.com>
|
|
Issue-ID: OOM-1390
Change-Id: I8fe0dbde62cb8d88ec18321078ea6740bad8524a
Signed-off-by: toshrajbhardwaj <toshrajbhardwaj@gmail.com>
|
|
Issue-ID: OOM-1306
Change-Id: I1a617718006ee845d675fead74ce075c3390ac2f
Signed-off-by: toshrajbhardwaj <toshrajbhardwaj@gmail.com>
|
|
Updated pod and job dependencies to provide consistent startup order.
Change-Id: Ib0d6aefbd59d30a5dd0f121415e3e8b4e3dcba01
Issue-ID: OOM-1022
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|
|
-adding sdc-onboarding-be chart
-sdc-cs and es are now in a cluster format
-using the sdc provided ready probe script for readiness
-increasing the initial delay as per sdc project team k8s specs
-fixed logging bugs. logs for be, fe, onboard-be are now in /var/log/onap/sdc/blah
-sdc-be readiness health check is failing which prevents sdb-be from
becoming "ready".
-the commit that changes the template is:
Add cluster resiliance support (c033cdce906efc3b6ccd1d2f45544af47e328ed4)
Issue-ID: OOM-1002
Change-Id: Ib231cb1e7daa287a41e04db95528edecbdbbf7bc
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
Issue-ID: OOM-906
Change-Id: Ic65127d3981cb0a696c784392cab59fbf06b1e66
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
-Basically compared docker_run.sh from sdc master branch
with charts/values in OOM
-disabling sdc-kb liveness until we tune the timing of it
Issue-ID: OOM-964
Change-Id: I7447eed47c919d5d64786f45e01b5f2a3bc490a0
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
-missed adding it to the original review before it was merged
Issue-ID: OOM-838
Change-Id: I04b515e2f4c58a14b4b4194e59e160b1f8534bc6
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
all pods come up
robot health reports HTTP 500 -> mostly due to missing dmaap
resolving filebeat merge conflict
addressing CI comments
do we need a pv/pvc for the logs?
Issue-ID: OOM-747
Change-Id: Id6f1e57fdaf3cd6d9f75e8bc1e5bfde39b91235e
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
Signed-off-by: Areli Fuss <af732p@intl.att.com>
(cherry picked from commit fe3e499547c91eadd71bde630594720b918c2af9)
|