diff --git a/doc/source/admin/cells.rst b/doc/source/admin/cells.rst index 293ada87f7..fd7422becb 100644 --- a/doc/source/admin/cells.rst +++ b/doc/source/admin/cells.rst @@ -57,7 +57,7 @@ for details on command usage. Known issues ~~~~~~~~~~~~ -#. **Services and Performance:** In case a cell is down during the startup of nova +1. **Services and Performance:** In case a cell is down during the startup of nova services, there is the chance that the services hang because of not being able to connect to all the cell databases that might be required for certain calculations and initializations. An example scenario of this situation is if @@ -73,7 +73,9 @@ Known issues "slowness" may be experienced in operations requiring hitting all the cells because of the aforementioned configurable timeout/retry values. -#. **Counting Quotas:** Another known issue is in the current approach of counting +.. _cells-counting-quotas: + +2. **Counting Quotas:** Another known issue is in the current approach of counting quotas where we query each cell database to get the used resources and aggregate them which makes it sensitive to temporary cell outages. While the cell is unavailable, we cannot count resource usage residing in that cell database and diff --git a/doc/source/user/quotas.rst b/doc/source/user/quotas.rst index 0d13f86373..a0984833fb 100644 --- a/doc/source/user/quotas.rst +++ b/doc/source/user/quotas.rst @@ -60,6 +60,7 @@ checks are made in order: the database manually as there is no REST API for removing quota class values from the database. +.. _quota-usage-from-placement: Quota usage from placement ========================== @@ -124,10 +125,9 @@ placement: Known issues ============ -TODO: talk about quotas getting out of sync and `how to recover`_ - -.. _how to recover: https://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/refresh-quotas-usage.html - +If not :ref:`counting quota usage from placement ` +it is possible for down or poor performing cells to impact quota calculations. +See the :ref:`cells documentation ` for details. Future plans ============