yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #49782
[Bug 1572655] Re: Neutron-LBaaS v2: Redundant protocols for Listener and Pool
Just one place won't work. I get that if it's pass-through, just one is
fine . But if you're terminated https, you might want cleartext back to
the members to offload SSL. Or not, if you're just being a sneaky
middleman.
** Changed in: neutron
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1572655
Title:
Neutron-LBaaS v2: Redundant protocols for Listener and Pool
Status in neutron:
Won't Fix
Bug description:
(This is more of a feature request than a bug.)
Examine the available protocols for Listener and Pool.
Listener: TCP, HTTP, HTTPS, TERMINATED_HTTPS
Pool: TCP, HTTP, HTTPS
This combination may be redundant:
Listener -> Pool
HTTPS -> HTTP
TERMINATED_HTTPS -> HTTP
It becomes quite complicated that we can create different combinations
of protocols for pool and listener.
I suggest having just a one time place to define a protocol - either
in pool or listener.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1572655/+subscriptions
References