Conversation
Signed-off-by: Yehuda Sadeh <yehuda@inktank.com>
Signed-off-by: Yehuda Sadeh <yehuda@inktank.com>
Previous commits introduced the tenant infrastructure such as rgw_user, but did not allow anyone to access it productively. Done: - radosgw-admin - bucket creation, listing, deletion with non-empty tenant - COPY - ACLs - Using colon for S3 with URL addressing TODO: - Fix S3 remapping of DNS so that period turns into colon in buckets, possibly using typed endpoint domains, some assuming tenants - Have Swift authentication to set tenant into URL, then pick it there - Resolve leftover XXX Signed-off-by: Pete Zaitcev <zaitcev@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
yehudasa
added a commit
that referenced
this pull request
Dec 3, 2015
rgw multitenancy Buckets and users can now have a tenant associated with them. Buckets can be specified as [<tenant>:]<bucket> and users can be specified as [<tenant>$]<uid>. The existing users and buckets are part of the default global tenant. This is first phase. Future work will add tighter integration (e.g., swift tenant mapping, s3 subdomain tenant mapping, etc.) Reviewed-by: Pete Zaitcev <zaitcev@redhat.com> Reviewed-by: Yehuda Sadeh <yehuda@redhat.com>
Vicente-Cheng
added a commit
to Vicente-Cheng/ceph
that referenced
this pull request
Mar 15, 2016
Description: If the user/admin removes a bucket using --force/--purge-objects options with s3cmd/radosgw-admin respectively, the user stats will continue to reflect the deleted objects for quota purposes, and there seems to be no way to reset them. User stats need to be sync'ed prior to bucket removal. Solution: Sync user stats before removing a bucket. Fixes: ceph#14507 Signed-off-by: Edward Yang <eyang@us.fujitsu.com> (cherry picked from commit 0650799) Backport: hammer Conflicts: src/rgw/rgw_op.cc reordering the check seqence and replace some ret to op_ret Backport Change: We remove the `tenant` parameter because this feature is not introduced on hammer version. The rgw multi-tenant feature is introduced on pr#6784 (ceph#6784) This feature is supported from v10.0.2 and later version. Signed-off-by: Vicente Cheng <freeze.bilsted@gmail.com>
Vicente-Cheng
added a commit
to Vicente-Cheng/ceph
that referenced
this pull request
Mar 15, 2016
Description: If the user/admin removes a bucket using --force/--purge-objects options with s3cmd/radosgw-admin respectively, the user stats will continue to reflect the deleted objects for quota purposes, and there seems to be no way to reset them. User stats need to be sync'ed prior to bucket removal. Solution: Sync user stats before removing a bucket. Fixes: ceph#14507 Signed-off-by: Edward Yang <eyang@us.fujitsu.com> (cherry picked from commit 0650799) Backport: hammer Conflicts: src/rgw/rgw_op.cc reordering the check seqence and replace some op_ret to ret Backport Change: We remove the `tenant` parameter because this feature is not introduced on hammer version. The rgw multi-tenant feature is introduced on pr#6784 (ceph#6784) This feature is supported from v10.0.2 and later version. Signed-off-by: Vicente Cheng <freeze.bilsted@gmail.com>
Vicente-Cheng
added a commit
to Vicente-Cheng/ceph
that referenced
this pull request
Mar 17, 2016
Description: If the user/admin removes a bucket using --force/--purge-objects options with s3cmd/radosgw-admin respectively, the user stats will continue to reflect the deleted objects for quota purposes, and there seems to be no way to reset them. User stats need to be sync'ed prior to bucket removal. Solution: Sync user stats before removing a bucket. Fixes: ceph#14507 Signed-off-by: Edward Yang <eyang@us.fujitsu.com> (cherry picked from commit 0650799) Backport: hammer Conflicts: src/rgw/rgw_op.cc reordering the check seqence and replace some op_ret to ret Backport Change: We remove the `tenant` parameter because this feature is not introduced on hammer version. The rgw multi-tenant feature is introduced on pr#6784 (ceph#6784) This feature is supported from v10.0.2 and later version. Signed-off-by: Vicente Cheng <freeze.bilsted@gmail.com>
Vicente-Cheng
pushed a commit
to Vicente-Cheng/ceph
that referenced
this pull request
Mar 19, 2016
Fixes: ceph#11076 Signed-off-by: Zengran Zhang <zhangzengran@h3c.com> (cherry picked from commit 4d59b1d) Backport: hammer Conflicts: src/rgw/rgw_bucket.cc remove the tenant parameter that describes as below Backport Change: We remove the `tenant` parameter because this feature is not introduced on hammer version. The rgw multi-tenant feature is introduced on pr#6784 (ceph#6784) This feature is supported from v10.0.2 and later version. Signed-off-by: Vicente Cheng <freeze.bilsted@gmail.com>
Vicente-Cheng
pushed a commit
to Vicente-Cheng/ceph
that referenced
this pull request
Mar 19, 2016
Fixes: ceph#11076 Signed-off-by: Zengran Zhang <zhangzengran@h3c.com> (cherry picked from commit 4d59b1d) Backport: hammer Conflicts: src/rgw/rgw_bucket.cc Do not use the rgw_user structure and remove the tenant parameter that describes as below Backport Change: We do not use the rgw_user structure and remove the `tenant` parameter because this feature is not introduced on hammer version. The rgw multi-tenant feature is introduced on pr#6784 (ceph#6784) This feature is supported from v10.0.2 and later version. Signed-off-by: Vicente Cheng <freeze.bilsted@gmail.com>
Vicente-Cheng
added a commit
to Vicente-Cheng/ceph
that referenced
this pull request
Apr 6, 2016
If the user/admin removes a bucket using --force/--purge-objects options with s3cmd/radosgw-admin respectively, the user stats will continue to reflect the deleted objects for quota purposes, and there seems to be no way to reset them. User stats need to be sync'ed prior to bucket removal. Solution: Sync user stats before removing a bucket. Fixes: ceph#14507 Signed-off-by: Edward Yang <eyang@us.fujitsu.com> (cherry picked from commit 0650799) Conflicts: src/rgw/rgw_op.cc reordering the check seqence and replace some op_ret to ret Backport Change: We remove the `tenant` parameter because this feature is not introduced on hammer version. The rgw multi-tenant feature is introduced on pr#6784 (ceph#6784) This feature is supported from v10.0.2 and later version.
Vicente-Cheng
added a commit
to Vicente-Cheng/ceph
that referenced
this pull request
Apr 6, 2016
Description: If the user/admin removes a bucket using --force/--purge-objects options with s3cmd/radosgw-admin respectively, the user stats will continue to reflect the deleted objects for quota purposes, and there seems to be no way to reset them. User stats need to be sync'ed prior to bucket removal. Solution: Sync user stats before removing a bucket. Fixes: ceph#14507 Signed-off-by: Edward Yang <eyang@us.fujitsu.com> (cherry picked from commit 0650799) Conflicts: src/rgw/rgw_op.cc reordering the check seqence and replace some op_ret to ret Backport Change: We remove the `tenant` parameter because this feature is not introduced on hammer version. The rgw multi-tenant feature is introduced on pr#6784 (ceph#6784) This feature is supported from v10.0.2 and later version.
Vicente-Cheng
pushed a commit
to Vicente-Cheng/ceph
that referenced
this pull request
Apr 13, 2016
Fixes: ceph#11076 Signed-off-by: Zengran Zhang <zhangzengran@h3c.com> (cherry picked from commit 4d59b1d) Conflicts: src/rgw/rgw_bucket.cc 1. Do not use the rgw_user structure and remove the tenant parameter that describes as below 2. user_id is not used so just remove the line 3. instead of system_obj_set_attr you can use the method set_attr Backport Change: We do not use the rgw_user structure and remove the `tenant` parameter because this feature is not introduced on hammer version. The rgw multi-tenant feature is introduced on pr#6784 (ceph#6784) This feature is supported from v10.0.2 and later version.
Abhishekvrshny
pushed a commit
to Abhishekvrshny/ceph
that referenced
this pull request
Jul 13, 2017
Description: If the user/admin removes a bucket using --force/--purge-objects options with s3cmd/radosgw-admin respectively, the user stats will continue to reflect the deleted objects for quota purposes, and there seems to be no way to reset them. User stats need to be sync'ed prior to bucket removal. Solution: Sync user stats before removing a bucket. Fixes: ceph#14507 Signed-off-by: Edward Yang <eyang@us.fujitsu.com> (cherry picked from commit 0650799) Conflicts: src/rgw/rgw_op.cc reordering the check seqence and replace some op_ret to ret Backport Change: We remove the `tenant` parameter because this feature is not introduced on hammer version. The rgw multi-tenant feature is introduced on pr#6784 (ceph#6784) This feature is supported from v10.0.2 and later version. (cherry picked from commit c722d00) Conflicts: src/rgw/rgw_op.cc
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.