Agenda:
The agenda will be:
- Discussion of the presentation regarding CSAR structure supported for R1Discussion on the sequence design in SDCby SDC.
- discussion regarding the SDC support for work flow files.
- general Q&A
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:
Action items (to be completed by Tuesday Aug-29):
- 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 | ||||
---|---|---|---|---|
|
meeting Chat:
provided documentation regarding the CSAR structure used in SDC:Csar Structure
- SDC requested that CSARS according to the defined structure be provided for testing.
- a concern was raised regarding the commitment of the tosca vendors to support the requested structure.
- from a discussion it looks like nokia did not yet approve the requirement.
- Tal from amdocs agreed to provide an example to the expected CSAR so that the other CSAR will be aligned accordingly.
- based on this example the MF file can be created for the rest of the CSARS.
- SDC provide information regarding the the support that can be achieved for workflow's in R1.
- SDC suggested a definition of a new artifact type for the workflows.
- 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.
- 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.
- all uploaded workflows will be distributed as part of the service CSAR.
- sdc suggested review rest API's exposed in order to provide an alternative the the workflow using the parser.
- 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.
- 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:00:38:55 maopeng: TOSCA-Meta-Version: 1.0 CSAR-Version: 1.0 Created-By: Winery 0.1.37-SNAPSHOT Entry-Definitions: Definitions/openons__vIMS_NS.yaml
00:40:16 maopeng: TOSCA-Meta-File-Version: 1.0 CSAR-Version: 1.1 Created-By: Carlos Santana Entry-Definitions: Definitions/service-33d1f589Dfbc492e8e9b-template.yml
00:45:21 DENG Hui: will VFC get same package format from SDC?
00:46:05 DENG Hui: one change in artificats, two directory: deployment
00:49:33 Nagesha (Nokia): what does helloworld.yml contain ?
00:52:56 DENG Hui: will CSAR package be used for heat vnf as well?
00:54:57 maopeng: In R1, can the VNF package incloude other directiories besides the three mentioned?
00:55:00 David Shadmi: There are some discussion about using it for vCPE. however it would not include HEAT.
00:55:25 David Shadmi: additional directories would be discarded.
00:56:14 David Shadmi: the comment about "additional directories would be discarded" is a response to @maopeng
01:00:15 maopeng: understand, but it is too limited for the VNF vendors. If it can support additional dirctories, it will be more helpful.
01:03:41 DENG Hui: maopeng, could it create other folder under artifact, not in the root directory?
01:04:31 maopeng: it has said it does not support the nesting directories in the artifacts
01:05:18 halfont: David said that we will check it tomaroow and give an answer about it
01:06:10 Nagesha (Nokia): Is this CSAR format for VNF package and also for service package (which user creates service using SDC gui) ?
01:15:08 DENG Hui: mainservice template.mf is duplicate of tosca.meta for SDC
01:16:01 Bharath Thiruveedula-Verizon: can we quickly discuss about the VNF sequencing after this topic, we raised about VNF sequencing in mailing list https://lists.onap.org/pipermail/onap-discuss/2017-August/003803.htm
01:17:41 Nagesha (Nokia): is "MainServiceTemplate" hardcoded name or it can be anything abc.yaml ?
01:17:52 DENG Hui: copy both files from definitions to root
01:18:02 DENG Hui: can u do it ?
01:20:17 DENG Hui: tosca.meta will still configure root direcotry?
01:20:24 maopeng: Entry-Definitions: ./MainserviceTemplate.yaml
01:21:40 DENG Hui: clear
01:22:15 DENG Hui: just copy, don't change content
01:23:54 Victor Gao: does the mainservicetemplate is hardcode?
01:24:13 Victor Gao: the name of ya m l
01:27:52 Nagesha (Nokia): in format the services are distributed ?