aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/common/mongo/templates/statefulset.yaml
AgeCommit message (Collapse)AuthorFilesLines
2020-02-01[ONAP-wide] Replace .Release.Name with common.releaseKrzysztof Opasiak1-3/+3
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
2019-12-05[Common] Use global storage templates for PVCSylvain Desbureaux1-25/+21
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 aligned the PV creation of the different charts. I've also aligned the PVC creation of the different charts. I've removed unused mysql chart and (badly) used nfs-provisioner chart. I've also make cassandra backup work with dynamic PV (but RWX only for now). Change-Id: I0ea3f8c7514ca648d94b6c682684c06b822bbe0a Issue-ID: OOM-2229 Issue-ID: OOM-2228 Issue-ID: OOM-2227 Issue-ID: OOM-1227 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2018-09-25Updating charts to use common resource templateMandeep Khinda1-1/+1
Issue-ID: OOM-1145 Change-Id: I1510339a820802554b6e8b9a201619ef66be17a0 Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-05-17Add External Interface NBI project into OOMSylvain Desbureaux1-0/+104
NBI (North Bound Interface) is one of the new project added for Beijing release. Features added ============== MongoDB common chart -------------------- Ability to start a mongo container, with a chart consistent with other common charts (readiness, liveness, persistence, resources, nfs, service, ...). Specific configuration: * name of the db to create if needed NBI chart --------- Ability to start a mariadb container, with a chart consistent with other common charts (readiness, liveness, persistence, resources, nfs, service, ...). Specific configuration: * name of the db to create if needed * name of the user that has access to the db * password of the user that has access to the db * root password of the database Ability to start a NBI container, with a chart consistent with other common charts (readiness, liveness, persistence, resources, nfs, service, ...). Specific configuration: * log level * cloudOwner * ecompInstanceId * openStackRegion * openStackServiceTenantName * sdc_authorization * aai_authorization * so_authorization ONAP chart ---------- Added a requirement on NBI chart, possibility to enable/disable and configuration to push to the chart. Current Status ============== - [*] adding a common chart for mongodb - [*] make mongo chart compiling - [*] testing the mongodb common role - [*] creating a mariadb chart inside nbi helm - [*] testing the mariadb chart - [*] make mariadb chart compiling - [*] make nbi use these charts - [*] make nbi chart compiling - [*] test the whole solution - [*] create a service for nbi Change-Id: I8dd3e79768c83b1553a05c892cf418f840931255 Issue-ID: EXTAPI-54 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>