Hi, about the question mentioned in the minutes, whether the VNF package be an executable, I would like to point us to the ETSI document specifying the package. The document is currently under “remote consensus” and available in the open area. You can download at: http://docbox.etsi.org/ISG/NFV/Open/Drafts/IFA011_VNF_Packaging_Spec/NFV-IFA011v073.zip
In Clause 4, you find a nice definition: “A VNF Package contains all of the required files and meta-data descriptors required to validate and instantiate a VNF.” Maybe this helps. Cheers, Uli From: [email protected] [mailto:[email protected]] On Behalf Of Min Yu Sent: Friday, 09 September, 2016 17:12 To: [OPNFV SPC] ([email protected]); [email protected] Subject: [opnfv-strategic-plan-committee] [SPC Polestar] Minutes from the OPNFV SPC Polestar WG call (September 8, 2016) Attendees: Anthony Soong, Bryan Sullivan, Larry Lamers, Margaret Chiosi, Michael Bugenhagen, Prakash Ramchandran, Steven Wright, Tapio Tallgren, Yunjun Zhang, Min Yu · Meeting Minutes/Agenda Approval: Approved · User Scenarios of Pain Points and Priorities by Steven o Steven noted that expansions and comments have been added to the Pain Points and a separate VNF Onboarding page<https://wiki.opnfv.org/pages/viewpage.action?spaceKey=EUAG&title=VNF+Onboarding+and+Deployment> has been created on the EUAG’s wiki. o A question was asked about the difference between “provider” and “operator” and if they have different requirements. A discussion then followed about the need to define these terms so the ecosystem operates from the same understanding. A suggestion was made that the Polestar WG could take this up as a future action item. o In the VNF Options section, a question was raised regarding the VNF Package being a “single binary object.” Steven noted that replacing “binary” with “executable” perhaps helps clarify the meaning. o A question was asked to define the OPNFV community as an actor. The attendees discussed whether this means OPNFV has a role to play in hosting technical validation of platform capability that enables VNFs rather than validating VNF packages in the market. A comment was made that if VNF onboarding is a feature in future OPNFV releases, OPNFV will also have a role in certifying that VNFs work with a particular release. The attendees generally agreed that it would be helpful for VNF vendors if operators start to outline what the processes are going to be, even though some are more business-oriented and do not apply to the OPNFV system. Such outlines would inform the vendors of the expectations and scope. o Margaret polled attendees’ plans to attend a F2F meeting at ODL Summit in Seattle to further discuss this. She also mentioned there was some overlap between what the MANO WG and the Polestar WG are doing. Bryan confirmed there are some overlaps and will clarify them for Margaret after the call. -- Min Yu Client Services Coordinator The Linux Foundation +1(530) 902-6464 (m) [email protected]<mailto:[email protected]> Skype: minyudecorah
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
