Hi See my comments
Best regards Tal Halfon Development Manager @ Amdocs P. +972 54 2213763 [cid:[email protected]] [ONAP_logo_Sig] From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, August 29, 2017 12:02 PM To: Halfon Tal <[email protected]> Cc: Marina Vinokurov <[email protected]>; Oren Kleks <[email protected]>; [email protected]; Tali Orenbach <[email protected]>; [email protected] Subject: [onap-discuss] 答复: RE: SDC weekly meeting notes 28/8 hi Thanks for your clarification. A few comments below. Thanks Maopeng 原始邮件 发件人： <[email protected]<mailto:[email protected]>>; 收件人： <[email protected]<mailto:[email protected]>>; <[email protected]<mailto:[email protected]>>;张茂鹏10030173;赵化冰10201488; 抄送人： <[email protected]<mailto:[email protected]>>; <[email protected]<mailto:[email protected]>>; <[email protected]<mailto:[email protected]>>; <[email protected]<mailto:[email protected]>>; 日 期 ：2017年08月29日 15:48 主 题 ：RE: SDC weekly meeting notes 28/8 Hi SDC community Action items from the meeting 1) Can the SDC support nested artifacts in imported CSAR? Yes, We are supporting folders in the /Artifacts [Maopeng] Have the folders in the artifacts some limits? Can the VNF vendor add some folders that they wants? 2) provide VNFSDK team with information and code location about the current SDC CSAR validations (owner Tal H.) We need two things if we want to meet the R1 timeline 1) Copy the MainServiceTemplate.yaml from the / Definitions to the ROOT CSAR and change is name to MainServiceTemplate.yaml 2) Copy the data from the Tosca.meta into the MainServiceTemplate.mf MainServiceTemplate.mf sample: metadata: vnf_product_name: VNF_Name vnf_provider_id: ZTE vnf_package_version: 1.0 vnf_release_data_time: 2017.01.01T10:00+03:00 source: MainServiceTemplate.yaml source: Definitions/GlobalSubstitutionTypesServiceTemplate.yaml source: Artifacts/install.sh source: Artifacts/create_stack.sh I have attach a sample of the MainServiceTemplate.mf to the mail [Maopeng] Tosca.meta content is different from the MainServiceTemplate.mf. For VNF vendors, it is not a copy from Tosca.meta. In the wiki page CSAR structure, it combines the ETSI or OASIS option1 and option2. it is almost a new one and has more duplicated contents. If the aim is to support both option1 and option2 in SDC, we should consider the issue and avoid to make it confused to the VNF vendor. If it is an temporary solution because of the develop time just for R1, we should note it. Yes it’s a temporary solution for R1. The target for R2 as I see it is to support option 2 only Best regards Tal Halfon Development Manager @ Amdocs P. +972 54 2213763 -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Lando,Michael Sent: Tuesday, August 29, 2017 12:46 AM To: [email protected]<mailto:[email protected]> Cc: Franko, Dudi <[email protected]<mailto:[email protected]>> Subject: [onap-discuss] SDC weekly meeting notes 28/8 Hi, Attached is a link to our meeting notes: https://wiki.onap.org/plugins/servlet/mobile?contentId=1015829#content/view/15990847 _______________________________________________ onap-discuss mailing list [email protected]<mailto:[email protected]> https://lists.onap.org/mailman/listinfo/onap-discuss This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer> This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer> This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
