Skip to content

Latest commit

 

History

History
98 lines (71 loc) · 3.57 KB

README-MULTISITE.md

File metadata and controls

98 lines (71 loc) · 3.57 KB
Raw

RGW Multisite

Directions for configuring the RGW Multisite support in ceph-ansible

Requirements

  • At least 2 Ceph clusters
  • 1 RGW per cluster
  • Jewel or newer

More details:

  • Can configure a Master and Secondary realm/zonegroup/zone on 2 separate clusters.

Configuring the Master Zone in the Primary Cluster

This will setup the realm, zonegroup and master zone and make them the defaults. It will also reconfigure the specified RGW for use with the zone.

``

  1. Generate System Access and System Secret Keys
echo system_access_key: $(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 20 | head -n 1) > multi-site-keys.txt
echo system_secret_key: $(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 40 | head -n 1) >> multi-site-keys.txt
  1. Edit the all.yml in group_vars
copy_admin_key: true
# Enable Multisite support
rgw_multisite: true
rgw_zone: jupiter
rgw_zonemaster: true
rgw_zonesecondary: false
rgw_multisite_proto: "http"
rgw_multisite_endpoint_addr: "{{ ansible_fqdn }}"
rgw_multisite_endpoints_list: "{{ rgw_multisite_proto }}://{{ ansible_fqdn }}:{{ radosgw_frontend_port }}"
rgw_zonegroup: solarsystem
rgw_zone_user: zone.user
rgw_realm: milkyway
system_access_key: 6kWkikvapSnHyE22P7nO
system_secret_key: MGecsMrWtKZgngOHZdrd6d3JxGO5CPWgT2lcnpSt

Note: rgw_zonemaster should have the value of true and rgw_zonesecondary should be false

Note: replace the system_access_key and system_secret_key values with the ones you generated

Note: ansible_fqdn domain name assigned to rgw_multisite_endpoint_addr must be resolvable from the secondary Ceph clusters mon and rgw node(s)

Note: if there is more than 1 RGW in the cluster, rgw_multisite_endpoints needs to be set.
rgw_multisite_endpoints is a comma seperated list, with no spaces, of the RGW endpoints in the format:
{{ rgw_multisite_proto }}://{{ ansible_fqdn }}:{{ radosgw_frontend_port }}
for example: rgw_multisite_endpoints: http://foo.example.com:8080,http://bar.example.com:8080,http://baz.example.com:8080

  1. Run the ceph-ansible playbook on your 1st cluster

Configuring the Secondary Zone in a Separate Cluster

  1. Edit the all.yml in group_vars
copy_admin_key: true
# Enable Multisite support
rgw_multisite: true
rgw_zone: mars
rgw_zonemaster: false
rgw_zonesecondary: true
rgw_multisite_proto: "http"
rgw_multisite_endpoint_addr: "{{ ansible_fqdn }}"
rgw_multisite_endpoints_list: "{{ rgw_multisite_proto }}://{{ ansible_fqdn }}:{{ radosgw_frontend_port }}"
rgw_zonegroup: solarsystem
rgw_zone_user: zone.user
rgw_realm: milkyway
system_access_key: 6kWkikvapSnHyE22P7nO
system_secret_key: MGecsMrWtKZgngOHZdrd6d3JxGO5CPWgT2lcnpSt
rgw_pull_proto: http
rgw_pull_port: 8080
rgw_pullhost: cluster0-rgw0

Note: rgw_zonemaster should have the value of false and rgw_zonesecondary should be true

Note: rgw_pullhost should be the rgw_multisite_endpoint_addr of the RGW that is configured in the Primary Cluster

Note: rgw_zone_user, system_access_key, and system_secret_key should match what you used in the Primary Cluster

Note: ansible_fqdn domain name assigned to rgw_multisite_endpoint_addr must be resolvable from the Primary Ceph cluster's mon and rgw node(s)

Note: if there is more than 1 RGW in the Secondary Cluster, rgw_multisite_endpoints needs to be set with the RGWs in the Secondary Cluster just like it was set in the Primary Cluster

  1. Run the ceph-ansible playbook on your 2nd cluster

Conclusion

You should now have a master zone on cluster0 and a secondary zone on cluster1 in an Active-Active mode.