Podling Report Reminder - February 2017

[johndament]

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, 15 February 2017, 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, February 01).

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:

https://wiki.apache.org/incubator/February2017

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: third party service to poll Fluo for absence of event

[Keith Turner]

On Tue, Jan 31, 2017 at 3:50 PM, Meier, Caleb  wrote:
> Hello,
>
> I’m looking into using Fluo to develop an event based notification system 
> that incrementally generates events of increasing complexity.  The one issue 
> that I’m running into is how to handle the non-event event.  That is, Fluo 
> (as I understand it) is not well-suited to handle the following request: 
> “generate a notification if no events of a given type have occurred within 
> the last 24 hours”.  This is because it is a push based notification 
> framework that only generates notifications when things actually happen.  So 
> the question is, has anyone looked into developing a service for generating 
> notifications at regular intervals (even if something doesn’t happen) that 
> works with Fluo?  I’m toying with the idea of creating some sort of Twill 
> application that tells Fluo to wake up at regular intervals to generate a 
> notification about the set of events falling within the given time window. 
> Before doing this I just wanted to make sure that something like this does 
> not already exist, and I also want to get a sense of how bad an idea it is to 
> delegate some of the logic of this periodic notification service to Fluo.   
> Would it be better to separate out the temporal portion of my notification 
> request to be processed entirely outside of Fluo to avoid transactional 
> overhead?
>

At one point in time I was thinking of delayed notifications, but I
can't remember what my specific use case was. I am not sure if this is
good idea or not.

How many event types are there in your use case?  Just curious about
the order of magnitude.  Like is it ~100 event types and millions of
events?

Just to make sure I understand your use case, are you interested in
finding which event types were not updated in the last 24hrs?  Or are
you interested in finding which events were not updated in the last
24hrs?  If none of these, would you be able to describe the use case
you want with an example?

> Caleb A. Meier, Ph.D.
> Software Engineer II ♦ Analyst
> Parsons Corporation
> 1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
> Office:  (703)797-3066
> caleb.me...@parsons.com ♦ 
> www.parsons.com
>

Re: third party service to poll Fluo for absence of event

[Christopher]

You could write an observer which rolls up timestamps from all the events
you are concerned about, and puts the most recent event timestamp into a
centralized place, which you could poll. If there is no ingest of these
events, then the last timestamp in this central place will exceed some
threshold and the poller could detect that and trigger additional actions.

On Tue, Jan 31, 2017 at 3:51 PM Meier, Caleb 
wrote:

> Hello,
>
> I’m looking into using Fluo to develop an event based notification system
> that incrementally generates events of increasing complexity.  The one
> issue that I’m running into is how to handle the non-event event.  That is,
> Fluo (as I understand it) is not well-suited to handle the following
> request: “generate a notification if no events of a given type have
> occurred within the last 24 hours”.  This is because it is a push based
> notification framework that only generates notifications when things
> actually happen.  So the question is, has anyone looked into developing a
> service for generating notifications at regular intervals (even if
> something doesn’t happen) that works with Fluo?  I’m toying with the idea
> of creating some sort of Twill application that tells Fluo to wake up at
> regular intervals to generate a notification about the set of events
> falling within the given time window. Before doing this I just wanted to
> make sure that something like this does not already exist, and I also want
> to get a sense of how bad an idea it is to delegate some of the logic of
> this periodic notification service to Fluo.   Would it be better to
> separate out the temporal portion of my notification request to be
> processed entirely outside of Fluo to avoid transactional overhead?
>
> Caleb A. Meier, Ph.D.
> Software Engineer II ♦ Analyst
> Parsons Corporation
> 1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
> Office:  (703)797-3066 <(703)%20797-3066>
> caleb.me...@parsons.com ♦ www.parsons.com<
> https://webportal.parsons.com/,DanaInfo=www.parsons.com+>
>
> --
Christopher

third party service to poll Fluo for absence of event

[Meier, Caleb]

Hello,

I’m looking into using Fluo to develop an event based notification system that 
incrementally generates events of increasing complexity.  The one issue that 
I’m running into is how to handle the non-event event.  That is, Fluo (as I 
understand it) is not well-suited to handle the following request: “generate a 
notification if no events of a given type have occurred within the last 24 
hours”.  This is because it is a push based notification framework that only 
generates notifications when things actually happen.  So the question is, has 
anyone looked into developing a service for generating notifications at regular 
intervals (even if something doesn’t happen) that works with Fluo?  I’m toying 
with the idea of creating some sort of Twill application that tells Fluo to 
wake up at regular intervals to generate a notification about the set of events 
falling within the given time window. Before doing this I just wanted to make 
sure that something like this does not already exist, and I also want to get a 
sense of how bad an idea it is to delegate some of the logic of this periodic 
notification service to Fluo.   Would it be better to separate out the temporal 
portion of my notification request to be processed entirely outside of Fluo to 
avoid transactional overhead?

Caleb A. Meier, Ph.D.
Software Engineer II ♦ Analyst
Parsons Corporation
1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
Office:  (703)797-3066
caleb.me...@parsons.com ♦ 
www.parsons.com

Podling Report Reminder - February 2017

[johndament]

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, 15 February 2017, 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, February 01).

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:

https://wiki.apache.org/incubator/February2017

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