Page Comparison

...

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

...

VDU OsContainer Data Model

...

• tosca.nodes.nfv.VduCP
• 4.2.1 added trunk_binding capability
• 4.2.1 removed the container_binding requirement from 4.1.1 based model
• 4.2.1 removed the node Vdu.Compute constraint from the virtual_binding requirement so that VduCp can also reference  Vdu.OsContainerDeployableUnit

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

...