| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
change in common/mysql/templates/pvc.yaml to allow pvc use
when persistence is required
change in common/mysql/templates/storageclass.yaml to be
led by the disableNfsprovisioner variable
change in appc/values to default the disableNfsprovisioner
to false as it is in sdnc
changing the default disableNfsprovisioner to true for both appc and sdnc
changing the stateful set avoid volumeclaimtemplates.
When used in helm, the volumeclaimtemplates is causing pvc to be left
after the helm delete --purge. I guess this is due to the fact the pvc
are not directly created by the helm install by indirectly by kubernetes
Now the tests are working in both cases (nfsprovisioner disabled or not)
The only piece remaining after a helm delete is pv in released state
in case we are using nfsprovisioner. That makes sense again because this
are objects created by the provisioner and not by helm.
removed some leftover
Issue-ID: OOM-787
Change-Id: Ieb1f1c482217aeb1b89be39a437bb891a299db71
Signed-off-by: Jerome Doucerain <jerome.doucerain@bell.ca>
|
|
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>
|
Jerome Doucerain
jmac
Mike Elliott