...
The Linkable-type requirement of the CP nodes are more important for modeling than the node type itself. When a the Linkable-type requirement of a CP is not used for an internal link and exposed through a substitution mapping of a model, this CP is external.
Capabilities
| Name | Required | Type | Constraints | Description |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Requirements
| Name | Required | Type | Description |
|---|
| binding | 0..1 | onap.capabilities.Bindable | The binding with a Network Function Component |
| link | 0..1 | onap.capabilities.Linkable | The link to a network. When left dangling, the CP is external. |
TOSCA Definition
| Code Block |
|---|
|
node_types:
onap.nodes.CP:
derived_from: onaptosca.nodes.ResourceRoot
description: a connection point
requirements:
- binding:
description: binding with a VFCNetworkFunctionComponent
capability: onap.capabilities.Bindable
occurrences: [1, 1] # exactly one occurrence
relationships: onap.relationships.BindsTo
- link:
description: link to a network. If left dangling, it is external.
capability: onap.capabilities.Linkable
occurrences: [1, 1]
# Exactly one occurrence;
# either spend it with an internal VL (and this is how this CP becomes internal)
# or leave it unsatisfied (and thus make the CP external)
relationships: onap.relationships.LinksTo
# without a relationship, a TOSCA requirement cannot have properties :(
|
...