I figured out the tpl error issue; looks like it was due to helm version mismatch.
Thanks, Gary From: Gary Wu Sent: Monday, March 12, 2018 3:27 PM To: 'Michael O'Brien' <frank.obr...@amdocs.com>; firstname.lastname@example.org Subject: RE: [onap-discuss] [OOM][INT] Heads up: ONAP Kubernetes healtcheck/demo parameters modified 20180302 - 1 of 2 CD systems needs adjustment Hi Michael, The original expectation was that the DCAE changes made in OOM amsterdam will be cherry-picked as-is into master, and used as the DCAE/OOM integration method for Beijing. As such, the beijing job was temporarily deploying OOM amsterdam to help test and stabilize the DCAE/OOM integration method expected for Beijing. Now that there will be a new DCAE/OOM integration method for beijing, that original expectation is no longer valid. So, I'll go ahead and switch the beijing job to start deploying OOM master directly. Speaking of which, I'm currently getting the following error while running "createAll.bash -n onap": Creating deployments and services ********** Error: parse error in "mso/templates/mso-log-configmap.yaml": template: mso/templates/mso-log-configmap.yaml:8: function "tpl" not defined The command helm returned with error code 1 Any ideas? Thanks, Gary From: Michael O'Brien [mailto:frank.obr...@amdocs.com] Sent: Friday, March 09, 2018 4:58 PM To: Gary Wu <gary.i...@huawei.com<mailto:gary.i...@huawei.com>>; email@example.com<mailto:firstname.lastname@example.org> Subject: RE: [onap-discuss] [OOM][INT] Heads up: ONAP Kubernetes healtcheck/demo parameters modified 20180302 - 1 of 2 CD systems needs adjustment Not that I know of - I don't know the plans of the DCAEGEN2 team right now - but I understand that the Beijing implementation of DCAEGEN2 is very different from amsterdam For myself I can only run DCAE on openlab via amsterdam. We will know when it is ported - by watching for changes in onap-parameters.yaml The one in master is still bare-bones. https://git.onap.org/oom/tree/kubernetes/config/onap-parameters.yaml https://git.onap.org/oom/tree/kubernetes/config/onap-parameters.yaml?h=amsterdam I know of 3 or 4 options - don't know which one will be the final Port amsterdam heatbridge (Alexis D.T.'s) over to master - either as is or reduced VM's - I hear the 7 cdap nodes are getting reduced in number Finish the containerization of cloudify manager - I hear it is almost complete Run openstack on kubernetes Fully containerize cloudify and dcae Q) is the Beijing job running Beijing or amsterdam - it looks like amsterdam but without DCAE running - I periodically get questions about it. https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/ I am trying to figure out why the 2 systems run differently since 2 March. From: Gary Wu [mailto:gary.i...@huawei.com] Sent: Friday, March 9, 2018 16:27 To: Michael O'Brien <frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>>; email@example.com<mailto:firstname.lastname@example.org> Subject: RE: [onap-discuss] [OOM][INT] Heads up: ONAP Kubernetes healtcheck/demo parameters modified 20180302 - 1 of 2 CD systems needs adjustment Hi Michael, Thanks for the heads up. Does this also mean that DCAE is now enabled in OOM master branch? Thanks, Gary From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Michael O'Brien Sent: Friday, March 09, 2018 12:46 PM To: email@example.com<mailto:firstname.lastname@example.org> Subject: [onap-discuss] [OOM][INT] Heads up: ONAP Kubernetes healtcheck/demo parameters modified 20180302 - 1 of 2 CD systems needs adjustment Team, A heads up that a change went in last Friday under OOM-722 that merged all the namespaces into one. One of the effects of this change was to add a parameter to the healthcheck and vFW demo scripts - that require the namespace name (usually "onap") ./ete-k8s.sh health ./ete-k8s.sh $ENVIRONMENT health See https://git.onap.org/oom/tree/kubernetes/robot/demo-k8s.sh https://gerrit.onap.org/r/#/c/32093/21/kubernetes/robot/ete-k8s.sh https://jira.onap.org/browse/OOM-722 For developers you will notice this right away when healthcheck commands fail. For automated systems the logs or the build should pick it up. Therefore all automated CD systems broke last Friday. The following CD system is fixed - I also had another issue with a stuck nodejs install - increased build freq to 2h http://jenkins.onap.info/job/oom-cd/ Corresponding 1-click entrypoint.sh script(and oom_rancher_install.sh, cd.sh) is updated as of yesterday. https://jira.onap.org/browse/OOM-710 Friendly information sharing between E2E teams The official CD system is still running without a fix - I would expect it to fail on the missing namespace - this means it is actually testing daily amsterdam builds (not Beijing) - unless I am missing a preset of the onap namespace Integration team - you will want to either rename the Jenkins jobs to "amsterdam" or change the OOM deployment script to clone -b master instead. https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/ https://jenkins.onap.org/view/External%20Labs/job/lab-tlab-beijing-oom-deploy/ for example this needs a "onap" parameter 17:41:47 + timeout 2m ssh -o StrictHostKeychecking=no -i /var/lib/jenkins/.ssh/onap_key email@example.com<mailto:firstname.lastname@example.org> 'sudo su -l root -c "/root/oom/kubernetes/robot/ete-k8s.sh health"' This is also an issue when running demo commands for the vFW (the part that is automated) ./demo-k8s.sh onap init Or we would see 04:14:50 Usage: demo.sh namespace <command> [<parameters>] 04:14:50 demo.sh <namespace> init 04:14:50 - Execute both init_customer + distribute Raised https://jira.onap.org/browse/INT-439 as a tracking taks Known issues: SDNC rarely comes up since mid Jan 2018 because of increased docker images size - usually a restart fixes it (done after all other dependent pods are up) ONAP components take 15-40 min to come up now instead of 15-20 - adjust your wait states. Thank you Michael O'Brien Amdocs Technology 16135955268 55268 [amdocs-a] This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer
_______________________________________________ onap-discuss mailing list email@example.com https://lists.onap.org/mailman/listinfo/onap-discuss