[DCAE] Use global storage templates for PVC 71/98971/3
authorSylvain Desbureaux <sylvain.desbureaux@orange.com>
Fri, 29 Nov 2019 14:22:29 +0000 (15:22 +0100)
committerSylvain Desbureaux <sylvain.desbureaux@orange.com>
Wed, 4 Dec 2019 09:06:21 +0000 (10:06 +0100)
commit03c36f95a0c287bf866acea7ba8bdbf72e578155
treeed09bed19a40af50a249246c1980285c63f9abfe
parent9b0adea0769b026875ee312d223960c559c700bb
[DCAE] Use global storage templates for PVC

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>
kubernetes/dcaegen2/components/dcae-cloudify-manager/templates/deployment.yaml
kubernetes/dcaegen2/components/dcae-cloudify-manager/templates/pv.yaml
kubernetes/dcaegen2/components/dcae-cloudify-manager/templates/pvc.yaml
kubernetes/dcaegen2/components/dcae-cloudify-manager/values.yaml
kubernetes/dcaegen2/components/dcae-redis/templates/pv.yaml
kubernetes/dcaegen2/components/dcae-redis/templates/statefulset.yaml