← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1386764] [NEW] Volumes tables need to support API filtering

 

Public bug reported:

In both Projects and Admin, the Volumes table does not support API
filtering.

The filtering that is currently in each table is only client-side, so it
only filters the table that was loaded into the browser. However, the
Cinder API supports filtering that operates on the entire dataset. This
filtering should be surfaced in the UI. Name and Status are bother
filterable. There is also a blueprint to add volume type:
https://blueprints.launchpad.net/cinder/+spec/list-volume-types-filters

This is how Horizon handles filtering for Nova Instances works, and for
Keystone Users.

** Affects: horizon
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1386764

Title:
  Volumes tables need to support API filtering

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  In both Projects and Admin, the Volumes table does not support API
  filtering.

  The filtering that is currently in each table is only client-side, so
  it only filters the table that was loaded into the browser. However,
  the Cinder API supports filtering that operates on the entire dataset.
  This filtering should be surfaced in the UI. Name and Status are
  bother filterable. There is also a blueprint to add volume type:
  https://blueprints.launchpad.net/cinder/+spec/list-volume-types-
  filters

  This is how Horizon handles filtering for Nova Instances works, and
  for Keystone Users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1386764/+subscriptions


Follow ups

References