From: Mandeep Khinda Date: Fri, 9 Mar 2018 14:29:37 +0000 (+0000) Subject: Updated git submodules X-Git-Tag: 2.0.0-ONAP~3320 X-Git-Url: https://gerrit.onap.org/r/gitweb?a=commitdiff_plain;h=2768983d370d8ae007b46de1fcbcf6c9885fbbec;p=doc.git Updated git submodules Project: oom master a57d8dd090a3d3d747ba40ef58e14215e88adfa2 iterating on new helm structure for SO with this change we can now do the following: can deploy umbrella chart with currently working components: helm install local/onap --name onap --namespace onap-all helm install local/onap --name onap-2 --namespace onap-all-2 \ --set global.nodePortPrefix=303 - umbrella includes setup chart can deploy a-la-carte component by component into a single namespace - Need to deploy a setup chart first. cannot be made a helm dependency as there will be conflicts if each app chart has the same setup dependency. helm install local/setup --name onap-setup --namespace onap-apps helm install local/so --name so1 --namespace onap-apps \ --set global.nodePortPrefix=304 helm list NAME REVISION STATUS CHART NAMESPACE onap 1 DEPLOYED onap-2.0.0 onap-all onap-2 1 DEPLOYED onap-2.0.0 onap-all-2 onap-setup 1 DEPLOYED setup-2.0.0 onap-apps so1 1 DEPLOYED so-2.0.0 onap-apps Unfortunately, the config maps all have fixed names, so installing the same app in the a-la-carte fashion will fail due to a collision. Not worrying about this as I'm not sure we want to support this. -made the common and setup charts standalone to remove relative file paths from requirements.yaml This will help when there are different levels of subcharts that need to include common Issue-ID: OOM-786 Issue-ID: OOM-789 Issue-ID: OOM-788 Change-Id: I20bacae6f0f20e8f3bb1527af1e7e53f187341d5 Signed-off-by: Mandeep Khinda --- diff --git a/docs/submodules/oom.git b/docs/submodules/oom.git index 41c491482..a57d8dd09 160000 --- a/docs/submodules/oom.git +++ b/docs/submodules/oom.git @@ -1 +1 @@ -Subproject commit 41c491482386f37ac876717e0f565ba0781e2d8a +Subproject commit a57d8dd090a3d3d747ba40ef58e14215e88adfa2