Whirr
  1. Whirr
  2. WHIRR-678

Apache Whirr is not using my whirr.location-id parameter on EC2

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Not a Problem
    • Affects Version/s: 0.8.1
    • Fix Version/s: 0.8.2
    • Component/s: None
    • Labels:
      None
    • Environment:

      AWS EC2

      Description

      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?

        Activity

        Hide
        Steve Loughran added a comment -

        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.

        Show
        Steve Loughran added a comment - 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.
        Hide
        Andrew Bayer added a comment -

        That is correct - if you don't change the AMI to one in us-west-2, you're going to get us-east-1 instances.

        Show
        Andrew Bayer added a comment - That is correct - if you don't change the AMI to one in us-west-2, you're going to get us-east-1 instances.
        Hide
        Daniel Borcherding added a comment -

        I have the following two flags set in my properties file

        whirr.location-id=us-west-1
        whirr.image-id=us-west-1/ami-3ffed17a

        I suspect that I am having an issues with my proxy trying to get outside of our firewall.

        I do note however that I am seeing the following error in my logs

        Unable to start the cluster. Terminating all nodes.
        org.jclouds.http.HttpResponseException: Connection refused connecting to POST https://ec2.us-east-1.amazonaws.com/ HTTP/1.1

        Seems like I should be trying to connect to us-west-1 location instead of the east.

        Same result if I leave off the image id flag.

        Show
        Daniel Borcherding added a comment - I have the following two flags set in my properties file whirr.location-id=us-west-1 whirr.image-id=us-west-1/ami-3ffed17a I suspect that I am having an issues with my proxy trying to get outside of our firewall. I do note however that I am seeing the following error in my logs Unable to start the cluster. Terminating all nodes. org.jclouds.http.HttpResponseException: Connection refused connecting to POST https://ec2.us-east-1.amazonaws.com/ HTTP/1.1 Seems like I should be trying to connect to us-west-1 location instead of the east. Same result if I leave off the image id flag.

          People

          • Assignee:
            Andrew Bayer
            Reporter:
            Jongwook Woo
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 24h
              24h
              Remaining:
              Remaining Estimate - 24h
              24h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development