Open Stack

Bruno,

Btw great idea add benchmark scenarios for quotas as well!

Best regards,
Boris Pavlovic


On Fri, Apr 4, 2014 at 7:28 PM, Bruno Semperlotti <
bruno.semperlotti at gmail.com> wrote:

> Hi Joshua,
>
> Quotas will not be expanded during the scenario, they will be updated
> *prior* the scenario with the requested values as context of this
> scenario. If values are too low, the scenario will continue to fail.
> This update does not allow to benchmark quotas update modification time.
>
> Regards,
>
>
> --
> Bruno Semperlotti
>
>
> 2014-04-04 0:45 GMT+02:00 Joshua Harlow <harlowja at yahoo-inc.com>:
>
>  Cool, so would that mean that once a quota is reached (for whatever
>> reason) and the scenario wants to continue running (instead of failing due
>> to quota issues) that it can expand that quota automatically (for cases
>> where this is needed/necessary). Or is this also useful for benchmarking
>> how fast quotas can be  changed, or is it maybe a combination of both?
>>
>>   From: Boris Pavlovic <boris at pavlovic.me>
>> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>> <openstack-dev at lists.openstack.org>
>> Date: Thursday, April 3, 2014 at 1:43 PM
>> To: "OpenStack Development Mailing List (not for usage questions)" <
>> openstack-dev at lists.openstack.org>
>> Subject: Re: [openstack-dev] [rally] Tenant quotas can now be updated
>> during a benchmark
>>
>>   Bruno,
>>
>>  Well done. Finally we have this feature in Rally!
>>
>>
>>  Best regards,
>> Boris Pavlovic
>>
>>
>> On Thu, Apr 3, 2014 at 11:37 PM, Bruno Semperlotti <
>> bruno.semperlotti at gmail.com> wrote:
>>
>>> Hi Rally users,
>>>
>>>  I would like to inform you that the feature allowing to update
>>> tenant's quotas during a benchmark is available with the implementation of
>>> this blueprint:
>>> https://blueprints.launchpad.net/rally/+spec/benchmark-context-tenant-quotas
>>>
>>>  Currently, only Nova and Cinder quotas are supported (Neutron coming
>>> soon).
>>>
>>>  Here a small sample of how to do it:
>>>
>>>  In the json file describing the benchmark scenario, use the "context"
>>> section to indicate quotas for each service. Quotas will be applied for
>>> each generated tenants.
>>>
>>>   {
>>>      "NovaServers.boot_server": [
>>>          {
>>>              "args": {
>>>                  "flavor_id": "1",
>>>                  "image_id": "6e25e859-2015-4c6b-9940-aa21b2ab8ab2"
>>>              },
>>>              "runner": {
>>>                  "type": "continuous",
>>>                  "times":100,
>>>                  "active_users": 10
>>>              },
>>>              "context": {
>>>                  "users": {
>>>                      "tenants": 1,
>>>                      "users_per_tenant": 1
>>>                  },
>>>                  *"quotas": {*
>>>  *                    "nova": {*
>>>  *                        "instances": 150,*
>>>  *                        "cores": 150,*
>>>  *                        "ram": -1*
>>>  *                    }*
>>>  *                }*
>>>              }
>>>          }
>>>      ]
>>>  }
>>>
>>>
>>>  Following, the list of supported quotas:
>>> *nova:*
>>>  instances, cores, ram, floating-ips, fixed-ips, metadata-items,
>>> injected-files, injected-file-content-bytes, injected-file-path-bytes,
>>> key-pairs, security-groups, security-group-rules
>>>
>>>  *cinder:*
>>>  gigabytes, snapshots, volumes
>>>
>>>  *neutron (coming soon):*
>>>  network, subnet, port, router, floatingip, security-group,
>>> security-group-rule
>>>
>>>
>>>  Regards,
>>>
>>> --
>>> Bruno Semperlotti
>>>
>>> _______________________________________________
>>> 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/20140404/868d3248/attachment.html>