VoLTE VNF Descriptor gaps August 2017

Global Types Global File ZTE introduce new global types. GlobalSubstitutionTypesServiceTemplate.yaml This file contains all of ONAP global types. The new VoLTE csar’s that supply by ZTE does not contain this file, but a separate file for each type. ZTE introduce new global types. Not all types are following ETSI/TOSCA NFV profile. We are still working on the gap

VoLTE Global Types – What we found till now Missing tosca.nodes.nfv.ext.zte.VL tosca.requirements.nfv.VirtualStorage tosca.nodes.nfv.ext.zte.VDU tosca.requirements.nfv.VirtualLink tosca.nodes.nfv.ext.zte.CP tosca.requirements.nfv.VirtualBinding tosca.requirements.nfv.Forwarder tosca.relationships.nfv.VirtualLinksTo tosca.capabilities.nfv.Forwarder tosca.relationships.nfv.VirtualBindsTo tosca.capabilities.nfv.ext.Compute.Container.Architecture tosca.relationships.nfv.VDU.AttachedTo tosca.nodes.nfv.VnfVirtualLinkDesc Mutual tosca.nodes.nfv.VduCpd tosca.capabilities.Scalable tosca.nodes.nfv.VDU.VirtualStorage tosca.capabilities.OperatingSystem tosca.nodes.nfv.VDU.Compute (we have tosca.nodes.compute) tosca.capabilities.nfv.Metric (in use, we have in global org.openecomp.capabilities.Metric) tosca.capabilities.nfv.VirtualStorage tosca.capabilities.network.Bindable tosca.capabilities.nfv.VirtualLinkable tosca.capabilities.Endpoint.Admin tosca.capabilities.nfv.VirtualCompute tosca.capabilities.Container tosca.capabilities.nfv.VirtualBindable tosca.capabilities.Attachment tosca.artifacts.nfv.SwImage tosca.nodes.nfv.NS tosca.nodes.nfv.NS.vEPC_NS tosca.nodes.nfv.NS.vIMS_NS

Global Types Solving the gap R1 New types – Need to finish research Vendor’s need to move the types to GlobalSubstitutionTypesServiceTemplate.yaml SDC will support the new types

SDNO data types All of the SDNO types are missing from our system. relationships capabilities Solving the gap We will need to add all the types into SDC types

Main Service Template The VoLTE csar’s does not contain mainServiceTemplate.yaml There is no support with nested service templates There is only one service template which its name is openovnf_csarName.yaml Solving the gap R1 No nested support Vendor need to change openovnf_csarName.yaml to mainServiceTemplate.yaml

Node Types The openovnf_csarName.yaml service template does not contain node types section. All of the node types are written inside a file named openovnf__tosca.nodes.nfv.VNF.csarName.yaml Solving the gap R1 Vendor need to change openovnf_csarName.yaml to mainServiceTemplate.yaml Vendor need to copy the node type to mainServiceTemplate.yaml

Inputs In VoLTE csar’s there is no inputs section, all of the values are static( Hard Coded ) Solving the gap R1 Does all values are static? No impact

Imports In VoLTE csar’s it represented as a list, In SDC it represented as a Map<String, List> Solving the gap R1 SDC will do the convert in run time Future release Using SDC import using Map<String, List>

Substitution Mappings VoLTE csar’s syntax capability / requirement id : [node_template_id, capability / requirement] SDC syntax capability / requirement id: - node_template_id - capability / requirement Solving the gap R1 SDC will do the convert in run time Future release Use SDC syntax

Global Types - VNF SDK versus TOSCA NVF Profile NFV Profile – ETSI tosca.requirements.nfv.VirtualStorage tosca.nodes.nfv.VDU.VirtualStorage (also as part of VDU.Compute) tosca.requirements.nfv.VirtualLink tosca.requirements.nfv.VirtualBinding No tosca.relationships.nfv.VirtualLinksTo Yes but Loosely specified tosca.relationships.nfv.VirtualBindsTo Yes tosca.relationships.nfv.VDU.AttachedTo tosca.nodes.nfv.VnfVirtualLinkDesc tosca.nodes.nfv.VduCpd tosca.nodes.nfv.VDU.VirtualStorage tosca.nodes.nfv.VDU.Compute (we have tosca.nodes.compute) tosca.capabilities.nfv.VirtualStorage tosca.capabilities.nfv.VirtualLinkable Yes but as attribute of tosca.nodes.nfv.VduCpd tosca.capabilities.nfv.VirtualCompute tosca.capabilities.nfv.VirtualBindable tosca.artifacts.nfv.SwImage