Hi Eagle community and mentors,
Please review the following Eagle podling status report for last 3 months, and if that is ok, we will put it to incubator status report page for mentors to sign off. 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 10:06 PM, Hao Chen <[email protected]> wrote: > *Community Development at Beijing/Shanghai/San Jose.* > > 1) 2016/4/21-4/23 QCon by Chen, Hao (Beijing) > http://2016.qconbeijing.com/speakers/202018 > > 2) 2016/5/12-5/14 DTCC2016 by Su, Liangfei (Beijing) > http://dtcc.it168.com/ > > 3) 2016/5/28 JavaCon 2016 by Chen, Hao (Shanghai) > http://javacon.topgeek.org/ > > 4) 2016/6/28-6/30 Hadoop Summit by Chen, Hao & Su, Liangfei (San Jose) > http://2016.hadoopsummit.org/san-jose/ > > 5) 2016/07/8 Data Asset Management Summit by Chen, Hao (Shanghai) > http://www.dams.org.cn/ > > - Hao > > On Tue, Aug 2, 2016 at 4:34 AM, Edward Zhang <[email protected]> > wrote: > > > 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 <[email protected]> > > wrote: > > > > > +1 to mention about graduation discussion. > > > > > > - Henry > > > > > > On Mon, Aug 1, 2016 at 12:14 AM, Julian Hyde <[email protected]> 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 < > [email protected] > > > > > > > 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 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, <[email protected]> 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 > > > > >> > > > > > > > > > >
