[RFE] Add support X-Forwarded-For header in LBaaSv2

[Kobi Samoray]

X-Forwarded-For headers are used by proxies and load balancers to pass on the original client's IP to the server, while NATing the request.
This is very handy for some applications but has some overheads and therefore has to be configurable.
LBaaSv2 API doesn't offer support for enabling XFF header.
Without having an XFF header, the members cannot conclude which IP address originated the NATed request - e.g for auditing purposes.
Changes required are addition of a boolean property to the listener - which will indicate that an XFF header should be appended to the requests.

[Henry Gessau (gessau)]

Should this be an RFE?

[Brandon Logan (brandon-logan)]

should be an rfe especially if its an api addition

[Armando Migliaccio (armando-migliaccio)]

@Doug: what is your recommendation for feature submission? Spec or no spec? This looks like it may require API changes.

[Armando Migliaccio (armando-migliaccio)]

If Kobi has the code lined up and Doug is happy to support this, so am I, because this sounds reasonable enough. Mind you to preserve the old way for the health monitor to work.

[Armando Migliaccio (armando-migliaccio)]

Patches look abandoned:

https://review.openstack.org/#/q/owner:%22Kobi+Samoray%22+status:open

[OpenStack Infra (hudson-openstack)]

Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/255963
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

[Gregory Thiemonge (gthiemonge)]

Abandoned after re-enabling the Octavia launchpad.