[jboss-jira] [JBoss JIRA] (WFCORE-325) Allow socket-binding-group-refType to override default-interface

[Brian Stansberry (JIRA)]

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

Brian Stansberry moved WFLY-1148 to WFCORE-325:
-----------------------------------------------

        Project: WildFly Core  (was: WildFly)
            Key: WFCORE-325  (was: WFLY-1148)
    Component/s: Domain Management
                     (was: Domain Management)


> Allow socket-binding-group-refType to override default-interface
> ----------------------------------------------------------------
>
>                 Key: WFCORE-325
>                 URL: https://issues.jboss.org/browse/WFCORE-325
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Todd Trimmer
>            Priority: Optional
>              Labels: configuration, domain, host-controller
>
> I want all the host controllers in my domain to use the same socket-binding-group. However, each host controller can have multiple servers, each with its own IP, but each IP still reuses the same port number (yet still a unique IP+port combo). The problem is that the socket-binding-group-refType will not let me override the @default-interface value from the referent socket-binding-group. I am forced to create a second, equally verbose, socket-binding-group exactly like the first group in every way, except for the @default-interface. I wish to avoid this. My particular scenario cannot rely on @port-offset because my hardware load-balancer needs all nodes in the same pool to use the same ports.
> Under my proposal, the host.xml could thus more easily be written like this:
> ...
>     <interfaces>
>         <interface name="public">
>             <inet-address value="10.10.10.1" />
>         </interface>
>         <interface name="public-two">
>             <inet-address value="10.10.10.2" />
>         </interface>
>     </interfaces>
> ...
>     <servers>
>         <server name="server-one" group="prod-server-group" auto-start="true">
>             <jvm name="jvm6g" />
>         </server>
>         <server name="server-two" group="prod-server-group" auto-start="false">
>             <jvm name="jvm2g" />
>             <socket-binding-group ref="standard-sockets" default-interface="public-two" />
>         </server>
>     </servers>
> ...
> This alleviates the burden of having to define a second socket-binding-group in domain.xml and maintaining the same set of socket-binding definitions in two places.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)