METRON-1560: Update MPack to support Pcap panel

[merrimanr]

Contributor Comments

This PR adds MPack support for the Pcap query feature. The pcap properties in application.yml are now exposed in Ambari. The page size can be changed in the REST tab while the paths (changing them shouldn't be common) can be done in the Advanced tab.

Changes Included

• Pcap properties in REST were added to Ambari
  • pcap_base_path
  • pcap_base_interim_result_path
  • pcap_final_output_path
  • pcap_page_size
• Pcap page size property can be changed in the REST config tab in Ambari
• HDFS directories for the 3 path properties are created on install, similar to how HDFS directories are created in other components
• Pcap topology output path now matches the default Pcap query input directory

Testing

This has been tested in full dev. Testing is similar very similar to #1123 and #1120. The only difference is that creating the HDFS directories in Step 2 is no longer required.

As an additional test, change the Pcap Page Size setting in the REST Configs tab in Ambari. After running a query the number of pages should reflect the page size.

Pull Request Checklist

Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.

In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:

For all changes:

• 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)?

For code changes:

• 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:

  mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh 
  

• 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?

For documentation related changes:

• Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:

  cd site-book
  mvn site
  

Note:

Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

[cestella]

+1 by inspection; this puts a nice bow on the backend.