VNFD and NSD modeling: Rel2 Thinh Nguyenphu, Nokia thinh

Slides:



Advertisements
Similar presentations
TOSCA Workloads with OpenStack Heat-Translator
Advertisements

NETWORK CONNECTIVITY USE CASES AT CARRIER / SERVICE PROVIDERS CloudBand June 2014.
TOSCA-in-NFV Qin Jin Deepanshu Gautam.
NETWORK CONNECTIVITY USE CASES AT CARRIER / SERVICE PROVIDERS CloudBand June 2014.
How TOSCA Adds Value in NFV world
IETF-53-IPv6 WG- Cellular host draft 1 Minimum IPv6 Functionality for a Cellular Host Jari Arkko Peter Hedman Gerben Kuijpers Hesham Soliman John Loughney.
Update for tosca-nfv-profile
Mapping between NFV model and TOSCA
ETSI NSD Overview & TOSCA model Thinh Nguyenphu, Nokia thinh
VNF Package CSAR Format Tal Halfon, Amdocs Andrei Kojukhov, PhD, Amdocs Aug 3, 2017.
VNF Package CSAR Format Tal Halfon, Amdocs Andrei Kojukhov, PhD, Amdocs Aug 3, 2017.
OPEN-O Modeling Directions (DRAFT 0.6)
ETSI NFV: IFA & SOL specifications list
VNF Package CSAR for ONAP Release 2 – adding Telco grade features Andrei Kojukhov, PhD, Amdocs Oct 6, 2017.
Change Log VNF Package Model Business Compute Req.
VoLTE VNF Descriptor gaps
Domino Release D Planning
ONAP SDC TOSCA Import Gap Analysis
NFV Updates Deepanshu Gautam.
ONAP Information Model and Data Model
ECOMP Information Model
Deployment Flavour as VNF Capability: Alt1_r3
ETSI NSD Overview & TOSCA model Thinh Nguyenphu, Nokia thinh
Instantiation Level, Scaling Aspect, Scale Info
Approach to finalize the TOSCA NFV profile
OASIS TOSCA Report for December ONAP Event
Clarification of CSAR format Thinh Nguyenphu, Nokia thinh
TOSCA Namespaces for tosca-nfv-profile
DF design as a node type.
Deployment Flavor Model – Challenges and Emerging trends for ONAP adaptation Priya TG, NetCracker Technology.
OASIS TOSCA Report for December ONAP Modeling Workshop
NSD modeling: Rel2 Nagesha Subramanya nagesha.
TOSCA Namespaces Explained
Network Service Model with TOSCA yaml
Capability issues Shitao li.
OASIS TOSCA Report for December ONAP Event
Documenting ONAP components (functional)
ACTN Information Model
DF design as a node type (output by Chris and shitao)
TOSCA NFV profile: short vs long-term approach
DF design as a node type (output by Chris and shitao)
NFV & SDN adhoc Progress
Enhancements for Simple YAML Profile v1.2
TOSCA Namespaces Explained
SwImageDesc Shitao li.
Remain issues
“Deployment Flavor” Concept Desired End-Goal
TOSCA Namespaces for tosca-nfv-profile
ETSI NFV ISG IM/DM Modelling progress Report
Defining ONAP VNF Package Model
VNF Package Model Per ETSI NFV SOL001, SOL004, SOL005
IFA007: VNF LCM The Or-Vnfm reference point is used for exchanges between Network Functions Virtualization Orchestrator (NFVO) and Virtualized Network.
ONAP modeling report shitao.
VDU proposal comparison
VNFD Overview & TOSCA model Thinh Nguyenphu, Nokia thinh
ONAP Information Model Topics Timeline
New VDU model proposal.
DF design as a node type (output by Chris and shitao)
Deployment Flavour as VNF Capability: Alt1_r2
Discussion of Publishing CSD03 version of NFV Profile
NFV adhoc Shitao li.
VDU proposal comparison
TOSCA Simple Profile for YAML: Changes proposed for 1.3 release
Open Source Projects Collaborations with ONAP
TOSCA v1.3 Enhancements February 21, 2019.
NFV adhoc Shitao li.
TOSCA v2.3 Naming Decisions
NFV adhoc Shitao li.
VNF Package CSAR Format Tal Halfon, Amdocs Andrei Kojukhov, PhD, Amdocs Aug 3, 2017.
NSD model in ONAP service descriptors (draft7)
Presentation transcript:

VNFD and NSD modeling: Rel2 Thinh Nguyenphu, Nokia thinh VNFD and NSD modeling: Rel2 Thinh Nguyenphu, Nokia thinh.nguyenphu@nokia.com September 27, 2017

NFV SOL001: Status SOL WG has taken a more proactive and collaborative approach by developing SOL001 GS specification. SOL001 will endorse a specific version (e.g. CSD04) of the OASIS TOSCA NFV document. Plus, additional technical contents based on Simple YAML Profile v1.2, IFA011 and IFA014. SOL001 latest draft : https://docbox.etsi.org/ISG/NFV/Open/Drafts/SOL001_TOSCA_desc/ NFV-SOL001v010.zip Estimate timeline: 90% VNFD content by end of 2017, 10% is mainly all of editor notes to be resolve. WG approved draft (VNFD) should be ready by end of January 2018. NSD within 4 months or less, or parallel work to meet milestone date.

SOL001: Contents Node Type: tosca.nodes.nfv.VNF as Properties Group Type: tosca.groups.nfv.ElementGroup Node Type: tosca.nodes.nfv.VNF as Properties Node Type: tosca.nodes.nfv.VDU.Compute Capabilities Type: tosca.capabilities.nfv.VirtualCompute Node Type: tosca.nodes.nfv.VDU.VirtualStorage tosca.nodes.nfv.VnfVirltualLinkDesc tosca.nodes.nfv.ExtCpd TBD Capabilitities Type: tosca.capabilities.nfv.VnfDeploymentFlavour Data Type: tosca.datatypes.nfv.VnfConfigurableProperties tosca.datatypes.nfv.VnfInfoModifiableAttributes Interface Type: tosca.interfaces.nfv.vnf.lifecycle.Basic tosca.interfaces.nfv.vnf.lifecycle.Healable tosca.interfaces.nfv.vnf.lifecycle.Scalable Capabilitities Type: tosca.capabilities.nfv.VnfIndicator

SOL001 ETSI NFV Element [IFA011] SOL001 Derived from VNF tosca.nodes.nfv.VNF tosca.nodes.Root VDU tosca.nodes.nfv.VDU.Compute tosca.nodes.compute Cpd (Connection Point) tosca.nodes.nfv.Cpd VduCpd (internal connection point) tosca.nodes.nfv.VduCpd VnfVirtualLinkDesc (Virtual Link) tosca.nodes.nfv.VnfVirtualLinkDesc External connection point tosca.nodes.nfv.VnfExtCpd Virtual Storage   Virtual Compute tosca.capabilities.nfv.VirtualCompute tosca.capabilities.Root Software Image tosca.artifacts.nfv.SwImage tosca.artifacts.Deployment.Image Deployment Flavour tosca.capabilities.nfv.DeploymentFlavour Scaling Aspect tosca.datatypes.nfv.ScalingAspect tosca.datatypes.Root Element Group tosca.groups.nfv.ElementGroup tosca.groups.Root Instantiation Level tosca.datatypes.nfv.InstantiationLevel

SOL001: Ref: https://docbox. etsi SOL001: Ref: https://docbox.etsi.org/ISG/NFV/Open/Drafts/SOL001_TOSCA_desc/NFV-SOL001v010.zip tosca.nodes.nfv.VNF: tosca.nodes.nfv.VNF: derived_from: tosca.nodes.Root properties: descriptor_id: # instead of vnfd_id type: string # GUID required: true descriptor_version: # instead of vnfd_version type: string provider: # instead of vnf_provider product_name: # instead of vnf_product_name software_version: # instead of vnf_software_version product_info_name: # instead of vnf_product_info_name required: false product_info_description: # instead of vnf_product_info_description vnfm_info: type: list entry_schema: localization_languages: default_localization_language: capabilities: vnf: type: tosca.capabilities.nfv.VNF deployment_flavour: type: tosca.capabilities.nfv.VnfDeploymentFlavour #monitoring_parameter: # modeled as ad hoc capabilities in VNF node template requirements: - virtual_link: capability: tosca.capabilities.nfv.VirtualLinkable relationship: tosca.relationships.nfv.VirtualLinksTo node: tosca.nodes.nfv.VL occurrences: [ 0, UNBOUNDED ]  

Avoid Spec collision or namespaces SOL001 GS must follow the rules from TOSCA Simple YAML, section 3.1; Nokia Proposal to ETSI NFV SOL WG. Under discussion. No decision yet Namespace Alias Namespace URI Specification Description tosca_simple_yaml_etsinfv TBD The SOL001 (VNFD and NSD) based on TOSCA Simple Profile v1.2 (YAML) target namespace and namespace alias. Prefer, not to create a new prefix name. Further discussion with TOSCA TC is needed Namespace Prefix Specification Description tosca The reserved TOSCA Simple Profile Specification prefix that can be associated with the default TOSCA Namespace URI TOSCA Namespacing in TOSCA Service Templates TOSCA Service Templates MUST always have, as the first line of YAML, the keyword “tosca_definitions_version” For SOL001: tosca_definitions_version: tosca_simple_yaml_etsinfv_1_0

Conclusion SOL001 is VNFD and NSD data models (Stage3): NFV descriptors based on TOSCA Specification. Any maintenance changes to IFA011 or IFA014: SOL001 shall be updated in the same maintenance release. SOL006 is VNFD and NSD data models: NFV descriptors based on YANG Specification. Based on IFA011, IFA014 and SOL001. Goal: all of SOL001 TOSCA types will be mapped to YANG model Recommendation #1: SOL001 should be part of ONAP Rel2: VNF and service descriptors modeling Recommendation #2: Namespaces alias and prefix: Must follow TOSCA rules per section 3, & avoid collisions.