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

Github user mraliagha commented on the issue: https://github.com/apache/metron/pull/620 Hi, There are few issues that we have faced during our testing. However, I am not sure they have been fixed already or not. I am just going to note them. - The play/pause button

Re: [VOTE][PROPOSAL] minor changes to release process

+1 on all. Sensible and much welcome changes. Thanks, -D... On Wed, Jul 5, 2017 at 5:47 PM, Matt Foley wrote: > (The below proposal is also stated in https://issues.apache.org/ > jira/browse/METRON-1020 ) > > The following proposed changes are small, but not just editorial

[GitHub] metron issue #633: METRON-1008: Updating travis to use trusty, moved install...

Github user jjmeyer0 commented on the issue: https://github.com/apache/metron/pull/633 Quote from @justinleet > I'd be inclined towards avoiding splitting the build if we were only getting a couple minutes out of it. I'm a little worried about being able to get three slots on

[GitHub] metron pull request #633: METRON-1008: Updating travis to use trusty, moved ...

GitHub user jjmeyer0 opened a pull request: https://github.com/apache/metron/pull/633 METRON-1008: Updating travis to use trusty, moved install to install … …step, moved verify license to earlier step, and added .npm to cache. ## Contributor Comments This is a

[GitHub] metron issue #632: METRON-1008: Updating travis to use trusty

Github user jjmeyer0 commented on the issue: https://github.com/apache/metron/pull/632 Unfortunately I will have to open a new PR. I squashed my commits when this PR was closed. Github doesn't allow to reopen PRs when force pushes occur when the PR is closed. @justinleet and

[VOTE][PROPOSAL] minor changes to release process

(The below proposal is also stated in https://issues.apache.org/jira/browse/METRON-1020 ) The following proposed changes are small, but not just editorial in nature, hence will require vote of the community to change. Our bylaws don’t have an action type of Modifying Policy, but it’s probably

Re: [ANNOUNCE] Apache Metron 0.4.0 release

Congrats, everyone! A lot of people helped out across the board, and I look forward to everyone's contributions moving ahead. On Wed, Jul 5, 2017 at 4:47 PM, Otto Fowler wrote: > Thank you Matt, your first metron release as well! > Congratulations to the community. > >

Re: [ANNOUNCE] Apache Metron 0.4.0 release

Thank you Matt, your first metron release as well! Congratulations to the community. On July 5, 2017 at 16:35:47, Matt Foley (ma...@apache.org) wrote: Friends and Colleagues, I’m happy to announce the completion and release of Apache Metron 0.4.0. Besides a bunch of great new features, this is

Re: [ANNOUNCE] Apache Metron 0.4.0 release

BTW, if you’ve recently accessed any URIs under http://metron.apache.org/, you may need to hit “refresh” in your browser to see the new updated versions. On 7/5/17, 1:35 PM, "Matt Foley" wrote: Friends and Colleagues, I’m happy to announce the completion and release

[GitHub] metron issue #632: METRON-1008: Updating travis to use trusty

Github user JonZeolla commented on the issue: https://github.com/apache/metron/pull/632 Obviously I was not very clear about what I was commenting on either so sorry about that. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[ANNOUNCE] Apache Metron 0.4.0 release

Friends and Colleagues, I’m happy to announce the completion and release of Apache Metron 0.4.0. Besides a bunch of great new features, this is also our first release as a TLP. The public website at http://metron.apache.org/ has been updated and has correct links to the new downloads and docs.

[GitHub] metron issue #632: METRON-1008: Updating travis to use trusty

Github user justinleet commented on the issue: https://github.com/apache/metron/pull/632 @JonZeolla ahh, I thought you were just making a note, so everyone knew that recommendation. Sorry about that. --- If your project is set up for it, you can reply to this email and have your

[GitHub] metron issue #632: METRON-1008: Updating travis to use trusty

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/632 I'm going to be honest. Now that we have the builds kind of working again, I'm a little hesitant to change them for anything but an absolute certainty of a return, that we completely

[GitHub] metron issue #632: METRON-1008: Updating travis to use trusty

Github user jjmeyer0 commented on the issue: https://github.com/apache/metron/pull/632 @JonZeolla that was a squashed commit that was probably a typo. I'll remove it. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

[GitHub] metron issue #632: METRON-1008: Updating travis to use trusty

Github user JonZeolla commented on the issue: https://github.com/apache/metron/pull/632 I was addressing "Testing sudo as false." In the body of the message above. --- 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

[GitHub] metron issue #632: METRON-1008: Updating travis to use trusty

Github user justinleet commented on the issue: https://github.com/apache/metron/pull/632 I'd be inclined towards avoiding splitting the build if we were only getting a couple minutes out of it. I'm a little worried about being able to get three slots on the occasionally stretched

[GitHub] metron issue #632: METRON-1008: Updating travis to use trusty

Github user justinleet commented on the issue: https://github.com/apache/metron/pull/632 @JonZeolla Completely counterintuitively, `sudo: required` is the counterpart of `sudo: false`. So this already got taken care of as part of METRON-1004. See:

[GitHub] metron pull request #632: METRON-1008: Updating travis to use trusty

GitHub user jjmeyer0 reopened a pull request: https://github.com/apache/metron/pull/632 METRON-1008: Updating travis to use trusty ….npm to cache. Added some more cacheing from 1004 ticket. Revert some changes. Reverted environment and put maven opts in

[GitHub] metron issue #572: METRON-633: Create better logging for HbaseEnrichmentWrit...

Github user zezutom commented on the issue: https://github.com/apache/metron/pull/572 @justinleet Will do, thanks for sorting out Travis! --- 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

[GitHub] metron pull request #632: METRON-1008: Updating travis to use trusty

Github user jjmeyer0 closed the pull request at: https://github.com/apache/metron/pull/632 --- 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

[GitHub] metron issue #632: METRON-1008: Updating travis to use trusty

Github user JonZeolla commented on the issue: https://github.com/apache/metron/pull/632 One brief note - I spoke to a friend on the travis infrastructure team and she recommended that if our build takes > 5m we should run on the VM (sudo: true). --- If your project is set up for

[GitHub] metron pull request #632: METRON-1008: Updating travis to use trusty

GitHub user jjmeyer0 opened a pull request: https://github.com/apache/metron/pull/632 METRON-1008: Updating travis to use trusty ….npm to cache. Added some more cacheing from 1004 ticket. Revert some changes. Reverted environment and put maven opts in

[GitHub] metron pull request #631: METRON-1019: Metron 0.4.0 manual installation guid...

GitHub user lvets opened a pull request: https://github.com/apache/metron/pull/631 METRON-1019: Metron 0.4.0 manual installation guide for CentOS 6 ## Contributor Comments This is a PR to METRON-1019. Is adds a manual installation guide for Metron 0.4.0 on CentOS 6 under a

[GitHub] metron pull request #629: METRON-1012 Update Metron public web site for 0.4....

Github user asfgit closed the pull request at: https://github.com/apache/metron/pull/629 --- 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

Re: [Request for Consensus Approval] dev branch for Stellar additional work

And another way suggested by Jon’s statement, is to not squash the commit, but leave at least one of each committer’s contributions intact. That might not be too hard to add to the prepare-commit script, it’s just an invocation of interactive rebase/squash. On 7/5/17, 10:32 AM, "Matt Foley"

Re: [Request for Consensus Approval] dev branch for Stellar additional work

Yeah, this is part of why we need the guide On July 5, 2017 at 09:23:03, zeo...@gmail.com (zeo...@gmail.com) wrote: That all sounds pretty reasonable to me. My biggest concern would be attribution during step 5 - we would need to make sure it isn't squash merged like we typically do (assuming

[GitHub] metron issue #629: METRON-1012 Update Metron public web site for 0.4.0 relea...

Github user mattf-horton commented on the issue: https://github.com/apache/metron/pull/629 Thanks, I'll proceed on @justinleet and @ottobackwards 's +1s. --- 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

Re: [Request for Consensus Approval] dev branch for Stellar additional work

Jon, good point. I was thinking we would just use the commit message to share attribution. It would be nicer to do something that would be picked up by github’s commit attribution, but unfortunately there is only one “author” field in a git commit metadata. There are discussions online

Re: [Request for Consensus Approval] dev branch for Stellar additional work

Okay, I’ll undertake to add to the committer’s guide before the first PR. From: Otto Fowler Date: Wednesday, July 5, 2017 at 6:28 AM To: "dev@metron.apache.org" , Matt Foley Subject: Re: [Request for Consensus Approval]

[GitHub] metron issue #629: METRON-1012 Update Metron public web site for 0.4.0 relea...

Github user JonZeolla commented on the issue: https://github.com/apache/metron/pull/629 I didn't review it, but I have no reason to hold it back. --- 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

[GitHub] metron issue #629: METRON-1012 Update Metron public web site for 0.4.0 relea...

Github user mattf-horton commented on the issue: https://github.com/apache/metron/pull/629 Hi @JonZeolla , you're quite right, I forgot I already opened METRON-718. Are we okay to push this patch then? --- If your project is set up for it, you can reply to this email and have

[GitHub] metron issue #619: METRON-939 Elasticsearch ES5 with Xshield client support

Github user wardbekker commented on the issue: https://github.com/apache/metron/pull/619 @JonZeolla done. --- 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,

[GitHub] metron issue #619: METRON-939 Elasticsearch ES5 with Xshield client support

Github user JonZeolla commented on the issue: https://github.com/apache/metron/pull/619 @wardbekker Can you please merge master and deconflict? --- 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

[GitHub] metron pull request #613: METRON-990: Clean up and organize flux properties

Github user asfgit closed the pull request at: https://github.com/apache/metron/pull/613 --- 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

FW: Runbook is ready for review

My apologies. I sent this doc to the wrong email alias. Please ignore this review request. Rita Rita McKissick ! Sr. Technical Writer On 7/5/17, 6:48 AM, "Rita McKissick" wrote: >There are still a couple sections that are work in progress: > > *

Re: Runbook is ready for review

Thank you for the catch, Otto. I will remove any references to incubating. Rita Rita McKissick ! Sr. Technical Writer From: Otto Fowler Date: Wednesday, July 5, 2017 at 6:51 AM To: default, "dev@metron.apache.org" Subject: Re: Runbook is ready for review Metron

Runbook is ready for review

There are still a couple sections that are work in progress: * Enriching Threat Intelligence * Configuring Indexing but please feel free to comment on the entire guide: http://dev.hortonworks.com.s3.amazonaws.com/HDPDocuments/HCS1/HCS-1-trunk/bk_runbook/content/index.html I’ll need

Re: [Request for Consensus Approval] dev branch for Stellar additional work

That all sounds pretty reasonable to me. My biggest concern would be attribution during step 5 - we would need to make sure it isn't squash merged like we typically do (assuming we do properly squash merge into the speculative branch). Not a big issue though, I guess, just need to make sure it

Re: [Request for Consensus Approval] dev branch for Stellar additional work

Just want to say, we will need updated versions of the commuter’s guide for doing commits and reviews to branches like this. The current scripts we use will need to be updated ( as we go ), the we should at least have a plan to provide these guides before the first pr. On July 5, 2017 at

[GitHub] metron issue #630: METRON-1014 StellarShell class name typo

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/630 +1 - I have been preforming this same operation in my vm's manually, this is the fix --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] metron issue #629: METRON-1012 Update Metron public web site for 0.4.0 relea...

Github user JonZeolla commented on the issue: https://github.com/apache/metron/pull/629 @mattf-horton Okay great, sounds good to me. I did a quick search before opening a new JIRA and it looks like you've already addressed this in

[GitHub] metron pull request #586: METRON-508 Expand Elasticsearch templates to suppo...

Github user asfgit closed the pull request at: https://github.com/apache/metron/pull/586 --- 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

[GitHub] metron issue #629: METRON-1012 Update Metron public web site for 0.4.0 relea...

Github user justinleet commented on the issue: https://github.com/apache/metron/pull/629 @mattf-horton To the best of my knowledge, this was the last pass that gets rid of the remaining incubator terminology. Only things left are old news items and so on that are actually from or

[GitHub] metron pull request #630: METRON-1014 StellarShell class name typo

GitHub user mattf-horton opened a pull request: https://github.com/apache/metron/pull/630 METRON-1014 StellarShell class name typo ## Contributor Comments Fix a path typo To test is trivial, but unfortunately requires building and then launching quick-dev or other

[Request for Consensus Approval] dev branch for Stellar additional work

Now that METRON-877 is in, I would like to proceed with Steps 3-6 of the remaining work to separate out Stellar functionality as an independent module. A couple people have suggested that this further development should be done in a Metron “dev branch”, where: a) changes are more visible than

[GitHub] metron issue #629: METRON-1012 Update Metron public web site for 0.4.0 relea...

Github user mattf-horton commented on the issue: https://github.com/apache/metron/pull/629 Hi @justinleet , thanks for looking at this. I removed instances of "incubator" from Website+PR+Merge, and had already fixed other cwiki pages I came across. Any other instances you noticed?