[
https://issues.apache.org/jira/browse/METRON-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564722#comment-16564722
]
ASF GitHub Bot commented on METRON-1695:
----------------------------------------
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1132
@anandsubbu Thanks for contributing this! The only thing I'm unsure of
after reviewing this is your comment regarding this belonging in
parser_master.py or not. On one hand, you could make a case that this is a
parser like any other with the exception that it is spout-only. On the other
hand, we don't currently provide a mechanism (iirc) to start/stop/manage the
PCAP topology from Ambari. Starting parsers doesn't start PCAP, does it?
It may be that PCAP deserves its own "master", e.g. pcap_master.py, and
lifecycle as a proper first class citizen (topology) within Ambari. Below is
the current list of components, and PCAP is not in it afaik, even as a parser
(there's a start_pcap_topology.sh script that is NOT the same as
start_parser_topology.sh). It seems like if we're going to add this to Ambari
we should also provide the ability to manage it. What do you think of that
approach?
> Expose pcap properties through Ambari
> -------------------------------------
>
> Key: METRON-1695
> URL: https://issues.apache.org/jira/browse/METRON-1695
> Project: Metron
> Issue Type: Bug
> Reporter: Anand Subramanian
> Assignee: Anand Subramanian
> Priority: Major
>
> Currently, the $METRON_HOME/config/pcap.properties file is hardcoded with the
> defaults. One has to hand edit the file before deploying the PCAP topology.
> These properties should be configurable via Ambari.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
