POMBA Initiating Audit

Owned by Sharon Chisholm
Last updated: Jan 17, 2019
1 min read

There will be two ways to initiate a POMBA Audit

  • Manually calling the REST API

  • Automatically by ensuring an end of transaction event is sent as part of SO flows (future)

Either way, results will available via the report (POMBA Reporting) or directly via DMaap Event (POMBA DMaaP)

Manual Audits

A manual audit can be triggered by calling the POMBA REST API with the following parameters as JSON in the body of a POST request to data-router/v1/orchestration-event-service/orchestration-event

  • serviceInstanceList

    • Model-version-id

    • Model-invariant-id

    • Service-instance-id



Currently manual Rest API triggering requires sending client certificate along with https request to satisfy 2 way SSL handshake protocol.

Https is the only supported option at this point with the above certs.  http is not available for audit initiation.



If the request is well-formed and valid, a response of 200 (OK) will be returned and the audit will return in the background

See also POMBA Audit Initiation Swagger



To set up POMBA Network Discovery to talk to Openstack, please see Network Discovery Context Builder

Automatic Audits

The ultimate goal is to have SO send an end of transaction event once is has completed it workflow. POMBA would listen for these events, and trigger an audit as appropriate. This event and the work to listen for it is not confirmed in Casablanca.



The following JIRA was raised to track the work required in SO to enable automatic audits