SDC 9/11/2017 weekly meeting report

Owned by Michael Lando
Last updated: Oct 29, 2020 by ChrisC
2 min read


Agenda:

 

The agenda will be:

  1.  

    1. Discussion regarding the parser CSAR parsing open issues

    2. Clarification on the work flow for R1

    3. general Q&A

discussion points:

  1. SDC provided a response to the parser open Issues.

    1. JSON type parameter: not relevant to Tosca import flow will be discussed in future releases:SDC-324: json type used by SDC is not a vlide tosaca typeClosed

    2. namespace collisions:  identified as a warning only will be discussed for R2 SDC-319: csar package should avoid name space colisionsClosed

    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 :SDC-321: SDC creates CSAR packages but does not inforece the required trueClosed

    6. status property is upper case, this is a warning and will  be discussed for R2 :SDC-322: status properties value need to be aligned Closed

    7. TOSCA scalar-unit typed values invalid grammar: the issue will be solved for R1 :SDC-323: The scalar unit type value is in correctly createdClosed

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

  3. SDC Will add a plan type artifact to support the workflow artifact attachment.SDC-327: add new artifact type to SDC Closed

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

  5. SDC was requested to provide clarification regarding the values in the Tosca.meta file and our support of Tosca.

 

 

Action items:

@maopeng zhang will provide input on the acknowledgment by the vendors providing the VNF for the VOLTE use case to align 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: