aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2019-09-04Removed exposed debug port 4001 in SDCr.bogacki1-1/+1
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)
2019-09-04Removed exposed debug port 6000 in SDCr.bogacki1-1/+1
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)
2019-09-04Removed exposed debug port 7000 in SDCr.bogacki1-1/+1
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)
2019-09-04Removed exposed debug port 4000 in SDCr.bogacki1-1/+1
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)
2019-09-03Add policy-api to xacml-pdp config for OOMJim Hahn1-0/+8
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>
2019-09-03Update git submodulesPavel Paroulek1-0/+0
* 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
2019-09-03Merge "update the release version of SO 1.5.1"Sylvain Desbureaux10-10/+10
2019-09-03Merge "Delete oom for ocata"Sylvain Desbureaux10-430/+1
2019-09-03Merge "Modifying dmaap job labels because of inconsistency with other jobs. ↵Sylvain Desbureaux4-0/+8
Mainly adding release label there."
2019-09-02Merge "Move Storage access to RWO"Alexis de Talhouët2-2/+2
2019-09-02Merge "Fix syntax and indentation in ingress common template."Alexis de Talhouët1-6/+6
2019-09-02Merge "Move Policy Storage to RWO"Alexis de Talhouët2-2/+2
2019-09-02Merge "add bath file for additional AAA user"Alexis de Talhouët2-0/+11
2019-09-02update the release version of SO 1.5.1seshukm10-10/+10
Issue-ID: SO-2223 Signed-off-by: seshukm <seshu.kumar.m@huawei.com> Change-Id: I978a79f2232505e42ff470aab53614d13fa629f7
2019-09-02Merge "update multicloud/artifactbroker version in OOM"Alexis de Talhouët1-2/+2
2019-09-02Merge "Move CLAMP Storage access to RWO"Alexis de Talhouët1-1/+1
2019-09-02Merge "Move DMaaP Storage access to RWO"Alexis de Talhouët3-5/+4
2019-09-02Merge "Update deployment YAML file"Alexis de Talhouët1-0/+8
2019-09-02Merge "Move Storage access to RWO"Alexis de Talhouët1-1/+1
2019-09-02Set master as branch in .gitmodulesCédric Ollivier1-1/+1
It avoids the next fatal error when updating gitmodules from doc (double levels of submodules). Submodule (kubernetes/aai) branch configured to inherit branch from superproject, but the superproject is not on any branch. Issue-ID: DOC-505 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com> Change-Id: Id2d6434210003c20de74fc6da87125c54506cfd1
2019-09-02Delete oom for ocataHaibin Huang10-430/+1
Issue-ID: MULTICLOUD-775 Signed-off-by: Haibin Huang <haibin.huang@intel.com> Change-Id: Ieeab8ba5e6fd5f9d307f6ec996ca724058a08c1b
2019-09-02Merge "Add OOM update so-bpmn-infra's Override.yaml file"Alexis de Talhouët1-1/+1
2019-09-02Fix cds-blueprint-processor and dependentAlexis de Talhouët2-5/+2
Change-Id: I2c4c57ba9783a4daae3584fcb9772569482d5b48 Issue-ID: OOM-2041 Signed-off-by: Alexis de Talhouët <adetalhouet89@gmail.com>
2019-09-02Modifying dmaap job labels because of inconsistency with other jobs.Ondřej Šmalec4-0/+8
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>
2019-09-02Move SDC Storage to RWOSylvain Desbureaux3-3/+3
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>
2019-09-02Move Modeling Storage to RWOSylvain Desbureaux1-1/+1
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>
2019-09-02Move PORTAL Storage access to RWOSylvain Desbureaux2-2/+2
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>
2019-09-02Merge "Update SDNC helm charts to use Neon version"Sylvain Desbureaux13-43/+33
2019-09-02Merge "Use nodePortPrefix variable in CLAMP-mariadb service template"Borislav Glozman1-1/+1
2019-09-02Merge "Removing nginx-ingress from helm charts. It is running by default via ↵Borislav Glozman2-6/+0
RKE."
2019-08-31Update SDNC helm charts to use Neon versionTimoney, Dan (dt5972)13-43/+33
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>
2019-08-30Fix if statement in DMaaP-dr-prov serviceMarco Platania1-1/+1
Issue-ID: OOM-2083 Signed-off-by: Marco Platania <platania@research.att.com> Change-Id: I0318115d85d8507ecba1133d6c8c1a2bc6333b63
2019-08-30Merge "DMaaP DR refactoring"Sylvain Desbureaux17-298/+565
2019-08-30Merge "Update VID values.yaml to version 5.0.1"Sylvain Desbureaux1-1/+1
2019-08-29Move Policy Storage to RWOSylvain Desbureaux2-2/+2
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>
2019-08-29Move DMaaP Storage access to RWOSylvain Desbureaux3-5/+4
RWO is sufficient for DMaaP PVC. Change-Id: I35339948b3164e83b92d2e81a1c772574ebb9e9a Issue-ID: DMAAP-1285 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2019-08-29Move CLAMP Storage access to RWOSylvain Desbureaux1-1/+1
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>
2019-08-29Move Storage access to RWOSylvain Desbureaux1-1/+1
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>
2019-08-29Move Storage access to RWOSylvain Desbureaux2-2/+2
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>
2019-08-29Update VID values.yaml to version 5.0.1Ittay Stern1-1/+1
✔ El-Alto first wave Issue-ID: VID-521 Change-Id: Ic34065a28a47d07e408ad345b493404a055740c6 Signed-off-by: Ittay Stern <ittay.stern@att.com>
2019-08-29Update deployment YAML fileOleg Mitsura1-0/+8
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
2019-08-29Fix syntax and indentation in ingress common template.Ondřej Šmalec1-6/+6
Issue-ID: OOM-2050 Signed-off-by: Ondřej Šmalec <o.smalec@partner.samsung.com> Change-Id: I7d54c4c8adc192d0c27249dde2fad4af2ed0a52a
2019-08-28DMaaP DR refactoringefiacor17-298/+565
# 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>
2019-08-26update multicloud/artifactbroker version in OOMLiang Ding1-2/+2
Issue-ID: MULTICLOUD-718 Change-Id: Iaba6a4b72c20f19eaf04c40e7beac47723bb8f78 Signed-off-by: Liang Ding <liang.ding@intel.com>
2019-08-26Updated resourceSourceMappings source-db/etcOleg Mitsura2-22/+22
Issue-ID: CCSDK-1623 Signed-off-by: Oleg Mitsura <oleg.mitsura@amdocs.com> Change-Id: Ie441afb7db312492c4abfe9590c271bf2a08d81b
2019-08-23Merge "Tune OpenDaylight parameters"Brian Freeman5-0/+283
2019-08-23add bath file for additional AAA userTaka Cho2-0/+11
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>
2019-08-23Merge "update AAF url"Brian Freeman1-4/+4
2019-08-23Merge "SO datasource config update"Brian Freeman9-15/+71
2019-08-23SO datasource config updatesarada prasad sahoo9-15/+71
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>