Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 2 Next »

Description

A templates of this type are atoms of application logic, and they must be hosted. 

They are expected to have connection point bindings and are used to compose a Network Function, particularly a virtual one.

Nodes of this type are normally concrete, implemented using deployment artifacts.

Properties


NameRequiredTypeConstraintsDescription
nfc_classificationyesonap.datatypes.NetworkFunctionComponentClassification
Structured description of this component


Attributes

Nothing special

Capabilities

Types derived from onap.nodes.NetworkFunctionComponent normally extend it by at least one capability of type onap.capabilities.Bindable.


Requirements


NameRequiredTypeDescription
hostyes
tosca.capabilities.Container
A Network Function Component must be hosted. This requirement is normally paired with the host capability of a Compute-typed node. It can also be paired with the host capability of a Container-typed node.



TOSCA Definition


onap.nodes.NetworkFunctionComponent 
  onap.nodes.NetworkFunctionComponent:
    description: |
      Software component within a larger software package that makes up a virtual network function
    derived_from: onap.nodes.Resource
    properties:
      nfc_classification:
        description: |
          data governed value used by operations to filter network function components
        type: onap.datatypes.NetworkFunctionComponentClassification
        required: true
    capabilities:
      # Expect to specify connection point bindings within the derived type
    requirements:
      - host:
        capability: tosca.capabilities.Container
        relationship: onap.relationships.HostedOn


Examples

Extending the basic NetworkFunctionComponent with 2 port bindings and 1 storage attachment. Each of its extra Bindable-typed capabilities has its own descriptive name and sub-type.

Example of a customized type 
 node_types:
  PartOfMyFirewall:
    derived_from: onap.nodes.NetworkFunctionResource
     capabilities:
      bind_1:
          capability: onap.capabilities.Bindable123
      bind_2:
          capability: onap.capabilities.Bindable456
     requirements:
      - storage_attachment:
          capability: onap.capabilities.AttachedStorage
  • No labels