...
| View file | ||||
|---|---|---|---|---|
|
SOL007 Design and SOL004 Onboarding
- SDC takes the vendor provided package and adds some files or changes files and meta data according to SDC procedure.
- SDC NS/VNF/PNF Onboarding Procedure and Original Vendor VNF/PNF Package Handling
- SDC onboarding enhancement was made to the SDC Dublin to support SOL004 PNF/VNF onboarding with .zip and .csar file extensions. We continue to support the current onboarding mechanism with some enhancements.
- SOL007 NS onboarding (stretch goal for Guilin) will follow the same procedure; i.e., storing the vendor SOL007 NS package into the “ETSI_PACKAGE” directory.
- SOL007 NS design will allow users to build SOL007 NS package including SOL001 NSD from scratch
- SDC VSP and Resource csar files have the “ETSI_PACKAGE” directory, which will contain the original vendor VNF/NS/PNF package.
- The “ONBOARDED_PACKAGE” directory name will be changed to “ETSI_PACKAGE” as a common ETSI directory name. This change is necessary to support design of SOL007 package
- ONAP-ETSI Catalog Manager will be extracted the ETSI packages from the “ETSI_PACKAGE” directory.
- The VNFM and external NFVO use the original vendor VNF/NS/PNF packages through ETSI Catalog Manager.
- SDC provides mapping from ETSI SOL001 NSD/VNFD/PNFD (PNF in the future) to SDC AID DM
- See the subsequent slides for mapping.
- Note: ETSI 2.7.1 handling will be discussed separately.
SDC CSAR for NS structure
ONAP Service CSAR
|-- Artifacts
|-- ETSI_PACKAGE
|-- etsi nsd csar
|-- <VF 1>
|-- Deployment
|-- ETSI_PACKAGE
|-- etsi vnf package
...
|-- <VF n>
|-- Deployment
|-- ETSI_PACKAGE
|-- etsi vnf package
Mapping of ETSI Information NS-related Elements with TOSCA types
...