Page History

Support Onboard ETSI SOL004 compliant VNF / CNF packages

• Executive Summary- Enable a vendor provided ETSI SOL004 v3.3.1 compliant VNF package including an ETSI SOL001 VNF / CNF Descriptor to  be onboarded into ONAP for composition into an ONAP Network Service
  • Support for onboarding ETSI v3.3.1SOL004 VNF CSAR Packages with CNF enhancements
  • Support for onboarding ETSI v3.3.1 SOL001 VNF Descriptor with CNF enhancements
  • Support for mapping of ETSI v3.3.1 SOL001 VNF Descriptor with CNF enhancements into SDC AID Data Model
• 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 v3.3.1SOL004 VNF CSAR Packages with CNF enhancements

• SDC users need to onboard ETSI v3.3.1 SOL004 VNF CSAR Packages with CNF enhancements
• SDC users should be also able to onboard ETSI v2.6.1 SOL004 CSAR packages - one level backward compatibility needs to be supported

• For backward compatibility support, SDC needs to check the package manifest file and metadata such as "compatible_specifcation_versions".
  • If it is 3.3.1+, SDC needs to follow

• • an onboarding path for the ETSI 3.3.1 version package.
  • If the version is smaller than 3.3.1, SDC follows the existing 2.x onboarding path. 
• The package version and its descriptor version should match.

Support for onboarding ETSI v3.3.1 SOL001 VNF Descriptors with CNF enhancements

• SDC users need to onboard ETSI v3.3.1 SOL001 VNF Descriptors

• SDC users should be also able to onboard ETSI v2.6.1/v2.5.1 SOL001 VNF Descriptors - one level backward compatibility needs to be supported

• For backward compatibility support, SDC needs to recognize the properties changes (e.g., VNFD_SCHEMA_VERSION

• ) for the Version indication. 
• SDC uses a separate onboarding process depending on the version.

SDC users need to onboard ETSI 3.3.1 with custom enhancements (Note: 4.1.1 is not stable now

, but 4.1.1 will be used in Honolulu)...

• SDC needs to support new CNF properties / classes / schema / data models based on defined Information Models
• SDC may use a separate onboarding process for CNF
• No backward compatibility for CNF support is necessary

Support for mapping of ETSI v3.3.1 SOL001 VNF Descriptor

into SDC AID Data Model

Once SDC onboards an ETSI v3.3.1 SOL001 VNF Descriptor, SDC needs to map the ETSI v3.3.1 SOL001 VNF Descriptor into SDC AID Data Model

• No backward compatibility ; only 3.3.1 mapping
• No mapping for 2.6.1: SDC should be also able to map ETSI v2.6.1/v2.5.1 VNF Descriptor into SDC AID Data Model (see the 

  84670319 section)

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)

Interface mapping is important for SDC to create Service and connect VNF to external networking, etc. ... TBD

for capacity and requirements, we need to investigate how SDC / ONAP uses... TBD

Once SDC onboards an ETSI v3.3.1 SOL001 VNF Descriptor with CNF enhancements, SDC needs to map the ETSI v3.3.1 SOL001 VNF Descriptor with CNF enhancements into SDC AID Data Model

• SDC supports VDU mapping for osContainer to SDC AID DM
  • create a new NF type for CNF
• SDC supports virtualCPD, MCIOP, Helm Chart...
• note: need to discuss with the non-ETSI team for compatibility
  • try to have unified modeling between

• • non-ETSI and ETS-based CNF modeling... To discuss with SO team...

SDC users should be able to edit onboarded ETSI v3.3.1 SOL001 VNF Descriptors

• no backward compatibility is necessary

• SDC supports value changes

• and also adding properties

Note: should we reflect the changes to original vendor packages in ETSI_PACKAGE directory??? need to think about impact...

SDC generates a new digital signature

for the package and distributes it to ETSI Catalog Manager.

Design ETSI SOL007 compliant Network Service Descriptor packages

• Executive Summary

• -

• Design, catalog and distribute  an ETSI SOL007 v3.3.1 compliant

• Network Service Descriptor package including an ETSI

• v3.3.1 SOL001 Network Service Descriptor (NSD)

• for

• deployment using an ETSI compliant NFVO.
  • Support for

• • designing an ETSI SOL001 v3.3.1

• • compliant Network Service

• • that can be deployed with an ETSI compliant NFVO
  • Compose of one or more VNFs and the Virtual Links that connect them.
  • Support for using VNFs with CNF enhancements
• Business Impact- Enables operators and service providers to use

• internally designed Network Service Descriptors with ONAP and existing NFVO. Industry compatibility.
• Business Markets

• - All operators and service providers that are developing and deploying 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

Support

for designing an ETSI SOL001 v3.3.1

compliant Network Service that can be deployed with an ETSI compliant NFVO

SDC users need to design an ETSI SOL001

v3.3.1 compliant

Network Service that can be deployed with an ETSI compliant NFVO

• backward compatibility .... TBD... handle old packages...
• to match the version with VNF / CNF ... 
• during SDC references VNFs, validate the version of VNFs... in the VNF descriptor... after 2.6.1 there is a version indicator in the metadata... The version number could be part of VNF onboarding... to move it to there...
• SDC users create NS 
• SDC users generate SOL007 NS package

Compose of one or more VNFs and the Virtual Links that connect them

SDC users need to compose one or more VNFs and the Virtual Links that connect them in NS

cover the VNF version validation... SAP descriptor has a version...

Support for

using VNFs with CNF enhancements

SDC users need to use VNFs with CNF enhancements

virtual CPD ... version...

SDC needs to support for mapping of ETSI SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model

• use SOL001 NSD as SDC AID DM
• support only ETSI NS and NsVirtualLink only.. maybe more...

Interfaces...

Yes

SDC users need to support design of Service templates, leveraging NSDs

ONAP service references NSDs...

Yes

Design Nested/Hierarchical ETSI SOL001 v3.3.1 Network Service Descriptor package

• Executive Summary- Design an ETSI SOL007 v3.3.1 compliant Network Service Descriptor package including an ETSI v3.3.1 SOL001 Network Service Descriptor (NSD) that includes references to other Network Service Descriptors for deployment using an ETSI compliant NFVO.
  • Composed of zero or more VNFs and one or more nested Network Services and the Virtual Links that connect them.
  • Support for using VNFs with CNF enhancements
• 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.

Support for using VNFs with CNF enhancements

Onboard Prototype Package based on ETSI IFA011 v4.1.1 supporting containerized VNF (CNF) packages

• Executive Summary- Enable a vendor provided ETSI SOL004 compliant containerized VNF package including an ETSI SOL001 VNF Descriptor with container enhancements to  be onboarded into ONAP for composition into an ETSI Network Service
  
  • Support for onboarding Prototype v4.1.1 CSAR Packages
  • Support for onboarding Prototype v4.1.1 VNF Descriptor
  • Support for mapping of Prototype v4.1.1 VNF Descriptor into SDC AID Data Model
  • Support for using a Prototype v4.1.1 VNF in an ETSI Network Service
• Business Impact- Enables operators and service providers to use same ETSI aligned containerized VNF (CNF) packages with ONAP and existing NFVO. Industry compatibility.
• Business Markets- All operators that are currently using ETSI packages to deploy containerized VNFs (CNFs)
• Funding/Financial Impacts- Reduction in operations expense from using industry standard containerized VNF (CNF)  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.

Support for onboarding Prototype v4.1.1 CSAR Packages

Support for onboarding Prototype v4.1.1 VNF Descriptor

Support for mapping of Prototype v4.1.1 VNF Descriptor into SDC AID Data Model

Support for using a Prototype v4.1.1 VNF in an ETSI Network Service

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 v3.3.1
• Update onboarding procedure for v3.3.1

Support for mapping of ETSI v3.3.1 SOL001 PNF Descriptor into SDC AID Data Model

Onboard ETSI SOL007 compliant Network Service Descriptor packages

Executive Summary - Onboard an ETSI SOL007 v3.3.1 compliant (Link to ETSI SOL007 v3.3.1)  Network Service Descriptor package including an ETSI version 3.3.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 v3.3.1 SOL001 Network Service Descriptor in the SOL007 package into SDC AID Data Model

• Support for deploying a service that contains an ETSI SOL001 v3.3.1 compliant Network Service using VF-C as the NFVO

• Support for deploying a service that contains an ETSI SOL001 v3.3.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. 

SDC users need to support onboarding for Cataloging and Preserving the original SOL007 package (Link to ETSI SOL001 v3.3.1)

ONAP supports vendor ETSI

3.3.1Package 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 ETSI 3.3.1 package signature and certificate

ONAP SDC supports

ETSI 3.3.1 SOL004 VNF/PNF Package security

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

ONAP SDC supports

ETSI 3.3.1 SOL007 NS Package security