Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1079141

Summary: [RFE][cinder]: Cinder Pagination Sorting Enhancements
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-cinderAssignee: Eric Harney <eharney>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: eharney, markmc, scohen, yeylon
Target Milestone: Upstream M3Keywords: FutureFeature, OtherQA
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/cinder/+spec/cinder-pagination
Whiteboard: upstream_milestone_kilo-3 upstream_definition_approved upstream_status_implemented
Fixed In Version: openstack-cinder-2015.1.0-2.el7ost Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-05 13:11:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-03-21 04:30:14 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/cinder/+spec/cinder-pagination.

Description:

Currently, the pagination support for Cinder allows the caller to specify a single sort key and sort direction.  This blueprint enhances the pagination support for the /volumes and /volumes/detail APIs so that multiple sort keys and sort directions can be supplied on the request.

The database layer already supports multiple sort keys and directions.  This blueprint will update the API layer to retrieve the sort information from the API request and pass that information down to the database layer.

Specification URL (additional information):

https://wiki.openstack.org/wiki/Cinder_Pagination

Comment 7 errata-xmlrpc 2015-08-05 13:11:49 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-2015:1548