Open Stack

Hi



I wasn't able to get % for the spreadsheet but our Product Manager
prioritized the features:



*Function*

*Priority (0 = highest)*

*HTTP+HTTPS on one device*

5

*L7 Switching*

2

*SSL Offloading*

1

*High Availability*

0

*IP4 & IPV6 Address Support*

6

*Server Name Indication (SNI) Support*

3

*UDP Protocol*

7

*Round Robin Algorithm*

4



 Susanne


On Thu, Apr 3, 2014 at 9:32 AM, Vijay Venkatachalam <
Vijay.Venkatachalam at citrix.com> wrote:

>
>
>                 The document has Vendor  column, it should be from Cloud
> Operator?
>
>
>
> Thanks,
>
> Vijay V.
>
>
>
>
>
> *From:* Eugene Nikanorov [mailto:enikanorov at mirantis.com]
> *Sent:* Thursday, April 3, 2014 11:23 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
>
> *Subject:* Re: [openstack-dev] [Neutron][LBaaS] Load balancing use cases.
> Data from Operators needed.
>
>
>
> Stephen,
>
>
>
> Agree with you. Basically the page starts looking as requirements page.
>
> I think we need to move to google spreadsheet, where table is organized
> easily.
>
> Here's the doc that may do a better job for us:
>
>
> https://docs.google.com/spreadsheet/ccc?key=0Ar1FuMFYRhgadDVXZ25NM2NfbGtLTkR0TDFNUWJQUWc&usp=sharing
>
>
>
> Thanks,
>
> Eugene.
>
>
>
> On Thu, Apr 3, 2014 at 5:34 AM, Prashanth Hari <hvprash at gmail.com> wrote:
>
>  More additions to the use cases (
> https://wiki.openstack.org/wiki/Neutron/LBaaS/Usecases).
>
> I have updated some of the features we are interested in.
>
>
>
>
>
>
>
> Thanks,
>
> Prashanth
>
>
>
>
>
> On Wed, Apr 2, 2014 at 8:12 PM, Stephen Balukoff <sbalukoff at bluebox.net>
> wrote:
>
>  Hi y'all--
>
>
>
> Looking at the data in the page already, it looks more like a feature
> wishlist than actual usage data. I thought we agreed to provide data based
> on percentage usage of a given feature, the end result of the data
> collection being that it would become more obvious which features are the
> most relevant to the most users, and therefore are more worthwhile targets
> for software development.
>
>
>
> Specifically, I was expecting to see something like the following (using
> hypothetical numbers of course, and where technical people from "Company A"
> & etc. fill out the data for their organization):
>
>
>
> == L7 features ==
>
>
>
> "Company A" (Cloud operator serving external customers): 56% of
> load-balancer instances use
>
> "Company B" (Cloud operator serving external customers): 92% of
> load-balancer instances use
>
> "Company C" (Fortune 100 company serving internal customers): 0% of
> load-balancer instances use
>
>
>
> == SSL termination ==
>
>
>
> "Company A" (Cloud operator serving external customers): 95% of
> load-balancer instances use
>
> "Company B" (Cloud operator serving external customers): 20% of
> load-balancer instances use
>
> "Company C" (Fortune 100 company serving internal customers): 50% of
> load-balancer instances use.
>
>
>
> == Racing stripes ==
>
>
>
> "Company A" (Cloud operator serving external customers): 100% of
> load-balancer instances use
>
> "Company B" (Cloud operator serving external customers): 100% of
> load-balancer instances use
>
> "Company C" (Fortune 100 company serving internal customers): 100% of
> load-balancer instances use
>
>
>
>
>
> In my mind, a wish-list of features is only going to be relevant to this
> discussion if (after we agree on what the items under consideration ought
> to be) each technical representative presents a prioritized list for their
> organization. :/ A wish-list is great for brain-storming what ought to be
> added, but is less relevant for prioritization.
>
>
>
> In light of last week's meeting, it seems useful to list the features most
> recently discussed in that meeting and on the mailing list as being points
> on which we want to gather actual usage data (ie. from what people are
> actually using on the load balancers in their organization right now).
> Should we start a new page that lists actual usage percentages, or just
> re-vamp the one above?  (After all, wish-list can be useful for discovering
> things we're missing, especially if we get people new to the discussion to
> add their $0.02.)
>
>
>
> Thanks,
>
> Stephen
>
>
>
>
>
>
>
> On Wed, Apr 2, 2014 at 3:46 PM, Jorge Miramontes <
> jorge.miramontes at rackspace.com> wrote:
>
>   Thanks Eugene,
>
>
>
> I added our data onto the requirements page since I was hoping to
> prioritize requirements based on the operator data that gets provided. We
> can move it over to the other page if you think that makes sense. See
> everyone on the weekly meeting tomorrow!
>
>
>
> Cheers,
>
> --Jorge
>
>
>
> *From: *Susanne Balle <sleipnir012 at gmail.com>
> *Reply-To: *"OpenStack Development Mailing List (not for usage
> questions)" <openstack-dev at lists.openstack.org>
> *Date: *Tuesday, April 1, 2014 4:09 PM
> *To: *"OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev at lists.openstack.org>
> *Subject: *Re: [openstack-dev] [Neutron][LBaaS] Load balancing use cases.
> Data from Operators needed.
>
>
>
> I added two more. I am still working on our HA use cases. Susanne
>
>
>
> On Tue, Apr 1, 2014 at 4:16 PM, Fox, Kevin M <Kevin.Fox at pnnl.gov> wrote:
>
>  I added our priorities. I hope its formatted well enough. I just took a
> stab in the dark.
>
> Thanks,
> Kevin
>  ------------------------------
>
> *From:* Eugene Nikanorov [enikanorov at mirantis.com]
> *Sent:* Tuesday, April 01, 2014 3:02 AM
> *To:* OpenStack Development Mailing List
> *Subject:* [openstack-dev] [Neutron][LBaaS] Load balancing use cases.
> Data from Operators needed.
>
> Hi folks,
>
>
>
> On the last meeting we decided to collect usage data so we could
> prioritize features and see what is demanded most.
>
>
>
> Here's the blank page to do that (in a free form). I'll structure it once
> we have some data.
>
> https://wiki.openstack.org/wiki/Neutron/LBaaS/Usecases
>
>
>
> Please fill with the data you have.
>
>
>
> Thanks,
>
> Eugene.
>
>
> _______________________________________________
> OpenStack-dev mailing list
> 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
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
>
> --
> Stephen Balukoff
> Blue Box Group, LLC
> (800)613-4305 x807
>
>
> _______________________________________________
> OpenStack-dev mailing list
> 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
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> 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/34d65c56/attachment.html>