[
https://issues.jboss.org/browse/AS7-4388?page=com.atlassian.jira.plugin.s...
]
Bela Ban commented on AS7-4388:
-------------------------------
Re probe and security: yes I agree there should only be a subset of operations that are
exposed. The more important question to me though is how we execute operation invocation,
and attribute querying and setting across a cluster. It we restrict ourselves to domain
mode, then we could use a server group to do that. However, this excludes standalone
instances and makes a cluster always a subset of a server group. Not sure I like that
(I'm sure Brian does) :-)
If we do it that way, there is no need to use multicasting to send requests (operations
and attribute gets/sets), as done with probe, but we'd use the mechanism used within
domain management that a master uses to talk to the slaves.
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.3.0.Alpha1
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