Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
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>
|
|
Today when deploying SDC with OOM, the PersistentVolumeClaim needs the
"ReadWriteMany" (or "RWX") capability.
According to Kubernetes Documentation (https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes),
ReadWriteMany stands for "the volume can be mounted as read-write by many nodes".
That means that a particular PVC needs to be read and written from many pods.
That also means that your code takes that into account and do the work to avoid
write at the same place at the same time.
An issue on RWX mode is that most "official" storage driver from Kubernetes doesn't
support it (13 over the 19 drivers doesn't support it, espacially OpenStack, Amazon
and Google storage classes).
SDC PVC for ES is used only for one POD.
Thus we don't need RWX.
The other values are not used as of today but changing them to RWO seems
better if they're reused again
Change-Id: I3dabbce120a14d19499330b51e808c5725588e0c
Issue-ID: SDC-2549
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Issue-ID: TEST-185
Change-Id: I2bce2a44aa540a846933c548dd0ab67f3e53e679
Signed-off-by: Brian Freeman <bf1936@att.com>
|
|
Upgrade SDC from Titan to Janus Graph
Change-Id: I3f14e07b3eb54401f806687e3110559ada5b7496
Issue-ID: SDC-2296
Signed-off-by: shrikantawachar <shrikant.awachar@amdocs.com>
|
|
Change-Id: I78125eed15afe4ee5f54c1334fe9d7c3261efd64
Issue-ID: SDC-2272
Signed-off-by: Ofir Sonsino <os0695@intl.att.com>
|
|
Change-Id: Ia601a7b4420adcfc82526805ab496c6194962b5e
Issue-ID: SDC-2272
Signed-off-by: Sonsino, Ofir (os0695) <os0695@intl.att.com>
|
|
Change-Id: I2ea2841c6902b786446c7bc850183fa21552214a
Issue-ID: OOM-1203
Signed-off-by: Mahendra Raghuwanshi <mahendra.raghuwanshi@amdocs.com>
|
|
Change-Id: Idb21ab06e23d4e0b38af2033f2bdfa96d7ce2bad
Issue-ID: SDC-1913
Signed-off-by: Sonsino, Ofir (os0695) <os0695@intl.att.com>
|
|
Sync docker tags with the release manifest from integration
repo commit 4c69929dd0acb06a028fabdbdab060be4db6348b.
Change-Id: I9795a9a316b8ab6c959655fee5f7ef65fbfea78c
Issue-ID: INT-663
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
Sync docker tags with the release manifest from integration
repo commit a7c98ae0fabb0a94fbdc030e6f7c519439923045.
Change-Id: Idb73aa4f05a948b7e1d70723cc6a52b8fd6f0517
Issue-ID: INT-663
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
Sync docker tags with the release manifest from integration
repo commit 0aad96cbbcdb97c2b074cb83d367c29dac6243df.
Issue-ID: INT-663
Change-Id: I877077c3a35cb196c89ebb0e27dfe452e12b5249
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
Sync docker tags with the release manifest from integration
repo commit a71e3709faa5f281361ddfcd79eb4bd11550edca.
Change-Id: Ib937100d49aedced19a83593596906cadabc12e4
Issue-ID: INT-663
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
SDC Fix initial values
Change-Id: I0723c936cca909c428abf9c522eb3e115662c8c1
Issue-ID: SDC-1893
Signed-off-by: Areli, Fuss (af732p) <areli.fuss@intl.att.com>
|
|
Sync docker tags with the release manifest from integration
repo commit 90e136c83ec5434abaeb9939b995f86aa4089850.
Change-Id: I771393adb429087752dc52df2cd2812dc9ff6a11
Issue-ID: INT-663
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
Sync docker tags with the release manifest. It is
assumed that the release manifest is the
"single source of truth" and that the versions in
the helm charts are out of date.
Change-Id: I2902e60b25f57409dd616780a626e63c92d26769
Issue-ID: INT-663
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
Adds the ability to turn them off if they are found to
cause issues
also cleaning up some whitespace
Issue-ID: OOM-1145
Change-Id: Idf0ee21f70e1bf65813b7f51ea028f2783a01cf8
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
|
|
|
|
Change-Id: Ic8f11dc20c425aab144fe28a5e761552eb7b025b
Issue-ID: OOM-1422
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
Issue-ID: OOM-1161
Change-Id: Ie8dbf32d2b77ed839be65f812cf2762f76f574c5
Signed-off-by: Mukul <mukul.joshi@amdocs.com>
|
|
As Robot and all has changed to interact with master
version of SDC code, we need to deploy proper SDC code.
Change-Id: I0b1f25485edefdc56fe54bc3633bf1f028b4b8e5
Issue-ID: OOM-1408
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
Issue-ID: OOM-1306
Change-Id: I1a617718006ee845d675fead74ce075c3390ac2f
Signed-off-by: toshrajbhardwaj <toshrajbhardwaj@gmail.com>
|
|
Sync OOM docker versions with docker-manifest.csv commit
a6e05c8c18624a1794abb1d3a3ab879a7a06bcfe
Change-Id: If8df538638670e0f1080d41d40d06de54ab1d93a
Issue-ID: OOM-1053
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
Change-Id: I2d1ff878c215becc9856af184eb0b11defd75e1d
Issue-ID: OOM-1064
Signed-off-by: BorislavG <Borislav.Glozman@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>
|
|
Readiness check version is not sinchronized in many pods
This causing deployment failures.
Issue-ID: OOM-936
Change-Id: Ieef91df17836adcdf24db536440d0a1624a50591
Signed-off-by: BorislavG <Borislav.Glozman@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)
|