Page Comparison

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

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)

• Support SDC AID DM VF descriptor (see the 

  SOL0012.7.1VNFDMappingfrom/toSDCAIDDMVNFD79200568 section)

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

VNF Mapping:

• Define a new data type based on the org.openecomp.resource.abstract.nodes.VF with ETSI SOL001 VNF data type attributes.

  • Make the org.openecomp.resource.abstract.nodes.ETSI.VNF a superset of both tosca.nodes.nfv.VNF and org.openecomp.resource.abstract.node.VF
  • During VNF onboarding, SDC copies SOL001 VNF attribute contents to the corresponding attributes in the org.openecomp.resource.abstract.nodes.ETSI.VNF
    • In Guilin, SO NFVO, VFC and SVNFM get those SOL001 VNF attributes from the descriptor, not from AAI. So, AAI schema changes are not expected in Guilin.
  • SOL001 VNF attributes in SDC AID DM VNF will be visible to SDC UI, so SDC UI can change the attributes.
    • But the onboarded vendor ETSI package will note be changed by the SDC UI users in Guilin.
    • Since SO NFVO, VFC and SVNFM use only the original ETSI package, those changes will not be used in Guilin;
    • For the Honolulu release, it is under consideration
      • to sync up between those modified SOL001 VNF attributes and the vendor ETSI Package attributes 
      • to reflect those modified SOL001 VNF attributes in the orchestration
  • ONAP specific attributes that are inherited from the org.openecomp.resource.abstract.nodes.VF will be filled up by SDC (design time)
    • Those attribute contents will not be mapped back into the SOL001 VNF (reverse mapping). For that case, only the SOL001 VNF corresponding attributes will be copied

VDU Mapping:

• Make the org.openecomp.resource.abstract.nodes.ETSI.VFC a superset of both tosca.nodes.nfv.Vdu and org.openecomp.resource.abstract.nodes.VFC
• Note: the org.openecomp.resource.abstract.nodes.VFC represents design-time VFC, not VFC instances
• During VNF onboarding, SDC copies SOL001 VDU attribute contents to the corresponding attributes in the org.openecomp.resource.abstract.nodes.ETSI.VFC
  • In Guilin, SO NFVO, VFC and SVNFM get those SOL001 VDU attributes from the descriptor, not from AAI. So, AAI schema changes are not expected in Guilin.
• SOL001 VDU attributes in SDC AID DM VNF will be visible to SDC UI, so SDC UI can change the attributes.
  • But the onboarded vendor ETSI package will note be changed by the SDC UI users in Guilin.
  • Since SO NFVO, VFC and SVNFM use only the original ETSI package, those changes will not be used in Guilin;
  • For the Honolulu release, it is under consideration
    • to sync up between those modified SOL001 VDU attributes and the vendor ETSI Package attributes 
    • to reflect those modified SOL001 VDU / VFC attributes in the orchestration

VF-Module Mapping:

• SDC deduces the VF-Module from the SOL001 VNFD Policies>scaling_aspects>properties>aspects
• Additional VF-Module attributes are deduced as the following table
• SOL003 Adapter may need to transform the VF-Module back to the SOL001 VNFD policies for the scaling and healing requests from VNFM(s) – not part of Guilin

• Support for editing ETSI v2.7.1 SOL001 VNF Descriptor

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

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 ETSI_PACKAGE directory.
• In the Guilin release, the ONBOARDED_PACKAGE directory is changed to the ETSI_PACKAGE.
• 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 ETSI_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

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 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. 

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

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

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. 

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

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

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. 

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. 

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

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

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

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

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

• ONAP supports vendor ETSI Package Security and validation

  • If the vendor package includes signature and certificate, ONAP supports the package security

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

• ONAP SDC supports the package security

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

• ONAP SDC supports the package security