RGW at all (re)deploying from scratch

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear list members,

we have a really old prod. cluster, meanwhile running Quincy(cephadm) with
RBD and CephFS very well. :-)

Now we would like to establish S3 object store for a customer, but it seems
that our existing RGW stack of Pools and RadosGateways are somewhat broken
due to lots of Upgrades etc. For instance, if iwetry to create a bucket
with the dashboard...

500 - Internal Server Error
RGW REST API failed request with status code 400
(b'{"Code":"InvalidLocationConstraint","Message":"The specified
location-constr' b'aint is not
valid","BucketName":"test23","RequestId":"tx00000b9944347834bd4b'
b'6-006369283b-53efce9-default","HostId":"53efce9-default-default"}')



Because we actually *do not use* RGW, are we fine to remove RGW services
and all originally created  "rgw" pools?

.rgw.root
default.rgw.control
default.rgw.meta
default.rgw.log
default.rgw.buckets.index
default.rgw.buckets.data

Is it right that all required pools for the "default" zone(group) will be
created "from scratch" if the first rgw daemon is deployed?

Thanks for any explanation
Christoph Ackermann
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux