Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
outlinetrue

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:  RT-Catalog rtc

Project description:

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

      Catalog Presentation Slide

...

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

In the Run-Time,  it is hard to manage the catalog in a unified way among runtime components.

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

Image Removed

Architecture Alignment:

  • How does this project fit into the rest of the ONAP Architecture?Please Include architecture diagram if possible
    Image RemovedImage 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

Scope:

      • Management Objects:

              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 Added

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

...

Facts

Info

PTL (first and last name)Maopeng zhang
Jira Project NameRun-Time Catalog
Jira KeyRTC
Project IDrtc
Link to Wiki Space

Release Components Name:

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

Components Name

Components Repository name

Maven Group ID

Components Description

catalog managerrtc/catalog-managerorg.onap.rtc.catalog-managerRT-catalog data model management
catalog distributionrtc/catalog-distibutionorg.onap.rtc.catalog-distibutionRT-catalog data model distribution to RT components
catalog modelsyncrtc/catalog-syncorg.onap.rtc.catalog-syncRT-catalog data model synchronization from SDC catalog
catalog portalrtc/catalog-portalorg.onap.rtc.catalog-portalRT-catalog model management and distribution portal for operator
catalog storagertc/catalog-storageorg.onap.rtc.catalog-storageRT-catalog certified model storage

Resources committed to the Release:

...

Committers
sa2785@att.com

Role

First Name Last Name

Linux Foundation ID

Email Address

Location

Role

First Name Last Name

Linux Foundation ID

Email Address

Location

PTL

AGRAHARAM,SANJAY

Maopeng Zhang
zhang.maopeng1@zte.com.cnBeijing, China. UTC +8
Committers

Fengyuanxing


feng.yuanxing@zte.com.cn

Beijing, China. UTC +8

Yueliang Liu

liuyueliang@chinamobile.com

Beijing, China. UTC +8

Zhanjie


zhang.jie1@zte.com.cn

Beijing, China. UTC +8

Maopeng Zhangzhang.maopeng1@zte.com.cnBeijing, China. UTC +8

AGRAHARAM,SANJAY


sa2785@att.com

US, EST

David Shadmi


David.shadmi@att.com

CST

Michael Lando


Michael.lando@att.com

Israel





ContributorsLuji

lu.ji3@zte.com.cn

Beijing, China. UTC +8

Shijie


shi.jie3@zte.com.cn

Beijing, China. UTC +8

Qidi Lv

lvqidi@chinamobile.com

Beijing, China. UTC +8
pengpeng
peng.peng@zte.com.cnBeijing, China. UTC +8

Ting Lu


Tingting.lu@att.com

US, EST