| 2021-09-05 02:27:57 |
Takashi Kajinami |
bug |
|
|
added bug |
| 2021-09-05 02:28:56 |
Takashi Kajinami |
description |
# This might not be the best place to discuss this but I hope this can initiate some discussion.
Currently RateLimitingMiddleware belongs to v2 API code, which is located under cinder.api.v2.
Ideally we should migrate this to v3 API code but there are some points we should consider
before we determine to keep that middleware.
- The middleware is not included in the pre-defined pipelines in api-paste.ini .
- The middleware was ported from Nova but Nova has already dropped the middleware
- The middleware uses local memory to count API frequency. Which means it doesn't work
properly in deployments with multiple nodes hosting cinder-api.
Considering this situation, it'd make more sense to deprecate/remove the middleware instad of keeping it under v3 API code. |
# This might not be the best place to discuss this but I hope this can initiate some discussion.
Currently RateLimitingMiddleware belongs to v2 API code, which is located under cinder.api.v2.
Ideally we should migrate this to v3 API code but there are some points we should consider
before we determine to keep that middleware.
- The middleware is not included in the pre-defined pipelines in api-paste.ini .
- The middleware was ported from Nova but Nova has already dropped the middleware
- The middleware uses local memory to count API frequency. Which means it doesn't work
properly in deployments with multiple nodes hosting cinder-api.
Considering these situations, it'd make more sense to deprecate/remove the middleware instad of keeping it under v3 API code. |
|
| 2021-09-05 02:50:31 |
OpenStack Infra |
cinder: status |
New |
In Progress |
|
| 2021-09-05 02:52:13 |
Takashi Kajinami |
description |
# This might not be the best place to discuss this but I hope this can initiate some discussion.
Currently RateLimitingMiddleware belongs to v2 API code, which is located under cinder.api.v2.
Ideally we should migrate this to v3 API code but there are some points we should consider
before we determine to keep that middleware.
- The middleware is not included in the pre-defined pipelines in api-paste.ini .
- The middleware was ported from Nova but Nova has already dropped the middleware
- The middleware uses local memory to count API frequency. Which means it doesn't work
properly in deployments with multiple nodes hosting cinder-api.
Considering these situations, it'd make more sense to deprecate/remove the middleware instad of keeping it under v3 API code. |
# This might not be the best place to discuss this but I hope this can initiate some discussion.
Currently RateLimitingMiddleware belongs to v2 API code, which is located under cinder.api.v2.
Ideally we should migrate this to v3 API code but there are some points we should consider before we determine to keep that middleware.
- The middleware is not included in the pre-defined pipelines in api-paste.ini .
- The middleware was ported from Nova but Nova has already dropped the middleware
- The middleware uses local memory to count API frequency. Which means it doesn't work properly in deployments with multiple nodes hosting cinder-api.
Considering these situations, it'd make more sense to deprecate/remove the middleware instead of keeping it under v3 API code. |
|
| 2021-09-05 02:52:20 |
Takashi Kajinami |
cinder: assignee |
|
Takashi Kajinami (kajinamit) |
|
| 2021-09-08 12:40:36 |
Sofia Enriquez |
cinder: importance |
Undecided |
High |
|
| 2021-09-08 12:46:28 |
Sofia Enriquez |
tags |
|
api |
|
| 2021-09-08 12:46:38 |
Sofia Enriquez |
tags |
api |
api v2 v3 |
|
| 2021-09-08 14:23:41 |
Sofia Enriquez |
cinder: importance |
High |
Medium |
|
