Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • SDC supports the following NSD Information Elements.
  • SDC supports the netestedNsdId(s) for nested NSDs.
  • SDC UI should be able to manage the NSD attributes.
  • SDC supports the virtualLinkDesc(s) to define constituent VLs.

...

Use Cases for Guilin

VCPE

The following is an example of VCPE model hierarchy. In VCPE, the E2E Service model includes one NS (vCPE). And the vCPE NS model includes vbng, vbrgemu, vgmux and vgw VNFs and a network VL.

  • SDC should be able to reference the vCPE NSD from the E2E Service model.
  • SDC should be able to reference all the constituent VNFs and VL(s).

Last vCPE CSARs

The latest (Frankfurt) vCPE CSARs can be retrieved from the https://git.onap.org/demo/tree/tosca/vCPE_F. There are one NS CSAR and five VNF CSARs:

  • ns.csar
  • infra.csar
  • vbng.csar
  • vbrgemu.csar
  • vgmux.csar
  • vgw.csar


Other Use Case

To represent nested NS cases, we will choose another use case.

...

<tosca.nodes.nfv.ext.zte.VL>

tosca.nodes.nfv.ext.zte.VL

namerequiredtype
segmentation_idfalsestring
network_namefalsestring
is_predefinedfalseboolean
mtufalseinteger
dns_nameserversfalselist
physical_networkfalsestring
dhcp_enabledfalseboolean
network_idfalsestring
host_routesfalselist
ip_versionfalseinteger
vendorfalsestring
namefalsestring
start_ipfalsestring
vlan_transparentfalseboolean
cidrfalsestring
gateway_ipfalsestring
network_typefalsestring
end_ipfalsestring
location_infofalsetosca.datatypes.nfv.ext.LocationInfo


  tosca.nodes.nfv.ext.zte.VL:

...