Audit CPN Tickets and OpenNMS Situations
Description
Acceptance / Success Criteria
None
Attachments
1
100% Done
Lucidchart Diagrams
Activity
Show:
Jesse White March 27, 2019 at 1:15 PM
Tooling completed
Jesse White January 14, 2019 at 4:43 PMEdited
We envision having the following commands:
oce-tools cpn-export --from “Jan 6 2019” --to “Jan 7th 2019”
Output: Dataset 1
oce-tools opennms-export --from “Jan 6 2019” --to “Jan 7th 2019”
Output: Dataset 2
oce-tools dataset-map --ds1 /tmp/cpn --ds2 /tmp/onms
Output: Map from Dataset1 to Dataset2
oce-tools dataset-merge --ds1 /tmp/cpn --ds2 /tmp/onms --map /tmp/map.xml
Output: Dataset 3
oce:score-situations -s peer -m map.xml /tmp/cpn/cpn.situations.xml /tmp/onms/onms.situations.xml
Jesse White January 14, 2019 at 4:42 PM
Here's a diagram for some of the data flows:
Jesse White January 7, 2019 at 9:28 PM
Work for this feature is in progress here: https://github.com/OpenNMS/oce-tools/tree/features/tsaudit
Goal: Build tooling that allows CPN Tickets to be compared to OpenNMS Situations using data available from the CPN reports and the OpenNMS Elasticsearch integration.
In order to compare these datasets, we should bring them to a common representation in order to make it easier for tools to build on. We already have a representation that we've used for exporting data from CPN and importing in into OCE for simulations - we can leverage these data structures: https://github.com/OpenNMS/oce/tree/75a1b3978b076bf7a2298f8b56245ccf86573333/datasource/jaxb/src/main/resources
Once datasets are in this common format, we can use the tooling to generate a "map" that would allow objects from one dataset to be associated with objects from another.