Agenda:
The agenda will be:
- Discussion of the CSAR structure supported for R1
- Discussion on the sequence design in SDC
discussion points:
SDC supported input CSAR structure which is supported for R1.
3 Directories: /TOSCA-Metadata, /Artifacts, /Definitions
SDC development team to check if the import CSAR structure can be the same as the output CSAR structure (nested directories inside /Artifacts)
- SDC is not supporting images in R1
- SDC is doing basic package validation and would fail incorrect package structure/content
- VNFSDK team asks about SDC TOSCA validation code
- SDC presented the number of options for VNF sequencing.
- 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: - Using the workflow - suggesting to check with SO and VF-C how this is done today
- 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)
- Aug-29 Modelling call will have a slot to discuss the leftovers about CSAR package format
- SDC suggested having a 3-hours call with VF-C team to manually craft one of VoLTE VNFs and the discuss SDC output
- 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):
- Option 1:
- VF-C implements DMaaP API to register on service and resource notification
- VF-C implements SDC catalog API to get service and VNFs
- Option 2:
- VF-C implements only SDC catalog API and based on SO call gets the service/VNFs from SDC
- Option 1:
...
- Can the SDC support nested artifacts in imported CSAR? (owner Tal H.)
- can the CSAR structure be aligned according to the request to have the service template yaml and mf in the root level (owner Meopeng)
- Provide VNFSDK team with information and code location about the current SDC CSAR validations (owner Tal H.)
- VF-C team to provide the list of artifacts that would be included in the onboarded VNF and used by VF-C (owner Meoperg)
- SDC team to make sure WiKi page is updated with the latest CSAR structure documentation (owner Michael L.)
- SDC development team to response VF-C questions about TOSCA parser (owner Michael L.)
SDC Supported Import CSAR Structure in R1:
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:
View file | ||||
---|---|---|---|---|
|
...