It was closed by mistake I reopened it.
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: ml6...@intl.att.com<mailto:ml6...@intl.att.com> From: feng.yuanx...@zte.com.cn [mailto:feng.yuanx...@zte.com.cn] Sent: Tuesday, October 31, 2017 3:35 AM To: Lando,Michael <ml6...@intl.att.com> Cc: onap-discuss@lists.onap.org; zhang.maope...@zte.com.cn; onap-discuss@lists.onap.org; ying.yunl...@zte.com.cn; fu.jin...@zte.com.cn Subject: The ticket SDC-533 was closed although the issue was not fixed, would you please check it? SPGW 2: type: org.openecomp.resource.vf.Spgw metadata: invariantUUID: 488587e7-051a-4fb8-9cd8-44738b3ef88c UUID: e524a291-da5c-481f-9059-c0df2e375f73 customizationUUID: 17c4b1c0-6a5d-4988-b135-683affec6b0e version: '0.2' name: SPGW description: SPGW type: VF category: Generic subcategory: Network Elements resourceVendor: zte resourceVendorRelease: '1.0' resourceVendorModelNumber: '' properties: nf_naming: ecomp_generated_naming: true availability_zone_max_count: 1 requirements: - virtualLink: capability: tosca.capabilities.nfv.VirtualLinkable node: mgmt - virtualLink: capability: tosca.capabilities.nfv.VirtualLinkable node: OM [cid:image001.png@01D3523C.C0119710] 原始邮件 发件人：冯远兴10034308 收件人： <ml6...@att.com<mailto:ml6...@att.com>>; 抄送人： <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>;张茂鹏10030173; 日 期 ：2017年10月25日 16:40 主 题 ：About the lack of requirements labels in service template using SDC to design vEPC service, I've created a ticket SDC-533. If there's anthing I've not described clearly, don't hesitate to contact me. Thanks. https://jira.onap.org/browse/SDC-533<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_SDC-2D533&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=RynqW2q8pkELnIhPvHEWeQ&m=TcSgnXVAqUuJ4NGSAwHT-1ktO_VudORz94AMwaPIAic&s=w9OOGaQhBZfZyBukbpptYfINgBeXkZuo6XgFoYfOHuk&e=> 1) Onboard 3rd-party VNF csar files in SDC catalog 2) Import VSP in order to import those 3rd-party VNFs 3) Design a vEPC service using those VNFs. When I am trying to drag a link between SPGW node, which is a VNF, and external virtual link. I could choose the requirement of SPGW node as the picture below shows. However, after I export this vEPC service template, I can't find the name of the requirement in that template. All I've got in service template is just virtual_link while I need the exact name of requirements, ToOM instead. During the period of instantiation, VF-C parses the NSD template and then passes the information to VNFM in order to instantiate VNF. Because of this issue, VF-C can't get the correct names of requirements. Therefore VNFM can't get those names too. So VNFM does not know how to attach the connection points to the external virtual link. SPGW: metadata: ... properties: ... requirements: - virtual_link: capability: tosca.capabilities.nfv.VirtualLinkable node: Control Network - virtual_link: capability: tosca.capabilities.nfv.VirtualLinkable node: Mgmt Network
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
