Page Comparison

Agenda:

The agenda will be:

1. 1. Discussion of the CSAR structure supported for R1
   2. Discussion on the sequence design in SDC

discussion points:

1. David Presented the SDC supported input CSAR structure which will be is supported for R1. 

2. in case the CSAR structure is incorrect the onboarding will fail.
3. SDC will use the modeling call to discuss the finalization of the CSAR package and its contents.
4. a meeting will be on Friday to try to model a vf using SDC based on one of the VF provided by ZTE for the VOLTE use case.
5. VFC sdc integration, the integration is still not finalized.

Action items:

1. can the SDC support nested artifacts in the CSAR? (owner TAL

   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 - 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

Action items (to be completed by Tuesday Aug-29):

1. Can the SDC support nested artifacts in imported CSAR?  (owner Tal H.)
2. can the CSAR structure be aligned according to the request to have the service template yaml and mf in the root level (owner meopengMeopeng)
3. provide vnf sdk with a location/explanation to the validations done on the CSAR on onboarding to allow them to validate the csar when they receive it (owner Tal)
4. VFC need to provide the artifacts that are needed by them in the csar.
5. SDC need to provide a csar structure documintatio.
6. SDC need to reply to the enquiries by ZTE regarding the parser issue identified.Provide VNFSDK team with information and code location about the current SDC CSAR validations (owner Tal H.)
7. VF-C team to provide the list of artifacts that would be included in the onboarded VNF and used by VF-C (owner Meoperg)
8. SDC team to make sure WiKi page is updated with the latest CSAR structure documentation (owner Michael L.)
9. SDC development team to response VF-C questions about TOSCA parser (owner Michael L.)

SDC Supported Import CSAR Structure in R1:

Image Added

root

/Artifacts - includes all artifacts.

No images
No nesting directories

/Definitions – includes all TOSCA yaml files

Need to include SDC global definition file(s).

MainServiceTemplate.yaml 
MainServiceTemplate.mf 

Metting recording:

...