Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
* Update kubernetes/aai from branch 'master'
to fde14dd1e9fec136f6ff9489dcb66ed8102ddb17
- Changing graphgraph nodeport
Signed-off-by: Pavel Paroulek <pavel.paroulek@orange.com>
Issue-ID: AAI-2596
Change-Id: I1259a884668c844447ca33c9c84334746db022fe
|
|
|
|
|
|
|
|
|
|
Issue-ID: OOM-1997
Signed-off-by: Akansha Dua <akansha.dua@amdocs.com>
Change-Id: I3a8b117c81219f75231bec6b61c99fe2dbcd0485
|
|
|
|
|
|
Removed exposed port 4001 by JDWP in sdc-onboarding-be
Issue-ID: OJSI-78
Signed-off-by: Robert Bogacki <r.bogacki@samsung.com>
Change-Id: Ied6cb6bd08358a03a44213545d3fb1928f7d008d
(cherry picked from commit 45d7963968e8d4a3be9c5f4d5df4224116804080)
|
|
Removed exposed port 6000 by JDWP in sdc-fe
Issue-ID: OJSI-77
Signed-off-by: Robert Bogacki <r.bogacki@samsung.com>
Change-Id: I9bfad007983510a8b877731fd35bffcf16590086
(cherry picked from commit fce96df6504488b7de1a71b75ecfd1d9272dfdfd)
|
|
Removed exposed port 7000 by JDWP in sdc-wfd-fe
Issue-ID: OJSI-80
Signed-off-by: Robert Bogacki <r.bogacki@samsung.com>
Change-Id: I356452da25b641e2e1c0ecf4cd8de69ffe4cd77d
(cherry picked from commit 3339ae164f3e3c7a4e8b0f45ebfc1c59826f9870)
|
|
Updated xacml-pdp config to add parameters so that it can connect to
policy-api to retrieve policy types.
Change-Id: Ib2fbd1523936a5b7c080e806b66eb0d31cb50365
Issue-ID: POLICY-2021
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
* Update kubernetes/aai from branch 'master'
to 3efe1df6fdba4af4e22849bec220c8daa4a68a49
- Adding Graphgraph k8s config
Issue-ID: AAI-531
Signed-off-by: Pavel Paroulek <pavel.paroulek@orange.com>
Change-Id: I2cb6471a0369ef8cc3f36b9988ff0df2045564a0
|
|
|
|
|
|
Mainly adding release label there."
|
|
|
|
|
|
|
|
|
|
Issue-ID: SO-2223
Signed-off-by: seshukm <seshu.kumar.m@huawei.com>
Change-Id: I978a79f2232505e42ff470aab53614d13fa629f7
|
|
|
|
|
|
|
|
|
|
|
|
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>
|
|
|
|
|
|
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>
|