metron-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (METRON-671) Refactor existing Ansible deployment to use Ambari MPack
Date Tue, 07 Mar 2017 15:38:38 GMT

    [ https://issues.apache.org/jira/browse/METRON-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899608#comment-15899608
] 

ASF GitHub Bot commented on METRON-671:
---------------------------------------

Github user dlyle65535 commented on the issue:

    https://github.com/apache/incubator-metron/pull/436
  
    @ottobackwards - I don't agree that automation breaks with this. It is different though.
If you're building automation now, you'd probably want to leverage Ambari Blueprints. 
    
    Unfortunately, as we go down this path, I don't see a way around checking Ambari. In reality,
that was always the case. If the Hadoop deployment failed, that was where you looked. If the
probes failed to start, you checked Monit. Ansible alerted you to the fact of the failure,
but anything but the simplest required poking around Ambari/Monit/Command Line.
    
    It sounds to me like you'd like to revisit the decision to reduce reliance on Ansible.
If that's the case, we can certainly do that. I thought we had consensus but maybe we don't.
Maybe we need to go back to the discuss thread?


> 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.15#6346)

Mime
View raw message