Thanks for your response, So clients can not get the value which they set in the LocationConstraint field in the create bucket request as in this doc <https://docs.ceph.com/en/latest/radosgw/placement/#s3-bucket-placement>? Best Regards, Mahnoosh On Mon, Jul 3, 2023 at 12:35 PM Konstantin Shalygin <k0ste@k0ste.ru> wrote:

Hi,

On 2 Jul 2023, at 17:17, mahnoosh shahidi <mahnooosh.shd@gmail.com> wrote:

Is there any way for clients (without rgw-admin access) to get the placement target of their S3 buckets? The "GetBucketLocation'' api returns "default" for all placement targets and I couldn't find any other S3 api for this purpose.

From S3 side you can't know the internals of API. The client can operate with S3 STORAGE CLASS, for example the output

√ ~ % s5cmd ls s3://restic/snapshots/ | head 2023/06/30 17:10:03 263 09c68acfe0cd536c3a21273a7adeee2911f370aa4f12fb9de5d13e1b8a93a7ef 2023/06/18 10:30:05 285 0e6d2982310da04e9c003087457286f5526481facfcd24b617604353af6a00fb 2023/06/30 01:00:02 270 133002c58d01afd187184bf4b25024d4247c173c01971f8f83409fb1bef8321a 2023/06/09 10:30:05 283 18a75ad87f240ad3e26c337f0e2b5b43008153c2a3e525c99a3f5cca404ba369 2023/06/28 17:05:06 264 19ad146ee7d6075d9450800f8b9bb920b30911c1812590409129eb5fcaa0aba5 2023/07/02 10:10:11 272 1d3adb612e90d6e6eef88d9f2d0d496f231be7dc6befd1da870966da22b42a8a 2023/06/07 10:30:05 282 1e676be243d7dd58bc39182ebb9767ffc8f8b9d49c8d812d343ed838fae76f4e 2023/06/05 01:00:03 268 226adc2d95c43a5c88c894fa93a93f263e1ae80a31b40e4b6f1ce28d50c64979 2023/07/02 15:10:12 274 2541bd2e646a78ab238675d8dc2eec6673cf4eb8354a7e6294e303c470facd07 2023/07/01 10:30:05 282 28d272ef897c18a8baf545a426b48121a085e458dc78f76989200567ce05739d

You can add -s flag, to see the S3 STORAGE CLASS

√ ~ % s5cmd ls -s s3://restic/snapshots/ | head 2023/06/30 17:10:03 STANDARD 263 09c68acfe0cd536c3a21273a7adeee2911f370aa4f12fb9de5d13e1b8a93a7ef 2023/06/18 10:30:05 STANDARD 285 0e6d2982310da04e9c003087457286f5526481facfcd24b617604353af6a00fb 2023/06/30 01:00:02 STANDARD 270 133002c58d01afd187184bf4b25024d4247c173c01971f8f83409fb1bef8321a 2023/06/09 10:30:05 STANDARD 283 18a75ad87f240ad3e26c337f0e2b5b43008153c2a3e525c99a3f5cca404ba369 2023/06/28 17:05:06 STANDARD 264 19ad146ee7d6075d9450800f8b9bb920b30911c1812590409129eb5fcaa0aba5 2023/07/02 10:10:11 STANDARD 272 1d3adb612e90d6e6eef88d9f2d0d496f231be7dc6befd1da870966da22b42a8a 2023/06/07 10:30:05 STANDARD 282 1e676be243d7dd58bc39182ebb9767ffc8f8b9d49c8d812d343ed838fae76f4e 2023/06/05 01:00:03 STANDARD 268 226adc2d95c43a5c88c894fa93a93f263e1ae80a31b40e4b6f1ce28d50c64979 2023/07/02 15:10:12 STANDARD 274 2541bd2e646a78ab238675d8dc2eec6673cf4eb8354a7e6294e303c470facd07 2023/07/01 10:30:05 STANDARD 282 28d272ef897c18a8baf545a426b48121a085e458dc78f76989200567ce05739d

And, there we can see that S3 STORAGE CLASS is STANDARD

k

I think this part of the doc shows that LocationConstraint can override the placement and I can change the placement target with this field. When creating a bucket with the S3 protocol, a placement target can be

provided as part of the LocationConstraint to override the default placement targets from the user and zonegroup.

I just want to get the value that I had set in the create bucket request. Best Regards, Mahnoosh On Mon, Jul 3, 2023 at 1:19 PM Konstantin Shalygin <k0ste@k0ste.ru> wrote:

Hi,

On 3 Jul 2023, at 12:23, mahnoosh shahidi <mahnooosh.shd@gmail.com> wrote:

So clients can not get the value which they set in the LocationConstraint field in the create bucket request as in this doc <https://docs.ceph.com/en/latest/radosgw/placement/#s3-bucket-placement>?

LocationConstraint in this case is a AZ [1], not the placement in Ceph (OSD pool, compression settings)

[1] https://docs.openstack.org/neutron/rocky/admin/config-az.html k