SOL 001 VNF Descriptor VNFD Overview ONAP example

SOL 001 VNF Descriptor (VNFD) Overview, ONAP example & extension Thinh Nguyenphu, Nokia Bell Labs ETSI NFV SOL Vice-Chair January 8, 2019 1 © Nokia 2018

Topics § VNF Descriptor (VNFD) Overview (Part #1 & #2) § Type definitions § Configurable properties & modifiable attributes § Type extension § VNFD service template design: single & multiple deployment flavours § SOL 001 status (Part #3) § ONAP v. CPE example (Part #4) § ONAP extension (Part #5) 2 © Nokia 2018

Part 1: VNFD Overview 3 © Nokia 2018

IFA 011: VNF Descriptor (VNFD) Logical view VNF Descriptor VNFD VNFC 2 VNFC 1 VDU Compute Storage Internal Cp Sw Image ICP 1 ECP 1 Internal VLD IVL 1 ICP 2 ICP 3 ICP 4 IVL 2 ECP 2 level of resources to be instantiated within a deployment flavour in term of the number VNFC instances to be created for each VDU Instantiation Level External CPD Deployment Flavour © simplified Nokia 2018 4 Note: view and contents, some information elements are not illustrated VDU Profile VL Profile VNF LCM Op Config Scaling Aspect describes additional instantiation data for a given VDU. Compute used in the a specific deployment flavour. additional instantiation data for a given VL used in a specific deployment flavour represents information to configure lifecycle management operations describes the details of an aspect used for horizontal scaling

SOL 001 (VNFD): TOSCA service template overview VNF properties: Interfaces: Vnflcm Virtual. Linkable Vnf. Virtual. Link properties: Virtual. Linkable Vdu. Cp properties: Virtual. Linkable Virtual. Bindable Vdu. Compute properties: Virtual. Compute Virtual. Storage Virtual. Bindable Vnf. Ext. Cp* artifacts: sw. Image properties: Vdu. Virtual. Block. Storage* properties: Virtual. Storage artifacts: sw. Image VDU Virtual. Linkable Symbol: capabilities requirements Policies instantiation level Policies Scaling Policy: Affinity & Anti. Affinity Policy: Security. Group. Rule VNFD service template 5 Ø SOL 001 (v 0. 11. 0): based on TOSCA Simple YAML Profile v 1. 2. Ø https: //docbox. etsi. org/ISG/NFV/Open/Drafts/SOL 001_TOSCA_desc/NFV-SOL 001 v 0110. zip Ø In the case of single deployment flavour, SOL 001 support both TOSCA Simple YAML Profile v 1. 1 and 1. 2. © Nokia 2018 SOL 001 NFV Type definition file: etsi_nfv_sol 001_vnfd_2_5_1_types. yaml Ø Includes

VNF: configurable_properties & modifiable_attributes § § configurable_properties: (tosca. datatypes. nfv. Vnf. Configurable. Properties): Describes the configurable properties of the VNF § additional. Configurable. Property: To be defined by the VNF provider to allow functional blocks such as the NFVO to instruct the VNFM to set certain properties of the VNF instance. § must be declared in VNFD and default value may be declared. These default values will be part of the Vnf. Info object, once the VNF instance is created. § It must be set by Modify VNF Information operation via SOL 003 or SOL 002 API. § Key point: this property is to be consume by VNF instance, via VNFM pass this information to VNF instance via Modify VNF Information operation. § Applicable to tosca. datatypes. nfv. Vnfc. Configurable. Properties modifiable_attributes: (tosca. datatypes. nfv. Vnf. Info. Modifiable. Attributes): Describes the modifiable attributes of the VNF § 6 These will allow an external functional block to set information that is typically for consumption by the VNFM, but is not always sent to the VNF instance. It can be used by VNF LCM script. © Nokia 2018 Additional info: https: //docbox. etsi. org/ISG/NFV/Open/Other/Tutorials 201810_SDN_NFV_World_Congress-The_Haque/ETSI_NFV_Layer 123_VNF%20 Configurationv 2_RX 15009. pdf

Type extension is used when VNF-specific type information is introduced in the VNFD: modifiable attributes, configurable properties, & additional parameters to LCM operations Type tosca. nodes. nfv. VNF Keyname properties interfaces Property name modifiable_attributes (as a new property) configurable_properties (as a new property) Vnflcm. {operation_name}. inputs. additional_parameters (as a new property) configurable_properties (as a new property) tosca. nodes. nfv. Vdu. Compute properties tosca. datatypes. nfv. Vnf. Info. Modifiable. Attributes properties tosca. datatypes. nfv. Vnf. Configurable. Properties properties extensions (as a new property) metadata (as a new property) additional_configurable_properties (as a new property) tosca. datatypes. nfv. Vnfc. Configurable. Properties properties additional_vnfc_configurable_properties (as a new property) tosca. datatypes. nfv. Vnf. Info. Modifiable. Attributes. Extensions properties (new properties) tosca. datatypes. nfv. Vnf. Info. Modifiable. Attributes. Metadata properties (new properties) tosca. datatypes. nfv. Vnf. Additional. Configurable. Properties properties (new properties) tosca. datatypes. nfv. Vnf. Additional. Vnfc. Configurable. Properties properties (new properties) tosca. datatypes. nfv. Vnf. Operation. Additional. Parameters (new properties) 7 © Nokia 2018 properties

Part 2: VNFD Service Template Design 8 © Nokia 2018

1 service template design*: based on tosca_simple_yaml_1_1 tosca_definitions_version: tosca_simple_yaml_1_1 VNF-specific node type: derived from tosca. nodes. nfv. vnf Imports: SOL 001 NFV types flavor_id : required *See backup slide for 2 Levels service template design 9 © Nokia 2018

Part 3: SOL 001 Status 10 © Nokia 2018

Summary & next steps SOL 001 VNF & NSD version 2. 5. 1 GS is published, December 14, 2018: https: //www. etsi. org/deliver/etsi_gs/NFV-SOL/001_099/001/02. 05. 01_60/ § The following are VNFD features not included in this publication as specified in ETSI GS NFV-IFA 011: § Vnf. Indicators; auto. Scale § The following are NSD features not included in this publication, as specified in ETSI GS NFV-IFA 014 : § Multiple NS deployment flavours; NS scaling Aspect; Multiple Ns instantiation levels; Nested NS design; Vnffgd; NS Monitoring; Vnf. Indicators; Dependencies § SOL 001 v 2. 6. 1 maintenance works has started 11 © Nokia 2018

Part 4: Examples 12 © Nokia 2018

13 © Nokia 2018

5 onboarding vnfs • • • 14 infra: v. DHCP, v. AAA, v. DNS, v. WEB vbrgemu: BRG Emulator(Bridged Residential Gateway Emulator) vbng: VPP based Broadband Network Gateway vgmux: VPP based Virtual Gateway Multiplexer vgw: VPP based Virtual Gateway © Nokia 2018

ONAP Use case: v. CPE § Based on ONAP v. CPE use case § https: //wiki. onap. org/display/DW/v. CPE+with+Tosca+VNF+Test+Guid e § ref: vsn CSAR package § VNF has two VDUs, which are connected to each other via Vdu. Cpds and Vnf. Virtual. Link (internal VL). § No external connection point (Vnf. Ext. Cp) § Interest to understand rational of not describing external connection point. 15 © Nokia 2018

SOL 001 example based on ONAP v. CPE CSAR package § Goal is to demonstrate SOL 001 VNFD in ONAP use case § This example illustrate SOL 001 type definitions with ONAP extension Disclaimer: This analysis was done prior receiving latest ONAP v. CPE CSAR packages (https: //wiki. onap. org/display/DW/v. CPE+with+Tosca+VNF+Test+Guide). Even though the content is different, but the mapping and conclusion is still the same. 16 © Nokia 2018

definition version & type definition Not applicable or missing from VNFD SOL 001 17 © Nokia 2018 ONAP

Inputs and Vnf. Info. Modifiable. Attributes SOL 001 18 © Nokia 2018 ONAP

VNF node type and substitution_mapping Not applicable or missing from VNFD SOL 001 19 © Nokia 2018 ONAP

Vnf. Virtual. Link SOL 001 20 © Nokia 2018 ONAP

Vdu. Compute 21 © Nokia 2018 SOL 001 ONAP

Key finding & discussion § YAML version: SOL 001 based on v 1. 2 vs ONAP based on 1. 0 § SOL 001 uses tosca. nodes. nfv. VNF and substitution_mapping to represent VNF as whole § Template inputs still be can use as part of general template inputs. However, for there are user data which can be use via tosca. datatypes. nfv. Vnf. Info. Modifiable. Attributes § SOL 001 does not support: § “physical. Network” property in tosca. nodes. nfv. Vnf. Virtual. Link § “fixed_ip_address” property in tosca. nodes. nfv. Vdu. Cp § “watchdog” property in tosca. datatypes. nfv. Vdu. Profile § “inject_files” property in tosca. nodes. nfv. Vdu. Compute § “user_data” mapped to “boot_data” 22 © Nokia 2018 Note: Open. Stack is deprecating file injection. For rationale and details: https: //specs. openstack. org/openstack/nova-specs/queens/implemented/deprecate -file-injection. html

Part 5: ONAP extension 23 © Nokia 2018

ONAP extension: not defined in IFA 011 v 2. 4. 1 or SOL 001 v 2. 5. 1 § tosca. datatypes. nfv. Vdu. Profile: § § Watchdog vm. Boot. Up. Time. Out § tosca. datatypes. nfv. Vl. Profile: § § § § § 24 initiation. Parameters cidr network. Name start. Ip & end. Ip gateway. Ip segmentation. Id physical. Network network. Type vlan. Transparent © Nokia 2018 § tosca. nodes. nfv. Vdu. Compute: § inject_files § tosca. nodes. nfv. Cp: § allowed. Address. Data § tosca. nodes. nfv. Vdu. Cp § vnic_name § vnic_order § vnic_type These node and data types are not compatible, which will collision

Way forward § Working assumption: Dublin release supports single deployment flavour. § These node and data types (previous slide) are not compatible, which will cause a collision § Recommend#1: member companies prepare and submit these additional extension to ETSI NFV IFA and SOL WG toward v 2. 6. 1 or later. § Recommend#2: ONAP adopts SOL 001 Type extension method, per clause 5. 6 § Recommend #3: update ONAP function block to support TOSCA grammar v 1. 1 and v 1. 2 (e. g. substitution_mapping) § Additional discussion on vnf configuration data, such as configurable properties, vnf. Infomodifivable input. 25 © Nokia 2018

26 © Nokia 2018

DISCLAIMER The contents of this presentation is for overview and discussion nature. To make this presentation easy to understand to non-experts, not all technical details are shown. In case of discrepancies between the contents of this present document and the ETSI NFV Group Specifications, the latter source of information takes precedence. 27 © Nokia 2018

Backup 28 © Nokia 2018

Virtual Storage types: Virtual File Storage • Persistent virtual storage resources: block, object, and file • Local or ephemeral disk(s): modeled as capability type: virtual_local_storage Vdu. Virtual. File. Storage properties: virtual_file_storage_data: Virtual Block Storage Vdu. Virtual. Block. Storage Virtual. Linkable properties: virtual_block_storage_data sw_image_data Vdu. Compute Virtual. Storage properties: Virtual. Compute virtual_local_storage artifacts: sw. Image Virtual. Storage virtual. Bindable Symbol: capabilities requirements Virtual Object Storage Vdu. Virtual. Object. Storage Node type artifacts: sw. Image properties: virtual_object_storage_data Virtual. Storage Virtual. File. Storage and Vdu. Compute must be connected to the same vnf. Virtual. Link (not shown in the picture) 29 © Nokia 2018

VNF external connection point Vnf. Virtual. Link properties: Vdu. Cp Note 1 properties: Virtual. Linkable properties: Virtual. Bindable Virtual. Linkable Vnf. Ext. Cp Vnf. Extcp (Vdu. Cp) Virtual. Linkable Virtual. Bindable Note 2 properties: Virtual. Linkable External connection point (CP) re-exposing an internal CP Virtual. Linkable External CP connected to internal virtual link (VL) Note 1: In the case of re-exposing a Vdu. Cp as external connection point (Vnf. Ext. Cp). Note 2: A node template of this type is used to represent a VNF external connection point only in the case the Vnf. Ext. Cp is connected to an internal virtual link. § internal_virtual_link requirement to allow to connect it to an internal virtual link 30 © Nokia 2018 § external_virtual_link requirement to allow to connect it to an external virtual link