[
https://issues.apache.org/jira/browse/METRON-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590840#comment-16590840
]
Simon Elliston Ball commented on METRON-1016:
---------------------------------------------
I agree that this would be a great step. Perhaps the demos belong in a more
structured version on the use-cases folder, or in contrib. I have a repo I use
of configs and scripts that have some basic demos in a standard-ish form which
was meant to fill this gap
[https://github.com/simonellistonball/metron-field-demos]
I'm not sure it would benefit from an extra Mpack or Ambari service, since
concepts like services in Ambari seem heavy for a Metron demo, but a set of
scripts to install makes sense. We could probably also do with stripping out
some of the default parsers into a separate section along with this, keeping
the core Metron lightweight with the generics (Grok, Java, CSV, JSON) and
pulling the device ones out into a separate location. That may go beyond the
scope of this exercise but does feel related.
For the full dev load, I would say that an ansible role running post blueprint
install would be a good full dev solution.
> METRON Demo System as separate install option
> ---------------------------------------------
>
> Key: METRON-1016
> URL: https://issues.apache.org/jira/browse/METRON-1016
> Project: Metron
> Issue Type: Improvement
> Reporter: Otto Fowler
> Priority: Major
>
> Right now, the demo system ( bro, snort, yaf ) are part of the default
> installation, and the default configurations required for those systems ( ES,
> Enrichment ) are in the main code base. For example bro's default enrichment
> is the enrichment that assumes the demo setup.
> This is not really correct. The demo system should be a separately
> installable feature of metron, and it's configurations should be managed
> outside the defaults for the parsers etc.
> This would allow separate development of the demo without affecting others.
> Either checkbox or a separate ambari service?
> What should the default enrichment be?
> How to have vagrant install the service
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
