transcloud environment woes.

[Curtis Hovey-Canonical]

Esteemed nephologists,

My hopes to setup a jenkins slave to test on ppc64el on a remote
network using juju itself are vexed.

Juju CI is currently in ec2. While I could update many tests to use
ssh to run on any remote machine, setting up a jenkins slave on other
machines (even in other networks) is faster. The ssh/config is already
setup and the unit tests are already using one of the machines on the
remote network. This command fails:

    juju add-machine --constraints "arch=ppc64" ssh:ubuntu at slave-ppc64
    ERROR no matching tools available

I think this error happens because juju visited streams.canonical.com,
which has a mirror pointing to juju-dist.s3.amazonaws.com. EC2 doesn't
have any ppc64 tools (ppc64el and powerpc to be precise).

Is there another way to add tools the the env or tell it where to find
tools (and ignore the mirror data)?

I could republish the extra tools to each certified public cloud so
that streams data supports tools that are not supported by the local
cloud.

I do not see juju looking at for new streams data though. This is a
problem because the extra archs are always made hours to days after
the common archs are published. I think juju is using stale data.

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