[
https://issues.jboss.org/browse/AS7-4388?page=com.atlassian.jira.plugin.s...
]
Dennis Reed commented on AS7-4388:
----------------------------------
Introduction of the cluster resource is experimental only and
presented now for discussion. I think its natural for a user
to want to see what is happening in a cluster, as opposed to only on a single node.
Feedback appreciated.
That should already be available in domain mode, or using any other tool (JON) that looks
at multiple nodes.
And it's not specific to the JGroups/Infinispan subsystems. The same argument of
wanting to see data across nodes would apply to most subsystems.
I don't think that functionality should be duplicated in a different way.
But this requires being able to take a resource X whose attributes
are exposed as storage=configuration, access=read-write in one part of
the tree and expose it in another part of the tree as storage=configuration,
access=read-only.
Don't duplicate the information already available under stack=!
What would be useful under the runtime part would be exposing the actual JGroups protocol
info (the current data, which could be different from the configuration if things were
changed at runtime).
It would also be nice to see the runtime part not be limited to channels created by the AS
JGroups subsystem, but also include any custom JGroups channels (maybe limited to those
channels using the shipped JGroups version to avoid version mismatch complications).
Provide clustering management use cases
---------------------------------------
Key: AS7-4388
URL:
https://issues.jboss.org/browse/AS7-4388
Project: Application Server 7
Issue Type: Task
Components: Console
Reporter: Heiko Braun
Assignee: Bela Ban
Fix For: 7.2.0.CR1
In order to prep the UI, we would need a list of typical clustering management use cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira