On Tue, 17 Nov 2015 16:00:12 -0800
Yehuda Sadeh-Weinraub <[email protected]> wrote:

> > <ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01";>
> >  <Name>foobucket</Name>
> >  <Tenant>footenant</Tenant>  <=============== this one
> >  <IsTruncated>false</IsTruncated>
> >
> > There's a certain problem with this, in case the client is constructing
> > the URLs for further access. In case it's trying to access across tenants,
> > it has to fetch the tenant name from the attribute. I thought about 
> > returning
> > the bucket name as <Name>footenant:foobucket</Name> for all buckets that
> > belong to non-empty tenant, but that seems asking for compatibility issues
> > even for access within the tenant.
> 
> Ah, I understand this point now. Note that a user will only have
> buckets under its own tenant (not going to own buckets from another
> tenant), so I'm not sure we need to add this.

Good point. I think I'll drop that.

> >> Does that work the same for object copy, and acls?
> >
> > ACLs do not list buckets, only users, which may be qualified (tenant$user).
> 
> Not tenant:user?

I forgot what happened when we did tenant:user. There was some kind
of metadata syntax that used colon somewhere in one of APIs. I shall
re-examine that and add a code comment near to_str() with dollar.

-- Pete
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to