I think I have a solution for this. It will imply fixing the existing python provider (but there is no way around that, right now, the files are fetched using "GET /api/1.0/files/?filename=filename&op=get"; if every user has its own store, we need the provider to use an extra piece of information to distinguish the files named "filename" but owned by different users). But the good news is that I think this solution will ensure a smooth transition for all the existing users, i.e. the change we will make to MAAS won't break the existing installations but juju itself (the MAAS provider part) will have to be SRUed for this bug to be fixed.
I'll write down what I have in mind on Monday.
I think I have a solution for this. It will imply fixing the existing python provider (but there is no way around that, right now, the files are fetched using "GET /api/1. 0/files/ ?filename= filename& op=get" ; if every user has its own store, we need the provider to use an extra piece of information to distinguish the files named "filename" but owned by different users). But the good news is that I think this solution will ensure a smooth transition for all the existing users, i.e. the change we will make to MAAS won't break the existing installations but juju itself (the MAAS provider part) will have to be SRUed for this bug to be fixed.
I'll write down what I have in mind on Monday.