[VOTE] Metron-bro-plugin-kafka Release Candidate 0.3.0-RC1

[Justin Leet]

This is a call to vote on releasing Apache Metron-bro-plugin-kafka 0.3.0
The release candidate is available at:
https://dist.apache.org/repos/dist/dev/metron/metron-bro-plugin-kafka/0.3.0-RC1/

Full list of changes in this release:
https://dist.apache.org/repos/dist/dev/metron/metron-bro-plugin-kafka/0.3.0-RC1/CHANGES

The tag to be voted upon is:
apache-metron-bro-plugin-kafka_0.3.0-rc1


The source archives being voted upon can be found here:
https://dist.apache.org/repos/dist/dev/metron/metron-bro-plugin-kafka/0.3.0-RC1/apache-metron-bro-plugin-kafka_0.3.0-rc1.tar.gz

Other release files, signatures and digests can be found here:
https://dist.apache.org/repos/dist/dev/metron/metron-bro-plugin-kafka/0.3.0-RC1/

The release artifacts are signed with the following key:
*https://dist.apache.org/repos/dist/release/metron/KEYS*

Please vote on releasing this package as Apache Metron-bro-plugin-kafka
0.3.0

When voting, please list the actions taken to verify the release.

Recommended build validation and verification instructions are posted here:
https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds

This is only for the plugin, so the VM validation is not required.

This vote will be open for until 3pm EDT on Friday November 27 2018.

[ ] +1 Release this package as Apache Metron 0.3.0-RC1

[ ] 0 No opinion

[ ] -1 Do not release this package because...

Re: Unzipping Cypress

[Otto Fowler]

I’m sorry for the confusion, but I see this locally.  I’m not looking at
travis.
I have been doing a lot of full dev deployments.



On November 27, 2018 at 11:40:42, Shane Ardell (shane.m.ard...@gmail.com)
wrote:

Otto,

Do you have a Travis log you can share that shows Cypress downloaded vs.
using a cached version? It looks like my latest merge to master uses a
cached version: https://travis-ci.org/apache/metron/jobs/458440883#L7292.

Thanks in advance.

On Mon, Nov 26, 2018 at 6:14 PM Shane Ardell 
wrote:

> It seems we can pretty easily configure the .travis.yml config file to
> cache our npm modules:
>
https://docs.cypress.io/guides/guides/continuous-integration.html#Caching-the-Cypress-binary
>
> It also looks like we are already trying to cache our npm modules in the
> Travis config, but, obviously, it's not working as intended. I can take a
> look into why tomorrow.
>
> On Mon, Nov 26, 2018 at 5:33 PM Michael Miklavcic <
> michael.miklav...@gmail.com> wrote:
>
>> Shane, Tibor - Can you guys chime in on this?
>>
>> On Mon, Nov 26, 2018 at 9:13 AM Otto Fowler 
>> wrote:
>>
>> > Isn’t there a way we can cache it?
>> >
>> >
>> > On November 26, 2018 at 10:59:20, Nick Allen (n...@nickallen.org)
>> wrote:
>> >
>> > Yes, I have noticed that too. If not a way to reduce the time, we
should
>> > not be logging the unzipping process percentile-by-percentile in the
>> Travis
>> > CI builds.
>> >
>> > On Sat, Nov 24, 2018 at 9:49 AM Otto Fowler 
>> > wrote:
>> >
>> > > Anyone else seeing a lot of time taken downloading and unzipping
>> Cypress
>> > on
>> > > builds?
>> > > What is up with that?™
>> > >
>> > > ottO
>> > >
>> >
>>
>

Re: Unzipping Cypress

[Shane Ardell]

Otto,

Do you have a Travis log you can share that shows Cypress downloaded vs.
using a cached version? It looks like my latest merge to master uses a
cached version: https://travis-ci.org/apache/metron/jobs/458440883#L7292.

Thanks in advance.

On Mon, Nov 26, 2018 at 6:14 PM Shane Ardell 
wrote:

> It seems we can pretty easily configure the .travis.yml config file to
> cache our npm modules:
> https://docs.cypress.io/guides/guides/continuous-integration.html#Caching-the-Cypress-binary
>
> It also looks like we are already trying to cache our npm modules in the
> Travis config, but, obviously, it's not working as intended. I can take a
> look into why tomorrow.
>
> On Mon, Nov 26, 2018 at 5:33 PM Michael Miklavcic <
> michael.miklav...@gmail.com> wrote:
>
>> Shane, Tibor - Can you guys chime in on this?
>>
>> On Mon, Nov 26, 2018 at 9:13 AM Otto Fowler 
>> wrote:
>>
>> > Isn’t there a way we can cache it?
>> >
>> >
>> > On November 26, 2018 at 10:59:20, Nick Allen (n...@nickallen.org)
>> wrote:
>> >
>> > Yes, I have noticed that too. If not a way to reduce the time, we should
>> > not be logging the unzipping process percentile-by-percentile in the
>> Travis
>> > CI builds.
>> >
>> > On Sat, Nov 24, 2018 at 9:49 AM Otto Fowler 
>> > wrote:
>> >
>> > > Anyone else seeing a lot of time taken downloading and unzipping
>> Cypress
>> > on
>> > > builds?
>> > > What is up with that?™
>> > >
>> > > ottO
>> > >
>> >
>>
>

Re: [DISCUSS] Add ngrx to handle state management in Angular

[Shane Ardell]

There are a couple of good examples in Metron Alerts showing different
advantages we would gain using NgRx. First, you’ll notice that a lot of
state does not persist between view changes. For example, if a user inputs
search criteria into the search bar, switches to the PCAP view, then
switches back, that search input is not persisted. If we used NgRx, the
application store can persist this state between view changes if we wanted
to. The importance of this will continue to become more apparent as the
application scales up and different views are added.

In addition, there is quite a bit of shared application data between
components. For example, you’ll see that both the GroupByComponent and
AlertFiltersComponent display the number of facets available. When you
filter by a facet, these numbers update. You can filter by clicking on the
facets available in the AlertFiltersComponent, or you can search with a
filter keyword and value in the search bar. Multiple areas of the
application are showing the same data, and multiple areas of the
application are manipulating that data. While passing data through @Input
and @Output decorators and services is fine for basic sharing of
application data, you’ll eventually create a complex web of data sharing
and mutation that can be hard to follow and debug. In my opinion, we are
nearing that point in our application. NgRx solves this with its
one-direction data flow and immutable data structures. The store is the
single source of truth which your component derives state from rather than
having components holding their own state and having to manage, communicate
and pass data between them.

There are also many debugging advantages. I don’t have a specific example
at the moment, but you can probably imagine how much easier it is to “time
travel” with NgRx debugging tools. What I mean by “time travel” is the
ability to move back and forth among the previous application states and
view the results in real-time rather than setting a breakpoint, reloading
the application, inspecting, setting another breakpoint to inspect a state
previous to your current breakpoint, reloading the application, etc. This
is a very repetitive and time-consuming thing to do when debugging on the
front-end, and is very common. For a visual example of this, here is a
video containing a decent overview of debugging with NgRx:
https://www.youtube.com/watch?v=70ojPxMA7Ig

On Tue, Nov 27, 2018 at 5:30 AM James Sirota  wrote:

> I found a helpful article here:
> https://brianflove.com/2018/01/08/ngrx-the-basics/
>
> A lot of this goes over my head, but in a nutshell, it's a tree-based
> state management object for JS.  Its main drawback seems to be added
> complexity, but if the guys who are more familiar with UI say we would
> benefit from it I am inclined to take them at their word.
>
> 26.11.2018, 13:09, "Michael Miklavcic" :
> > Shane, thanks for sharing this. Can you perhaps describe a sample use
> case
> > in the UI currently and explain for us how it currently works (or
> doesn't,
> > ha) versus how it would be modified and improved with using NgRx?
> >
> > Thanks,
> > Mike
> >
> > On Fri, Nov 23, 2018 at 7:44 AM Shane Ardell 
> > wrote:
> >
> >>  What I'm referring to is roughly the entire contents of the UI
> >>  application's memory.
> >>
> >>  On Thu, Nov 22, 2018 at 6:29 PM Otto Fowler 
> >>  wrote:
> >>
> >>  > Can you describe what you mean by “state” in a little more detail?
> Not a
> >>  > complete description, maybe just a crib list.
> >>  >
> >>  >
> >>  > On November 22, 2018 at 07:21:43, Shane Ardell (
> shane.m.ard...@gmail.com
> >>  )
> >>  > wrote:
> >>  >
> >>  > As both the Management and Alerts UI grow in size, managing
> application
> >>  > state continues to become more and more complex. To help us deal with
> >>  > managing all of this state and ensuring our application derives state
> >>  from
> >>  > a single source of truth, I suggest we start using NgRx, a state
> >>  > management
> >>  > library based on the Redux pattern but built for Angular. It is by
> far
> >>  the
> >>  > most popular library of this type for Angular. As you can see in the
> >>  > project's GitHub Insights tab <
> https://github.com/ngrx/platform/pulse>,
> >>  > it's quite actively worked on and releases are pretty frequent. The
> >>  > project
> >>  > is licensed under MIT.
> >>  >
> >>  > As far as an approach to integration, I don't think we necessarily
> need a
> >>  > big refactoring right off the bat. I feel something like this can be
> done
> >>  > in a piecemeal approach over time. I think we can start by
> introducing it
> >>  > into the project the next time we have a new application feature.
> >>  >
> >>  > What are everyone's thoughts around this?
> >>  >
> >>  > Cheers,
> >>  > Shane
> >>  >
> >>  >
>
> ---
> Thank you,
>
> James Sirota
> PMC- Apache Metron
> jsirota AT apache DOT org
>
>

Re: [ANNOUNCE] Shane Ardell is a committer

[Casey Stella]

Congrats Shane!  Well deserved!

On Tue, Nov 27, 2018 at 7:24 AM Tamás Fodor  wrote:

> Congratulations Shane! 
>
> On Mon, Nov 19, 2018 at 5:58 PM Mohan Venkateshaiah <
> mvenkatesha...@hortonworks.com> wrote:
>
> > Congrats Shane !!
> >
> > Thanks
> > Mohan DV
> >
> > On 11/19/18, 10:26 PM, "Michael Miklavcic"  >
> > wrote:
> >
> > Congrats!
> >
> > On Mon, Nov 19, 2018 at 8:56 AM Shane Ardell <
> shane.m.ard...@gmail.com
> > >
> > wrote:
> >
> > > I want to extend a huge thank you to everyone part of Apache
> > Metron's PMC
> > > for offering me this opportunity!
> > >
> > > Cheers,
> > > Shane
> > >
> > > On Mon, Nov 19, 2018 at 4:53 PM zeo...@gmail.com  >
> > wrote:
> > >
> > > > Congrats Shane!
> > > >
> > > > Jon
> > > >
> > > > On Mon, Nov 19, 2018 at 10:43 AM Anand Subramanian <
> > > > asubraman...@hortonworks.com> wrote:
> > > >
> > > > > Many congratulations, Shane!
> > > > >
> > > > > Cheers,
> > > > > Anand
> > > > >
> > > > > On 11/19/18, 8:36 PM, "James Sirota" 
> wrote:
> > > > >
> > > > >
> > > > > The Project Management Committee (PMC) for Apache Metron
> has
> > > invited
> > > > > Shane Ardell to become a committer and we are pleased to
> > announce that
> > > he
> > > > > has accepted.  I wanted to congratulate Shane on this
> > achievement.
> > > > >
> > > > >
> > > > > Being a committer enables easier contribution to the
> project
> > since
> > > > > there is no need to go via the patch submission process. This
> > should
> > > > enable
> > > > > better productivity. Being a PMC member enables assistance with
> > the
> > > > > management and to guide the direction of the project.
> > > > > ---
> > > > > Thank you,
> > > > >
> > > > > James Sirota
> > > > > PMC- Apache Metron
> > > > > jsirota AT apache DOT org
> > > > >
> > > > >
> > > > >
> > > > > --
> > > >
> > > > Jon Zeolla
> > > >
> > >
> >
> >
> >
>

Re: [ANNOUNCE] Shane Ardell is a committer

[Tamás Fodor]

Congratulations Shane! 

On Mon, Nov 19, 2018 at 5:58 PM Mohan Venkateshaiah <
mvenkatesha...@hortonworks.com> wrote:

> Congrats Shane !!
>
> Thanks
> Mohan DV
>
> On 11/19/18, 10:26 PM, "Michael Miklavcic" 
> wrote:
>
> Congrats!
>
> On Mon, Nov 19, 2018 at 8:56 AM Shane Ardell  >
> wrote:
>
> > I want to extend a huge thank you to everyone part of Apache
> Metron's PMC
> > for offering me this opportunity!
> >
> > Cheers,
> > Shane
> >
> > On Mon, Nov 19, 2018 at 4:53 PM zeo...@gmail.com 
> wrote:
> >
> > > Congrats Shane!
> > >
> > > Jon
> > >
> > > On Mon, Nov 19, 2018 at 10:43 AM Anand Subramanian <
> > > asubraman...@hortonworks.com> wrote:
> > >
> > > > Many congratulations, Shane!
> > > >
> > > > Cheers,
> > > > Anand
> > > >
> > > > On 11/19/18, 8:36 PM, "James Sirota"  wrote:
> > > >
> > > >
> > > > The Project Management Committee (PMC) for Apache Metron has
> > invited
> > > > Shane Ardell to become a committer and we are pleased to
> announce that
> > he
> > > > has accepted.  I wanted to congratulate Shane on this
> achievement.
> > > >
> > > >
> > > > Being a committer enables easier contribution to the project
> since
> > > > there is no need to go via the patch submission process. This
> should
> > > enable
> > > > better productivity. Being a PMC member enables assistance with
> the
> > > > management and to guide the direction of the project.
> > > > ---
> > > > Thank you,
> > > >
> > > > James Sirota
> > > > PMC- Apache Metron
> > > > jsirota AT apache DOT org
> > > >
> > > >
> > > >
> > > > --
> > >
> > > Jon Zeolla
> > >
> >
>
>
>