[
https://issues.apache.org/jira/browse/METRON-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564791#comment-16564791
]
ASF GitHub Bot commented on METRON-1695:
----------------------------------------
Github user anandsubbu commented on the issue:
https://github.com/apache/metron/pull/1132
@mmiklavc thanks for the review. I concur with your observations. PCAP
topology does deserve its own place in Ambari and the Management UI.
As far as the scope of this PR goes, this IMHO, would be a first cut
towards it. This PR addresses the immediate need for exposing the parameters in
`pcap.properties` via Ambari. It also addresses auto-populating the ZK quorum
in `pcap.properties` thus simplifying the manual steps that would be otherwise
required in a multi-node deployment.
Would you be okay if we create a separate JIRA to cover the broader change?
Let me know your thoughts.
> 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)
