Page Comparison

The purpose of the page is to have content for review with the ARCHCOM before the end of July 2020

:

1. Design the Model Driven CPS PoC

   Jira Legacy
   server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key REQ-384

2. Start the design of a stand-alone CPS
3. Engage with the CPS community on the design of the stand-alone CPS
4. Review with the ARCHCOM to ensure broad ONAP community awareness and agreed direction

PoC Overview Diagram

Topic Areas

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

...

C4 diagram of main components

Logical view of the CPS as a project

Key sequences/flows

Interfaces

Initial draft specification REST & Java

Behavior

Initial sata structure specification, REST & Java

The blue software encapsulates the handling of models and data related to xNF (mirrored data). This implementation is not required to prove the model driven aspects of the CPS.

The pink software encapsulates the integration with other data stores. This is being taken by the temporal DB PoC. This PoC needs to provide a feed of change notifications for any joint demonstrations. Configuring the parts of the model that will emit change notifications is part of the stretch goal.

Data lake and access control

The CPS will make it possible to share data across components. This is beneficial where it is expensive to source data or access latency is a concern.

The ability to share data raises concerns w.r.t. uncontrolled coupling between components. This makes system maintenance difficult.

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.

Access is provided by the CPS. Access may be qualified as read only or write.

The ability to interpret data requires access to the model that defines the structure and constraints of the data.

Consider the following scenario.

Image Added

Svc A and Svc B are considered to own their data, A and B respecively.

Data A and Data B are stored in a Common Data Service (e.g. DBMS). This is important, but not relevant to this discussion.

Data A and Data B may represent multiple instances of the same model – for example there may be multiple instances of the same xNF in the scope of the ONAP system, each would need to be in a separate tree, all compliant to the same model.

Svc C would like to access Data A and Data B, without going through the public interfaces exposed by Svc A and Svc B.

Svc C must petition Svc A and Svc B for access rights (this may be a design or run-time activity) to their data.

Once access has be provided by the owners (Svc A and Svc B) Svc C may use this permission to access data directly.

Svc C cannot completely interpret the data without access to the models. The model is the responsibility of the owning service, and is provided to Svc C together with the permission and any relevant instances of data trees.

This is also the case for the CPS. It cannot persist or validate data without access to the model. It is the responsibility of the data owner to provide the model to the CPS prior to data access.

The run-time aspect of the granting of permission has some potential to also address some race conditions.

The key benefits are: (1) Data lake use cases are enabled; (2) Coupling between components at the level of 'shared' data are explicitly declared/published.

PoC implemetaion

The PoC will start with a compatible subset of the above implementation. Nothing in the PoC implementation will preclude the development of the above solution.

Image Added

All access to data will be via the owning service.

Model handling

Below a simplified view of model handling artifacts and their relationships.

Image Added

The run-time artifacts are shaded (orange). A typical simplified flow:

• A document representing xNF data is given to the CPS.
• It will parse (and validate) the document,
• Map data to the generic DB schema and store data.

In order for this to work:

• The document must be compliant to an xNF schema model. This schema model describes the structure of the data and any constraints that need to be checked to ensure integrity.
• The xNF schema model must be written in YANG. This language describes syntax and capabilities (basic concepts).
• A Yang parser is required to interpret documents compliant with the YANG language. The parser is dependent on the language.
• To store data in a DBMS, typically a schema is required. This is denoted above as, 'Generic schema model'.
• Obviously the xNF schema model and the Generic schema model are not the same. Therefor a mapping is required. Depending on how simple/generic/abstract the generic schema model, the mapping may be coupled with either the language or the xNF schema model. One of the aims of the PoC is to be agnostic to the xNF model at run-time, thus the mapping is made to the YANG language.
• To support multiple container run-times (Java, Python, Go, Rust, ...) for the CPS, the mapping is described in a 'Language Capability Map'.
• The model mapper depends on the language capability map and the Yang parser (in particular the java representation of the language features).

Model ingestion

Model ingestion is subject to a design discussion. See below. This section will be updated when that discussion has been concluded and a decision made.

Note that for the purposes of the PoC, model ingestion will be via a model life-cycle REST interface.

Model upgrade

T.B.D. See Upgrade of models for discussion and decision

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.

Detailed design

Key sequences/flows

Add a model

Store data (including validation)

Read data

Reading data is very similar to storing data. The uuid of the model instance is assumed. Validation is not needed. Queries will need to be processed and mapped to DB technology specifics.

Upgrade a model

T.B.D. Needs to wait until upgrade behavior is specified.

Adapt change notification behavior as described in model

T.B.D. Show how the model spec is used to control interactions between CPS Core and CPS Notification

Interfaces

Style and payload structure

The payload will be represented as Generic objects/documents. For more reasoning and discussion, see Data Representation

In java, the CPSDataObject will be a 'glorified' map -- not a basic map, but one level more concrete (in terms of abstractions). I.e. at the language level
The sample java code below illustrates ubiquitous use of the CPSDataObject.

public class CPSDataObject extends Map {...}

CPSDataObject tree = cps.getTree(obj, level, filter)
List<CPSDataObject> refs = cps.getRefs(obj)
CPSDataObject parent = cps.getParent(obj)
List<CPSDataObject> children = cps.getChildren(obj)

Filters will be encoded as XPath expressions.

YANG <-> Java type mapping will be inherited from the selection of YANG parser

For REST, the payload will be a document complying to a generic JSON schema.

The style of the interface will be such that access methods are associated with the CPS. Data is provided as context. For more reasoning and discussion, see Interface style.

The pseudo Java code below illustrates this style by showing how complementary relationships could be navigated.

CPSDataObject cpsRootObject = CPS.getRootObject(uuid_to_identify_inventory_item);
System.out.println(cpsRootObject);
List<CPSDataObject> kids = CPS.getChildren(cpsRootObject);
for (CPSDataObject kid: kids) {
	System.out.println(CPS.getParent(kid));
}

REST payload structure

Java payload structure

Access methods

Service Provider Interface (SPI)

T.B.D. An internal interface that defines how the CPS Core will interact with the DBMS. The design of the SPI will be informed by agreed CPS behavior and minimum requirements for the DBMS.

The SPI is required to ensure that different DB technologies can be used in different deployments.

Behavior

T.B.D.: Eventual consistency; Data integrity guarantees; Fast failure; Progress; Cancellation;

REST

Will be specified as part of the PoC execution, and updated/referenced from here

This will follow REST rules and guidelines as defined by ONAP documentation (TODO: add link)

Java

Will be specified as part of the PoC execution, and updated/referenced from here

Decision reference

Issues decisions and assumptions