aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/so/charts
AgeCommit message (Collapse)AuthorFilesLines
2020-05-22[so][msb] Update MSB url to match with its certificateKonrad Bańka4-5/+5
Change tested on so-openstack-adapter but it should impact each subcomponent the same way. Issue-ID: MSB-467 Signed-off-by: Konrad Bańka <k.banka@samsung.com> Change-Id: I3f2ffef25b614701b23aeb9b248db24eee671188
2020-05-15Merge "bump the SO release version 1.6.1"Sylvain Desbureaux11-11/+11
2020-05-13add nssmf adpter endpoint and so infra endpoint, update the oof endpointhetengjiao1-1/+5
Issue-ID: SO-2921 Signed-off-by: hetengjiao <hetengjiao@chinamobile.com> Change-Id: I28524030291cac3b5e4b04221ee23b8354872d73
2020-05-11bump the SO release version 1.6.1seshukm11-11/+11
Issue-ID: SO-2818 Signed-off-by: seshukm <seshu.kumar.m@huawei.com> Change-Id: I99506f2bfb4aa9944dda9a23f6fbe0d66a60cb37
2020-04-30Merge "Adding NSSMF adapter chart"Krzysztof Opasiak8-0/+407
2020-04-30Adding NSSMF adapter chartjananib8-0/+407
OOM SO-NSSMF adapter Issue-ID: OOM-2343 Change-Id: I93c7bfc58601202dd61455431d2720162ee9e69c Signed-off-by: jananib <janani.b@huawei.com> Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2020-04-10Addressed openstack override file missing requestDB endpointRamesh Parthasarathy1-0/+4
integration team reported that openstack is missing request db adapter endpoint from override file. This has been addressed here. Issue-ID: SO-2801 Signed-off-by: Ramesh Parthasarathy(rp6768)<ramesh.parthasarathy@att.com> Change-Id: I1f67575fbea813587ec83c7ff88bc294c09eef71
2020-04-07Adding trust-store and trust-store-password paramswaqas.ikram1-2/+6
for MSB Change-Id: I4a23fccbc50453969f1c1d0665933f88ea4971ff Issue-ID: SO-2574 Signed-off-by: waqas.ikram <waqas.ikram@est.tech>
2020-04-05Added trust store for SOL003 Adapter & ETSI Catalog ManagerRamesh Parthasarathy3-3/+22
Added the trust store provided by waqas to be included with vnfm adapter jvm arguments. Issue-ID: SO-2765 Signed-off-by: Ramesh Parthasarathy(rp6768)<ramesh.parthasarathy@att.com> Change-Id: Ifbe7bd54dcf1f79b49bed1f887e472ad9b7ac634
2020-04-03Merge "[SO] Correct connection configuration to sdnc"Krzysztof Opasiak4-11/+17
2020-04-02Bump chart versionSylvain Desbureaux13-13/+13
Use 6.0.0 in preparation for Frankfurt release Issue-ID: OOM-2320 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I8ad82dfdf48b56c38c0e85d640b18cc13c8d9e67
2020-04-01[SO] Correct connection configuration to sdncKonrad Bańka4-11/+17
Issue-ID: INT-1511 Signed-off-by: Konrad Bańka <k.banka@samsung.com> Change-Id: I1e44830206c9e1124952078584a769869caa6ffb
2020-04-01Bump SO version to 1.6.0seshukm9-9/+9
Issue-ID: SO-2519 Signed-off-by: seshukm <seshu.kumar.m@huawei.com> Change-Id: Ib340900d834f1b74b1ca936dc5c2de96d3c6ad96 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2020-03-31[SO] Onboard ONAP CA during init phaseSylvain Desbureaux22-31/+159
Workaround for retrieving ONAP root CA and keeping SO container being run by no root user. Issue-ID: SO-2730 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: Ib1b48c0a6fcca359a780640b8c705e75fd78dc1a
2020-03-28[SO] Use common secret template in soKrzysztof Opasiak9-23/+23
Generate passwords for: - so_user - so_admin and distribute them to all SO subcharts. mariadb-galera root password is taken as a reference to existing secret (shared mariadb instance) or also generated if local cluster is used. Three other DB users also have generated passwords but they are not distributed outside of so-mariadb as they were never used. Issue-ID: OOM-2328 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: Ic4af5c9b12b00d2a52d2597e3fe1161d0d1a9f20
2020-03-27[SO] Use common secret template in so-mariadbKrzysztof Opasiak7-32/+98
When porting so-mariadb component I've not noticed a few DB credentials hardcoded in shell scripts... Let's fix this and move all of them to common secret template Issue-ID: OOM-2328 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I8b42b22b1eb67ee8f15aebf0f4fccaa62cf6fde5
2020-03-26Merge "[SO] Use common secret template in so-sdnc-adapter"Sylvain Desbureaux3-16/+44
2020-03-26Merge "[SO] Use common secret template in so-sdc-controller"Sylvain Desbureaux3-16/+44
2020-03-25Merge "[SO] Use common secret template in so-vfc-adapter"Krzysztof Opasiak3-16/+44
2020-03-25Merge "[SO] Use common secret template in so-request-db-adapter"Krzysztof Opasiak3-16/+44
2020-03-25Merge "[SO] Use common secret template in so-openstack-adapter"Krzysztof Opasiak3-16/+44
2020-03-25[SO] Use common secret template in so-vfc-adapterKrzysztof Opasiak3-16/+44
Use common secret template in so-vfc-adapter component. For now passwords are stil hardcoded but this will be removed in further commits. Issue-ID: OOM-2328 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I276e0814775ac68efe9df2f4d1ef5f919d3bef0f
2020-03-25[SO] Use common secret template in so-sdnc-adapterKrzysztof Opasiak3-16/+44
Use common secret template in so-sdnc-adapter component. For now passwords are stil hardcoded but this will be removed in further commits. Issue-ID: OOM-2328 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I57c88fcdbaded8fc73fd066f39519be0eae3d670
2020-03-25[SO] Use common secret template in so-sdc-controllerKrzysztof Opasiak3-16/+44
Use common secret template in so-sdc-controller component. For now passwords are stil hardcoded but this will be removed in further commits. Issue-ID: OOM-2328 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I87439d4a4fe545610a2d423180530d57c09ff376
2020-03-25[SO] Use common secret template in so-request-db-adapterKrzysztof Opasiak3-16/+44
Use common secret template in so-request-db-adapter component. For now passwords are stil hardcoded but this will be removed in further commits. Issue-ID: OOM-2328 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I7231ac14d1f19d27c11c980e446a4809fae5dadd
2020-03-25[SO] Use common secret template in so-openstack-adapterKrzysztof Opasiak3-16/+44
Use common secret template in so-openstack-adapter component. For now passwords are stil hardcoded but this will be removed in further commits. Issue-ID: OOM-2328 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: Id01fcc655768bfe965b4d731f99ba3921d90ddd5
2020-03-25[SO] Use common secret template in so-monitoringKrzysztof Opasiak3-19/+45
Use common secret template in so-monitoring component. For now passwords are stil hardcoded but this will be removed in further commits. Issue-ID: OOM-2328 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: Iff0ae7e14924d5e4e3484e509a7a4962f623e487
2020-03-25[SO] Use faster version of common secret templateKrzysztof Opasiak6-14/+14
Issue-ID: OOM-2051 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I4975939da127f596d4a78cf8e144b8f71e72194e
2020-03-18Merge "Fixed openstack credentials for calling bpmn external tasks"Krzysztof Opasiak1-0/+5
2020-03-18Fixed openstack credentials for calling bpmn external tasksRamesh Parthasarathy1-0/+5
when so.global.security.aaf.enabled is false, openstack should use basic credentials to call bpmn. This is being addressed in this fix Issue-ID: SO-2747 Signed-off-by: Ramesh Parthasarathy(rp6768)<ramesh.parthasarathy@att.com> Change-Id: Ie16f6a8d94a3f099b461eefbfc478723c2a9a9c0
2020-03-17Merge "fix for the 30224 with the debugEnabled"Sylvain Desbureaux1-1/+2
2020-03-17fix for the 30224 with the debugEnabledseshukm1-1/+2
Issue-ID: SO-2519 Signed-off-by: seshukm <seshu.kumar.m@huawei.com> Change-Id: Iee36c5f5182686a8d18ba8d178a5d002623cd0a1
2020-03-11Changes for MDONS usecaseSrinivasan Ramanathan1-0/+6
Change-Id: I182419f83c8296b25be2aa4ce729d6ea27b33836 Issue-ID: SO-2460 Signed-off-by: Srinivasan Ramanathan <srinivasan.ramanathan2@us.fujitsu.com>
2020-03-09[SO] Use common secret template in so-mariadbKrzysztof Opasiak3-42/+35
Use common secrete template in so-mariadb component. For now passwords are stil hardcoded but this will be removed in further commits. Issue-ID: OOM-2328 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I70b13b14d0ddad8913f45c7cabed0c0d221d0005
2020-03-09Merge "[SO] Support LCM API of SDNC"Sylvain Desbureaux2-0/+16
2020-03-06Merge "[SO] Use common secret template in so-catalog-db-adapter"Krzysztof Opasiak3-16/+46
2020-03-05Merge "readd so filebeat sidecar ELK endpoint"Sylvain Desbureaux8-0/+137
2020-03-05Merge "[SO] Use common secret template in so-bpmn-infra"Sylvain Desbureaux3-17/+47
2020-03-05[SO] Support LCM API of SDNCEnbo Wang2-0/+16
Issue-ID: SO-2588 Signed-off-by: Enbo Wang <wangenbo@huawei.com> Change-Id: I809336bcc7528e4196ddb59a9c25939fd891b502
2020-03-04[SO] Use common secret template in so-catalog-db-adapterKrzysztof Opasiak3-16/+46
Use common secret template in so-catalog-db-adapter component. For now passwords are stil hardcoded but this will be removed in further commits. Issue-ID: OOM-2328 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I2ac98729b47d15ab4c360c3bb8c759370d6ec7d2
2020-03-04Add parameter http scheme for multicloud adapterEric Multanen1-1/+2
Add support to build endpoint from SO to multicloud via msb using http or https scheme. Change-Id: I474fdd7c885e437c1c8136bffe3e40e41c86dab5 Issue-ID: SO-1450 Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
2020-03-02[SO] Use common secret template in so-bpmn-infraKrzysztof Opasiak3-17/+47
Use common secrete template in so-bpmn-infra component. For now passwords are stil hardcoded but this will be removed in further commits. Issue-ID: OOM-2328 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I828d6a5713cf023d72ab22ea758e78e91d1944b9
2020-02-27Added an SO K8S POD for SOL002 (Ve-Vnfm-Adapter)Piotr Borelowski6-0/+226
Ve-Vnfm-Adapter POD Issue-ID: OOM-2307 Signed-off-by: Piotr Borelowski <p.borelowski@partner.samsung.com> Change-Id: I2bb95b1867338964e3f3dce74e50ac3e11231bcd
2020-02-25readd so filebeat sidecar ELK endpointsunilb8-0/+137
Issue-ID: SO-1110 Signed-off-by: sunilb <sb00577584@techmahindra.com> Change-Id: Ic468a1b28d681d14e862f4405890d996b42660f6
2020-02-13[SO] Enable use of Keystone v3Sylvain Desbureaux2-1/+3
SO can handle keystone v3 but override file must be capable to handle this. If openStackKeystoneVersion is set to "KEYSTONE_V3" in so-catalog-db-adapter config part, SO will be able to use keystone v3 for OpenStack Issue-ID: OOM-2221 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I14db318d25842a08ef380f6edb708e26dae050ad
2020-02-07These OOM changes are related AAF IntegrationRamesh Parthasarathy26-100/+240
Here we have the ability to optionally disable AAF integration. A global variable global.security.aaf.enabled=true will turn on AAF security. with global.security.aaf.enabled=false it will use spring.security to ensure backward compatibilty. updated based on review comments Issue-ID: SO-2452 Signed-off-by: Ramesh Parthasarathy(rp6768)<ramesh.parthasarathy@att.com> Change-Id: Ia83622ad681cfd122ee906ccd1654b10b5e31fe4
2020-02-01[ONAP-wide] Replace .Release.Name with common.releaseKrzysztof Opasiak33-123/+123
ONAP is too big to be deployed using helm install so we need to use a custom helm plugin helm deploy. This script deloys onap component by component instead of deploying evrything at once. Unfortunately this script also modifies the helm release by appending component name to it. As a result of this behavior our objects are called for example: onap-mariadb-galera-mariadb-galera-0 instead of just being called onap-mariadb-galera-0. This patch simplifies this naming convention by replacing all direct usages of .Release.Name with common.release macro which strips the component specific part from the release name. Issue-ID: OOM-2275 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: Ia8cead50d305adb00eef666d0a1ace74479b5183
2020-01-30Merge "Revert "basic auth for so-monitoring""Morgan Richomme1-8/+0
2020-01-15Update SO-VNFM-Adapter override.yaml for ETSIrope2521-0/+8
Change-Id: I6b99ccf9bd50d2ec50693df9d4122417b22bcf7a Issue-ID: SO-2575 Signed-off-by: rope252 <gareth.roper@est.tech>
2019-12-11Merge "Add ingress configuration for so-monitoring"Borislav Glozman4-3/+17