Hello, I have a test lab and its use VirtualBox with two VMs as below: VM1 (node1): This VM has two NICs (NAT, Host-only Adapter) VM2 (node2): This VM has one NIC (Host-only Adapter)
On VM1, I use the NAT interface for the port forwarding: "127.0.0.1:2080" on Host FORWARDING TO 127.0.0.1:80 on Guest.
The IP addresses of my VMs are: 192.168.56.7 node1 192.168.56.8 node2
These nodes using the Pacemaker clustering and when node1 stopped, then a floting IP address (192.168.56.9) replace it.
# pcs cluster stop node1 node1: Stopping Cluster (pacemaker)... node1: Stopping Cluster (corosync)... # pcs status Error: error running crm_mon, is pacemaker running? Could not connect to the CIB: Transport endpoint is not connected crm_mon: Error: cluster is not available on this node # curl http://192.168.56.9 <html> <body>My Test Site - node2</body> </html>
In normal state, when I browse "http://127.0.0.1:2080" on my host, then it shows me "My Test Site - node1", but when I stopped node1 cluster and browse "http://127.0.0.1:2080" it doesn't show me "My Test Site - node2". Can I use Firewalld to forward the requests to "http://192.168.56.9" when node1 stopped?
Thank you.
On Thu, Mar 25, 2021 at 09:11:05AM -0000, Jason Long wrote:
Hello, I have a test lab and its use VirtualBox with two VMs as below: VM1 (node1): This VM has two NICs (NAT, Host-only Adapter) VM2 (node2): This VM has one NIC (Host-only Adapter)
On VM1, I use the NAT interface for the port forwarding: "127.0.0.1:2080" on Host FORWARDING TO 127.0.0.1:80 on Guest.
The IP addresses of my VMs are: 192.168.56.7 node1 192.168.56.8 node2
These nodes using the Pacemaker clustering and when node1 stopped, then a floting IP address (192.168.56.9) replace it.
# pcs cluster stop node1 node1: Stopping Cluster (pacemaker)... node1: Stopping Cluster (corosync)... # pcs status Error: error running crm_mon, is pacemaker running? Could not connect to the CIB: Transport endpoint is not connected crm_mon: Error: cluster is not available on this node # curl http://192.168.56.9
<html> <body>My Test Site - node2</body> </html>
In normal state, when I browse "http://127.0.0.1:2080" on my host, then it shows me "My Test Site - node1", but when I stopped node1 cluster and browse "http://127.0.0.1:2080" it doesn't show me "My Test Site - node2". Can I use Firewalld to forward the requests to "http://192.168.56.9" when node1 stopped?
No. You can't use firewalld for that. I think you need a real load balance - something like haproxy.
How about a Bash script that check that IP address if that IP was unreachable, then use Firewalld to do a forward!
On Thursday, March 25, 2021, 04:15:41 PM GMT+4:30, Eric Garver egarver@redhat.com wrote:
On Thu, Mar 25, 2021 at 09:11:05AM -0000, Jason Long wrote:
Hello, I have a test lab and its use VirtualBox with two VMs as below: VM1 (node1): This VM has two NICs (NAT, Host-only Adapter) VM2 (node2): This VM has one NIC (Host-only Adapter)
On VM1, I use the NAT interface for the port forwarding: "127.0.0.1:2080" on Host FORWARDING TO 127.0.0.1:80 on Guest.
The IP addresses of my VMs are: 192.168.56.7 node1 192.168.56.8 node2
These nodes using the Pacemaker clustering and when node1 stopped, then a floting IP address (192.168.56.9) replace it.
# pcs cluster stop node1 node1: Stopping Cluster (pacemaker)... node1: Stopping Cluster (corosync)... # pcs status Error: error running crm_mon, is pacemaker running? Could not connect to the CIB: Transport endpoint is not connected crm_mon: Error: cluster is not available on this node # curl http://192.168.56.9
<html> <body>My Test Site - node2</body> </html>
In normal state, when I browse "http://127.0.0.1:2080" on my host, then it shows me "My Test Site - node1", but when I stopped node1 cluster and browse "http://127.0.0.1:2080" it doesn't show me "My Test Site - node2". Can I use Firewalld to forward the requests to "http://192.168.56.9" when node1 stopped?
No. You can't use firewalld for that. I think you need a real load balance - something like haproxy.
On Thu, Mar 25, 2021 at 12:12:20PM +0000, Jason Long wrote:
How about a Bash script that check that IP address if that IP was unreachable, then use Firewalld to do a forward!
Sure. I'm sure you could hack something up.
On Thursday, March 25, 2021, 04:15:41 PM GMT+4:30, Eric Garver egarver@redhat.com wrote:
On Thu, Mar 25, 2021 at 09:11:05AM -0000, Jason Long wrote:
Hello, I have a test lab and its use VirtualBox with two VMs as below: VM1 (node1): This VM has two NICs (NAT, Host-only Adapter) VM2 (node2): This VM has one NIC (Host-only Adapter)
On VM1, I use the NAT interface for the port forwarding: "127.0.0.1:2080" on Host FORWARDING TO 127.0.0.1:80 on Guest.
The IP addresses of my VMs are: 192.168.56.7 node1 192.168.56.8 node2
These nodes using the Pacemaker clustering and when node1 stopped, then a floting IP address (192.168.56.9) replace it.
# pcs cluster stop node1 node1: Stopping Cluster (pacemaker)... node1: Stopping Cluster (corosync)... # pcs status Error: error running crm_mon, is pacemaker running? Could not connect to the CIB: Transport endpoint is not connected crm_mon: Error: cluster is not available on this node # curl http://192.168.56.9
<html> <body>My Test Site - node2</body> </html>
In normal state, when I browse "http://127.0.0.1:2080" on my host, then it shows me "My Test Site - node1", but when I stopped node1 cluster and browse "http://127.0.0.1:2080" it doesn't show me "My Test Site - node2". Can I use Firewalld to forward the requests to "http://192.168.56.9" when node1 stopped?
No. You can't use firewalld for that. I think you need a real load balance - something like haproxy.
firewalld-users@lists.fedorahosted.org
-
Eric Garver -
Jason Long