Dear Metron Devs,

As Metron users/customers, we are very keen to have all high priority
related features/bugs to the Security as well as Metron-UI and Metron
Management-UI.

Thanks,
Ali

On Thu, Apr 6, 2017 at 8:04 AM, Ryan Merriman <merrim...@gmail.com> wrote:

> We just finished responding to the first round of feedback so I don't think
> we're that far away on METRON-623.
>
> On Wed, Apr 5, 2017 at 3:30 PM, Matt Foley <ma...@apache.org> wrote:
>
> > Totally agree would be good to have MPack support.  Let’s see how it
> > goes.  Wouldn’t want to cut it out for the sake of a day or two.
> >
> > On 4/5/17, 1:14 PM, "Justin Leet" <justinjl...@gmail.com> wrote:
> >
> >     I've made fairly good progress on
> >     https://issues.apache.org/jira/browse/METRON-799 (The MPack should
> > function
> >     in a kerberized cluster).  The PR itself might cut close to the
> > deadline,
> >     and in particular might be tough to get reviewed in time.
> >
> >     I'll do a best effort attempt to get it in to make our Kerberos story
> > more
> >     complete, but I'd say the release can go on without this (and we use
> > manual
> >     Kerberos in its absence).
> >
> >     Justin
> >
> >     On Wed, Apr 5, 2017 at 4:07 PM, Matt Foley <ma...@apache.org> wrote:
> >
> >     > Sure.  To be clear, I wasn’t proposing an exclusive list, just
> > making the
> >     > argument that there seemed to be enough to proceed with.  Any duly
> >     > committed content in the master branch, at the time we create the
> > first RC
> >     > (ie, some time after METRON-623 goes in, but not before Monday)
> will
> > surely
> >     > be included in the RC, unless something has a bug that can’t be
> > readily
> >     > resolved.
> >     >
> >     > Thanks,
> >     > --Matt
> >     >
> >     > On 4/5/17, 12:56 PM, "David Lyle" <dlyle65...@gmail.com> wrote:
> >     >
> >     >     I'm working on METRON-826 right now. I'll have a PR up today or
> >     > tomorrow at
> >     >     the latest. I'd like to see it go as well.
> >     >
> >     >     https://issues.apache.org/jira/browse/METRON-826
> >     >
> >     >     -D...
> >     >
> >     >
> >     >     On Wed, Apr 5, 2017 at 3:52 PM, Nick Allen <n...@nickallen.org
> >
> > wrote:
> >     >
> >     >     > I would like to include #509 with the Fastcapa improvements..
> >     > Already have
> >     >     > a +1.  I'm just letting it soak giving others some time to
> > review if
> >     > they
> >     >     > feel so inclined.
> >     >     >
> >     >     > https://github.com/apache/incubator-metron/pull/509
> >     >     >
> >     >     >
> >     >     > On Wed, Apr 5, 2017 at 3:50 PM, James Sirota <
> > jsir...@apache.org>
> >     > wrote:
> >     >     >
> >     >     > > I second this.  I want to see 623 go in in addition to the
> >     > kerberos work.
> >     >     > > When both are in I think it makes sense to do the release
> >     >     > >
> >     >     > > 04.04.2017, 11:33, "Simon Elliston Ball" <
> >     > si...@simonellistonball.com>:
> >     >     > > > I'd really like to see METRON-623 (the ui) get into the
> > release.
> >     > It
> >     >     > > feels like the current PR review is getting close, and that
> >     > getting it in
> >     >     > > then focussing on follow on tasks in a separate release
> > would work
> >     > well.
> >     >     > > >
> >     >     > > > I would be all for getting a release out if only for the
> >     > Kerberos work.
> >     >     > > >
> >     >     > > > Simon
> >     >     > > >
> >     >     > > >>  On 4 Apr 2017, at 20:15, zeo...@gmail.com <
> > zeo...@gmail.com>
> >     > wrote:
> >     >     > > >>
> >     >     > > >>  How far out is the management UI?
> >     >     > > >>
> >     >     > > >>  Jon
> >     >     > > >>
> >     >     > > >>>  On Tue, Apr 4, 2017, 2:09 PM Matt Foley <
> > ma...@apache.org>
> >     > wrote:
> >     >     > > >>>
> >     >     > > >>>  Hi all,
> >     >     > > >>>  Although it’s only been a few weeks since the last
> > release was
> >     >     > finally
> >     >     > > >>>  published, that process started in January :-)
> >     >     > > >>>  Also, the last commit in 0.3.1 was Feb 23, and there’s
> > been a
> >     > ton of
> >     >     > > >>>  really cool new stuff added since then:
> >     >     > > >>>
> >     >     > > >>>  Biggest items:
> >     >     > > >>>  - Multiple commits for REST API (base Jira:
> METRON-503)
> >     >     > > >>>  - Multiple commits to work with Kerberized (secure)
> > clusters
> >     > (mult.
> >     >     > > Jiras)
> >     >     > > >>>
> >     >     > > >>>  Other major new features:
> >     >     > > >>>  - METRON-690: DSL-based sparse time window
> > specification for
> >     >     > Profiler
> >     >     > > >>>  - METRON-733: Remove Geo db from ParserBolt
> >     >     > > >>>  - METRON-686: Record rule set that fired during Threat
> > Triage
> >     >     > > >>>  - METRON-743: Sort files when reading results from
> Pcap
> >     >     > > >>>  - METRON-701: Triage metrics produced by Profiler
> >     >     > > >>>  - METRON-744: Stellar external functions loaded from
> > HDFS
> >     > (and huge
> >     >     > > >>>  speed-up for function resolution)
> >     >     > > >>>  - METRON-694: Index errors from Topologies, and
> >     >     > > >>>  - METRON-745: Create Error dashboards
> >     >     > > >>>  - METRON-712: Separate eval from parse in Stellar
> >     >     > > >>>  - METRON-765: Add GUID to messages
> >     >     > > >>>  - METRON-793: Updated to storm-kafka-client spout
> >     >     > > >>>
> >     >     > > >>>  We’ve also had numerous bug fixes, docs improvements,
> > and
> >     >     > > improvements to
> >     >     > > >>>  deployment tools (docker, ansible, mpack, quickdev,
> and
> >     > fulldev).
> >     >     > > >>>
> >     >     > > >>>  I think the REST API and Kerberization, by themselves,
> > would
> >     >     > justify a
> >     >     > > >>>  release. Along with the others, I’d like to propose
> > that we
> >     > make a
> >     >     > > release
> >     >     > > >>>  soon. The time frame I had in mind was at the end of
> > this
> >     > week I
> >     >     > > could cut
> >     >     > > >>>  a release branch (so on-going work in master doesn’t
> get
> >     > blocked)
> >     >     > and
> >     >     > > start
> >     >     > > >>>  the process of generating an RC.
> >     >     > > >>>
> >     >     > > >>>  What do you-all think?
> >     >     > > >>>  Also, what additional work do you think should be
> > included in
> >     > this
> >     >     > > >>>  release, and can it realistically get done by the end
> > of this
> >     > week?
> >     >     > > The
> >     >     > > >>>  time frame is, of course, flexible at the pleasure of
> > the
> >     > community
> >     >     > –
> >     >     > > but
> >     >     > > >>>  also, there will be another release in another couple
> > months
> >     > or so,
> >     >     > > so no
> >     >     > > >>>  need to rush stuff.
> >     >     > > >>>
> >     >     > > >>>  Thanks,
> >     >     > > >>>  --Matt
> >     >     > > >>>
> >     >     > > >>>  --
> >     >     > > >>
> >     >     > > >>  Jon
> >     >     > >
> >     >     > > -------------------
> >     >     > > Thank you,
> >     >     > >
> >     >     > > James Sirota
> >     >     > > PPMC- Apache Metron (Incubating)
> >     >     > > jsirota AT apache DOT org
> >     >     > >
> >     >     >
> >     >
> >     >
> >     >
> >     >
> >     >
> >
> >
> >
> >
>



-- 
A.Nazemian

Reply via email to