Bug 1201116

Summary:	[RFE][glance]: Glance Sorting Enhancements
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-glance	Assignee:	Flavio Percoco <fpercoco>
Status:	CLOSED ERRATA	QA Contact:	nlevinki <nlevinki>
Severity:	urgent	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	dnavale, eglynn, fpercoco, markmc, scohen, yeylon
Target Milestone:	Upstream M3	Keywords:	FutureFeature, OtherQA
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/glance/+spec/glance-sorting-enhancements
Whiteboard:	upstream_milestone_kilo-3 upstream_definition_approved upstream_status_implemented
Fixed In Version:	openstack-glance-2015.1.0-6.el7ost	Doc Type:	Enhancement
Doc Text:	With this change, it is now possible to filter the list operations by more than one filter option and in multiple directions. For example: /images?sort=status:asc,name:asc,created_at:desc With the above, a list of images will be returned and they will be sorted by status, name, and creation date with the following directions respectively: ascending, ascending, and descending.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:22:17 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 2015-03-12 04:09:50 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/glance/+spec/glance-sorting-enhancements.

Description:

Currently, the sorting support for Glance allows the caller to specify
multiple sort keys and one sort direction. This blueprint enhances the
sorting support for the /images and /images/detail APIs so that
multiple sort keys and sort directions can be supplied on the request.

Specification URL (additional information):

https://review.openstack.org/#/c/155841/

Comment 6 errata-xmlrpc 2015-08-05 13:22:17 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