Hi,
As far as I know the only supported combinations are VIP:HTTPS POOL:HTTP and vice versa.
Do you see any other relevant combinations?
From validation perspective – If a Pool that is configured with protocol (ex: TCP) is connected to a VIP with incompatible protocol, what should be the behavior?
Regards,
-Sam.
From: Youcef Laribi [mailto:Youcef.Laribi at eu.citrix.com]
Sent: Sunday, February 10, 2013 8:59 PM
To: OpenStack Development Mailing List
Cc: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [Quantum][LBaaS] - lb protocols defined twice
One is the VIP protocol (e.g. HTTPS on the front from the clients) and the other is the pool members protocol (e.g. HTTP in the back to the members), or the reverse. The LB device would do the translation between the two. SSL Offload is not supported in Grizzly release so this is for allowing future addition post Grizzly and extensibility.
Youcef
On Feb 10, 2013, at 8:05, "Avishay Balderman" <AvishayB at Radware.com<mailto:AvishayB at Radware.com>> wrote:
Hi
The field ‘protocol’ is defined twice in the model:
1) Pool
2) Vip
Can you please explain why we need this double definition?
Thanks
Avishay
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130211/da7d2175/attachment.html>