I just went through the Tribes code and figured out that the local member
host and bind address can be configured to be different values. It is the
localMemberHost that is advertised by Tribes while
the localMemberBindAddress is the IP address used for binding the server
socket. I will make the necessary changes to Axis2 and inform this list. My
plan is to add a new optional parameter called localMemberBindAddress to
the axis2.xml's clustering section, in addition to the already existing
localMemberHost. If localMemberBindAddress is not specified, we assume that
it is same as the localMemberHost.
e.g.
<parameter name="localMemberHost">10.100.3.67</parameter>
<parameter name="*localMemberBindAddress*">192.168.1.121</parameter>
Then we have to setup iptables on the physical machine to do port
forwarding. In this model, we have to make sure that all Carbon processes
started within LXCs have unique ports. Otherwise the port forwarding will
not work.
Thoughts welcome.
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* <http://www.apache.org/>**
email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919
blog: **http://blog.afkham.org* <http://blog.afkham.org>*
twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
