[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7180) Unable to locate AMI in images list

[Jeff Johnston (JIRA)]

    [ https://jira.jboss.org/browse/JBIDE-7180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556128#action_12556128 ] 

Jeff Johnston commented on JBIDE-7180:
--------------------------------------

While I agree that for this particular user that the tools are unusable, saying the image view is generally 
unusable is unwarranted.  Being able to manage what images are shown is essential to make it useful and
this relies on seeing all the images from the source.

I have added filter support in HEAD to both the Cloud View and Images view which allow the end-user to specify
what images show in the view (can filter on multiple aspects, name, id, architecture, and description).  Right now 
it is regex because of the underlying implementation, but I am going to switch it over to just allow wildcard characters
(e.g. * is anything, aki-* is any string starting with aki-) as regex power isn't really needed and it is not reasonable
to assume a UI user knows regex.

I have also opened a bug upstream against Deltacloud: https://bugzilla.redhat.com/show_bug.cgi?id=641405
as the list of images is being truncated there and not in Deltacloud Tools.

Ideally, I could see the Cloud View adding additional folders to the tree when the number exceeds 100.
E.g. 1-100, 101-200, 201-300, etc... as needed to make it more manageable.

The Images View is under a scroll bar and I don't see more images as a real inconvenience as it is up to the user to scroll
down or not.  Putting 100 images there and saying there is more doesn't help any.  The filters allow the user to concentrate
the list to what is useful to them (e.g. Images that start with aki- and are on x86_64).  If a user isn't completely
familiar with all the images set up for the cloud, they will need to see all of them.  This would allow them to choose
the most intelligent filtering parameters (e.g. they might notice that JBoss is mentioned in some of the descriptions
and can experiment filtering to find a particular Image or set of Images that would be useful to them). 

Filters are stored across sessions and are per-cloud connection.

> Unable to locate AMI in images list
> -----------------------------------
>
>                 Key: JBIDE-7180
>                 URL: https://jira.jboss.org/browse/JBIDE-7180
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: deltacloud
>    Affects Versions: 3.2.0.M2
>            Reporter: Pete Muir
>            Assignee: Jeff Johnston
>            Priority: Critical
>
> deltacloud appears to return some size limited set of images available, and in EC2 I have > 5000 -- so obviously the one I want isn't in this sublist (nb I have made this guess based upon going to the deltacloud web interface and browsing the images (the AMI I want isn't there), and then restricting by owner id (it is).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira