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
  
• Benefits
  •    Benefit for the ONAP R2 TOSCA model implementation in RT-time
  •    Unified catalog management related to RT-Components  for operator
    

Scope:

• Management Objects: 

  • E2E Service (templates, workflow, recipes, ……)
  • NS (templates, workflow, recipes, ……), WAN (templates, workflow,….)
  • VNF(VNF image, templates, scripts, recipes,……), PNF(….), ……
    
    Note: provide common package and artifact and common information model, not touching the specific attribute or objects analysis, such as the service attribute or NS attribute,... etc ,which belong to RT-Components.
    
    

• Functions:
  • Provide catalog storage of models, model instances and execution logs
  • provide catalog management operations, including synchronization, enable, disable, update, and delete etc.
  • provide catalog relation management among different catalog objects
  • Provide catalog relation management among different ONAP runtime components
  • Provide catalog status and version management
  • 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:

• RT-Catalog architecture
  
  
  
  
  
  

• RT-Catalog Storage

• What other ONAP projects does this project depend on?
  • SDC(DT-Catalog)
  • RT-Components(UI\SO\VFC\APPC\Policy\.......)
  • 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.