aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/onap
AgeCommit message (Collapse)AuthorFilesLines
2018-04-22Add DCAE Cloudify-Manager supportBorislavG1-1/+1
22/Apr: This review is ready to merge. ** Resolves issue by using the k8s-provided secret. No longer need to map .kube/config. Change-Id: I0f51f7d8bb9ed9a5653089e77be495dc7456ef22 Issue-ID: OOM-855 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com> Signed-off-by: Jack Lucas <jflucas@research.att.com>
2018-04-19fix nfs-provisioner for appc and sdncJerome Doucerain1-1/+1
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>
2018-04-16Fix SDN-C bundles that don't come up properlyjmac2-0/+18
Change-Id: Ieccbd863e45bb68d76f4f1f066433276c9adf3cd Signed-off-by: jmac <james.macnider@amdocs.com> Issue-ID: OOM-945
2018-04-12Merge "Add Standardized Configuration to VNFSDK"Mike Elliott1-1/+1
2018-04-12VFC Communication fails because MSB service namemahendrr1-1/+1
Change-Id: I26e27cfb3b973bbffd0a94e3ec8411f5218cdf4f Issue-ID: OOM-804 Signed-off-by: mahendrr <mahendra.raghuwanshi@amdocs.com>
2018-04-11Add Standardized Configuration to VNFSDKjasmineWen1-1/+1
Issue-ID: OOM-751 Change-Id: I3a9909d4bbb82b874baf9088109a1930a2bfb671 Signed-off-by: jasmineWen <jasmine.wen@amdocs.com>
2018-04-10Standardized Config for VFCMike Elliott2-2/+2
Change-Id: Ie7064b59032c6cd81ee37466c89a5dee74530939 Issue-ID: OOM-750 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
2018-04-06Add standardized helm chart for multicloudkj1-1/+1
-mk: updating umbrella requirements.yaml Issue-ID: OOM-744 Change-Id: Iae202a60ff5fd8d4fa98bd29184df1444b616186 Signed-off-by: kj <keren.joseph@amdocs.com> Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-04-04Message Router Helm Chart Standardizationpramod2-2/+2
Issue-ID: OOM-731 Change-Id: I2137b9dbe7c7a320094c13779e8e43dadef964c7 Signed-off-by: pramod <pramod.kumarsharma@amdocs.com> Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
2018-04-03Remove global repository from onap chartMike Elliott3-22/+103
See description in linked issue id. Change-Id: I3bcec1214875cb318dc45162013aec8957443dc8 Issue-ID: OOM-845 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
2018-04-02Merge "Consul Helm Chart Standardization"Mandeep Khinda1-1/+1
2018-04-02Merge "Add Standardized Configuration to SDN-C Chart"Mandeep Khinda3-1/+11
2018-04-02Consul Helm Chart StandardizationjasmineWen1-1/+1
Issue-ID: OOM-730 Change-Id: I742979aa27022e553b33062762a1ad5f80940726 Signed-off-by: jasmineWen <jasmine.wen@amdocs.com>
2018-04-02Add Standardized Configuration to SDN-C Chartjmac3-1/+11
Change-Id: I9f4d43c2a3f0766b9c8477a180f5a0bd45fde243 Signed-off-by: jmac <james.macnider@amdocs.com> Issue-ID: OOM-748
2018-03-29fixing umbrella reqs for cliMandeep Khinda1-1/+1
doesn't make Issue-ID: OOM-736 Change-Id: If3a2097988066560e9d31bc9b875c3b461080777 Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-03-29Standardizing ONAP PortalMandeep Khinda1-1/+1
-synched up with Beijing (master) -pods come up without cassandra music: sed: couldn't edit /docker-entrypoint-initdb.d/\ zzz_portal.cql: not a regular file ONAPPORTAL webapp in tomcat is failing to star resulting in HTTP 404 robot health Not sure how logging works in beijing so removed some of the ubuntu-init dir creation. need someone familiar with logging to investigate -addressed some CI comments. -removing configmap now that portaldb was fixed Issue-ID: OOM-746 Change-Id: I123d1ec6889db40b1721475a43665ef8efefc057 Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-03-28Add Standardized Configuration to POLICYmayankg27031-1/+1
Change-Id: Iabdb2bba14b5095c08ff2920aec97a213e0acb30 Issue-ID: OOM-745 Signed-off-by: mayankg2703 <mayank.gupta@amdocs.com> Signed-off-by: Mike Elliott <mike.elliott@amdocs.com> Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com>
2018-03-28Merge "Helm Chart Standardization of uui"Mandeep Khinda1-1/+1
2018-03-28Merge "standardizing SDC helm charts"Jerome Doucerain1-1/+1
2018-03-28standardizing SDC helm chartsMandeep Khinda1-1/+1
all pods come up robot health reports HTTP 500 -> mostly due to missing dmaap resolving filebeat merge conflict addressing CI comments do we need a pv/pvc for the logs? Issue-ID: OOM-747 Change-Id: Id6f1e57fdaf3cd6d9f75e8bc1e5bfde39b91235e Signed-off-by: Mandeep Khinda <mandeep.khinda@amdocs.com> Signed-off-by: Areli Fuss <af732p@intl.att.com> (cherry picked from commit fe3e499547c91eadd71bde630594720b918c2af9)
2018-03-28Merge "Add standardized helm chart for aaf"Borislav Glozman1-1/+1
2018-03-28Add standardized helm chart for aafkj1-1/+1
AAF crashes due to "could not find or load main class org.onap.aaf.authz.service.AuthAPI" see https://jira.onap.org/browse/OOM-324 Issue-ID: OOM-732 Change-Id: I1c5f93d6e9a4d91224bfc0df2894ca7ab7d1de38 Signed-off-by: kj <keren.joseph@amdocs.com>
2018-03-28Helm Chart Standardization of uuivaibhav_16dec1-1/+1
Issue-ID: OOM-749 Change-Id: Ie71686869da88a8bb7f6d09d38a5fa4a92b02aeb Signed-off-by: vaibhav_16dec <vaibhav.chopra@amdocs.com>
2018-03-27Vid Standardization ConfigPriyanka1-1/+1
Issue-ID: OOM-729 Change-Id: Ic5b082e2d87ca7ef7944cd1ccce635ea2309e1f5 Signed-off-by: Priyanka <Priyanka.Jain3@amdocs.com>
2018-03-27ESR Configuration StandardizationPriyanka1-2/+2
Issue-ID: OOM-738 Change-Id: I2cf23fceb74507b592469de3f709af6cdcbe3982 Signed-off-by: Priyanka <Priyanka.Jain3@amdocs.com>
2018-03-27Add standardized helm chart for aaikj1-1/+1
Issue-ID: OOM-734 Change-Id: I6b1a85017d79b92afcae44cf823ab000a10ce4be Signed-off-by: kj <keren.joseph@amdocs.com>
2018-03-27Add standardized helm chart for logBorislavG2-2/+2
Change-Id: Ic9f0eb567716224893955d9379e9ed9308b9ea79 Issue-ID: OOM-740 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-03-26Add standardized helm chart for msbBorislavG1-1/+1
Change-Id: I63fbb58167a3e352f05e7e9af4d28f3531546dff Issue-ID: OOM-742 Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
2018-03-24Add standardized helm chart for appcMike Elliott1-1/+1
This is a standardization (based on helm community best practices) of a Helm chart for the Application Controller (appc) in ONAP. How to deploy the helm chart (outside of the parent onap chart) from the local oom/kubernetes codebase. Run local helm repository in the background: $ nohup helm serve & In kubernetes directory run: $ make all 2 ways to install (--set are for testing purposes) Full onap: $ helm install onap --name onap --namespace onap --set global.pullPolicy=Never,mysql.replicaCount=2,appc.replicaCount=2 Appc only: $ helm install setup --name onap-setup --namespace onap-apps $ helm install appc --name appc --namespace onap-apps Change-Id: Ib780f979ad25ecafb08110504b5941e980ca8a95 Issue-ID: OOM-733 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com> Signed-off-by: ah415j <ah415j@att.com>
2018-03-23Enable all helm charts by default in parent chartMike Elliott3-29/+72
This is as a means towards obsoleting the oneclick scripts from the Beijing release, in favour of directly using Helm. From this point on, users of onap should use the follow command: helm install local/onap -n onap --namespace onap Please refer to the official documentation for all the steps required to deploy onap. Currently as a patched to be merged: https://gerrit.onap.org/r/#/c/37871/ Change-Id: I75e5dbc9a79fec86a9b7c0cff487b10ec9df9a20 Issue-ID: OOM-816 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
2018-03-22Move deployment-specific templates to parent chartMike Elliott3-3/+59
This change provides a single centralized location (onap parent chart) to change/install secrets, persistent volumes, service account(s), RBAC and configuration overrides. It also eliminates the need for a 2-step install of setup and application charts. Users would customize the onap parent chart to install both the deployment-specific resources and one or more "enabled" sub charts, using a command like the following: helm install local/onap -f dev.yaml where dev.yaml (or prod.yaml, etc.) provides the customization of application subcharts to deploy. Change-Id: Idbef28ffa404ea35922a4c3994605bdc27f3471e Issue-ID: OOM-817 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
2018-03-22License addition in all yamlsvaibhav_16dec4-0/+56
Issue-ID: OOM-821 Change-Id: I627ac962afe8cd6bf2859a30a0e88f6c9ac89d34 Signed-off-by: vaibhav_16dec <vaibhav.chopra@amdocs.com>
2018-03-19Robot Helm Chart Standardizationvaibhav_16dec2-2/+2
Issue-ID: OOM-728 Change-Id: I2e6b298a78e7d10c47ce1d531bf089c928a40284 Signed-off-by: vaibhav_16dec <vaibhav.chopra@amdocs.com>
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>