Documentation #26997

doc: federated architecture link broken on doc/master/radosgw

Added by James McClune over 4 years ago. Updated about 4 years ago.

Target version:
% Done:


Affected Versions:
Pull request ID:


The federated architecture link is broken (404 error) on doc/master/radosgw.

There's no section on federated architecture for versions above Jewel. If my understanding is correct, multisite configurations
replace the federated architecture terminology.


A federated Ceph Object Gateway configuration means that you run a Ceph Object Storage service in a geographically distributed manner for fault tolerance and failover.

When you deploy a Ceph Object Store service that spans geographical locales, 
configuring Ceph Object Gateway regions and metadata synchronization agents enables the service to maintain a global namespace, 
even though Ceph Object Gateway instances run in different geographic locales and potentially on different Ceph Storage Clusters.


Multi-zone-group: Formerly called ‘regions’, Ceph Object Gateway can also support multiple zone groups, each zone group with one or more zones. 
Objects stored to zones in one zone group within the same realm as another zone group will share a global object namespace, 
ensuring unique object IDs across zone groups and zones.

The Ceph Object Gateway supports multi-site deployments and a global namespace by using the notion of zone groups. 
Formerly called a region in Infernalis, a zone group defines the geographic location of one or more Ceph Object Gateway instances within one or more zones.

In my eyes, if I wanted to create a fault-tolerant Ceph object store (radosgw), I would create two Ceph storage clusters and distribute them geographically (each cluster would be in a zone).
The two zones would then be in a multi-zone group (formerly region). One would be a primary object store, the other would be a secondary.
Being that the primary and secondary stores are in the same zone group, the data should replicate across the two object stores (sharing global namespace).
If the primary would fail, the secondary could take its place.

Like this:


#1 Updated by James McClune over 4 years ago

I opened a pull request to resolve this:

#2 Updated by Nathan Cutler over 4 years ago

  • Status changed from New to Fix Under Review

#3 Updated by James McClune about 4 years ago

This issue is now resolved. PR #23660 has been merged (

#4 Updated by Marcos de Souza about 4 years ago

James McClune wrote:

This issue is now resolved. PR #23660 has been merged (

So, if the patch was merged, can this bug be closed?

#5 Updated by James McClune about 4 years ago

Yes, I don't have the rights to change status.


#6 Updated by Nathan Cutler about 4 years ago

  • Status changed from Fix Under Review to Resolved

Also available in: Atom PDF