summaryrefslogtreecommitdiffstats
path: root/kubernetes/sdnc/sdnc-prom/templates
AgeCommit message (Collapse)AuthorFilesLines
2020-05-08[Tree-wide] Make chart build process predictibleKrzysztof Opasiak4-220/+0
ONAP is built using plain makefile rules. List of targets is generated using wildcard function. Based on make changelog: http://git.savannah.gnu.org/cgit/make.git/tree/NEWS since version 3.82 wildcard is not going to sort its results which means that charts are being processed in an arbitrary order which may lead to build failure due to missing dependencies. Since version 4.3 make started sorting the wildcard results once again which may lead to build issues. To avoid that and make our builds predictible independently from Makefile version let's make sure that we always sort wildcard results. Addinally let's use 'file://' instead of '@local' for charts in common to resolve dependencies between them. Issue-ID: OOM-2399 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: Iacb02dcdbd577ce0e9ca1078dd0586d296ec9375
2020-03-30[SDNC] Use faster version of common secret templatesKrzysztof Opasiak2-0/+4
Issue-ID: OOM-2051 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: I6cf72e3d6dcd8eab5f913b86febc7a21d02c1ecb
2020-02-01[ONAP-wide] Replace .Release.Name with common.releaseKrzysztof Opasiak4-8/+8
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-16[SDNC] Use global storage templates for PVCSylvain Desbureaux3-2/+84
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 "range" for PV creation of the statefulset I've created one file per PV (one for mdsal, one for certs). sdnc-prom was using hostpath directly on deployment, move to a PV/PVC. Change-Id: Id9eed3b13ac85595c386e380f41cfbc38b52c69f 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-09-18Backup Task-SDNC ConfigMaptoshrajbhardwaj1-0/+10
Issue-ID: OOM-1404 Change-Id: If2ea6cc54a5dbfbb475e9abc8b2444a2053c6603 Signed-off-by: toshrajbhardwaj <toshrajbhardwaj@gmail.com>
2018-07-15SDN-C Multi-site High-availability - Auto-failoverMohammadreza Pasandideh2-0/+124
Change-Id: I4e028b31ce7a60154d2c04c63431c5ea996de8f8 Signed-off-by: Mohammadreza Pasandideh <mohammadreza.pasandideh@amdocs.com> Issue-ID: SDNC-213