Re: [Result][VOTE] Graduate Apache Kylin from the Apache Incubator

2015-10-25 Thread Luke Han 
Hi John,
 Thank you to remind and I'm sorry I was count votes only
based on my understanding, per previous discussion and your
comments in vote thread about SGA [1],  as a programmer,
I was thinking:
 if ( SGA == confirmed) {
 John's Vote = +1
 } else {
 John's Vote = -1
 }

 that's why I count your vote to +1 since the SGA is confirmed
and the status file has been updated (2015-10-17, for the copyright).

 For the date you mentioned here (2015-06-10, for license), it's
updated during the first apache release [2] [3], added Apache
license header to all source files, cleaned up any GPL or other
one and updated LICENSE, NOTICE and other files. The majority
efforts happened during that time for license and copyright. That's
why I would like to continue to keep that date.
 For v1.1 release, the situation already has been clarified
and LICENSE files has been updated [4].

 Would you mind to continue count your vote as +1 as my original
"brain computing logical":)


*[1]:*


*Thanks Luke.  If you can get a reference out to people and have
thekylin.xml updated to reflect the date, I'd be happy to add a +1
butotherwise its -1 for me for now.*
*[2]: **https://issues.apache.org/jira/browse/KYLIN-669
*
*[3]: https://issues.apache.org/jira/browse/KYLIN-715
*
*[4]: https://issues.apache.org/jira/browse/KYLIN-999
*


Best Regards!
-

Luke Han

On Mon, Oct 26, 2015 at 7:53 AM, John D. Ament 
wrote:

> Ted,
>
> After catching up on email, I see the SGA was now processed.
>
> I am concerned though after looking at their latest release vote that we're
> still missing a few things related to "Verify distribution rights."  It's
> not enough for me to say that they're far off, but after seeing the issues
> related to both SGA and license/header declarations I can't say that I can
> give the podling a warm +1 on their graduation.  Note that per the
> podling's status page they completed these steps on 2015-06-10.
>
> John
>
> On Sun, Oct 25, 2015 at 7:36 PM Ted Dunning  wrote:
>
> > John,
> >
> > Was this issue not rectified to your satisfaction?
> >
> >
> >
> > On Sun, Oct 25, 2015 at 10:15 AM, John D. Ament 
> > wrote:
> >
> > > Hi Luke,
> > >
> > > Actually I voted -1 due to your open SGA issues.
> > > On Oct 22, 2015 11:24 PM, "Luke Han"  wrote:
> > >
> > > > The vote for Apache Kylin to become a top-level project has passed
> > > > with 27 +1 votes and no 0 or -1 votes.
> > > >
> > > > Thank you everyone for taking the time to review and cast your vote.
> > > >
> > > > We will now prepare a resolution for the next Board meeting.
> > > >
> > > > 10 binding:
> > > > * Henry Saputra
> > > > * Andrew Purtell
> > > > * Bertrand Delacretaz
> > > > * Julian Hyde
> > > > * P. Taylor Goetz
> > > > * Ted Dunning
> > > > * Edward J. Yoon
> > > > * Alexander Bezzubov
> > > > * John D. Ament
> > > > * Owen O'Malley
> > > >
> > > > 17 non-binding:
> > > > * Luke Han
> > > > * Shaofeng Shi
> > > > * Jason Zhong
> > > > * Qianhao Zhou
> > > > * Dong Li
> > > > * Droopy Hu
> > > > * Xiaoyong Bai (lostitle)
> > > > * Qi Liu (Goroutine)
> > > > * Yerui Sun
> > > > * Xu Jiang
> > > > * Debashis Saha
> > > > * Yang Li
> > > > * Chad Chun
> > > > * Atri Sharma
> > > > * Hao Chen
> > > > * Eddy Cai
> > > > * Naresh Agarwal
> > > >
> > > > Luke
> > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > >
> >
>

Re: [VOTE] Accept Eagle into Apache Incubation

2015-10-25 Thread Li Yang 
+1 (non-binding)

On Mon, Oct 26, 2015 at 10:50 AM, hongbin ma  wrote:

> +1 (non binding)
>
> On Mon, Oct 26, 2015 at 12:20 AM, Ralph Goers 
> wrote:
>
> > +1 (binding)
> >
> > Ralph
> >
> > > On Oct 23, 2015, at 7:11 AM, Manoharan, Arun 
> > wrote:
> > >
> > > Hello Everyone,
> > >
> > > Thanks for all the feedback on the Eagle Proposal.
> > >
> > > I would like to call for a [VOTE] on Eagle joining the ASF as an
> > incubation project.
> > >
> > > The vote is open for 72 hours:
> > >
> > > [ ] +1 accept Eagle in the Incubator
> > > [ ] ±0
> > > [ ] -1 (please give reason)
> > >
> > > Eagle is a Monitoring solution for Hadoop to instantly identify access
> > to sensitive data, recognize attacks, malicious activities and take
> actions
> > in real time. Eagle supports a wide variety of policies on HDFS data and
> > Hive. Eagle also provides machine learning models for detecting anomalous
> > user behavior in Hadoop.
> > >
> > > The proposal is available on the wiki here:
> > > https://wiki.apache.org/incubator/EagleProposal
> > >
> > > The text of the proposal is also available at the end of this email.
> > >
> > > Thanks for your time and help.
> > >
> > > Thanks,
> > > Arun
> > >
> > > 
> > >
> > > Eagle
> > >
> > > Abstract
> > > Eagle is an Open Source Monitoring solution for Hadoop to instantly
> > identify access to sensitive data, recognize attacks, malicious
> activities
> > in hadoop and take actions.
> > >
> > > Proposal
> > > Eagle audits access to HDFS files, Hive and HBase tables in real time,
> > enforces policies defined on sensitive data access and alerts or blocks
> > user’s access to that sensitive data in real time. Eagle also creates
> user
> > profiles based on the typical access behaviour for HDFS and Hive and
> sends
> > alerts when anomalous behaviour is detected. Eagle can also import
> > sensitive data information classified by external classification engines
> to
> > help define its policies.
> > >
> > > Overview of Eagle
> > > Eagle has 3 main parts.
> > > 1.Data collection and storage - Eagle collects data from various hadoop
> > logs in real time using Kafka/Yarn API and uses HDFS and HBase for
> storage.
> > > 2.Data processing and policy engine - Eagle allows users to create
> > policies based on various metadata properties on HDFS, Hive and HBase
> data.
> > > 3.Eagle services - Eagle services include policy manager, query service
> > and the visualization component. Eagle provides intuitive user interface
> to
> > administer Eagle and an alert dashboard to respond to real time alerts.
> > >
> > > Data Collection and Storage:
> > > Eagle provides programming API for extending Eagle to integrate any
> data
> > source into Eagle policy evaluation framework. For example, Eagle hdfs
> > audit monitoring collects data from Kafka which is populated from
> namenode
> > log4j appender or from logstash agent. Eagle hive monitoring collects
> hive
> > query logs from running job through YARN API, which is designed to be
> > scalable and fault-tolerant. Eagle uses HBase as storage for storing
> > metadata and metrics data, and also supports relational database through
> > configuration change.
> > >
> > > Data Processing and Policy Engine:
> > > Processing Engine: Eagle provides stream processing API which is an
> > abstraction of Apache Storm. It can also be extended to other streaming
> > engines. This abstraction allows developers to assemble data
> > transformation, filtering, external data join etc. without physically
> bound
> > to a specific streaming platform. Eagle streaming API allows developers
> to
> > easily integrate business logic with Eagle policy engine and internally
> > Eagle framework compiles business logic execution DAG into program
> > primitives of underlying stream infrastructure e.g. Apache Storm. For
> > example, Eagle HDFS monitoring transforms audit log from Namenode to
> object
> > and joins sensitivity metadata, security zone metadata which are
> generated
> > from external programs or configured by user. Eagle hive monitoring
> filters
> > running jobs to get hive query string and parses query string into object
> > and then joins sensitivity metadata.
> > > Alerting Framework: Eagle Alert Framework includes stream metadata API,
> > scalable policy engine framework, extensible policy engine framework.
> > Stream metadata API allows developers to declare event schema including
> > what attributes constitute an event, what is the type for each attribute,
> > and how to dynamically resolve attribute value in runtime when user
> > configures policy. Scalable policy engine framework allows policies to be
> > executed on different physical nodes in parallel. It is also used to
> define
> > your own policy partitioner class. Policy engine framework together with
> > streaming partitioning capability provided by all streaming platforms
> will
> > make sure policies and events can be

Re: [VOTE] Accept Eagle into Apache Incubation

2015-10-25 Thread Don Bosco Durai 
+1 non binding 
Bosco 



_
From: Li Yang 
Sent: Sunday, October 25, 2015 8:13 PM
Subject: Re: [VOTE] Accept Eagle into Apache Incubation
To:  


+1 (non-binding)

On Mon, Oct 26, 2015 at 10:50 AM, hongbin ma  wrote:

> +1 (non binding)
>
> On Mon, Oct 26, 2015 at 12:20 AM, Ralph Goers 
> wrote:
>
> > +1 (binding)
> >
> > Ralph
> >
> > > On Oct 23, 2015, at 7:11 AM, Manoharan, Arun 
> > wrote:
> > >
> > > Hello Everyone,
> > >
> > > Thanks for all the feedback on the Eagle Proposal.
> > >
> > > I would like to call for a [VOTE] on Eagle joining the ASF as an
> > incubation project.
> > >
> > > The vote is open for 72 hours:
> > >
> > > [ ] +1 accept Eagle in the Incubator
> > > [ ] ±0
> > > [ ] -1 (please give reason)
> > >
> > > Eagle is a Monitoring solution for Hadoop to instantly identify access
> > to sensitive data, recognize attacks, malicious activities and take
> actions
> > in real time. Eagle supports a wide variety of policies on HDFS data and
> > Hive. Eagle also provides machine learning models for detecting anomalous
> > user behavior in Hadoop.
> > >
> > > The proposal is available on the wiki here:
> > > https://wiki.apache.org/incubator/EagleProposal
> > >
> > > The text of the proposal is also available at the end of this email.
> > >
> > > Thanks for your time and help.
> > >
> > > Thanks,
> > > Arun
> > >
> > > 
> > >
> > > Eagle
> > >
> > > Abstract
> > > Eagle is an Open Source Monitoring solution for Hadoop to instantly
> > identify access to sensitive data, recognize attacks, malicious
> activities
> > in hadoop and take actions.
> > >
> > > Proposal
> > > Eagle audits access to HDFS files, Hive and HBase tables in real time,
> > enforces policies defined on sensitive data access and alerts or blocks
> > user’s access to that sensitive data in real time. Eagle also creates
> user
> > profiles based on the typical access behaviour for HDFS and Hive and
> sends
> > alerts when anomalous behaviour is detected. Eagle can also import
> > sensitive data information classified by external classification engines
> to
> > help define its policies.
> > >
> > > Overview of Eagle
> > > Eagle has 3 main parts.
> > > 1.Data collection and storage - Eagle collects data from various hadoop
> > logs in real time using Kafka/Yarn API and uses HDFS and HBase for
> storage.
> > > 2.Data processing and policy engine - Eagle allows users to create
> > policies based on various metadata properties on HDFS, Hive and HBase
> data.
> > > 3.Eagle services - Eagle services include policy manager, query service
> > and the visualization component. Eagle provides intuitive user interface
> to
> > administer Eagle and an alert dashboard to respond to real time alerts.
> > >
> > > Data Collection and Storage:
> > > Eagle provides programming API for extending Eagle to integrate any
> data
> > source into Eagle policy evaluation framework. For example, Eagle hdfs
> > audit monitoring collects data from Kafka which is populated from
> namenode
> > log4j appender or from logstash agent. Eagle hive monitoring collects
> hive
> > query logs from running job through YARN API, which is designed to be
> > scalable and fault-tolerant. Eagle uses HBase as storage for storing
> > metadata and metrics data, and also supports relational database through
> > configuration change.
> > >
> > > Data Processing and Policy Engine:
> > > Processing Engine: Eagle provides stream processing API which is an
> > abstraction of Apache Storm. It can also be extended to other streaming
> > engines. This abstraction allows developers to assemble data
> > transformation, filtering, external data join etc. without physically
> bound
> > to a specific streaming platform. Eagle streaming API allows developers
> to
> > easily integrate business logic with Eagle policy engine and internally
> > Eagle framework compiles business logic execution DAG into program
> > primitives of underlying stream infrastructure e.g. Apache Storm. For
> > example, Eagle HDFS monitoring transforms audit log from Namenode to
> object
> > and joins sensitivity metadata, security zone metadata which are
> generated
> > from external programs or configured by user. Eagle hive monitoring
> filters
> > running jobs to get hive query string and parses query string into object
> > and then joins sensitivity metadata.
> > > Alerting Framework: Eagle Alert Framework includes stream metadata API,
> > scalable policy engine framework, extensible policy engine framework.
> > Stream metadata API allows developers to declare event schema including
> > what attributes constitute an event, what is the type for each attribute,
> > and how to dynamically resolve attribute value in runtime when user
> > configures policy. Scalable policy engine framework allows policies to be
> > executed on different physical nodes in parallel. It is

Request to be added to Incubator PMC

2015-10-25 Thread Patrick Wendell 
Hi All,

I would like to be added to the Incubator PMC to help mentor a new project.
I am an Apache Member. I am not sure the exact process to be added, so I am
emailing this list as a first step!

Cheers,
- Patrick

Re: [Result][VOTE] Graduate Apache Kylin from the Apache Incubator

2015-10-25 Thread John D. Ament 
Ted,

After catching up on email, I see the SGA was now processed.

I am concerned though after looking at their latest release vote that we're
still missing a few things related to "Verify distribution rights."  It's
not enough for me to say that they're far off, but after seeing the issues
related to both SGA and license/header declarations I can't say that I can
give the podling a warm +1 on their graduation.  Note that per the
podling's status page they completed these steps on 2015-06-10.

John

On Sun, Oct 25, 2015 at 7:36 PM Ted Dunning  wrote:

> John,
>
> Was this issue not rectified to your satisfaction?
>
>
>
> On Sun, Oct 25, 2015 at 10:15 AM, John D. Ament 
> wrote:
>
> > Hi Luke,
> >
> > Actually I voted -1 due to your open SGA issues.
> > On Oct 22, 2015 11:24 PM, "Luke Han"  wrote:
> >
> > > The vote for Apache Kylin to become a top-level project has passed
> > > with 27 +1 votes and no 0 or -1 votes.
> > >
> > > Thank you everyone for taking the time to review and cast your vote.
> > >
> > > We will now prepare a resolution for the next Board meeting.
> > >
> > > 10 binding:
> > > * Henry Saputra
> > > * Andrew Purtell
> > > * Bertrand Delacretaz
> > > * Julian Hyde
> > > * P. Taylor Goetz
> > > * Ted Dunning
> > > * Edward J. Yoon
> > > * Alexander Bezzubov
> > > * John D. Ament
> > > * Owen O'Malley
> > >
> > > 17 non-binding:
> > > * Luke Han
> > > * Shaofeng Shi
> > > * Jason Zhong
> > > * Qianhao Zhou
> > > * Dong Li
> > > * Droopy Hu
> > > * Xiaoyong Bai (lostitle)
> > > * Qi Liu (Goroutine)
> > > * Yerui Sun
> > > * Xu Jiang
> > > * Debashis Saha
> > > * Yang Li
> > > * Chad Chun
> > > * Atri Sharma
> > > * Hao Chen
> > > * Eddy Cai
> > > * Naresh Agarwal
> > >
> > > Luke
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
>

Re: [Result][VOTE] Graduate Apache Kylin from the Apache Incubator

2015-10-25 Thread Ted Dunning 
John,

Was this issue not rectified to your satisfaction?



On Sun, Oct 25, 2015 at 10:15 AM, John D. Ament 
wrote:

> Hi Luke,
>
> Actually I voted -1 due to your open SGA issues.
> On Oct 22, 2015 11:24 PM, "Luke Han"  wrote:
>
> > The vote for Apache Kylin to become a top-level project has passed
> > with 27 +1 votes and no 0 or -1 votes.
> >
> > Thank you everyone for taking the time to review and cast your vote.
> >
> > We will now prepare a resolution for the next Board meeting.
> >
> > 10 binding:
> > * Henry Saputra
> > * Andrew Purtell
> > * Bertrand Delacretaz
> > * Julian Hyde
> > * P. Taylor Goetz
> > * Ted Dunning
> > * Edward J. Yoon
> > * Alexander Bezzubov
> > * John D. Ament
> > * Owen O'Malley
> >
> > 17 non-binding:
> > * Luke Han
> > * Shaofeng Shi
> > * Jason Zhong
> > * Qianhao Zhou
> > * Dong Li
> > * Droopy Hu
> > * Xiaoyong Bai (lostitle)
> > * Qi Liu (Goroutine)
> > * Yerui Sun
> > * Xu Jiang
> > * Debashis Saha
> > * Yang Li
> > * Chad Chun
> > * Atri Sharma
> > * Hao Chen
> > * Eddy Cai
> > * Naresh Agarwal
> >
> > Luke
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>

Re: [VOTE] Accept Eagle into Apache Incubation

2015-10-25 Thread hongbin ma 
+1 (non binding)

On Mon, Oct 26, 2015 at 12:20 AM, Ralph Goers 
wrote:

> +1 (binding)
>
> Ralph
>
> > On Oct 23, 2015, at 7:11 AM, Manoharan, Arun 
> wrote:
> >
> > Hello Everyone,
> >
> > Thanks for all the feedback on the Eagle Proposal.
> >
> > I would like to call for a [VOTE] on Eagle joining the ASF as an
> incubation project.
> >
> > The vote is open for 72 hours:
> >
> > [ ] +1 accept Eagle in the Incubator
> > [ ] ±0
> > [ ] -1 (please give reason)
> >
> > Eagle is a Monitoring solution for Hadoop to instantly identify access
> to sensitive data, recognize attacks, malicious activities and take actions
> in real time. Eagle supports a wide variety of policies on HDFS data and
> Hive. Eagle also provides machine learning models for detecting anomalous
> user behavior in Hadoop.
> >
> > The proposal is available on the wiki here:
> > https://wiki.apache.org/incubator/EagleProposal
> >
> > The text of the proposal is also available at the end of this email.
> >
> > Thanks for your time and help.
> >
> > Thanks,
> > Arun
> >
> > 
> >
> > Eagle
> >
> > Abstract
> > Eagle is an Open Source Monitoring solution for Hadoop to instantly
> identify access to sensitive data, recognize attacks, malicious activities
> in hadoop and take actions.
> >
> > Proposal
> > Eagle audits access to HDFS files, Hive and HBase tables in real time,
> enforces policies defined on sensitive data access and alerts or blocks
> user’s access to that sensitive data in real time. Eagle also creates user
> profiles based on the typical access behaviour for HDFS and Hive and sends
> alerts when anomalous behaviour is detected. Eagle can also import
> sensitive data information classified by external classification engines to
> help define its policies.
> >
> > Overview of Eagle
> > Eagle has 3 main parts.
> > 1.Data collection and storage - Eagle collects data from various hadoop
> logs in real time using Kafka/Yarn API and uses HDFS and HBase for storage.
> > 2.Data processing and policy engine - Eagle allows users to create
> policies based on various metadata properties on HDFS, Hive and HBase data.
> > 3.Eagle services - Eagle services include policy manager, query service
> and the visualization component. Eagle provides intuitive user interface to
> administer Eagle and an alert dashboard to respond to real time alerts.
> >
> > Data Collection and Storage:
> > Eagle provides programming API for extending Eagle to integrate any data
> source into Eagle policy evaluation framework. For example, Eagle hdfs
> audit monitoring collects data from Kafka which is populated from namenode
> log4j appender or from logstash agent. Eagle hive monitoring collects hive
> query logs from running job through YARN API, which is designed to be
> scalable and fault-tolerant. Eagle uses HBase as storage for storing
> metadata and metrics data, and also supports relational database through
> configuration change.
> >
> > Data Processing and Policy Engine:
> > Processing Engine: Eagle provides stream processing API which is an
> abstraction of Apache Storm. It can also be extended to other streaming
> engines. This abstraction allows developers to assemble data
> transformation, filtering, external data join etc. without physically bound
> to a specific streaming platform. Eagle streaming API allows developers to
> easily integrate business logic with Eagle policy engine and internally
> Eagle framework compiles business logic execution DAG into program
> primitives of underlying stream infrastructure e.g. Apache Storm. For
> example, Eagle HDFS monitoring transforms audit log from Namenode to object
> and joins sensitivity metadata, security zone metadata which are generated
> from external programs or configured by user. Eagle hive monitoring filters
> running jobs to get hive query string and parses query string into object
> and then joins sensitivity metadata.
> > Alerting Framework: Eagle Alert Framework includes stream metadata API,
> scalable policy engine framework, extensible policy engine framework.
> Stream metadata API allows developers to declare event schema including
> what attributes constitute an event, what is the type for each attribute,
> and how to dynamically resolve attribute value in runtime when user
> configures policy. Scalable policy engine framework allows policies to be
> executed on different physical nodes in parallel. It is also used to define
> your own policy partitioner class. Policy engine framework together with
> streaming partitioning capability provided by all streaming platforms will
> make sure policies and events can be evaluated in a fully distributed way.
> Extensible policy engine framework allows developer to plugin a new policy
> engine with a few lines of codes. WSO2 Siddhi CEP engine is the policy
> engine which Eagle supports as first-class citizen.
> > Machine Learning module: Eagle provides capabilities to define user
> activity patterns or

Re: [Result][VOTE] Graduate Apache Kylin from the Apache Incubator

2015-10-25 Thread John D. Ament 
Hi Luke,

Actually I voted -1 due to your open SGA issues.
On Oct 22, 2015 11:24 PM, "Luke Han"  wrote:

> The vote for Apache Kylin to become a top-level project has passed
> with 27 +1 votes and no 0 or -1 votes.
>
> Thank you everyone for taking the time to review and cast your vote.
>
> We will now prepare a resolution for the next Board meeting.
>
> 10 binding:
> * Henry Saputra
> * Andrew Purtell
> * Bertrand Delacretaz
> * Julian Hyde
> * P. Taylor Goetz
> * Ted Dunning
> * Edward J. Yoon
> * Alexander Bezzubov
> * John D. Ament
> * Owen O'Malley
>
> 17 non-binding:
> * Luke Han
> * Shaofeng Shi
> * Jason Zhong
> * Qianhao Zhou
> * Dong Li
> * Droopy Hu
> * Xiaoyong Bai (lostitle)
> * Qi Liu (Goroutine)
> * Yerui Sun
> * Xu Jiang
> * Debashis Saha
> * Yang Li
> * Chad Chun
> * Atri Sharma
> * Hao Chen
> * Eddy Cai
> * Naresh Agarwal
>
> Luke
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

[Result][VOTE] Graduate Apache Kylin from the Apache Incubator

2015-10-25 Thread Andrew Purtell 
Hi Luke,

By my count there was more than one binding -1 raised during the vote and I
don't think all were changed during subsequent discussion.  At a minimum
let's post a corrected RESULT, but I believe by ensuring the raised issues
are satisfactorily resolved and then starting another vote you can achieve
an unanimously positive outcome, if that is desirable (and of course it is
(smile)).


> On Oct 22, 2015, at 8:24 PM, Luke Han >
wrote:
>
> The vote for Apache Kylin to become a top-level project has passed
> with 27 +1 votes and no 0 or -1 votes.
>
> Thank you everyone for taking the time to review and cast your vote.
>
> We will now prepare a resolution for the next Board meeting.
>
> 10 binding:
> * Henry Saputra
> * Andrew Purtell
> * Bertrand Delacretaz
> * Julian Hyde
> * P. Taylor Goetz
> * Ted Dunning
> * Edward J. Yoon
> * Alexander Bezzubov
> * John D. Ament
> * Owen O'Malley
>
> 17 non-binding:
> * Luke Han
> * Shaofeng Shi
> * Jason Zhong
> * Qianhao Zhou
> * Dong Li
> * Droopy Hu
> * Xiaoyong Bai (lostitle)
> * Qi Liu (Goroutine)
> * Yerui Sun
> * Xu Jiang
> * Debashis Saha
> * Yang Li
> * Chad Chun
> * Atri Sharma
> * Hao Chen
> * Eddy Cai
> * Naresh Agarwal
>
> Luke
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org

> For additional commands, e-mail: general-h...@incubator.apache.org



-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

Re: [VOTE] Accept Eagle into Apache Incubation

2015-10-25 Thread Ralph Goers 
+1 (binding)

Ralph

> On Oct 23, 2015, at 7:11 AM, Manoharan, Arun  wrote:
> 
> Hello Everyone,
> 
> Thanks for all the feedback on the Eagle Proposal.
> 
> I would like to call for a [VOTE] on Eagle joining the ASF as an incubation 
> project.
> 
> The vote is open for 72 hours:
> 
> [ ] +1 accept Eagle in the Incubator
> [ ] ±0
> [ ] -1 (please give reason)
> 
> Eagle is a Monitoring solution for Hadoop to instantly identify access to 
> sensitive data, recognize attacks, malicious activities and take actions in 
> real time. Eagle supports a wide variety of policies on HDFS data and Hive. 
> Eagle also provides machine learning models for detecting anomalous user 
> behavior in Hadoop.
> 
> The proposal is available on the wiki here:
> https://wiki.apache.org/incubator/EagleProposal
> 
> The text of the proposal is also available at the end of this email.
> 
> Thanks for your time and help.
> 
> Thanks,
> Arun
> 
> 
> 
> Eagle
> 
> Abstract
> Eagle is an Open Source Monitoring solution for Hadoop to instantly identify 
> access to sensitive data, recognize attacks, malicious activities in hadoop 
> and take actions.
> 
> Proposal
> Eagle audits access to HDFS files, Hive and HBase tables in real time, 
> enforces policies defined on sensitive data access and alerts or blocks 
> user’s access to that sensitive data in real time. Eagle also creates user 
> profiles based on the typical access behaviour for HDFS and Hive and sends 
> alerts when anomalous behaviour is detected. Eagle can also import sensitive 
> data information classified by external classification engines to help define 
> its policies.
> 
> Overview of Eagle
> Eagle has 3 main parts.
> 1.Data collection and storage - Eagle collects data from various hadoop logs 
> in real time using Kafka/Yarn API and uses HDFS and HBase for storage.
> 2.Data processing and policy engine - Eagle allows users to create policies 
> based on various metadata properties on HDFS, Hive and HBase data.
> 3.Eagle services - Eagle services include policy manager, query service and 
> the visualization component. Eagle provides intuitive user interface to 
> administer Eagle and an alert dashboard to respond to real time alerts.
> 
> Data Collection and Storage:
> Eagle provides programming API for extending Eagle to integrate any data 
> source into Eagle policy evaluation framework. For example, Eagle hdfs audit 
> monitoring collects data from Kafka which is populated from namenode log4j 
> appender or from logstash agent. Eagle hive monitoring collects hive query 
> logs from running job through YARN API, which is designed to be scalable and 
> fault-tolerant. Eagle uses HBase as storage for storing metadata and metrics 
> data, and also supports relational database through configuration change.
> 
> Data Processing and Policy Engine:
> Processing Engine: Eagle provides stream processing API which is an 
> abstraction of Apache Storm. It can also be extended to other streaming 
> engines. This abstraction allows developers to assemble data transformation, 
> filtering, external data join etc. without physically bound to a specific 
> streaming platform. Eagle streaming API allows developers to easily integrate 
> business logic with Eagle policy engine and internally Eagle framework 
> compiles business logic execution DAG into program primitives of underlying 
> stream infrastructure e.g. Apache Storm. For example, Eagle HDFS monitoring 
> transforms audit log from Namenode to object and joins sensitivity metadata, 
> security zone metadata which are generated from external programs or 
> configured by user. Eagle hive monitoring filters running jobs to get hive 
> query string and parses query string into object and then joins sensitivity 
> metadata.
> Alerting Framework: Eagle Alert Framework includes stream metadata API, 
> scalable policy engine framework, extensible policy engine framework. Stream 
> metadata API allows developers to declare event schema including what 
> attributes constitute an event, what is the type for each attribute, and how 
> to dynamically resolve attribute value in runtime when user configures 
> policy. Scalable policy engine framework allows policies to be executed on 
> different physical nodes in parallel. It is also used to define your own 
> policy partitioner class. Policy engine framework together with streaming 
> partitioning capability provided by all streaming platforms will make sure 
> policies and events can be evaluated in a fully distributed way. Extensible 
> policy engine framework allows developer to plugin a new policy engine with a 
> few lines of codes. WSO2 Siddhi CEP engine is the policy engine which Eagle 
> supports as first-class citizen.
> Machine Learning module: Eagle provides capabilities to define user activity 
> patterns or user profiles for Hadoop users based on the user behaviour in the 
> platform. These user profiles are modeled using Machine Learning algorithms

Re: [Result][VOTE] Graduate Apache Kylin from the Apache Incubator

2015-10-25 Thread John D. Ament 
I don't think resubmission of a vote is required.  According to
http://incubator.apache.org/guides/graduation.html#ipmc-top-level-recommendation
it's
a consensus vote.  I don't believe it has to be unanimous, I would just
prefer to not be misrepresented.

John

On Sun, Oct 25, 2015 at 1:54 PM Andrew Purtell  wrote:

> Hi Luke,
>
> By my count there was more than one binding -1 raised during the vote and I
> don't think all were changed during subsequent discussion.  At a minimum
> let's post a corrected RESULT, but I believe by ensuring the raised issues
> are satisfactorily resolved and then starting another vote you can achieve
> an unanimously positive outcome, if that is desirable (and of course it is
> (smile)).
>
>
> > On Oct 22, 2015, at 8:24 PM, Luke Han  >
> wrote:
> >
> > The vote for Apache Kylin to become a top-level project has passed
> > with 27 +1 votes and no 0 or -1 votes.
> >
> > Thank you everyone for taking the time to review and cast your vote.
> >
> > We will now prepare a resolution for the next Board meeting.
> >
> > 10 binding:
> > * Henry Saputra
> > * Andrew Purtell
> > * Bertrand Delacretaz
> > * Julian Hyde
> > * P. Taylor Goetz
> > * Ted Dunning
> > * Edward J. Yoon
> > * Alexander Bezzubov
> > * John D. Ament
> > * Owen O'Malley
> >
> > 17 non-binding:
> > * Luke Han
> > * Shaofeng Shi
> > * Jason Zhong
> > * Qianhao Zhou
> > * Dong Li
> > * Droopy Hu
> > * Xiaoyong Bai (lostitle)
> > * Qi Liu (Goroutine)
> > * Yerui Sun
> > * Xu Jiang
> > * Debashis Saha
> > * Yang Li
> > * Chad Chun
> > * Atri Sharma
> > * Hao Chen
> > * Eddy Cai
> > * Naresh Agarwal
> >
> > Luke
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> 
> > For additional commands, e-mail: general-h...@incubator.apache.org
> 
>
>
> --
> Best regards,
>
>- Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>

Re: [Result][VOTE] Graduate Apache Kylin from the Apache Incubator

2015-10-25 Thread Henry Saputra 
Seemed like John is the only -1 due to missing update on SGA information.

John said he +1 given that the XML status file is updated to reflect
it and it had been updated so we just assumed his VOTE become +1
automatically per his statement.

John, if you would like to still to record your VOTE as -1 we could
update the tally with comment that we have addressed the SGA issue.

- Henry

On Sun, Oct 25, 2015 at 11:52 AM, John D. Ament  wrote:
> I don't think resubmission of a vote is required.  According to
> http://incubator.apache.org/guides/graduation.html#ipmc-top-level-recommendation
> it's
> a consensus vote.  I don't believe it has to be unanimous, I would just
> prefer to not be misrepresented.
>
> John
>
> On Sun, Oct 25, 2015 at 1:54 PM Andrew Purtell  wrote:
>
>> Hi Luke,
>>
>> By my count there was more than one binding -1 raised during the vote and I
>> don't think all were changed during subsequent discussion.  At a minimum
>> let's post a corrected RESULT, but I believe by ensuring the raised issues
>> are satisfactorily resolved and then starting another vote you can achieve
>> an unanimously positive outcome, if that is desirable (and of course it is
>> (smile)).
>>
>>
>> > On Oct 22, 2015, at 8:24 PM, Luke Han > >
>> wrote:
>> >
>> > The vote for Apache Kylin to become a top-level project has passed
>> > with 27 +1 votes and no 0 or -1 votes.
>> >
>> > Thank you everyone for taking the time to review and cast your vote.
>> >
>> > We will now prepare a resolution for the next Board meeting.
>> >
>> > 10 binding:
>> > * Henry Saputra
>> > * Andrew Purtell
>> > * Bertrand Delacretaz
>> > * Julian Hyde
>> > * P. Taylor Goetz
>> > * Ted Dunning
>> > * Edward J. Yoon
>> > * Alexander Bezzubov
>> > * John D. Ament
>> > * Owen O'Malley
>> >
>> > 17 non-binding:
>> > * Luke Han
>> > * Shaofeng Shi
>> > * Jason Zhong
>> > * Qianhao Zhou
>> > * Dong Li
>> > * Droopy Hu
>> > * Xiaoyong Bai (lostitle)
>> > * Qi Liu (Goroutine)
>> > * Yerui Sun
>> > * Xu Jiang
>> > * Debashis Saha
>> > * Yang Li
>> > * Chad Chun
>> > * Atri Sharma
>> > * Hao Chen
>> > * Eddy Cai
>> > * Naresh Agarwal
>> >
>> > Luke
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> 
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>>
>>
>> --
>> Best regards,
>>
>>- Andy
>>
>> Problems worthy of attack prove their worth by hitting back. - Piet Hein
>> (via Tom White)
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org