[
https://issues.jboss.org/browse/AS7-430?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry commented on AS7-430:
--------------------------------------
Please go ahead and close PR 3593, since we know for sure that will not go in as-is. This
generic stuff is a good thing to have.
I didn't notice before that the only child allowed under <discovery-options> was
S3. Now you can support both static and S3, via the generic element. That's great, as
it allows an important use case of configuring for a 2nd master HC, which would be brought
on-line when the primary failed, with no need for any config change on the slaves to let
them detect it and connect.
For static discovery, a non-generic configuration is better though. That's so basic
it's something we'd always support, so it's a bit different from the more
specialized S3.
{code}
<discovery-option>
<static-discovery host="172.16.81.100" port="9999"/>
<discovery-option name="option-one"
code="org.jboss.as.host.controller.discovery.S3Discovery">
<property name="access-key" value="s3_access_key"/>
<property name="secret-access-key"
value="s3_secret_access_key"/>
<property name="location" value="s3_bucket_name"/>
</discovery-option>
</discovery-option>
{code}
DomainController discovery system
---------------------------------
Key: AS7-430
URL:
https://issues.jboss.org/browse/AS7-430
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Farah Juma
Fix For: 7.3.0.Alpha1
Mechanism(s) by which a Host Controller finds a Domain Controller so it can begin the
process of integrating into the domain.
Task includes the host.xml schema elements to configure this, the domain object model
classes behind those elements, and the actual implementation of discovery from both the
ServerManager and DomainController sides.
--
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