[
https://issues.apache.org/jira/browse/METRON-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530833#comment-15530833
]
ASF GitHub Bot commented on METRON-466:
---------------------------------------
Github user nickwallen commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/279#discussion_r81014011
--- Diff: metron-deployment/inventory/full-dev-platform/group_vars/all ---
@@ -78,7 +79,7 @@ sensor_test_mode: True
install_pycapa: False
install_bro: True
install_snort: True
-install_yaf: True
+install_yaf: False
--- End diff --
Before this change, Snort, Bro and YAF were all installed and started by
default. That is my understanding of how it has been for months.
This PR changes that behavior so that YAF is neither installed nor started.
The comments in your PR only say that you don't want YAF started. You don't
mention anything about YAF not being installed.
Since there was this gap between what the PR says and what the PR does, I
wanted to make sure we bring it to light.
There is a fair amount of documentation that describes to users that when
they deploy Metron, they are going to see YAF, Snort and Bro data in the Metron
Dashboard. This PR will change that. The user will not see YAF data.
> Full Dev Platform build sometimes fails
> ---------------------------------------
>
> Key: METRON-466
> URL: https://issues.apache.org/jira/browse/METRON-466
> Project: Metron
> Issue Type: Bug
> Reporter: David M. Lyle
> Assignee: David M. Lyle
>
> Full Dev Platform build will sometimes fail with:
> "Ambari client exception occurred: No JSON object could be decoded"
> As a workaround to the services not all starting, we have 2 calls to start
> all services in the Vagrant deploy. The second call seems to fail if the
> services are already started.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
