...
- ETSI Package Onboarding and Distribution
- SOL004 VNF/PNF /NS 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.
- 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 /NS 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.
- SOL003/SOL005 Adapters passes vendor packages to SVNFM/NFVO SVNFM/NFVO extracts the CSAR files file from the vendor packages 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 |
ONAP
| SDC supports ETSI package management (onboarding and distribution) and package security | Partially Done | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDC-2610 |
---|
|
|
| SDC supports onboarding of the SOL004 VNF package includes SOL001 VNFD |
SOL004 VNF/PNF/NS Package includes SOL001 VNFD/PNFD/NSD with the original vendor package - 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
| No | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDC-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
| Yes | Done |
| 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
| No | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDC-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
| Yes | Done |
| 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 | |
support . | 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
| No | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SDC-2614 |
---|
|
|
| - SDC will store the vendor package with signature and certificate in a zip format in the
|
ONBOARDING- ONBOARDED_PACKAGE directory.
| | Done | - |
| |
ONBOARDING- ONBOARDED_PACKAGE zip files in the ONAP-ETSI Catalog DB through ONAP-ETSI Catalog Manager APIs.
|
SOL003/SOL005 Adapters passes vendor packages to SVNFM/NFVO- Refer to the ONAP-ETSI Catalog Manager and SO ETSI Catalog Manager use cases
| Yes | - |
| - SVNFM/NFVO extracts the CSAR
|
files packages - 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 NS | TBD |
|
| VNF SDK will support ETSI VNF package pre-onboarding for validation | VNF SDK will support ETSI VNF package pre-onboarding for validation | TBD |
|
| VNF SDK will support ETSI NS package pre-onboarding for validation | VNF SDK will support ETSI NS package pre-onboarding for validation | TBD |
|
ETSI Package Management Architecture
...
- SDC supports SOL004 VNF/PNF package onboarding, and stores the original vendor VNF/PNF package inside the SDC package – Ericsson contribution in Dublin
- SOL004 package includes SOL001 VNFD/PNFD
- PNF onboarding was has been tested
- VNF onboarding is being will be tested in El Alto / Frankfurt
- SDC will support SOL007 NS package onboarding and store the original vendor NS package inside the SDC package
- NS onboarding will be supported
- This feature is postponed to the Guilin release
- SDC supports supports VNF/PNF package onboarding and/or accepts VNF/PNF package management interfaces from OSS/BSS via SOL005 Package Management APIs (TBD)
- SO supports NS package management interfaces from OSS via SOL005 Package Management APIs (TBD)
- ONAP Runtime components store SOL004 Packages as neededfor their operations
- For the SO case, SO stores SOL004 packages for NS, VNF and PNF by leveraging the ONAP-ETSI Catalog Manager
- For the SO case, SO stores SOL007 packages for NS by leveraging the ONAP-ETSI Catalog DB microservicesManager
- SOL003 VNFM Adapter provides VNFMs Query/Fetch VNF packages/contents/artifacts, Reading VNFD and subscription/notification services
- SOL005 Adapter provides NSD/PNFD management and SOL005 VNF package management
- SOL007 (NS package) support is under discussion.
- To simplify the package distribution and storage, the Runtime Catalog Manager is suggested for the future.NS/PNF/VNF package management to VF-C/External NFVO by leveraging SOL005 package management APIs
Gliffy Diagram |
---|
name | ONAP ETSI Package Management |
---|
pagePin | 617 |
---|
|
- ETSI Package Distribution Flows
PlantUML Macro |
---|
|
@startuml
participant OSS_BSS
participant SDC
participant SO
participant ONAP_ETSI_Catalog_Mgr
participant SOL003_Adapter
participant SOL005_Adapter
participant VNFM
participant VFC
participant Ext_NFVO
autonumber
OSS_BSS -> SDC : Vendor SOL004/SOL007 package onboarding,\nincluding SOL001 VNFD
group VNF PACKAGE TO SVNFM
SDC -> SO : ONAP internal package with the \noriginal vendor CSAR/Zip
SO -> ONAP_ETSI_Catalog_Mgr: store ONAP internal package \nwith the original vendor CSAR/Zip invoke ETSI Catalog Manager, passing
ONAP_ETSI_Catalog_Mgr -> SDC : query the SDC CSAR with the SDC CSAR id
ONAP_ETSI_Catalog_Mgr --> ONAP_ETSI_Catalog_Mgr : extract SOL004 package CSAR/Zip from the SDC CSAR \nand store it
ONAP_ETSI_Catalog_Mgr -> SOL003_Adapter : retrieve the original vendor CSAR/Zip
SOL003_Adapter -> VNFM : forward the original vendor CSAR/Zip
end
group VNF PACKAGE TO Ext NFVO
SDC -> SO : ONAP internal package with the original vendor CSAR/Zip
SO -> ONAP_ETSI_Catalog_Mgr : store ONAP internal package with the original vendor CSAR/Zip
ONAP_ETSI_Catalog_Mgr -> SDC : query the SDC CSAR with the SDC CSAR id
ONAP_ETSI_Catalog_Mgr --> ONAP_ETSI_Catalog_Mgr : extract SOL007 package CSAR/Zip from the SDC CSAR \and store it
ONAP_ETSI_Catalog_Mgr -> SOL005_Adapter : retrieve the original vendor CSAR/Zip
SOL005_Adapter -> Ext_NFVO : forward the original vendor CSAR/Zip
end
group VNF PACKAGE TO VFC
SDC -> VFC : ONAP internal package with the original vendor CSAR/Zip
end
@enduml |
...
- 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.
...
- At onboarding, SDC checks the file extension and performs the following procedures
- If the file is .zip, SDC unzips
- If it has .cert & .cms, it is a package with security and security validation will be performed.
- 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.?.1 keywords, the package will be handled as SOL004v2.?.1.
- 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
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
...
- 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 release, VNFM and VF-C will unzip the file and take the CSAR file from the zip file without validationthe 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.