simplestreams path

[Andreas Hasenack]

On Thu, Aug 1, 2013 at 11:33 AM, Scott Moser <smoser at ubuntu.com> wrote:

> I can't speak to what is implemented, but what I had thought we were going
> for was something like this:
>  * There are 2 "data locations" that juju needs to know about
>    - cloud_image_data_path
>    - juju_tools_path
>  * For each of these there is:
>    - global default
>    - provider-default
>    - user default
>    - user-specified value
>
>
One of the complications I can see is that the "path" you speak of is just
one for both things in some cases.

For example, the global default, let's say it's the service publication in
keystone (in the case of openstack).

We have two such services right now in keystone catalog: product-streams
and juju-tools. Nice and dandy. It's like DNS SRV.

But if you want to override one of them, you have to use public-bucket-url
in your environments.yaml file. And only that. This means you have no
choice but to override both product-streams and juju-tools, since they will
both live and be searched for under public-bucket-url now. There is no
config key specific for tools or streams.

That being said, I just tried to upload streams data
(streams/v1/{index,imagemetadata}.json) to the specially named juju-dist
bucket, and also to a bucket called "streams", but juju still uses the
images from the product-stream service, and not mine. Maybe there is a bug
in that product-stream can't be overridden if it's found.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20130801/66246b7f/attachment-0001.html>