Here is the summary of MANO meeting today Nov 9 and some common approach between Opera and Orchestra for on boarding, service invocation and API versions / testing - as summarized below.
I will be updating links etc provided by Giuseppe and Yingjun Li for same. Any suggestions for next week call besides the ones agreed today, please feel free reply back for me or Bryan to include in next mano-wg or Models calls. Subscribe for mano-wg if you want to keep upto date on mano-wg summary : https://lists.opnfv.org/mailman/listinfo/ Agenda of meeting November 9, 2016 14.00 UTC /7.00 PDT Meeting #11 and summary updates 1. What should we document for MANO best practice for OPEN-O and OpenBaton integration through Opera and Orchestra. * What use case to start with - - Should vIMS be the first use case? vIMS is agreed use case to document as first one for MANO integration Besides Clearwater vIMS Blueprint in OPNFV, Arthur from Canonical suggested using OpenIMS and JuJu can handle both. * VNF On-Boarding - TOSCA Node Template <similar to> NFV (VNFD, VLD, VNNFGD, PNFD) - Onboarding OpenBaton / Orchestra indicated that they like to see VNF Package to include VNFD along with image name and script to instantiate the VNF. So did Yingjun Li PTL Opera chimed and thus there is agreement on this from both projects. The issue of formats to use include CSAR & JSON and run times both Python and Java are being considered. Thus there will be attempt by both teams to define them along with VNFM's they plan to use like JujU and Tacker. The VNF package, and data model / representations for NSD and VNFD, and how/why those vary across MANO projects b1. OpenBaton: JSON for VNFD<http://openbaton.github.io/documentation/vnf-descriptor/>, NSD<http://openbaton.github.io/documentation/ns-descriptor/>; TOSCA for NSD<http://openbaton.github.io/documentation/tosca-nsd/> b2. Open-O: ...Needs input from Opera team (OPNE-O : https://wiki.open-o.org/view/OPEN-O_Sun_Release_Notes#Release_Overview ) * Service Invocation and Deletion - TOSCA Service template = NFV NSD, How do we handle SO & RO for this? This will follow NFVO flow to VNFM asking to allocate resource and if it does not that capability then NFVO will reroute the request to VIM. On success of Resource reservation (Quota) etc. the NFVO will ask VNFM to instantiate the service for the deployment completion as first target. Life cycle management will follow that based on agreed hooks to be defined as common between the Opera , Orchestra, Juju and Tacker teams. A proposal will be reviewed next week. * API versioning - which API? The API versioning is of abstractions or wrappers that is being proposed by OpenBaton and will be reviewed by other MANO participants to agree on a common wrapper approach for IFA 5, 6,7 and OPNFV VIM and VNFM drivers from NFVO. 1. At what point should upstream integration project consider OPNFV Models topology design and templates to choose and use. - This will be discussed at next Models call with Bryan Sullivan. 2. What should be test strategy (refer item 3 Nov 2 meeting) - Await FUNCTEST-237 response from Morgan and Action for MANO teams to create new FUNCTEST JIRA ticket based on vIMS use case. 3. Where is the test plan and how will the projects share the testing codes? - Proposal to be discussed next week with inputs for Giuseppe of Orchestra (OpenBaton team). 4. How would the results of collaboration through MANO WG reflect in D-release of OPNFV. - A template to be reviewed to see what should the best practices to include in the D-release based on MANO WG participation by Opera, Orchestra and associated VNFM. 5. What is reasonable deliverable expected from UNH Plug-fest for cross-project co-ordination? - The Open-O team from China Mobile plans to demo OPEN-O and OpenBaton team indicated that they may not be bale to make it to UNH Plug-fest but plan to Demo their efforts in ETSI Plugtest in February. Attendees: irc+GTM aimeeu,B_Smith,bryan_att,ChrisPriceAB,collabot`,dmcbride,ljlamers, rprakash, yingjun Li, Arthur Tyloc, Narinder Gupta Thanks Prakash [logo_huawei] R&D USA FutureWei Technologies, Inc Email: prakash.ramchand...@huawei.com<mailto:s.c...@huawei.com> Work: +1 (408) 330-5489 Mobile: +1 (408) 406-5810 2330 Central Expy, Santa Clara, CA 95050, USA
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
