Re: Graduation resolution

[Edward Zhang]

Thanks Julian. I also wanted to ask how to do the next step :-)
Let me know if anything I need do for next steps.

Thanks
Edward

On Thu, Dec 15, 2016 at 11:07 AM, Julian Hyde  wrote:

> Now the IPMC vote has passed, next step is to get the resolution onto the
> board agenda. The meeting is on Wed 21st, so we are just about in time. I
> am doing that this morning.
>
> Julian
>
>

Re: [VOTE] Graduate Apache Eagle to top level project

[Edward Zhang]

Ok, I have summarized yesterday. Plus today's VOTE @dev list, the result is

15  +1
0+0
0-1

Thanks
Edward

On Mon, Dec 5, 2016 at 9:56 PM, Henry Saputra <henry.sapu...@gmail.com>
wrote:

> Hi Edward,
>
> Could you tally up the VOTE result in dev@ list?
>
> - Henry
>
> On Mon, Dec 5, 2016 at 9:30 PM, Edward Zhang <yonzhang2...@gmail.com>
> wrote:
> > Thanks. I have noticed this error and corrected that in formal vote in
> > general DL.
> >
> > Thanks
> > Edward
> >
> > On Mon, Dec 5, 2016 at 9:25 PM, Amareshwari Sriramdasu <
> > amareshw...@apache.org> wrote:
> >
> >> +1
> >>
> >> Please correct Jijun Tang's link in final vote.
> >>
> >> On Thu, Dec 1, 2016 at 11:16 AM, Edward Zhang <yonzhang2...@gmail.com>
> >> wrote:
> >>
> >> > Hi Eagle community,
> >> >
> >> > After a very positive discussion in Apache Eagle community
> http://apache
> >> .
> >> > markmail.org/thread/s2yegpmxf3g7fa34, I'd like to bring the following
> >> > resolution for a formal vote in Eagle community and after this we need
> >> > another formal vote in IPMC and then we reach a stage close to
> graduation
> >> > :-)
> >> >
> >> > Please vote on the resolution pasted below to graduate Apache Eagle
> from
> >> > the incubator to top level project.
> >> >
> >> >
> >> > [ ] +1 Graduate Apache Eagle from the Incubator.
> >> >
> >> > [ ] +0 Don't care.
> >> >
> >> > [ ] -1 Don't graduate Apache Eagle from the Incubator because...
> >> >
> >> >
> >> > This vote will be open for at least 72 hours.
> >> >
> >> >
> >> > Many thanks to our mentors and everyone else for the support,
> >> >
> >> > Edward Zhang (on behalf of the Apache Eagle PPMC).
> >> >
> >> > Resolution:
> >> >
> >> >   Establish the Apache Eagle Project
> >> >
> >> >   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, related to a distributed monitoring solution for
> >> > identifying security and performance issues in real time on big data
> >> > platforms, including Hadoop and Spark etc.
> >> >
> >> >   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >> >   Committee (PMC), to be known as the "Apache Eagle Project",
> >> >   be and hereby is established pursuant to Bylaws of the
> >> >   Foundation; and be it further
> >> >
> >> >   RESOLVED, that the Apache Eagle Project be and hereby is
> >> >   responsible for the creation and maintenance of software
> >> >   related to a distributed monitoring solution for identifying
> >> security
> >> > and performance issues in real time on big data platforms, including
> >> Hadoop
> >> > and Spark etc.;
> >> >   and be it further
> >> >
> >> >   RESOLVED, that the office of "Vice President, Apache Eagle" 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 Eagle Project, and to have primary responsibility
> >> >   for management of the projects within the scope of
> >> >   responsibility of the Apache Eagle 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 Eagle Project:
> >> >
> >> >
> >> > * Edward Zhang yonzhang2...@apache.org
> >> >
> >> > * Hao Chen h...@apache.org
> >> >
> >> > * Qingwen Zhao qingwz...@apache.org
> >> >
> >> > * jilin Jiang ji...@apache.org
> >> >
> >> > * Ralph Su ralp...@apache.org
> >> >
> >> > * Jinhu Wu jinh...@apache.org
>

Re: [VOTE] Graduate Apache Eagle to top level project

[Edward Zhang]

Thanks. I have noticed this error and corrected that in formal vote in
general DL.

Thanks
Edward

On Mon, Dec 5, 2016 at 9:25 PM, Amareshwari Sriramdasu <
amareshw...@apache.org> wrote:

> +1
>
> Please correct Jijun Tang's link in final vote.
>
> On Thu, Dec 1, 2016 at 11:16 AM, Edward Zhang <yonzhang2...@gmail.com>
> wrote:
>
> > Hi Eagle community,
> >
> > After a very positive discussion in Apache Eagle community http://apache
> .
> > markmail.org/thread/s2yegpmxf3g7fa34, I'd like to bring the following
> > resolution for a formal vote in Eagle community and after this we need
> > another formal vote in IPMC and then we reach a stage close to graduation
> > :-)
> >
> > Please vote on the resolution pasted below to graduate Apache Eagle from
> > the incubator to top level project.
> >
> >
> > [ ] +1 Graduate Apache Eagle from the Incubator.
> >
> > [ ] +0 Don't care.
> >
> > [ ] -1 Don't graduate Apache Eagle from the Incubator because...
> >
> >
> > This vote will be open for at least 72 hours.
> >
> >
> > Many thanks to our mentors and everyone else for the support,
> >
> > Edward Zhang (on behalf of the Apache Eagle PPMC).
> >
> > Resolution:
> >
> >   Establish the Apache Eagle Project
> >
> >   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, related to a distributed monitoring solution for
> > identifying security and performance issues in real time on big data
> > platforms, including Hadoop and Spark etc.
> >
> >   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >   Committee (PMC), to be known as the "Apache Eagle Project",
> >   be and hereby is established pursuant to Bylaws of the
> >   Foundation; and be it further
> >
> >   RESOLVED, that the Apache Eagle Project be and hereby is
> >   responsible for the creation and maintenance of software
> >   related to a distributed monitoring solution for identifying
> security
> > and performance issues in real time on big data platforms, including
> Hadoop
> > and Spark etc.;
> >   and be it further
> >
> >   RESOLVED, that the office of "Vice President, Apache Eagle" 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 Eagle Project, and to have primary responsibility
> >   for management of the projects within the scope of
> >   responsibility of the Apache Eagle 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 Eagle Project:
> >
> >
> > * Edward Zhang yonzhang2...@apache.org
> >
> > * Hao Chen h...@apache.org
> >
> > * Qingwen Zhao qingwz...@apache.org
> >
> > * jilin Jiang ji...@apache.org
> >
> > * Ralph Su ralp...@apache.org
> >
> > * Jinhu Wu jinh...@apache.org
> >
> > * Jijun Tang jjt...@apache.org <jinh...@apache.org>
> >
> > * Daniel Zhou daz...@apache.org
> >
> > * Kumar Senthil senthilec...@apache.org
> >
> > * Dendukuri Hemanth hdenduk...@apache.org
> >
> > * Wu Michael m...@apache.org
> >
> > * Manoharan Arun arunmanoha...@apache.org
> >
> > * Gupta Chaitali cgu...@apache.org
> >
> > * Libin Sun lib...@apache.org
> >
> >
> >
> >   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Edward Zhang
> >   be appointed to the office of Vice President, Apache Eagle, 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 Eagle PMC be and hereby is
> >   tasked with the creation of a set of bylaws intended to
> >   encourage open development and increased participation in the
> >   Apache Eagle Project; and be it further
> >
> >   RESOLVED, that the Apache Eagle Project be and hereby
> >   is tasked with the migration and rationalization of the Apache
> >   Incubator Eagle podling; and be it further
> >
> >   RESOLVED, that all responsibilities pertaining to the Apache
> >   Incubator Eagle podling encumbered upon the Apache Incubator
> >   Project are hereafter discharged.
> >
>

[VOTE] Graduate Apache Eagle to top level project

[Edward Zhang]

Hi Eagle community,

After a very positive discussion in Apache Eagle community http://apache.
markmail.org/thread/s2yegpmxf3g7fa34, I'd like to bring the following
resolution for a formal vote in Eagle community and after this we need
another formal vote in IPMC and then we reach a stage close to graduation
:-)

Please vote on the resolution pasted below to graduate Apache Eagle from
the incubator to top level project.


[ ] +1 Graduate Apache Eagle from the Incubator.

[ ] +0 Don't care.

[ ] -1 Don't graduate Apache Eagle from the Incubator because...


This vote will be open for at least 72 hours.


Many thanks to our mentors and everyone else for the support,

Edward Zhang (on behalf of the Apache Eagle PPMC).

Resolution:

  Establish the Apache Eagle Project

  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, related to a distributed monitoring solution for
identifying security and performance issues in real time on big data
platforms, including Hadoop and Spark etc.

  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
  Committee (PMC), to be known as the "Apache Eagle Project",
  be and hereby is established pursuant to Bylaws of the
  Foundation; and be it further

  RESOLVED, that the Apache Eagle Project be and hereby is
  responsible for the creation and maintenance of software
  related to a distributed monitoring solution for identifying security
and performance issues in real time on big data platforms, including Hadoop
and Spark etc.;
  and be it further

  RESOLVED, that the office of "Vice President, Apache Eagle" 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 Eagle Project, and to have primary responsibility
  for management of the projects within the scope of
  responsibility of the Apache Eagle 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 Eagle Project:


    * Edward Zhang yonzhang2...@apache.org

* Hao Chen h...@apache.org

* Qingwen Zhao qingwz...@apache.org

* jilin Jiang ji...@apache.org

* Ralph Su ralp...@apache.org

* Jinhu Wu jinh...@apache.org

* Jijun Tang jjt...@apache.org <jinh...@apache.org>

* Daniel Zhou daz...@apache.org

* Kumar Senthil senthilec...@apache.org

* Dendukuri Hemanth hdenduk...@apache.org

* Wu Michael m...@apache.org

* Manoharan Arun arunmanoha...@apache.org

* Gupta Chaitali cgu...@apache.org

* Libin Sun lib...@apache.org



  NOW, THEREFORE, BE IT FURTHER RESOLVED, that Edward Zhang
  be appointed to the office of Vice President, Apache Eagle, 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 Eagle PMC be and hereby is
  tasked with the creation of a set of bylaws intended to
  encourage open development and increased participation in the
  Apache Eagle Project; and be it further

  RESOLVED, that the Apache Eagle Project be and hereby
  is tasked with the migration and rationalization of the Apache
  Incubator Eagle podling; and be it further

  RESOLVED, that all responsibilities pertaining to the Apache
  Incubator Eagle podling encumbered upon the Apache Incubator
  Project are hereafter discharged.

Re: [Discuss] Proposed Board Resolution for Eagle

[Edward Zhang]

Based on Henry's suggestion, I modified proposed PMC to use real name.

Resolution:

  Establish the Apache Eagle Project

  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, related to a distributed monitoring solution for
identifying security and performance issues in real time on big data
platforms, including Hadoop and Spark etc.

  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
  Committee (PMC), to be known as the "Apache Eagle Project",
  be and hereby is established pursuant to Bylaws of the
  Foundation; and be it further

  RESOLVED, that the Apache Eagle Project be and hereby is
  responsible for the creation and maintenance of software
  related to a distributed monitoring solution for identifying security
and performance issues in real time on big data platforms, including Hadoop
and Spark etc.;
  and be it further

  RESOLVED, that the office of "Vice President, Apache Eagle" 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 Eagle Project, and to have primary responsibility
  for management of the projects within the scope of
  responsibility of the Apache Eagle 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 Eagle Project:


    * Edward Zhang yonzhang2...@apache.org

* Hao Chen h...@apache.org

* Qingwen Zhao qingwz...@apache.org

* jilin Jiang ji...@apache.org

* Ralph Su ralp...@apache.org

* Jinhu Wu jinh...@apache.org

* Daniel Zhou daz...@apache.org

* Kumar Senthil senthilec...@apache.org

* Dendukuri Hemanth hdenduk...@apache.org

* Wu Michael m...@apache.org

* Manoharan Arun arunmanoha...@apache.org

* Gupta Chaitali cgu...@apache.org

* Libin Sun lib...@apache.org



  NOW, THEREFORE, BE IT FURTHER RESOLVED, that Edward Zhang
  be appointed to the office of Vice President, Apache Eagle, 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 Eagle PMC be and hereby is
  tasked with the creation of a set of bylaws intended to
  encourage open development and increased participation in the
  Apache Eagle Project; and be it further

  RESOLVED, that the Apache Eagle Project be and hereby
  is tasked with the migration and rationalization of the Apache
  Incubator Eagle podling; and be it further

  RESOLVED, that all responsibilities pertaining to the Apache
  Incubator Eagle podling encumbered upon the Apache Incubator
  Project are hereafter discharged.






On Mon, Nov 14, 2016 at 10:40 PM, Edward Zhang <yonzhang2...@apache.org>
wrote:

> Hi,
>
> This email is for reviewing proposed board Resolution for Eagle, please
> read through carefully and provide feedback.
>
> For resolution, here is the template, template https://svn.apache.or
> g/repos/private/committers/board/templates/podling-tlp-resolution.txt.
>
> Destination: Top-level project
>
> Resolution:
>
>   Establish the Apache Eagle Project
>
>   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, related to a distributed monitoring solution for
> identifying security and performance issues in real time on big data
> platforms, including Hadoop and Spark etc.
>
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache Eagle Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
>
>   RESOLVED, that the Apache Eagle Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to a distributed monitoring solution for identifying
> security and performance issues in real time on big data platforms,
> including Hadoop and Spark etc.;
>   and be it further
>
>   RESOLVED, that the office of "Vice 

Re: 答复: [ANNOUNCE] new committer: Jijun Tang

[Edward Zhang]

Welcome Jijun, nice to meet you here.

Thanks
Edward

On Tue, Nov 15, 2016 at 12:14 AM, Tang Jijun(上海_技术部_数据平台_唐觊隽) <
tangji...@yhd.com> wrote:

> Hi Eagle Community ,
>
> Thank you all :).
> My name is JiJun Tang. I'm from China and I live in Shanghai with my wife
> and 6 month old daughter. At the moment, I'm a software engineer working at
> Yihaodian, Inc, focusing on big data platforms.
>
> For Apache Eagle, I've made some contributions to Unit test, JDBC
> implementation for Metadata and Oozie audit application.
>
> It's a great honor for me to be accepted as a member and committer to
> Apache Eagle! I look forward to working together with community in the
> future.
>
> JiJun Tang
> Jr. Engineer , Architecture - Fundation, Tech Dept
> Floor 4, 295 ZUCHONGZHI RD, Zhangjiang, Shanghai (201203)
>
>
>
>
> -邮件原件-
> 发件人: Zhao Qingwen [mailto:qingwen...@gmail.com]
> 发送时间: 2016年11月15日 15:39
> 收件人: dev@eagle.incubator.apache.org
> 主题: [ANNOUNCE] new committer: Jijun Tang
>
> The Project Management Committee (PMC) for Apache Eagle has asked Jijun
> Tang to become a committer and we are pleased to announce that He has
> accepted.
>
> Being a committer enables easier contribution to the project since there
> is no need to go via the patch submission process. This should enable
> better productivity.
>
> Please join me to welcome Jijun.
>
> Jijun, please share with us a little about yourself.
>
> Qingwen
>
> On behalf of the Apache Eagle PPMC
>
> Best Regards,
> Qingwen Zhao | 赵晴雯
>

[Discuss] Proposed Board Resolution for Eagle

[Edward Zhang]

Hi,

This email is for reviewing proposed board Resolution for Eagle, please
read through carefully and provide feedback.

For resolution, here is the template, template https://svn.apache.
org/repos/private/committers/board/templates/podling-tlp-resolution.txt.

Destination: Top-level project

Resolution:

  Establish the Apache Eagle Project

  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, related to a distributed monitoring solution for
identifying security and performance issues in real time on big data
platforms, including Hadoop and Spark etc.

  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
  Committee (PMC), to be known as the "Apache Eagle Project",
  be and hereby is established pursuant to Bylaws of the
  Foundation; and be it further

  RESOLVED, that the Apache Eagle Project be and hereby is
  responsible for the creation and maintenance of software
  related to a distributed monitoring solution for identifying security
and performance issues in real time on big data platforms, including Hadoop
and Spark etc.;
  and be it further

  RESOLVED, that the office of "Vice President, Apache Eagle" 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 Eagle Project, and to have primary responsibility
  for management of the projects within the scope of
  responsibility of the Apache Eagle 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 Eagle Project:


* yonzhang2...@apache.org

* h...@apache.org

* qingwz...@apache.org

* ji...@apache.org

* ralp...@apache.org

* jinh...@apache.org

* daz...@apache.org

* senthilec...@apache.org

* hdenduk...@apache.org

* m...@apache.org

* arunmanoha...@apache.org

* cgu...@apache.org

* lib...@apache.org



  NOW, THEREFORE, BE IT FURTHER RESOLVED, that Edward Zhang
  be appointed to the office of Vice President, Apache Eagle, 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 Eagle PMC be and hereby is
  tasked with the creation of a set of bylaws intended to
  encourage open development and increased participation in the
  Apache Eagle Project; and be it further

  RESOLVED, that the Apache Eagle Project be and hereby
  is tasked with the migration and rationalization of the Apache
  Incubator Eagle podling; and be it further

  RESOLVED, that all responsibilities pertaining to the Apache
  Incubator Eagle podling encumbered upon the Apache Incubator
  Project are hereafter discharged.

Re: 答复: Eagle graduation steps

[Edward Zhang]

Thanks Henry and all!

I will start another email to discuss proposed resolution for Apache Eagle,
which will be reviewed by board when graduation.

We provided resolution in previous emails, but looks we should have a
separate email to review that more.

Thanks
Edward

On Mon, Nov 14, 2016 at 11:40 AM, Jayesh Senjaliya <jhsonl...@gmail.com>
wrote:

> Agree with Henry,
>
> +1 for Edward Zhang as VP for Apache Eagle
>
> good luck!
>
> -Jayesh
>
> On Sun, Nov 13, 2016 at 11:48 PM, Tang Jijun(上海_技术部_数据平台_唐觊隽) <
> tangji...@yhd.com> wrote:
>
> > +1 for Edward Zhang as VP for Apache Eagle
> >
> > Best Wishes
> >
> > Ji Jun Tang
> > Jr. Engineer , Architecture - Fundation, Tech Dept
> > Floor 4, 295 ZUCHONGZHI RD, Zhangjiang, Shanghai (201203)
> >
> > -邮件原件-
> > 发件人: Zhao Qingwen [mailto:qingwen...@gmail.com]
> > 发送时间: 2016年11月14日 15:36
> > 收件人: dev@eagle.incubator.apache.org
> > 主题: Re: Eagle graduation steps
> >
> > +1 for Edward Zhang as VP for Apache Eagle
> >
> >
> > Best Regards,
> > Qingwen Zhao | 赵晴雯
> >
> >
> >
> >
> > 2016-11-14 15:28 GMT+08:00 Liangfei.Su <suliang...@gmail.com>:
> >
> > > +1 for Edward Zhang as VP for Apache Eagle
> > >
> > > Ralph
> > >
> > >
> > > On Mon, Nov 14, 2016 at 1:35 PM, Hao Chen <h...@apache.org> wrote:
> > >
> > > > +1 for nominating Edward as VP and Chair of Eagle.
> > > >
> > > > - Hao
> > > >
> > > > On Mon, Nov 14, 2016 at 1:14 PM, Henry Saputra
> > > > <henry.sapu...@gmail.com>
> > > > wrote:
> > > >
> > > > > Thanks for driving the graduation discussion, Edward,
> > > > >
> > > > > One thing that we need for graduation is VP or Chair for Eagle as
> > > > > Top
> > > > Level
> > > > > project.
> > > > >
> > > > > I am nominating Edward Zhang as VP for Apache Eagle since he has
> > > > > been
> > > > very
> > > > > active to drive Apache Eagle community,
> > > > >
> > > > > - Henry
> > > > >
> > > > > On Mon, Nov 7, 2016 at 9:27 PM, Edward Zhang
> > > > > <yonzhang2...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Hi Mentors,
> > > > > >
> > > > > > Can you please reply this email if you have remaining issues
> > > regarding
> > > > > > Eagle graduation before we call official vote?
> > > > > >
> > > > > > According to Apache project graduation guideline, we need make
> > > > > > sure
> > > > > mentors
> > > > > > and IPMC have no remaining issues.
> > > > > >
> > > > > >
> > > > > >- Ensure Mentors
> > > > > ><http://incubator.apache.org/incubation/Roles_and_
> > > > > > Responsibilities.html#Mentor>
> > > > > > and IPMC
> > > > > ><http://incubator.apache.org/incubation/Roles_and_
> > > > > > Responsibilities.html#Incubator+Project+Management+
> > > > Committee+%28PMC%29>
> > > > > > have
> > > > > >no remaining issues
> > > > > >
> > > > > > <http://incubator.apache.org/guides/graduation.html#notes-issues
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > Thanks
> > > > > > Edward
> > > > > >
> > > > > > On Sun, Nov 6, 2016 at 11:01 AM, Edward Zhang <
> > > yonzhang2...@apache.org
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Henry and Eagle Mentors,
> > > > > > >
> > > > > > > Seems we have gone through most of check list for graduation,
> > > > > > > can I
> > > > > start
> > > > > > > formal community vote on graduation according to
> > > > > http://incubator.apache
> > > > > > .
> > > > > > > org/guides/graduation.html#process?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >- a charter for your 

Re: Eagle graduation steps

[Edward Zhang]

Hi Mentors,

Can you please reply this email if you have remaining issues regarding
Eagle graduation before we call official vote?

According to Apache project graduation guideline, we need make sure mentors
and IPMC have no remaining issues.


   - Ensure Mentors
   
<http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor>
and IPMC
   
<http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29>
have
   no remaining issues
   <http://incubator.apache.org/guides/graduation.html#notes-issues>



Thanks
Edward

On Sun, Nov 6, 2016 at 11:01 AM, Edward Zhang <yonzhang2...@apache.org>
wrote:

> Hi Henry and Eagle Mentors,
>
> Seems we have gone through most of check list for graduation, can I start
> formal community vote on graduation according to http://incubator.apache.
> org/guides/graduation.html#process?
>
>
>
>- a charter for your project(Draft resolution was done)
>- a positive community graduation VOTE
><http://www.apache.org/foundation/voting.html>
>- a positive IPMC recommendation VOTE
><http://www.apache.org/foundation/voting.html>
>- the acceptance of the resolution
><http://incubator.apache.org/guides/graduation.html#tlp-resolution> by
>the Board
>
> Also, do you have any remaining issues about graduation before we do vote?
>
>
>- Ensure Mentors
>
> <http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor>
> and IPMC
>
> <http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29>
>  have
>no remaining issues
>    <http://incubator.apache.org/guides/graduation.html#notes-issues>
>
>
>
> Thanks
> Edward
>
> On Sun, Oct 30, 2016 at 8:59 PM, Edward Zhang <yonzhang2...@apache.org>
> wrote:
>
>> Hi Eagle community,
>>
>> As one step towards graduation, the following is proposed project
>> destination and resolution and please provide your feedback.
>>
>> For destination, according to the guide line
>> http://incubator.apache.org/guides/graduation.html#subprojec
>> t-or-top-level, because Apache Eagle is sponsored by IPMC, we should put
>> it to be top-level project instead of subproject.
>>
>> For revision, here is the template, template https://svn.apache.or
>> g/repos/private/committers/board/templates/podling-tlp-resolution.txt. I
>> put initial committers there and we need a chair for this project.
>>
>> Destination: Top-level project
>>
>> Revision:
>>
>>   Establish the Apache Eagle Project
>>
>>   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, related to a distributed monitoring solution for
>> identifying security and performance issues in real time on big data
>> platforms, including Hadoop and Spark etc.
>>
>>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>   Committee (PMC), to be known as the "Apache Eagle Project",
>>   be and hereby is established pursuant to Bylaws of the
>>   Foundation; and be it further
>>
>>   RESOLVED, that the Apache Eagle Project be and hereby is
>>   responsible for the creation and maintenance of software
>>   related to a distributed monitoring solution for identifying
>> security and performance issues in real time on big data platforms,
>> including Hadoop and Spark etc.;
>>   and be it further
>>
>>   RESOLVED, that the office of "Vice President, Apache Eagle" 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 Eagle Project, and to have primary responsibility
>>   for management of the projects within the scope of
>>   responsibility of the Apache Eagle 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 Eagle Project:
>>
>>
>> * yonzhang2...@apache.org
>>
>> * h...@apache.org
>>
>> * qingwz...@apache.org
>>
>> * ji...@apache.org
>>
>> 

Re: Eagle graduation steps

[Edward Zhang]

Hi Henry and Eagle Mentors,

Seems we have gone through most of check list for graduation, can I start
formal community vote on graduation according to
http://incubator.apache.org/guides/graduation.html#process?



   - a charter for your project(Draft resolution was done)
   - a positive community graduation VOTE
   <http://www.apache.org/foundation/voting.html>
   - a positive IPMC recommendation VOTE
   <http://www.apache.org/foundation/voting.html>
   - the acceptance of the resolution
   <http://incubator.apache.org/guides/graduation.html#tlp-resolution> by
   the Board

Also, do you have any remaining issues about graduation before we do vote?


   - Ensure Mentors
   
<http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor>
and IPMC
   
<http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29>
have
   no remaining issues
   <http://incubator.apache.org/guides/graduation.html#notes-issues>



Thanks
Edward

On Sun, Oct 30, 2016 at 8:59 PM, Edward Zhang <yonzhang2...@apache.org>
wrote:

> Hi Eagle community,
>
> As one step towards graduation, the following is proposed project
> destination and resolution and please provide your feedback.
>
> For destination, according to the guide line http://incubator.apache.org/
> guides/graduation.html#subproject-or-top-level, because Apache Eagle is
> sponsored by IPMC, we should put it to be top-level project instead of
> subproject.
>
> For revision, here is the template, template https://svn.apache.
> org/repos/private/committers/board/templates/podling-tlp-resolution.txt.
> I put initial committers there and we need a chair for this project.
>
> Destination: Top-level project
>
> Revision:
>
>   Establish the Apache Eagle Project
>
>   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, related to a distributed monitoring solution for
> identifying security and performance issues in real time on big data
> platforms, including Hadoop and Spark etc.
>
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache Eagle Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
>
>   RESOLVED, that the Apache Eagle Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to a distributed monitoring solution for identifying
> security and performance issues in real time on big data platforms,
> including Hadoop and Spark etc.;
>   and be it further
>
>   RESOLVED, that the office of "Vice President, Apache Eagle" 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 Eagle Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache Eagle 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 Eagle Project:
>
>
> * yonzhang2...@apache.org
>
> * h...@apache.org
>
> * qingwz...@apache.org
>
> * ji...@apache.org
>
> * ralp...@apache.org
>
> * jinh...@apache.org
>
> * daz...@apache.org
>
> * senthilec...@apache.org
>
> * hdenduk...@apache.org
>
> * m...@apache.org
>
> * arunmanoha...@apache.org
>
> * cgu...@apache.org
>
> * lib...@apache.org
>
>
>
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that {$name}
>   be appointed to the office of Vice President, Apache Eagle, 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 Eagle PMC be and hereby is
>   tasked with the creation of a set of bylaws intended to
>   encourage open development and increased participation in the
>   Apache Eagle Project; and be it further
>
>   RESOLVED, that the Apache Eagle Project be and hereby
>   is tasked w

Re: Podling Report Reminder - November 2016

[Edward Zhang]

I will do this by end of this week.

Thanks
Edward

On Wed, Oct 26, 2016 at 4:01 PM,  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 16 November 2016, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, November 02).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
>
> This should be appended to the Incubator Wiki page at:
>
> http://wiki.apache.org/incubator/November2016
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: Eagle graduation steps

[Edward Zhang]

I have verified the first 4 points in #1 preparations
  - update Eagle status page with latest information
http://incubator.apache.org/projects/eagle.html
  - name search was done last year with ticket solved
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-85
  - ability to create Apache releases, 2 releases was made,
https://github.com/apache/incubator-eagle/tree/branch-0.4 and
https://github.com/apache/incubator-eagle/tree/branch-0.3
  - community readiness. Some detailed information from Hao Chen
  1) Added *4+* new committers and *20+* contributors from
different organizations
around the world side
  2) Successfully released *2* major versions and some minor versions,
  3) resolved *632+* jira tickets and *577+* pull requests.
  4) *5+* public originations (e.g. eBay, Paypal, Yihaodian, Dataguise,
 etc.) are using or adopting eagle to monitor their hadoop clusters.
  5) Shared eagle and apache way in *10+* tech conferences in* 8+
*different cities around the world (e.g. Hadoop Summit, Hadoop Stratus,
QCon, etc.)


If you got time please review and give your feedback.
I will continue to check the rest of information.

Thanks
Edward

On Thu, Oct 20, 2016 at 9:01 PM, Edward Zhang <yonzhang2...@apache.org>
wrote:

> I found the document about Apache project graduation steps, we can use
> that to graduate step by step.
>
> http://incubator.apache.org/guides/graduation.html
>
> I will update the status frequently on the following check list and will
> call for a VOTE if necessary.
>
> Graduation Check List
>
> The following is a short checklist giving an overview, not a substitute
> for reading the content below.
>
>1. Preparations
>   - Complete (and sign off) tasks documented in the status file
>   <http://incubator.apache.org/guides/graduation.html#notes-status>
>   - Ensure suitable names
>   <http://incubator.apache.org/guides/graduation.html#notes-names> for
>   project name and product names
>   - Demonstrate ability to create Apache releases
>   <http://incubator.apache.org/guides/graduation.html#releases>
>   - Demonstrate community readiness
>   <http://incubator.apache.org/guides/graduation.html#community>
>   - Ensure Mentors
>   
> <http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor>
>and IPMC
>   
> <http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29>
>  have
>   no remaining issues
>   <http://incubator.apache.org/guides/graduation.html#notes-issues>
>2. Decide upon destination
>
> <http://incubator.apache.org/guides/graduation.html#subproject-or-top-level>
>3. Prepare a resolution
><http://incubator.apache.org/guides/graduation.html#tlp-resolution> *(top
>level candidates only)*.
>4. Subproject acceptance VOTE
><http://incubator.apache.org/guides/graduation.html#subproject-acceptance> 
> by
>destination Project *(subproject candidates only)*
>5. Incubator PMC (IPMC)
>
> <http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29>
>:
>   - For top level candidates, this is a recommendation VOTE
>   
> <http://incubator.apache.org/guides/graduation.html#ipmc-top-level-recommendation>
>   - For subproject candidates, this is a graduation approval VOTE
>   
> <http://incubator.apache.org/guides/graduation.html#subproject-graduation>
>6. Final hand-over
><http://incubator.apache.org/guides/graduation.html#notes-on-hand-over>
>7. Consider post graduation tasks
><http://incubator.apache.org/guides/graduation.html#project-first-steps>
>
>

[DISCUSS] restart Eagle graduate discussion

[Edward Zhang]

s a security-related
> product I
> >> would expect there to be a well-defined process/protocol that
> ensured
> >> vulnerability reports were kept private until patched, CVE
> process, etc.
> >> Eagle hasn't had any major security issues during incubation,
> but should be
> >> prepared for them after graduation.
> >> >
> >> > Here [1] [2] are two great resources for understanding what
> is expected
> >> from an ASF standpoint.
> >> >
> >> > -Taylor
> >> >
> >> > [1] http://www.apache.org/security/
> >> > [2] http://www.apache.org/security/committers.html
> >> >
> >> >> On Aug 23, 2016, at 6:52 PM, Julian Hyde <jh...@apache.org>
> wrote:
> >> >>
> >> >> I reviewed https://cwiki.apache.org/confl
> >> uence/display/EAG/Eagle+Podling+Maturity+Assessment <
> >> https://cwiki.apache.org/confluence/display/EAG/Eagle+Podli
> >> ng+Maturity+Assessment> and it looks good.
> >> >>
> >> >> Only one issue. Regarding QU30: The dev list and JIRA
> (listed in
>     >> http://eagle.incubator.apache.org/sup/index.html <
> >> http://eagle.incubator.apache.org/sup/index.html>) do not seem
> >> appropriate places to report security issues, because they are
> public. Is a
> >> private channel needed?
> >> >>
> >> >> Can some other mentors please review?
> >> >>
> >> >> I think the consensus is emerging that Eagle is ready to
> graduate. The
> >> community should start taking steps to graduate, including
> agreeing bylaws
> >> (or deciding that bylaws are not necessary), choosing an
> initial PMC chair,
> >> crafting the resolution for the Board, and starting a vote
> thread.
> >> >>
> >> >> Julian
> >> >>
> >> >>
> >> >>
> >> >>> On Jul 31, 2016, at 9:05 PM, Edward Zhang <
> yonzhang2...@apache.org>
> >> wrote:
> >> >>>
> >> >>> I have commented some assessment points and we can remove
> that once
> >> after
> >> >>> they are reviewed.
> >> >>>
> >> >>> Thanks
> >> >>> Edward
> >> >>>
> >> >>>> On Sun, Jul 31, 2016 at 7:09 PM, Hao Chen <h...@apache.org>
> wrote:
> >> >>>>
> >> >>>> Thanks Michael for preparing the "Eagle Podling Maturity
> Assessment".
> >> >>>>
> >> >>>> Eagle community,
> >> >>>>
> >> >>>> could you (in particular Mentors & PPMC) please help
> review and
> >> comment?
> >> >>>>
> >> >>>> - Hao
> >> >>>>
> >> >>>>> On Fri, Jul 29, 2016 at 4:36 PM, Michael Wu <
> mchl@gmail.com>
> >> wrote:
> >> >>>>>
> >> >>>>> Hi guys,
> >> >>>>>
> >> >>>>> Following the model Julian cited, we created a wiki page
> for
> >> >>>>> self-assessment at:
> >> >>>>>
> >> >>>>>
> >> >>>> https://cwiki.apache.org/confluence/display/EAG/Eagle+
> Podlin
> >> g+Maturity+Assessment
> >> >>>>> .
> >> >>>>> Please take a look at it and make your valuable judgement
> and
> >> >>>> instructions.
> >> >>>>>
> >> >>>>> Overall, according to the aspects that the model values
> and
> >> inspects, and
> >> >>>>> traverse the results listed in the wiki page, personally,
> I think
> >> Eagle
> >> >>>> is
> >> >>>>> approaching the point of graduation, and is facing the
> right way

[jira] [Updated] (EAGLE-531) Dedup alerts according to state change

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang updated EAGLE-531:
---
Description: This is for stateful and stateless logs  (was: 
https://wiki.vip.corp.ebay.com/pages/viewpage.action?pageId=361488851)

> Dedup alerts according to state change
> --
>
> Key: EAGLE-531
> URL: https://issues.apache.org/jira/browse/EAGLE-531
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Garrett Li
>Assignee: Garrett Li
> Fix For: v0.5.0
>
>
> This is for stateful and stateless logs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Can You Give Me More Sample Data to Be Used for Training

[Edward Zhang]

Hi Xin Wu,

Sorry for late reply. Thanks for your interest in user profile but it looks
very hard to provide more sample data. Sometimes you need production data
to simulate your test.

But if you need sample data, probably you can write program to generate
random ip, user, read/write cmd etc and do some fault injection. Anyway its
purpose is to find out the obvious difference between training data and
test data.

2015-04-24 12:49:16,145 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfosrc=/tmp
dst=null   perm=null  proto=rpc
2015-04-24 12:49:16,192 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfo
src=/user/ambari-qadst=null   perm=null  proto=rpc
2015-04-24 12:49:20,518 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfosrc=/tmp
dst=null   perm=null  proto=rpc
2015-04-24 12:49:20,570 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfo
src=/user/ambari-qadst=null   perm=null  proto=rpc
2015-04-24 12:49:20,587 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfosrc=/
dst=null   perm=null  proto=rpc
2015-04-24 12:49:20,664 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=mkdirs src=/tmp   dst=null
perm=hdfs:hdfs:rwxr-xr-x   proto=rpc
2015-04-24 12:49:20,677 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfosrc=/user
dst=null   perm=null  proto=rpc
2015-04-24 12:49:20,686 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=mkdirs src=/user/ambari-qa
 dst=null   perm=hdfs:hdfs:rwxr-xr-x   proto=rpc
2015-04-24 12:49:24,828 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfosrc=/tmp
dst=null   perm=null  proto=rpc
2015-04-24 12:49:24,915 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=setPermission  src=/tmp
dst=null   perm=hdfs:hdfs:rwxrwxrwx   proto=rpc
2015-04-24 12:49:29,375 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfo
src=/user/ambari-qadst=null   perm=null  proto=rpc
2015-04-24 12:49:29,453 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=setPermission
src=/user/ambari-qadst=null   perm=hdfs:hdfs:rwxrwx---   proto=rpc
2015-04-24 12:49:33,542 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfosrc=/tmp
dst=null   perm=null  proto=rpc
2015-04-24 12:49:37,844 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfo
src=/user/ambari-qadst=null   perm=null  proto=rpc
2015-04-24 12:49:37,929 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=setOwner
src=/user/ambari-qadst=null   perm=ambari-qa:hdfs:rwxrwx---
proto=rpc
2015-04-24 12:51:31,798 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfo
src=/apps/hbase/data   dst=null   perm=null  proto=rpc
2015-04-24 12:51:31,863 INFO FSNamesystem.audit: allowed=true
ugi=hdfs (auth:SIMPLE) ip=/10.0.2.15  cmd=getfileinfo
src=/apps/hbase/stagingdst=null   perm=null  proto=rpc


Thanks

Edward


On Sat, Sep 17, 2016 at 7:41 PM, 辛武  wrote:

> Dear Eagle Development Team:
> My name is Xin Wu, a college student of Peking University, and I am
> writing in the hope of your assistance to provide more sample data to me.
> First and foremost I know Eagle is the first activity monitoring
> system on the Hadoop-ecosystem for the detection of intrusion-related
> activities using behavior-based profiles of users. I am particularly
> interested in the project of Eagle and its ideas, at the same time, I also
> read the paper, Eagle: User Profile-based Anomaly Detection for Securing
> Hadoop Clusters. And I want to learn more, I need more sample data for
> research. Will you be able to supply more data to me?
> Looking forward to a prompt reply from you.
>
>  Sincerely yours,
>Xin Wu
>

Re: MySql Connection properties in eagle-service.conf

[Edward Zhang]

In order not to block your current work, maybe you can try to config
storage-connection-url
to append extra connection properties, for example the following

url="jdbc:mysql://localhost/eagle_db?useUnicode=yescharacterEncoding=utf8"


On Wed, Sep 21, 2016 at 11:26 AM, Edward Zhang <yonzhang2...@apache.org>
wrote:

> This connection-props is not applied in the code, but it should be
> appended to end of connection string. I am looking into the place where we
> can hook this configuration. Are you using Eagle 0.3?
>
> Thanks
> Edward
>
> On Wed, Sep 21, 2016 at 10:51 AM, Jaspaul Chahal <jasp...@dataguise.com>
> wrote:
>
>> Anyone from Apache Eagle team please?
>>
>> Regards,
>> Jaspaul
>>
>> From: Jaspaul Chahal
>> Sent: Tuesday, September 20, 2016 5:26 PM
>> To: dev@eagle.incubator.apache.org
>> Cc: Subra Ramesh (sram...@dataguise.com) <sram...@dataguise.com>
>> Subject: MySql Connection properties in eagle-service.conf
>>
>> Hello Team,
>>
>> It's regarding MySql as backend repo fro Apache Eagle.
>>
>> In eagle-service.conf file for MySql we have the following property:
>>storage-connection-props="encoding=UTF-8"
>>
>> But, I couldn't find the code using this property for the connection
>> creation in  TorqueConnectionManagerImpl.buildConfiguration(ConnectionConfig
>> config) .
>>
>> Can someone please point me to the code where we are using this
>> connection properties for the connection. I need to pass some extra
>> connection parameters for MySql.
>>
>> Thanks in advance!
>>
>> Regards,
>> Jaspaul Chahal
>>
>
>

Re: MySql Connection properties in eagle-service.conf

[Edward Zhang]

This connection-props is not applied in the code, but it should be appended
to end of connection string. I am looking into the place where we can hook
this configuration. Are you using Eagle 0.3?

Thanks
Edward

On Wed, Sep 21, 2016 at 10:51 AM, Jaspaul Chahal 
wrote:

> Anyone from Apache Eagle team please?
>
> Regards,
> Jaspaul
>
> From: Jaspaul Chahal
> Sent: Tuesday, September 20, 2016 5:26 PM
> To: dev@eagle.incubator.apache.org
> Cc: Subra Ramesh (sram...@dataguise.com) 
> Subject: MySql Connection properties in eagle-service.conf
>
> Hello Team,
>
> It's regarding MySql as backend repo fro Apache Eagle.
>
> In eagle-service.conf file for MySql we have the following property:
>storage-connection-props="encoding=UTF-8"
>
> But, I couldn't find the code using this property for the connection
> creation in  TorqueConnectionManagerImpl.buildConfiguration(ConnectionConfig
> config) .
>
> Can someone please point me to the code where we are using this connection
> properties for the connection. I need to pass some extra connection
> parameters for MySql.
>
> Thanks in advance!
>
> Regards,
> Jaspaul Chahal
>

[jira] [Updated] (EAGLE-541) Application policy template framework

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang updated EAGLE-541:
---
Description: 
policy is pretty complex for example it should contain
1) siddhi expression (filter, timed window, etc.)
2) data partition keys
3) dedupe configuration
4) publishment configuration

Eagle should provide a wizard for user to easily onboard polices whatever it is 
a simple filtering policy or complicated timed windows

> Application policy template framework
> -
>
> Key: EAGLE-541
> URL: https://issues.apache.org/jira/browse/EAGLE-541
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.5.0
>Reporter: Hao Chen
>Assignee: Hao Chen
> Fix For: v0.5.0
>
>
> policy is pretty complex for example it should contain
> 1) siddhi expression (filter, timed window, etc.)
> 2) data partition keys
> 3) dedupe configuration
> 4) publishment configuration
> Eagle should provide a wizard for user to easily onboard polices whatever it 
> is a simple filtering policy or complicated timed windows



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-187) JDK 1.8 support for Eagle Build

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang closed EAGLE-187.
--
Resolution: Fixed

JDK 1.8 is already supported

> JDK 1.8 support for Eagle Build
> ---
>
> Key: EAGLE-187
> URL: https://issues.apache.org/jira/browse/EAGLE-187
> Project: Eagle
>  Issue Type: Bug
> Environment: Eagle should build with JDK1.8 and support it.
>Reporter: hemanth dendukuri
>Assignee: Edward Zhang
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-116) StormTopologyCompiler's boltCache looks not working

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang closed EAGLE-116.
--
Resolution: Won't Fix

This feature won't be useful with the new alert engine

> StormTopologyCompiler's boltCache looks not working
> ---
>
> Key: EAGLE-116
> URL: https://issues.apache.org/jira/browse/EAGLE-116
> Project: Eagle
>  Issue Type: Bug
>    Reporter: Edward Zhang
>    Assignee: Edward Zhang
>Priority: Minor
>
> I saw boltCache is not used anymore, need investigate and clean that if 
> necessary.
>   val boltCache = scala.collection.mutable.Map[StreamProducer[Any], 
> StormBoltWrapper]()
> def createBoltIfAbsent(graph: StreamProducerGraph, producer : 
> StreamProducer[Any]): BaseRichBolt ={
> boltCache.get(producer) match{
>   case Some(bolt) => bolt
>   case None => {
> StormBoltFactory.getBoltWrapper(graph, producer, config)
>   }
> }
>   }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-105) add test cases for state recovery in stream join, partitions, event table etc.

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang closed EAGLE-105.
--
Resolution: Won't Fix

This is no longer a feature because new alert engine can do stream join 
automatically

> add test cases for state recovery in stream join, partitions, event table etc.
> --
>
> Key: EAGLE-105
> URL: https://issues.apache.org/jira/browse/EAGLE-105
> Project: Eagle
>  Issue Type: Improvement
>    Reporter: Edward Zhang
>    Assignee: Edward Zhang
>Priority: Minor
>
> stream join, partitions, and event tables are features Eagle will use, we 
> need test if fault tolerance(state store and recover) can be successful under 
> those cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-43) Eagle Job Running Spout should support HTTPS

[Edward Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15501842#comment-15501842
 ] 

Edward Zhang commented on EAGLE-43:
---

Jinhu, does job spout already support HTTPS?

> Eagle Job Running Spout should support HTTPS
> 
>
> Key: EAGLE-43
> URL: https://issues.apache.org/jira/browse/EAGLE-43
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Libin, Sun
>Assignee: wujinhu
>
> Job Running Spout is a data source for hive security monitoring, it get data 
> from RM yarn API and RM web page, currently we only support HTTP, should add 
> HTTPS supprot



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-43) Eagle Job Running Spout should support HTTPS

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang updated EAGLE-43:
--
Assignee: wujinhu  (was: Edward Zhang)

> Eagle Job Running Spout should support HTTPS
> 
>
> Key: EAGLE-43
> URL: https://issues.apache.org/jira/browse/EAGLE-43
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.3.0
>Reporter: Libin, Sun
>Assignee: wujinhu
>
> Job Running Spout is a data source for hive security monitoring, it get data 
> from RM yarn API and RM web page, currently we only support HTTP, should add 
> HTTPS supprot



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-39) Policy State Management for robustness - replay events upon node crash

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang closed EAGLE-39.
-
Resolution: Won't Fix

This ticket will be considered in long time. We can revisit this feature when 
it is really necessary for that.

> Policy State Management for robustness - replay events upon node crash
> --
>
> Key: EAGLE-39
> URL: https://issues.apache.org/jira/browse/EAGLE-39
> Project: Eagle
>  Issue Type: New Feature
>    Reporter: Edward Zhang
>    Assignee: Edward Zhang
>
> Most useful policies are stateful, for example slide-window based policy is 
> evaluated not only for current event but also for a sequential set of events 
> happening before current event. 
> When the node which runs the stateful policy crashes, the policy would be 
> built up in another node by Eagle, but problem is we never see the events 
> which were populated for this policy before node crash.
> The problem sometimes will cause serious issues as it may miss some alerts. 
> Think about a policy which takes one month's data is gone because of the node 
> crash, how do we recover the one-month data for continuous evaluation.
> Unfortunately neither Storm as stream infrastructure nor Siddhi as CEP engine 
> provides state management of intermediate data generated in the program.
> Storm can bring up another bolt when one bolt goes down, but it is not 
> responsible for replay the events which application were previously received. 
> Siddhi does not provide any state recover when CEP runtime goes down.
> Eagle should provide some API for easy state management between monitoring 
> application and CEP engine. That would make a lot of sense when we define 
> complex policies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-26) Generic solution for Eagle topology merge

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang closed EAGLE-26.
-

> Generic solution for Eagle topology merge
> -
>
> Key: EAGLE-26
> URL: https://issues.apache.org/jira/browse/EAGLE-26
> Project: Eagle
>  Issue Type: New Feature
>    Reporter: Edward Zhang
>    Assignee: Edward Zhang
> Fix For: 0.5
>
>
> One Eagle topology can have multiple data sources, but in practice, some 
> policies need to join streams from multiple different topologies on the fly. 
> For example user security logging stream and user audit logging stream are 2 
> different physical topologies, if we want a policy like "user tries logon xxx 
> times and then access sensitive information", then we have develop a new 
> topology to join the 2 data sources. That is not good. We should provide a 
> way of easily merge the streams from the 2 existing topologies in runtime 
> instead of in development time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Switch develop to master branch

[Edward Zhang]

Like we discussed a few weeks back, community wants to use master branch as
development branch instead of develop branch.

We just make master to have the latest commit in develop branch, and from
now on, master branch will be the place where intensive development
happens. Any un-merged PR should be merged onto master branch.

Having master as develop branch has a few benefits like automatically to
close PR when commit and clearly to show github activities.

Going forward, we will clean develop branch. Also master branch is backed
in branch master-backup-20160907 for a while.

Thanks
Edward

Re: EAGLE-517

[Edward Zhang]

Hi Jayesh,

eagle-webservice is going to be replaced by eagle-server, I could not find
build issue in your ticket. Please copy/paste your build error.

Thanks
Edward

On Thu, Sep 1, 2016 at 2:20 PM, Jayesh Senjaliya 
wrote:

> Hi Guys,
>
> I found some issues while building it.
> can somebody pls take a look at the ticket : EAGLE-517 ?
>
> Thanks
> Jayesh
>

[jira] [Commented] (EAGLE-509) make streaming application's sink type to be java bean

[Edward Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15447189#comment-15447189
 ] 

Edward Zhang commented on EAGLE-509:


I am still not convinced by myself for how to do this correctly. We should 
think through some problems before we try to fix

1) is that possible we have multiple output streams from one application?

2) is that possible for one output stream to have multiple sink type e.g. kafka 
and log file?

3) is the binding between output stream and sink type configurable or fixed in 
code?

4) how to configure specific settings for one sink type per output stream

> make streaming application's sink type to be java bean
> --
>
> Key: EAGLE-509
> URL: https://issues.apache.org/jira/browse/EAGLE-509
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> Application's sink is used by alert engine, i.e. alert engine needs know each 
> field type for one sink.
> Sink type now is a Map type, which means developer has to configure each 
> field type in application descriptor file, that is boring and error-prone. If 
> we make sink type to be a java bean, then framework can automatically 
> generate field type to be used for defining alert metadata.
> Also with java bean, we can use annotation to customize more metadata, for 
> example use annotation to specify which field is timestamp column



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-505) oozie auditlog parser dontn`t deal with NullPointerException

[Edward Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446997#comment-15446997
 ] 

Edward Zhang commented on EAGLE-505:


oozie audit log monitoring needs to be converted to use app framework, are you 
going to do that?

> oozie auditlog parser dontn`t deal with NullPointerException
> 
>
> Key: EAGLE-505
> URL: https://issues.apache.org/jira/browse/EAGLE-505
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Lingang Deng
>Assignee: Lingang Deng
>Priority: Minor
>
> entity = parser.parse(logLine); object entity maybe is null.
> It will cause NullPointerException if there is no processing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-509) make streaming application's sink type to be java bean

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-509:
--

 Summary: make streaming application's sink type to be java bean
 Key: EAGLE-509
 URL: https://issues.apache.org/jira/browse/EAGLE-509
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


Application's sink is used by alert engine, i.e. alert engine needs know each 
field type for one sink.

Sink type now is a Map type, which means developer has to configure each field 
type in application descriptor file, that is boring and error-prone. If we make 
sink type to be a java bean, then framework can automatically generate field 
type to be used for defining alert metadata.

Also with java bean, we can use annotation to customize more metadata, for 
example use annotation to specify which field is timestamp column



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Please take notice to check-in only meaningful javadoc.

[Edward Zhang]

Run 'mvn javadoc:javadoc javadoc:test-javadoc', it now immediately failed
:-(

So looks like mvn javadoc can find out useless param.  Do we need do both
checkstyle and javadoc while in building?

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:javadoc (default-cli)
on project alert-common: An error has occurred in JavaDocs report
generation:
[ERROR] Exit code: 1 -
/Users/yonzhang/projects/incubator-eagle/eagle-core/eagle-alert-parent/eagle-alert/alert-common/src/main/java/org/apache/eagle/alert/config/ConfigBusProducer.java:32:
warning: no description for @param
[ERROR] * @param topic
[ERROR] ^
[ERROR]
/Users/yonzhang/projects/incubator-eagle/eagle-core/eagle-alert-parent/eagle-alert/alert-common/src/main/java/org/apache/eagle/alert/config/ConfigBusProducer.java:33:
warning: no description for @param
[ERROR] * @param config
[ERROR] ^



On Wed, Aug 24, 2016 at 9:55 AM, Julian Hyde  wrote:

> This bugs me too. FWIW, in Calcite we run ‘mvn javadoc:javadoc
> javadoc:test-javadoc’ as part of the automated build (as of JDK 1.8,
> javadoc is quite strict). Neither javadoc nor checkstyle will flag useless
> javadoc like ‘@param x’, so I wrote a checkstyle module[1] and call it from
> Calcite’s check style config[2].
>
> Julian
>
> [1] https://github.com/julianhyde/toolbox  julianhyde/toolbox>
>
> [2] https://issues.apache.org/jira/browse/CALCITE-1034 <
> https://issues.apache.org/jira/browse/CALCITE-1034>
>
> > On Aug 24, 2016, at 12:13 AM, Hao Chen  wrote:
> >
> > Good reminding. @Contributors, not only about java docs, pls. make sure
> all
> > the code style matches the checkstyle, currently I just keep the
> checkstyle
> > as WARNING as we still have lots of style warning to clean, in future we
> > should throw ERROR if any check-style doesn't match. Pls. start to spend
> > sometime cleaning the checkstyle warning in your code right now.
> >
> > - Hao
> >
> > On Wed, Aug 24, 2016 at 3:04 PM, Michael Wu  wrote:
> >
> >> Hi guys,
> >>
> >> Recently, when I tried to deploy eagle 0.5.0-incubating-snapshot
> artifacts
> >> based on develop branch, the entire build flow was broken by lots of
> faulty
> >> javadoc, which are classified in following aspects. I'll try to erase
> >> illegal/meaningless javadoc, and please PAY ATTENTION to your
> contribution
> >> and avoid checking-in such inappropriate javadoc:
> >>
> >> 1. Illegal character found, e.g. "<", or ">". Except for recognized html
> >> tags, such as "", "", etc., other angle brackets
> should
> >> be replaced with entities, say, "<" should be "", and ">" should be
> >> "".
> >>
> >> 2. Many "" and "" found in apache license comment, enclosing the
> >> license url. This kind of "p" tag is not allowed by javadoc, and
> actually,
> >> it's useless to be placed in the license comment either. Next time you
> >> create a new java file, please refer to another existing java file and
> >> copy+paste the correct license comment to the head of your new file, and
> >> make sure it does contain the "" pair around the license url.
> >>
> >> 3. Many meaningless parameters and javadoc blocks found in files. This
> >> issue could be more descriptive with a sample, see below javadoc
> fragment
> >> that appears many times in eagle project on develop branch:
> >>/**
> >> *
> >> * @param arg1
> >> * @param arg2
> >> * @return
> >> */
> >>This is a sample for rather meaningless javadoc. First, if there is
> no
> >> description, why shall we add this javadoc? Seconds, if we don't add
> >> description for arguments, who can know what to pass to the methods
> exactly
> >> by reading the javadoc? Third, if we don't add description for return
> >> value, how can customers understand the returning stuff by reading the
> >> javadoc? As a whole, such javadoc should be erased because we are not
> >> adding javadoc just for "adding", but for users or even code writers
> >> themselves to understand code more clearly.
> >>
> >> 4. Wrong upper case javadoc tag found. E.g. "@since" should be written
> in
> >> all lowercase, but found as "@Since", which make the javadoc generator
> >> complain with errors.
> >>
> >> So far, I've deployed eagle 0.5.0-incubating-snapshot to apache maven
> >> snapshot repository (
> >> https://repository.apache.org/content/repositories/
> >> snapshots/org/apache/eagle/).
> >> It currently doesn't include javadoc jars because there were too many
> >> javadoc error occurring while I was building the artifacts. When I
> erased
> >> incorrect ones in a sub model, that model ran pass and the next model in
> >> building chain raised up to complain. Therefore, it may cost me more
> time
> >> to erase all the faulty javadoc until all models are built successfully.
> >>
> >> Thank you for your understanding and cooperation.
> >>
> >> Michael
> >>
>
>

[jira] [Updated] (EAGLE-493) Create alert metadata based on application stream sink configuration

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang updated EAGLE-493:
---
Description: 
When I integrate hdfs audit log application with alert engine, it looks streams 
defined in applicationProvider.xml is not useful, because anyway we have to 
define data source, stream, policy and publishment using alert API. It is very 
difficult to convert streams in applicationProvider.xml to metadata used by 
alert engine. 

To achieve better user experience, we should create alert metadata 
automatically when application is installed based on application stream sink.

  was:
When I integrate hdfs audit log application with alert engine, it looks streams 
defined in applicationProvider.xml is not useful, because anyway we have to 
define data source, stream, policy and publishment using alert API. It is very 
difficult to convert streams in applicationProvider.xml to metadata used by 
alert engine. 

So my suggestion is to remove streams definition in applicationProvider.xml, 
and put related metadata scripts into docs in applicationProvider.xml.

By this way, stream definition becomes optional and application developer can 
write script for integrating application with alert engine.


> Create alert metadata based on application stream sink configuration
> 
>
> Key: EAGLE-493
> URL: https://issues.apache.org/jira/browse/EAGLE-493
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
> Fix For: v0.5.0
>
>
> When I integrate hdfs audit log application with alert engine, it looks 
> streams defined in applicationProvider.xml is not useful, because anyway we 
> have to define data source, stream, policy and publishment using alert API. 
> It is very difficult to convert streams in applicationProvider.xml to 
> metadata used by alert engine. 
> To achieve better user experience, we should create alert metadata 
> automatically when application is installed based on application stream sink.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-493) Create alert metadata based on application stream sink configuration

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang updated EAGLE-493:
---
Summary: Create alert metadata based on application stream sink 
configuration  (was: Move stream definition in streams of provider.xml to docs)

> Create alert metadata based on application stream sink configuration
> 
>
> Key: EAGLE-493
> URL: https://issues.apache.org/jira/browse/EAGLE-493
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
> Fix For: v0.5.0
>
>
> When I integrate hdfs audit log application with alert engine, it looks 
> streams defined in applicationProvider.xml is not useful, because anyway we 
> have to define data source, stream, policy and publishment using alert API. 
> It is very difficult to convert streams in applicationProvider.xml to 
> metadata used by alert engine. 
> So my suggestion is to remove streams definition in applicationProvider.xml, 
> and put related metadata scripts into docs in applicationProvider.xml.
> By this way, stream definition becomes optional and application developer can 
> write script for integrating application with alert engine.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-493) Move stream definition in streams of provider.xml to docs

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-493:
--

 Summary: Move stream definition in streams of provider.xml to docs
 Key: EAGLE-493
 URL: https://issues.apache.org/jira/browse/EAGLE-493
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
Priority: Minor
 Fix For: v0.5.0


When I integrate hdfs audit log application with alert engine, it looks streams 
defined in applicationProvider.xml is not useful, because anyway we have to 
define data source, stream, policy and publishment using alert API. It is very 
difficult to convert streams in applicationProvider.xml to metadata used by 
alert engine. 

So my suggestion is to remove streams definition in applicationProvider.xml, 
and put related metadata scripts into docs in applicationProvider.xml.

By this way, stream definition becomes optional and application developer can 
write script for integrating application with alert engine.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-491) AlertPublisherImpl dedup throws exception when dedup column is not configured

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-491:
--

 Summary: AlertPublisherImpl dedup throws exception when dedup 
column is not configured
 Key: EAGLE-491
 URL: https://issues.apache.org/jira/browse/EAGLE-491
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
Priority: Trivial
 Fix For: v0.5.0


2016-08-22 14:51:49,728 WARN [alertBolt1-evaluator_stage1] 
runner.AlertBolt[127]: Spec Version [spec_version_1471902692329] of AlertBolt 
is newer than Stream Event Version [null]!
2016-08-22 14:51:49,729 ERROR [Thread-45-alertPublishBolt] 
impl.AlertPublisherImpl[80]: Fail invoking publisher's onAlert, continue 
java.lang.NullPointerException
at 
org.apache.eagle.alert.engine.publisher.impl.DefaultDeduplicator.dedup(DefaultDeduplicator.java:114)
at 
org.apache.eagle.alert.engine.publisher.impl.AbstractPublishPlugin.dedup(AbstractPublishPlugin.java:68)
at 
org.apache.eagle.alert.engine.publisher.impl.AlertEmailPublisher.onAlert(AlertEmailPublisher.java:67)
at 
org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.notifyAlert(AlertPublisherImpl.java:78)
at 
org.apache.eagle.alert.engine.publisher.impl.AlertPublisherImpl.nextEvent(AlertPublisherImpl.java:65)
at 
org.apache.eagle.alert.engine.runner.AlertPublisherBolt.execute(AlertPublisherBolt.java:68)
at 
backtype.storm.daemon.executor$fn__3441$tuple_action_fn__3443.invoke(executor.clj:633)
at 
backtype.storm.daemon.executor$mk_task_receiver$fn__3364.invoke(executor.clj:401)
at 
backtype.storm.disruptor$clojure_handler$reify__1447.onEvent(disruptor.clj:58)
at 
backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:125)
at 
backtype.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:99)
at 
backtype.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:80)
at 
backtype.storm.daemon.executor$fn__3441$fn__3453$fn__3500.invoke(executor.clj:748)
at backtype.storm.util$async_loop$fn__464.invoke(util.clj:463)
at clojure.lang.AFn.run(AFn.java:24)
at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-490) KafkaStreamSink should not assume fixed field user to do partition

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-490:
--

 Summary: KafkaStreamSink should not assume fixed field user to do 
partition
 Key: EAGLE-490
 URL: https://issues.apache.org/jira/browse/EAGLE-490
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


KafkaStreamSink assumes user as the field to do partition. This should be 
configurable in application metadata file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-451) oozie ingestion+alert engine preview

[Edward Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431226#comment-15431226
 ] 

Edward Zhang commented on EAGLE-451:


yes, they are the same, I have close #448

> oozie ingestion+alert engine preview
> 
>
> Key: EAGLE-451
> URL: https://issues.apache.org/jira/browse/EAGLE-451
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Lingang Deng
>Assignee: Lingang Deng
>Priority: Trivial
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-448) convert eagle-oozie app to use new app framework

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang closed EAGLE-448.
--
Resolution: Duplicate

same to #451

> convert eagle-oozie app to use new app framework
> 
>
> Key: EAGLE-448
> URL: https://issues.apache.org/jira/browse/EAGLE-448
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> eagle-oozie app should use new app framework to manage its lifecycle



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [Discussion] How to refactor EagleConfigFactory

[Edward Zhang]

EagleConfigFactory, LogReader, LogWriter are developed for reading/writing
data to HBase only at the beginning of Eagle open source. At that time,
HBase acts as both metadata storage and log/metric data storage. But some
feedback from community is that Eagle sometimes is used for monitoring
where HBase is not ready. There is a requirement that Eagle can be run
without HBase dependency. That is why in Eagle 0.5, all metadata are stored
in relational database or mongodb which is common to most users.

But for application data, for example metrics or logs, it is still not
decided yet which storage is final choice. But for job related performance
monitoring, all data including metrics and logs are stored in HBase.  Some
other storage is also evaluated for example druid for metrics and
elasticsearch for log. But it is not finalized.

Difference between log and metric is that metric stores numeric data with
dimensions, while log stores any type of data. Some storage like TSDB,
Druid they made optimization for metric storage.

Thanks
Edward

On Mon, Aug 22, 2016 at 2:08 AM, Chang Chen <baibaic...@gmail.com> wrote:

> What make me confused is EagleConfigFactory directly depends on HBase. But
> there are 2 interfaces for persisting data, one is DataStorage, the other
> are LogReader and LogWriter.  Which one will be removed?
>
> I also noticed that eagle 0.5 architecture (
> https://cwiki.apache.org/confluence/display/EAG/Architecture+of+Eagle+0.5)
> was updated. What are the difference between "log" and "metric"?
>
> Thanks
> Chang
>
> On Wednesday, August 17, 2016, Liangfei.Su <suliang...@gmail.com> wrote:
>
> > On test scenario with different config need for differest, i simply do
> > ConfigFactory.invalidateCaches() in setup().
> >
> >
> > On Wed, Aug 17, 2016 at 9:43 AM, Edward Zhang <yonzhang2...@apache.org
> > <javascript:;>>
> > wrote:
> >
> > > Sorry I mean "remove" :-)
> > >
> > > Thanks
> > > Edward
> > >
> > > On Tue, Aug 16, 2016 at 6:35 PM, Chang Chen <baibaic...@gmail.com
> > <javascript:;>> wrote:
> > >
> > > > Hi Edward
> > > >
> > > > Does remote mean run TestEagleConfig in different JVM?
> > > >
> > > > Thanks
> > > > Chang
> > > >
> > > > On Wednesday, August 17, 2016, Edward Zhang <yonzhang2...@apache.org
> > <javascript:;>>
> > > > wrote:
> > > >
> > > > > TestEagleConfig is not a valid test case because it assumes that it
> > can
> > > > > initialize EagleConfigFactory, but when we execute multiple test
> > cases,
> > > > > this may not work as EagleConfigFactory may already be initialized
> > > before
> > > > > this test case is executed. So setting "config.resource" will not
> > have
> > > > any
> > > > > effect.
> > > > >
> > > > > I suggest we remote TestEagleConfig, and also going forward we can
> > need
> > > > > refactor EagleConfigFactor to be not a singleton but use
> > > > > com.typesafe.config.Config as constructor parameter.
> > > > >
> > > > > Thanks
> > > > > Edward
> > > > >
> > > > > On Tue, Aug 16, 2016 at 4:26 AM, Chang Chen <baibaic...@gmail.com
> > <javascript:;>
> > > > > <javascript:;>> wrote:
> > > > >
> > > > > > Hi Guys
> > > > > >
> > > > > > In the middle of writing UT for Eagle, we found it is difficult
> to
> > > mock
> > > > > >  EagleConfigFactory, since it has static method. The current
> > > workaround
> > > > > is
> > > > > > introducing powermock, so that we can set manager to mock object
> ,
> > > i.e.
> > > > > >
> > > > > >Whitebox.setInternalState(EagleConfigFactory.class,
> "manager",
> > > > > > eagleConfigFactory);
> > > > > >
> > > > > > This is OK in most cases, but TestEagleConfig.testInit could be
> > > failed,
> > > > > > because manager only initialized at first time and
> > > >  EagleConfigFactory's
> > > > > > Constructor is private:
> > > > > >
> > > > > >private static EagleConfigFactory manager = new
> > > > EagleConfigFactory();
> > > > > >
> > > > > > EagleConfigFactory actually has two roles, one is factory and
> > another
> > > > is
> > > > > > configuration. I propose refactoring EagleConfigFactory and
> > > distinguish
> > > > > > these two roles:
> > > > > >
> > > > > > public class EagleConfigImpl implements EagleConfig{
> > > > > > }
> > > > > >
> > > > > > public class EagleConfigFactory {
> > > > > >   public static EagleConfig load(){}
> > > > > >   public static void reset(EagleConfig config){
> > > > > > if (config == null) {
> > > > > >   //default
> > > > > > }else{
> > > > > > }
> > > > > >   }
> > > > > > }
> > > > > >
> > > > > > However doing so, we need call EagleConfigFactory.reset at the
> > > > beginning
> > > > > of
> > > > > >  eagle start.
> > > > > >
> > > > > > Any ideas?
> > > > > >
> > > > > > Thanks
> > > > > > Chang
> > > > > >
> > > > >
> > > >
> > >
> >
>

[jira] [Updated] (EAGLE-487) use guice module better in app framework

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang updated EAGLE-487:
---
Description: 
There are multiple issues with using guice module in app framework.

1. ApplicationProviderServiceImpl is instantiated twice

2. the interface between application and eagle server is not clear. It is not 
correct to only let application to register submodules,, instead it should 
includes some state inherited from eagle server, for example metadata storage 
type.

3. not necessary to use module scope, it is pretty over-engineering when 
application only want to register some module.

4. MemoryMetadataStore should use singleton

  was:
There are multiple issues with using guice module in app framework.

1. ApplicationProviderServiceImpl is instantiated twice

2. the interface between application and eagle server is not clear. It is not 
correct to only let application to register submodules,, instead it should 
includes some state inherited from eagle server, for example metadata storage 
type.

3. not necessary to use module scope, it is pretty over-engineering when 
application only want to register some module.


> use guice module better in app framework
> 
>
> Key: EAGLE-487
> URL: https://issues.apache.org/jira/browse/EAGLE-487
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> There are multiple issues with using guice module in app framework.
> 1. ApplicationProviderServiceImpl is instantiated twice
> 2. the interface between application and eagle server is not clear. It is not 
> correct to only let application to register submodules,, instead it should 
> includes some state inherited from eagle server, for example metadata storage 
> type.
> 3. not necessary to use module scope, it is pretty over-engineering when 
> application only want to register some module.
> 4. MemoryMetadataStore should use singleton



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-487) use guice module better in app framework

[Edward Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429520#comment-15429520
 ] 

Edward Zhang commented on EAGLE-487:


Proposed solution:
We have several level of modules:
1. eagle server module, for example config 
2. alert service module, for example alertMetadata service
3. app service module, for example appProviderService, appEntityService etc.
4. app specific module, for example security monitoring service module



> use guice module better in app framework
> 
>
> Key: EAGLE-487
> URL: https://issues.apache.org/jira/browse/EAGLE-487
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> There are multiple issues with using guice module in app framework.
> 1. ApplicationProviderServiceImpl is instantiated twice
> 2. the interface between application and eagle server is not clear. It is not 
> correct to only let application to register submodules,, instead it should 
> includes some state inherited from eagle server, for example metadata storage 
> type.
> 3. not necessary to use module scope, it is pretty over-engineering when 
> application only want to register some module.
> 4. MemoryMetadataStore should use singleton



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-487) use guice module better in app framework

[Edward Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15428850#comment-15428850
 ] 

Edward Zhang commented on EAGLE-487:


different createInjector will separate different implementations for one 
interface. This would cause multiple instances.

> use guice module better in app framework
> 
>
> Key: EAGLE-487
> URL: https://issues.apache.org/jira/browse/EAGLE-487
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> There are multiple issues with using guice module in app framework.
> 1. ApplicationProviderServiceImpl is instantiated twice
> 2. the interface between application and eagle server is not clear. It is not 
> correct to only let application to register submodules,, instead it should 
> includes some state inherited from eagle server, for example metadata storage 
> type.
> 3. not necessary to use module scope, it is pretty over-engineering when 
> application only want to register some module.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-487) use guice module better in app framework

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-487:
--

 Summary: use guice module better in app framework
 Key: EAGLE-487
 URL: https://issues.apache.org/jira/browse/EAGLE-487
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


There are multiple issues with using guice module in app framework.

1. ApplicationProviderServiceImpl is instantiated twice

2. the interface between application and eagle server is not clear. It is not 
correct to only let application to register submodules,, instead it should 
includes some state inherited from eagle server, for example metadata storage 
type.

3. not necessary to use module scope, it is pretty over-engineering when 
application only want to register some module.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-481) Make alert engine topology to be one application so to be managed by Eagle API

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-481:
--

 Summary: Make alert engine topology to be one application so to be 
managed by Eagle API
 Key: EAGLE-481
 URL: https://issues.apache.org/jira/browse/EAGLE-481
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


Eagle alert engine as of 0.5 is multiple separate storm topologies. Instead of 
running alert engine manually, we can leverage Eagle 0.5 application API to 
manage alert engine. 

Options:
1. Wrapper alert engine topology to be one Eagle application

2. Define a new service API to directly start/stop alert engine



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-480) Make Hadoop jmx monitoring working in Eagle 0.5

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-480:
--

 Summary: Make Hadoop jmx monitoring working in Eagle 0.5
 Key: EAGLE-480
 URL: https://issues.apache.org/jira/browse/EAGLE-480
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


Hadoop jmx metrics data will go to alert engine directly, we need verify how to 
create data source, stream and policies in Eagle 0.5



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-478) Eagle README in Eagle 0.5 version

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-478:
--

 Summary: Eagle README in Eagle 0.5 version
 Key: EAGLE-478
 URL: https://issues.apache.org/jira/browse/EAGLE-478
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
Priority: Minor
 Fix For: v0.5.0


Readme for starting Eagle 0.5 services:
1) start eagle-server
2) start one application
3) start alert engine topology



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-477) eagle-data-process project clean up to contain only common processing classes

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-477:
--

 Summary: eagle-data-process project clean up to contain only 
common processing classes
 Key: EAGLE-477
 URL: https://issues.apache.org/jira/browse/EAGLE-477
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
Priority: Minor
 Fix For: v0.5.0


eagle-data-process was used for orchestrating application logic, but now it is 
not useful any more, we only need keep some common classes for example spout 
factory and some custom partitioning code



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-474) some improvements of app framework: appId naming, jarFile field, InstallOperation etc.

[Edward Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425625#comment-15425625
 ] 

Edward Zhang commented on EAGLE-474:


appId in ApplicationEntity should be renamed to appType. It is not necessary to 
let appId to contain site.

Application instance should be identified by app type and uuid (uuid can 
contain site)

> some improvements of app framework: appId naming, jarFile field, 
> InstallOperation etc.
> --
>
> Key: EAGLE-474
> URL: https://issues.apache.org/jira/browse/EAGLE-474
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>Reporter: Edward Zhang
>    Assignee: Edward Zhang
>Priority: Minor
> Fix For: v0.5.0
>
>
> App framework has some bugs and also needs some improvement
> 1. appId in ApplicationEntity should not contain "[,]" chars, which will make 
> storm UI not show the topology details
> 2. jarPath is not necessary to be part of ApplicationDesc or metadata xml file
> 3. InstallOperation should contain jarPath which should be in the same level 
> of appType etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Eagle mongodb test case failed in develop branch

[Edward Zhang]

It failed in Apache Jenkins, in my local it is ok.
Can you fix if you know how?


https://builds.apache.org/job/incubator-eagle-develop/40/testReport/org.apache.eagle.service.alert.resource.impl/MongoImplTest/org_apache_eagle_service_alert_resource_impl_MongoImplTest/



Error Message

Couldn't kill mongod process!
 Something bad
happend. We couldn't kill mongod process, and tried a lot. If you want
this problem solved you can help us if you open a new issue.  Follow
this link: https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo/issues
 Thank you:) 

Stacktrace

java.lang.IllegalStateException: Couldn't kill mongod process!


Something bad happend. We couldn't kill mongod process, and tried a lot.
If you want this problem solved you can help us if you open a new issue.

Re: [Discussion] How to refactor EagleConfigFactory

[Edward Zhang]

TestEagleConfig is not a valid test case because it assumes that it can
initialize EagleConfigFactory, but when we execute multiple test cases,
this may not work as EagleConfigFactory may already be initialized before
this test case is executed. So setting "config.resource" will not have any
effect.

I suggest we remote TestEagleConfig, and also going forward we can need
refactor EagleConfigFactor to be not a singleton but use
com.typesafe.config.Config as constructor parameter.

Thanks
Edward

On Tue, Aug 16, 2016 at 4:26 AM, Chang Chen  wrote:

> Hi Guys
>
> In the middle of writing UT for Eagle, we found it is difficult to mock
>  EagleConfigFactory, since it has static method. The current workaround is
> introducing powermock, so that we can set manager to mock object , i.e.
>
>Whitebox.setInternalState(EagleConfigFactory.class, "manager",
> eagleConfigFactory);
>
> This is OK in most cases, but TestEagleConfig.testInit could be failed,
> because manager only initialized at first time and   EagleConfigFactory's
> Constructor is private:
>
>private static EagleConfigFactory manager = new EagleConfigFactory();
>
> EagleConfigFactory actually has two roles, one is factory and another is
> configuration. I propose refactoring EagleConfigFactory and distinguish
> these two roles:
>
> public class EagleConfigImpl implements EagleConfig{
> }
>
> public class EagleConfigFactory {
>   public static EagleConfig load(){}
>   public static void reset(EagleConfig config){
> if (config == null) {
>   //default
> }else{
> }
>   }
> }
>
> However doing so, we need call EagleConfigFactory.reset at the beginning of
>  eagle start.
>
> Any ideas?
>
> Thanks
> Chang
>

[jira] [Created] (EAGLE-469) make dataSource configuration extremely simple

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-469:
--

 Summary: make dataSource configuration extremely simple
 Key: EAGLE-469
 URL: https://issues.apache.org/jira/browse/EAGLE-469
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
Priority: Minor
 Fix For: v0.5.0


Today dataSource configuration is very cumbersome, we actually can reduce 
significantly the size of config entries as most of configurations use the 
default values.
"dataSourceConfig": {
"topic" : "sandbox_hbase_security_log",
"zkConnection" : "sandbox.hortonworks.com:2181",
"zkConnectionTimeoutMS" : 15000,
"consumerGroupId" : "EagleConsumer",
"fetchSize" : 1048586,
"deserializerClass" : 
"org.apache.eagle.security.hbase.HbaseAuditLogKafkaDeserializer",
"transactionZKServers" : "sandbox.hortonworks.com",
"transactionZKPort" : 2181,
"transactionZKRoot" : "/consumers",
"consumerGroupId" : "eagle.hbasesecurity.consumer",
"transactionStateUpdateMS" : 2000
  }

The new data source config would be like:
"dataSourceConfig": {
"topic" : "hbase_audit_log",
"zkConnection" : "server.eagle.apache.org:2181",
"txZkServers" : "server.eagle.apache.org:2181",
"schemeCls" : "storm.kafka.StringScheme"
  }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-468) clean up eagle-application-service to be replaced by new app framework

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-468:
--

 Summary: clean up eagle-application-service to be replaced by new 
app framework
 Key: EAGLE-468
 URL: https://issues.apache.org/jira/browse/EAGLE-468
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
Priority: Minor
 Fix For: v0.5.0


application service provides web resources for managing storm topology 
remotely, this is replaced by new app framework.
But in new app framework, we still need investigate how to monitor application 
status.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-463) One App type may be run as multiple instances in one site

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-463:
--

 Summary: One App type may be run as multiple instances in one site
 Key: EAGLE-463
 URL: https://issues.apache.org/jira/browse/EAGLE-463
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


Today in one site, one app type can be run only as one instance. In some 
scenarios, one application code can be run with multiple instances, for example 
to deal with different topics.

One typical example is JMX metric application can be for namenode, datanode , 
resource manager etc. They are all the same type of applications, i.e. code 
logic with different configurations for example topic for data sources



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Heads up for Eagle 0.5 in develop branch

[Edward Zhang]

Hi Eagle Community,

There are some on-going significant changes in Eagle 0.5 regarding code
structure and features. These changes happen in develop branch, so we see
many PRs recently.

One heads up is those changes may break the existing way of you running an
Eagle application. It needs one week or so to make all applications to run
in a new way consistently.

Those significant changes are as follows:

1. Alert engine is decoupled into a separate component. Before Eagle 0.5,
application uses alert engine as a java library. In Eagle 0.5, Alert engine
becomes a multi-tenant platform where data from different applications can
potentially go into one single (or multiple) storm topology to be evaluated
based on some CEP rules. Also, Alert engine will support correlation of
different streams of events by declaring multiple input streams in one
policy.

This decoupling brings extra benefit e.g. any data in Kafka can go to alert
engine directly for alerting purposing without having to write code if the
data in Kafka is already ready for setting up rule.

2. Application configuration and lifecycle management. Before Eagle 0.5,
application is one storm topology which we use local configuration file to
manage, start, stop in a linux box. But Eagle in production normally
consists of many topologies which process different type of data sources.
Operational cost is very big without Eagle to manage those applications'
configuration and lifecycle.

In Eagle 0.5, application constitutes 2 parts, i.e. managed storm topology
and web resources. Both parts need configurations and those configurations
are managed by Eagle API. By this way, operations can start/stop/status
check storm topology remotely and manage multiple sites(datacenter) in one
organization.

Another benefit of application management is that it is very easy to
onboard a new Eagle monitoring application because processing(topology) and
web(UI/API) are both managed by Eagle platform.

3. More features. Besides existing security features, Eagle community has
integrated more Hadoop monitoring related features into Eagle, including
Hadoop running job, history job, Yarn queue, JMX metrics, Namenode log, GC
log, bad node check etc.

Because of #1 and #2, Eagle platform now becomes more open and friendly to
add any new monitoring features.

Thanks
Edward

[jira] [Updated] (EAGLE-432) Application status monitoring

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang updated EAGLE-432:
---
Assignee: DanielZhou  (was: Edward Zhang)

> Application status monitoring
> -
>
> Key: EAGLE-432
> URL: https://issues.apache.org/jira/browse/EAGLE-432
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: DanielZhou
> Fix For: v0.5.0
>
>
> App framework needs to probe application status periodically or on demand.
> ApplicationEntity contains status field, and this field's value should come 
> from physical storm applications.
> We can start background threads to check application status or on-demand.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (EAGLE-447) convert eagle-maprfs app to use new app framework

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang updated EAGLE-447:
---
Assignee: DanielZhou  (was: Edward Zhang)

> convert eagle-maprfs app to use new app framework
> -
>
> Key: EAGLE-447
> URL: https://issues.apache.org/jira/browse/EAGLE-447
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: DanielZhou
> Fix For: v0.5.0
>
>
>  eagle-maprfs app should use new app framework to manage its lifecycle



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-449) clean inner process alert engine code

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-449:
--

 Summary: clean inner process alert engine code
 Key: EAGLE-449
 URL: https://issues.apache.org/jira/browse/EAGLE-449
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


alert engine now is separated into a standalone storm topology, it is not 
necessary to keep inner process alert engine



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-448) convert eagle-oozie app to use new app framework

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-448:
--

 Summary: convert eagle-oozie app to use new app framework
 Key: EAGLE-448
 URL: https://issues.apache.org/jira/browse/EAGLE-448
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


eagle-oozie app should use new app framework to manage its lifecycle



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-447) convert eagle-maprfs app to use new app framework

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-447:
--

 Summary: convert eagle-maprfs app to use new app framework
 Key: EAGLE-447
 URL: https://issues.apache.org/jira/browse/EAGLE-447
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


 eagle-maprfs app should use new app framework to manage its lifecycle



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-446) convert eagle-hive app to use new app framework

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-446:
--

 Summary: convert eagle-hive app to use new app framework
 Key: EAGLE-446
 URL: https://issues.apache.org/jira/browse/EAGLE-446
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


eagle-hive should use new application framework



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-444) convert eagle-gc app to use new app framework

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-444:
--

 Summary: convert eagle-gc app to use new app framework
 Key: EAGLE-444
 URL: https://issues.apache.org/jira/browse/EAGLE-444
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-426) Load app web classes and app topology classes using configured lib dir

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang closed EAGLE-426.
--

> Load app web classes and app topology classes using configured lib dir
> --
>
> Key: EAGLE-426
> URL: https://issues.apache.org/jira/browse/EAGLE-426
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
> Fix For: v0.5.0
>
>
> App framework has the following issues after remove hard dependency from 
> eagle server to individual applications
> 1. load web app class through jersey package scanner by providing correct 
> context classloader
> 2. load web topology class through correct classloader
> Basically we use SPI and application.provider.dir to specify libraries and 
> load them



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EAGLE-420) HBase audit log monitoring using new app framework

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang resolved EAGLE-420.

Resolution: Fixed

> HBase audit log monitoring using new app framework
> --
>
> Key: EAGLE-420
> URL: https://issues.apache.org/jira/browse/EAGLE-420
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> This ticket is used for converting HBase audit log monitoring to use new 
> monitoring application framework
> New monitoring application supports the following 2 features
> 1) in development time,  developer can write topology and test topology 
> without knowing this topology will be managed by Eagle service API
> 2) in runtime, operator can manage topology lifecycle using API



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-420) HBase audit log monitoring using new app framework

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang closed EAGLE-420.
--

> HBase audit log monitoring using new app framework
> --
>
> Key: EAGLE-420
> URL: https://issues.apache.org/jira/browse/EAGLE-420
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> This ticket is used for converting HBase audit log monitoring to use new 
> monitoring application framework
> New monitoring application supports the following 2 features
> 1) in development time,  developer can write topology and test topology 
> without knowing this topology will be managed by Eagle service API
> 2) in runtime, operator can manage topology lifecycle using API



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EAGLE-426) Load app web classes and app topology classes using configured lib dir

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang resolved EAGLE-426.

Resolution: Fixed

> Load app web classes and app topology classes using configured lib dir
> --
>
> Key: EAGLE-426
> URL: https://issues.apache.org/jira/browse/EAGLE-426
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Minor
> Fix For: v0.5.0
>
>
> App framework has the following issues after remove hard dependency from 
> eagle server to individual applications
> 1. load web app class through jersey package scanner by providing correct 
> context classloader
> 2. load web topology class through correct classloader
> Basically we use SPI and application.provider.dir to specify libraries and 
> load them



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EAGLE-430) explore new packaging method for eagle using new app framework

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang resolved EAGLE-430.

Resolution: Fixed

> explore new packaging method for eagle using new app framework
> --
>
> Key: EAGLE-430
> URL: https://issues.apache.org/jira/browse/EAGLE-430
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> New app framework will manage application jars in central place, while 
> application jars include topology jars and web jars. 
> We need figure out Eagle 0.5 binary layout.
> The goal is with only Eagle 0.5 server we can start any topology remotely.
> /eagle-server
> /conf  (application.conf)
> /bin(add class path)
> /lib
>/eagle-server.jar
>/apps
> app1.jar
> app1-web.jar
> app2.jar
> /web
> index.html
> /js



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-430) explore new packaging method for eagle using new app framework

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang closed EAGLE-430.
--

> explore new packaging method for eagle using new app framework
> --
>
> Key: EAGLE-430
> URL: https://issues.apache.org/jira/browse/EAGLE-430
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> New app framework will manage application jars in central place, while 
> application jars include topology jars and web jars. 
> We need figure out Eagle 0.5 binary layout.
> The goal is with only Eagle 0.5 server we can start any topology remotely.
> /eagle-server
> /conf  (application.conf)
> /bin(add class path)
> /lib
>/eagle-server.jar
>/apps
> app1.jar
> app1-web.jar
> app2.jar
> /web
> index.html
> /js



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-437) create workable fat jar for starting application remotely

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang closed EAGLE-437.
--

> create workable fat jar for starting application remotely
> -
>
> Key: EAGLE-437
> URL: https://issues.apache.org/jira/browse/EAGLE-437
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> Explore ways to package fat jar for starting applications
> 1) package all topology jars together into one single fat jar. Need fix
>a. metadata.xml should be differentiated by different directory, for 
> example metadata.xml is under directory of 
> /META-INF/apps//metadata.xml
>b. SPI configuration file should be removed and 
> ApplicationProviderSPILoader should be redesign to get all providers
> 2) package fat jar on demand.
> No far jar after packaging.
> Need remember all dependent jars and write code to package fat jar on 
> demand



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EAGLE-437) create workable fat jar for starting application remotely

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang resolved EAGLE-437.

Resolution: Fixed

> create workable fat jar for starting application remotely
> -
>
> Key: EAGLE-437
> URL: https://issues.apache.org/jira/browse/EAGLE-437
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> Explore ways to package fat jar for starting applications
> 1) package all topology jars together into one single fat jar. Need fix
>a. metadata.xml should be differentiated by different directory, for 
> example metadata.xml is under directory of 
> /META-INF/apps//metadata.xml
>b. SPI configuration file should be removed and 
> ApplicationProviderSPILoader should be redesign to get all providers
> 2) package fat jar on demand.
> No far jar after packaging.
> Need remember all dependent jars and write code to package fat jar on 
> demand



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (EAGLE-428) Hbase monitoring's metadata browse API in new app framework

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang closed EAGLE-428.
--

> Hbase monitoring's metadata browse API in new app framework
> ---
>
> Key: EAGLE-428
> URL: https://issues.apache.org/jira/browse/EAGLE-428
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> Hbase monitoring's metadata browse API is used for retrieve hbase's table, 
> column etc, and check against sensitivity type.
> We should use the configuration from ApplicationEntity to manage metadata 
> query



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EAGLE-428) Hbase monitoring's metadata browse API in new app framework

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang resolved EAGLE-428.

Resolution: Fixed

> Hbase monitoring's metadata browse API in new app framework
> ---
>
> Key: EAGLE-428
> URL: https://issues.apache.org/jira/browse/EAGLE-428
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> Hbase monitoring's metadata browse API is used for retrieve hbase's table, 
> column etc, and check against sensitivity type.
> We should use the configuration from ApplicationEntity to manage metadata 
> query



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-438) Multiple Inputs for Hadoop JMX Collector Python Script

[Edward Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414305#comment-15414305
 ] 

Edward Zhang commented on EAGLE-438:


[~senthilec566] I think we already have resource manager related script?
[~petkim] are you going to have all components share the same script? but they 
are using different topic right?

> Multiple Inputs for Hadoop JMX Collector Python Script
> --
>
> Key: EAGLE-438
> URL: https://issues.apache.org/jira/browse/EAGLE-438
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Peter Kim
>Priority: Trivial
>  Labels: features
>
> It would be very useful for the hadoop jmx collector to be able to collect 
> jmx metrics for multiple components at once. So here, I wish to extend the 
> default python script that collects Hadoop JMX Metrics to support multiple 
> inputs as oppose to only one. So, with this, one can collect all jmx metrics 
> for multiple components such as namenode, datanode, resource manager, 
> hmaster, etc. all at once. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-437) create workable fat jar for starting application remotely

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-437:
--

 Summary: create workable fat jar for starting application remotely
 Key: EAGLE-437
 URL: https://issues.apache.org/jira/browse/EAGLE-437
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


Explore ways to package fat jar for starting applications
1) package all topology jars together into one single fat jar. Need fix
   a. metadata.xml should be differentiated by different directory, for example 
metadata.xml is under directory of /META-INF/apps//metadata.xml
   b. SPI configuration file should be removed and ApplicationProviderSPILoader 
should be redesign to get all providers

2) package fat jar on demand.
No far jar after packaging.
Need remember all dependent jars and write code to package fat jar on demand



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-430) explore new packaging method for eagle using new app framework

[Edward Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414218#comment-15414218
 ] 

Edward Zhang commented on EAGLE-430:


We should think about fat jar packaging process.
When we package, metadata.xml and SPI file are overridden with each other.
One solution is to build fat jar on-demand when we start an application in 
remote.
When we do package on-demand, we should know all names of dependent jars and 
try to package them together.
This is not scope for this ticket, will have another ticket for this problem

> explore new packaging method for eagle using new app framework
> --
>
> Key: EAGLE-430
> URL: https://issues.apache.org/jira/browse/EAGLE-430
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: v0.5.0
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
> Fix For: v0.5.0
>
>
> New app framework will manage application jars in central place, while 
> application jars include topology jars and web jars. 
> We need figure out Eagle 0.5 binary layout.
> The goal is with only Eagle 0.5 server we can start any topology remotely.
> /eagle-server
> /conf  (application.conf)
> /bin(add class path)
> /lib
>/eagle-server.jar
>/apps
> app1.jar
> app1-web.jar
> app2.jar
> /web
> index.html
> /js



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-432) Application status monitoring

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-432:
--

 Summary: Application status monitoring
 Key: EAGLE-432
 URL: https://issues.apache.org/jira/browse/EAGLE-432
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


App framework needs to probe application status periodically or on demand.

ApplicationEntity contains status field, and this field's value should come 
from physical storm applications.

We can start background threads to check application status or on-demand.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-431) MetadataDaoFactory should use config from eagle server

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-431:
--

 Summary: MetadataDaoFactory should use config from eagle server
 Key: EAGLE-431
 URL: https://issues.apache.org/jira/browse/EAGLE-431
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


org.apache.eagle.alert.metadata.impl.MetadataDaoFactory uses  
ConfigFactory.load() to get configuration. We should use config object from 
eagle server.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-430) explore new packaging method for eagle using new app framework

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-430:
--

 Summary: explore new packaging method for eagle using new app 
framework
 Key: EAGLE-430
 URL: https://issues.apache.org/jira/browse/EAGLE-430
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


New app framework will manage application jars in central place, while 
application jars include topology jars and web jars. 
We need figure out Eagle 0.5 binary layout.
The goal is with only Eagle 0.5 server we can start any topology remotely.

/eagle-server
/conf  (application.conf)
/bin(add class path)
/lib
   /eagle-server.jar
   /apps
app1.jar
app1-web.jar
app2.jar
/web
index.html
/js




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-429) CoordinatorTest.test_01 sometimes fail

[Edward Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412737#comment-15412737
 ] 

Edward Zhang commented on EAGLE-429:


Maybe that is because of some temporary failure of zk

2016-08-08 17:47:42,786 INFO [main] impl.GreedyPolicyScheduler[150]: work set 
calculation: []
2016-08-08 17:47:47,818 ERROR [main] curator.ConnectionState[200]: Connection 
timed out for connection string (localhost:2181) and timeout (5000) / elapsed 
(5046)
org.apache.curator.CuratorConnectionLossException: KeeperErrorCode = 
ConnectionLoss
at 
org.apache.curator.ConnectionState.checkTimeouts(ConnectionState.java:197)
at 
org.apache.curator.ConnectionState.getZooKeeper(ConnectionState.java:87)
at 
org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:115)
at 
org.apache.curator.framework.imps.CuratorFrameworkImpl.getZooKeeper(CuratorFrameworkImpl.java:477)
at 
org.apache.curator.framework.imps.ExistsBuilderImpl$2.call(ExistsBuilderImpl.java:172)
at 
org.apache.curator.framework.imps.ExistsBuilderImpl$2.call(ExistsBuilderImpl.java:161)
at org.apache.curator.RetryLoop.callWithRetry(RetryLoop.java:107)
at 
org.apache.curator.framework.imps.ExistsBuilderImpl.pathInForeground(ExistsBuilderImpl.java:158)
at 
org.apache.curator.framework.imps.ExistsBuilderImpl.forPath(ExistsBuilderImpl.java:148)
at 
org.apache.curator.framework.imps.ExistsBuilderImpl.forPath(ExistsBuilderImpl.java:36)
at 
org.apache.eagle.alert.config.ConfigBusProducer.send(ConfigBusProducer.java:39)
at 
org.apache.eagle.alert.coordinator.Coordinator.postSchedule(Coordinator.java:137)
at 
org.apache.eagle.alert.coordinator.Coordinator.schedule(Coordinator.java:115)
at 
org.apache.alert.coordinator.CoordinatorTest.test_01(CoordinatorTest.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at 
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
at 
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
at 
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
2016-08-08 17:47:47,843 INFO [main-SendThread(fe80:0:0:0:0:0:0:1%1:2181)] 
zookeeper.ClientCnxn[975]: Opening socket connection to server 
fe80:0:0:0:0:0:0:1%1/fe80:0:0:0:0:0:0:1%1:2181. Will not attempt to 
authenticate using SASL (unknown error)
2016-08-08 17:47:47,843 INFO [main-SendThread(fe80:0:0:0:0:0:0:1%1:2181)] 
zookeeper.ClientCnxn[852]: Socket

> CoordinatorTest.test_01 sometimes fail
> --
>
> Key: EAGLE-429
> URL: https://issues.apache.org/jira/browse/EAGLE-429
> Project: Eagle
>

[jira] [Created] (EAGLE-429) CoordinatorTest.test_01 sometimes fail

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-429:
--

 Summary: CoordinatorTest.test_01 sometimes fail
 Key: EAGLE-429
 URL: https://issues.apache.org/jira/browse/EAGLE-429
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Su Ralph
Priority: Minor
 Fix For: v0.5.0


This happens from time to time that test_01 use case fails.

2016-08-08 17:47:48,957 INFO [main-SendThread(localhost:2181)] 
zookeeper.ClientCnxn[852]: Socket connection established to 
localhost/127.0.0.1:2181, initiating session
2016-08-08 17:47:48,960 INFO [main-SendThread(localhost:2181)] 
zookeeper.ClientCnxn[1235]: Session establishment complete on server 
localhost/127.0.0.1:2181, sessionid = 0x156629bb321002f, negotiated timeout = 
1
2016-08-08 17:47:48,960 INFO [main-EventThread] 
state.ConnectionStateManager[228]: State change: CONNECTED
2016-08-08 17:47:49,003 ERROR [main-EventThread] listen.ListenerContainer[96]: 
Listener 
(org.apache.eagle.alert.config.ConfigBusConsumer$$Lambda$3/1403704789@1fb700ee) 
threw an exception
org.junit.ComparisonFailure: expected:<spec_version_1470703[662789]> but 
was:<spec_version_1470703[468432]>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at 
org.apache.alert.coordinator.CoordinatorTest$2.onNewConfig(CoordinatorTest.java:117)
at 
org.apache.eagle.alert.config.ConfigBusConsumer.lambda$new$0(ConfigBusConsumer.java:46)
at 
org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:294)
at 
org.apache.curator.framework.recipes.cache.NodeCache$4.apply(NodeCache.java:288)
at 
org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:92)
at 
com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:310)
at 
org.apache.curator.framework.listen.ListenerContainer.forEach(ListenerContainer.java:84)
at 
org.apache.curator.framework.recipes.cache.NodeCache.setNewData(NodeCache.java:286)
at 
org.apache.curator.framework.recipes.cache.NodeCache.processBackgroundResult(NodeCache.java:253)
at 
org.apache.curator.framework.recipes.cache.NodeCache.access$300(NodeCache.java:54)
at 
org.apache.curator.framework.recipes.cache.NodeCache$3.processResult(NodeCache.java:112)
at 
org.apache.curator.framework.imps.CuratorFrameworkImpl.sendToBackgroundCallback(CuratorFrameworkImpl.java:728)
at 
org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundOperation(CuratorFrameworkImpl.java:505)
at 
org.apache.curator.framework.imps.GetDataBuilderImpl$3.processResult(GetDataBuilderImpl.java:254)
at 
org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:561)
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498)

java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at 
org.apache.alert.coordinator.CoordinatorTest.test_01(CoordinatorTest.java:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRun

[jira] [Created] (EAGLE-428) Hbase monitoring's metadata browse API in new app framework

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-428:
--

 Summary: Hbase monitoring's metadata browse API in new app 
framework
 Key: EAGLE-428
 URL: https://issues.apache.org/jira/browse/EAGLE-428
 Project: Eagle
  Issue Type: Improvement
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


Hbase monitoring's metadata browse API is used for retrieve hbase's table, 
column etc, and check against sensitivity type.

We should use the configuration from ApplicationEntity to manage metadata query



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [Discuss] How do you think rename "develop" branch to "trunk"branch so that able to close pull request automatically?

[Edward Zhang]

Today master branch is only used for mirroring latest stable release branch
because in the first impression, people will use master to build and run.

To avoid too many breaks in master branch, Eagle community starts to use
develop branch for bleeding development work.

But that is redundant for mirroring latest stable release to master.

So if we can use master as develop branch, that should be good as anyway we
should make master to be very stable.

Vote master branch if that is common practice to use master as latest
development work.

Thanks
Edward


On Sun, Aug 7, 2016 at 11:19 PM, Henry Saputra 
wrote:

> +1 to move it to master.
>
>
> On Sun, Aug 7, 2016 at 8:09 PM, Julian Hyde  wrote:
>
> > +1 moving to “trunk” or “master”.
> >
> > Regarding the name. These days more projects use the name “master” rather
> > than “trunk”. (At least, that’s my impression. Hive, for instance, used
> > “trunk” when it was primarily svn, and switched to “master” now it’s
> based
> > on git.) But frankly either would be fine.
> >
> > Julian
> >
> >
> >
> > > On Aug 7, 2016, at 7:47 PM, Don Bosco Durai  wrote:
> > >
> > > I also feel that moving development to “trunk” will be a good thing.
> > Right now, synchronizing the final release branch to the “trunk” seems to
> > be a redundant activity. In the release notes, we can always ask the
> users
> > to use the release branch and also when we create sub releases, they
> would
> > be off the previous release branch, so it would just work naturally.
> > >
> > > Bosco
> > >
> > >
> > >
> > > On 8/7/16, 7:12 PM, "Michael Wu"  wrote:
> > >
> > >Sounds good to me, as long as it benefits the project.
> > >
> > >On Fri, Aug 5, 2016 at 3:22 PM, Hao Chen  wrote:
> > >
> > >> Currently we are faced a problem that we can't close the pull request
> > from
> > >> contributors automatically.
> > >>
> > >> When a pull request is merged in develop branch, github could not
> close
> > the
> > >> pull request automatically and committers don't have permission to
> close
> > >> the pull request manually on github page, so that we have to ask the
> > >> contributor to close the branch manually otherwise there would be lots
> > of
> > >> "OPEN" pull requests listed though most are merged.
> > >>
> > >> Learning from github service:
> > >>
> > >> "
> > >> To close this pull request, make a commit to your *master/trunk
> *branch
> > >> with (at least) the following in the commit message:
> > >>
> > >>This closes #305
> > >> "
> > >>
> > >> Commits with *"Closes #PULL-REQUEST-ID"* will only work on
> > master/trunk, in
> > >> fact *trunk* branch should be our *develo *in purpose and would be
> > better
> > >> for management.
> > >>
> > >> Any comments are appreciated.
> > >>
> > >> - Hao
> > >>
> > >
> > >
> > >
> >
> >
>

[jira] [Created] (EAGLE-410) stream tumbling window aggregate library

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-410:
--

 Summary: stream tumbling window aggregate library
 Key: EAGLE-410
 URL: https://issues.apache.org/jira/browse/EAGLE-410
 Project: Eagle
  Issue Type: Task
Affects Versions: v0.5.0
Reporter: Edward Zhang
Assignee: Edward Zhang
 Fix For: v0.5.0


Many use cases need aggregate data in streaming process, but Storm does not 
provide high level aggregation API. The most frequently used example is to 
aggregate data per minute while data is streamlined.

After investigation, we found Siddhi CEP engine is good for this task.

https://docs.wso2.com/display/CEP420/Inbuilt+Windows#InbuiltWindows-externalTimeBatchexternalTimeBatch

This ticket will develop a preview of simple aggregation API for Eagle use case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Eagle build broken in github

[Edward Zhang]

It is in Jekins.
https://builds.apache.org/job/incubator-eagle-main/94/console

Thanks
Edward

On Wed, Aug 3, 2016 at 10:42 AM, Henry Saputra <henry.sapu...@gmail.com>
wrote:

> Edward,
>
> Where do you see this error log from?
>
> - Henry
>
> On Mon, Jul 25, 2016 at 5:40 PM, Don Bosco Durai <bo...@apache.org> wrote:
>
> > I had the same issue with OpenJDK 1.8. But it works with Sun JDK 1.8.
> >
> > Bosco
> >
> >
> > On 7/25/16, 5:37 PM, "Edward Zhang" <yonzhang2...@apache.org> wrote:
> >
> > Seems it is JDK issue?
> >
> > [INFO] Compiling 16 source files to
> >
> >
> /home/jenkins/jenkins-slave/workspace/incubator-eagle-main/eagle-core/eagle-data-process/eagle-stream-process-base/target/classes
> > at 1469439473203[ERROR] error: error while loading CharSequence,
> class
> > file
> >
> '/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8/jre/lib/rt.jar(java/lang/CharSequence.class)'
> > is broken[INFO] (class java.lang.RuntimeException/bad constant pool
> > tag 18 at byte 10)[ERROR] error: error while loading
> AnnotatedElement,
> > class file
> >
> '/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8/jre/lib/rt.jar(java/lang/reflect/AnnotatedElement.class)'
> > is broken[INFO] (class java.lang.RuntimeException/bad constant pool
> > tag 18 at byte 76)[ERROR] error: error while loading ConcurrentMap,
> > class file
> >
> '/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8/jre/lib/rt.jar(java/util/concurrent/ConcurrentMap.class)'
> > is broken[INFO] (class java.lang.RuntimeException/bad constant pool
> > tag 18 at byte 61)[ERROR] three errors found
> >
> >
> >
> >
>

Re: [discuss] do we need to add build-status upon develop branch to README.md of eagle?

[Edward Zhang]

That is a nice change, very informational. Thanks.

Thanks
Edward

On Tue, Aug 2, 2016 at 7:49 PM, Michael Wu  wrote:

> Guys,
>
> I've updated README.md by adding a "Status" section that holds build
> status, latest release info. Taking this, PR #291
>  is opened towards
> develop branch, and PR #292
>  is opened towards
> master branch.
>
> Please help review them if you have the bandwidth. Thanks.
>
> Michael
>
> On Tue, Aug 2, 2016 at 2:58 PM, Michael Wu  wrote:
>
> > Agree with you, I think we do need to have a new section to clarify
> > different branch on different build status.
> >
> > On Tue, Aug 2, 2016 at 2:52 PM, Hao Chen  wrote:
> >
> >> I think at least we should add following informations on *master *branch
> >> READM
> >> as the entry page for a github project.
> >>
> >>- Latest released version, link, say Latest Released Version is
> >>[0.4.0](tags/0.4.0), [Build Passed]
> >>- Latest development version, link, status, say Latest Development
> >>Branch is [0.5.0-SNAPSHOT](branch/develop), [Build Passed]
> >>
> >> - Hao
> >>
> >> On Tue, Aug 2, 2016 at 1:30 PM, Michael Wu  wrote:
> >>
> >> > Hi guys,
> >> >
> >> > As once discussed, we may need to check build status on develop
> branch.
> >> > I've created a CI job that builds upon develop branch, triggered by
> any
> >> > check-in operation towards develop branch.
> >> >
> >> > CI job is here:
> https://builds.apache.org/job/incubator-eagle-develop/
> >> > Build Status icon url is: [![Build Status](
> >> >
> >> >
> >>
> https://builds.apache.org/buildStatus/icon?job=incubator-eagle-develop)](https://builds.apache.org/job/incubator-eagle-develop/
> >> > )
> >> > Jira ticket is: https://issues.apache.org/jira/browse/EAGLE-406
> >> >
> >> > We need to discuss what, how, where we'd like it to show up for eagle.
> >> Your
> >> > great thoughts will be appreciated.
> >> >
> >> > Michael
> >> >
> >>
> >
> >
>

Re: Podling Report Reminder - August 2016

[Edward Zhang]

Good point on "steps to graduation". That should be something we
will/should do instead of something we have done to get Eagle graduated.

@Hao/@Ralph, can you add activities in China conferences in section of
"community development"? Looks you had some activities in last quarter.


Project name:

Eagle

Project short description:

Apache Eagle (incubating) is an open source analytics solution for
identifying security and performance issues instantly on big data
platforms, e.g. Apache Hadoop, Apache Spark etc. It analyzes data
activities, Yarn application, Hadoop JMX metrics and daemon logs etc.,
provides state-of-the-art alert engine to identify security breach,
performance issues and shows insights.

Eagle has been incubating since 2015-10-26.


Three most important issues to address in the move towards graduation:

1. Eagle community is discussing graduation and use Apache maturity
assessment to measure the gap to graduation. That should be completed, see
https://cwiki.apache.org/confluence/display/EAG/Eagle+Podling+Maturity+Assessment

2. Complete one requirement from self assessment which is to *provide a
well-documented channel to report security issues, along with a documented
way of responding to them.*

3. Identify other housekeeping before graduation, for example agreement on
bylaws, PMC composition etc.


Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be

aware of?

NIL


How has the community developed since the last report?

. Presented in Apache Con, May 2016

. Presented in London Stratus + Hadoop, May 2016

. Presented in San Jose Hadoop Summit, June 2016

. Presented in China ...

Communities showed continuous interest in Apache Eagle project. Some
company tried to integrate Eagle as part of whole solution and some
contributed different use case to Eagle platform, for example MapR support,
Oozie monitoring support etc.


How has the project developed since the last report?

Technically we added more documents for user to easily use Eagle

Besides Hadoop security monitoring, we have started working on performance
monitoring design and development based on the requests from community.

As we may have multiple different use cases running on top of Eagle, a
design discussion and prototype is conducted to make sure Eagle is a
framework to host multiple use cases and user will use Eagle to manage
those use cases.

Alert engine is going to be decoupled from data processing so that alert
engine will be multi-tenant and easy to be used by multiple use cases by
incorporating well-designed metadata.


Date of last release:

2016-07-19


When were the last committers or PMC members elected?

Daniel Zhou, 2016-06-15

Michael Wu, 2016-06-17


Signed-off-by:

[ ](eagle) Owen O'Malley

[](eagle) Henry Saputra

[](eagle) Julian Hyde

[](eagle) P. Taylor Goetz

[](eagle) Amareshwari Sriramdasu

Shepherd/Mentor notes:


On Mon, Aug 1, 2016 at 11:56 AM, Henry Saputra <henry.sapu...@gmail.com>
wrote:

> +1 to mention about graduation discussion.
>
> - Henry
>
> On Mon, Aug 1, 2016 at 12:14 AM, Julian Hyde <jh...@apache.org> wrote:
>
> > I think you should mention that the community is discussing
> > graduation, and that is completed the maturity assessment.
> >
> > Maybe revise the "steps to graduation" in the light of those
> > discussions. None of those 3 came up when I asked "What is left to do
> > before Eagle graduates?". I think Eagle is close to the end game;
> > there is some housekeeping to do, and needs to agree on things like
> > bylaws (if any), PMC composition, and the text of the motion to put
> > before the Board.
> >
> > Julian
> >
> >
> > On Sun, Jul 31, 2016 at 12:13 PM, Edward Zhang <yonzhang2...@gmail.com>
> > wrote:
> > > I listed some achievement we have made for Eagle in last quarter, it
> > should
> > > not be sufficient, please review and add back
> > >
> > >
> > > Eagle
> > >
> > >
> > > 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 has been incubating since 2015-10-26.
> > >
> > >
> > > Three most important issues to address in the move towards graduation:
> > >
> > > 1. Release of Apache Eagle 0.4.0
> > >
> > > 2. Community is growing and contributors built multiple use cases on
> top
> > of
> > > Eagle framework
> > >
> > > 3. Eagle site is modified to have more useful user guide content and to
> > be
> > > more aligned with Apache Podling policies.
> > >
> > >
> > > Any issues that

Re: Podling Report Reminder - August 2016

[Edward Zhang]

I listed some achievement we have made for Eagle in last quarter, it should
not be sufficient, please review and add back


Eagle


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 has been incubating since 2015-10-26.


Three most important issues to address in the move towards graduation:

1. Release of Apache Eagle 0.4.0

2. Community is growing and contributors built multiple use cases on top of
Eagle framework

3. Eagle site is modified to have more useful user guide content and to be
more aligned with Apache Podling policies.


Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be

aware of?

NIL


How has the community developed since the last report?

. Presented in Apache Con, May 2016

. Presented in London Stratus + Hadoop, May 2016

. Presented in San Jose Hadoop Summit, June 2016

. Presented in China ...

Communities showed continuous interest in Apache Eagle project. Some
company tried to integrate Eagle as part of whole solution and some
contributed different use case to Eagle platform, for example MapR support,
Oozie monitoring support etc.


How has the project developed since the last report?

Technically we added more documents for user to easily use Eagle

Besides Hadoop security monitoring, we have started working on performance
monitoring design and development based on the requests from community.

As we may have multiple different use cases running on top of Eagle, a
design discussion and prototype is conducted to make sure Eagle is a
framework to host multiple use cases and user will use Eagle to manage
those use cases.

Alert engine is going to be decoupled from data processing so that alert
engine will be multi-tenant and easy to be used by multiple use cases by
incorporating well-designed metadata.


Date of last release:

2016-07-19


When were the last committers or PMC members elected?

Daniel Zhou, 2016-06-15

Michael Wu, 2016-06-17


Signed-off-by:

[ ](eagle) Owen O'Malley

[](eagle) Henry Saputra

[](eagle) Julian Hyde

[](eagle) P. Taylor Goetz

[](eagle) Amareshwari Sriramdasu

Shepherd/Mentor notes:



On Sun, Jul 31, 2016 at 6:15 AM,  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 17 August 2016, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, August 03).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
>
> This should be appended to the Incubator Wiki page at:
>
> http://wiki.apache.org/incubator/August2016
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: 答复: 答复: [DISCUSS] Is Eagle ready to graduate?

[Edward Zhang]

I suggest we show develop branch's build status in Eagle github
https://github.com/apache/incubator-eagle as develop branch has a lot of
code changes frequently. And master is pretty stable and we only mutate
master when a release was made according to Eagle branch convention.
https://cwiki.apache.org/confluence/display/EAG/Branching+Convention

Thanks
Edward

On Thu, Jul 28, 2016 at 5:23 PM, Tang Jijun(上海_技术部_架构部_大数据平台_唐觊隽) <
tangji...@yhd.com> wrote:

> For develop branch
>
> Best Wishes
>
> 唐觊隽
> Jr. Engineer , Architecture - Fundation, Tech Dept
> Floor 4, 295 ZUCHONGZHI RD, Zhangjiang, Shanghai (201203)
>
>
> -邮件原件-
> 发件人: Edward Zhang [mailto:yonzhang2...@apache.org]
> 发送时间: 2016年7月29日 8:21
> 收件人: dev@eagle.incubator.apache.org
> 主题: Re: 答复: [DISCUSS] Is Eagle ready to graduate?
>
> For unit testing, not sure if Apache infrastructure provides Sonar tools
> to expose unit test coverage, so community can improve from that.
>
> For the issue that code is not stable, are you saying develop branch or
> master branch?
>
> Thanks
> Edward
>
> On Thu, Jul 28, 2016 at 5:12 PM, Tang Jijun(上海_技术部_架构部_大数据平台_唐觊隽) <
> tangji...@yhd.com> wrote:
>
> > I don't think eagle is ready to graduate.
> > Because
> > 1 Code is not stable.
> > 2 Project need more unit test.
> >
> > Best Wishes
> >
> > 唐觊隽
> > Jr. Engineer , Architecture - Fundation, Tech Dept Floor 4, 295
> > ZUCHONGZHI RD, Zhangjiang, Shanghai (201203)
> >
> > -邮件原件-
> > 发件人: Edward Zhang [mailto:yonzhang2...@apache.org]
> > 发送时间: 2016年7月29日 5:19
> > 收件人: dev@eagle.incubator.apache.org
> > 主题: Re: [DISCUSS] Is Eagle ready to graduate?
> >
> > Yes, we should discuss that on the list, and will go through maturity
> > model first soon.
> >
> > Thanks
> > Edward
> >
> > On Thu, Jul 28, 2016 at 2:15 PM, Julian Hyde <jh...@apache.org> wrote:
> >
> > >
> > > > … also want to discuss this with other contributors.
> > >
> > > Why not discuss with them on this list?
> > >
> > > Julian
> > >
> > >
> >
>

Re: 答复: [DISCUSS] Is Eagle ready to graduate?

[Edward Zhang]

For unit testing, not sure if Apache infrastructure provides Sonar tools to
expose unit test coverage, so community can improve from that.

For the issue that code is not stable, are you saying develop branch or
master branch?

Thanks
Edward

On Thu, Jul 28, 2016 at 5:12 PM, Tang Jijun(上海_技术部_架构部_大数据平台_唐觊隽) <
tangji...@yhd.com> wrote:

> I don't think eagle is ready to graduate.
> Because
> 1 Code is not stable.
> 2 Project need more unit test.
>
> Best Wishes
>
> 唐觊隽
> Jr. Engineer , Architecture - Fundation, Tech Dept
> Floor 4, 295 ZUCHONGZHI RD, Zhangjiang, Shanghai (201203)
>
> -邮件原件-
> 发件人: Edward Zhang [mailto:yonzhang2...@apache.org]
> 发送时间: 2016年7月29日 5:19
> 收件人: dev@eagle.incubator.apache.org
> 主题: Re: [DISCUSS] Is Eagle ready to graduate?
>
> Yes, we should discuss that on the list, and will go through maturity
> model first soon.
>
> Thanks
> Edward
>
> On Thu, Jul 28, 2016 at 2:15 PM, Julian Hyde <jh...@apache.org> wrote:
>
> >
> > > … also want to discuss this with other contributors.
> >
> > Why not discuss with them on this list?
> >
> > Julian
> >
> >
>

Eagle build broken in github

[Edward Zhang]

Seems it is JDK issue?

[INFO] Compiling 16 source files to
/home/jenkins/jenkins-slave/workspace/incubator-eagle-main/eagle-core/eagle-data-process/eagle-stream-process-base/target/classes
at 1469439473203[ERROR] error: error while loading CharSequence, class
file 
'/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8/jre/lib/rt.jar(java/lang/CharSequence.class)'
is broken[INFO] (class java.lang.RuntimeException/bad constant pool
tag 18 at byte 10)[ERROR] error: error while loading AnnotatedElement,
class file 
'/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8/jre/lib/rt.jar(java/lang/reflect/AnnotatedElement.class)'
is broken[INFO] (class java.lang.RuntimeException/bad constant pool
tag 18 at byte 76)[ERROR] error: error while loading ConcurrentMap,
class file 
'/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8/jre/lib/rt.jar(java/util/concurrent/ConcurrentMap.class)'
is broken[INFO] (class java.lang.RuntimeException/bad constant pool
tag 18 at byte 61)[ERROR] three errors found

Re: Build failure in branch "develop"

[Edward Zhang]

Thanks. Are you saying that you will build docker file for community to use?
As far as I know current docker image is not fully tested and sometimes may
not be stable as it contains HBase which is often down unexpectedly.

Thanks
Edward

On Mon, Jul 25, 2016 at 12:21 PM, Don Bosco Durai  wrote:

> Thanks. This worked. Additionally, I had to install node.js. Let me see if
> I can make the Dockerfile available in some form for others to use it (if
> needed).
>
> Bosco
>
>
> On 7/25/16, 1:28 AM, "Michael Wu"  wrote:
>
> This issue has been fixed in develop branch.
>
> Michael
>
> On Mon, Jul 25, 2016 at 3:07 PM, Zhao, Qingwen 
> wrote:
>
> > OK.
> >
> > Seems there are some problems in this new branch, which is in the
> > development and unstable right now. Sorry about that.
> >
> > If you are trying Eagle, please use the newly released version
> branch 0.4.
> > If you want to contribute new features, develop branch is ok.
> >
> > For this issue, we are fixing :)
> >
> > Regards,
> > Qingwen Zhao | Apache Eagle
> > Desk: 20998167 | Cell: +86 18818215025
> >
> >
> >
> >
> >
> >
> > On 7/25/16, 2:31 PM, "Don Bosco Durai"  wrote:
> >
> > >Yes, I am running mvn from the root folder of the project.
> > >
> > >Bosco
> > >
> > >
> > >On 7/24/16, 11:29 PM, "Michael Wu"  wrote:
> > >
> > >Just to make sure, are you executing from the project root
> folder? If
> > >you're executing the mvn command from within a sub folder, it
> may
> > >require
> > >that you've installed depended artifacts to your local maven
> > >repository in
> > >previous builds.
> > >
> > >Michael
> > >
> > >On Mon, Jul 25, 2016 at 1:46 PM, Don Bosco Durai <
> bo...@apache.org>
> > >wrote:
> > >
> > >> Still same issue on my mac and fresh docker image with Sun
> JDK 1.8
> > >>
> > >> [root@500777b9b778 incubator-eagle]# git branch
> > >> * develop
> > >>
> > >> [root@500777b9b778 incubator-eagle]# $JAVA_HOME/bin/java
> -version
> > >> java version "1.8.0_101"
> > >> Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
> > >> Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed
> mode)
> > >>
> > >> [root@500777b9b778 incubator-eagle]# mvn clean
> > >> [INFO] Scanning for projects...
> > >> [ERROR] [ERROR] Some problems were encountered while
> processing the
> > >POMs:
> > >> [WARNING] 'parent.relativePath' of POM
> > >> org.apache.eagle:eagle-common:[unknown-version]
> > >> (/work/incubator-eagle/eagle-core/eagle-common/pom.xml)
> points at
> > >> org.apache.eagle:eagle-core instead of
> > >org.apache.eagle:eagle-query-parent,
> > >> please verify your project structure @ line 22, column 10
> > >> [FATAL] Non-resolvable parent POM for
> > >> org.apache.eagle:eagle-common:[unknown-version]: Could not
> find
> > >artifact
> > >>
> org.apache.eagle:eagle-query-parent:pom:0.5.0-incubating-SNAPSHOT
> > >and
> > >> 'parent.relativePath' points at wrong local POM @ line 22,
> column 10
> > >> [WARNING]
> > >'dependencies.dependency.(groupId:artifactId:type:classifier)'
> > >> must be unique: joda-time:joda-time:jar -> duplicate
> declaration of
> > >version
> > >> (?) @ org.apache.eagle:alert-engine:[unknown-version],
> > >>
> >
> >/work/incubator-eagle/eagle-core/eagle-alert-parent/eagle-alert/alert-engi
> > >ne/pom.xml,
> > >> line 115, column 15
> > >> [WARNING]
> > >'dependencies.dependency.(groupId:artifactId:type:classifier)'
> > >> must be unique: org.apache.kafka:kafka-clients:jar ->
> duplicate
> > >declaration
> > >> of version (?) @
> org.apache.eagle:alert-engine:[unknown-version],
> > >>
> >
> >/work/incubator-eagle/eagle-core/eagle-alert-parent/eagle-alert/alert-engi
> > >ne/pom.xml,
> > >> line 127, column 15
> > >> [WARNING]
> > >'dependencies.dependency.(groupId:artifactId:type:classifier)'
> > >> must be unique: org.apache.eagle:eagle-metadata-base:jar ->
> version
> > >> ${project.version} vs 0.5.0-incubating-SNAPSHOT @
> > >> org.apache.eagle:eagle-app-base:[unknown-version],
> > >>
> /work/incubator-eagle/eagle-core/eagle-app/eagle-app-base/pom.xml,
> > >line 95,
> > >> column 21
> > >> [WARNING]
> > >'dependencies.dependency.(groupId:artifactId:type:classifier)'
> > >> must be unique: junit:junit:jar -> duplicate declaration of
> version
> > >(?) @
> > >> org.apache.eagle:eagle-app-base:[unknown-version],
> > >>
> 

Re: Apache Ranger integration for Audit Logs...

[Edward Zhang]

Thanks Bosco.

For new features, please do under develop branch where Eagle 0.5 is
targeted.

And in develop branch, we have different programming paradigm than before.
Alert engine is separated into a general storm topology and the
applications which prepare data is separate storm topologies so that output
from application will be input to alert engine.

So you can write application based on whatever framework you like, storm,
spark etc. But in Eagle 0.5 we will only support storm based application,
where Eagle provides a framework to manage application lifecycle.

But at beginning, probably you just need write plain storm topology to
process data from Apache Ranger.

Thanks
Edward

On Fri, Jul 15, 2016 at 2:00 PM, Don Bosco Durai <bo...@apache.org> wrote:

> I have some spare time and was planning to work on this. If no one
> currently looking into this JIRA, then can you assign it to me?
>
> https://issues.apache.org/jira/browse/EAGLE-59
>
>
> Thanks
>
> Bosco
>
>
> On 11/29/15, 8:43 PM, "Don Bosco Durai" <bo...@apache.org> wrote:
>
> Edward
>
> Thanks. I will look into HdfsAuditLogProcessorMain class.
>
> I will upload the sample files in the JIRA.
>
>
>
> Thanks
>
> Bosco
>
>
> On 11/29/15, 7:56 PM, "Zhang, Edward (GDI Hadoop)" <yonzh...@ebay.com>
> wrote:
>
> >One more thing, Bosco, could you please copy some sample hdfs audit
> log,
> >hbase log and hive log to here?
> >
> >I realize with Ranger data source, we probably still need some minor
> code
> >development as follows
> >1. Substitute existing eagle data source(raw hdfs audit log) with
> Ranger
> >data source, for example, in HdfsAuditLogProcessorMain, modify the
> code to
> >use different log deserializer
> >2. Ensure output of Ranger log deserializer is compatible to existing
> >eagle data source.
> >
> >With the above code change, we can automatically get all capabilities
> like
> >sensitivity data join, user hadoop command reassembly, hive query
> >semantics parsing etc.
> >
> >Thanks
> >Edward Zhang
> >
> >On 11/29/15, 18:52, "Zhang, Edward (GDI Hadoop)" <yonzh...@ebay.com>
> wrote:
> >
> >>Hi Bosco,
> >>
> >>Thanks for creating this ticket. It is very helpful if EAGLE can use
> >>Ranger as data source and automatically get monitoring capability in
> 9
> >>Hadoop components.
> >>
> >>If a datasource is not from Kafka, and needs a lot of
> pre-processing, it
> >>is not trivial to integrate that data source.
> >>
> >>Ranger¹s data source should be uniform in syntax and the integration
> >>should be straightforward, if we have a uniform deserializer.
> >>
> >>I think we can document the steps of integrating a new datasource.
> >>
> >>Thanks
> >>Edward Zhang
> >>
> >>On 11/29/15, 12:00, "Don Bosco Durai" <bo...@apache.org> wrote:
> >>
> >>>Hi Eagle team
> >>>
> >>>I am excited to see all the activities on this project. I have
> created a
> >>>JIRA (https://issues.apache.org/jira/browse/EAGLE-59) to track the
> >>>integration with Apache Ranger.
> >>>
> >>>One way to integrate is for Ranger to send the audit logs in the
> same way
> >>>as native log format to Kafka. However, Ranger already is doing the
> >>>normalization of the audit format for all the components. So
> >>>reconstructing might not be a good way to go.
> >>>
> >>>I am still getting familiar with the internals of Apache Eagle, but
> if
> >>>someone can help me or document how a 3rd party source can be
> integrated
> >>>with Apache Eagle, then it will be great. Also, what is the change
> >>>required on the analytics side to support new data sources? E.g. If
> we
> >>>integrate with Ranger Audit Logs, we would get audit logs from
> around 9
> >>>components right away. How can we use it?
> >>>
> >>>If you are okay, I am willing to work on this JIRA.
> >>>
> >>>Thanks
> >>>
> >>>Bosco
> >>>
> >>>
> >>
> >
>
>
>
>
>

[jira] [Updated] (EAGLE-59) Add support for Audit Logs from Apache Ranger

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang updated EAGLE-59:
--
Assignee: Don Bosco Durai

> Add support for Audit Logs from Apache Ranger
> -
>
> Key: EAGLE-59
> URL: https://issues.apache.org/jira/browse/EAGLE-59
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Don Bosco Durai
>Assignee: Don Bosco Durai
>
> Apache Ranger centralizes the audit logs for most of the Hadoop components. 
> The logs are also standardized in common format. It might be good if we can 
> ensure the audit format is supported by Apache Eagle.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Why?

[Edward Zhang]

I feel the same. Eagle project today needs more discussion in Eagle dev DL.
I do see many discussions and code reviews within individual emails instead
of going through Eagle dev DL. And some users also ask questions to
individual email directly :-)

Could I suggest Eagle committers and community please discuss important
plans and issues in Eagle dev DL to have public record for people to review
at any time?

Thanks
Edward


On Fri, Jul 15, 2016 at 10:07 AM, Julian Hyde  wrote:

> I am seeing a few JIRA cases which are basically just check-in comments.
> They are created just before the commit, they explain what was done in the
> commit, do not explain why, do not link to any previous or future work.
>
> An example of this is EAGLE-378. It arrives a couple of days after I had a
> conversation with Michael [1] about cleaning up included jars, yet it seems
> to be doing exactly the opposite.
>
> Is the Eagle project operating commit-then-review or review-then-commit?
> It seems to be operating commit-then-review, but if so, there’s not enough
> information in the public record for people to review what is happening.
>
> As my math teacher used to say: don’t just write down the answer, you need
> to show your working!
>
> Julian
>
> [1] https://issues.apache.org/jira/browse/EAGLE-378 <
> https://issues.apache.org/jira/browse/EAGLE-378>
>
> [2] https://issues.apache.org/jira/browse/EAGLE-377 <
> https://issues.apache.org/jira/browse/EAGLE-377>

[jira] [Commented] (EAGLE-251) Run eagle on flink/samza

[Edward Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378425#comment-15378425
 ] 

Edward Zhang commented on EAGLE-251:


[~milap.wadhwa] looks this jira ticket is pretty long and probably we need 
revisit the request for running eagle on flink/samza.

In current development branch, Eagle now evolves to have applications and alert 
engine separated. And application can be on top of apache storm, spark etc. and 
alert engine is designed to run on top of apache storm.

So when we look at this ticket, we need make sure what we are going to do, is 
that application's runtime or alert engine runtime.

> Run eagle on flink/samza
> 
>
> Key: EAGLE-251
> URL: https://issues.apache.org/jira/browse/EAGLE-251
> Project: Eagle
>  Issue Type: New Feature
>Affects Versions: v0.3.0
>Reporter: Su Ralph
>Priority: Minor
>  Labels: new
>
> Eagle is running on storm. One might want to do some interesting port to 
> other stream framework like flink/samza.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release: Apache Eagle 0.4.0-incubating (Release Candidate 3)

[Edward Zhang]

+1 (binding)

* Downloaded & built successfully with Hotspot JDK1.7 on OSX
* Signature checked, md5, sha1 verified (
https://httpd.apache.org/dev/verification.html)
* Apache rat:check passed (mvn apache-rat:check)

* no jar files included.


Thanks

Edward

On Mon, Jul 11, 2016 at 10:34 PM, Hao Chen  wrote:

> +1 (binding)
>
> Invalid JAR files issue reported in previous apache-eagle-0.4.0-incubating
> rc2 have been resolved.
>
> * Downloaded & Built successfully on MacOSX 10.10.5 with Java
> HotSpot 1.7.0_75.
> * Verified signature
> * Ran rat:check and passed
>
> - Hao
>
> On Tue, Jul 12, 2016 at 6:39 AM, Lu, Huizhi  wrote:
>
> > +1 (non-binding)
> >
> > * Downloaded & built successfully on HotSpot 64-bit JDK 1.7 OS X
> > * Signature checked, md5, sha1 verified
> > * Apache rat:check passed (mvn apache-rat:check)
> > * Release matches tag.
> >
> >
> > -Huizhi
> >
> > > On Jul 11, 2016, at 2:40 AM, Michael Wu  wrote:
> > >
> > > Hi all,
> > >
> > > This is a release vote for Apache Eagle, version 0.4.0-incubating,
> > release
> > > candidate 3.
> > >
> > > Highlighted changes in this release are as the following:
> > >  * JBDC Metadata Storage Extension
> > >  * Topology management in remote mode including start/stop/status
> > > operations
> > >  * Auditlogparser for MapR's audit log
> > >  * Oozie auditlog integration for Oozie security monitoring
> > >  * Add applicaiton "maprFSAuditLog"
> > >  * Refactor bin/eagle-sandbox-starter.sh to make it easier to use
> > >
> > > Thanks to everyone who has contributed to this release.
> > >
> > > Here's the release note:
> > > *
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f=CHANGELOG.txt;hb=refs/heads/branch-0.4.0
> > > <
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-eagle.git;a=blob_plain;f=CHANGELOG.txt;hb=refs/heads/branch-0.4.0
> > >*
> > >
> > > The artifacts to be voted on are located at:
> > > *
> >
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.4.0-incubating-rc3/
> > > <
> >
> https://dist.apache.org/repos/dist/dev/incubator/eagle/0.4.0-incubating-rc3/
> > >*
> > >
> > > The commit to be voted upon:
> > > *
> >
> https://github.com/apache/incubator-eagle/commit/eac0f27958f2ed8c6842938dad0a995a87fd0715
> > > <
> >
> https://github.com/apache/incubator-eagle/commit/eac0f27958f2ed8c6842938dad0a995a87fd0715
> > >*
> > >
> > > Release tag is:
> > > *
> >
> https://github.com/apache/incubator-eagle/releases/tag/v0.4.0-incubating-rc3
> > > <
> >
> https://github.com/apache/incubator-eagle/releases/tag/v0.4.0-incubating-rc3
> > >*
> > >
> > > Release artifacts are signed with the following key:
> > > http://people.apache.org/keys/committer/mw.asc
> > >
> > > The hashes of the artifacts are as follows:
> > > apache-eagle-0.4.0-incubating-src-rc3.tar.gz.md5:
> > > 5781048a2fc2b3dcfe5e30a09be86d25
> > > apache-eagle-0.4.0-incubating-src-rc3.tar.gz.sha1:
> > > a98b565604b3921a4ea5c53e30479427b227e1e2
> > >
> > > Please vote on releasing this package as: Apache Eagle
> 0.4.0-incubating.
> > >
> > > The vote is open for the next 72 hours and passes if a majority of at
> > least
> > > three +1 PPMC votes are cast.
> > >
> > > [ ] +1 Release this Apache Eagle 0.4.0-incubating Release Candidate 3.
> > >
> > > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > >
> > > [ ] -1 Do not release this package because...
> > >
> > >
> > > Thanks.
> > > Michael
> >
> >
>

[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch

[Edward Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15374047#comment-15374047
 ] 

Edward Zhang commented on EAGLE-371:


We tried with Eagle branch 
https://github.com/apache/incubator-eagle/tree/document long time ago, and will 
officially move all documents to this branch in Eagle 0.5. Use 
https://issues.apache.org/jira/browse/EAGLE-373 to track

> remove eagle-docs from develop branch
> -
>
> Key: EAGLE-371
> URL: https://issues.apache.org/jira/browse/EAGLE-371
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.5
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Trivial
> Fix For: 0.5
>
>
> eagle-docs will be maintained in 
> https://github.com/eaglemonitoring/eaglemonitoring.github.io, so we don't 
> need maintain duplicated documentation



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-373) Move Eagle document to Eagle source code control

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-373:
--

 Summary: Move Eagle document to Eagle source code control
 Key: EAGLE-373
 URL: https://issues.apache.org/jira/browse/EAGLE-373
 Project: Eagle
  Issue Type: Improvement
Affects Versions: 0.5
Reporter: Edward Zhang
Assignee: Edward Zhang
Priority: Minor
 Fix For: 0.5


Today Eagle's document is maintained in 
https://github.com/eaglemonitoring/eaglemonitoring.github.io, it does not 
conform to Apache policy. We should move this into Apache git source control. 
The approach is to create a branch called document in 
https://github.com/apache/incubator-eagle/tree/document and put document into 
it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch

[Edward Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372026#comment-15372026
 ] 

Edward Zhang commented on EAGLE-371:


[~julianhyde]maybe your concern is we should maintain eagle documents in apache 
git. If that is the concern, today eagle does not maintain document in apache 
git. We may need do that in eagle 0.5 when we have document maintained in one 
branch of apache git

> remove eagle-docs from develop branch
> -
>
> Key: EAGLE-371
> URL: https://issues.apache.org/jira/browse/EAGLE-371
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.5
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Trivial
> Fix For: 0.5
>
>
> eagle-docs will be maintained in 
> https://github.com/eaglemonitoring/eaglemonitoring.github.io, so we don't 
> need maintain duplicated documentation



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-371) remove eagle-docs from develop branch

[Edward Zhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15372017#comment-15372017
 ] 

Edward Zhang commented on EAGLE-371:


[~julianhyde] we have eagle document well maintained in 
https://github.com/eaglemonitoring/eaglemonitoring.github.io, and the URL 
http://eagle.incubator.apache.org/docs still remains the same.

This is a temporary solution, and we want to move all documents into one branch 
of eagle github but not embedded together with source code.

We look at many projects in terms of document lifecycle management, for Eagle 
we want to use branch to manage eagle doc. And document differences between 
different eagle releases are maintained in eagle eagle release if we want to 
keep old document.



> remove eagle-docs from develop branch
> -
>
> Key: EAGLE-371
> URL: https://issues.apache.org/jira/browse/EAGLE-371
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.5
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Trivial
> Fix For: 0.5
>
>
> eagle-docs will be maintained in 
> https://github.com/eaglemonitoring/eaglemonitoring.github.io, so we don't 
> need maintain duplicated documentation



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EAGLE-371) remove eagle-docs from develop branch

[Edward Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Zhang resolved EAGLE-371.

Resolution: Fixed

merged

> remove eagle-docs from develop branch
> -
>
> Key: EAGLE-371
> URL: https://issues.apache.org/jira/browse/EAGLE-371
> Project: Eagle
>  Issue Type: Improvement
>Affects Versions: 0.5
>    Reporter: Edward Zhang
>Assignee: Edward Zhang
>Priority: Trivial
> Fix For: 0.5
>
>
> eagle-docs will be maintained in 
> https://github.com/eaglemonitoring/eaglemonitoring.github.io, so we don't 
> need maintain duplicated documentation



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)