[
https://issues.apache.org/jira/browse/WHIRR-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067347#comment-13067347
]
Adrian Cole commented on WHIRR-341:
-----------------------------------
I think we should use this issue to document the "random changing id" problem
before establishing a new legacy of maintenance. If the problem of a changed
image breaking everything occurs as often, randomly, and severely as you
suggest, we'll get evidence to support this move quickly.
When that does, I'd suggest recognizing the image ids that are attached in the
patch. We can use these to compare against the random id that comes back and
breaks the test.
P.s. note that very few clouds outside Amazon have this problem as most base
images are cloud provider maintained.
> 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
