[
https://issues.apache.org/jira/browse/METRON-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683694#comment-15683694
]
Justin Leet commented on METRON-552:
------------------------------------
Addendum to the addendum. The metron user doesn't have a /user/metron created
on HDFS, so it's necessary to create and chown it appropriately. At that
point, the script should be run as the Metron user. This should all be handled
by the Ambari service.
{code}
su - hdfs
hadoop fs -mkdir /user/metron
hadoop fs -chown metron:hadoop /user/metron
{code}
> 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)
