...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
node_types:
# the very base of the hierarchy of VDU types
onap.nodes.VDU:
derived_from: onap.nodes.Resource
artifacts:
vdu_image:
type: tosca.artifacts.Deployment
description: an image used to launch the VDU
interfaces:
Standard:
start:
implementation: vdu_image
capabilities:
host:
type: tosca.capabilities.Container # the TOSCA Specs type is good enough
occurrences: [0..UNBOUNDED]
requirements:
- cpu:
capability: onap.capabilities.infrastructure.CPU:
occurrences: [0..UNBOUNDED]
- memory:
capability: onap.capabilities.infrastructure.Memory:
occurrences: [0..UNBOUNDED]
- storage:
capability: onap.capabilities.infrastructure.Storage:
occurrences: [0..UNBOUNDED]
- io:
capability: onap.capabilities.infrastructure.IO:
occurrences: [0..UNBOUNDED]
- nic:
capability: onap.capabilities.infrastructure.NIC:
occurrences: [0..UNBOUNDED]
|
Please note that VDU is derived from Resource, and thus inherits a requirement for a host. This way we are able to model the situations when a container is hosted by another container, for example a docker container running on a specific VM.
To create a reusable VDU customization, create a sub-type:
...