Versions Compared

Key

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

...

     The ONAP RT-Catalog project aims to provide unified catalog management in ONAP runtime environment.

      

  • Problem Resolved
    Image RemovedImage Added

Scope:

    • Management Objects: 

    • E2E Service (templates, workflow, recipes, ……)
    • NS (templates, workflow, recipes, ……), WAN (templates, workflow,….)
    • VNF(VNF image, templates, scripts, recipes,……), PNF(….), ……
    • Functions:

    • provide
    • •Provide catalog storage of models, model instances and execution logs
      •provide catalog management operations, including

    • design time catalog
    • synchronization,

    • upload,
    • enable, disable, update, and delete

    • catalog operations in the Run-Timeprovide
    • etc.
      •provide catalog relation management among different catalog objects
      •Provide catalog relation management among different ONAP runtime components

    • Provide
    • •Provide catalog status management

    • in the run-time, such as IN_USE, NOT_IN_USE, ENABLED, DISABLED, etc
    • Provide packages or artifact files downloading for External Systems
    • Provide TOSCA model and instance model query for all RT-components via integration with parser

    • •Provide search capacity for fast access across run-time catalog models and instances
      •Provide portal for the Human Interface
      •Provide S3P related capacity for RT-Catalog

Architecture Alignment:

  • How to Cooperate between DT-catalog and RT-catalogCatalog architecture
    Image Removed

    What’s Differences Between DT-catalog and RT-catalog

    Items

    SDC DT Catalog

    RT Catalog

    Users or Roles

    Designers

    Operators

    S3P requirements

    Low

    Strong

    Operations

    onboard/check out/check in/distribute/....

    Sync/upload/enable/disable/update/delete/.....

    Status 

    check in/check out/draft/...

    in_use,  not_in_use, enable, disable,....

    Storage

    Bind to the SDC designer studio

    Graph DB

    Distributed among DCs(Global RTC/Local RTC)

    Files & packages

    TOSCA Instance model

    Input

    SDC Design Model message

    (type schema, type, template, etc)

    TOSCA CSAR Packages

    Output

    TOSCA Packages for Runtime

    TOSCA instances via parser and inputs



    RT-Catalog architecture
    Image Removed
    Image Added


  • RT-Catalog Storage

Image Added


  • What other ONAP projects does this project depend on?
    • SDC(DT-Catalog)
    • Parser
    • Common service(MSB/DMaaP/.....)

  • How does this align with external standards/specifications?
    • APIs/Interfaces - REST/PubSub
    • Information/data models - Swagger JSON
       
  • Are there dependencies with other open source projects?
    • APIs/Interfaces - mysql, Django
    • Integration Testing
    • etc.

...