1.) Currently multi-site can only be configured when system is being
deployed from scratch, migration works by renaming the existing
Zone/Zonegroups (Z/ZG) to Juju config values on primary site before
secondary site pulls the realm data and then rename and configure
secondary Zone accordingly.
During migration:
2.) If multiple Z/ZG not matching the config values are present at
primary site, the leader unit will block and prompt use of
'force-enable-multisite' which renames and configures selected Z/ZG
according to multisite config values.
3.) If the site being added as a secondary already contain Buckets,
the unit will block and prompt the operator to purge all such Buckets
before proceeding.
Reviewed: https:/ /review. opendev. org/c/openstack /charm- ceph-radosgw/ +/848739 /opendev. org/openstack/ charm-ceph- radosgw/ commit/ 44fee84d4d61e8c cda78dfb9afd68e 0048686d4a
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 44fee84d4d61e8c cda78dfb9afd68e 0048686d4a
Author: utkarshbhatthere <email address hidden>
Date: Tue Jul 5 17:27:36 2022 +0530
Adds support for migration to multi-site system.
1.) Currently multi-site can only be configured when system is being
deployed from scratch, migration works by renaming the existing
Zone/Zonegroups (Z/ZG) to Juju config values on primary site before
secondary site pulls the realm data and then rename and configure
secondary Zone accordingly.
During migration: enable- multisite' which renames and configures selected Z/ZG
2.) If multiple Z/ZG not matching the config values are present at
primary site, the leader unit will block and prompt use of
'force-
according to multisite config values.
3.) If the site being added as a secondary already contain Buckets,
the unit will block and prompt the operator to purge all such Buckets
before proceeding.
Closes-Bug: #1959837 7f0a32951dfbde8 a1a4126c2d6 /github. com/openstack- charmers/ zaza-openstack- tests/pull/ 840
Change-Id: I01a4c1c4551c79
func-test-pr: https:/