METRON-2301 Building Against Wrong Storm Flux Version

[nickwallen]

When we upgraded to Storm 1.2.1, we did not update the version of Storm's Flux library that we use. We are still building against org.apache.storm:flux-core:1.0.1

Acceptance Testing

This PR should be tested using the centos7 development environment.

1. Start up the centos7 dev environment.

   cd metron-deployment/development/centos7
   vagrant destroy -f
   vagrant up
   

Basic Indexing and Enrichment

Ensure that we can continue to parse, enrich, and index telemetry. Verify data is flowing through the system, from parsing to indexing

1. Open Ambari and navigate to the Metron service http://node1:8080/#/main/services/METRON/summary

2. Open the Alerts UI. Verify alerts show up in the main UI - click the search icon (you may need to wait a moment for them to appear)

3. Go to the Alerts UI and ensure that an ever increasing number of telemetry from Bro, Snort, and YAF are visible by watching the total alert count increase over time.

4. Ensure that geoip enrichment is occurring. The telemetry should contain fields like enrichments:geo:ip_src_addr:location_point.

5. Head back to Ambari and select the Kibana service http://node1:8080/#/main/services/KIBANA/summary

6. Open the Kibana dashboard via the "Metron UI" option in the quick links

7. Verify the dashboard is populating

Pull Request Checklist

• Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
• Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
• Has your PR been rebased against the latest commit within the target branch (typically master)?
• Have you included steps to reproduce the behavior or problem that is being changed or addressed?
• Have you included steps or a guide to how the change may be verified and tested manually?
• Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
• Have you written or updated unit tests and or integration tests to verify your changes?
• If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
• Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

[ottobackwards]

ansible.log

Failed for me. I'm not sure what the issue is, since the build log is a mess in ansible.
I'll try to build from root

[ottobackwards]

mvn clean && time mvn -q -T 2C -DskipTests install && time mvn -q -T 2C surefire:test@unit-tests && time mvn -q surefire:test@integration-tests && time mvn -q test --projects metron-interface/metron-config && time build_utils/verify_licenses.sh

[nickwallen]

Thanks @ottobackwards . I'll dig in. Seems like the API changed slightly.

[ottobackwards]

@nickwallen let me know when travis passes and this is ready for retest

[nickwallen]

This is ready now. The only other changes required impact the integration tests only.

[ottobackwards]

+1,

• inspection
• ran through prescribed testing steps

Thanks for the contribution!

[nickwallen]

Thanks for the review @ottobackwards . I have merged this into the feature branch.