You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Objective

Represent PNFs in the TOSCA model, using TOSCA syntax and semantics to define the mapping between PNF resources used in ONAP services and the physical devices themselves.

PNF Modelling - Resources and Devices

Proposed approach is to use a “PNF Resource” node type (network function) representing the PNF’s appearance in services, and a separate “PNF Device” node type to represent the device itself (in the model and in inventory).  TOSCA requirements and capabilities are used to map the PNF Resources within services to their corresponding PNF Devices.

Currently, all PNF devices are pre-populated in inventory before they are assigned for use by services.  This makes them a good candidate for Requirements/Capabilities logic, where the PNF Resource has a dangling requirement for a PNF Device.  The mapping would be established at run-time by selecting which pre-deployed (and inventoried) PNF Device is to be used.

In this model, a new Capability base type is defined for PNF Devices.  Individual PNF devices would declare this capability (or one derived from it).  Their matching PNF Resource types would declare a requirement for its PNF Device capability.

PNF Resources are modelled as peers to VNFs and Allotted Resources, all being derivations of a base “Network Function” node type.  This would permit the three types to be used interchangeably in Abstract Node resolution.  The three resource types (VNF, PNF, AR) do not require explicit subtypes, but instead are identified by their defined requirements:

  • Allotted Resources have a requirement for an Allotted Resource Provider service
  • PNF Resources have a requirement for a PNF Device
  • VNF Resources have neither A-R Provider nor PNF Device requirements.

TOSCA Definitions

PNF Device Capability, exposed by all PNFs, allows PNF resources to be tied to individual device instances via a PNF Hosted On relationship.

PNF Capabilities and Relationships 
capability_types:
   onap.capabilities.PNFDevice:
      derived_from: tosca.capabilities.Root
      description:  Declaration of being a PNF Device
      valid_source_types:  []
      properties:
         # TBD if any properties needed
      attributes:
         # TBD if any attributes needed

relationship_types:
   onap.relationships.PNFHostedOn:
      derived_from: tosca.relationships.HostedOn
      description:  Relationship between a PNF resources and the physical device
      properties:
         # TBD if any properties needed
      attributes:
         # TBD if any attributes needed


Base PNF Device node type, from which all individual PNF Devices would be derived.  There is no explicit PNF Resource node type, since all PNF resources may derive from the base Network Function type, and be identified as PNFs based on the existence of a PNF Device requirement.

PNF Device 
node_types:
   onap.nodes.PNFDevice:
      derived_from: tosca.nodes.Root
      description:  Base type for PNF Device node types
      properties:
         # TBD if any properties needed
      attributes:
         # TBD if any attributes needed

Examples

This example shows a specific PNF device, along with the PNF resource that it exposes for use in ONAP services.

PNF Example 
# A specific capability for this firewall PNF device
capability_types:
   vendor.capabilities.pnfDevice.MyFirewall:
      derived_from: onap.capabilities.PNFDevice
      description:  Declaration of being a specific PNF Device

# node types for the Firewall PNF device and corresponding PNF Resource
node_types:
   vendor.nodes.devices.pnfs.MyFirewall:
      derived_from: onap.nodes.PNFDevice
      description:  A PNF Firewall Device
      properties:
         # as needed
      attributes:
         # as needed
      capabilities:
         pnf_device:
            type:  vendor.capabilities.pnfDevice.MyFirewall

   # My Firewall PNF Resource node type.
   # Note that this could derive from an abstract Firewall node type for run-time selection.
   vendor.nodes.resources.network_functions.MyFirewallPNF:
      derived_from: onap.nodes.resources.NetworkFunction
      description:  A PNF Firewall Resource
      properties:
         # as needed
      attributes:
         # as needed
      requirements:
         pnf_device:
            capabilities:
               type:  vendor.capabilities.pnfDevice.MyFirewall
               relationship: onap.relationships.PNFHostedOn
               node: vendor.nodes.devices.pnfs.MyFirewall


This example shows a Service template consuming a PNF Firewall resource.

Service using PNF 
node_templates:
   # Node for the PNF Firewall Resource.
   # Note that the requirement for PNF Device was declared in the MyFirewallPNF node
   # type, and hence does not need to be restated here.
   my_pnf_firewall:
      type:  vendor.nodes.resource.network_functions.MyFirewallPNF
      properties:
         # as needed
      attributes:
         # as needed
  • No labels