[ https://issues.jboss.org/browse/JBIDE-7864?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-7864: ------------------------------------ Priority: Minor (was: Major) -- 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-7864?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-7864 at 12/22/10 4:02 PM: ------------------------------------------------------------------- I implemented this by testing if the cloud the command is chosen on has any images. At first sight this might not be the proper solution since the wizard that allows you to launch an instance checks the server and the local cache for a given image. It may therefore fail if the cloud we want to launch an instance on is valid but has no images listed. Thinking about this twice I don't see any case where this might happen and might be of any relevance to the user. The only case where we need to check the server for a given image-id is where deltacloud does not report all images that are available on ec2. The client has images in this use case, but does not have all of them. I therefore believe that my test is absolutely sufficient. was (Author: adietish): I implemented this by testing if the cloud the command is chosen on has any images. At first sight this might not be the proper solution since the wizard that allows you to launch an instance checks the server and the local cache for a given image. It may therefore fail if the cloud we want to launch an instance on is valid but has no images listed. Thinking about this twice I dont see any case where this might happen and might be of any relevance to the user. The only case where the images we need to check the server for a given image-id is where deltacloud does not report all images that are available on ec2. But deltacloud still reports images in this case. I therefore believe that my test is absolutely sufficient. -- 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-7864?page=com.atlassian.jira.plugin... ] Andre Dietisheim edited comment on JBIDE-7864 at 12/22/10 4:23 PM: ------------------------------------------------------------------- I implemented this by testing if the cloud the command is chosen on has any images. This issue wants to disallow the user to launch an instance on a cloud-connection that is not valid, which we achieve with my current implementation. The only case where we cannot rely on the images that are present in the client is where deltacloud does not report all images that are available on ec2. We then need to check the server for a given image-id. The client then has images, but does not have all of them. "Launch instance" is then availble and the aim is fullfilled. A case I see where this test may fail, is where an image gets added to the server after we defined the connection in the client. The image may then only show up upon refresh and "launch instance" may not be availble although we may be able to launch an instance out of this new image. IMHO offering "Launch instance" then may be misleading and not consistent for the user. Another case is where the server may get available after we defined the connection to it (first we define a connection to the server and then the server gets available). Similar to the above you then need to refresh the views to get images and get "Launch instance" available. I therefore believe that my test is absolutely sufficient. was (Author: adietish): I implemented this by testing if the cloud the command is chosen on has any images. This issue wants to disallow the user to launch an instance on a cloud-connection that is not valid, which we achieve with my current implementation. The only case where we cannot rely on the images that are present in the client is where deltacloud does not report all images that are available on ec2. We then need to check the server for a given image-id. The client then has images, but does not have all of them. "Launch instance" is then availble and the aim is fullfilled. The only case I see where this test may fail, is where an image gets added to the server after we defined the connection in the client. The image may then only show up upon refresh and "launch instance" may not be availble although we may be able to launch an instance out of this new image. IMHO offering "Launch instance" then may be misleading and not consistent for the user. I therefore believe that my test is absolutely sufficient. -- 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-7864?page=com.atlassian.jira.plugin... ] Andre Dietisheim resolved JBIDE-7864. ------------------------------------- Resolution: Cannot Reproduce Bug committed to TRUNK (CR1) -- 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-7864?page=com.atlassian.jira.plugin... ] Libor Zoubek closed JBIDE-7864. ------------------------------- verified on 3.2.0.v20110110-1949-H35-CR1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira