...
**Configuration Management FUNCTIONS** - Enables OSS configuration, optimization, and LCM operations.
**TOPOLOGY TRAVERSAL** - It will enable the ability for something to traverse the relationship between data elements.
**MODEL ADAPTION** - Depending on the schemas used to define the DB data elements; it allows for the adaptation or transformation of models from other sources (e.g. ORAN or 3GPP models).
**CENTRAL/DISTRIBUTED** - Because it is a common service, it is part of an ONAP installation, so it could be deployed with either an Edge ONAP installation or a centralized ONAP installation. The DB shall be designed to accommodate distributed operation as part of its role in the ONAP installation.
CPS Concepts
- Dataspace is a logical separation of data
-Any application can define its own dataspace to store the model(s) and data it owns.
- Anchor is a logical separation of data within a dataspace
-e.g. can be used to distinguish (xNF) instances with of the same model
- Schema set is a representation of a Yang model
-Preserves the original format to avoid collisions and poorly defined models
- DataNode is a YANG container or YANG list
-A DataNode can have 0 or more descendants and together they form an data instance tree
- Leaves is the term used (as in Yang) for the attributes of a DataNode
OVERVIEW CONFIGURATION PERSISTENCE SERVICE INFORMATION FLOW
...
FLOW : Data is read from CPS
Race Conditions - a hysteresis (a time difference) between writing information (from a Kafka broker) and a read request arriving before the writing has finished.
Diagrams (sources)
| draw.io Diagram | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
the basic concepts diagram:
from CPS Internal Relation DB Schema