Merge lp:~dave-cheney/juju-core/052-environs-ec2-always-request-public-tools-from-us-east-1 into lp:~juju/juju-core/trunk
Proposed by
Dave Cheney
Status: | Rejected |
---|---|
Rejected by: | Dave Cheney |
Proposed branch: | lp:~dave-cheney/juju-core/052-environs-ec2-always-request-public-tools-from-us-east-1 |
Merge into: | lp:~juju/juju-core/trunk |
Diff against target: |
123 lines (+34/-23) 4 files modified
environs/ec2/config.go (+18/-9) environs/ec2/ec2.go (+2/-1) environs/ec2/local_test.go (+12/-11) juju/bootstrap.go (+2/-2) |
To merge this branch: | bzr merge lp:~dave-cheney/juju-core/052-environs-ec2-always-request-public-tools-from-us-east-1 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
The Go Language Gophers | Pending | ||
Review via email: mp+136077@code.launchpad.net |
Description of the change
environs/ec2: specify public-
Fixes LP #1083017
Our public bucket, juju-dist, lives in the us-east-1 region and can only be accessed via that endpoint. If you attempt to do so via another endpoint you get an unhelpful 301 error with an xml blob telling you how to request the bucket. The solution is to add a configuration option, with sensible default, to ec2/config.go to specify the region of the public bucket independantly of the private bucket.
To post a comment you must log in.
Seems ok. I'm not sure if having a configurable "grab the tools from
this region" is better than providing the tools in all regions. If this
is the best way forward, than LGTM.
https:/ /codereview. appspot. com/6843112/ diff/2001/ environs/ ec2/ec2. go
File environs/ec2/ec2.go (left):
https:/ /codereview. appspot. com/6843112/ diff/2001/ environs/ ec2/ec2. go#oldcode162 ec2/ec2. go:162: }
environs/
It seems like if you've connected you might want to reuse s3Unlocked if
region == publicBucketRegion.
Beyond that, having to access us-east-1 from outside of it means paying
bandwidth charges, etc. Is it worthwhile to try and put the tools on all
regions?
https:/ /codereview. appspot. com/6843112/