I'd like to propose a vote to change our dev guidelines which will clarify
the tooling we use to produce diagrams and share the source files for those
diagrams. The original discuss thread is noted at the end of this email. I
propose the dev guidelines
0.7.1 Ryan
> > Merriman
> > METRON-2067Done 0.7.1 Michael
> > Miklavcic
> > METRON-2074Done 0.7.1 Michael
> > Miklavcic
> > METRON-2082Done
release. The last build failure on master I see was from 21 days
> > ago.
> >
> > Otherwise, I'd really like to kick off the next release.
> >
> > On Tue, Apr 16, 2019 at 11:25 AM Michael Miklavcic <
> > michael.miklav...@gmail.com> wrote:
> >
+1 to starting a feature branch for this.
+1 to removing our custom implementations if the newest revs are in fact
stable now.
Regarding the profile option - if it's possible to keep 2.6.5 for a bit and
not require separate branches or code trees, this is probably OK.
Otherwise, I'm inclined to
Just an fyi, if you run into the FileFilterUtilTest failing, pull latest
from master. There was a time-sensitive unit test condition that has now
been fixed in https://issues.apache.org/jira/browse/METRON-2166
Mike
I want to tease out your thoughts on this a bit - I've also thought that we
might want to do a bit more on the primary Jiras independent of the
associated PR. How about for PRs that go up immediately? The main PR
commend field should (or at least has traditionally, anyhow) cover all
necessary
It looks like we have come pretty close to our build time limit with Travis
again. Some builds are sneaking in under 50 minutes while others are
surpassing the limit and tripping the Travis timeout. This is a separate
issue from the maven binary download issue
Great work Justin, thanks for the contribution and ushering this through to
completion.
On Fri, Aug 16, 2019 at 1:36 PM Justin Leet wrote:
> The PR is now in master, so please update your PRs and branches
> accordingly.
>
> Justin
>
> On Fri, Aug 16, 2019 at 2:29 PM Justin Leet wrote:
>
> > Hi
Hi devs and users,
Some questions were asked in the Slack channel about our ongoing HDP/Hadoop
upgrade and I'd like to get a discussion rolling. The original Hadoop
upgrade discuss thread can be found here
Hey all,
I'm seeing quite a few Jiras that have been completed but not closed out
and marked as done. Can the committers do a quick spin through their PRs
and Jiras and check?:
1. The reporter and assignee are correct (assignee should be the
committer or contributor that did the PR - if
ork and the feature
> branch.
>
> https://issues.apache.org/jira/browse/METRON-2088
>
> On Mon, Apr 22, 2019 at 3:32 PM Michael Miklavcic <
> michael.miklav...@gmail.com> wrote:
>
> > +1 to starting a feature branch for this.
> > +1 to removing our custom impl
If this is only applicable to Centos 7, I would add it to the Centos 7
README.md. As I looked for it, it appears that this file is missing for
Centos 7. We have one for 6 here -
https://github.com/apache/metron/blob/master/metron-deployment/development/centos6/README.md.
I think it's important
, etc.
Best,
Mike
On Fri, Aug 23, 2019 at 10:52 AM Michael Miklavcic <
michael.miklav...@gmail.com> wrote:
> Hi devs,
>
> We've been at this a while now, and I want to share an update with you.
> Here's the current HDP 3.1 upgrade Jira again for reference -
> https://issues.a
t; integrations/applications. Of course definition of metron’s value beyond
> integration, and what those features and application boundaries are would
> be necessary.
>
>
>
>
> On August 26, 2019 at 18:52:57, Michael Miklavcic (
> michael.miklav...@gmail.com) wrote:
>
> Hi
can upgrade.
>>
>> The issue of what metron *is* features wise may be another one we want
>> to take up at some point. The idea being can we separate the metron
>> _integration parts from the metron core functionality such that we can work
>> on them separately and thus s
status update, Mike
>
> 28.08.2019, 16:48, "Michael Miklavcic" :
> > Update on current HDP upgrade progress.
> >
> > A separate DISCUSS thread has been spun up around how we should handle
> the
> > upgrade, backwards compatibility issues, semanti
etron’ application.
>
> Can we think of a better example for inspiration?
>
>
>
>
> On September 12, 2019 at 16:15:06, Michael Miklavcic (
> michael.miklav...@gmail.com) wrote:
>
> I'd like to discuss Metron's installation and management. We have used
> Am
I'd like to discuss Metron's installation and management. We have used
Ambari for some time now, with and without an MPack for Metron (and
Elasticsearch). While this mechanism has proved useful to the project, it
is not without cost. This makes us an outlier among Apache projects in
terms of what
in one
fell swoop as a zip and explode it out onto a node.
On Thu, Sep 12, 2019 at 3:22 PM Michael Miklavcic <
michael.miklav...@gmail.com> wrote:
> > There is no equivalent usable ‘Metron’ application.
>
> That is absolutely part of the problem here. We are a platform on a
> p
Hey all,
While working through the feature branch upgrade for HDP 3.1, we came
across some classpath related issues conflicting with Storm and Guava while
testing out Kerberos. Initially, this seemed reasonable to roll into the
Kerberos fix PR, but the scope has expanded a bit because we found
r.
>
> On Tue, Sep 17, 2019 at 1:13 PM Michael Miklavcic <
> michael.miklav...@gmail.com> wrote:
>
> > Hey all,
> >
> > While working through the feature branch upgrade for HDP 3.1, we came
> > across some classpath related issues conflicting with Storm and
Welcome Dale!
On Tue, Jul 30, 2019 at 6:37 AM Otto Fowler wrote:
> Welcome Dale!
>
> Btw: Dale is Tigerquoll on slack :)
>
>
>
>
> On July 30, 2019 at 03:09:22, Dale Richardson (tigerqu...@outlook.com)
> wrote:
>
> Hi folks,
> Greetings from down under! I just thought I'd introduce myself now
+1. I don't think there's really much to discuss, tbh. Definitely
appreciate your putting this out to the dev list, however, and I'd have
been just as happy to see it roll in via a PR. This just seems like prudent
UX design IMO. The sooner we get this, the better.
Cheers,
Mike
On Wed, Jul 24,
reasons to motivate a Curator upgrade now, but this may be
premature without more concrete details and having tried a smaller scope
change with dependency relocation first.
Mike
On Tue, Sep 17, 2019 at 4:04 PM Otto Fowler wrote:
> +1
>
>
>
>
> On September 17, 2019 at 14:53:13,
Hi all,
We're getting close to wrapping up the feature branch work for upgrading to
HDP 3.1. As previously discussed, this is a backwards incompatible upgrade
and is going to require a 1.x Metron release. There has already been some
discussion on this here -
t the Amazon script and stuff, the documentation for that?
>
I'm honestly not sure how to handle the AWS stuff because it's not free to
do. Is anyone willing to donate some resources for testing this?
>
> I see if I can think of more, hopefully you all will too.
>
>
>
>
>
. The
Zookeeper version is the same from HDP 2.5 to 2.6 to 3.1, so there should
be no added risk.
On Fri, Sep 20, 2019 at 1:52 PM Michael Miklavcic <
michael.miklav...@gmail.com> wrote:
> Discussed this a bit further with Nick and Ryan offline. The original
> issue with Curator appears to have co
Hi all,
I wanted to share that we have made available an upgrade helper script.
This will help manage backup and restore of:
- Ambari configurations pertinent to Metron
- Zookeeper configurations for Metron
This will not backup any custom jars you may have placed in parser_contrib
or
That is correct - this was/is handled in the feature branch.
On Wed, Nov 13, 2019 at 7:35 AM Justin Leet wrote:
> Someone working more on the feature branch can correct me if I'm wrong, but
> I believe that's occurring as part of the general "Upgrade HDP version"
> branch, since that involves a
I think the junit upgrade should go in also. I'm almost finished reviewing
that.
On Thu, Dec 5, 2019, 8:50 AM Justin Leet wrote:
> If we're going to do a bug fix release, I'd like to see some of the low
> hanging fix PRs get finished and merged prior to the release. We've been
> lax about
I also propose we deprecate and remove the Ubuntu OS or move that to
contrib alongside the current Docker container POC.
On Tue, Oct 29, 2019 at 11:29 AM Michael Miklavcic <
michael.miklav...@gmail.com> wrote:
> +1 regarding completely removing the AWS automated install. I also bel
+1 regarding completely removing the AWS automated install. I also believe
we should initiate work to remove Ambari and allow individual vendors to
provide their own installation packages built on top of a base platform
install. See previous discussion here -
Congrats all!
> I’m pleased to announce the release of Metron 0.3.0!
Metron-bro-plugin-kafka (to mitigate any potential future mailing list
search confusion)
On Thu, Oct 17, 2019 at 8:51 AM Otto Fowler wrote:
> Just a reminder, if you used my script to verify the RC, please comment :
>
I'd like to kick off a discussion to get a sense of how the broader
community is currently using Metron.
1. What features are you using or seriously considering? e.g.
1. enrichments
2. streaming enrichments
3. profiler
4. pcap
5. flatfile summarizer
6. MaaS
We've been working with feature branches for nearly 2 years now on this
project. We started fairly ad-hoc, and as it currently stands, we still
appear to be fairly ad-hoc after looking for documentation on feature
branch processes :). I propose we create a wiki page that includes some
basic
or perhaps a different “flavour” of
> metron that caters for finance domain and can be built as a separate
> project, although not sure how to go about it. Is that something the
> community/project owners might be interested in considering or supporting?
>
>
>
> Best regards,
&g
EOM
s to page is restricted'. *Later I got to
> know that I have to purchase their product since it is behind a payment
> wall (reference
> <https://community.cloudera.com/t5/Support-Questions/Unable-to-access-Ambari-repo/td-p/286813>
> ).
>
> If you have any information of a work aroun
Head over to Ambari http://node1:8080 and click the activity icon (should
be somewhere along the top menu bar). You should be able to see more
details about what Ambari was doing at the time of failure. It's possible
there were just some minor issues in starting up the services. If that's
the
ler
wrote:
> yes
>
>
>
>
> On January 14, 2020 at 13:05:17, Michael Miklavcic (
> michael.miklav...@gmail.com) wrote:
>
> We should probably also get this resolved for this release.
> https://issues.apache.org/jira/browse/METRON-2340. Thoughts?
>
> On Mon,
I haven't had a chance to read the details yet, but we may need to make
this portion of the dev environment manual. Other libraries, e.g. mysql,
had issues like this as well.
On Mon, Jan 13, 2020 at 4:52 AM Otto Fowler wrote:
> https://issues.apache.org/jira/browse/METRON–2340
>
>
>
Hey Otto,
As I mentioned above, we have had this issue with other components before,
e.g. mysql. I don't see a compelling reason to discontinue or push this
component to contrib just yet - it's a type of enrichment that happens to
require an additional manual step. Per the article (
13, 2020 at 5:20 PM Otto Fowler
> wrote:
>
> > I agree with all of that, my only thinking on contrib is, if that
> component
> > is not tested and has no coverage, and needs manual steps, then we may
> want
> > to separate it.
> > We would have to have some handle
> > > > > > On Thu, Dec 5, 2019 at 12:06 PM Shane Ardell <
> > > shane.m.ard...@gmail.com
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > >> Speaking on the UI-related PRs that Justin me
t; > > > >
> > > > >> Speaking on the UI-related PRs that Justin mentioned, I also would
> > > like
> > > > to
> > > > >> see both of them merged before a release. At the moment, #1527
> does
> > > not
> > >
all out they need to clean
> it up, but that may cause a lot of friction for our users.
>
> On Mon, Jan 13, 2020 at 5:52 PM Michael Miklavcic <
> michael.miklav...@gmail.com> wrote:
>
> > +1 to Apache Legal advice
> >
> > On Mon, Jan 13, 2020 at 3:30 PM Otto Fow
on that you should just denote in
> > the commit that it was a dependabot contribution, squash like we normally
> > do and not rewrite the user for attribution. dependabot does not appear
> to
> > have a username, so I think that's ok.
> >
> > On Wed, Jan 15, 2020 at 6:1
https://github.com/apache/metron/pull/1552 is now merged.
On Thu, Jan 16, 2020 at 10:22 PM Michael Miklavcic <
michael.miklav...@gmail.com> wrote:
> Thanks for the suggestion, Casey. Good find, Justin. Per the
> recommendations in the legal thread, I'm going to merge this PR now. I
&
There are notebooks part of the Ambari install/offering. I don't think it
should break anything core - you could try removing it from the deps here,
along with the config -
+1
On Mon, Nov 16, 2020 at 7:01 AM Justin Leet wrote:
> Hi all,
>
> This is a vote thread to retire Metron to the Attic, and dissolve the PMC.
> This follows a discussion thread on the dev list ([DISCUSS] Retire Metron
> to the Attic
> <
>
301 - 350 of 350 matches
Mail list logo
