I am using the official ceph/daemon docker image. It starts RGW and
creates a zonegroup and zone with their names set to an empty string:
$RGW_ZONEGROUP and $RGW_ZONE are both empty strings by default:
Here's what I get when I query RGW:
$ radosgw-admin zonegroup list
$ radosgw-admin zone list
On 20/02/2018 10:33 AM, Yehuda Sadeh-Weinraub wrote:
What is the name of your zonegroup?
On Mon, Feb 19, 2018 at 3:29 PM, F21 <f21.gro...@gmail.com> wrote:
I've done some debugging and the LocationConstraint is not being set by the
SDK by default.
I do, however, need to set the region on the client to us-east-1 for it to
work. Anything else will return an InvalidLocationConstraint error.
On 20/02/2018 8:40 AM, Yehuda Sadeh-Weinraub wrote:
Sounds like the go sdk adds a location constraint to requests that
don't go to us-east-1. RGW itself is definitely isn't tied to
us-east-1, and does not know anything about it (unless you happen to
have a zonegroup named us-east-1). Maybe there's a way to configure
the sdk to avoid doing that?
On Sun, Feb 18, 2018 at 1:54 PM, F21 <f21.gro...@gmail.com> wrote:
I am using the AWS Go SDK v2 (https://github.com/aws/aws-sdk-go-v2) to
to my RGW instance using the s3 interface. I am running ceph in docker
the ceph/daemon docker images in demo mode. The RGW is started with a
zonegroup and zone with their names set to an empty string by the scripts
I have ForcePathStyle for the client set to true, because I want to
all my buckets using the path: myrgw.instance:8080/somebucket.
I noticed that if I set the region for the client to anything other than
us-east-1, I get this error when creating a bucket:
InvalidLocationConstraint: The specified location-constraint is not
If I set the region in the client to something made up, such as "ceph"
the LocationConstraint to "ceph", I still get the same error.
The only way to get my buckets to create successfully is to set the
region to us-east-1. I have grepped the ceph code base and cannot find
references to us-east-1. In addition, I looked at the AWS docs for
calculating v4 signatures and us-east-1 is the default region but I can
that the region string is used in the calculation (i.e. the region is not
ignored when calculating the signature if it is set to us-east-1).
Why do my buckets create successfully if I set the region in my s3 client
us-east-1, but not otherwise? If I do not want to use us-east-1 as my
default region, for example, if I want us-west-1 as my default region,
should I be configuring in ceph?
ceph-users mailing list
ceph-users mailing list