...
| Table of Contents |
|---|
PoC Overview Diagram
Topic Areas
| Topic Area | Description |
|---|---|
| MODEL DRIVEN SCHEMA: Relates to Design time activities. SDC operation. Distribution of the CSAR and the Model-driven Schema coming from Design time |
| UPDATE: Takes incoming Standards Defined VES event from DCAE (PNF) and is published on DMAAP |
| SYNCHRONIZATION: C&PS synchronizes to A&AI, which allows it to get the latest view of what is in A&AI and align it with the C&PS data records. |
| SERVICE PROVIDER INTERFACE: The C&PS interface to the DBMS |
| C&PS API: The API that allows other micro-services and other components to access C&PS DB with CRUD operations. |
Scope
TODO
- Select a YANG model for PoC. Needs to be simple, yet drive validation and upgrade. Ideally will have multiple objects/attributes to associate different CPS behavior
Base scope
- Read/write persisted Configuration Management data:
- defined by xNF (simple YANG model), published as YANG
- Models deployed @ runtime with no ONAP platform impacts or LCM events
- Show the benefits in terms of constraint validation, access and upgrade
...
- Automating the ingestion of models from SDC or controller (unless we get to it in the stretch target). The model LCM interface will be exercised manually during the PoC.
- Syncing with A&AI. The PoC will work on a fixed topology
High Level Design
Context of CPS
| draw.io Diagram | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...