To avoid memory bloat issues in the nova-api workers, the nova project is planning to add pagination logic to the simple-tenant-usage API extension in Ocata:
In order to avoid continuing to DOS the nova-api tier, Horizon will need to support this new pagination scheme by traversing between pages via the next link, then subsequently stitching back up the response such that the server_usages list for each tenant is made whole (such lists may cross page boundaries under the proposed solution).
Notes for using the API:
Places that will probably need changing:
A draft patch https://review.openstack.org/#/c/410337/
We still need to resolve a problem with specifying the API version https://review.openstack.org/#/c/410688/ and make Horizon load the correct microversion of the Nova API.
We also need to write tests for all this.
This feature is not visible to the users and as such can't be easily tested. The improvements in performance are not visible in small scale deployments.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.