As an Ops person i would like to enhance the data mapping to include additional information from the MSO event payload so that i can further automate the initiation of POMBA audit.

General Information

LOG-419 uses the MSO orchestration complete event to trigger POMBA.  This user story will expand on this capability by mapping additional fields from the event into the payload going to context aggregator.  This additional information will be used in LOG-437 and LOG-438 in order to determine whether or not to proceed with an audit and then in turn which components will need to be audited.

This story concerns itself with consuming the new information provided by the MSO ‘orchestration complete’ message being published to DMaaP at the completion of orchestration events.  Sample mapping is shown in the attachments.

[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 and enables further enhancements to automated 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