Bug 1041905 - [RFE][keystone]: Extend pagination into the identity backends wherever possible to improve scaling and performance
Summary: [RFE][keystone]: Extend pagination into the identity backends wherever possib...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/keys...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 20:00 UTC by RHOS Integration
Modified: 2016-02-29 14:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:02:21 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 20:00:13 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/pagination-backend-support.

Description:

In v3, our identity APIs support pagination.  However, such pagination support is only skin deep - in that the controller re-fetches the entire list upon each "get next page" request from the client.  We should therefore extend the pagination into the backends (e.g. SQLAlchemy supports such a concept) to improve the scaling and performance of keystone.

A good pagination system will still require good filtering.  The addition of this is covered by a separate blueprint (https://blueprints.launchpad.net/keystone/+spec/filtering-backend-support)

Related wishlist bug: https://bugs.launchpad.net/keystone/+bug/1009023

Specification URL (additional information):

https://etherpad.openstack.org/pagination


Note You need to log in before you can comment on or make changes to this bug.