Versions Compared

Key

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


Analysis content

...

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:

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

B2 issue example:


Fix it to align with the SOL001 spec

C90

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

•Which
  • Which types have to be kept ?
•Which
  • 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

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
  • Which types have to be kept ?
•Which
  • Which types can be replaced by the TOSCA normative types as defined in tosca-simple-profile-yaml or NFV types as defined in SOL001

Options to fix the above issues

Option
1

Description

Option1Fix A and B (including B1 and B2) in Dublin release
Option2

Fix all the issues (A, B, C and D) in Dublin release

Option3

Keep it without any fix, and only correct them when designing the new target internal DM (TIDM):

  • The rules for designing TIDM have to be considered and decided in Dublin release, e.g.,

Issue A and B1 have to be avoid
B2 should align with the SOL001 spec
C should be obsoleted and replaced by TIDM or other on-boarding DM (e.g. SOL001)
D should be obsoleted and replaced by TIDM or other on-boarding DM (e.g. SOL001)
Other rules?

  • Provide guidance and suggestion for the related projects about using which TOSCA parser (SDC TOSCA Parser or NFV Parser).
Option4..........





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

...