Is public-bucket-url used for both tools and streams?

[Ian Booth]

Hi Andreas

The juju-tools endpoint in the keystone catalog is used as the so called
public-bucket-url. You are now overriding that with the environment config
setting. Juju looks to find tools in the public bucket. As you have found, there
is a set of places that Juju looks at when deciding what the public bucket is,
and when the bucket URL is determined, that is what is used for everything.

So you need to upload tools to your alternative public bucket, either via:

1. the --upload-tools option to bootstrap if you are running from source
2. using the sync-tools command if you have installed the PPA

Note that only Openstack ever supported the use of default-image-id. If you
wanted a custom image when using EC2, you were out of luck. default-image-id
provides ways for the user to shoot themselves in the foot. With the use of
simplestreams metadata, there will be a uniform way for any cloud type to use a
custom image. We are working on improving the tooling so this becomes easier.
There's also discussion around using constraints to allow specific images and
instance types (aka flavors in Openstack) to be used.

On 01/08/13 06:13, Andreas Hasenack wrote:
> Hi,
> 
> the scenario is the following:
> - the openstack cloud I'm working with has juju-tools and product-streams
> published in keystone catalog
> - I'm using juju-core from the ppa (1.11.4-1~1514~raring1)
> - someone already took care of uploading the corresponding tools to the
> product-streams service of this openstack cloud. juju bootstrap works.
> - I want juju to use a custom image, and not the one published in the
> product-streams
> 
> Since someone decided default-image-id had to go, I went on to produce my
> own simplestreams and upload it. And I added public-bucket-url to
> environments.yaml so that juju would look there. But now I'm getting an
> error about the tools:
> $ juju bootstrap -v
> 2013-07-31 20:09:01 INFO juju provider.go:115 environs/openstack: opening
> environment "serverstack"
> 2013-07-31 20:09:01 INFO juju provider.go:417 environs/openstack:
> bootstrapping environment "serverstack"
> 2013-07-31 20:09:11 INFO juju tools.go:26 environs: reading tools with
> major version 1
> 2013-07-31 20:09:12 INFO juju tools.go:30 environs: falling back to public
> bucket
> 2013-07-31 20:09:12 ERROR juju supercommand.go:235 command failed: failed
> to list contents of container: juju-dist
> caused by: Unauthorised URL
> http://hyc7y-cofgod.1ss.qa.lexington:8080/v1/AUTH_98ad73deb8eb41ad8f118fd4badfe430/juju-dist?delimiter=&marker=&prefix=tools%2Fjuju-
> (...)
> 
> juju is looking for the tools in public-bucket-url. I understand it's not
> finding it there, and not trying the keystone catalog url for tools.
> 
> Does public-bucket-url, if specified, need to contain both? Tools and
> streams? What should I do if I want juju to use a custom image?
> 
> 
>