All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abhishek L <abhishek.lekshmanan@gmail.com>
To: Wido den Hollander <wido@42on.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Bucket name restrictions in RGW
Date: Sun, 14 Jun 2015 11:00:23 +0530	[thread overview]
Message-ID: <87lhfmx3f4.fsf@gmail.com> (raw)
In-Reply-To: <557C9185.1050305@42on.com>

[-- Attachment #1: Type: text/plain, Size: 2107 bytes --]


Wido den Hollander writes:

> On 06/13/2015 01:29 AM, Robin H. Johnson wrote:
>> On Fri, Jun 12, 2015 at 07:13:48PM -0400,  Yehuda Sadeh-Weinraub wrote:
>>> Whatever we end up doing, we need to make it configurable, and also
>>> keep backward compatibility, so that buckets that were created prior
>>> to such a change will still remain accessible. Some setups would not
>>> need this limitation and will find it too restricting so I'm not sure
>>> that it's really that needed. In short, make it configurable.
>> Configurable:
>> - Can we obsolete 'rgw relaxed s3 bucket names', and convert it to a new
>>   option: 'rgw s3 bucket name create strictness'
>>   Value '0' => existing 'rgw relaxed s3 bucket names = true' logic
>>   Value '1' => existing 'rgw relaxed s3 bucket names = false' logic
>>   Value '2' => compliance with AmazonS3 DNS rules

Alternatively we could just add an opt `rgw s3 bucket name create
strictness` (maybe `rgw s3 bucket dns comply` instead) as a bool which
would set your value '2' logic when both `relaxed s3 bucket names` and
this value are set, so that we dont break backwards compatibility?
>> 
>> Backwards-Compatibility:
>> - Make a new option 'rgw s3 bucket name access strictness'
>>   Same values as above, but used to access buckets, not create new ones.
>> - Proposed default values:
>>   rgw s3 bucket name create strictness = 2
>>   rgw s3 bucket name access strictness = 1
>> 
>> So you can only create DNS-compliant buckets, but still access your
>> existing non-compliant buckets. Maybe also have keywords of major
>> releases and 'relaxed' supported in addition to the integer values.
>> 
>> I don't like the names of the config keys, but I'm coming up blank on
>> something that is shorter while still being immediately clear.
>> 
>
> Seems like a good plan to me. I would like to restrict them as much as
> possible, but we shouldn't break anything which is online now.
>
> -- 
> Wido den Hollander
> 42on B.V.
> Ceph trainer and consultant
>
> Phone: +31 (0)20 700 9902
> Skype: contact42on

-- 
Abhishek

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2015-06-14  5:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 15:28 Bucket name restrictions in RGW Harshal Gupta
2015-06-12 18:44 ` Wido den Hollander
2015-06-12 22:50   ` Robin H. Johnson
2015-06-12 23:13     ` Yehuda Sadeh-Weinraub
2015-06-12 23:29       ` Robin H. Johnson
2015-06-13 20:24         ` Wido den Hollander
2015-06-14  5:30           ` Abhishek L [this message]
2015-06-15 17:26             ` Harshal Gupta
2015-06-18 17:58               ` Harshal Gupta
2015-06-19  4:13                 ` Harshal Gupta
2015-06-15 17:59             ` Robin H. Johnson

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=87lhfmx3f4.fsf@gmail.com \
    --to=abhishek.lekshmanan@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=wido@42on.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.