Re: MaaS + Apache Twill ?

Lambda or Kubernetes or whatever for model deployment, which would be really neat. On Tue, Apr 18, 2017 at 3:02 PM, Casey Stella <ceste...@gmail.com> wrote: > Regarding model performance, I've thought about that a bit. What I'd like > to see MaaS be able to do is provide an API that th

Re: MaaS + Apache Twill ?

Regarding model performance, I've thought about that a bit. What I'd like to see MaaS be able to do is provide an API that the models can communicate through that will send events to kafka and provides a telemetry like any other. Performance statistics, raw results for downstream analysis. We

Re: [DISCUSS] MPack components that don't support Kerberos

tto Fowler <ottobackwa...@gmail.com> wrote: > Can we test kerberized support in integration? > > > On April 13, 2017 at 10:24:43, Casey Stella (ceste...@gmail.com) wrote: > > Agreed, +1 > > On Thu, Apr 13, 2017 at 10:14 AM, Otto Fowler <ottobackwa...@gmail.com>

Re: [DISCUSS] MPack components that don't support Kerberos

Agreed, +1 On Thu, Apr 13, 2017 at 10:14 AM, Otto Fowler <ottobackwa...@gmail.com> wrote: > This should be in the dev guide and pr template > > > On April 13, 2017 at 09:43:48, Casey Stella (ceste...@gmail.com) wrote: > > Based on my understanding, we have a few axioms

Re: [DISCUSS] MPack components that don't support Kerberos

Based on my understanding, we have a few axioms that we're working from: - The installer should install a complete and workable product (i.e. after install, everything should work). Afterall, that has to be the sensible definition of 'working' for an installer - Metron should support

Re: [DISCUSS] Extracting Stellar as a component/module

I'm ok with google docs as long as when consensus is reached, it lives in the wiki. On Tue, Apr 11, 2017 at 6:35 PM, Matt Foley wrote: > I’ve copied it to the cwiki, but the thing is that cwiki only allows > comments at the bottom. With a long doc like this, that’s not very

Re: [DISCUSS] next release proposal

+1 to 0.4.0 On Tue, Apr 11, 2017 at 2:03 PM, Otto Fowler wrote: > +1 > > > On April 11, 2017 at 13:59:46, Matt Foley (ma...@apache.org) wrote: > > Hi all, > Looks to me like the vast majority of the material mentioned below has been > committed. There are still 8 recent

Re: Failing build

Yeah, this is an intermittent test failure and has to do with the migration to storm 1.0.3 and how it handles shutting down in local mode. The slot worker refuses to shut down and freezes and therefore we wait forever. I thought I had it fixed by manually clobbering the slots, but alas it

Re: [DISCUSS] The bro kafka plugin

; >>>> > > um > >>>> > > > let’s say > >>>> > > > a maven plugin and the bro plugin? > >>>> > > > > >>>> > > > > >>>> > > > > >>>> > &

Re: [DISCUSS] The bro kafka plugin

> That > > > > solves the challenge of using the packaging mechanism. > > > > > > > > We do need to reconcile what is in bro/bro-plugins and what is in > > > > Metron. > > > > There are some enhancements that I and others have mad

Re: [DISCUSS] next release proposal

I'd like to see METRON-820 get in since it's correcting a performance regression introduced earlier in the release. I'll have it in by wednesday of this week. On Tue, Apr 4, 2017 at 2:33 PM, Simon Elliston Ball < si...@simonellistonball.com> wrote: > I'd really like to see METRON-623 (the ui)

Re: Kerberos changes affected quick-dev and full-dev

Thanks David! On Mon, Apr 3, 2017 at 8:43 PM, David Lyle <dlyle65...@gmail.com> wrote: > I've pushed a new Vagrant image for Quick Dev. You should be asked to > update the box the next time you 'vagrant up' Quick Dev. > > -D... > > > On Mon, Apr 3, 2017 at 2

Re: Journey out of the Incubator (update)

/e5d106456b28562bdc947624c6f33e3281297dfd3803aab3d171bbad@%3Cgeneral.incubator.apache.org%3E On Mon, Apr 3, 2017 at 6:30 PM, Casey Stella <ceste...@gmail.com> wrote: > Hi All, > > For those of you who aren't following the discussion and vote, the > incubator general, after a vigorous discussion

Journey out of the Incubator (update)

Hi All, For those of you who aren't following the discussion and vote, the incubator general, after a vigorous discussion, voted to approve recommending Metron to become a top level project with all +1s. I will next submit the resolution to the apache board. For those following along, the

Re: Kerberos changes affected quick-dev and full-dev

t; > indexing.workers=1 > > indexing.executors=0 > > topology.worker.childopts= > > > > Justin > > > > On Mon, Apr 3, 2017 at 10:46 AM, Casey Stella <ceste...@gmail.com> > wrote: > > > >> Hey guys, > >> > >> Just a quick heads

Re: [DISCUSS] The bro kafka plugin

ing > > I agree that having a separate repo provided by Apache would be optimal, I > just don't know the process for that or if it was even reasonable to > suggest. > > Jon > > On Thu, Mar 30, 2017, 11:01 PM Casey Stella <ceste...@gmail.com> wrote: > > > Looking

Re: [DISCUSS] The bro kafka plugin

see how you'd push releases for bro plugins. On Thu, Mar 30, 2017 at 10:49 PM, Casey Stella <ceste...@gmail.com> wrote: > So, I do agree with the concern. Is there a way to host the package > within Metron? I definitely would like to see the modifications at > https://github.com/

Re: [DISCUSS] The bro kafka plugin

So, I do agree with the concern. Is there a way to host the package within Metron? I definitely would like to see the modifications at https://github.com/bro/bro-plugins/commit/b9f1f35415cb0db065348da0a5043a 8353b4a0a8 brought back into Metron and I'd love for us to host the plugin. Thoughts?

Re: Changes to development guidelines

yes indeed, I have seen taht before, created a JIRA and a PR to fix it and forgot to submit it. https://issues.apache.org/jira/browse/METRON-773 I'll submit the PR. On Mon, Mar 27, 2017 at 10:06 AM, Otto Fowler wrote: > I’m working on METRON-806, which is basically a

Re: [DISCUSS] Kerberos Support

automatically rather than relying on the set of extra kafka configs (though both approaches would work here). Sorry about that! Casey On Sat, Mar 25, 2017 at 12:14 PM, Casey Stella <ceste...@gmail.com> wrote: > Actually, METRON-797 (https://github.com/apache/incubator-metron/pull/490) >

Re: [DISCUSS] Kerberos Support

to get it to a > PR-able form. > > Thoughts? > > -D... > > On Fri, Mar 24, 2017 at 23:03 Casey Stella <ceste...@gmail.com> wrote: > > > Hi All, > > > > I'd like to talk and start to formulate a plan around supporting running > > Metron on a kerberized c

[DISCUSS] Kerberos Support

Hi All, I'd like to talk and start to formulate a plan around supporting running Metron on a kerberized cluster. This is a big bundle of work and seems dauntingly nebulous, so I wanted to have a chat and get a firm direction. When initially contemplating the issue, it's apparent that there are a

Re: [MENTORS] initiating the TLP vote

Sounds good, thanks Taylor. I'll write up the email and start the discussion on incubator general. On Thu, Mar 23, 2017 at 1:58 PM, P. Taylor Goetz wrote: > Anyone can do this, it doesn’t need to be a mentor or the proposed VP. > It’s much like a release vote: Forward a copy

Re: [DISCUSS][PROPOSAL] Acceptance Tests

e property or inventory files. Just need to run > > scripts and hit rest endpoints right? Just an idea, maybe it's overkill. > > I'm cool with rolling our own. > > > > On Wed, Mar 22, 2017 at 1:49 PM, Casey Stella <ceste...@gmail.com> > wrote: > > > >> May

Re: [DISCUSS][PROPOSAL] Acceptance Tests

n. > > On Wed, Mar 22, 2017 at 1:49 PM, Casey Stella <ceste...@gmail.com> wrote: > > > Maybe, but I'd argue that we would want this to be run against a > > non-ansible installed cluster. For a first pass, I'd recommend just a > set > > of shell scripts utilizin

Re: [DISCUSS][PROPOSAL] Acceptance Tests

ample, I don't think it makes sense to cover most of the profiler > > windowing DSL language edge cases in acceptance tests instead of or in > > addition to unit/integration tests unless there is something specific to > > the integration with a given an environment that we thi

Re: [DISCUSS] Stepping down as release manager

e the responsibilities of a > > release manager for the Metron project. > > > > On Mar 21, 2017 6:57 PM, "Casey Stella" <ceste...@gmail.com> wrote: > > > > > I've been extremely honored to spend the last few months as the Metron > > > Rel

[DISCUSS] Stepping down as release manager

I've been extremely honored to spend the last few months as the Metron Release Manager. That being said, my watch is ended and it's time for another release manager to step into my place. Who would like to volunteer to be release manager for the next release of Metron? Best, Casey

Re: [ANNOUNCE] Apache Metron (incubating) 0.3.1 is released

ron Integration classes (ottobackwards) closes apache/incubator-metron#350 * METRON-561 ShellEditor tests hang if vim is set as EDITOR in your profile (ottobackwards) closes apache/incubator-metron#351 On Fri, Mar 17, 2017 at 11:18 AM, Casey Stella <ceste...@gmail.com> wrote: > I am very proud to

[ANNOUNCE] Apache Metron (incubating) 0.3.1 is released

I am very proud to announce that the 0.3.1 release bits have been released. You can see this reflected on our website at http://metron.apache.org/documentation/#releases Also, I want to point out that our github documentation for the release is currently located at

Re: [DISCUSS] Apache Rat Exclusions

t; in the LICENSE?* > > These come from Bento and are Apache licensed. LICENSED and NOTICED. > > Agree with your conclusions above. > > -D... > > > > > On Thu, Mar 16, 2017 at 3:25 PM, Casey Stella <ceste...@gmail.com> wrote: > > > As part

[DISCUSS] Apache Rat Exclusions

As part of the mentor feedback on our 0.3.1 release, it was noted that we have broad apache rat exclusions in our top level pom. It was suggested that we distribute those to the individual relevant modules rather than having them in the top level pom. The concern is for broad exclusions from rat

Re: [VOTE] Final Board Resolution Draft

ibility of the Apache Metron Project; and be it further > > RESOLVED, that the persons listed immediately below be and > hereby are appointed to serve as the initial members of the > Apache Metron Project: > > > PPMC: > Mark Bittmann > Sheetal Dolas > Debo Dutta > Disc

Re: [MENTORS] POLL: Staying after graduation

+1 to that. Thanks Billie! On Mon, Mar 13, 2017 at 6:28 PM, James Sirota wrote: > Billie, thank you for your guidance and support. We really appreciate you > being a part of this journey with us > > 13.03.2017, 08:09, "Billie Rinaldi" : > > James, > > >

Re: [VOTE] Metron to graduate to TLP

+1 (binding) On Mon, Mar 13, 2017 at 6:37 PM, James Sirota wrote: > +1 (binding) > > 13.03.2017, 15:37, "James Sirota" : > > Do we feel it's time for us to exit the Apache incubator and petition to > make Metron a TLP? > > > > Please vote 1 for yes, -1

Re: [DISCUSS] Metron VP

Thanks so much for the confidence, James. I'm happy to serve if selected. On Mon, Mar 13, 2017 at 12:20 AM, James Sirota <jsir...@apache.org> wrote: > I would like to propose that Casey Stella be our VP upon graduation. I > think has been the most outspoken proponent of the "A

Re: [Discuss] SIDELOADING PARSERS: Parsers as components

t; deployed part if it is newer ) > * setting up the classloader hierarchy between the ‘system’ and provided > things, and the dependencies of the individual plugin > > > > On March 10, 2017 at 15:56:08, Casey Stella (ceste...@gmail.com) wrote: > > Why would we need classpath

Re: [Discuss] SIDELOADING PARSERS: Parsers as components

Zeolla, isn’t going to care > about the intermediate step, > he wants the archetype that builds the ‘metron parser plugin’. > > Which is why I hesitate to put out an archetype that is going to obsolete > so soon. > > Does that make sense? > > On March 10, 2017 at 14:50:55, Cas

Re: [Discuss] SIDELOADING PARSERS: Parsers as components

Why would we need classpath isolation here in the case of the parser? On Fri, Mar 10, 2017 at 3:55 PM, Otto Fowler <ottobackwa...@gmail.com> wrote: > I *would* use the classloader part, extending it with VFS. > > > > On March 10, 2017 at 15:53:05, Casey Stella (ceste...@gmai

Re: [Discuss] SIDELOADING PARSERS: Parsers as components

Also, it's not clear that we're ever going to need the classloader bits from nar for parsers since they are naturally isolated by storm topology. I might be wrong there though; do you see a scenario? On Fri, Mar 10, 2017 at 3:53 PM, Casey Stella <ceste...@gmail.com> wrote: > I'm a bi

Re: [DISCUSS] SIDELOADING PARSERS: Packaging and Loading and Extensions [oh.my]

ices > where multiple parsers or plugin types may need to be loaded, it would make > more sense. > Rest may be that case. Stellar may be that case too, if anyone ever > writes a stellar function with different dependencies than the platform. > > > > On March 10, 2017 at 14:32:00,

Re: [DISCUSS] SIDELOADING PARSERS: REST API

This is another reason to consider deploying custom parsers to HDFS and reusing the classloader, we can adjust the REST api to search the centralized store of 3rd party parsers (HDFS). On Fri, Mar 10, 2017 at 10:10 AM, Otto Fowler wrote: > As previously discussed here,

Re: [Discuss] SIDELOADING PARSERS: Parsers as components

I'm a little concerned about this increasing the size and length of the build due to the repeated shading. Should we figure out a way to deploy jars with provided dependencies on metron-parser-common as suggested in the previous JIRAs first? On Fri, Mar 10, 2017 at 2:31 PM, Matt Foley

Re: [DISCUSS] SIDELOADING PARSERS: Packaging and Deployment

I really don't like the 2x build size. I think we can at this point do something similar to side-loading of stellar functions to remove that concern. This should be easy now that that's in master. What I'd like to see as a MVP is: - the maven archetype to have a "provided" dependency to

Re: [DISCUSS] Unique id for messages

Yes, we do use a UUID in the enrichment topology; this is our message join key on the join portion of the split/join enrichment. The logic being used is EnrichmentSplitterBolt.java line 63. We might bring that out and make it part of the message IMO and be able to reuse that unique identifier

Re: SHELL_EDIT Stellar command and execution context

That means that it will attempt to get the capability and if it's not there, it won't throw an exception, but rather just return Optional.empty(). Yeah, we probably actually *do* want an exception thrown there in the case where we're not in a shell context (probably don't want vim starting inside

Re: [MENTORS][REQUEST] Please review the release currently going on in incubator-general

Sorry, I missed an email in my search. We have 1 review (thanks Billie! :), need 2 more. On Thu, Mar 9, 2017 at 1:25 PM, Casey Stella <ceste...@gmail.com> wrote: > Hi Mentors, > > We have a release going on in incubator-general for around 10 days now > with no reviews. Would

[MENTORS][REQUEST] Please review the release currently going on in incubator-general

Hi Mentors, We have a release going on in incubator-general for around 10 days now with no reviews. Would a couple of y'all mind reviewing for us? Thanks, Casey

Re: Metron Rest - where is reflections coming from?

It should get it from Metron common and IntelliJ is showingnme the same issue. I'm baffled by it, slightly. Maven builds just fine, so who knows. Its on my list of oddities to look at post-vacation. On Tue, Mar 7, 2017 at 12:57 Otto Fowler wrote: > >

Re: [DISCUSS][PROPOSAL] Acceptance Tests

d *tightly* associate with real > uses and additonally include non-happy-path? > > On Fri, Mar 3, 2017 at 12:57 PM, Casey Stella <ceste...@gmail.com> wrote: > > > It is absolutely not a naive question, Matt. We don't have a lot (or > any) > > docs about our integra

Re: Site Book

Not yet, we don't have an official 0.3.1 release yet. When the voting ends in incubatorngeneral there will be a PR to update our website with the current one. On Sun, Mar 5, 2017 at 14:43 Nick Allen wrote: > Is the site book for the *official* 0.3.1 release available

Re: [DISCUSS][PROPOSAL] Acceptance Tests

amount of time. There are obviously tickets to optimize these things, > but > I would like to make sure we don't pile too much on to every testing > cycle > before a PR. Having said that, I think the testing proposed is > absolutely > valuable enough to go forward with. >

Re: [DISCUSS][PROPOSAL] Acceptance Tests

Justin > > On Fri, Mar 3, 2017 at 8:33 AM, Casey Stella <ceste...@gmail.com> wrote: > > > I also propose, once this is done, that we modify the developer bylaws > and > > the github PR script to ensure that PR authors: > > > >- Update the acceptance

Re: [DISCUSS][PROPOSAL] Acceptance Tests

I also propose, once this is done, that we modify the developer bylaws and the github PR script to ensure that PR authors: - Update the acceptance tests where appropriate - Run the tests as a smoketest On Fri, Mar 3, 2017 at 8:21 AM, Casey Stella <ceste...@gmail.com> wrote: &g

[DISCUSS][PROPOSAL] Acceptance Tests

Hi All, After doing METRON-744, where I had to walk through a manual test of every place that Stellar touched, it occurred to me that we should script this. It also occurred to me that some scripts that are run by the PR author to ensure no regressions and, eventually maybe, even run on an INFRA

Re: [PROPOSAL] Reduce Reliance on Ansible for Deployment

Just to clarify, your 1 and 2, which you're working on, will give us the ability with full-dev (not quick-dev) to exercise the RPMs and management pack on the non-sensor code (i.e. the current state of the management pack). As far as I'm concerned, this is huge. This ensures we have an easy

Re: [GitHub] incubator-metron issue #468: METRON-744: Allow Stellar functions to be loade...

I did not see anything like that in the ansible logs, but I guess I can't be sure. On Thu, Mar 2, 2017 at 8:49 AM, David Lyle wrote: > I have not. Did HDFS die while quick-dev was coming up? > > -D... > > On Wed, Mar 1, 2017 at 9:15 PM, cestella

Re: [DISCUSS] Making adding new 3rd-party Stellar functions easier

f loading from a configured location in HDFS. This > gives a far smaller scope of filesystem to be watched and/or searched, and > of course obviates the deploy-to-many-servers problem. Altho it costs > another upload/maintenance tool for the admin to fiddle with. > > Thanks, >

Re: [DISCUSS] System time vs. Event Time

I think this is a really tricky topic, but necessary. I've given it a bit of thought over the last few months and I don't really see a great way to do it given the Profiler. Here's what I've come up with so far, though, in my thinking. - Replaying events will compress events in time (e.g. 2

Re: METRON-646 commit attribution

+1 On Mon, Feb 27, 2017 at 10:11 PM, Kyle Richardson <kylerichards...@gmail.com > wrote: > Just to confirm. Please reply +1 if you're okay for me to commit the revert > / re-commit of METRON-646 (PR#441). > > Thanks, > Kyle > > On Mon, Feb 27, 2017 at 9:25 PM, Casey

Re: Travis CI Changes have broken my heart..... or my builds

gt; Of course the same commands build locally > > > > On February 25, 2017 at 09:17:50, Otto Fowler (ottobackwa...@gmail.com) > wrote: > > https://s3.amazonaws.com/archive.travis-ci.org/jobs/205276680/log.txt > > > On February 25, 2017 at 08:20:54, Casey Stella (c

Re: METRON-646 commit attribution

b 27, 2017 at 6:55 PM, Casey Stella <ceste...@gmail.com> wrote: > > > I think it should be changed, but I'm not sure how to change it. I think > it > > should be changed because our git history is our legal trail of > > attribution. Mucking with it is relatively seri

Re: METRON-646 commit attribution

I think it should be changed, but I'm not sure how to change it. I think it should be changed because our git history is our legal trail of attribution. Mucking with it is relatively serious business. As to how, normally I'd say git commit --amend --author "kylerichardson <

Re: question about shading

Metron-common is shaded so that we can use a more recent version of guava which some of our functionality relies upon but does not play nice with the version brought in with HBase (by relocating gauva). I, personally, believe that we should - Reduce our dependence on guava until we no longer

[DISCUSS] Making adding new 3rd-party Stellar functions easier

Hi All, The benefit of Stellar is that adding new functionality is as simple as providing a Jar. This enables people who want to integrate with Metron to easy add enrichments or other functionality. The snag currently with this is that we provide a single jar, so all stellar functions that we

[RESULT] [VOTE] Releasing Apache Metron (incubating) 0.3.1-RC5

The release passes: +1 (binding): - James Sirota - David Lyle - Ryan Merriman - Casey Stella +1 (non-binding): - Justin Leet

Re: Odd integration-test failures on Fedora/CentOS for RC5

METRON-743 (https://github.com/apache/incubator-metron/pull/467) for reference. On Sat, Feb 25, 2017 at 11:51 PM, Casey Stella <ceste...@gmail.com> wrote: > Hmm, that's a very good catch if it's the issue. I was able to verify > that if you botch the sort order of the files t

Re: Odd integration-test failures on Fedora/CentOS for RC5

Hmm, that's a very good catch if it's the issue. I was able to verify that if you botch the sort order of the files that it fails. Would you mind sorting the files on PcapJob line 199 by filename? Something like Collections.sort(files, (o1,o2) -> o1.getName().compareTo(o2.getName())); I'm going

Re: Files modified after building

n 2/25/17, 7:39 PM, "Casey Stella" <ceste...@gmail.com> wrote: > > Crap, those are generated by the new profile selector dsl committed > Friday. > I must've missed them on a commit on the PR. They are generated by the > build, so it was f

Re: Files modified after building

Crap, those are generated by the new profile selector dsl committed Friday. I must've missed them on a commit on the PR. They are generated by the build, so it was factored into the tests and such for the PR. Sorry for the inconvenience, I'll have to make another PR on Monday to get them in. On

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.1-RC5

What exactly are the errors that you saw, Ryan? On Sat, Feb 25, 2017 at 07:31 David Lyle <dlyle65...@gmail.com> wrote: > Is there any reason full dev shouldn't be working? > > On Fri, Feb 24, 2017 at 9:19 PM, Casey Stella <ceste...@gmail.com> wrote: > > > Sounds

Re: Travis CI Changes have broken my heart..... or my builds

I have not seen those "no output received for 10m errors before. Can you change the Travis command to not have -q for maven so we can see more context? On Sat, Feb 25, 2017 at 07:56 Otto Fowler wrote: > I have not had a build work on Travis CI ( linked to my fork ) in 4

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.1-RC5

t 9:22 AM, Justin Leet <justinjl...@gmail.com> > wrote: > > > +1 (non-binding) > > > > Verified signature > > Ran build and tests in maven > > Ran up in quick-dev and saw data flow through topologies into the UI > > Ensured the REPL spun up and p

Re: JSONMapParser Normalizer aka Flattener

I don't know, I think I'm ok with lists, but I might be biased. I think it's the nested maps that were the issue. Flattening lists seems...wrong to me. Maybe that's wrong-headed, but there it is. ;) On Fri, Feb 24, 2017 at 10:12 AM, Nick Allen wrote: > Per Otto's advice,

Re: [DISCUSS] Top domains enrichment config/extractor management

Late to chime in here, but I feel that we have discussed Ambari's role before and I think we should probably clarify, as a community a few things with regards Ambari vs a management UI built around the REST PR currently under review. (I promise, I will get to the topic at hand eventually ;) :

Re: [DISCUSS] Metron Alerts UI

d not be > complex to implement. > - Agreed on offering intuitive ways to filter messages by fields. > > Ryan > > On Thu, Feb 23, 2017 at 6:42 PM, Casey Stella <ceste...@gmail.com> wrote: > > >- What does "Escalate" do exactly? > >- Where does

Re: [DISCUSS] Metron Alerts UI

- What does "Escalate" do exactly? - Where does the Alert ID come from? - Are the fields displayed configurable? - It'd be nice to be able to select a set of fields for a message and have the list of messages filter to just those where those fields are the same as the one viewed.

[VOTE] Releasing Apache Metron (incubating) 0.3.1-RC5

This is a call to vote on releasing Apache Metron 0.3.1-RC5 incubating Full list of changes in this release: https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5-incubating/CHANGES The tag/commit to be voted upon is apache-metron-0.3.1-rc5-incubating:

Travis is taking a long time to start Metron builds

Yesterday we waited all day for the METRON-734 PR to even start (only to have it fail in a sporadic failure, but there's a PR for that too ;). On the PR, I moved to allow the travis result to be an indication of a good build after waiting 3 hours for Travis to start our build. I would prefer to

Re: [MENTORS] The 0.3.1 RC is up at incubator-general, but we need your assistance

ooks like the community supports cancelling that vote and > issuing a new RC, do you still want reviews? > > -Taylor > > > On Feb 22, 2017, at 9:01 AM, Casey Stella <ceste...@gmail.com> wrote: > > > > We have a release candidate up for a vote at incubator-general but it

Re: [DISCUSS] 0.3.1 Release situation

gt; > > > On Wed, Feb 22, 2017 at 10:27 AM, Casey Stella <ceste...@gmail.com> > wrote: > > > > > As you are all aware by now, we have an issue with our maven build. In > > > short, we tripped on https://github.com/maxmind/GeoIP2-java/issues/77 > > > &

[DISCUSS] 0.3.1 Release situation

As you are all aware by now, we have an issue with our maven build. In short, we tripped on https://github.com/maxmind/GeoIP2-java/issues/77 As such, our build no longer works, but also our RC for 0.3.1 no longer builds. I am inclined to pull the release candidate from voting on incubator

Re: [DISCUSS] Sketch Libraries

, not a dealbreaker per se, just a thought. On Wed, Feb 22, 2017 at 6:11 AM, Casey Stella <ceste...@gmail.com> wrote: > So looking at it, it seems to fit the bill, with a couple of comments: > >- The quantiles stuff provides a CDF and PMF function, which is >sufficient for our pu

Re: [DISCUSS] Coding style via checkstyle

it would be. Either > way, I > > don't > > > > think there's a huge amount of effort to just do the reformat, > but > > we'd > > > > still want to spin everything up and test it and so on. It's > > probably > > > mor

Re: Build failures because of transitive dependencies.

I'd vote to exclude and pull in ours and then test that it still functions. I'd say that having the integration tests function should give a decent idea if it'll work in vagrant, but of course we should run it up in vagrant as well. Casey On Wed, Feb 22, 2017 at 6:07 AM, Justin Leet

Re: [DISCUSS] Sketch Libraries

So looking at it, it seems to fit the bill, with a couple of comments: - The quantiles stuff provides a CDF and PMF function, which is sufficient for our purposes. I haven't seen any real comparison between t-digests and their approach. A cursory glance at the source code leads me

[MENTORS] The 0.3.1 RC is up at incubator-general, but we need your assistance

We have a release candidate up for a vote at incubator-general but it's not gotten much attention (it's been up for more than 72 hours, but it only has one vote). Would any of you with a binding vote be willing to review it for us? Casey

Re: [DISCUSS] Coding style via checkstyle

t to just do the reformat, but we'd > > > still want to spin everything up and test it and so on. It's probably > > more > > > work for everybody to rebase onto the (vastly) reformatted code than > > > anything else, which will vary pretty significantly. > > > >

Re: [DISCUSS] Coding style via checkstyle

Any idea, with those modifications to checkstyle, how much effort it will take to reformat the code to conform? On Tue, Feb 21, 2017 at 8:23 AM, Justin Leet wrote: > As part of: > https://issues.apache.org/jira/browse/METRON-726 >

Re: [DISCUSS][PROPOSAL] Side Loading and Installation of telemetry sources [METRON-258]

Ok, This is a long one, so don't expect a coherent response just yet, but I will give some initial impressions: - I strongly agree with the premise of this idea. Making Metron extensible is and should be among the top of our priorities and at the moment, it's painful to develop a new

Re: dependencies_with_url.csv

+1 to that :) On Wed, Feb 15, 2017 at 8:15 AM, Otto Fowler <ottobackwa...@gmail.com> wrote: > METRON-722 > > > On February 15, 2017 at 10:16:02, Casey Stella (ceste...@gmail.com) wrote: > > to verify that nobody has created a transitive > dependency with a licen

Re: How would one debug MaaS service components during the integration test?

Ok, so it's a bit weird, I'll admit, but it's the nature of the beast with Yarn apps. Here's the issue: Code which executes in Yarn containers (e.g. org.apache.metron.maas.service.runner.Runner which is what the container executes and is responsible for spinning up the model shell script and

Re: dependencies_with_url.csv

It's hand-edited and used to verify that nobody has created a transitive dependency with a license that we don't know about in the build. We should probably document it in the developer guidelines. On Wed, Feb 15, 2017 at 7:14 AM, Otto Fowler wrote: > Is this generated

Re: [DISCUSS] Update Metron Release Documentation

On the subject, we should also document updating the releases page after a release and figure out how old books are stored/served up. Anyone have thoughts on that? On Wed, Feb 15, 2017 at 9:53 AM, Casey Stella <ceste...@gmail.com> wrote: > Yeah I agree we need to document it there. &

[RESULTS][VOTE] Releasing Apache Metron (incubating) 0.3.1-RC4

This vote passes. I will be submitting this to the incubator general. +1: Casey Stella (binding) James Sirota (binding) Anand Subramanian (non-binding) Matt Foley (non-binding)

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.1-RC4

+1 On Wed, Feb 15, 2017 at 7:03 AM, Casey Stella <ceste...@gmail.com> wrote: > Done. > > On Wed, Feb 15, 2017 at 10:00 AM, Casey Stella <ceste...@gmail.com> wrote: > >> That sounds good to me, Matt. I'll substitute the file and we can note >> it as a known

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.1-RC4

Done. On Wed, Feb 15, 2017 at 10:00 AM, Casey Stella <ceste...@gmail.com> wrote: > That sounds good to me, Matt. I'll substitute the file and we can note it > as a known issue. > > > On Tue, Feb 14, 2017 at 22:55 Matt Foley <ma...@apache.org> wrote: > >> I

Re: [DISCUSS] Update Metron Release Documentation

Yeah I agree we need to document it there. On Tue, Feb 14, 2017 at 09:57 zeo...@gmail.com wrote: > As a follow-up to METRON-716, I would like to suggest that we update our > Metron > Release documentation > to

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.1-RC4

S7 VM, with Ambari-2.4.2.0 and HDP-2.5.3.0 > stack (with changes from METRON-609 as known needed for single-node > deployment, especially reduced elasticsearch.master.yml) > > Ran bro data through the system and observed proportional emits from > parser, enrichment, and indexing topologies

Re: Site-Book

Yes, definitely. On Mon, Feb 13, 2017 at 09:01 Otto Fowler wrote: > Should Site-Book have a README.md describing the contents, how to build > etc? >

  1   2   3   4   >