Versions Compared

Old Version 58

changes.mady.by.user Byung-Woo Jun

Saved on

compared with

New Version Current

changes.mady.by.user Byung-Woo Jun

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • ETSI Package Onboarding and Distribution
    • SOL004 VNF/PNF Package includes SOL001 VNFD/PNFD with the original vendor package will be distributed from SDC to SVNFM/External NFVO.
    • SOL007 NS Package includes SOL001 NSD with the original vendor package will be distributed from SDC to External NFVO.
    • SOL003 and SOL005 Package Management APIs will be used for the distribution.
    • SOL004 VNF/PNF Package Security will be supported by the package signature and certificate.
    • SOL007 NS Package Security will be supported by the package signature and certificate
  • ETSI Package Pre-onboarding validation
    • VNF SDK will support SOL004 VNF package pre-onboarding
    • VNF SDK will support SOL007 NS package pre-onboarding 

Feature Descriptions

Feature

Description

ETSI Package Management
  • SOL004 VNF/PNF Package includes SOL001 VNFD/PNFD with the original vendor package will be distributed from SDC to SVNFM/External NFVO.
  • SOL007 NS Package includes SOL001 NSD with the original vendor package will be distributed from SDC to SVNFM/External NFVO.
  • SOL003 and SOL005 Package Management APIs will be used for the distribution.
    • SOL003/SOL005 Adapters passes vendor packages to SVNFM/NFVO
ETSI Package Security

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

  • SOL004 VNF/PNF Package security will be supported by the package signature and certificate
  • SOL007 NS Package security will be supported by the package signature and certificate
  • SDC will store the vendor package with signature and certificate in a zip format in the ONBOARDINGONBOARDED_PACKAGE directory.
  • SO stores ONBOARDINGONBOARDED_PACKAGE zip files in the ONAP-ETSI Catalog DB through ONAP-ETSI Catalog Manager APIs.
  • SVNFM/NFVO extracts the CSAR file from the vendor package 
    • For Frankfurt, extracting the CSAR without validation is allowed
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

Frankfurt?JIRA
Support ETSI Package Management onboarding and distribution


SDC supports ETSI package management (onboarding and distribution) and package securityYesPartially Done

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2610


SDC supports onboarding of the SOL004 VNF package includes SOL001 VNFD

  • VNFD onboarding is testing in El Alto, and its regression testing will be done
  • SOL004 VNF package onboarding is tested in El Alto
    • Further testing is necessary in Frankfurt
    • Mapping from SOL001 VNFD to SDC internal TOSCA template
    • Mapping from SOL001 VNFD to SDC AID DM is under consideration
YesNo

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2611


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

SDC supports onboarding of the SOL007 NS package includes SOL001 NS
  • SOL007 NS package onboarding will be supported
    • Mapping from SOL001 NSD to SDC internal TOSCA template needs to be done
    • Mapping from SOL001 NSD to SDC AID DM is under consideration
YesNo

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2612


SDC VSP and Resource CSAR files include the original vendor package

  • This is done in Dublin and its regression testing will be done
  • Storing the original vendor package in the SDC CSAR is done
YesDone

The vendor package will be distributed from SDC to SVNFM/External NFVO

  • The vendor package will be stored at the ONAP-ETSI Catalog DB
  • SOL003 and SOL005 Package Management APIs will be used for the distribution
  • SOL003/SOL005 Adapters passes vendor packages to SVNFM/NFVO
  • Refer to the ONAP-ETSI Catalog Manager, SO ETSI Catalog Manager and SOL003/SOL005 Package Management use cases
Yes-

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 Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-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
YesNo

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2614


  • SDC will store the vendor package with signature and certificate in a zip format in the ONBOARDINGONBOARDED_PACKAGE directory.
  • It is done in El Alto
Done-

  • SO stores ONBOARDINGONBOARDED_PACKAGE zip files in the ONAP-ETSI Catalog DB through ONAP-ETSI Catalog Manager APIs.
  • Refer to the ONAP-ETSI Catalog Manager and SO ETSI Catalog Manager use cases
Yes-

  • SVNFM/NFVO extracts the CSAR file from the vendor package 
    • For Frankfurt, extracting the CSAR without validation is allowed
  • SVNFM and External NFVO requirements on how to handle the zip-format packages
    • For Frankfurt, extracting the CSAR file without validation is allowed
Yes-
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. This feature is postponed to the Guilin release
  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. ONAP Runtime components store SOL004 Packages for their operations
    1. For the SO case, SO stores SOL004 packages for VNF and PNF by leveraging the ONAP-ETSI Catalog Manager
    2. For the SO case, SO stores SOL007 packages for NS by leveraging the ONAP-ETSI Catalog Manager
  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

...

Gliffy
nameONAP ETSI Package Management
pagePin1317


  • ETSI Package Distribution Flows

...

  • 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 ONBOARDINGONBOARDED_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 ONBOARDINGONBOARDED_PACKAGE artifact.

SDC SOL004/SOL007 VNF Package Security

...

  • Transform SOL001-based VNFD into SDC internal models
  • Store the original Vendor package into the ONBOARDINGONBOARDED_PACKAGE directory
    • If the original vendor package is a zip file with signature and certificate, the ONBOARDINGONBOARDED_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.

...