Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Use 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 ONAP-ETSI Catalog management
    • VFC Catalog Manager will be migrated as a common component, ETSI Catalog Manager Hereinafter, it is called as "ETSI Catalog Manager"
    • ETSI Catalog Manager will be enhanced to handle the vendor package in the ONBOARDING_PACKAGE directory.
  1. VF-C ETSI Catalog DB Microservice
  • Database: nfvocatalog (vfc-nfvo-catalog-createdb.sql // create db scripts)      // vfc prefix should be generalized
  • Database Table (vfc-nfvo-catalog-createobj.sql // create tables scripts) .         // vfc prefix should be generalized
  • Catalog_NSPackage
  • Catalog_VNFPackage
  • Catalog_PNFPackage
  • Catalog_SoftwareImageModel

2.VF-C Catalog (API) Microservice / ETSI Catalog (API) Microservice

  • vfc-catalog dockerdocker                 // vfc prefix should be generalized
  • ETSI Catalog REST VFC Catalog REST APIs
    • The following APIs are part of VF-C Swagger REST APIs. For the complete ApIs, https://docs.onap.org/en/latest/_downloads/0fea611e8b07fb4042e1a66ce202898c/CATALOG_API_Specification_v1.json

      NS Package Management

      VNF Package Management

      PNF Management

      •GET /nspackages                             // query NS package info

      •POST /nspackages                           // NS package distribute / create

      •GET /nspackages/{csarId}              // query NS package info

      •DELETE /nspackages/{csarId}        // delete NS package

      •GET /vnfpackages                        //query vnf package info

      •POST /vnfpackages                      // vnf package distribute / create

      •GET /vnfpackages/{csarId}         // query vnf package info

      •DELETE /vnfpackages/{csarId}   // delete vnf package

      •PUT /vnfpackages/{csarId}.        // create/upload vnf package

      •GET /pnf_descriptors

      •POST /pnf_descriptors

      •GET /pnf_descriptors/{pnfdInfoId}

      •DELETE /pnf_descriptors/{pnfdInfoId}

      Model Parsing

      Job Management (used for async LCM)

      More…

      •POST /parsernsd                             // NS package model

      •POST /parservnfd                            // VNF package model

      •GET /jobs/{jobId}                         // Job Status

      •POST /jobs/{jobId}                       // Update Job Status


...

  • SDC Stores Service models/templates into the existing SO Catalog DB, and ETSI 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.
  • Deployment location of ONAP-ETSI Catalog Manager microservices is under discussion.
  • SO and other ONAP run-time components could leverage the ONAP-ETSI Catalog Manager function, as a common service.

Gliffy Diagram
nameSDC-SO SDC Controller-ETSI Catalog Manager2
pagePin13

...