Currently if you're running JBoss-Cloud in a VMware environment you must tell somehow JBoss AS instances where is the loadbalancer (front-end-appliance) located. You can do that in two ways:
- manually,
- using VM2.
Manually
The only thing you must edit is JBOSS_PROXY_LIST parameter in all back-end-appliances (jboss-as5-appliance).
Your /etc/jboss-as5.conf might look like this:
JBOSS_GOSSIP_PORT=12001
JBOSS_GOSSIP_REFRESH=5000
JBOSS_SERVER_PEER_ID=134
# Comma-separated list of address:port for mod_cluster front-end proxies
JBOSS_PROXY_LIST=
JBOSS_IP=172.16.10.134
JAVA_HOME=/usr
If your front-end-appliance has a 172.16.10.133 IP address, edit this file like this:
JBOSS_GOSSIP_PORT=12001
JBOSS_GOSSIP_REFRESH=5000
JBOSS_SERVER_PEER_ID=134
# Comma-separated list of address:port for mod_cluster front-end proxies
JBOSS_PROXY_LIST=172.16.10.133:80
JBOSS_IP=172.16.10.134
JAVA_HOME=/usr
Note: Remeber to add valid port too!
Using VM2
VM2 bring Amazon EC2 to your computer with VMware help. Read more about VM2 on the project page. At this time VM2 only supports VMware Fusion on OSX. This is a great way to develop and test appliances.
See full list of commands available in VM2.
If you are using VM2 for booting appliances, VM2 takes care on injecting right front-end-appliance IP address to all JBoss AS configurations in the cloud.
Running JBoss Cloud on VMware Enterprise (ESX/ESXi)
Please make sure, that after you add appliances to ESX/ESXi inventory you have selected approriate Network label. JBoss Cloud default is NAT.
