Hi Ignasi, Thank you for the explanation.
I don't think we are using locationId in building the template. Will check the possibility of changing the code to take locationId into consideration or using jclouds.regions property. On Mon, Sep 21, 2015 at 1:36 PM, Ignasi Barrera <n...@apache.org> wrote: > Hi! > > jclouds uses the DescribeRegionsForRegionURIs class [1] to build a map > of "regionId -> endpoint" that is used to determine the endpoint for > each region. > > Could you share a code snippet so we can see if there is something > wrong in your code? > > If you are using the ComputeService and the TemplateBuilder, verify > that you are setting the right "locationId" when building the template > and that the image you are using is available in the region you want. > > As an alternative, you can limit the regions jclouds will take into > account by creating the context with the "jclouds.regions" property > set to the comma separated list of region ids you want to use. > > > HTH! > > I. > > [1] > https://github.com/jclouds/jclouds/blob/jclouds-1.7.1/apis/ec2/src/main/java/org/jclouds/ec2/suppliers/DescribeRegionsForRegionURIs.java > > On 18 September 2015 at 19:59, Isuru Haththotuwa <isu...@apache.org> > wrote: > > Hi Devs, > > > > How does JClouds determine which EC2 endpoint to call? I'm using version > > 1.7.1. > > > > I have observed that for a setup that is using JClouds library to > > spin/terminate instances, which is based on EC2 us-west region (setup and > > relevant AMIs), API calls are happening to ap-southeast endpoint [1], > etc. > > Therefore trying to find out how this works. Is there a way we configure > > JCouds to use a particular EC2 endpoint? > > > > [1]. ec2.ap-southeast-1.amazonaws.com >
