You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Agenda:


The agenda will be:

    1. Discussion of the CSAR structure supported for R1
    2. Discussion on the sequence design in SDC

discussion points:

  1. David Presented the CSAR structure which will be supported for R1. 

  2. in case the CSAR structure is incorrect the onboarding will fail.
  3. SDC will use the modeling call to discuss the finalization of the CSAR package and its contents.
  4. a meeting will be on Friday to try to model a vf using SDC based on one of the VF provided by ZTE for the VOLTE use case.
  5. VFC sdc integration, the integration is still not finalized.

Action items:

  1. can the SDC support nested artifacts in the CSAR? (owner TAL)
  2. can the CSAR structure be aligned according to the request to have the service template yaml and mf in the root level (owner meopeng)
  3. provide vnf sdk with a location/explanation to the validations done on the CSAR on onboarding to allow them to validate the csar when they receive it (owner Tal)
  4. VFC need to provide the artifacts that are needed by them in the csar.
  5. SDC need to provide a csar structure documintatio.
  6. SDC need to reply to the enquiries by ZTE regarding the parser issue identified.

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 ?



  • No labels