Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make a bucket name compatible with the aws-s3 naming rule of US region #98

Closed
mocchira opened this issue Nov 7, 2013 · 8 comments
Closed

Comments

@mocchira
Copy link
Member

mocchira commented Nov 7, 2013

To make it easy to replace S3 with LeoFS for users,
I think we need to adopt a more relax naming rule.

http://docs.aws.amazon.com/ja_jp/AmazonS3/latest/dev/BucketRestrictions.html

@ghost ghost assigned mocchira Nov 7, 2013
@yosukehara
Copy link
Member

We need to write this spec in the manual.

@mocchira
Copy link
Member Author

mocchira commented Nov 7, 2013

modify two things as follows.

  • Max length is 255
  • Able to use _ char in a bucket

@yosukehara
Copy link
Member

it's OK.

@firejun
Copy link

firejun commented Nov 7, 2013

I confirmed this issue.
So, I have a question.

I don't able to use numeric character only bucket name?
I try to add 255bytes numeric character only bucket.
But it failed as below command.

[Berow is numeric only(255bytes)]
add-bucket 123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345 47d0e9061169c47f3ddc
[ERROR] "Invalid bucket format"

[Berow is alphabet only(255bytes)]
add-bucket abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstu 47d0e9061169c47f3ddc
OK

@mocchira
Copy link
Member Author

mocchira commented Nov 7, 2013

YES.
This spec will be published at the next stable version release day.

@firejun
Copy link

firejun commented Nov 7, 2013

Thank you for your reply.
I understand this issue.

@yosukehara
Copy link
Member

Reference: Bucket Restrictions and Limitations(En)

@yosukehara
Copy link
Member

I've written "rules for bucket naming" in the manual - https://github.com/leo-project/leofs_docs/commit/d48fc90f28607f773a4ca8719627d6639ecff9f2
It will be published on the website after released LeoFS-v0.16.1 next week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants