...
ETSI 3.3.1 SOL001 Data Model with minimum CNF Properties from 4.1.1
VNF Data Model
- property "vnfm_info" constraint pattern: "(etsivnfm:v[0-9]?[0-9]\.[0-9]?[0-9]\.[0-9]?[0-9]$)|([0-9]:[a-zA-Z0-9.-]$)"
- values must be in format etsivnfm:v3.3.1 or <int>:<string>
- this is not enforced by constraint in type definition in ONAP
- property "vnf_profile" has not changed, but it is commented out in existing version in ONAP
- new attribute "scale_status" added
tosca.nodes.nfv.VNF: derived_from: tosca.nodes.Root description: The generic abstract type from which all VNF specific node types shall be derived to form, together with other node types, the TOSCA service template(s) representing the VNFD | ||||
| Id | Type | Cardinality | Description | |
|---|---|---|---|---|
| descriptor_id | String #UUID | 1 | Identifier for the VNFD | |
| descriptor_version | String | 1 | Identifies the version of the VNFD | |
| provider | String | 1 | provider of the VNF and of the VNFD | |
| product_name | String | 1 | name to | |
tosca.nodes.nfv.VNF: derived_from: tosca.nodes.Root description: The generic abstract type from which all VNF specific node types shall be derived to form, together with other node types, the TOSCA service template(s) representing the VNFD | ||||
| Id | Type | Cardinality | Description | |
| descriptor_id | String #UUID | 1 | Identifier for the VNFD | |
| descriptor_version | String | 1 | Identifies the version of the VNFD | |
| provider | String | 1 | provider of the VNF and of the VNFD | |
| product_name | String | 1 | name to identify the VNF product. Invariant for the VNF Product lifetime | |
| software_version | String | 1 | Software version of the VNF | |
| product_info_name | String | 0..1 | Human readable name of the VNF Product | |
| product_info_description | String | 0..1 | Human readable name for the VNF product | |
| vnfm_info | list of String | 1..n | Identifies VNFM(s) compatible with the VNF | |
| localization_languages | list of String | 0..n | Information about localization languages of the VNF | |
lcm_operations_configuration | tosca.datatypes.nfv.VnfLcmOperationsConfiguration | 0..n | Describes the configuration parameters for the VNF LCM operations | |
monitoring_parameters | list of tosca.datatypes.nfv.VnfMonitoringParameter | 0..n | Describes monitoring parameters applicable to the VNF. | |
flavour_id | String | 1 | Identifier of the Deployment Flavour within the VNFD | |
flavour_description | String | 1 | Human readable description of the DF | |
| vnf_profile | tosca.datatypes.nfv.VnfProfile | 0..1 | Describes a profile for instantiating VNFs of a particular NS DF according to a specific VNFD and VNF DF | |
| mciop_profile | list of tosca.datatypes.nfv.MciopProfile | 0..n | Describes additional instantiation data for the MCIOPs used in this deployment | |
| scale_status | :map of tosca.datatypes.nfv.ScaleInfo | 0..n | description:Scale status of the VNF, one entry per aspect. Represents for every scaling aspect how "big" the VNF has been scaled w.r.t. that aspect. | |
entry_schema: type: tosca.datatypes.nfv.ScaleInfo requirements: - virtual_link: capability: tosca.capabilities.nfv.VirtualLinkable relationship: tosca.relationships.nfv.VirtualLinksTo occurrences: [ 0, 1 ] # Additional requirements shall be defined in the VNF specific node type (deriving from tosca.nodes.nfv.VNF) corresponding to NS virtual links that need to connect to VnfExtCps | ||||
interfaces: Vnflcm: type: tosca.interfaces.nfv.Vnflcm # VnfIndicator: # type: tosca.interfaces.nfv.VnfIndicator # derived types are expected to introduce Vnf Indicator interfaces # with their type derived from tosca.interfaces.nfv.VnfIndicator | ||||
...
vnfExtCp Data Model
- tosca.nodes.nfv.VnfExtCP
- No Change since 2.7.1
VduCompute Data Model
- tosca.nodes.nfv.Vdu.Compute
- No Change since 2.7.1
- There are some changes from 2.6.1 to 2.7.1
- property "bootvnic_order" changed from list to boolean
- Backwards incompatible change from 2.6.1 -> 2.7.1
- property "nfvi_constraints" changed from list to map
- Backwards incompatible change from 2.6.1 -> 2.7.1
- property "boot_data" changed from string to tosca.datatypes.nfv.BootData
- property "bootvnic_order" changed from list to boolean
- The configurable_properties is still out of scope in Honolulu
...
- type" has the following extra valid_values:
- macvtap, baremetal, virtio-forwarder, smart-nic
- and the following removed valid_values - backwards incompatible:
- virtio
- requirement "virtual_link" cardinality changed from default (1-1) to 0-1
- requirement "virtual_binding" cardinality changed from default (1-1) to 1-1, i.e. no effective change
- type" has the following extra valid_values:
- requirement "external_virtual_link" cardinality changed from default (1-1) to 0-1
- requirement "internal_virtual_link" cardinality changed from default (1-1) to 1-1, i.e. no effective change
VduCompute Data Model
- tosca.nodes.nfv.Vdu.Compute
...
derived_from: tosca.nodes.Root
description: Describes the virtual compute part of a VDU which is a construct supporting the description of the deployment and operational behavior of a VNFC
...
name
...
String
...
1
...
Human readable name of the VDU
...
description
...
Human readable description of the VDU
...
boot_order
...
indicates whether the order of the virtual_storage requirements is used as the boot index (the first requirement represents the lowest index and defines highest boot priority)
default: false
...
nfvi_constraints
...
Describes constraints on the NFVI for the VNFC instance(s) created from this VDU. This property is reserved for future use in the present document.
...
monitoring_parameters
...
tosca.datatypes.nfv.VnfcMonitoringParameter
...
Describes monitoring parameters applicable to a VNFC instantiated from this VDU
...
#configurable_properties
...
tosca.datatypes.nfv.VnfcConfigurableProperties
...
derived types are expected to introduce configurable_properties with its type derived from tosca.datatypes.nfv.VnfcConfigurableProperties
...
vdu_profile
...
tosca.datatypes.nfv.VduProfile
...
Defines additional instantiation data for the VDU.Compute node
...
sw_image_data
...
tosca.datatypes.nfv.SwImageData
...
Defines information related to a SwImage artifact used by this Vdu.Compute node
...
boot_data
...
tosca.datatypes.nfv.BootData
...
Contains the information used to customize a virtualised compute resource at boot time. The bootData may contain variable parts that are replaced by deployment specific values before being sent to the VIM.
- No Change since 2.7.1
- There are some changes from 2.6.1 to 2.7.1
- property "boot_order" changed from list to boolean
- Backwards incompatible change from 2.6.1 -> 2.7.1
- property "nfvi_constraints" changed from list to map
- Backwards incompatible change from 2.6.1 -> 2.7.1
- property "boot_data" changed from string to tosca.datatypes.nfv.BootData
- property "boot_order" changed from list to boolean
- The configurable_properties is still out of scope in Honolulu
tosca.nodes.nfv.Vdu.Compute: derived_from: tosca.nodes.Root description: Describes the virtual compute part of a VDU which is a construct supporting the description of the deployment and operational behavior of a VNFC | ||||
| Id | Type | Cardinality | Constraints | Description |
|---|---|---|---|---|
name | String | 1 | Human readable name of the VDU | |
description | String | 1 | Human readable description of the VDU | |
boot_order | boolean | 1 | indicates whether the order of the virtual_storage requirements is used as the boot index (the first requirement represents the lowest index and defines highest boot priority) default: false | |
nfvi_constraints | map of String | 0..n | Describes constraints on the NFVI for the VNFC instance(s) created from this VDU. This property is reserved for future use in the present document. | |
monitoring_parameters | list of tosca.datatypes.nfv.VnfcMonitoringParameter | 0..n | Describes monitoring parameters applicable to a VNFC instantiated from this VDU | |
#configurable_properties | tosca.datatypes.nfv.VnfcConfigurableProperties | 0..n | derived types are expected to introduce configurable_properties with its type derived from tosca.datatypes.nfv.VnfcConfigurableProperties | |
vdu_profile | tosca.datatypes.nfv.VduProfile | 1 | Defines additional instantiation data for the VDU.Compute node | |
sw_image_data | tosca.datatypes.nfv.SwImageData | 0..1 | Defines information related to a SwImage artifact used by this Vdu.Compute node | |
boot_data | tosca.datatypes.nfv.BootData | 0..1 | Contains the information used to customize a virtualised compute resource at boot time. The bootData may contain variable parts that are replaced by deployment specific values before being sent to the VIM. | |
capabilities: virtual_compute: type: tosca.capabilities.nfv.VirtualCompute occurrences: [ 1, 1 ] virtual_binding: type: tosca.capabilities.nfv.VirtualBindable occurrences: [ 1, UNBOUNDED ] | ||||
requirements: - virtual_storage: capability: tosca.capabilities.nfv.VirtualStorage relationship: tosca.relationships.nfv.AttachesTo occurrences: [ 0, UNBOUNDED ] | ||||
VduVirtualBlockStorage Data Model
tosca.nodes.nfv.Vdu.VirtualBlockStorage
- property "sw_image_data" deprecated in 3.3.1
VduVirtualObjectStorage Data Model
tosca.nodes.nfv.Vdu.VirtualObjectStorage
- No Change since 2.7.1
VduVirtualFileStorage Data Model
tosca.nodes.nfv.Vdu.VirtualFileStorage
- requirement "virtual_binding" cardinality changed from default (1-1) to 1-1, i.e. no effective change in 3.3.1
VnfVirtualLink Data Model
tosca.nodes.nfv.VnfVirtualLink
- No Change since 2.7.1
VipCp Data Model
- New to SDC
tosca.nodes.nfv.VipCp: derived_from: tosca.nodes.nfv.Cp description: Describes a connection point to allocate one or a set of virtual IP addresses | ||||
| Id | Type | Cardinality | Constraints | Description |
|---|---|---|---|---|
vip_function | String | 1 | - valid_values: [ high_availability, load_balance ] | Describes the algorithm used to obtain the checksum value |
requirements: - target: capability: tosca.capabilities.Node relationship: tosca.relationships.DependsOn occurrences: [ 1, UNBOUNDED ] - virtual_link: capability: tosca.capabilities.nfv.VirtualLinkable relationship: tosca.relationships.nfv.VipVirtualLinksTo occurrences: [1, 1] | ||||
VirtualCp Data Model
tosca.nodes.nfv.VirtualCp: derived_from: tosca.nodes.nfv.Cp description: Describes a virtual connection point allowing the access to a number of VNFC instances (based on their respective VDUs). | ||||
| Id | Type | Cardinality | Constraints | Description |
|---|---|---|---|---|
additionalServiceData | list of tosca.datatypes.nfv.AdditionalServiceData | 1 | References the VDU(s) which implement this service | |
requirements: - target: capability: tosca.capabilities.Node relationship: tosca.relationships.DependsOn occurrences: [ 1, UNBOUNDED ] - virtual_link: capability: tosca.capabilities.nfv.VirtualLinkable relationship: tosca.relationships.nfv.VirtVirtualLinksTo occurrences: [1, 1] | ||||
Data types
Changed
The following data types already in ONAP have been changed from 2.5.1:
- tosca.datatypes.nfv.VirtualMemory:
- property "numa_enabled" default value changed from false to true
- tosca.datatypes.nfv.VnfcConfigurableProperties:
- property "additional_vnfc_configurable_properties" commented out
- tosca.datatypes.nfv.VnfcAdditionalConfigurableProperties:
- property "description" removed
- tosca.datatypes.nfv.VduProfile:
- version in ONAP contains extra properties not in ETSI:
- "watchdog", "vmBootUpTimeOut"
- version in ONAP contains extra properties not in ETSI:
- tosca.datatypes.nfv.L2ProtocolData:
- property "vlan_transparent" now mandatory
- version in ONAP contains extra properties not in ETSI:
- "segmentation_id" -> now in ONAP but as a string rather than int
- "physical_network"
- tosca.datatypes.nfv.VnfLcmOperationsConfiguration:
- new properties added:
- change_current_package, create_snapshot, revert_to_snapshot
- new properties added:
- tosca.datatypes.nfv.VnfInstantiateOperationConfiguration:
- property "description" removed"
- tosca.datatypes.nfv.VnfScaleOperationConfiguration
- property "scaling_by_more_than_one_step_supported" now mandatory
- tosca.datatypes.nfv.VnfConfigurableProperties:
- new optional properties added:
- vnfm_interface_info, vnfm_oauth_server_info, vnf_oauth_server_info
- existing property commented out:
- additional_configurable_properties
- new optional properties added:
- tosca.datatypes.nfv.VnfAdditionalConfigurableProperties:
- new required property added:
- is_writable_anytime
- existing property removed:
- description
- new required property added:
- tosca.datatypes.nfv.VnfInfoModifiableAttributes:
- existing properties commented out:
- extensions, metadata
- existing properties commented out:
- tosca.datatypes.nfv.VnfInfoModifiableAttributesExtensions:
- existing property removed:
- description
- existing property removed:
- tosca.datatypes.nfv.VnfInfoModifiableAttributesMetadata:
- existing property removed:
- description
- existing property removed:
- tosca.datatypes.nfv.SwImageData:
- new optional property added:
- provider
- property "checksum" changed type from string to tosca.datatypes.nfv.ChecksumData
- property "min_disk" new constraint added "greater_or_equal: 0 B"
- property "min_ram" new constraint added "greater_or_equal: 0 B"
- new optional property added:
- tosca.datatypes.nfv.VirtualBlockStorageData:
- property "size_of_storage" new constraint added "greater_or_equal: 0 B"
- property "rdma_enabled" now required
- tosca.datatypes.nfv.VirtualObjectStorageData:
- property "max_size_of_storage" new constraint added "greater_or_equal: 0 B"
- tosca.datatypes.nfv.VirtualFileStorageData:
- property "size_of_storage" new constraint added "greater_or_equal: 0 B"
- tosca.datatypes.nfv.VirtualLinkBitrateLevel:
- existing property removed:
- description
- existing property removed:
- tosca.datatypes.nfv.VnfOperationAdditionalParameters:
- existing property removed:
- description
- existing property removed:
- tosca.datatypes.nfv.VnfChangeFlavourOperationConfiguration:
- existing property removed:
- description
- existing property removed:
- tosca.datatypes.nfv.VnfChangeExtConnectivityOperationConfiguration:
- existing property removed:
- description
- existing property removed:
- tosca.datatypes.nfv.VnfcMonitoringParameter
- property "performance_metric" new valid_values added:
- v_cpu_usage_mean, v_cpu_usage_peak,v_memory_usage_mean,v_memory_usage_peak, v_disk_usage_mean, v_disk_usage_peak, v_net_byte_incoming, v_net_byte_outgoing, v_net_packet_incoming, v_net_packet_outgoing, usage_mean_vStorage, usage_peak_vStorage
- property "performance_metric" new valid_values added:
- tosca.datatypes.nfv.VirtualLinkMonitoringParameter:
- property "performance_metric" valid_values added:
- byte_incoming, byte_outgoing, packet_incoming, packet_outgoing
- property "performance_metric" valid_values removed:
- packet_outgoing_virtual_link, packet_incoming_virtual_link
- property "performance_metric" valid_values added:
- tosca.datatypes.nfv.VnfProfile
- new optional property "service_availability_level"
- tosca.datatypes.nfv.L3AddressData
- version in SDC contains extra property not defined in ETSI:
- fixed_ip_address
- version in SDC contains extra property not defined in ETSI:
Unchanged
The following data types are included in SDC but have no changes:
- tosca.datatypes.nfv.VirtualNetworkInterfaceRequirements
- tosca.datatypes.nfv.RequestedAdditionalCapability
- tosca.datatypes.nfv.VirtualCpu
- tosca.datatypes.nfv.VirtualCpuPinning
- tosca.datatypes.nfv.VlProfile
- tosca.datatypes.nfv.VirtualLinkProtocolData
- tosca.datatypes.nfv.L3ProtocolData
- tosca.datatypes.nfv.IpAllocationPool
- tosca.datatypes.nfv.InstantiationLevel
- tosca.datatypes.nfv.VduLevel
- tosca.datatypes.nfv.VnfScaleToLevelOperationConfiguration
- tosca.datatypes.nfv.VnfHealOperationConfiguration
- tosca.datatypes.nfv.VnfTerminateOperationConfiguration
- tosca.datatypes.nfv.VnfOperateOperationConfiguration
- tosca.datatypes.nfv.ScaleInfo
- tosca.datatypes.nfv.ScalingAspect
- tosca.datatypes.nfv.LogicalNodeData
- tosca.datatypes.nfv.InterfaceDetails
- tosca.datatypes.nfv.UriComponents
- tosca.datatypes.nfv.UriAuthority
- tosca.datatypes.nfv.ConnectivityType
- tosca.datatypes.nfv.LinkBitrateRequirements
- tosca.datatypes.nfv.CpProtocolData
- tosca.datatypes.nfv.AddressData
- tosca.datatypes.nfv.L2AddressData
- tosca.datatypes.nfv.Qos
- tosca.datatypes.nfv.VnfMonitoringParameter
Not Present
The following data types are not in SDC:
- introduced 2.6.1
- tosca.datatypes.nfv.ChecksumData
- introduced 2.7.1
- tosca.datatypes.nfv.VnfmInterfaceInfo
- tosca.datatypes.nfv.OauthServerInfo
- tosca.datatypes.nfv.BootData
- tosca.datatypes.nfv.KvpData
- tosca.datatypes.nfv.ContentOrFileData
- tosca.datatypes.nfv.BootDataVimSpecificProperties
- introduced 3.3.1
- tosca.datatypes.nfv.VnfPackageChangeSelector
- tosca.datatypes.nfv.VnfPackageChangeComponentMapping
- tosca.datatypes.nfv.VnfChangeCurrentPackageOperationConfiguration
- tosca.datatypes.nfv.VnfCreateSnapshotOperationConfiguration
- tosca.datatypes.nfv.VnfRevertToSnapshotOperationConfiguration
...
capabilities:
virtual_compute:
type: tosca.capabilities.nfv.VirtualCompute
occurrences: [ 1, 1 ]
virtual_binding:
type: tosca.capabilities.nfv.VirtualBindable
occurrences: [ 1, UNBOUNDED ]
...
requirements:
- virtual_storage:
capability: tosca.capabilities.nfv.VirtualStorage
relationship: tosca.relationships.nfv.AttachesTo
occurrences: [ 0, UNBOUNDED ]
VduVirtualBlockStorage Data Model
tosca.nodes.nfv.Vdu.VirtualBlockStorage
- No Change since 2.7.1
VduVirtualObjectStorage Data Model
tosca.nodes.nfv.Vdu.VirtualObjectStorage
- No Change since 2.7.1
VduVirtualFileStorage Data Model
tosca.nodes.nfv.Vdu.VirtualFileStorage
- No Change since 2.7.1
VnfVirtualLink Data Model
tosca.nodes.nfv.VnfVirtualLink
- No Change since 2.7.1
VipCp Data Model
...
tosca.nodes.nfv.VipCp:
derived_from: tosca.nodes.nfv.Cp
description: Describes a connection point to allocate one or a set of virtual IP addresses
...
vip_function
...
String
...
1
...
- valid_values: [ high_availability, load_balance ]
...
Describes the algorithm used to obtain the checksum value
...
requirements:
- target:
capability: tosca.capabilities.Node
relationship: tosca.relationships.DependsOn
occurrences: [ 1, UNBOUNDED ]
- virtual_link:
capability: tosca.capabilities.nfv.VirtualLinkable
relationship: tosca.relationships.nfv.VipVirtualLinksTo
occurrences: [1, 1]
VirtualCp Data Model
...
tosca.nodes.nfv.VirtualCp:
derived_from: tosca.nodes.nfv.Cp
description: Describes a virtual connection point allowing the access to a number of VNFC instances (based on their respective VDUs).
...
additionalServiceData
...
list of
tosca.datatypes.nfv.AdditionalServiceData
...
1
...
References the VDU(s) which implement this service
requirements:
- target:
capability: tosca.capabilities.Node
relationship: tosca.relationships.DependsOn
occurrences: [ 1, UNBOUNDED ]
- virtual_link:
capability: tosca.capabilities.nfv.VirtualLinkable
relationship: tosca.relationships.nfv.VirtVirtualLinksTo
...