Re: Metron dev environments moving to require Ansible 2.4+

2018-10-01 Thread Michael Miklavcic
I ran it up a second time and it seems to be working now. I'm not sure what happened there, but I'll keep an eye on it. On Mon, Oct 1, 2018 at 2:48 PM Nick Allen wrote: > I have been able to spin-up a development environment today without a > problem. > > On Mon, Oct 1, 2018 at 3:58 PM Michael

Re: Metron dev environments moving to require Ansible 2.4+

2018-10-01 Thread Nick Allen
I have been able to spin-up a development environment today without a problem. On Mon, Oct 1, 2018 at 3:58 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > Anyone run latest master today with full dev? I'm seeing > NoClassDefFoundError exceptions on starting enrichments. I upgraded

Re: Metron dev environments moving to require Ansible 2.4+

2018-10-01 Thread Michael Miklavcic
Anyone run latest master today with full dev? I'm seeing NoClassDefFoundError exceptions on starting enrichments. I upgraded to latest Ansible and the provisioning part seemed to work just fine. https://gist.github.com/mmiklavc/56205526b4736e859aa7ba52468ff4f3 On Mon, Oct 1, 2018 at 6:46 AM

Re: Metron dev environments moving to require Ansible 2.4+

2018-10-01 Thread zeo...@gmail.com
Hi All, This has been pushed to master. Please updated your Ansible appropriately. Thanks! Jon On Fri, Sep 28, 2018 at 12:18 PM Otto Fowler wrote: > Yeah, I thought we had more but maybe they where removed. > Many places in *.md files referencing Ansible and versions too > > > On September

Re: [DISCUSS] Add e2e step to PR checklist

2018-10-01 Thread Casey Stella
I'd also like to make sure that clear instructions are provided (or linked to) about how to run them. Also, we need to make sure the instructions are rock-solid for running them. Looking at https://github.com/apache/metron/tree/master/metron-interface/metron-alerts#e2e-tests, would someone who

Re: [DISCUSS] Add e2e step to PR checklist

2018-10-01 Thread Casey Stella
I'm not super keen on expanding the steps to contribute, especially in an avenue that should be automated. That being said, I think that until we get to the point of automating the e2e tests, it's sensible to add them to the checklist. So, I would support it, but I would also urge us to move

[DISCUSS] Add e2e step to PR checklist

2018-10-01 Thread Shane Ardell
Hello everyone, In another discussion thread from July, I briefly mentioned the idea of adding a step to the pull request checklist asking contributors to run the UI end-to-end tests. Since we aren't running e2e tests as part of the CI build, it's easy for contributors to unintentionally break