R3 onap.nodes.NetworkFunctionComponent

Network Function Components must be hosted, as they are atomic applications. 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.

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: onap.capabilities.Compute
        relationship: onap.relationships.HostedOn

Example of a customized type:

Extending the basic NetworkFunctionComponent with 2 port bindings and 1 storage attachment

Example of a customized type

 node_types:
  PartOfMyFirewall:
    derived_from: onap.nodes.NetworkFunctionResource
    requirements:
      - bind_1:
          capability: onap.capabilities.Bindable
      - bind_2:
          capability: onap.capabilities.Bindable
      - storage_attachment:
          capability: onap.capabilities.AttachedStorage