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.

       View filenameONAP Runtime Catalog Proposal (1).pptxheight400

• Problem Resolved
  Image Added
  
• vDesign time catalog

SDC now support the VNF package onboard, and NS design. After the VNF package onboard and design, the packages will be categorized and put into the SDC catalog.  SDC catalog also supports the package status of design time, such as check in/ check out/ in design/Ready for testing/in testing/Certified/distributed.

• • vRun-Time in R1

In Run-Time,  there exists template and recipes, workflows in different components(SO, VFC,  SDNC,  APPC, Policy, …). 

•SO consumes service template and workflow
•VFC consumes network service and VNF template and workflow 
•policy consumes service/network/VNF rule recipes 
•……

• • vLack of unified catalog management in the Run-Time

...

• 
  
  • 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 API to fetch the packages or files in the catalog, including the external system, and inner components
Provide API to consume the descriptor parser result, reducing the package download time consuming between the different components.

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

• RT-Catalog architecture
  

...

• 
  Image Added
  
  
  
  
  

• RT-Catalog Storage

                Image Added

What other ONAP projects does this project depend on?

• SDC(DT-Catalog)
• Multi-VIM
• AAI/ESR
• MSB/DMaaP
• Model
• OOM
Integration
• 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:

...