...
for example ROOT\Licenses\ License_term.txt
VNF Package Authenticity
tbdR-XXXXX: The VNF package Manifest file MUST contain a Signature calculated on all the contents of the Manifest file, as specified in ETSI GS NFV-SOL004.
Note: Moved to Dublin release.
VNF Package ONAP Extensions
- TOACA data type extension tosca.datatypes.nfv.injectFile is used for vCPE use case
- ONAP extensions for VNF package that is currently proposed for Dublin release is VES extension described below.
...
Info Element From ETSI GS NFV-IFA 011 | Implementation in TOSCA NFV Profile and Endorsement in ETSI GS NFV-SOL001 | Derived from | Description | Supported in ONAP Casablanca release | ||
VNFDVNF | tosca.nodes.nfv.VNF | tosca.nodes.Root | TOSCA main service template and describes a VNF in terms of deployment and operational behavior requirements, connectivity, interfaces and virtualized resource requirements | Y | ||
VDU Compute Descriptor R-09467 | tosca.nodes.nfv.VDU.Compute | tosca.nodes.Root | Represents VNF-C (or VM) with deployment flavours. Represents the virtual compute part of a VDU entity which it mainly describes the deployment and operational behavior of a VNFC Note: Currently not directly supported but allowed via tosca.capabilities.nfv.VirtualCompute | Y but different way | ||
VDU VirtualCompute Descriptor | tosca.capabilities.nfv.VirtualCompute | tosca.capabilities.Root | Represents the virtual compute part of a VDU entity which it mainly describes the deployment and operational behavior of a VNFC | Y | ||
VDU VirtualStorage Descriptor R-09467 | tosca.nodes.nfv.VDU.VirtualStorage | tosca.nodes.Root | Represents a virtual storage entity which it describes the deployment and operational behavior of a virtual storage resources Note: This node type is split into three in latest SOL001 draft how the data model uses an older version for Casablanca release | Y | Cpd - Connection Point Descriptor | toscaY |
Cpd - Connection Point Descriptor | tosca.nodes.nfv.Cp | tosca.nodes.Root | Represents network connectivity to a compute resource or a VL - abstract type used as parent for the various Cpd types. | Y | ||
VduCpd R-35851 | tosca.nodes.nfv.VduCp | tosca.nodes.nfv.Cp | Represents a type of TOSCA Cpd node and describes network connectivity between a VNFC instance (based on this VDU) and an internal VL | Y | ||
VnfVirtualLinkDesc R-35851 | tosca.nodes.nfv.VnfVirtualLink | tosca.nodes.Root | Node type represents a logical internal virtual link | Y | ||
VnfExtCpd (External Connection Point) R-35851 | tosca.nodes.nfv.VnfExtCp | tosca.nodes.nfv.CpRoot | Represents a logical external connection point, exposed by this VNF enabling connecting with Virtual Link, | N | ||
SwImageDesc R-02454 | tosca.artifacts.nfv.SwImage | tosca.artifacts.Deployment.Image | Artifact type describes the software image which is directly loaded on the Virtualisation container of the VDU or is to be loaded on a virtual storage resource Note: Currently not supported in Casablanca release as well as SW image artifact in CSAR | N | ||
DeploymentFlavour VnfDf info element R-41215 | tosca.capabilities.nfv.DeploymentFlavour | tosca.capabilities.Root | Note: Current ONAP release support a single deployment flavour | N | ||
Scaling Aspect R-96634 The VNF provider MUST describe scaling capabilities to manage scaling characteristics of the VNF. | tosca.datatypes.nfv.ScalingAspect | tosca.datatypes.Root | TBD in ETSI NFV-SOL001 | N |
...
A node type that includes the VirtualBindable capability indicates that it can be pointed by tosca.relationships.nfv.VirtualBindsTo relationship type.
tosca.capabilities.nfv.VirtualLinkableMetric
A node type that includes the VirtualLinkable Metric capability indicates that it can be pointed by monitored using a tosca.relationships.nfv.VirtualLinksToMonitor relationship type.
tosca.capabilities.nfv.ExtVirtualLinkableVirtualLinkable
A node type that includes the ExtVirtualLinkable VirtualLinkable capability indicates that it can be pointed by tosca.relationships.nfv.VirtualLinksTo relationshipNote: This capability type is used in Casablanca how it does not exist in the last SOL001 draft
tosca.capabilities.nfv.ExtVirtualLinkable
A node type that includes the ExtVirtualLinkable capability indicates that it can be pointed by tosca.relationships.nfv.VirtualLinksTo relationship
tosca.capabilities.nfv.VirtualCompute and tosca.capabilities.nfv.VirtualStorage includes flavours of VDU
...
This relationship type represents an association relationship between VDU and CP node types.
tosca.relationships.nfv.VirtualLinksToMonitor
This relationship type represents an association relationship between the VduCpd’s and VirtualLinkDesc to the Metric capability of VDU node types.
...
tosca.relationships.nfv.VirtualLinksTo
This relationship type represents an association relationship between the VduCpd’s and VirtualLinkDesc node types.
Interface Types
R-XXXXX: The VNFD provided by VNF vendor may use the below described TOSCA interface types. An on-boarding entity (ONAP SDC) MUST support them.
tosca.interfaces.nfv.vnf.lifecycle.Nfv supports LCM operations
5.1.9. HPA Requirements
(existing text remains)
5.1.10. VES Requirements
Note: ONAP proprietary extensions in ETSI SOL004 standards for VES support in CSAR package need to be manually loaded in R3 (Casablanca) for VNF and PNFs. Platform support will be developed for this in upcoming releases.CSAR provided by VNF vendor may include the ONAP proprietary extensions supported by SOL004 standard. The ONAP extensions should be registered in ETSI as specified in SOL004.
R-XXXXX: The CSAR extensions to support ONAP VES shall be described in both CSAR archive and manifest file as following:
- the CSAR includes:
!------Lfnetworkingonap
!----- ves.yaml
- the manifest file includes:
non_mano_artifacts_sets:
lfn_onap:
Source: Lfnetworkingonap/ves.yaml
Note: The VES extension is not supported in Casablanca release