Actually, METRON-797 (https://github.com/apache/incubator-metron/pull/490)
is inspired by that work, Dave.
Specifically here are the differences:
- The mpack work is not included
- It's based on 793, so it uses storm-kafka-client rather than
storm-kafka
- It adds a flag when starting
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/488
I don't have an objection. I made that change because there was some issue
with user_group. Unfortunately, I can't remember exactly what that was. In it's
current state, what's the
Sounds good to me. A few of us did some initial exploration on that topic a
week or so back. The branch is here:
https://github.com/dlyle65535/incubator-metron/tree/kerb-testing?files=1
It contains a prototype quality version of everything you've identified
except METRON-793 and the probes.
If
A cool thing about the MPack is that you can now leverage blueprints [1] in
an automated way.
I'm traveling this week, so this is from my phone, please excuse if there
are more typos than usual
The overall flow is pretty much what we're doing in Ansible (it uses
blueprints under the hood).
Just to add onto this, that is a feature I have similarly been looking for
but my environment hasn't matured enough yet for me to push the topic.
I've been installing various versions of master in my hardware environment
using Ansible, but ever since the Ambari mpack I have been doing it more
