Comment 4 for bug 1568642

Revision history for this message
Travis Tripp (travis-tripp) wrote :

For Reference: http://pasteboard.co/8p6Tzuh.png

Okay, I see a few things here.

1) It would be nice to provide sorting to users and the legacy launch instance didn't have anything but a drop down with no sorting. I see a couple of solutions here that are NOT mutually exclusive and in my mind deprecate the stated purpose in the docs for this setting.

A) We could also very easily change / add to the available columns in the table which would provide the user the ability to sort on disk and ram.

B) When search is enabled, we could show the searchlight table locked to images. This would then provide really powerful filtering.

http://pasteboard.co/8pn5Obw.png

2) The note that Eric made above about deployers wanting to do some sort of server side deprecation of images and showing them last in the list seems almost more like it should just add a "deprecated" or "support status" property onto the images. IMO, this actually should just be a piece of metadata added on image properties themselves. Horizon could claim support for a particular one and we could even add a Horizon metadefs namespace to the Glance Metadata definition catalog so it would show up in the update metadata widget on horizon. We could then put it as a column (hidden?) and add a default sort to it. Doing this would also make it visible in the API, CLI, and in Searchlight.