Hi Shilpa,
Thank you very much for the suggestion.
My understanding of the (admittedly not officially documented) concept
of default_placement should precisely be to act as the name implies if
the client does *not* specify a placement. For my use-case
(multi-tenancy support), relying on tenants to do this would seem rather
counter-productive.
Also my version of Ceph (Firefly) seems to ignore any attempt to specify
a location by the client, per [2]. This appears to have changed in
later versions.
As it happens, I've figured out the cause of my problem; as per the
blog, I relied on 'radosgw reload' to refresh the region. I tried a
stop/start instead and that worked!
Cheers,
Christian
[2] http://docs.ceph.com/docs/v0.80/radosgw/s3/#features-support
On 09/10/15 09:23, Shilpa Manjarabad Jagannath wrote:
[1] http://cephnotes.ksperis.com/blog/2014/11/28/placement-pools-on-rados-gw
When you made a bucket creation request, did you specify the placement-target? I think we need to pass it in the request as well.
From blog[1]:
"Data placement pool is define in this order :
from the request (“bucket location”)
from user (“default_placement” : see with radosgw-admin metadata get user:<uid>)
from region map (“default_placement”)"
Cheers,
Shilpa
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
