Bug 1352922

Summary:	[RFE] Simple Tenant Usage Pagination Support
Product:	Red Hat OpenStack	Reporter:	Eoghan Glynn <eglynn>
Component:	openstack-nova	Assignee:	Diana Clarke <dclarke>
Status:	CLOSED ERRATA	QA Contact:	Joe H. Rahme <jhakimra>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	11.0 (Ocata)	CC:	berrange, dasmith, dclarke, eglynn, kchamart, lruzicka, nlevinki, panbalag, sbauza, sclewis, sferdjao, sgordon, srevivo, vromanso
Target Milestone:	Upstream M3	Keywords:	FutureFeature, Triaged
Target Release:	11.0 (Ocata)	Flags:	panbalag: needinfo+
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/paginate-simple-tenant-usage
Whiteboard:	upstream_milestone_ocata-3 upstream_definition_approved upstream_status_implemented
Fixed In Version:		Doc Type:	Release Note
Doc Text:	This release adds pagination support to avoid resource-consuming usage requests on systems with a large number of instances. The v2.40 microversion of the nova API simple-tenant-usage endpoints use new optional query parameters 'limit' and 'marker' for pagination. The 'marker' option sets the starting point and the 'limit' option sets the number of records to be displayed after the starting point. If 'limit' is not set, nova will use the configurable 'max_limit' (1000 by default). Although older microversions will not accept these new query parameters, they will start to enforce the max_limit and results may be truncated as a result. Consider using the new microversion to avoid DoS-like usage requests and potentially truncated responses.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-17 19:31:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1427448

Description Eoghan Glynn 2016-07-05 13:39:03 UTC

The simple tenant usage API can return extremely large amounts of data and provides no way to paginate the results. Because the API does not use the pagination code, it doesn't even respect the "max results" sanity limit. Because it can query a ton of data, it also causes the api workers to inflate their memory footprint to the size of the DB result set, which is large. Since horizon queries this by default, most users are affected unless their ops team is extremely diligent about purging deleted instances (which are returned by the API by design).

Cloned from https://blueprints.launchpad.net/nova/+spec/paginate-simple-tenant-usage

Comment 2 Stephen Gordon 2016-11-25 14:45:50 UTC

Hi Prasanth,

Can I please get a QA ack for this one?

Thanks,

Steve

Comment 13 Joe H. Rahme 2017-04-18 10:13:30 UTC

Hey Lukas,

You're correct. The `marker` is the last instance UUID in the `server_usages` list from the previous page.

Comment 15 errata-xmlrpc 2017-05-17 19:31:29 UTC

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.

https://access.redhat.com/errata/RHEA-2017:1245