Description
A templates of this type are atoms of application logic, and they must be hosted.
...
| Name | Required | Type | Constraints | Description |
|---|---|---|---|---|
| nfc_classification | yes | onap.datatypes.Classification | 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
| Name | Required | Type | Description |
|---|---|---|---|
| host | yes | 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
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
onap.nodes.NetworkFunctionComponent:
description: |
Software component within a larger software package that makes up a virtual network function
derived_from: tosca.nodes.Root
properties:
nfc_classification:
description: |
data governed value used by operations to filter network function components
type: onap.datatypes.Classification
required: true
catalog_info:
type: onap.datatypes.CatalogInfo
description:
required: true
# generated by Design Time Catalog once, then never changed
role:
type: string
description: the role a template plays in a topology
required: false
attributes:
instance_name:
type: string
description: the name of the run-time instance of in the deployment
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.
...