[jira] [Commented] (WHIRR-678) Apache Whirr is not using my whirr.location-id parameter on EC2

["Steve Loughran (JIRA)" <ji...@apache.org>]

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

Steve Loughran commented on WHIRR-678:
--------------------------------------

I've got it working by setting the {{whirr.image-id}} property {{whirr.image-id=us-west-2/ami-f627a9c7}}

I think the location is implicit in that image ID.
                
> Apache Whirr is not using my whirr.location-id parameter on EC2
> ---------------------------------------------------------------
>
>                 Key: WHIRR-678
>                 URL: https://issues.apache.org/jira/browse/WHIRR-678
>             Project: Whirr
>          Issue Type: Bug
>    Affects Versions: 0.8.1
>         Environment: AWS EC2
>            Reporter: Jongwook Woo
>             Fix For: 0.8.2
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> I've been using Apache Whirr(0.8.0) to create Hadoop+HBase clusters on EC2 using the CDH ami (and default AMI), turns out that Whirr is not using my whirr.location-id parameter. I specifically pass it as an argument --location-id=us-west-2 when I create the cluster and I also added it to the whirr recipe as whirr.location-id=us-west-2 but when I fire up the clusters they always get created in the us-east-1 region. My guess is that the Whirr recipe for CDH (and default) is overriding the region and I wonder if there is any way to disable this or force an specific EC2 region?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira