ONAP – Centralization & Externalization of Parser Distribution

Project Name:

Project description:

Preface:

A clear separation of “Design Time” and “Run Time” execution platforms with in ONAP gives an opportunity to truly model drive the run time execution platforms from the design time modelling platform.
On the Design Front : Various developments in R1 of ONAP’s SDC and SO (MSO) modules have provided a ground for defining a logically centralized reference platform for designs & models using multitude of design patterns & grammar, it in-effect proposes a placeholder for future evolution of ONAP to truly model drive ONAP
On the Run Time Front : R1 proposes a Run Time Catalogue embedded within each Execution Platform with certain common set of functionalities that can be centralized (in model driven architecture spirit) and eventually externalized for triggering business cases for much better interop between non-ONAP and ONAP based B/OSS stacks in various service providers
This proposal is an evolutionary idea to further the model driven concept and it also suggests an even greater inter-op construct with non-ONAP Service Provider B/OSS stacks for a global ONAP and truly model driven stack adoption & evolution
At a high level, this proposal is achieved in 2 stages (a) Centralization and (b) Externalization of Parser Binaries

Idea:

As part of R2, we are proposing an improvisation of parser implementation function under the “Centralization of Parser” part of the proposal
current Understanding of Parser Implementation (as part of Design / Run time catalogue) are as below –

A model creation UI (model designer) as part of “Design Time Catalogue”

Below picture depicts the segregation / dissection of parsing function spread across design and run time environments
Highlighted / Encircled Portion in Red shows functional blocks that Design Time Catalogue covers

“Design Grammar” for creation (En-Coding) of models being proposed usin