Comment 5 for bug 1624791
Revision history for this message
| Jean-Philippe Evrard (jean-philippe-evrard) wrote | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
So, just to be clear 10.0.3.121 is the IP of one of your horizon containers, not the VIP for the haproxy on the internal side, right?
I could see a few things going wrong, including haproxy backend selection and hairpinning.
But at first, I agree with Jesse, having horizon directly target the VIP on the internal side, seems better. This would make your system more reliable. Then proper deterministic load balancing could be the solution for you.
BUT with all of this blob of text above, I wonder why you happen to have problems now.
This is what we need to focus on.
Could you tell me if you are using haproxy, how are your LB backend balancing defined and which IP is the 10.0.3.121, please?
Thank you.