Regarding Kyle's question, that assessment is what I'm getting from the
thread. We're not saying Metron has to be Kerberized, but that components
that will be managed by the mpack need to support it (otherwise Ambari will
have issues Kerberizing and running a cluster where a mandatory component
isn
Just to clarify, we're saying when adding a service to the mpack that Kerberos
support is required... but we're not saying that installing Metron requires a
kerberized cluster correct? I think we should support it but should allow
installation and use of Metron without it (for testing or other r
My thought was that if it was a requirement, or blocker for contribution we
would want
to provide something to help.
I am not sure everyone will have a kerberos cluster to test with. Maybe
they will.
Maybe the answer is Docker or Vagrant as Casey suggests and not integration
testing.
On April
Hi Guys,
I don't like further bloating our integration tests so I am not sure I like the
idea. I think when people add new services they should test on real clusters
using kerberos. Also, community members can take on end-to-end testing in
advance of a release on a cluster using kerberos. Bu
I honestly don't know if we can mock out a KDC for integration tests. If
we did move the integration tests to running against docker, that might be
an option as we could dockerize a KDC as well.
Long story short, "probably, but not for free. ;)"
On Thu, Apr 13, 2017 at 10:41 AM, Otto Fowler
wro
Can we test kerberized support in integration?
On April 13, 2017 at 10:24:43, Casey Stella (ceste...@gmail.com) wrote:
Agreed, +1
On Thu, Apr 13, 2017 at 10:14 AM, Otto Fowler
wrote:
> This should be in the dev guide and pr template
>
>
> On April 13, 2017 at 09:43:48, Casey Stella (ceste...@
Agreed, +1
On Thu, Apr 13, 2017 at 10:14 AM, Otto Fowler
wrote:
> This should be in the dev guide and pr template
>
>
> On April 13, 2017 at 09:43:48, Casey Stella (ceste...@gmail.com) wrote:
>
> Based on my understanding, we have a few axioms that we're working from:
>
> - The installer should
This should be in the dev guide and pr template
On April 13, 2017 at 09:43:48, Casey Stella (ceste...@gmail.com) wrote:
Based on my understanding, we have a few axioms that we're working from:
- The installer should install a complete and workable product (i.e.
after install, everything should
Based on my understanding, we have a few axioms that we're working from:
- The installer should install a complete and workable product (i.e.
after install, everything should work). Afterall, that has to be the
sensible definition of 'working' for an installer
- Metron should support
There is a PR up for review (
https://github.com/apache/incubator-metron/pull/518) that updates our MPack
to support a Kerberized environment. There is also a PR up for review that
adds the REST service to the MPack (
https://github.com/apache/incubator-metron/pull/500).
However, the REST applica
10 matches
Mail list logo
