aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/dcaegen2/components/dcae-redis
AgeCommit message (Collapse)AuthorFilesLines
2020-07-24Make DCAEGEN compatible with Kubernetes v1.17Krzysztof Kuzmicki1-1/+4
Issue-ID: OOM-2454 Signed-off-by: Krzysztof Kuzmicki <krzysztof.kuzmicki@nokia.com> Change-Id: I7dc8044384f32930d2c3af7b59d39a94c3c4c103
2020-04-02Bump chart versionSylvain Desbureaux1-1/+1
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-02-02Merge "redis config optimization"Borislav Glozman1-4/+2
2020-02-01[ONAP-wide] Replace .Release.Name with common.releaseKrzysztof Opasiak3-6/+6
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-21redis config optimizationVijay Venkatesh Kumar1-4/+2
- replication count set to 3 - removing nodeport Change-Id: Ie3431c59ffdd44f207eddfbc013ab4fc3f6ed5f9 Signed-off-by: Vijay Venkatesh Kumar <vv770d@att.com> Issue-ID: DCAEGEN2-1720 Issue-ID: OJSI-187
2019-12-11Merge "[DCAE] Use global storage templates for PVC"Borislav Glozman2-210/+32
2019-12-06Add ingress controler support to DCAELucjan Bryndza2-1/+10
Issue-ID: OOM-2178 Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com> Change-Id: Id4c679431d5d5e0362acbd08757250f1bb5a0616 Signed-off-by: Lucjan Bryndza <l.bryndza@samsung.com>
2019-12-04[DCAE] Use global storage templates for PVCSylvain Desbureaux2-210/+32
OOM has now templates in order to create the needed PVC, using: * a PV with a specific class when using a common nfs mount path between nodes (sames as today use) --> is the default behavior today * or a storage class if we want to use dynamic PV. On this case, we use (in order of priority): - persistence.storageClassOverride if set on the chart - global.persistence.storageClass if set globally - persistence.storageClass if set on the chart I've also used a "range" for PV creation of redis in order to have only the needed number. Change-Id: I6bb326f8aaece11bcf503e9300e5c39a87214f81 Issue-ID: OOM-1227 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2019-11-07Attempt 2 at chart restructureUbuntu10-0/+685
Helm value override file now supports component-specific settings: dcae-bootstrap: enabled: true dcae-cloudify-manager: enabled: true dcae-config-binding-service: enabled: true dcae-healthcheck: enabled: true dcae-redis: enabled: true dcae-servicechange-handler: enabled: true dcae-inventory-api: enabled: true dcae-deployment-handler: enabled: true dcae-policy-handler: enabled: true dcae-dashboard: enabled: true Issue-ID: OOM-1574 Signed-off-by: Ubuntu <dgl@research.att.com> Change-Id: I85e0fe6ae19e176d954611549ec954a5fe662307 Signed-off-by: Ubuntu <dgl@research.att.com>