GitHub user nickaccuweb added a comment to the discussion: What things to do after setting up load balancer on top of management servers.
@anirudh09041, We have a similar CloudStack setup where we use HAProxy as the load balancer and Keepalived to manage the floating VIP. In our setup: - VIP: 10.50.0.100 - Port 8080 (UI/API): HAProxy uses balance source to keep client connections on the same management server. - Port 8250 (Agent): HAProxy uses balance first, with MGMT1 as primary and MGMT2 as backup. Your Oracle Load Balancer configuration looks fine as a starting point. Since you can access the CloudStack dashboard, port 8080 appears to be working. I would suggest checking a few more things: 1. Verify that the CloudStack host global setting is configured correctly for your load balancer setup. 2. Make sure KVM hosts and System VMs can communicate through port 8250. 3. Configure proper health checks for both backend sets. 4. Check session persistence, especially for port 8250, as agent connections should remain stable. 5. Test failover by stopping the CloudStack management service on one server and checking whether the remaining servers handle the connections properly. One thing I noticed is that both your backend sets use IP hash. For port 8250, we prefer a primary/backup approach to keep agent connections on the preferred management server. Also, confirm that all three management servers are connected to the same CloudStack database. Could you share your CloudStack version and the current value of the host global setting? Nick R Accuweb.Cloud Team GitHub link: https://github.com/apache/cloudstack/discussions/14400#discussioncomment-18950104 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
