Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »


Types that doesn't comply with the Tosca or ESTI NFV SOL001 or Tosca-nfv syntax

Specification reference:

TOSCA Simple Profile YAML 1.2 Referecne:  http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.2/TOSCA-Simple-Profile-YAML-v1.2.html  [TOSCA-YAML-1.2]

ESTI NFV-SOL 001 V2.5.1 Reference: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/001/02.05.01_60/gs_NFV-SOL001v020501p.pdf  [SOL001]

                                                           https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/001/02.05.01_60/gs_NFV-SOL001v020501p0.zip (YAML definitions)

TOSCA Simple Profile YAML NFV 1.0 Referecne  http://docs.oasis-open.org/tosca/tosca-nfv/v1.0/tosca-nfv-v1.0.html [TOSCA-NFV]  (According to Former user (Deleted)TOSCA-NFV's conent has already been incorporated by the early version of  [SOL001], and no longer being updated).


SDC TypeRelationship to [TOSCA-YAML-1.2] [SOL001] [TOSCA-NFV]issueNote
org.openecomp.annotations.SourceSDC privateThis is SDC's own private extension 'annotation_type' to TOSCA.Parser SHOULD ignore this unknown 'annotation_type'.

tosca.artifacts.Root

tosca.artifacts.Deployment

tosca.artifacts.Deployment.Image

tosca.artifacts.Deployment.Image.VM

tosca.artifacts.Implementation

tosca.artifacts.Implementation.Bash

tosca.artifacts.Implementation.Python

tosca.artifacts.File

same as [TOSCA-YAML-1.2]n/a
tosca.artifacts.nfv.SwImagesame as [SOL001]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
tosca.capabilities.Containerquite 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.

org.openecomp.capabilities.PortMirroring

org.openecomp.capabilities.AllottedResource

org.openecomp.capabilities.Metric

SDC private

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

tosca.capabilities.Endpoint.Public

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

tosca.capabilities.Endpoint.Admin

tosca.capabilities.Endpoint.Admin:
  derived_from: tosca.capabilities.Endpoint
  properties:
    secure: true
same as [TOSCA-YAML-1.2]

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

The grammar correct definition should be as the following:

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

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

tosca.capabilities.Container.Dockerquite 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:

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

tosca.capabilities.network.Linkable








R3 CSAR 

vCPE：

CCVPN:



  • No labels