On Sun, Jun 14, 2015 at 11:00:23AM +0530, Abhishek L wrote: > > 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? If the NEW option names are unset, then: default 'create strictness' = 2 default 'access strictness' = (relaxed s3 bucket names) ? 0 : 1 That gets us the new strictness on create AND compatibility with existing configurations. -- Robin Hugh Johnson Gentoo Linux: Developer, Infrastructure Lead E-Mail : robbat2@xxxxxxxxxx GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
