Page History

Agenda:

The agenda will be:

1. 1. Discussion regarding the parser CSAR parsing open issues
   2. Clarification on the work flow for R1
   3. presentation regarding CSAR structure by SDC.
   4. discussion regarding the SDC support for workflow files.
   5. 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 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 support that can be achieved for workflows 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 vendor 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 workflows.
   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 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. provided a response to the parser open Issues.

   1. JSON type parameter: not relevant to Tosca import flow will be discussed in future releases:

      Jira
      server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SDC-324

   2. namespace collisions:  identified as a warning only will be discussed for R2 

      Jira
      server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SDC-319

   3. required true: SDC provided two options for handeling the issue:
      1. check if there is an option in the parser to define what is an error and what is a warning and define the required as a warning.
      2. define the properties that have no value but have required true as inputs. and check if this solves the issue.
   4. SDC explained that from our point we are a design time catalog and are not obligated to fill this values as opposed to a run time catalog.
   5. for R2 we will continue to discuss the handling of this issue :

      Jira
      server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SDC-321

   6. status property is upper case, this is a warning and will  be discussed for R2 :

      Jira
      server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SDC-322

   7. TOSCA scalar-unit typed values invalid grammar: the issue will be solved for R1 :

      Jira
      server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SDC-323

10. SDC Work Flow clarified that for R1 there is no plan to integrate the work flow design with the SDC API's, the workflow attachment will be added manually.
11. SDC Will add a plan type artifact to support the workflow artifact attachment.

    Jira
    server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SDC-327

12. ON the call there were questions regarding how can a property be updated after design time if it was not declared as an input. it was a mistake on my part, the way a property will be configured at run time is using the input.
13. SDC was requested to provide clarification regarding the values in the Tosca.meta file and our support of Tosca.sdc provided a review of 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:
14. JSON type show in the csar is not an issue for volte since it will only apper in the heat based usecases.
15. requirement default is true but no value is assigned, this is under review.
scalar unit type support under review

Action items:

•  maopeng zhang will provide input on the acknowlegment acknowledgment by the vendors providing the VNF for the VOLTE use case to aligne with the SDC requirmentsalign with the SDC requirements.
•  Michael Lando will provide clarification regarding the Values defined in the Tosca.meta
•  Michael Lando will provide a CSAR with the properties with no value declared as inputs to check if thsi solves the issue wioth regured to the OPENSTACK parser.
  
  

Metting recording:

meeting Chat: