As a quick note the api-ref you are linking to has some gaps/has not been kept in sync with the official api specifications.
The official API specification is located at http://specs.openstack.org/openstack/keystone-specs/ (v2 and v3 sections at the top) and there is a known open bug to work with the docs team to get this in sync (somehow). Unfortunately there are a number of cases especially with the identity backend where pagination just does not work (or works completely unreliably) such as utilizing the ldap driver. Either a cursor must be maintained (problematic in REST) or the results could be wildly different every single request meaning each page is not really guaranteed to be the "next page" it could be the same/show inconsistent results. The second issue is that the pagination is not a good UX even where it works - the simple question is: if you can filter the results how many pages deep do you go before refining the query; think of your use of search engines. In light of these issues Keystone has opted for a filter / limit (config). If the results exceed the limit there is a truncation that occurs and it is recommended extra filtering be applied to reduce the total number of results. This discussion has gone around a few times, pagination in keystone is not currently on the roadmap. In addition to the above doc bug, we should work to better socialize this filter-over-paginate methodology. --Morgan Sent via mobile > On Aug 14, 2015, at 05:46, Timur Sufiev <[email protected]> wrote: > > Hello, Keystone folks! > > I've just discovered an unfortunate fact that Horizon pagination for > Tenants/Projects list that worked with Keystone v2 doesn't work with Keysone > v3 anymore - its API call simply lacks the 'marker' and 'limit' parameters > [1] that Horizon is relying upon. Meanwhile having looked through [2] and [3] > I'm a bit confused: while Keystone v3 API states it supports [2] pagination > for every kind of entities (by using 'page' and 'per_page' parameters), the > related blueprint [3] is not yet approved, meaning that most likely the API > implementation did not make it into existing Keystone codebase. So I wonder > whether there are some plans to implement pagination for Keystone API calls > that list its entities? > > P.S. I'm aware of SearchLight project that tries to help Horizon with other > OpenStack APIs (part of its mission), what I'm trying to understand here is > are we going to have some fallback pagination mechanism for Horizon's > Identity in a short-term/mid-term perspective. > > [1] http://developer.openstack.org/api-ref-identity-admin-v2.html > [2] http://developer.openstack.org/api-ref-identity-v3.html > [3] https://blueprints.launchpad.net/keystone/+spec/pagination > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
