Move volume snapshots table to volumes panel

[Kieran Spear]

Now that instance snapshots are just images, the images & snapshots page only has images and volume snapshots. This is an odd combination. I think we should now move volume snapshots to the volumes panel, since a volume snapshot is tied to a volume.

[Victoria Martinez de la Cruz (vkmc)]

Totally agree that this relation is odd and that having volumes and instances separated makes more sense.

Besides that, this makes me recall that we would be falling in the same discussion we had with images/instance snapshots: a volume snapshot is a volume.

Shouldn't we do the same thing we did with instances? That is, having a new column to specify if it is a snapshot or not.

Let me know your thoughts, thanks.

[Kieran Spear (kspear)]

This case is a bit different in that volumes and volume snapshots actually are different things. You can't boot a volume snapshot directly, you need to create a new volume from that snapshot first.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/58224

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/58224
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=3d25f1d5951beca1a73683567725ed26620ab373
Submitter: Jenkins
Branch: master

commit 3d25f1d5951beca1a73683567725ed26620ab373
Author: Zhenguo Niu <email address hidden>
Date: Tue Feb 18 10:14:00 2014 +0800

    Move volume snapshots table to volumes panel

    Now that instance snapshots are just images, the images & snapshots
    page only has images and volume snapshots. This is an odd combination.
    I think we should now move volume snapshots to the volumes panel,
    since a volume snapshot is tied to a volume.

    Closes-Bug: #1190843
    Change-Id: I3e12cec8b859a30db9f131e9889a92277e064086