Page History

...

Mapping of ETSI Information NS-related Elements with TOSCA types

• For E2E (OSS Service) modeling, use org.openecomp.resource.abstract.nodes.service
  • E2E (OSS Service-Level) is outside of ETSI scope, and it could be ONAP-specific that is orchestrated by ONAP SO
  • The E2E model references/includes associated NSs
• For NS modeling, use tosca.nodes.nfv.NS
  • ONAP SO-NFVO, VFC and external NFVO manage the NS models and packages

Questions:

• openecomp-sdc-enrichement-lib > openecomp-sdc-enrichement-impl
  • openecomp vs. openecomp-heat vs. tosca 

• The following diagram depicts ONAP ETSI-Alignment Modeling hierarchy.

Mapping between SOL001 Data Model and SDC AID DM

The following summarizes the mapping between two models:

SOL001 VNF	SDC AID DM	comments
N/A	org.openecomp.resource.abstracts.nodes.service	represents OSS Service models
org.

SDC: nfv-typesSDC: heat-typesETSI NFV IESDC Descriptor / SOL001TOSCA TypeDerived fromSDC DescriptorTOSCA TypeDerived fromNSDnodes.yml / SOL001

tosca.nodes.nfv.NS

tosca.nodes.nfv.

RootGeneric_Service.yml

org.openecomp.resource.abstract.nodes.service

(use it for NS)

NS	NS; use of SOL001 as SDC AID DM NS
tosca.nodes.nfv.NsVirtualLink	tosca.nodes.nfv.NsVirtualLink	NS VirtualLink; use of SOL001 as SDC AID DM VL
tosca.nodes.

RootNSD

nfv.

yml

Vnf	org.openecomp.resource.

vfc

abstract.

NSDtosca

nodes.

nodes

ETSI.

RootN/ASapD

VNF

VNF

SOL001

tosca.nodes.nfv.

Sap

vdu

tosca

org.openecomp.

nodes.RootNsVirtualLinkDescSOL001tosca

resource.abstract.nodes.

nfv.NsVirtualLink(there is

VFC	VDU and SDC VFC
tosca.nodes.nfv.

VnfVirtualLink)tosca.nodes.Rootvl.yml

VirtualLink

org.openecomp.

resource

resources.vl

.

	VNF VL
tosca.nodes.

network

nfv.

Network

VduCp

extVl.yml

org.openecomp.

resource

resources.

vl.extVLtosca.nodes.RootinternalVl.yml

cp	VDU CP
N/A	org.openecomp.resource.

vl.internalVL

allottedResource
tosca.nodes.

network

nfv.

NetworkextZteVL.ymltosca

Pnf	org.openecomp.resource.abstract.nodes.PNF	PNF

Current SDC Resource Models

nfv.ext.zte.VLPnfdorg.openecomp.resource.abstract.nodes.VFRoot

SDC: nfv-types					SDC: heat-types
ETSI NFV IE	SDC Descriptor / SOL001	TOSCA Type	Derived from		SDC Descriptor	TOSCA Type	Derived from
NSD	nodes.yml / SOL001	tosca.nodes.Root			tosca.nodes.nfv.PNFNS	tosca.nodes.Root	Generic_PNFService.yml	org.openecomp.resource.abstract.nodes. PNF service (use it for both E2E (OSS Service) and NS)	tosca.nodes.Root	Vnfd
	VNFNSD.yml	toscaorg.nodesopenecomp.nfvresource.vfc.VNFNSD	tosca.nodes.Root		Generic_VF.yml		N/A
SapD	SOL001	tosca.nodes.nfv.Sap	tosca.nodes.Root
NsVirtualLinkDesc	SOL001	tosca.nodes.nfv.	NsVirtualLink (there is		Vnffgd	tosca. groups nodes.nfv. VNFFG VnfVirtualLink)	tosca.groupsnodes.Root	forwardingPathvl.yml(?)	org.openecomp.resource.vl.VL	tosca.nodes.network.Network
					extVl.yml	org.openecomp.resource.vl.extVL.ForwardingPath	tosca.nodes.Root

NSD Mapping to SDC AID DM

Initial Input

• Internal NSD representation

NSD Mapping to SDC AID DM

A benefit of mapping an onboarded ETSI NS to the internal representation of an ONAP Service is that the ETSI NS can access the standard ONAP runtime functionality implemented or planned for support of ONAP Services.

SOL001 NSD mapping to/from NS SDC AID DM

...

...

...

...

...

• SDC generates SOL001 tosca.nodes.nfv.NSD node type
• SDC takes SOL001 NSD with tosca.nodes.nfv.NSD node type as is, without mapping; i.e., no mapping is necessary
• ONAP SO NFVO uses the SOL001 NSD
• VFC needs to use the SOL001 NSD
• There could be some impact on VID and ONAP SO Catalog DB for the SOL001 NSD - to be analyzed.

...

• SDC generates SOL001 tosca.nodes.nfv.NSD node type, and uses it as SDC AID DM.

NSD Mapping to SDC AID DM

Initial Input

• Internal NSD representation

NSD Mapping to SDC AID DM

A benefit of mapping an onboarded ETSI NS to the internal representation of an ONAP Service is that the ETSI NS can access the standard ONAP runtime functionality implemented or planned for support of ONAP Services.

SOL001 NSD mapping to/from NS SDC AID DM

• ONAP previous analysis
  • The SDC NSD node type, org.openecom.resource.vfc.NSD, is modeled as a component of a VF to represent an allotted resource. But, it is not derived from the

SOL001 NS

...

SDC NSD

• • org.openecomp.resource.vfc.AllottedResource, either. 
  • The SDC NSD might be designed for Volte use case support, and used by the VFC.
  • It is recommended to deprecate the current SDC NSD node type, and to replace with SOL001 tosca.nodes.nfv.NSD node type.
• Solutions
  • SDC generates SOL001 tosca.nodes.nfv.NSD node type
  • SDC takes SOL001 NSD with tosca.nodes.nfv.NSD node type as is, without mapping; i.e., no mapping is necessary
  • ONAP SO NFVO uses the SOL001 NSD
  • VFC needs to use the SOL001 NSD
  • There could be some impact on VID and ONAP SO Catalog DB for the SOL001 NSD - to be analyzed.
• Guilin Decisions
  • SDC generates SOL001 tosca.nodes.nfv.NSD node type, and uses it as SDC AID DM.

SOL001 NS

...

Define a new data type based on the tosca.nodes.nfv.VNF with optional attributes that are specific to ONAP.

...

.

...

Proposal A

• Make the org.openecomp.resource.abstract.nodes.ETSI.VNF a superset of both tosca.nodes.nfv.VNF and org.openecomp.resource.abstract.node.VF

...