[
https://issues.jboss.org/browse/WFLY-716?page=com.atlassian.jira.plugin.s...
]
Claudio Miranda commented on WFLY-716:
--------------------------------------
Hi, I would like to help on this. The DC port is visible in several places of
wildfly-host-controller project, classes: DomainRootDefinition,
RemoteDomainControllerAddHandler, but I could not find where to expose it as runtime
attribute,
Should the dc port be displayed at this level (this is the slave hc) ?
/host=hc-1/core-service=host-environment:read-resource(include-runtime=true)
{
"outcome" => "success",
"result" => {
"backup-domain-files" => false,
"default-jvm" => "/opt/javavm/bin/java",
"domain-base-dir" =>
"/home/claudio/alphaworks/projects/wildfly/dist/target/wildfly-9.0.0.Alpha1-SNAPSHOT/bin/../domain2",
"domain-config-dir" =>
"/home/claudio/alphaworks/projects/wildfly/dist/target/wildfly-9.0.0.Alpha1-SNAPSHOT/bin/../domain2/configuration",
"domain-config-file" => undefined,
"domain-content-dir" =>
"/home/claudio/alphaworks/projects/wildfly/dist/target/wildfly-9.0.0.Alpha1-SNAPSHOT/bin/../domain2/data/content",
"domain-data-dir" =>
"/home/claudio/alphaworks/projects/wildfly/dist/target/wildfly-9.0.0.Alpha1-SNAPSHOT/bin/../domain2/data",
"domain-log-dir" =>
"/home/claudio/alphaworks/projects/wildfly/dist/target/wildfly-9.0.0.Alpha1-SNAPSHOT/bin/../domain2/log",
"domain-servers-dir" =>
"/home/claudio/alphaworks/projects/wildfly/dist/target/wildfly-9.0.0.Alpha1-SNAPSHOT/bin/../domain2/servers",
"domain-temp-dir" =>
"/home/claudio/alphaworks/projects/wildfly/dist/target/wildfly-9.0.0.Alpha1-SNAPSHOT/bin/../domain2/tmp",
"home-dir" =>
"/home/claudio/alphaworks/projects/wildfly/dist/target/wildfly-9.0.0.Alpha1-SNAPSHOT",
"host-config-file" =>
"/home/claudio/alphaworks/projects/wildfly/dist/target/wildfly-9.0.0.Alpha1-SNAPSHOT/domain2/configuration/host.xml",
"host-controller-address" => "/127.0.0.1",
"host-controller-port" => 0,
"host-name" => "pavlov",
"initial-running-mode" => "NORMAL",
"is-restart" => false,
"modules-dir" =>
"/home/claudio/alphaworks/projects/wildfly/dist/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules",
"process-controller-address" => "/127.0.0.1",
"process-controller-port" => 51563,
"qualified-host-name" => "pavlov",
"use-cached-dc" => false
}
}
Also, can you provide some guidance about which class should I take a look about adding
this runtime attribute ?
Expose address of DC as runtime attributes on the HC
----------------------------------------------------
Key: WFLY-716
URL:
https://issues.jboss.org/browse/WFLY-716
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Domain Management
Reporter: Heiko Rupp
Labels: rhq
Fix For: Awaiting Volunteers
Currently there is no way to learn about the http management port of the DC from a
slave's host.xml or runtime.
17:02:31] <pilhuhn> I am reading host.xml to find the DC, so that I can contact its
http port for e.g. querying the /socket-binding-group if the one on the host is undefined
[17:02:41] <+bstansberry> I don't want it in the config, but I'm ok with
adding it as a runtime attribute
[17:04:13] <pilhuhn> bstansberry fine with me when I can query the HC for the http
port of the DC
[17:04:46] <+bstansberry> pilhuhn: the native API port should be a runtime
attribute as well
[17:04:51] <+bstansberry> yes please
[17:05:04] <+bstansberry> what i mean by that is we should expose it as a runtime
attribute
17:05:49] <+bstansberry> the config bit is an instruction to the HC, but we are
going to add alternatives, e.g. a multicast address
[17:06:55] <+bstansberry> so using the config will not be a reliable source;
runtime can be
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)