I have created https://issues.apache.org/jira/browse/WHIRR-478 scheduled for 0.8.0.
On Tue, Jan 17, 2012 at 8:17 PM, Andrei Savu <[email protected]> wrote: > Nice trick we should use to speed-up test execution. We are running them > on us-east-1. > > Anyone want's to give it a try at updating the test .properties? > > ---------- Forwarded message ---------- > From: Adrian Cole <[email protected]> > Date: Tue, Jan 17, 2012 at 7:29 PM > Subject: How to deal with unresponsive aws regions > To: [email protected], [email protected] > > > Hi, all. > > Some of you reported problems with jclouds hanging on us-west-2 > region, due to it timing out yesterday. This timeout would have > occured in DesribeAvailabiltyZones if you were using ComputeService, > which is by default multi-region. > > When we get a stacktrace from someone (or a clever anticipatory unit > test), we can probably gracefully deal with this. In the mean time, > here's how you can blacklist an aws region: > > When creating a context in jclouds, there's a special property > "jclouds.regions" that defaults to. > > "us-east-1,us-west-1,us-west-2,sa-east-1,eu-west-1,ap-southeast-1,ap-northeast-1" > in all aws services outside aws-s3 > in aws-s3, it is slightly different > > "us-standard,us-west-1,EU,sa-east-1,eu-west-1,ap-southeast-1,ap-northeast-1" > in all aws services outside aws-s3 > > create your context, overriding "jclouds.regions" property without the > bad region, and you'll be ok. * > > Properties overrides = new Properties(); > overrides.setProperty( "jclouds.regions", "us-east-1"); > context = new > ComputeServiceContextFactory().createContext("aws-ec2", > ImmutableSet.<Module> of( > new SLF4JLoggingModule(), new SshjSshClientModule()), > overrides); > > I hope this helps! > -Adrian > > * note that if you are taking out us-east-1 in aws-ec2, also unset the > following property > overrides.setProperty("jclouds.ec2.cc-regions", ""); > >
