From: Yang Joseph <joseph.yang@xtaotech.com>
To: Yehuda Sadeh-Weinraub <yehuda@redhat.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>,
"ceph-users@lists.ceph.com" <ceph-users@lists.ceph.com>,
Javen Wu <javen.wu@xtaotech.com>
Subject: Re: [ceph-users] rgw: how to prevent rgw user from creating a new bucket?
Date: Mon, 5 Dec 2016 11:01:23 +0800 [thread overview]
Message-ID: <5844D883.7060806@xtaotech.com> (raw)
In-Reply-To: <CADRKj5Rt6gDPXwQH9UivgWhLRqzbzVD7VECogU7iTmKUAihBHg@mail.gmail.com>
Thank you very much for your response.
I‘m confused about what this cap related to?
On 12/03/2016 12:13 AM, Yehuda Sadeh-Weinraub wrote:
> On Fri, Dec 2, 2016 at 3:18 AM, Yang Joseph <joseph.yang@xtaotech.com> wrote:
>> Hello,
>>
>> I would like only to allow the user to read the object in a already existed
>> bucket, and not allow users
>> to create new bucket. It supposed to execute the following command:
>>
>> $ radosgw-admin metadata put user:test3 < ...
>> ...
>> "caps": [
>> {
>> "type": "buckets",
>> "perm": "read"
>> }
>>
>> But why user test3 can still create new bucket after I have set its caps to
>> "buckets=read"?
>>
>
> Because this cap is unrelated. iirc starting at jewel you can do:
>
> $ radosgw-admin user modify --uid=test3 --max-buckets=-1
>
> 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
>
prev parent reply other threads:[~2016-12-05 3:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 11:18 rgw: how to prevent rgw user from creating a new bucket? Yang Joseph
[not found] ` <584158A2.9020303-/BaA95PH9wJWk0Htik3J/w@public.gmane.org>
2016-12-02 16:13 ` Yehuda Sadeh-Weinraub
2016-12-05 3:01 ` Yang Joseph [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=5844D883.7060806@xtaotech.com \
--to=joseph.yang@xtaotech.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-users@lists.ceph.com \
--cc=javen.wu@xtaotech.com \
--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.