1. Proposed title of this feature request Pagination support for cinder snapshot-list 3. What is the nature and description of the request? If there are large number of cinder snapshots (for ex. 37k) then, returning this much data is not feasible from a performance perspective, so the osapi_max_limit configuration parameter, which defines the maximum number of entries that can be returned from an API call has been returned to the default of 1000. In the case of Cinder volumes, returning the full set of volumes requires multiple API calls, which use pagination to retrieve the data. However pagination support for cinder snapshots does not appear to be present in the API.
Changing to RFE. Someone upstream already proposed a blueprint [1], but the work is not started yet. [1] https://blueprints.launchpad.net/cinder/+spec/snapshots-and-bakcup-support-pagination-query
Server side is implemented. Still waiting for the client implementation.
We still have to implement the cinderclient part of that feature, which probably is backportable, but meantime moving this RFE to 9.0.
cinderclient part is addressed by: https://review.openstack.org/225582
cinderclient patch didn't make it for Liberty, I am working to backport it downstream in order to complete the feature in 8.0
Link to polarion test-plan: https://polarion.engineering.redhat.com/polarion/#/project/RHELOpenStackPlatform/wiki/Cinder/RFE-1214230-Pagination%20support%20for%20cinder%20snapshot-list
Tested using: python-cinderclient-1.5.0-1.el7ost.noarch openstack-cinder-7.0.1-6.el7ost.noarch python-cinder-7.0.1-6.el7ost.noarch Tested according to following polarion test-plan: https://polarion.engineering.redhat.com/polarion/#/project/RHELOpenStackPlatform/wiki/Cinder/RFE-1214230-Pagination%20support%20for%20cinder%20snapshot-list There is one failure while using 'sort' argument, describe in the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1310401
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://rhn.redhat.com/errata/RHEA-2016-0603.html