Code Review / oom.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: cdda4e2) | patch
Restore pv and pvc in mysql chart 97/41597/5
authorjmac <james.macnider@amdocs.com>
Sun, 8 Apr 2018 19:28:01 +0000 (19:28 +0000)
committerBorislavG <Borislav.Glozman@amdocs.com>
Tue, 10 Apr 2018 07:54:36 +0000 (07:54 +0000)
commita4ddffab35edfb474dbd9a5376398cb2bf88ea18
treed078ad79fc9c99ea70c5ca15a5a7a5a9c4cf73fetree | snapshot
parentcdda4e20f3904dcb193625350c91d596a0bc4197commit | diff
Restore pv and pvc in mysql chart

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
12 files changed:
kubernetes/appc/values.yaml diff | blob | history
kubernetes/common/mysql/Chart.yaml diff | blob | history
kubernetes/common/mysql/requirements.yaml diff | blob | history
kubernetes/common/mysql/templates/configmap.yaml diff | blob | history
kubernetes/common/mysql/templates/nfs-provisoner.yaml diff | blob | history
kubernetes/common/mysql/templates/pv.yaml [new file with mode: 0644] blob
kubernetes/common/mysql/templates/pvc.yaml [new file with mode: 0644] blob
kubernetes/common/mysql/templates/secrets.yaml diff | blob | history
kubernetes/common/mysql/templates/service.yaml diff | blob | history
kubernetes/common/mysql/templates/statefulset.yaml diff | blob | history
kubernetes/common/mysql/templates/storageclass.yaml diff | blob | history
kubernetes/common/mysql/values.yaml diff | blob | history
Introduces the ONAP Platform OOM (ONAP Operations Manager) to efficiently Deploy, Manage, Operate the ONAP platform and its components (e.g. MSO, DCAE, SDC, etc.) and infrastructure (VMs, Containers).