...
- SDC Stores Service models/templates into the existing SO Catalog DB, and ETSI Catalog model will be stored in the ONAP-ETSI Catalog Manager database.
- Note: the ONAP-ETSI Catalog Manager function could be realized by the VFC (or equivalent) ONAP-ETSI Catalog API and ONAP-ETSI Catalog DB Microservices - To be discussed further.
- VF-C DB and Catalog are two Microservices, which they can be deployed independently from VF-C, and they don't have dependency with other VF-C components.
- SO and other ONAP run-time components could leverage the ONAP-ETSI Catalog Manager function, as a common service.
...
- ONAP-ETSI Catalog Manager POST API will be used to store the VNF packages
- POST /api/catalog/v1/vnfpackages // passing csarId, vimIds and labVimId
- Operation Requirements
| API Action | Actor | Method | Endpoint URI | Description |
|---|---|---|---|---|
| Store ETSI package | SDC Controller | POST | /api/catalog/v1/vnfpackages | Invoke the ONAP-ETSI Catalog to store SOL004 VNF packages to ONAP-ETSI Catalog DB |
SO Catalog Modelling
- The service database table has TOSCA_CSAR_ARTIFACT_UUID column. We continue to use this column to link the TOSCA CSAR.
- The TOSCA_CSAR database has a logical relationship with Catalog_NSPackage, Catalog_PNFPackage and Catalog_VNFPackage.
- When a record is entered in the TOSCA_CSAR,
- if the CSAR artifact type is NS, add a NS package into Catalog_NSPackage
- if the CSAR artifact type is VNF, add a VNF package into Catalog_VNFPackage
- if the CSAR artifact type is PNF, add a PNF package into Catalog_NSPackage
- When a record is entered in the TOSCA_CSAR,
- For the SOL004 VNF onboarding into SO,
- SO does not populate data info the VF-Module database table if the VF-Module is not populated in the modeling.
- It depends on the SOL001 VNFD mapping to SDC AID DM whether it populates VF-Modules or not.
- SO does not populate data into the HEAT-Template database table
- Heat-Template is part of the VNF package
- SO invokes the ONAP-ETSI Catalog Manager APIs with the CSAR UUID.
- ToscaResourceInstaller (InstallTheVfResource, InstallThePNFResource) will be modified to invoke the ONAP-ETSI Catalog Manager.
- Note: the NS use case needs to be defined since SDC does not support SOL007 (NS Package) yet.
- The ONAP-ETSI Catalog Manager receives VNF packages and stores them into the ONAP-ETSI Catalog Database Catalog_VNFPackage
- It stores the VNF package as a whole and its APIs can extract the VNFD, artifacts, softwareImage, etc.
- SO does not populate data info the VF-Module database table if the VF-Module is not populated in the modeling.
...
- Need to pass artifacts (images) to VIM thru the Adapter
- Get the original vendor VNF package
- Retrieving VNFD for SOL003 Adapter
- Retrieving NSD/VNFD for SOL005 Adapter
- GET /nspackages/{csarId} // query NS package info
- More SOL005 Adapter requirements are being collected.
- Operation Requirements
API Action Actor Method Endpoint URI Description Query ETSI VNF package SOL003 Adapter GET /api/catalog/v1/vnfpackages/{csarId}
Invoke a SOL004 VNF package from ONAP-ETSI Catalog Query ETSI NS Package
SOL005 Adapter GET /nspackages/{csarId} Query NS Package info from the ONAP-ETSI Catalog