Uploaded image for project: 'Logging analytics'
  1. Logging analytics
  2. LOG-419

Post Orchestration Audit – Systematic triggering of Audits

XMLWordPrintable

      As an Ops person I would like POMBA to be triggered in a systematic fashion based upon completion of orchestration events so that I can have up to date information regarding data integrity of instance artifacts vs design model.

       

      General Information

      This story concerns itself with consuming the new MSO ‘orchestration complete’ message being published to DMaaP at the completion of orchestration events.  In order to take advantage of the MSO event being published, it must now be consumed by Data Router.  Data Router will consume the topic, re-map [if necessary] and republish to DMaaP as a audit topic so that it can be consumed BAU by Context Aggregator and used to initiate requests to the various Context Builders.

      MSO will publish "orchestration complete" event into their own topic, so POMBA data-router will need to add additional consumer route, subscribing to MSO topic, processing the event and republish it in audit topic

      At the completion of this user story, audit will be triggered automatically by consuming MSO orchestration complete event from DMaaP.
       

      [DRAFT] Event Content ( see attached )

      audit-init-event should be also enhanced to include additional information received from MSO
      please see attached suggested updated structure of audit-init-event payload

      data-router is responsible to map mso triggered event into audit-event payload

       
      Value

      Implements systematic initiation of Post orchestration audits

       ** 

      Success Criteria

      • Compliant to the ask above
        • Support for all ONAP best practices
        • Code checked in, use documented on Wiki
        • Demo to working group

            Unassigned Unassigned
            dkedrosk dkedrosk
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: