eod report 28/6/2012

[David Cheney]

Howdy, 

A brief report

* bootstrap *nearly* works for non us-east-1*. You can bootstrap in a different region successfully now

% juju -v bootstrap -e ap-southeast-1 --upload-tools
2012/06/28 18:24:33 JUJU environs/ec2: opening environment "ap-southeast-1"
2012/06/28 18:24:33 JUJU environs/ec2: bootstrapping environment "ap-southeast-1"
2012/06/28 18:24:44 JUJU environs: putting tools tools/juju-0.0.0-precise-amd64.tgz
2012/06/28 18:25:47 JUJU findTools searching for {{0 0 0} precise amd64} in ["tools/juju-0.0.0-precise-amd64.tgz"]
2012/06/28 18:25:50 JUJU environs/ec2: started instance "i-1ced8848"



^ except, i-1ced8848 is actually in us-east-1. I haven't figured out why that happens.

* i've continued to add to rogers bootstrap branch but I'm not at a point where I can propose anything because of various issues preventing me from writing working tests. I've outlined those in the previous email. In summary they are
** running live tests against local/dummy needs some reorganisation to cmd/jujud -- discuss!
** running live tests against amazon needs some way to push secrets to the provisioning agent so it can action a call to state.AddMachine.

* gustavo - i have a fix for goamz to handle different s3 regions, but I would like to discuss how to test it as s3test doesn't support parsing the LocationConstraint xml atm.

Cheers

Dave

* why am i spending time on this ? because us-east-1 is the least reliable region from my perspective. not just because it's a long way away from me, but because of the continual timeouts and handshake errors issuing commands