Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
Change-Id: I2ea2841c6902b786446c7bc850183fa21552214a
Issue-ID: OOM-1203
Signed-off-by: Mahendra Raghuwanshi <mahendra.raghuwanshi@amdocs.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-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>
|
|
Issue-ID: OOM-851
Change-Id: I431a54d7b218a7271efba8496a71412085052959
Signed-off-by: kj <keren.joseph@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)
|