[ https://jira.jboss.org/browse/JBIDE-7180?page=com.atlassian.jira.plugin.s... ] Pete Muir commented on JBIDE-7180: ---------------------------------- Marking as critical as EC2 Image support is not usable right now. -- 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

[ https://jira.jboss.org/browse/JBIDE-7180?page=com.atlassian.jira.plugin.s... ] 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. -- 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

[ https://jira.jboss.org/browse/JBIDE-7180?page=com.atlassian.jira.plugin.s... ] Jeff Johnston commented on JBIDE-7180: -------------------------------------- It appears to have been moved to: https://bugzilla.redhat.com/show_bug.cgi?id=641130 Perhaps I opened the original bug incorrectly. I can edit the bug number in my previous comment to avoid confusion, if that makes sense. -- 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

[ https://jira.jboss.org/browse/JBIDE-7180?page=com.atlassian.jira.plugin.s... ] Andre Dietisheim updated JBIDE-7180: ------------------------------------ Fix Version/s: 3.2.0.CR1 (was: 3.2.0.Beta2) -- 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

[ https://jira.jboss.org/browse/JBIDE-7180?page=com.atlassian.jira.plugin.s... ] Andre Dietisheim edited comment on JBIDE-7180 at 11/18/10 4:11 PM: ------------------------------------------------------------------- The latest client allows you to use an image that you may not find in the list of the available images that the client cached (JBIDE-7581). The appropriate wizard ("launch instance") checks if the image indicated is either present in the client or on the server. This workaround might help while we agree on a proper solution. The filters are a nice feature, but it only helps if you exactly know what your filter should look like. IMHO a search dialog with results (or a life filter: type and see what you get) would be a nice addition. was (Author: adietish): the latest client allows you to use an image that you may not find in the list of the available images that the client cached (JBIDE-7581). The appropriate wizard ("launch instance") checks if the image indicated is either present in the client or on the server. This workaround might help while we agree on a proper solution. IMHO a search dialog with results would be a nice feature. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-7180?page=com.atlassian.jira.plugin.s... ] Andre Dietisheim edited comment on JBIDE-7180 at 11/18/10 4:15 PM: ------------------------------------------------------------------- The latest client allows you to use an image that you may not find in the list of the available images that the client cached (JBIDE-7581). The appropriate wizard ("launch instance") checks if the image indicated is either present in the client or on the server. This workaround might help while we agree on a proper solution. I think that the problems discussed here are twofold: 1) deltacloud seems not to deliver all images that are available on EC2 2) Even if deltacloud would deliver them, the user would be overwhelmed by such a huge list. Filtering helps a lot here, but it only helps if you exactly know what your filter should look like. IMHO a search dialog with results (or a live filter: type and see what you get) would be a nice addition. was (Author: adietish): The latest client allows you to use an image that you may not find in the list of the available images that the client cached (JBIDE-7581). The appropriate wizard ("launch instance") checks if the image indicated is either present in the client or on the server. This workaround might help while we agree on a proper solution. I think that the problems discussed here are twofold: 1) deltacloud seems not to deliver all images that are available on EC2 2) Even if deltacloud would deliver them, the user would be overwhelmed by such a huge list. Filtering helps a lot here, but it only helps if you exactly know what your filter should look like. IMHO a search dialog with results (or a live filter: type and see what you get) would be a nice addition. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-7180?page=com.atlassian.jira.plugin.s... ] Andre Dietisheim edited comment on JBIDE-7180 at 11/18/10 4:26 PM: ------------------------------------------------------------------- The latest client allows you to use an image that you may not find in the list of the available images that the client cached (JBIDE-7581). The appropriate wizard ("launch instance") checks if the image indicated is either present in the client or on the server. This workaround might help while we agree on a proper solution. I think that the problems discussed here are twofold: 1) deltacloud seems not to deliver all images that are available on EC2 2) Even if deltacloud would deliver them, the user would be overwhelmed by such a huge list. Filtering helps a lot here, but it only helps if you exactly know what your filter should look like. IMHO a search dialog with results (or a live filter: type and see what you get) would be a nice addition but we need deltacloud to provide proper search capabilities. was (Author: adietish): The latest client allows you to use an image that you may not find in the list of the available images that the client cached (JBIDE-7581). The appropriate wizard ("launch instance") checks if the image indicated is either present in the client or on the server. This workaround might help while we agree on a proper solution. I think that the problems discussed here are twofold: 1) deltacloud seems not to deliver all images that are available on EC2 2) Even if deltacloud would deliver them, the user would be overwhelmed by such a huge list. Filtering helps a lot here, but it only helps if you exactly know what your filter should look like. IMHO a search dialog with results (or a live filter: type and see what you get) would be a nice addition. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-7180?page=com.atlassian.jira.plugin.s... ] Andre Dietisheim commented on JBIDE-7180: ----------------------------------------- JBIDE-7581 brings a valid workaround for this issue. You have to know the exact name of your image though. Postpone to LATER since we need to decide what to do here. We need more functionalities on the server side anyway. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7180?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-7180 at 2/7/11 6:08 PM: ----------------------------------------------------------------- I talked to bbrowning on #deltacloud and opened a bug that reports the list of images being incomplete: https://issues.apache.org/jira/browse/DTACLOUD-16 was (Author: adietish): I talked to bbrowning on #deltacloud and opened a bug for the incomplete list of images: https://issues.apache.org/jira/browse/DTACLOUD-16 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7180?page=com.atlassian.jira.plugin... ] Andre Dietisheim resolved JBIDE-7180. ------------------------------------- Resolution: Out of Date we're not developing Deltacloud any longer. See JBIDE-12458 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira