Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
Issue-ID: MULTICLOUD-775
Signed-off-by: Haibin Huang <haibin.huang@intel.com>
Change-Id: Ieeab8ba5e6fd5f9d307f6ec996ca724058a08c1b
|
|
|
|
Change-Id: I2c4c57ba9783a4daae3584fcb9772569482d5b48
Issue-ID: OOM-2041
Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
|
|
Mainly adding release label there.
Issue-ID: OOM-2043
Signed-off-by: Ondřej Šmalec <o.smalec@partner.samsung.com>
Change-Id: Ieeedec79fd85b7ede4752a973ec42ea648f7d6a0
Signed-off-by: Ondřej Šmalec <o.smalec@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>
|
|
Today when deploying Policy 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).
Modeling PVC for is used only for one POD.
Thus we don't need RWX.
Change-Id: Ic4b8f5a336f2b9edfdf25ef3cc549b389f9b6f65
Issue-ID: MODELING-213
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Today when deploying Portal 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).
Portal PVC are only used by a mariadb instance or a cassandra instance.
Thus we don't need RWX.
Change-Id: I706e13759d3af829d61d7a33d068263aaf9e9158
Issue-ID: PORTAL-724
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
|
|
|
|
RKE."
|
|
Update SDNC helm charts to use Neon-based El Alto images
Change-Id: If91320bc663992355f665b3f57f77214e96985cd
Issue-ID: SDNC-874
Signed-off-by: Timoney, Dan (dt5972) <dtimoney@att.com>
|
|
Issue-ID: OOM-2083
Signed-off-by: Marco Platania <platania@research.att.com>
Change-Id: I0318115d85d8507ecba1133d6c8c1a2bc6333b63
|
|
|
|
|
|
Today when deploying Policy 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).
Policy PVC for Nexus and Policy PVC for mariadb are used only for one POD.
Thus we don't need RWX.
Change-Id: Idf8a6ba8ef14ce7ca397438c2200c11517d0458e
Issue-ID: POLICY-2019
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
RWO is sufficient for DMaaP PVC.
Change-Id: I35339948b3164e83b92d2e81a1c772574ebb9e9a
Issue-ID: DMAAP-1285
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Today when deploying CLAMP 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).
CLAMP PVC is used only for one ES instance. Thus we don't need RWX.
Change-Id: I3a17195bca4f0f01b5cdb0d8e803bb2a8ab2dd38
Issue-ID: CLAMP-488
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Mariadb PVC are created in 1 to 1 mapping with galera replicas thus we
don't need RWX.
Change-Id: I438855b2d4b2f90932387e056c168b0a995975a5
Issue-ID: OOM-2081
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Today when deploying NBI 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).
MongoDb PVC is used only for one Mongo instance and it's the same for
maria. Thus we don't need RWX
Change-Id: I4d54cd7853778d8ba6c83551a211abe34d383382
Issue-ID: EXTAPI-305
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
✔ El-Alto first wave
Issue-ID: VID-521
Change-Id: Ic34065a28a47d07e408ad345b493404a055740c6
Signed-off-by: Ittay Stern <ittay.stern@att.com>
|
|
Due to SSL support for CBS Client in SDK new ENVs containing
paths to the certs & their passwords were added:
- truststore path
- truststore password path
- keystore path
- keystore password path
Issue-ID: DCAEGEN2-1552
Signed-off-by: Piotr Wielebski <piotr.wielebski@nokia.com>
Change-Id: Ib73048454db45a81d553afbe2d80fbb6253be711
|
|
Issue-ID: OOM-2050
Signed-off-by: Ondřej Šmalec <o.smalec@partner.samsung.com>
Change-Id: I7d54c4c8adc192d0c27249dde2fad4af2ed0a52a
|
|
# Increase docker images
# Refactor global vars
# Fix logstash paths etc
# Remove default feed script
Change-Id: Ib15fecc57d6f7f2d4049eff7903c08bc3adb78da
Issue-ID: DMAAP-1283
Signed-off-by: efiacor <fiachra.corcoran@est.tech>
|
|
Issue-ID: MULTICLOUD-718
Change-Id: Iaba6a4b72c20f19eaf04c40e7beac47723bb8f78
Signed-off-by: Liang Ding <liang.ding@intel.com>
|
|
Issue-ID: CCSDK-1623
Signed-off-by: Oleg Mitsura <oleg.mitsura@amdocs.com>
Change-Id: Ie441afb7db312492c4abfe9590c271bf2a08d81b
|
|
|
|
to comply for jolokia security
vulnerability, another three AAA users
will be added
Issue-ID: OJSI-63
Change-Id: I476df578f457f862a76afec2df6ded34bb3cae64
Signed-off-by: Taka Cho <takamune.cho@att.com>
|
|
|
|
|
|
SO datasource config update as per
new Hikari library changes in SO
Issue-ID: OOM-1970
Signed-off-by: sarada prasad sahoo <sarada.prasad.sahoo@huawei.com>
Change-Id: I84ca506936c332775fd20f604e6f553f94a4dc74
Signed-off-by: sarada prasad sahoo <sarada.prasad.sahoo@huawei.com>
|
|
the old URL is not
working with AAF 2.1.15 image
Issue-ID: AAF-942
Change-Id: I83cabb1048ccd87313784d45ffe27c967d9502c3
Signed-off-by: Taka Cho <takamune.cho@att.com>
|
|
* Update kubernetes/robot from branch 'master'
to b6b5b0e6f8880e3a922a2fef97e95e5013475228
- these are not used anywhere so removing to avoid confusion
Issue-ID: TEST-184
Change-Id: I227f0002f36a72e350f0008eef20661ee04c3e26
Signed-off-by: DR695H <dr695h@att.com>
|
|
Add files to tune akka settings in OpenDaylight.
Also, added setenv to tune Java settings.
Change-Id: I2071fceb48f990929cd9f4c885bd0c9f7db0263c
Issue-ID: SDNC-858
Signed-off-by: Timoney, Dan (dt5972) <dtimoney@att.com>
|
|
RKE.
Issue-ID: OOM-2050
Signed-off-by: Ondřej Šmalec <o.smalec@partner.samsung.com>
Change-Id: I72802282d296c6e1f23f96112a6406ded18aa5ab
|
|
|
|
Issue-ID: DMAAP-1272
Change-Id: I193bfae6dc39d584838cb3da561684dc7854499c
Signed-off-by: su622b <su622b@att.com>
|
|
Remove http node port 30202. Users should instead use https node
port 30267
Change-Id: I44a907126384092b5f18ad85115c6269279c9d80
Issue-ID: OJSI-99
Signed-off-by: Timoney, Dan (dt5972) <dtimoney@att.com>
|
|
Change-Id: Icc7eaff6798367f717680c051b146fa5a4860278
Issue-ID: SDC-2521
Signed-off-by: Ofir Sonsino <os0695@intl.att.com>
(cherry picked from commit d7b6ac82af6349f96910c059aa50432c1c04b5e8)
|
|
Update sdnc version to 1.6.2 to pick up fixes:
SDNC-855
SDNC-853
Change-Id: I2ee5f3d892c9204d56ce7c92f5503b605a607de7
Issue-ID: SDNC-855
Signed-off-by: Timoney, Dan (dt5972) <dtimoney@att.com>
|
|
* Update kubernetes/robot from branch 'master'
to d5025d6ad1b1741e15ef09873b6a0ba65a8da717
- moving endpoints for SO to properties
Issue-ID: INT-1205
Change-Id: If313f3919df3a19616e91fbac3f03a33a617baa1
Signed-off-by: DR695H <dr695h@att.com>
|
|
* Update kubernetes/robot from branch 'master'
to 95cf864561df0b88aee012cd38589f301df8f6b5
- updating to latest release
Issue-ID: TEST-184
Change-Id: I2ed9c05b47e2d2c3d53811aa0bfcae7a7507f72f
Signed-off-by: DR695H <dr695h@att.com>
|
|
|
|
|
|
* Update kubernetes/aai from branch 'master'
to 55cb73cadc59537643c0fe5cb7ededadc9ff2b48
- Add misc as a volumeMount
Issue-ID: AAI-2440
Signed-off-by: Jimmy Forsyth <jf2512@att.com>
Change-Id: Ie9b90135cac72c4eadd5e727e79ff505ceaf934f
|
|
evert Kafka Docker image to onap/dmaap/kafka111:1.0.1
Changes related to AAF image changes
Fix the logback.xml errors
Enhancements to ZooKeeper ensemble and Kafka cluster lookup
Issue-ID: DMAAP-1272
Change-Id: I53e9cff94c9ccf83f82383fe865f31d16f5416bc
Signed-off-by: su622b <su622b@att.com>
|
|
|
|
|