I answered your questions in the wiki under the csar structure.
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: Manoj K Nair [mailto:[email protected]] Sent: Thursday, September 07, 2017 10:30 PM To: SHADMI, DAVID <[email protected]>; denghui (L) <[email protected]>; Gaoweitao (Victor, MANO) <[email protected]>; Lando,Michael <[email protected]> Cc: [email protected] Subject: RE: [onap-discuss] [SDC][VNFSDK][VFC]Some questions on CSAR structure Hi David/Michael, We have posted couple of questions (listed below) in the wiki w.r.t CSAR structure presented in last SDC meeting. Can you please clarify 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=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY&m=_MWqniPM2n8GTS6XoDOvfEPzJCqWGI4VnTBrbCtNLGg&s=illtjWnkVmZK66FIi_HP8yVzElA_X7rKFOlGk5Z0PYI&e=> * Which are the mandatory information in "CSAR provided by the vendor to the SDC for onboarding" . We are assuming all the folders/files under ROOT are mandatory except for the Artifacts. * Regarding "Artifacts at the root directory or unrecognized folder(s) will be classified as type “Other” " . This means artifacts need not be placed under Artifacts, it can be loosely placed in the root directory. * Can you please clarify if any validation is done inside SDC to check the Artifact Type to Artifact file name extension. * As we understand from above - Following is typical proposed structure . Kindly confirm * Root * TOSCA-MetaData * Artifacts * Informational * Deployment * HEAT * Heat File 1 * Heat File 2 * HEAT_ENV * Heat_Env1 * Heat_Env2 * Definitions * TOSCA YAML 1 * TOSCA YAML 2 * Can you please clarify the typical artifacts placed in Informational and Deployment subfolders ? Is there any restrictions from SDC side on the placement of specific type of artifact in specific folders in CSAR (Informational/Deployment) * Can you please let us know where we can see a sample CSAR for the 3 cases mentioned above ? Regards Manoj From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of SHADMI, DAVID Sent: Wednesday, September 06, 2017 7:37 AM To: denghui (L); Gaoweitao (Victor, MANO); LANDO, MICHAEL Cc: [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] [SDC][VNFSDK][VFC]Some questions on CSAR structure Hi Deng, Victor, Michael should come back with answers tomorrow morning. In the meantime, I will try to answer some of the questions. 1. Artifacts at the root directory, “Other” directory or unrecognized directory would be classified as “Other” type. This includes the vendor specific files archived as a zip. 2. The addition of the “Informational” and “Deployment” folders inside the “Artifacts” folder was discussed in our weekly call last week. There was an ask to align the input VNF package with the output VNF package. I assume these two folders are mandatory only if you have artifacts of that type, but will let Michael to response. 1. <VFC TOSCA name>, VFC here refers to “Virtual Function Component”. It is an OpenECOMP name for VNF components. The “Informational” and “Deployment” folders at the “Artifacts” root directory are VNF-level for VNF-level artifacts. The “Informational” and “Deployment” folders at the “<VFC TOSCA name>” folder are VFC-level artifacts. I assume the <VFC TOSCA name> is mandatory if you have VFC-level artifacts. Again, I will let Michael confirm. 1. That was discussed on Monday or Tuesday last week as a solution for R1 to reduce development time (SDC onboarding has been implemented according to option2). Thanks, David From: denghui (L) [mailto:[email protected]] Sent: Tuesday, September 05, 2017 8:23 PM To: Gaoweitao (Victor, MANO) <[email protected]<mailto:[email protected]>>; LANDO, MICHAEL <[email protected]<mailto:[email protected]>>; SHADMI, DAVID <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: RE: [SDC][VNFSDK][VFC]Some questions on CSAR structure Hi David I haven’t see those questions been answered, they would like to understand what’s is mandatory or optional for import and output CSAR package according to : 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=DwMFbw&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=skpdiP0xw2R60zh8xAfHt4Tdi4HAeGA-0qjI34v8-NQ&s=m20-TIuBrX1Ko2zuRrWDIftJi31YHZd6HChhZ3gnv14&e=> Thanks a lot for your kind help Best regards, DENG Hui From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Gaoweitao (Victor, MANO) Sent: Tuesday, September 05, 2017 10:34 PM To: LANDO, MICHAEL; SHADMI, DAVID Cc: [email protected]<mailto:[email protected]> Subject: [onap-discuss] [SDC][VNFSDK][VFC]Some questions on CSAR structure Hi Michael, David, I saw the link on the wiki about the CSAR package for SDC input/output: 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=DwMFbw&c=LFYZ-o9_HUMeMTSQicvjIg&r=6LxcToBRYH6m8VI0NilcXQ&m=skpdiP0xw2R60zh8xAfHt4Tdi4HAeGA-0qjI34v8-NQ&s=m20-TIuBrX1Ko2zuRrWDIftJi31YHZd6HChhZ3gnv14&e=> As we discussed in Last Friday, I have couple of questions here: 1. We agree have a vendor-specific zip file under Artifacts folder and should the wiki page update for support this? 2. I don't see the requirement of “Informational” and “Deployment” folder on the meeting. Does SDC have some special requirement /restriction on this or these folders will added during SDC onboard VNF CSAR package? 3. What’s the difference between “VF-C TOSCA NAME”‘s “Informational” and “Deployment” folders and ROOT’s “Informational” and “Deployment” folder? Could these folders be optional? 4. By the way, could you help us clarify usage of Metadata and Manifest in SDC? Cause I think we already got the consensus on choosing Option1(with metadata as R1 selection), I think manifest is duplicate functionality (find the entry point for VNF main service template) with metadata in R1. In my understanding, last Friday we got the consensus is like this as VNF CSAR for SDC input: [cid:[email protected]] Please correct me if any mistake or misunderstanding. BR Victor ************************************************************************************************* 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使 用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通 知发件人并删除本邮件！ ************************************************************************************************* ************************************************************************************************* This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! ************************************************************************************************* ________________________________ The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
image001.emz
Description: image001.emz
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
