Angularize Volumes Table

Summary:
Angularize Volumes Table

Motivation:
Continue movement of shifting rendering logic that currently resides on the server to client side using AngularJS.

Enabled taking advantage of magic search and searchlight (https://wiki.openstack.org/wiki/Searchlight)

Description:

This BP depends upon https://blueprints.launchpad.net/horizon/+spec/reorganise-volumes being completed first.

One of the major hurdles in developing this table is the integration with the existing other tabs under the Volumes Panel. This blueprint will take the approach that the existing tab infrastructure will be retained as much as possible, only changing the implementation of the volume table page. This is a deviation from other angularised panels where the routing for the panel is taken over by angular. Eventually, once more tabs are implemented, we can switch over to having an angular top-level tab control and routing using angular (most likely ui-router).

An alternative is to break out the tabs into separate panels, which could make for a better user navigation experience, and would make the migration much simpler.

The volumes table will otherwise follow/model the development being done for blueprint,
https://blueprints.launchpad.net/horizon/+spec/angularize-identity-tables.

In addition, the current table filter will be replaced with the “Magic Search” widget. More information for Magic Search can
be found under blueprint https://blueprints.launchpad.net/horizon/+spec/filtered-client-side-table.

UX:
The UX will look and work similarly.

Outside Dependencies:
None.

Requirements Update Required:
None.

Doc Impact:
The table look and function will be the same, so I expect no document impacts.