Table of Contents outline true
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
- Benefits
- Benefit for the ONAP R2 TOSCA model implementation in RT-time Unified catalog management related to RT-Components for operator
- 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(….), ……
- Provide catalog storage of models, model instances and execution logs provide catalog management operations, including
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
, update,
and delete etc
.Provide catalog status and version management- provide catalog relation management among different catalog objects
- Provide catalog relation management among different ONAP runtime components
- 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
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
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.
Functions:
Architecture Alignment:
RT-Catalog architecture
RT-Catalog Storage
...
Catalog models: storage of certified models
Catalog instances: which instances of which components uses which model in 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.
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
...
Facts | Info |
---|---|
PTL (first and last name) | Maopeng zhang |
Jira Project Name | Run-Time Catalog |
Jira Key | RTC |
Project ID | rtc |
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 manager | rtc/catalog-manager | org.onap.rtc.catalog-manager | RT-catalog data model management |
catalog distribution | rtc/catalog-distibution | org.onap.rtc.catalog-distibution | RT-catalog data model distribution to RT components |
catalog modelsync | rtc/catalog-sync | org.onap.rtc.catalog-sync | RT-catalog data model synchronization from SDC catalog |
catalog portal | rtc/catalog-portal | org.onap.rtc.catalog-portal | RT-catalog model management and distribution portal for operator |
catalog storage | rtc/catalog-storage | org.onap.rtc.catalog-storage | RT-catalog certified model storage |
Resources committed to the Release:
...
Role | First Name Last Name | Linux Foundation ID | Email Address | Location | |
---|---|---|---|---|---|
Role | First Name Last Name | Linux Foundation ID | Email Address | Location | |
PTL | CommittersAGRAHARAM,SANJAY | sa2785@att.comMaopeng Zhang | zhang.maopeng1@zte.com.cn | Beijing, China. UTC +8 | |
Committers | Fengyuanxing | Beijing, China. UTC +8 | |||
Yueliang Liu | Beijing, China. UTC +8 | ||||
Zhanjie | zhang.jie1@zte.com.cn | Beijing, China. UTC +8 | Maopeng Zhang | zhang.maopeng1@zte.com.cn | |
Beijing, China. UTC +8 AGRAHARAM,SANJAY | US, EST | ||||
David Shadmi | CST | ||||
Michael Lando | Israel | ||||
Contributors | Luji | Beijing, China. UTC +8 | |||
Shijie | Beijing, China. UTC +8 | ||||
Qidi Lv | Beijing, China. UTC +8 | ||||
pengpeng | peng.peng@zte.com.cn | Beijing, China. UTC +8 | |||
Ting Lu | US, EST |