NFV adhoc Shitao li

Main progress Latest draft: tosca-nfv-v1.0-wd04-rev09 https://www.oasis- open.org/committees/document.php?document_id=60645&wg_abbrev=tosca Main content Partially done Done Done Done Done Under discussion Partially done Done Done Under discussion Under discussion Under discussion Under discussion

VDU Two VDU design principles: 1,flat method 2,composition method

tosca.nodes.nfv.VDU.VirtualStorage This solution aligns with VNFD info model as defined in IFA011, but there are problems of misalignment with TOSCA existing features Three suggestions: 1, delete all the content of VirtualStorage in the document if agreement can not meet before the deadline (May 10) 2, wait the response from Bruce and IFA if IFA decide to make the change based on TOSCA definition 3, create the new relationship based on Matt suggested in Feb

Deployment flavour Potential proposals from TOSCA NFV Adhoc group VNF Package contains: the VNF descriptor (VNFD) that defines metadata for package onboarding and VNF management Artifacts: the software images needed to run the VNF optional additional files to manage the VNF (e.g. scripts, vendor-specific files etc.) Is digitally signed and delivered by the VNF provider as a whole Is immutable (protected from modification) Is stored in a repository by the NFVO Can be accessed by VNFM Option 1 Option 2 VNF Package VNF Package VNFD(s) VNFD Artifact(s) Artifact(s) Discussion: Option 1: Single VNF package contains all of VNFD(s) + all of supported artifacts + manifest file. Or, Option 2: Single VNF package contains a VNFD + all of supported artifacts + manifest file. If multiple DFs has to be supported, multiple VNF packages are needed. Manifest Manifest

Deployment flavour Common understanding from NFV&SDN adhoc Current working assumption from OASIS TOSCA NFV adhoc Support single DF per TOSCA service template . Support one or more TOSCA service templates in the CSAR VNF package. 1 TOSCA Service Template = a VNFD with a single DF. CSAR package contains one or more TOSCA service templates. (option 1 and option 2 can both support) For option 1 All VNFDs have the same VNFD Identifier (GUID). “flavour_id” will be used to identify which VNFD (service template) © ETSI 2014. All rights reserved

New milestone The latest draft includes the basic modeling components of VNFD: CP ,VL, VDU, image Ask for approval of tosca-nfv-profile-CSD04 based on the latest draft: https://www.oasis- open.org/committees/document.php?document_id=60700&wg_abbrev=tosc a 2019/2/22

Other activity ONAP Project Developer Event May 2 - 5, 2017 AT&T Labs Research, Middletown, NJ https://wiki.onap.org A modelling project proposal has been submitted to ONAP: One of the project scope using TOSCA as service design language (including TOSCA Parser) 2019/2/22

Thank you! 2019/2/22