Re: [RESULT][VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-30 Thread Justin Leet
Mike is right, this is what I get for copy pasting, then not double checking the email before I sent it. I'd open up a discuss thread, rather than have it on the vote result thread. On Tue, Apr 30, 2019 at 6:59 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > btw, it's 2 "binding" -1

Re: [RESULT][VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-30 Thread Michael Miklavcic
btw, it's 2 "binding" -1’s (Otto, Mike) I started taking a look at that PR and it looks like this isn't quite as close to being able go in as I had originally expected. I want to talk about options here. It seems to me that we can: 1. Wait for PR#1360 to go in, but this is likely going to take

[RESULT][VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-30 Thread Justin Leet
The vote has failed. The voting was: 2 binding +1’s (Justin, Nick) 2 non-binding -1’s (Otto, Mike) no 0’s As discussed in the release thread, any further RC's are pending the review and merge of PR#1360 (Parser aggregation UI implementation). Thanks,

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-29 Thread Michael Miklavcic
Based on the latest comments, it looks to me like this feature for the UI is nearly complete at this point. I independently spoke with Tibor Meller offline about this and am told that 8 days were spent on testing, which is how METRON-2034 was found in the first place. That PR needs some cleanup bec

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-29 Thread Ryan Merriman
I am working on the backend change mentioned above ( https://issues.apache.org/jira/browse/METRON-2034) and should a PR up today. On Mon, Apr 29, 2019 at 1:16 PM Tamás Fodor wrote: > As Justin pointed out, we've already implemented the frontend related part > of the aggregation in https://github

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-29 Thread Tamás Fodor
As Justin pointed out, we've already implemented the frontend related part of the aggregation in https://github.com/apache/metron/pull/1360. Since it's a very big changeset, we would like to double check it again before we merge it back to master. Also, we're waiting for a small change in the backe

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-28 Thread Nick Allen
I agree with Justin. My +1 stands. Considering that this is a known gap, we have already released with this gap, and we have a backlog of numerous improvements that should be released to the community, I am not in favor of delaying the release. Metron provides a wide variety of functionality at

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-27 Thread Otto Fowler
while we can land a pr and accept the regressions, I do not think we should do a release with our default sample environment broken. -1 On April 27, 2019 at 18:11:42, Justin Leet (justinjl...@gmail.com) wrote: > Mike is correct, that is because of the combination of full dev > restrictions and t

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-27 Thread Justin Leet
Mike is correct, that is because of the combination of full dev restrictions and the lack of support in the configuration UI for parser aggregation. This was introduced in https://github.com/apache/metron/pull/1207 and also was true of the last release. Currently, parser aggregation is an advanced

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-27 Thread Anand Subramanian
I can confirm that I've seen the Mgmt UI shows the sensor status correctly when they run as single topologies. -Anand On 4/27/19, 11:37 PM, "Michael Miklavcic" wrote: I believe that is bc of parser aggregation. The UI does not support it currently. IIRC there was a PR to change the br

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-27 Thread Anand Subramanian
Hey Otto, I believe that should be possible. I currently rely on Cloudera's openstack infrastructure and framework to spin up VMs, after which I deploy the cluster by going through the install wizard manually. -Anand On 4/26/19, 7:34 PM, "Otto Fowler" wrote: Curious Anand, are your

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-27 Thread Michael Miklavcic
I believe that is bc of parser aggregation. The UI does not support it currently. IIRC there was a PR to change the bro, snort, and yaf sensors to aggregated bc full dev didn't have enough resources. The upshot is that the UI still works for single sensors, but the feature for enabling aggregated s

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-27 Thread Otto Fowler
-1 Ran the script and ran full dev, all good. In the configuration ui, the status of the sensors is not correct. It does not show any running, but they are running in storm and the data was moved correctly. On April 26, 2019 at 09:58:02, Otto Fowler (ottobackwa...@gmail.com) wrote: Curious Ana

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-26 Thread Otto Fowler
Curious Anand, are your steps for bringing up an open stack cluster something we could script like the AWS stuff? On April 26, 2019 at 09:35:29, Anand Subramanian ( asubraman...@hortonworks.com) wrote: +1 (non-binding) * Built RPMs and mpacks. * Brought up Metron stack on 12-node CentOS 7 opens

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-26 Thread Anand Subramanian
+1 (non-binding) * Built RPMs and mpacks. * Brought up Metron stack on 12-node CentOS 7 openstack cluster. * Ran sensor-stubs and validated events in the Alerts UI for the default sensors. * Management UI, Alerts UI and Swagger UI sanity check Regards, Anand On 4/26/19, 5:18 AM, "Nick Allen"

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-25 Thread Nick Allen
No, not AWS. On Thu, Apr 25, 2019, 8:49 PM Michael Miklavcic wrote: > Just curious, did you also do AWS? I haven't run that in a while. Wondered > if it worked ok. > > On Thu, Apr 25, 2019, 5:48 PM Nick Allen wrote: > > > +1 Verified release with all documented steps and ran up Full Dev. > > >

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-25 Thread Michael Miklavcic
Just curious, did you also do AWS? I haven't run that in a while. Wondered if it worked ok. On Thu, Apr 25, 2019, 5:48 PM Nick Allen wrote: > +1 Verified release with all documented steps and ran up Full Dev. > > On Thu, Apr 25, 2019 at 6:10 PM Michael Miklavcic < > michael.miklav...@gmail.com>

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-25 Thread Nick Allen
+1 Verified release with all documented steps and ran up Full Dev. On Thu, Apr 25, 2019 at 6:10 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > Ok cool, just finished the validation and updated the steps in the doc to > reflect the current code base. > > On Thu, Apr 25, 2019 at 3:45

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-25 Thread Michael Miklavcic
Ok cool, just finished the validation and updated the steps in the doc to reflect the current code base. On Thu, Apr 25, 2019 at 3:45 PM Nick Allen wrote: > No voting required. Those are just docs. Whoever is willing to correct > and has access, should be able to. Good catch. > > On Thu, Apr

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-25 Thread Michael Miklavcic
+1, I verified everything in the outlined steps except for AWS. On Thu, Apr 25, 2019 at 2:32 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > We're also not "incubator-metron" any longer. Do we require any kind of > voting or +1 on that verification page to make corrections to it? > >

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-25 Thread Nick Allen
No voting required. Those are just docs. Whoever is willing to correct and has access, should be able to. Good catch. On Thu, Apr 25, 2019 at 4:32 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > We're also not "incubator-metron" any longer. Do we require any kind of > voting or +1

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-25 Thread Michael Miklavcic
We're also not "incubator-metron" any longer. Do we require any kind of voting or +1 on that verification page to make corrections to it? On Thu, Apr 25, 2019 at 2:29 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > fyi, the steps in this doc have changed slightly per this naming > co

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-25 Thread Michael Miklavcic
fyi, the steps in this doc have changed slightly per this naming convention change as well - https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds. On Thu, Apr 25, 2019 at 1:25 PM Justin Leet wrote: > For everyone taking the time to validate and vote on the RC, there is a > cavea

Re: [VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-25 Thread Justin Leet
For everyone taking the time to validate and vote on the RC, there is a caveat. The naming conventions for the two repos are now aligned (_, instead of being '-' in the main repo and '_' in the plugin repo) along with the location of the KEYS file, I have a PR out to update the metron-rc-check scr

[VOTE] Metron Release Candidate 0.7.1-RC1

2019-04-25 Thread Justin Leet
This is a call to vote on releasing Apache Metron 0.7.1 Full list of changes in this release: https://dist.apache.org/repos/dist/dev/metron/0.7.1-RC1/CHANGES The tag to be voted upon is: apache-metron_0.7.1-rc1 The source archives being voted upon can be found here: https://dist.apache.org/repos/