Declined by TSC as a stand-alone project. Recommended as a component of Service Design & Creation Project

Project Name:

• Proposed name for the project: ONAP Runtime Catalog
• Proposed name for the repository:  RTCatalog rtc

Project description:

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

• Problem Resolved
  Image Removed
  Image Added
  
  
  • Benefits

• • • Separation of concerns – Model Design  vs. Runtime Using
    • Simplification of Design time to Runtime model distribution
    • Flexibility by allowing runtime component’s self-define model view & data subscription
    • Consolidation of Runtime Data storage and management

Scope:

• • Management Objects:

     

• E2E Service (templates, workflow, recipes, ……)
• NS (templates, workflow, recipes, ……), WAN (templates, workflow,….)
• VNF(VNF image, templates, scripts, recipes,……), PNF(….), ……
• Functions:
• provide catalog management, including design time catalog synchronization, upload, enable, disable, update, delete catalog operations in the Run-Time
• provide catalog relation management among different components
• 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

• •     All Certified Design Model

          Consistent definitions with SDC Design Catalog

• 
  

• • •  Functions:

      
      

      • Provide RT-catalog GUI, storage and management functions, including CRUD, distribution, synchronization, enable, disable, etc

      • Provide RT-catalog view distribution for RT component, including RT component self-composed views, subscriptions, and data access
      • Provide RT-catalog data status & Tracking
      • Provide search capacity for fast access across run-time catalog data
      • Provide portal for the Human Interface
      • Provide S3P related capacity for RT-Catalog

Architecture Alignment:

Image Modified

• How to Cooperate between DT-catalog and

  RT-

  catalog

  Catalog 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
• RT-Components(UI\SO\VFC\APPC\Policy\.......)
• Common service(MSB/DMaaP/Parser.....)
  
  

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, DjangoInterfaces 
• Integration Testing
• etc.

Other Information:

link to seed code (if applicable)

Vendor Neutral

• if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?

Meets Board policy (including IPR)

Use the above information to create a key project facts section on your project page

...

Release Components Name:

Note: refer to existing project for details on how to fill out this table

Resources committed to the Release:

...