metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mattf-horton <>
Subject [GitHub] incubator-metron issue #408: METRON-608 Mpack to install a single-node test ...
Date Wed, 25 Jan 2017 07:58:25 GMT
Github user mattf-horton commented on the issue:
    Hi @dlyle65535 , from a design perspective, I totally agree that we should have a single
MPack that works on any size cluster, and I hope to replace both the 4(+)-node and single-node
versions in the future with a more general solution.  I even have a prototype of such.  My
reasons for proceeding with the split-off version at this time were entirely pragmatic, due
to time pressure:
    - I really needed a single-node that works with Ambari, for testing other PRs.  
    - I spent several days trying to make Elasticsearch work on a single node installation,
while retaining the generality of the multi-node case, but couldn't make it work.  This chewed
up a lot of time.
    - I put together a unified Mpack that used two different template files for Elasticsearch,
depending whether it was for a single-node or multi-node install.  That worked just fine,
on the surface, but was clearly going to require in-depth testing of 1, 2, 3, and 4 node cases.
 I do not currently have time to thoroughly test all the special cases.
    - Doing it this way I only had to test the single-node case, which was fairly fast.
    - Having made one that works, I'd like to make it available to others.
    - Now, if it is not accepted into the code, the high rate of change in metron-deployment
will soon obsolete it.
    That's pretty much it.  It's a throw-away, but not until we do the work of actually producing
the generalized solution and testing it thoroughly.  Which I evaluate as lower priority than
a number of other more urgent needs.  Thanks.

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