Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
This change restores the pv.yaml and pvc.yaml that were previously
removed. These are required for the case when the NFS provisioner is
disabled. I've added a condition to these files such that they should
be disabled if the NFS provisioner is enabled. The two ways of
managing entities need to be mutually exclusive.
Borislav: Solution for directory creation problem
upon first deployment with persistence enabled
Borislav: Fixed licenses for mysql
Change-Id: I9879b3b6574f8026a28793b9d86d6ef3ec9ce2e9
Signed-off-by: jmac <james.macnider@amdocs.com>
Issue-ID: OOM-889
|
|
Moved mysql and dgbuilder under common (built first)
to ensure they are built before appc and sdnc charts
that depend on them.
Change-Id: I2fc28f0537b2639bd2b761c6f115544965a228b1
Issue-ID: OOM-830
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|