[Openstack-operators] [Large Deployments Team][Tags] Ops Tag for "Scale"

Shamail Tahir itzshamail at gmail.com
Sun Sep 27 17:57:00 UTC 2015

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

> 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

+1, the intention of this email was to get the initial criteria used by the
LDT team to qualify a "large deployment".

We will need to factor in the dimensions as well as establishing a baseline
RA/testing criteria for validation eventually.  Do you think that we should
bring up the "test scale on real HW" with the OpenStack Innovation Center
(OSIC) team since they will have multiple clusters running with 1K nodes
eventually?  I think Clint's reply ties in well with yours (establish
tests, deployment model for testing, and benchmark workloads).

> 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

Shamail Tahir
t: @ShamailXD
tz: Eastern Time
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150927/996641e6/attachment.html>

More information about the OpenStack-operators mailing list