Page tree
Skip to end of metadata
Go to start of metadata

This page will compare key aspects of various modeled artifacts, for use cases supported by multiple MANO implementations, including:

  • VNF Package
  • Descriptors (NSD, VNFD/VNFR, VLD/VLR, PNFD, VNFFGD)
  • Model basic features (nodes, attributes, relationships, policies, lifecycle hooks) and approaches to defining/processing those feature-related capabilities

Service/VNF Package

The table below will describe key differences in the way that these projects define/process Service/VNF packages, e.g. package format, contents, metadata.

Service/VNFOpenBatonOpen-OOSM
vIMS   
    
    

 

Descriptors

The table below will describe key differences in the way that these projects define/process Service/VNF descriptors.

DescriptorOpenBatonOpen-OOSM
NSD   
VNFD/VNFR   
VLD/VLR   
PNFD   
VNFFGD   

 

Model Features

The table below will describe key differences in the way that these projects define/process these feature-related capabilities of descriptors.

  • "=" means same as defined in the TOSCA NFV Simple Profile
  • "~=" means somewhat the same
  • "n/s" means not supported (yet, hopefully...)

...artifacts:....VM_image:....type:....file:

 

 

Feature

TOSCA NFV Simple Profile

TackerOpenBatonOpen-OOSM
topology_template:topology_template:=   
.substitution_mappings:.substitution_mappings:    
nodes
.node_templates

.node_templates:

=

   

..VDU:
...type:
...requirements:

..VDU[n]:
...type:
...requirements:
=
=
n/s
   
...capabilities:...capabilities:=   
....nfv_compute

....nfv_compute:

=   
.....properties:.....properties:=   
......num_cpus:......num_cpus:..VDU.properties.num_cpus:   
......mem_size:......mem_size:..VDU.properties.mem_size:   
......disk_size:......disk_size:..VDU.properties.disk_size:   
......mem_page_size:......mem_page_size:......mem_page_size:   

......cpu_allocation:
.......cpu_affinity:
.......thread_allocation:
.......socket_count:
.......core_count:
.......thread_count:

......cpu_allocation:
.......cpu_affinity:
.......thread_allocation:
.......socket_count:
.......core_count:
.......thread_count:
=   

......numa_nodes:
.......node[n]:

......numa_nodes:
.......node[n]:
=
=
   
......numa_node_count:?......numa_node_count:   
...artifacts:
....VM_image:
....type:
....file:

...artifacts:
....VM_image:
....type:
....file:

=
....VNFImage:
=
=
   

lifecycle hooks
...interfaces:
....Standard:
.....create:
......implementation:
.....configure:
......implementation:


...interfaces:
....Standard:
.....create:
......implementation:
.....configure:
......implementation:


n/s
   
  

..VDU.properties:
...image:
...flavor:
...availability_zone:
...mem_size:
...disk_size:
...num_cpus:
...config_drive:
...config:
...mgmt_driver:
...service_type:
...user_data:
...user_data_format:
...key_name:

   
  

...monitoring_policy:
....name:
....parameters
:.....monitoring_delay:
......count:
......interval:
......timeout::
......actions:
......retry:
......port:

   
  

...metadata:
....entry_schema:

   
relationships

 .CP:
..type:
..properties:
...management:
...anti_spoofing_protection:
...type:
...order:
...security_groups:

.CP:
..type: (tosca.nodes.nfv.CP)
..properties:
?
...anti_spoofing_protection:
?
?
?

=
= (tosca.nodes.nfv.CP.Tacker)
=
=
=
=
=
=
   

..requirements:
...- virtualLink:
....node:
...- virtualBinding:
....node:

..requirements:
...- virtualLink:
....node:
...- virtualBinding:
....node:

=
=
=
=
=
   
policies     
profiles     

"profiles" are referenced objects for specific purposes, e.g. SLA

VDU.properties.mem_size:

  • No labels