Bug 1041865

Summary:	[RFE][keystone]: Provide ability for length of list responses to be limited
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-keystone	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED ERRATA	QA Contact:	Udi Kalifon <ukalifon>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	aberezin, ayoung, breeler, ddomingo, markmc, nkinder, slong, ukalifon, yeylon
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/keystone/+spec/list-limiting
Whiteboard:	upstream_milestone_icehouse-3 upstream_status_implemented upstream_definition_approved
Fixed In Version:	openstack-keystone-2014.1-4.el7ost	Doc Type:	Enhancement
Doc Text:	A change was introduced to limit the number of results returned by list commands. This was done to avoid problems when the number of results can be larger than available memory. For example, a user list on a system where there are millions of users would return all of them. Now users can provide a configuration value (list_limit=[integer value]) on calls to the Identity API list functions. Lists that have values beyond those limits will return a 'truncated' value in the body of the results.	Story Points:	---
Clone Of:
Clones:	1081959 (view as bug list)		Environment:
Last Closed:	2014-07-08 15:24:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1081959

Description RHOS Integration 2013-12-12 19:46:52 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/list-limiting.

Description:

It should be possible for a cloud provider to optional set a limit of the maximum number of records that will be returned, ensuring that poorly filtered queries do not take excessive time.

Like filtering, this should be enabled in the backends wherever possible to allow this to be passed to the underlying subsystem (e.g SQL)

Specification URL (additional information):

None

Comment 2 Udi Kalifon 2014-04-27 10:36:05 UTC

Setting list_limit in keystone.conf indeed limits the length of the returned results. However, I can't find documentation on how to query for the remainder of the list that was truncated. There should be something that I can add to the URL, like "?part=2", to get the next batch of results etc... What's the query form, please?

Comment 9 errata-xmlrpc 2014-07-08 15:24:03 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.

http://rhn.redhat.com/errata/RHEA-2014-0854.html