metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dlyle65535 <...@git.apache.org>
Subject [GitHub] incubator-metron issue #436: METRON-671: Refactor existing Ansible deploymen...
Date Tue, 07 Mar 2017 15:38:18 GMT
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?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message