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 RemovedBenefits
• 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
  •    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 base on the tosca grammar
not touching the specific attribute or objects analysis, such as the service attribute or NS attribute,... etc ,which belong to RT-Components.


• • All Certified Design Model

          Consistent definitions with SDC Design Catalog

• 
  

• • •  Functions:

      
      

      • Provide RT-catalog GUI, storage and management functions, including CRUD, distribution,

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 tracking which ONAP component is using which model
• • • • 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 catalog status and version management
• • • • Provide search capacity for fast access across run-time catalog
models and instances
• Provide API to let RT-components consume package, artifacts, and model instances
                Note: using API to get package or Model instances is decided by the PTL of RT-components. 
• • • • data
      • Provide portal for the Human Interface
      • Provide S3P related capacity for RT-Catalog

Architecture Alignment:

• RT-Catalog architecture
  

  Image Removed

  
  Image Added
  
  
  
  
  

• RT-Catalog Storage

...

                         Catalog models:       storage of certified models

                         Catalog instances:  which instances of which components uses which model at what time.

                                                             Model status, such as update, enable,disable,....

                                                             Model instance: model parsed results via model template and inputs

                                                               for example:

                                                                     There is a service TOSCA template, which needs some inputs parameters.

                                                                      When operator uses it to deploy A service with TOSCA template and input A,  the parser will generate TOSCA instances A  for A service.

                                                                      When operator uses it to deploy B service with TOSCA template and input B,  the parser will generate TOSCA instances B for B service.

                         Execution Logs:       Log the transaction between other components, including important operation log of portal, SDC, and RT-components.

  Image Added

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, 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:

...

Resources committed to the Release:

...