[rhos-list] Gluster UFO 3.4 swift Multi tenant question

Ramana Raja rraja at redhat.com
Tue Sep 3 00:55:08 UTC 2013


Hi Paul,

Currently, gluster-swift doesn't support the feature of multiple accounts/tenants accessing the same volume. Each tenant still needs his own gluster volume. So I'm wondering how you were able to observe the reported behaviour.

How did you prepare the ringfiles for the different tenants, which use the same gluster volume?  Did you change the configuration of the servers? Also, how did you access the files that you mention? It'd be helpful if you could share the commands you used to perform these actions.

Thanks,

Ram  


----- Original Message -----
From: "Vijay Bellur" <vbellur at redhat.com>
To: "Paul Robert Marino" <prmarino1 at gmail.com>
Cc: rhos-list at redhat.com, "Luis Pabon" <lpabon at redhat.com>, "Ramana Raja" <rraja at redhat.com>, "Chetan Risbud" <crisbud at redhat.com>
Sent: Monday, September 2, 2013 4:17:51 PM
Subject: Re: [rhos-list] Gluster UFO 3.4 swift Multi tenant question

On 09/02/2013 01:39 AM, Paul Robert Marino wrote:
> I have Gluster UFO installed as a back end for swift from here
> http://download.gluster.org/pub/gluster/glusterfs/3.4/3.4.0/RHEL/epel-6/
> with RDO 3
>
> Its working well except for one thing. All of the tenants are seeing
> one Gluster volume which is some what nice, especially when compared
> to the old 3.3 behavior of creating one volume per tenant named after
> the tenant ID number.
>
> The problem is I expected to see is sub directory created under the
> volume root for each tenant but instead what in seeing is that all of
> the tenants can see the root of the Gluster volume. The result is that
> all of the tenants can access each others files and even delete them.
> even scarier is that the tennants can see and delete each others
> glance images and snapshots.
>
> Can any one suggest options to look at or documents to read to try to
> figure out how to modify the behavior?
>

Adding gluster swift developers who might be able to help.

-Vijay




More information about the rhos-list mailing list