Open Stack

Shamail,

It's really quite hard thing to standardize because there are few
dimensions:
- Amount of resources (VMs, Volumes, Images, ... of service),
- Amount of active users (how ofter resource are created/deleted),
- Size of cloud (amount of nodes)
- Cloud deployment architecture
- ...

What I believe is that we should standardize:

- Amount of  resource per service per node
- Typical sizes of cloud: 10, 20, 50, 100, ... nodes
- Workloads that we should be run:
   For example In Rally team we are trying to standardize them here:
   https://github.com/openstack/rally/tree/master/certification/openstack
- Deployment Reference Architecture
- Somebody should find enough resources to run at least for each release
  those tests on real hardware

And create depending on this few scale tags:
works-on-X-scale


Best regards,
Boris Pavlovic

On Sat, Sep 26, 2015 at 5:19 PM, Boris Pavlovic <bpavlovic at mirantis.com>
wrote:

> Shamail,
>
> It's really quite hard thing to standardize because there are few
> dimensions:
> - Amount of resources (VMs, Volumes, Images, ... of service),
> - Amount of active users (how ofter resource are created/deleted),
> - Size of cloud (amount of nodes)
> - Cloud deployment architecture
> - ...
>
> What I believe is that we should standardize:
>
> - Amount of  resource per service per node
> - Typical sizes of cloud: 10, 20, 50, 100, ... nodes
> - Workloads that we should be run:
>    For example In Rally team we are trying to standardize them here:
>    https://github.com/openstack/rally/tree/master/certification/openstack
> - Deployment Reference Architecture
> - Somebody should find enough resources to run at least for each release
>   those tests on real hardware
>
> And create depending on this few scale tags:
> works-on-X-scale
>
>
> Best regards,
> Boris Pavlovic
>
> On Sat, Sep 26, 2015 at 11:40 AM, Shamail <itzshamail at gmail.com> wrote:
>
>> Hi Large Deployments Team,
>>
>> The ops-tags team was brainstorming potential future tags at our last
>> meeting and one topic of interest was to express the "scale" a service can
>> operate at via tags.
>>
>> Scale, of course, can imply several different dimensions (not to mention
>> test types).  We figured who better to talk to about the definition of
>> scale than the large deployment team.  :-)
>>
>> Can you please help us understand how your team classifies a deployment
>> as being large?  I recall that, in the initial discussions, LDT was using
>> the number of nodes.  Is this still the case?  Does large deployment factor
>> in things such as throughout requirements, number of networks, number of
>> volumes, etc. when deciding if a deployment is "large"?
>>
>> Thanks in advance for your help.  If it makes more sense to discuss this
>> topic at the next LDT meeting then I would be glad to join.
>>
>> Thank you,
>> Shamail Tahir
>> t: @ShamailXD
>> tz: EST
>>
>>
>>
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150926/d8beb8b4/attachment.html>