Increase nova rate limits

[Matthew Mosesohn]

The defaults are too small to run any benchmarking tests. We ought to increase our rate limits by an order of magnitude (or offer an option to disable nova rate limits when deploying)

[Dmitry Borodaenko (angdraug)]

At the very least we should document how the rate limits can be changed or lifted. Depending on how much damage an overloaded nova service can do, shipping with limits disabled by default might expose customers to risks of breakage, DoS attacks or worse, so not a good idea unless we can prove the opposite.

[Dmitry Ilyin (idv1985)]

Just edit these structures is site.pp

$nova_rate_limits = {
  'POST' => 1000,
  'POST_SERVERS' => 1000,
  'PUT' => 1000, 'GET' => 1000,
  'DELETE' => 1000
}
$cinder_rate_limits = {
  'POST' => 1000,
  'POST_SERVERS' => 1000,
  'PUT' => 1000, 'GET' => 1000,
  'DELETE' => 1000
}

[Ivan Kolodyazhny (e0ne)]

How much should we increase nova and cinder rate limits? They are such as Dmitry provided now.

[Ivan Kolodyazhny (e0ne)]

As decided in discussion with Matthew, we should change rate limits to 100 000.

[Openstack Gerrit (openstack-gerrit)]

Fix proposed to branch: master
Review: https://review.openstack.org/89550

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/89550
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=b5c5e84a89cd7dec03c65301a445bb930219a3d6
Submitter: Jenkins
Branch: master

commit b5c5e84a89cd7dec03c65301a445bb930219a3d6
Author: Ivan Kolodyazhny <email address hidden>
Date: Tue Apr 22 15:41:35 2014 +0300

    Increase nova and cinder rate limits

    Change-Id: Ibacec6d2294583237233050ffe20a926a375b620
    Closes: bug #1272839