Analysis content
...
- A : Not comply with tosca grammar
This classification is used to record types that don't comply with the basic tosca syntax specification - B1: Not comply with existing TOSCA-simple-YAML-1.2
- B2: Not comply with existing SOL001-v2.5.1
Type definitions quite like the types which defined in specification, but still have some difference, such as base type difference, property difference, etc - C: SDC private extension
This classification is used to record SDC private extension - D: Use Case private extension
This classification is used to record the extension types which used to support specific use case
...
Analysis Statistics and Suggestion
Class | Type Number which belongs to this class | The Issue Example | Suggestion | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
A | 3 |
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 |
B
58B2: 44 | B2 issue example: | Fix it to align with the SOL001 spec | |
C | 90 | 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 ? |
D | 17 | 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 ? |
R3 CSAR which exported by SDC in CCVPN use case and CPE use case
...