GitHub user justinleet opened a pull request:
https://github.com/apache/incubator-metron/pull/340
METRON-520: /apps/metron/enrichment directory does not get created for
Metron cluster deployed via Ambari
In addition to the main goal, there's a couple minor changes I made while I
was in the neighborhood for simple changes that didn't seem to make sense to
bother with separate PRs. If anyone wants them to be split out, I'm happy to
break the commit up appropriately.
This PR covers 3 things:
1. The original directory fix. It did exist before, but was configured to
be /tmp/metron/enriched. This moves it to be consistent with quick-dev and
adjusts the folder's permissions appropriately so that it can actually be
written to by Storm (owned by the Hadoop group with 755 perms, same as quick
dev). Complimentary to this the /apps/metron/patterns folder is properly
created and used. It was defined in configs before, but /apps/metron was
passed instead of the /apps/metron/patterns.
2. Pcap RPM never got installed. It's a simple three line change to make
sure the scripts get deployed.
3. Made the is_configured files consistent (enrichment had slightly
different file pattern). One line config change.
To test, I used the docker-ambari procedure outline at:
https://www.evernote.com/shard/s530/sh/c5551fbd-0ac1-4861-89ce-9c5e37065c52/b13e05f39eaac1a6
After spinning up the instance and installing the service, the directories
are appropriately created (/apps/metron/enrichments and /apps/metron/patterns).
The Metron home directory on the nodes contains the pcap scripts and yum
reports the pcap rpm as installed. Finally, the configured files are all just
metron_<indexing|enrichment|parsers>_configured
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/justinleet/incubator-metron METRON-520
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-metron/pull/340.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #340
----
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
