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

• • • 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: All Certified Design Model

    Mainly include the following elements:
    
    • Object definitions – templates
    • Recipes – workflows, configurations, Scripts for service delivery & assurance
    • Policy Rules
    • Analysis related Definition
    • Event Collection Definition
• 
  

     Functions:

• 
  
  • • Provide RT-catalog storage and management functions, including CRUD, 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:

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/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, 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.