aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/portal/charts/portal-mariadb/templates/pv.yaml
AgeCommit message (Collapse)AuthorFilesLines
2020-02-01[ONAP-wide] Replace .Release.Name with common.releaseKrzysztof Opasiak1-2/+2
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-09[PORTAL] Use global storage templates for PVCSylvain Desbureaux1-0/+3
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 Change-Id: I28b4ac5f612de75918973148865cf82f7a7de5e8 Issue-ID: OOM-1227 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
2018-08-30Apache2 License additiontoshrajbhardwaj1-0/+1
Issue-ID: OOM-1306 Change-Id: I1a617718006ee845d675fead74ce075c3390ac2f Signed-off-by: toshrajbhardwaj <toshrajbhardwaj@gmail.com>
2018-03-29Standardizing ONAP PortalMandeep Khinda1-0/+37
-synched up with Beijing (master) -pods come up without cassandra music: sed: couldn't edit /docker-entrypoint-initdb.d/\ zzz_portal.cql: not a regular file ONAPPORTAL webapp in tomcat is failing to star resulting in HTTP 404 robot health Not sure how logging works in beijing so removed some of the ubuntu-init dir creation. need someone familiar with logging to investigate -addressed some CI comments. -removing configmap now that portaldb was fixed Issue-ID: OOM-746 Change-Id: I123d1ec6889db40b1721475a43665ef8efefc057 Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>