Page History

...

• • SDC VNF SOL001/SOL004 Support

    • VNFM Adapter depends on the following SDC capabilities:

      • SOL004-based VNF CSAR package onboarding, including storing the original VNF package in SDC output.
      • Manual onboarding of VNF package thru SDC UI.
      • Mapping VNFD (SOL001) to SDC AID DM, including VF-Module deduction based on ScaleAspect + Delta
      • SDC TOSCA Parser for SDC/ONAP Internal model
      • TOSCA Parser for SOL001
      • VNF SDK support of VNF package verification
    • SDC support scope for VNF SOL001/SOL004 is under discussion (Ericsson, Nokia contribution)
    • In Dublin, SDC does not support SOL004 VNF package fully. 
      • The SDC package structure support is not flexible and requires proprietary convention. 
      • SDC limitations and restrictions have been identified and under discussion for the El Alto release.

• CSAR Import, Store and Retrieve Sequences 

  • SDC stores the original vendor VNF package along with the transformed ONAP-compliant package.
    • Note: this will not supported SDC Dublin.
  • SO uses SDC-transformed CSAR packages and VNFM Adapter uses the original Vendor CSAR package.

  ...

  • • • Note: since SDC Dublin does not support the original vendor CSAR package, SO VNFM Adapter will retrieve VNFDs from SDC.
      • For that reason, the following steps 1, 2, 3 and 4 have been simplified and adjusted.

  Image Added

  • 
    

    • Design 

  Note 1: the following design will be completed in the El Alto release. For Dublin, the steps 2 and 3 are not used, and the step 4 will be used to retrieve VNFDs from SDC

  Note 2: the step 1 is not important for SO VNFM Adapter in Dublin since the Adapter will get VNFD from SDC directly. 

  • 1. SO SDC Controller gets a SOL004 VNF package with an SOL001 VNFD (for El Alto)
       1. SDC could generate two output: one ONAP-compliant CSAR and one original CSAR (maybe the first file includes the second one)
       2. SO will use the ONAP-compliant CSAR
       3. VNFM Adapter will use original CSAR
    2. SO SDC Controller stores a VNF CSAR file reference to the SO Catalog DB (e.g., TOSCA_CSAR database table) - for El Alto
    3. VNFM Adapter gets a CSAR package URL from the SO TOSCA_CSAR database table - for El Alto
    4. VNFM Adapter gets an original CSAR package file from the SDC repository
       1. It is assumed that the Adapter retrieves the original vendor provided CSAR package from SDC repository directory before it passes the package to SVNFM, where SVNFM handles the original CSAR. For that, SDC copy the full original package.
       2. There would be two CSAR packages for a service: one original package, one SDC transformed package.
       3. VNFM Adapter passes the original CSAR package to SVNFM because the SVNFM is outside of ONAP and is designed to handle the vendor CSAR package.

  Note: SO future release could consider SOL001/SOL004 internal representation in its Catalog DB, or using the Run-time Catalog DB

  • Design

  ...

  
  

  • VNFM Adapter VNF Flow Design (Run-time Scenarios)

    • The following diagram depicts VNF flow design.

  ...