Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Integration with DCAE  


DCAE stores "fault data" in postgrepsql DB

POMBA would like to access that DB via APIs


Pluggable Data Dictionary

    TBF..

 

Dynamic Rules 

POMBA should support the mechanism of separating 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


Audit Trigger

Manual Trigger

Rest API is exposed to any orchestration tool (VID,..)  

Automated Trigger  

The audit process will be triggered by consuming "orchestration complete" event from message router which will be generated by Service Orchestrator.

There are two types of orchestration flow:

  • Macro flows
  •  A la cart flow

In case of Marco flow, the Service Orchestrator will produce "orchestration complete" event  when the workflow of service instance with all its resources is completed  In case of "A la-cart" flow, there are several workflows processed by SO, and SO may generate "orchestration complete" event at the end of each workflow request, which may represent only partial service instantiation process.

Orchestration Complete message published by SO into Message Router should include the following info


Field  name                                             DescriptionDesc
service instance id
model version id
transaction-id 
Macro / A la-cart flow indicator 
  
  
  • No labels