[undertow-dev] Frontent Load Balancer with Mod-Cluster using a virtual IP address

[ralf_boogie_blues at bluewin.ch]

Thanks a lot Stuart, you pointed me to the right direction. We are using Wildfly. I added a new interface and added a second socketBinding as you have described. That works nicely. 

Really cool, the interface can be configured to listen on a nic name too. This is exactly what I am looking for.

What I didn't manage is only to open the management console. What is the path for accessing the management console? I saw in some tests "/mod_cluster_manager" but I was not able to access the console with this path.

I think, it would make sense to update the official wildfly undertow load balancer documentation: https://docs.jboss.org/author/display/WFLY9/Using+Wildfly+as+a+Load+Balancer

Thanks again
Ralf


----Ursprüngliche Nachricht----
Von : sdouglas at redhat.com
Datum : 18/09/2015 - 01:46 (WEDT)
An : ralf_boogie_blues at bluewin.ch
Cc : undertow-dev at lists.jboss.org
Betreff : Re: [undertow-dev] Frontent Load Balancer with Mod-Cluster using a	virtual IP address

Are you using Wildfly or standalone Undertow? The procedure for configuring a listener is different for each. For Wildfly just add a socket binding to the interface you want to listen on then add a http-listener in the Undertow subsystem that references that binding.

For standalone Undertow simply call addListener() multiple times for each interface you want to listen on.

Stuart

----- Original Message -----
> From: "ralf boogie blues" <ralf_boogie_blues at bluewin.ch>
> To: undertow-dev at lists.jboss.org
> Sent: Wednesday, 16 September, 2015 10:57:33 PM
> Subject: [undertow-dev] Frontent Load Balancer with Mod-Cluster using a	virtual IP address
> 
> Hi
> 
> I trying to replace your Apache Httpd with mod_cluster load balancer with
> Undertow frontend modcluster as part of Wildfly 9.0.1.
> 
> It works fine when I define a 'real' IP address defined in /etc/hosts:
> 
> 127.0.0.1 localhost
> 10.22.62.40 mdzhrnesir01.standard.six-group.net mdzhrnesir01
> 
> 
> But this IP address 10.22.62.117 is not taken by untertow:
> 
> ip addr
> .
> 8: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue
> state UP
> link/ether 00:17:a4:77:f0:b6 brd ff:ff:ff:ff:ff:ff
> inet 10.22.62.40/24 brd 10.22.62.255 scope global bond0
> inet 10.22.62.117/24 scope global secondary bond0
> 
> 
> I also faced to problem, that running the example presented by Stuart Douglas
> doesn't work inside a docker container. Even I execute step by step.
> 
> Without digging into the source code, what are the criteria under which
> Undertow frontend modcluster accepts IP address(es)?
> 
> Do you also have a proposal for configuring Undertow modcluster to listen to
> two interfaces? Say an internal IP address and an virtual external IP
> address?
> 
> I think with Apache, we defined 0.0.0.0 and then Apache with mod_cluster was
> listening on all interfaces, if I remember correctly.
> 
> Thanks a lot in advance
> Ralf
> 
> _______________________________________________
> undertow-dev mailing list
> undertow-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/undertow-dev