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.

Unable to embed resource: service-ZteEpcNs-template.yml of type application/octet-stream

SPGW:
  metadata:

  ...
  properties:

  ...
  requirements:
  - virtual_link:
    capability: tosca.capabilities.nfv.VirtualLinkable
    node: Control Network
  - virtual_link:
    capability: tosca.capabilities.nfv.VirtualLinkable
    node: Mgmt Network

service-ZteEpcNs-template.ymlresource-ZteSpgwFix-csar.csar