Re: [Proposal] Dynamical Topology Manager

2016-01-20 Thread Zhang, Edward (GDI Hadoop)
Thanks. We will prepare the features we need soon thanks Edward On 1/20/16, 15:57, "P. Taylor Goetz" wrote: >I'm happy to help facilitate/coordinate wherever I can. > >The Storm community has been very busy prepping our 1.0 release (which >includes a ton of new features and may benefit Eagle),

Re: [Proposal] Dynamical Topology Manager

2016-01-20 Thread P. Taylor Goetz
I'm happy to help facilitate/coordinate wherever I can. The Storm community has been very busy prepping our 1.0 release (which includes a ton of new features and may benefit Eagle), but the dust should settle soon. Please let me know if there's anything I can do to help. -Taylor > On Jan 19, 2

Re: [Proposal] Dynamical Topology Manager

2016-01-18 Thread Henry Saputra
I think we could start with a list of what Apache Eagle needed from Topology lifecycle management and see if we do cross-post to both dev@ list of Eagle and Storm to see if enough interest from Storm to work on it or accept contributions from Eagle. - Henry On Fri, Jan 15, 2016 at 4:06 PM, Zhang,

Re: [Proposal] Dynamical Topology Manager

2016-01-15 Thread Zhang, Edward (GDI Hadoop)
I had a short discussion with Henry about this. We probably need discuss a more graceful way to tackle the problem of whether eagle does this or storm does this. Today we know that Storm also provides topology view/statistics features but does not have topology lifecycle management UI. But can we a

Re: [Proposal] Dynamical Topology Manager

2016-01-11 Thread Edward Zhang
Thanks for the valuable comments, you are right in the high-level observations :-) (I participated some offline discussion on this proposal) I think this proposal is based on the requirements that Eagle not only monitors security events from hadoop but also monitors security events from other data

Re: [Proposal] Dynamical Topology Manager

2016-01-11 Thread Julian Hyde
Can I make a high-level observation? (And, although I’m a mentor of this project, I’m not speaking as a mentor, just someone who has built various database and streaming systems over the years.) I’ve noticed that Eagle is taking on several problems that — architecturally speaking — should be pa

[Proposal] Dynamical Topology Manager

2016-01-11 Thread Hao Chen
Currently eagle is requiring user to manually manage topologies completely independent of eagle components, which is not very smooth for the user and management experience end-to-end from on-boarding datasource, starting topologies, defining policy and also monitoring policy and execution status,