Storage vs. PublicStorage

John Arbash Meinel john at arbash-meinel.com
Tue Mar 12 06:10:53 UTC 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-03-12 9:54, Jeroen Vermeulen wrote:
> On 03/12/2013 12:07 PM, Ian Booth wrote:
> 
>> 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.
> 
> Is there even such a thing as a bucket outside of the
> ec2/openstack providers?
> 
> PublicStorage() used to be documented as optional, but it no
> longer seems to be.  We tried implementing a PublicStorage() that
> just returns nil, but in our test, that made Bootstrap() crash
> during findMongo(). Returning the same storage object from
> Storage() and PublicStorage() does get us past that.
> 
> 
> Jeroen
> 

To start with "Public" is a bit of a misnomer, you can think of it
more as "Shared". The goal is just that if you have a place you can
put the tools, rather than
a) Downloading them from ec2
b) Having to upload them to each User's private space.

Arguably for many cases for MaaS (a) should be explicitly blocked by
the firewall.

For MaaS I don't know if there is an idea of many user accounts, so
there may only be the shared space.


As for findMongo(), if the documentation says it can return nil, then
we just need to teach findMongo about what to do if it gets nil
(return immediately). [aka just a bug]

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlE+xu0ACgkQJdeBCYSNAAP9rwCfXEPKzYt8gTwSDjag23gOh8My
cI4AoNI07cDdcpPgPMF3ygrAwGKUOb03
=ydC3
-----END PGP SIGNATURE-----



More information about the Juju-dev mailing list