Too many stat warning logs

[Wu Wenxiang]

In deploying environment.
I run multi keystone processes in multi ports, and use a haproxy to proxy all of them, like below:

_____Haproxy(5000)
                           |______Keystone-1(5000)
                           |______Keystone-2(5001)
                           |______Keystone-3(5002)
                           |______Keystone-4(5003)

I use this topo because of performance.

details: https://answers.launchpad.net/keystone/+question/230455

And I found too many warning logs in syslog:
Unable to resolve API as either public or admin: Haproxy:5000
Unable to resolve API as either public or admin: Haproxy:5000
Unable to resolve API as either public or admin: Haproxy:5000
....

Reason:
The root cause is Keystone-2~Keystone-4 not listened in 5000 as same as haproxy, so stat logic could handle.

I think this warning should be removed.
Or we should find another way to stat port.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/32312

[Wu Wenxiang (wu-wenxiang)]

In fact, I really prefer using "multi-worker children processes" which was the same as nova-api and cinder-api. With multi-worker solution, we could launch more than 1 process listened at the same port, which fix this issue more graceful.
How about your opinions?

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/32312
Committed: http://github.com/openstack/keystone/commit/6ca63a77e228a32b6e4763ec3d6b198a14769bb8
Submitter: Jenkins
Branch: master

commit 6ca63a77e228a32b6e4763ec3d6b198a14769bb8
Author: Wu Wenxiang <[e-mail]>
Date: Sun Jun 9 17:24:27 2013 +0800

    Remove a stat warning log

    If using load balancer before keystone and the port numbers was
    different between load balancer and keystone, too many stat warning logs
    could be found in logs. The root cause is the keystone servers' stat
    logic getting the request host information which point to load balancer
    ip address and port rather than the ips and ports of themselves.

    Fixes bug #1189118
    Change-Id: Ic837af77bc2509086c0e37194ba70b683f693ae5