...
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
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, not touching the specific attribute or objects analysis, such as the service attribute or NS attribute,... etc ,which belong to RT-Components.
...
- What other ONAP projects does this project depend on?
- SDC(DT-Catalog)
- Parser
- RT-Components(UI\SO\VFC\APPC\Policy\.......)
- Common service(MSB/DMaaP/.....)
- 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.
...