Ruijing, Hi, thanks for raising these questions. Right now in OOM, there are 3 failing containers likely due to config mismatch in master that are not required for the vFirewall use case, but may be required for the more advanced vVolte and vCPE cases. These are vfc, clamp and aaf. You can safely ignore these 3 of 70 containers for vFirewall level testing. Hopefully the jira’s on these will be fixed soon – several of us are assigned these along with other JIRA’s – you are very welcome to attend the weekly OOM meeting at 1000EDT on Wed and take on some of this work to help us in prep of the 4th Dec KubeCon and 11th Dec ONAP conference – the more the better.
vfc https://jira.onap.org/browse/OOM-326 aaf https://jira.onap.org/browse/OOM-324 the msb healthcheck is a good one https://jira.onap.org/browse/OOM-414 For the second question on closed-loop – you will require appc and dcae (DCAE is currently hybrid K8S/HEAT – so you need a public or private openstack depending on where you are running your OOM host/client – even before closed-loop to bring up the 3 VMs via MSO/SO) See the diagram on vFW flow at https://wiki.onap.org/display/DW/Tutorial%3A+Verifying+and+Observing+a+deployed+Service+Instance#Tutorial:VerifyingandObservingadeployedServiceInstance-vFirewallDemoRuntimeBehaviour Join all of us in triaging/getting-the-vfw-running in the daily sessions off of https://wiki.onap.org/display/DW/Vetted+vFirewall+Demo+-+Full+draft+how-to+for+F2F+and+ReadTheDocs#VettedvFirewallDemo-Fulldrafthow-toforF2FandReadTheDocs-OpenlabVNCandCLI thanks for bringing these issues up – for all of us /michael From: Guo, Ruijing [mailto:[email protected]] Sent: Monday, November 27, 2017 06:54 To: [email protected] Cc: Michael O'Brien <[email protected]> Subject: [onap-discuss] ONAP on K8s Hi, Michael, I can automatically set up ONAP on K8s (vagrant/libvirt/kubeadm + oom) except the following components are in crashloop: vagrant@onap:~$ kubectl get pods --all-namespaces | grep onap | grep Run | wc 73 438 7750 vagrant@onap:~$ kubectl get pods --all-namespaces | grep onap | grep -v Run onap-clamp clamp-2925721051-bx059 0/1 Error 32 3h onap-kube2msb kube2msb-registrator-4293827076-q3lf8 0/1 CrashLoopBackOff 45 3h onap-vfc vfc-workflow-2530549902-b9q8r 0/1 CrashLoopBackOff 4 15m I saw you update “ONAP Minimum R1 Installation Helm Apps” in wiki HELM_APPS=('mso' 'message-router' 'sdnc' 'vid' 'robot' 'portal' 'policy' 'appc' 'aai' 'sdc' 'log') Q1: Do you create openstack and run closed-loop with onap on k8s? which components should be enabled to run closed-loop? Q2: I assume all components can be run in R1 release, right? Thanks, -Ruijing 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 <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
