Page Comparison

...

1. SDC supported input CSAR structure which is supported for R1.

   1. 3 Directories: /TOSCA-Metadata, /Artifacts, /Definitions

   2. SDC development team to check if the import CSAR structure can be the same as the output CSAR structure (nested directories inside /Artifacts)

   3. SDC is not supporting images in R1
   4. SDC is doing basic package validation and would fail incorrect package structure/content
   5. VNFSDK team asks about SDC TOSCA validation code
2. SDC presented the number of options for VNF sequencing. 
   1. Using the relationships between the nodes - more information The following example (https://www.semanticscholar.org/paper/Combining-Declarative-and-Imperative-Cloud-Applica-Breitenb%C3%BCcher-Binz/61332d7f1763d56e298ce59855aed921a61d1f87)
      Shows how the relationships in the model translated to the instantiation sequencing:
      Image Added
   2. Using the workflow - suggesting to check with SO and VF-C how this is done today
3. Aug-29 Modelling call will have a slot to discuss the leftovers about CSAR package format
4. SDC suggested having a 3-hours call with VF-C team to manually craft one of VoLTE VNFs and the discuss SDC output 
5. VF-C needs to discuss with VoLTE use case team the E2E flow how the design-time output gets to VF-C. Possible options (additional options might exist):
   
   1. Option 1: 
      1. VF-C implements DMaaP API to register on service and resource notification
      2. VF-C implements SDC catalog API to get service and VNFs
   2. Option 2:
      1. VF-C implements only SDC catalog API and based on SO call gets the service/VNFs from SDC

...