You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

Requirements & Use Cases

The following requirements are defined in the Guilin release - functional requirements proposed list, Guilin release - functional requirements proposed list

  • Onboard ETSI SOL004 compliant VNF packages 
    • Support for onboarding ETSI v2.7.1 SOL004 CSAR Packages (Link to ETSI SOL004 v2.7.1 )
    • Support for onboarding ETSI v2.7.1 SOL001 VNF Descriptor (Link to ETSI SOL001 v2.7.1)
    • Support for mapping of ETSI v2.7.1 SOL001 VNF Descriptor into SDC AID Data Model
    • Support for using an ETSI v2.7.1 VNF in an ONAP Service
  • Onboard ETSI SOL007 compliant Network Service Descriptor packages
    • 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
  • Design ETSI SOL007 compliant Network Service Descriptor packages
    • 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
  • Support for Nested/Hierarchical ETSI SOL001 v2.7.1 Network Service Descriptor

Feature Descriptions

Feature

Description

SDC ETSI Package Management
  • SOL004 VNF/PNF Package includes SOL001 VNFD/PNFD with the original vendor package will be onboarded into SDC and  distributed from SDC to SVNFM/External NFVO.
  • SOL007 NS Package includes SOL001 NSD with the original vendor package will be onboarded into SDC and distributed from SDC to SVNFM/External NFVO.
  • SDC supports design of ETSI SOL007 compliant NSD packages and distribute them to SVNFM/External NFVO
  • SDC supports Nested/Hierarchical ETSI SOL001 v2.7.1 NSD onboarding and distribution to ONAP runtime components.
ETSI Package Security

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

  • SOL004 VNF/PNF Package security is supported by the package signature and certificate
  • SOL007 NS Package security is supported by the package signature and certificate
  • SDC will store the vendor package with signature and certificate in a zip format in the ONBOARDED_PACKAGE directory
  • ETSI Catalog Manager stores the vendor package zip files from the ONBOARDED_PACKAGE directory
  • SVNFM/NFVO extracts the vendor package zip/CSAR files with package validation
ETSI Package Validation
  • VNF SDK will support SOL004 VNF package pre-onboarding for validation - optional
  • VNF SDK will support SOL007 NS package pre-onboarding for validation - optional

Epic and User Story

Epic

User Story

Description

Guilin Plan?

JIRA

Onboard 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

SDC-2610 - SDC supports ETSI Package management onboarding, mapping and distribution and package security for SOL004 and SOL007 OPEN


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

SDC-2617 - Getting issue details... STATUS


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

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. 

Yes

SDC-2801 - Getting issue details... STATUS


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)

Yes

SDC-2806 - Getting issue details... STATUS


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

SDC-2618 - Getting issue details... STATUS


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

SDC-2612 - Getting issue details... STATUS


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

SDC-2804 - Getting issue details... STATUS

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

SDC-2802 - Getting issue details... STATUS


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

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

  • Create NS and compose NS with its sub components
  • Generate SOL007 NS package
Yes

SDC-2808 - Getting issue details... STATUS


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 VF-C as the NFVO

  • Wrap the NS package in the Service for VF-C
Yes

SDC-2809 - Getting issue details... STATUS


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

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

SDC-2810 - Getting issue details... STATUS

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. 

Yes

SDC-2803 - Getting issue details... STATUS


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 ServiceSupport for onboarding of the SOL007 v2.7.1 compliant NSD package including SOL001 NSD that includes references to other NSDs for composition into ONAP ServiceYes

SDC-2811 - Getting issue details... STATUS

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

SDC-2805 - Getting issue details... STATUS


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
    • Mapping from SOL001 PNFD to SDC AID DM is done
YesDone
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

SDC-2613 - Getting issue details... STATUS


  • 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

SDC-2614 - Getting issue details... STATUS

Support of ETSI Package Validation
VNF SDK will support ETSI package validation for VNF and NSTBD

VNF SDK will support ETSI VNF package pre-onboarding for validationVNF SDK will support ETSI VNF package pre-onboarding for validationTBD

VNF SDK will support ETSI NS package pre-onboarding for validationVNF SDK will support ETSI NS package pre-onboarding for validationTBD

ETSI Package Management Architecture

The diagram depicts the package management architecture. 

  1. SDC supports SOL004 VNF/PNF package onboarding, and stores the original vendor VNF/PNF package inside the SDC package
    1. SOL004 package includes SOL001 VNFD/PNFD
    2. PNF onboarding has been tested
    3. VNF onboarding will be tested in El Alto / Frankfurt
  2. SDC will support SOL007 NS package onboarding and store the original vendor NS package inside the SDC package
    1. NS onboarding will be supported
    2. NS onboarding will be tested
  3. SDC supports VNF/PNF package management interfaces from OSS/BSS via SOL005 Package Management APIs (TBD)
  4. SO supports NS package management interfaces from OSS via SOL005 Package Management APIs (TBD)
  5. ETSI Catalog Manager stores SOL004/SOL007 Packages for other ONAP runtime components such as SO, SOL003/SOL005 Adapters, VFC and others
    1. ONAP-ETSI Catalog Manager will store SOL004 packages for VNF and PNF
    2. ONAP-ETSI Catalog Manager will store SOL007 packages for NS
  6. SOL003 VNFM Adapter provides VNFMs Query/Fetch VNF packages/contents/artifacts, Reading VNFD and subscription/notification services
  7. SOL005 Adapter provides NS/PNF/VNF package management to VF-C/External NFVO by leveraging SOL005 package management APIs


Onboarding

SDC VNF/PNF/NS Onboarding and Distribution

This section describes SDC VNF/PNF onboarding and the End-to-End package distribution from SDC to SVNFM/external NFVOs.

SDC takes the vendor provided package and adds some files or changes files and meta data according to SDC procedure.

SDC VNF/PNF Onboarding Procedure and Original Vendor VNF/PNF Package Handling

  • Enhancement (Ericsson contribution) was made to the SDC Dublin to support SOL004 PNF onboarding with .zip and .csar file extensions.
    • The enhancement can be used for VNF onboarding – it is being tested.
    • 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.

  1. 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
  2. If the file is .csar, it is a package without security.
  3. Next, SDC will check the TOSCA.meta file.
  4. If it contains SOL004v2.?.1 keywords, the package will be handled as SOL004v2.?.1.
  5. Otherwise, it will be handled as existing TOSCA (non-SOL004) package onboarding which will not have the ONBOARDED_PACKAGE artifact.


ETSI SDC Onboarding


Design NS

Design SOL007 NS package

Distribution

ETSI packages will be distributed from SDC to the ETSI Catalog Manager for other ONAP runtime components such as SO (SOL003/SOL005 Adapter) and VF-C.

  • The original vendor package format could be one of the following.
    • Vendor package including certificate and signature (Zip format)
    • Vendor package without certificate and signature (CSAR format)
  • Open Issues:
    1. Distribution of vendor VNF packages with certificates and signatures to SVFNM need to be sorted out.


Package Distribution Components Interactions

The following diagram depicts the ETSI package distribution. 


ONAP ETSI Package Management - Guilin

 

ETSI Package Distribution Flows


OSS_BSS OSS_BSS SDC SDC ONAP_ETSI_Catalog_Mgr ONAP_ETSI_Catalog_Mgr SOL003_Adapter SOL003_Adapter SOL005_Adapter SOL005_Adapter VNFM VNFM VFC VFC Ext_NFVO Ext_NFVO 1Vendor SOL004/SOL007 package onboarding,including SOL001 2onboard SOL004/SOL007 package and put the vendor packageinto the ONBOARD_PACKAGE directory 3register for SDC notification 4send a notification for SDC CSAR with the original vendor CSAR/Zip 5query the SDC CSAR with the SDC CSAR id 6extract SOL004/Sol007 package CSAR/Zip from the SDC CSARand store it VNF PACKAGE TO SVNFM 7send a notification to SOL003_Adapter 8send a notification 9query for a VNF package 10query for a VNF package 11send a VNF package 12sends a VNF package VNF PACKAGE TO Ext NFVO 13send a notification to SOL005_Adapter 14send a notification 15query for a VNF/PNF/NS package 16query for a VNF/PNF/NS package 17send a VNF/PNF/NS package 18sends a VNF/PNF/NS package VNF PACKAGE TO VFC 19send a notification to SOL005_Adapter 20send a notification 21query for a VNF/PNF/NS package 22query for a VNF/PNF/NS package 23send a VNF/PNF/NS package 24sends a VNF/PNF/NS package

SDC SOL004/SOL007 VNF Package Security

Among the SOL004/SOL007 VNF package security options, the SDC supports the option2 as depicted below. In the option 2, there are two ways to zip the VNF packages, and SDC supports both.

SDC validates the VNF packages based on the embedded signature and certificate by leveraging CA.

  • Vendor SOL004/SOL007 VNF Package with certificate and signature is onboarded into SDC
    • ZIP-format VNF package includes CSAR, Signature and Certificate
  • SDC validates VNF package based on the certificate and signature
  • SDC generates SDC internal model plus the vendor SOL004/SOL007 package CSAR and ZIP (with certificate and signature) – the supported format is TBD based on the security requirement


Package Security

A VNF package uses the signature and certificate to ensure package integrity and validity. A CSAR file is digitally signed with the VNF provider private key. During the VNF package onboarding to SDC, SDC validates the package and then does the following:

  • Transform SOL001-based VNFD into SDC internal models
  • Store the original Vendor package into the ONBOARDED_PACKAGE directory
    • If the original vendor package is a zip file with signature and certificate, the ONBOARDED_PACKAGE directory will contain the zip file. 
  • VNFM and VF-C will receive the zip-format file.
  • For Frankfurt, the SVNFM and external NFVO will receive a zip-format package with signature and certificate if the original vendor package contains signature and certificate.
    • SVNFM and NFVO will unzip the incoming zip package files and extract CSAR files from the zip package files without validation.
    • After the Frankfurt release, it is assumed that SVNFM and NFVO validate the incoming packages based on signature and certificate.


  • No labels