[
https://issues.apache.org/jira/browse/WHIRR-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068067#comment-13068067
]
Adrian Cole commented on WHIRR-341:
-----------------------------------
also, not to make our lives difficult, but s3 backed image won't work on the
t1.micro, so probably doesn't save us any money on services that will run on
t1.micro. Also, the cluster compute images are tricky as you cannot use normal
amis, moreover troublesome as cluster compute is only in 1 region. In all, we
have some extremes where hardware profiles will suggest a different image. ex
t1.micro and cluster have more specific choices whereas all the midrange sizes
could safely use the same image.
You might want to look at the enhanced image query syntax for aws-ec2 scheduled
for jclouds 1.1.0
http://code.google.com/p/jclouds/issues/detail?id=613
> Hard code the images used for integration testing
> -------------------------------------------------
>
> Key: WHIRR-341
> URL: https://issues.apache.org/jira/browse/WHIRR-341
> Project: Whirr
> Issue Type: Sub-task
> Components: core
> Reporter: Andrei Savu
> Assignee: Andrei Savu
> Fix For: 0.6.0
>
> Attachments: WHIRR-341.patch
>
>
> I suggest we should hard code the images that we are using for integration
> testing (the default images selected by Whirr) so that we can make the
> process more predictable. Right now you don't really know what image jclouds
> is going to select for you and that makes things complicated.
> By doing this we should also be able to publish a list of officially
> supported images for Apache Whirr, a list of images that we should be testing
> against before making a new release.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
