ceph-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abhishek Lekshmanan <abhishek@suse.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Queries on RGW Multitenancy
Date: Wed, 20 Apr 2016 18:14:36 +0200	[thread overview]
Message-ID: <87shyggsur.fsf@suse.com> (raw)

A few questions on URLs behaviour after enabling multitenancy.

Are there any changes in the way bucket and object urls are used by
clients after creating a user with a tenant? My understanding so far has
been that the urls look the same for clients, and based on the
credentials passed in, we determine the tenant for requests. Is this
correct?

Also on making a bucket/object public the urls follow a format like:
`<host>/<tenant>:<bucket>`

Is there an equivalent s3 vhost style url for the above? Trying any of
tenant.bucket.host combos mostly gave  404s

And similarly for swift making a bucket public, the only url that seemed
accessible was the above mentioned `<host>/<tenant>:<bucket>` format and
there is no swift url of the format
`<host>/swift/v1/<tenant>/<container>` etc? Is this also the expected
behaviour?

Thanks
Abhishek
--
Abhishek Lekshmanan
SUSE Linux GmbH,
GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2016-04-20 16:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20 16:14 Abhishek Lekshmanan [this message]
2016-04-21 21:59 ` Queries on RGW Multitenancy Pete Zaitcev
2016-04-21 23:30   ` Pete Zaitcev
2016-04-22 16:32   ` Abhishek Lekshmanan
2016-04-22 17:23     ` Pete Zaitcev
2016-04-22 17:36       ` Abhishek L

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87shyggsur.fsf@suse.com \
    --to=abhishek@suse.com \
    --cc=ceph-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).