charm-ceph-radosgw/actions.yaml
utkarshbhatthere 44fee84d4d
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:
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.

Closes-Bug: #1959837
Change-Id: I01a4c1c4551c797f0a32951dfbde8a1a4126c2d6
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/840
2022-08-07 13:32:37 +05:30

22 lines
848 B
YAML

pause:
description: Pause the ceph-radosgw unit.
resume:
descrpition: Resume the ceph-radosgw unit.
promote:
description: Promote the zone associated with the local units to master/default (multi-site).
readonly:
description: Mark the zone associated with the local units as read only (multi-site).
readwrite:
description: Mark the zone associated with the local units as read/write (multi-site).
tidydefaults:
description: Delete default zone and zonegroup configuration (multi-site).
force-enable-multisite:
description: Reconfigure provided Zone and Zonegroup for migration to multisite.
params:
zone:
type: string
description: Existing Zone to be reconfigured as the 'zone' config value.
zonegroup:
type: string
description: Existing Zonegroup to be reconfigured as the 'zonegroup' config value.