Page History

...

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

VDU

...

OsContainerDeployableUnit Data Model

Mciop Data Model

VnfInstantiateOperationConfiguration Data Model

VnfInstantiateOperationConfiguration Data Model

...

VnfProfile Data Model

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

...

vduCp Data Model

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

vnfExtCp Data Model

• 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
  • 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

  ...

  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 ]
  (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:       -

  virtual_storage

  target:           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

  • New to SDC

  - virtual_link:           capability: tosca.capabilities.nfv.VirtualLinkable           relationship: tosca.relationships.nfv.VipVirtualLinksTo           occurrences: [1, 1]

  
  

  VirtualCp Data Model

  Gliffy Diagram
  macroId a3b53088-8b52-4dbe-8925-e26a5ae6eba4 name v4.2.1 VirtualCp pagePin 1

  
  

  tosca.datatypes.nfv.ServicePortData:

    tosca.nodes.nfv.VipCp:

     

  derived_from: tosca.

  nodes

  datatypes.

  nfv.Cp

  Root

    description: Describes a connection point to allocate one or a set of virtual IP addresses 

  description: describes the service identifying port properties exposed by the VirtualCp
  Id	Type	Cardinality

  ConstraintsDescriptionvip_function

  	Constraints	Description
  name	String	1		The name of this port exposed by the VirtualCp.
  protocol	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

  ...

  TCP, UDP, SCTP ]	The L4 protocol for this port exposed by the VirtualCp.
  port	Integer	1		The L4 port number exposed by the VirtualCp.
  PortConfigurable	Boolean	1		Specifies whether the port attribute value is allowed to be configurable.

  
  

  tosca.datatypes.nfv.AdditionaServiceData:      derived_from: tosca.datatypes.Root      description: describes the additional service data of the VirtualCp used to expose properties of the VirtualCp
  Id	Type	Cardinality	Constraints	Description
  portData	List of tosca.datatypes.nfv.ServicePortData	1		Service port numbers exposed by the VirtualCp.
  serviceData	String	0..1		Service matching information exposed by the VirtualCp.

  ...

  
  

  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 toscaof 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.VirtVirtualLinksToVirtualLinksTo           occurrences: [10, 1]

  
  

  Data types. (Input from Michael Morris)

  ...