Page Comparison

Agenda:

The agenda will be:

1. 1. presentation regarding CSAR structure by SDC.
   2. discussion regarding the SDC support for work flow workflow files.
   3. general Q&A

discussion points:

1. SDC 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 Tosca vendors to support the requested structure.
4. from a discussion it discussion, it looks like nokia did Nokia did not yet approve the requirement.
5. Tal from amdocs 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 workflows in R1.
   1. SDC suggested a definition of a new artifact type for the workflows.
   2. the artifact type coupled with the csar CSAR will allow SDC to ingest the workflows from the vendore csar vendor CSAR into SDC in case the workflows are coming from the vendor.
   3. sdc 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 flowsworkflows.
   4. all uploaded workflows will be distributed as part of the service CSAR.
   5. sdc SDC suggested review rest API's exposed in order to provide an alternative the the t e workflow using the parser.
   6. workflow design team clarified that for R1 they will not be creating an API integration with SDC and the workflow attachment process will be manual.
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 the issues identified by parcing the SDC CSAR using the open stack parser,
   with the inpout provided by ZTE the issues were categerized into errors and warnings, the warnings will recive a liser priorety the errors will be reviewed and the solution will be discussed:
   1. JSON type show in the csar is not an issue for volte since it will only apper in the heat based usecases.
   2. requirement default is true but no value is assigned, this is under review.
   3. scalar unit type support under review

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
•  
•  Tal Halfon will provide an example of the CSAR expected by SDC with an emphasis on the MF file structure.
  

  View file
  name vCSCF.csar height 150

  
  
•  maopeng zhang will provide the A description of the orcastration flow in order to provide a better butter understanding of the flow and the SDC role in it.
•  maopeng zhang will provide input on the acknowlegment by the vendors providing the VNF for the VOLTE use case to aligne with the SDC requirments.
•  Michael Lando will provide a sugestion to solve the isuess identifed in the CSAR.
•  Former user (Deleted) will review the SDC API and provide input if any information is missing to support the workflow artifact upload.

Metting recording:

meeting Chat:

...