whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrei Savu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WHIRR-341) Hard code the images used for integration testing
Date Mon, 18 Jul 2011 17:16:58 GMT

    [ https://issues.apache.org/jira/browse/WHIRR-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067152#comment-13067152

Andrei Savu commented on WHIRR-341:

> we should document the template parameters that passed tests (and led to a release of


> We should be optimizing for predictability across images, not honing for only a single
version with a set of patches frozen in time.

I agree but I'm not sure this task is doable without slowing down the development even more.
This is why I am proposing this change.

> Besides, devs can already set whirr test properties, so if one of us wants to only use
a favorite image, we can already do that.

I don't understand how this simplifies things if we still want to support as many random AMIs?

> Finally, the maintenance of image id per provider/region/os mix is a pretty big job and
requires constant attention. This isn't a legacy I'd recommend us entering. 

IMO this is better than having tests that randomly fail as new images are added or updated.

> If image updates become troublesome, I'd instead recommend fortification. For example,
automated forensics gathering, or hardening configuration scripts to reveal dependencies needed
or incompatible with a specific service role. 

+1 is anyone available to work on this? 

> 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
> 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


View raw message