| Thread Previous • Date Previous • Date Next • Thread Next |
LBaaS is no longer part of neutron. LBaaS issues should be reported in
storyboard under the Octavia project.
That said, this is available in Octavia.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1713424
Title:
[RFE] Support proxy protocol enablement in Neutron LBaaS API
Status in neutron:
Invalid
Bug description:
Problem: servers behind a TCP load balancer, as provisioned using the
Neutron LBaaS API, can't determine the source IP of a TCP connection.
Instead they will always see the load balancer IP as origin of
requests. This makes troubleshooting client connection issues using
logs gathered behind a LB very hard and often impossible.
Solution: the PROXY protocol has been introduced to forward the
missing information across a load balancer:
http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt
A number of backend services can make use of it, such as Nginx
https://www.nginx.com/resources/admin-guide/proxy-protocol/
but also Apache, Squid, Undertow. Proxy protocol is also supported by
Amazon ELB since 2013.
As HAproxy, the implementation behind the Neutron LBaaS API, does
already offer native support, this RFE is about its enablement using
the LBaaS API and corresponding Heat resources.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1713424/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
