...
The ONAP RT-Catalog project aims to provide unified catalog management in ONAP runtime environment.
View file
name | ONAP Runtime Catalog Proposal (1).pptx |
---|---|
height | 400 |
- 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.
- Problem Resolved
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.
Architecture Alignment:
- How to Cooperate between DT-catalog and RT-catalog
What’s Differences Between DT-catalog and RT-catalog
architectureItems
SDC DT Catalog
...
RT Catalog
Users or Roles
Designers
Operators
S3P requirements
Low
Strong
Operations
onboard/check out/check in/distribute/....
Sync/upload/enable/disable/update/delete/.....
Status
check in/check out/draft/...
in_use, not_in_use, enable, disable,....
Storage
Bind to the SDC designer studio
Graph DB
Distributed among DCs(Global RTC/Local RTC)
Files & packages
TOSCA Instance model
Input
SDC Design Model message
(type schema, type, template, etc)
TOSCA CSAR Packages
Output
TOSCA Packages for Runtime
TOSCA instances via parser and inputs
- RT-Catalog architecture
- What other ONAP projects does this project depend on?
- SDC
- Multi-VIM
- AAI/ESR
- MSB/DMaaP
- Model
- OOM
- (DT-Catalog)
- Parser
- Common service(MSB/DMaaP/.....)Integration
- What other ONAP projects does this project depend on?
- 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.
...