[jboss-jira] [JBoss JIRA] (AS7-430) DomainController discovery system

[Farah Juma (JIRA)]

    [ https://issues.jboss.org/browse/AS7-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740034#comment-12740034 ] 

Farah Juma commented on AS7-430:
--------------------------------

Created a pull request: https://github.com/jbossas/jboss-as/pull/3593

This allows a slave host controller to discover a master domain controller via S3. In particular, both the slave and the master can be configured with information needed to access an S3 bucket (sample configuration is shown below). When a master domain controller is started, if it has been configured to allow S3 discovery, it will write its address and port to an S3 file (jboss-domain-master-data) in the given bucket. There are now 2 remote domain controller discovery options for a slave host controller:

1. static discovery, i.e., statically configure the remote domain controller's host and port, exactly as before
2. S3 discovery, i.e., provide the <S3-discovery> configuration shown below

When a slave uses S3 discovery, it gets the remote domain controller's address and port from an S3 file in the given bucket. A slave must be configured with at least one of the two discovery options. Whenever a slave needs to connect to the master, it will now loop through all provided discovery options. (Note that when both discovery options are provided, static discovery will be attempted first. If this fails, then S3 discovery will be attempted next.) 

Sample Configuration -
An optional <discovery-options> element can now be added to <remote> for a slave host controller and to <local> for the master domain controller, as follows:

Slave host controller (note: this example configures both static and S3 discovery):
{code:xml}
<remote host="${jboss.domain.master.address}" port="${jboss.domain.master.port:9999}" security-realm="ManagementRealm">
    <discovery-options>
        <S3-discovery>
            <access-key value="s3_access_key"/>
            <secret-access-key value="s3_secret_access_key"/>
            <location value="s3_bucket_name"/>
        </S3-discovery>
     </discovery-options>
</remote>
{code}

Master domain controller:
{code:xml}
<local>
    <discovery-options>
        <S3-discovery>
            <access-key value="s3_access_key"/>
            <secret-access-key value="s3_secret_access_key"/>
            <location value="s3_bucket_name"/>
        </S3-discovery>
     </discovery-options>
</local>
{code}

Note that right now, the only child the <discovery-options> element can have is <S3-discovery>. However, the way the discovery system has been implemented should allow other discovery options to easily be added in the future as well.
                
> 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.2.0.CR1
>
>
> 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