With the new SDC model, and using sdc tosca 1.5.1 version, the parse tool can’t find the path “virtual_network_interface_requirements#network_interface_requirements” of CP Node:
11:50:53.959 [main] ERROR org.onap.sdc.tosca.parser.utils.PropertyUtils - processProperties - property virtual_network_interface_requirements is not found

From the output CSAR from SDC, there is one resource-VduCp-template.yml file inside service-Ns01-csar.zip, there is no properties definition compared with R3 output CSAR.

it should include as follows:
tosca.nodes.nfv.VduCp:
derived_from: tosca.nodes.nfv.Cp
description: describes network connectivity between a VNFC instance based on this VDU and an internal VL
properties:
bitrate_requirement:
type: integer # in bits per second
description: Bitrate requirement in bit per second on this connection point
required: false
constraints:

• greater_or_equal: 0
  virtual_network_interface_requirements:
  type: list
  description: Specifies requirements on a virtual network interface realising the CPs instantiated from this CPD
  required: false
  entry_schema:
  type: tosca.datatypes.nfv.VirtualNetworkInterfaceRequirements
  order:
  type: integer
  description: The order of the NIC on the compute instance (e.g.eth2)
  required: false
  constraints:
• greater_or_equal: 0
  vnic_type:
  type: string
  description: Describes the type of the virtual network interface realizing the CPs instantiated from this CPD
  required: false
  constraints:
• valid_values: [ normal, virtio, direct-physical ]
  vnic_name: # Introduced from Beijing release, aligned with ONAP resource IM, outside the scope of SOL001 v2.5.1
  type: string
  required: false
  requirements:
• virtual_link:
  capability: tosca.capabilities.nfv.VirtualLinkable
  relationship: tosca.relationships.nfv.VirtualLinksTo
• virtual_binding:
  capability: tosca.capabilities.nfv.VirtualBindable
  relationship: tosca.relationships.nfv.VirtualBindsTo
  node: tosca.nodes.nfv.Vdu.Compute

reproduced steps:
1. Onboard the attached csar vgw0422.csar
2. Import VSP as resource
3. Use it to create a service