Bug 968334
Summary: | Head gear haproxy configs hard code the IP address of the sub gears... | ||
---|---|---|---|
Product: | OpenShift Online | Reporter: | Thomas Wiest <twiest> |
Component: | Containers | Assignee: | Mrunal Patel <mpatel> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.x | CC: | agoldste, bhatiam, bmeng, ccoleman, jhonce, mpatel |
Target Milestone: | --- | Keywords: | UpcomingRelease |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-01-24 03:22:28 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Thomas Wiest
2013-05-29 13:27:34 UTC
The reason we went with IPs was because the DNS took time to resolve. Also, AFAIK the connection hooks are run after a move and they should fix up the haproxy configuration. If they aren't run then they should be run. I see, ok, well that still doesn't address the problem of stopping and starting an ex-node in AWS. Unfortunately, for a number of reasons, stopping and starting instances in AWS is something we have to be able to do without breaking a bunch of apps / gears. According to our internal monitoring, Dyn now takes on average 10.15 seconds between when we register new DNS and when it propagates to AWS. It does sometimes take much longer (like minutes), but that's pretty rare these days. It might be possible to use validate configuration feature to fix the haproxy config. We've talked about this a few times and per gear DNS records may be the only way to do this across all the use cases we are going to need to support. In 2.0.35 we now use the public_hostname instead of the IP address. Checked on latest STG (devenv-stage_552), issue has been fixed. $ cat haproxy.cfg <---> server gear-52788aaadbd93cc3ab00004b-bmeng1stg ex-std-node1.stg.rhcloud.com:43401 check fall 2 rise 3 inter 2000 cookie 52788aaadbd93cc3ab00004b-bmeng1stg Move bug to verified. |