[
https://issues.apache.org/jira/browse/METRON-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840460#comment-15840460
]
ASF GitHub Bot commented on METRON-671:
---------------------------------------
Github user mattf-horton commented on the issue:
https://github.com/apache/incubator-metron/pull/425
@dlyle65535 , makes sense to me. METRON-671 is very important for
rationalizing our install scenarios, and clearly these fixes can be pipelined
as you describe. I'm super glad you're picking these up.
FYI, the METRON-634 fixes included here have all been proven out in my
single-node installer, which I've used quite a bit over the past month. Also,
all but the last 2 of the 12 items "not affecting the Ambari database" are bug
fixes, not enhancements, without which some piece or other of the ES
installation doesn't work correctly in today's Mpack, at least with Centos7.
> Refactor existing Ansible deployment to use Ambari MPack
> --------------------------------------------------------
>
> Key: METRON-671
> URL: https://issues.apache.org/jira/browse/METRON-671
> Project: Metron
> Issue Type: Bug
> Reporter: David M. Lyle
> Assignee: David M. Lyle
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
