metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ottobackwards <>
Subject [GitHub] incubator-metron issue #436: METRON-671: Refactor existing Ansible deploymen...
Date Tue, 07 Mar 2017 15:13:10 GMT
Github user ottobackwards commented on the issue:
    I can offer a slightly different perspective on this PR, from the pov of someone working
downstream ( i rebased on it ), and who has been working on adding things to the spec and
    Many of my issues have been of my own doing ( trying and failing to use templates for
spec's but not go all the way ), not doing everything in maven from the start since ansible
is more flexible etc .
    What I would like to bring up is the 'black box' nature of this build now.  I don't see
errors surface into the ansible log they way they would before.  
    The build starts building, and while it is running all the maven commands there is no
output, and no logging.   I have had to drop down into the rpm level and build there to see
errors, or go into the vagrant image and hunt down logs to see problems with deployment (
a good tip is when the ansible log says it is deploying cluster, connect to ambari and monitor
the ops, which tail the logs and give the file names, with are NOT var/log based ).
    The point of this specific feedback is that we have added a very large amount of time
to the vagrant up, during which many many things could go wrong, and none of them surface
to the user.

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 or file a JIRA ticket
with INFRA.

View raw message