C inline
Best regards Tal Halfon Development Manager @ Amdocs P. +972 54 2213763 [cid:[email protected]] [ONAP_logo_Sig] From: [email protected] [mailto:[email protected]] Sent: Friday, September 22, 2017 4:40 AM To: [email protected] Cc: [email protected]; [email protected]; [email protected]; [email protected]; Halfon Tal <[email protected]>; [email protected] Subject: 答复: Re: [onap-discuss]答复: [sdc]pply for add a Discussion Item about "review VoLTE VNF CSAR example" at SDC weekly meeitng Hi Michael, Thanks for your reply. I have two questions about MainServiceTemplate.yaml. As you said, it is a copy of the main service template located under Definitions and TOSCA.meta points to this file. My understanding is that there are two files called MainServiceTemplate.yaml. One is in the root dir, the other is located in Definitions dir. If I understood correctly, 1) Which one of those two yaml files is going to be parsed as the main entry template? There should be only one mainServiceTemplate.yaml file, and it needs to be under the root. 2) What will happen if we have those two yaml files without entry-point defined in TOSCA.meta? For looking for the entry definition point, we’re parsing the manifest file (mainServiceTemplate.mf). if there is no entry point defined in there, we’re blocking the upload. If we will have the same main service template inside definitions folder, we will not parse the whole file, only its types that are defined under node_types section. Many Thanks, Feng yuanxing 原始邮件 发件人： <[email protected]<mailto:[email protected]>>; 收件人： <[email protected]<mailto:[email protected]>>; <[email protected]<mailto:[email protected]>>;张茂鹏10030173; <[email protected]<mailto:[email protected]>>; <[email protected]<mailto:[email protected]>>; 抄送人： <[email protected]<mailto:[email protected]>>; 日 期 ：2017年09月21日 19:41 主 题 ：Re: [onap-discuss]答复: [sdc]pply for add a Discussion Item about "review VoLTE VNF CSAR example" at SDC weekly meeitng Tal please provide the info regarding the MF file. See my answers below. BR, Michael Lando Opensource TL , SDC AT&T Network Application Development · NetCom Tel Aviv | Tampa | Atlanta | New Jersey |Chicago ··········································································· Office: +972 (3) 5451487 Mobile: +972 (54) 7833603 e-mail: [email protected]<mailto:[email protected]> From: 杨艳 [mailto:[email protected]] Sent: Thursday, September 21, 2017 11:47 AM To: Lando,Michael <[email protected]<mailto:[email protected]>>; SHADMI, DAVID <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Cc: 'onap-discuss' <[email protected]<mailto:[email protected]>> Subject: 答复: [onap-discuss] 答复: [sdc]pply for add a Discussion Item about "review VoLTE VNF CSAR example" at SDC weekly meeitng Hi Michael and David, We haven't received your reply, can you help answer the following questions? Best Regards, Yan 发件人: [email protected]<mailto:[email protected]> [mailto:[email protected]] 代表 杨艳 发送时间: 2017年9月18日 18:48 收件人: 'Lando,Michael'; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> 抄送: 'onap-discuss' 主题: [onap-discuss] 答复: [sdc]pply for add a Discussion Item about "review VoLTE VNF CSAR example" at SDC weekly meeitng Hi Michael, Thanks for your arrangement, here is one VNF csar package from ZTE, please review it in today’s meeting , About the other VNF csar package examples, I will send you later and you can help us to review them offline. The following I list some questions about the VNF csar package structure and hope you can help clarify. Thank you. ROOT\ MainServiceTemplate.mf [a map representing the different parts of the CSAR structure.] About the questions for this file I list the following . MainServiceTemplate.yaml [copy of the main service template located under Definitions] \TOSCA-Metadate\ TOSCA.meta [ metadata regarding the CSAR structure], What’s the relationship between this file and the MainServiceTemplate.yaml at the rrot directory? If the file refer to simple profile 1.1? [Michael the main service template file in the root dir is the same as the one this file points to.] \Artifacts\ [includes all artifacts.] Images are not supported. Artifact type will be identified by an additional folder under “Informational”/“Deployment” that will define the artifact type SDC supported artifact types can be found here: SDC supported artifact types<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_SDC-2Bsupported-2Bartifact-2Btypes&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY&m=8_WJ2naDPC6x7MsZGiVKkLBhBcGh5Ne_-UzZdIyK8K4&s=unFvJn0E4JWTF0uZbWKl3Ou6tsqBQducDJSM6JjYsQM&e=>. Artifacts at the root directory or unrecognized folder(s) will be classified as type “Other” What check and validation SDC will do for VNF csar package content. The directory or the file under root of the Artifacts directory or other directory will be passed directly and not be checked, is it right or not? [Michael the validation differ according to artifact type for yaml files we check that the yaml is valid and the file ending the same is done for xml.] \Informational\ [will hold all informative artifacts in the direct asset level] What artifacts belongs to informational and what artifacts belongs to deployment, Can you help explain it? [Michael information artifacts are doc files pdf etc deployment artifacts are heat tiles workflow files scripts etc.] \Deployment\ [Sub-folder directly under “Artifacts”– Deployment artifacts in the direct asset level] \<VFC TOSCA name>\ \Informational\ [will hold all informative artifacts on VFC level ] \Deployment\ [will hold all deployment artifacts on VFC level ] \Definitions\ [includes all TOSCA yaml files ] MainServiceTemplate.mf Whether it contains all the contents of mf file here and what check will do for this file. Whether it should contains hash values, private key signatures, and public key certificates. metadata: vnf_product_name: vCSCF Whether vnf has naming rules and whether the vnf name should be consisted with A&AI and DCAE vnf_provider_id: ZTE For the provider id, is there a naming standard? vnf_package_version: 1.0 What does the version number represent here? vnf_release_data_time: 2017.01.01T10:00+03:00 what the time means here? source: MainServiceTemplate.yaml source: Definitions/openonfv__tosca.capabilities.nfv.ext.LocalAttachment.yaml Best Regards, Yan 发件人: Lando,Michael [mailto:[email protected]] 发送时间: 2017年9月18日 1:25 收件人: 杨艳 抄送: 'onap-discuss'; SHADMI, DAVID 主题: RE: [sdc]pply for add a Discussion Item about "review VoLTE VNF CSAR example" at SDC weekly meeitng Hi, We can add this to our topics. We have an open item regarding Nokia support of the csar structure we agreed on. Our csar structure is available in the wiki: https://wiki.onap.org/display/DW/Csar+Structure<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Csar-2BStructure&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY&m=8_WJ2naDPC6x7MsZGiVKkLBhBcGh5Ne_-UzZdIyK8K4&s=PdxnunhJhxEn1cnRJ-5G2ncpv_CgoqM5XZ7Vvb_kGqs&e=> and up until today we did not receive all the CSAR examples for the volte use case in the agreed on format. BR, Michael Lando Opensource TL , SDC AT&T Network Application Development · NetCom Tel Aviv | Tampa | Atlanta | New Jersey |Chicago ··········································································· Office: +972 (3) 5451487 Mobile: +972 (54) 7833603 e-mail: [email protected]<mailto:[email protected]> From: 杨艳 [mailto:[email protected]] Sent: Friday, September 15, 2017 2:09 PM To: Lando,Michael <[email protected]<mailto:[email protected]>>; SHADMI, DAVID <[email protected]<mailto:[email protected]>> Cc: 'onap-discuss' <[email protected]<mailto:[email protected]>> Subject: [sdc]pply for add a Discussion Item about "review VoLTE VNF CSAR example" at SDC weekly meeitng Hi Michael and David, We are collecting VNF CSAR package from VoLTE VNF Vendor and want to make sure these VNF CSARs can be supported by SDC. Do you mind adding a discussion Item about "review VoLTE VNF CSAR example" at SDC weekly meeting next week? Best Regards, Yan 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
