[WHIRR-478] Speedup compute service context creation for integration tests

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 0.9.0
• Assignee: Unassigned
• Reporter: Andrei Savu
• Created: 17/Jan/12 21:59
• Updated: 03/Mar/12 01:47

Description

Here is the email from Adrian that explain how we change the scope of jclouds to target a single region when using Amazon:

------------------------------------------------------------------------

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", "");