Page History

...

The following describes Data Model based on the ETSI v3.3.1 SOL001 VNFD plus CNF enhancements, which came from 4.1.1.

• in Honolulu, the VDU and Container relation is 1:1. We plan to enhance it in the future.
• 2.7.x for backward compatibility during SDC onboarding + 3.3.1 with CNF enhancements
  • If the type is changed, separate properties for 2.7.x and 3.3.1 will be used
• As the ETSI SOL001 WG produces a stable draft/release of SOL001 4.X specification , we expect to update the data model to align with that specifcation.

ETSI 3.3.1 SOL001 Data Model with minimum CNF Properties from 4.1.1 

VNF Data Model

...

...

...

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

OsContainer VDU  Data Model

VDU OsContainer Data Model

...

 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

...

Identifies the version of the VNFD

...

lcm_operations_configuration

...

tosca.datatypes.nfv.VnfLcmOperationsConfiguration

...

Describes the configuration parameters for the VNF LCM operations

...

monitoring_parameters

...

tosca.datatypes.nfv.VnfMonitoringParameter

...

Describes monitoring parameters applicable to the VNF.

...

flavour_id

...

Identifier of the Deployment Flavour within the VNFD

...

flavour_description

...

Human readable description of the DF

...

tosca.datatypes.nfv.VnfProfile

...

Describes a profile for instantiating VNFs of a particular NS DF according to a specific VNFD and VNF DF

...

Describes additional instantiation data for the MCIOPs used in this deployment

...

    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

VDU OsContainer Data Model

VDU OsContainerGroup Data Model

MciopProfile Data Model

...

  tosca.datatypes.nfv.MciopProfile:

    derived_from: tosca.datatypes.Root

    description: describes a profile for instantiating VNFs of a particular NS DF according to a specific VNFD and VNF DF.

...

mciopId

...

Identifies the MCIOP in the VNF package.

...

deploymentOrder

...

Indicates the order in which this MCIOP shall be deployed in relation to other MCIOPs.  A lower value specifies an earlier deployment.

null is allowed

...

#     affinityOrAntiAffinityGroupId

...

References the affinity or anti-affinity groups(s) the MCIOP belongs to.

...

associatedVdu

...

List of VDUs which are associated to this MCIOP and which are deployed using this MCIOP

VnfInstantiateOperationConfiguration Data Model

...

  tosca.datatypes.nfv.VnfInstantiateOperationConfiguration:

   derived_from: tosca.datatypes.Root

   description: represents information that affect the invocation of the InstantiateVnf operation.

...

VnfMonitoringParameter Data Model

...

tosca.datatypes.nfv.VnfMonitoringParameter:
    derived_from: tosca.datatypes.Root
    description: Represents information on virtualised resource related performance metrics applicable to the VNF.

...

name

...

String

...

1

...

Human readable name of the monitoring parameter

...

performance_metric

...

String

...

1

...

- valid_values: [ v_cpu_usage_mean_vnf, v_cpu_usage_peak_vnf,
v_memory_usage_mean_vnf, v_memory_usage_peak_vnf,
v_disk_usage_mean_vnf, v_disk_usage_peak_vnf,
byte_incoming_vnf_ext_cp, byte_outgoing_vnf_ext_cp,
packet_incoming_vnf_ext_cp, packet_outgoing_vnf_ext_cp

...

Identifies the performance metric, according to ETSI GS NFV-IFA 027.

...

collection_period

...

scalar-unit.time

...

0..1

...

- greater_than: 0 s

...

Describes the recommended periodicity at which to collect the performance information.

MciopProfile Data Model

VnfProfile Data Model

SwImageData Data Model

...

VnfInstantiateOperationConfiguration Data Model

VnfMonitoringParameter Data Model

VnfProfile Data Model

BootData Data Model

...

tosca.datatypes.nfv.BootData:

    derived_from: tosca.datatypes.Root

    description: describes the information used to customize a virtualised or containerized compute resource at boot time.

...

SwImageData Data Model

• Change: checksum propeorty is used to be string in 2.6.x. Now, it is tosca.datatypes.nfv.ChecksumData. During SDC onboarding, the old type checksum data will be stored in a new property in SDC (e.g., checksum261).

...

vim_specific_properties

...

tosca.datatypes.nfv.BootDataVimSpecificProperties

...

0..1

...

Properties used for selecting VIM or CISM specific capabilities when setting the boot data.

...

kvp_data

...

tosca.datatypes.nfv.KvpData

...

0..1

...

A set of key-value pairs for configuring a virtual or container compute resource.

...

content_or_file_data

...

tosca.datatypes.nfv.ContentOrFileData

...

0..1

...

A string content or a file for configuring a virtual or container compute resource. 

BootDataVimSpecificProperties Data Model

KvpData Data Model

ContentOrFileData Data Model

BootData Data Model

ChecksumData Data Model

vduCp Data Model

• tosca.nodes.nfv.VduCP
• No Change since 2.7.1

vnfExtCp Data Model

• tosca.nodes.nfv.VnfExtCP
• No Change since 2.7.1
• There are some changes from 2.6.1 to 2.7.1
  • property "vnic_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
• 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
• 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
• The configurable_properties is still out of scope in Honolulu

BootDataVimSpecificProperties Data Model

KvpData Data Model

ContentOrFileData Data Model

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

ChecksumData Data Model

vduCp Data Model

...

vnfExtCp Data Model

...

• tosca.nodes.nfv

...

    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

          occurrences: [1, 1]

• .VnfExtCP
• No Change since 2.7.1
• There are some changes from 2.6.1 to 2.7.1
  • property "vnic_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
• 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
• 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
• The configurable_properties is still out of scope in Honolulu

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

#VirtualCp Data Model

Data types. (Input from Michael Morris)

• Will refine the following...

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.  // In ONAP, the default is still false
  • in ETSI, there is no Change since 2.5.1/2.7.1
• tosca.datatypes.nfv.VnfcConfigurableProperties:
  • property "additional_vnfc_configurable_properties" commented out in ONAP dataTypes.yml
  • In ETSI, there is no other change since 2.5.1/2.7.1
• tosca.datatypes.nfv.VnfcAdditionalConfigurableProperties:
  • property "description" removed
  • In ETSI, there is no other change since 2.5.1/2.7.1
• tosca.datatypes.nfv.VduProfile:
  • version in ONAP contains extra properties not in ETSI:
    • "watchdog", "vmBootUpTimeOut"
    • Keep the extra properties in ONAP; no change in ONAP
  • In ETSI, there is no other change since 2.5.1/2.7.1
• tosca.datatypes.nfv.L2ProtocolData:
  • property "vlan_transparent" now mandatory; change required to Yes; in ONAP change the required to true; default to true;
  • property "segmentation_id" is introduced in 2.7.1. Now it is in both ETSI and ONAP, but ETSI defined it as a string, but ONAP defined it as integer; If possible, change it to String to conform to ETSI
  • version in ONAP contains extra properties not in ETSI:
    • "physical_network" with type String and required false
• tosca.datatypes.nfv.VnfLcmOperationsConfiguration:
  • new properties added in ETSI 3.3.1:
    • change_current_package: optional, type: tosca.datatypes.nfv.VnfChangeCurrentPackageOperationConfiguration
    • create_snapshot: optional, type: tosca.datatypes.nfv.VnfCreateSnapshotOperationConfiguration
    • revert_to_snapshot: optional, type: tosca.datatypes.nfv.VnfRevertToSnapshotOperationConfiguration
  • Add the above properties to ONAP dataTypes.yml
     
• tosca.datatypes.nfv.VnfInstantiateOperationConfiguration:
  • property "description" removed"; need to remove this description property from ONAP dataType.yml
  • there is no change in ETSI since 2.5.1/2.7.1

•  tosca.datatypes.nfv.VnfScaleOperationConfiguration
  • property "scaling_by_more_than_one_step_supported" now mandatory for 3.3.1; change its "required" to true and "default" to true.

• tosca.datatypes.nfv.VnfConfigurableProperties:
  • new optional properties added since 2.7.1
    • vnfm_interface_info: optional, type: tosca.datatypes.nfv.VnfmInterfaceInfo
    • vnfm_oauth_server_info: optional, type: tosca.datatypes.nfv.OauthServerInfo
    • vnf_oauth_server_info: optional, type: tosca.datatypes.nfv.OauthServerInfo
  • existing property commented out:
    • additional_configurable_property
  • In ONAP dataType.yml, change the property "additional_configurable_properties" to "additional_configurable_property" 

• tosca.datatypes.nfv.VnfAdditionalConfigurableProperties:
  • new required property added since 2.7.1
    • is_writable_anytime: required true, type: boolean
  • existing property removed: (remove it from ONAP dataType.yml)
    • description

• tosca.datatypes.nfv.VnfInfoModifiableAttributes:
  • existing properties commented out:
    • extensions, metadata
  • No change since 2.5.1/2.7.1

• tosca.datatypes.nfv.VnfInfoModifiableAttributesExtensions:
  • existing property removed: need to remove the following property from ONAP dataTypes.yml
    • description
  • In ETSI, there is no change since 2.5.1/2.7.1

• tosca.datatypes.nfv.VnfInfoModifiableAttributesMetadata:
  • existing property removed: need to remove the following property from ONAP dataTypes.yml
    • description
  • In ETSI, there is no change since 2.5.1/2.7.1

• tosca.datatypes.nfv.SwImageData:
  • new optional property added since 2.7.1; add the property to ONAP dataType.yml
    • provider: optional, type: string

Data types. (Input from Michael Morris)

• Will refine the following...

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"
• 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
• 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
• tosca.datatypes.nfv.VnfAdditionalConfigurableProperties:
  • new required property added:
    • is_writable_anytime
  • existing property removed:
    • description
• tosca.datatypes.nfv.VnfInfoModifiableAttributes:
  • existing properties commented out:
    • extensions, metadata
• tosca.datatypes.nfv.VnfInfoModifiableAttributesExtensions:
  • existing property removed:
    • description
• tosca.datatypes.nfv.VnfInfoModifiableAttributesMetadata:
  • existing property removed:
    • description
• tosca.datatypes.nfv.SwImageData:
  • new optional property added:
    • provider
  • property "checksum" changed type from string to tosca.datatypes.nfv.ChecksumData since 2.7.1; change ONAP dataType.yml for this.
  • property "min_disk" new constraint added "greater_or_equal: 0 B" since 2.7.1; change ONAP dataType.yml for this
  • property "min_ram" new constraint added "greater_or_equal: 0 B" since 2.7.1; change ONAP dataType.yml for this

• tosca.datatypes.nfv.VirtualBlockStorageData:
  • property "size_of_storage" new constraint added "greater_or_equal: 0 B" since 2.7.1; change ONAP dataType.yml for this
  • property "rdma_enabled" now required" now required; change ONAP dataType.yml for this

• tosca.datatypes.nfv.VirtualObjectStorageData:
  • property "max_size_of_storage" new constraint added "greater_or_equal: 0 B" since 2.7.1; change ONAP dataType.yml for this

• tosca.datatypes.nfv.VirtualFileStorageData:
  • property "size_of_storage" new constraint added "greater_or_equal: 0 B"_or_equal: 0 B" since 2.7.1; change ONAP dataType.yml for this

• tosca.datatypes.nfv.VirtualLinkBitrateLevel:
  • existing property removed: need to remove this property from ONAP dataType.yml
    • description
  • In ETSI, there is no change since 2.5.1/2.7.1

• tosca.datatypes.nfv.VirtualLinkBitrateLevelVnfOperationAdditionalParameters:
  • existing property removed: need to remove this property from ONAP dataType.yml
    • description
  • In ETSI, there is no change since 2.5.1/2.7.1

• tosca.datatypes.nfv.VnfOperationAdditionalParametersVnfChangeFlavourOperationConfiguration:
  • existing property removed:
    • description
     need to remove this property from ONAP dataType.yml
    • description
  • In ETSI, there is no change since 2.5.1/2.7.1

• tosca.datatypes.nfv.VnfChangeFlavourOperationConfigurationVnfChangeExtConnectivityOperationConfiguration:
  • existing property removed: need to remove this property from ONAP dataType.yml
    • description
  • In ETSI, there is no change since 2.5.1/2.7.1

• tosca.datatypes.nfv.VnfChangeExtConnectivityOperationConfiguration:
  • existing property removed:
    • description
• tosca.datatypes.nfv.VnfcMonitoringParameter
  • property "performance_metric" new valid_values added :since 2.7.1; add the new valid_values to ONAP dataType.yml
    • 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

...

• tosca.datatypes.nfv.VirtualLinkMonitoringParameter:
  • property "performance_metric" valid_values added:valid_values added since 2.7.1; add the new valid_values to ONAP dataType.yml
    • byte_incoming, byte_outgoing, packet_incoming, packet_outgoing
  • property "performance_metric" valid_values removed :since 2.7.1; remove the valid_values from ONAP dataType.yml
    • packet_outgoing_virtual_link, packet_incoming_virtual_link

...

• tosca.datatypes.nfv.VnfProfile
  • new optional property "service_availability_level" since 2.7.1; optional, type: tosca.datatypes.nfv.ServiceAvailability; add the property to ONAP dataType.yml

• tosca.datatypes.nfv.L3AddressData
  • version in SDC contains extra property not defined in ETSI: keep the extra property in ONAP dataType.yml
    • fixed_ip_address
  • In ETSI, there is no change since 2.5.1/2.7.1

Unchanged

 The following data types are included in SDC but have no changes:

...