All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis Pabón" <lpabon@redhat.com>
To: Yehuda Sadeh <yehuda@redhat.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: RGW Swift questions
Date: Thu, 14 Aug 2014 12:52:50 -0400	[thread overview]
Message-ID: <53ECE962.8090208@redhat.com> (raw)
In-Reply-To: <CABBk=J94xz+0oCcnoq-EnFXNrPYCrgkv3zw2-O7Aa19+z+egMw@mail.gmail.com>

Great thanks!

- Luis

On 08/14/2014 12:40 PM, Yehuda Sadeh wrote:
> On Thu, Aug 14, 2014 at 9:00 AM, Luis Pabon <lpabon@redhat.com> wrote:
>> Thanks for the quick turnaround Yehuda.  I have just a few more comments below:
>>
>> ----- Original Message -----
>> From: "Yehuda Sadeh" <yehuda@redhat.com>
>> To: "Luis Pabón" <lpabon@redhat.com>
>> Cc: ceph-devel@vger.kernel.org
>> Sent: Thursday, August 14, 2014 11:02:06 AM
>> Subject: Re: RGW Swift questions
>>
>> On Thu, Aug 14, 2014 at 7:27 AM, Luis Pabón <lpabon@redhat.com> wrote:
>>> Hi Yehuda,
>>>      I am starting work on RGW and have a few questions:
>>>
>>> * Why is the command 'user create' when I am sending '--subuser'. Seems
>>> confusing.  Is there a reason why we are not to use 'subuser create'?
>> A subuser needs to have the containing user in order to be created.
>> The 'user create' command generates ones. The order of things would be
>> to create a user, then create a subuser for that user. By specifying
>> --subuser=.. on the user creation it should do both.
>>
>> [LP] Great, thank you
>>
>>> * If I use "user create --subuser", the JSON returned shows the entry for
>>> "subusers" is empty.  What is subusers for? (This is related to the previous
>>> question)
>> So I assume the subuser wasn't created?
>> The rgw user model follows the S3 user model which is a bit different
>> from the swift one. In S3 there's basically a single tenant, multiple
>> users. With swift there are multiple tenants (originally referred to
>> as 'accounts'), each have different users that share a similar view of
>> the system (e.g., share list of containers, etc.). The more natural
>> (although not perfect) mapping is by having an rgw user map to a swift
>> account. That's why we needed to add a second level of identification,
>> the subuser.
>>
>> [LP] I will have to check why it is empty.
>>
>>
>>> * Where do I place the OpenStack Tenant information?
>> The tenant id should be the user name.
>>
>> [LP] Cool, thanks. So if the tenant is the user name in RGW, what is the Swift user
>> map to?
> It maps into the subuser.
>
> Yehuda
>
>>> * Is there a document which describes how to setup RGW for OpenStack Swift?
>> Not that I'm aware of. Basically rgw is set to work with both S3 and
>> Swift out of the box. Here's how to integrate with keystone:
>> http://ceph.com/docs/master/radosgw/keystone/
>>
>>> * The radosgw-admin help screen does not explain which options to use for
>>> certain commands.  Is this something that we should fix?
>> We should certainly improve documentation. This can either go into the
>> man page, or a complete rework of the usage help.
>>
>>> * On page: http://ceph.com/docs/master/radosgw/swift/auth/ , clicking on
>>> "see radosgw-admin" does not work.
>> I opened issue #9116.
>>
>>
>> Thanks,
>> Yehuda
>> --
>> 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

--
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:[~2014-08-14 16:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14 14:27 RGW Swift questions Luis Pabón
2014-08-14 15:02 ` Yehuda Sadeh
2014-08-14 16:00   ` Luis Pabon
2014-08-14 16:40     ` Yehuda Sadeh
2014-08-14 16:52       ` Luis Pabón [this message]

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=53ECE962.8090208@redhat.com \
    --to=lpabon@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=yehuda@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.