...
- SDC Stores Service models/templates into the existing SO Catalog DB, and ETSI Catalog will be stored in the ETSI Catalog Manager database.
- Note: the ETSI Catalog Manager function could be realized by the VFC (or equivalent) ETSI Catalog API and 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 ETSI Catalog Manager function, as a common service.
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
SDC - SO SDC Controller - ETSI Catalog Manager
...
- SO SDC Controller module (ASDCController and ToscaResourceInstall) needs to be updated for handling SOL004 packages including SOL001 VNFD and PNFD.
- Service-level catalog and other non-ETSI catalog (SDC AID DM) will be stored in SO Catalog DB.
- VNF/PNF/NS-level catalog handling would be simplified:
- By using the ETSI Catalog Manager, ETSI VNF/PNF/NS-level catalogs (i.e., original vendor packages) will be stored in ETSI Catalog DB
- SO itself does not need to manage ETSI-based VNF LCM; i.e., delegates the LCM to VNFM through the SOL003 VNFM Adapter
- In Frankfurt, VNF package management is the first focus.will be supported.
- The following diagram depicts the component interactions for VNF Package store for ONAP runtime.
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
- ETSI Catalog Manager POST API will be used to store the VNF packages
- POST /api/catalog/v1/vnfpackages // passing csarId, vimIds and labVimId
- Q&A:
- How does VFC handle VNF packages from SDC? Does it use SDC AID DM? Does it use VF-Modules?
- Answer:
- VF-C supports SDC internal models with the original vendor package and ETSI-based VNF package
- Currently, no VF-Module support from VF-C and SOL003 VNFM Adapter
- VF-Module mapping and handling need to be sorted out.
...