Taking into account the desire for different tools streams, and the advantage of
providing the ability to maintain a single source tree for tools metadata,
here's a slightly revised implementation plan:
where <tag> is one of:
- released
- proposed
- devel
- testing
Just as we currently have an "image-stream" config setting for simplestreams
image metadata, there will be an equivalent "tools-stream" setting for tools
metadata to specify the tag. This keeps everything nice and consistent. The new
tools metadata is in a different location to what exists today, so 1.18 Juju can
still upgrade.
Note: the file paths inside the json metadata will need to contain the full path under tools
ie
streams/v1/cpc-mirrors.json becomes <tag>/treams/v1/cpc-mirrors.json etc
Taking into account the desire for different tools streams, and the advantage of
providing the ability to maintain a single source tree for tools metadata,
here's a slightly revised implementation plan:
The tools metadata will live in this location:
http:// streams. canonical. com/juju/ tools/<tag>/streams/v1
where <tag> is one of:
- released
- proposed
- devel
- testing
Just as we currently have an "image-stream" config setting for simplestreams
image metadata, there will be an equivalent "tools-stream" setting for tools
metadata to specify the tag. This keeps everything nice and consistent. The new
tools metadata is in a different location to what exists today, so 1.18 Juju can
still upgrade.
Note: the file paths inside the json metadata will need to contain the full path under tools v1/cpc- mirrors. json becomes <tag>/treams/ v1/cpc- mirrors. json etc
ie
streams/