Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents


POMBA Definition 

What is POMBA - Post Orchestration Model Based Audit

Architecture Intent

High level view of POMBA components

Gliffy Diagram
size900
namePOMBA Architecture
pagePin13
   


Design

Design Principles

  • Reusable Components

POMBA is developed based on microservices-based architecture to ensure pluggable capability into other Data Integrity sub-system

POMBA uses other microservices initially designed for A&AI component promoting them as a platform modules.

  •  Event-Driven

POMBA is event-driven application to ensure auditing without affecting existing systems.

  • Extensibility

POMBA is implemented based on Context Builders Framework to ensure that core audit process is decoupled from the target system integration specifics.

            

Sequence Diagrams

Initiate Audit


Gliffy Diagram
size1200
namePOMBA Seq Diagram
pagePin11


Process Flow


Sub-Components

POMBA leverages context builders approach to provide pluggable framework of accessing various ONAP components to retrieve the data. 

It allows to encapsulate the complexity of reaching a component as well as implement the mapping and transformation component’s related data to common model consumed by audit process. 

SDC Context Builder 

The purpose of SDC Context Builder is to encapsulate the complexity of interaction with SDC component .

High level view of SDC Context Builder mS:

Gliffy Diagram
nameSDC Context Builder
pagePin4

 


A&AI Context Builder

The purpose of A&AI Context Builder is to encapsulate the complexity of interaction with A&AI component .

High level view of A&AI Context Builder mS:


Gliffy Diagram
nameAAI Context Builder
pagePin2



SDN-C Context Builder

SDN-C Context Builder is aimed to encapsulate the functionality of accessing SDN-C via RESTful APIs and transform the data into common model structure used by audit process.


Gliffy Diagram
nameSDN-C Context Builder
pagePin2



Validation Service

Validation service is a core microservice which implements rule processing engine.

Audit rules are stored in groovy format file. The file is injected into a service and rules are processed by the engine.

POMBA will support the mechanism of separting rules from validation service code, thereby allowing changing the rules without a rebuild or restart of the validation service.

The text of the message displayed for each violation will be kept separately to allow text change without touching the code

 

Gliffy Diagram
nameValidation Service
pagePin3



Deployment Model

Containers

IDNameport pod dependenciesAttributes

ONAP referencing dependencies

Incoming API

ONAP ref dependencies

Outgoing API

Notes
1synapse service9502 dmaap, search-data-service
/data-router/v1/orchestration-event-service/orchestration-eventdmaap APIs, /services/search-data-service/v1/search/indexes 
 2search-data-service9509 elastic-search   /services/search-data-service/v1/search/indexeselasticSearch APIs 
 3elastic-search 9200n/a   n/a n/a 
aai-context-builder9530 aai-service  /aaicontextbuilder/service/context  A&AI APIs 
 5 sdn-c-context-builder9531  sdnc /sdnccontextbuilder/service/context  SDN-GC APIs 
 6 sdc-context-builder9532  sdc-be /sdccontextbuilder/service/context  SDC BE APIs 
 7 context-aggregator9529 aai-context-builder,sdc-context-builder, sdn-c-context-builder, dmaap  dmaap APIsdmaap APIs  
 8 validation-service9501 dmaap dmaap APIs dmaap APIs  
 9dcae-context-builder 9540 DCAE, Vertica DB ?     


Design Issues

DevOps

Links