aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/onap
AgeCommit message (Collapse)AuthorFilesLines
2018-03-12Deploy kube2msb along with msb containersHuabingZhao2-8/+2
Issue-ID: OOM-280 Deploy kube2msb along with msb contianers, so the ONAP services can be sync to MSB after MSB is restarted Change-Id: I408e27c72c4b2169c0babe2562e74d4a645683de Signed-off-by: HuabingZhao <zhao.huabing@zte.com.cn>
2018-03-09iterating on new helm structure for SOMandeep Khinda2-0/+7
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 <mandeep.khinda@amdocs.com>
2018-02-23Add onap parent chartMike Elliott4-0/+275
This is a top-level parent helm chart which deploys customizations of the ONAP platform. The parent ONAP chart represents the start of OOM's move away from the oneclick bash scripts and towards the direct use of Helm to manage configuration and deployment of ONAP. How to deploy onap chart from local oom/kubernetes codebase. ** need to create/update dependencies defined in the chart's ** requirements.yaml helm dep update onap/ ** deploy the onap parent chart (and all referenced subcharts) ** with the "release" name of 'onap' helm install onap/ -n onap Change-Id: I71bee25770bdce82a47bfabb04946bb4fad069a2 Issue-ID: OOM-265 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>