[jboss-jira] [JBoss JIRA] (WFCORE-81) Expose address of DC as runtime attributes on the HC

[ https://issues.jboss.org/browse/WFCORE-81?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFCORE-81: ---------------------------------------- It belongs somewhere in /host=hc-1 itself. Not in the core-service=host-environment child as that resource is about the environmental info the HC picked up at initial boot, i.e. stuff that comes in from the command line. The most relevant place is the domain-controller attribute on the /host=hc-1 resource: {code} [domain@localhost:9999 host=slave-a] :read-resource { "outcome" => "success", "result" => { "directory-grouping" => "by-server", "domain-controller" => {"remote" => { "port" => expression "${jboss.domain.master.port:9999}", "host" => expression "${jboss.domain.master.address}", "username" => undefined, "admin-only-policy" => undefined, "security-realm" => "ManagementRealm" }}, {code} That would need something like "resolved-scheme", "resolved-host" and "resolved-port" fields added. The "resolved-scheme" comes in because of WFCORE-75 which is currently being worked on. We can no longer assume the protocol scheme is "remote". My thinking is we only expose this for the slave HC's; i.e. it's part of that domain-controller => remote structure that only exists on a slave. We don't add something to the domain-controller => local structure that exists on the master, because it would be redundant, and once WFCORE-75 is done, vague. The way to learn about how to communicate with any HC that you're already connected to is via the existing /host=*/core-service=management/management-interface=* resources. As for what class to use to expose this... that's a tough question. Looking at this, it's quite complex. Possible places are org.jboss.as.host.controller.MasterDomainControllerClient or org.jboss.as.domain.controllerLocalHostControllerInfo. The way that domain-controller attribute is handled would need to change though. Currently its contents are set once via RemoteDomainControllerAddHandler (for the slave aka remote case) and LocalDomainControllerAddHandler (for the master aka local case) and thereafter reading that attribute is a simple, using the default read handler. But now HostResourceDefinition L250 would need to register a custom read handler instead of null, one that can read the add in the dynamically determined "resolved-scheme", "resolved-host" and "resolved-port" fields. So, not a simple task. -- This message was sent by Atlassian JIRA (v6.3.1#6329)