...
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
...
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: onapTosca.nodes.ResourceRoot properties: nfc_classification: description: | data governed value used by operations to filter network function components type: onap.datatypes.NetworkFunctionComponentClassificationClassification required: true capabilities: # Expect to specify connection point bindings within the derived type requirements: - host: capability: tosca.capabilities.Container relationship: onap.relationships.HostedOn |
...
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
node_types: PartOfMyFirewall: derived_from: onap.nodes.NetworkFunctionResourceNetworkFunctionComponent capabilities: bind_1: capability: onap.capabilities.Bindable123 bind_2: capability: onap.capabilities.Bindable456 requirements: - storage_attachment: capability: onap.capabilities.AttachedStorage |