...
| Code Block |
|---|
| title | onap.capabilities.infrastructure.NIC |
|---|
| linenumbers | true |
|---|
| collapse | true |
|---|
|
capability_types:
onap.capabilities.infrastructure.NIC:
derived_from: onap.capabilities.Infrastracture
description: basic IO specifications
bitrate:
description: bits per second
type: integer
required: false
|
The In spite the changes made in the capability type defininitions, the definition of the node type onap.nodes.Container does not change:
| Code Block |
|---|
| title | onap.nodes.Container |
|---|
| linenumbers | true |
|---|
| collapse | true |
|---|
|
node_types:
# the very base of the hierarchy of VDU types
onap.nodes.Container:
derived_from: onap.nodes.Resource
artifacts:
container_image:
type: tosca.artifacts.Deployment
description: an image used to launch the Container
interfaces:
Standard:
start:
implementation: container_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..1]
- 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] |