Deployment Flavor Model Challenges and Emerging trends for

Deployment Flavor Model – Challenges and Emerging trends for ONAP adaptation Priya TG, Net. Cracker Technology

Deployment Flavour for NFV - Drivers q Dynamically deploy and change configurations, supported by E 2 E orchestration v Support different VNF and NS deployments during development , testing and production v Simulate a live network for testing purposes v Adapt to evolving architectures and underlying infrastructure requirements q Cope up with varying traffic demands through dynamic scaling of nodes within a deployed topology q Address variations in VNF Placement and Grouping requirements q Address variations in Qo. S and bandwidth requirements

VNF Deployment Flavour VNF VDU 1 VDU 3 VDU 5 VDU 2 VDU 4 VDU 6 Deployment topology in Deployment Flavor 1 ` q Number of VDUs during VNF instantiation q Affinity and anti affinity rules for VDUs and Virtual Links q Qos/bandwidth requirements of virtual links q Scaling aspect for horizontal scaling q Life Cycle Management Operations Deployment topology in Deployment Flavor 2 VDU 1 VDU 3 VDU 5 VDU 2 VDU 4 VDU 6 Deployment Flavour attribute in ETSI IFA 11 VNF Descriptor

Network Service Deployment Flavour q VNF Profile: Network Service VNF 2 o Minimum, Maximum number of VNF instances allowed in the NS o Affinity and anti affinity rules for VNFs o Connection information between VNF and NS virtual link VNF 3 VNF 1 q Virtual Link Profile: VNF 4 o Affinity and anti affinity rules for Virtual Links o Bit rate requirements VNF 5 q PNF Profile: o Connection relationship between a PNF connection point and NS virtual Link. Deployment Topologies VNF 2 VNF 4 VNF 3 VNF 5 VNF 1 VNF 2 VNF 4 q NS Profile: VNF 3 VNF 5 o Minimum, Maximum number of nested NS instances allowed in the NS o Affinity and anti affinity rules for nested NS q Number of VNF and Virtual Link instances during NS instantiation q Order in which VNF and nested NS instances need to be created q Scaling Aspect

TOSCA Approach v Address limitation of TOSCA which allows only one topology template per service template VNF Package VNF Service template Deployment Flavour service templates Artifact(s) Manifest Approach 1: Describe Deployment Flavours in multiple service templates within a VNF Package q Describe Deployment Flavour in a separate TOSCA service template, multiple service templates (1 per DF) in the same VNF Package q The VNF and NS Service templates are uniquely identifiable by the VNF Descriptor Id and NS Descriptor Id, and every deployment flavour service template is uniquely identified by flavour. Id q The VNF/NS and Deployment Flavour service templates describe the “common” info and the specific DF information q A mechanism to select the Deployment Flavour service template during run time should be identified using TOSCA Approach 2: One VNF Package for a Deployment Flavour, multiple VNF packages for a VNF q An alternative approach is to package every Deployment Flavour service template in a separate VNF package, implying multiple VNF packages and VNF Descriptors for multiple VNF deployment flavours. Single Deployment Flavour: Describe VNF Descriptor and Deployment flavour in a single service template

Challenges and Considerations - TOSCA Data Model Single VNF Descriptor Approach: Ø Address limitation of TOSCA which allows only one topology template per service template v Describe different deployment topologies in different service templates v Main service template to serve as “Entry point” for TOSCA orchestrator v “Child” service templates or “lower level” templates describe complete VNF information or Deployment Flavour specific information Ø Handle Single and Multiple deployment flavours in a consistent manner - a single design pattern to satisfy both use cases v Only a small % of VNF packages delivered by vendors have multiple deployment flavours v Ensure a simple straightforward approach for single deployment flavour while addressing multiple deployment flavour use case

Challenges and Considerations - TOSCA Data Model Ø Ensure consistency of common VNFD parts between service templates v If the entire VNF is described in lower level template, ensure consistency of common VNFD parts through “import” or appropriate design pattern Ø How to “wire” different service templates v A suitable mechanism for wiring the main service template with lower level templates ü “Property constraints” ü “Node filter” ü Requirements Vs Capabilities v Assembling a “deployable” service template - Design time Vs Run time v If the lower level service template describes the entire VNF (i. e. VNF Descriptor + Deployment Flavour), then the service template is independently deployable v If common VNF parts are described in top level service template, a suitable mechanism to assemble both service templates in to a “deployable” service template is needed at run time

Trends in SDOs Deployment Flavour as a capability – NOKIA Issue_TOSCA 317_NFV_VNFD_ Deployment_flavour_Alt 1_r 3. zip OASIS: ETSI SOL: NFVSOL(17)000541 r 2_SOL 001_VNFD_Vnf. Deployment. Flavour. docx v Deployment Flavour as a capability of VNF v TOSCA Simple Profile v 1. 2 grammar v Abstract VNF top level template, complete topology described in lower level templates Deployment Flavour as a Group – ZTE OASIS: TOSCA-317_VNFD_Deployment_Flavour. docx ETSI SOL: NFVSOL(17)000687 r 3_SOL 001_VNFD_Deployment_Flavour. docx v Deployment Flavour as a Group, DF attributes described as properties of the group v Single service template for entire VNF + DF v TOSCA Simple Profile v 1. 2 grammar Deployment Flavour as an Abstract Node - NETCRACKER OASIS: VNF ETSI SOL: Deployment Flavor proposal with end-to-end example-r 4 NFVSOL(17)000583 r 5_SOL 001_VNF_Deployment_Flavour. docx v Deployment Flavour as an abstract node in VNF descriptor v TOSCA Simple Profile v 1. 2 grammar v Top level service template with Virtual links, connection points etc. , DF related attributes in lower level templates Deployment Flavour as an Abstract Node – Ericsson OASIS: ETSI SOL: TOSCA_VNF_Deployment. Flavor-proposal. docx NFVSOL(17)000726 r 1_SOL 001_VNF_Deployment_Flavour. do cx v VNF and Deployment Flavour described as abstract nodes with flavour id as a capability of abstract DF node v TOSCA Simple Profile v 1. 1 grammar v Abstract VNF top level template, complete topology described in lower level templates

s Thank You