[jboss-jira] [JBoss JIRA] (WFCORE-401) Consider using a "describe" notion for providing the model to slaves on registration

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry reassigned WFCORE-401:
---------------------------------------

    Assignee: Kabir Khan  (was: Emanuel Muckenhuber)


Kabir, this is the JIRA that resulted in all that host controller stuff you took over. It went in quite a different direction from the description here, which is fine. I'm assigning this to you because you're dealing with the overall task and should know best how to clean up this JRIA (reject, reword to fit the actual work, etc.)

> Consider using a "describe" notion for providing the model to slaves on registration
> ------------------------------------------------------------------------------------
>
>                 Key: WFCORE-401
>                 URL: https://issues.jboss.org/browse/WFCORE-401
>             Project: WildFly Core
>          Issue Type: Task
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: Kabir Khan
>             Fix For: 1.0.0.Beta1
>
>
> When a slave HC registers, the master provides it a copy of the domain-wide model as a DMR tree. This has a weakness in that the Resource impl types that comprise that tree on the master side are not transmitted. If custom Resource impls are used, they may not be recreated on the slave.
> Consider instead sending a list of mgmt ops, a la what we do with servers when starting from an HC.
> This could potentially be limited to subsystems, with the core model sent as it is now. The core model is handled by core-AS code on the slave side, so we can reasonably ensure that code always uses the correct Resource type. There are places where we already do that. The bigger problem is subsystems. 



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)