> We don't want a shared namespace - having different users see each other's
> files is crazy.
You're definitely right. That's also how the other providers do it. Unfortunately, we've implemented this the wrong way: a shared namespace is what we have now :/.
We need to change the store so that each user has a independent view of the file store. Also, each file should have a random string attached to it so that it can be accessed (read-only) anonymously via the API with that key (i.e. /api/1.0/files/?get=filename&key=secret-key-specific-to-this-file).
That's rather easy to change but :
> Also bear in mind that we can't change the behaviour of already-release juju
> code. This *has* to be fixed in MAAS. Then MAAS will work like all the other
> providers Juju deals with.
Indeed, that's where the real problem is really. We need to think hard to fix this while still supporting the exiting provider's code.
> We don't want a shared namespace - having different users see each other's
> files is crazy.
You're definitely right. That's also how the other providers do it. Unfortunately, we've implemented this the wrong way: a shared namespace is what we have now :/.
We need to change the store so that each user has a independent view of the file store. Also, each file should have a random string attached to it so that it can be accessed (read-only) anonymously via the API with that key (i.e. /api/1. 0/files/ ?get=filename& key=secret- key-specific- to-this- file).
That's rather easy to change but :
> Also bear in mind that we can't change the behaviour of already-release juju
> code. This *has* to be fixed in MAAS. Then MAAS will work like all the other
> providers Juju deals with.
Indeed, that's where the real problem is really. We need to think hard to fix this while still supporting the exiting provider's code.