What I had in mind is more or less what you say. Only, any image used
once will be automatically added to your favorites list, which makes a
recently used list redundant. And the "image browser" wouldn't need to
be shown per default. Besides being slow (look how long it takes for
the image browser of the AWS Maganement console to load!), it can't be
easier to manually look for an image than to just enter the ami id?
An thing about real work at a real organization. The 98% use case will
be to select an image from a list of 2 or 3 anyway, not loose time
browsing through hundreds of images.
2010/11/8 lusis <lusi...@gmail.com>:
All is done in-place, in the new node form. The form now loads
instantly, as it only pulls favorite images from the DB. There is a
link below the image list, which calls an in-line form that allows to
add another image to the favorites list, choosing from the complete
image set of the provider or entering an image id (ami for EC2). The
image list, even though it is indeed huge for EC2, is now
alphabetically ordered, so it is not so difficult to find something on
the few occasions when you will need to browse.
I think it works quite nicely, specially when you keep in mind the
normal use case: choose from the few images you use in daily work.
I left out removing images from the list. I will look again at that
part when I implement a real UI.
What do you think of this implementation?
2010/11/9 Miquel Torres <tob...@googlemail.com>:
just wanted to say that I have refined the image handling quite a bit.
You can now mark and unmark images as favorite and your last used
image is remembered and pre-selected by the new node form.
Also, sizes now show their price, both in the node form and in the
node tooltip (overview). Bear in mind thought that clouds do not
always provide pricing info through their APIs, and libcloud has
hardcoded prices as of version 0.4 (probably from November). They have
plans to put up an online prices database so that libcloud users can
get up-to-date pricing without having to release a new libcloud
version, but for the mean time this will do.
It still is nice to be able to see a ballpark figure for each instance
size. What I need to think about now is how to display some kind of
disclaimer about prices...
If anyone has a look at the new Overmind master version please give
some feedback here (DB must be rebuilt)!
PS: These changes and small refactorings and polish in other areas
have kept me busy, but now all is clear for the next step: the job
2010/11/10 Miquel Torres <tob...@googlemail.com>: