Table filtering using API query attributes

Registered by Justin Pomeroy on 2014-03-12

The table filtering currently performed on paged tables can be very misleading because it only filters the current page of data. This blueprint would add support for filtering these tables using API query attributes so that the filtering is performed on all the data even if only a single page will be returned.

The available filters and filtering behavior would depend on API support, which is currently inconsistent. For example, nova servers can be filtered by name using a regular expression, but glance images can only be filtered by name using an exact match. So there is room for improvement.

API filtering would be added to the admin images, admin instances, and project instances tables.

Blueprint information

Status:
Complete
Approver:
David Lyle
Priority:
Medium
Drafter:
Justin Pomeroy
Direction:
Approved
Assignee:
Justin Pomeroy
Definition:
Approved
Series goal:
Accepted for juno
Implementation:
Implemented
Milestone target:
milestone icon 2014.2
Started by
Justin Pomeroy on 2014-03-19
Completed by
David Lyle on 2014-09-02

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/table-filtering-by-api-query,n,z

Addressed by: https://review.openstack.org/81574
    Add API filtering to paged tables

[david-lyle | 2014.07.23] Moving to Juno-3.

[mrunge | 2014.08.25]
Looks like https://review.openstack.org/112744 is not included yet.
resetting implementation status

Gerrit topic: https://review.openstack.org/#q,topic:bug/1321483,n,z

[david-lyle 2014.09.01] Marking as implemented. The identity patch is not required for this blueprint, but instead enabled by it.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.