Bug 1403322

Summary: [RFE] Complete sorting in horizon across pagination
Product: Red Hat OpenStack Reporter: Andreas Karis <akaris>
Component: python-django-horizonAssignee: Radomir Dopieralski <rdopiera>
Status: CLOSED WONTFIX QA Contact: Ido Ovadia <iovadia>
Severity: low Docs Contact:
Priority: low    
Version: 9.0 (Mitaka)CC: athomas, beth.white, mrunge, opavlenk, srevivo
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: NeedsAllocation
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-13 16:21:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Andreas Karis 2016-12-09 16:15:26 UTC 
Description of problem:
You can only sort a single page of results in Horizon's GUI.  Customers want to be able to sort the whole column at once.

A example is finding all the "public" glance images. Customer has do this on each page vs sorting on the first page for all in the state that he/she is looking for. One can do this VIA the CLI but a GUI helps end users.

What information can you provide around timeframes and urgency?

Low (a update on if its going to be included in OSP9 is fine)

Customer comment:
This has been a issue for us since Icehouse (OSP5)  and we were sad to see it not be fixed by now. I do understand the issue as to why it snot  but having a config switch to flip would be awesome (it might exist )if its not default.

Version-Release number of selected component (if applicable):
wanted for OSP 9

Additional info:
Upstream bug:
https://bugs.launchpad.net/horizon/+bug/1473117

Related bugzillas:
https://bugzilla.redhat.com/show_bug.cgi?id=1272424
Comment 1 Andreas Karis 2016-12-09 16:20:35 UTC 
If it's not possible to sort this server side, would a client side filter be an option?
Comment 2 Radomir Dopieralski 2016-12-12 07:42:04 UTC 
To do proper sorting client-side, the browser would need to retrieve complete set of data (often thousands of entries) bypassing pagination. This introduces problems with efficiency and scaling. We already have problems with some views that get too much data at once from the services and can thus bring them down to their kness -- for instance https://bugzilla.redhat.com/show_bug.cgi?id=1318250

To do sorting on the server side, the given API call has to support that on the side of the service. This depends on the service and the particular API call. There is some work on some services to add support for this (also for pagination), but this is rather low priority and slow (especially since it involves API changes).

We do hope to get it all sorted out (no pun intended) eventually, but it will take some time to do it for all possible views. In the mean time, if the customer specified which views they want fixed in the first order, we could prioritize those and reach out to the teams working on those services, asking to for the necessary changes in the API.
Comment 8 Beth White 2018-03-13 16:21:01 UTC 
The behavior you describe would be desirable, but for most services is not available. Many service APIs in OpenStack do not support sorting results. The remaining option would be for Horizon to try and pull the entire data set from the API pass it down to the client for sorting. This is not practical. The column sorting functionality is intended to be client side only, and thus just a sort of the items on the page. In the future, should searchlight become more mature, it is conceivable that Horizon could provide the option you are asking for, but that is down the road.