You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

SO ETSI Catalog DB Support for NS, VNF and PNF

For the ETSI package storage, SO does the following:

  • SO (SDC Controller component) queries the package from SDC
  • SO stores ETSI (including SDC AID DM) + vendor VNF package CSAR or ZIP
    • Not all VNFD needs to be transformed to the SDC AID DM - TBD
  • For Non-ETSI models (Service + Non-ETSI Resource), SO will use the existing SO embedded Catalog DB

Instead of building ETSI Catalog management in SO, SO will leverage the existing ETSI Catalog Manager function.

  • Consideration of leveraging VF-C Catalog Microservices for the NS, VNF and PNF catalog support, https://wiki.onap.org/pages/viewpage.action?pageId=63996543
    • VFC Catalog Manager function consists of two microservices: VF-C DB and VF-C Catalog. Deployment of these microservices is independent of VF-C, and the microservices have no dependency on other VF-C components – a good stepping stone towards common ETSI Catalog management
    • VFC Catalog Manager will be enhanced to handle the vendor package in the ONBOARDING_PACKAGE directory.
  1. VF-C Catalog DB Microservice
  • Database: nfvocatalog (vfc-nfvo-catalog-createdb.sql // create db scripts)
  • Database Table (vfc-nfvo-catalog-createobj.sql // create tables scripts)
  • Catalog_NSPackage
  • Catalog_VNFPackage
  • Catalog_PNFPackage
  • Catalog_SoftwareImageModel

2.VF-C Catalog (API) Microservice


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.
  • 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.


ETSI Catalog Manager - SOL003/SOL005 Adapter

  • ETSI Catalog Manager consists of two microservices:
    • ETSI Catalog API
    • ETSI Catalog DB
  • ETSI Catalog Manager provides RESTful services to Adapters:
    • ETSI package management for the Adapters.
      • GET /api/catalog/v1/vnfpackages/{csarId}

      • Need to pass artifacts (images) to VIM thru the Adapter
      • Get the original vendor VNF package
        • ETSI Catalog APIs will be enhanced to extract the original vendor VNF package from the ONBOARDING_PACKAGE directory
        • Does the vendor original package include VNF software image or path?
    • 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.
  • No labels