Page Comparison

one one

Analysis Result Class

SDC Type

Relationship to [TOSCA-YAML-1.2] [SOL001] [TOSCA-NFV]

issue

Note

n/a

tosca.capabilities.Root

tosca.capabilities.Attachment

tosca.capabilities.Node

tosca.capabilities.Endpoint

tosca.capabilities.Endpoint.Database

tosca.capabilities.OperatingSystem

tosca.capabilities.Scalable

tosca.capabilities.network.Bindable

same as [TOSCA-YAML-1.2]

n/a

B1

tosca.capabilities.Container

quite like the tosca.capabilities.Compute defined [TOSCA-YAML-1.2]

Compared to tosca.capabilities.Compute defined [TOSCA-YAML-1.2], 'name' property is not defined in SDC's tosca.capabilities.Container type.

C: SDC private extension

org.openecomp.capabilities.PortMirroring

org.openecomp.capabilities.AllottedResource

org.openecomp.capabilities.Metric

org.openecomp.capabilities.metric.Ceilometer

org.openecomp.capabilities.metric.SnmpPolling

org.openecomp.capabilities.metric.SnmpTrap

org.openecomp.capabilities.Forwarder

org.openecomp.capabilities.VLANAssignment

org.openecomp.capabilities.RoutingConfiguration

org.openecomp.capabilities.FabricConfiguration

SDC private

D: Use Case private extension

tosca.capabilities.DatabaseEndpoint

same as the tosca.capabilities.Endpoint.Database defined in [TOSCA-YAML-1.2]

A : Not comply with tosca grammar

tosca.capabilities.Endpoint.Public

Code Block

language	yml
collapse	true

tosca.capabilities.Endpoint.Public:
  derived_from: tosca.capabilities.Endpoint
  properties:
    network_name: PUBLIC
    ... ...

tosca.capabilities.Endpoint.Admin

Code Block

language	yml
collapse	true

tosca.capabilities.Endpoint.Admin:
  derived_from: tosca.capabilities.Endpoint
  properties:
    secure: true

same as [TOSCA-YAML-1.2], but definitions doesn't follow TOSCA grammar

SDC's definitions doesn't follow TOSCA grammar, it should be a SDC bug.

The grammar correct definition should be as the following:

Code Block

language	yml
title	tosca.capabilities.Endpoint.Public
collapse	true

tosca.capabilities.Endpoint.Public:
  derived_from: tosca.capabilities.Endpoint
  properties:
    network_name:
      type: string
      default: PUBLIC
      constraints:
      - equal: PUBLIC
... ...

Code Block

language	yml
title	tosca.capabilities.Endpoint.Admin
collapse	true

tosca.capabilities.Endpoint.Admin:
  derived_from: tosca.capabilities.Endpoint
  properties:
    secure:
      type: boolean
      default: true
      constraints:
        - equal: true

This is NOT TOSCA compliant. Expected reported error by parser.

B1

tosca.capabilities.Container.Docker

quite like the tosca.capabilities.Container.Docker
defined [TOSCA-YAML-1.2]

Compared to [TOSCA-YAML-1.2], the following properties are missing in SDC's definition:

Code Block

language	yml
title	missing properties:
collapse	true

... ...
  properties:
    host_id: 
      type: string
      required: false
    volume_id: 
      type: string
      required: false

B1

tosca.capabilities.network.Linkable

Code Block

language	yml
collapse	true

tosca.capabilities.network.Linkable:
  derived_from: tosca.capabilities.Root

Different from tosca.capabilities.network.Linkable in [TOSCA-YAML-1.2] due to different base type:

Code Block

language	yml
collapse	true

tosca.capabilities.network.Linkable:
  derived_from: tosca.capabilities.Node

Maybe a SDC bug???

n/a

tosca.capabilities.nfv.VirtualStorage

tosca.capabilities.nfv.VirtualLinkable

same as [SOL001]

B2

tosca.capabilities.nfv.VirtualCompute

Code Block

language	yml
title	SDC's
collapse	true

tosca.capabilities.nfv.VirtualCompute:
  derived_from: tosca.capabilities.Root
  properties:
    logical_node:
      type: tosca.datatypes.nfv.LogicalNodeData
      required: false
    compute_requirements:
      type: map
      entry_schema:
        type: string
      required: false
    requested_additional_capabilities:
      type: map
      entry_schema:
         type: tosca.datatypes.nfv.RequestedAdditionalCapability
      required: false
    virtual_memory:
      type: tosca.datatypes.nfv.VirtualMemory
      required: true
    virtual_cpu:
      type: tosca.datatypes.nfv.VirtualCpu
      required: true

Different with [SOL001]

Code Block

language	yml
title	SOL001
collapse	true

tosca.capabilities.nfv.VirtualCompute: 
    derived_from: tosca.capabilities.Node
    description: Describes the capabilities related to virtual compute resources 
    properties:
      logical_node:
        type: map
        description: Describes the Logical Node requirements 
        required: false
        entry_schema:
           type: tosca.datatypes.nfv.LogicalNodeData
      requested_additional_capabilities:
        type: map
        description: Describes additional capability for a particular VDU 
        required: false
        entry_schema:
           type: tosca.datatypes.nfv.RequestedAdditionalCapability
      compute_requirements:
        type: map
        required: false 
        entry_schema:
           type: string
      virtual_memory:
        type: tosca.datatypes.nfv.VirtualMemory
        description: Describes virtual memory of the virtualized compute 
        required: true
      virtual_cpu:
        type: tosca.datatypes.nfv.VirtualCpu
        description: Describes virtual CPU(s) of the virtualized compute 
        required: true
      virtual_local_storage:
        type: list
        description: A list of virtual system disks created and destroyed as part of the VM lifecycle 
        required: false
        entry_schema:
          type: tosca.datatypes.nfv.VirtualBlockStorageData
          description: virtual system disk definition

[SOL001] made following changes compared to SDC's

:

Base type changed from tosca.capabilities.Root to tosca.capabilities.Node.
Property 'logical_node' changed from a single data type to be a map of data type 'tosca.datatypes.nfv.LogicalNodeData'.
New property 'virtual_local_storage' is added as a list of date type 'tosca.datatypes.nfv.VirtualBlockStorageData'.

B2

tosca.capabilities.nfv.VirtualBindable

Different with [SOL001]

[SOL001] made following changes compared to SDC's

: