[jboss-jira] [JBoss JIRA] (WFLY-5790) Use a separate interface for JGroups sockets

[Brian Stansberry (JIRA)]

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

Brian Stansberry reassigned WFLY-5790:
--------------------------------------

    Assignee: Paul Ferraro  (was: Brian Stansberry)


[~jason.greene][~pferraro] My experimental PR passed CI and I know you wanted to get this done, Jason, so I created a JIRA and changed my PRs commit message to reflect it.

I'm assigning this over to you, though, Paul, as your team would know better if there are any gotchas here, particularly any testsuite tweaks that are necessary to ensure the test servers are using the expected addresses. My PR has the basic change to the xslt that's used to change the default addresses to IPv6.

> Use a separate interface for JGroups sockets
> --------------------------------------------
>
>                 Key: WFLY-5790
>                 URL: https://issues.jboss.org/browse/WFLY-5790
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: Clustering, Domain Management
>            Reporter: Brian Stansberry
>            Assignee: Paul Ferraro
>             Fix For: 10.0.0.Final
>
>
> Our standard configs currently use the "public" interface for the JGroups sockets. However, best practice is to put intra-cluster traffic on a separate network from the network handling end user requests, both for possible performance reasons and to reduce the risk of exposing clustering to unwanted, possibly malevolent, traffic.
> Since that is best practice, our standard configs should reflect that. So we'll create a new 'private' interface to go along with the existing 'public', 'management', and 'unsecure' ones, and use it for the JGroups sockets.
> The default address will be ${jboss.bind.address.private:127.0.0.1} consistent with the others.
> Users using our standard configs who wish to use -b startup switches to control the network address will need to add -bprivate=<theaddress> to the startup command. Simply using -b=<theaddress> will no longer affect the JGroups traffic if our standard configs are used.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)