[openstack-dev] [Neutron][LBaaS] Load balancing use cases and web ui screen captures

Samuel Bercovici SamuelB at Radware.com
Wed Apr 9 07:46:54 UTC 2014


Hi Eugene,

As far as I recall people wanted to balance how a "common" case would be used vs. an "advanced" case.
For this I have created a range of use cases listed in the document so that people can go over, make sure they agree (ex: the question about availability zones) and then we can select two that represent the simple case and the advanced case.
I also think that the one you have listed below stands a very good case of being used for the "advanced" case.

Regards,
                -Sam.


From: Eugene Nikanorov [mailto:enikanorov at mirantis.com]
Sent: Monday, April 07, 2014 6:15 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Load balancing use cases and web ui screen captures

Hi Sam,

I find google doc a little bit too heavy for ML discussion.
So I'd like to extract the gist of the overall use case that we want to use when discussing an API (for ex, single-call API).
Here it is as I see it (Sam, correct me if I'm wrong):

User wants to setup web application that is available both via HTTP and HTTPS protocols and consists of various parts.
One part http://ip-addr/part1 is only available via HTTP, another part http://ip-addr//part2<http://ip-addr/part2> is available via both HTTP and HTTPS.
Webapp parts part1 and part2 are served with two different group of nodes which reside on different (option: same) private networks.

Please provide a call or a set of calls that would allow to configure balancing for such app. Consider additional options like HA.

Thanks,
Eugene.


On Mon, Apr 7, 2014 at 4:12 PM, Alun Champion <prof at achampion.net<mailto:prof at achampion.net>> wrote:
Yes, to ensure availability the same application could be deployed
across multiple availability zones/cells, as these can offer some
level of independence of risk. The use-cases seemed to expect same
network, which may not be achievable given the above, but ideally
should be able to load-balance across zones/cells. Other cloud
management solutions have moved to name based LB because of the above,
is this something being considered?

On 7 April 2014 05:27, Samuel Bercovici <SamuelB at radware.com<mailto:SamuelB at radware.com>> wrote:
> Please elaborate, do you mean that the nodes could be on different zones/cells or something else?
>
>
> -----Original Message-----
> From: Alun Champion [mailto:prof at achampion.net<mailto:prof at achampion.net>]
> Sent: Sunday, April 06, 2014 4:51 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Neutron][LBaaS] Load balancing use cases and web ui screen captures
>
> How do these use-cases relate to availability zones or cells, is the assumption that the same private network is available across both? An application owner could look to protect availability not just provide scalability.
>
> On 6 April 2014 07:51, Samuel Bercovici <SamuelB at radware.com<mailto:SamuelB at radware.com>> wrote:
>> Per the last LBaaS meeting.
>>
>>
>>
>> 1.       Please find a list of use cases.
>>
>> https://docs.google.com/document/d/1Ewl95yxAMq2fO0Z6Dz6fL-w2FScERQXQR1
>> -mXuSINis/edit?usp=sharing
>>
>>
>>
>> a)      Please review and see if you have additional ones for the
>> project-user
>>
>> b)      We can then chose 2-3 use cases to play around with how the CLI,
>> API, etc. would look
>>
>>
>>
>> 2.       Please find a document to place screen captures of web UI. I took
>> the liberty to place a few links showing ELB.
>>
>> https://docs.google.com/document/d/10EOCTej5CvDfnusv_es0kFzv5SIYLNl0uH
>> erSq3pLQA/edit?usp=sharing
>>
>>
>>
>>
>>
>> Regards,
>>
>>                 -Sam.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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
>>
>
> _______________________________________________
> 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
>
> _______________________________________________
> 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

_______________________________________________
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/20140409/ef7e2019/attachment.html>


More information about the OpenStack-dev mailing list