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

Andrei Savu commented on WHIRR-341:
-----------------------------------

Adrian let me try to clarify this misunderstanding :). The main reasons I'm 
trying to propose this change are:
* we should develop against a vanilla OS install so that install / configure 
scripts do not depend on packages that are not available by default (the 
Rightscale EBS AMI selected by default is far from this). This should make the 
code portable enough to work across a wide range of arbitrary AMIs. 
* EBS images add an extra costs (Amazon specific)
* we should have a flag that we can use to change between testing against 
apt-get / yum based systems
* we should be able to publish for each release the AMIs we used for testing

As you can see we want almost the same things! :) I agree that probably my 
change is not the best way to do this and I'm open to alternatives. 

bq. Note that in clouds such as vCloud, or any private cloud image and location 
ids are different per-user, so we'll probably have to think about this more

If you look at the code you will see that if the cloud provider is unknown will 
use the jclouds template selection mechanism. 



> 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

        

Reply via email to