Description
A NetworkFunction is a resource which is able to fulfill a well-defined, non-trivial functionality for a service.
...
TODO: explain why this type does not have any capabilities and requirements
Properties
Name | Required | Type | Constraints | Description |
---|---|---|---|---|
classification | yes | onap.datatypes.Classification | Inherited from onap.nodes.Resource. Structured description of this function. For abstract function nodes, may be used for finding an implementation. |
Attributes
Nothing special
Capabilities
TODO: explain why this type does not have any capabilities and requirements
Requirements
TODO: explain why this type does not have any capabilities and requirements
TOSCA Definition
Code Block | ||||
---|---|---|---|---|
| ||||
node_types: onap.nodes.NetworkFunction: description: | a base of the ONAP hierarchy of network functions If you have a requirement for a factory, you're allotted If you have a requirement for a PNFdevice, you're physical If you have neither, you're virtual. Expect to see network functions be group members for naming and homing. derived_from: onap.nodes.Resource properties: # classification is inherited from onap.nodes.Resource, type, role, function should be required capabilities: # Expect to define these in the derived node_type, with mappings to appropriate the NetworkFunctionComponent CP # This exposes external CPs of the NF. requirements: # Expect to define these in the derived node_type, with mappings to appropriate inner nodes |
Examples
The examples below show possible type definitions of a firewall network function abstraction.
...