You need separate pools for the different zones, otherwise both zones will
have the same data.
You could use the defaults for the first zone, but the second zone will
need it's own. You might as well follow the convention of creating
non-default pools for the zone.
This is all semantics, but re
So I really need to create the region also? I thought it was using the
default region, so I didn't have to create extra regions.
Let me try to figure this out, the docs are a little bit confusing.
Marco Garcês
On Thu, Nov 6, 2014 at 6:39 PM, Craig Lewis wrote:
> You need to tell each radosgw d
You need to tell each radosgw daemon which zone to use. In ceph.conf, I
have:
[client.radosgw.ceph3c]
host = ceph3c
rgw socket path = /var/run/ceph/radosgw.ceph3c
keyring = /etc/ceph/ceph.client.radosgw.ceph3c.keyring
log file = /var/log/ceph/radosgw.log
admin socket = /var/run/ceph/rado
Update:
I was able to fix the authentication error, and I have 2 radosgw
running on the same host.
The problem now, is, I believe I have created the zone wrong, or, I am
doing something wrong, because I can login with the user I had before,
and I can access his buckets. I need to have everything s
By the way,
Is it possible to run 2 radosgw on the same host?
I think I have created the zone, not sure if it was correct, because
it used the default pool names, even though I had changed them in the
json file I had provided.
Now I am trying to run ceph-radosgw with two different entries in the
Your solution of pre-pending the environment name to the bucket, was
my first choice, but at the moment I can't ask the devs to change the
code to do that. For now I have to stick with the zones solution.
Should I follow the federated zones docs
(http://ceph.com/docs/master/radosgw/federated-config
You could setup dedicated zones for each environment, and not
replicate between them.
Each zone would have it's own URL, but you would be able to re-use
usernames and bucket names. If different URLs are a problem, you
might be able to get around that in the load balancer or the web
servers. I wo
