Run-Time Catalog

Project Name:

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

Project description:

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

• Problem Resolved
  
  

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

Architecture Alignment:

• How to Cooperate between DT-catalog and RT-catalog
  
  
  
  
  

• 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
  
  
  
  

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

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

Key Project Facts:

Primary contact: zhang.maopeng1@zte.com.cn

Release Components Name:

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

Resources committed to the Release:

Note 1: No more than 5 committers per project. Balance the committers list and avoid members representing only one company.

Note 2: It is critical to complete all the information requested, that we help to fast forward the onboarding process.