You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Justin Leet (JIRA)" <ji...@apache.org> on 2016/11/04 16:25:59 UTC

[jira] [Created] (METRON-552) Ambari Mpack should be able to manage pcap topology

Justin Leet created METRON-552:
----------------------------------

             Summary: Ambari Mpack should be able to manage pcap topology
                 Key: METRON-552
                 URL: https://issues.apache.org/jira/browse/METRON-552
             Project: Metron
          Issue Type: Improvement
    Affects Versions: 0.2.1BETA
            Reporter: Justin Leet


Right now, the mpack installs the pcap RPM, but doesn't do any management of it.  This should be handled by Ambari.  With the current boundaries of the mpack (i.e. responsibility begins at kafka, not before), using pycapa to produce data to Kafka wouldn't be managed by Ambari.

As a workaround (which will also have to happen in the Ambari service), pcap topology can be run on an Ambari managed Metron instance by
1) Updating /usr/metron/0.2.1BETA/config/pcap.properties by editing kafka.zk manually. Ambari should manage these configs itself, once the service is up.
2) Creating /apps/metron/pcap on HDFS, owning it to metron:hadoop, and updating permissions to 775 on the folder.

At this point, /usr/metron/0.2.1BETA/bin/start_pcap_topology.sh should be able to be run normally.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)