OpenStack rate limit validation doesn't reveal potential problems about docs-deploying-cf HOT 7 CLOSED

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/121205093

The labels on this github issue will be updated when the story is started.

from docs-deploying-cf.

Hi @loewenstein! I just saw this slack thread and wanted to follow up with you https://cloudfoundry.slack.com/archives/cf-docs/p1465928312000007. Do you have any updates surrounding this issue?

from docs-deploying-cf.

No. Unfortunately I did not get any response yet.

from docs-deploying-cf.

Hello @loewenstein, if you haven't heard anything back, I think I'm going to go ahead an close this issue. But please feel free to re-open if you get any new information!

from docs-deploying-cf.

Hi @ljarzynski,

The current description in the docu is apparently pretty useless (though harmless as well).

1. The code snippet executes the REST call once instead of a 100 times (at least for recent versions of fog).
2. Recent versions of OpenStack have no rate limit for GET requests and a default of 120/minute for other requests.
   Thus I would remove (or at least adapt) the docu unless you can trace down the origin of that requirement and figure out that it indeed still applies.

My 2 cents.

Regards
Jan

from docs-deploying-cf.

@loewenstein That is helpful! I'll figure out who I can talk to about this.

from docs-deploying-cf.

Closing this issue as we received the following explanation:

"I don't know how we came to that example to validate the API rate limit. It never make sense, even on previous OpenStack versions, the default rate limit for GET request was higher than 100req/sec, it only makes sense to validate POST request. I remember that we were hit frequently when updating the server metadata, so maybe this is a better validation."

Docs will be updated via PR.

from docs-deploying-cf.