Re: [VOTE] Apache Metron 0.4.0 release

2017-07-03 Thread Otto Fowler 
Great job everyone


On July 4, 2017 at 00:49:59, Matt Foley (ma...@apache.org) wrote:

The vote has passed, with:
+1: 7 (3 binding, 4 non-binding)
0: none
-1: none

Thanks to all who tested and voted!
I am now going through the release process and will “ANNOUNCE” when done.

Thanks,
--Matt

On 6/30/17, 1:46 PM, "Ryan Merriman"  wrote:

+1 (binding)

- Verified Keys
- Verified mvn clean install
- Ran full dev and performed several smoke tests including:
- tested several REST endpoints
- verified data in ES
- tested Management UI
- verified Storm topologies in Storm UI
- verified data in Kibana


On Fri, Jun 30, 2017 at 12:24 PM, Matt Foley 
wrote:

> Hey all, we need more votes!
>
> So far we have 6 +1’s (including mine) and no 0’s or -1’s.
> BUT, only two are binding, ie from PMC members.
> Rules require 3 or more PMC member +1’s. Could one more
> member please step up and vote?
>
> Thanks!
> --Matt
>
> On 6/29/17, 3:00 PM, "James Sirota"  wrote:
>
> +1 (Binding)
>
> * Verified Keys
> * Verified mvn clean install completed successfully
> * Verified AWS install of core via Mpack
>
>
> 29.06.2017, 09:14, "Justin Leet" :
> > +1 (Non-binding)
> >
> > * Verified Keys
> > * Verified mvn clean install completed successfully
> > * Ran full dev: saw data flow through, ran a couple of the REST
> APIs, and
> > opened up and clicked through a bit of the Management API.
> > * Examined site-book and didn't see any issues
> >
> > On Thu, Jun 29, 2017 at 11:46 AM, Casey Stella 
> wrote:
> >
> >> +1 (binding)
> >> * Verified keys
> >> * Verified mvn build
> >> * Verified unit and integration tests run
> >> * Verified license check runs
> >> * Verified fulldev spun up with smoketest
> >>
> >> On Wed, Jun 28, 2017 at 8:10 PM, Anand Subramanian <
> >> asubraman...@hortonworks.com> wrote:
> >>
> >> > +1 (non-binding)
> >> >
> >> > * Brought up Metron stack on 12-node CentOS7 openstack cluster
> >> > * Verify all services come up fine [PASS]
> >> > * Bro, YAF and snort - ingest into respective kafka topics and
> write
> >> > indices [PASS]
> >> > * Add squid telemetry, ingest into kafka topic and write indices
> [PASS]
> >> > * Metron YAF Zeppelin dashboard with sample ingested YAF data
> [PASS]
> >> > * Management UI and REST Swagger UI sanity check [PASS]
> >> >
> >> >
> >> > -Anand
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > On 6/28/17, 12:06 AM, "Matt Foley"  wrote:
> >> >
> >> > >This is a call to vote on releasing this rc4 as “Apache Metron
> 0.4.0”.
> >> > >(Note: this is rc4 because the release candidate needed to be
> modified
> >> > with another commit after the rc3 tag was pushed to public.)
> >> > >
> >> > >Full list of changes in this release:
> >> > >https://dist.apache.org/repos/dist/dev/metron/0.4.0-
> RC4/RELEASE_NOTES
> >> > >
> >> > >The tag/commit to be voted upon is:
> >> > >d52f574f8294e453ecad3871526858a0c3c2033d (tag
> apache-metron-0.4.0-rc4)
> >> > >
> >> > >The source archive being voted upon can be found here:
> >> > >https://dist.apache.org/repos/dist/dev/metron/0.4.0-
> >> > RC4/apache-metron-0.4.0-rc4.tar.gz
> >> > >and in github at:
> >> > >https://github.com/apache/metron/tree/Metron_0.4.0
> >> > >
> >> > >Other release files, signatures and digests can be found here:
> >> > >https://dist.apache.org/repos/dist/dev/metron/0.4.0-RC4/KEYS
> >> > >
> >> > >The release artifacts are signed with the following key:
> >> > >https://dist.apache.org/repos/dist/dev/metron/0.4.0-RC4/KEYS
> >> > >pub rsa4096/4169AA27ECB31663 2011-07-31 [SCEA]
> >> > >Key fingerprint = 7854 36A7 8258 6B71 829C 67A0 4169 AA27 ECB3
> 1663
> >> > >uid = Matthew Foley (CODE SIGNING KEY) 
> >> > >
> >> > >Please vote on releasing this package as Apache Metron 0.4.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 vote will be open for at least 72 hours. Please vote one
> of the
> >> > following responses:
> >> > >+1 Release this package as Apache Metron 0.4.0-RC4
> >> > >0 No opinion
> >> > >-1 Do not release this package because...
> >> > >
> >> > >Thank you,
> >> > >--Matt
> >> > >(your friendly release manager)
> >> > >
> >> > >
> >> > >
> >> >
>
> ---
> Thank you,
>
> James Sirota
> PPMC- Apache Metron (Incubating)
> jsirota AT apache DOT org
>
>
>
>

Re: [VOTE] Apache Metron 0.4.0 release

2017-07-03 Thread Matt Foley 
The vote has passed, with:
+1:  7 (3 binding, 4 non-binding)
0: none
-1: none

Thanks to all who tested and voted!
I am now going through the release process and will “ANNOUNCE” when done.

Thanks,
--Matt

On 6/30/17, 1:46 PM, "Ryan Merriman"  wrote:

+1 (binding)

   - Verified Keys
   - Verified mvn clean install
   - Ran full dev and performed several smoke tests including:
  - tested several REST endpoints
  - verified data in ES
  - tested Management UI
  - verified Storm topologies in Storm UI
  - verified data in Kibana


On Fri, Jun 30, 2017 at 12:24 PM, Matt Foley  wrote:

> Hey all, we need more votes!
>
> So far we have 6 +1’s (including mine) and no 0’s or -1’s.
> BUT, only two are binding, ie from PMC members.
> Rules require 3 or more PMC member +1’s.  Could one more
> member please step up and vote?
>
> Thanks!
> --Matt
>
> On 6/29/17, 3:00 PM, "James Sirota"  wrote:
>
> +1 (Binding)
>
> * Verified Keys
> * Verified mvn clean install completed successfully
> * Verified AWS install of core via Mpack
>
>
> 29.06.2017, 09:14, "Justin Leet" :
> > +1 (Non-binding)
> >
> > * Verified Keys
> > * Verified mvn clean install completed successfully
> > * Ran full dev: saw data flow through, ran a couple of the REST
> APIs, and
> > opened up and clicked through a bit of the Management API.
> > * Examined site-book and didn't see any issues
> >
> > On Thu, Jun 29, 2017 at 11:46 AM, Casey Stella 
> wrote:
> >
> >>  +1 (binding)
> >>  * Verified keys
> >>  * Verified mvn build
> >>  * Verified unit and integration tests run
> >>  * Verified license check runs
> >>  * Verified fulldev spun up with smoketest
> >>
> >>  On Wed, Jun 28, 2017 at 8:10 PM, Anand Subramanian <
> >>  asubraman...@hortonworks.com> wrote:
> >>
> >>  > +1 (non-binding)
> >>  >
> >>  > * Brought up Metron stack on 12-node CentOS7 openstack cluster
> >>  > * Verify all services come up fine [PASS]
> >>  > * Bro, YAF and snort - ingest into respective kafka topics and
> write
> >>  > indices [PASS]
> >>  > * Add squid telemetry, ingest into kafka topic and write indices
> [PASS]
> >>  > * Metron YAF Zeppelin dashboard with sample ingested YAF data
> [PASS]
> >>  > * Management UI and REST Swagger UI sanity check [PASS]
> >>  >
> >>  >
> >>  > -Anand
> >>  >
> >>  >
> >>  >
> >>  >
> >>  >
> >>  > On 6/28/17, 12:06 AM, "Matt Foley"  wrote:
> >>  >
> >>  > >This is a call to vote on releasing this rc4 as “Apache Metron
> 0.4.0”.
> >>  > >(Note: this is rc4 because the release candidate needed to be
> modified
> >>  > with another commit after the rc3 tag was pushed to public.)
> >>  > >
> >>  > >Full list of changes in this release:
> >>  > >https://dist.apache.org/repos/dist/dev/metron/0.4.0-
> RC4/RELEASE_NOTES
> >>  > >
> >>  > >The tag/commit to be voted upon is:
> >>  > >d52f574f8294e453ecad3871526858a0c3c2033d (tag
> apache-metron-0.4.0-rc4)
> >>  > >
> >>  > >The source archive being voted upon can be found here:
> >>  > >https://dist.apache.org/repos/dist/dev/metron/0.4.0-
> >>  > RC4/apache-metron-0.4.0-rc4.tar.gz
> >>  > >and in github at:
> >>  > >https://github.com/apache/metron/tree/Metron_0.4.0
> >>  > >
> >>  > >Other release files, signatures and digests can be found here:
> >>  > >https://dist.apache.org/repos/dist/dev/metron/0.4.0-RC4/KEYS
> >>  > >
> >>  > >The release artifacts are signed with the following key:
> >>  > >https://dist.apache.org/repos/dist/dev/metron/0.4.0-RC4/KEYS
> >>  > >pub rsa4096/4169AA27ECB31663 2011-07-31 [SCEA]
> >>  > >Key fingerprint = 7854 36A7 8258 6B71 829C 67A0 4169 AA27 ECB3
> 1663
> >>  > >uid = Matthew Foley (CODE SIGNING KEY) 
> >>  > >
> >>  > >Please vote on releasing this package as Apache Metron 0.4.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 vote will be open for at least 72 hours. Please vote one
> of the

[GitHub] metron issue #620: Metron-988: UI for viewing alerts generated by Metron

2017-07-03 Thread iraghumitra 
Github user iraghumitra commented on the issue:

https://github.com/apache/metron/pull/620
  
@cestella & @merrimanr I have abstracted all the API calls to 
data-source.ts this should simplify plugging in any API provider.

@merrimanr plz let me know if search api looks better in terms of typings. 
Now you can look at abstract class 'DataSource' and 
'ElasticSearchLocalstorageImpl' to review all the API calls.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] metron issue #628: METRON-1011 Enforce submission of 4 params Stellar ENRICH...

2017-07-03 Thread ottobackwards 
Github user ottobackwards commented on the issue:

https://github.com/apache/metron/pull/628
  
+1 by inspection pending filling out the PR template.   Thanks for the 
contribution Jasper!


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [GitHub] metron issue #616: METRON-877 Extract core implementation and UDF support, c...

2017-07-03 Thread Otto Fowler 
This still has not hit.  Should we be concerned about merges/commits before
it does?



On July 2, 2017 at 19:27:43, mattf-horton (g...@git.apache.org) wrote:

Github user mattf-horton commented on the issue:

https://github.com/apache/metron/pull/616

This has been committed to git-wip-us.apache.org/repos/asf/metron.
Propagation seems a little slow today.



---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [GitHub] metron issue #616: METRON-877 Extract core implementation and UDF support, c...

2017-07-03 Thread Matt Foley 
Yes, it could cause problems. Not sure what to do about it. Should we open an 
INFRA ticket, or does our PMC have auth to poke it?

One can browse the (real) Apache repo and see it, it hasn't been pushed from 
there.

--Matt



On Mon, Jul 3, 2017 at 4:16 AM -0700, "Otto Fowler" 
> wrote:


This still has not hit.  Should we be concerned about merges/commits before
it does?



On July 2, 2017 at 19:27:43, mattf-horton (g...@git.apache.org) wrote:

Github user mattf-horton commented on the issue:

https://github.com/apache/metron/pull/616

This has been committed to git-wip-us.apache.org/repos/asf/metron.
Propagation seems a little slow today.



---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: PLEASE DON'T COMMIT TO APACHE METRON until propagation issue is fixed

2017-07-03 Thread Matt Foley 
All fixed! Great service from INFRA!!
Yes, we’re green to go.  Just make sure it keeps doing so as you commit new 
things :-)

On 7/3/17, 11:56 AM, "Justin Leet"  wrote:

Looks like it's already been closed, with a5b1377 as the latest commit.

We should be good to go at this point.  Any objections, Matt?

On Mon, Jul 3, 2017 at 2:39 PM, Matt Foley  wrote:

> https://issues.apache.org/jira/browse/INFRA-14502 has been opened.
>
> On 7/3/17, 11:25 AM, "Matt Foley"  wrote:
>
> It seems propagation from git-wip-us.apache.org/repos/asf/metron to
> github.com/apache/metron is currently broken.  If you browse
> https://git1-us-west.apache.org/repos/asf?p=metron.git you see that
> commit a5b13777a, for METRON-877, was committed yesterday but is still not
> present in github: https://github.com/apache/metron/commits/master (as of
> 11:20am PDT).
>
> Making commits to Apache from an incompletely merged starting point
> could cause deletion or corruption of previous commits (although of course
> experts with git could do it right if they’re aware of the problem).  I’m
> opening an INFRA ticket to request help restarting the propagation.
>
> Thanks,
> --Matt
>
> On Mon, Jul 3, 2017 at 4:16 AM -0700, "Otto Fowler" <
> ottobackwa...@gmail.com> wrote:
>
>
> This still has not hit.  Should we be concerned about
> merges/commits before
> it does?
>
>
>
> On July 2, 2017 at 16:27:43, mattf-horton (g...@git.apache.org)
> wrote:
>
> Github user mattf-horton commented on the issue:
>
> https://github.com/apache/metron/pull/616
>
> This has been committed to git-wip-us.apache.org/repos/asf/metron.
> Propagation seems a little slow today.
>
>
>
>
>
>

PLEASE DON'T COMMIT TO APACHE METRON until propagation issue is fixed

2017-07-03 Thread Matt Foley 
It seems propagation from git-wip-us.apache.org/repos/asf/metron to 
github.com/apache/metron is currently broken.  If you browse 
https://git1-us-west.apache.org/repos/asf?p=metron.git you see that commit 
a5b13777a, for METRON-877, was committed yesterday but is still not present in 
github: https://github.com/apache/metron/commits/master (as of 11:20am PDT).

Making commits to Apache from an incompletely merged starting point could cause 
deletion or corruption of previous commits (although of course experts with git 
could do it right if they’re aware of the problem).  I’m opening an INFRA 
ticket to request help restarting the propagation.

Thanks,
--Matt 

On Mon, Jul 3, 2017 at 4:16 AM -0700, "Otto Fowler" 
> wrote:


This still has not hit.  Should we be concerned about merges/commits before
it does?



On July 2, 2017 at 16:27:43, mattf-horton (g...@git.apache.org) wrote:

Github user mattf-horton commented on the issue:

https://github.com/apache/metron/pull/616

This has been committed to git-wip-us.apache.org/repos/asf/metron.
Propagation seems a little slow today.

Re: PLEASE DON'T COMMIT TO APACHE METRON until propagation issue is fixed

2017-07-03 Thread Matt Foley 
https://issues.apache.org/jira/browse/INFRA-14502 has been opened.

On 7/3/17, 11:25 AM, "Matt Foley"  wrote:

It seems propagation from git-wip-us.apache.org/repos/asf/metron to 
github.com/apache/metron is currently broken.  If you browse 
https://git1-us-west.apache.org/repos/asf?p=metron.git you see that commit 
a5b13777a, for METRON-877, was committed yesterday but is still not present in 
github: https://github.com/apache/metron/commits/master (as of 11:20am PDT).

Making commits to Apache from an incompletely merged starting point could 
cause deletion or corruption of previous commits (although of course experts 
with git could do it right if they’re aware of the problem).  I’m opening an 
INFRA ticket to request help restarting the propagation.

Thanks,
--Matt 

On Mon, Jul 3, 2017 at 4:16 AM -0700, "Otto Fowler" 
> wrote:


This still has not hit.  Should we be concerned about merges/commits 
before
it does?



On July 2, 2017 at 16:27:43, mattf-horton (g...@git.apache.org) wrote:

Github user mattf-horton commented on the issue:

https://github.com/apache/metron/pull/616

This has been committed to git-wip-us.apache.org/repos/asf/metron.
Propagation seems a little slow today.

[GitHub] metron pull request #616: METRON-877 Extract core implementation and UDF sup...

2017-07-03 Thread asfgit 
Github user asfgit closed the pull request at:

https://github.com/apache/metron/pull/616


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: PLEASE DON'T COMMIT TO APACHE METRON until propagation issue is fixed

2017-07-03 Thread Justin Leet 
Looks like it's already been closed, with a5b1377 as the latest commit.

We should be good to go at this point.  Any objections, Matt?

On Mon, Jul 3, 2017 at 2:39 PM, Matt Foley  wrote:

> https://issues.apache.org/jira/browse/INFRA-14502 has been opened.
>
> On 7/3/17, 11:25 AM, "Matt Foley"  wrote:
>
> It seems propagation from git-wip-us.apache.org/repos/asf/metron to
> github.com/apache/metron is currently broken.  If you browse
> https://git1-us-west.apache.org/repos/asf?p=metron.git you see that
> commit a5b13777a, for METRON-877, was committed yesterday but is still not
> present in github: https://github.com/apache/metron/commits/master (as of
> 11:20am PDT).
>
> Making commits to Apache from an incompletely merged starting point
> could cause deletion or corruption of previous commits (although of course
> experts with git could do it right if they’re aware of the problem).  I’m
> opening an INFRA ticket to request help restarting the propagation.
>
> Thanks,
> --Matt
>
> On Mon, Jul 3, 2017 at 4:16 AM -0700, "Otto Fowler" <
> ottobackwa...@gmail.com> wrote:
>
>
> This still has not hit.  Should we be concerned about
> merges/commits before
> it does?
>
>
>
> On July 2, 2017 at 16:27:43, mattf-horton (g...@git.apache.org)
> wrote:
>
> Github user mattf-horton commented on the issue:
>
> https://github.com/apache/metron/pull/616
>
> This has been committed to git-wip-us.apache.org/repos/asf/metron.
> Propagation seems a little slow today.
>
>
>
>
>
>