[
https://issues.apache.org/jira/browse/METRON-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15819929#comment-15819929
]
ASF GitHub Bot commented on METRON-654:
---------------------------------------
Github user mattf-horton commented on the issue:
https://github.com/apache/incubator-metron/pull/413
+1 Used these RPMs to add Profiler, after installing a single-node Centos7
vm with the Ambari mpack, using OracleJDK8, HDP-2.5.3, and Ambari-2.4.2.
Performed `rpm -ivh metron-profiler.rpm`, validated as above, then did
`bin/start_profiler_topology.sh`, and used it to test PR-414, during which Bro
data was pumped through the usual sequence of topologies, and was observed in
Storm UI to propagate through all into indexer and profiler. Elasticsearch and
HBase were queried from outside Metron to confirm presence and format of data,
and PROFILE_GET was used in Stellar REPL to read the profile data back out as
expected.
Looking forward to the mpack additions! Thanks, @nickwallen .
> Create RPM Installer for Profiler
> ---------------------------------
>
> Key: METRON-654
> URL: https://issues.apache.org/jira/browse/METRON-654
> Project: Metron
> Issue Type: Improvement
> Affects Versions: 0.3.0
> Reporter: Nick Allen
> Assignee: Nick Allen
> Fix For: Next + 1
>
>
> The Profiler currently must be installed using the Ansible deployment
> scripts. Prior to getting the Profiler integrated with the rest of the
> Ambari installation process, we need to package the Profiler in an RPM.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
