Page History

...

Epic

User Story

Description

Guilin Plan?

JIRA

Onboard and Design ETSI SOL004 compliant VNF packages

Executive Summary - Enable a vendor provided ETSI SOL004 compliant VNF package including an ETSI SOL001 VNF Descriptor to be onboarded into ONAP for composition into an ONAP Service

Business Impact - Enables operators and service providers to use same ETSI compliant VNF packages with ONAP and existing NFVO. Industry compatibility.

Business Markets - All operators that are currently using ETSI packages to deploy VNFs

Funding/Financial Impacts - Reduction in operations expense from using industry standard VNF packaging. Reduction in capital expense from vendors using a single packaging methodology.

Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2610

Support for onboarding ETSI v2.7.1 SOL001 VNF Descriptor (Link to ETSI SOL001 v2.7.1)

Support for onboarding ETSI v2.7.1 SOL001 VNF Descriptor (Link to ETSI SOL001 v2.7.1)

Yes

SDC-2611 - SDC supports onboarding of the SOL004 VNF Package includes SOL001 VNFD OPEN

Support for mapping of ETSI v2.7.1 SOL001 VNF Descriptor into SDC AID Data Model

Support for mapping of ETSI v2.7.1 SOL001 VNF Descriptor into SDC AID Data Model

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2617

Support for editing ETSI v2.7.1 SOL001 VNF Descriptor

Support for editing ETSI v2.7.1 SOL001 VNF Descriptor

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2881

Support for using an ETSI v2.7.1 VNF in an ONAP Service

Support for using an ETSI v2.7.1 VNF in an ONAP Service

TBD

Support the substitution_mappings in the VNFD.

Currently, the substitution_mappings is not supported by SDC. Lack of this support blocks SOL004 VNF package management and ETSI Catalog Manager:

Prior to Frankfurt, as a workaround, the operator creates a dummy VNF without the substitution_mappings or node_types in the MainServiceTemplate.yaml and added a real VNF package with the substitution_mappings and user-define nodes in its Artifacts>DEPLOYMENT>OTHER directory.
It is to trick the current SDC onboarding issues because SDC does not check the OTHER directory.
In the Frankfurt/Dublin release, SDC was enhanced to support the vendor VNF package in the ONBOARDED_PACKAGE directory.
Since SDC Frankfurt/Dublin, we don't have to use the secondary VNF package unnecessary, but we still needs to follow an old way because of lack of substitution_mappings and user-defined node_types.
When SDC supports the subscription_mappings user-defined node types, the vendor VNF package does not have to add another VNF package in the Artifacts>DEPLOYMENT>OTHER directory, and the ETSI Catalog Manager will support the VNF package in the ONBOARDED_PACKAGE directory.
- ETSI Catalog Manager will depend on this SDC support.

Support of the substitution_mappings and user-defined node_types will remove the issues and support ETSI package management and others.

Support of the user-defined node types is handled by another task. This task needs to handle the substitution_mappings only.

For the testing, use the vgw6.csar

For the Frankfurt release workaround, we added the following to the MainServiceTemplate.yaml, so the ETSI Catalog Manager can retrieve the descriptor_id from the metadata, instead of from the node_type. Once the substitution_mapping is supported by SDC, we don't have to use the descriptor_id in the metadata section.

descriptor_id: b1bb0ce7-2222-4fa7-95ed-4840d70a1177

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2957

Onboard ETSI SOL007 compliant Network Service Descriptor packages

Executive Summary - Onboard an ETSI SOL007 v2.7.1 compliant (Link to ETSI SOL007 v2.7.1) Network Service Descriptor package including an ETSI version 2.7.1 SOL001 Network Service Descriptor (NSD) to be onboarded into ONAP for composition into an ONAP Service or deployment using an ETSI compliant NFVO.

Support for Cataloging and Preserving the original SOL007 package
Support for mapping of ETSI v2.7.1 SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model
Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using VF-C as the NFVO
Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using an external NFVO

Business Impact - Enables operators and service providers to use vendor provided and internally designed Network Service Descriptors with ONAP and existing NFVO. Industry compatibility.

Business Markets - All operators and service providers that are developing ETSI compatible Network Services

Funding/Financial Impacts - Reduction in operations expense from using industry standard NSD packaging.

Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.

stretch goal

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2801

Support onboarding for Cataloging and Preserving the original SOL007 package

Support onboarding for Cataloging and Preserving the original SOL007 package (Link to ETSI SOL001 v2.7.1)

stretch goal

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2806

Support for mapping of ETSI v2.7.1 SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model

use SOL001 NSD as SDC AID DM

stretch goal

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2618

~~Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using VF-C as the NFVO~~

No

Close this, expect the current SDC distribution is sufficient

~~Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using an external NFVO~~

No

Close this, expect the current SDC distribution is sufficient

Design ETSI SOL007 compliant Network Service Descriptor & packages

Executive Summary - Design, catalog and distribute an ETSI SOL007 v2.7.1 compliant (Link to ETSI SOL007 v2.7.1) Network Service Descriptor package including an ETSI version 2.7.1 SOL001 Network Service Descriptor (NSD) for deployment using an ETSI compliant NFVO.

Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using VF-C as the NFVO
Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using an external NFVO

Business Impact - Enables operators and service providers to use vendor provided and internally designed Network Service Descriptors with ONAP and existing NFVO. Industry compatibility.

Business Markets - All operators and service providers that are developing ETSI compatible Network Services

Funding/Financial Impacts - Reduction in operations expense from using industry standard NSD packaging.

Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2802

Note: there is a PoC for this. Soon, the PoC design could be shared as initial input for discussions

Design ETSI SOL001 NSD and generate an ETSI SOL001 v2.7.1 compliant Network Service Descriptor & package

Design ETSI SOL001 NSD and generate ETSI SOL007 v2.7.1 compliant Network Service package

Create NS and compose NS with its sub components, such as VNFs, VLs, ~~VNF-FG~~ and dependencies between VNFs, etc. - final support scope will be defined
Support for mapping of ETSI v2.7.1 SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model
- use SOL001 NSD as SDC AID DM
Generate SOL007 NS package

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2808

~~Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using VF-C as the NFVO~~

~~Wrap the NS package in the Service for VF-C~~

~~Yes~~

Close this, expect the current SDC distribution is sufficient

~~Support for deploying a service that contains an ETSI SOL001 v2.7.1 compliant Network Service using an external NFVO~~

~~Wrap the NS package in the Service for an external NFVO~~

~~Yes~~

Close this, expect the current SDC distribution is sufficient

Support for Nested/Hierarchical ETSI SOL001 v2.7.1 Network Service Descriptor

Executive Summary - Onboard an ETSI SOL007 v2.7.1 compliant (Link to ETSI SOL007 v2.7.1) Network Service Descriptor package including an ETSI version 2.7.1 SOL001 Network Service Descriptor (NSD) that includes references to other Network Service Descriptors for composition into an ONAP Service or deployment using an ETSI compliant NFVO.

Business Impact - Enables operators and service providers to use vendor provided and internally designed Network Service Descriptors with ONAP and existing NFVO. Industry compatibility.

Business Markets - All operators and service providers that are developing ETSI compatible Network Services especially for 5G Slicing where each Slice Subnet is associated with a Network Service

Funding/Financial Impacts - Reduction in operations expense from using industry standard NSD packaging.

Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.

No

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2803

Support for onboarding of the SOL007 v2.7.1 compliant NSD package including SOL001 NSD that includes references to other NSDs for composition into ONAP Service

No

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2811

Onboard ETSI SOL004 compliant PNF packages

Executive Summary - Enable a vendor provided ETSI SOL004 compliant PNF package including an ETSI SOL001 PNF Descriptor to be onboarded into ONAP for composition into an ONAP Service

Business Impact - Enables operators and service providers to use same ETSI compliant PNF packages with ONAP and existing NFVO. Industry compatibility.

Business Markets - All operators that are currently using ETSI packages to deploy PNFs

Funding/Financial Impacts - Reduction in operations expense from using industry standard PNF packaging. Reduction in capital expense from vendors using a single packaging methodology.

Organization Mgmt, Sales Strategies -There is no additional organizational management or sales strategies for this requirement outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2805

SDC supports onboarding of the SOL004 PNF package includes SOL001 PNFD

PNFD onboarding is done and its regression testing will be done

SOL004 PNF package onboarding is done in Dublin but support v2.7.1
Update onboarding procedure for v2.7.1

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2837

Support for mapping of ETSI v2.7.1 SOL001 PNF Descriptor into SDC AID Data Model

SOL001 PNFD 2.7.1 Mapping to SDC AID DM

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2836

Support design of Service templates, leveraging NSDs

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2882

Support design of Service templates, includingNSDs

Support design of Service templates, including NSDs

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2883

Support additional package artifact Indicators for ETSI packages and Non-ETSI packages

SDC supports additional package artifact types to split ETSI packages from other non-ETSI TOSCA packages

SDC (notification) generates additional artifact types
SDC client filters on the additional artifact types

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2813

SDC Notification supports additional package artifact types to split ETSI package from other non-ETSI TOSCA packages

SDC (Notification) supports additional package artifact types to split ETSI package from other non-ETSI TOSCA packages

for SOL004 and SOL007 packages, artifact type = ONBOARDED_ETSI_PACKAGE
for non-ETSI TOSCA package, artifact type = ONBOARDED_ONAP_PACKAGE

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2814

SDC client supports additional filtering on the artifact types for distinguishing between ETSI packages and Non-ETSI packages

for SOL004 and SOL007 packages, filtering for artifact type = ONBOARDED_ETSI_PACKAGE
for non-ETSI TOSCA package, filtering for artifact type = ONBOARDED_ONAP_PACKAGE

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2815

Support ETSI Package Security and validation

ONAP supports vendor ETSI Package Security and validation
- If the vendor package includes signature and certificate, ONAP supports the package security

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2613

SOL004 VNF/PNF Package security will be supported by SDC, based on the package signature and certificate

ONAP SDC supports the package security

Done

SOL007 NS Package security will be supported by SDC, based on the package signature and certificate

ONAP SDC supports the package security

Yes

Jira

server	ONAP JIRA
serverId	425b2b0a-557c-3c0c-b515-579789cceedb
key	SDC-2614

Support of ETSI Package Validation

VNF SDK will support ETSI package validation for VNF and NS

TBD

VNF SDK will support ETSI VNF package pre-onboarding for validation

TBD

VNF SDK will support ETSI NS package pre-onboarding for validation

TBD

...

Enhancement (Ericsson contribution) was made to the SDC Dublin to support SOL004 PNF/VNF onboarding with .zip and .csar file extensions.
- SDC VSP and Resource csar files have the ONBOARDED_PACKAGE, which contains the original vendor VNF package.
  - The VNFM and external NFVO use the original vendor VNF/NS packages.
  - ONAP-ETSI Catalog Manager will be changed for the location of the original vendor package.
  - Author note: a common directory name, replacing the ONBOARDED_PACKAGE, is under discussion.
- SOL007 NS onboarding will follow the same procedure; i.e., storing the vendor SOL007 NS package into the ONBOARDED_PACKAGE directory.
  - Author note: a common directory name, replacing the ONBOARDED_PACKAGE, is under discussion.

At onboarding, SDC checks the file extension and performs the following procedures
1. If the file is .zip, SDC unzips
  1. If it has .cert & .cms, it is a package with security and security validation will be performed.
  2. If it does not include .cert & .cms, it is an existing Heat template onboarding, and SDC follows the Heat template onboarding procedure
If the file is .csar, it is a package without security.
Next, SDC will check the TOSCA.meta file.
If it contains SOL004v2.x.1 keywords, the package will be handled as SOL004v2.x.1. In the Guilin release, v2.7.1 will be supported.
Otherwise, it will be handled as existing TOSCA (non-SOL004) package onboarding which will not have the ONBOARDED_PACKAGE artifact.

...

extend OrchestrationTemplateProcessCsarHandler.java to handle SOL007
- processCsar()
  - instantiateToscaConverterFor(resourceType).convert(fileContentHandler)
    - calling ToscaSolModelDrivenConverterPNF()
      - pndfTransformationEngine.transform()
    - calling ToscaSolConverterVnf()
      - vnfTopologyTemplateConverter().convertTopologyTemplate(serviceTemplate, readerService)
        convertInputs()
        convertNodeTemplates()
        convertOutputs()
        convertSubstitutionMappings()
        convertPolicies()
    - need to call ToscaSolModelDrivenConverterNS()
create ToscaSolModelDrivenConverterNS class
- create NSdNodeTemplateTransformationEngine class
  - transform() to SDC AID DM NS
generate the SDC package for NS with the original vendor SOL007 NS package

...

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

ETSI NFV IE	SDC Descriptor / SOL001	TOSCA Type	Derived from	SDC Descriptor	TOSCA Type	Derived from
SDC: nfv-types				SDC: heat-types
NSD	nodes.yml / SOL001	tosca.nodes.nfv.NS	tosca.nodes.Root	Generic_Service.yml	org.openecomp.resource.abstract.nodes.service (use it for NS)	tosca.nodes.Root
NSD	NSD.yml	org.openecomp.resource.vfc.NSD	tosca.nodes.Root	N/A
SapD	SOL001	tosca.nodes.nfv.Sap	tosca.nodes.Root
NsVirtualLinkDesc	SOL001	tosca.nodes.nfv.NsVirtualLink (there is tosca.nodes.nfv.VnfVirtualLink)	tosca.nodes.Root	vl.yml	org.openecomp.resource.vl.VL	tosca.nodes.network.Network
				extVl.yml	org.openecomp.resource.vl.extVL	tosca.nodes.Root
				internalVl.yml	org.openecomp.resource.vl.internalVL	tosca.nodes.network.Network
	extZteVL.yml	tosca.nodes.nfv.ext.zte.VL	tosca.nodes.Root
Pnfd		tosca.nodes.nfv.PNF	tosca.nodes.Root	Generic_PNF.yml	org.openecomp.resource.abstract.nodes.PNF	tosca.nodes.Root
Vnfd	VNF.yml	tosca.nodes.nfv.VNF	tosca.nodes.Root	Generic_VF.yml	org.openecomp.resource.abstract.nodes.VF	tosca.nodes.Root
Vnffgd		tosca.groups.nfv.VNFFG	tosca.groups.Root	forwardingPath.yml(?)	org.openecomp.nodes.ForwardingPath	tosca.nodes.Root

NSD Mapping to SDC AID DM

...

SOL001 VNF (tosca.nodes.nfv.VNF) from SOL001 v2.7.1			SDC AID DM VNF (org.openecomp.resource.abstract.nodes.VF) from SDC Generic_VF.yml			org.openecomp.resource.vf.vcpeInfrastructureGwDemoApp (derived from org.openecomp.resource.abstract.nodes.VF)
name	required	type	name	required	type	name	required	type
descriptor_id	yes	string	nf_function		string	nf_function		string
descriptor_version	yes	string	nf_role		string	nf_role		string
provider	yes	string	nf_type		string	nf_type		string
product_name	yes	string	nf_naming_code		string	nf_name_code		string
software_version	yes	string	nf_naming		org.openecomp.datatyhpes.Naming	nf_naming		org.openecomp.datatyhpes.Naming
product_info_name	no	string	availability_zone_max_count		integer	availablity_zone_max_count		integer
vnfm_info	yes	list of string	min_instances		integer	min_instances		integer
localization_languages	no	list of string	max_instances		integer	max_instances		integer
default_localization_language	no	string	multi_stage_design		boolean	multi_stage_design		boolean
configurable_properties	no	tosca.datatypes.nfv.VnfconfigurableProperties	sdnc_model_name		string	vf_module_id	no
modifiable_attributes	no	tosca.datatypes.nfv.VnfInfoModifiableAttributes	sdnc_artifact_name		string	vcpe_image_name	no
lcm_operations_configuraion	no	tosca.datatypes.nfv.VnfLcmOperationsConfiguration	skip_post_instantiation_configuration		boolean (default true) constraints : true, false	public_net_id	no
monitoring_parameters	no	list of tosca.dataypes.nfv.VnfMonitoringParameter	controller_actor		string (default: SO-REF-DATA) constraints: SO-REF-DATA, CDS, SDNC, APPC	vgw_name_0	no
flavour_id	yes	string				nexus_artifact_repo	no
flavour_description	yes	string				mux_ip_addr	no
vnf_profile	no	tosca.datatyhpes.nfv.VnfProfile				vnf_id	no
						cpe_public_net_cidr	no
						vg_vgmux_tunnel_vni	no
						nf_naming	no
						multi_stage_design	no
						nf_naming_code	no
						vgw_private_ip_0	no
						vgw_private_ip_1	no
						vgw_private_ip_2	no
						pub_key	no
						install_script_version	no
						onap_private_net_cidr	no
						cpe_public_net_id	no
						mux_gw_private_net_id	no
						dcae_collector_ip	no
						dcae_collector_port	no
						onap_private_net_id	no
						cloud_env	no

SOL001 2.7.1 VNF Template

tosca_defintions_version: tosca_simple_yaml_1_2

description:

imports:

data_types:

node_types:

topology_template:

inputs:

node_templates:

VNF

substitution_mappings:

SDC VF Template

Image Added

VF-Module Initial Input

The following is a summary of initial input from Gil Bullard (AT&T).

...

Space shortcuts

Page tree

Versions Compared

Old Version 103

New Version 104

Key

NSD Mapping to SDC AID DM

SOL001 2.7.1 VNF Template

SDC VF Template

VF-Module Initial Input