tree fd1597da5c896e33848d1a3dcb945a072ae8dc79
parent 8b68bebeeea6811a5d67813a49a404f3c6e46925
author Jerome Doucerain <jerome.doucerain@bell.ca> 1523636693 -0400
committer Gerrit Code Review <gerrit@onap.org> 1524147050 +0000

Updated git submodules

Project: oom master dee57fd5c546ee0b68d3e6c003cdc06ada987abe

fix nfs-provisioner for appc and sdnc

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>