Page Comparison

Agenda:

The agenda will be:

1. 1. Discussion of the presentation regarding CSAR structure supported for R1Discussion on the sequence design in SDCby SDC.
   2. discussion regarding the SDC support for work flow files.
   3. general Q&A

discussion points:

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 - 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 Removed
   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 Meopeng)
3. Provide VNFSDK team with information and code location about the current SDC CSAR validations (owner Tal H.)
4. VF-C team to provide the list of artifacts that would be included in the onboarded VNF and used by VF-C (owner Meoperg)
5. SDC team to make sure WiKi page is updated with the latest CSAR structure documentation (owner Michael L.)
6. SDC development team to response VF-C questions about TOSCA parser (owner Michael L.)

SDC Supported Import CSAR Structure in R1:

Image Removed

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:

meeting Chat:

...

1. provided documentation regarding the CSAR structure used in SDC:Csar Structure

2. SDC requested that CSARS according to the defined structure be provided for testing.
3. a concern was raised regarding the commitment of the tosca vendors to support the requested structure.
4. from a discussion it looks like nokia did not yet approve the requirement.
5. Tal from amdocs agreed to provide an example to the expected CSAR so that the other CSAR will be aligned accordingly.
6. based on this example the MF file can be created for the rest of the CSARS.
7. SDC provide information regarding the the support that can be achieved for workflow's in R1.
   1. SDC suggested a definition of a new artifact type for the workflows.
   2. the artifact type coupled with the csar will allow SDC to ingest the workflows from the vendore csar into SDC in case the workflows are coming from the vendor.
   3. sdc provides a set of rest API's to upload the workflows to VF instances and to the service, the update will be done using the defined type for the work flows.
   4. all uploaded workflows will be distributed as part of the service CSAR.
   5. sdc suggested review rest API's exposed in order to provide an alternative the the workflow using the parser.
8. SDC continued the discussion regarding the integration with VFC, vfc provided a solution where on orchestration  information regarding the service is passed to VFC by so and using that information the CSAR is retrieved from SDC.
9. sdc provided a review of the issues 

Action items:

•  
•  Type your task here, using "@" to assign to a user and "//" to select a due date
•  Type your task here, using "@" to assign to a user and "//" to select a due date
•  Type your task here, using "@" to assign to a user and "//" to select a due date
•  

Metting recording:

meeting Chat: