Age | Commit message (Collapse) | Author | Files | Lines |
|
Add the frontend container as the main chart, and add clamp-backend as
the a sub chart
Issue-ID: CLAMP-486
Change-Id: Ib02562d608011047157b77b302902de86c0d954d
Signed-off-by: sebdet <sebastien.determe@intl.att.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fix the image name and SQL for mariadb as it has been updated
Issue-ID: CLAMP-467
Change-Id: I0bb9bf48b86a8eb3cc7a0f74dd5a5f20e46e8b44
Signed-off-by: sebdet <sebastien.determe@intl.att.com>
|
|
|
|
Issue-ID: OOM-2076
Signed-off-by: Akansha Dua <akansha.dua@amdocs.com>
Change-Id: Ide894e27c417a3e2a010cbc24f18353ffe698ce5
|
|
Issue-ID: PORTAL-709
Signed-off-by: Welch, Lorraine (lb2391) <lb2391@att.com>
Change-Id: I70c35ebcaf76fa157da777c28cca6513a22c4465
|
|
|
|
|
|
* 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
|
|
Issue-ID: OOM-2088
Signed-off-by: Akansha Dua <akansha.dua@amdocs.com>
Change-Id: Ie7f25c812984abc8631a86b2385dd14a365a8ea5
|
|
|
|
Removed exposed port 7001 by JDWP in sdc-wfd-be
Issue-ID: OJSI-79
Signed-off-by: Robert Bogacki <r.bogacki@samsung.com>
Change-Id: I5ccad4c0d5330bd7e0bffa2cca6b7e3d8ef18f6a
(cherry picked from commit 09dca2aef073f493e63f11198f44246008567597)
|
|
|
|
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)
|
|
Removed exposed port 4000 by JDWP in sdc-wfd-be
Issue-ID: OJSI-76
Signed-off-by: Robert Bogacki <r.bogacki@samsung.com>
Change-Id: I9e9caa59623c58d1deebd3320cdfce9f73c83ebc
(cherry picked from commit 674916aa2b762a45e4a394ea6ea1198cf8965c8c)
|
|
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>
|
|
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>
|