Storage vs. PublicStorage

[Ian Booth]

Public Storage is used as a place to which to upload the juju tools tarball, and
is shared amongst all juju deployments ie they download the tools from there
when bootstrapping. There's a well known public bucket used for the EC2 provider
http://juju-dist.s3.amazonaws.com/. For Openstack deployments, we want the tools
to come from an Openstack container, not an EC2 bucket. So for a given Openstack
deployment, there's a config item which allows the URL of a public container to
be specified, and like the EC2 example above, is shared across all juju
deployments on that cloud instance. But it's not strictly speaking compulsory.
It's possible to run up an Openstack juju environment without a public bucket,
but in that case you need to have uploaded the tools to the control bucket
before hand. But that's just a provider implementation detail. If you don't want
to use public bucket for the MAAS provider, then just don't bother setting it.
The tools code will just ignore it if it is not set.

On 12/03/13 14:36, Jeroen Vermeulen wrote:
> Hi all,
> 
> We just noticed that the documentation for Environ.PublicStorage() has
> been updated.  It no longer says that the public storage is optional,
> and now it explains that this storage is meant to be shared between
> environments.
> 
> This combination is problematic for our ongoing provider implementation.
>  So my question is: would it actually be a problem if our
> PublicStorage() were not shared between environments?  For instance, a
> very simple thing for us to do would be to have Storage() and
> PublicStorage() return the same Storage.
> 
> 
> Jeroen
>