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
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
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.