...
- architecture - allows the VFC vendors to focus their requirements on a specific hardware architecture, for example "Intel x86".
- custom_features - an opaque container for a list of feature definitions. Any text, the only limitation is that it should not break the YAML/TOSCA formatting. The contents of this property is actually not part of the TOSCA model!
Based on this generic onap,capabilities.Infrastructure capability type, the Data Model introduces a family of types that provide TOSCA support for the Informational Model elements.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
capability_types:
onap.capabilities.infrastructure.CPU:
derived_from: onap.capabilities.Infrastracture
description: processor capabilities
properties:
num_cpus:
type: integer
required: false
constraints:
- greater_or_equal: 1
cpu_frequency:
type: scalar-unit.frequency
required: false
constraints:
- greater_or_equal: 0.1 GHz
onap.capabilities.infrastructure.Memory:
derived_from: onap.capabilities.Infrastracture
description: memory capabilities
properties:
mem_size:
type: scalar-unit.size
required: false
constraints:
- greater_or_equal: 0 MB
onap.capabilities.infrastructure.Storage:
derived_from: onap.capabilities.Infrastracture
description: storage specifications
properties:
storage_size:
type: scalar-unit.size
required: false
constraints:
- greater_or_equal: 0 MB
onap.capabilities.infrastructure.IO:
derived_from: onap.capabilities.Infrastracture
description: basic IO specifications
bitrate:
description: bits per second
type: integer
required: false
onap.capabilities.infrastructure.NIC:
derived_from: onap.capabilities.Infrastracture
description: basic IO specifications
bitrate:
description: bits per second
type: integer
required: false
|