ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Ignite Web Control Center Architecture
Date Fri, 03 Jul 2015 14:47:43 GMT
On Fri, Jul 3, 2015 at 3:47 AM, Andrey Novikov <anovikov@gridgain.com>
wrote:

> How about to use websockets as transport protocol?
>
> On agent side we can use https://github.com/TooTallNate/Java-WebSocket <
> https://github.com/TooTallNate/Java-WebSocket> (MIT)
> On web server side https://github.com/websockets/ws <
> https://github.com/websockets/ws> (MIT)
>

I think it is worth a try.


>
> --
> Andrey Novikov
> GridGain Systems
> www.gridgain.com <http://www.gridgain.com/>
> > On 02 Jul 2015, at 23:35, Dmitriy Setrakyan <dsetrakyan@apache.org>
> wrote:
> >
> > On Thu, Jul 2, 2015 at 8:08 AM, Sergey Evdokimov <
> sevdokimov@gridgain.com>
> > wrote:
> >
> >> Yes, Web Agent can open connection to Control Center at any time. Web
> Agent
> >> is started up as much as started up cluster, but user looks to Control
> >> Center infrequently. Web Agent have to keep connection always opened or
> we
> >> need a way to notify Web Agent about new web-session on Web Control
> Center.
> >>
> >
> > Sergey, the agent should automatically reconnect whenever a connection is
> > lost. For example, it can send a keep-alive ping every 2 seconds back to
> > the web control center.
> >
> > If you having doubts in the approach, please ping me on Skype so we could
> > flush out the details.
> >
> >
> >>
> >> On Thu, Jul 2, 2015 at 5:53 PM, Dmitriy Setrakyan <
> dsetrakyan@apache.org>
> >> wrote:
> >>
> >>> On Thu, Jul 2, 2015 at 7:29 AM, Sergey Evdokimov <
> >> sevdokimov@gridgain.com>
> >>> wrote:
> >>>
> >>>> Web Agent can be shipped as Ignite plugin and start inside the cluster
> >> as
> >>>> service to avoid unnecessary configuration.
> >>>>
> >>>> How Web Agent will detect that Web Control Center need a data? Web
> >>> Control
> >>>> Center cannot open connection to cluster, because cluster may be in
> >> local
> >>>> network without static IP. Do you mean that Web Agent will keep opened
> >>>> connection to Web Control Center always?
> >>>>
> >>>
> >>> However, the Ignite web agent should be able to open a connection to
> the
> >>> web control center, no?
> >>>
> >>>
> >>>>
> >>>> On Thu, Jul 2, 2015 at 5:12 PM, Alexey Kuznetsov <
> >>> akuznetsov@gridgain.com>
> >>>> wrote:
> >>>>
> >>>>> Igniters,
> >>>>>
> >>>>> I'm working on Web Control Center and first release is near.
> >>>>> In first release we will provide UI for cluster and caches
> >>> configuration.
> >>>>>
> >>>>> In next releases we will provide Monitoring, SQL and Schema Import
> >>>> Utility.
> >>>>> But those advanced features require access to Ignite cluster (for
> >>>>> Monitoring and SQL)
> >>>>> and access to DB server for Schema Import.
> >>>>>
> >>>>> After some thoughts we decided to create a so-called "web agent"
it
> >>> will
> >>>> be
> >>>>> started "near" cluster and DB will connect to it and send all needed
> >>> info
> >>>>> to Web Control Center.
> >>>>>
> >>>>> Any ideas, thoughts and suggestions are very welcome.
> >>>>>
> >>>>> Thanks.
> >>>>>
> >>>>> --
> >>>>> Alexey Kuznetsov
> >>>>> GridGain Systems
> >>>>> www.gridgain.com
> >>>>>
> >>>>
> >>>
> >>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message