[infinispan-dev] Management interface
Heiko W. Rupp
hwr at redhat.com
Wed May 6 09:06:08 EDT 2009
Manik Surtani schrieb:
> would see information scoped on a few things:
> + app-1-cluster
> + data-cache
> + node1
> + node2
> + node3
> + some-other-cache
> + node1
> + node2
> + node3
> + app-2-cluster
Yeah, that tree with cluster->cache makes sense.
If the list of nodes is relatively static, it makes sense too to expose
them as child resources.
If they are relatively dynamic, it will be better to have them just
exposed as count metric and
then have operations on cache level to obtain the list of nodes and
perhaps some code to
manipulate them.
> So it makes sense that the console talks to agents, and agents talk to
> the process being run locally, which is fine. But how does the console
> find agents? :-) Or is the console's location statically configured on
That is something Jopr takes care of. Bascially when you install the agent,
you pass some properties for the server(s) location. There is multicast
support for this too.
> each agent so the agent reports its location on startup? This makes
> sense to me...
This does not directly cater for agents on changing IP addresses, but
this is
a Jopr internal issue and does not change at all the way plugins are
written.
One thing we may need to take care of (but then, it may be no issue at
all) is to not
discover a cache or cluster from different agents. But then if it an
issue we need to
take care of that in Jopr (imho).
Heiko
More information about the infinispan-dev
mailing list