Open Stack

Comments inline (and not in red this time!).

On 5/6/14 3:30 PM, "Jay Pipes" <jaypipes at gmail.com> wrote:

>On 05/06/2014 03:16 PM, Jorge Miramontes wrote:
>> I agree that everyone's thoughts should be in it. I don't see why a
>> representative vote does not allow for that. Sam put a text box on each
>> use case to capture extra thoughts.
>
>Because all of us have different experiences. Not all of us have worked
>for the specific company we work at now for the past 20 years. We all
>have different customer experiences and use cases based on a variety of
>job positions and past employers.
>
>> I would hope that no organization would be so confused as to have widely
>> varying viewpoints on *what their customers want*
>
>You have only one type of customer?

No, but our statistics cover 100% of all Rackspace customers' use cases
for LBaaS (based on current usage and feature requests) -- that's the
whole point of the stats gathering we did. We didn't just pick a couple of
customers and look at their loadbalancers to decide what use cases to
propose, which seems to be what you're implying?

>
>, since that is the
>> supposed purpose of all of this, right? We're supposed to be deciding
>> which use-cases matter *to our customers*,
>
>Yep, and there are many different types of customers even within a
>single company. I'm sure you don't assume that RAX Public Cloud
>customers have the same needs of RAX private cloud or enterprise hosting
>customers. At the same time, is there a single person at RAX that can
>adequately speak for all those segments? As a former Racker, I can
>remember meeting no such person.

We don't assume anything -- our team did extensive stats gathering for
*ALL* types of customers, and that is what our statistics (which are based
on hard data) reflect. So, at this point, I would say that we can in fact
speak definitively on this subject for our organization.

>
>  so there should be no real
>> variance for what I would vote versus what my teammates would vote,
>>since
>> we have the same customersŠ
>
>And there are multiple teams at Rackspace, no?

With regard to LBaaS, it is only our team (CLB) and the team that handles
hardware LBs (F5, etc), and this falls pretty cleanly in the CLB domain.

>
>> Also, if we are using this as a type of voting mechanism then interests
>>of
>> large/vocal organizations drown out smaller organizations. If this is
>> being used as a voting mechanism then how do you suggest we weight votes
>> for smaller companies so that we do not alienate them from further
>> voting/discussions?
>
>Through consensus and discussion, same as any other OpenStack project.
>
>Best,
>-jay
>
>> Cheers,
>> --Jorge
>>
>>
>>
>>
>> On 5/6/14 1:52 PM, "Jay Pipes" <jaypipes at gmail.com> wrote:
>>
>>> On 05/06/2014 02:42 PM, Jorge Miramontes wrote:
>>>> Sam,
>>>>
>>>> I'm assuming you want one person from each company to answer correct?
>>>> I'm pretty sure people in each organization will vote the sameŠat
>>>>least
>>>> I'd hope!
>>>
>>> I'd hope not! :)
>>>
>>> Even within the same organization or company, we all have different
>>> ideas on use cases, the appropriateness of certain things "in the
>>> cloud", and the role of a load balancer service in the general mix of
>>> things.
>>>
>>> I certainly would hope that lots of Mirantis engineers other than
>>>myself
>>> fill out the use case survey and offer their own insights.
>>>
>>> Best,
>>> -jay
>>>
>>> _______________________________________________
>>> 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