Testing Juju devel 2.0-alpha1 in AWS, Azure, and Joyent

[Curtis Hovey-Canonical]

We are investigating an issue with the agent stream mirrors in AWS,
Azure, and Joyent. Bootstrapping will fail with a report there are not
matching tools. There are. The work-around is to set this in the
environments.yaml:
     agent-metadata-url: https://streams.canonical.com/juju/tools

^ this is non-obvious since it should be a no-op, but in fact restores
the 1.x default behaviour. Agents are indeed found in the public
cloud.

Users GCE, Rackspace, and private clouds are not affected by this issue.

We believe this is a temporary issue. We will send announcement to
this list when the issue is resolved and the work-around is not
needed.

-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui