...
| Drawio | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Participant Name | Functional purpose | PoC handling |
|---|---|---|
| YANG Model parser | Converts YANG models into java objects | Required |
| YANG Data parser | Converts data compliant with a YANG model into java primitives, assists the CPS core | Required |
| Model store | Keeps a local cache of the structures and relationships (generated from the YANG models) required by the CPS | Required |
| SDC Model loader | Subscribes to DMaaP for CSAR publication. Parses and extracts the models from the CSAR and gives them to the mirror servicexNF Model Data Proxy | Not required |
| Topology sync | Does initial sync and maintains an up to date view of the active topology state. Informs the mirror service of any changes | Not requiredMirror service |
| xNF Model Data Proxy | Encapsulation of all model and data access that relates to xNF | Not required |
| Mirror xNF Proxy Data access | REST interface that provides access to xNF data | Not required |
| CPS Core | Provides validation of and access to data. Is agnostic to the DB technology and schema | Required |
| CPS Data access | Provides REST CRUD access to the data | Required |
| CPS notification | Provides a DMaaP notification in the event that (1) data is changed and (2) it has been tagged/marked for notifcation | Required for stretch |
| PostgreSQL plugin | Maps the java primitive representation of the YANG data objects to their DB technology (PostgreSQL) and schema specifics (SQL) | Required |
| PostgreSQL | Database Management System for current data | Required |
| Temporal [Stack] | Placeholder for logical components representing the temporal handling of data | Not required |
| Temporal DB | Database Management System for temporal data | Not required |
...
The CPS will provide a balance between these competing needs.
For more discussion, see: Common information model, Data lake and Access control
Solution
To be useful to an application, data must be accessible and possible to interpret.
...
The key benefits are: (1) Data lake use cases are enabled; (2) Coupling between components a at the level of 'shared' data are explicitly declared/published.
...
The PoC will start with a compatible subset of the above implementation. Noting Nothing in the PoC implementation will preclude the development of the above solution.
All access to data will be via the owning service.
...
Backward compatibility
See decision for more information. Compatibility will be provided by either a dedicated component, or ONAP applications depending on legacy interfaces will be updated. This will depend on resources.
...