Re: [VOTE] Accept Eagle into Apache Incubation

[Samant, Medha]

+1
-Medha

On 10/23/15, 1:14 PM, "Balaji Ganesan"  wrote:

>+1
>
>On Fri, Oct 23, 2015 at 12:26 PM, Chris Nauroth 
>wrote:
>
>> +1 (binding)
>>
>> --Chris Nauroth
>>
>>
>>
>>
>> On 10/23/15, 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
>> 

Re: [VOTE] Release Apache Kylin 1.1-incubating (rc1)

[Samant, Medha]

+1

> On Oct 19, 2015, at 7:40 AM, Julian Hyde  wrote:
> 
> Forwarding my vote from the dev list:
> 
> +1 (binding)
> 
>> On Oct 19, 2015, at 1:18 AM, 周千昊  wrote:
>> 
>> +1
>> mvn test passed
>> 
>> hongbin ma 于2015年10月19日周一 上午11:28写道：
>> 
>>> +1
>>> 
>>> unit test passed on my CI
>>> 
 On Mon, Oct 19, 2015 at 10:46 AM, Li Yang  wrote:
 
 +1
 
 Checksum is correct.
 
 Unit test passed on java version "1.7.0_71", OpenJDK Runtime Environment
 (rhel-2.5.3.1.el6-x86_64 u71-b14)
 
 
> On Thu, Oct 15, 2015 at 10:00 AM, Luke Han  wrote:
> 
> +1
> 
> MD5 & SHA1 checksum verified
> License files are all there
> 
> Unit Test passed
> 
> 
> 
> Best Regards!
> -
> 
> Luke Han
> 
> On Thu, Oct 15, 2015 at 9:42 AM, ShaoFeng Shi 
> wrote:
> 
>> Hi all,
>> 
>> The Apache Kylin community has voted on and approved a proposal to
> release
>> Apache Kylin 1.1-incubating.
>> 
>> Proposal:http://s.apache.org/Jzu
>> 
>> Vote result:
>> 7 binding +1 votes
>> 6 non-binding +1 votes
>> No -1 voteshttp://s.apache.org/kylin-1.1-result_rc1
>> 
>> 
>> The commit to be voted
>> upon:
>>> https://github.com/apache/incubator-kylin/commit/1955a2f9aea7b7f608f0496c00807715ea4246a5
>> 
>> Its hash is 1955a2f9aea7b7f608f0496c00807715ea4246a5.
>> 
>> The artifacts to be voted on are located
>> here:
>>> https://dist.apache.org/repos/dist/dev/incubator/kylin/apache-kylin-1.1-incubating-rc1/
>> 
>> The hashes of the artifacts are as follows:
>> apache-kylin-1.1-incubating-src.tar.gz.md5
> 18dfbb012e1eb807b1a5c1b134a537aa
>> apache-kylin-1.1-incubating-src.tar.gz.sha1
>> 041ee010c67a0b5611d9dd06f7fd6f37388c5374
>> 
>> A staged Maven repository is available for review
>> at:
>>> https://repository.apache.org/content/repositories/orgapachekylin-1012/
>> 
>> Release artifacts are signed with the following
>> key:https://people.apache.org/keys/committer/shaofengshi.asc
>> 
>> Pursuant to the Releases section of the Incubation Policy and with
>> the endorsement of our mentors we would now like to request
>> the permission of the Incubator PMC to publish the release. The vote
>> is open for 72 hours, or until the necessary number of votes (3 +1)
>> is reached.
>> 
>> [ ] +1 Release this package
>> [ ]  0 I don't feel strongly about it, but I'm okay with the release
>> [ ] -1 Do not release this package because...
>> 
>> 
>> Shaofeng Shi, on behalf of Apache Kylin ppmcshaofeng...@apache.org
>>> 
>>> 
>>> 
>>> --
>>> Regards,
>>> 
>>> *Bin Mahone | 马洪宾*
>>> Apache Kylin: http://kylin.io
>>> Github: https://github.com/binmahone
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: [DISCUSS] Graduate Kylin from the Apache Incubator

[Samant, Medha]

+1

On 10/9/15, 10:13 AM, "Adunuthula, Seshu"  wrote:

>+1 
>
>On 10/7/15, 8:32 AM, "John D. Ament"  wrote:
>
>>I would be happy to see kylin graduate.
>>On Oct 7, 2015 11:28, "Luke Han"  wrote:
>>
>>> The Kylin community and project made significant advances during the
>>> incubating (from Nov 2014) and
>>> believes it is ready to graduate as a top-level project.
>>>
>>> The Apache Kylin is very active. The PPMC doubled in size (added 6
>>> committers and 2 mentors) and
>>>  increased diversity in the past year. Released 3 version in the past 6
>>> months. There were presentations about Kylin
>>> at most of the big conferences of the world (including Strata+Hadoop
>>>World
>>> London, Hadoop Summit San Jose,
>>> ApacheCon EU, Big Data Technology China, Database Technology Conference
>>> China) and some meetups (Bay Area,
>>> Beijing and one is coming in this weekend in Shanghai), and many talks
>>> around the world.
>>> The dev mailing list is growing very month, about 500+ topics per month
>>> now.
>>> The community created 1000+ JIRA tickets, many patches from
>>> contributors/committers have been merged into code base.
>>>
>>> A vote passed unanimously on the dev@ list (27 +1 votes). Please find
>>> below
>>> references to the graduation preparation artifacts:
>>> * discussion on dev list [1]
>>> * vote thread [2]
>>> * podling name search (still in progress) [3]
>>> * incubation status [4]
>>> * proposed resolution below
>>>
>>> We believe Apache Kylin is ready to become a top-level project and if
>>>the
>>> IPMC agree we will move to a formal vote.
>>> There are a few more items to be updated on the project status page and
>>> others during the next couple of days.
>>>
>>>
>>> Many thanks to the mentors and the IPMC for the support,
>>> Luke Han (on behalf of the Apache Kylin PPMC)
>>>
>>> [1] http://s.apache.org/KylinDisGraduate
>>> [2] http://s.apache.org/KylinGraduateVote
>>> [3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-86
>>> [4] http://incubator.apache.org/projects/kylin.html
>>>
>>>
>>>
>>> Apache Kylin top-level project resolution:
>>> ===
>>>
>>>WHEREAS, the Board of Directors deems it to be in the best
>>>interests of the Foundation and consistent with the
>>>Foundation's purpose to establish a Project Management
>>>Committee charged with the creation and maintenance of
>>>open-source software, for distribution at no charge to the
>>>public, relative to distributed and scalable OLAP engine
>>>
>>>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>>Committee (PMC), to be known as the "Apache Kylin Project",
>>>be and hereby is established pursuant to Bylaws of the
>>>Foundation; and be it further
>>>
>>>RESOLVED, that the Apache Kylin Project be and hereby is
>>>responsible for the creation and maintenance of open-source
>>>software related to distributed and scalable OLAP engine;
>>>and be it further
>>>
>>>RESOLVED, that the office of "Vice President, Kylin" be and
>>>hereby is created, the person holding such office to serve at
>>>the direction of the Board of Directors as the chair of the
>>>Apache Kylin Project, and to have primary responsibility for
>>>management of the projects within the scope of responsibility
>>>of the Apache Kylin 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 Kylin Project:
>>>
>>> * Dayue Gao 
>>> * Jason Zhong 
>>> * Julian Hyde 
>>> * Luke Han 
>>> * Henry Saputra 
>>> * Hongbin Ma 
>>> * Hua Huang 
>>> * Owen O'Malley 
>>> * P. Taylor Goetz 
>>> * Qianhao Zhou 
>>> * Shaofeng Shi 
>>> * Song Yi 
>>> * Ted Dunning 
>>> * Xu Jiang 
>>> * Yang Li 
>>> * Yerui Sun < sunyerui at apache dot org>
>>>
>>>
>>>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Luke Han
>>>be appointed to the office of Vice President, Kylin, to serve
>>>in accordance with and subject to the direction of the Board of
>>>Directors and the Bylaws of the Foundation until death,
>>>resignation, retirement, removal or disqualification, or until
>>>a successor is appointed; and be it further
>>>
>>>RESOLVED, that the initial Apache Kylin Project be and hereby
>>>is tasked with the creation of a set of bylaws intended to
>>>encourage open development and increased participation in the
>>>Kylin Project; and be it further
>>>
>>>RESOLVED, that the initial Apache Kylin Project be and hereby
>>>is tasked with the migration and rationalization of the Apache
>>>