Difference between revisions of "ApiFlow"
Line 5: | Line 5: | ||
[[Image:ApiFlow$api.png]] | [[Image:ApiFlow$api.png]] | ||
− | * HTTP API | + | * HTTP API Authentication Middleware |
** Already in place | ** Already in place | ||
** nova.api.openstack.auth:[[AuthMiddleware]] | ** nova.api.openstack.auth:[[AuthMiddleware]] | ||
** '''No proposed changes.''' | ** '''No proposed changes.''' | ||
− | * HTTP API | + | * HTTP API Rate Limiting Middleware |
** Already in place | ** Already in place | ||
** nova.api.openstack.ratelimiting:[[RateLimitingMiddleware]] | ** nova.api.openstack.ratelimiting:[[RateLimitingMiddleware]] | ||
** '''Proposed changes:''' | ** '''Proposed changes:''' | ||
*** Test | *** Test |
Revision as of 21:47, 7 February 2011
API Flow Proposal
As an example I'll detail a user's POST request to the /servers module. Historically this was a very intensive and heavily monitor action and as such heavy rate limits were imposed.
- HTTP API Authentication Middleware
- Already in place
- nova.api.openstack.auth:AuthMiddleware
- No proposed changes.
- HTTP API Rate Limiting Middleware
- Already in place
- nova.api.openstack.ratelimiting:RateLimitingMiddleware
- Proposed changes:
- Test