Code Review / oom.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: d96413f) | patch
Removing aai oxm files from configmaps 15/41815/1
authorMandeep Khinda <mandeep.khinda@amdocs.com>
Mon, 9 Apr 2018 21:09:51 +0000 (21:09 +0000)
committerMandeep Khinda <mandeep.khinda@amdocs.com>
Mon, 9 Apr 2018 21:09:51 +0000 (21:09 +0000)
commit9ed650535002af727f79bb33af89ed4f9947bb84
treefdac36fd32b563edfdffddba5ca67b07e506c163tree | snapshot
parentd96413f48c8a5709a54bdb22a565035313ecef02commit | diff
Removing aai oxm files from configmaps

-they have no parameterization, are huge files, and are breaching the configmap space
removing them and finding an alternate way of getting them into the containers
if they need to be externalized that can be done in a separate issue.
for now emptyDir{} is good enough.

Issue-ID: OOM-858

Change-Id: I05602302890dd3e0363dc355f1697b76fea509a1
Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
kubernetes/aai/charts/aai-data-router/resources/config/model/aai_oxm_v10.xml [deleted file] blob | history
kubernetes/aai/charts/aai-data-router/resources/config/model/aai_oxm_v11.xml [deleted file] blob | history
kubernetes/aai/charts/aai-data-router/resources/config/model/aai_oxm_v8.xml [deleted file] blob | history
kubernetes/aai/charts/aai-data-router/resources/config/model/aai_oxm_v9.xml [deleted file] blob | history
kubernetes/aai/charts/aai-data-router/templates/configmap.yaml diff | blob | history
kubernetes/aai/charts/aai-data-router/templates/deployment.yaml diff | blob | history
kubernetes/aai/charts/aai-data-router/values.yaml diff | blob | history
kubernetes/aai/charts/aai-sparky-be/resources/config/model/aai_oxm_v9.xml [deleted file] blob | history
kubernetes/aai/charts/aai-sparky-be/templates/configmap.yaml diff | blob | history
kubernetes/aai/charts/aai-sparky-be/templates/deployment.yaml diff | blob | history
kubernetes/aai/charts/aai-sparky-be/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).