Versions Compared

Old Version 19

changes.mady.by.user Yan Yang

Saved on

compared with

New Version 20

changes.mady.by.user Yan Yang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Analysis content

...

Analysis Statistics and Suggestion


Class Type Number which belongs to this classThe Issue ExampleSuggestion
A3
Code Block
languageyml
titleSDC
collapsetrue
org.openecomp.annotations.Source:
    description: Indicates the origin source of an input
    properties:
        source_type:
          type: string
        vf_module_label:
          type: list
          description: List of VF Modules this input was originated from
          entry_schema:
            type: string
        param_name:
            type: string
            description: Source parameter name

Missing derived_from in the definition

Fix it to align with the correct TOSCA grammar


B

58

B1 14

B1 issue example:

Image Modified

B1 Fix it to align with the TOSCA spec
B2: 44

B2 issue example:

Image Modified


Fix it to align with the SOL001 spec

C90

Image Modified

Grammar is complied with TOSCA spec, but defined by SDC only, those are not included in TOSCA spec or SOL001 spec.

•Which types have to be kept ?
•Which types can be replaced by the TOSCA normative types as defined in tosca-simple-profile-yaml or NFV types as defined in SOL001, or the types as defined in the target internal DM (ONAP Target Internal DM (TIDM), Base Proposal)

D17

Image Modified

Grammar is complied with TOSCA spec, but defined and used by SDC for a specific use case or vendor, those are not included in TOSCA spec or SOL001 spec.

•Which types have to be kept ?
•Which types can be replaced by the TOSCA normative types as defined in tosca-simple-profile-yaml or NFV types as defined in SOL001






R3 CSAR which exported by SDC in CCVPN use case and CPE use case 

...