| 2017-09-21 03:35:05 |
Zhenyu Zheng |
description |
TBA |
In https://blueprints.launchpad.net/nova/+spec/cells-count-resources-to-check-quota-in-api
we introduced a new workflow of Quota checks. It is possible that concurrent requests can
pass API layer checks, but blocked by conductor layer checks.
This can actually trigger user-noticeable API behavior changes:
As an user, previously, If my request is blocked by quota checks, I will get HTTP 409 response, and no instance records will be left.
After the above mentioned change, it is possible that when my requests failed at conductor layer Quota check and I got an instance in ERROR state. And in an busy cloud, users may
got a lot of ERROR instances according to this and the instance number may beyond the limit.
We should at least mention this behavior change in the release note. |
|
| 2017-09-22 06:41:30 |
Zhenyu Zheng |
description |
In https://blueprints.launchpad.net/nova/+spec/cells-count-resources-to-check-quota-in-api
we introduced a new workflow of Quota checks. It is possible that concurrent requests can
pass API layer checks, but blocked by conductor layer checks.
This can actually trigger user-noticeable API behavior changes:
As an user, previously, If my request is blocked by quota checks, I will get HTTP 409 response, and no instance records will be left.
After the above mentioned change, it is possible that when my requests failed at conductor layer Quota check and I got an instance in ERROR state. And in an busy cloud, users may
got a lot of ERROR instances according to this and the instance number may beyond the limit.
We should at least mention this behavior change in the release note. |
In https://blueprints.launchpad.net/nova/+spec/cells-count-resources-to-check-quota-in-api
we introduced a new workflow of Quota checks. It is possible that concurrent requests can
pass API layer checks, but blocked by conductor layer checks.
This can actually trigger user-noticeable API behavior changes:
As an user, previously, If my request is blocked by quota checks, I will get HTTP 403 response, and no instance records will be left.
After the above mentioned change, it is possible that when my requests failed at conductor layer Quota check and I got an instance in ERROR state. And in an busy cloud, users may
got a lot of ERROR instances according to this and the instance number may beyond the limit.
We should at least mention this behavior change in the release note. |
|
