Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 

Gliffy Diagram

VNF Data Model

macroIdc7393fef-6931-46eb-8f77-1087da9cc235
nameETSI CNF Extensions to SOL001 v3.3.1
pagePin6

Gliffy Diagram
macroIdf879f224-7dcc-483e-aba5-8c6a0db670d9
nameETSI SOL004 with 4.1.1 VNFD and non-MANO artifact
pagePin1

VNF Data Model

  • property "vnfm_info" constraint pattern: "(etsivnfm:v[0-9property "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

IdTypeCardinalityDescription
descriptor_idString #UUID1Identifier for the VNFD
descriptor_versionString1

Identifies the version of the VNFD

providerString1provider of the VNF and of the VNFD
product_nameString1name to identify the VNF product. Invariant for the VNF Product lifetime
software_versionString1Software version of the VNF
product_info_nameString0..1Human readable name of the VNF Product
product_info_descriptionString0..1Human readable name for the VNF product
vnfm_infolist of String1..nIdentifies VNFM(s) compatible with the VNF
localization_languageslist of String0..nInformation 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

String1

Identifier of the Deployment Flavour within the VNFD

flavour_description

String1

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_profilelist of tosca.datatypes.nfv.MciopProfile0..n

Describes additional instantiation data for the MCIOPs used in this deployment

scale_statusmap of tosca.datatypes.nfv.ScaleInfo0..nScale 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.

    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

...






OsContainer VDU  Data Model

Gliffy Diagram
macroId2eaccb5d-5830-48ff-ac07-2f937e784599
namev4.1.1 VDU and OsContainerDesc mapping
pagePin2

VDU OsContainer Data Model


tosca.nodes.nfv.Vdu.osContainer:

    derived_from: tosca.nodes.Root

    description: Describes the resources of a single container within a VDU

IdTypeCardinalityDescription
nameString1Human readable name of the Container
descriptionString1Human readable description of the Container
logical_nodemap of tosca.datatypes.nfv.LogicalNodeData0..n

Describes the logical node requirements

requested_additional_capabilities

map of 

tosca.datatypes.nfv.RequestedAdditionalCapability

0..n

Describes additional capabilities to host this container

compute_requirements

map of String

0..1

requestedCpuResources

integer

0..1

Number of milli-Cpus

CpuResourcesLimit

integer

0..1

Limit (Max) Number of milli-Cpus

requestedMemoryResources

scalar-unit.size

0..1

Amount of Memory requested

MemoryResourcesLimit

scalar-unit.size

0..1

Limit (Max) Memory

virtual_local_storage

list of tosca.datatypes.nfv.VirtualBlockStorageData
requestedEphemeralStorageResourcesscalar-unit.size0..
n
1Amount of Ephemeral Storage Requested

    capabilities:

      ContainerGroupable:

        type: tosca.capabilities.nfv.ContainerGroupable

        occurrences: [ 1, UNBOUNDED ]

    requirements

ephemeralStorageResourcesLimit

scalar-unit.size

0..1

Limit on Ephemeral Storage

    capabilities:

     

- virtual_storage

ContainerGroupable:

       

  capability 

type: tosca.capabilities.nfv.

VirtualStorage

          relationship: tosca.relationships.nfv.AttachesTo

ContainerGroupable

        occurrences: [

 0

1, UNBOUNDED ]

VDU OsContainerGroup Data Model

...

tosca.nodes.nfv.Vdu.osContainerGroup:

    derived_from: tosca.nodes.Root

    description: Describes the aggregate of container(s) of a VDU which is a construct  supporting the description of the deployment and operational behavior of a VNFC; Corresponds to a "Pod" in K8S; Can have multiple constitute containers.

IdTypeCardinalityDescription
nameString1Human readable name of the VDU
descriptionString1Human readable description of the VDU
nfvi_constraintsmap of String0..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; Per Container on IFA011 v4.1.1 but more relevant at the VDU (Pod) Level

#configurable_properties

tosca.datatypes.nfv.VnfcConfigurableProperties

0..1

# 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.OsContainer OsContainerGroup node

boot_data

tosca.datatypes.nfv.BootData

0..1

Contains the information used to customize a container compute resource at boot time. The bootData may contain variable parts that are replaced by deployment specific values before being sent Per Container on IFA011 v4.1.1 but more relevant at the VDU (Pod) Level

    capabilities:

      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 ]

   - container_grouping:

       capability: tosca.capabilities.nfv.ContainerGroupable

       relationship: tosca.relationships.nfv.GroupsTo

       occurrences:  [ 1, UNBOUNDED ]


MciopProfile Data Model

Gliffy Diagram
macroId52d3d86d-0434-4565-9ea9-ca1b16d0c8ff
name4.1.1 MciopProfile
pagePin2

  tosca.datatypes.nfv.MciopProfile:

   

  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.

IdTypeCardinalityConstraintsDescription

mciopId

String1

Identifies the MCIOP in the VNF package.

deploymentOrder

Integer0..1greater_or_equal: 0

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

list of String0..n

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

associatedVdu

list of String0..n

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

...

  tosca.datatypes.nfv.ChecksumData:

     derived_from: tosca.datatypes.Root

     description: Describes information about the result of performing a checksum operation over some arbitrary data 

IdTypeCardinalityConstraintsDescription

algorithm

String

1


Describes the algorithm used to obtain the checksum value

hash

String1

Contains the result of applying the algorithm indicated by the algorithm property to the data to which this ChecksumData refers 


vduCp Data Model

tosca.nodes.nfv.

...

VduCp:

    derived_from:

vnfExtCp Data Model

tosca.nodes.nfv.

...

  • 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

...

Cp

    description: Describes network connectivity between a VNFC instance based on this VDU and an internal VL 

IdTypeCardinalityDescription
bitrate_requirementinteger0..1Bitrate requirement in bit per second on this connection point
virtual_network_interface_requirementslist of tosca.datatypes.nfv.VirtualNetworkInterfaceRequirements0..nSpecifies requirements on a virtual network interface realising the CPs instantiated from this CPD
orderinteger0..1

The order of the NIC on the compute instance (e.g.eth2)

vnic_type

string0..1

Describes the type of the virtual network interface realizing the CPs instantiated from this CPD.

Valid values:  normal, macvtap, direct, baremetal, virtio-forwarder, direct-physical, smart-nic, bridge, ipvlan, loopback, macvlan, ptp, vlan, host-device

    capabilities:

      virtual_binding:

        type: tosca.capabilities.nfv.VirtualBindable

        occurrences: [ 1, UNBOUNDED ]

    requirements:

        - virtual_link:

             capability: tosca.capabilities.nfv.VirtualLinkable
             relationship: tosca.relationships.nfv.VirtualLinksTo
             occurrences: [0, 1]
     - virtual_binding:
           capability: tosca.capabilities.nfv.VirtualBindable
           relationship: tosca.relationships.nfv.VirtualBindsTo
           node: tosca.nodes.nfv.Vdu.Compute
           occurrences: [0, 1]
      - container_binding:
           capability: tosca.capabilities.nfv.VirtualBindable
           relationship: tosca.relationships.nfv.ContainerBindsTo
           node: tosca.nodes.nfv.Vdu.OsContainerGroup
          occurrences: [0, 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

  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 

IdTypeCardinalityConstraintsDescription

name

String

1


Human readable name of the VDU 

description

String1

Human readable description of the VDU 

boot_order

boolean1

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 String0..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 

IdTypeCardinalityConstraintsDescription

vip_function

String

1

- valid_values: [ high_availability, load_balance ]

Describes the algorithm used to obtain the checksum value

    requirements:

      - target

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

  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 

IdTypeCardinalityConstraintsDescription

name

String

1

Human readable name of the VDU 

description

String1

Human readable description of the VDU 

boot_order

boolean1

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 String0..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

Node

          relationship: tosca.relationships.

nfv.AttachesTo

DependsOn

          occurrences: [

0

1, 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

...

      - virtual_link:

          capability: tosca.capabilities.nfv.VirtualLinkable

          relationship: tosca.relationships.nfv.VipVirtualLinksTo

          occurrences: [1, 1]


#VirtualCp Data Model

Gliffy Diagram
macroId7382e3d4-b2aa-40fe-8653-3420b8c9d980
namev4.1.1 VirtualCp
pagePin1

...

  tosca.nodes.nfv.VipCpVirtualCp:

    derived_from: tosca.nodes.nfv.Cp

    description: Describes a virtual connection point allowing the access to allocate one or a set of virtual IP addresses number of VNFC instances (based on their respective VDUs).

IdTypeCardinalityConstraintsDescription

additionalServiceData

list of 

tosca.datatypes.nfv.AdditionalServiceData

1


References the VDU(s) which implement this service

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.VipVirtualLinksToVirtVirtualLinksTo

          occurrences: [1, 1]

...


Data

...

  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).

...

types. (Input from Michael Morris)

  • Will refine the following...
Changed

The following data types already in ONAP have been changed from 2.5.1:

...

additionalServiceData

...

  • tosca.datatypes.nfv.

...

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]

  • 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

Data types. (Input from Michael Morris)

  • Will refine the following...
Changed

...

  • tosca.datatypes.nfv.VirtualMemory:
    • property "numa_enabled" default value changed from false to true
    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.VnfcConfigurableProperties:
    • property "additional_vnfc_configurable_properties" commented out
  • tosca.datatypes.nfv.VnfcAdditionalConfigurablePropertiesL2ProtocolData:
    • property "description" removed
    tosca.datatypes.nfv.VduProfile:
    • 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:
      • "watchdog", "vmBootUpTimeOut"physical_network" with type String and required false
  • tosca.datatypes.nfv.L2ProtocolDataVnfLcmOperationsConfiguration:
    • 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"
    • new properties added in ETSI 3.3.1:
      • change_current_package: optional, type: tosca.datatypes.nfv.VnfChangeCurrentPackageOperationConfiguration
      • create_snapshot: optional, type: tosca.datatypes.nfv.
    VnfLcmOperationsConfiguration:
      • VnfCreateSnapshotOperationConfiguration
      • revert_to_snapshot: optional, type: tosca.datatypes.nfv.VnfRevertToSnapshotOperationConfiguration
    • Add the above properties to ONAP dataTypes.yml
       
    • new properties added:change_current_package, create_snapshot, revert_to_snapshot
  • 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


  •  toscatosca.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, vnfm_oauth_server_info, vnf: optional, type: tosca.datatypes.nfv.OauthServerInfo
      • vnf_oauth_server_info: optional, type: tosca.datatypes.nfv.OauthServerInfo
    • existing property commented out: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
    • existing property removed:
      • description
      • : 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.VnfInfoModifiableAttributesVnfInfoModifiableAttributesExtensions:
    • existing properties commented out: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.1extensions, metadata


  • tosca.datatypes.nfv.VnfInfoModifiableAttributesExtensionsVnfInfoModifiableAttributesMetadata:
    • existing property removed: need to remove the following property from ONAP dataTypes.yml
      • description
  • tosca.datatypes.nfv.VnfInfoModifiableAttributesMetadata:
    • existing property removed:
      • 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
      • provider
    • property "checksum" changed type from string to tosca.datatypes.nfv.ChecksumDatafrom 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_diskram" new constraint added "greater_or_equal: 0 B" since 2.7.1; change ONAP dataType.yml for this



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


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


  • tosca.datatypes.nfv.VirtualObjectStorageDataVirtualFileStorageData:
    • 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.VirtualFileStorageDataVirtualLinkBitrateLevel:
    • 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.1property "size_of_storage" new constraint added "greater_or_equal: 0 B"


  • 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 since 2.7.1; add the new valid_values added: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:

...